How to differentiate the Purch Orders created with reference to in table

Hi all
how to differentiate the Purch Orders which are created with reference to Purch requsitions, contract, manual by copying inforecord in the table EKKO/EKPO? Is there any Field Indicators?
Rgds
Ramesh

Hi Ramesh,
Go through EKPO there is a Table BANFN it will update when you create a PO with reference to PR
Do se11 > Table EKPO> CtrlShiftF10 > Assign any of PO no. in the EBELN > Execute > you will find BANFN table
it indicates Purchase Requisition Number. it will update when you create PO with reference to PR.
Regards,
Vraj

Similar Messages

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 stop the prodution order creating when the product is not valued?

Hi guyes:
How to stop the prodution order creating when the product is not valued using CO01?
I hope that when i create the production order,the system will check the product is valued or not,if not
the system will show an error or warning message!
How to config for this?
Thank you!

Dear Zhao Gang,
Check with this user Exits mentioned in this link,
Prevent Production Order from "Release" if there is no Cost Estimate
Re: User Exit at Production Order Release
Check and revert back.
Regards
Mangalraj.S

Error : Sales order 'create with Reference' to the contract

We have made a value contract. Now we are trying to make a Sales order 'create with Reference' to the contract.
when we do that, we am getting error 'copying material in any value contract item is not permitted'
Any help or directions would be greatly appreciated . We are on Ecc 6.0
Rohit

As of now my value contract has just one material. so i dont need assortment module settings. right?
in VTAA settings are as follows
Target type: OR
Source type: ZK1
there is only on item category
Target item category: TAN
Source item category: WKN
Copying requirement : 301
update doc flow : 2
pricing type : C
cont item copy mode : A
DataT am using 151,102,002
There are no schedule line.
Rohit
Edited by: rohit kumar on May 15, 2008 7:36 PM

Change of Sold to Party in Sales order created with Reference to Contract

Dear Gurus
I want to change the sold to party in Sales Order created with reference to contract.
When I create a Sales order with reference to contract the system copies all the partner functions- Sold to, Ship to, Bill to and Payer alongwith other data.
However Sold to is marked as "Grey" and not changable, rest of the partners can be changed.
There is no subsiquent document created with reference to this Sales Order.
Please advice.
Thanks a lot.
Regards
Raghu

Hi ,
Please follow the below mentioned step.
1) Create a partner function letts say Authorized SP .
2) Assign all the possible authorised SP (customer) in the contract.
3) When you create sales order with reff to Contract. Put the customer for whom you wish to create a sales order in release partner tab.
Hop this will resolve our problem
Regards,
Krishna O

Sales Order Created with reference to Contract - Exchange rate Issue

When Sales Order created with reference to contract VBKD fields KURSK and KURSK_DAT gets copied from contract and not redetrmined based on pricing date and Exchange rate type. I expected it to be determined based on pricing date is standard. What I am missing, should it be controlled by data transfers
If Document currency and condition currency are different it cause problems with incorrect condition values are calculated, as KOMP-KURSK are copied from VBKD-KURSK
Any help or directions would be greatly appreciated . We are on 4.7 ISOIL
Sincerely Julietta

Well,
and if we have the same issue, but we don't have OIL Version, but simple 4.6C, which solution has to be applied then?
Thank you
Standa

Add pricing condition within order created with reference to SPA

Hi,
I have a requirement wherein I need to add a $50 fine to order if the total order weight is below 75 kg.
Problem I am facing is with orders created with reference to SPA wherin pricing is not calculated but copied from SPA.
Please help me in solving this issue.
Also, Please let me know the pricing userexit / BADI for CRM wherein this can be coded.
Regards,
Willban
Edited by: willban_sap on Jul 21, 2010 11:43 AM

Hi Willban,
wonder wether you could use any weight dependent (net or gross) group condition with a scale. Delow 75 kg across all grouped items you would charge 50 $ and starting at 75 kg you would charge 0 $. As the scale base should get adjusted with the copy / create with reference step, I see no need for custom code.
Best Regards,
Michael

High level contract and orders created with reference

Dear All,
The client is an integrated flat steel manufacturer. They have entered into quantity contract with high level products like for example Hot rolled coils + Cold rolled coils + Heat Treated plates 5000 T per month. There is no clear cut quantity breakup of each product. On monthly basis customer releases purchase orders with exact grade and dimensions. The requirement is to capture contact for 5000T and create orders with reference to the contract with necessary completion rule. Since exact break up of the high level products is not known controlling of order quantity to 5000T will involve lot of manual intervention. I was thinking in the contract we have high level material "X with 5000T and orders created with reference with actual materials like Hot rolled coils, Cold rolled coils and exact dimension/grade mentioned. Is this possible to have different materials in contract and order with enhancement?
Any other idea of fulfilling the requirements is welcome.
Thanks,

