To Be Process Revision Level Management document.doc Version: Status: Released Author: -CDB Date last update: 06/02/2005 Date printed: 23/6/2022 Table of content 1 DOCUMENT UPDATES AND VALIDATIONS...........................................2 2 SCOPE...................................................................... 3 2.1 PROCESS SCOPE DESCRIPTION................................................... 3 2.2 APPLICATION ARCHITECTURE (GLOBAL).............................................3 2.3 CROSS REFERENCES...........................................................3 3 PROCESS.................................................................... 4 3.1 CORE MODEL - PROCESS FLOW AND DESCRIPTION......................................4 3.1.1 Revision Level Definition...................................................................................................................... 4 3.1.2 Impacts on Material Master Records................................................................................................. 4 3.1.3 Impacts on other Master Data............................................................................................................ 5 3.2 COUNTRY SPECIFIC - PROCESS FLOW AND DESCRIPTION.................................5 4 BUSINESS RULES............................................................. 6 4.1 CORE MODEL – BUSINESS RULES FOR MASTER DATA DOMAIN.............................6 4.1.1 Business requirements......................................................................................................................... 6 4.1.2 As-Is Situation in the SAP Sekurit Countries....................................................................................... 7 4.1.3 To-Be Business Rules for Revision Level Change............................................................................... 8 4.1.4 Business Scenarios for a Revision Level Change............................................................................... 9 4.1.5 Impacts of the To-Be Revision Level management on the Controlling ......................................... 13 4.1.6 Impacts of the To-Be Revision Level management on the Logistics .............................................. 17 4.2 COUNTRY SPECIFIC – BUSINESS RULES...........................................20 5 KEY ELEMENTS OF SAP IMPLEMENTATION........................................20 6 APPLICATION SPECIFIC DEVELOPMENT REQUIREMENTS.............................20 7 Key volume & performance indicators.......................................20 1 23/06/22 - 09:31
Transcript
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
Table of content
1 DOCUMENT UPDATES AND VALIDATIONS................................................................................................2
3.1 CORE MODEL - PROCESS FLOW AND DESCRIPTION...........................................................................................43.1.1 Revision Level Definition..................................................................................................................... 43.1.2 Impacts on Material Master Records....................................................................................................43.1.3 Impacts on other Master Data.............................................................................................................. 5
3.2 COUNTRY SPECIFIC - PROCESS FLOW AND DESCRIPTION..................................................................................5
4 BUSINESS RULES............................................................................................................................................ 6
4.1 CORE MODEL – BUSINESS RULES FOR MASTER DATA DOMAIN.......................................................................64.1.1 Business requirements.......................................................................................................................... 64.1.2 As-Is Situation in the SAP Sekurit Countries.........................................................................................74.1.3 To-Be Business Rules for Revision Level Change..................................................................................84.1.4 Business Scenarios for a Revision Level Change...................................................................................94.1.5 Impacts of the To-Be Revision Level management on the Controlling.................................................134.1.6 Impacts of the To-Be Revision Level management on the Logistics.....................................................17
4.2 COUNTRY SPECIFIC – BUSINESS RULES........................................................................................................20
5 KEY ELEMENTS OF SAP IMPLEMENTATION........................................................................................20
6 APPLICATION SPECIFIC DEVELOPMENT REQUIREMENTS..............................................................20
Date last update: 06/02/2005 Date printed: 18/4/2023
1 Document updates and validations
UpdatesDate Version Author Comment
10/06/02 V1 CDB TBP initialization for Master Data domain14/06/02 V2 CDB First release as a draft01/07/02 V2.2 CDB Integration of CO inputs03/09/02 V2.3 CDB Update of the TBP after validation of the RL management04/11/02 V2.4 CDB Integration of transition rules when RL changes.04/11/02 V2.5 CDB Modification of the TB.19/11/02 V2.6 CDB Modification of the TB based on KU remarks22/11/02 V3.0 CDB Modification of the TB based on PO remarks06/02/05 V3.1 CBR Update of the TBP after French RO.
ValidationsDate Version Validation
Resp.Comment
19/11/02 V2.6 KU Validation of the TB by the Key Users22/11/02 V3.0 PO Validation of the TB by the Process Owner
2 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
2 Scope2.1 Process scope description
The subject of this To-Be-Process is the definition and the management of the Customer Revision Level in SAP.
The To-Be-Process aims at- Defining the Customer Revision Level- Defining the Business Rules related to the modification of the Revision Level- Identifying the impacts on the Material Master Records of a Revision Level modification
A revision level modification will also impact the following Master Data: - Impacts on Production Planning Objects (PP)- Impacts on Sales Documents (SD)- Impacts on Purchasing Documents (MM)- Impacts on Controlling objects (CO)
However, the current document will not treat theses related impacts that will be more detailed in some other To-Be-Processes.
This To-Be-Process is defined for the perimeter of Saint-Gobain Sekurit Avenir V2 Project. It concerns the Glass Manufactured Products, with the Material Types: FER1, HLB1 and ZPRO.
2.2 Application architecture (global)
Not Applicable
2.3 Cross references
This document could refer to other To Be Processes as:
TBMD01 Product Characteristics TBMD03 Glass Product Creation Process TBMD06 Logistic flow and master data creation TBMM13 Purchasing process: Scheduling Agreement TBSD09 Scheduling Agreement Management TBPP03 Define BOM structure TBPP05 Defined Planning Parameter TBPDC01 Production Initialization TBCO06 Consolidated Margin
3 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
3 Process
3.1 Core model - process flow and description
3.1.1 Revision Level Definition
Each customer product can be identified in a unique manner with both Customer Part Number and Customer Revision Level:
Customer Product = {Customer Part Number + Customer Revision Level} .
When a customer decides to modify a product without modifying its Part Number (e.g.: extra hole on a glass, change of tolerance ratio…), he can just upgrade the revision level ( the “Revision Level” can exclusively be modified by the Sekurit Customer himself).
Remark: However, some car manufacturers (e.g.: Volkswagen) integrate implicitly the Revision Level within the Customer Part Number. In this case, each revision level change will correspond to a new product Part Number.
A product modification that is not requested by the Sekurit Customer (as change of silver print, furnace type…) is not a Revision Level case, and will not imply any creation of new finished product (product sold to SGS Customer). This kind of information could be managed in the WMS as described in the To Be Process “TBPDC01– Production Initialization”.
As the Revision level is not usually sent in the DELINS of the OEM, it cannot be used as criteria to manage the order/shipping process in SAP.Thus the To-Be Process should enable to manage DELINS without any revision level indication and to ensure that a new OEM revision level is created at each OEM modification.
3.1.2 Impacts on Material Master Records
Depending on where the modification related to the new Revision Level takes place (Glass Plant, Extrusion / Encapsulation Plant or Service Center), only the products that are physically impacted by will have to be re-created in the system. Those which are no physically impacted will only have their Revision Level updated without other modifications.
4 18/04/23 - 22:48
Modification
Manufacturing Process Steps
SGS Customer
(New Revision Level)
New Master Records To Be Created
Master Records To Be Updated
(Revision Level)
Modification
Manufacturing Process Steps
SGS Customer
(New Revision Level)
New Master Records To Be Created
Master Records To Be Updated
(Revision Level)
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
3.1.3 Impacts on other Master Data
The following chart details on a manufacturing process flow what are the different master data impacted by the modification of revision level
For more details on the Purchasing Master Data and on the Sales Master Data creation / modification process, refer to the document TBMD06 –Logistic Flow & Master Data Creation
For more details on the MM Scheduling Agreement creation / modification process, refer to the document TBMMM13 – Purchasing process: Scheduling Agreement
For more details on the SD Scheduling Agreement creation / modification process, refer to the document TBSD09 – Scheduling Agreement Management
3.2 Country specific - process flow and description
Not Applicable
5 18/04/23 - 22:48
Plant 1 Service Center OEM
X1’ X1’’…. X1
Plant 2
X1 X2’ X2’’…. X2 X2 X3’ X3’’…. X3 X3 = ref OEM
Modification
SD Sch. Agreement
MM Sch. Agreement
SD Sch. Agreement
MM Sch. Agreement
SD Sch. Agreement
Purchasing Master Data
Sales Master Data
Sales Master Data
Purchasing Master Data
Sales Master Data
PP & CO Master Data
PP & CO Master Data
PP & CO Master Data
Master Data Impacted by the new Revision Level
Master Records Non-Impactedby the New Revision Level
Plant 1 Service Center OEM
X1’ X1’’…. X1
Plant 2
X1 X2’ X2’’…. X2 X2 X3’ X3’’…. X3 X3 = ref OEM
Modification
SD Sch. Agreement
MM Sch. Agreement
SD Sch. Agreement
MM Sch. Agreement
SD Sch. Agreement
Purchasing Master Data
Sales Master Data
Sales Master Data
Purchasing Master Data
Sales Master Data
PP & CO Master Data
PP & CO Master Data
PP & CO Master Data
Master Data Impacted by the new Revision Level
Master Records Non-Impactedby the New Revision Level
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
4 Business Rules
4.1 Core model – Business rules for Master Data Domain
4.1.1 Business requirements
4.1.1.1 Business requirements for Planning
The following business requirements have been expressed by the “Planning” domain workgroup:
If the revision level generates changes on the physical characteristics of the product, it must be possible to anticipate the impacts on finished products and all revised semi-finished products:
Analysis of demand for each revision level Definition of switch dates for production (end of former revision level / start of new
revision level) Definition of target profiles for stock (decrease for former revision level / increase
for new revision level) Adjustment of the supplying programs on components at each BOM level
(e.g.: anticipation of supplying requirements for new float article)
For the planning process, it must be possible to group together same articles with same physical characteristics, regardless the OEM revision level on finished product
The target stocks are managed on a global basis, regardless accounting considerations
The campaigns for articles with the same characteristics must be grouped together, in order to improve the TRS
Planning efficiency is facilitated if the number of articles is limited
4.1.1.2 Business requirements for Controlling
The following business requirements have been expressed by the “Controlling” domain workgroup:
All needs for Controlling are targeted to obtain an Extended Margin by revision level.
Industrial variances settlement on the correct Revision Level BOM levels and sub-levels should be changed Standard cost & Sales price by Revision level Stock management by Revision level Manage returns at the revision level
6 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
4.1.1.3 Business requirements for Sales and Logistics
At each Revision level change, a deal is made with the OEM. Sekurit can or cannot deliver the remaining stock on the old Revision level. The needs related to the RL Change are
Being able to integrate the DELINS in the SD Scheduling agreements with the minimum of manual workload
Being able to ship to the product on a FIFO Mode considering the agreement with our customer
Stock management at the revision level Billing : Invoice price managed at the revision level
4.1.2 As-Is Situation in the SAP Sekurit Countries
This paragraph describes the situation previous to SGS Avenir V2 go-live and is given as an information for a better understanding of the SG Sekurit Avenir V2 design.
Spain:
One product code (Nomenclatura) is managed for each Revision Level. At each Change of Revision Level, a new Nomenclatura is created.
The Delins are re-treated manually in the EDI box to dispatch the OEM needs on the several Nomenclatura code (Nomenclatura 1 for old revision level & Nomenclatura 2 for new Revision level).
The shipping of the remaining stock on the old revision level is manage manually by dispatching the Delins.
France
One SAP product code is created by OEM Part Number. At each Change of Revision Level (without any change of the OEM Part Number), the Revision level field is updated (From RL1 to RL2): no new SAP code is created.
No Delins re-treatment is needed because only one SAP code is managed The shipping of the remaining stock is ensured by a FIFO mode based on the
batch number (Linked to the production date)
Germany
One SAP product code is managed for each Revision Level. At each Change of Revision Level, a new SAP code is created.
SD Scheduling agreements are re-treated manually to change the link between the OEM Part Number (sent in the Delins) and the SAP Code to be delivered and to make a delivery of correction to match with the cumulated quantity sent in the Delins
7 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
Difficulty to determine to exact cut-off day for updating the SD Scheduling agreements to deliver the maximum of remaining stock on the old revision level.
8 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
4.1.3 To-Be Business Rules for Revision Level Change
4.1.3.1 Business Rule
The main business rule concerning a Revision Level Change will be
“One SAP code by physical Reference at a Revision Level Change”
This means that all the products that physically change will have a new SAP code=> This rule can impact both serial products (FER1 / HLB1) and Prototypes (ZPRO) and ZNOM.
Remark: No distinction will be made between the products of a same plant; in case of a change in a given plant, whatever the first impacted product is, all the HLB1 of this plant will be re-created.
=> For the products that will not physically change (ZPRO, FER1, HLB1 & ZNOM), it will be necessary to update the Revision Level in the Master Data Records (refer to the TBMD03 – Glass Product Creation Process).
4.1.3.2 Revision Level in the Master Data Record
The revision level will be managed in the heading (basic data) of the Material Master Record (refer to the document TBMM02 –Material Master Management).
In case the revision level is not provided by the Sekurit Customer, the value to be completed in the Material Master Record will be the date of CAD files started with a “Z”
Therefore, the format will be: Z-DD/MM/YYYY.
- In case there are several dates in the CAD files; the one of the first file received will be used.- In case the date of the CAD files is not available, the date will be the one of the customer request.
4.1.3.3 Impact on SAP Master Data Records
A new revision level with physical modifications will mandatorily initialize:
The creation of a new SAP FER1/ZPRO (Finished product that will be sent to the customer)
The creation of new intermediary SAP FER1/ZPRO (products sold between Sekurit entities), only if they are impacted by the modification
The creation of the SAP HLB1 related to the new created FER1
The update of the OEM Revision level and Product Level characteristic on intermediary SAP FER1/ZPRO and related HLB1 that are not impacted by the manufacturing changes
9 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
Material genealogy :If the new revision level triggers the creation of a new SAP material, it is recommended to fill in these two information fields (optionnal fields) : - Father material (MARA – ZZPERE) : Material code from whom the considered material is an evolution, in case of a client request of evolution.- Creation reason (MARA-ZZMOTI) : Explanation of the change made on material, which had led to create the considered material (change between the father material and the considered material).These two fields are on Basic Data 1. They are used for reporting and user information. A report is available : ZMGE.
10 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
Business Scenarios for a Revision Level Change
In case of a New Revision Level required by the SGS Customer, 4 different scenarios will be possible according to the plant where the physical modification takes place:
The modification impacts the Glass Plant The modification impacts the Extrusion / Encapsulation Plant The modification impacts the Service Center The modification does not physically impact the product
4.1.3.4 Scenario 1 : the modification impacts the Glass Plant
In this scenario, the modification requested by the Sekurit Customer is located on the production process within the Glass Plant.
As it is the first step of the global production process, this type of modification impacts all the products (HLB1 and FER1) throughout the global production process. Therefore, all these products will be re-created in SAP, with new SAP codes.
Date last update: 06/02/2005 Date printed: 18/4/2023
4.1.3.5 Scenario 2 : the modification impacts the Extrusion / Encapsulation Plant
In this scenario, the modification requested by the Sekurit Customer is located on the production process within the Extrusion / Encapsulation Plant.
As it is an intermediary step of the global production process, this type of modification impacts all the products (HLB1 and FER1) that are manufactured in this plant and the one(s) that will follow. For these products, the SAP objects will be re-created.
Concerning the other products (HLB1 and FER1) produced in the plant(s) located before this step of production the Revision Level will be updated in the SAP Material Master Records.
Date last update: 06/02/2005 Date printed: 18/4/2023
4.1.3.6 Scenario 3 : the modification impacts the Pre-assembly Plant
In this scenario, the modification requested by the Sekurit Customer is located on the production process within the Service Center.
As it is the last step of the global production process, this type of modification impacts only the products (HLB1 and FER1) that are manufactured in this location. For these products, the SAP objects will be re-created.
Concerning the other products (HLB1 and FER1) produced in the plant(s) located before this step of production the Revision Level will be updated in the SAP Material Master Records.
Date last update: 06/02/2005 Date printed: 18/4/2023
4.1.3.7 Scenario 4 : the modification does not physically impact the Product
In this scenario, the modification requested by the Sekurit Customer does not impact physically the product (as for the update of the Sekurit Customer drawings, without any impact on the glass product…)
In that case, as no physical product is modified throughout the manufacturing process, there is no creation of new SAP product.However, it is important to update the Revision Level field in all the Master Data Records impacted.
OEM Revision Level Management Scenario 4: changes does not physically impact the Product
Date last update: 06/02/2005 Date printed: 18/4/2023
4.1.4 Impacts of the To-Be Revision Level management on the Controlling
A) UPDATE OF THE REVISION LEVEL FOR THE NON PHYSICALLY IMPACTED INTERMEDIARY PRODUCTS
To make the Extended Margin calculation more reliable, the change of a revision level of a product (from A to B) will be carried out before the start of the new level production (within the accounting period as much as possible). For these products that are not physically impacted by the new Revision Level, the Controlling impacts will be the followings:
Impacts on the Revenues Allocation by revision level :Products with revision level A are usually sold until the stock is near to 0. However when a product with revision A is still sold, the same product but with revision level B is produced.However, since the revision level has been changed the revenues still generated by a level A product yet impact the level B Profits & Losses. This situation ends when the stock of A level is back to zero or when level is no more delivered to the OEM
Impacts on the Industrial variances Allocation by revision level :The productions variances are calculated at the closing of each period and therefore impact the product with revision level B even if some variances come from the product with revision level A. The consolidated view by revision level is therefore never totally right.
B) CONSOLIDATED MARGIN AT A REVISION LEVEL
To obtain the Consolidated Margin of a product by Revision Level, all the finished or semi-finished products involved in the same production process – from Glass phase to pre-assembly phase _ have to be identified in a unique manner. Therefore the combination of the “Consolidation Code” (controlling characteristics – Refer to TBP Consolidated Margin) and the Revision Level (field of the Material Master Record) will be this common reference between all the involved products.
The following paragraphs give examples of the use of the couple “consolidation code and revision level” depending on different logistic flows.
15 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
4.1.4.1 General Logistic Flows
In the following examples, a specific naked glass (FER1 in Glass Plant) is assigned to only one customer Part Number
Logistic Flow # 1 : A FER1 is used on a single logistic flow
Illustrative Example based on the Logistic Flow # 1 :
Before ChangePlant 1: X1 Plant 2: X2 Service Center: X3
SAP Code 1001133 1001134 1001135Consolidation Code RENJ77--RD01Revision Level 74C
After ChangePlant 1: X1 Plant 2: X2 Service Center: X3
SAP Code 1001133 1001165 1001166Consolidation Code RENJ77--RD01Revision Level 83W
In this example, the couple {Consolidation Code + Revision Level} of all the FER1 and HLB1 composing a physical Customer Part Number (at a given revision level) is both unique and common to these products.
Logistic Flow # 2 : A FER1 is used in different logistic flows but for manufacturing a same physical product
16 18/04/23 - 22:48
Modification = New Revision Level
Unique Reference:RENJ77--RD01
+74C
Unique Reference:RENJ77--RD01
+83W
Plant 1 Service Center OEM
X1’ X1’’…. X1
Plant 2
X1 X2’ X2’’…. X2 X2 X3’ X3’’…. X3 X3 = ref OEM
HLB1 FER1 HLB1 FER1 HLB1 FER1FER1 FER1
Plant 1
Service Center 1
OEM
X1’ X1’’…. X1
Plant 2
X1 X2’ X2’’…. X2 X2 X3’ X3’’…. X3
X3 = ref OEMHLB1 FER1
HLB1 FER1 HLB1 FER1FER1 FER1
Service Center 2Plant 3
X1 X2’ X2’’…. X2 X2 X3’ X3’’…. X3
HLB1 FER1 HLB1 FER1FER1 FER1
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
4.1.4.2 Specific Logistic Flows
In the following examples, a specific naked glass (FER1 in Glass Plant) can be assigned to several customer Part Numbers
Logistic Flow # 1 : A FER1 is used for manufacturing different physical products
Illustrative Example based on the Logistic Flow # 1 :
SAP Code 1001133 1001165 1001166 1001167 1001168Consolidation Code RENJ77--RD01
Rev. Level 83W
In this example, the couple {Consolidation Code + Revision Level} of all the FER1 and HLB1 composing a physical Customer Part Number (at a given revision level) is both unique and common to these products.
It can occur in some particular cases that the Revision Levels of X ’4 and X5 evolve independently. Therefore, this business rule will not be applicable, as described in the following table:
SAP Code 1001133 1001165 1001166 1001167 1001168Consolidation Code RENJ77--RD01
Rev. Level 83W 85Z
17 18/04/23 - 22:48
Unique Reference:RENJ77--RD01
+74C
Unique Reference:RENJ77--RD01
+83W
Service Center 1
OEM
Plant 2
X1 X2’ X2’’…. X2 X2 X3’ X3’’…. X3X3 = ref-1 OEM
HLB1 FER1
HLB1 FER1
FER1
FER1
Plant 3
X1 X4’ X4’’ … X4
HLB1 FER1FER1
Plant 3
X1 X4’ X4’’ … X4
HLB1 FER1FER1
X4 X5’ X5’’…. X5
X5 = ref-2 OEM
Plant 1
X1’ X1’’…. X1
HLB1 FER1
Service Center 2
HLB1 FER1FER1
Modification = New Revision Level
Modification = New Revision Level
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
Logistic Flow # 2 : A FER1 is sold to both internal and external customers
4.1.4.3 Particular case: same intermediary product assigned to several finished products
It can occur that a semi-finished product (HLB1) is assigned to several finished products related to several customer products (with different “Customer Part Numbers” or “Customer Revision Levels”). For instance: a sixlite can be manufactured with or without Antenna, and the HLB1 before the
printing phase could be the same for both versions.
In this case, the “Customer Par Number” and the “Customer Revision Level“ assigned to the intermediary product (on the material master record) will be the ones corresponding to the final product which should have the most important production volume (This particular case should not represent more than 10% of the business cases in order to match with the Controlling Margin Specifications)
Example : The first HLB1 is used in 2 different flows to obtain 2 different Revision Levels
Date last update: 06/02/2005 Date printed: 18/4/2023
19 18/04/23 - 22:48
≠
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
4.1.5 Impacts of the To-Be Revision Level management on the Logistics
4.1.5.1 Objective of the Logistics Department
The main objective of the SGSI Logistics Department is to minimize as much as possible the obsolete stocks when a product changes of revision level.Therefore, the KAM is in charge of negotiating the best agreement with the SGS Customer in order to limit the remaining old revision level stocks to a quantity equivalent to ‘X’ weeks of the usual Customer consumption (‘X’ will be defined by SGSI Logistics Department as an objective to be reached for all the products).
=> The remaining stock is the amount of parts not delivered or not paid by the customer.
A report will be put in place to compare the quantity of obsolete stocks due to Revision Level modifications to the SGSI Objectives of ‘X’ weeks of remaining stocks (refer of chapter 6 of the current document).
4.1.5.2 Process for Revision Level Switch in SAP
The KAM is responsible for negotiating the authorization to send the “old revision level stocks” to the OEM and for defining the cut-off date (date of start-up of OEM production on new revision level).This cut-off date or the agreed quantity of stocks to be shipped is pre-requisite information for activating the use of the new SAP reference.
Moreover, as two SAP codes are managed for the 2 different Revision level the following manual actions are needed to ensure the shipping of the stock of old product to SGS Customer:
Maintain manually the SD Scheduling agreements (to root the “Delins” on the new SAP Code)
Maintain manually the MM Scheduling agreements for the session flows.
Depending on the type of information sent by the Customer on the “Delins”, there are two different possible scenarios:
1. The Customer Part Number included in the “Delins” is the same before and after the Revision Level ModificationE.g.: For Renault or PSA the reference in the Delins will be the same whatever the revision level is.
2. The Customer Part Number included in the “Delins” is different before and after the Revision Level ModificationE.g.: For Volkswagen the reference in the Delins will change when the revision level will evolve.
20 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
Scenario 1: Same Customer Part Number in the “Delins” before and after the Revision Level Modification
In this first scenario, the “Delins” does not contain exploitable information on the Revision Level. Therefore, the “Delins” sent before or after the Revision Level Modification is the same.The process to be followed is described in the following drawing:
Scenario 1: new Revision Level but same reference in the Delins
Shipping RL A RL A then RL B RL B
Delins Ref. 1 Ref. 1 Ref. 1
Detailed Scheduling
Scheduling Agreement RL A
Only RL. A can be produced
Only RL. B can be shipped
RL A RL B RL B
RL A
RL A + RL BStocks taken into account RL A
RL B
RL B
RL A Stock Blocked in CIM+ (batch level)
Stock Level
Req
uir
emen
tsR
eso
urc
es
The Demand Forecaster manually anticipates the
production of RL B
A A A A A A A B B B B B B B
Ref. 1
RL B
RL B
Cut-off date 1
Customer allows RL.B shipping
Cut-off date 2
Customer forbids RL.A shipping
Both RL. A and RL. B be shipped
A A A A A A B B B B B B B B B BB B
Creation of a new Scheduling agreement
Switching date
The “Cut-off date 1” is the one from which the Customer authorizes SGS to send the new Revision Level.
From this date, the Delins always refers to the scheduling agreement of the old Revision Level (RL.A). However the Demand Forecaster will have to manually re-assign the production requirements from RL.A to RL.B (new Revision Level), in order to avoid any production on RL.A.
The “Switching Date” has been calculated by the Logistics Dept and Commercial Dept according to the forecasts and the remaining stocks, in order to have the stocks of RL.A empty before the cut-off date 2.
From the switching date, a new Scheduling Agreement referring to RL.B is created, and the previous one is deactivated. Therefore, the “Delins” is now routed on the New Revision Level (RL.B), and the requirements are generated on this reference.
21 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
On the “Cut-off date 2”, no RL.A could be shipped to the Customer. Therefore, to avoid any error, the RL.A products will have to be blocked for shipping in the Warehouse Management System.
22 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
Scenario 2: New Customer Part Number in the “Delins after the Revision Level Modification
In this second scenario, the Revision Level modification impacts the Customer Part Number into the “Delins”.The process to be followed is described in the following drawing:
Cut-off date 1
Customer allows RL.B shipping
Shipping RL A RL A then RL B RL B
Delins Ref. 1 Ref. 2
Detailed Scheduling
Scheduling Agreement RL A
Only RL. A can be produced
Only RL. B can be shipped
RL A RL B RL B
Stocks taken into account
RL A
RL B
RL B
RL A Stock Blocked in WMS (batch level)
Stock Level
Req
uir
emen
tsR
eso
urc
es
The Demand Forecaster manuall y modifi es the requirements by taking into account current
stock of RL A
A A A A A A A A A A A A A A A A B B B B B B B
Ref. 2
RL B
RL A + B
B BB B B BB BB
Scenario 2: new Revision Level and New reference in the Delins
Cut-off date 2
Customer forbids RL.A shi pping
Creation of a new Scheduling agreement
Both RL. A and RL. B be shipped
The “Cut-off date 1” is the one from which the Customer authorizes SGS to send the new Revision Level.
From this date, a new scheduling agreement referring to the new Revision Level (RL.B) is created. However the Demand Forecaster could manually re-assign the production requirements from RL.B to RL.A in order to empty the remaining RL.A stocks.
On the “Cut-off date 2”, no RL.A could be shipped to the Customer. Therefore, to avoid any error, the RL.A products will have to be blocked for shipping in the Warehouse Management System.
23 18/04/23 - 22:48
To Be ProcessRevision Level Management
document.doc
Version: -3.1Status: -ReleasedAuthor: -CDB
Date last update: 06/02/2005 Date printed: 18/4/2023
4.2 Country specific – Business Rules
Not applicable.
5 Key elements of SAP implementation
Not applicable.
6 Application specific development requirements
A) Material Master Record specificationsThe Customer Revision Level and the Customer Part Number are managed in the header of the material master record, in the following “free text” fields:
CUSTOMER REVISION LEVEL : MARA-BISMT (18 characters) CUSTOMER PART NUMBER : MARA-EXTWG (18 characters)
B) Specific ReportIn order to control the good application of the following rule, a report should be set up:
In case of a new Revision Level on a product, the obsolete stocks should be limited to ‘X’ weeks of usual Customer consumption (‘X’ will be defined by SGSI Logistics Department).
The remaining stock of each product will be compared to the ‘X’ weeks of normal consumptions (sales).
