APO Technical Information
This page is specifically meant for collecting relevant technical information for APO. Useful BAPIs, User-exits and how-to for APO will be placed here.
SCM Function Modules
SCM Reports
SCM BAPIs
SCM BADIs
SCM User Exits
SCM Useful Tables
SCM Code Gallery
If you are a Functional Consultant looking for Technical details related to Custom Development then go here.
Useful Forum Posts related to SCM Technical Objects
BAPI / BAdI / Function Module | For | Remarks | Link |
---|---|---|---|
BAPI_POSRVAPS_SAVEMULTI3 | Delivery | ATP Category BR in APO DRP | |
BAPI_PBSRVAPS_GETDETAIL2 | Planning Book data | Input Parameters Planningbook, Data_view, Planning_Version, | |
/SAPAPO/EFPL_ORD_NET_GET | Pegging relationship | For pegging relationship across the entire strucuture | |
EXIT_/SAPAPO/SAPMMCP6_005 ZXDMUSERU05 | User exit macro | Add code in ZXDMUSERU05 | |
/SAPAPO/RRP_LC_PEGID_GET_IO | MRP Data from Live Cache | to get the data from live cache. Pass the pegid to the export parameter 'it_pegarea'. Determine pegid by using the function module '/SAPAPO/DM_MATERIAL_GET_PEGID' | |
/SAPAPO/OM_PEG_CAT_GET_ORDERS | To get data from LC at matches the PEGID (= plant, material, storage location) and ATP-category | You will just have to specify the ATP-categories that match the MRP elements you would like to retrieve - LC doesn't store the names of the MRP elements | |
/SAPAPO/OM_ORDER_GET_DATA | Order details from liveCache | To retrieve all information of an order from LC that corresponds to an order id. You just have to use the field IS_GEN_PARAMS-SIMVERSION = '000' and fill the table IT_ORDER with your order id. If you only want to have the OUTPUT_FIXED indicator it would be faster if you use the FM I suggested and then only request ET_ORDKEY as an output table - this table contains the OUTPUT_FIXED indicator | |
/SAPAPO/DM_ORDKEY_SELECT_ORDNO | GUID of Order from liveCache | Need to provide Order No. and SIMID | |
/SAPAPO/RRP_HEURISTIC_GET_DATA | Heuristic details | EXPORTING iv_heur_id = heur_id iv_langu = sy-langu IMPORTING ev_heur_text = lv_heur_text EXCEPTIONS | |
BAPI_PBSRVAPS_CHANGEKEYFIGVAL | To load a KF of planning book |
| |
BAPI_STSRVAPS_SAVEMULTI2 | To create stocks in SNP | Parameter for Version | |
/SAPAPO/RRP_LC_PEGID_GET_IO | Sales Order Fetch in APO | quantitiy, GUID and Pegging Area id but the sales order number | |
BAdI /SAPAPO/RRP_IO_COL | Additional Columns in Product View | RRP_USEX_COLS_GET_TEXT_01 method APPEND 'USEXIT1' to CT_CUS_FIELDS. | |
/SAPAPO/TS_DM_LOCK | User Change/Display Mode in Interactive Planning | Pass Values for GUI Id of Planning Area, Data Selection, Group By parameter | |
/SAPAPO/ADV_ALERT_SET | Generate Alert |
| |
/SAPAPO/MSDP_NOTE_WRITE | Write notes in SDP |
| |
/SAPAPO/TS_PLOB_CREATE | Creates CVC | Pass Plob ID and Selection Conditions for Characteristics |
|
/SAPAPO/TS_LCM_PLOB_DELTA_SYNC | After all char combos have been created call the sync | Pass Plob ID |
|
/SAPAPO/TS_PLOB_DELETE | CVC Deletion | Pass Plob ID and Selection Conditions for Characteristics |
|
RSDRC_CUBE_DATA_GET | Read Infocube | Pass Infocube, List of Characteristics and key Figues |
|
Other Generic Forum Posts
How to find a BADI in APO
Difference between BADI and User exit
Difference between BADI and BAPI
How to find BAPI
Additional Information
Common Terminologies
Terminology | Details |
---|---|
Planned Order | Manufacturing Order created in APO resulting from Production Planning run for In-house Produced Product |
Production Order | Planned Order is converted to a Production Order in R/3 which is then executed up (actual production carried out) |
Purchase Requisition / STR | Planned requisition resulting from Production Planning run for an Externally Procured Product |
Purchase Order / STO | Requisition is converted to a firmed Order in R/3 for subsequent execution |
Independent Requirement / Demand | Requirement for a finished product coming from customer. This may not be the firm demand but just a plan |
Sales Order | Firm demand from customer with a confirmed requirement date and quantity |
Stock | Quantity of product available at a location either after production or procurement |
Pegging Area | Combination of Product - Location - Account Assignment Object - Planning Version = Planning Segment in R/3 |
GUID | Unique ID used to identify each Master and Transaction Data element in APO. 40 character alpha-numeric code automatically system generated |
Planning Version | All Transaction and many Master data in APO stored in liveCache against a planning version. Default Planning Version to use is 000 - Active Version |
Common Transactions
Txn Name | Txn Code | Details |
---|---|---|
Master Data Related | ||
Location | /SAPAPO/LOC3 | Plants (Manufacturing / DC), Vendors, Customers, MRP Areas in R/3 all map to Location master in APO differentiated by Location Type (1001, 1002, 1011, 1010, 1007) |
Product | /SAPAPO/MAT1 | Material in R/3 is mapped to Product in APO. Has multiple tabs similar to that in R/3. Many field values come from R/3 while APO-specific field values are either manually populated or automatically during CIF transfer from R/3 to APO |
Resource | /SAPAPO/RES01 | Work Center (or Capacity) in R/3 defines the machine or equipment used for Production, Storage or Transportation |
PDS | /SAPAPO/CURTO_SIMU | Combination of Bill-of-Material and Routing in R/3 (Production Version). Used for In-house Produced Products to determine components and resource (capacity and time) requirements |
Transportation Lane | /SAPAPO/SCC_TL3 | Purchasing Inforecords and Contracts in R/3 map to Transportation Lanes in APO that define from where - to where products can be moved and the transportation duration |
Procurement Relationship | /SAPAPO/PWBSRC1 | Displays Contracts, Purchasing Inforecords and Scheduling Agreements coming from R/3 |
Transaction Data Related | ||
Product View | /SAPAPO/RRP3 | Most commonly used - needs Planning Version 000, Product and Location. This is equivalent to MD04 txn in R/3 |
Planning Board | /SAPAPO/CDPSO | Detailed View of Orders/operations used by End-users for Scheduling. Not much useful from Technical perspective |
Order Resource Reporting | /SAPAPO/CDPS_REPT | Combination of multiple reports |
Interactive SDP | /SAPAPO/SDP94 | Used to display DP and SNP data through a Planning Book / Data View combination and selecting CVCs |
Interactive Load Builder | /SAPAPO/SNPTLB | Used to carry out Transport Load Building - creation of Shipments |
Display LC Contents | /SAPAPO/OM16 | User-friendly way to display LC data by type of data. Need to know Order Type, Business System Group (BSG01) |
liveCache Browser | /SAPAPO/OM19 | You need to select liveCache option and browse the tables. This is not a very user-friendly option |
ATP Categories - APO Order Type Mapping
ATP Category | APO Order Type (Use in OM16 &OM19) | Details |
---|---|---|
CC | 11 | Stock (Unrestrcited) |
BU | 14 | Inspection Lot |
AC, AD | 31 | Production Order |
AI, AJ, AK, AL | 31 | Planned Order |
AG | 21, 22 | Purchase Requisition |
BF | 21 | Purchase Order |
BM | 52, 53 | Sales Order |
BR | 41 | Delivery |
FA, FC |
| Forecast |
Tip: Refer APO Table /SAPAPO/V_ATP03
<put links to other information sources on SDN/BPX or beyond here>
1 Comment
Former Member
Thanks for the useful tehnical info on APO