11. April 2021 · Write a comment · Categories: Uncategorized

The output at 10 is a precondition for publication with 20 (defined in the next step). If you know, then please tell me how to configure the thought plan…….. You can test a sharing policy used by the purchase document by clicking on the “Liberation Strategy” button on the screen above. You can also simulate the policy output with the “Simulate Release” button. If you use LP, you can do the GR without permission, but with LPA, you have to release the calendar line above ME38. Step 1) Let`s define a sharing strategy that requires only a manual unlock for the purchase of supporting documents worth more than 100 eur. If z.B we have a po worth 50 eur, it will be automatically released (there is no need to do so). An order greater than 100 eur would require unlocking. We can use the T ME28 code for sharing the voucher.

Those who can use which sharing codes are controlled by permissions. If a link to SAP Business Workflow has been set for the sharing code, the person may share (authorize) or refuse to share it (refuse permission), thus rejecting the article or document. Those who work with the traditional approach to customize delivery plans in SAP know that setting types and categories as well as maintaining output profiles can be difficult if you don`t know what you`re doing. The above information should be a reminder for those who are in the acquisition and introduction for those who started with SAP. This problem refers to the publishing policy for Scheduling Agreement (SA) Example: You create an S1 version policy, which consists of two codes of version 10 and 20. If it`s lpA (exit document), you can`t publish the GR until the publication is concerned. We can have many different strategies for different situations. You can set, for example. B, a sharing policy that depends on occupancy, you can set a sharing strategy based on the purchase organization, buying group or other important information for a purchase letter.

Cancellation of a version is not possible if your publishing policy does not allow the publication to be cancelled. This is a parameter that is maintained at the exit indicators and exit strategy. If it is LP (without a publication document), the publication will do nothing BUT 2. Another thing…. The key to indicate the backlog and the instant requirement are not displayed in the SA version…. (I think it should be displayed in the “calendar line type” column. although I established the SA with the creative profile that the relevant indicator for the backlog and the immediate requirement defined in the overall parameter of the creation profile. Did I miss something? Important information you know is that proof of purchase cannot be changed after it has been released. This means that only the final version should be published.

Unpublished supporting documents (request for quotes – quote request, order – order, delivery plan, contract) cannot be processed further (RFQ conversion to offer, order in receipt, audit of accounts). Process Flow: Select the field with the ID as a shared column and chgable with value, i.e. assign the output strategy to a combination of configuration category, materials group, factory, PR value and currency. Determine which sharing codes are included in a sharing policy. Specify whether a code is set for the release state after publication and if the release state is a condition for another. Until now, the authorization applied only to contracts with our client. But we now plan to introduce it also for SA. Such a feature is available in SAP, but the problem is that with the given output policy, GR is not allowed until the release is affected. The system allows you to book the delivery plan.

Comments closed.