Billing Document is Created with reference to Cancelled Sales Document

Hi Experts!!
Please Help me.. I'm so confused why does the system allows creation of billing document with reference to a cancelled sales document.
Settings:
We use document type (ZRAS-Repairs/Service) for service order and use billing document (ZFR-Invoice Repair).
I have already assigned reason for rejection for each line item, but still I can create billing document with reference to that SO.
Help Help Help...
Regards,
Carla

Go to OVAG, this is where we maintain reasons for rejection
IMG > Sales & Distribution > Sales > Sales Documents > Sales Document Item > Define Reasons for Rejection
Select your reason for rejection and put a check under the column "BIC", this means that your items will not be relevant for billing..
Hope this answers your question..

Similar Messages

  • IDOC message type WMMBXY not including Serial numbers in GR material documents when created with reference to an Inbound delivery

    Hello,
    We currently have an inbound ALE process (message type WMMBXY and basic type WMMBID02) to post GR's against inbound delivery. If the inbound delivery item is maintained with serial numbers, we want those serial numbers to be pulled into the goods movement material document (and stored in SER03).
    Currently segment E1MBXYJ is maintained with the inbound delivery number in field VLIEF_AVIS and Inbound delivery item number in field
    VBELP_AVIS. In segment E1MBXYI, no purchase order is assigned and the fields EBELN and EBELP are blank. The movement indicator (KZBEW) has the value 'B'.
    Even after making the above settings, the serial number(s) maintained on the Inbound delivery item do not get saved to the material document.I did look at OSS note 833603 (Solution for 2 - GR for Inbound delivery) and we have followed the same settings. This works when there is no serial number in the Inbound delivery. However if we have serial numbers, the IDOC posts successfully, however the material documents in MB03 do not have any serial numbers copied over from the Inbound delivery where the serial numbers are definitely assigned.
    Any help you can provide is greatly appreciated!
    Thanks,
    Ashvin
    P.S
    If we manually create the GR via MIGO, the serial numbers are automatically applied to the GR material document. This is what we want to accomplish via the above IDoc process.

    Hi
    Try with enhancement MWMIDO08. See note 833603 - EDI: Goods receipt for stock transport order for further information.
    I hope this helps you
    Regards
    Eduardo

  • 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

  • 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

  • Single Invoice with reference to 2 Sales Order

    Hi,
    How can i make a single  billing invoice no (vf01) with reference to 2 sales order?
    billing plan has been maintained from each sales order,we dont have any pgi process.
    so process is sales order->billing plan-> invoice
    my user want to generate single invoice with reference to 2 sales order - same customer no.

    For processing  billing due list (VF04) - The system combines documents with the same customer number, proposal billing type and sales organization, and attempts to include them all in the same billing document. If the preconditions are met, then a single invoice is created for the deliveries and/or orders.
    To do a collective billing. Collective Billing Documents
    The selected documents in the billing due list are billed. The system tries to combine them as much as possible. Processing of the selected documents is carried out in the background. After processing of the documents, you return to the billing due list. The sysytem will indicate whether or not a document has been billed successfully.
    If successful, then Save
    You can also carry out a simulation of billing. In this case, select Simulate. The system simulates the collective billing / online function described above.
    -After the collective run you can display a log for the collective run. This displays possible errors during billing.
    -You can also branch to the resulting billing documents, in order to carry out a split analysis.
    -The billing documents of a collective run can also be canceled.
    Re: VF04
    Hope it assist you.
    Thanks & Regards
    JP

  • 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

  • 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.

  • 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?

  • TO CREATE AN INVOICE WITH REFERENCE TO THE SALES ORDER

    I have a credit memo request(sales order) and I need to create a credit memo(invoice) on saving the sales order without creating the delivery order in between.The invoice(credit memo) must be created directly with "reference" to the sales order(credit memo request) without the delivery order in between

    Hi,
      You can deliver the standard sales order by VA02 going to sales document-> deliver.
    then save it it will give you outbound delivery number then go to vl02n the do the PGI of the same.
    and for Invoices first create billing document byVF01 then create invoice list VF21
    Thanks
    Ankur
    Edited by: Ankur Sharma on Jul 23, 2008 7:51 AM

  • 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.

  • 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

  • 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

  • Can Two Invoice be created with reference to one Return order

    Dear All.
                  Can two SR Invoice be created with reference to one SR Order.

    Thanks JP Sir,
                       Much appriciated ,we are having SAP IS:AFS(Our Business is of Manufacturing & Marketiing.Consumer product.
    Sir- I created a SR Order after creating it forgot to do PGR & without  doing PGR I opened sales log in order & created SR Invoice without doing PGR & when I check it in VF03 ,Issue print out then there was not any material discription in Created Credit Invoice & when I checked Display document then there were no any delivery document then I came to know without doing PGR how material  can be copied  & then did PGR  with reference to same SR Order  n created another Invoice .but my question is that without cancelling previous SR Invoice how another Invoice can be created with reference to same SR Order.
    Thanks,
    Kamlesh

  • Create with reference using BAPI_SALESDOCU_CREATEFROMDATA

    Hi,
      I have been trying to use BAPI_SALESDOCU_CREATEFROMDATA to create with reference. I am trying to use the fields REF_DOC and REF_DOC_CA in structure ORDER_HEADER_IN
    but the created order is not copying any data from the referenced order. Aaprt from the ref order I am passing the sales area data and sold to customer. Am i missing something or is create with reference not supported?
    Regards,
    Hari.

    Hi,
    This bapi will work when you try to copy invoice to the credit memo request..pass the billing document number in salesdocument parameter and pass the sales document type(CMR type) in documenttype.
    Thanks
    Naren

Maybe you are looking for