Creation of saleorder with reference to order using BAPI_SALESORDER_CREATE

hello
iam trying to create a sale order with respect to order BAPI_SALESORDER_CREATEFROMDAT2.
the parameters i am passing is
*Fill the header information for the order.
wa_order_header_in-doc_type = Sales Doc type of order to be created.
wa_order_header_in-sales_org = sales org.
wa_order_header_in-distr_chan = distribution channel.
wa_order_header_in-division = division.
wa_order_header_in-ref_doc = order number(This is the order i refer to).
wa_order_header_in-refdoc_cat = 'C' (c stands for order).
*Fill the item level information for the order.
wa_order_items_in-itm_number = item number.
wa_order_items_in-material = material number.
wa_order_items_in-ref_doc = order number(This is the order i refer to).
wa_order_items_in-ref_doc_it = Item number of order i create.
wa_order_items_in-ref_doc_ca = 'C'.
APPEND wa_order_items_in TO i_order_items_in.
*Fill the partner information for the order.
wa_order_partners-partn_role = partner function.
wa_order_partners-partn_numb = partner number.
APPEND wa_order_partners TO i_order_partners.
& likewise conditions structure
i have done bapi_transaction_commit after bapi call.
probelm which i am facing is , BAPI is creating a new sale order.. but it is not creating a order with reference order.
thanks

see this example as how to add text and multiple lines...
loop at it_tab into wa_tab.
        record_no = sy-tabix.
        serial_no = wa_tab-ser_no.
*       ORDER_TYPE = WA_TAB-ORD_TYP.
        sales_office = wa_tab-sal_off.
        sales_group = wa_tab-sal_grp.
        old_ref_no = wa_tab-ref_shp_to_par.
        shipping_condition = wa_tab-ship_cond.
        perform sales_info using sales_office sales_group
shipping_condition.
        condense shipping_condition.
        ship_cond = shipping_condition.
        on change of old_ref_no.
          refresh it_bapisdhead.
          refresh it_bapisdhead1x.
          refresh it_bapiparnr.
             wa_bapisdhead-doc_type     = wa_tab-ord_typ.
             wa_bapisdhead1x-doc_type   = 'X'.
             wa_bapisdhead-sales_org    = '5088'.
             wa_bapisdhead1x-sales_org = 'X'.
             wa_bapisdhead-distr_chan   = '01'.
             wa_bapisdhead1x-distr_chan = 'X'.
             wa_bapisdhead-division     = '00'.
             wa_bapisdhead1x-division   = 'X'.
             wa_bapisdhead-sales_grp    = sales_group.
             wa_bapisdhead1x-sales_grp = 'X'.
             wa_bapisdhead-sales_off    = sales_office.
             wa_bapisdhead1x-sales_off = 'X'.
             wa_bapisdhead-purch_no_c   = wa_tab-po_no.
             wa_bapisdhead1x-purch_no_c = 'X'.
             wa_bapisdhead-purch_date   = wa_tab-po_date.
             wa_bapisdhead1x-purch_date = 'X'.
             wa_bapisdhead-req_date_h   = wa_tab-req_del_date.
             wa_bapisdhead1x-req_date_h = 'X'.
             wa_bapisdhead-incoterms1   = 'EXW'.
             wa_bapisdhead1x-incoterms1 = 'X'.
             wa_bapisdhead-incoterms2   = wa_tab-inco_terms2.
             wa_bapisdhead1x-incoterms2 = 'X'.
             wa_bapisdhead-ship_cond    = ship_cond.
             wa_bapisdhead1x-ship_cond = 'X'.
             wa_bapisdhead-ref_1        = wa_tab-ref_sld_to_par.
             wa_bapisdhead1x-ref_1      = 'X'.
             wa_bapisdhead-ref_1_s      = wa_tab-ref_shp_to_par.
             wa_bapisdhead1x-ref_1_s    = 'X'.
             append wa_bapisdhead to it_bapisdhead.
             append wa_bapisdhead1x to it_bapisdhead1x.
             wa_bapiparnr-unload_pt    = wa_tab-unload_pt.
             wa_bapiparnr-partn_role   = 'AG'.
             wa_bapiparnr-partn_numb   = wa_tab-sld_to_par.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
             wa_bapiparnr-partn_role   = 'VE'.
             wa_bapiparnr-partn_numb   = '777'.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
             wa_bapiparnr-partn_role   = 'ZM'.
             wa_bapiparnr-partn_numb   = '999'.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
           if wa_tab-bill_to_par <> ' '.
             wa_bapiparnr-partn_role   = 'RE'.
             wa_bapiparnr-partn_numb   = wa_tab-bill_to_par.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
           endif.
           if wa_tab-payer <> ''.
             wa_bapiparnr-partn_role   = 'RG'.
             wa_bapiparnr-partn_numb   = wa_tab-payer.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
           endif.
           if wa_tab-ship_to_par <> ''.
             wa_bapiparnr-partn_role   = 'WE'.
             wa_bapiparnr-partn_numb   = wa_tab-ship_to_par.
             append wa_bapiparnr to it_bapiparnr.
             clear wa_bapiparnr.
           endif.
           wa_bapisdtext-text_id   = 'Z113'.
           wa_bapisdtext-langu     = 'EN'.
           wa_bapisdtext-text_line = wa_tab-add_txt.
           append wa_bapisdtext to it_bapisdtext.
           clear wa_bapisdtext.
           if wa_tab-banker <> ''.
             wa_bapisdtext-text_id   = 'ZKT1'.
             wa_bapisdtext-langu     = 'EN'.
             wa_bapisdtext-text_line = wa_tab-banker.
             append wa_bapisdtext to it_bapisdtext.
             clear wa_bapisdtext.
           endif.
           if wa_tab-fwd_age <> ''.
             wa_bapisdtext-text_id   = 'ZKT1'.
             wa_bapisdtext-langu     = 'EN'.
             wa_bapisdtext-text_line = wa_tab-fwd_age.
             append wa_bapisdtext to it_bapisdtext.
             clear wa_bapisdtext.
           endif.
        endon.
