SAP BUSENTITY_SELOPTASSIGN Function Module for









BUSENTITY_SELOPTASSIGN is a standard busentity seloptassign 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 busentity seloptassign FM, simply by entering the name BUSENTITY_SELOPTASSIGN into the relevant SAP transaction such as SE37 or SE38.

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



Function BUSENTITY_SELOPTASSIGN 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 'BUSENTITY_SELOPTASSIGN'"
EXPORTING
* PID_DATEFROM1 = "
* PID_DATEFROM2 = "
* PID_DATETO1 = "
* PID_DATETO2 = "
* PID_DATECUTOFF1 = "
* PID_DATECUTOFF2 = "

TABLES
* PIT_SO_BUKRV = "
* PIT_SO_SMENR = "
* PIT_SO_SNUNR = "
* PIT_SO_SMIVE = "
* PIT_SO_ESMIV = "
* PIT_SO_ROLT1 = "
* PIT_SO_ROLT2 = "
* PIT_SO_PART1 = "
* PIT_SO_PART2 = "
* PIT_SO_RECNN = "
* PIT_SO_RECNT = "
* PIT_SO_RECNC = "
* PIT_SO_BUKRS = "
* PIT_SO_GSBER = "
* PIT_SO_SWENR = "
* PIT_SO_SGRNR = "
* PIT_SO_SGENR = "
.



IMPORTING Parameters details for BUSENTITY_SELOPTASSIGN

PID_DATEFROM1 -

Data type: DVONDAT
Optional: Yes
Call by Reference: Yes

PID_DATEFROM2 -

Data type: DVONDAT
Optional: Yes
Call by Reference: Yes

PID_DATETO1 -

Data type: DBISDAT
Optional: Yes
Call by Reference: Yes

PID_DATETO2 -

Data type: DBISDAT
Optional: Yes
Call by Reference: Yes

PID_DATECUTOFF1 -

Data type: DBISDAT
Optional: Yes
Call by Reference: Yes

PID_DATECUTOFF2 -

Data type: VVDSTCHTAG
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for BUSENTITY_SELOPTASSIGN

PIT_SO_BUKRV -

Data type:
Optional: Yes
Call by Reference: Yes

PIT_SO_SMENR -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

PIT_SO_SNUNR -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

PIT_SO_SMIVE -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

PIT_SO_ESMIV -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

PIT_SO_ROLT1 -

Data type:
Optional: Yes
Call by Reference: Yes

PIT_SO_ROLT2 -

Data type:
Optional: Yes
Call by Reference: Yes

PIT_SO_PART1 -

Data type:
Optional: Yes
Call by Reference: Yes

PIT_SO_PART2 -

Data type:
Optional: Yes
Call by Reference: Yes

PIT_SO_RECNN -

Data type:
Optional: Yes
Call by Reference: Yes

PIT_SO_RECNT -

Data type:
Optional: Yes
Call by Reference: Yes

PIT_SO_RECNC -

Data type:
Optional: Yes
Call by Reference: Yes

PIT_SO_BUKRS -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

PIT_SO_GSBER -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

PIT_SO_SWENR -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

PIT_SO_SGRNR -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

PIT_SO_SGENR -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BUSENTITY_SELOPTASSIGN 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:
lt_pit_so_bukrv  TYPE STANDARD TABLE OF STRING, "   
lv_pid_datefrom1  TYPE DVONDAT, "   
lt_pit_so_smenr  TYPE STANDARD TABLE OF DVONDAT, "   
lt_pit_so_snunr  TYPE STANDARD TABLE OF DVONDAT, "   
lt_pit_so_smive  TYPE STANDARD TABLE OF DVONDAT, "   
lt_pit_so_esmiv  TYPE STANDARD TABLE OF DVONDAT, "   
lt_pit_so_rolt1  TYPE STANDARD TABLE OF DVONDAT, "   
lt_pit_so_rolt2  TYPE STANDARD TABLE OF DVONDAT, "   
lt_pit_so_part1  TYPE STANDARD TABLE OF DVONDAT, "   
lt_pit_so_part2  TYPE STANDARD TABLE OF DVONDAT, "   
lt_pit_so_recnn  TYPE STANDARD TABLE OF DVONDAT, "   
lv_pid_datefrom2  TYPE DVONDAT, "   
lv_pid_dateto1  TYPE DBISDAT, "   
lt_pit_so_recnt  TYPE STANDARD TABLE OF DBISDAT, "   
lv_pid_dateto2  TYPE DBISDAT, "   
lt_pit_so_recnc  TYPE STANDARD TABLE OF DBISDAT, "   
lt_pit_so_bukrs  TYPE STANDARD TABLE OF DBISDAT, "   
lv_pid_datecutoff1  TYPE DBISDAT, "   
lt_pit_so_gsber  TYPE STANDARD TABLE OF DBISDAT, "   
lv_pid_datecutoff2  TYPE VVDSTCHTAG, "   
lt_pit_so_swenr  TYPE STANDARD TABLE OF VVDSTCHTAG, "   
lt_pit_so_sgrnr  TYPE STANDARD TABLE OF VVDSTCHTAG, "   
lt_pit_so_sgenr  TYPE STANDARD TABLE OF VVDSTCHTAG. "   

  CALL FUNCTION 'BUSENTITY_SELOPTASSIGN'  "
    EXPORTING
         PID_DATEFROM1 = lv_pid_datefrom1
         PID_DATEFROM2 = lv_pid_datefrom2
         PID_DATETO1 = lv_pid_dateto1
         PID_DATETO2 = lv_pid_dateto2
         PID_DATECUTOFF1 = lv_pid_datecutoff1
         PID_DATECUTOFF2 = lv_pid_datecutoff2
    TABLES
         PIT_SO_BUKRV = lt_pit_so_bukrv
         PIT_SO_SMENR = lt_pit_so_smenr
         PIT_SO_SNUNR = lt_pit_so_snunr
         PIT_SO_SMIVE = lt_pit_so_smive
         PIT_SO_ESMIV = lt_pit_so_esmiv
         PIT_SO_ROLT1 = lt_pit_so_rolt1
         PIT_SO_ROLT2 = lt_pit_so_rolt2
         PIT_SO_PART1 = lt_pit_so_part1
         PIT_SO_PART2 = lt_pit_so_part2
         PIT_SO_RECNN = lt_pit_so_recnn
         PIT_SO_RECNT = lt_pit_so_recnt
         PIT_SO_RECNC = lt_pit_so_recnc
         PIT_SO_BUKRS = lt_pit_so_bukrs
         PIT_SO_GSBER = lt_pit_so_gsber
         PIT_SO_SWENR = lt_pit_so_swenr
         PIT_SO_SGRNR = lt_pit_so_sgrnr
         PIT_SO_SGENR = lt_pit_so_sgenr
. " BUSENTITY_SELOPTASSIGN




ABAP code using 7.40 inline data declarations to call FM BUSENTITY_SELOPTASSIGN

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!