SAP Function Modules

APO_COLLECT_PLANNED_ORDER SAP Function module - Convert and Append Planned Order Data for Collective update(Header & Com







APO_COLLECT_PLANNED_ORDER is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name APO_COLLECT_PLANNED_ORDER into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MRP6
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM APO_COLLECT_PLANNED_ORDER - APO COLLECT PLANNED ORDER





CALL FUNCTION 'APO_COLLECT_PLANNED_ORDER' "Convert and Append Planned Order Data for Collective update(Header & Comp)
  EXPORTING
    i_apokz =                   " c
    i_plaf =                    " plaf
    i_method =                  " cif_r3ord-methode
  TABLES
    it_mdpm =                   " mdpm
    .  "  APO_COLLECT_PLANNED_ORDER

ABAP code example for Function Module APO_COLLECT_PLANNED_ORDER





The ABAP code below is a full code listing to execute function module APO_COLLECT_PLANNED_ORDER including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_it_mdpm  TYPE STANDARD TABLE OF MDPM,"TABLES PARAM
wa_it_mdpm  LIKE LINE OF it_it_mdpm .

DATA(ld_i_apokz) = 'Check type of data required'.
DATA(ld_i_plaf) = 'Check type of data required'.

DATA(ld_i_method) = some text here

"populate fields of struture and append to itab
append wa_it_mdpm to it_it_mdpm. . CALL FUNCTION 'APO_COLLECT_PLANNED_ORDER' EXPORTING i_apokz = ld_i_apokz i_plaf = ld_i_plaf i_method = ld_i_method TABLES it_mdpm = it_it_mdpm . " APO_COLLECT_PLANNED_ORDER
IF SY-SUBRC EQ 0. "All OK ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_i_apokz  TYPE C ,
it_it_mdpm  TYPE STANDARD TABLE OF MDPM ,
wa_it_mdpm  LIKE LINE OF it_it_mdpm,
ld_i_plaf  TYPE PLAF ,
ld_i_method  TYPE CIF_R3ORD-METHODE .

ld_i_apokz = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_it_mdpm to it_it_mdpm.
ld_i_plaf = 'Check type of data required'.

ld_i_method = some text here

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name APO_COLLECT_PLANNED_ORDER or its description.