SAP JGBP_0003_IMPORT_DATA_II Function Module for Conversion: Determine Program Parameters
JGBP_0003_IMPORT_DATA_II is a standard jgbp 0003 import data ii SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion: Determine Program Parameters 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 jgbp 0003 import data ii FM, simply by entering the name JGBP_0003_IMPORT_DATA_II into the relevant SAP transaction such as SE37 or SE38.
Function Group: JGBP_CONVERT
Program Name: SAPLJGBP_CONVERT
Main Program: SAPLJGBP_CONVERT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JGBP_0003_IMPORT_DATA_II 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 'JGBP_0003_IMPORT_DATA_II'"Conversion: Determine Program Parameters.
EXPORTING
* I_UCUS = "
* I_GRID = "
* I_ROLE = "
* I_ROLE_OLD = "Business Partner Role Category
* I_EXPN = "
* I_CORR = "
* I_UMST = "
* I_COUM = "
* I_STAN = "
* I_ANUM = "
* I_PNUM = "
* I_DEBI = "
* I_CHCE = "
EXCEPTIONS
ZTPKT = 1
IMPORTING Parameters details for JGBP_0003_IMPORT_DATA_II
I_UCUS -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_GRID -
Data type: BUT000-BU_GROUPOptional: Yes
Call by Reference: Yes
I_ROLE -
Data type: BUT100-RLTYPOptional: Yes
Call by Reference: Yes
I_ROLE_OLD - Business Partner Role Category
Data type: BP1000-ROLETYPOptional: Yes
Call by Reference: Yes
I_EXPN -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_CORR -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_UMST -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_COUM -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_STAN -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_ANUM -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_PNUM -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_DEBI -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
I_CHCE -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ZTPKT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for JGBP_0003_IMPORT_DATA_II 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_ztpkt | TYPE STRING, " | |||
| lv_i_ucus | TYPE BOOLE-BOOLE, " | |||
| lv_i_grid | TYPE BUT000-BU_GROUP, " | |||
| lv_i_role | TYPE BUT100-RLTYP, " | |||
| lv_i_role_old | TYPE BP1000-ROLETYP, " | |||
| lv_i_expn | TYPE BOOLE-BOOLE, " | |||
| lv_i_corr | TYPE BOOLE-BOOLE, " | |||
| lv_i_umst | TYPE BOOLE-BOOLE, " | |||
| lv_i_coum | TYPE BOOLE-BOOLE, " | |||
| lv_i_stan | TYPE BOOLE-BOOLE, " | |||
| lv_i_anum | TYPE BOOLE-BOOLE, " | |||
| lv_i_pnum | TYPE BOOLE-BOOLE, " | |||
| lv_i_debi | TYPE BOOLE-BOOLE, " | |||
| lv_i_chce | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'JGBP_0003_IMPORT_DATA_II' "Conversion: Determine Program Parameters |
| EXPORTING | ||
| I_UCUS | = lv_i_ucus | |
| I_GRID | = lv_i_grid | |
| I_ROLE | = lv_i_role | |
| I_ROLE_OLD | = lv_i_role_old | |
| I_EXPN | = lv_i_expn | |
| I_CORR | = lv_i_corr | |
| I_UMST | = lv_i_umst | |
| I_COUM | = lv_i_coum | |
| I_STAN | = lv_i_stan | |
| I_ANUM | = lv_i_anum | |
| I_PNUM | = lv_i_pnum | |
| I_DEBI | = lv_i_debi | |
| I_CHCE | = lv_i_chce | |
| EXCEPTIONS | ||
| ZTPKT = 1 | ||
| . " JGBP_0003_IMPORT_DATA_II | ||
ABAP code using 7.40 inline data declarations to call FM JGBP_0003_IMPORT_DATA_II
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 BOOLE FROM BOOLE INTO @DATA(ld_i_ucus). | ||||
| "SELECT single BU_GROUP FROM BUT000 INTO @DATA(ld_i_grid). | ||||
| "SELECT single RLTYP FROM BUT100 INTO @DATA(ld_i_role). | ||||
| "SELECT single ROLETYP FROM BP1000 INTO @DATA(ld_i_role_old). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_expn). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_corr). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_umst). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_coum). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_stan). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_anum). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_pnum). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_debi). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_chce). | ||||
Search for further information about these or an SAP related objects