Customer Hierarchy In Condition Contract / delta accrual

[BBB123]

Hi,

I am using a customer hierarchy node in a condition table for a condition contract. The accruals are generated via the normal SD F2 invoice and the customer hierarchy works fine. But when doing a delta accrual, the pricing analysis shows that the value for the customer hierarchy isnt found, while using the same condition table as in the SD invoice pricing. Any idea what the cause of this is.

[GauthierVictor · Accepted solution]

Hi @BBB123, 

Assumptions: 

• You're talking about Single Customer Sales Condition Rebates contract (0S01 or 0S03 or 0SG1 or 0SG3) 

In the standard scenario above, the system doesn't have all the source information inside the Settlement document about Sold-to, Ship-to, Bill-to, Payer... The rebate recipient can be completely different than the business volume you're considering for the contract. 
For pricing determination, the information should be stored in the Settlement document or determined via a specific logic (e.g. via transfer manager). 

For your scenario, you should have the relevant data transferred to the Settlement document using split criteria at line item level (i.e. Sold-to) + use transfer manager to change the value of the Sold-to in the pricing communication header table. 
By default, the Sold-to in those scenario will be the rebate recipient (unique partner present in the settlement document) and not the sold-to or other partner functions from the business volume, and I guess in your case the rebate recipient is not part of the customer hierarchy. 

Regards,
Gauthier Victor 

[jb123 · Accepted solution]

Hi, it is actually not a Single Customer Sales Condition Rebates contract

[BBB123 · Accepted solution]

Hi, I am using a copy of 0s02 contract type. All other key combinations work just fine in the pricing procedure of the delta accrual document 0s42