SAP JBD_FOBJ_ARCH_JBFO1_0300 Function Module for am Ende des Massenlaufs
JBD_FOBJ_ARCH_JBFO1_0300 is a standard jbd fobj arch jbfo1 0300 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for am Ende des Massenlaufs 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 jbd fobj arch jbfo1 0300 FM, simply by entering the name JBD_FOBJ_ARCH_JBFO1_0300 into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBD_FOBJ_ARCH_JBFO1_PP
Program Name: SAPLJBD_FOBJ_ARCH_JBFO1_PP
Main Program: SAPLJBD_FOBJ_ARCH_JBFO1_PP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JBD_FOBJ_ARCH_JBFO1_0300 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 'JBD_FOBJ_ARCH_JBFO1_0300'"am Ende des Massenlaufs.
EXPORTING
* I_APPLCATG = "
* I_FLG_JOB_ABORTED = "
* I_FLG_EXT_BREAK = "
I_PROGN = "
I_PROGDATE = "
I_PROGNO = "
* I_RUNSTARTNO = "
* I_RUNSTATUS = "
* I_XSIMULRUN = "
* I_PROCESS_ID = "
* I_RUNID_EXT = "
IMPORTING
E_APPL_RETURNCODE = "
IMPORTING Parameters details for JBD_FOBJ_ARCH_JBFO1_0300
I_APPLCATG -
Data type: BANK_DTE_PP_PAAPPLCATGOptional: Yes
Call by Reference: Yes
I_FLG_JOB_ABORTED -
Data type: BANK_DTE_PP_FLG_JOB_ABORTEDOptional: Yes
Call by Reference: Yes
I_FLG_EXT_BREAK -
Data type: XFELDOptional: Yes
Call by Reference: Yes
I_PROGN -
Data type: BANK_DTE_PP_PROGNOptional: No
Call by Reference: Yes
I_PROGDATE -
Data type: BANK_DTE_PP_PROGDATEOptional: No
Call by Reference: Yes
I_PROGNO -
Data type: BANK_DTE_PP_PROGNOOptional: No
Call by Reference: Yes
I_RUNSTARTNO -
Data type: BANK_DTE_PP_RUNSTARTNOOptional: Yes
Call by Reference: Yes
I_RUNSTATUS -
Data type: BANK_DTE_PP_RUNSTATUSOptional: Yes
Call by Reference: Yes
I_XSIMULRUN -
Data type: XFELDOptional: Yes
Call by Reference: Yes
I_PROCESS_ID -
Data type: BANK_DTE_JC_PROC_IDOptional: Yes
Call by Reference: Yes
I_RUNID_EXT -
Data type: BANK_DTE_PP_RUNID_EXTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for JBD_FOBJ_ARCH_JBFO1_0300
E_APPL_RETURNCODE -
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for JBD_FOBJ_ARCH_JBFO1_0300 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: | ||||
| lv_i_applcatg | TYPE BANK_DTE_PP_PAAPPLCATG, " | |||
| lv_e_appl_returncode | TYPE SY-SUBRC, " | |||
| lv_i_flg_job_aborted | TYPE BANK_DTE_PP_FLG_JOB_ABORTED, " | |||
| lv_i_flg_ext_break | TYPE XFELD, " | |||
| lv_i_progn | TYPE BANK_DTE_PP_PROGN, " | |||
| lv_i_progdate | TYPE BANK_DTE_PP_PROGDATE, " | |||
| lv_i_progno | TYPE BANK_DTE_PP_PROGNO, " | |||
| lv_i_runstartno | TYPE BANK_DTE_PP_RUNSTARTNO, " | |||
| lv_i_runstatus | TYPE BANK_DTE_PP_RUNSTATUS, " | |||
| lv_i_xsimulrun | TYPE XFELD, " | |||
| lv_i_process_id | TYPE BANK_DTE_JC_PROC_ID, " | |||
| lv_i_runid_ext | TYPE BANK_DTE_PP_RUNID_EXT. " |
|   CALL FUNCTION 'JBD_FOBJ_ARCH_JBFO1_0300' "am Ende des Massenlaufs |
| EXPORTING | ||
| I_APPLCATG | = lv_i_applcatg | |
| I_FLG_JOB_ABORTED | = lv_i_flg_job_aborted | |
| I_FLG_EXT_BREAK | = lv_i_flg_ext_break | |
| I_PROGN | = lv_i_progn | |
| I_PROGDATE | = lv_i_progdate | |
| I_PROGNO | = lv_i_progno | |
| I_RUNSTARTNO | = lv_i_runstartno | |
| I_RUNSTATUS | = lv_i_runstatus | |
| I_XSIMULRUN | = lv_i_xsimulrun | |
| I_PROCESS_ID | = lv_i_process_id | |
| I_RUNID_EXT | = lv_i_runid_ext | |
| IMPORTING | ||
| E_APPL_RETURNCODE | = lv_e_appl_returncode | |
| . " JBD_FOBJ_ARCH_JBFO1_0300 | ||
ABAP code using 7.40 inline data declarations to call FM JBD_FOBJ_ARCH_JBFO1_0300
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 SUBRC FROM SY INTO @DATA(ld_e_appl_returncode). | ||||
Search for further information about these or an SAP related objects