JBD_FCTY_ARCH_JBFC1_1000 SAP Function module - Initialisierung eines Arbeitspaketes

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

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

Pattern for FM JBD_FCTY_ARCH_JBFC1_1000 - JBD FCTY ARCH JBFC1 1000

CALL FUNCTION 'JBD_FCTY_ARCH_JBFC1_1000' "Initialisierung eines Arbeitspaketes
  EXPORTING
*   i_applcatg =                " bank_dte_pp_paapplcatg
    i_progn =                   " bank_dte_pp_progn
    i_progdate =                " bank_dte_pp_progdate
    i_progno =                  " bank_dte_pp_progno
    i_currstartno =             " bank_dte_pp_runstartno
    i_xsimulation =             " bank_dte_pp_xsimulrun
    i_currstepno =              " bank_dte_pp_stepno
*   i_str_applparam =           "
*   i_str_package_key =         " bank_str_pp_packagekey
*   i_limit_low =               " bank_dte_pp_objno
*   i_limit_high =              " bank_dte_pp_objno
    i_xrestart =                " xfeld
*   i_str_packattr =            "
*   i_cnt_packages =            " bank_dte_pp_cnt_packages
*   i_flg_aborted =             " xfeld
    .  "  JBD_FCTY_ARCH_JBFC1_1000

ABAP code example for Function Module JBD_FCTY_ARCH_JBFC1_1000

The ABAP code below is a full code listing to execute function module JBD_FCTY_ARCH_JBFC1_1000 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_i_applcatg) = 'Check type of data required'.

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

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

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

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

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

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

DATA(ld_i_str_applparam) = 'some text here'.

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

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

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

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

DATA(ld_i_str_packattr) = 'some text here'.

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

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

CALL FUNCTION 'JBD_FCTY_ARCH_JBFC1_1000'
  EXPORTING
*   i_applcatg =                 ld_i_applcatg
    i_progn =                    ld_i_progn
    i_progdate =                 ld_i_progdate
    i_progno =                   ld_i_progno
    i_currstartno =              ld_i_currstartno
    i_xsimulation =              ld_i_xsimulation
    i_currstepno =               ld_i_currstepno
*   i_str_applparam =            ld_i_str_applparam
*   i_str_package_key =          ld_i_str_package_key
*   i_limit_low =                ld_i_limit_low
*   i_limit_high =               ld_i_limit_high
    i_xrestart =                 ld_i_xrestart
*   i_str_packattr =             ld_i_str_packattr
*   i_cnt_packages =             ld_i_cnt_packages
*   i_flg_aborted =              ld_i_flg_aborted
    .  "  JBD_FCTY_ARCH_JBFC1_1000

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_applcatg
 
 TYPE BANK_DTE_PP_PAAPPLCATG ,
ld_i_progn
 
 TYPE BANK_DTE_PP_PROGN ,
ld_i_progdate
 
 TYPE BANK_DTE_PP_PROGDATE ,
ld_i_progno
 
 TYPE BANK_DTE_PP_PROGNO ,
ld_i_currstartno
 
 TYPE BANK_DTE_PP_RUNSTARTNO ,
ld_i_xsimulation
 
 TYPE BANK_DTE_PP_XSIMULRUN ,
ld_i_currstepno
 
 TYPE BANK_DTE_PP_STEPNO ,
ld_i_str_applparam
 
 TYPE STRING ,
ld_i_str_package_key
 
 TYPE BANK_STR_PP_PACKAGEKEY ,
ld_i_limit_low
 
 TYPE BANK_DTE_PP_OBJNO ,
ld_i_limit_high
 
 TYPE BANK_DTE_PP_OBJNO ,
ld_i_xrestart
 
 TYPE XFELD ,
ld_i_str_packattr
 
 TYPE STRING ,
ld_i_cnt_packages
 
 TYPE BANK_DTE_PP_CNT_PACKAGES ,
ld_i_flg_aborted
 
 TYPE XFELD .


ld_i_applcatg = 'Check type of data required'.
ld_i_progn = 'Check type of data required'.
ld_i_progdate = 'Check type of data required'.
ld_i_progno = 'Check type of data required'.
ld_i_currstartno = 'Check type of data required'.
ld_i_xsimulation = 'Check type of data required'.
ld_i_currstepno = 'Check type of data required'.
ld_i_str_applparam = 'some text here'.
ld_i_str_package_key = 'Check type of data required'.
ld_i_limit_low = 'Check type of data required'.
ld_i_limit_high = 'Check type of data required'.
ld_i_xrestart = 'Check type of data required'.
ld_i_str_packattr = 'some text here'.
ld_i_cnt_packages = 'Check type of data required'.
ld_i_flg_aborted = 'Check type of data required'.