aco_mm_tbp_25_logistic flow and master data creation.v2.0

To Be ProcessLogistic Flow & Master Data creation

document.doc

Version: -2.0Status: -ReleasedAuthor: -CDB

Date last update: 17/10/2003 Date printed:

Table of content

1 DOCUMENT UPDATES AND VALIDATIONS................................................................................................2

2 SCOPE............................................................................................................................................................... 3

2.1 PROCESS SCOPE DESCRIPTION........................................................................................................................ 32.2 APPLICATION ARCHITECTURE (GLOBAL).........................................................................................................32.3 CROSS REFERENCES....................................................................................................................................... 4

3 PROCESS.......................................................................................................................................................... 5

3.1 CORE MODEL - PROCESS FLOW....................................................................................................................... 53.2 COUNTRY SPECIFIC - PROCESS FLOW.............................................................................................................. 5

4 BUSINESS RULES............................................................................................................................................ 6

4.1 CORE MODEL – MASTER DATA LAYOUT........................................................................................................ 64.2 CORE MODEL – MASTER DATA PROCESS CREATION IN SAP...........................................................................7

4.2.1 Creation of a Strategic Components / Prelaminat / Re-extruded PVB...................................................84.2.2 Creation of Vendors........................................................................................................................... 114.2.3 Creation of Purchasing Master Data for STRA...................................................................................134.2.4 Creation of finished glass products (FER1 / ZPRO)............................................................................144.2.5 Creation of Purchasing, Sales and Packaging Master Data for FER1 / ZPRO....................................144.2.6 Creation of HLB1 / ZHLB and Production Planning Master Data......................................................174.2.7 Cost Calculation, Run Schedule Header and Cost Collector...............................................................184.2.8 Validation of the Material Master Records.........................................................................................18

4.3 COUNTRY SPECIFIC – BUSINESS RULES........................................................................................................19

5 KEY ELEMENTS OF SAP IMPLEMENTATION........................................................................................19

5.1 COUNTRY SPECIFIC – KEY ELEMENTS OF SAP IMPLEMENTATION..................................................................195.2 SUMMARY.................................................................................................................................................. 19

6 ORGANIZATIONAL ROLES AND IMPACTS.............................................................................................20

6.1 OEM DATA SPECIALIST.............................................................................................................................. 206.1.1 Role.................................................................................................................................................... 206.1.2 Location............................................................................................................................................. 20

6.2 LOCAL DATA SPECIALIST............................................................................................................................ 22

7 APPLICATION SPECIFIC DEVELOPMENT REQUIREMENTS..............................................................22

8 KEY VOLUME & PERFORMANCE INDICATORS...................................................................................22

9 Added value for the Business and economical considerations............................................................................22

1 18/04/23 - 22:48


document.doc



1 Document updates and validationsUpdates

Date Version Author Comment04/11/02 V1 CDB Document creation12/11/02 V1.1 CDB Modification of Rack Type creation process19/11/02 V1.2 CDB Modifications based on KU comments06/02/03 V1.3 CDB Update of ZHLB creation process17/10/03 V2.0 CDB Update of document after Spanish Go-Live

ValidationsDate Version Validation

Resp.Comment

19/11/02 V1.2 KU Validation of the To Be by the KU06/02/03 V1.3 C. Gemayel Validation of the To Be modification

2 18/04/23 - 22:48


document.doc



2 Scope

2.1 Process scope description

The subject of this procedure is the description of the Master Data maintenance process in SAP, including the management rules to be applied for the Creation and the Modification of these Data in the system.

The Master Data within the scope of this To-Be-Process are the following:

MM (Material Management) Master data : Material Master Records Purchasing Info Records Source Lists Quota Arrangements Vendors

PP (Production Planning) Master data : Bill Of Materials (BOM) Routings Production Versions Run Schedule Headers Cost Collectors (Controlling oriented object)

Packaging Master data : Rack Types Packaging Instructions

SD (Sales & Distribution) data : Customers1

Customer Material Info Records

This document does not aim at detailing the content or the technical description of these Master Data in SAP. The reader could refer to other To-Be-Processes where those information will be detailed.

