Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BAPI_SALESORDER_CREATEFROMDAT2?

Former Member
0 Likes
2,336

hi,

Does anybody has the documentation of BAPI_SALESORDER_CREATEFROMDAT2. I am in currently 4OB. What is the field SALESDOCUMENT in import parameter & in order_header_in it is asking for reference document.

Can I able to create sales order with two condition types without any reference to other document.

Regards,

Karthik.k

2 REPLIES 2
Read only

Former Member
0 Likes
1,214

Hello, Is there anybody to give some information.

Regards,

Karthik.k

Read only

uwe_schieferstein
Active Contributor
0 Likes
1,214

Hello Karthik

Here is the FM documentation ECC 5.0 for your BAPI:

 FU BAPI_SALESORDER_CREATEFROMDAT2

 ____________________________________________________

 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.

 Parameters

     SALESDOCUMENTIN
     ORDER_HEADER_IN
     ORDER_HEADER_INX
     SENDER
     BINARY_RELATIONSHIPTYPE
     INT_NUMBER_ASSIGNMENT
     BEHAVE_WHEN_ERROR
     LOGIC_SWITCH
     TESTRUN
     CONVERT
     SALESDOCUMENT
     RETURN
     ORDER_ITEMS_IN
     ORDER_ITEMS_INX
     ORDER_PARTNERS
     ORDER_SCHEDULES_IN
     ORDER_SCHEDULES_INX
     ORDER_CONDITIONS_IN
     ORDER_CONDITIONS_INX
     ORDER_CFGS_REF
     ORDER_CFGS_INST
     ORDER_CFGS_PART_OF
     ORDER_CFGS_VALUE
     ORDER_CFGS_BLOB
     ORDER_CFGS_VK
     ORDER_CFGS_REFINST
     ORDER_CCARD
     ORDER_TEXT
     ORDER_KEYS
     EXTENSIONIN
     PARTNERADDRESSES

 Exceptions

 Function Group

     2032

Regarding your second question I am not sure what you are asking. The BAPI has a TABLES parameter ORDER_CONDITIONS_IN where you can define multiple conditions for each item in your sales order.

Regards

Uwe