SAP SPOOL_ES_WRITE_BAPI_IMPORTS Function Module for spools the creation of a service entry sheet









SPOOL_ES_WRITE_BAPI_IMPORTS is a standard spool es write bapi imports SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for spools the creation of a service entry sheet 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 spool es write bapi imports FM, simply by entering the name SPOOL_ES_WRITE_BAPI_IMPORTS into the relevant SAP transaction such as SE37 or SE38.

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



Function SPOOL_ES_WRITE_BAPI_IMPORTS 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 'SPOOL_ES_WRITE_BAPI_IMPORTS'"spools the creation of a service entry sheet
EXPORTING
I_GUID = "
COMM_NO = "Technisches Referenzfeld der externen Erfassungsblattnummer
ENTRYSHEET = "Erfassungsblattnummer

TABLES
* ENTRYSHEETACCOUNTASSIGNMENT = "Kommunikation Anlegen Kontierung Erfassungsblatt (BBP-BAPI)
* ENTRYSHEETSERVICES = "Kommunikationsstruktur Anlegen Leistungszeile
* ENTRYSHEETSRVACCASSVALUES = "Komm.struktur Anlege Kontierungsverteilung Leistungszeile
RETURN = "
* CONTROL_RECORD = "

EXCEPTIONS
INTERNAL_ERROR = 1
.



IMPORTING Parameters details for SPOOL_ES_WRITE_BAPI_IMPORTS

I_GUID -

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

COMM_NO - Technisches Referenzfeld der externen Erfassungsblattnummer

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

ENTRYSHEET - Erfassungsblattnummer

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

TABLES Parameters details for SPOOL_ES_WRITE_BAPI_IMPORTS

ENTRYSHEETACCOUNTASSIGNMENT - Kommunikation Anlegen Kontierung Erfassungsblatt (BBP-BAPI)

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

ENTRYSHEETSERVICES - Kommunikationsstruktur Anlegen Leistungszeile

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

ENTRYSHEETSRVACCASSVALUES - Komm.struktur Anlege Kontierungsverteilung Leistungszeile

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

RETURN -

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

CONTROL_RECORD -

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

EXCEPTIONS details

INTERNAL_ERROR -

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

Copy and paste ABAP code example for SPOOL_ES_WRITE_BAPI_IMPORTS 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_guid  TYPE CRMD_ORDERADM_H-GUID, "   
lv_internal_error  TYPE CRMD_ORDERADM_H, "   
lt_entrysheetaccountassignment  TYPE STANDARD TABLE OF BBP_BAPIESKNC, "   
lv_comm_no  TYPE BBPS_BAPIESSR-COMM_NO, "   
lt_entrysheetservices  TYPE STANDARD TABLE OF BAPIESLLC_ECI, "   
lv_entrysheet  TYPE BBPS_BAPIESSR-SHEET_NO, "   
lt_entrysheetsrvaccassvalues  TYPE STANDARD TABLE OF BBPS_BAPIESKLC, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_control_record  TYPE STANDARD TABLE OF BBP_CONTROL_RECORD. "   

  CALL FUNCTION 'SPOOL_ES_WRITE_BAPI_IMPORTS'  "spools the creation of a service entry sheet
    EXPORTING
         I_GUID = lv_i_guid
         COMM_NO = lv_comm_no
         ENTRYSHEET = lv_entrysheet
    TABLES
         ENTRYSHEETACCOUNTASSIGNMENT = lt_entrysheetaccountassignment
         ENTRYSHEETSERVICES = lt_entrysheetservices
         ENTRYSHEETSRVACCASSVALUES = lt_entrysheetsrvaccassvalues
         RETURN = lt_return
         CONTROL_RECORD = lt_control_record
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " SPOOL_ES_WRITE_BAPI_IMPORTS




ABAP code using 7.40 inline data declarations to call FM SPOOL_ES_WRITE_BAPI_IMPORTS

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 GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_i_guid).
 
 
 
"SELECT single COMM_NO FROM BBPS_BAPIESSR INTO @DATA(ld_comm_no).
 
 
"SELECT single SHEET_NO FROM BBPS_BAPIESSR INTO @DATA(ld_entrysheet).
 
 
 
 


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!