Copy with Reference

Does anyone know why this happens or where it is controlled? When I create a sales order using the Create with Reference button on the Initial Screen, my order uses the pricing procedure of the copied document. But when I create a sales order using the Create with Reference found in the Sales Document drop down menu on the order Overview Header screen, my order uses the pricing procedure assigned to the new order type. Is there somewhere I can make them both work the same way? Big points to anyone who knows this answer. Laurie

HI Laurie,
The explanation is as below
first when you copy from the reference order or quotation, the pricing is also copies from the reference document.
the settinngs that determine this are set in VTAA t code and the pricing option at item level there.
when you add a document from the second option of header and then reference, the system has already determined the
pricing procedure and it only adds the incremental items to the exisitng sales order
for the scenario described , i assume that you have different pricing procedures set for both the documents
hope this helps
Thanks
akasha

Similar Messages

BAPI SALES ORDER & Copy with reference

Hello,
I'm creating sales order copied with reference to an invoice. My problem is that the data item is empty. When I create the sales order manually and use the option 'Create with reference' and choose an invoice, the sales order is created with all data item. I don't know how I can get to copy the data item from the invoice in the new sales order. The code that I'm using is the following:
DATA: order_header_in      LIKE bapisdhd1,
      order_partners       LIKE bapiparnr OCCURS 0 WITH HEADER LINE,
      order_text           LIKE bapisdtext OCCURS 0 WITH HEADER LINE,
      order_header_inx     LIKE bapisdhd1x,
      order_item_in        LIKE bapisditm OCCURS 0 WITH HEADER LINE,
      order_schedules_in   LIKE bapischdl OCCURS 0 WITH HEADER LINE,
      order_conditions_in LIKE bapicond OCCURS 0 WITH HEADER LINE,
      extensionin          LIKE bapiparex OCCURS 0 WITH HEADER LINE,
      partneraddresses     LIKE bapiaddr1 OCCURS 0 WITH HEADER LINE,
      order_cfgs_ref       like BAPICUCFG occurs 0 with header line.
DATA: salesdocument LIKE bapivbeln-vbeln.
DATA: return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
order_header_in-doc_type   = 'ZA09'.
order_header_in-sales_org = '1700'.
order_header_in-distr_chan = '01'.
order_header_in-division   = '01'.
order_header_in-BILL_DATE   = '20060701'.
order_header_in-ref_doc    = '0900000019'.
order_header_in-refdoc_cat = 'M'.
*order_header_in-REF_DOC_L_LONG = '0900000019'.
order_header_in-purch_no_c ='prueba'.
*order_header_in-ord_reason = '003'.
*order_header_in-pmnttrms   = '0002'.
*order_header_in-sales_off = '2800'.
order_header_in-ref_doc_l = 'FACTURA ES'.
*order_header_in-fix_val_dy = '20060701'.
*order_header_in-currency   = 'USD'.
*order_header_in-exchg_rate = '1.2'.
order_partners-partn_role = 'AG'.
order_partners-partn_numb = '0000000001'.
order_partners-langu      = 'EN'.
order_partners-name       = 'El corte aleman'.
order_partners-country = 'ES'.
APPEND order_partners.
order_partners-partn_role = 'RE'.
order_partners-partn_numb = 'ARR000'.
order_partners-addr_link = '0000030044'.
APPEND order_partners.
CALL FUNCTION 'ADDR_GET_COMPLETE_ALL_TYPES'
EXPORTING
    addrnumber                 = order_partners-addr_link
PERSNUMBER                 =
    address_object_type        = '1'
IV_CURRENT_COMM_DATA       = 'X'
IMPORTING
ADDR1_COMPLETE             =
ADDR2_COMPLETE             =
ADDR3_COMPLETE             =
   ADDR1_COMPLETE_BAPI        = partneraddresses
