SAP HRCA_UNIQUE_RECEIVER_COMPCODE Function Module for
HRCA_UNIQUE_RECEIVER_COMPCODE is a standard hrca unique receiver compcode 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 hrca unique receiver compcode FM, simply by entering the name HRCA_UNIQUE_RECEIVER_COMPCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHDS
Program Name: SAPLRHDS
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRCA_UNIQUE_RECEIVER_COMPCODE 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 'HRCA_UNIQUE_RECEIVER_COMPCODE'".
EXPORTING
OBJECT = "
METHOD = "
COMP_CODE = "
IMPORTING
LOGICAL_SYSTEM = "
RFC_DESTINATION = "
EXCEPTIONS
ERROR_IN_FILTEROBJECTS = 1 ERROR_IN_ALE_CUSTOMIZING = 2 NOT_UNIQUE_RECEIVER = 3 NO_RFC_DESTINATION_MAINTAINED = 4 OTHER_ERROR = 5
IMPORTING Parameters details for HRCA_UNIQUE_RECEIVER_COMPCODE
OBJECT -
Data type: BDI_BAPI-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
METHOD -
Data type: BDI_BAPI-METHODOptional: No
Call by Reference: No ( called with pass by value option)
COMP_CODE -
Data type: HRCA_COMPANY-COMP_CODEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HRCA_UNIQUE_RECEIVER_COMPCODE
LOGICAL_SYSTEM -
Data type: BDBAPIDEST-LOG_SYSOptional: No
Call by Reference: No ( called with pass by value option)
RFC_DESTINATION -
Data type: BDBAPIDEST-RFC_DESTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_IN_FILTEROBJECTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_IN_ALE_CUSTOMIZING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_UNIQUE_RECEIVER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_RFC_DESTINATION_MAINTAINED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OTHER_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HRCA_UNIQUE_RECEIVER_COMPCODE 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 | TYPE BDI_BAPI-OBJECT, " | |||
| lv_logical_system | TYPE BDBAPIDEST-LOG_SYS, " | |||
| lv_error_in_filterobjects | TYPE BDBAPIDEST, " | |||
| lv_method | TYPE BDI_BAPI-METHOD, " | |||
| lv_rfc_destination | TYPE BDBAPIDEST-RFC_DEST, " | |||
| lv_error_in_ale_customizing | TYPE BDBAPIDEST, " | |||
| lv_comp_code | TYPE HRCA_COMPANY-COMP_CODE, " | |||
| lv_not_unique_receiver | TYPE HRCA_COMPANY, " | |||
| lv_no_rfc_destination_maintained | TYPE HRCA_COMPANY, " | |||
| lv_other_error | TYPE HRCA_COMPANY. " |
|   CALL FUNCTION 'HRCA_UNIQUE_RECEIVER_COMPCODE' " |
| EXPORTING | ||
| OBJECT | = lv_object | |
| METHOD | = lv_method | |
| COMP_CODE | = lv_comp_code | |
| IMPORTING | ||
| LOGICAL_SYSTEM | = lv_logical_system | |
| RFC_DESTINATION | = lv_rfc_destination | |
| EXCEPTIONS | ||
| ERROR_IN_FILTEROBJECTS = 1 | ||
| ERROR_IN_ALE_CUSTOMIZING = 2 | ||
| NOT_UNIQUE_RECEIVER = 3 | ||
| NO_RFC_DESTINATION_MAINTAINED = 4 | ||
| OTHER_ERROR = 5 | ||
| . " HRCA_UNIQUE_RECEIVER_COMPCODE | ||
ABAP code using 7.40 inline data declarations to call FM HRCA_UNIQUE_RECEIVER_COMPCODE
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 OBJECT FROM BDI_BAPI INTO @DATA(ld_object). | ||||
| "SELECT single LOG_SYS FROM BDBAPIDEST INTO @DATA(ld_logical_system). | ||||
| "SELECT single METHOD FROM BDI_BAPI INTO @DATA(ld_method). | ||||
| "SELECT single RFC_DEST FROM BDBAPIDEST INTO @DATA(ld_rfc_destination). | ||||
| "SELECT single COMP_CODE FROM HRCA_COMPANY INTO @DATA(ld_comp_code). | ||||
Search for further information about these or an SAP related objects