SAP ALE_REQUISITION_CREATE Function Module for NOTRANSL: BAPI -> IDoc: ALE_REQUISITION_CREATE









ALE_REQUISITION_CREATE is a standard ale requisition 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 NOTRANSL: BAPI -> IDoc: ALE_REQUISITION_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 requisition create FM, simply by entering the name ALE_REQUISITION_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_REQUISITION_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_REQUISITION_CREATE'"NOTRANSL: BAPI -> IDoc: ALE_REQUISITION_CREATE
  EXPORTING
*  SKIPITEMSWITHERROR =  "Selection flag
*  AUTOMATICSOURCE = 'X' "Selection flag
*  OBJ_TYPE = 'BUS2105' "Object Type
*  SERIAL_ID = '0' "ALE channel number

TABLES
   REQUISITIONITEMS =  "Transfer Structure: Create Requisition Item
*  EXTENSIONIN =  "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
   RECEIVERS =  "Transfer structure for logical systems
*  COMMUNICATION_DOCUMENTS =  "Structure for Object ID
*  APPLICATION_OBJECTS =  "Structure for Object ID
*  REQUISITIONACCOUNTAS =  "Transfer Structure: Create/Display Requisition Acct Assgt
*  REQUISITIONITEMTEXT =  "BAPI Purchase Requisition: Item Text
*  REQUISITIONLIMITS =  "Communication Structure: Limits
*  REQUISITIONCONTRACTL =  "Communication Structure: Contract Limits
*  REQUISITIONSERVICES =  "Communication Structure: Create Service Line
*  REQUISITIONSRVACCASS =  "Create Comm. Structure: Acct Assgt Distr. for Service Line
*  REQUISITIONSRVTEXT =  "BAPI Services Long Text
*  REQUISITIONADDRDELIVERY =  "PO Item: Address Structure BAPIADDR1 for Inbound Delivery

EXCEPTIONS
   ERROR_CREATING_IDOCS = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLMEWQ_001 Customer Exit: Creation of Purch. Requisition via BAPI_REQUISITION_CREATE

IMPORTING Parameters details for ALE_REQUISITION_CREATE

SKIPITEMSWITHERROR - Selection flag

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

AUTOMATICSOURCE - Selection flag

Data type: BAPIMMPARA-SELECTION
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJ_TYPE - Object Type

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

SERIAL_ID - ALE channel number

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

TABLES Parameters details for ALE_REQUISITION_CREATE

REQUISITIONITEMS - Transfer Structure: Create Requisition Item

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

EXTENSIONIN - Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut

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

RECEIVERS - Transfer structure for logical systems

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

COMMUNICATION_DOCUMENTS - Structure for Object ID

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

APPLICATION_OBJECTS - Structure for Object ID

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

REQUISITIONACCOUNTAS - Transfer Structure: Create/Display Requisition Acct Assgt

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

REQUISITIONITEMTEXT - BAPI Purchase Requisition: Item Text

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

REQUISITIONLIMITS - Communication Structure: Limits

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

REQUISITIONCONTRACTL - Communication Structure: Contract Limits

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

REQUISITIONSERVICES - Communication Structure: Create Service Line

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

REQUISITIONSRVACCASS - Create Comm. Structure: Acct Assgt Distr. for Service Line

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

REQUISITIONSRVTEXT - BAPI Services Long Text

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

REQUISITIONADDRDELIVERY - PO Item: Address Structure BAPIADDR1 for Inbound Delivery

Data type: BAPIMERQADDRDELIVERY
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_REQUISITION_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_requisitionitems  TYPE STANDARD TABLE OF BAPIEBANC, "   
lv_skipitemswitherror  TYPE BAPIMMPARA-SELECTION, "   
lv_error_creating_idocs  TYPE BAPIMMPARA, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_automaticsource  TYPE BAPIMMPARA-SELECTION, "   'X'
lt_requisitionaccountas  TYPE STANDARD TABLE OF BAPIEBKN, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'BUS2105'
lt_requisitionitemtext  TYPE STANDARD TABLE OF BAPIEBANTX, "   
lv_serial_id  TYPE SERIAL-CHNUM, "   '0'
lt_requisitionlimits  TYPE STANDARD TABLE OF BAPIESUHC, "   
lt_requisitioncontractl  TYPE STANDARD TABLE OF BAPIESUCC, "   
lt_requisitionservices  TYPE STANDARD TABLE OF BAPIESLLC, "   
lt_requisitionsrvaccass  TYPE STANDARD TABLE OF BAPIESKLC, "   
lt_requisitionsrvtext  TYPE STANDARD TABLE OF BAPIESLLTX, "   
lt_requisitionaddrdelivery  TYPE STANDARD TABLE OF BAPIMERQADDRDELIVERY. "   

  CALL FUNCTION 'ALE_REQUISITION_CREATE'  "NOTRANSL: BAPI -> IDoc: ALE_REQUISITION_CREATE
    EXPORTING
         SKIPITEMSWITHERROR = lv_skipitemswitherror
         AUTOMATICSOURCE = lv_automaticsource
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
    TABLES
         REQUISITIONITEMS = lt_requisitionitems
         EXTENSIONIN = lt_extensionin
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
         REQUISITIONACCOUNTAS = lt_requisitionaccountas
         REQUISITIONITEMTEXT = lt_requisitionitemtext
         REQUISITIONLIMITS = lt_requisitionlimits
         REQUISITIONCONTRACTL = lt_requisitioncontractl
         REQUISITIONSERVICES = lt_requisitionservices
         REQUISITIONSRVACCASS = lt_requisitionsrvaccass
         REQUISITIONSRVTEXT = lt_requisitionsrvtext
         REQUISITIONADDRDELIVERY = lt_requisitionaddrdelivery
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_REQUISITION_CREATE




ABAP code using 7.40 inline data declarations to call FM ALE_REQUISITION_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 SELECTION FROM BAPIMMPARA INTO @DATA(ld_skipitemswitherror).
 
 
 
 
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_automaticsource).
DATA(ld_automaticsource) = 'X'.
 
 
"SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'BUS2105'.
 
 
"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!