Quantcast
Channel: SCN: Message List - SAP ERP SD Billing
Viewing all articles
Browse latest Browse all 6807

Re: Customer hierarchy

$
0
0

Hi Prathisbha,

 

Good day. Please check if the following notes are able to help you.

 

410579     FAQ: Rebate processing

114756     Customer hierarchy determination for pricing

75778      Consulting/troubleshooting for rebate processin

 

I tested the following steps:

--------------------------------------

1,Create Hierarchy Node - VD01
2.Create Customer Hierarchy - VDH1N.  Connect customer master records
3.Create Rebate Agreement - VBO1
4.updated using SDBONT06 report - VBOF

I tested the above and the following passage from note 75778 is correct

h) Hierarchy rebate

    In Sales and Distribution, it is possible to define a rebate so
    that payment is made on the basis of sales volumes of customer
    hierarchies.
    Maintain the customer hierarchy nodes (maintenance using TA VDH1)
    as customers. These must then be indicated as being relevant for
    rebate.
    IMPORTANT: If you need to make changes concerning relevance to
    rebate in the customer master, after you complete the changes,
    you must branch to maintenance of the customer hierarchy to
    update it and include this change.
    In accordance with the Customizing settings for partner
    determination, the system determines the hierarchy nodes at a
    higher level than the customer in the corresponding documents.
    These are then available for pricing or for rebate processing
    (fields: HIEBOxx).
    IMPORTANT: Since no new partner determination is subequently
    possible for documents, these cannot be updated. That is, changes
    to the customer hierarchy no longer affect partners in existing
    documents and therefore no longer affect existing sales volumes
    within a rebate arrangement.

The thing is when a hierarchy is detected the heirarchy partner is
written into table XVBPA in the sales document, then it becomes
available to pricing.

 

SDBONT06 does a new pricing with pricing type 'I' but in the case of
subsequent invoices the partner function of the hierarchy is missing in
the document so the heirarchy field used by pricing is not filled and
the condition not found.

It might be possible for you to use the pricing user exits in RV60AFZZ
to fill the heirarchy partner in which case SDBONT06 might be able to do
the update.

I hope the above information is able to clarify the standard system
behaviour to you.

Thanks,

 

Best Regards;

Lohyh


Viewing all articles
Browse latest Browse all 6807

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>