SAP BAPI_RE_JL_CREATE Function Module for
BAPI_RE_JL_CREATE is a standard bapi re jl create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bapi re jl create FM, simply by entering the name BAPI_RE_JL_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RELM_BAPI_JOINT_LIAB
Program Name: SAPLRELM_BAPI_JOINT_LIAB
Main Program: SAPLRELM_BAPI_JOINT_LIAB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_RE_JL_CREATE 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 'BAPI_RE_JL_CREATE'".
EXPORTING
JOINT_LIABILITY_NUMBER_EXT = "
* JOINT_LIABILITY = "
* TRANS = "
* TEST_RUN = ' ' "
IMPORTING
JOINTLIABILITYNUMBER = "
TABLES
* LAND_REG_REL = "
* RESUBM_RULE = "
* STATUS = "
* EXTENSION_IN = "
RETURN = "
IMPORTING Parameters details for BAPI_RE_JL_CREATE
JOINT_LIABILITY_NUMBER_EXT -
Data type: BAPI_RE_JOINT_LIAB_KEY-JOINT_LIABILITY_NUMBEROptional: No
Call by Reference: No ( called with pass by value option)
JOINT_LIABILITY -
Data type: BAPI_RE_JOINT_LIAB_DATOptional: Yes
Call by Reference: No ( called with pass by value option)
TRANS -
Data type: BAPI_RE_ADDITIONAL_FIELDS-TRANSOptional: Yes
Call by Reference: No ( called with pass by value option)
TEST_RUN -
Data type: BAPI_RE_ADDITIONAL_FIELDS-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_RE_JL_CREATE
JOINTLIABILITYNUMBER -
Data type: BAPI_RE_JOINT_LIAB_KEY-JOINT_LIABILITY_NUMBEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_RE_JL_CREATE
LAND_REG_REL -
Data type: BAPI_RE_JL_LR_REL_DATOptional: Yes
Call by Reference: Yes
RESUBM_RULE -
Data type: BAPI_RE_RESUBM_RULE_DATOptional: Yes
Call by Reference: No ( called with pass by value option)
STATUS -
Data type: BAPI_RE_STATUS_DATOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSION_IN -
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_RE_JL_CREATE 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: | ||||
| lt_land_reg_rel | TYPE STANDARD TABLE OF BAPI_RE_JL_LR_REL_DAT, " | |||
| lv_jointliabilitynumber | TYPE BAPI_RE_JOINT_LIAB_KEY-JOINT_LIABILITY_NUMBER, " | |||
| lv_joint_liability_number_ext | TYPE BAPI_RE_JOINT_LIAB_KEY-JOINT_LIABILITY_NUMBER, " | |||
| lt_resubm_rule | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE_DAT, " | |||
| lv_joint_liability | TYPE BAPI_RE_JOINT_LIAB_DAT, " | |||
| lv_trans | TYPE BAPI_RE_ADDITIONAL_FIELDS-TRANS, " | |||
| lt_status | TYPE STANDARD TABLE OF BAPI_RE_STATUS_DAT, " | |||
| lv_test_run | TYPE BAPI_RE_ADDITIONAL_FIELDS-TESTRUN, " SPACE | |||
| lt_extension_in | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BAPI_RE_JL_CREATE' " |
| EXPORTING | ||
| JOINT_LIABILITY_NUMBER_EXT | = lv_joint_liability_number_ext | |
| JOINT_LIABILITY | = lv_joint_liability | |
| TRANS | = lv_trans | |
| TEST_RUN | = lv_test_run | |
| IMPORTING | ||
| JOINTLIABILITYNUMBER | = lv_jointliabilitynumber | |
| TABLES | ||
| LAND_REG_REL | = lt_land_reg_rel | |
| RESUBM_RULE | = lt_resubm_rule | |
| STATUS | = lt_status | |
| EXTENSION_IN | = lt_extension_in | |
| RETURN | = lt_return | |
| . " BAPI_RE_JL_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_RE_JL_CREATE
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 JOINT_LIABILITY_NUMBER FROM BAPI_RE_JOINT_LIAB_KEY INTO @DATA(ld_jointliabilitynumber). | ||||
| "SELECT single JOINT_LIABILITY_NUMBER FROM BAPI_RE_JOINT_LIAB_KEY INTO @DATA(ld_joint_liability_number_ext). | ||||
| "SELECT single TRANS FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_trans). | ||||
| "SELECT single TESTRUN FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_test_run). | ||||
| DATA(ld_test_run) | = ' '. | |||
Search for further information about these or an SAP related objects