SAP CNIF_CONSTRUCT_STATUS_STRING Function Module for NOTRANSL: String der aktiven 4-stelligen Status erzeugen
CNIF_CONSTRUCT_STATUS_STRING is a standard cnif construct status string 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: String der aktiven 4-stelligen Status erzeugen 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 cnif construct status string FM, simply by entering the name CNIF_CONSTRUCT_STATUS_STRING into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNIF
Program Name: SAPLCNIF
Main Program: SAPLCNIF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNIF_CONSTRUCT_STATUS_STRING 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 'CNIF_CONSTRUCT_STATUS_STRING'"NOTRANSL: String der aktiven 4-stelligen Status erzeugen.
EXPORTING
* IV_TAB = ' ' "Selection indicator
* IV_STAT_SPE = 'I0043' "Object status
* IV_ABG = ' ' "Selection indicator
* IV_LOE = ' ' "Selection indicator
* IV_LVM = ' ' "Selection indicator
* IV_SPE = ' ' "Selection indicator
* IV_STAT_TAB = 'I0045' "Object status
* IV_STAT_ABG = 'I0046' "Object status
* IV_STAT_LOE = 'I0013' "Object status
* IV_STAT_LVM = 'I0076' "Object status
IMPORTING
EV_STATUS_STRING = "Predefined Type
IMPORTING Parameters details for CNIF_CONSTRUCT_STATUS_STRING
IV_TAB - Selection indicator
Data type: FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: Yes
IV_STAT_SPE - Object status
Data type: JEST-STATDefault: 'I0043'
Optional: Yes
Call by Reference: Yes
IV_ABG - Selection indicator
Data type: FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: Yes
IV_LOE - Selection indicator
Data type: FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: Yes
IV_LVM - Selection indicator
Data type: FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: Yes
IV_SPE - Selection indicator
Data type: FLG_SELDefault: SPACE
Optional: Yes
Call by Reference: Yes
IV_STAT_TAB - Object status
Data type: JEST-STATDefault: 'I0045'
Optional: Yes
Call by Reference: Yes
IV_STAT_ABG - Object status
Data type: JEST-STATDefault: 'I0046'
Optional: Yes
Call by Reference: Yes
IV_STAT_LOE - Object status
Data type: JEST-STATDefault: 'I0013'
Optional: Yes
Call by Reference: Yes
IV_STAT_LVM - Object status
Data type: JEST-STATDefault: 'I0076'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CNIF_CONSTRUCT_STATUS_STRING
EV_STATUS_STRING - Predefined Type
Data type: STRINGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNIF_CONSTRUCT_STATUS_STRING 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_iv_tab | TYPE FLG_SEL, " SPACE | |||
| lv_ev_status_string | TYPE STRING, " | |||
| lv_iv_stat_spe | TYPE JEST-STAT, " 'I0043' | |||
| lv_iv_abg | TYPE FLG_SEL, " SPACE | |||
| lv_iv_loe | TYPE FLG_SEL, " SPACE | |||
| lv_iv_lvm | TYPE FLG_SEL, " SPACE | |||
| lv_iv_spe | TYPE FLG_SEL, " SPACE | |||
| lv_iv_stat_tab | TYPE JEST-STAT, " 'I0045' | |||
| lv_iv_stat_abg | TYPE JEST-STAT, " 'I0046' | |||
| lv_iv_stat_loe | TYPE JEST-STAT, " 'I0013' | |||
| lv_iv_stat_lvm | TYPE JEST-STAT. " 'I0076' |
|   CALL FUNCTION 'CNIF_CONSTRUCT_STATUS_STRING' "NOTRANSL: String der aktiven 4-stelligen Status erzeugen |
| EXPORTING | ||
| IV_TAB | = lv_iv_tab | |
| IV_STAT_SPE | = lv_iv_stat_spe | |
| IV_ABG | = lv_iv_abg | |
| IV_LOE | = lv_iv_loe | |
| IV_LVM | = lv_iv_lvm | |
| IV_SPE | = lv_iv_spe | |
| IV_STAT_TAB | = lv_iv_stat_tab | |
| IV_STAT_ABG | = lv_iv_stat_abg | |
| IV_STAT_LOE | = lv_iv_stat_loe | |
| IV_STAT_LVM | = lv_iv_stat_lvm | |
| IMPORTING | ||
| EV_STATUS_STRING | = lv_ev_status_string | |
| . " CNIF_CONSTRUCT_STATUS_STRING | ||
ABAP code using 7.40 inline data declarations to call FM CNIF_CONSTRUCT_STATUS_STRING
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.| DATA(ld_iv_tab) | = ' '. | |||
| "SELECT single STAT FROM JEST INTO @DATA(ld_iv_stat_spe). | ||||
| DATA(ld_iv_stat_spe) | = 'I0043'. | |||
| DATA(ld_iv_abg) | = ' '. | |||
| DATA(ld_iv_loe) | = ' '. | |||
| DATA(ld_iv_lvm) | = ' '. | |||
| DATA(ld_iv_spe) | = ' '. | |||
| "SELECT single STAT FROM JEST INTO @DATA(ld_iv_stat_tab). | ||||
| DATA(ld_iv_stat_tab) | = 'I0045'. | |||
| "SELECT single STAT FROM JEST INTO @DATA(ld_iv_stat_abg). | ||||
| DATA(ld_iv_stat_abg) | = 'I0046'. | |||
| "SELECT single STAT FROM JEST INTO @DATA(ld_iv_stat_loe). | ||||
| DATA(ld_iv_stat_loe) | = 'I0013'. | |||
| "SELECT single STAT FROM JEST INTO @DATA(ld_iv_stat_lvm). | ||||
| DATA(ld_iv_stat_lvm) | = 'I0076'. | |||
Search for further information about these or an SAP related objects