Customer Hierarchy modifyable

[Former Member]

Hi,

We are using Customer hierarchy in 4 levels. where as the highest level is 1D, next is 1C. these two partner functions are maintained as modifiable in partner function definition in partner determination procedure for sales document header. Example procedure is TA.

Against these 2 partner functions in the procedure we have maintained origin as B (customer hierachy table KNVH).

When we create a Sales Order, in header level partners tab we are observing the 1D and 1C as grayed out (not changable).

Now our requirement is, is there any possibility to make it as changeble, so that we can change the hierarchy node in the sales order too.

Venkat Cheedalla.

[Former Member]

Hi Venkat,

The customer hierarchy cannot be changed in the sales order.

It is something of a dynamic nature and therefore even if you have the correct customizing, SAP surely has some hardcode to avoid that someone change the customer hierarchy in a sales document.

http://help.sap.com/saphelp_45b/helpdata/en/dd/55f5c3545a11d1a7020000e829fd11/frameset.htm

Customer Hierarchies in Sales Order Processing 
Customer hierarchies are used to determine pricing and rebates in sales and billing documents. When you process a sales order for a customer who is assigned to a customer hierarchy, the system automatically determines the corresponding hierarchy path.
The hierarchy path shows the relationship of a customer to the chain of nodes all the way up to the top level of the hierarchy. The system uses partner determination to build the hierarchy path in the sales order.

My recommendation: Check why you need to update the customer hierarchy and re-evaluate the need.

You might want to use a different payer (RG partner function) in the sales order from the sold-to-party (AG) to improve flexibility regarding invoicing.

Also be aware that in the standard system, when you create a sales and distribution document, the system does not correctly determine the hierarchy condition records.

Reason:

The system does not read the customer hierarchy with the pricing date (PRSDT), but always with the current date (SY-DATUM).

You need to apply OSS Note 114756 - Customer hierarchy determination for pricing, to resolve the problem!

Hope it helps,

Best Regards,

Franck