SAP C10DGPACK_ENTRY_DETAIL Function Module for NOTRANSL: Dummy; neede for double-click functionality









C10DGPACK_ENTRY_DETAIL is a standard c10dgpack entry detail 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: Dummy; neede for double-click functionality 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 c10dgpack entry detail FM, simply by entering the name C10DGPACK_ENTRY_DETAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function C10DGPACK_ENTRY_DETAIL 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 'C10DGPACK_ENTRY_DETAIL'"NOTRANSL: Dummy; neede for double-click functionality
EXPORTING
I_ACTYPE = "Activity Type in the Transaction
I_ADDINF = "EHS: Additional Information for Function Module Calls
I_KEYPATH = "EHS: 'Key' path substance/list/property for FM call
I_TRTYPE = "Transaction Type
* I_CUA_SET_FUNC = 'C101_CUA_SET' "Name of Function Module
I_OKCODE = "ABAP Program, Current Transaction Code

IMPORTING
E_OKCODE = "ABAP Program, Current Transaction Code

EXCEPTIONS
INCORRECT_CALL = 1
.



IMPORTING Parameters details for C10DGPACK_ENTRY_DETAIL

I_ACTYPE - Activity Type in the Transaction

Data type: RCGDIALCTR-ACTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_ADDINF - EHS: Additional Information for Function Module Calls

Data type: RCGADDINF
Optional: No
Call by Reference: No ( called with pass by value option)

I_KEYPATH - EHS: 'Key' path substance/list/property for FM call

Data type: RCGKPATH
Optional: No
Call by Reference: No ( called with pass by value option)

I_TRTYPE - Transaction Type

Data type: RCGDIALCTR-TRTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_CUA_SET_FUNC - Name of Function Module

Data type: TFDIR-FUNCNAME
Default: 'C101_CUA_SET'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_OKCODE - ABAP Program, Current Transaction Code

Data type: ESP1_OKCODE_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for C10DGPACK_ENTRY_DETAIL

E_OKCODE - ABAP Program, Current Transaction Code

Data type: ESP1_OKCODE_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INCORRECT_CALL -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for C10DGPACK_ENTRY_DETAIL 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_e_okcode  TYPE ESP1_OKCODE_TYPE, "   
lv_i_actype  TYPE RCGDIALCTR-ACTYPE, "   
lv_incorrect_call  TYPE RCGDIALCTR, "   
lv_i_addinf  TYPE RCGADDINF, "   
lv_i_keypath  TYPE RCGKPATH, "   
lv_i_trtype  TYPE RCGDIALCTR-TRTYPE, "   
lv_i_cua_set_func  TYPE TFDIR-FUNCNAME, "   'C101_CUA_SET'
lv_i_okcode  TYPE ESP1_OKCODE_TYPE. "   

  CALL FUNCTION 'C10DGPACK_ENTRY_DETAIL'  "NOTRANSL: Dummy; neede for double-click functionality
    EXPORTING
         I_ACTYPE = lv_i_actype
         I_ADDINF = lv_i_addinf
         I_KEYPATH = lv_i_keypath
         I_TRTYPE = lv_i_trtype
         I_CUA_SET_FUNC = lv_i_cua_set_func
         I_OKCODE = lv_i_okcode
    IMPORTING
         E_OKCODE = lv_e_okcode
    EXCEPTIONS
        INCORRECT_CALL = 1
. " C10DGPACK_ENTRY_DETAIL




ABAP code using 7.40 inline data declarations to call FM C10DGPACK_ENTRY_DETAIL

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 ACTYPE FROM RCGDIALCTR INTO @DATA(ld_i_actype).
 
 
 
 
"SELECT single TRTYPE FROM RCGDIALCTR INTO @DATA(ld_i_trtype).
 
"SELECT single FUNCNAME FROM TFDIR INTO @DATA(ld_i_cua_set_func).
DATA(ld_i_cua_set_func) = 'C101_CUA_SET'.
 
 


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!