SAP CIF_PROGRAM_INSERT Function Module for NOTRANSL: Einfügen eines Programmes in die Entwicklungsumgebung
CIF_PROGRAM_INSERT is a standard cif program insert 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: Einfügen eines Programmes in die Entwicklungsumgebung 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 cif program insert FM, simply by entering the name CIF_PROGRAM_INSERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CIFG
Program Name: SAPLCIFG
Main Program: SAPLCIFG
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CIF_PROGRAM_INSERT 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 'CIF_PROGRAM_INSERT'"NOTRANSL: Einfügen eines Programmes in die Entwicklungsumgebung.
EXPORTING
* APPLICATION = 'X' "
* TRANSPORT_NUMBER = ' ' "
* AUTHORIZATION_GROUP = ' ' "
* DEVELOPMENT_CLASS = ' ' "
* EDIT_LOCK = ' ' "
* LOG_DB = ' ' "
PROGRAM_NAME = "
* PROGRAM_TYPE = '1' "
* TEMPORARY = ' ' "
TITLE_STRING = "
TABLES
SOURCE = "
EXCEPTIONS
ALREADY_EXISTS = 1 CANCELLED = 2 NAME_NOT_ALLOWED = 3 PERMISSION_ERROR = 4
IMPORTING Parameters details for CIF_PROGRAM_INSERT
APPLICATION -
Data type: RGLIF-APPLDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TRANSPORT_NUMBER -
Data type: RGLIF-TRKORRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
AUTHORIZATION_GROUP -
Data type: RGLIF-AUTHDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DEVELOPMENT_CLASS -
Data type: RGLIF-DEVCLASSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EDIT_LOCK -
Data type: RGLIF-EDIT_LOCKDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOG_DB -
Data type: RGLIF-LOGDBDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PROGRAM_NAME -
Data type: RGLIF-INCLUDEOptional: No
Call by Reference: No ( called with pass by value option)
PROGRAM_TYPE -
Data type: RGLIF-PROGTYPEDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TEMPORARY -
Data type: RGLIF-TEMPORARYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TITLE_STRING -
Data type: RGLIF-TITLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CIF_PROGRAM_INSERT
SOURCE -
Data type: ABAPSOURCEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ALREADY_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANCELLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NAME_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PERMISSION_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CIF_PROGRAM_INSERT 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: | ||||
| lt_source | TYPE STANDARD TABLE OF ABAPSOURCE, " | |||
| lv_application | TYPE RGLIF-APPL, " 'X' | |||
| lv_already_exists | TYPE RGLIF, " | |||
| lv_transport_number | TYPE RGLIF-TRKORR, " SPACE | |||
| lv_cancelled | TYPE RGLIF, " | |||
| lv_authorization_group | TYPE RGLIF-AUTH, " SPACE | |||
| lv_name_not_allowed | TYPE RGLIF, " | |||
| lv_development_class | TYPE RGLIF-DEVCLASS, " SPACE | |||
| lv_edit_lock | TYPE RGLIF-EDIT_LOCK, " SPACE | |||
| lv_permission_error | TYPE RGLIF, " | |||
| lv_log_db | TYPE RGLIF-LOGDB, " SPACE | |||
| lv_program_name | TYPE RGLIF-INCLUDE, " | |||
| lv_program_type | TYPE RGLIF-PROGTYPE, " '1' | |||
| lv_temporary | TYPE RGLIF-TEMPORARY, " SPACE | |||
| lv_title_string | TYPE RGLIF-TITLE. " |
|   CALL FUNCTION 'CIF_PROGRAM_INSERT' "NOTRANSL: Einfügen eines Programmes in die Entwicklungsumgebung |
| EXPORTING | ||
| APPLICATION | = lv_application | |
| TRANSPORT_NUMBER | = lv_transport_number | |
| AUTHORIZATION_GROUP | = lv_authorization_group | |
| DEVELOPMENT_CLASS | = lv_development_class | |
| EDIT_LOCK | = lv_edit_lock | |
| LOG_DB | = lv_log_db | |
| PROGRAM_NAME | = lv_program_name | |
| PROGRAM_TYPE | = lv_program_type | |
| TEMPORARY | = lv_temporary | |
| TITLE_STRING | = lv_title_string | |
| TABLES | ||
| SOURCE | = lt_source | |
| EXCEPTIONS | ||
| ALREADY_EXISTS = 1 | ||
| CANCELLED = 2 | ||
| NAME_NOT_ALLOWED = 3 | ||
| PERMISSION_ERROR = 4 | ||
| . " CIF_PROGRAM_INSERT | ||
ABAP code using 7.40 inline data declarations to call FM CIF_PROGRAM_INSERT
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 RGLIF INTO @DATA(ld_application). | ||||
| DATA(ld_application) | = 'X'. | |||
| "SELECT single TRKORR FROM RGLIF INTO @DATA(ld_transport_number). | ||||
| DATA(ld_transport_number) | = ' '. | |||
| "SELECT single AUTH FROM RGLIF INTO @DATA(ld_authorization_group). | ||||
| DATA(ld_authorization_group) | = ' '. | |||
| "SELECT single DEVCLASS FROM RGLIF INTO @DATA(ld_development_class). | ||||
| DATA(ld_development_class) | = ' '. | |||
| "SELECT single EDIT_LOCK FROM RGLIF INTO @DATA(ld_edit_lock). | ||||
| DATA(ld_edit_lock) | = ' '. | |||
| "SELECT single LOGDB FROM RGLIF INTO @DATA(ld_log_db). | ||||
| DATA(ld_log_db) | = ' '. | |||
| "SELECT single INCLUDE FROM RGLIF INTO @DATA(ld_program_name). | ||||
| "SELECT single PROGTYPE FROM RGLIF INTO @DATA(ld_program_type). | ||||
| DATA(ld_program_type) | = '1'. | |||
| "SELECT single TEMPORARY FROM RGLIF INTO @DATA(ld_temporary). | ||||
| DATA(ld_temporary) | = ' '. | |||
| "SELECT single TITLE FROM RGLIF INTO @DATA(ld_title_string). | ||||
Search for further information about these or an SAP related objects