Overview

1. Introduction

The Bensberg component `Scheduling agreement quality / Requirement analysis` is the central analysis for customer requirements of the SD and its environment.

The following functions are introduced in this document:

– Scheduling agreement requirement

– Order requirement and total requirement

– Open quantities

– Transit quantity and delivery quantity without goods issue

– Capacity analysis

– Planning scenarios

– Original quantities IDoc

– Requirement development

– Delivery schedule comparison with contradiction by form via mail or fax

– Requirement deviations according VDA 5009

– Requirement environment EDL/TAM/JIT

– Analysis JIT delivery schedule/forecast delivery schedule

– Analysis Scheduling

– Analysis DELINS

– Planned orders and delivery quantities of the production

– Original schedule lines, harmonized schedule lines and JDS/FDS offset

 

2. Scheduling agreement requirement

The analysis of the scheduling agreement requirement shows the current requirement quantities of the available delivery schedule types in a result matrix.

The temporal grouping is carried out either according to month, week or day up to 50 periods at the most into the future.

Additionally it is possible to analyze the delivery quantities of the past, which are assigned to the result matrix according to character.

The selection and aggregation of the requirement and delivery quantities are carried out dynamically; each field of a scheduling agreement and the referenced master data can be considered as character. This can be agreed on by user, user group or global by entries in the respective tables.

The current stock can be shown in a separate column and if requested a colored marking shows the coverage of the requirement in the future.

An update function ensures that the display is in accordance with the current delivery schedule status of the scheduling agreement.

Parallel to the actual requirement, further information can be provided displayed multiline:
– value in target currency, price basis is selectable
– additional delivery schedule type, e.g. planning delivery schedules
– deviations in quantity and/or percent

Each value displayed is interactive and branches by double-click into a context-referring analysis, e.g. display of the pegged requirement.


3. Order and total requirement

By the analysis of the order requirement the result, matrix showing the requirements of scheduling agreements, is extended by the display of adjustable order types (standard orders, immediate order etc.). The display is multiline according to character. If there is no scheduling agreement requirement available for a character, the order requirement appears as single requirement.

So far the display of the deliveries of the past has been activated upon the selection of the scheduling agreement requirement, the delivery quantities are also displayed for order requirements.

The temporal grouping, the selection options, the aggregation level and the display of detail information correspond to those of the scheduling agreement requirement.

If requested, the total requirement, which is the sum of scheduling agreement requirement and order requirement, can be displayed in a separate line.


4. Open quantities

The analysis of the open quantities extents the result screens of the scheduling agreement requirement by the display of the open quantity including a backlog view. The display is multiline according to character. If there is no scheduling agreement and/or order requirement, the open quantity is the only information displayed.

The display respectively considered document scope depends on the selection options agreed on and includes the open quantities of scheduling agreements as well as of orders.

The temporal grouping, the selection options, the aggregation level and the display of detail information correspond to those of the scheduling agreement requirement.

For the calculation of the open quantity the following variants are offered, which can be activated individually but also parallel:
– Open quantities for the schedule line date, delivery quantities without goods issue are open
– Open quantities for the schedule line date, delivery quantities without goods issue are not open
– Open quantities for arrival date, quantities without goods issue are open
– Open quantities for arrival date, quantities without goods issue are not open

– Open quantities for goods issue date, delivery quantities without goods issue are open
– Open quantities for goods issue date, delivery quantities without goods issue are not open

– Open quantities for material staging date, delivery quantities without goods issue are open

– Open quantities for material staging date, delivery quantities without goods issue are not open

A possible backlog is displayed in a separate column.


5. Quantity in transit and delivery quantity without goods issue

The quantity in transit and the delivery quantity without goods issue are displayed in two additional columns in the result screen of the scheduling agreement requirement. The quantity in transit corresponds to the information available in the current delivery schedule, the delivery quantity without goods issue is calculated based on the document flow of the involved scheduling agreements.

The detail analysis provides further information.


6. Capacity analysis

The capacity analysis extents the result screen of the scheduling agreement requirement by the display of the available capacity of a period and the possible shortfall or overlap.

In the standard the basis for the calculation is the ‘open quantity’ scheduled for the material staging date, but however, each quantity considered as open or also the scheduling agreement and order requirement can be referred to as basis.

