SAP ALE_OUTB_DELIVERY_CONFIRM_DEC Function Module for BAPI -> IDoc: ALE_OUTB_DELIVERY_CONFIRM_DEC









ALE_OUTB_DELIVERY_CONFIRM_DEC is a standard ale outb delivery confirm dec 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_OUTB_DELIVERY_CONFIRM_DEC 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 outb delivery confirm dec FM, simply by entering the name ALE_OUTB_DELIVERY_CONFIRM_DEC into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_OUTB_DELIVERY_CONFIRM_DEC 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_OUTB_DELIVERY_CONFIRM_DEC'"BAPI -> IDoc: ALE_OUTB_DELIVERY_CONFIRM_DEC
  EXPORTING
   HEADERDATA =  "
   HEADERCONTROL =  "
   DELIVERY =  "Outbound Delivery Number
*  TECHCONTROL =  "
*  HEADERCONTROLSPL =  "
*  OBJ_TYPE = 'LIKP' "
*  SERIAL_ID = '0' "

TABLES
*  HEADERPARTNER =  "
*  HANDLINGUNITSERNO =  "
*  EXTENSION1 =  "Data Container (Unstructured)
*  EXTENSION2 =  "Data Container (Structured)
*  TOKENREFERENCE =  "Reference of CSL Token
*  ITEMDATASPL =  "
   RECEIVERS =  "
*  COMMUNICATION_DOCUMENTS =  "
*  APPLICATION_OBJECTS =  "
*  HEADERPARTNERADDR =  "
*  HEADERDEADLINES =  "
*  ITEMDATA =  "
*  ITEMCONTROL =  "
*  ITEMSERIALNO =  "
*  SUPCONDATA =  "
*  HANDLINGUNITHEADER =  "
*  HANDLINGUNITITEM =  "

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_SAPLV50I_001 User Exit BAPI Inbound Delivery Replication
EXIT_SAPLV50I_002 User Exit BAPI Inbound Delivery Confirmation
EXIT_SAPLV50I_003 User Exit BAPI Outbound Delivery Replication
EXIT_SAPLV50I_004 User Exit BAPI Outbound Delivery Confirmation
EXIT_SAPLV50I_009 User Exit BAPI for Changing Inbound Deliveries
EXIT_SAPLV50I_010 User Exit BAPI for Changing Outbound Deliveries

IMPORTING Parameters details for ALE_OUTB_DELIVERY_CONFIRM_DEC

HEADERDATA -

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

HEADERCONTROL -

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

DELIVERY - Outbound Delivery Number

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

TECHCONTROL -

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

HEADERCONTROLSPL -

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

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'LIKP'
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_OUTB_DELIVERY_CONFIRM_DEC

HEADERPARTNER -

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

HANDLINGUNITSERNO -

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

EXTENSION1 - Data Container (Unstructured)

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

EXTENSION2 - Data Container (Structured)

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

TOKENREFERENCE - Reference of CSL Token

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

ITEMDATASPL -

Data type: /SPE/BAPIOBDLVITEMCONF
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)

HEADERPARTNERADDR -

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

HEADERDEADLINES -

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

ITEMDATA -

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

ITEMCONTROL -

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

ITEMSERIALNO -

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

SUPCONDATA -

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

HANDLINGUNITHEADER -

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

HANDLINGUNITITEM -

Data type: BAPIDLVHDUNITM
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_OUTB_DELIVERY_CONFIRM_DEC 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_headerdata  TYPE BAPIOBDLVHDRCON, "   
lt_headerpartner  TYPE STANDARD TABLE OF BAPIDLVPARTNERCHG, "   
lv_error_creating_idocs  TYPE BAPIDLVPARTNERCHG, "   
lt_handlingunitserno  TYPE STANDARD TABLE OF BAPIDLVHDUNSERNO, "   
lt_extension1  TYPE STANDARD TABLE OF BAPIEXTC, "   
lt_extension2  TYPE STANDARD TABLE OF BAPIEXT, "   
lt_tokenreference  TYPE STANDARD TABLE OF BAPITOKENREFERENCE, "   
lt_itemdataspl  TYPE STANDARD TABLE OF /SPE/BAPIOBDLVITEMCONF, "   
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_headercontrol  TYPE BAPIOBDLVHDRCTRLCON, "   
lt_headerpartneraddr  TYPE STANDARD TABLE OF BAPIDLVPARTNADDRCHG, "   
lv_delivery  TYPE BAPIOBDLVHDRCON-DELIV_NUMB, "   
lt_headerdeadlines  TYPE STANDARD TABLE OF BAPIDLVDEADLN, "   
lt_itemdata  TYPE STANDARD TABLE OF BAPIOBDLVITEMCON, "   
lv_techcontrol  TYPE BAPIDLVCONTROL, "   
lt_itemcontrol  TYPE STANDARD TABLE OF BAPIOBDLVITEMCTRLCON, "   
lv_headercontrolspl  TYPE /SPE/BAPIOBDLVHDRCTRLCON, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'LIKP'
lt_itemserialno  TYPE STANDARD TABLE OF BAPIDLVITMSERNO, "   
lv_serial_id  TYPE SERIAL-CHNUM, "   '0'
lt_supcondata  TYPE STANDARD TABLE OF BAPIOBDLVITEMSUPCON, "   
lt_handlingunitheader  TYPE STANDARD TABLE OF BAPIDLVHDUNHDR, "   
lt_handlingunititem  TYPE STANDARD TABLE OF BAPIDLVHDUNITM. "   

  CALL FUNCTION 'ALE_OUTB_DELIVERY_CONFIRM_DEC'  "BAPI -> IDoc: ALE_OUTB_DELIVERY_CONFIRM_DEC
    EXPORTING
         HEADERDATA = lv_headerdata
         HEADERCONTROL = lv_headercontrol
         DELIVERY = lv_delivery
         TECHCONTROL = lv_techcontrol
         HEADERCONTROLSPL = lv_headercontrolspl
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
    TABLES
         HEADERPARTNER = lt_headerpartner
         HANDLINGUNITSERNO = lt_handlingunitserno
         EXTENSION1 = lt_extension1
         EXTENSION2 = lt_extension2
         TOKENREFERENCE = lt_tokenreference
         ITEMDATASPL = lt_itemdataspl
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
         HEADERPARTNERADDR = lt_headerpartneraddr
         HEADERDEADLINES = lt_headerdeadlines
         ITEMDATA = lt_itemdata
         ITEMCONTROL = lt_itemcontrol
         ITEMSERIALNO = lt_itemserialno
         SUPCONDATA = lt_supcondata
         HANDLINGUNITHEADER = lt_handlingunitheader
         HANDLINGUNITITEM = lt_handlingunititem
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_OUTB_DELIVERY_CONFIRM_DEC




ABAP code using 7.40 inline data declarations to call FM ALE_OUTB_DELIVERY_CONFIRM_DEC

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 DELIV_NUMB FROM BAPIOBDLVHDRCON INTO @DATA(ld_delivery).
 
 
 
 
 
 
"SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'LIKP'.
 
 
"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!