SA Release with Industry Month or Interval Schedule Line

Receive Industry Month or User-Defined Periods

You can use user-defined periods, for example industry months, for sales scheduling agreement schedule lines. This means that you can also receive and process releases from your customers that contain periods other than daily, weekly or monthly quantities.

An industry month includes all weeks that lie entirely within a calendar month, plus the weeks on either side of the month, if the Wednesday lies within the calendar month in question. The beginning of the week or industry month is Monday.

Prerequisites

To use industry months or user-defined periods you must implement the Business Add-In (BAdI) Edit User-Defined Period Formats (/SAPAPO/CMDS_SL_DATE).

The BAdI contains example coding for the implementation of industry months.

This BAdI is called up in the following cases:

When releases are created or changed in master data maintenance for sales scheduling agreements.
When new releases, which you have received by IDoc, are created in the system.
When the due delivery schedule is generated from the from forecast/planning (F/P) or operative delivery schedule, if the system has to carry out a delivery schedule split for the F/P delivery schedule, so that these periods are also split.

You implement this BAdI in Customizing for Supply Chain Planning under Start of the navigation path Delivery Schedule Processing for Sales Schedule Agreement Next navigation step Business Add-Ins (BAdIs) for Sales Scheduling Agreement Processing Delivery Schedule Split and Due Delivery Schedule End of the navigation path .

If you want the system to also take user-defined periods into account in the delivery schedule split (during due delivery schedule creation) then you must:

In the split profile, assign appropriate splitting rules to the date or period type that you want to use. ( Supply Chain Planning Delivery Schedule Processing for the Sales Scheduling Agreement Delivery Schedule Split Maintain Delivery Schedule Split Profile ).
Assign delivery schedule splitting rule and delivery schedule splitting profile for the date or period type in question ( Assign Delivery Schedule Rules ).

Example Example

For example, if you use industry months then the industry month March in the year 2003 would cover the time period from March 3 ^rd to March 30 ^th and the industry month April would cover the time period March 31 ^st to May 4 ^th .

The user can for example, enter a schedule line in the industry month March 03 or enter an exact date.

If the user enters a schedule line for the 15 ^th April (with the date or period type Industry Month ), the system determines the industry month to which it belongs. Depending on how the BAdI has been implemented, the display of the date entered can be converted either into the period industry month April 03 or into the start date of the industry month (31 ^st March 2003).

The schedule line is always saved to the database with the start of the period, in this case 31.03.2003.

End of the example.

Receive Interval Schedule Lines

You can receive operative or F/P delivery schedules with interval schedule lines by IDoc.

These are split into daily quantities during IDoc inbound processing, before operative and F/P delivery schedules are created, and they are displayed in the release history.

The system carries out the split according to the splitting rule defined in Customizing without taking a calendar into account so that interval schedule lines can be distributed to days on which an outbound delivery is possible. If no split rule if specified the system assumes a 7-day week.

Therefore releases are first split and then saved. The due delivery schedule is then generated. The due delivery schedule generated from the F/P and operative delivery schedules contains only the split daily quantities and does not contain information about the intervals that were transmitted originally.

In contrast, the splitting of “normal” F/P delivery schedules only takes place after releases have been created during creation of the due delivery schedule (and not during IDoc inbound processing) with reference to a calendar.

Prerequisites

The following prerequisites exist:

Your customer must send the correct date type ( PRGRS = I – Interval) and also the start and end date of the interval ( EDATUV and EDATUB) in the IDoc DELFOR02 in segment E1EDP16.
In Customizing for Sales Scheduling Agreement Processing under Delivery Schedule Splitting , define a splitting rule.
Assign this splitting rule to the sold-to party in the task level menu under Supply Chain Collaboration Sales Scheduling Agreement Processing IDoc Inbound Processing Define Inbound Release Processing .

Differences During Delivery Schedule Splitting of Interval Schedule Lines and “Normal” Schedule Lines

	Interval Schedule Lines	Delivery Schedule Split in “Normal” Schedule Lines (For Example, Industry Month or Monthly Schedule Lines)
How is inbound processing carried out?	By IDoc	Manually or by IDoc
When does the split take place?	During IDoc inbound processing, before the delivery schedules are created	After delivery schedules are created, during subsequent due delivery schedule creation
Which delivery schedules are split?	Operative and F/P delivery schedule	F/P delivery schedule
Is a calendar used?	No calendar	Calendar for the customer location or calendar specified for determining non-working days by the BAdI Modification of Delivery Schedules /SAPAPO/CMDS_DS_MOD.