Create with reference where original document is incomplete

Hi Guys
We use variant configuration as part of our sales order process. Within the VC we have 'discontinued' validation i.e. a component of the configuration may be discontinued and therefore unavailable. In this case, we would want to lock the configuration, reject the order item and create a new order item for a different component. We do not wish to delete the order item because of the effect this has on BI sales reporting.
However, if we later wish to create another document (such as a FOC replacement) with reference to this document we receive an error message to the effect that the document being referenced is incomplete and cannot be used as a reference.
Does anyone know of a way of being able to copy complete items only during create with reference or being able to set the status of an incomplete ('being processed') item to complete.

"Incomplete" and "being processed" are two different things. If document is "incomplete", there are some fields that are required and must be filled in before the document may be processed any further. As correctly pointed out above, such fields will appear in the incompletion log.
There is no way to work around the incompletion procedure. If you need to make the field required only in certain situations, you might want to take it out of the incompletion procedure and add a user exit instead.
If an order is displayed as "being processed", this means that one of the statuses (see Status tab on header and item level) is "partially processed". Normally setting the rejection reason updates the overall item's status (not to be confused with the header's status) to "complete", but I've heard of some cases when for some reason this does not happen. Unfortunately, I don't recall if there was any solution.
Hope this helps.

Similar Messages

Condition types doubling/tripling/...when sales documents created with reference to other documents

Hi,
When I create a sales order with reference to a Quote, the pricing condition types are duplicating. Same is happening when subsequent documents like Billing, credit memo request and credit memo are created. Particularly, the condition types are doubled/tripled/.... in the subsequent documents. Because of this, pricing net value is calculated wrong. For example, freight charges getting added twice. I searched the forum and found similar issue was discussed at Condition types - Doubling UP raised by forum member Sridhar Vijjhalwar, however there is no solution added in it.
Has any other member came across this issue and resolved?
I have checked the access sequence and exclusive indicators are checked. Copy controls are also checked, looked good and I tested by adding copying type D/G. Checked OSS note also and found one OSS note 1459807 - Invoice has missing/incorrect conditions when created from a sales order.
but it is not solving the problem either. Issue also elevated to SAP for their investigation. Our system is SAP ECC 6.0 - EHP6.
Quote Pricing:
Sales order Pricing:
I appreciate any pointers to resolve the issue.
Regards,

what was the scenario, and how did you replicate?
It is a configuration for a new project (France country), however we found that the same issue popping up for existing business processes also. As for replicating, we just tried the same procedures, the issue is found in subsequent documents.
If you have observed one notable thing is - all the condition types which duplicated were Z Conditions, and the standard conditions were never duplicated at least in my case.
In our case even standard condition types like MWST, SKTO, GRWR, VPRS also shows duplicating.
if you can throw about the business process?
As you have mentioned order created with reference to quote was only the straight forward scenario?
I tested other scenario also, like creating a sales order, then delivery and then billing. In this case in billing document, the condition types are duplicating. If I create a credit memo request against the billing document, then it further duplicating.
I am not sure what is causing this. I initially thought it may be copy control settings pertaining to the new project, however other business documents also has the same issue. Other business are using different document types.
Thanks for your follow-up.
Regards,

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

Credit memo to be created with reference to return delivery

Dear Gurus,
We have a requirement for mapping return process
Credit memo to be created with reference to return delivery (instead of with reference to return order)
Following issue faced in mapping the same:
Billing document No. 1234 dated 25.03.2010 where there is 4% VAT.
when we are creating return order with reference to billing document 1234
4% VAT is calculated since the Service Rendered date is 25.03.2010 (Copied form Billing document)
return delivery is created today 08.04.2010. (VAT revised to 5%)
when credit memo is created with reference to delivery document
VAT is calculated 5% which is applicable from 01.04.2010
since the service rendered date is appearing in billing document
08.04.2010 (the date of Post Goods Receipt).
The VAT should be actually 4% in Credit Memo.
regards,
Rajesh T

In the copy controls from delivery to Invoice, at the item level try to use pricing type C and Pricing source Blank ( Blank is order).
If it doesnt work , then you might have to go for a requirement routine for this Tax , based on the document category that is being processed, read the tax from the originating order.Assign the routine to tax condition in the pricing procedure.
Regards
Sai

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