Hi Ramesh,
Go through EKPO there is a Table BANFN it will update when you create a PO with reference to PR
Do se11 > Table EKPO> CtrlShiftF10 > Assign any of PO no. in the EBELN > Execute > you will find BANFN table
it indicates Purchase Requisition Number. it will update when you create PO with reference to PR.
Regards,
Vraj

Error while posting a sales order created with reference from contract for

Hi,
I am posting a sales document( Type: WA) created with reference from contract document( type wk2) for delivery. The item category in the sales order of the Item is WAN. On posting this document for delivery I am getting the error as "Item category WAN is not defined". Please help me out how to resolve this issue.
Thanks
Jayant

Hi Jayant,
I think its value contract releated error,
You suppose to check material item category group through T.code-MM02 into sales2 tab and maintain VCIT,
and do item category assignment through T.code- VOV4.
plz.maintain like that,
WK2 -          -VCIT-         -           - WAN(contract item category),
wk2 -          -        -VCTR-          - WAN((contract item category),
you should also maintain same against your standard Sales Document type and for Standard Item category into VOV4,
WA(standard docu.type) -VCIT-                             -                -TAN(your standard docu.type item category),
WA(standard docu.type) -         -VCTR(item usage)-              -TAN(your standard docu.type item category),

Sales Order CReated with Reference

Hi,
I created a sales order with reference to an existing order. I created delivery based on the new order that was created with reference. HOwever, if i try to get the sales order number of my delivery, the sales order that i am getting is the sales order number that was referenced. How will I retreived the new sales order number from VBFA?
Thanks,
Louisse

Hello,
         We can follow the below Procedure to get the Sales Order Number from VBFA Table.
1. Input the Delivery in VBELN field to get VBELV (Sales Order)
    Number with VBTYP_V = 'C' (Order).
2. Now, if the Sales Order which is fetched is the one which is
    referenced, then Input the Sales Order Number again in the
    VBFA Table into the Field VBELV and fetch the Sales Order
    Number (New) in the VBELN Field with VBTYP_N = 'C'.
3. You should be able to satisfy your requirement.
Hope it was clear.
Thanks and Regards,
Venkat Phani Prasad Konduri

Remove Header text from a sales order, created with reference to quotation

Hi all,
I have a sales order(in VA01) which is created with reference to quotation (in VA21).
If header text (Notes for logistics, Note for responsible person, Header text Doc & Declaration) in texts tab is maintained in the quotation they are getting copied in Sales Order which is NOT the requirement.
I need suggestions on how to disable the text that is getting copied.
Any pointers would be of great help.
Regards,
Vamsee Priya.

Hi Nilesh,
I created a routine in vofm and this solved my problem.
Now, I'm having a similar problem where I'm creating an Invoice(through transaction VF01) giving the delivery document number and document type (Invoice F2).
we are maintaining Header text in Order through which the above mentioned delivery document number is created and this header text should get copied in the Invoice.
For this, I went into Transaction VOTXN, from there selected billing header, from here kept a break point for the routine BEDINGUNG_PRUEFEN_001 through which the text will get copied.
Now, when I'm creating the Invoice this routine is getting executed, but still the text is not getting copied.
Any pointers on this would be of great help.
Also at the end of your previous mail, you are telling about SPRO - text assignment. Can you please let me know how to I should navigate to this text-assignment??
Thanks and Regards,
Vamsee Priya.

BAPI Sales order create with reference

Hi
I need to use BAPI to create sales order with reference to Quantity Contract. The line item material quantity would be less than or equal to quantity contract quantity.
Sales order needs to be created with new quantity.
Quantity contract quantity change needs to be maintained.
Document flow needs to be maintained.
Is any one aware if this is possible using BAPI_SALESORDER_CREATEFROMDAT2. If yes, how?
Any insights would be highly appreciated.

Hi Maninder,
The BAPI does not allow the Pricing Conditions to be sourced from the Contract. I debugged the BAPI and it uses a piece of code (don't recall which subroutine though) from SAPMV45A which is relevant for dialog processing where it reads from the VBAP and *VBAP structures. Well this structure is only populated when you are using the Front End transaction (VA41, VA42, etc). Because this structure is empty, pricing conditions do not flow across.
Here is a little prototype program I whipped up to test my method of creating a Sales order and then changing the Sales Order:
REPORT ypat_salesorder_create LINE-SIZE 256.
* This program will create a ZOC Sales Order with Reference to Contract
* 20000720 / 10. This will be done via BAPI. There are 2 BAPi calls,
* BAPI_SALESORDER_CREATEFROMDAT2 and BAPI_SALESORDER_CHANGE. We need to
* perform 2 BAPI calls as the BAPI to create the Sales Order does not
* bring across the Pricing Conditions properly. To get around this we
* create the Order with reference to the Contract, then we get the
* related Pricing Conditions from the COntract and then update the newly
* created Order.
* Constants
CONSTANTS: c_contract LIKE vbak-vbeln VALUE '0020000720',
           c_item      LIKE vbap-posnr VALUE '000010'.
* Structures
* Structure to hold BAPI Header
DATA: st_bapisdhd1   LIKE bapisdhd1.
* Internal Tables
* Sales Order Create BAPI Return Messages
DATA: tbl_return     TYPE STANDARD TABLE OF bapiret2
                     WITH HEADER LINE.
* Sales Order BAPI Line Item
DATA: tbl_bapisditm TYPE STANDARD TABLE OF bapisditm
                     WITH HEADER LINE.
* Sales Order BAPI Line Item
DATA: tbl_bapisditmx TYPE STANDARD TABLE OF bapisditmx
                     WITH HEADER LINE.
* Sales Order BAPI Pricing Conditions
DATA: tbl_bapicond   TYPE STANDARD TABLE OF bapicond
                     WITH HEADER LINE.
* Sales Order BAPI Partner Functions
DATA: tbl_bapiparnr TYPE STANDARD TABLE OF bapiparnr
                     WITH HEADER LINE.
* Sales Order BAPI Schedule Lines
DATA: tbl_bapischdl TYPE STANDARD TABLE OF bapischdl
                     WITH HEADER LINE.
* Sales Order BAPI Schedule Lines
DATA: tbl_bapischdlx TYPE STANDARD TABLE OF bapischdlx
                     WITH HEADER LINE.
* Sales Order BAPI Pricing Conditions
DATA: tbl_bapicondx    TYPE STANDARD TABLE OF bapicondx
                       WITH HEADER LINE.
* Customer Enhancement for VBAK, VBAP, VBEP
DATA: tbl_bapiparex    TYPE STANDARD TABLE OF bapiparex
                       WITH HEADER LINE.
* Table to hold BAPI Detail Conditions
DATA: tbl_bapisdcond   TYPE STANDARD TABLE OF bapisdcond
                       WITH HEADER LINE.
* Table to hold Return Messages from Sales Order Change BAPI
DATA: tbl_return_chg TYPE STANDARD TABLE OF bapiret2
                      WITH HEADER LINE.
* Variables
DATA: g_vbeln_created   LIKE vbak-vbeln,
      g_valid_contract TYPE c,
      g_cont_price_date TYPE d.
* Start of Selection
START-OF-SELECTION.
PERFORM validate_contract.
PERFORM create_sales_ord.
PERFORM update_sales_ord.
* End of Selection
END-OF-SELECTION.
PERFORM write_output_report.
* Subroutines
*&      Form create_sales_ord
*       Create the Sales Order
FORM create_sales_ord .
PERFORM populate_bapi_tables.
PERFORM call_create_sales_ord_bapi.
ENDFORM.                    " create_sales_ord
*&      Form populate_bapi_tables
*       Fill up the BAPI Tables
FORM populate_bapi_tables .
PERFORM populate_bapi_header.
PERFORM build_bapi_partners.
PERFORM build_bapi_items.
PERFORM build_bapi_sched_lines.
ENDFORM.                    " populate_bapi_tables
*&      Form populate_bapi_header
*       Build BAPI Header Details
FORM populate_bapi_header .
CLEAR st_bapisdhd1.
st_bapisdhd1-doc_type     = 'ZOC'.         "Order type
st_bapisdhd1-sales_org    = '026'.         "Sales Org
st_bapisdhd1-distr_chan   = '00'.          "Dist Channel
st_bapisdhd1-division     = '00'.          "Division
st_bapisdhd1-purch_no_c   = 'Cust Po No'. "Cust PO No
st_bapisdhd1-name         = 'Orderer'.     "Name of Orderer
st_bapisdhd1-ord_reason   = ''.            "Order Reason
st_bapisdhd1-sales_off    = '3001'.        "Sales Office
st_bapisdhd1-sales_grp    = '301'.         "Market Area
IF g_valid_contract = 'X'.
    st_bapisdhd1-price_date = g_cont_price_date.
ENDIF.
ENDFORM.                    " populate_bapi_header
*&      Form build_bapi_partners
*       Build BAPI Partner Functions
FORM build_bapi_partners .
CLEAR tbl_bapiparnr.
tbl_bapiparnr-partn_role   = 'AG'.
tbl_bapiparnr-partn_numb   = '0000100750'.
APPEND tbl_bapiparnr.
CLEAR tbl_bapiparnr.
tbl_bapiparnr-partn_role   = 'WE'.
tbl_bapiparnr-partn_numb   = '0000504472'.
APPEND tbl_bapiparnr.
ENDFORM.                    " build_bapi_partners
*&      Form build_bapi_items
*       Build The BAPI Line Items
FORM build_bapi_items .
DATA: l_matnr LIKE mara-matnr.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = '10000072'
    IMPORTING
      output = l_matnr.
CLEAR tbl_bapisditm.
tbl_bapisditm-itm_number = c_item.
IF g_valid_contract = 'X'.
    tbl_bapisditm-ref_doc     = c_contract.
    tbl_bapisditm-ref_doc_it = c_item.
    tbl_bapisditm-ref_doc_ca = 'G'.       "Contract
ENDIF.
tbl_bapisditm-material    = l_matnr.
tbl_bapisditm-plant       = '3012'.
tbl_bapisditm-target_qty = '5.000'.
tbl_bapisditm-target_qu   = 'M3'.
tbl_bapisditm-item_categ = 'ZZOC'.
tbl_bapisditm-sales_dist = '301'.
tbl_bapisditm-dlv_prio    = '02'.
tbl_bapisditm-prc_group5 = '080'.
tbl_bapisditm-cust_mat35 = 'kdmat'.
tbl_bapisditm-route       = 'TESYS'.
tbl_bapisditm-usage_ind   = 'CIV'.
APPEND tbl_bapisditm.
CLEAR tbl_bapisditmx.
tbl_bapisditmx-itm_number = c_item.
tbl_bapisditmx-ref_doc    = 'X'.
tbl_bapisditmx-ref_doc_it = 'X'.
tbl_bapisditmx-ref_doc_ca = 'X'.
tbl_bapisditmx-material   = 'X'.
tbl_bapisditmx-updateflag = 'I'.
tbl_bapisditmx-plant      = 'X'.
tbl_bapisditmx-target_qty = 'X'.
tbl_bapisditmx-target_qu = 'X'.
tbl_bapisditmx-item_categ = 'X'.
tbl_bapisditmx-sales_dist = 'X'.
tbl_bapisditmx-dlv_prio   = 'X'.
tbl_bapisditmx-prc_group5 = 'X'.
tbl_bapisditmx-cust_mat35 = 'X'.
tbl_bapisditmx-usage_ind = 'X'.
tbl_bapisditmx-route      = 'X'.
APPEND tbl_bapisditmx.
ENDFORM.                    " build_bapi_items
*&      Form build_bapi_sched_lines
*       Build the BAPI Schedule Lines
FORM build_bapi_sched_lines .
CLEAR tbl_bapischdl.
tbl_bapischdl-itm_number = c_item.
tbl_bapischdl-req_qty     = '1'.
tbl_bapischdl-req_date    = sy-datum.
APPEND tbl_bapischdl.
ENDFORM.                    " build_bapi_sched_lines
*&      Form build_bapi_conditions
*       Pull the BAPI Pricing Conditions from the Contract
FORM build_bapi_conditions .
LOOP AT tbl_bapisdcond.
    CLEAR tbl_bapicond.
    MOVE-CORRESPONDING tbl_bapisdcond TO tbl_bapicond.
    APPEND tbl_bapicond.
    CLEAR tbl_bapicondx.
    tbl_bapicondx-itm_number = tbl_bapicond-itm_number.
    tbl_bapicondx-cond_st_no = tbl_bapicond-cond_st_no.
    tbl_bapicondx-cond_count = tbl_bapicond-cond_count.
    tbl_bapicondx-cond_type = tbl_bapicond-cond_type.
    tbl_bapicondx-updateflag = 'I'.
    tbl_bapicondx-cond_value = 'X'.
    tbl_bapicondx-currency   = 'X'.
    tbl_bapicondx-cond_unit = 'X'.
    tbl_bapicondx-cond_p_unt = 'X'.
    tbl_bapicondx-varcond    = tbl_bapicond-varcond.
    APPEND tbl_bapicondx.
ENDLOOP.
ENDFORM.                    " build_bapi_conditions
*&      Form call_create_sales_ord_bapi
*       Call the Sales Order Create BAPI
FORM call_create_sales_ord_bapi .
CLEAR g_vbeln_created.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
      order_header_in    = st_bapisdhd1
    IMPORTING
      salesdocument      = g_vbeln_created
    TABLES
      return             = tbl_return
      order_items_in     = tbl_bapisditm
      order_items_inx    = tbl_bapisditmx
      order_partners     = tbl_bapiparnr
      order_schedules_in = tbl_bapischdl.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
ENDFORM.                    " call_create_sales_ord_bapi
*&      Form update_sales_ord
*       Update the newly created Sales Order with the Pricing Conditions
*       from the Contract
FORM update_sales_ord .
CHECK g_valid_contract EQ 'X'.
PERFORM get_contract_details.
PERFORM build_bapi_conditions.
PERFORM call_change_sales_ord_bapi.
ENDFORM.                    " update_sales_ord
*&      Form get_contract_details
*       Get Contract Details
FORM get_contract_details .
* Need to manually get the relevant Pricing Conditions as the BAPI
* BAPISDORDER_GETDETAILEDLIST causes problems when we call the BAPI
* BAPI_SALESORDER_CREATEFROMDAT2 and BAPI_SALESORDER_CHANGE (I think
* this is due to the fact that these BAPIs belong to the same Function
* Group and there must be some common structures that are not cleared
* causing us all sorts of grief when we try and call the next BAPI)
DATA: tbl_konv TYPE STANDARD TABLE OF konv WITH HEADER LINE.
DATA: tbl_komv TYPE STANDARD TABLE OF komv WITH HEADER LINE.
DATA: tbl_vbak TYPE STANDARD TABLE OF vbak WITH HEADER LINE.
* Pricing Condition Master
DATA: BEGIN OF tbl_t685a OCCURS 0,
          kschl     LIKE t685a-kschl,
          kaend_wrt LIKE t685a-kaend_wrt,
        END OF tbl_t685a.
SELECT *
         INTO TABLE tbl_vbak
         FROM vbak
         WHERE vbeln = c_contract.
READ TABLE tbl_vbak INDEX 1.
SELECT *
         INTO TABLE tbl_konv
         FROM konv
         WHERE knumv = tbl_vbak-knumv AND
               kposn = c_item.
CHECK sy-subrc EQ 0.
* We now need to make sure we only bring across the Condition Types that
* are EDITABLE. If we bring across non editable conditions (such as
* 'ZPR1') the Change Sales Order BAPI will fail
SELECT kschl kaend_wrt
         INTO TABLE tbl_t685a
         FROM t685a
         FOR ALL ENTRIES IN tbl_konv
         WHERE kappl     EQ 'V'             AND "Sales
               kschl     EQ tbl_konv-kschl AND
               kaend_wrt EQ 'X'             AND "Value is Editable
               kmanu     NE 'D'.                 "Process manually
* Prepare for Binary Search
SORT tbl_t685a BY kschl.
LOOP AT tbl_konv.
    READ TABLE tbl_t685a WITH KEY kschl = tbl_konv-kschl BINARY SEARCH.
    IF sy-subrc EQ 0.
      MOVE-CORRESPONDING tbl_konv TO tbl_komv.
      APPEND tbl_komv.
    ENDIF.
ENDLOOP.
CHECK NOT tbl_komv[] IS INITIAL.
* Map KOMV into the more BAPI friendly BAPISDCOND structure
CALL FUNCTION 'MAP_INT_TO_EXT_STRUCTURE'
    TABLES
      fxvbak        = tbl_vbak
      fxkomv        = tbl_komv
      fxbapikomv    = tbl_bapisdcond
    EXCEPTIONS
      entry_missing = 1
      OTHERS        = 2.
ENDFORM.                    " get_contract_details
*&      Form call_change_sales_ord_bapi
*       Call the Change Sales Order BAPI
FORM call_change_sales_ord_bapi .
DATA: st_head_chg      LIKE bapisdh1x,
        st_logic_switch TYPE bapisdls.
CHECK NOT g_vbeln_created IS INITIAL.
CHECK g_valid_contract EQ 'X'.
st_head_chg-updateflag     = 'U'.
st_logic_switch-cond_handl = 'X'.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
      salesdocument    = g_vbeln_created
      order_header_inx = st_head_chg
      logic_switch     = st_logic_switch
    TABLES
      return           = tbl_return_chg
      conditions_in    = tbl_bapicond
      conditions_inx   = tbl_bapicondx.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
ENDFORM.                    " call_change_sales_ord_bapi
*&      Form write_output_report
*       Produce Output Report
FORM write_output_report .
IF NOT g_vbeln_created IS INITIAL.
    WRITE:/ 'Success! Sales Order', g_vbeln_created, 'was created!'.
ELSE.
    WRITE:/ 'Failure! Sales Order was not created!'.
ENDIF.
SKIP.
WRITE:/ 'Sales Order Create Log'.
LOOP AT tbl_return.
    WRITE:/ tbl_return-type, tbl_return-id, tbl_return-number,
            tbl_return-message.
ENDLOOP.
SKIP.
WRITE:/ 'Sales Order Change Log'.
LOOP AT tbl_return_chg.
    WRITE:/ tbl_return_chg-type, tbl_return_chg-id,
            tbl_return_chg-number, tbl_return_chg-message.
ENDLOOP.
ENDFORM.                    " write_output_report
*&      Form validate_contract
*       Make sure that the Contract is Valid
FORM validate_contract .
DATA: l_gueen LIKE vbak-gueen,
        l_prsdt LIKE vbkd-prsdt.
SELECT SINGLE vbak~gueen vbkd~prsdt
         INTO (l_gueen, l_prsdt)
         FROM vbak
         INNER JOIN vbkd
         ON vbak~vbeln = vbkd~vbeln
         WHERE vbak~vbeln = c_contract AND
               vbkd~posnr = '000000'.
IF sy-datum LE l_gueen.
* Contract is valid! Set Order Price Date
    g_valid_contract = 'X'.
    g_cont_price_date = l_prsdt.
ENDIF.
ENDFORM.                    " validate_contract
Hope this helps.
Cheers,
Pat.

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

Need no document flow update for sales order create with reference

Dear All.
We would like to have the ability to create a sales order with reference to another sales order, and have the document flow of the sales order not updated.
Unlike the case of a standard create with reference where the documents are linked, in this case there is no relationship between the documents. The first document is just acting like a template for the remaining documents, to save time during order entry.
We have turned off update of document flow at the line item level.
But I don't see a way for us to turn this off at the header (document level). So wondering if there's another way to turn this off, or possibly through user-exit or VOFM requirement?
Has anyone else done this?
I think that CRM has this functionality, but we're still entering orders through ERP-SD.
Many Thanks!

Hello Colleague;
The issue you have reported is SAP standard. The checkbox "Update Document Flow" (V_TVCPAAP-UPFLU) controls document flow at item level. If this checkbox is set to blank, there will be no document flow at item level.
However, the document flow cannot be completely turned off - if the 'update document flow' indicator is blank, you will still see an entry in the document flow, but there will be no update to table VBFA (Sales Document Flow) and the document flow of the predecessor will not be updated at item level (no record in VBFA at item level).
The reason is that the system checks VBAP (Sales Document: Item Data) for fields VGBEL (Document number of the reference document) and VGPOS (Item number of the reference item) for values. You will always have document flow information on header and item level in the successor because it stores this information in table VBAP.
Related with this issue, you can find a Note 53383 for your review.
I hope it can clarify the case.
Regards
Ruy Castro

Order - create with reference - more information in Item selection ??

Hi all:
We are using "Copy control " from Quotation to Sales order..., it works OK.
But we are facing a problem now... The user used to copy all Quotation as 1 SO and now they need to choose the specific items.
So, they using VA01 -> Create with reference -> Item selection -> "Then Choose items"
But the screen only has information about "Item/Material No./Material description and Open quantiry"... not enought for user, they need more info like Plant, batch ... to choose the item.... any setting can make it??
I have tried "Table setting" and IMG but found nothing !!
I know we can copy all first and remove it, but is there any way we can choose them from "Item selection"...
Thanks..

Hi Amit
Thanks your answer and which enhancement do you recommand ??
if there is "easy" enhancement can do it, we might do it otherwise we will use "Copying requirements" only...
Thanks again

How to differentiate the Purch Orders created with reference to in table

Similar Messages

Maybe you are looking for