This To-Be-Process is defined for the perimeter of Saint-Gobain Sekurit Avenir V2 Project.

2.2 Application architecture (global)

Not Relevant.

1 To Be Confirmed and Detailed by the Change Management team if it is included in SG Sekurit AvennirV2 project scope.

3 18/04/23 - 22:48


document.doc



2.3 Cross references

The following documents will be referenced all along the current To-Be-Process:

TBMD01 Product characteristicsTBMD02 Revision LevelTBMD03 Glass Product Creation ProcessTBMD04 Pricing ProcedureTBMM02 Material Master ManagementTBMM03 Vendor Master DataTBMM04 Purchasing Master DataTBPP02 PP Master Data - Define Rate Routing structureTBPP03 PP Master Data - Define BOM structureTBPP04 PP Master Data - Define other Repetitive Master DataTBIN04 Rack ManagementTBSD02 Customer Info RecordTBSD03 Customer Master DataTBCO05 Budget elaboration

4 18/04/23 - 22:48


document.doc



3 Process

3.1 Core model - process flow

All along its life, a glass manufactured product will pass through different phases (Development Phase and Mass Production phase) and different physical states (prototypes / initial samples and serial products). For each of these phases and each of these physical states, some master data will have to be created in SAP.The following chart specifies which kind of Master Data could be required for each evolution step.

Master Data all along Glass Products Lifecycle

Prototypes creation

SAP Master Data that could be required for the Prototype creation :

ZPRO (Master Record) NLAG (Master Record) Routings Vendor Customers

Development phase Mass Production

Prototypes creation

Serial Product creations

Prototypes creation

Prototypes creation



SAP Master Data that could be required for the Serial Product creation :

FER1 (Master Record) HLB1 (Master Record) STRA (Master Record) ZHLB (Master Record) BOM Routings Production Versions Run Schedule Header Cost Collector Purchasing Info Records Source Lists Quota Arrangements Client Material Info Records Vendor Customers

SOP Evolutions of the productDevelopment

The different creation process for all these Master Data are described in the paragraph “Business Rules” of the current document.

3.2 Country specific - process flow

Not Relevant.

5 18/04/23 - 22:48


document.doc



4 Business Rules

4.1 Core model – Master Data Layout

The following flowchart describes how the different SAP Master Data are imbedded around the creation of a Serial Glass Product (“FER1”).

8

VENDOR(SGSx)

FER1

Source List

Purchasing Info Record

MM. Sch. Agreement

Master Data in SAPMaster Data in SAP

CUSTOMERSold-to

Cust. Mat. Info Record

SD. Sch. Agreement

Rack Type

Packaging Instruction

Customer Packaging Instruction

Production Version

HLB1STRA

Routing BOM

Run Schedule Header

Quota arrangement

VENDOR(Ext.)

Source List

Purchasing Info Record

MM. Sch. Agreement

MM Master Data

MM Master Data

Packaging Master Data

SD Master Data

PP Master Data

Out of

scope

Out of

scope

The flowchart for the creation of a prototype (“ZPRO”) would be built on the same basis, but with the following specificities:

No semi-finished products (“HLB1”) are managed with the prototypes, No Strategic components (“STRA”) are supposed to be created. If some new components

are required for the development phase, they could be purchased with generic materials (“NLAG”).

As no BOM will be managed with the prototypes, neither Production Version, nor Run Schedule Header will be created.

6 18/04/23 - 22:48


document.doc



4.2 Core model – Master Data Process Creation in SAP

The different Master Data detailed in the previous chart can be created at international level for a part, and at local level (plants or country) for the other part.

The main steps for the creation of a serial Glass Product in SAP are detailed in the following table:

1- Part creation template initialization Project Leader -

2 - Initialization of the creation-update Template for FER1 ZPRO OEM Data Specialist -

2.1 Data collection Local Data Specialist -

3 - Consolidation and check of the product datas OEM Data Specialist -

4 -

OEM Data Specialist MM01/MMSC

5 - Customer Material Info record (CMIR) OEM Data Specialist VD51

6 - Initialization of the local template Local Data Specialist -

6.1 - MRP views (FER1) Local Logistics MM01

6.2 - Creation of the HLB1 Local Logistics MM01

