
Explore vendor master concepts in SAP MM, detailing vendor segregation (import, local, international, dealers), central versus local ordering, currency and payment terms, invoicing, and international commercial terms with transport responsibilities.
Explore vendor master configurations in sap mm, including minimum order value, payment terms, and blocking versus deleting vendors, plus creating and managing vendor groups and data deletion timelines.
Explore SAP MM purchasing release strategies, comparing item-level and document-level release, with approvals and scenarios for single or multiple line items and vendors.
I have explained below all the concepts clearly
What is ERP
SAP Requirement
Procurement cycle
Material master
Vendor Master
PIR-Purchase Info record
Source list
Quota Arrangement
Release Strategy
Release procedure defines, how the document is going to release. The document can be PR, PO, Contract, Scheduled agreement, RFQ. Here we study about the purchase requisition.
Purchase requisition will be created by the respective stake holders of there plant, if a request is created it will go to buyers Que to create purchase order and before that who ever is created purchase requisition he should approve and after that respective manager should approve.
We can create an N number of approvers for the documents like PR, where as an SAP MM consultant its their duty to maintain the release approvers.
We can maintain the release process for respective documents also.
Eg: we can maintain the release strategy for plant or material group also.
To maintain the release procedure for particular document types in SAP MM, we have communication tables/Structure for document types, mentioned below
Document type Communication table
PR- CEBAN
PR, PO, CO, SA, RFQ CEKKO
SES CESSR
In the above-mentioned communication tables are used to know the details for respective document type field component.
We have T-code to help to find the component for the respective field in the communication table, that is SE11, where we can only display the data (ABAP Data), its mainly used to find the component for the document type with the help of communication table.
Eg: CEBAN is used for PR, if we are maintaining the release procedure with respect to plant than we need to find the respective component for the plant filed in PR.
So, go to SE11, maintain the communication table as CEBAN if you are working for PR or else you can maintain CEKKO, CESSR for the remaining data field components.
As mentioned in the example, we have only one condition (Plant) to maintain the release strategy, if I would like to maintain the release strategy with combination of conditions then we need to define as mentioned below.
Ne PO.