*                  ***** ITEM LEVEL DATA *****
             wa_bapiitemin-material     = wa_tab-matno.
             wa_bapiiteminx-material    = 'X'.
             wa_bapiitemin-target_qty   = wa_tab-qty.
             wa_bapiiteminx-target_qty = 'X'.
             wa_bapiitemin-plant        = wa_tab-plant.
             wa_bapiiteminx-plant       = 'X'.
             wa_bapiitemin-item_categ   = 'YAPS'.
             wa_bapiiteminx-item_categ = 'X'.
             append wa_bapiitemin to it_bapiitemin.
             append wa_bapiiteminx to it_bapiiteminx.
             clear wa_bapiitemin.
             clear wa_bapiiteminx.
*             WA_BAPICOND-COND_TYPE      = 'PR00'.
*             WA_BAPICONDX-COND_TYPE     = 'X'.
             wa_bapicond-cond_value     = wa_tab-amt * wa_tab-qty.
             wa_bapicondx-cond_value    = 'X'.
             append wa_bapicond to it_bapicond.
             append wa_bapicondx to it_bapicondx.
             clear wa_bapicond.
             clear wa_bapicondx.
        at end of ref_shp_to_par.
          call function 'BAPI_SALESORDER_CREATEFROMDAT2'
            exporting
*             SALESDOCUMENTIN               =
              order_header_in               = wa_bapisdhead
              order_header_inx              = wa_bapisdhead1x
*             SENDER                        =
*             BINARY_RELATIONSHIPTYPE       =
*             INT_NUMBER_ASSIGNMENT         =
*             BEHAVE_WHEN_ERROR             =
*             LOGIC_SWITCH                  =
*             TESTRUN                       =
*             CONVERT                       = ' '
*           IMPORTING
*             SALESDOCUMENT                 =
            tables
              return                        = it_errmsg
              order_items_in                = it_bapiitemin
              order_items_inx               = it_bapiiteminx
              order_partners                = it_bapiparnr
