I haven`t done it myself yet for contracts or appointments, but a colleague has used it. I supported it. Therefore, this type of delivery plans cannot be This structure must be filled with head level data of the delivery plan to be established. „Delivery plans at time-independent terms are not supported“ BAPI_SAG_CHANGE (and BAPI_SAG_CREATE) can only process the schedule A delivery plan is a framework contract between a supplier and a customer. A sales plan (not to be confused with the purchase plan) is a long-term sales contract that contains the details of the delivery plan and deliveries to the customer are made according to the schedule provided in the document. the error message MEOUT019: „Delivery plans with This table must be filled in to fill in the Z fields at the head or position of the distribution agreement. [Note that the LPA document type cannot be created with this BAPI. Error delivery plans with time-independent conditions are not supported. Check the SAP note 1046794] The delivery plan (SA) is a form of framework contract in which materials are purchased on predefined dates within a set period of time. It consists of a number of positions and a purchase type is defined for each item. Agreements with time conditions. The conditions of proof are not the article that describes the procedure for setting up or modifying delivery plans with BAPI_SAG_CREATE or BAPI_SAG_CHANGE. You want to change a delivery plan on BAPI_SAG_CHANGE and the delivery plan is returned in the import setting SALESDOCUMENT_EX and if the RETURN table does not contain error or cancellation messages, BAPI_TRANSACTION_COMMIT is called.
BAPI_SAG_CREATE you can create a delivery plan. The BAPI uses the technology behind the creation transaction OF SA (ME31L). The parameters of this table to be filled in are: i. Take a variable, say w_last_item, add its 00010 for the position number. Move this value into ITEM_INTVL field. . SAP COMMUNITY NETWORK SDN – sdn.sap.com | BPX – bpx.sap.com | BOC – boc.sap.com · Improve BAPE_VBAPX by adding a structure (ZMSOTC_LIFNRX) that contains two flag fields – ZZMTLIFNR (unique character) and ZZMTIDNEX (unique character). . . .