6.3 - Creation of the ZHLB (cut PVB) Local Logistics MM01

6.4 - BOMs (Only for produced FER1 and HLB1/ZHLB) Local Logistics CS01

6.5 - Routings (Only for produced FER1 and HLB1/ZHLB ) Local Logistics CA21

6.6 - Other variable costs set in the routings Controlling CA22

6.7 - Production Versions (Only for produced FER1 and HLB1/ZHLB ) Local Logistics MM02

6.8 - Quotas Regulation (optional) Local Logistics MEQ1/MEQ4/MEQM

6.8.1 - BOMs, Routings, Prod. Versions. (Optional) Controlling CS01/CA21/MM02

6.8.2 - Change of the blockage status (from Z2 to Z1) Controlling MM02

6.8.3 - Calculation CCR (Only for FER1 and HLB1/ZHLB) Controlling CK11

6.8.4 - Update of the standard cost Controlling CK14

6.8.5 - Change of the status of the BOMs and Routings Controlling CS02/CA22

6.8.6 - Repetitive orders (Only for FER1 and HLB1/ZHLB1) Controlling MF01

6.9 - Packaging Instructions (for all the FER1/HLB1) Local Logistics ZPOP1/ZPOP2

6.10 - Customer Packaging Instructions Local Logistics ZPOF1/ZPOF2

6.11 - Subload of Packaging Local Logistics

6.12 -Local Logistics ME11/ME1L/ME1M

6.13 - Scheduling Agreement (for all procured FER1) Local Logistics ME31L/ME32L/ME38

6.14 - Source List (for all procured FER1) Local Logistics ME01/ME0M

7 - Checking of the Master D ata Local Data Specialist -

8 - Unblocking of the FER1 and HLB1/ZHLB Local Data Specialist MM02

9 - Product creation notification OEM Data Specialist -

Main Transactions

Creation of FER1 (all the views except MRP): - Basic Data - Classification (characteristics) - Sales - Purchasing - Storage - Accounting - Costing

Purchasing Info Record (only for procured FER1 in Intercompany flows

Tasks Responsibles

NB: The Master Data related to the Strategic Material are not in the previous table, but will be detailed in the following paragraphs.

7 18/04/23 - 22:48


document.doc



4.2.1 Creation of a Strategic Components / Prelaminat / Re-extruded PVB

The Strategic components are represented in SAP with the Material Type “STRA”. The Prelaminat or Re-extruded PVB are represented in SAP with the Material Type “ZHLB

These products can be managed with different creation processes depending on the type of components to be created or maintained.

4.2.1.1 Strategic components other than Raw Glass Products and Prelaminat / Re-extruded PVB

A strategic component is provided by a Strategic Vendor. These products are managed by a central purchasing organization either at an international level (SGS international purchasing department) or at a country level (one person assigned by country). For more details on the products managed at international level or Country level, refer to the TBMM02 – Material Master Management

CREATION OF A STRA OR ZHLB The following chart details the creation procedure for the STRA:

8 18/04/23 - 22:48

Product Creation Process

STRA CreationProduction

New articleneeded

Purchasing department

Is the new article usefull ? STOPBlok at alocal level

No

Yes

Purchasing departmentLocal data Local data

Send of a « creationfile »

Central Creation of Article

CommonData

Yes

No

New article Created

LOCAL

CENTRAL

1

2

3

4

5

Article already exist ? Extension of the article


document.doc



1) ANALYSIS OF THE NEW PRODUCT REQUIREMENT

Responsible : Local Purchasing Department (LPD) Trigger : A new component is required for some recurring production purposes Action Items : following the request of the Production Department, the LPD checks

if this product already exists on the system and if the creation is really required2. Output : In case the component exists on other SG plants, the LPD has to ask for

the opening of this material master on his plant (to the Central Purchasing Organization). In case the product does not exist, the LPD initializes a Part Creation Request

2) DATA COLLECTION FOR THE PART CREATION

Responsible : Local Purchasing Department (LPD) Trigger : A Part Creation Request has been initialized Action Items : the Local Purchasing Department fills-in a “Part Creation Form” by

collecting all the required local data for the creation of the STRA. Output : the “Part Creation Form” has been filled-in, and sent to the central