*             ORDER_SCHEDULES_IN            =
*             ORDER_SCHEDULES_INX           =
              order_conditions_in           = it_bapicond
              order_conditions_inx          = it_bapicondx
*             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                    = it_bapisdtext
*             ORDER_KEYS                    =
*             EXTENSIONIN                   =
*             PARTNERADDRESSES              =
    read table it_errmsg into wa_errmsg with key type = 'E'
    binary search.
    if sy-subrc ne 0.
             call function 'BAPI_TRANSACTION_COMMIT'
    endif.
endloop.

Similar Messages

Sales order creation with reference to quote using BAPI

Hi All,
I am trying to create a sales order with reference to quote using BAPI BAPI_SALESORDER_CREATEFROMDAT2.
I am passing the Quote number and preceding doc.category (B) at the header level and
at item level I am passing the quote number and the line item number in the quote for REF_DOC and REF_DOC_IT.
The order is created but there seems to be some issue with the document flow.
I do not see the Reference Doc number at the header level from the Sales order document flow whereas I can see the Reference Doc for each line item.
In VBFA I can see the Ref.Doc number at the header level along with the Ref.Doc at the line item level.
Why do you think it is not showing at the header level from Sales Document Document Flow?
Is there any bug in the standard BAPI or is there any OSS note?
Any answer would be greatly appreciated.
Thanks
Sandeep

hi,
Are you giving different quotation numbers in the different line items, if that is the case you will not get that in the header document flow, as it cann't point to all the quotations.
Thanks,
Mahesh.

Creation of PO with reference only

Dear Fiends,
Can anyone explain,how can we make creation of PO with Reference to PR mandatory for Certain documents types of PO.
Regards
SAPMM

Hi,
Copy the field selection key NBF(Define screen lay out at document level in spro>Matmgmt>Purchasing>Purch.order>)
In new field selection key go to reference data item and make mandatory to PR
Define some PO document type and link this New field selection key at "define document types"
Regards,
Sattuj

BAPI For CREATE SALES ORDER WITH REFERENCE TO ORDER

Hi ,
I want to develop a new RFC for 'Creating Sales Order' with reference to another sales order -
Is there any BAPI available for the same ? (Version 4.7) - I know its available for new create and change
but couldn't find for create with reference to Order ...
Thanks in advance ...
Regards
Rajesh.

Hi,
You can use this FM "/SAPNEA/SMAPI_ORDER_CREATE". I haven;t tried this but you can still give it a try. Mention the Reference Order Type and other data in the header work area and pass it to the FM.
Reward if it's useful.
Thanks,
Anil

MIGO vs MB1a - cancellation with reference to order

Folks,
Within MB1A we have the option to make a cancellation with reference to order by going into the menu in the selection screen:
Goods issue / Cancel with reference / To order.
This allows the user to only cancel issues for those items that were initially issued on the order. I was trying to find the same logic in MIGO but I cant find it. Customizing also only shows Material document as reference document for cancellations. We cannot add another reference document, or can we?
Thanks,
MZ

Hi,
MIGO is the enjoy transaction can be used for GR,GI and CANCELLATION. If you want to cancell with reference to order, that order might be partially completed, still delivery need to done on this, to which quantity in order you will post cacellation. Hence SAP system proposed to refer materila document as a reference for cancellation. With that reference the items which are issued or received can be cancelled exactly (quantity and amount)
In MB1A :It is purely related to GI and refer the order
Hence in standard SAP in MIGO, you cannot have option of order as reference for cancellation. I hope it will help you. Thanking you.

Create Inbound Delivery with Reference to PO using Serial Numbers

I guys.
I didn't find any BAPI to create an Inbound Delivery with Reference to PO using Serial Numbers so I've made a Function Module with BDCData.
LOOP AT serial.
    ADD 1 TO ld_count.
    ld_value = serial-sernr.
    CONCATENATE 'RIPW0-SERNR(' ld_count ')' INTO ld_field.
    PERFORM bdc_field USING ld_field ld_value.
