SAP RS_NAVIGATION_PUSH___OB Function Module for Stack entry for object types in the Business Object Repository
RS_NAVIGATION_PUSH___OB is a standard rs navigation push ob SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Stack entry for object types in the Business Object Repository 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 rs navigation push ob FM, simply by entering the name RS_NAVIGATION_PUSH___OB into the relevant SAP transaction such as SE37 or SE38.
Function Group: NAVI
Program Name: SAPLNAVI
Main Program: SAPLNAVI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RS_NAVIGATION_PUSH___OB 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 'RS_NAVIGATION_PUSH___OB'"Stack entry for object types in the Business Object Repository.
EXPORTING
* OBJTYPE = "Object type
* COLUMN = "
* INCLNAME = "
* MODE = "
* KEYWORD = "Short text
FCODE = "Function to be carried out
* DISPLAY = 'X' "Flag for display mode
* ELEMENT = "Sub-object
* VERBTYPE = "Sub-object type
* USE_OBJECTNAMES = "
* TOPLINE = "
* LINE = "
IMPORTING Parameters details for RS_NAVIGATION_PUSH___OB
OBJTYPE - Object type
Data type: SWOTBASDAT-OBJTYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
COLUMN -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
INCLNAME -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
MODE -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
KEYWORD - Short text
Data type: SWOTBASDAT-KEYWORDOptional: Yes
Call by Reference: No ( called with pass by value option)
FCODE - Function to be carried out
Data type: SWOTEDITOR-FUNCEXITOptional: No
Call by Reference: No ( called with pass by value option)
DISPLAY - Flag for display mode
Data type: SWOTEDITOR-DISPLAYDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ELEMENT - Sub-object
Data type: SWCONTEDIT-ELEMENTOptional: Yes
Call by Reference: No ( called with pass by value option)
VERBTYPE - Sub-object type
Data type: SWCONTEDIT-VERBTYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
USE_OBJECTNAMES -
Data type: SWOTEDITOR-USEOBJNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
TOPLINE -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
LINE -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RS_NAVIGATION_PUSH___OB 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_objtype | TYPE SWOTBASDAT-OBJTYPE, " | |||
| lv_column | TYPE SWOTBASDAT, " | |||
| lv_inclname | TYPE C, " | |||
| lv_mode | TYPE C, " | |||
| lv_keyword | TYPE SWOTBASDAT-KEYWORD, " | |||
| lv_fcode | TYPE SWOTEDITOR-FUNCEXIT, " | |||
| lv_display | TYPE SWOTEDITOR-DISPLAY, " 'X' | |||
| lv_element | TYPE SWCONTEDIT-ELEMENT, " | |||
| lv_verbtype | TYPE SWCONTEDIT-VERBTYPE, " | |||
| lv_use_objectnames | TYPE SWOTEDITOR-USEOBJNAME, " | |||
| lv_topline | TYPE SWOTEDITOR, " | |||
| lv_line | TYPE SWOTEDITOR. " |
|   CALL FUNCTION 'RS_NAVIGATION_PUSH___OB' "Stack entry for object types in the Business Object Repository |
| EXPORTING | ||
| OBJTYPE | = lv_objtype | |
| COLUMN | = lv_column | |
| INCLNAME | = lv_inclname | |
| MODE | = lv_mode | |
| KEYWORD | = lv_keyword | |
| FCODE | = lv_fcode | |
| DISPLAY | = lv_display | |
| ELEMENT | = lv_element | |
| VERBTYPE | = lv_verbtype | |
| USE_OBJECTNAMES | = lv_use_objectnames | |
| TOPLINE | = lv_topline | |
| LINE | = lv_line | |
| . " RS_NAVIGATION_PUSH___OB | ||
ABAP code using 7.40 inline data declarations to call FM RS_NAVIGATION_PUSH___OB
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 OBJTYPE FROM SWOTBASDAT INTO @DATA(ld_objtype). | ||||
| "SELECT single KEYWORD FROM SWOTBASDAT INTO @DATA(ld_keyword). | ||||
| "SELECT single FUNCEXIT FROM SWOTEDITOR INTO @DATA(ld_fcode). | ||||
| "SELECT single DISPLAY FROM SWOTEDITOR INTO @DATA(ld_display). | ||||
| DATA(ld_display) | = 'X'. | |||
| "SELECT single ELEMENT FROM SWCONTEDIT INTO @DATA(ld_element). | ||||
| "SELECT single VERBTYPE FROM SWCONTEDIT INTO @DATA(ld_verbtype). | ||||
| "SELECT single USEOBJNAME FROM SWOTEDITOR INTO @DATA(ld_use_objectnames). | ||||
Search for further information about these or an SAP related objects