SAP CACS_OUTBOUND_PRC_0002 Function Module for NOTRANSL: Musterbaustein für EXIT: Feld 'Beschreibung' füllen
CACS_OUTBOUND_PRC_0002 is a standard cacs outbound prc 0002 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: Musterbaustein für EXIT: Feld 'Beschreibung' füllen 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 outbound prc 0002 FM, simply by entering the name CACS_OUTBOUND_PRC_0002 into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_OUTBOUND
Program Name: SAPLCACS_OUTBOUND
Main Program: SAPLCACS_OUTBOUND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_OUTBOUND_PRC_0002 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_OUTBOUND_PRC_0002'"NOTRANSL: Musterbaustein für EXIT: Feld 'Beschreibung' füllen.
EXPORTING
I_APPL = "Commission Application Identification
I_CTRTBU_ID = "Commission Contract Number
I_VERSION = "Version of Master Data or Customizing Object
I_CTRTST_ID = "Number of Standard Commission Contract
I_GPART = "Number of Commission Contract Partner
IMPORTING
E_DESCR_LONG = "Short description of standard commission contract
EXCEPTIONS
NO_DESTINATION = 1 NO_COMPONENT_ACTIVE = 2 ERROR_MULTIPLE_SELECTION = 3
IMPORTING Parameters details for CACS_OUTBOUND_PRC_0002
I_APPL - Commission Application Identification
Data type: CACS_CTRTBU-APPLOptional: No
Call by Reference: No ( called with pass by value option)
I_CTRTBU_ID - Commission Contract Number
Data type: CACS_CTRTBU-CTRTBU_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_VERSION - Version of Master Data or Customizing Object
Data type: CACS_CTRTBU-VERSIONOptional: No
Call by Reference: No ( called with pass by value option)
I_CTRTST_ID - Number of Standard Commission Contract
Data type: CACS_CTRTBU-CTRTST_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_GPART - Number of Commission Contract Partner
Data type: CACS_CTRTBU-GPARTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CACS_OUTBOUND_PRC_0002
E_DESCR_LONG - Short description of standard commission contract
Data type: CACS_CTRTSTT-DESCR_LONGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DESTINATION - Error in Remote Function Call
Data type:Optional: No
Call by Reference: Yes
NO_COMPONENT_ACTIVE - No active component
Data type:Optional: No
Call by Reference: Yes
ERROR_MULTIPLE_SELECTION - More than one entry exists
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_OUTBOUND_PRC_0002 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_i_appl | TYPE CACS_CTRTBU-APPL, " | |||
| lv_e_descr_long | TYPE CACS_CTRTSTT-DESCR_LONG, " | |||
| lv_no_destination | TYPE CACS_CTRTSTT, " | |||
| lv_i_ctrtbu_id | TYPE CACS_CTRTBU-CTRTBU_ID, " | |||
| lv_no_component_active | TYPE CACS_CTRTBU, " | |||
| lv_i_version | TYPE CACS_CTRTBU-VERSION, " | |||
| lv_error_multiple_selection | TYPE CACS_CTRTBU, " | |||
| lv_i_ctrtst_id | TYPE CACS_CTRTBU-CTRTST_ID, " | |||
| lv_i_gpart | TYPE CACS_CTRTBU-GPART. " |
|   CALL FUNCTION 'CACS_OUTBOUND_PRC_0002' "NOTRANSL: Musterbaustein für EXIT: Feld 'Beschreibung' füllen |
| EXPORTING | ||
| I_APPL | = lv_i_appl | |
| I_CTRTBU_ID | = lv_i_ctrtbu_id | |
| I_VERSION | = lv_i_version | |
| I_CTRTST_ID | = lv_i_ctrtst_id | |
| I_GPART | = lv_i_gpart | |
| IMPORTING | ||
| E_DESCR_LONG | = lv_e_descr_long | |
| EXCEPTIONS | ||
| NO_DESTINATION = 1 | ||
| NO_COMPONENT_ACTIVE = 2 | ||
| ERROR_MULTIPLE_SELECTION = 3 | ||
| . " CACS_OUTBOUND_PRC_0002 | ||
ABAP code using 7.40 inline data declarations to call FM CACS_OUTBOUND_PRC_0002
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 APPL FROM CACS_CTRTBU INTO @DATA(ld_i_appl). | ||||
| "SELECT single DESCR_LONG FROM CACS_CTRTSTT INTO @DATA(ld_e_descr_long). | ||||
| "SELECT single CTRTBU_ID FROM CACS_CTRTBU INTO @DATA(ld_i_ctrtbu_id). | ||||
| "SELECT single VERSION FROM CACS_CTRTBU INTO @DATA(ld_i_version). | ||||
| "SELECT single CTRTST_ID FROM CACS_CTRTBU INTO @DATA(ld_i_ctrtst_id). | ||||
| "SELECT single GPART FROM CACS_CTRTBU INTO @DATA(ld_i_gpart). | ||||
Search for further information about these or an SAP related objects