ADDR2_COMPLETE_BAPI        =
ADDR3_COMPLETE_BAPI        =
EXCEPTIONS
PARAMETER_ERROR            = 1
ADDRESS_NOT_EXIST          = 2
PERSON_NOT_EXIST           = 3
INTERNAL_ERROR             = 4
OTHERS                     = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
data: vl_texto(40) value 'NUEVOOOOO'.
partneraddresses-name    = vl_texto. clear vl_texto.
partneraddresses-name_2 = vl_texto.
partneraddresses-name_3 = vl_texto.
partneraddresses-name_4 = vl_texto.
partneraddresses-langu   = 'E'.
APPEND partneraddresses.
DATA: vl_cantidad LIKE bapisditm-target_qty.
vl_cantidad = 1.
order_item_in-itm_number = 10.
order_item_in-material = 'HONORARIOS'.
order_item_in-ref_doc = '0900000019'.
order_item_in-ref_doc_it = 10.
order_item_in-ref_doc_ca = 'M'.
APPEND order_item_in.
order_schedules_in-itm_number = 10.
order_schedules_in-req_qty = vl_cantidad.
APPEND order_schedules_in.
order_text-text_id = 'Z001'.
order_text-ITM_NUMBER = ''.
order_text-langu = 'EN'.
order_text-text_line = 'Hola, CARACOLAcola'.
APPEND order_text.
order_text-text_id = 'Z001'.
order_text-langu = 'EN'.
order_text-text_line = 'Adios caracol'.
APPEND order_text.
order_text-itm_number = '000010'.
order_text-text_id = '0001'.
order_text-langu = 'EN'.
order_text-text_line = 'Hola, POSICIÓN'.
APPEND order_text.
extensionin-structure = 'BAPE_VBAK'.
extensionin-valuepart1 = '          BCL 7'.
APPEND extensionin.
order_cfgs_ref-posex = '10'.
order_cfgs_ref-config_id = '10'.
order_cfgs_ref-root_id = '00000001'.
append order_cfgs_ref.
CALL FUNCTION 'ZBAPI_SALESORDER_CREATEFROMDT2'
EXPORTING
   SALESDOCUMENTIN               = salesdocument
    order_header_in               = order_header_in
   ORDER_HEADER_INX              = order_header_inx
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
IMPORTING
   salesdocument                 = salesdocument
TABLES
    return                        = return
    order_items_in                = order_item_in
ORDER_ITEMS_INX               =
    order_partners                = order_partners
    order_schedules_in            = order_schedules_in
ORDER_SCHEDULES_INX           =
    order_conditions_in           = order_conditions_in
ORDER_CONDITIONS_INX          =
    ORDER_CFGS_REF                = 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_text
ORDER_KEYS                    =
   extensionin                   = extensionin
    partneraddresses              = partneraddresses
PERFORM report TABLES return.
*DATA: salesdocument LIKE bapivbeln-vbeln.
*DATA: return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
*refresh return.
*CALL FUNCTION 'BAPI_SALESDOCUMENT_COPY'
EXPORTING
   salesdocument          = '0400000191'
   documenttype           = 'ZA04'
TESTRUN                = ' '
IMPORTING
   SALESDOCUMENT_EX       = salesdocument
TABLES
   RETURN                 = return
*PERFORM report TABLES return.
*write: / salesdocument.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT          =
IMPORTING
RETURN        =
*&      Form report
      text
     -->P_MENSAJE text
FORM report TABLES   p_mensaje STRUCTURE bapiret2.
DATA: vl_mensaje TYPE string.
LOOP AT return.
    CLEAR vl_mensaje.
    MESSAGE ID     return-id
            TYPE   return-type
            NUMBER return-number
            INTO   vl_mensaje
            WITH   return-message_v1
                   return-message_v2
                   return-message_v3
                   return-message_v4.
    WRITE: / vl_mensaje.
ENDLOOP.
ENDFORM.                    " report

Hi Manuel,
There are some function modules which is there to copy the order details. I am not sure about the function module name. But you can search in SE37. But bapi for creating the sales order does not have the functionality of copying the data from one document to another document.
You can try using this function module.
BAPI_SALESDOCUMENT_COPY
Data will be copied based on the copy control routines that is set between the two document types.
Thanks,
Arun

Copy with reference to Customer Master

Hi experts,
If the user creates customer master(XD01) with reference to another customer master then system should not copy all the fields say Name and contact number. How can I restrict this in SAP.
Can any body helps???
Thanks!!!
Poorna

Hi.
Normally when we copy existing customer to a new customer we use XD01 with reference and we don't select the items we don't want to copy or we delete the value when we are copying.
But if you want user to have a feature through which when ever they create a new customer using the existing customer they should not copy the recon a/c for Ex, than you have to create a Z transaction by copying the orignial XD01 and have your restrictions coded there..
Regards

Order should be copied with reference to other order

Hi Friends,
We have two order types zext and zexm. Zext should be always created with reference to zexm. we done this through copy controls.Both are sales orders.Now our requirement is
suppose we done a sales order 100001000 of type zexm. untill it is delivery done ie pgi has been done zext is not allowed to be copied from zexm. so please tell me how to do this.
Thank you so much for all the replies.

