SAP Function Modules

comments icon Comments

BUS_OP_ENTRY SAP Function module - Entry Screen for all Business Transactions







BUS_OP_ENTRY is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BUS_OP_ENTRY into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FVN_BUS_OPERATION
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM BUS_OP_ENTRY - BUS OP ENTRY 





CALL FUNCTION 'BUS_OP_ENTRY' "Entry Screen for all Business Transactions
  EXPORTING
    i_tcode =                   " sy-tcode      Transaction Code
  IMPORTING
    e_vdarl =                   " vdarl
    e_date_range =              " vddate_range
    e_activity =                "
    e_flg_act_allowed =         "
    .  "  BUS_OP_ENTRY

ABAP code example for Function Module BUS_OP_ENTRY





The ABAP code below is a full code listing to execute function module BUS_OP_ENTRY including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_vdarl    TYPE VDARL
,
ld_e_date_range    TYPE VDDATE_RANGE
,
ld_e_activity    TYPE STRING
,
ld_e_flg_act_allowed    TYPE STRING
.




DATA(ld_i_tcode) = 'some text here'.
.

CALL FUNCTION 'BUS_OP_ENTRY'
  EXPORTING
    i_tcode =                    ld_i_tcode
  IMPORTING
    e_vdarl =                    ld_e_vdarl
    e_date_range =               ld_e_date_range
    e_activity =                 ld_e_activity
    e_flg_act_allowed =          ld_e_flg_act_allowed
    .  "  BUS_OP_ENTRY

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_e_vdarl  TYPE VDARL ,
ld_i_tcode  TYPE SY-TCODE ,
ld_e_date_range  TYPE VDDATE_RANGE ,
ld_e_activity  TYPE STRING ,
ld_e_flg_act_allowed  TYPE STRING .




ld_i_tcode = 'some text here'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BUS_OP_ENTRY or its description.


   
 

BUS_OP_ENTRY - Entry Screen for all Business Transactions
BUS_OP_EARLY_REPAYMENT - Curtailment
BUS_OP_CHARGES - Enter Charges Individually
BUS_OP_BEPP_READ - Read BEPP Entries for a Business Transaction
BUS_OPERATION_UPDATE - Save, Activate, and Post Business Transactions
BUS_OPERATION_TO_POST - Business Transaction for Item (For Example, Called From Due Date List)