SAP CACS_ORG_PARTNER_GET Function Module for NOTRANSL: BP zu User ermitteln
CACS_ORG_PARTNER_GET is a standard cacs org partner 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 NOTRANSL: BP zu User ermitteln 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 cacs org partner get FM, simply by entering the name CACS_ORG_PARTNER_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_ORG_PERMISSION
Program Name: SAPLCACS_ORG_PERMISSION
Main Program: SAPLCACS_ORG_PERMISSION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_ORG_PARTNER_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 'CACS_ORG_PARTNER_GET'"NOTRANSL: BP zu User ermitteln.
EXPORTING
* I_PERSON_ID = "Person number
* I_BU_PARTNER_GUID = "Business Partner GUID
* I_EMPLOYEE_ID = "Personnel Number
* I_USERNAME = "SAP System, User Logon Name
IMPORTING
E_PARTNER = "Business Partner Number
E_PARTNER_GUID = "Business Partner GUID
E_PARTNER_EXTERNAL = "Business Partner Number in External System
TABLES
* ET_RETURN = "Notifications
IMPORTING Parameters details for CACS_ORG_PARTNER_GET
I_PERSON_ID - Person number
Data type: PERSONIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BU_PARTNER_GUID - Business Partner GUID
Data type: BUPAGUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EMPLOYEE_ID - Personnel Number
Data type: PERNR_DOptional: Yes
Call by Reference: No ( called with pass by value option)
I_USERNAME - SAP System, User Logon Name
Data type: SYUNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CACS_ORG_PARTNER_GET
E_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
E_PARTNER_GUID - Business Partner GUID
Data type: BU_PARTNER_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
E_PARTNER_EXTERNAL - Business Partner Number in External System
Data type: BU_BPEXTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CACS_ORG_PARTNER_GET
ET_RETURN - Notifications
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CACS_ORG_PARTNER_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: | ||||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_e_partner | TYPE BU_PARTNER, " | |||
| lv_i_person_id | TYPE PERSONID, " | |||
| lv_e_partner_guid | TYPE BU_PARTNER_GUID, " | |||
| lv_i_bu_partner_guid | TYPE BUPAGUID, " | |||
| lv_i_employee_id | TYPE PERNR_D, " | |||
| lv_e_partner_external | TYPE BU_BPEXT, " | |||
| lv_i_username | TYPE SYUNAME. " |
|   CALL FUNCTION 'CACS_ORG_PARTNER_GET' "NOTRANSL: BP zu User ermitteln |
| EXPORTING | ||
| I_PERSON_ID | = lv_i_person_id | |
| I_BU_PARTNER_GUID | = lv_i_bu_partner_guid | |
| I_EMPLOYEE_ID | = lv_i_employee_id | |
| I_USERNAME | = lv_i_username | |
| IMPORTING | ||
| E_PARTNER | = lv_e_partner | |
| E_PARTNER_GUID | = lv_e_partner_guid | |
| E_PARTNER_EXTERNAL | = lv_e_partner_external | |
| TABLES | ||
| ET_RETURN | = lt_et_return | |
| . " CACS_ORG_PARTNER_GET | ||
ABAP code using 7.40 inline data declarations to call FM CACS_ORG_PARTNER_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.Search for further information about these or an SAP related objects