ENDLOOP.
This works fine for 10 entries, but when I'm trying to use 1000 entries in serial Internal Table I'm getting the error: Screen 0000 is too large for internal batch input area - Message no. 00379.
Please note that my issue is the Serial numbers, so don't answer me please with BAPIs that doesnt allow me to deal with this.
Any idea?
Thanks in advance,
Nuno

As I expect, it solved my problem. It's not pretty, but it works...
PERFORM bdc_dynpro      USING 'SAPLIPW1'       '0200'.
PERFORM bdc_field       USING 'BDC_CURSOR'     'RIPW0-SERNR(01)'.
DATA: ld_valor(4) TYPE n,
        ld_next,
        ld_tabix TYPE sy-tabix.
LOOP AT serial.
    ld_tabix = sy-tabix.
    IF ld_next = 'X'.
      CLEAR ld_next.
      ld_count = 2.
    ELSE.
      ADD 1 TO ld_count.
    ENDIF.
    ld_value = serial-sernr.
    CONCATENATE 'RIPW0-SERNR(' ld_count ')' INTO ld_field.
    PERFORM bdc_field USING ld_field ld_value.
    ld_valor = ld_tabix + 17.
    ld_valor = ld_valor MOD 18.
    IF ld_tabix NE 1 AND ( ld_tabix EQ 19 OR ld_valor EQ 0 ).
      ld_next = 'X'.
      PERFORM bdc_field       USING 'BDC_OKCODE'     '=PNPG'.
      PERFORM bdc_dynpro      USING 'SAPLIPW1'       '0200'.
      PERFORM bdc_field       USING 'BDC_CURSOR'     'RIPW0-SERNR(01)'.
    ENDIF.
ENDLOOP.
PERFORM bdc_field       USING 'BDC_OKCODE'     '=RWS'.

Creating sales order with reference to order

Hi SD gurus.
I try creating a sales order with reference to order, but I get this error message: "Flow control: Entry SAPMV45B, UER1, E0, * , AU , * is missing in T185". I don't know what is missing. Please, could you help me?
Thanks a lot.
Marta.

hi,
this is to inform you that,
i went to SE16N given there T185 and checked with UER1 which is an FCODE FOR OVER VIEW SCREEN in VOV8.
this entry is missing for the combination.
please check in your sales order in VOV8 whether you have maintained UER1 in the above field.
if not :
please maintain the entries missed in T185 in SM30.
because i have checked teh same in SM30 it is having opportunity to maintain.
hope this will solve your issue.
regards,
balajia
Edited by: balaji timmampalli achari on Nov 23, 2010 12:00 PM

IST OPERATION SUBCONTRACTED WITH REFERENCE TO ORDER

Hello SAP Experts,
i am doing operation subcontractiing. My first operation is subcontracted. So, I have assigned PP02 control key to first operation and maintained external processing data for opration in routing. When i saved the order, for that operation PR gets generated.
Now, I converted PR into PO and assigned raw material that has to be send to vendor. By 541 mvt. type material is issued to vendor. When i do goods receipt in MIGO, system is not showing storage location field. I dont find material in stock anywhere.
But i can see quantity received in external processing tab of first operation in routing overveiw in order.HERE P.O is generated with reference to order.& it is in cost center.while confirming the second operation system will ask for storage location of material received from vendor.it ie not seen in mmbe.iam creating new code and it is assigned to second operation .
Then how can i issue the material from storage for second operation if it is not in stock?
How can i get stock of subcontracted material by MIGO?
Please help me.
regards,
RAHUL

Hi!,
When you say operation subcontracting, in SAP it is considered as a service you are recieving and hence there is no material movement involved in that because you are sending a WIP material and recieving a WIP material back. But as per indian requirements whenever a material is sent out side the factory premises, you need to send a challan alongwith that. To print a challan you need to have a material movement. This movement (541) happens in normal material subcontracting but not in operation subcontracting. To generate a material doc, you can send the raw material with 541 movement but on GR of the processed material just reverse that movement so that raw material will again come in the stock. Then issue that raw material on order with 261 movement.
I hope this will help in resolving your problem.
Regards,
Uday

