SAP C15A_MANDATORY_FIELDS_GET Function Module for NOTRANSL: EHS: obligatorische Felder zur Tabelle
C15A_MANDATORY_FIELDS_GET is a standard c15a mandatory fields get 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: obligatorische Felder zur Tabelle 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 c15a mandatory fields get FM, simply by entering the name C15A_MANDATORY_FIELDS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: C15A
Program Name: SAPLC15A
Main Program: SAPLC15A
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function C15A_MANDATORY_FIELDS_GET 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 'C15A_MANDATORY_FIELDS_GET'"NOTRANSL: EHS: obligatorische Felder zur Tabelle.
EXPORTING
I_TABLENAME = "Table Name
TABLES
E_MANDATORY_FIELD_TAB = "Required Fields
IMPORTING Parameters details for C15A_MANDATORY_FIELDS_GET
I_TABLENAME - Table Name
Data type: DD02L-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for C15A_MANDATORY_FIELDS_GET
E_MANDATORY_FIELD_TAB - Required Fields
Data type: ESP1_FIELDNAME_TAB_TYPEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for C15A_MANDATORY_FIELDS_GET 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_tablename | TYPE DD02L-TABNAME, " | |||
| lt_e_mandatory_field_tab | TYPE STANDARD TABLE OF ESP1_FIELDNAME_TAB_TYPE. " |
|   CALL FUNCTION 'C15A_MANDATORY_FIELDS_GET' "NOTRANSL: EHS: obligatorische Felder zur Tabelle |
| EXPORTING | ||
| I_TABLENAME | = lv_i_tablename | |
| TABLES | ||
| E_MANDATORY_FIELD_TAB | = lt_e_mandatory_field_tab | |
| . " C15A_MANDATORY_FIELDS_GET | ||
ABAP code using 7.40 inline data declarations to call FM C15A_MANDATORY_FIELDS_GET
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 DD02L INTO @DATA(ld_i_tablename). | ||||
Search for further information about these or an SAP related objects