SAP SDOK_PHIO_TO_RELATIONS_GET Function Module for Determine outgoing relationships for physical information object
SDOK_PHIO_TO_RELATIONS_GET is a standard sdok phio to relations get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine outgoing relationships for physical information object 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 sdok phio to relations get FM, simply by entering the name SDOK_PHIO_TO_RELATIONS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDCL
Program Name: SAPLSDCL
Main Program: SAPLSDCL
Appliation area: S
Release date: 29-Oct-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function SDOK_PHIO_TO_RELATIONS_GET 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 'SDOK_PHIO_TO_RELATIONS_GET'"Determine outgoing relationships for physical information object.
EXPORTING
OBJECT_ID = "BOR Key for the Object
* RELATION_CLASS = "Relationship Class
* CLIENT = SY-MANDT "Client
TABLES
* CLASS_FILTER = "Filter for Allowed Class Combinations
RESULT = "Relationships with Associated Partner Objects
EXCEPTIONS
NOT_EXISTING = 1 BAD_CLASS = 2 NOT_AUTHORIZED = 3 EXCEPTION_IN_EXIT = 4
IMPORTING Parameters details for SDOK_PHIO_TO_RELATIONS_GET
OBJECT_ID - BOR Key for the Object
Data type: SDOKOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
RELATION_CLASS - Relationship Class
Data type: SDOKRECL-RE_CLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - Client
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SDOK_PHIO_TO_RELATIONS_GET
CLASS_FILTER - Filter for Allowed Class Combinations
Data type: SDOKRECLFLOptional: Yes
Call by Reference: No ( called with pass by value option)
RESULT - Relationships with Associated Partner Objects
Data type: SDOKRELISTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_EXISTING - Object does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BAD_CLASS - Relationship class is invalid or does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_AUTHORIZED - No Authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTION_IN_EXIT - Exception in application exit
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SDOK_PHIO_TO_RELATIONS_GET 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_object_id | TYPE SDOKOBJECT, " | |||
lt_class_filter | TYPE STANDARD TABLE OF SDOKRECLFL, " | |||
lv_not_existing | TYPE SDOKRECLFL, " | |||
lt_result | TYPE STANDARD TABLE OF SDOKRELIST, " | |||
lv_bad_class | TYPE SDOKRELIST, " | |||
lv_relation_class | TYPE SDOKRECL-RE_CLASS, " | |||
lv_client | TYPE SY-MANDT, " SY-MANDT | |||
lv_not_authorized | TYPE SY, " | |||
lv_exception_in_exit | TYPE SY. " |
  CALL FUNCTION 'SDOK_PHIO_TO_RELATIONS_GET' "Determine outgoing relationships for physical information object |
EXPORTING | ||
OBJECT_ID | = lv_object_id | |
RELATION_CLASS | = lv_relation_class | |
CLIENT | = lv_client | |
TABLES | ||
CLASS_FILTER | = lt_class_filter | |
RESULT | = lt_result | |
EXCEPTIONS | ||
NOT_EXISTING = 1 | ||
BAD_CLASS = 2 | ||
NOT_AUTHORIZED = 3 | ||
EXCEPTION_IN_EXIT = 4 | ||
. " SDOK_PHIO_TO_RELATIONS_GET |
ABAP code using 7.40 inline data declarations to call FM SDOK_PHIO_TO_RELATIONS_GET
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 RE_CLASS FROM SDOKRECL INTO @DATA(ld_relation_class). | ||||
"SELECT single MANDT FROM SY INTO @DATA(ld_client). | ||||
DATA(ld_client) | = SY-MANDT. | |||
Search for further information about these or an SAP related objects