Enable - Create With Reference in Sales order

Hi All,
I want to enable - Create With Reference in Sales order
We have 1 billing doc type YX1 to be used as reference for a sales order type ZX3
How to enable Create with reference from Sales Document type YX1 to Sales Document type ZX3.
Currently, I am getting error 'Copying from sales document type YX1 to ZX3 is not supported'.
Please let me know the steps to be followed.
Thank you!
Regards,
Shanu Jain

Hi,
The error clearly suggests that there is no copy control maintained b/w invoice YX1 and sales order type ZX3. You need to maintain that in SPRO > Sales and Distribution > Sales Documents > Copy control for sales documents. (You may check the correct node here). Here, you select the billing document to sales document.
Check for source and destination. You can take the source as F2 and CR (if ZX3 is a credit Memo request) as Destination document. You can copy the same and change the source and destination as YX1 as source and ZX3 as destination. Then, at the item level, if you have a new item category you can specify it as the 'Proposed Item Category'. Save it.
Now try to create the sales document ZX3 w.r.t YX1... It should work.
Hope this helps
Thanks
Mukund S

With reference to which document Delivery is created in Sub contract

Hi Friends
With Reference to which document delivery document is created in subcontract process .
through which T code I can see this reference document .
Suppose , there are 10 quantity in delivery document , where can I see this 10 numbers are from in delivery document .
In delivery ,in subcontract process , from which document , delivery quantities are copied from . And what should I do in order to avoid over delivery in subcontract process .
Pala

Hi,
Delivery is created with reference to Purchase order for subcontracting, to view the delivery check in purchase order history it displays the delivery double click on the delivery.Check in VL02N.
Delivery quantity are copied from Purchase order,
To avoid over delivery in subcontract process in material master purchasing view there field called purchase value key which controls this.
Regards
Ravi Shankar.

Creating sales order document with reference to billing document

I have to create sales order with reference to existing billing document. I have tried to following bapis.
1. BAPI_SALESORDER_CREATEed
I have successfully created document with following details.
-->ORDER_HEADER_IN:
DOC_TYPE = ZRK
SALES_ORG = 3000
DISTR_CHAN = 00
DIVISION = 00
ORD_REASON = 100
SD_DOC_CAT = L
CURRENCY = EUR
REF_DOC = 100000028
REF_DOC_CA = M
-->ORDER_ITEMS_IN:
ITM_NUMBER = 000010
MATERIAL = 701791
TARGET_QTY = 0000000001000
CURRENCY = EUR
REF_DOC = 100000028
REF_DOC_CA = M
-->ORDER_PARTNERS:
PARTN_ROLE = SP
PARTN_NUMB = W12001
COUNTRY = NL
by providing this input i am able to create the document but it is not picking up the net value. so i have passed some extra paramters in ORDER_ITEMS_IN
COND_TYPE = PNET
COND_VALUE = 14,56
COND_D_UNT = PC.
folowing error is occured: Condition PNET is missing in pricing procedure A V Z0000.
is it something related to configuration problem?
2.BAPI_SALESORDER_CREATEFROMDAT1 or BAPI_SALESORDER_CREATEFROMDAT2
I have used same test data that is used for BAPI_SALESORDER_CREATEFROMDATA (where in i coudl succefully create doc). but here i encounterd following error.
Unpermitted combination of business object BUS2032 and sales doc. category L.
When i created manually using transaction : VA01
I could do the same by passing following inputs:
DOC_TYPE = ZRK
SALES_ORG = 3000
DISTR_CHAN = 00
DIVISION = 00
Reference document number.
Please suggest me right way of approach.

Hi,
In SAP, when the sub-sequent document is existing , we can not cancel the preceeding document. Therefore if you want to cancel the billing document you need to calcel the documents which are created with reference to that.
Check and confirm.
Regards,
Ravi Duggirala

Create Sales Order With Reference to Billing Document Using BAPI_SALESORDER

Hi,
How can i create a sales order With Reference to Billing Document Using BAPI_SALESORDER_CREATEFROMDAT2?
Thanks in advance,
Alejandro.

