Ansicht
Dokumentation

FSH_API_SALESDOCUMENT_CREATE - Sales order: Create Sales Order

FSH_API_SALESDOCUMENT_CREATE - Sales order: Create Sales Order

rdisp/max_wprun_time - Maximum work process run time   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

You can use this method to create sales orders.

You must enter at least sales order header data (via ORDER_HEADER_IN structure) and partner data (via the ORDER_PARTNERS table) as input parameters.

Enter the item data via the ORDER_ITEMS_IN table. You can allocate item numbers manually, by filling in the relevant fields, or the system does it, according to the settings for Customizing, by leaving the relevant fields blank.

If you have configurable items, you must enter the configuration data in the ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF and ORDER_CFGS_VALUE tables.

Credit cards can be transferred via the BAPICCARD structure, on the one hand, data for card identification, on the other, data for a transaction which has taken place in an external system.

Once you have created the sales order successfully, you will receive the document number (SALESDOCUMENT field). Any errors that may occur will be announced via the RETURN parameter.

If no sales area has been created in the sales order header, then the system 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 cannot be created, you will receive a system message, and the sales order will not be created.

Example

Note

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 role, SP sold-to party
PARTN_NUMB Customer number

ORDER_ITEMS_IN..: MATERIAL Material number

2. Ship-to party:

If no ship-to party is entered, use the following: Ship-to party =
sold-to party.

3. Commit control:
The BAPI does not have a database commit. This means that the relevant application must leave the commit, in order that can be carried out on on the database. The BAPI BAPI_TRANSACTION_COMMIT is available for this.

4. 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

Notes

Further information

You can find further information in the OSS. The note 93091 contains general information on the BAPIs in SD.





Parameters

BEHAVE_WHEN_ERROR
BINARY_RELATIONSHIPTYPE
CONTRACT_DATA_IN
CONTRACT_DATA_INX
CONVERT
EXTENSIONEX
EXTENSIONIN
FSH_ORDER_HEADER_IN
FSH_ORDER_HEADER_INX
FSH_ORDER_ITEM_EX
FSH_ORDER_ITEM_IN
FSH_ORDER_ITEM_INX
FSH_VAS_ITEM_IN
FSH_VAS_TEXT
INT_NUMBER_ASSIGNMENT
LOGIC_SWITCH
ORDER_CCARD
ORDER_CFGS_BLOB
ORDER_CFGS_INST
ORDER_CFGS_PART_OF
ORDER_CFGS_REF
ORDER_CFGS_REFINST
ORDER_CFGS_VALUE
ORDER_CFGS_VK
ORDER_CONDITIONS_IN
ORDER_CONDITIONS_INX
ORDER_HEADER_IN
ORDER_HEADER_INX
ORDER_ITEMS_IN
ORDER_ITEMS_INX
ORDER_KEYS
ORDER_PARTNERS
ORDER_SCHEDULES_IN
ORDER_SCHEDULES_INX
ORDER_TEXT
PARTNERADDRESSES
RETURN
SALESDOCUMENT
SALESDOCUMENTIN
SENDER
TESTRUN

Exceptions

Function Group

FSH_SD_API

CPI1466 during Backup   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 7205 Date: 20240523 Time: 111548     sap01-206 ( 71 ms )