Creation of sales order with reference to Quotation using BAPI

Hi All,
I am using BAPI "BAPI_SALESORDER_CREATEFROMDAT2" for creating sales order. Can you please tell how can I create a sales order with reference to a Quotation.

Vinit,
In your header structure, set like this:
hdr-REF_DOC = i_order-vbeln. "assign quotation # to sales order
hdr-REFDOC_CAT = 'B'.         "assign Quotation to VBTYP_N.
For each line item, set as follows:
Assigning ref doc to create line item entries in VBFA.
    itm-REF_DOC    = i_order-vbeln. "quote number
    itm-REF_DOC_IT = i_vbap-posnr.   "quote line item #
    itm-REF_DOC_CA = 'B'.
data: ret_text type BAPIRET2.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
      ORDER_HEADER_IN           = hdr
      convert                   = 'X'
    IMPORTING
      SALESDOCUMENT             = salesdoc
    TABLES
      return                    = ret_tbl
      ORDER_ITEMS_IN            = itm
      ORDER_PARTNERS            = prtnr
      ORDER_ITEMS_inx           = itmx
      ORDER_CONDITIONS_IN       = conds
      ORDER_CONDITIONS_INX      = condsx
      order_schedules_in        = schd_lin.
Don't forget those points.

Creation of compliants with reference to r/3 sales order.

dear friends
Is it possible to create compliants in CRM with reference to r/3 sales order? if answer is yes please provide the solution how to configure the same.
regards
naveen

Hi Naveen
I dont know why you want to create complaints with respect to the sales order.
The usual process the companies follow is to create complaints wrt to the invoice number.
But incase you wish to create complaints wrt to sales order, then you can use implementation of a BAdI CRM_COPY_BADI_EXT for the same in the CRM system which will allow you to create a complaint in CRM System wrt sales order in ECC.The path for the same in CRM system is IMG>CRM>Transactions> Settings for Complaints> Integration>Business Add-Ins for Document Referencing> Business Add-In: Create Complaints with Reference to External Document
Secondly maintian the assignment between the Business Object type of referenced doc and Transaction type using path IMG>CRM>Transactions> Settings for Complaints> Integration>Business Add-Ins for Document Referencing> Assign Business Object Types to Transaction Types
Now go to CRMD_ORDER and open the transaction type CRLP, you will get pop-up for creation of complaint where you can choose the transaction type and business object type and reference sales order number/ invoice number and create the complaint.
Hope this will help
Regards,
Rekha Dadwal
You gain a point for every point that you reward. So reward helpful answers generously

CREATE SALES ORDER WITH REFERENCE TO INVOICE USING RECORDING

Hi,
I wanted to know if it was possible to create a sales order with reference to an invoice using recording(SHDB transaction).If there is some other method please explain the method in detail(Its very urgent)

Hi,
You should be able to use BAPI_SALESORDER_CREATEFROMDAT2 instead of doing a BDC and you can populate the reference document in the relevant header field.
Gareth.

Creation of IBase with reference to sales order for Configurable product.

Hi Experts,
Can any one tell me How to create Ibase with reference to sales order for Configurable Products. I know we can create this using IB63, but what i need to do in this Transaction code and what settings i need to do in SPRO.
pls send ur replies to [email protected]
Thank you..

Hi
You can create IBase using T-Code-IB53 and in there you can give Parent and child products.
A)Define Installed Base Category and Installation Rules-CRM
B)Define Object Families
C)Define default settings for equipment replication
D)Define Serial Number Profiles-ECC
E)Txn BF31-ECC
F)Set up attributes for individual objects
G)Set up set types
H)Set up category
I)Set up views
J)Allow reference product for IO
I hope it helps
If you require further help let me know.
Cheers
Raj

Creation of Billing with reference to the Sales Order

