SAP BOS01_ENTRYSHEETTOBOS_CONVERT Function Module for Service entry sheet to BOS structure conversion









BOS01_ENTRYSHEETTOBOS_CONVERT is a standard bos01 entrysheettobos convert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Service entry sheet to BOS structure conversion 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 bos01 entrysheettobos convert FM, simply by entering the name BOS01_ENTRYSHEETTOBOS_CONVERT into the relevant SAP transaction such as SE37 or SE38.

Function Group: BOS01
Program Name: SAPLBOS01
Main Program: SAPLBOS01
Appliation area: S
Release date: 25-Jun-2001
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BOS01_ENTRYSHEETTOBOS_CONVERT 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 'BOS01_ENTRYSHEETTOBOS_CONVERT'"Service entry sheet to BOS structure conversion
EXPORTING
PACKNO = "

TABLES
SERVICES = "
BOS_OUTLINES = "
BOS_SERVICES = "
UNPLANNED_SERVICES = "Generated Table for View ML_ESLL
.



IMPORTING Parameters details for BOS01_ENTRYSHEETTOBOS_CONVERT

PACKNO -

Data type: ESLL-PACKNO
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BOS01_ENTRYSHEETTOBOS_CONVERT

SERVICES -

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

BOS_OUTLINES -

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

BOS_SERVICES -

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

UNPLANNED_SERVICES - Generated Table for View ML_ESLL

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

Copy and paste ABAP code example for BOS01_ENTRYSHEETTOBOS_CONVERT 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_packno  TYPE ESLL-PACKNO, "   
lt_services  TYPE STANDARD TABLE OF ML_ESLL, "   
lt_bos_outlines  TYPE STANDARD TABLE OF ML_ESLL, "   
lt_bos_services  TYPE STANDARD TABLE OF ML_ESLL, "   
lt_unplanned_services  TYPE STANDARD TABLE OF ML_ESLL. "   

  CALL FUNCTION 'BOS01_ENTRYSHEETTOBOS_CONVERT'  "Service entry sheet to BOS structure conversion
    EXPORTING
         PACKNO = lv_packno
    TABLES
         SERVICES = lt_services
         BOS_OUTLINES = lt_bos_outlines
         BOS_SERVICES = lt_bos_services
         UNPLANNED_SERVICES = lt_unplanned_services
. " BOS01_ENTRYSHEETTOBOS_CONVERT




ABAP code using 7.40 inline data declarations to call FM BOS01_ENTRYSHEETTOBOS_CONVERT

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 PACKNO FROM ESLL INTO @DATA(ld_packno).
 
 
 
 
 


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!