The basis for the agreement on the offered capacity is the requested aggregation level of the requirements and open quantities and is defined in the respective tables of the component.  A multiple use of a demand considered as open is recognized and obtains a colored marking in the result screen.

Furthermore materials groups can be defined and if necessary a weighting factor (pro rata factor) can be allocated to each of the single groups.

On the offered capacity it can be agreed either linear but also variable, i.e. adjusted to a period (once/repeatedly) by considering percentage or quantity alterations.

For the calculation of the capacity the following variants are available, which can be activated separately but also parallel:
– capacity without consideration of the respective previous period, no consideration of stock
– capacity with consideration of the respective previous period, no consideration of stock
– capacity without consideration of the respective previous period, with consideration of stock
– capacity with consideration of the respective previous period, with consideration of stock

The calculation can be checked in a comprehensive detail analysis.


7. Planning scenarios

The forecast data transmitted in delivery schedules of the customers in general remain stable only in a relatively short temporal horizon (e.g. 3 months). After this horizon the requirements deviate heavily from delivery schedule to delivery schedule, so that they hardly can be used for a precise planning.

The analysis ‘planning‘ extends the result screen of the scheduling agreement requirement by the display of calculated, smoothed requirement forecast values, which in respect to time are behind an individually defined horizon.

The result line is separated and shows in the front (left) part the requirements of the customer 1:1, in the rear (right) part the calculated requirement, marked colored according to the degree of deviation. If requested, also a separate deviation line can be generated.

The calculation of the smoothed requirement forecast values is based on the actual delivery schedule data (short-term period), delivery schedules of the past (histories), the delivery quantities of the past and on a series of table settings, which also consider seasonal changes or start-up and phase out curves.

For each calculated forecast value a detailed analysis is available showing the complete calculation process.

As special release (customer specific) the calculated requirement forecast values can be transferred into a planning delivery schedule of the corresponding scheduling agreement (VA32).


8. Original quantities IDOC

The transfer of delivery schedules of a customer often are carried out electronically by DELINS-IDoc. During the posting process of an IDoc into the SAP-standard different procedures are available, by which the original quantities of the IDoc can be amended before transferred into the delivery schedule (splitting procedures).

The analysis ‘Original quantities IDoc‘ extends the result screen of the scheduling agreement requirement by the display of the deadlines and quantities of the IDoc according to the transmission of the customer. In this case the display is multiline per character.

The temporal grouping, the selection options, the aggregation levels and the display of detail information correspond to those of the scheduling agreement requirement.

On request, also a separate deviation line can be created.


9. Requirement development

The requirement development is an independent analysis showing the development of the current requirement during the past for defined key dates.

The possibility of temporal groupings allows running the analysis either by month, by week or by day for up to 50 periods back in time.

The key dates can individually be defined in the selection screen, i.e. the requirement can be analyzed e.g. always for the 1st of the month or always for the Monday of a week.

The selection and the aggregation options, which requirement quantities are to be considered can be defined individually, i.e. as character it can be referred to each field of the scheduling agreement and the referenced master data by entries in the respective tables. The agreement can be made according to user, user group or global.

Parallel to the actual requirement additional information can be shown by a multiline display:
– value in target currency with selectable price basis
– an additional type of delivery schedule, e.g. planning delivery schedule
– deviations in quantity and/or percent
– delivery quantities for the respective time unit
– average quantity of all delivery schedules of the respective time unit

Each value displayed is interactive and branches by double-click to the context-referred detail analysis, e.g. display of the pegged requirement.


10. Delivery schedule comparison with contradiction

With a new delivery schedule the current requirements of a customer are transmitted. Often an agreement is reached that the requirement quantities of the short-term period (frozen zone) may not be changed by a new delivery schedule. In case of a high delivery schedule sequence and the transmittal of a high number of delivery schedules this cannot be controlled.

With the analysis ’Delivery schedule comparison’ the respective current valid delivery schedule of a scheduling agreement is compared with its direct predecessor and the difference is determined by considering the cumulative quantities etc.

By means of ‘time windows‘, time areas can be defined for a delivery schedule (e.g. 2 weeks starting with delivery schedule date), which together with the limit values also agreed on in the time window (maximum deviations), form the basis for the analysis. For example, it can be agreed that for the first week before the delivery date no requirement deviation is allowed (0% deviation, no deadline shift), for the second week a deviation up to 5% (warning level) respectively 10% (error level) is permitted. The time windows can be defined according to day, week or month, global or according to customer and/or material.

