automotive consulting solution - websmp106.sap-ag.desapidp/012002523100019216702016d/... · proven...

Automotive Consulting SolutionTolerance checks for scheduling agreement releases in the sales process

2© SAP SE or an SAP affiliate company. All rights reserved.

Agenda

1. Benefit for the Customer

2. Description of the Function

3. The Function in the System

4. Technical Information


Proven solutions/services of SAP Automotive Consulting

Solutions already running productive at several customers

Solutions and documentation are available in German and English

Customer Benefit

Prompt implementation possible

Defined timeframe for implementation

Exact calculation of implementation cost. Implementation for fixed price

6 months of free follow up care operations for bug corrections starting at

the date of installation within the development landscape. Afterwards

chargeable consulting support starts

No additional ongoing costs (i.e. maintenance cost)

Time

Cost

Solution


Agenda






Motivation/Concept

The delivery schedules from the customers that are provided by EDI are normally posted automatically as a forecast delivery schedule or JIT delivery schedule in the scheduling agreement. Additionally the planning delivery schedule is used to fine-tune the requirements planning.

New forecast or JIT delivery schedule lines can differ (date/quantity) from the last planning delivery schedule lines posted. Additionally new schedule lines could differ from the prior agreed/maintained rounding quantity.

The enhanced tolerance check enables you to compare new forecast or JIT delivery schedule lines with the current planning delivery schedule lines to identify tolerance violations. The “frozen zone”, that might have been negotiated with the customer, can also be controlled. Backlog delivery schedule lines are checked on a daily, future delivery schedule lines within three time horizons on a daily/weekly or on a period basis.

A monitor to control these tolerance violations enables you to manually change or to automatically process the new delivery schedule lines situation. The results could also be used as evidence or discussion basis with the MRP controller from the customer side (Objection, takeover of costs for special transports, introduction of additional production shifts,…).


Agenda






Example: current delivery schedule situation

Schedule line type in the planning delivery

schedule indicates the schedule line origin:

F = Forecast delivery schedule

J = JIT delivery schedule

The real JIT horizon, in this example July 15.,

is mapped in the call header (additional data)


New JIT delivery schedule with quantity increase

Today is July 11. Quantity change from July 08. is backlog change


Monitor for delivery schedule analysis with tolerance

violations



violations

Overview about the scheduling agreements having rounding or backlog violations,

as well as tolerance violations within the three checking horizons based on a

daily/weekly/periodic check logic

Review and create the planning delivery schedule individually or process the new

proposals in the background



violations

Display call details and the tolerance profile that is the basis for the checks

Comparison of the new FDS/JIT-call schedules with the existing planning delivery

schedule and showing the resulted deviations

Automatic proposal for new planning delivery schedule, with manual change control


Explanation

Today is July 11. so July 08. is Backlog, quanity increase with a difference of +50 PC

Weekly tolerance check based on customizing up to the JIT horizon, as the JIT call triggered the tolerance

check:

July 11. +50 PC + July 12. +100 PC + July 13. +1400 PC + July 14. +1000 PC + July 15. +450 PC = +3000 PC


Practical example: new scheduling agreement releases

with existing tolerance violations – stopp logic

Inbound forecast delivery schedules are stopped, in case that for the scheduling

agreement a violation based on a JIT delivery schedule does exist.

Inbound JIT delivery schedules are stopped, in case that for the scheduling

agreement a violation based on a forecast delivery schedules does exist.

Delivery schedules of the same type are always processed.

Scheduling

Agreement

JIT delivery schedule

violations

Forecast

delivery

schedele Stop

Scheduling

Agreement

forcecast delivery schedule

violations

JIT delivery

schedele Stop


Practical example: Frozen Zone logic

Definition Frozen Zone: Time period in the short-term horizon, in which schedule

line changes are not possible any longer, e.g. goods are already in transit. The

Frozen Zone is either defined via a fixed number of (working) days or based on the

cumulative quantity in transit, depending which time period is longer.

Inbound forecast delivery schedules or JIT delivery schedules will be stopped, in

case of violations within the Frozen Zone time period. Negative impacts with

respect to evaluations on Quantity reliability / On-time delivery performance can be

avoided.

Example: schedule lines changes up to the

28th July would be considered as Frozen Zone

violation, as of the 200 pieces cumulative

quantity in transit.


Practical example: Check rounding quantity

If new schedule lines deviate from the maintained rounding quantity in the

scheduling agreement, a violation will be protocolled. In this case no checks

regarding the tolerance violations are processed any further.


Agenda






Technical Information

Available for SAP ERP ECC 6.0

Activation of automotive industrialized solution in SAP ERP System is

necessary

Technical installation is possible remotely

Modification-free

Delivery in Z-namespace


Source of Information

OSS-System

Notes (Search term: Automotive Consulting Solutions)

Internet

Overview-, Detail- and Customer presentations

http://www.sap.com/acs

Email - distribution list

Signing up through [email protected]

http://www.sap.com/acs

Thank you!

Mario Rebitzer

Platinum Consultant

Industry Area Automotive

SAP Deutschland SE & Co. KG

Hasso-Plattner-Ring 7

69190 Walldorf, Germany

M +49/ 170 22 00 287

S +49/ 6227 7 44674

E [email protected]

mailto:[email protected]


© SAP SE or an SAP affiliate company.

All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an

SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE

(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional

trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,

and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or

SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and

services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related

presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated

companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be

changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,

promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties

that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking

statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global12.sap.com/corporate-en/legal/copyright/index.epx

automotive consulting solution - websmp106.sap-ag.desapidp/012002523100019216702016d/... · proven...

Documents