You are currently working with the following scalability field (YY1_SD_DS): For 3 individual positions, the delivery schedule is 0000 02/08/2008 . 2 other items, the delivery plan 05/07/2008 . because of these different delivery plans for the posts in the delivery plan. Each time the user creates the delivery, the distribution of transmissions takes place. Because of these different requirement dates, there is always a sharing of deliveries. In addition to the fields described above, you can use the Description field to manage the information to identify a delivery plan. For example, a car manufacturer in North America could enter the model year of a given series. I can ask you to help me solve this problem pls. The user wanted it to be a single delivery.

Should I expect the system, if the delivery date is a non-working day, to postpone it to the next work date? – Calendar line with date, time and quantity of order If the user changes this delivery plan for these items, there are effects in ?. How to proceed from here depends on whether you want to manually enter delivery plans with classifications. In each delivery plan, you will find two calendars, i.e. JIT forecasts and calendars. calendars you have on JIT can be converted into deliveries. In my opinion, if you only have one calendar, you can only create one delivery. In general, these schedues are automatically downloaded when you use IDOCs. When debtors update the next delivery plan, the value of the Expandable field will not be updated in the sales delivery plan. You can try to create a computational profile and add it to the order cycle, allowing you to calculate the delivery time for release using factory production days rather than regular calendar days. we do, but right now we still use orders, not delivery plans, but should work? If the user agrees with this, you can ask the user to change the date of the schedule to avoid distribution. The other option is to re-plan with t.code V_V2 so that quantities are confirmed based on the priority and availability of the hardware. We don`t need to change the calendar lines.

Calendar positions are managed in ME38 and we need to share a delivery plan established in MM in ME31L for the outsourcing process. – Rounding quantity (Fill this amount to round up the delivery volume during shipping, so that complete shipping units are created during packing.) You`re absolutely right. Don`t forget that you are scheduled for the delivery plan. Delivery plans are drawn up by MRPor Kanban or the user. In this case, I use kanban to create delivery plans; The problem is to update the ME38/EKES delivery plan. No alerts or error messages yet. 1. As far as I know, these delivery plans were mentioned in the development of this delivery plan. Subsequently, no updates were made for the delivery plans. Elements of the EDI delivery plan: SchedulingAgrement/PurchasingScheduling, SchedulingAgreement/MatlUsageIndicator, SchedulingAgreement/SalesItemProposalDescription, Article/Product/BuyerProductID, Item/PurchasingUnloadingPoint (Unseen, Party/BuyerPartyID (PartyType – `DepartResp`), Item/PurchasingReceivingPlant (If not sent, Party/BuyerPartyID (PartyType – `Plant`), Party/PartyType (`Provider`), Party/BuyerPartyID