Solution : https://service.sap.com/sap/support/notes/584902 (SAP Service marketplace login required)
Summary :
In the function module BAPI_REQUISITION_CHANGE, there is an issue where customer-provided data passed through the ExtensionIn structure for CI_EBAN (item data) and CI_COBL (account assignment data) does not reflect in the purchase requisition. To resolve this, customer-specific fields need to be solely transmitted using the ExtensionIn structure as mixing old and new data is technically unsupported. Additionally, the ALE interface won't accommodate dynamic regeneration for PurchaseRequisition.Change operations. A workaround involves modifying the method in the Business Object Repository by cloning BUS2105 to a custom object ensuring only compatible data types are used in ExtensionIn.
Key words :
ale message type preqch, data type char fields, user-defined fields, account assignment data, bapi_requisition_create function module, business object repository, business object bus2105, similar data types, standard table fields, bapi_requisition_change function module
Related Notes :
| 792132 | EBAN, EBKN: user-defined fields are not filled |
| 499627 | FAQ: BAPIs for purchase requisitions |
| 485557 | BAPI_REQUISITION_CREATE: 'EXTENSIONIN' customer enhancements |