Hello,
Yes.... this can'e be achieved through any config setting, but can be achieved through the cupying requirements. In the copy control of sales documents to sales documents you need to maintian a requirement for the same. Talk to your ABAP consultant with a detailed requirement, he may be able to help you.
Prase

Req Deliv. Date required on order create VA01 Copy with Reference to Quote

When creating an order with reference to a quote, the screen allows Req Deliv Date entry. I would like to make this field mandatory on the window 'Create with Reference'. Program is SAPLV45C and the screen is not certain: could be 0100, 0301, 0302, 0303, 0900.
Have been looking at maintenance via SE51, but not sure if any of the element characteristics translate into 'required' so user is unable to click "Copy" if the date is without a value.
Thank you.

It is possible by changing the SAP standard.
You can change the special attirbutes (Tick the checkbox in Req. field) in elements list of each screen which you have mentioned through SE51 transcation
Regards,
Udayasankar Rajagopalan

Error while copy with reference of quotation to Sales Order

Dear All
I am creating the sales order with reference to quotation . while , doing so , I get an error of
Customer not maintained in Distribution channel - 'D1' .
The Quotaion is having following structure
Sales Organisation -- AAAA
Distribution Channel - S7
Division - D3
But while copy the error erupts notifying to create the customer master for division 'D1' . If created of division D1 then the sales order is created with reference of quotation.
Kindly guide.
AVS

Perhaps the configuration settings have been changed (to make D1 the reference division for D3 for master data ) since the quotation was originally created.

Sales order create/change line item with reference to contract - Open quantity not getting deducted for copied line item from the contract

Hi friends,
Please provide some valuable inputs for the following scenario:
When a sales order line item is created(VA01) or changed(VA02) with reference to a Contract the open quantity is deducted in the contract which is a standard functionality. If the referenced line item is copied (custom enhancement to copy line item), then for the copied line item the open quantity is not getting deducted instead ATP quantity i.e. Available-to-promise is deducted.
Any inputs on how we can fix this functionality i.e. deduct the open quantity from the contract for the copied line item?
P.S. : Custom enhancement to copy line item is working fine, but open quantity is not getting deducted if the copied line item was referenced to a contract.
Thanks,
Sandeep
Message was edited by: sandeep

Sandeep,
Yes, that was my original interpretation. I was having a hard time believing that someone would ask such a question.
I guess, then, that you already know that you will have to add this logic to your enhancement. You should create your specifications and hand them off to a developer; ideally the one who created this enhanced solution in the first place.
I do not provide advice in these forums about details of enhanced solutions. Perhaps one of the other members will be more willing to do your work for you.
Best Regards,
DB49

COPY CONTROL: SALES ORDER WITH REFERENCE TO QUOTATION

Hi.
We are creating a sales orders with reference to a quotation. When copying, we'd like to be able to include another new position type in the sales orders.
For example:
QUOTATION:
POSITION 10: TYPE ZTAB
SALES ORDERS:
POSITION 10: TYPE ZTAB
POSITION 20: TYPE IRSS.
Where could we place this change?. We suppose when saving the sales orders. Does anybody know how could we make this change?.
Thank you very much!.
Raú

What do you mean by position type?
Please use the language used by SAP so that it could be easily understood.
What is ZTAB & IRSS. Are they materials?
Regarding copying, this is a brief theory
In copy control, you define control data for the document flow of sales documents.
You can specify for a particular sales document type, which document type is to be assigned to copied reference documents, and which item categories or schedule line categories are to be copied.
You must also make specifications for copying requirements and data transfer, as well as quantity and value updates in document flow.
In precise, you are telling the system what data to copy from QT to sales order. It copies data from Quotation order type to Standard order type basing on settings you indicated in copying control.
System won't do anything more than copying from preceding documents and it would transfer data based on copying rules in copy control.

Copy Sales Order with reference to a Contract

Hello,
how can I create a copy of a sales order referred to a contract mantaining the reference?
I have an order referred to a contract; I would like to create a new order in copy ( va01 - create with Reference) maintaining the relationship to the contract.
Thank to all,
Antonio

Hi,
You can create a new order by referring to a contract by clicking on "Create with reference".
Click on Contract and enter the contract number here.You can change teh requested delivery date manually.
Click on Copy.
Before this,make sure that the copy controls have been mainatined for these two document types.
Regards,
Krishna.
Note:Please search in the forum before posting basic questions.

Create sales order (return) with reference - PO number not copied