purchasing organization.

3) CHECK OF THE PART CREATION FORM

Responsible : Central Purchasing Organization Trigger : The creation request has been initialized and transmitted to the Central

Purchasing Organization. Action Items : The Central Purchasing Organization checks the data:

o If data look wrong or uncompleted, the form is returned to the sender for completion of correction,

o If the part already exists in the system, the existing material master is extended on the new plant,

o If the form is completed, the new product can be created. Lead-time : 1 working day Output : the product can be created or modified

4) CREATION OF THE MATERIAL MASTER RECORD

Responsible : Central Purchasing Organization Trigger : A new product has to be created. Action Items : creation of all the required views of the master data record in SAP. It

can occur that the Central Purchasing Organization has to modify some data collected in the “Part Creation Form”.

Lead-time : 3 working days Output : the product has been created in SAP.

2 The products used during the development or homologation phases will be generic products (NLAG)

9 18/04/23 - 22:48


document.doc



4) COMMUNICATION ON THE CREATION OF THE NEW PART

Responsible : Central Purchasing Organization Trigger : A new product has been created. Action Items : the Central Purchasing Organization sends an email to the requester

with the SAP code of the new product. Lead-time : 1 working day Output : the product is available for the production department.

MAINTENANCE OF A STRA OR ZHLB The modification of an existing STRA will be done with the same procedure than for the creation of a new one. In this case, the “Part Creation Form” will contain the reference of the SAP code to be modified, and the type of modification to be carried-out.The lead-time for the modification of a STRA will not overstep 2 working days.

The different maintenance operations are the followings: Extension of an existing product on a new plant Modification of specific plant data on the existing product

DELETION OF A STRA OR ZHLB The STRA can be flagged for deletion in two different manners:

One shot deletion : The same Form than for the Creation Process can be used to ask for the deletion of an existing STRA. The form will contain the reference of the SAP code to be flagged for deletion, the related plant, and the reason for such a deletion.

Deletion Campaign : an annual report of the non-used part will be sent once a year to the different purchasers that will highlight the ones to be flagged.

The lead-time to flag a STRA for deletion will not overstep 2 working days.

4.2.1.2 Raw Glass Products

The Raw Glass Products are created and maintained by the same central organization than the other STRA (International Purchasing Department).

Except specific requirements from SG Sekurit Customer or plant constraints, the raw glass products are exclusively those mentioned in the Official Glass Branch Catalog of Saint-Gobain.

Once a year, an annual release of this catalog is published and the existing Glass Products will have to be updated or some new Products will have to be created.Otherwise, all the other maintenance operations will have to be done in accordance with this catalog.

For the specific requirements mentioned here before and not managed in the Catalog, the Local Logistics Department will be in charge of the Creation / Maintenance of the Material in SAP.

10 18/04/23 - 22:48


document.doc



4.2.2 Creation of Vendors

There are different types of Vendors depending on the type of purchased products:- Strategic vendors for Raw Glass- Strategic vendors for components used in the BOM (as defined in the “TBMM02:

Material Master Management”)- Vendors for Manufactured Glass products (external or group)- Vendors for Transports,- Other vendors.

4.2.2.1 Strategic vendors for Raw Glass

The Strategic Vendor for Raw glass are created and maintained by the same purchasing entity (belonging to SG Sekurit international Purchasing Department) that creates the Raw Glass Products (STRA).

4.2.2.2 Strategic vendors for Strategic Components other than raw glass

A strategic vendor provides a STRA material. The vendor negotiations have been made by the Pilot Purchaser (PP), who is in charge of the product family of the vendor. The PP will validate the entry of a new vendor in his panel The creation of a vendor will be central and at an International level.

CREATION OF A STRATEGIC VENDOR The following chart details the creation procedure for the strategic vendor:

11 18/04/23 - 22:48

Supplier Creation Process

Strategic SupplierCreation

STRA article provide by a newsupplier

Purchasing department

Use this Supplier ? STOPBlok at alocal levelNo

Yes

Purchasing departmentLocal data Local data

Send of a « creationfile »

Central Creation of Supplier

CommonData

Yes

No

