SAP BAPI_CUSTSCHEDULAGREE_CONFDELV Function Module for Customer Sched. Agreement: Confirmation of Delivery; Document Flow Update
BAPI_CUSTSCHEDULAGREE_CONFDELV is a standard bapi custschedulagree confdelv SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Customer Sched. Agreement: Confirmation of Delivery; Document Flow Update 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 bapi custschedulagree confdelv FM, simply by entering the name BAPI_CUSTSCHEDULAGREE_CONFDELV into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2035
Program Name: SAPL2035
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_CUSTSCHEDULAGREE_CONFDELV 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 'BAPI_CUSTSCHEDULAGREE_CONFDELV'"Customer Sched. Agreement: Confirmation of Delivery; Document Flow Update.
EXPORTING
SALESDOCUMENT = "Sales Document
TABLES
DLVITEM = "BAPI: Delivery Confirmation
DLVITEMDATA = "BAPI: Delivery Confirmation Data
* TOKENREFERENCE = "CSL: Data Element CSL_TR_EXT as Structure (BAPI Tab.Arg.)
* RETURN = "Return Parameter
IMPORTING Parameters details for BAPI_CUSTSCHEDULAGREE_CONFDELV
SALESDOCUMENT - Sales Document
Data type: BAPIVBELN-VBELNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_CUSTSCHEDULAGREE_CONFDELV
DLVITEM - BAPI: Delivery Confirmation
Data type: BAPISDDLVITEMOptional: No
Call by Reference: No ( called with pass by value option)
DLVITEMDATA - BAPI: Delivery Confirmation Data
Data type: BAPISDDLVITEMDATAOptional: No
Call by Reference: No ( called with pass by value option)
TOKENREFERENCE - CSL: Data Element CSL_TR_EXT as Structure (BAPI Tab.Arg.)
Data type: CSL_TR_EXSOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_CUSTSCHEDULAGREE_CONFDELV 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_dlvitem | TYPE STANDARD TABLE OF BAPISDDLVITEM, " | |||
| lv_salesdocument | TYPE BAPIVBELN-VBELN, " | |||
| lt_dlvitemdata | TYPE STANDARD TABLE OF BAPISDDLVITEMDATA, " | |||
| lt_tokenreference | TYPE STANDARD TABLE OF CSL_TR_EXS, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BAPI_CUSTSCHEDULAGREE_CONFDELV' "Customer Sched. Agreement: Confirmation of Delivery; Document Flow Update |
| EXPORTING | ||
| SALESDOCUMENT | = lv_salesdocument | |
| TABLES | ||
| DLVITEM | = lt_dltitem | |
| DLVITEMDATA | = lt_dltitemdata | |
| TOKENREFERENCE | = lt_tokenreference | |
| RETURN | = lt_return | |
| . " BAPI_CUSTSCHEDULAGREE_CONFDELV | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_CUSTSCHEDULAGREE_CONFDELV
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 VBELN FROM BAPIVBELN INTO @DATA(ld_salesdocument). | ||||
Search for further information about these or an SAP related objects