Scheduling Agreement For Subcontracting

Then create the reference agreement with the “L” position category in ME31L First, Create the delivery plan in ME31L for a lender with material, quantity, validity and item category that Someone can explain the delivery agreement process with the external work scenario, Componenets assignment, component output, etc. and then GR will be executed for the expected quantity relative to the delivery plan The use of delivery plans can reduce processing times and reduce the paperwork you are facing. A delivery plan can replace many discrete orders or devotional orders. I have concluded an appointment in which the article that I will call subcontracting (c-ategory-20 L) and, in the strain of the material, I define the type of specific supply: As usual, since I set the schedule, I put the compass. In the screen on which I insert the components, there are 2 dates, one is for date of 1st, which is the date on which the material is to arrive at our compass, and 20 is the application date which, according to the documentation, must be the date on which the sub-component is the “meet-20” required by the seller. The delivery date for the parent material.-20 My questions are:-20 According to the documentation, the request/sharing date is calculated by `Have you thought about the calendar factor, because the data always depends on calendars. looksNaval – “ via sap-r3-log” writes:> Supply chain information review – >> > dear sapiens experts, > > I made an appointment here that marks Article I> as a subcontractor (category > L), and in the strain of the material, I define the specific type of supply>: > subcontract. As usual, as I maintain the schedule, I > enter the components. In > screen, there are 2> data, one is for delivery > date the equipment is to arrive> and > other is the application date> which must be the documentation > > the date on which the sub-component is required by the supplier> to complete > delivery date of the starting material. > My questions are: > According to the documentation, the > requirement date is calculated after > delivery date with scheduled delivery date> date, processing of purchases > time, and so on according to the normal disposition procedure.> According to logic, as I > the delivery date, for example, 9.10,11,12> and then according to the formula > the application date should be (for example> (assuming the > time is 6 days), but the system> calculates the application date > 3,3,3,4, which doesn`t really make sense to me> because if the delay > considered the only factor, at least all the data > should be > different, right? > > Can I be helped here….. if I missed something> something….