New Supplier Created

LOCAL

CENTRAL

1

2

3

4

5

Pilot Buyer Agreement Creation Canceled

New supplierSupplier alreadyexist in another

division

Extension to this division


document.doc



1) ANALYSIS OF THE NEW VENDOR REQUIREMENT

Responsible : Local Purchasing Department (LPD) Trigger : Need of a new vendor for a STRA Material. A new Vendor could be

required for customer specifications, development and/or logistics needs, suppliers’ competition…

Action Items : The LPD will check if no vendor already exists, and if it will not be more interesting to use an existing vendor. If an vendor already exists in one plant, he will extend it on another plant

Output : The creation of a new vendor seems to be necessary

2) DATA COLLECTION FOR THE VENDOR CREATION

Responsible : L.P.D. Trigger : When a creation demand has to be made in central Actions : A “Vendor form” has to be initialized. This form contains all the information

required for the new vendor creation. So, the local data have to be collected in order to fill this form. These data will be controlled by the PP.

Output : The creation of the vendor form is filled-in and sent to the central purchasing organization

3) VENDOR CONTROL

Responsible : Pilot Purchaser. Trigger : The Pilot Purchaser receives a creation form for a new vendor from the

central purchasing organization Actions : The Pilot Purchaser will control if some negotiation has been done with

this vendor. If there are some errors in the form or missing values, he will contact the ordering plant for correction.

Lead -time: 5 working days Output : The vendor can be created or the creation is cancelled

4) CREATION OF THE VENDOR MASTER DATA

Responsible : Central Purchasing Organisation Trigger : Agreement from the Pilot Purchaser. Actions: The Central Purchasing Organisation checks that no vendor exists. If there is

one, he extends it to another plant. Otherwise, he creates all the different views of the vendor in SAP: General, Control Data, Accounting… Some information given by the intermediary “creation form” could be corrected under the responsibility of the Central Purchasing Organisation.

Lead-time: 3 working days Result : Creation of the vendor

3) COMMUNICATION ON THE CREATION OF THE NEW VENDOR

Responsible : Central Purchasing Organisation Trigger : A new Vendor has been created Actions : the Central Purchasing Organization sends an email to the requester with the

SAP code of the new Vendor Lead-time : 1 working day Output : the Vendor is available in the system.

12 18/04/23 - 22:48


document.doc



4.2.2.3 Vendors for Manufactured Glass products and Transports

For the logistics vendors creation / maintenance (Transport and Glass), a person is assigned in each country purchasing organization.In any case, before any creation of a new Vendor, each country should take care of the international database, i.e. should check whether vendors are already existing and/or used by other countries.

4.2.2.4 Other Vendors

Each country purchasing organization is responsible for its own Vendors Master Data creation and maintenance.In any case, before any creation of a new Vendor, each country should take care of the international database, i.e. should check whether vendors are already existing and/or used by other countries.

4.2.3 Creation of Purchasing Master Data for STRA

The purchasing Master Data regroups the following Master Data: Purchasing Info Record Source List Quota Arrangement

The prerequisites for the creation of these Purchasing Master Data are that both Master Data Records and Vendors have already been created.

As for the Vendors, the process for the creation/maintenance of the Purchasing Master Data will differ depending on the type of purchased strategic products:

- Purchasing Master Data for Raw Glass- Purchasing Master Data for components used in the BOM (a detailed list is defined in the

“TBMM02: Material Master Management”)

4.2.3.1 Purchasing Master Data for Raw Glass

The process for the Creation / Maintenance of the Purchasing Master Data related to the Raw Glass is the same than for the Vendors (refer to Vendor paragraph).

4.2.3.2 Purchasing Master Data for components used in the BOM

The process for the Creation / Maintenance of the Purchasing Info Record related to the components used in the BOM will be the same than for the Vendors (refer to Vendor paragraph).

The Creation / Maintenance of the Source List and the Quota Arrangement will be managed by the Local Purchasing Dept.

13 18/04/23 - 22:48


document.doc



4.2.4 Creation of finished glass products (FER1 / ZPRO)

The creation of a new finished glass product (FER1 or ZPRO) is issued from SG Sekurit Customer requirements, in the conditions as defined in the To-Be-Process TBMD03 - Glass Product Creation Process.

