In SAP MM materials management, Plant represents a location where valuated stocks are maintained. In other cases, plant can also be looked at as a location for maintaining or servicing. Transaction code OX10 can be used to define a plant in SAP. However, SAP MM requires certain pre-requisites before a plant can be defined in SAP. The three maiin requirements for configuring plant are country keys, factory calendar and region keys.
Internal Tables of ABAP
Internal tables are a way to store variable datasets of a fixed structure in the working memory of ABAP. The data is stored on a row-by-row basis, where each row has the same structure.
Internal tables provide the functionality of dynamic arrays and relieve the programmer of the expenditure of a program-controlled dynamic memory management (see Memory management of deep data objects. Internal tables are preferably used to store and format the content of database tables from within a program. Furthermore, internal tables in connection with structures are the most important means of defining very complex data structures in an ABAP program.
Release Procedure for Purchase Requisitions in SAP
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
Creation of Purchase Order Automatically
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
Frequently Used Transactions for XI Developers
Here are listed an overview of the most frequently used transactions and URLs, aimed at XI developers
XI Transactions
| 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 |
Useful Tables and Functional Modules(Updated)
- To find all the tables used in a transaction use table : D010TAB (Get the main program of the transaction from SE93)
- To find all the tables which contains a specific field use table : DD03L ( For text DD03T)
- To find all the segments that contains a specific fields use table : EDSAPPL
- To find all the Idoc basic type that contains a specific segment use table: IDOCSYN
- To find all the Idoc extensions that contains a specific segment use table: CIMSYN
- To find all the parameter Id Use table : TPARA
- To get the main program of a include use FM : RS_GET_MAINPROGRAMS
PP Transactional Flow
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