SAP PTRV_GET_CCC_MERGE Function Module for









PTRV_GET_CCC_MERGE is a standard ptrv get ccc merge 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 ptrv get ccc merge FM, simply by entering the name PTRV_GET_CCC_MERGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRTRV_UTIL
Program Name: SAPLHRTRV_UTIL
Main Program: SAPLHRTRV_UTIL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PTRV_GET_CCC_MERGE 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 'PTRV_GET_CCC_MERGE'"
EXPORTING
STRUC_NA = "
CCC_STRUC_MERGE_IN = "

CHANGING
CCC_STRUC_MERGE_CH = "

EXCEPTIONS
INTERNAL_ERROR = 1
.



IMPORTING Parameters details for PTRV_GET_CCC_MERGE

STRUC_NA -

Data type: DD02V-TABNAME
Optional: No
Call by Reference: Yes

CCC_STRUC_MERGE_IN -

Data type: ANY
Optional: No
Call by Reference: Yes

CHANGING Parameters details for PTRV_GET_CCC_MERGE

CCC_STRUC_MERGE_CH -

Data type: ANY
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PTRV_GET_CCC_MERGE 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_struc_na  TYPE DD02V-TABNAME, "   
lv_internal_error  TYPE DD02V, "   
lv_ccc_struc_merge_ch  TYPE ANY, "   
lv_ccc_struc_merge_in  TYPE ANY. "   

  CALL FUNCTION 'PTRV_GET_CCC_MERGE'  "
    EXPORTING
         STRUC_NA = lv_struc_na
         CCC_STRUC_MERGE_IN = lv_ccc_struc_merge_in
    CHANGING
         CCC_STRUC_MERGE_CH = lv_ccc_struc_merge_ch
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " PTRV_GET_CCC_MERGE




ABAP code using 7.40 inline data declarations to call FM PTRV_GET_CCC_MERGE

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 TABNAME FROM DD02V INTO @DATA(ld_struc_na).
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!