SAP APO_COLLECT_PLANNED_ORDER Function Module for Convert and Append Planned Order Data for Collective update(Header & Comp)
APO_COLLECT_PLANNED_ORDER is a standard apo collect planned order SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert and Append Planned Order Data for Collective update(Header & Comp) processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for apo collect planned order FM, simply by entering the name APO_COLLECT_PLANNED_ORDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: MRP6
Program Name: SAPLMRP6
Main Program: SAPLMRP6
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function APO_COLLECT_PLANNED_ORDER pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'APO_COLLECT_PLANNED_ORDER'"Convert and Append Planned Order Data for Collective update(Header & Comp).
EXPORTING
I_APOKZ = "
I_PLAF = "
I_METHOD = "
TABLES
IT_MDPM = "
IMPORTING Parameters details for APO_COLLECT_PLANNED_ORDER
I_APOKZ -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_PLAF -
Data type: PLAFOptional: No
Call by Reference: No ( called with pass by value option)
I_METHOD -
Data type: CIF_R3ORD-METHODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for APO_COLLECT_PLANNED_ORDER
IT_MDPM -
Data type: MDPMOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for APO_COLLECT_PLANNED_ORDER Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lt_it_mdpm | TYPE STANDARD TABLE OF MDPM, " | |||
lv_i_apokz | TYPE C, " | |||
lv_i_plaf | TYPE PLAF, " | |||
lv_i_method | TYPE CIF_R3ORD-METHODE. " |
  CALL FUNCTION 'APO_COLLECT_PLANNED_ORDER' "Convert and Append Planned Order Data for Collective update(Header & Comp) |
EXPORTING | ||
I_APOKZ | = lv_i_apokz | |
I_PLAF | = lv_i_plaf | |
I_METHOD | = lv_i_method | |
TABLES | ||
IT_MDPM | = lt_it_mdpm | |
. " APO_COLLECT_PLANNED_ORDER |
ABAP code using 7.40 inline data declarations to call FM APO_COLLECT_PLANNED_ORDER
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8."SELECT single METHODE FROM CIF_R3ORD INTO @DATA(ld_i_method). | ||||
Search for further information about these or an SAP related objects