SAP SDU_OUTGOING_RELATION_ADD Function Module for Create Outgoing Relationship
SDU_OUTGOING_RELATION_ADD is a standard sdu outgoing relation add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Outgoing Relationship 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 sdu outgoing relation add FM, simply by entering the name SDU_OUTGOING_RELATION_ADD into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDU7
Program Name: SAPLSDU7
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SDU_OUTGOING_RELATION_ADD 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 'SDU_OUTGOING_RELATION_ADD'"Create Outgoing Relationship.
EXPORTING
ENTIDFROM = "
* ENTIDTO = ' ' "
* EBROLNR = ' ' "Relationship role
* POPUP = 'X' "
IMPORTING
OK_CODE = "
RELATION_INFOS = "
EXCEPTIONS
PARAMETER_ERROR = 1 RELATION_ALREADY_EXISTS = 2 ENTIDTO_NOT_EXISTING = 3 ENTIDFROM_NOT_EXISTING = 4 ACTION_CANCELED = 5
IMPORTING Parameters details for SDU_OUTGOING_RELATION_ADD
ENTIDFROM -
Data type: DM42S-ENTIDFROMOptional: No
Call by Reference: No ( called with pass by value option)
ENTIDTO -
Data type: DM42S-ENTIDTODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EBROLNR - Relationship role
Data type: DM42S-EBROLNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
POPUP -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SDU_OUTGOING_RELATION_ADD
OK_CODE -
Data type: DMINF-FLG_ENTRYOptional: No
Call by Reference: No ( called with pass by value option)
RELATION_INFOS -
Data type: DM42VOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAMETER_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RELATION_ALREADY_EXISTS - Relationship Already Exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENTIDTO_NOT_EXISTING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENTIDFROM_NOT_EXISTING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ACTION_CANCELED - Action canceled
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SDU_OUTGOING_RELATION_ADD 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_ok_code | TYPE DMINF-FLG_ENTRY, " | |||
lv_entidfrom | TYPE DM42S-ENTIDFROM, " | |||
lv_parameter_error | TYPE DM42S, " | |||
lv_entidto | TYPE DM42S-ENTIDTO, " SPACE | |||
lv_relation_infos | TYPE DM42V, " | |||
lv_relation_already_exists | TYPE DM42V, " | |||
lv_ebrolnr | TYPE DM42S-EBROLNR, " SPACE | |||
lv_entidto_not_existing | TYPE DM42S, " | |||
lv_popup | TYPE DM42S, " 'X' | |||
lv_entidfrom_not_existing | TYPE DM42S, " | |||
lv_action_canceled | TYPE DM42S. " |
  CALL FUNCTION 'SDU_OUTGOING_RELATION_ADD' "Create Outgoing Relationship |
EXPORTING | ||
ENTIDFROM | = lv_entidfrom | |
ENTIDTO | = lv_entidto | |
EBROLNR | = lv_ebrolnr | |
POPUP | = lv_popup | |
IMPORTING | ||
OK_CODE | = lv_ok_code | |
RELATION_INFOS | = lv_relation_infos | |
EXCEPTIONS | ||
PARAMETER_ERROR = 1 | ||
RELATION_ALREADY_EXISTS = 2 | ||
ENTIDTO_NOT_EXISTING = 3 | ||
ENTIDFROM_NOT_EXISTING = 4 | ||
ACTION_CANCELED = 5 | ||
. " SDU_OUTGOING_RELATION_ADD |
ABAP code using 7.40 inline data declarations to call FM SDU_OUTGOING_RELATION_ADD
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 FLG_ENTRY FROM DMINF INTO @DATA(ld_ok_code). | ||||
"SELECT single ENTIDFROM FROM DM42S INTO @DATA(ld_entidfrom). | ||||
"SELECT single ENTIDTO FROM DM42S INTO @DATA(ld_entidto). | ||||
DATA(ld_entidto) | = ' '. | |||
"SELECT single EBROLNR FROM DM42S INTO @DATA(ld_ebrolnr). | ||||
DATA(ld_ebrolnr) | = ' '. | |||
DATA(ld_popup) | = 'X'. | |||
Search for further information about these or an SAP related objects