Hello all,
I have a question regarding creating a sales order (return, VA01) with the option "create with reference" where a sales order number can be added as reference.
The system will copy values from the sales order into the return document like the item, the sold-to-party etc.
The PO Number (customer PO number) is not being copied in our system, so I was wondering if there is a way to tell the system to copy the PO number from the sales order?
Thanks,
Anne

Hi,
In the transaction code VTAA, select the target and source document types (return order <- sales order) and click on the details button. Check the data transfer routine (the first one for VBAK) assigned here. You may need to clone this routine (in transaction VOFM -> Data transfers -> orders) and create a new routine to add field VBAK-BSTNK into it.
Check with an ABAP'er for further details.
Regards,

Copy the Purchase order # to the Sales order created with reference

Generally if you create a new sales order with reference to a pre-existing sales-order, then the PO# does not get copied.
What would you have to do in-order to get the PO# copied into the new sales order ?
Thanks

Dear Noel,
As per the standard it will not get copy if you want you need to take help from the technical people (ABAPers) they may able tohelp you on that.
I hope it will help you
Regards,
Murali.

How to implement a Copy or Create with Reference scenario

For business objects, you might want to implement a Copy or Create with Reference scenario. The following procedure describes the UI configuration that you need if you want to place a copy button (in our example on an OWL) that starts a quick activity floorplan (on the same BO = Copy, or a different BO = Create with Reference). Pre-requisie in the target BO: The target BO requires a BO element SourceBOID and a Copy action that reads the SourceBO by SourceBOID by query, and copies the elements from the source to the target BO.
The UI configuration in the target floor plan is:
1. Open the QAF floor plan of the target BO (target floor plan).
2. In the DataModel view of the target floor plan, select the Root entry and select Add Data Field from the context menu. Rename the created data element to OBN_OriginBOID.
3. Choose the Controller tap, and select INPORTS and choose ADD INPORT from the context menu. A new in-port is created. Rename the in-port, for example to Copy.
4. In the in-port maintenance form, activate the check box OBN INPORT.
5. Select the namespace of your solution and the target business object.
6. In the input field SELECT OPERATION enter Copy. A new select operation is created. The combination of business object name (including namespace), business object node and operation identifies the in-port and therefore the related floor plan as navigation target.
7. Select the port type package /SAP_BYD_UI/SystemPortTypes.PTP.uicomponent.
8. In the PARAMETERS section of the form, click the ADD button. Maintain the binding of the created parameter to /Root/OBN_OriginBOID. Based on this configuration, the system will transfer the parameter of the in-port to the element in the data model when the OBN is executed.
9. In the Properties view, select the drop-down list box of the property EVENTS u2022 ONFIRE. Scroll down and select the entry u2026 NEW EVENT HANDLER u2026. The system starts the maintenance window for event handlers. Rename the event handler to CopyIn.
10. In the OPERATIONS table of the maintenance window for event handlers, select type: BUSINESS OBJECT OPERATION. In the form below the table select the value CREATE for the input field BUSINESS OBJECT OPERATION TYPE. This operation will create a BO instance in the backend when the OBN is executed.
11. In the OPERATIONS table, create a new operation of type: DATAOPERATION. In the configuration of the data operation, select the operation type ASSIGN, source expression /Root/OBN_OriginBOID and target expression /Root/<BO>/OriginBOID.
12. Create a third operation of type: BUSINESS OBJECT ACTION. Select the Copy action of the target business object and click the BIND button. Note: This action enforces another roundtrip to the backend. The Copy action must be implemented so that it will read the origin BO and copy selected data from the origin to the newly created object.
13. Test the changes in the preview. If no error message is issued, save and activate the floor plan.
The following procedure describes the configuration in the source floor plan (e.g. OWL floorplan ):
1. Open the Source BO OWL floor plan (source floor plan).
2. In the Designer view, place cursor the on the toolbar area and select ADD u2022 APPLICATION-SPECIFIC BUTTON u2022 MY BUTTON from a context menu. Rename the new button to Copy.
3. In the Properties view, select the drop-down list box of the property MENU INFORMATION u2022 NAVIGATION. The system launches the maintenance window for OBN configuration.
4. Select the in-port of the target floor plan by selecting the target business object (with namespace and name) the target business object node and the target operation, and the operation Copy.
5. Choose the navigation style NEWWINDOW.
6. Close the OBN configuration maintenance window by clicking the OK button. The system creates the OBN configuration, an out-port, that is used by the OBN configuration, and an event handler that uses the out-port and that is assigned to the button (see Properties view, EVENTS u2022 ONFIRE).
7. Go to the Controller view and rename the OBN configuration to Copy, the new out port to Copy and the new event handler to CopyOut.
8. Check that the event handler CopyOut fires the out-port Copy.
9. In the Parameters section of the out-port maintenance form, click the ADD button. Maintain the binding of the created parameter as /Root/<BO>/<BO>ID. Based on this configuration, the system will transfer the identifier of the selected source BO to the out-port data structure when the OBN is executed.
10. In the Operations table, select type: FIREOUTPORT. In the form below the table select the out-port CopyOut.
11. Test the changes in the preview. If no error message is issued, save and activate the floor plan.

