SAP C1D3_ENTRY Function Module for NOTRANSL: EHS: Einstieg in die Layoutkopfbearbeitung mit Werteübergabe

Search SAP Function Modules

C1D3_ENTRY is a standard c1d3 entry 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: EHS: Einstieg in die Layoutkopfbearbeitung mit Werteübergabe 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 c1d3 entry FM, simply by entering the name C1D3_ENTRY into the relevant SAP transaction such as SE37 or SE38.

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

Function C1D3_ENTRY 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 'C1D3_ENTRY'"NOTRANSL: EHS: Einstieg in die Layoutkopfbearbeitung mit Werteübergabe
  EXPORTING
   I_ACTYPE =  "Current activity type
   I_TRTYPE =  "Current transaction type
   I_ADDINF =  "Additional information
   I_SEL_VALUES =  "

 IMPORTING
   E_FLG_CHANGED =  "Indicates whether data has been changed
   E_OKCODE =  "OKCODE that still needs to be processed
   E_HEAD =  "Substance header data that has probably been changed
   E_ACTYPE =  "

EXCEPTIONS
   NO_AUTHORITY = 1 

.

IMPORTING Parameters details for C1D3_ENTRY

I_ACTYPE - Current activity type

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

I_TRTYPE - Current transaction type

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

I_ADDINF - Additional information

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

I_SEL_VALUES -

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

EXPORTING Parameters details for C1D3_ENTRY

E_FLG_CHANGED - Indicates whether data has been changed

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

E_OKCODE - OKCODE that still needs to be processed

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

E_HEAD - Substance header data that has probably been changed

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

E_ACTYPE -

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

EXCEPTIONS details

NO_AUTHORITY -

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

Copy and paste ABAP code example for C1D3_ENTRY 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.

ABAP code using 7.40 inline data declarations to call FM C1D3_ENTRY

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