regarding BAPI_SALESORDER_CREATEFROMDAT2

[Former Member]

Hey guys,

<b>Regarding BAPI "BAPI_SALESORDER_CREATEFROMDAT2"</b>

I have developed a program for creating SALES ORDER using BAPI.(BAPI_SALESORDER_CREATEFROMDAT2)

I want to know how to check the confirmation of values stored in sales order tables..is there any specific table

i have to check for the datas stored or not?

or otherwise how can i know the correct input format to fields and store the values to BAPI..

Please guide me.

ambichan.

[Former Member]

Check the tables

vbak,vbap,VBEP

regds

gv

Message was edited by: Venkatesan G

[jayanthi_jayaraman]

Hi,

Check the documentation.You can get the following details.

Short text

Sales order: Create Sales Order

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.

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

Further Information

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

[jayanthi_jayaraman]

Hi,

Adding to my previous reply,

if you check for the function group of the Fm[2032] in se49,you can find the following tables used.

T001 Company Codes

TPAR Business Partner: Functions

TVAK Sales Document Types

TVKO Organizational Unit: Sales Organizations

VBAK Sales Document: Header Data

VBAP Sales Document: Item Data

VBFA Sales Document Flow

VBUK Sales Document: Header Status and Administrative Data

VBUP Sales Document: Item Status