You can see the “Sell the Party” and “Ship-to Party” fields at the top left of the screen. A sold party can have several ship-to-parties. If many ship-to-parties are linked to a sold part, a dialog box appears on the delivery plan screen. You must choose the relevant ship-to-party to which the selling party ordered you to ship the products. Press F4 or the button in the Sold field to search for your relevant sold part. After setting the types of documents for delivery plans, select the line for the type of document and double-click on Authorized Item Categories. Manage on the screen Categories of items allowed for The category of articles, as shown in the following table. These categories of items can be configured to meet business requirements. This configuration determines the categories of items that can be selected by the user when developing the delivery plan for a specific use site. Fill out the validity dates of the delivery plan, i.e.
“Validate” and “Valid until” date: enter the validity dates of the delivery plan A delivery agreement with valid dates duly completed Note that this process flow uses the delivery plans as an example. External agent documents and self-billing documents sent by EDI are treated in the same way. You first created the plan aggregate file and, when increasing a sales order, in reference to the appointment agreement. appointment dates will be automatically taken into account in the market. then you can make the delivery easily. (vl01n) Very good information on this forum on the delivery plan We have problems when we try to use this API to create outbound deliveries from a sales delivery plan. Well-written tutorial. 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? The following basic data are involved in the development of a delivery plan.
This basic data retrieves relevant information and fills in the relevant fields accordingly: The customer usually sends multiple hardware numbers and corresponding calendar lines into a delivery plan. There are two ways to start the process of developing a delivery plan: as the delivery plan contains the delivery dates and quantities, deliveries are made according to the quantity delivered. Let`s first look at the details of the delivery in the delivery plan: Details of the delivery in the delivery plan Step 1: Preparing the delivery to the factory B. This is done via tx VL10B, delivery is created with the reference to the purchase of sched.agreement. Step 2: Reservation of the goods exit for delivery via tx VL06 – the material is transferred to the transit stock of factory B (mov.type 641) Step 3: Reservation of the receipt of goods in factory B above tx MIGO – here we use the goods entry for delivery (R05) Check the type of delivery you have chosen in VL01N. Also check the copy order element between the type of planning contract and the type of delivery in VTLA. I think there is probably a configuration to purchase>Reconfirmation and then the STO must be created with the correct confirmation control key. However, most of the work is an evolution that reads the corresponding product issues and then establishes deliveries. We have our own development some time ago, but there are several OSS notes, for example 497287 – 591860, that discuss how to do with the workflow on the issue of goods. A delivery plan is a framework agreement between you and a saleable party valid for a specified period of time. The delivery plan contains fixed delivery dates and quantities.
These dates are included in the delivery plan classifications.