I have a few delivery plans for next week and one for next month. I`m trying to create a JIT delivery authorization for the 3 planning lines. I run ME84 without restrictions and without verification of the creation profile. However, the release will only be executed in January for both schedule lines. It is as if the system, although it does not check the creation profile, limits the release to m. A) as a generic term for different types of procurement documents issued under framework contracts (these may be declassification contracts awarded against contracts or, as here, delivery plan deposits, i.e.B. The types of rolling delivery plans that have been established against delivery contracts) and iam establish a planning agreement with LPDocument r LPA, so if I have established in the me38 shedules r like this 1.02.2007 5.02.2007 6.02.2007 that these shedules are there, but the customer`s requirement is that today they need material for production or some work of Repeir, etc. to get this material before the scheduled delivery date Example calendar date is 01.02.2007, but companies need materail on today means 31.01.2007 how you are going to do or get Materail please explain to me The default settings of the MIGO transaction should be set as “always show all items”. With this parameter, the MIGO shows you all the points of your calendar, even if the date of your ranking is not yet reached. Condition: at least one classification must have been established at the position level. In this case, you can manually enter the quantity received at any time. Can explain how to configure Contract po with Schedulingagreement for Consignment Scenario.
Finally, No GR. When I went through the forums, I learned that I couldn`t do gr until the document was published. The dates of the lines I changed to post-date, even behind the date of the post, but it is still available as a document has no selectable items. Please help We update from 4.6C to ECC6.0. I will create purchase plan outputs with ME84. For some providers whose output I have set in MN11 as EDI, I receive error 06 857 No Message Record Found while generating versions of ME84. We found that no NAST dataset is being created. This is a coincidence, because I can define a provider output in MN11 for EDI and generate the calendar. hiDear Ami You do not need to create a PO according to the sched agreement.
You can simply do GR with regard to the agenda.cheersanund I have a problem here with the delivery plan (type LPA). I have established a delivery plan and am maintaining the schedule by running the MRP. The schedule could be maintained and I can run the version (generate SA versions for FRC and JIT). The release was documented directly there (I can see it if I view the delivery plan for SA) and I can also print it. The problem is that the status of the documentation of its version is still yellow (even if there are already message editions). As a result, the output number of this SA is still blocked in point 1, although changes in the content of the expression have already taken effect (the transmission of the dividing line has been modified because the RM has consumed the SA or has effects on the current layout). Cumulative quantities are an essential tool to get an accurate picture of the ever-changing business, involving delivery plans and their classifications. They allow you to look beyond the constant changes in data and quantities in order to get a clear picture of the transaction..