SAP OCS_DISPLAY_INVALID_KEEPS Function Module for
OCS_DISPLAY_INVALID_KEEPS is a standard ocs display invalid keeps SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ocs display invalid keeps FM, simply by entering the name OCS_DISPLAY_INVALID_KEEPS into the relevant SAP transaction such as SE37 or SE38.
Function Group: OCS_UI
Program Name: SAPLOCS_UI
Main Program: SAPLOCS_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OCS_DISPLAY_INVALID_KEEPS 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 'OCS_DISPLAY_INVALID_KEEPS'".
EXPORTING
POPUP_TITLE = "
* START_COLUMN = 5 "
* START_ROW = 5 "
* DOCU_CLASS = 'DT' "
* TEXT_OBJECT = ' ' "
IMPORTING
ANSWER = "
TABLES
* PARAMETER = "
IT_INVALID_KEEPS = "
* IT_QCALC_TRC = "
EXCEPTIONS
ERROR_IN_TEXT = 1 TEXT_NOT_FOUND = 2
IMPORTING Parameters details for OCS_DISPLAY_INVALID_KEEPS
POPUP_TITLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
START_COLUMN -
Data type: SY-CUCOLDefault: 5
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_ROW -
Data type: SY-CUROWDefault: 5
Optional: Yes
Call by Reference: No ( called with pass by value option)
DOCU_CLASS -
Data type: DOKIL-IDDefault: 'DT'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TEXT_OBJECT -
Data type: DOKHL-OBJECTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OCS_DISPLAY_INVALID_KEEPS
ANSWER -
Data type: RSNEWLENG-FCODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OCS_DISPLAY_INVALID_KEEPS
PARAMETER -
Data type: SPAROptional: Yes
Call by Reference: Yes
IT_INVALID_KEEPS -
Data type: SPAM_CVERSOptional: No
Call by Reference: Yes
IT_QCALC_TRC -
Data type: PAT_Q_TRCOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_IN_TEXT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TEXT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OCS_DISPLAY_INVALID_KEEPS 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_answer | TYPE RSNEWLENG-FCODE, " | |||
| lt_parameter | TYPE STANDARD TABLE OF SPAR, " | |||
| lv_popup_title | TYPE SPAR, " | |||
| lv_error_in_text | TYPE SPAR, " | |||
| lv_start_column | TYPE SY-CUCOL, " 5 | |||
| lv_text_not_found | TYPE SY, " | |||
| lt_it_invalid_keeps | TYPE STANDARD TABLE OF SPAM_CVERS, " | |||
| lv_start_row | TYPE SY-CUROW, " 5 | |||
| lt_it_qcalc_trc | TYPE STANDARD TABLE OF PAT_Q_TRC, " | |||
| lv_docu_class | TYPE DOKIL-ID, " 'DT' | |||
| lv_text_object | TYPE DOKHL-OBJECT. " SPACE |
|   CALL FUNCTION 'OCS_DISPLAY_INVALID_KEEPS' " |
| EXPORTING | ||
| POPUP_TITLE | = lv_popup_title | |
| START_COLUMN | = lv_start_column | |
| START_ROW | = lv_start_row | |
| DOCU_CLASS | = lv_docu_class | |
| TEXT_OBJECT | = lv_text_object | |
| IMPORTING | ||
| ANSWER | = lv_answer | |
| TABLES | ||
| PARAMETER | = lt_parameter | |
| IT_INVALID_KEEPS | = lt_it_invalid_keeps | |
| IT_QCALC_TRC | = lt_it_qcalc_trc | |
| EXCEPTIONS | ||
| ERROR_IN_TEXT = 1 | ||
| TEXT_NOT_FOUND = 2 | ||
| . " OCS_DISPLAY_INVALID_KEEPS | ||
ABAP code using 7.40 inline data declarations to call FM OCS_DISPLAY_INVALID_KEEPS
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 FCODE FROM RSNEWLENG INTO @DATA(ld_answer). | ||||
| "SELECT single CUCOL FROM SY INTO @DATA(ld_start_column). | ||||
| DATA(ld_start_column) | = 5. | |||
| "SELECT single CUROW FROM SY INTO @DATA(ld_start_row). | ||||
| DATA(ld_start_row) | = 5. | |||
| "SELECT single ID FROM DOKIL INTO @DATA(ld_docu_class). | ||||
| DATA(ld_docu_class) | = 'DT'. | |||
| "SELECT single OBJECT FROM DOKHL INTO @DATA(ld_text_object). | ||||
| DATA(ld_text_object) | = ' '. | |||
Search for further information about these or an SAP related objects