Ansicht
Dokumentation

BAPI_SALESORDER_CREATEFROMDAT1 - Sales order: Create Sales Order

PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Functionality

You can use this method to create sales orders.

You must enter at least the order header data (from the ORDER_HEADER_IN structure) as well as partner data (using the ORDER_PARTNERS table) as input parameters.

Enter item data using the ORDER_ITEMS_IN table. You can allocate the item number by filling in the relevant fields manually, or the system does it according to the settings in Customizing, whereby the relevant fields remain blank.

If the item is configurable, you need to enter the configuration data in the ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF and ORDER_CFGS_VALUE tables.

You can use the BAPICCARD structure to enter credit card data. You can either enter data for identifying the card or, you can enter data for an authorization in an external system.

Once you have successfully created the sales order, the system displays the document number (in the SALESDOCUMENT field), as well as detailed data about the other parties (in the OLD_TO_PARTY, SHIP_TO_PARTY and BILLING_PARTY structures). The RETURN parameter displays any errors that may have occured.

The ORDER_ITEMS_OUT table contains more detailed information that will enable you to judge the pricing and availability of an item.

Example

Notes

1. Mandatory entries:

ORDER_HEADER_IN : DOC_TYPE Sales document type
SALES_ORG Sales organization
DISTR_CHAN Distribution channel
DIVISION Division

ORDER_PARTNERS..: PARTN_ROLE Partner functions, SP sold-to party
PARTN_NUMB Customer number

ORDER_ITEMS_IN..: MATERIAL Material number
REQ_QTY Order quantity in sales unit

1. Ship-to party
   
   
   If a ship-to party hasn't been entered, the ship-to party = sold-to
   party
2. COMMIT control:Parameter WITHOUT_COMMIT
   If this switch is activated, the system does not process any Commit Work and the application that has called it up must trigger the Commit itself. To do this, useBAPI_TRANSACTION_COMMIT.
3. German keywords:
   The following keywords must be entered in German, regardless of the
   logon language:
   DOC_TYPE Sales document type, for example TA for standard order
   PARTN_ROLE Partner function, for example, WE for ship-to party

Further information

You can see further notes in OSS. Note 93091 contains general information about the SD BAPIs.

Parameters

BILLING_PARTY
CONVERT_PARVW_AUART
ORDER_CCARD
ORDER_CFGS_BLOB
ORDER_CFGS_INST
ORDER_CFGS_PART_OF
ORDER_CFGS_REF
ORDER_CFGS_VALUE
ORDER_HEADER_IN
ORDER_ITEMS_IN
ORDER_ITEMS_OUT
ORDER_PARTNERS
ORDER_SCHEDULE_EX
REFRESH_V45I
RETURN
SALESDOCUMENT
SHIP_TO_PARTY
SOLD_TO_PARTY
WITHOUT_COMMIT

Exceptions

Function Group

2032

ROGBILLS - Synchronize billing plans   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4711 Date: 20240523 Time: 184021     sap01-206 ( 61 ms )