Here we would like to draw your attention to the VA33 transaction code in SAP. As we know, it is used in the SAP SD-SLS (Sales in SD) component, which is part of the SD (Sales – Distribution) module. VA33 is a booking code used for SAP`s delivery plan. The framework agreement is a long-term sales contract between Kreditor and Debitor. The configuration agreement is of two types: check the possible menu paths to access the same report without entering the transaction code. Path 1Logistics → materials industry → foreign trade/customs → general processing of foreign trade → environment → distribution – Export → sale → display contract → Display contract The contract is a draft contract and does not contain delivery dates for the equipment. The contract consists of two types: Here, you can see that no value has been updated in the net worth field in the top part of the delivery plan: Net value is null Populate Delivery Plan Validity Dates, i.e. “Validate” and “Valid until” Date: Enter the validity dates of the delivery plan A calendar agreement with valid dates properly completed There are two options to start the process of creating a plan. Some suggestions/requests: `Menu path to VL10A would help, as it is completely different from other SD menu paths tutorials. A little more explanation on the list of delivery would help – i.e.
delivery on the 10th green watch (which I guess, meant), while on the 4th amber (which I guess is going on). How was the position for the 4th displayed in the delivery plan? This part is not clear. Did the system enter it? You see here that the Ship-to Party A7000 has two deliveries that oppose the delivery plan number 30000053 that we have created before. These deliveries are due on November 4, 2016 and November 10, 2016, respectively. Appointment lines in the press entry of the delivery plan, once you have selected the part sold to allow the SAP system to accept the debitor and proceed with the development of the delivery plan.