Solution : https://service.sap.com/sap/support/notes/375886 (Connexion à SAP Service Marketplace requise)
Résumé :
This SAP Note addresses issues reported by customers regarding the use of BAPIs for purchasing functions. It provides a methodology for the SAP Support Team to effectively analyze and reproduce the issues. Steps include creating replicable test data in SE37, clearly documenting how the BAPI interface was populated, utilizing RM06HL35 report to aid data transfer, and referencing other pertinent Notes for quicker resolution and understanding of BAPI functionalities. Additional guidance is given on handling BAPI_PO_CREATE1 and BAPI_PO_CHANGE regarding value transfers to applications and the avoidance of direct COMMIT WORK statements within BAPIs.
Mots Clés :
sap easy access undernode tools > business framework, find general information, required entry field, commit work statements, create test data, test data directory, bapis purchase requisition, sap support team, sap test system, symptom efficient processing
Notes associées :
| 539978 | Automatic generation of BAPI test data directory |
| 517767 | Generate test data for function modules |
| 499626 | FAQ: BAPIs in the service procurement |
| 420646 | EnjoySAP purchase orders via BAPI not updated in SE37 |
| 335720 | SE37: Upload of test data in customer message (RM06HL35) |
| 197958 | BAPIs for purchase orders: Missing functions |
| 197048 | Advance clarification in purchasing (MM-PUR) |