Hi Dries-
There are no pre-packaged solutions with BADIs since they are, by definition, custom development. If that's the path you need to go down then consider the following high level alternatives:
Incorporate custom code into the BPC Write Back BADI. You can restrict the execution of the BADI using filters on the BADI definition, so that the BADI execution only occurs when a data manager package is called, and only for some defined combination of applications/appsets. Utilized the standard copy/move functions delivered in Data Manager. When the BADI is called, interrogate each record being processed (table CT_ARRAY) and determine if the record has a value you want to process (i.e. save to the target application). Skip any record that has a zero value.
Another alternative is to develop the BADI as custom logic. Data Manager parameters can be picked up in Script Logic and the values can be sent to the BADI by adding parameters. Please see an example of parmater use in the "How To" document for Destination App at:
[EPM How To Guides|https://wiki.sdn.sap.com/wiki/display/BPX/Enterprise%20Performance%20Management%20%28EPM%29%20How-to%20Guides] > "How-to Desitnation App"
Regards,
Sheldon

KE28 with" Copy Characteristic Value with Reference Data" doesn't work

Hi experts:
We need to make a top-down setting the processing option 'Copy Characteristic Value with Reference Data'. We have the following source data:
Customer Business Unit Value field.
6        #              100
On the other hand, we have plan data as reference data:
Customer Business Unit Value field.
       A              40
       C              40
       D              20
We need to run a top-down to distribute from client to Business Unit but copying client of reference data. Then, we set 'Copy Characteristic Value with Reference Data' and, in the selection criteria we set '*' for customer.
After running, the result is that the system can find 1 sender and 3 receivers. It is exactly what we are expecting. However, program doesn't make individual items and anything is distributed.
We have found notes 1086282 and 1273924 but the result is the same after implementing these notes.
Thanks in advance for your help.
Best regards
Jose

There are some restrictions on the XML Schema format that you can report off of in Crystal Reports.
If you're using the ODBC XML driver, you may find this of relevance:
[http://resources.businessobjects.com/support/communitycs/TechnicalPapers/cr_xml_data_sources.pdf|http://resources.businessobjects.com/support/communitycs/TechnicalPapers/cr_xml_data_sources.pdf]
and if you're using the native XML driver, the following gives a guide for the accepted formats:
[http://resources.businessobjects.com/support/communitycs/TechnicalPapers/cr_xi_native_xml_driver.pdf|http://resources.businessobjects.com/support/communitycs/TechnicalPapers/cr_xi_native_xml_driver.pdf]
Sincerely,
Ted Ueda

Condition Values not being copied when creating sales order with reference

hi experts
i am copy a sales order with reference in va01 , when i copy the order it status is shown as incomplete beacue the condition values in some condition type sis zero, whereas if i delete amount for some condition type and re-eneter it the condition values for all conditon types appears ...
in all after copying order i go to condition at item level some codition values are zero but if erase amount for any condition type and then re enter it value comes for all condition types

Hi Sunny,
Maintain some value against that condition type in VK11.
This must solve your question. Please set to resolved if it solves your doubt.
Regards
Abhii....

Create internal order with reference - Do not copy distribution rule group

Hi,
I'm creating an internal order with reference to another order through tcode KO01. When i will display the new internal order, i already have distribuion rule group that was copied from the reference order. To delete the incorrect distribution rule group i execute tcode KO02, however this information do not appear in tcode KO02.
What should be done to delete this settlement rule? I do not want to copy the settlement rules from the old internal order.
Thanks in advance.
Regards,
Ana Fernandes

Hi.
'What should be done in order to do not copy this information when i create the internal order with reference?'
in tcode kot2_opa do not maintain Settlement profile for Order category 3
Also go to KOM2 and delete Settlement rule for order, from which you copying.
'in table COBRB i can see the information however i can not delete it. The validy period is empty.'-in su53 check authority

Copy with Reference

Similar Messages

Maybe you are looking for