Ansicht
Dokumentation
/SMERP/SD_DODELIVERY_NOREF_CRT - BAPI Wrapper: Generates Delivery Without Reference
General Material Data Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Functionality
This BAPI creates a delivery without a reference. A delivery split can mean that several deliveries are created.
Interface
| Parameter | Opt. | Description | |
|---|---|---|---|
| Import | |||
| SHIP_POINT | Shipping point | ||
| DLV_TYPE | Delivery type | ||
| SALESORG | Sales organization | ||
| DISTR_CHAN | Distribution channel | ||
| DIVISION | Division | ||
| SHIP_TO | Ship-to party | ||
| DATE_USAGE | X | Use of dates in DATES | |
| DEBUG_FLG | X | Forces termination (ALE analysis) | |
| Export | |||
| DELIVERY | X | First generated delivery | |
| NUM_DELIVERIES | X | Number of generated deliveries | |
| Tables | Direction | ||
| DATES | Import | Delivery date | |
| DLV_ITEMS | Import | Delivery items to be created without reference | |
| SERIAL_NUMBERS | X | Import | Serial numbers |
| EXTENSION_IN | X | Import | Additional input data |
| DELIVERIES | X | Export | Generated deliveries |
| CREATED_ITEMS | X | Export | Generated delivery items |
| EXTENSION_OUT | X | Export | Additional output data |
| RETURN | X | Export | Error log |
Opt.: Optional
Direction: Shows the direction used for table parameters.
Caution:
The exported table parameters are initialized before processing. This deletes any data that was in these parameters before the BAPI was called.
Imported parameters (selection)
Use of dates (DATE_USAGE)
DATE_USAGE decides which dates from parameter DATES are copied to the delivery.
- DATE_USAGE = '1' Material availability date
- DATE_USAGE = '2' Delivery date
- DATE_USAGE = '0' (or no entry for DATE_USAGE) Planned goods issue date
See also the documentation for parameter DATE_USAGE.
DEBUG_FLG
For internal use only. The DEBUG_FLG can be used in ALE inbound processing to force a termination, thereby making the analysis of the process easier.
Delivery dates (DATES)
The following dates can be entered as a time stamp in this table parameter:
- Delivery date
- Planned goods issue date
- Loading date
- Transportation planning date
- Material availability date
See also the documentation for parameters DATE_USAGE and DATES.
Delivery items to be created (DLV_ITEMS)
Here, the delivery items to be created
are specified. The delivery item number cannot be specified. For more detailed information about optional and required fields, see the documentation for this parameter.
External delivery number (DLV_ITEMS-DELIV_NUMB)
A delivery number from the external number range interval can be specified.
Serial numbers (SERIAL_NUMBERS)
In parameter SERIAL_NUMBERS, serial numbers can be assigned to the delivery items that supply the specified order items.
Additional import data (EXTENSION_IN)
In Parameter EXTENSION_IN, additional data can be transferred. For more information, see the documentation for BAdI BADI_DLV_CREATE_NOREF_EXTIN.
Exported parameters
Delivery number (DELIVERY)
Generated delivery (key field in BOR object type LIKP). In case of a delivery split, this is the first generated delivery.
Number of generated deliveries (NUM_DELIVERIES)
In case of a delivery split, more than one delivery may be generated.
Generated deliveries (DELIVERIES)
List of all generated deliveries (including DELIVERY).
Generated delivery items (CREATED_ITEMS)
List of all generated delivery items.
Additional export data (EXTENSION_OUT)
In case of a synchronous call, additional
data can be returned to the caller after delivery creation, in parameter EXTENSION_OUT. See the documentation for BAdI BADI_DLV_CREATE_EXTOUT.
Error log (RETURN)
Parameter RETURN contains the error log. In the same way as
in transaction VL10, deliveries may be created even if there were error messages during processing.
Since an asynchronous caller of the BAPI (ALE) only learns of the success of processing via the RETURN
parameter, error messages are converted to warning messages if at least one delivery could be created. If a delivery is created successfully with converted error messages, message VLBAPI061 (see below) is output.
In addition, RETURN contains the following important messages:
| Message | Description |
|---|---|
| BAPI000 | A delivery could be created |
| BAPI001 | A delivery could not be created |
| VLBAPI061 | Delivery created with errors (see warning messages) |
| VL311 | Delivery |
Thus, in case of an asynchronous call, the VL311 messages tell you which deliveries could be created.
Transactional Behavior
- No COMMIT WORK.
- ROLLBACK WORK, if no delivery could be created.
Example
Notes
- This BAPI is not optimized for the creation of large numbers of invoices.
- The BAPI cannot be called multiple times in one logical unit of work (LUW). After a successful call, a COMMIT WORK is required of the caller before this BAPI or another BAPI of function group V50I can be called.
- The BAPI cannot specify delivery item numbers.
Further information
- Documentation for the parameters
- Documentation for the BAdIs:
- BADI_DLV_CREATE_NOREF_EXTIN
- BADI_DLV_CREATE_EXTOUT.
Parameters
ES_BAPI_OUTPUTET_CREATED_ITEMS
ET_DELIVERIES
ET_EXTENSION_OUT
ET_RETURN
EV_DELIVERY
EV_NUM_DELIVERIES
IS_BAPI_INPUT
IT_DATES
IT_DLV_ITEMS
IT_EXTENSION_IN
IT_SERIAL_NUMBERS
IV_CREATE_TYPE
IV_DATE_USAGE
IV_DISTR_CHAN
IV_DIVISION
IV_DLV_TYPE
IV_SALESORG
IV_SHIP_POINT
IV_SHIP_TO
Exceptions
Function Group
RP/SAPLBAPI_SD_DELIVERYSUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 11509 Date: 20240425 Time: 004440 sap01-206 ( 84 ms )
