SAP CBIH_PT13_ENTRY Function Module for
CBIH_PT13_ENTRY is a standard cbih pt13 entry 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 cbih pt13 entry FM, simply by entering the name CBIH_PT13_ENTRY into the relevant SAP transaction such as SE37 or SE38.
Function Group: CBIH_PT13
Program Name: SAPLCBIH_PT13
Main Program: SAPLCBIH_PT13
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CBIH_PT13_ENTRY 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 'CBIH_PT13_ENTRY'".
EXPORTING
I_ACTYPE = "Current Activity Type
I_TRTYPE = "Current Transaction Type
I_ADDINF = "Additional info
I_KEYPATH = "
IMPORTING
E_FLG_CHANGED = "
E_FLG_NO_AUTHORITY = "
E_OKCODE = "
EXCEPTIONS
NO_AUTHORITY = 1
IMPORTING Parameters details for CBIH_PT13_ENTRY
I_ACTYPE - Current Activity Type
Data type: RCGDIALCTR-ACTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_TRTYPE - Current Transaction Type
Data type: RCGDIALCTR-TRTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_ADDINF - Additional info
Data type: RCGADDINFOptional: No
Call by Reference: No ( called with pass by value option)
I_KEYPATH -
Data type: CCIHS_WAKPATHOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CBIH_PT13_ENTRY
E_FLG_CHANGED -
Data type: ESP1_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
E_FLG_NO_AUTHORITY -
Data type: ESP1_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
E_OKCODE -
Data type: ESP1_OKCODE_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CBIH_PT13_ENTRY 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_actype | TYPE RCGDIALCTR-ACTYPE, " | |||
| lv_no_authority | TYPE RCGDIALCTR, " | |||
| lv_e_flg_changed | TYPE ESP1_BOOLEAN, " | |||
| lv_i_trtype | TYPE RCGDIALCTR-TRTYPE, " | |||
| lv_e_flg_no_authority | TYPE ESP1_BOOLEAN, " | |||
| lv_e_okcode | TYPE ESP1_OKCODE_TYPE, " | |||
| lv_i_addinf | TYPE RCGADDINF, " | |||
| lv_i_keypath | TYPE CCIHS_WAKPATH. " |
|   CALL FUNCTION 'CBIH_PT13_ENTRY' " |
| EXPORTING | ||
| I_ACTYPE | = lv_i_actype | |
| I_TRTYPE | = lv_i_trtype | |
| I_ADDINF | = lv_i_addinf | |
| I_KEYPATH | = lv_i_keypath | |
| IMPORTING | ||
| E_FLG_CHANGED | = lv_e_flg_changed | |
| E_FLG_NO_AUTHORITY | = lv_e_flg_no_authority | |
| E_OKCODE | = lv_e_okcode | |
| EXCEPTIONS | ||
| NO_AUTHORITY = 1 | ||
| . " CBIH_PT13_ENTRY | ||
ABAP code using 7.40 inline data declarations to call FM CBIH_PT13_ENTRY
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 ACTYPE FROM RCGDIALCTR INTO @DATA(ld_i_actype). | ||||
| "SELECT single TRTYPE FROM RCGDIALCTR INTO @DATA(ld_i_trtype). | ||||
Search for further information about these or an SAP related objects