SAP BURS_RELATIONS_INIT Function Module for
BURS_RELATIONS_INIT is a standard burs relations init 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 burs relations init FM, simply by entering the name BURS_RELATIONS_INIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: BURS
Program Name: SAPLBURS
Main Program: SAPLBURS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BURS_RELATIONS_INIT 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 'BURS_RELATIONS_INIT'".
EXPORTING
* IV_XFILTER = ' ' "
* IV_CODTETR = 'S' "Indicator: Transfer differentiation type specifications
* IV_DATE_FIX = "
* IV_XSAVE = 'X' "Indicator: Business partner safeguards himself
* IV_XUPDTASK = 'X' "
* IV_RELMODE = GC_MODE_STANDALONE "Session for maint.bus.partner's relationship/role definition
* IV_XALL = ' ' "Maintain all relationships for a partner
* IV_PARTNER = "Business Partner Number
IMPORTING
EV_XEXIT_DTE = "
TABLES
* IT_RLTYP_MAINTENANCE = "
* IR_RELTYP = "
* IR_RLDTYP = "
* IR_PARTNER1 = "
* IR_RLTYP = "
* IR_PARTNER2 = "
* IT_DTEVAL = "
IMPORTING Parameters details for BURS_RELATIONS_INIT
IV_XFILTER -
Data type: BOOLE-BOOLEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CODTETR - Indicator: Transfer differentiation type specifications
Data type: BU_CODFTTRDefault: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_DATE_FIX -
Data type: SYDATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_XSAVE - Indicator: Business partner safeguards himself
Data type: BU_XSAVEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_XUPDTASK -
Data type: BOOLE-BOOLEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_RELMODE - Session for maint.bus.partner's relationship/role definition
Data type: BU_RELMODEDefault: GC_MODE_STANDALONE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_XALL - Maintain all relationships for a partner
Data type: BU_XALLDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BURS_RELATIONS_INIT
EV_XEXIT_DTE -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BURS_RELATIONS_INIT
IT_RLTYP_MAINTENANCE -
Data type: BUS0RLTYPOptional: Yes
Call by Reference: Yes
IR_RELTYP -
Data type: BUS050_BTROptional: Yes
Call by Reference: Yes
IR_RLDTYP -
Data type: BUS050_BTROptional: Yes
Call by Reference: Yes
IR_PARTNER1 -
Data type: BUS050_GPOptional: Yes
Call by Reference: Yes
IR_RLTYP -
Data type: BUS050_RTROptional: Yes
Call by Reference: Yes
IR_PARTNER2 -
Data type: BUS050_GPOptional: Yes
Call by Reference: Yes
IT_DTEVAL -
Data type: BUB01_DTELEM_TABOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BURS_RELATIONS_INIT 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_iv_xfilter | TYPE BOOLE-BOOLE, " ' ' | |||
| lv_ev_xexit_dte | TYPE BOOLE-BOOLE, " | |||
| lt_it_rltyp_maintenance | TYPE STANDARD TABLE OF BUS0RLTYP, " | |||
| lt_ir_reltyp | TYPE STANDARD TABLE OF BUS050_BTR, " | |||
| lv_iv_codtetr | TYPE BU_CODFTTR, " 'S' | |||
| lt_ir_rldtyp | TYPE STANDARD TABLE OF BUS050_BTR, " | |||
| lv_iv_date_fix | TYPE SYDATUM, " | |||
| lv_iv_xsave | TYPE BU_XSAVE, " 'X' | |||
| lt_ir_partner1 | TYPE STANDARD TABLE OF BUS050_GP, " | |||
| lt_ir_rltyp | TYPE STANDARD TABLE OF BUS050_RTR, " | |||
| lv_iv_xupdtask | TYPE BOOLE-BOOLE, " 'X' | |||
| lv_iv_relmode | TYPE BU_RELMODE, " GC_MODE_STANDALONE | |||
| lt_ir_partner2 | TYPE STANDARD TABLE OF BUS050_GP, " | |||
| lv_iv_xall | TYPE BU_XALL, " ' ' | |||
| lt_it_dteval | TYPE STANDARD TABLE OF BUB01_DTELEM_TAB, " | |||
| lv_iv_partner | TYPE BU_PARTNER. " |
|   CALL FUNCTION 'BURS_RELATIONS_INIT' " |
| EXPORTING | ||
| IV_XFILTER | = lv_iv_xfilter | |
| IV_CODTETR | = lv_iv_codtetr | |
| IV_DATE_FIX | = lv_iv_date_fix | |
| IV_XSAVE | = lv_iv_xsave | |
| IV_XUPDTASK | = lv_iv_xupdtask | |
| IV_RELMODE | = lv_iv_relmode | |
| IV_XALL | = lv_iv_xall | |
| IV_PARTNER | = lv_iv_partner | |
| IMPORTING | ||
| EV_XEXIT_DTE | = lv_ev_xexit_dte | |
| TABLES | ||
| IT_RLTYP_MAINTENANCE | = lt_it_rltyp_maintenance | |
| IR_RELTYP | = lt_ir_reltyp | |
| IR_RLDTYP | = lt_ir_rldtyp | |
| IR_PARTNER1 | = lt_ir_partner1 | |
| IR_RLTYP | = lt_ir_rltyp | |
| IR_PARTNER2 | = lt_ir_partner2 | |
| IT_DTEVAL | = lt_it_dteval | |
| . " BURS_RELATIONS_INIT | ||
ABAP code using 7.40 inline data declarations to call FM BURS_RELATIONS_INIT
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_iv_xfilter). | ||||
| DATA(ld_iv_xfilter) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_ev_xexit_dte). | ||||
| DATA(ld_iv_codtetr) | = 'S'. | |||
| DATA(ld_iv_xsave) | = 'X'. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_iv_xupdtask). | ||||
| DATA(ld_iv_xupdtask) | = 'X'. | |||
| DATA(ld_iv_relmode) | = GC_MODE_STANDALONE. | |||
| DATA(ld_iv_xall) | = ' '. | |||
Search for further information about these or an SAP related objects