SAP ALE_PO_GETDETAIL Function Module for BAPI -> IDoc: ALE_PO_GETDETAIL









ALE_PO_GETDETAIL is a standard ale po getdetail 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_PO_GETDETAIL 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 po getdetail FM, simply by entering the name ALE_PO_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_PO_GETDETAIL 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_PO_GETDETAIL'"BAPI -> IDoc: ALE_PO_GETDETAIL
EXPORTING
PURCHASEORDER = "Purchase Order Number
* SERVICETEXTS = ' ' "
* OBJ_TYPE = 'BUS2012' "
* SERIAL_ID = '0' "
* ITEMS = 'X' "Also Provide Item Data
* ACCOUNTASSIGNMENT = ' ' "
* SCHEDULES = ' ' "Also Provide Schedule Lines
* HISTORY = ' ' "Also Provide PO History
* ITEMTEXTS = ' ' "
* HEADERTEXTS = ' ' "
* SERVICES = ' ' "Also Provide Services and Limits
* CONFIRMATIONS = ' ' "Also Provide Confirmations

TABLES
* POHEADERTEXTS = "
* POITEMCONTRACTLIMITS = "
* POITEMSERVICES = "
* POITEMSRVACCASSVALUES = "
* POSERVICESTEXTS = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
* POITEMS = "
* POITEMACCOUNTASSIGNM = "
* POITEMSCHEDULES = "
* POITEMCONFIRMATIONS = "
* POITEMTEXTS = "
* POITEMHISTORY = "
* POITEMHISTORYTOTALS = "
* POITEMLIMITS = "

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_SAPLMEWP_001 Customer Exit for Object Determination (Procurement via Catalogs)
EXIT_SAPLMEWP_002 Customer Exit: Creation of Purchase Order via BAPI_PO_CREATE
EXIT_SAPLMEWP_003 Customer Exit to Determine Allowed Catalogs

IMPORTING Parameters details for ALE_PO_GETDETAIL

PURCHASEORDER - Purchase Order Number

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

SERVICETEXTS -

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

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUS2012'
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)

ITEMS - Also Provide Item Data

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

ACCOUNTASSIGNMENT -

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

SCHEDULES - Also Provide Schedule Lines

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

HISTORY - Also Provide PO History

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

ITEMTEXTS -

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

HEADERTEXTS -

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

SERVICES - Also Provide Services and Limits

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

CONFIRMATIONS - Also Provide Confirmations

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

TABLES Parameters details for ALE_PO_GETDETAIL

POHEADERTEXTS -

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

POITEMCONTRACTLIMITS -

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

POITEMSERVICES -

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

POITEMSRVACCASSVALUES -

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

POSERVICESTEXTS -

Data type: BAPIESLLTX
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)

POITEMS -

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

POITEMACCOUNTASSIGNM -

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

POITEMSCHEDULES -

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

POITEMCONFIRMATIONS -

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

POITEMTEXTS -

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

POITEMHISTORY -

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

POITEMHISTORYTOTALS -

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

POITEMLIMITS -

Data type: BAPIESUH
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_PO_GETDETAIL 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_poheadertexts  TYPE STANDARD TABLE OF BAPIEKKOTX, "   
lv_purchaseorder  TYPE BAPIEKKO-PO_NUMBER, "   
lv_error_creating_idocs  TYPE BAPIEKKO, "   
lv_servicetexts  TYPE BAPIMMPARA-SELECTION, "   SPACE
lt_poitemcontractlimits  TYPE STANDARD TABLE OF BAPIESUC, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'BUS2012'
lt_poitemservices  TYPE STANDARD TABLE OF BAPIESLL, "   
lv_serial_id  TYPE SERIAL-CHNUM, "   '0'
lt_poitemsrvaccassvalues  TYPE STANDARD TABLE OF BAPIESKL, "   
lt_poservicestexts  TYPE STANDARD TABLE OF BAPIESLLTX, "   
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_items  TYPE BAPIMMPARA-SELECTION, "   'X'
lt_poitems  TYPE STANDARD TABLE OF BAPIEKPO, "   
lv_accountassignment  TYPE BAPIMMPARA-SELECTION, "   SPACE
lt_poitemaccountassignm  TYPE STANDARD TABLE OF BAPIEKKN, "   
lv_schedules  TYPE BAPIMMPARA-SELECTION, "   SPACE
lt_poitemschedules  TYPE STANDARD TABLE OF BAPIEKET, "   
lv_history  TYPE BAPIMMPARA-SELECTION, "   SPACE
lt_poitemconfirmations  TYPE STANDARD TABLE OF BAPIEKES, "   
lv_itemtexts  TYPE BAPIMMPARA-SELECTION, "   SPACE
lt_poitemtexts  TYPE STANDARD TABLE OF BAPIEKPOTX, "   
lv_headertexts  TYPE BAPIMMPARA-SELECTION, "   SPACE
lt_poitemhistory  TYPE STANDARD TABLE OF BAPIEKBE, "   
lv_services  TYPE BAPIMMPARA-SELECTION, "   SPACE
lt_poitemhistorytotals  TYPE STANDARD TABLE OF BAPIEKBES, "   
lt_poitemlimits  TYPE STANDARD TABLE OF BAPIESUH, "   
lv_confirmations  TYPE BAPIMMPARA-SELECTION. "   SPACE

  CALL FUNCTION 'ALE_PO_GETDETAIL'  "BAPI -> IDoc: ALE_PO_GETDETAIL
    EXPORTING
         PURCHASEORDER = lv_purchaseorder
         SERVICETEXTS = lv_servicetexts
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
         ITEMS = lv_items
         ACCOUNTASSIGNMENT = lv_accountassignment
         SCHEDULES = lv_schedules
         HISTORY = lv_history
         ITEMTEXTS = lv_itemtexts
         HEADERTEXTS = lv_headertexts
         SERVICES = lv_services
         CONFIRMATIONS = lv_confirmations
    TABLES
         POHEADERTEXTS = lt_poheadertexts
         POITEMCONTRACTLIMITS = lt_poitemcontractlimits
         POITEMSERVICES = lt_poitemservices
         POITEMSRVACCASSVALUES = lt_poitemsrvaccassvalues
         POSERVICESTEXTS = lt_poservicestexts
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
         POITEMS = lt_poitems
         POITEMACCOUNTASSIGNM = lt_poitemaccountassignm
         POITEMSCHEDULES = lt_poitemschedules
         POITEMCONFIRMATIONS = lt_poitemconfirmations
         POITEMTEXTS = lt_poitemtexts
         POITEMHISTORY = lt_poitemhistory
         POITEMHISTORYTOTALS = lt_poitemhistorytotals
         POITEMLIMITS = lt_poitemlimits
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_PO_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM ALE_PO_GETDETAIL

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 PO_NUMBER FROM BAPIEKKO INTO @DATA(ld_purchaseorder).
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_servicetexts).
DATA(ld_servicetexts) = ' '.
 
 
"SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'BUS2012'.
 
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 
 
 
 
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_items).
DATA(ld_items) = 'X'.
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_accountassignment).
DATA(ld_accountassignment) = ' '.
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_schedules).
DATA(ld_schedules) = ' '.
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_history).
DATA(ld_history) = ' '.
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_itemtexts).
DATA(ld_itemtexts) = ' '.
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_headertexts).
DATA(ld_headertexts) = ' '.
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_services).
DATA(ld_services) = ' '.
 
 
 
"SELECT single SELECTION FROM BAPIMMPARA INTO @DATA(ld_confirmations).
DATA(ld_confirmations) = ' '.
 


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!