Solution : https://service.sap.com/sap/support/notes/509898 (Connexion à SAP Service Marketplace requise)
Résumé :
Transfer errors can occur when using the BAPI customer enhancement concept with Unicode and non-Unicode systems due to the handling of non-character-like additional customer data. The original documentation did not fully address the issue of data type compatibility. To remedy this, users must define their own data structures in character-like formats for inbound and outbound data (ExtensionIn and ExtensionOut parameters), ensuring correct mapping and conversion processes between these custom structures and the structure BAPIPAREX. Additionally, the structure S2 should contain character-like representations of the data fields, which can be mapped back and forth to the original data format S1, and due diligence is required when non-standard data types are used, as modifications in the supplied source code might be necessary for accurate data transfer.
Mots Clés :
sap-designed bapi table extensions, symptom transfer errors occur, bapi table extension concept, bapi customer enhancement concept, sap-designed processing, bapi table extension, customer exits / badis, additional mapping step, actual data type, data record x1
Notes associées :
| 1446967 | FMMC against PRs abrupts with NOT_REGISTERED |
| 1393723 | CNIF_PI: Syntax Error with non char fields in CI structures. |
| 1346636 | SSR Reconciliation upload: IDoc extensionin is not processed |
| 1319517 | Unicode Collection Note |
| 1166092 | BAPI_INTERNALORDER_CREATE: Packed fields |
| 637345 | Syntax error with enhanced PS tables (Unicode) |
| 582221 | FAQ: BAPIs for purchase orders |
| 550431 | FAQ: BAPI in sales - general questions |
| 143580 | Information on SD BAPIs and customer enhancement concept |