4.2.4.1 Creation process

Responsible : The OEM Data Specialist and Local Data Specialist Related Master Data : all related FER1 or ZPRO throughout the production process Action : based on the data stored in a “data collection template” (refer to TBMD03 - Glass

Product Creation Process for details on this template), the OEM Data Specialist will create the new material master records (all required views, excepted MRP ones). If some products do not physically changes, but need to be maintained because of a new Revision Level or a new Customer Reference (refer to the document TBMD02 – Revision Level), the OEM Data Specialist will also update theses data in the material master records. Finally, the Local data Specialist will be in charge of creating the MRP views of the FER&/ZPRO.

4.2.4.2 Maintenance process

All over its life and due to different circumstances the Material Master Records can be subject to various maintenance operations. Depending on the material type and the views that are affected by the modifications, the people in charge of the maintenance are:

ZPRO : Basic Data views: OEM Data Specialist Classification: OEM Data Specialist Sales views: OEM Data Specialist Purchasing view: OEM Data Specialist Storage view: OEM Data Specialist Accounting view: OEM Data Specialist MRP views: Central Planners

FER1 : Basic Data views: OEM Data Specialist Classification: OEM Data Specialist Sales views: OEM Data Specialist Purchasing view: OEM Data Specialist Storage view: OEM Data Specialist Accounting view: OEM Data Specialist Costing view: OEM Data Specialist MRP views: Central Planners

14 18/04/23 - 22:48


document.doc



4.2.5 Creation of Purchasing, Sales and Packaging Master Data for FER1 / ZPRO

4.2.5.1 Purchasing Master Data

The purchasing Master Data regroups the following Master Data: Purchasing Info Record Source List Quota Arrangement

The prerequisites for the creation of these Purchasing Master Data are that both Master Data Records (FER1) and Vendors have already been created.

The creation process will be the following: Responsible : The Local Logistics or Country Purchasing Department for importations Related Master Data : all the FER1 purchased (to internal or external Vendors) Action : Once the FER1 have been created (during the previous step), the responsible can

create the Purchasing Master Data

The Responsible mentioned here above will be also in charge to perform the maintenance operations for these Purchasing Master Data.

15 18/04/23 - 22:48


document.doc



4.2.5.2 Sales & Distribution Master Data

The prerequisites for the creation of the Customer Info Record are that both the Customer “Sold-To-Party” and the Master Data Records (FER1) have already been created.

The creation process will be the following: Responsible : The OEM Data Specialist Related Master Data : all the FER1 sold (to internal or external Customers) Action : Once the FER1 have been created (during the previous step), and assuming that

the Customers “Sold-To-Party” already exists, the OEM Data Specialist is in charge of creating the Customer Info Records.

The OEM Data Specialist will be also in charge to perform the maintenance operations for the Customer Info Records.

Remark: The OEM Data Specialist could be also in charge of creating and maintaining the Customer “Ship-to-Party” and the Customer “Sold-To-Party” Master Data3.

4.2.5.3 Packaging Master Data

The Packaging Master Data regroups the following Master Data: Customer Packaging Instructions Packaging Instructions Sub-loads of Packaging Rack Types

The prerequisites for the creation of the Packaging Master Data are that both the Customer “Ship-To-Party” and the Master Data Records (FER1, HLB1 and ZHLB) have already been created.

The creation process will be the following: Responsible : The Local Logistics departments Related Master Data : all the FER1, HLB1 and ZHLB sold (to internal or external

Customers) and produced Action : Once the materials have been created (during the previous step), and assuming

that the Customers “Ship-To-Party” already exists, the Local Logistics is in charge of creating the Packaging Master Data.

The Local Logistics departments will be also in charge to perform the maintenance operations for the Packaging Master Data.

3 To be Confirmed and Detailed by the Change Management team if it is included in SG Sekurit AvennirV2 project scope

16 18/04/23 - 22:48


document.doc



4.2.6 Creation of HLB1 / ZHLB and Production Planning Master Data

Once the FER1 or ZPRO have been created, the OEM Data Specialist informs the different Local Data Specialists of the Plants where the products will be manufactured. The Local Data Specialist will be in charge of monitoring the good progress of the master data creation all along the process.

