SAP BUS_OP_ENTRY Function Module for Entry Screen for all Business Transactions

Search SAP Function Modules

BUS_OP_ENTRY is a standard bus op entry SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Entry Screen for all Business Transactions 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 bus op entry FM, simply by entering the name BUS_OP_ENTRY into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVN_BUS_OPERATION
Program Name: SAPLFVN_BUS_OPERATION
Main Program: SAPLFVN_BUS_OPERATION
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUS_OP_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 'BUS_OP_ENTRY'"Entry Screen for all Business Transactions
  EXPORTING
   I_TCODE =  "Transaction Code

 IMPORTING
   E_VDARL =  "
   E_DATE_RANGE =  "
   E_ACTIVITY =  "
   E_FLG_ACT_ALLOWED =  "

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLFVN_BUS_OPERATION_001 Customer Functions for SAPLFvn_bus_operation
EXIT_SAPLFVN_BUS_OPERATION_101 Additional Data for FN8D
EXIT_SAPLFVN_BUS_OPERATION_102 User Exit for ZUONR and RSOLL
EXIT_SAPLFVN_BUS_OPERATION_500 Customer Function for Determining Country

IMPORTING Parameters details for BUS_OP_ENTRY

I_TCODE - Transaction Code

Data type: SY-TCODE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for BUS_OP_ENTRY

E_VDARL -

Data type: VDARL
Optional: No
Call by Reference: Yes

E_DATE_RANGE -

Data type: VDDATE_RANGE
Optional: No
Call by Reference: Yes

E_ACTIVITY -

Data type:
Optional: No
Call by Reference: Yes

E_FLG_ACT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BUS_OP_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.

ABAP code using 7.40 inline data declarations to call FM BUS_OP_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.

Search for further information about these or an SAP related objects