The profiles can all be maintained via the menu path described above. Some of the profiles can also be maintained directly in the product master or via Customizing for Supply Network Planning.

You can choose the fair share and push rules described below in either the Deployment profile, or on the SNP 2 tab in the location product master.

The following examples depict the three different ways that fair share logic can be implemented according to the selection you make in the Supply Network Planning deployment profile.

The objective of fair share rule A is to distribute the stock proportionally to all demand locations according to planned distribution demand.

The objective of fair share rule B is to raise the stock levels in all demand locations to approximately the same percentage of target stock level The percentage per target location is defined as projected stock level divided by the target stock level. If there is a negative projected stock level, the system first attempts to raise the stock level at all target locations up to zero. The system then attempts to raise the stock level at all target locations up to the same percentage of target stock level.

The objective of fair share rule C is to distribute the stock according to demand priority and/or quota arrangement at the demand locations. In order to apply rule C, you must define outgoing quotas for products of the source location in the SCE.

The objective of fair share rule D is to distribute the stock according to the priorities of the outgoing transportation lanes of the source location. If a fair share situation occurs, the system attempts to satisfy all the demands from the current date until the ATD quantity is exhausted. For example, you have three outgoing transportation lanes to your target locations (A, B, and C), each with the corresponding priorities (1, 2, and 3). Your ATD quantity is 150, and the requested quantity at each location is 100. If you choose fair share rule D, target location A, the transportation lane of which has been assigned priority 1, receives a quantity of 100. Target location B, the transportation lane of which has been assigned priority 2, receives 50, and target location C, the transportation lane of which has been assigned priority 3, receives nothing. You use fair share rule D in conjunction with the Deployment heuristic.

You specify a push rule in the Supply Network Planning deployment profile to indicate how you want the push logic to be implemented:

• With pull distribution (leave the field blank), all demand within the pull deployment horizon is met through deployment. Distribution occurs according to the due date specified at the demand locations. No supply is distributed to the demand source in advance of the demand date.

• With pull/push distribution (enter P in the field), all supply is distributed immediately to the demand locations to meet all demand within the pull deployment horizon without regard to the requirement dates specified by the demand locations.

• With push distribution (enter X in the field), all supply is distributed immediately to the demand locations for the entire planning horizon such that all the requirements are met immediately.

The following example depicts the three different ways that push logic can be implemented according to the time horizons maintained in the demand and supply profiles.

Pull¾A quantity of 200 is distributed to the DCs on each day for which demand exists within the pull horizon (four days into the future).

Pull/Push¾A quantity of 200 is distributed on the first day, when the supply is 200. A quantity of 600 is distributed on the second day. Although the supply is 1000, the demand within the pull horizon is only 600, so only 600 are distributed.

Push¾A quantity of 200 is distributed on the first day, when the supply is 200, and a quantity of 1000 is distributed on the second day, when the supply is 1000. Since the demand in the system is 1400, all the supply can be distributed. A demand of 200 at the end of the planning horizon is left uncovered due to lack of supply within the push horizon. If the demand in the system had been 800, only 800 would be deployed on the second day.

In Release 3.0A, further push rules have been included:

Q (Push by quota arrangement)¾Using this rule, instead of taking just the demands into account, the system uses the demand-dependent quota arrangements assigned to the transportation lanes to distribute supply.

S (Push considering the safety stock horizon)¾Using this rule, safety stock at the source location is used to fulfill only the demands within the corresponding safety stock horizon, and not other demand beyond this horizon.