Based on the time windows, in the first result screen the current analysis result is displayed in form of traffic lights. By this, on the first view it is visible how often the customer did not meet the agreements. In the detail screen the deviations are displayed in pieces or percent per selected period, colored indications show the breaches.

A detailed comparison of the delivery schedules old/new and the respective environment enable a precise interpretation of the deviations. By a link to the analysis ’Requirement development’, it is shown how the deviations have developed over a longer period in the past.

From the detail view, automatically a contradiction form can be send to the customer. As communication channel mail, fax or printer is offered.  On request it can be applied to customer-specific forms.


11. Requirement deviation according to VDA 5009

With VDA-standard 5009 a procedure is offered by which the average deviation margin (FQ key figure) of a requirement of a month, week or day is expressed in a key figure. Additionally the tracking signal (TS) shows the tendency, if the requirement of an evaluated time period has been over- or underestimated. In the Bensberg component this procedure is depicted 1:1.

By applying to a dynamic prognosis horizon, the analysis period can be divided in short, medium and long term period. The criteria in respect to time as well as the maximum permitted deviation in percent can be defined global or customer-specific. The usage of a manual prognosis horizon for an individual analysis is also possible.

The analysis result is shown as a traffic light overview, by which an immediate overview is attained without the need of having a detailed knowledge of the VDA-rule. By additional detail analyses the result is explained step by step down until to calculation of the VDA-formula.

The selection options and aggregation levels for the analysis results can be defined dynamically, i.e. by respective table entries, it can be applied to each field of a scheduling agreement and the belonging master data as evaluation character. This can be agreed on according to user, user group or global.


12. Requirement environment ESA / TAM / JIT

With the analysis of the requirement environment for the processes ESA, TAM and JIT it is checked, if the forecast data in the delivery schedules match the follow-up process in respect to time and quantity. The following individual data are shown:
– the scheduling agreement requirement of the past
– the own delivery quantities of the past
– the quantity of the ESA- consignment issue in relation to the LK-scheduling agreements
– the quantities of the TAM-delivery orders in relation to the LZM-scheduling agreements
– the quantities of the JIT-delivery schedules (quantity calls) in relation to the allocated   scheduling agreements

The grouping in respect to time can be carried out either according to month, week or day for up to 50 periods back in the past.

The selection options and the aggregation levels of the requirement and environment quantities can be defined dynamically, i.e. by respective table entries it can be applied to each field of a scheduling agreement and the belonging master data as evaluation character. This can be agreed on according to user, user group or global.

By a multiline display, additional information can be shown parallel for the actual requirement:
– value in target currency, price basis is selectable
– an additional delivery schedule type, e.g. JIT delivery schedule

All displayed values are interactive and by a double-click branch to a context-referred detail analysis, e.g. display of the pegged requirement.


13. Analysis JIT-delivery schedule/forecast delivery schedule

With JIT-delivery schedule, customers specify the transmitted ’rough’ requirement (forecast delivery schedule) for the short-term period (JIT-delivery schedule horizon). Whereas the forecast delivery schedule mostly reports month requirements, the JIT-delivery schedule is specified to a day basis. The SAP-standard system doesn’t offer a check, if the JIT-delivery schedule matches the forecast delivery schedule, especially in respect to quantity deviations.

The Bensberg component checks each JIT-delivery schedule. Based on the JIT-delivery schedule horizon it is determined, by considering the respective calendars, which quantity of the forecast delivery schedule can be used. The part quantity of the forecast delivery schedule is compared with the quantity of the forecast delivery schedule and possible deviations are determined. The result is displayed with respective colored indications for warning and error level.


14. Analysis Scheduling

Delivery schedules are often transferred into the scheduling agreements without a previous availability check. This might lead to the problem that, due to the transmittal of a new delivery schedule, the customers immediately creates a backlog at the supplier (requirement sent today to be delivered yesterday).

The Bensberg component checks each delivery schedule and based on the schedule line date, determines the complete scheduling: material staging date, schedule line date, goods issue date etc. With regard to the delivery schedule date, for each date it is check, if it lies in the past by considering a possible tolerance. Deadlines of the same day as the delivery schedule are displayed with a yellow indication, deadlines in the past in red.


