Functionality
You can use this method to create sales orders.
You must enter at least sales order header data (via ORDER_HEADER_INstructure) and partner data (via the ORDER_PARTNERS table) as inputparameters.
Enter the item data via the ORDER_ITEMS_IN table. You can allocate itemnumbers manually, by filling in the relevant fields, or the system doesit, according to the settings for Customizing, by leaving the relevantfields blank.
If you have configurable items, you must enter the configuration datain the ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF andORDER_CFGS_VALUE tables.
Credit cards can be transferred via the BAPICCARD structure, on the onehand, data for card identification, on the other, data for atransaction which has taken place in an external system.
Once you have created the sales order successfully, you will receivethe document number (SALESDOCUMENT field). Any errors that may occurwill be announced via the RETURN parameter.
If no sales area has been created in the sales order header, then thesystem creates the sales area from the sold-to party or ship-to party,who has been entered in the partner table. If a clear sales area cannotbe created, you will receive a system message, and the sales order willnot be created.

Notes
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 role, SP sold-to party
PARTN_NUMB Customer number
ORDER_ITEMS_IN..: MATERIAL Material number
Ship-to party:
If no ship-to party is entered, use the following: Ship-to party =
sold-to party.
Commit control:
The BAPI does not have a database commit. This means that the relevantapplication must leave the commit, in order that can be carried out onon the database. The BAPI BAPI_TRANSACTION_COMMIT is available forthis.
German key words:
The following key words must be entered in German, independantly of
the logon language:
DOC_TYPE Sales document type, for example: TA for standard order
PARTN_ROLE Partner role, for example: WE for ship-to party

Further information
You can find further information in the OSS. The note 93091 containsgeneral information on the BAPIs in SD.
INCLUDE SD_BAPI_SALESDOCUMENT_EX OBJECT DOKU ID TX
INCLUDE SD_BEHAVE_WHEN_ERROR OBJECT DOKU ID TX
INCLUDE SD_BAPI_BINRELTYPE OBJECT DOKU ID TX
INCLUDE SD_BAPI_CONVERT_PARVW_AUART OBJECT DOKU ID TX
INCLUDE SD_BAPI_INTNUMASS OBJECT DOKU ID TX
INCLUDE SD_LOGIC_SWITCH OBJECT DOKU ID TX

Description
This parameter contains data for the sales document header.
You can find information explaining the meaning of the individualparameter fields in the relevant data element documentation in the ABAPdictionary.
INCLUDE SD_BAPISDHEADX1_DOCU OBJECT DOKU ID TX
INCLUDE SD_BAPIVBELN_DOCU OBJECT DOKU ID TX
INCLUDE SD_BAPI_SENDER OBJECT DOKU ID TX
INCLUDE SD_BAPI_TESTRUN OBJECT DOKU ID TX
INCLUDE SD_EXTENSIONIN OBJECT DOKU ID TX

Description
The table contains credit card data, data for identification andauthorization.
The currency must be entered so that the amount fields are converted inthe correct currency.
INCLUDE SD_BAPI_CFGS_BLOB OBJECT DOKU ID TX
INCLUDE SD_BAPI_CFGS_INST OBJECT DOKU ID TX
INCLUDE SD_BAPI_CFGS_PART_OF OBJECT DOKU ID TX
INCLUDE SD_BAPI_CFGS_REF OBJECT DOKU ID TX
INCLUDE SD_BAPI_CFGS_REFINST OBJECT DOKU ID TX
INCLUDE SD_BAPI_CFGS_VALUE OBJECT DOKU ID TX
INCLUDE SD_BAPI_CFGS_VK OBJECT DOKU ID TX
INCLUDE SD_BAPICONDITION_DOCU OBJECT DOKU ID TX

Description
This parameter contains item input data for the sales order.
INCLUDE SD_BAPISDITEMX_DOCU OBJECT DOKU ID TX
INCLUDE SD_BAPI_KEYS OBJECT DOKU ID TX
INCLUDE SD_BAPIPARTNR_DOCU OBJECT DOKU ID TX

Description
This parameter contains schedule line data
INCLUDE SD_BAPISCHEDULEX_DOCU OBJECT DOKU ID TX
INCLUDE SD_BAPI_TEXT OBJECT DOKU ID TX
INCLUDE SD_PARTNERADDRESSES OBJECT DOKU ID TX
INCLUDE SD_BAPI_RETURN OBJECT DOKU ID TX