Customer PO number as the split criteria for Debit Memo

[Former Member]

Hi,

We have the below given business scenario. If we create DMR wrt to original billing document and then create DM, PO number is not considered as the split critera.

Debit Memo Request (DMR) will be created wrt original billing document. Due to some business reason, we create more than one DMR on the same day against the same original billing document. Our requirement is to have 1:1 relation between DMR & Debit Memo (DM) for this scenario.

While creating DMR we are using different PO number, so that invoice get split due to PO number. However during the batch job system combines all the DMR for the day into one DM, and it never considers the PO number as a split critera.

Please note that if we create DMR without reference, PO number works fine as split critera. Only issue is while we create DMR with reference.

We can use single invoice to make this scenario work, but the issue is then it will be always 1:1. Our requirement is to split if the PO number is different.

Is there any standard way to meet this?

Regards,

[Lakshmipathi · Accepted solution]

Not sure what your copy control in VTFA is ?   If you have maintained "A" for "Reference number", system will split your debit memo based on PO reference.

G. Lakshmipathi

[Former Member · Accepted solution]

HI Lakshipathi,

We need invoice number as the reference due to AR requirement and hence left it blank. Other settings are as given under.

Copying requirements   001  Header/

Determ.export data     B

Assignment Number      A

Reference number

Target Bill. Type  ZL2                   Ref. SalesDoc Type ZDR
                   Debit Memo                               Debit Memo Request

Item Cat. Proposal                       Item Category      ZL2N
                                                            Debit Memo

Copying requirements   002  Item/order-related          Billing quantity     A
Data VBRK/VBRP         002  Ord-rel.credit memo         Pos./neg. quantity   +
                                                        Pricing type         D
                                                        PricingExchRate type
                                                        Price source

Please do check and advise if there is any other option to meet this requirement.

Thanks & Regards

[Former Member · Accepted solution]

HI Laxmipathi,

I have made the suggested changes, and this works for debit memo request created without reference. However this is not wokring for the debit memo request with reference. In this scenario it always, picks the orginal billing document details in the assingment and reference field.

Is there anything missing in the config?

Regards,