15. Analysis DELINS

New delivery schedules are often transmitted in form of DELINS-IDOC. For this process, the Bensberg component offers check procedures, which take a closer look on this environment:
– Analysis Minimum and Maximum quantities
– Analysis Cumulative quantity received
– Analysis Delivery schedule number
– Analysis ’last’ delivery
– Analysis Order number
– Analysis Text modification and text content
– Analysis of zero quantities
– Analysis Field content IDoc and environment
– Analysis Target quantities
– Analysis IDoc-sequence
– Analysis Scheduling agreement determination

IDoc-referred analyses enable a detailed display of IDoc-contents and their DELINS-specific environment.

Search functions enable the trace of IDoc in reference to IDoc-contents, check results or referenced master data.

If requested, a stop of the IDoc can be activated, which already reacts before the posting of the IDoc due to checks of the environment (e.g. quantity monitoring, delivery schedule comparison) and then prevents the automatic posting of the IDoc. In this case, the IDoc-posting is carried out user-controlled out of the analysis of the component.


16. Planning orders and delivery quantities Production

The analysis of the planning orders and delivery quantities of the production extends the result screen of the scheduling agreement requirement in the requirement analysis (please refer to 2.) by the display of the created planning orders, scheduled on the requirements of the future. In this case, for each character the display is multiline.

So far delivery quantities of the past have been activated upon the selection of the scheduling agreement requirement, the delivery quantities of the production (defined goods movement) are displayed analogously.

The time-referred grouping, the selection options, aggregation levels and the display of detail information correspond to those of the scheduling agreement requirement.

All displayed values are interactive and by a double-click branch to a context-referred analysis.


17. Original deadlines, harmonized deadlines and offset of JIT/FDS

For the here-described analyses and procedures, it has to be considered that the requirements of the scheduling agreement releases and the order requirements are provided in different variants:

Original deadlines:

The customer requested deadline is used analogous to the used deadline indicator day, week and month and allocated in the analyses correspondingly. This allocation is carried out analogous to the SAP-standard during the processing of scheduling agreements and orders.

If the customer sends in a month deadline, the quantity is allocated in case of
– a month evaluation 1:1 to the month
– a week evaluation to the week in which the 1st of the month falls
– a day evaluation to the first of the month

If the customer sends in a week deadline, the quantity is allocated in case of
– a month evaluation to the month, in which the Monday of the week lies
– a week evaluation 1:1 to the week
– a day evaluation to the Monday of the week

If the customer sends in a day deadline, the quantity is allocated in case of
– a month evaluation to the month
– a week evaluation to the week
– a day evaluation 1:1 to the day

 

Harmonized deadlines:

The customer requested deadline is converted into the corresponding time unit analogous to the deadline indicator day, week or month, i.e. aggregated and/or distributed among working days.

If the customer sends in a month deadline, the quantity is allocated in case of
– a month evaluation 1:1 to the month
– a week evaluation to the weeks being part of the month, proportionally distributed (calendar)
– a day evaluation to the working days of the month (calendar)

If the customer sends in a week deadline, the quantity is allocated in case of
– a month evaluation to the months, which are part of the week (calendar)
– a week evaluation 1:1 to the week
– a day evaluation to the working days of the week (calendar)

If the customer sends in a day deadline, the quantity is allocated in case of
– a month evaluation to the month
– a week evaluation to the week
– a day evaluation 1:1 to the day

JIT DS/FDS-Offset:

During the JDS/FDS-offset the interaction of the two delivery schedule types is observed by considering the delivery schedule control:

– The JIT delivery schedule is considered until the JIT delivery schedule horizon. That means that these requirements are used. Thereafter it is applied to the requirements of the delivery schedule. The overlap between the two delivery schedules (part quantity at JIT delivery horizon) is created corresponding to the allocated calendar (working days).

The single deadline types need to be activated in the Bensberg component, only then they are available for the analysis. If more than one deadline type is available, during the selection the user can decide, which type he wants to use. Preset options are:

– Requirement forecast: original deadlines
– Requirement development: harmonized deadlines
– Analysis VDA 5009: harmonized deadlines
– Delivery schedule comparison: original deadlines

In case of a parallel analysis of requirements and open quantities, the JDS/FDS offset is of advantage as the SAP standard provides the open quantities also according to this procedure.


Purchase order number
402118