Solution : https://service.sap.com/sap/support/notes/552189 (SAP Service marketplace login required)
Summary :
This SAP Note addresses limitations in BAPI_PO_CREATE1 and BAPI_PO_CHANGE where technical fields such as message determination and rounding deactivation could not be adjusted. New interfaces and table definitions must be implemented. It's recommended to incorporate these changes through a support package for ease. Manual implementation involves defining new import parameters and attributes for message control, authorization checks, and price sourcing. These extensions apply to multiple related structures and require precise correlation to existing data types. The provided correction instructions must be followed meticulously to ensure system compatibility and functionality.
Key words :
class cl_po_header_handle_mm attribute type visibility type spec, no_price_from_po instance public type mmpur_bool 3, no_messaging instance public type mmpur_bool, no_message_req instance public type mmpur_bool, no_authority instance public type mmpur_bool, im_no_messaging type xfeld, im_no_message_req type xfeld, im_no_authority type xfeld, im_no_price_from_po type xfeld, component component type
Related Notes :
| 1225535 | BAPI_PO_CHANGE Pricing with B changes price after GR IR |
| 842320 | BAPI_PO_CREATE1: Authorization check on PReq |
| 797454 | BAPI_PO_CHANGE Technical fields overwritten with space |
| 658590 | Mobilization item triggers messaging |
| 639739 | EnjoySAP order BAPI: Rounding is not executed |
| 614936 | ME21N: Info update indicator set in spite of default value |
| 586672 | Automatic rounding for purchase order change in WWP1 |
| 580225 | Purchasing BAPIs: Conditions and pricing |
| 561221 | ME25: Checking the EFB parameter with call of ME21N |
| 494759 | BAPI_PO_CREATE1 and BAPI_PO_CHANGE: This is due to a redesig |