Solution : https://service.sap.com/sap/support/notes/439390 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues associated with the application of BAPIs across various APO releases. Key concerns include unexpected error messages despite correct data entries through BAPIs or their function modules, uncertainties about available BAPIs per APM release, and difficulties understanding field requirements and accessing proper documentation. Solutions offered involve ensuring all relevant fields are filled, recognizing the internal versus external key dependencies, using correct GUID specifications, and confirming logical system definitions for object identification. Guidance is also provided on using transaction BAPI for exploring available BAPIs, and the need for external COMMIT control handling is highlighted. Furthermore, the note discusses potential discrepancies in function results when BAPIs are tested in different environments, such as SE37 versus ALE/IDOC interfaces, emphasizing the importance of context-specific data and parameter handling.
Key words :
exist/sapapo/mat 040 /sapapo/loc 040 059 /sapapo/cif 003 reason, terms location product resource ppm plan order, normal bapi table parameter, relevant required entry fields, transaction /sapapo/c3, ale/idoc interfaces, found simply due, valid selection combination, valid selection combinations, ale/idoc interface
Related Notes :
| 568955 | Incorrect entries RETURN parameter of "RequestList" method |
| 541268 | Additional checks in "GetList" BAPIs |
| 520161 | Transaction behavior/COMMIT control of BAPIs in APO |