Schedule Agreement Release in Sap Mmadmin
You can only create versions for planning agreements with the release documentation. (The document type in the standard is LPA or the Release Documentation flag must be marked in Customizing for Purchasing -> Scheduling Agreement -> Define Document Types.) If you have multiple planning agreements for a material, use quota scheduling to distribute requirements across vendors. Aggregation horizons: In the “Aggregation horizons” area, you specify for each type of release the time horizon used by the system to determine the quantities released and the periods for which the system aggregates the quantities into “period quantities”, if necessary. The following example sets the parameters in the Aggregation Horizons pane to send monthly request quantities for the next nine months in the forecast plan and daily quantities for the next ten days in the JIT schedule. LPA for planning agreements with publication documentation. The extended configuration options in the authoring profile allow you to produce a wide variety of results as part of the build version. In the EKEK table, Status of release (STAAB) field, you can see how a version was created, either manually or against RM06EFLB. SAPLEINL – Main Program for Release Documentation RM06EFLB – Release Generation Report from Release 4.5 RM06EFAB – from Release 4.0 RM06ELAB – from Release 3.x You send the supplier a planning agreement release in the form of a forward planning agreement in which you tell them how many tons of Steel 1 material you are expected in the next nine months: e.B. 1000 tonnes in January, 900 tonnes in February, etc.
(In general, data from this approximate schedule and the time frame less precise.) You then specify the exact dates and quantities in a JIT planning agreement (the second form of SA release). For example, you need 30 tons of steel 1 on January 10, 20 tons on January 14, etc. It generates an SA version (either a forecast planning agreement or a JIT planning agreement) based on the creation strategy and the entries on the initial screen for creating the SA version. You can process message records for newly created versions immediately or in a later group output. Messages are sent immediately when the transmission time is set to `4`. Collective editing is possible if you are working with transmission time `1` (output via RSNAST00) or `3` (output via the application-specific output program). Assign this MRP group in the material sheets ordered via the SA versions. 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. MEDE – MRP classification lines EINL – Release documentation 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. 3. Define the publishing procedure for the scheduling agreement After you determine the type of message that updates the print-dependent data for each version type (that is, for each operation), you must ensure that versions are always created with that type of message (called the “primary message type”). You can create a second message type in parallel, where the primary message type must be the one that is created first (for example.B. LPH2 as the second message type for LPH1). 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. If there are messages for the scheduling agreement that have not been issued and you then set the “Messages per call” flag, you can still find the messages that were not -> output overload messages. The newly created messages can be found in the version documentation (ME38 -> select the corresponding item -> the SA version documentation. -> select the corresponding version -> messages per version).
In this case, the system always creates scheduling agreement lines whose delivery dates match the request dates because the system never schedules them. 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 calendar lines Basically, Version generation “translates” the current global planning agreement into one version. The press releases inform the supplier of the quantities of a material to be delivered, on what date. Individual versions are saved on the basis of the publication documentation and can therefore be displayed at any time. The system saves a transmitted version with a version number and includes the document in the version history. The system then generates the next version of that particular version type with a number increased by one. Forecast plans and JIT calendars have separate number ranges. .