Originally posted by: paul.brett
As you may know, the WTX/ITX BAPI adapter that comes with the TX Pack for SAP R/3 doesn't do Unicode very well, whilst SAP is now quite happy with it.
...
Two simple steps to convert a BAPI map to work with JBAPI instead. Review the attached example for additional help.
1. Re-import the BAPI Typetree using the UNICODE option:
2. Alter your rule to call the JBAPI adapter instead of BAPI and make sure that you change PACKAGE() to CPACKAGE() with the "Native" qualifier, to ensure data is kept Unicode throughout:
= VALID( GET("BAPI","-C 800 -U user -P password -H saphost.domain.com -S 01 -TV bapi_trace.txt",PACKAGE(BAPI)),FAIL( "Get BAPI failed with code " + LASTERRORCODE() + ": " + LASTERRORMSG()))
to
= VALID( GET("JBAPI","-C 800 -U user -P password -H saphost.domain.com -S 01 -TV bapi_trace.txt",CPACKAGE(BAPI,"Native")),FAIL( "Get BAPI failed with code " + LASTERRORCODE() + ": " + LASTERRORMSG()))
And that should do it!
Thank-you.
Paul.
Follow me on Twitter
#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender#DataExchange