SAP OIJ_GET_ROLES_FOR_OBJECT Function Module for Get TSW-Roles for Object (Customer/Vendor/Plant/Stor.Loc)
OIJ_GET_ROLES_FOR_OBJECT is a standard oij get roles for object SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get TSW-Roles for Object (Customer/Vendor/Plant/Stor.Loc) 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 oij get roles for object FM, simply by entering the name OIJ_GET_ROLES_FOR_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJR
Program Name: SAPLOIJR
Main Program: SAPLOIJR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIJ_GET_ROLES_FOR_OBJECT 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 'OIJ_GET_ROLES_FOR_OBJECT'"Get TSW-Roles for Object (Customer/Vendor/Plant/Stor.Loc).
EXPORTING
RPART = "Describe Source of Objects (e.g. WK=Werk (Plant)
* KUNNR = "Object ID Customer
* LIFNR = "Object ID Vendor
* WERK = "Object ID Plant
* LGORT = "Object ID Storage Location
TABLES
SEL_OIJRRA_TAB = "Return Table with selected Partner Roles
EXCEPTIONS
WRONG_PARTNER_TYPE = 1 KUNNR_NOT_FOUND = 2 LIFNR_NOT_FOUND = 3 WERK_NOT_FOUND = 4 SL_NOT_FOUND = 5 NO_ENTRY_FOUND = 6 WRONG_IMPORT_PARAMETER = 7
IMPORTING Parameters details for OIJ_GET_ROLES_FOR_OBJECT
RPART - Describe Source of Objects (e.g. WK=Werk (Plant)
Data type: OIJRRA-RPARTOptional: No
Call by Reference: No ( called with pass by value option)
KUNNR - Object ID Customer
Data type: OIJRRA-KUNNROptional: Yes
Call by Reference: No ( called with pass by value option)
LIFNR - Object ID Vendor
Data type: OIJRRA-LIFNROptional: Yes
Call by Reference: No ( called with pass by value option)
WERK - Object ID Plant
Data type: OIJRRA-WERKOptional: Yes
Call by Reference: No ( called with pass by value option)
LGORT - Object ID Storage Location
Data type: OIJRRA-LGORTOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OIJ_GET_ROLES_FOR_OBJECT
SEL_OIJRRA_TAB - Return Table with selected Partner Roles
Data type: OIJRRAOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_PARTNER_TYPE - RPART ne KN/LF/WK/LG see Table OIJRRPART
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
KUNNR_NOT_FOUND - what could that mean ?
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LIFNR_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WERK_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SL_NOT_FOUND - Storage Location n.f.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ENTRY_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_IMPORT_PARAMETER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIJ_GET_ROLES_FOR_OBJECT 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_rpart | TYPE OIJRRA-RPART, " | |||
| lt_sel_oijrra_tab | TYPE STANDARD TABLE OF OIJRRA, " | |||
| lv_wrong_partner_type | TYPE OIJRRA, " | |||
| lv_kunnr | TYPE OIJRRA-KUNNR, " | |||
| lv_kunnr_not_found | TYPE OIJRRA, " | |||
| lv_lifnr | TYPE OIJRRA-LIFNR, " | |||
| lv_lifnr_not_found | TYPE OIJRRA, " | |||
| lv_werk | TYPE OIJRRA-WERK, " | |||
| lv_werk_not_found | TYPE OIJRRA, " | |||
| lv_lgort | TYPE OIJRRA-LGORT, " | |||
| lv_sl_not_found | TYPE OIJRRA, " | |||
| lv_no_entry_found | TYPE OIJRRA, " | |||
| lv_wrong_import_parameter | TYPE OIJRRA. " |
|   CALL FUNCTION 'OIJ_GET_ROLES_FOR_OBJECT' "Get TSW-Roles for Object (Customer/Vendor/Plant/Stor.Loc) |
| EXPORTING | ||
| RPART | = lv_rpart | |
| KUNNR | = lv_kunnr | |
| LIFNR | = lv_lifnr | |
| WERK | = lv_werk | |
| LGORT | = lv_lgort | |
| TABLES | ||
| SEL_OIJRRA_TAB | = lt_sel_oijrra_tab | |
| EXCEPTIONS | ||
| WRONG_PARTNER_TYPE = 1 | ||
| KUNNR_NOT_FOUND = 2 | ||
| LIFNR_NOT_FOUND = 3 | ||
| WERK_NOT_FOUND = 4 | ||
| SL_NOT_FOUND = 5 | ||
| NO_ENTRY_FOUND = 6 | ||
| WRONG_IMPORT_PARAMETER = 7 | ||
| . " OIJ_GET_ROLES_FOR_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM OIJ_GET_ROLES_FOR_OBJECT
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 RPART FROM OIJRRA INTO @DATA(ld_rpart). | ||||
| "SELECT single KUNNR FROM OIJRRA INTO @DATA(ld_kunnr). | ||||
| "SELECT single LIFNR FROM OIJRRA INTO @DATA(ld_lifnr). | ||||
| "SELECT single WERK FROM OIJRRA INTO @DATA(ld_werk). | ||||
| "SELECT single LGORT FROM OIJRRA INTO @DATA(ld_lgort). | ||||
Search for further information about these or an SAP related objects