Define Split Management

This document explains how you define a split model, which determines how delivery schedule (DS) demands will be split during validation.

A split is necessary when the received demands are aggregated for a specific demand bucket (such as monthly demands) and you want to break them down to weekly or daily demands. The reason for doing this is to create a more detailed planning overview and a more correct replacement between forecast and call-off DS.

Outcome

Automatic Split

The DS demands will be split during validation if this is specified in the '060 Check if quantity split should be performed' field in 'Settings - Partners' (RSS015) along with a split model defined in 'Delivery Split Model. Open' (RSS055).

Manual Split

This is used to perform split calculation manually via option 72=Split in 'Delivery Schedule. Connect Items' (RSS101). The split can also be reversed via option 73='Delete split' in (RSS101).

Follow these steps

Define a Split Model and Connect Period Types

  1. Start 'Delivery Split Model. Open' (RSS055). Define a split model.

  2. Select option 11=Period types. This starts 'Split Model. Connect Period Types' (RSS056).

  3. Connect a period type to the split model.

    Period types are defined in (CRS910), connected to periods in (CRS900) and connected to companies/divisions in (MNS100).

Determine Whether Split Will Be Performed Automatically or Manually

  1. Start 'Settings - Partners' (RSS015) and open the E panel.

  2. Activate the '060 Check if quantity split should be performed' field if you want the split be performed automatically during validation of the DS. Connect a split model in the second field.

  3. Do not activate the field if you want to perform the split manually via option 72=Split in 'Delivery Schedule. Connect Items' (RSS101).

Parameters to set

Program ID/Panel Field The field indicates …
(RSS055/B) Model

… a split model.

This is used to connect a defined split model to a delivery schedule that belongs to a defined combination of direction, partner, and message and application reference.

The split functionality splits a quantity into several deliveries and is defined in (RSS055) and (RSS056).

(RSS056/B) Period type

… a key identity in the period table, which makes it possible to work simultaneously with up to five different periods per division.

For each record in the system calendar (CRS900), you can see that the day is connected to one of five different period types.

Besides the five period types, period type 9 can be defined. It is used in the forecasting component to enable forecasting item numbers per week.

(RSS056/E) Demand bucket

… the time bucket, or time period, covered by the demand in the delivery schedule.

The valid alternatives are:

1 = Daily demand

2 = Weekly demand

3 = Monthly demand

4 = Yearly demand

5 = Two-week demand.

The default value is 1 unless it is overridden via parameter 205 in (RSS015) or received in the EDI transmission.

The demand bucket can be used to perform a demand split if defined in parameter 060 in (RSS015).

(RSS056/E) Demand commitment

… the buyer's desired level of commitment for the demand in the delivery schedule.

The valid alternatives are:

1 = Firm

2 = Manufacturing

3 = Raw material only

4 = Forecast

9 = Reference to agreement between partners.

(RSS056/E) Period qualifier

… the period qualifier, which specifies the type of period referred to in the 'Number of periods' field.

The valid alternatives are:

1 = Days

2 = Weeks

3 = Months

4 = Years.

(RSS056/E) No. of periods … the number of periods referred to by the value in the 'Period qualifier' field above. The period qualifier indicates the type of period, such as days, weeks and so on.
(RSS056/E) After period

… whether to use a new period type after the current period type.

The valid alternatives are:

0 = No. the periods will overlap each other

1-9 = Yes. The periods are in sequence. Types 1-9 can be used.

If 0 is entered, the delivery status indicator must be defined.

(RSS015/E)

060 Check if quantity split should be performed

(field 1)

… whether the information for splitting specified in (RSS056) should be used to split quantity buckets, such as weekly requirements to daily requirements.

The valid alternatives are:

0 = No

1 = Yes

If activated, split will be performed automatically after validation.

(RSS015/E

060 Check if quantity split should be performed

(field 2)

… a split model.

This is used to connect a defined split model to a delivery schedule belonging to definition of direction/partner/ message/application reference.

The split functionality splits a quantity into several deliveries and is defined in (RSS055) and (RSS056).

Related topics