on 05-21-2008 8:28 AM
I am trying to create a collective billing document ( credit memo ) for multiple credit memo requests which inturn were created with reference to different invoices.. But a collective credit memo is not happening. When I do it through VF04 , the split analysis shows difference in header data like ' reference number . assignment number, exchange rate , translation date etc. All this data is copied into creditmemo requests from respective reference invoices..
How do I overcome that ?
Regards
Mahesh
Hello,
First, make sure the header data is the same for all the documents from which you are trying to make collective invoices. Go to VTFA, check the copying control between your order type and the billing type. Clear the fields Allocation Number and Reference Number in the copying control. Now you try to generate the consolidated invoice and let us know the result.
Prase
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prashanth ,
The reference and assignment fileds are getiing copied from reference invoices into credit requests which inturn get carried to the credit memo and causing split in billing . Also there is business palce difference that is causing the split .
is there a way we can overcome the split criteria to combine credit requests referenced from different invocices into a single credit memo ?
Regards
Mahesh.
Hi Prashanth ,
The reference and assignment fileds are getiing copied from reference invoices into credit requests which inturn get carried to the credit memo and causing split in billing . Also there is business palce difference that is causing the split .
is there a way we can overcome the split criteria to combine credit requests referenced from different invocices into a single credit memo ?
Regards
Mahesh.
Hi Prashanth ,
The reference and assignment fileds are getiing copied from reference invoices into credit requests which inturn get carried to the credit memo and causing split in billing . Also there is business palce difference that is causing the split .
is there a way we can overcome the split criteria to combine credit requests referenced from different invocices into a single credit memo ?
Regards
Mahesh.
Hello,
The invoice split may have been carried out for the following reasons:
a) Explicit setting in Customizing
Explicit setting in Customizing:
On the detail screen of the document flow table (TVCPF) in the entry
field 'DATEN VBRK/VBRP' (as of Rel.2.2..: 'Data transfer') the
routine '003' (single invoice) was entered and thus an invoice split
was created.
b) Different header partners
The header partners in the billing documents created are not
identical which causes an invoice split. With regard to partner
processing, an invoice split also occurs if the entries in the
partner table of the reference document and the billing document
also differ only in one field for the partner functions of the
billing document header (in the standard system, these are SP, BP
and PY).
c) Different header fields
The header fields in the billing documents created are not identical
which causes an invoice split.
Attention: Not all header fields in the billing document are
visible on the header detail screen of the billing document.
d) The billing date of all documents is equated in a data transfer
routine (for example, by VBRK-FKDAT = SY-DATUM). This works when
you are billing using VF01; a single billing document is
generated. However, if you use VF04 or in case of a batch,
several billing documents might be generated.
When using transaction VF04 or Billing (background) the date of the
billing document (e.g. the current date) must be entered (In VF04:
settings, default data. In VF06 or background: variant with
parametrization) to avoid an unwanted split due to the billing date.
I hope that the information are helpful.
Regards
Claudia
Please don't forget to give Reward Points if you are satusfied with the answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
100 | |
11 | |
10 | |
6 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.