SAP ALE_SETTRQSLIST_CREATE Function Module for BAPI -> IDoc: ALE_SETTRQSLIST_CREATE









ALE_SETTRQSLIST_CREATE is a standard ale settrqslist create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_SETTRQSLIST_CREATE 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 ale settrqslist create FM, simply by entering the name ALE_SETTRQSLIST_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_SETTRQSLIST_CREATE 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 'ALE_SETTRQSLIST_CREATE'"BAPI -> IDoc: ALE_SETTRQSLIST_CREATE
  EXPORTING
   LISTHEADDATA =  "Settlement Request List Header Data (Input)
*  OBJ_TYPE = 'BUS2100001' "
*  SERIAL_ID = '0' "

TABLES
   HEADDATA =  "Document Header Data (input)
*  ITEMTEXTOUT =  "Item Texts (Output)
*  VENDORCONDIN =  "Vendor Conditions
*  CUSTOMERCONDIN =  "Customer Conditions
*  PARTNERADDRESSES =  "BAPI Reference Structure for Addresses (Org./Company)
   RECEIVERS =  "
*  COMMUNICATION_DOCUMENTS =  "
*  APPLICATION_OBJECTS =  "
   ITEMDATA =  "Document Item Data (Input)
*  HEADDATAOUT =  "Document Header Data (Output)
*  ITEMDATAOUT =  "Document Item Data (Output)
*  LISTITEMDATAOUT =  "Settlement Request List Item Data (Output)
*  EXTENSIONIN =  "Enhancements (Input)
*  HEADTEXTIN =  "Header Texts (Input)
*  ITEMTEXTIN =  "Item Texts (Input)
*  HEADTEXTOUT =  "Header Texts (Output)

EXCEPTIONS
   ERROR_CREATING_IDOCS = 1
.



IMPORTING Parameters details for ALE_SETTRQSLIST_CREATE

LISTHEADDATA - Settlement Request List Header Data (Input)

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

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUS2100001'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_SETTRQSLIST_CREATE

HEADDATA - Document Header Data (input)

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

ITEMTEXTOUT - Item Texts (Output)

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

VENDORCONDIN - Vendor Conditions

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

CUSTOMERCONDIN - Customer Conditions

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

PARTNERADDRESSES - BAPI Reference Structure for Addresses (Org./Company)

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

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

APPLICATION_OBJECTS -

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

ITEMDATA - Document Item Data (Input)

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

HEADDATAOUT - Document Header Data (Output)

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

ITEMDATAOUT - Document Item Data (Output)

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

LISTITEMDATAOUT - Settlement Request List Item Data (Output)

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

EXTENSIONIN - Enhancements (Input)

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

HEADTEXTIN - Header Texts (Input)

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

ITEMTEXTIN - Item Texts (Input)

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

HEADTEXTOUT - Header Texts (Output)

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

EXCEPTIONS details

ERROR_CREATING_IDOCS -

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

Copy and paste ABAP code example for ALE_SETTRQSLIST_CREATE 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_headdata  TYPE STANDARD TABLE OF BAPIACHEAD, "   
lv_listheaddata  TYPE BAPISLHEAD, "   
lv_error_creating_idocs  TYPE BAPISLHEAD, "   
lt_itemtextout  TYPE STANDARD TABLE OF BAPIABITEMCTEXT, "   
lt_vendorcondin  TYPE STANDARD TABLE OF BAPILFCOND, "   
lt_customercondin  TYPE STANDARD TABLE OF BAPILFCONDU, "   
lt_partneraddresses  TYPE STANDARD TABLE OF BAPIADDR1, "   
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID, "   
lt_itemdata  TYPE STANDARD TABLE OF BAPIACITEM, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'BUS2100001'
lv_serial_id  TYPE SERIAL-CHNUM, "   '0'
lt_headdataout  TYPE STANDARD TABLE OF BAPIACHEADO, "   
lt_itemdataout  TYPE STANDARD TABLE OF BAPIACITEMO, "   
lt_listitemdataout  TYPE STANDARD TABLE OF BAPIILITEMO, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_headtextin  TYPE STANDARD TABLE OF BAPIABHEADTEXT, "   
lt_itemtextin  TYPE STANDARD TABLE OF BAPIABITEMTEXT, "   
lt_headtextout  TYPE STANDARD TABLE OF BAPIABHEADCTEXT. "   

  CALL FUNCTION 'ALE_SETTRQSLIST_CREATE'  "BAPI -> IDoc: ALE_SETTRQSLIST_CREATE
    EXPORTING
         LISTHEADDATA = lv_listheaddata
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
    TABLES
         HEADDATA = lt_headdata
         ITEMTEXTOUT = lt_itemtextout
         VENDORCONDIN = lt_vendorcondin
         CUSTOMERCONDIN = lt_customercondin
         PARTNERADDRESSES = lt_partneraddresses
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
         ITEMDATA = lt_itemdata
         HEADDATAOUT = lt_headdataout
         ITEMDATAOUT = lt_itemdataout
         LISTITEMDATAOUT = lt_listitemdataout
         EXTENSIONIN = lt_extensionin
         HEADTEXTIN = lt_headtextin
         ITEMTEXTIN = lt_itemtextin
         HEADTEXTOUT = lt_headtextout
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_SETTRQSLIST_CREATE




ABAP code using 7.40 inline data declarations to call FM ALE_SETTRQSLIST_CREATE

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 OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'BUS2100001'.
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 
 
 
 
 
 
 
 


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!