It generates an SA version based on the creation policy and the entries on the initial screen for creating the SA version. 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. With sap S/4HANA Logistics` loB Sourcing and Procurement, it is possible to use the SAP Best Practices activation approach for adapting planning agreements. However, if you use the traditional customizing approach, this blog post can be helpful. Planning agreements are defined and managed in the system as documents. It is possible to group these documents between different types of documents according to the needs of the company. First, you need to define the document types and their attributes in Customizing. Create a versioning profile with the following details on the Aggregation tab. 1.) Concept and why is it used in scheduling agreements? On the Aggregation tab, create a version profile with the following details. It generates an SA version in accordance with the creative strategy and the entries on the home screen for the creation of SA. The version profile is the profile that actually makes the difference between the JIT calendar and the forecast plan.
If you do not assign an outbound profile to the planning agreement, there is no difference between jit and the planning agreement. This can be included in printing LPJ1 LPH1 messages for the same calendar lines. In addition, we control the schedules of the lines to be sent and in what type of release. Z .B. Only NEw, changed, next date, etc. The following tables contain the default settings for SAP. IMG (SPRO) can be used to define additional delivery instructions via IMG (SPRO), > > purchases > planning contract define > types of processes. When a creation profile is available, it aggregates delivery data (i.e., expected) into quantities and dates. With SAP S/4HANA Logistics` LoB procurement and procurement system, SAP`s best practices activation approach can be used to customize planning agreements.
The versioning profile is the one that actually makes the difference between the jit calendar and the forecast planning agreement. If you do not assign a versioning profile to the planning agreement, there is no difference between JIT and the forecast planning agreement. This can be understood in the expression of the LPJ1 and LPH1 messages for equal divisions. It also controls which appointment lines to send in which type of release. E.B. only NEw, modified, next date, etc. Here, the system does not take into account the remaining planning lines after the 7th day in the EEM or the 180th day in the forecast day from today, as maintained in the creation profile (publication horizon: total number of working days). After you define the document types for planning agreements, select the row for the document type and double-click Allowed Item Categories. In the Allowed Item Categories for Document Type screen, keep the item type as listed in the following table. These types of items can be configured according to business needs. This configuration determines which types of items for a particular document type can be selected by the user when creating the planning agreement.
If a creation profile exists, it aggregates release dates and quantities. The following criteria can also be configured in the profile: Generate JIT & Forecast version without assigning a version creation profile. You create planning agreement versions (planning agreements) that include the planning lines for a specific planning agreement line. These are snapshots of the entire planning agreement stored in the system at specific times. 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. 1.) Concept and why is it used in scheduling agreements? Assign a versioning profile now and generate both JIT and Forecast I would like to see the following aspects as below in the context of «Release Creation Profile» in the process of creating a planning agreement? 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. However, if you use the traditional customizing approach, this blog post can be helpful.
Now assign the version production profile and generate both JIT and forecasts Generate In this step, a version profile for planning agreements is kept with a version document. This profile determines the execution strategy and how delays and immediate requirements are taken into account during implementation. To maintain the output profile, navigate to IMG (SPRO) > Materials Management > planning contract > > manage the operating profile of its with the release document. Those who work with the traditional approach to customizing planning agreements in SAP know that defining types and categories, as well as managing exit 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 process of acquiring and adopting for those who started with SAP. After you define the document types for planning agreements, select the row for the document type and double-click Allowed Item Types. On the screen, manage the categories of items that are allowed for the item category, as shown in the following table. These item categories can be configured to meet business needs. This configuration determines the categories of items that the user can select when developing the deployment plan for a specific usage site. A validation profile is used to determine the period during which the sharing (delivery methods) of a planning agreement is generated and submitted to the supplier.
A versioning profile is used to determine the period during which versions (schedule agreement types) are generated against a scheduling agreement and passed to the vendor. This also controls the frequency of versioning; the aggregation of the quantities provided for from the day following the creation of the release; and the conduct of a tolerance test. 01.11.2013>>>>30 so the first of each month until the following 12 months. Editor`s Note: This article is from a section of Justin Ashlock`s book Sourcing and Procurement with SAP S/4HANA. You already have an active moderator notification for this content. Note: The above rough estimate may not be the same, depending on the working days Result: All lines are sent as maintained above. Can you pls .. describe. Weekly aggregation (empty)>>>>6>>30 (not possible with JIT) Example: Profile creation and SA version creation.
When creating such versions, the system does the following: Choose the purchase data of the supplier maintenance, find the Extras–add > submenu. Purchase data – > data again. Factory-level allowed, then select Alternate Data, then Yes to create it, type Factory 1000, select Purchase Data, and then choose Next. Attachments: Up to 10 attachments (including images) can be used, each with a maximum of 1.0 MB and a total of 10.5 MB. Now select the row for each item type and double-click Link Purchase Requisition Document Type. In the edit view «Link Purchase Requisition Document Type»: Overview, set the allowed document tracking. New ranges of numbers can also be defined and used if necessary. This step is usually required if new document types are defined in the previous step.
The menu path for creating number ranges is IMG (SPRO) > Materials Management > Purchasing > Scheduling agreement define > number ranges. If you have an answer to this question, please use the Your Answer form at the bottom of the page. How is the publication profile of a scheduling agreement assigned to a = supplier? I couldn`t find it in the Vendor Master. Please advise. . Your complete guide to SAP S/4HANA procurement and procurement is available here! Get step-by-step instructions on how to set up procurement, billing, supplier management and evaluation, and centralized procurement. Learn how to integrate SAP S/4HANA with SAP Ariba, SAP Fieldglass, and more.