CX_CRP_PLANNED_ORDER_SCHEDULE SAP Function module - Scheduling for planned order

CX_CRP_PLANNED_ORDER_SCHEDULE 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 CX_CRP_PLANNED_ORDER_SCHEDULE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CXPA
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM CX_CRP_PLANNED_ORDER_SCHEDULE - CX CRP PLANNED ORDER SCHEDULE

CALL FUNCTION 'CX_CRP_PLANNED_ORDER_SCHEDULE' "Scheduling for planned order
  EXPORTING
    plaf_imp =                  " plaf          Planned order
*   i_kbed_typkz = SPACE        " kbed-typkz    if scheduling level is known
*   i_flg_only_bt = SPACE       " c             Structure only order tables
*   i_flg_protocol = 'X'        " c             with scheduling log
*   i_flg_capapl = 'X'          " cm61s-flg_capapl  Call from scheduling/deallocation
  IMPORTING
    e_aufnr_fein =              " afko-aufnr
    e_aufnr_grob =              " afko-aufnr
    e_aufnr_rate =              " afko-aufnr
    plaf_exp =                  " plaf
    .  "  CX_CRP_PLANNED_ORDER_SCHEDULE

ABAP code example for Function Module CX_CRP_PLANNED_ORDER_SCHEDULE

The ABAP code below is a full code listing to execute function module CX_CRP_PLANNED_ORDER_SCHEDULE 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:
ld_e_aufnr_fein  
 
 TYPE AFKO-AUFNR
,
ld_e_aufnr_grob  
 
 TYPE AFKO-AUFNR
,
ld_e_aufnr_rate  
 
 TYPE AFKO-AUFNR
,
ld_plaf_exp  
 
 TYPE PLAF
.


DATA(ld_plaf_imp) = 'Check type of data required'.
 

SELECT single TYPKZ 
  FROM KBED 
  INTO @DATA(ld_i_kbed_typkz).


DATA(ld_i_flg_only_bt) = 'Check type of data required'.

DATA(ld_i_flg_protocol) = 'Check type of data required'.


DATA(ld_i_flg_capapl) = some text here
.

CALL FUNCTION 'CX_CRP_PLANNED_ORDER_SCHEDULE'
  EXPORTING
    plaf_imp =                   ld_plaf_imp
*   i_kbed_typkz =               ld_i_kbed_typkz
*   i_flg_only_bt =              ld_i_flg_only_bt
*   i_flg_protocol =             ld_i_flg_protocol
*   i_flg_capapl =               ld_i_flg_capapl
  IMPORTING
    e_aufnr_fein =               ld_e_aufnr_fein
    e_aufnr_grob =               ld_e_aufnr_grob
    e_aufnr_rate =               ld_e_aufnr_rate
    plaf_exp =                   ld_plaf_exp
    .  "  CX_CRP_PLANNED_ORDER_SCHEDULE

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_e_aufnr_fein
 
 TYPE AFKO-AUFNR ,
ld_plaf_imp
 
 TYPE PLAF ,
ld_e_aufnr_grob
 
 TYPE AFKO-AUFNR ,
ld_i_kbed_typkz
 
 TYPE KBED-TYPKZ ,
ld_e_aufnr_rate
 
 TYPE AFKO-AUFNR ,
ld_i_flg_only_bt
 
 TYPE C ,
ld_plaf_exp
 
 TYPE PLAF ,
ld_i_flg_protocol
 
 TYPE C ,
ld_i_flg_capapl
 
 TYPE CM61S-FLG_CAPAPL .


ld_plaf_imp = 'Check type of data required'.

SELECT single TYPKZ 
  FROM KBED 
  INTO ld_i_kbed_typkz.

ld_i_flg_only_bt = 'Check type of data required'.
ld_i_flg_protocol = 'Check type of data required'.

ld_i_flg_capapl = some text here