I need to retrieve the types of conditions from the planning agreement. 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. 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. Here is the standard documentation available and some details about the fields that make up this table. You can view more information about the SAP EKETH table and the data it contains in relevant transactions such as SE11, SE80, or SE16. Also see the Comments section below to see or add related articles and sample screenshots. It was in KONP, but there is no link field for every planning agreement. 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. To get the condition type for the planning agreement, first go to table A016, enter the corresponding details, the planning agreement number, the item, and receive the condition record number (KNUMH). Use this condition record number to access the KONP table and enter the condition record number in KNUMH.
This is the unique key in both tables. Here you get types of conditions. 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. 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. 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.
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. I don`t want a BAPI for that. The only thing I need is a query between tables. UoM delivery and UoM attachment order: Up to 10 attachments (including images) of up to 1.0 MB each and a total of 10.5 MB can be used. 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 Screen, set the allowed document tracking. .
. # 52 DELIVERY DATE – Transfer date at transfer place # 41 WAUHR – Time of issue of goods (local, factory-related) # 18 MAHNZ – Stock Transfer No. for Purch. RESB Booking/Dependent Requirements EKES Supplier Confirmations Roles of EKPA Partners in Purchase EKBEH Order History, Planning Agreement (Reorganized) Delivery Cost History EKBZH, Sched. . . .