4.2.6.1 HLB1/ZHLB Creation process

Responsible : The Local Logistics Related Master Data : all HLB1/ZHLB (for cut PVB) in each involved plant and for all

possible production circuits Action : The local Logistics is in charge of creating the different HLB1 and ZHLB

(based on the related FER1).

As for the FER1, the HLB1/ZHLB can be subjected to various maintenance operations.Depending on the views that are affected by the modifications, the people in charge of the maintenance are:

Basic Data views: OEM Data Specialist Classification: OEM Data Specialist Storage view: Local Logistics Accounting view: Local Logistics Costing view: Local Logistics MRP views: Local Logistics

Remark: No HLB1 will be created for a ZPRO

4.2.6.2 BOM, Routings, Production Versions Creation Process

Responsible : The Local Logistics Department with the contribution of the Local Controlling Related Master Data : all HLB1 / ZHLB / FER1 or ZPRO in each involved plant and for all

possible production circuits Action : First of all, BOM, Routings and Production Versions will be created in each plant

(for Controlling and Planning purpose). Some specific data of the Routing should be provided by the Local Controlling (“Other Variable Cost", “FCA” and “FGU”).

The Local Logistics Department will be also in charge to perform the maintenance operations for these Master Data.

Remark: Only routings will be created for a ZPRO. No BOM & Production Version will be required

17 18/04/23 - 22:48


document.doc



4.2.6.3 Specificities of the Budget Phase

Once a year, during the budget calculation phase, the BOM, Routings and Standard Costs have to be updated for all the products assigned to the new Budget.The process will be the following:

The Local Planning Department (with the contribution of the Local Controlling) updates all the BOM and Routings

For the products subjected to multi-circuits, the Local Controlling Department creates specific “budget BOM” and “budget Routing” resulting from the different circuits, that will be only used for the standard cost calculation.

Then, the Local Controlling Department performs the standard cost calculation for each of the products within the new budget scope

Finally, the SGS Center Of Competencies, on the Behalf of SGSI Controlling Department, is in charge of running a batch that will update the standard costs of all the related products.

All the manufactured glass products (ZPRO, FER1 and HLB1) only created for the budget purpose will support the BUDGET classification. In case these products will be released for production, the BUDGET classification should be updated.

For more details on this budget calculation phase, refer to TBCO05 - Budget Elaboration

4.2.7 Cost Calculation, Run Schedule Header and Cost Collector

Responsible : The Local Controlling Related Master Data : all HLB1 / ZHLB / FER1 in each involved plant. Action : Once the Production Versions are created, the Local Controlling has to calculate

and update the standard costs for each product, and then create the Run Schedule Header (the Cost Collector will be automatically initialized)

Remark: No Cost Calculation will be carried-out for a ZPRO

4.2.8 Validation of the Material Master Records

Once the Standard Costs have been released, the Local Controlling has to inform on a written order the Logistic Department.

Responsible : Local Data Specialist Related Master Data : all SAP products at a plant level Action : Once he has verified following SAP objects and operations:

MRPs’ views, BOMs, Routings and Production Version, Cost calculation and standard cost update,

The Local Data Specialist releases the FER1 and HLB1/ZHLB (or the ZPRO) for production.Finally, the Local Data Specialist has to inform the OEM data Specialist of the products availability in the SAP system.

18 18/04/23 - 22:48


document.doc



4.3 Country specific – Business Rules

Not applicable.

5 Key elements of SAP implementation

The technical definitions of the different master data mentioned in the current document are detailed in the To-Be-Processes referenced hereafter:

MM Master data The rules for the Master Data Records are defined in the To-Be TBMM02 - Material

Master Management The rules for the Purchasing Info Records, Source Lists and Quota Arrangements

are defined in the To-Be TBMM04 - Purchasing Master Data The rules for the Vendors are detailed in the To-Be TBMM03 - Vendor Master Data

PP (Production Planning) Master data : The BOM are defined in the To-Be TBPP03 - PP Master Data - Define BOM

structure The Routings are defined in the To-Be TBPP02 - PP Master Data - Define Rate

Routing Structure The Production Versions, Run Schedule Headers are defined and Cost Collectors

(partially) are detailed in the To-Be TBPP04 - PP Master Data - Define other Repetitive Master Data

Packaging Master data : The Rack Types and Packaging Instructions are defined in the To-Be TBIN04 -

Rack Management

SD (Sales & Distribution) data : The Customers are defined in the To-Be TBSD03 - Customer Master Data Customer Info Records are defined in the To-Be TBSD02 - Customer Info Record

5.1 Country specific – Key elements of SAP implementation

Not applicable.

5.2 Summary

Not applicable.

19 18/04/23 - 22:48


document.doc



6 Organizational roles and impacts

6.1 OEM Data Specialist

6.1.1 Role

According to the procedure of creation for the Master Data described in this To-Be-Process and in the document TBMD03 – Glass Product Creation Process, the OEM Data Specialist is in charge of the following actions:

Initialization of the procedure and supervision of the process of Data Collection among the involved plants

Consolidating the collected Data Creating / maintaining the following objects in the SAP system: ZNOM, FER1, ZPRO,

Customer Info Records and Customer Packaging Instructions Notifying the New Product’s Creation in SAP Managing the rules of blockage, blockage’s release and deletion on the created products

6.1.2 Location

The OEM Data Specialist is in charge of managing on international basis the Creation Process of the products belonging to the customers for which he is responsible. In practice it means that there is just one OEM Data Specialist per customer, covering all the Saint-Gobain Sekurit Companies.

The OEM Data Specialists will be physically based in France, Germany and Spain.

The following list represents the allocation of OEM Data Specialist by customer / country. The OEM Data Specialist is responsible for the customer data maintenance at an international level:

20 18/04/23 - 22:48


document.doc



21 18/04/23 - 22:48

Car BrandOEM Data

Specialist CoutryALFA ROMEO FranceALPINE FranceARVINMERITOR FranceAUDI GermanyAUSTIN GermanyBENTLEY GermanyBMW GermanyCHRYSLER GermanyCITROEN FranceDAEWOO GermanyDAIMLER GermanyFERRARI FranceFIAT FranceFORD GermanyGENERAL MOTORS GermanyHONDA FranceINALFA FranceISUZU GermanyIVECO FranceJAGUAR GermanyKARMANN GermanyLADA GermanyLANCIA FranceLAND ROVER GermanyLOTUS GermanyMASERATI FranceMAZDA GermanyMC LAREN GermanyMCC SMART GermanyMERCEDES GermanyMG ROVER GermanyMINI COOPER GermanyMITSUBISHI GermanyNEDCAR GermanyNISSAN SpainOPEL GermanyPEUGEOT FrancePORSCHE GermanyRENAULT FranceROLLS ROYCE GermanySAAB GermanySEAT SpainSKODA GermanySUBARU FranceSUZUKI SpainTOYOTA FranceTRIUMPH GermanyVAUXHALL GermanyVOLKSWAGEN GermanyVOLVO GermanyWEBASTO France


document.doc



6.2 Local Data Specialist

The Local Data Specialist will be the single point of contact of the OEM Data Specialist at the plant level.

He is in charge of the following actions:

Collecting, monitoring and tracking the data required for products creation at the plant level

Managing the HLB1 creation Managing the update of the MRPs’ view of FER1, ZPRO and HLB1/ZHLB (at a plant

level), and the creation of the BOMs, Routings, Production Versions, and Run Schedule Headers

Checking that all SAP products have been created (at a plant level) Releasing the blockage for production of the created FER1 and HLB1 (after written order

from Local Controlling or Project Leader, as detailed in the paragraph “Rules on Blocking products and Flagging products for deletion” of the document TBMD03 – Glass Product Creation Process).

Notifying the New Product Creation in SAP to the OEM data Specialist

7 Application specific development requirements

Not relevant.Refer to other mentioned To-Be-Process for details on the specific development related to Master Data.

8 Key volume & performance indicators

Not relevant.

9 Added value for the Business and economical considerations

Not relevant.

22 18/04/23 - 22:48

aco_mm_tbp_25_logistic flow and master data creation.v2.0

Documents