Access hierarchy for processing rules

For some processing rules, a hierarchy of key fields and key field combinations are used to access the configuration data for the message import.

For BOD separation rules and the message processing rules the key fields are Customer, Internal Item, and Ship To. These key fields or combinations of them are used to search for the processing rules in a predefined search sequence. The search sequence that is used to evaluate the appropriate processing rules for an incoming release order is shown in this table:


Key fields	Processing rule	Search sequence
Customer, Internal Item, Ship To	BOD separation rule	Internal Item + Ship To + Customer
	Message processing rule	Internal Item + Ship To
		Internal Item + Customer
		Customer + Ship To
		Internal Item
		Ship To
		Customer
		None

Release Management uses a combination of the customer, internal item, and ship to to start the search for a valid processing rule. If a processing rule cannot be found, a combination of internal item and ship to is used to continue the search for a valid rule. If a valid processing rule that is based on the extracted key data cannot be found, a general processing rule is used. A general processing rule is defined without key fields for a special period. This rule is then applied to control the import of an incoming release order.

Note: We recommend that you configure one general rule for the majority of business cases. For example, configure one BOD separation rule for planning schedules and exceptions from the general rule on item level.

For CUM adjustment rules, requirement consolidation rules, and date range rules, the key fields are Customer, Ship To, and Message Subtype. These key fields or combinations of them are used to search for the processing rules in a predefined search sequence. For this search the message type is required. The search sequence that is used to evaluate the appropriate processing rules for an incoming release order is shown in this table:


Key fields	Processing rule	Search sequence
Message Subtype, Customer, Ship To	CUM adjustment rule	Message Subtype + Ship To + Customer
	Requirement consolidation rule	Customer + Ship To
	Date range rule	Message Subtype + Ship To
		Message Subtype + Customer
		Ship To
		Customer
		Message Subtype
		None

Release Management uses a combination of the customer, ship to, and message subtype to start the search for a valid processing rule. If a processing rule cannot be found, a combination of customer and ship to is used to continue the search for a valid rule. If a valid processing rule that is based on the extracted key data cannot be found, a general processing rule is used. A general processing rule is defined without key fields for a special period. This rule is then applied to control the import of an incoming release order.