Dear Friends,
I need your suggestion for the following scenario.
Client wants to create the Billing Document with reference to the Sales order.I mean when he is entering sales Order while creating the billing document ,the system should generate the billing document only for the delivered quantity.
e.g sales order is created for 100 Tons.And there are 5 delivery documents for 50 Tons.(Still the Sales order is open).
Now when billing document is created with reference to the sales order ( Not with reference to the Delivery Document) it should create the billing document only for these five deliveries.
Is it possible? If yes,how?
Thanks in advance.
Regards,
Shrikant

Hi Murali,
Currently client has software where he enters only Sales Order no and their software creates the billing for the delivery document for this Sales Order.
Here client does not want to enter multiple delivery document nos if any.He wants to enter only Sales Order no.
Regards,
Shrikant

Create a Sales Order with Reference to Contract using IDoc / LSMW ( AFS )

Hi Gurus,
I need to crate a Sales Order with reference to a Contract. I need to upload Sales Orders with reference to contract via LSMW.
So far, I've been able to create the Sales Order with ref to contract. But, the Sales Order Quantity is not getting deducted from the Original Qty in Referred Contract ( When try to create another Sales Order referring to the same Contract.) When a Sales Order is created manually, this is working fine.
Please tell me if I've missed some parameter which stopping it create the link to exact schedule line ( Sizes level )
The Details of the IDoc which is been created via LSMW are as follows;
Message Type: ORDERS
Basic Type     : /AFS/ORDERS05
Process Code : ORDE / DELO
( Tried with both process codes. But the Identification is the same for both: IDOC_INPUT_ORDERS )
*_In Header;_
Segment : E1EDK02 - IDoc: Document header reference data *
Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
Contract Order is mapped for field BELNR
*_In Item;_
Segment : E1EDP02 - IDoc: Document Item Reference Data *
Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
Contract Order is mapped to field BELNR
Line Item of the Contract is mapped to field ZEILE
I also tried passing the Schedule line of Contract in Segment : E1J3P01 AFS IDoc: Doc.item general data
to following fields;
J_3AETENV
J_3AVGETE
/AFS/UETENR
Still its not getting updated in the VBEP also..
Please help me with regard to this. Points will be awarded for your valuable contribution.
Thanks.

Hi,
This issue is been resolved.
One of my friend helped me with resolving this issue..
Once the below mentioned configurations were done on SPRO, the Sales Order was created with reference to Contract and the Qty was reflected when tried to create a new Order referring the same contract.;
u2022     SPRO --> SD -->Sales --> Sales Documents --> Sales Document Header --> Define Sales Document Types --> Field : Outline agreement message; from blank to u201CBu201D.
u2022     SPRO -->SD -->Sales --> Sales Documents --> Sales Document Header --> Maintain Sales Document Types for AFS --> Field : Outline agreement message; from blank to u201CAu201D

Sales order with reference to contract using IDOC_INPUT_ORDERS

Hi all,
I had the requirement to create sales order with reference to contract based on some validations of idoc values and then passing the modified idoc data table to IDOC_INPUT_ORDERS. I have completed the coding till the modification of data in a new function module ('Z') and then calling the IDOC_INPUT_ORDERS FM inside that. Now my problem is while creating the sales order, the bdc for Txn VA01 is not populating those values to screen fields which I want to populate. I could find out that some modifs needs to be done in some user exit for reference to contract case.But finding difficulty in getting the exact place to make the modifications. Any pointer to this problem would be highly appreciated.
Regards,
Divya

Hi,
This issue is been resolved.
One of my friend helped me with resolving this issue..
Once the below mentioned configurations were done on SPRO, the Sales Order was created with reference to Contract and the Qty was reflected when tried to create a new Order referring the same contract.;
u2022 SPRO --> SD -->Sales --> Sales Documents --> Sales Document Header --> Define Sales Document Types --> Field : Outline agreement message; from blank to u201CBu201D.
u2022 SPRO -->SD -->Sales --> Sales Documents --> Sales Document Header --> Maintain Sales Document Types for AFS --> Field : Outline agreement message; from blank to u201CAu201D

Creation of saleorder with reference to order using BAPI_SALESORDER_CREATE

Similar Messages

Maybe you are looking for