Random header image... Refresh for more!

Sap Outline Agreement Planned Delivery Time

I wonder about the functionality of the expected delivery time (TDP) in framework agreements. What interests me the most is the influence on the layout. Look at the deadline that is respected in your framework agreement (contract). If you have cared for one, it outweighs the one maintained in the trunk. The expected delivery time is not specific to the supplier in the material rod (display “Provision 2”). You record a delivery time per supplier in the purchase information kit or in the framework contract. It is used in the scheduling procedure when the label “information set/appointment agreement” is used in customizing as an installation parameter (OPPQ) or layout group parameter in the “acquisition” and if, in the field of automatic source search, only one provider can be assigned. I assume you`re talking about the delivery date (calculated by the MRP). So I remove it from “additional data for the layout element” and it can also be seen in the PR created in the “Quantities / Dates” tab. Excuse me, I`m not sure about your question. What exactly does “delay” mean? Framework contract is a long-term sales contract between the supplier and the customer. There are two types of framework agreements: hello everyone. We have an obligation to update the delivery times of our contracts, some of which have been created with false information.

Is there a way to change in bulk the passage times (expected delivery times) as they are respected in a contract in the EKPO-PLIFZ field? Thank you in advance for all this help. Best of all, Grant Isaacs My experience is that the MRP does not take into account the TDP of the framework agreement. For me, it`s weird. If I delete the list of sources – and req closes, then mrp turns off again for the factory and material to generate a new Req – the delivery date is correctly calculated on req [taking into account the expected delivery time]. If someone could explain the meanings of the different TDPs (framework agreement, info-recort, material base), it would be of great help. Hello world. Thank you for your comments – much appreciated. Unfortunately, MEMASSPO only works on orders, not on framework agreements (contracts). MM17 is also used for massive modifications of material strains, not for purchase coatings. Are there other possibilities? Thanks.Grant maintains the expected delivery time in the supplier`s database in XK01. Since this value does not go to Quick Question, we try to use source lists to automatically assign the purchase price to the right supplier and GOA.

We discovered that by adding a list of sources – that the order requirements generated by the MRP are behind on the delivery date until tomorrow – and ignore the delivery time related to the factory, the material number in the material stem. If I understand the expected delivery time in the supplier`s database, the information kit and the hardware database, what expected delivery time is it in the process of being commissioned? Can you explain to me with an appropriate example? Each gently relevant one is very useful for me. Check your configuration in OMDT. Here you determine whether the material base or the information set/contract determines the passage time. The delivery plan is a long-term sales contract with the supplier in which a supplier is required to supply material on specified terms. information on the delivery date and quantity communicated to the supplier in the form of the delivery plan. Is there any additional information I need to set up to have req created with the correct delivery date? [We created an information dataset that was tagged to remove it] If you put this license plate, the system checks whether a planned delivery time is recorded in the purchase information kit or in the framework contract. It is from this expected delivery time that the delivery date and the release date are calculated. Create the list of sources and rank the agreement from the source list and make the MRP flag in the active source list when it takes the PDT of the trust.

Sharing is the Best Form of Caring
  • Facebook
  • Twitter
  • LinkedIn
  • StumbleUpon
  • Digg
  • Technorati
  • Mixx