Release Procedures (approval) can be used for Purchase Requisitions (PR), Purchase Orders (PO), RFQ’s, Outline Agreements and Service Entry Sheets. The principle is exactly the same for all. If you can master one, you will know them all.
This guide contains an example of release procedures for Purchase Requisition
Create Purchase Order Automatically in Purchasing
For creation of purchase Order automatically from Purchase Requisitions we need to do the following additional settings in addition to our standard ones.
Activate ‘auto PO’ indicator for material master
Activate ‘auto PO’ indicator for vendor master
Create Purchase Requisitions using T Code ME51 or ME51N
Use T. Code ME59 or ME59N for auto conversion of PR into purchase order
Here are listed an overview of the most frequently used transactions and URLs, aimed at XI developers
| SXMB_IFR | Start Integration Builder |
| SXMB_MONI | Integration Engine – Monitoring |
| SXI_MONITOR | XI: Message Monitoring |
| SLDCHECK | Test SLD Connection |
| SLDAPICUST | SLD API Customizing |
| SXMB_ADM | Integration Engine – Administration |
| SXI_CACHE | XI Directory Cache |
| SXMB_MONI_BPE | Process Engine – Monitoring |
| SWF_XI_CUSTOMIZING | Automatic BPM Customizing |
Step 1: Material Master
Logistics > Production > Master Data > Material Master > Material > Create General > Immediately MM01
Step 2: BOM creation
Logistics > Production > Master Data > Bills of Material > Bills of Material > Material BOM > Create CS01
Step 3: Work Center creation
Logistics > Production > Master Data > Work Center > ( New Screen ) Work Center > Create CR01
An Overview of Determination & Configuration of Pricing Procedure is as follows:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
The provided file list consists of various processes related to SAP Product Costing which are essential for managing and analyzing costs associated with materials, production orders, and cost estimates within the SAP system. Here is the list of files shared:
Contents:
C088 Settlement Prod Cost Collector Collective
CK11N Create Material Cost Estimate
CK13N Display Material Cost Estimate
CK24 Mark Future Price
CK24 Release Price Update
CK40N Edit Costing Run
CK44 Delete Costing run