Those who work with the traditional approach to customizing scheduling agreements in SAP know that defining types and categories, as well as managing versioning profiles, can be a problem if you don`t know what you`re doing. The above information should prove useful for those working in procurement and as an introduction to those who are just starting out with SAP. If you enabled the Stop Recovery feature for a schedule agreement line, reminders are stopped after they are created. Stopped SA versions must be self-released (released for output) so that they can be printed or transferred. In this step, a versioning profile for planning agreements is preserved with a publishing document. This profile determines the versioning strategy and how the backlog and immediate requirements are taken into account when creating versions. To manage the versioning profile, go to IMG (SPRO) > Materials Management > Purchasing > Scheduling Agreement > Maintain Release Creation Profile for SA with Release Document. In this example, if you check the schedule rows individually, the system will create a release because you changed the quantity in the first row by more than 20%, and it therefore exceeds the tolerance limit. If a creation profile exists, it aggregates release dates and quantities. The planning agreement is plant-specific, with item categories M and W not allowed. For the type of subcontracting item, the hardware components to be supplied for each delivery date can be entered separately. Note: There are no release documents for transportation planning agreements. Even if the documentary output.
is marked for the LU document type in Customizing, this has no effect. Overall process The processing of the planning agreement consists of three main steps:-Material Requirements Planning -Publication Generation (FRC/JIT) -Output/Transfer of Recoveries In the EKEK table, STAAB (Version Status) field, you can see how a version was created, either manually or against RM06EFLB. Release/Expediter -> fine-tuning control: Provisional delivery schedule/Expediter. You should always use the main message type to create all versions, otherwise the system will not update the print-dependent data. This is especially important if you are using several different types of messages. When the system issues a message, some updates occur that mark the version as « completed and out ». If the system has not yet issued a version as a message, the last version that the system has not yet issued is replaced each time another version is generated. In the tolerance test, the upper and lower tolerance limits are set at 20 % for this period. If you make these changes to the planning lines, with a basic global check with 20% as the upper and lower tolerance limits, the system does not create a new version. The total amount of time lines was 90 pieces and after the changes, the sum of the new schedule lines is 106. Therefore, the change does not exceed the upper limit of 20%.
20% of 90 pieces = 18 pieces and the quantity has only changed by 16 pieces. The quantity proposed for receipts of goods is based on the last release relevant for the delivery transmitted. If you use both types of sharing, the system suggests the data in the JIT schedule. If you use only the forecast calendar, the system suggests the data in the forecast calendar. I have a question about the sharing of the JIT schedule. Is there a way (using a creation profile or elsewhere) to divide the backlog of JIT planned quantities based on schedule flax data and not aggregate it? I tried to change the profile configuration, but every time the jIT idoc goes to the provider, the cumulative quantity for the backlog contains. The following tables contain the default settings for SAP; ImG (SPRO) > Materials Management > Purchasing > Scheduling Agreement > document types can be used to define additional types of planning agreements based on business needs. You can use scheduling agreements with or without version documentation. A landfill can be used to inform the supplier that he must deliver the material notice on the dates. When the system creates a version, it also creates a message record at the same time.
This set of messages is a prerequisite for the transmission and transmission of the landfill to the supplier. Prerequisites for passing schedule agreement versions as messages to the provider: Starting with version 4.0, you must define exactly one message type as the « primary message type » for each version type in Customizing for MM, message determination for scheduling agreements. The `U` (Update print-dependent data) field must be marked for the message type in Customizing for Materials Management -> Purchasing -> Messages -> Output Control -> Message Types -define message types -> message types for the planning agreement We can create a planning agreement with or without reference to a purchase requisition or framework agreement, offer or even other planning agreement. The SAP planning agreement is a long-term agreement with a supplier for the delivery of the material under predefined conditions that are valid for a certain period of time for a certain quantity. SA versions can be generated for planning agreements with version documentation. The version of the planning agreement can be created manually or automatically using a report. SA versions can be generated either for all selected elements of the respective planning agreement or only for items for which planning rows are newly created or modified. Forecast and JIT are two types of planning agreement publishing. ANALYSE_PROFIL – analyzes the transfer profile with regard to the periodicity BESTIMMEN_ABRUF_NR – determines the version number FUELLEN_KOPF – creates new EKEK data records FUELLEN_EINTEILUNGEN_NEU – creates new EKEH data records with regard to ameng (without versioning profile) AGGREGIEREN_EINTEILUNGEN_NEU – aggregates the planning lines After the system has issued the version with the main message type (see below), the `Release Date` and `Release Time` fields are filled in. Another important detail that is updated at this point is the reset of the Modified flag in the planning agreement line.
This means that after a version is released, the element of the planning agreement in question is no longer considered « modified » (compared to the overall planning agreement in the system) until you. we solved our problem for the liberation SA here… thx everything for your kind concern about this, The system stores messages for release in the NAST table with the following key: I notice that the version number in the EKET table and EKEH are not identical and the version number does not make sense (1, 2 and directly 6). The prerequisite for automatically creating schedule lines during DEMAND scheduling is that a schedule agreement is marked as relevant to MRP in the source list. You can do this in the Purchases menu: Master Data -> Maintain the list of sources -> (transaction ME01). You must keep a record for the material here and in this register, the `DISPOSITION` field must contain the indicator `2`. If you have set the JIT spread sign in the item card and the planning agreement has already been created, you cannot create JIT dates for this planning agreement. Check if there are any change documents in the material card for the JIT board sign and check when the planning agreement element was created. You can also enter this indicator manually in ME32L on the additional data screen.
You create planning agreement versions (PLANNING AGREEMENTS sent to the vendor) that include the planning lines for a specific planning agreement line. . . .