I have to create sales order with reference to existing billing document. I have tried to following bapis.
1. BAPI_SALESORDER_CREATEed
I have successfully created document with following details.
-->ORDER_HEADER_IN:
DOC_TYPE =                  ZRK
SALES_ORG =              3000
DISTR_CHAN   =            00
DIVISION =                    00
ORD_REASON =            100
SD_DOC_CAT   =          L
CURRENCY       =         EUR
REF_DOC          =         100000028
REF_DOC_CA    =         M
-->ORDER_ITEMS_IN:
ITM_NUMBER    =           000010
MATERIAL          =          701791
TARGET_QTY     =          0000000001000
CURRENCY        =          EUR
REF_DOC           =          100000028
REF_DOC_CA     =          M
-->ORDER_PARTNERS:
PARTN_ROLE      =          SP
PARTN_NUMB      =         W12001
COUNTRY             =         NL
by providing this input i am able to create the document but it is not picking up the net value. so i have passed some extra paramters in ORDER_ITEMS_IN
COND_TYPE          =        PNET
COND_VALUE        =        14,56
COND_D_UNT        =         PC.
folowing error is occured: Condition PNET is missing in pricing procedure A V Z0000.
is it something related to configuration problem?
2.BAPI_SALESORDER_CREATEFROMDAT1 or BAPI_SALESORDER_CREATEFROMDAT2
I have used same test data that is used for BAPI_SALESORDER_CREATEFROMDATA (where in i coudl succefully create doc). but here i encounterd following error.
Unpermitted combination of business object BUS2032 and sales doc. category L.

Create Return PO using ME21N with reference to Original Purchase Order

Dear Experts,
Does anyone knows how to create Return POs with reference to Original Purchase Order using ME21N. The Purchasing Department will be initiating the Stock Return to Vendor so we don't want to use MB01, 161 Movement Type to create the return PO. Can anyone help.
Thanks.

Hi,
It is not possible to create a Return PO w.r.t. the original PO. Even if you will copy, it will just copy the details from PO but not store the reference of original PO in return PO.
Better instead of creating a new return PO, add a separate line item in the orginal PO by marking it as "Return" and perform all the subsequent transactions. This will provide the better traking and reporting. But this may affect your release strategy (need to be tested).

BAPI Sales Order create with reference Invoice document

Hi
I am using BAPI ''SD_SALESDOCUMENT_CREATE'' to create debit memo request with reference Invoice document.
First time its successfully created with reference Invoice.When i am going to create 2nd time debit memo request with same reference Invoice and item
no its giving following error.
      Reference quantity:
10 EA (total referenced:
40 EA)
       Error in SALES_ITEM_IN 000010
       Condition ZSLS is not allowed as header condition
       Sales document was not changed
    Please help any one to resolved this issue.
   Regards
   Shyam

SD_SALESDOCUMENT_CREATE is not a BAPI. Is there any specific reason you're using this FM when the actual BAPI exists?
ZSLS is a custom condition. There might as well be some user exit that attempts to add it [possibly incorrectly], how would we know this on SCN? There is enough information in the error message to troubleshoot on your own, it seems. What kind of analysis have you done before posting on SCN?

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.

POs created with reference to PRs

Dear All
I want PR item valuation price is to be copied in to the PO item as net price, when this PO item is being created with reference to a PR item.
This is required for both materials PR items and Service PR items
Presently for material PRs, system is coping the prices from material master, whereas for services no prices are copied as I am not following any service master.
I want prices directly from PR item. Is this possible in SAP (ECC 6.0)?
Thank you

1. Go to SPRO > MM > Purchasing > Authorization Management > Define Function Authorizations for Buyers > Function Authorizations: Purchase Order > Here "New Entries" and define Function Authorization Key as "01" and give description.
OR use T. Code - OMET
Here under "General parameters" subscreen, cctivate "Adopt PO Price" indicator and select "Enter conditions"
In "Possible ref. objects", select "W/o reference" otherwise reference documents (for e.g. PR, RFQ, etc...) for PO creation will become mandatory.
2. Now go to SU01 > Enter User ID > Parameters Tab > Here for Parameter ID EFB i.e. Function Authorization: Purchase Order, maintain value "01" and check in PO, PR will become mandatory for that user.
3. Now during creation of PR in ME51N, under "Valuation" Tab, you will get option for PO Price Adoption as Net or Gross. Select as per your requirement and it will copy Price to PO.

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

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

Create with reference where original document is incomplete

Similar Messages

Maybe you are looking for