Preventive Service Planning
Abstract
Use the links in the following table to find detailed information about the fixes and enhancements included in InfoSphere Information Server Pack for SAP Applications version 7.1.
Content
| APAR | Summary |
| JR31843 | The ABAP code does not stop processing if a job is aborted |
| JR41763 | The IDoc Load stage cannot process IDocs with an empty SAP release value |
| JR41863 | ABAP RFC Extract: When a job aborts or is stopped forcefully by the user, the background job cleanup is not performed |
| JR42181 | If the ABAP program is re-generated, the summarized length of all columns of the table in an ABAP code is doubled |
| JR42343 | The BAPI stage fails to create the log folder on Windows |
| JR42353 | When multiple jobs run concurrently, the ABAP stage that is using the RFC transfer method fails to delete the RFC destination |
| JR42396 | The IDoc Load stage does not set the control record correctly |
| JR43161 | A BAPI job with a large number of records aborts |
| JR43304 | When a job follows another ABAP job, it sporadically finishes without processing data |
| JR43704 | An ABAP Extract job that is using the qRFC data transfer method hangs during execution. This error was introduced with JR43304 |
| JR43947 | The French version of StageDsc.xml in abappack.jar is invalid |
| JR44053 | The BAPI return log file on a Windows 2008 server contains line breaks in UNIX format |
| JR44092 | Improve extract performance and transaction stability in the ABAP Extract stage |
| JR44112 | The CPI-C to RFC migration tool does not open in InfoSphere Information Server version 9.1 |
| JR44296 | The Segment hierarchy of loaded IDocs is broken |
| JR44462 | The ABAP stage displays the following warning in the job log: An error occurred deregistering the RFC destination. SAP message: 'NOT_AVAILABLE' |
| JR44601 | (Combined IS + SAP Pack patch) Initialization fails on conductor node if a job contains multiple Java-based connector stages |
| JR45061 | A non-Unicode BAPI load job completes without any errors, but writes corrupt data to the target |
| JR45207 | The BAPI stage does not handle binary data correctly |
| JR45242 | Received IDocs are not processed in Test Mode |
| JR45338 | The ABAP Stage Extract binary columns are in binary representation instead of hexadecimal |
| JR45704 | The ABAP stage produces a memory error if it is unable to read the RFC Queue property; the job aborts with an unknown exception |
| JR46061 | An ABAP Extract job aborts with error message "exception from runLocally()" |
| JR46074 | The transport files generated by non-unicode SAP 4.7 that are included in the Pack for SAP Applications version 7.0 are incompatible with SAP 4.6C |
| JR46380 | The IDoc Listener Manager fails to start |
| JR46514 | Pressing the "Browse for IDoc" button in the IDoc Extract or Load stage UI produces an error |
| JR46563 | SAP metadata imported using InfoSphere Rapid Modeler for SAP Applications is corrupted |
| JR46910 | The BAPI stage crashes due to missing column description on table parameter |
| JR47037 | Improve generated ABAP code with exception detection and keep alive statements |
| JR47151 | When ABAP RFC job are migrated from a non-Unicode SAP server to unicode, the column length values are not updated correctly |
| JR47196 | In the ABAP stage during RFC data transfer in the background mode, the SAP job fails to get deleted after several retries |
| JR47408 | The CPI-C to RFC migration tool cannot connect to Information Server when SSL is activated |
| JR47532 | In InfoSphere Rapid Generator, attempting to validate the SAP settings leads to an empty result window |
| JR47834 | IDoc Connector stage fails to open, error message is "Failed to create tab page: VMDataStage.CCustomStage.SAPIDocExtractConnector.IDocTypePg..." |
| JR48072 | When multiple ABAP RFC stages run simultaneously, some jobs might incorrectly detect that they are running on non-master nodes |
| JR48495 | When multiple ABAP RFC stages run simultaneously and the SAP server is under load, some of the stages might not extract complete data |
| JR48601 | The ABAP stage does not handle errors related to creation of RFC destination correctly |
| JR48669 | The ABAP code generator in the ABAP Stage creates erroneous code when regenerating the ABAP program |
| JR49136 | In the ABAP code, when a job parameter is used in IN condition, an invalid parameter section name is generated |
| JR49344 | The IDoc Listener cannot connect to SAP in a load balanced configuration |
| JR49370 | The FTP data transfer in the ABAP stage times out on small files |
| JR49524 | The CPI-C to RFC migration tool does not list jobs when Information Server uses an Oracle database |
| JR49536 | The IDoc Cleanup Tool in SAP Pack V7 incorrectly deletes IDocs created with Pack V6.5 |
| JR49625 | The ABAP stage Extraction Object does not allow job parameters for more than one IN operator |
| JR49652 | The ABAP stage with RFC data transfer aborts with SIGTERM on Windows |
| JR49695 | The IDoc Connector load stage aborts with a null pointer exception error message |
| JR50101 | ABAP stage with RFC data transfer: Reintroduce individual transactions for the ABAP program as separate unit to enable extraction of DataStage rows as soon as the SELECT statement is completed in SAP |
| JR53184 | BAPI Stage cannot handle empty numeric (NUMC) values |
| JR55712 | IDoc Extract version 7.0 job fails on account of new line character received in IDoc Segment Data from SAP |
[{"Product":{"code":"SSZJPZ","label":"IBM InfoSphere Information Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Pack for SAP Applications","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1","Edition":"Edition Independent","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21667687