Solution : https://service.sap.com/sap/support/notes/399791 (SAP Service marketplace login required)
Summary :
In SAP environments, issues are observed with BAPI_PO_CREATE1 and BAPI_PO_CHANGE where entered conditions are not transferring correctly. Specifically, with BAPI_PO_CREATE1, the system fails to transfer the values, while BAPI_PO_CHANGE results in deletion of existing conditions not explicitly reassigned. This is problematic especially when integrating external system data. To rectify, implement corrections as per your release which will ensure conditions from price determination and interface are managed correctly and not merely replaced. Additional functionality in Release 4.7 improves merging of conditions. Support Package SAPKH46C22 resolves the problem of external number assignment error with message 06 243.
Key words :
internal number assignment, document number reason, function modules rv_konv_select, external number assignment, system displays message 06 243, support package sapkh46c22, terms purchase order, oryou assign conditions, merge existing conditions, purchase order
Related Notes :
| 622634 | BAPI_PO_CHANGE: New PD despite follow-on documents |
| 580225 | Purchasing BAPIs: Conditions and pricing |
| 571860 | BAPI_PO_CREATE1: Price is not transferred |
| 439110 | Enjoy PO BAPI: Conditions |
| 428621 | EnjoySAP purchase order BAPIs - price det. & cond. change |
| 425996 | BAPI_PO_CREATE1: Termination msge 00151 w/ header conditions |
| 383975 | ME21N: Fixed exchange rate is copied from contract |
| 197958 | BAPIs for purchase orders: Missing functions |