PO authorization is often required due to changes in PO, the buyer must have with the purchasing manager for the release PO. Sharing agreement sharing strategy with workflow. Just to add, I checked the delivery plan (PurchSchedAgrement). There is no event that refuses the agreement, whereas in case of order request, the event is already in place (PurchaseRequisition.rejected). So you won`t encounter this problem with PR. To solve these problems, delivery plans are used to replace the often needed standard component orders. 3.All delivery plans (TCODE-ME35) (TCODE-ME35) Hello, I would like to share with you one of the purchase scenarios in which the order has been replaced by delivery plans. A sharing profile determines the period during which versions (delivery plan types) are generated against a delivery plan and passed to the provider. This also controls the frequency of versioning; the aggregation of the quantities provided for from the day following the establishment of the release; and the carrying out of a tolerance check. 4.List of sources established for components with delivery plan and use of provisions 2 (residue data set). Sched lines. automatically generated) In this step, a sharing profile is maintained for delivery plans with proof of sharing.
This profile determines the output creation strategy and how backlog and immediate requirements will be taken into account when creating output. To maintain the release profile, you can go to IMG (SPRO) > the materials > purchasing industry > delivery plan > release profile for SA with proof of sharing. 3.No follow-up of the market authorisation is necessary once it has been released, it shall be valid for the period of validity mentioned therein. . . .