Troubleshooting
Problem
Data is not correctly loaded when the BAPI stage connects to a non-unicode SAP Server. No errors are reported by the job. The issue happens for both the passive and the active scenario. No issues when connecting to a unicode SAP Server.
Resolving The Problem
The issue is caused by a negative side effect of code fix for APAR JR36363 (BAPI stage performance enhancement): truncation of internal strings, as shown in the temporary BAPI log files. It was introduced in FixPack 1 for Pack for SAP R/3 6.5 (6.5.0.1) and it's present also in FixPack 2 (6.5.0.2) as well as in Pack for SAP Applications 7.0.
A code fix was made under APAR JR45061 and a patch can be requested from Support by opening a PMR.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21625681