ACO MM TBP 45 Process Internal Moves- V3.1

To Be ProcessInternal movements

document.doc

Version: -2Status: -ReleasedAuthor: -GKR

Date last update: 18/4/2023 Date printed: 18/4/2023

Table of content

1 DOCUMENT UPDATES AND VALIDATIONS................................................................................................3

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

2.1 PROCESS SCOPE DESCRIPTION........................................................................................................................ 32.1.1 General description.............................................................................................................................. 32.1.2 Position in Process Map....................................................................................................................... 42.1.3 Process pre-requisites.......................................................................................................................... 42.1.4 Process objectives................................................................................................................................ 42.1.5 Limits................................................................................................................................................... 52.1.6 Transition period.................................................................................................................................. 5

2.2 APPLICATION ARCHITECTURE (GLOBAL).........................................................................................................52.3 CROSS REFERENCES....................................................................................................................................... 5

2.3.1 To Be Processes................................................................................................................................... 52.3.2 Other related documents....................................................................................................................... 5

3 BUSINESS RULES............................................................................................................................................ 6

3.1 CORE MODEL – BUSINESS RULES................................................................................................................... 63.1.1 Physical and logical warehouse structure.............................................................................................63.1.2 Putaway strategy.................................................................................................................................. 63.1.3 Picking strategy.................................................................................................................................... 73.1.4 Change of material code....................................................................................................................... 73.1.5 Repackaging......................................................................................................................................... 73.1.6 Internal stocks movements and transfers...............................................................................................73.1.7 Drying time management...................................................................................................................... 83.1.8 Scrapping............................................................................................................................................. 83.1.9 Traceability.......................................................................................................................................... 9

3.2 COUNTRY OR CUSTOMER SPECIFIC – BUSINESS RULES....................................................................................9

4 PROCESS........................................................................................................................................................ 10

4.1 CORE MODEL - PROCESS FLOW AND DESCRIPTION.........................................................................................104.1.1 Warehouse logical structure............................................................................................................... 104.1.2 Warehouse physical structure............................................................................................................. 124.1.3 Block / Unblock storage bin................................................................................................................ 144.1.4 Process flow : product change status..................................................................................................164.1.5 Market management........................................................................................................................... 194.1.6 Process flow : change of market......................................................................................................... 214.1.7 Material code change......................................................................................................................... 244.1.8 Process flow : stock transfer............................................................................................................... 264.1.9 Process flow : Transfer of material between racks (repackaging).......................................................294.1.10 Process flow : Logistics scrapping......................................................................................................324.1.11 General warehouse scrap................................................................................................................... 344.1.12 Inter-buildings transfers..................................................................................................................... 364.1.13 Put away strategy............................................................................................................................... 384.1.14 Picking strategy.................................................................................................................................. 494.1.15 Transformation movements in Service Centers....................................................................................524.1.16 Transfer of components from general warehouse to production storage location................................534.1.17 Drying time management.................................................................................................................... 544.1.18 Traceability........................................................................................................................................ 55

4.2 COUNTRY OR CUSTOMER SPECIFIC - PROCESS FLOW AND DESCRIPTION..........................................................674.2.1 Country specific process Flow – country-1.........................................................................................674.2.2 Country specific process Flow – country-2.........................................................................................67

5 KEY ELEMENTS OF SYSTEM IMPLEMENTATION...............................................................................67

5.1 CORE MODEL – KEY ELEMENTS OF SYSTEM IMPLEMENTATION.....................................................................67

1 18/04/23 - 22:50


document.doc



5.1.1 Change of material code initiated by CIM+........................................................................................675.1.2 Cycle counting.................................................................................................................................... 675.1.3 Scrapping in CIM+............................................................................................................................. 685.1.4 Logistics scrap of components not managed in CIM+.........................................................................695.1.5 Change of market initiated by CIM+..................................................................................................705.1.6 Transfer of components to production zone before consumption..........................................................705.1.7 Putaway and stock transfer initiated by CIM+....................................................................................715.1.8 Stock transfer of finished products initiated by CIM+.........................................................................715.1.9 Stock transfer of glass, PVB / PET initiated by CIM+.........................................................................725.1.10 Change of material status initiated by CIM+......................................................................................725.1.11 Consumption declaration in CIM+.....................................................................................................735.1.12 Consumption declaration in SAP........................................................................................................ 73

5.2 SUMMARY.................................................................................................................................................. 73

6 ORGANIZATIONAL ROLES AND IMPACTS.............................................................................................73

7 APPLICATION SPECIFIC DEVELOPMENT REQUIREMENTS..............................................................73

2 18/04/23 - 22:50


document.doc



1 Document updates and validationsThe table below lists all modifications and updates done on the considered document. Fill in Date, Author and a summary of the document’s update content, reason and/or objectives.

UpdatesDate Version Author Comment02/09/2002 V0 Geoffroy Krieg Document creation31/10/2002 V1 Elian Faggion Internal validation.04/11/02 V2 EFA/GKR BR : It is mandatory to manage in SAP M1, M2 and M3 as

distinct storage location, but it is possible to have several storage locations groups M1, M2 and M3.

06/01/03 V1.1 GKR Add modification after TB validation meeting :Scrap : attribution of the defects to the responsible plant (PPM indicators)Repackaging : the latest prod date is kept, add BRChange status : edition of internal label is optional, status A instead of U. Logistics : cannot use the status Q, but only B or A.

24/10/03 V3 GKR Review28/01/05 V3 NZO Review:

Repackaging: This transaction is valid also for glass of low by scanning the card quality instead of the internal label.

31/08/05 V3.1 ABA Global Review

The table below lists all the successful validations done on the document ; if the document was asked for validation but not validated then there is no entry in this table (status by default is OK).

ValidationsDate Version Validation Resp. Comment

2 Scope2.1 Process scope description

2.1.1 General description

The purpose of this document is to describe “Sekurit Core Business process” in order to design WMS tool implementation in AVENIR V2 scope.It describes SGS warehouses (factories and service centers) physical and logical structure for raw materials (Glass, PVB, PET), semi-finished and finished products, and the following business cases.

Business CasesThe business cases described in this process are the following:

- Market and quality management for finished products.- Putaway strategy and process for finished products,- Picking strategy for finished products,- Internal stocks movements (status change, transfer to consignment, repackaging, inter-building

transfers),- Scrapping for finished products and components,- Drying time management for finished products,- Logistics traceability.

Material Types

3 18/04/23 - 22:50


document.doc



Material types managed in this process are the following:- Semi-finished products,- Finished products,- Strategic components,- Other components managed in stock.

Packaging typesPackaging types managed in this process are the following:

- Products with re-usable racks,- Products with disposable racks,- Products with customer’s rack.

2.1.2 Position in Process Map

2.1.3 Process pre-requisites Mention the business pre-requisites of the considered process : organizational pre-requisites, material equipment constraints,…(e.g. in order to apply this process, printers need to be put in place at every line,…labels have to be put on racks,…)

Described in the document for each process flow.

2.1.4 Process objectives Write in detail the outputs of the considered process and the value generated

4 18/04/23 - 22:50

FLOWS process mapFLOWS process map

Process goods receipt

IN02

Process internal movements

IN03

Process shipments

IN08

Count inventory

IN05

WMS Master Data and interfaces

IN01

Process Sequencing

IN09

Stock reports and evaluation

IN06

Process returns

IN07

Rack management

IN04

Intra-company Inter-company

Stock comparisonWMS-SAP

IN10

Reference documents


document.doc



The purpose of this document is to describe how Sekurit will manage its internal movements : described for each process flow in the document.

.

2.1.5 Limits Indicate explicitly what is out of scope.

Out of the to be process scope :Empty rack managementInter-buildings transfers of empty racksAll physical and logical flows of goods between sites (plant and Service Centers) : Shipping, receivingProduction declaration

2.1.6 Transition period If applicable, write in detail the alternative process to be used during the period when not all countries are integrated in Avenir V2.

Not relevant

2.2 Application architecture (global)To fill in only if relevant - If the process spans over several applications, describe with help of a scheme those involved systems, as well as all involved interfaces with their Sekurit Avenir codified name. Scheme must be “global”, i.e. including core model and all country- or client specific systems.

Not relevant

2.3 Cross referencesMention eventual other linked To Be Process or any related document (working document, comparison of all scenarios studied and explanation of the choice presented in the document,…). List related To Be processes dealing with data and the others dealing with flows.

2.3.1 To Be Processes

TBIN02_Process goods receipt TBIN04_Empty rack managementTBIN05_Inventory countTBIN06_Stocks reportsTBIN08_Process shipmentTBIN09_Process sequencingTBIN10_Stock comparison WMS-SAP

TBMM31_Logistics Warehouse Issues and Transfers

TBPDC04_Components consumptionTBPDC03_Production DeclarationTBPDC06_Scrap & Rework management

2.3.2 Other related documents

5 18/04/23 - 22:50


document.doc



3 Business Rules3.1 Core model – Business rules

3.1.1 Physical and logical warehouse structure

The SAP storage location will not necessary correspond to the physical locations. Namely, the finished goods will always be managed in 3 storage locations (M1, M2 and M3) independently of the physical disposition. It is mandatory to manage in SAP M1, M2 and M3 as distinct storage location, but it is possible to have several storage locations groups M1, M2 and M3. For example : in order to manage 2 buildings, it is possible to have : In Building A : storage locations AA40 (M1), AA50 (M2), AA60 (M3) In Building B : storage locations BB40 (M1), BB50 (M2), BB60 (M3)

The physical locations will be managed in CIM+ only. The goods which are in CIM+ stock are valued in SAP It is possible to manage in CIM+ the physical storage locations as bins. The management of

geographical location of the bins will be available for warehouse where operator’s movements paths are to be optimized.

All bins are associated to zones (production zone, logistics zone, shipping zone…) In CIM+ all bins are part of a “Warehouse ID”. This warehouse ID symbolizes the building. In SAP, one site (plant or SC) is always a single “plant ID”, whether it has one or several buildings. A velocity rate code can be attributed to storage bins in CIM+. Each country can customize its bins characteristics. Blocking is only possible at a storage bin level.

3.1.2 Putaway strategy

The objective is to be able to find and propose to the user the best storage BIN location where to store the rack in process. In order to proceed, the kernel must use some customizable procedures. The user will be able to customize those procedures, according to its own warehouses configurations.

The customizable procedures are checking different criteria between the rack in process and the existing warehouse locations contents. Among the criteria, one will find the following:

- Rack type- Material(s) in the rack- Material type(s) of the material(s) in the rack- Product Glass position- Quantity(ies) in the rack- If the rack is complete or not (comparison between PI quantity and quantity in the rack)- Market of the rack- Production date of the materials in the rack- Production lot number- Quality status of the label (quality status = inventory status)- Origin code of the rack (when it exist)- Velocity rate of the material in the rack (when it exist)

If the system does not find any location, the last location which has been full of with a product (with the same criteria of grouping) is proposed to the user.The capacity of the storage bin is taken into account when it is managed.

6 18/04/23 - 22:50


document.doc



The user can always override the system proposal.There is no putaway for empty racks.

3.1.3 Picking strategy

The system will find automatically the racks to pick using the following mandatory criteria : Product code Market Packaging instruction

A pick list report is printed with the corresponding racks. The order of the racks is determined with the following criteria (by priority) :1. FIFO window (if managed).2. FIFO date (if FIFO window is not managed).3. The bin the most empty4. CIM+ will consider the movement path to optimize the change of location one to another (available only

if bins and geographical locations are managed).

3.1.4 Change of material code

The change of product code is initiated by CIM+ for the following cases :- When prototype is validated for mass production by the OEM (from ZPRO to FER1) : the market of

the new product is M1.- When the LOGO is erased (from FER1 to FER1) the market is updated to M3 (out of scope : c.f.

TBPDC06_Scrap and rework)- For “derimage” of products (out of scope : c.f. TBPDC06_Scrap and rework)

3.1.5 Repackaging

A multi-products rack has one physical label per product code with the same label number.A rack (mono or multi-products) has 1 inventory content status, 1 market. A mono-product rack cannot contain more than one origin code.When destination rack has the same product that the one in process, the latest production date is kept (coming either from the to-product or from the product in process).If destination rack becomes multi-products, the latest production date is kept (coming either from the to-product or the product in process).

3.1.6 Internal stocks movements and transfers

3.1.6.1 Market

3 markets are managed :M1 : OEM seriesM2 : OEM replacementM3 : Free marketIn CIM+, the market is managed as a status, whereas in SAP it is a storage location.

Most of SGS’s customers are not specialized in OEM series or OEM replacement.The product code can be the same for OEM series or OEM replacement.

7 18/04/23 - 22:50


document.doc



Products can be manufactured for any market.The change of market is initiated by CIM+.

3.1.6.2 Stock status (as opposed to “rack status”)

4 status are managed :Unrestricted useBlockedInspection Consignment The change of status on a product is always initiated by CIM+.

3.1.6.3 Internal label reprinting

Reprinting is mandatory or optional for the following movements :

Automatic Optional Not requiredStock transfer XPutaway XMarket change XStock status change (A, B, Q)

X

Repackaging XChange of material code XLogistics scrapping X

3.1.6.4 Inter – buildings transfer

The use of legal shipping document is mandatory for the transfer of racks between 2 buildings of the same plant ID.

3.1.7 Drying time management

Products not dried can be delivered to SC.Products not dried can be delivered to the customer (not dried at the departure of the truck but dried once arrived).

3.1.8 Scrapping

All scrapping imputable to warehouse handling or logistics operation is not linked to a production process : the industrial yield will not be impacted. The cost center is automatically determined.The possible logistics scrap are the following : Internal scrap : because of warehouse handling or obsolete stock scrap. Scrap after physical return of external customer Scrap after physical return of internal customer Non physical returns : the scrap trigers a return order to the vendorAll scraps require the intervention of a logistics supervisor.

3.1.9 Traceability

Traceability

8 18/04/23 - 22:50


document.doc



The link between consumed and manufactured products from bending plants to final customer will be available. 2 types of links will be used : internal links and external links.Internal link :

- Through the batch number- Through the label number- Through the production date

External link :- Through the Customer label- Through the shipping / reception document number

Harmonized internal label

All Sekurit locations with manufacturing process edit harmonized internal labels.Internal labels are harmonized in Sekurit Avenir scope sharing the same data to improve international exchanges and respect traceability rules.One single internal label template is used all along the production process and for all movements between Sekurit sites.

3.2 Country or customer specific – Business Rules

9 18/04/23 - 22:50


document.doc



4 Process

4.1 Core model - process flow and description

4.1.1 Warehouse logical structure

Definition : a warehouse is physically localized in the factory (or close to the factory, as Auvelais site in Belgium), and it can also be physically independent as a Service Center. The physical structure is relatively standard with a receiving zone, a production zone (if production line or transformation shop-floor), a storage zone, a quality zone, a shipping zone (shipping dock).

To integrate the physicals specificity in the logical structure, each zone has to be detailed and divided so as to correspond to the rules of put away, picking, internal moves, storage rules…

10 18/04/23 - 22:50


document.doc



11 18/04/23 - 22:50

Production zone : semi-finished,

finished products

&glass (spain)

Production zone : semi-finished,

finished products

&glass (spain)

CIM+

Components zone :

PVB, PET & glass (excepted Spain)

Logistics zone : finished products

Market info : M1 / M2 / M3

bin

bin

binBin

bin

Receiving zoneMarket info M1 / M2 / M3

bin

bin

bin

bin

Shipping staging zone

bin

bin



bin

bin

General warehouse

storage location :

all components

managed in SAP

General warehouse

storage location :

all components

managed in SAP

Production storage

location :

semi-finished,

finished products &

glass (Spain)

Production storage

location :

semi-finished,

finished products &

glass (Spain)

Storage location :

PVB, PET, Prelaminat

Storage location :

PVB, PET, Prelaminat

For Devisa only

Valladolid componentsValladolid

components

M1 storage location :

finished products


finished products


finished products


finished products


finished products


finished products

Abreracomponents

Abreracomponents

Barcelonacomponents

Barcelonacomponents

Landabencomponents

Landabencomponents

Sillacomponents

Sillacomponents


document.doc



4.1.2 Warehouse physical structure

The following diagram outlines the flow of materials through the warehouse structure. Starting from the reception of materials or empty racks from the supplier, the production, and the internal inventory movements and ending with the shipment to the customer.

12 18/04/23 - 22:50


document.doc



4.1.2.1 Description table

CIM+ Zones TINM006 – Warehouse management structure SAP storage locations

Receiving zone : optionnal

The logical receiving zone is not managed with receiving points. Receiving staging zone : the racks transit by this zone

before to be put away when the truck is received.The receiving staging zone does not exist when Logistics zone is a single bin in CIM+ (ex : small Spanish service centers): there is no put away after receiving (c.f. TBIN02_Process goods receipt)

For the user it will be possible to view the racks in a “To be received” phase, displayed by ASN. Cf TBIN06_Stock views and reports.

M1(XX40), M2 (XX50) or M3 (XX60) storage locations

Production zone : mandatory if production declaration

Semi-finished and finished products : the rack and its content go to the production zone at production declaration and this before put away in logistics zone. This zone can be divided in storage locations.

Production storage location

Logistics zone : mandatory

It is possible to manage in CIM+ the physical storage locations as bins. The management of geographical location of the bins will be available for warehouse where operator’s movements paths are to be optimized.All bins are associated to zones (production zone, logistics zone, shipping zone…)In CIM+ all bins are part of a “Warehouse ID”. This warehouse ID symbolizes the building. In SAP, one site (plant or SC) is always a single “plant ID”, whether it has one or several buildings. A velocity rate code can be attributed to storage bins in CIM+.Each country can customize its bins characteristics.Blocking is only possible at a storage bin level.The storage bin is the smallest location zone in the warehouse, it is a unique position within a zone in the warehouse used for storage, staging, or manipulation of finished products.Zones are used to define finished products storage, movement, tracking, picking and replenishments. A single zone can occupy more than one physical position in the warehouse.

The Logistics zone can be a single bin (most of the Spanish’s SC).All products (PVB, PET, Glass, semi-finished, finished) can be managed with storage bins : in this case there will systematically be a transaction of putaway behind the reception.


Logistics zone :Quality zone

Quality zone : the finished products in this zone cannot be shipped (picking forbidden), if their status is “Unrestricted” they have to be moved to a storage location to be picked. If their status is “Blocked” or “Quality inspection”, the status has to be updated to “Unrestricted” and they have to be moved


13 18/04/23 - 22:50


document.doc



to a storage location to be picked.Logistics zone :Mixed racks zone

This zone is divided in bins that accept only multi-products racks.


Logistics zone : sequencing zone

Mandatory at Abrera and Landaben. M1(XX70) storage location with the status customer consignment

Components zone(s)

Stock of glass, PBV, PET. This zone can be divided with binsIn Spain, glass is directly received in production zone.

General warehouse storage location

Shipping zone : mandatory

Shipping staging zone : is divided in multiple shipping locations. As soon as the picking is started, the racks and their content are transferred from the storage zone to the shipping staging zone, the racks in the shipping staging zone process are no more available for picking. The stock is still valorized in SAP as far as the truck is not logically closed.


4.1.2.2 Definition of a storage bin

For each roll-out of a new site, the following elements will have to be customized to define the zones and the storage bins :Storage bins : definition of the number aisle between storage locations velocity rate assigned to storage locations (finished products) building

Zones : definition of the number aisle between zones closest staging point building

4.1.3 Block / Unblock storage bin List the main process steps and represent all steps in a diagram. Use the recommended template to represent process steps, triggers, related system, actors,…


Step Responsible Description : CDM screen CIM flow

1 Logistics operator Key bin number

2 Logistics operator Flag a bin : “blocked”

3 Logistics operator Put off the flag “blocked” of the bin or plant blocked

4.1.3.2 Prerequisites

14 18/04/23 - 22:50


document.doc



The warehouse has to be composed with bins if bins are blocked.The clamping concerns only the bin, the stock does not take the status “Blocked”.

4.1.3.3 Objectives

To block one or several bins : the logistics operator or manager wants to reserve racks for a shipping for example.

4.1.3.4 Inputs / outputs

Inputs : This transaction is initiated by CIM+ on the CDM screen. Outputs : There is no impact in SAP : no idoc uploaded to SAP.The stock status (unrestricted use, blocked or inspection) is not modified with this transaction.There is no impact on the pick list report edition : racks stored in a blocked bin can be proposed by the picking list. Racks and products in the bin blocked cannot be moved.

4.1.3.5 Transition periodIf relevant, indicate how this step is performed in the transition period.

Not relevant.

4.1.3.6 System flowFor each action performed in the process step, mention the related transaction code when the action is performed in SAP – when performed in CIM+, mention the main data to be considered and the flow of screens (mention the type of transaction : RF or CDM)

Action on CDM Trans. /data

Comments

Key storage bin number

1 The user keys the bin on the CDM screen.

Flag the bin as “blocked”

2 The user flags the mention “block the bin”. This transaction can be done by any user.RESULT :The bin is blocked : the racks cannot be picked / shipped. No movement can be done in this bin or from this bin to other bins.The stock status (unrestricted use, inspection, blocked) is not modified.

Put off the flag of the “blocked” bin

3 The user put off the flag. The transaction can be done by any user.RESULT :The bin is no more blocked. Picking / shipping is possible as any other internal moves.

15 18/04/23 - 22:50


document.doc



4.1.4 Process flow : product change status


Step Responsible Description CIM flow

1 Logistics manager / Quality manager

Key / Scan rack ID.Or key / scan batch number

TINM001


Select the new status. TINM001


Confirm the update TINM001

16 18/04/23 - 22:50

Scan rack ID or lot n°

1

Logistic operator

SAPStock

Change status

Select new status 2

Logistic operator

Confirm updateof status & enter a reason if “B” or “Q”

3

Logistic operator

WMMBXY

CIM +database

Print internal label(facultative)

4

Logistic operator


document.doc




For this transaction, CIM+ will propose the 3 following status :

SAP appellation CIM+ appellation Symbol on Internal label and system CIM+ for all countries

Unrestricted use Unrestricted use ABlocked Blocked BQuality inspection Quality inspection Q

Unrestricted use :

Unrestricted stock is available for all kind of movements and the stock can have the status Unrestricted in all logistics storage zones.

Blocked :

The quality department is in charge of the “Blocked” stock and decides to put it for “Unrestricted use” or not after sorting. “Blocked” stock cannot be picked / shipped : “Blocked” stock is not proposed by the Pick list report edited at the delivery preparation.The MRP does not take into account the stock with the status “blocked”.

Quality inspection : Can be used by production or logistics people when the stock has to be inspected before sorting, rework or scrap. It can also be used after returns. If quality problems are very critical, it is preferable to put the products in the blocked status so that they are not taken into account by the MRP.The MRP takes into account the stock with the status “quality inspection”.

Mono-product racks :The change of status is done on all the rack content and cannot be done on a limited quantity of goods.

Multi-products racks :The change of status is done on all the rack content and cannot be done on a limited quantity of goods.

Batch number :The user has also the possibility to assign the status “Blocked” or “Quality inspection” to a batch number.

The change of status can be done in any BIN, even if the BIN has restricted criteria for the put away. The user will have to do a put way (only if he wants to optimize his warehouse storage !) behind the transaction of change of status if the change of status is done in a BIN which is flagged as mono inventory status.

Privileges :

When stock is blocked, it is important to record the : Name of the person who block the stock (corresponds to the login name) The date The time

The goods can take the status “Blocked” when : Blocked by a supervisor to forbid racks movements (picking, shipping…).

17 18/04/23 - 22:50


document.doc



Blocked by the quality department for inspection. Goods are systematically and automatically blocked after customer returns.

4.1.4.3 Objectives

Possibility to assign the “Blocked” or “Quality inspection” status to a batch number or to a rack content after quality inspection.To differentiate in CIM+ and in SAP the different status that can take products.


Inputs :Transaction always triggered by CIM+ available for all materials managed in CIM+.

Outputs :Idoc WMMBXY uploaded to SAP.The user has the possibility to print a new internal label at the end of the transaction.Movements codes are described in 5. Keys elements of system implementation.


Not relevant


Action with RF Trans. /data

Change of product status

Scan the rack ID or the label number

1 All the rack content is updated in this transaction. The screen gives the following information : Rack ID The choice between the 3 status : A, B or QThe user is stopped if one of the following controls is positive : Rack phase “Delivered” Rack phase “To be received” Rack phase “picked” Empty rack status “In Maintenance” Empty rack status “Removed”The rack phase has to be “Inside plant”.

Select the status and confirm

2 & 3 If the status “Blocked” or “Quality Inspection” has been assigned to the rack content, the following step proposes to the user to key a reason of blocking (maintained in a reason code table). It is mandatory to enter a reason of blocking (for the status B and Q) otherwise the user cannot block the products.

Scan the batch number

1 The user keys the batch number and validates . The screen gives the following information : Batch number Total quantity (of goods)The user is stopped if the following control is positive : Batch number unknown is keyed.

Validate the status 2 & 3 The user validates the new status assigned to the batch number.The next step proposes to the user to key a reason of blocking

18 18/04/23 - 22:50


document.doc



It is mandatory to enter a reason of blocking (for the status B and Q) otherwise the user cannot block the products.

.

19 18/04/23 - 22:50


document.doc



4.1.5 Market management

Description :

Markets are managed by storage locations in SAP. Markets are managed by market information (attribute of the rack) in CIM+.

Production declaration is done in CIM+ in the scheduled market of the campaign, it is a stock information in CIM+. Products are then stocked in the PRODUCTION storage location in SAP : at production declaration the notion of Market is not known in SAPThe user can changed the market information in CIM+ at the quality control, this transaction triggers a label edition. There is no idoc send to SAP, the CIM+ data base is updated.At putaway : stock transfer from PRODUCTION zone to LOGISTICS zone : idoc WMMBXY send to SAP to transfer the stock from storage location PRODUCTION to storage location M1, M2 or M3.

For the transfers, in order to ensure the correspondence between CIM+ and SAP, the following correspondence table is used :

20 18/04/23 - 22:50

M 1

W M M B X Y I n t e r n a ll a b e l

P R O D U C T I O N

M 2

M 1

M 3

L O G I S T I C S

C h a n g e o f m a r k e t ?

C h a n g e o f M a r k e tT I N M 0 0 2

M 1 M 2 M 3

P r o d u c t i o nD e c l a r a t i o n

P u t a w a yT I N M 0 0 6

1 3 1

W M M B X Y

W M M B X Y

W M M B X Y

3 1 1

3 1 1

3 1 1

M 3

M 2P R O D U C T I O N

C i m +d a t a b a s e

y e s

n o




document.doc



4.1.6 Process flow : change of market List the main process steps and represent all steps in a diagram. Use the recommended template to represent process steps, triggers, related system, actors,…

TINM002 - Change of market without change of product code


Step Responsible Description : change of market without change of product code CIM flow

21 18/04/23 - 22:50

Key / Scan rack ID

1

Logistic supervisor

SAPStock

Change market

Select new market 2

Logistic supervisor

Confirm updateof market

3

Logistic supervisor

WMMBXY

InternalLabel

CIM +database


document.doc



1 Logistics manager or Shop floor responsible

Key / scan the rack ID TINM002


Select new market TINM002


Confirm the change of market and print internal label TINM002


The movement is always triggered by CIM+. The change of market is done by the quality department on finished products (or logistics supervisors / operators : with agreement of the quality department). The change of market is only allowed here when the product code is not changed. Change of market with change of product code is described in TBPDC06_Scrap and rework management (for the cases of “derimage” and when the logo is erased).

Mono-product racks : The change of market is done on all the rack content.

Multi-products racks : The change of market is done on all the rack content.

M1 M2 : When goods are returned by the customer, and after quality inspection and sorting the market generally goes from M1 to M2. Besides this, the product are put to an Unrestricted use.OEM replacement delivered by the service centers can be generated with this update if there is no stock of OEM replacement, but only with agreement of the quality department (this transaction is generally used for tempered glass).

M2 M1 : In case of stock outage of M1 in a service center, it is possible to change the stock from M2 to M1, but only with agreement of the quality department. This is also a reverse transaction of M1 change into M2.

M2 M3 : the quality of the glass is not good enough for the OEM replacement, but can be accepted by the free market. For example, Windscreen : when market M2 is updated to M3, the product code is also changed because the LOGO is removed from the laminated glass.

M3 M2 : after quality inspection, the market can go from M3 to M2. This is also a reverse transaction of M2 change into M3.

M1 M3 : for the free market.If there is rework, the product code is changed (LOGO is erased).

M3 M1 : after quality inspection, the market can go from M3 to M1. this is also a reverse transaction of M1 change into M3.

4.1.6.3 ObjectivesTo assign the good quality to the finished products.

22 18/04/23 - 22:50


document.doc



4.1.6.4 Inputs / outputsInputs :CIM + initiates the movement.

Outputs :Each movement initiated by CIM+ is uploaded to SAP with an idoc WMMBXY. Transfer of goods from one MM storage location to another one.Movements 311, 323 and 325 in SAP when there is a change of market without change of product code. When the market is changed in production zone : no idoc uploaded to SAP.

4.1.6.5 System flowAction with RF Trans. /

data Comments : change of market without change of product code

Scan the rack ID or the label number

1 The user scans the rack ID. All the rack content is updated in this transaction. The screen gives the following information : Rack Id or label number Quantity of pieces Current Market (M1, M2 or M3) The others market (M2/M3 if the current market is M1)

The user is stopped if one of the following control is positive : Storage bin flagged as “blocked” Rack phase “Delivered” Rack phase “Picked” Rack phase “To be received” Empty rack status “In Maintenance” Empty rack status “Removed” If the product cannot change of market without change of product codeThe rack phase has to be “Inside the plant”.

Select the market and confirm

2 & 3 When the new market is updated, a new internal label is automatically printed.

23 18/04/23 - 22:50


document.doc



4.1.7 Material code change


Step Responsible Description : Material code change CIM flow

1 Logistic supervisor

Scan the rack ID giver or the label number TINM003

2 Logistics supervisor

Scan new product TINM003


Scan the rack ID receiver or the label number TINM003


Print internal label (automatic) TINM003


The change of product code is initiated by CIM+ for the following cases :- When prototype is validated for mass production by the OEM (from ZPRO to FER1) : there is a

control on the product ID.- When the LOGO is erased and the market updated to M3 (from FER1 to FER1) - For “derimage” of products (from FER1 to HLB1)

- There is a control on the 11th first characters of product ID when the product code is changed for the following cases : logo erased and “derimage”

The source rack must be mono-product.

4.1.7.3 Objectives

24 18/04/23 - 22:50

SAPStock

WMMBXY

Scan source rack1

Log supervisor

2

Scan rack ID receiver

3Log supervisor

Log supervisor

Scan new product code

Material codechange

InternalLabel

CIM+ database


document.doc



Transfer of one material to another one : When prototype is validated for mass production by the OEM (from ZPRO to FER1).

4.1.7.4 Inputs / Outputs

Inputs :CIM + initiates the movement.

Outputs :The new product code will have no batch number, the origin code will be the current plant origin code, the inventory content status will be unrestricted use and the market M1.

- When prototype is validated for mass production by the OEM (from ZPRO to FER1) : the market of the new product is M1.

Each movement initiated by CIM+ is uploaded to SAP with an idoc WMMBXY.Movement 309 in SAP when there is a change of product code.

4.1.7.5 Transition period

Not relevant

4.1.7.6 System flow


Comments : Material change code

Scan the source rack or source label number

1 Source rack is a mono product rack :The screen gives the following information : Rack ID Product (s) code QuantityThe user is stopped if one of the following control is positive : Storage bin flagged as “blocked” Rack phase “Delivered” Rack phase “Picked” Rack phase “To be received” Rack content is multi-productsThe rack phase has to be “inside the plant”.

Key quantity and confirm

2 The operator confirms the new product code.The operator is stopped when the following controls are done : Product code unknown New product code incompatible with packaging instruction Quantity keyed in step 2 is > standard quantity (determined by the couple

product code B – packaging instruction rack receiver)

There is a control on the product ID when the product code is changed for the following case : from ZPRO to FER1.

Key / scan destination rack

3 / 4 When the destination rack is scanned it triggers automatically the edition of an internal label.

25 18/04/23 - 22:50


document.doc



4.1.8 Process flow : stock transfer


Step Responsible Move to sequencing zone CIM flow

1 Logistic operator Scan the rack ID or label number or quality sheet TINM008

2 Logistic operator Scan destination BIN TINM008


The transaction will be done with the RF media. The transfer of materials to production zone is a logical operation handled by a decision of the operator, which means that the system will not tell to the user that there are components to move to production before consumption. However, when the user initialize the transfer to production transaction, according to the FIFO CIM+ system will propose to the user the best bases to pick in case he has not picked the oldest batch number : based on the oldest batch number for the combination product code / market / inventory content status A. Therefore the user will be “forced” to consume the products respecting the FIFO rule, however this picking will never be blocking in case the user wanted to pick a batch later than another one.The system will not guide the user for glass, and PVB/PET rolls because the quality sheet number is incremental and the stocks are not big enough to have a guided proposal. Moreover, the FIFO is very well managed physically in the warehouses.If the user does not want to be guided by the system when he has to put away racks after production, external or internal receiving ; he makes his stock transfer using the transaction “stock transfer operation” : which can be a saving of time for him because the system does not check all the put away customizing. The system will not optimize the put away with this transaction, therefore the rules defined in the customized strategy of put away can be by-passed.

26 18/04/23 - 22:50

Scan rack or

label number

1

Logistics Operator

Stock transfer

Scan destination BIN 2

Logistics Operator

WMMBXYSAP stock

CIM+ data base


document.doc



4.1.8.3 Objectives

Stock transfer operation is available for the following internal movements :- Transfer of racks from one BIN to another BIN- Transfer from production zone to a logistics BIN after production declaration- Transfer from a logistics BIN to production zone (before components consumption)- Transfers of racks to a logistics BIN after external or internal receiving- Transfer of quality sheet (PVB / PET and glass) to production zone before consumption - Transfer of racks to sequencing zone- Transfer of racks to customer consignment (kanban with consignment stock : Ford in Spain)

4.1.8.4 Input / Output

Inputs :Transaction triggered by CIM+.

Outputs :Idoc WMMBXY uploaded to SAP for the following cases :

- Transfer from production to logistics (ZHLB, HLB1 or FER1) : emulation of transaction MB1B, movement 311 from unrestricted use stock. The “Reverse production declaration” flag is removed.

- Transfer to sequencing or to customer consignment : emulation of transaction MB1B movement 631, the stock takes the status k (customer consignment).

27 18/04/23 - 22:50

M 1 s t o r a g el o c a t i o n

P R O D U C T I O N :b a s e s , r a w g l a s s ,

P V B , P E T

M 2

M 1

M 3L O G I S T I C S :s t o c k o f b a s e s

W M M B X YW M M B X Y

W M M B X Y3 1 1

3 1 13 1 1



P R O D U C T I O Ns t o r a g e l o c a t i o n

G e n a r a lw a r e h o u s e :s t o c k o f g l a s s ,P V B / P E T

C o m p o n e n t s s t o r a g e l o c a t i o n

S t o c k t r a n s f e rT I N M 0 0 8

S t o c k t r a n s f e rT I N M 0 0 8

S t o c k t r a n s f e r T I N M 0 0 8

C o m p o n e n t s c o n s u m p t i o n

d e c l a r a t i o n

1

2

S t o c k t r a n s f e r T I N M 0 0 8

W M M B X Y4 1 1

o r3 1 1


document.doc



- Transfer of PVB / PET and glass (STRA) from general warehouse to production before consumption : emulation of transaction MB1B, movement 411 : transfer from vendor consignment to own stock.


Not relevant

4.1.8.6 System flow


Stock transfer operation – TINM008

Scan the destination BIN

1 The destination BIN is correct according to the data element scanned in the previous step :Only material type FER1 with market 1 can be transferred to sequencing or to customer consignment.When the destination BIN scanned is production, then the system checks for the combination product code / market / inventory content status if the product selected is the oldest one.

Scan rack ID, label number or quality sheet

2 The user scans a rack ID or label number or a quality sheet :If the rack status must be is N “new, in plant”, if not then the user is not stopped.If the rack is blocked it must be transferred in the same zone type.A rack which status is changed to ‘Quality inspection’ is automatically transferred to the rework bin linked.When a rack is scanned, then the rack or label is unloaded in the destination BIN.Several racks can be transferred to the same bin without rescanning it.

28 18/04/23 - 22:50


document.doc



4.1.9 Process flow : Transfer of material between racks (repackaging)



1 Logistics operator The rack ID giver is scanned. TINM004

2 Logistics operator The quantity to transfer is keyed and confirmed. TINM004

3 Logistics operator The rack ID receiver is scanned. TINM004

4 Logistics operator The new packaging instruction is selected and validated TINM004

5 Automatic Edition of an internal label TINM004

29 18/04/23 - 22:50

Scanrack ID/label giver 1

Logistics OperatorRepackaging

For new combination

rack type/product code,is there more than 1 PI ?

Key quantity to betransferred

Logistics Operator

2

3

WMMBXYSAPstock

Scan rack IDreceiver

Logistics Operator

Change PI

Logistics Operator

yes

CIM+ database

Table rack ID/rack type

4

Internal labeledition

Is it a mixedrack ?

Scan product code

Logistics Operator yes

no

no


document.doc




A multi-products rack has one physical label per product code with the same label number.A multi-products rack can contain different products with different origin codes.A mono-product rack cannot can contain only 1 origin code. The transfer of goods from 1 rack to another rack is done with the RF and the quantity can be choose by the operator. This transaction enables also the transfer of boxes from one rack to another rack.The 2 racks do not have be in a single storage bin. If an empty rack (not stored in a bin) receives goods, the system will not tell to the user to put it away after, he will have to do a put away by himself (that will guide the user of course !).

4.1.9.3 Objectives

To complete racks, to do multi-products racks…Update the good packaging instruction if necessary.


Inputs :Movements of goods or boxes between racks and update of the PI are initiated by CIM+.

Outputs :After transfer of goods and change of PI the table rack ID / rack type is updated when the packaging instruction is changed.If the rack giver becomes “empty” after the transaction, it stays in it storage BIN.Result after packing :

- One production date per rack/label- One batch number per rack/label- One origin code per arck/label- One Market per rack/label- One status per rack/label

If source and destination rack have the same product code and if production date are different on source and destination rack, the latest production date is kept (coming either from the to-product or the product in process).If destination rack has no batch number, it inherits the batch number of source rack.If source batch number is different from destination batch, then destination batch is kept and source one is erased.It is not possible to make repackaging between 2 racks with same materials and with 2 different origin codes, a material with different origin codes has to be packed on physical distincts racks.Repack of the same product in a same racks but with 2 origin codes is possible but only destination origin code is kept.When destination rack has another product than the one in process and when the destination origin code is different than the one in process, the latest production date is kept (coming either from the to-product or the product in process), the destination batch and destination origin code are kept.When destination rack has another product than the one in process and when the destination origin code is = to origin code in process, both production date are kept and the destination batch number is kept (coming either from the to-product or the product in process).


Not relevant

30 18/04/23 - 22:50


document.doc





Transfer of material between racks

Operator scans the source rack ID or label number

1 Mono-product rack :When the source rack is scanned, the screen gives the following information : Rack ID Product Quantity

The user is stopped if one of the following control is positive : Storage bin flagged as “blocked” Rack phase “Delivered” Rack phase “To be received” Rack phase “picked” Empty rack status “In Maintenance” Empty rack status “Available” Empty rack status “Removed”The rack phase has to be “inside the plant”.

Multi-product racks :After step 1, the users scans the product code.

Operator keys / scans the quantity to transfer

2 Mono and multi-products racks :The user keys the quantity to transfer and validates.The user is stopped if one of the following control is positive : Quantity selected > quantity on the rack.

Operator scans destination rack

3 The user is stopped when the following controls are done : Empty Rack status “In Maintenance” Empty Rack status “Removed” Rack phase “Delivered” Rack phase “To be received” Standard quantity already reached Storage bin flagged as blocked Packaging instruction incompatible with product code

If the rack giver is emptied, it is removed from the storage bin : it is empty with the status “Available”.

Operator selects new PI (facultative)

4 If there is only 1 PI for the new combination product code / rack type, it is attributed automatically when the rack receiver is scanned.

If there is more than 1 Packaging Instruction for the eventual new combination rack type / product code, the next screen proposes to the user up to 4 of the alternatives PI for this combination.

If the rack type of the rack receiver is the same as the rack type of the rack giver, the first PI proposed is the one used by the rack giver.

New label for destination rack automatically edited

5 The internal label of the source or destination rack (if it is not emptied) is automatically printed, and takes into account the new data to be integrated : all attributes of the product code in process.

31 18/04/23 - 22:50


document.doc



4.1.10 Process flow : Logistics scrapping

See further (5. Key elements of system implementation) for more details.


Step Responsible Description SAP/CIM flow


Choose the scrap movement TINM007


Scan rack id or label number TINM007


Key quantity to be scrapped TINM007


Scan reason code of scrap TINM007

32 18/04/23 - 22:50

1RF : Logisticsscrap

2

Logistics

Scan rack id or label n°

Logistics

SAPStock

WMMBXY

Flexnet database

Chose scrap movement 1)After external return2)After internal return3)Manipulation/obsolete4)Non physical return

Key quantity to be scrapped

Logistics

Scan reason code of scrap

Logistics

Key or scan responsable plant

Logistics

3

4

5

Print internal label ?

Logistics 6

Yes


document.doc



5 / 6

Logistics manager or Shop floor responsible

Scan responsible plant and print internal label TINM007


It will be possible for the user to reverse a scrap.Scrapping can be done on blocked, unrestricted use or quality inspection stock.The quantity scrapped can be chosen by the operator.

4.1.10.3 Objectives

The scrap consists in breaking physically the glass. The goods scrapped are decreased from CIM+ and SAP stock.Products are scrapped in the Logistics zone for the following reasons : Warehouse scrap : handling or scrap of obsolete stock, Scrap after physical return of external customer, Scrap after physical return of internal customer, Non physical return of goods (triggers a return order to the vendor : c.f. TBIN007_Process returns)The scrap must increase the PPM indicator of the plant responsible of the defect.PPM indicator are only impacted after physical return from a customer. (not for a warehouse scrap)


Inputs :Transaction initiated in CIM+, the user keys the quantity to be scrapped, chooses the reason code of the defect, the movement type and the plant responsible of the defect.

Outputs :Idoc WMMBXY uploaded to SAP for each transaction of scrapping : the plant responsible of the defect and the reason code are uploaded to SAP (in order to impute the corresponding PPM indicator).If the rack is emptied, it stays in its storage location.All scrapping imputable to the 4 reasons mentioned above are not linked to a production process : the industrial yield will not be impacted.The warehouse scrap for handling and scrap of obsolete stock will have the same movement code in SAP (CO does not need to differentiate 2 different movements types).Detailed movements are described in 5. Key system of implementation.


Not relevant



Scrapping

Operator chooses the scrap movement

1 Products are scrapped in the Logistics zone for the following reasons : Warehouse scrap : handling or scrap of obsolete stock Scrap after physical external customer returns, Scrap after physical internal customer returns.

33 18/04/23 - 22:50


document.doc



Non physical return of goods : triggers return order to the vendor.Reverse movements are only possible for the 3 firsts cases. The non physical return of goods is a particular case of scrap deeply analyzed and treated in TBIN07_Returns process.

Operator scans rack or label number to be scanned

2 When the rack is scanned, the screen gives the following information : Product code Quantity

The user is stopped if one of the following control is positive : Rack status picked Rack status to be linked Rack status linked Rack status delivered Rack status consumed

- The rack status as to be “new, in plant”.

Operator keys quantity to be scraped

3 The user can choose the quantity on the rack to be scrapped. - If the quantity keyed is >0 and <= label current quantity, then the system

will consider that the quantity keyed is the quantity to be scrapped.- If the quantity keyed is > label current quantity, then the system will

consider that (quantity keyed – label current quantity) is the quantity to be reversed (for reverse movements). The quantity keyed will be the new quantity of the label.

Operator chooses the scarp movement

4 A reason code can be assimilated to a macro-phase.A reason code list is common between logistics and production : the PPM indicators will be charged in the same way.

Operator chooses the plant responsible

5 - 6 The user chooses the plant responsible in order to charge correctly the right PPM indicator. The user can print a new internal label at the end of the transaction.

4.1.11 General warehouse scrap

4.1.11.1 Pre-requites

Transaction available in SAP for components managed only in SAP.

4.1.11.2 Objectives

The user can scrap components for the following reasons :- Warehouse scrap (component damaged or broken when handled)- Obsolete stock scrap.


Inputs :This transaction is initiated by SAP for all materials managed in SAP and not in CIM+.

Outputs :Transaction MB1A, movement 551. The same cost center is automatically determined for the 2 reasons of scrap.All scrapping imputable to warehouse handling or logistics operation is not linked to a production process : the industrial yield will not be impacted.

34 18/04/23 - 22:50


document.doc



4.1.11.4 Description

Step Responsible Description SAP flow

1 Operator (can be a production operator, a purchaser…)

Perform transaction MB1A to enter in SAP stocks issues.Movement type 551PlantStorage locationSAP material numberQuantitySelect the appropriate reason code : warehouse scrap (when handled) obsolete stock scrap

MB1A, movement 551

35 18/04/23 - 22:50


document.doc



4.1.12 Inter-buildings transfers

The model proposed will be applied to : Italy between Savigliano and Aimeri Germany between Building A logistic warehouse (Plant Stolberg Hall 3) and Building B logistic

warehouse (Eschweiler).Inter-buildings transfer are done with the CIM delivery transaction : TSHI007_Create CIM delivery.


Step Responsible Description CIM flowc.f. TBIN08_Process shipment TSHI007

4.1.12.2 Prerequisites – description of the Italian model

The model described is valid only if : each operator is affected to one building.In some occasions, the system may even face the following situation : Delivery 1 prepared and staged in Savigliano Delivery 2 prepared and staged in Aimeri Delivery 2 loaded on truck at Aimeri, which comes to pick up the delivery 1 in Savigliano as well.

Any transfer between the 2 buildings requires a shipping paperwork, except the transfers of empty racks. However no customer label is needed. The delivery note must fulfill the usual delivery note constraints : mandatory information, external delivery note number…

All transfers between Savigliano and Aimeri must be done physically through “true” deliveries, in particular because the public road network is used.A standard delivery note (“bolla”) is required as shipping paperwork, and a normal reception is done at the receiving point, except when only empty racks are exchanged.

36 18/04/23 - 22:50

Warehouse ID 600-1 Warehouse ID 600-2

RF : Inter-buildings transfer :creation of a transfer order

Bolla

Public road

1 SAP plant n° 600


document.doc



4.1.12.3 Objectives

Transfers between 2 buildings occur frequently to : Move some parts from the building Savigliano where the stock is quite small, to the main stock Aimeri ; Send from Savigliano to Aimeri parts for aftermarket ;Send back from Aimeri to Savigliano parts to be shipped in Savigliano departing trucks…


Inputs :SAP is not able to generate any delivery order for such transfers.

Outputs :Depending on the country customizing, the transfer of racks between 2 buildings can or cannot be seen by SAP.1. If a group of 3 SAP storage locations XX40, XX50 and XX60 are created for each building, For example :

- In Building A : AA40 (M1), AA50 (M2), AA60 (M3)- In Building B : BB40 (M1), BBA50 (M2), BB60 (M3)

Then these transfers exclusively initiated by CIM+ are always seen by SAP, since SAP always knows in which building the parts are stored : Italian model

2. If 3 SAP storage locations M1, M2, M3 are created for the 2 buildings :- In Building A and B : XX40 (M1),XX50 (M2) and XX60 (M3).

Then the transfers exclusively initiated by CIM+ are never seen by SAP, since SAP never knows where the parts are physically stored in Building A or B : German model

For the both cases, once the transfer is confirmed, the rack status goes from P “picked” to N “new, in plant” : there is no receiving process to do in the destination building. In the destination building, the user can eventually do a put away in order to optimize his storage.

Inter-Buildings transfers of empty rack : refer to TBIN05_Rack management.


Not relevant.



Comments

c.f. TBIN08_Process shipment

4.1.13 Put away strategy

37 18/04/23 - 22:50


document.doc



4.1.13.1 Definition

The put away is the process of bringing the racks and the products contained in the rack to a specific storage BIN in the warehouse. The choice of the putaway mode is customizable by warehouse. The put away follows the receiving process for : reception of production declaration external receipts internal receipts

Put away is also the process of bringing a rack from one CIM+ bin to another CIM+ bin.

The strategy proposed is defined for a standard SGS warehouse and is available where :

All locations are physically located in the same main building (for example Würselen), or The locations are at least located in the same facility where the movements from one building to the

other one is just a simple transfer (for example Italy plant 600) The received parts always arrive at the same building (for example Noyon).

4.1.13.2 Process flow List the main process steps and represent all steps in a diagram. Use the recommended template to represent process steps, triggers, related system, actors,…

38 18/04/23 - 22:50


document.doc



4.1.13.3 Algorithm to be used


1 Logistics operator Scan the rack (s) ID or label number to putaway, or scan BOL number for “mass” putaway

TINM006

2 CIM system Retrieve rack information TINM006

3 CIM system Find best fitting zone TINM006

3a CIM system Find best fitting BIN in the best fitting zone TINM006

4 CIM system Loop on action 3, with the next best fitting zone in case no best fitting BIN could be found in the last zone checked

TINM006

5a Logistics operatorCIM system

The user can scan other racks to load into his forklift- Check that the new racks scanned can be stored in the

determined BIN- Consider that the determined BIN contains all the racks

already in the BIN--- and also the all the racks currently on the forklift for

the above test

TINM006

5b Logistics operatorCIM system

The user can unload all the content of his forklift into a BIN- If BIN scanned is the determined BIN, then unload all

the racks into the BIN- If BIN scanned is another BIN, then check if the BIN

scanned (considering all that it contains) can contain all the racks currently on the forklift

TINM006

39 18/04/23 - 22:50

Scanrack ID or BOL n° 1

Logistics OperatorPutawayTINM006

With rack info, retrieve best fitting zone

Scan rack or BIN

Logistics Operator

2

WMMBXYWMMBXY Idoc to SAP only for putaway after production declaration

SAPstock

CIM retrieve rack information

Find best fitting

BIN in best fitting zone

If no BIN found

rack

CIMUnload rack(s)

in BIN

BIN

3 3a

5a

5b

4


document.doc




Putaway operations are performed using radio-frequency terminal. The warehouse operator is guided by the RF screen. Put away is initiated by informing the system that the operator wishes to store racks received. A bin is then proposed by CIM+ depending on the rules defined for the SGS Service Centers. It is not possible to chose a quantity on a rack to be put away : all the rack content is putaway.

If the BOL n° is scanned, the system knows that it is to put away all the racks linked to the BOL n°. A “mass” putaway is then possible. It means that all the racks which were just received will be stored on one storage bin.

Process of putaway after production receiving and external / internal receiving :

PUTAWAY After external and internal receiving

After production receiving

Warehouse with 1 Production zone and 1 Logistics zone divided in bins

Putaway mandatory Putaway mandatory

Warehouse with 1 Production zone and 1 Logistics zone (no bins)

No putaway Putaway mandatory

The procedures must retrieve the best location for the rack in process. This “best location” fits the requirements from the customizable procedure. Unfortunately, every warehouse bin is assigned to a different zone ID. In addition, every zone ID has its own customizable procedure. Therefore, in order to find out the “best location”, the kernel must look in all the racks that are stored in the same zone ID with the customizable procedure of this zone ID.

This process might be very time consuming in case there is many warehouse bins assigned to many different zone IDs. Therefore, it might be necessary to have

The 2 levels of customizable procedures :

1. The first level of customizable procedures is sorting the zone IDs in terms of “best fitting zone” for the rack in process. It is basically choosing the best zone ID, according to the rack in process content.

2. The second level of customizable procedures is sorting the warehouse locations to be displayed to the user. It is basically choosing the best warehouse bin, according to the rack in process content and the warehouse bins content

This way, the kernel is finding the zone ID (and thus the customizable procedures) to be used, then it is looking in a zone ID for the warehouse bin that best fits the content of the rack in process, according the customizable procedure of the zone ID.

It is important to understand that the system is not looking for a warehouse bin, which attributes are fitting the rack in process content (according to the customizable procedure to be used for the warehouse bin zone ID). In fact, the aim is to retrieve a bin which content is fitting the rack in process content (according to the customizable procedure to be used for the warehouse bin zone ID). The advantage of such a solution is that the locations do not have attributes : any bin can contain anything (according to the customizable procedure to be used for the warehouse bin zone ID).

Each zone criteria defined in 3.1.2, could be customized as blocking or as a warning.

40 18/04/23 - 22:50


document.doc



A blocking criteria can’t be overpass (ex : you try to transfer a M2 market in a bin mono market with only stock in M1, this message will be displayed : ERR! New Market). You can’t forced the transfer and put away process will never proposed a bin which is not fitting to the label scan (it will prefer an empty bin)

A warning will display a message to the operator (ex : you try to transfer a new market in a bin linked to a zone mono market, ‘New market, do you want to continue YES\NO?’). If the operator validate label stock transfer, the stock is logically transferred and criteria will disappeared until all the bins of the zone linked respect the criteria. So, you can forced a warning but put away process process will never proposed a bin which is not fitting to the label scan (it will prefer an empty bin)

Change market, scrap, status change, stock transfer , receiving, change material, repackaging transactions are impacted by putaway use : if some criterias are defined at zone level it won’t be possible to override them. (Ex : If there is a blocking mono market criteria on a zone, it will be impossible to change the market of a label linked to a bin of this zone, in order to keep it mono market.)

It is also impossible to define a blocking criteria on a zone if any bin linked to this zone doesn’t respect this criteria. (Ex: Impossible to set criteria “mono market” to a zone if in a bin linked to this zone contains labels in M1 & labels in M2)

4.1.13.5 Objectives

To propose a guided strategy of putaway to the user in order to optimize the warehouse management and the user’s work.


Inputs :Movement initiated by CIM+.

Outputs :Put away after production declaration : idoc WMMBXY is uploaded to SAP.

41 18/04/23 - 22:50


document.doc



4.1.13.7 System flow – rules – results


PUTAWAY

Scan rack ID or scan BOL n°

1 & 2 The racks scanned have inner properties that depends from their content:

- Rack type- Material(s) in the rack- Material type(s) of the material(s) in the rack- Product Glass position- Quantity(ies) in the rack- If the rack is complete or not (comparison between PI quantity and

quantity in the rack)- Market of the rack- Production date of the materials in the rack- Production lot number- Quality status of the label (quality status = inventory status)- Origin code of the rack (when it exist)- Velocity rate of the material in the rack (when it exist)

3 The Zones have inner properties (zones attributes):

- First market allowed in the zone- Second market allowed in the zone- Third market allowed in the zone- Zone is mono or multi product Glass position

- To know which Glass position the zone accepts in case the zone is mono Glass position, the system must retrieve 1 rack that is already stored in the zone

- In case there is no rack stored in the zone and zone is mono Glass position, then the zone can only accepts materials from the same Glass position as the material scanned in the rack in process

- In case the zone is multi Glass position, then do not check the Glass position of the rack in process against the Glass position of the zone

- Zone is mono or multi material type- To know which material type the zone accepts in case the zone

is mono material type, the system must retrieve 1 rack that is already stored in the zone

- In case there is no rack stored in the zone and zone is mono material type, then the zone can only accepts materials from the same material type as the material scanned in the rack in process

- In case the zone is multi material type, then do not check the material type of the rack in process against the material type of the zone.

3a BIN have inner properties (zone attributes):

42 18/04/23 - 22:50


document.doc



- BIN of the zone are mono or multi product- If BIN of the zone are mono product, then the material of the

rack in process must be the same as the material of any rack already stored in the BIN checked

- If BIN of the zone is mono product and there is no rack in the BIN checked, then all racks in process must contain the same product

- If BIN of the zone are multi product, then do not check the material of the rack in process against the materials of the BIN of zone

- All the other attributes of the BIN works in the same way as the mono or multi product attribute- Mono or multi production lot attribute- Mono or multi quality status attribute- Mono or multi market attribute (note that the markets inside

the BIN must belong to the authorized markets of the zone)- Mono or multi origin code attribute- Mono or multi rack type attribute- Mono or multi velocity attribute- Mono or multi PI complete attribute

- The FIFO window works slightly differently: the time interval defined by the oldest production date and the youngest production date of the racks inside the BIN or in process must be smaller than the time interval defined as the FIFO window. Note that all the BIN of a zone have the same FIFO window.

4 Loop on action 3, with the next best fitting zone in case no best fitting BIN could be found in the last zone checked

5a The user can scan other racks to load into his forklift- Check that the new racks scanned can be stored in the determined

BIN- Consider that the determined BIN contains all the racks already in

the BIN and also the all the racks currently on the forklift for the above test

5b The user can unload all the content of his forklift into a BIN- If BIN scanned is the determined BIN, then unload all the racks

into the BIN- If BIN scanned is another BIN, then check if the BIN scanned

(considering all that it contains) can contain all the racks currently on the forklift

Notes Capacity of the storage bin :A bin marked as full will never be proposed.A bin can be proposed until its maximum capacity is reached.In case several bins have been found, the system will propose the bin where the last putaway has been done.In case there is no bin that fits the current rack criteria (= there is no bin that contains racks that have similar criteria than the current rack), the system proposes empty BIN of the best fitting zone. The user is also free to chose the bin he wants (the BIN scanned will be controlled according to the putaway strategy).The user always keeps the possibility to not chose the bin proposed by CIM+, but to select another one (and scan it with the RF) that he may

43 18/04/23 - 22:50


document.doc



consider more adequate for the storage, for example because of physical constraints, because the racks are physically already in their final destination…and provided that the location scanned will be controlled according to the putaway strategy.

4.1.13.8 FIFO window management for picking and putaway

The master data manager manages the FIFO window for each product in SAP (this is optional) : this FIFO window is modifiable by the logistics supervisors in SAP.

The FIFO window is a value in days that specifies the age window in which the product is considered equal for putaway and picking : only for mono-product storage bin. The FIFO window is set for each product and is defined in the material part master data.Multi-products location are not managed with FIFO window neither for putaway nor for picking.

Example :The FIFO window is set to 20 days and the oldest rack in the bin has been manufactured on 04th-July, CIM+ will allow to putaway additional racks in that storage bin until 24 th-July, provided that they respect the other criteria (batch number, quantity, part number…) and the bin is not set as full.

Remark :When the product is received without manufactured date, the FIFO window will begin at the date of reception.

The FIFO window will determine if some racks can still be stored in the bin, should the zone be single-part. Once the FIFO window of one bin has expired, i.e. the oldest rack’s FIFO date + the part’s FIFO window < current date, then CIM+ will not allow any more racks storage in the bin and will prompt the user to store in another one, empty if necessary.This will also ease the “pick-to-empty” process, since the FIFO management used for the picking will force the user to pick the oldest racks in the stock, that are likely to be stored in locations where no more putaway can be done because of the expiration of the FIFO window.Anyone of the racks stored in a single-part bin is valid for picking if directed to that bin.

Example :Bin 001 contains 6 racks, and the part’s FIFO window is 20 days.E000001 has a FIFO date = 08-July-02 E000002 has a FIFO date = 08-July-02E000003 has a FIFO date = 11-July-02E000004 has a FIFO date = 12-July-02E000005 has a FIFO date = 19-July-02E000006 has a FIFO date = 20-July-02

If the user receives full racks of the same part manufactured on the 24/25/26-July-02, CIM+ will propose bin 001, because 08-July + 20 days = 27-July-02 maximum.If the user receives full racks on the 29-July, they must be stored in another bin. If we pick the racks E000001 and E000002 for a delivery on the 21-July, then we can still refill bin 001 until 30-July-02 with new racks.

4.1.13.9 FIFO management for production line replenishment

44 18/04/23 - 22:50


document.doc



Stock reports can be edited at any moment by reference (for all references managed in CIM+), storage bins… (more details in TBIN06_Stocks reports and evaluation). This report will guide the user to pick (physically) the goods respecting the FIFO date to replenish the production line.

4.1.13.10 Storage location capacity management

All adjustments and updates of quantity can be done by the user with RF.1. At the creation of the bin, a notion of bin capacity can be managed : it corresponds to the theoretical

quantity of rack per storage bin. The bin have been assigned a maximum quantity of racks that can be stored in it, which depends on each physical warehouse configuration. Once this maximum capacity has been reached, the bin is automatically marked as full and thus will not be included in the storage proposal.

2. At the creation of the bin, the notion of bin capacity is not managed : the capacity is not informed. The user can store as many racks as he wants in the logical bin.

Proposition 1 and 2 can coexist.

Nevertheless, the user has also the possibility to set a full bin flag when storing some racks in one bin (proposition 1 or 2 above), if for any reason the physical configuration prevents from storing anything else in that location even if the maximum capacity is not reached. The cause of the update can be a physical obstacle, the storage of unusually large racks that prevent any additional storage in the bin.

Example : A bin has a “default maximum capacity” = 30 racks, it will remain available for storage until 30 racks are indeed putaway. But after 22 racks whose dimensions are important, the bin appears physically full, then the user can adjust the “current maximum capacity” to 22, and the location will not be proposed any more. Or if after 22 racks the user finds out that there is only room for 2 more racks, he can update the “current maximum capacity” to 24.The “current maximum capacity” will remain to 22 until it is changed again, or until all the racks are picked from that bin, which be automatically reset the current capacity to the “default maximum capacity” of 30.Last, if the current capacity is 22 and the location full, any rack pick will allow further storage in the bin until full again.

4.1.13.11 Velocity rate

Each part number can have a velocity rate which is set up in SAP for each reference : A = fast mover B = medium mover C = slow mover

All storage bin can have a velocity rate, and therefore for the putaway, the parts are stored in a storage bin which is corresponding to their velocity rate. The velocity rate of the part must match the velocity rate of the storage bin.With the product velocity rate, the warehouse manager can optimize his storage : the fast movers can be stored close to the shipping point for example.In case of overflow of the storage bin, the next storage bin must be given by the system (basis : the velocity rate of the part number).

Part X with velocity rate AIf bins with velocity rate A full, CIM+ suggests bin with velocity rate B

Part Y with velocity rate B

45 18/04/23 - 22:50


document.doc



If bins with velocity rate B full, CIM+ suggests bin with velocity rate C

Part Z with velocity rate CIf bins with velocity rate C full, CIM+ suggests location with velocity rate B. In the case that bins with velocity rate B is also full, CIM+ suggests bin with velocity rate A.

Each time the user stores products in a storage bin with a velocity rate different from the product’s one, he is warned on the RF.

Calculation of the velocity rate :Number of picking orders per product code in an interval of 1 month (at least).

Velocity rate is calculated by product in SAP

Report for velocity rate :The report shows the current velocity rate per product code and per storage bin. It proposes also to the warehouse manager the velocity which might be the more appropriate to the products.For example : A part number has the assigned velocity rate A on the report. The report also shows the number of picking orders during the last 3 months. If the number of pickings is smaller than required for an A part number, CIM+ suggests the warehouse manager to change the velocity rate.

4.1.13.12 Multi-buildings guided putaway – description of the Italian model

Description :The SGSI Savigliano’s finished products stock is physically split into 2 distinct areas : The Savigliano area located in the main factory facility ; The Aimeri area located at ~ 1 km from Savigliano factory, warehouse operated by the 3 rd party logistics

Aimeri Transporti.

The 2 places are defined as distinct work zones in CIM+, which are divided into work zones, to which are assigned the individual bins.

When working in guided putaway mode, either from production or for external receiving (transfer from another plant, reception from a sub-contractor, customer return, external purchase…), CIM+ guides the user to store the racks in the appropriate building (i.e. the one he is doing the transaction from).

Issue :

46 18/04/23 - 22:50

nombre of moves on 1 reference / month : 1 movement = 1 picking order = 1 rack picked

Velocity rate type of mover

at least 11 A Fast4 < nb mvt < 10 B Mediumnb mvt < 3 C Slow


document.doc



In Savigliano, putaway from production can only be done in Savigliano building. If necessary, the racks are later transferred to Aimeri for subsequent delivery.When receiving in the warehouse some parts, 2 modes can be used : Stock transfer operations (TINM008) : CIM+ does not guide the user, then the user chooses the

destination BIN. In all cases the storage rules are never checked. The guided put away mode (TINM006) = CIM+ chooses the “best” BIN to store the rack into, given the

storage rules defined for the particular warehouse. Moreover, the user can decide where he wants to store the rack (will be accepted provided that the storage location rules are respected, for example not 2 parts in the same location in the OEM warehouse).

The multi-buildings configuration should remain an option, activated or not (activated in Italy and in Germany – Stolberg).In case of activation, CIM+ will search the building where the user performs the putaway :

For this, assign the appropriate work zone (sort of network code) to every RF terminal and workstation. CIM+ proposes the bins of the building in which the user is logged.

47 18/04/23 - 22:50

Warehouse ID 600 -1 Warehouse ID 600-2

Public road

1 SAP plant n° 600

Productionor externalreceiving


document.doc



4.1.14 Picking strategy


Picking is the process of selecting and moving inventory : bringing the racks and the products contained in the rack from a storage bin to a staging zone in order to ship the goods. The user will be guided by the picking list. The picking precedes the shipping process for :

- External shipping- Internal shipping (intra-company flow)

Picking operations are performed using radio-frequency terminal. Picking is initiated by informing the user that there is a delivery order to process.

4.1.14.2 Picking rules

The picking checks that the racks picked corresponds to the delivery order (shipment in process) : Are mandatory :

material part number market packaging instruction

4.1.14.2.1 System-guided picking strategy for M1 & M2 (OEM).

The strategy is the following one : when condition 1 is found, look to condition 2. The pick list report is sorted by the following way :

1. All the racks in the bin will be considered as valid since they respect the FIFO window, which means the user can pick the first racks of the bin (usually they are physically stored in LIFO within one bin, due to the aisle configuration and to the stackeability of the racks). For a product (same FIFO window), the system will look for the storage bin which date of beginning of FIFO window is the oldest. If FIFO window is not managed, picking is done on FIFO date.

2. The system will propose to pick the most empty storage bin.

48 18/04/23 - 22:50


document.doc



49 18/04/23 - 22:50

1 2

3 4

001

002

007

004

003

006

005

008

009

010

013

012

011 021

014

015

016

017

018

019

020

022

023

024

025

026

027

028

029

030

5 6

7 8

031

032

037

034

033

036

035

038

039

040

043

042

041 051

044

045

046

047

048

049

050

052

053

054

055

056

057

058

059

060

STG11 STG21STG12 STG13

STG24

STG23STG22

STG25

STG26

Area 1 Area 2

5 25FIFO window : 20 days



Storage bin 001

part A, quantity 27

Storage bin 002

part A, quantity 27

Storage bin 003

part A, quantity 13

July

July

July


document.doc



Results :1. Storage bin 011 and 026 are selected.2. Storage bin 026 is finally selected.

4.1.14.2.2 System-guided picking strategy for M3 (OES)

The strategy is the following one : when condition 1 is found, look to condition 2.

The pick list report is sorted by the following way :

1. All the racks in the bin will be considered as valid since they respect the FIFO date : the oldest rack are proposed.

2. The system will propose to pick the emptiest storage location.

The pick list report does not propose stocks with the status “blocked” or “inspection”.No guided picking is proposed for the returns.

4.1.14.3 Movement path for picking

The picking path is guided by the pick list report and the way it is sorted.

The movement path is used for the picking strategy in order to optimize the change of bin one to another. The picking path proposed by the report will try to optimize the work of the user, by minimizing the amount of moves between the areas / aisles / locations depending on their physical location : The whole shipment is grouped to one picking order with the shortest movement path. Picking of the different part numbers is done aisle by aisle. Advantage : the operator does not have to go several times to the same aisle to pick the different part numbers.

For example, the rack selected by the system are in bins 032, 034, 045 and 060 : the report will edit the racks ID list in the order 032 / 034 / 045 and then 060 and not 032 / 060 / 034 / 045.

Picking list information :All the racks ID in the order that they must be picked with FIFO, packaging instruction and bin in which they are stored.

This picking report will also propose in last 5 additional racks for each triplet product code / market / packaging instruction.

When the system does not respond to all the criteria of search, the picking report will propose in last 5 alternatives racks for each couple product code / market :

racks with alternatives packaging instruction racks with more recent FIFO racks which products are not dried

This will also ease the “pick-to-empty” process, since the FIFO management used for the picking will force the user to pick the oldest racks in the stock (defined by the manufactured date), that are likely to be stored in bins where no more putaway can be done because of the expiration of the FIFO window. The CIM+ work management system is be used to efficiently manage :

- The constant flow of picking work in the facility.- The RF operators by assigning picking work based on permission, priority and proximity.

4.1.15 Transformation movements in Service Centers

50 18/04/23 - 22:50


document.doc



4.1.15.1 Production initialization in Service Centers

The business requirement for Spain Service Centers with pre-assembly activities is to keep the production initialization process and the production declaration process as simple as possible.

As the number of materials managed by these Service Centers is relatively low, this requirement will be satisfied by creating active campaigns for all materials pre-assembled, and by keeping them with status ‘active’ in the system (no campaign closing)

This operation will have to be done only one time for each material, on only one declaration point (one work center is defined for each Service Center with pre-assembly)

For production declaration, the operator will only have to select the right campaign (= material on which to produce), and then to load racks (only three scan movements for each rack).

For consumption declaration process, the operator will only have to scan the component rack and to validate the consumption (one scan movement for each rack).

4.1.15.2 Production declaration4.1.15.3 Components consumption in Spain Service Centers

The following business rules have been defined for components in Spain Service Centers:o Components in Service Centers are managed by Devisa, in Devisa stock.o The BoM of the finished product in Service Centers contains only the glass product.

For components not in BOM (all components excluding glass product):o The consumption declaration is nearly the same than activity 2C (consumption declaration for

components stocked and not in BOM) In order to take the cost of these components into account, their cost is included in

«Other variable costs» in the routing. All these components are consumed on cost center (one cost Center is defined by

Service Center), with transaction MB1A and mvt code 201.o The consumption declaration is performed at least one a month (frequency to be defined

according to the stock level accuracy requirement) in Service Centers.o The component is issued from the warehouse defined in Devisa plant for the relevant Service

Center.

For glass products:o The consumption declaration for the glass product is entered with the same general principles

than activity 1A (consumption of glass products): Consumption of glass product racks is declared in CIM+ with a RF terminal Consumption costs are collected on the cost collector of the produced material.

o The main differences are the following: Campaigns do not need to be managed in Service Centers Cases of cut-off do not need to be managed.

Note : Transactions and process flow for production initialization, components consumption and production declaration are described in TBPDC02_Production initialization, TBPDC03_Production declaration and TBPDC04_Components consumption

4.1.16 Transfer of components from general warehouse to production storage location

4.1.16.1 Pre-requites

51 18/04/23 - 22:50


document.doc



Transaction available for components which are managed in SAP and not in CIM+. This transaction is described, but maybe will not be used.

4.1.16.2 Objectives

Transfer of components to production storage location before consumption


Inputs :Transaction triggered by SAP.

Outputs :No idoc downloaded to CIM+.In SAP : transaction MB1B, movement 311. Stock of component transferred is in production storage location.

4.1.16.4 Process flow


Step Responsible Description SAP flow

1 Operator (can be a production operator, a purchaser…)

Perform transaction MB1B to enter in SAP stocks transfers.Movement type 311PlantSAP material numberQuantityThe issuing storage location is automatically retrieved by the systemEnter receiving storage location and validate

MB1B, movement 311

52 18/04/23 - 22:50

G e n e r a l w a r e h o u s e s t o r a g e l o c a t i o n :

c o m p o n e n t s

P r o d u c t i o n s t o r a g e l o c a t i o n

O p e r a t o r

T r a n s f e r f r o m G W t o p r o d u c t i o n

M B 1 B , M o v e m e n t 3 1 1


document.doc



4.1.17 Drying time management

Drying time management The Drying Time is declared in the Material Part Master Data in SAP and is integrated with the Material Part in CIM+. The End of drying date is not available in SAP MM view. The value is 0 or > 0. CIM+ calculates the End of drying date = date of production declaration + number of days of drying.

Production declaration At production declaration, the End of Drying Date is also declared. Warehouse management When racks (containing products which Drying Time > 0) are put away in

LOGISTICS zone : they have to be kept in stock during few days (5 days in average) before products are completely dried and can be delivered (theoretically). The user has a visibility on these products managed with a Drying Time : the inventory screen CIM+ gives for each rack, part… the manufactured date and the date of End of Drying Date.The manufactured date and the End of Drying Date have to figure on the internal label.

End of Drying Date The products with a Drying Time > 0 are declared with the status “Unrestricted”. These products are declared in CIM+ with an End of Drying Date. The End of Drying date ignores the hours and the minutes. It makes no difference whether a rack was received from production declaration the morning or the evening. In both cases the rack will have the same Drying Time. If a rack has a manufactured date on Monday 17/06/02 and its drying time is 3 days, products will be dried on Thursday. When the End of Drying date is reached, the product can be transformed or / and be delivered to the final customer.

Shipping management Sometimes the products have to be delivered to the SCs (lack of storage place in the warehouse, customer order : the products have to be delivered to the SC) before End of Drying date is reached. The user has to be warned at picking that he is picking products not dried. At the Extrusion / Encapsulation plant, the selection guide proposes the racks which products are not dried for the deliveries to the SCs but not the ones for the final customer.

FP B Drying Time > 0 At Extrusion / Encapsulation plant

Shipping to final customer is forbidden, but shipping to SC is authorized : the user has to be warned. Internal moves from storage bins to others are allowed respecting the rules defined between storage bins.

FP B Drying Time > 0At the Service Center

Shipping to the final customer may be possible (with agreement of logistics supervisor and warning at picking), for example : at the departure products are not dried but because of a long carriage they can dry on the road. These products cannot be transformed if an operation of premontage for example is required.

At the SC, these products can be returned to the vendor after quality inspection (before the operation of premontage).

FP B Drying Time = 0 (status unrestricted)At Extrusion / Encapsulation plant

When products are dried (no idoc up to SAP), the racks can be shipped to the SC or to the final customer if they do not transit by a SC.

FP B Drying Time = 0(status unrestricted)

These products can be transformed.If no process of transformation : the shipping to the final customer is

53 18/04/23 - 22:50


document.doc



At the Service Center authorized. ASN between CIM+ - Plant and CIM+ - SC

The information of end of drying date is included in the Advanced Shipment Notification (ASN) that gets exchanged between CIM+ sites.

4.1.18 Traceability

Windshields are considered as security parts by constructors, Sekurit has to keep historical data in an archiving system for a certain duration (15 years for security parts – Norm 43R).

Traceability must be ensured all along the supply chain from bending plants to final customers.- Within a Sekurit location (internal link)- Between two Sekurit locations (external link)

Traceability support is :- Labels serial numbers (internal label and customer label)* - Rack serial numbers

* : Customer label, refer to TBIN08_Process ShipmentsInternal label is harmonized for all countries in all the supply chain to facilitate products interpretation and international exchanges.

4.1.18.1 Internal label

54 18/04/23 - 22:50


document.doc



Description Ex. printed value Bar codedLabel serial number 560000012 XRack Id F000001SAP product code 1081343 XOEM logo Y or N, printed : "LOGO" or

"NO LOGO"External color / Internal color TSA3+ / PLXVisa box and logo qualityCustomer reference 6025410900Composition (external thickness / internal thickness)

2.6 / 2.1

Part master type Printed : “PROTOTYPE” if ZPRO, nothing if not ZPRO

Real quantity 032 XStandard quantity 032Product ID CITN68—RDL01AAA0

55 18/04/23 - 22:50


document.doc



Batch number 5601 XProduct description PICA.TE.--.-WP-.---.X--Origin code 560 XProduct status AReason description Only when status is B or QExternal material group (customer revision level)

18 digits max

Technical version 01Production lineProduction date 21-SEP-02 10:35Market M1 XRack type P04Net weight (KG) 1109Drying date 26-SEP-02Gross weight (KG) 1135Printed date 21-SEP-02 10:35

Label serial number : single incremental number. The same label number is used on each label of a mixed rack. The codification is PPPNNNNNN, PPP is the plant ID where the product has been manufactured. For external reception without ASN, PPP becomes the plant ID of the reception site.

SAP product code : information common in Sekurit Avenir scope (always 7 numeric digits). Real quantity : current quantity of product on the rack. Batch number : is defined in the manufacturing plant. Codification : PPP (plant ID) followed by an

incremental number. Origin code : used only for finished products. It permits to know where the products come from not to

mix different origin in production or in put away. Codification : PPP (alphanumeric) (corresponds to the plant ID or to a sub –contractor, e.g. : SME for SMET in Italy).

Market : permits to respect the criteria of put away, the values are M1, M2 or M3 Rack type : permits to respect the criteria of put away. Standard quantity : is useful to determine if a rack is complete or not. Product status : 3 different values, A : unrestricted use, B : blocked, Q : Quality inspection. Serial rack number : is readable in all sites. The information is not displayed on the label when labels

are printed before production declaration. Car maker logo : informs production and logistics people if there is a customer logo on the glass or

not. Composition (thickness) : always displayed in mm, is not in the product description. Net and gross weight : unit of measure is the KG. External material group (customer revision level) : not to mix different revision level in the same

production. It is a light product or process change imposed by the customer : it can be a date, alphanumeric characters…

Production date : date and time of production declaration on the label, the label traceability will be better. Codification : DD-MMM-YY hh:mm. It is manually written on the label when the labels are printed before production declaration. The production date is conserved on the label as soon as there is a next production declaration and even if the rack is re-labeled for any type of reason (change of market, change of status, repackaging, receiving without ASN…)

Drying date : is the End of drying date for the finished products that require a drying time. Codification : DD-MMM-YY.

Printed date : is different from the production date when the label are printed before production declaration.

Production line : useful for production people (label traceability). Product description

56 18/04/23 - 22:50


document.doc



E.g.: CITN68--S3L01AB+0.PICA.TE--.-WP-.---.X--

The structure of this Product Description is the following:

1 2 3 4 5 6 7 8 910

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

e.g. : C I T N 6 8 - - S 3 L 0 1 A B + 0 . P I C A . T E - - . - W P - . - - - . X - -

1 2 3 4 5 6 7 8 910

11

12

13

14

15

16

Product ID: 17 characters (refer to the following chapter for a detailed definition of the product ID)Car Model: 4 charactersGlass Type: 1 character (T for Tempered, L for Laminated, D for Double Glazing, M for Multi-Laminated, ‘-’ for Not Applicable)External Color: 1 character (color “letter” as defined in the classification) Internal Color: 1 character (color “letter” as defined in the classification) or ‘-’ for No applicablePVB: 1 character (S for Standard, A for Acoustic, H for HUD, T for Tinted, O for Others, ‘-’ for No Applicable)Heated: 1 character (C for heatable by coating, W for heatable by wires (Totally or Partially) P for heatable by silk print (Totally or Partially) or ‘-’ for Not Applicable)Antenna: 1 character (W for Wires, P for Printed, L for Layer or ‘-’ for No Antenna)Alarm: 1 character (W for Wires, P for Printed or ‘-’ for No Alarm)VIN Label : 1 character (V for VIN Label or ‘-’ for No VIN Label)Rain Sensor: 1 character (R for Rain sensor or ‘-’ for No Rain sensor)Mirror Bracket: 1 character (M for Mirror Bracket or ‘-’ for No Mirror Bracket)Infra Red reflecting: 1 character (K for KAPPA, A for AIRCO, P for PET, 3 for 3M, O for Other, or ‘-’ for No Solar Control)Extrusion: 1 character (X for Extruded or ‘-’ for Not Extruded or Later Extruded)Encapsulation: 1 character (Y for Encapsulated or ‘-’ for Not Encapsulated or Later Encapsulated)Primer: 1 character (P for Primer or ‘-’ for No Primer)

Objectives

The product ID will be printable on the internal and external labels of the racks.Moreover, it will be possible to barcode it on internal labels (compliant with the font “3 of 9”)

Any update of the Product ID must be triggered by an Official Request of the Customer of Saint-Gobain Sekurit : new OEM revision level or new OEM part number. For more details of the impacts of the revision level on the Product Id, refer to the To-Be-Process “TBMD02 - Revision Level”.

The Product ID must be created / updated in the Change Management Tool and downloaded in SAP system, or be manually entered in the Material Master Record.

Product ID structure

57 18/04/23 - 22:50


document.doc



The structure of this Product ID is composed of two main parts: A fixed aggregation of characteristic values1 defining the project the product belongs to. A group of five meaningful indexes or indicators defining the different versions and evolution of

the product.

E.g.:

1

58 18/04/23 - 22:50

CITN68--RDL 01 A A A 0

Index for glass version

Index for glass evolution

Index for extrusion /encapsulation evolution

Index for pre-assembly evolution

Indicator for pre-assembly’s sequencing

Project description

CITN68--RDL 01 A A A 0

Index for glass version

Index for glass evolution

Index for extrusion /encapsulation evolution

Index for pre-assembly evolution

Indicator for pre-assembly’s sequencing

Project description


document.doc



Product ID definition

This paragraph gives a detailed definition of the Product ID, based on the following example:

C I T N 6 8 - - R D L 0 1 B C A 0

1 2 3 4 5 6 7 8 9

1) Car Brand or Roof Maker: 3 characters (if a Roof Maker has been specified in the classification, it will prevail on the Car Brand)

2) Development Code: 5 characters.

3) Glass Position: 2 characters.

4) Side: 1 character (R for Right, L for Left or ‘-‘ for No Applicable).

5) Glass Version Index: 2 numerals.Index corresponding to a set of functional features of the product. The exhaustive list of these features is:

Glass Type External Color Internal color Infra red reflecting Mobile Heated Antenna (Yes/No) Alarm (Yes/No) PVB Shade Band Color Logo (Yes/No) VIN Label window Number of holes Printing (Yes/No)

59 18/04/23 - 22:50

To Be ProcessProcess Internal Movements

IN03- Internal movements

Special functions

Any variant/modification of one or several of these functional features will initialize a new Glass Version.N.B.: Modifications that only affect the extrusion, the encapsulation and / or the Pre-assembly will not have any impact on the Glass Version

Example: Peugeot 206 Windscreen

Customer reference Differentiating FeaturesGlass Versio

n8200677480 Green, with Primer… 018200677493 Green, without Primer… 018200677527 Grey, with Primer… 028200677614 Grey, without Primer… 028200677628 Green with VIN Label… 038200677701 Grey with VIN Label… 04

6) Evolution index for glass: 1 letter.Initialized to ‘A’, this index will change whenever, further to the Customer’s request, there is a change of the geometrical features of the glass product (all other modification on the glass that is not a modification of Glass Version)

7) Evolution index for Encapsulation / Extrusion: 1 characterThis index will change whenever, further to the Customer’s request, there is a change of the encapsulation and/or extrusion process’ of the product.

When the encapsulation and/or extrusion process’ takes place in the underway Plant or in any up-stream Plant the index will be a letter (from A to Z).

When the encapsulation and/or the extrusion process’ takes place in any down-stream plant the index will be ‘+’.

When the product is not Encapsulated nor Extruded all along its whole production process the index will be ‘-’.

8) Evolution index for Pre-assembly: 1 characterThis index will change whenever, further to the Customer’s request, there is a change of the pre-assembly process’ of the product.

When the pre-assembly process’ takes place in the underway Plant or in any up-stream Plant the index will be a letter (from A to Z).

When the pre-assembly process’ takes place in any down-stream plant the index will be ‘+’.

When the product is not pre-assembled all along its whole production process the index will be ‘-’.

9) Indicator for pre-assembly’s sequencing: 1 numeralThis index allows distinguishing the different pre-assembly sequencings between SGS entities.This index will change whenever several pre-assembly sequencings are carried-out for the same final product (sold to an External Customer). Each index will characterize a pre-assembly process’.

Created by : Geoffroy KriegModified by: Elian Faggion

Page 60 / 72 Created on : 01 September 02Modified on : 18 April 2023



However, as this index is only related to internal pre-assembly flows, the product sold to an External Customer, or without preassembly on it, will always have this index set to ‘0’ (‘non used’)

Product ID indexes’ management

Each time the Glass Version Index changes (new functional feature), all the 3 evolution indexes will be re-initialized at the initial position (‘A’)

The 3 evolution indexes will evolve individually The Glass Version Index (related to the manufacturing process in the glass plant) will prevail on the

evolution indexes. If both occurs at the same time (for example thickness and color), only the new version will be considered.

The Indicator for pre-assembly’s sequencing will not change for a modification of the type of pre-assembly (except if it only impacts the process).

Examples of Product ID on simple Flows

Assumptions:

Extrusion / Encapsulation takes place in an Extrusion / Encapsulation Plant Pre-assembly takes place in a Service Center

Example #1: Extruded and Pre-assembled Product

Example #2: Extruded and not Pre-assembled Product

Example #3: Pre-assembled and not Extruded Product



CITN68--WS- 01 A + + 0

Glass Plant Ext/Enc Plant Service Center

CITN68--WS- 01 A A + 0 CITN68--WS- 01 A A A 0

OEM

CITN68--WS- 01 A + + 0


CITN68--WS- 01 A A + 0 CITN68--WS- 01 A A A 0

OEM

CITN68--WS- 01 A + - 0

Glass Plant Ext/Enc Plant

CITN68--WS- 01 A A - 0

OEM

CITN68--WS- 01 A + - 0

Glass Plant Ext/Enc Plant

CITN68--WS- 01 A A - 0

OEM

CITN68--WS- 01 A - + 0

Glass Plant Service Center

CITN68--WS- 01 A - A 0

OEM

CITN68--WS- 01 A - + 0

Glass Plant Service Center

CITN68--WS- 01 A - A 0

OEM



Example #4: Not Extruded and not Pre-assembled Product

Example of Product ID on multiple Flows

Assumptions:

Extruded and Pre-assembled Product, with different pre-assembly flows Extrusion / Encapsulation takes place in an Extrusion / Encapsulation Plant

In this example, the different pre-assembly operations take place in different places, but the product sold to the OEM is always the same

4.1.18.2 Logistic needsTo locate a part of productionTo determine a part of production in case of quality problemTo be able to choose to deliver a set of part before an other To be able to prohibit the picking of a set of racks



CITN68--WS- 01 A - - 0

Glass Plant OEM

CITN68--WS- 01 A - - 0

Glass Plant OEM

CITN68--WS- 01 A + A 1


CITN68--WS- 01 A A A 1 CITN68--WS- 01 A A A 0

OEM

Flow 1 :Pre-assembly Operations : Mirror Bracket Primer

CITN68--WS- 01 A + A 2 CITN68--WS- 01 A A A 2 CITN68--WS- 01 A A A 0Flow 2 :Pre-assembly Operations : Mirror BracketPrimer

CITN68--WS- 01 A + + 0 CITN68--WS- 01 A A A 3 CITN68--WS- 01 A A A 0Flow 3 :Pre-assembly Operations : Mirror BracketPrimer

CITN68--WS- 01 A + + 0 CITN68--WS- 01 A A + 0 CITN68--WS- 01 A A A 0Flow 4 :Pre-assembly Operations : Primer +Mirror Bracket

CITN68--WS- 01 A + A 1


CITN68--WS- 01 A A A 1 CITN68--WS- 01 A A A 0

OEM

Flow 1 :Pre-assembly Operations : Mirror Bracket Primer

CITN68--WS- 01 A + A 2 CITN68--WS- 01 A A A 2 CITN68--WS- 01 A A A 0Flow 2 :Pre-assembly Operations : Mirror BracketPrimer

CITN68--WS- 01 A + + 0 CITN68--WS- 01 A A A 3 CITN68--WS- 01 A A A 0Flow 3 :Pre-assembly Operations : Mirror BracketPrimer

CITN68--WS- 01 A + + 0 CITN68--WS- 01 A A + 0 CITN68--WS- 01 A A A 0Flow 4 :Pre-assembly Operations : Primer +Mirror Bracket



For this, logistics wants to go back to the origin of a batch number from a rack ID.The technical version is changed when there is modification on the reference (serigraphy…). The technical version will be a free field used or not used.

4.1.18.3 Campaign

4.1.18.3.1 DescriptionFor more details refer to TBPDC02_Production initialisation.

Campaign number (CIM creation) Work Center (Main) / Machine group Product ID Product Number Production Version Date of production beginning automatically created Date of the end of production automatically created Market, used by default on the batches linked to the campaign Status

The campaign number is a sequential number identifying a campaign planed on the installation. This identifier is linked to the main Work Center of the installation. The identifier is single for a site.

4.1.18.3.2 Traceability and follow-up

The campaign is a local data.The data of the campaign is not transmitted to the other sites and is not printed on the internal or customer labels.

4.1.18.4 Technical version (TV)

4.1.18.4.1 Definition

Technical version represent an internal change of the product. This change can be decided in order to ensure : An evolution of the producing method for a better answering to the customer specification. An optimization of the producing method, while respecting the customer specification.

The changes on the producing methods can affect :

The process (routing) The choice of the components.

Those changes can imply:

A physical modification on the product ( New layer for the heating system). Non physical modification on the product ( Better follow-up of OEM specification, new component

supplier)

The Technical Version is managed in the site which produces the parts. The TV creations are defined by the production department. The Technical Version is a batch attribute and then can be changed on the batch. When the TV is changed, the batch is also changed.





Several TV can exist on the same campaign.The main reasons are described below :

Family Sub-Family DetailsChange of component Material

HoldersRetro supportRain detector supportSilver pasteSolderTV on basisPVB TypeSupplier Locating pieceAdhesive tape

Process change Oven / Oven TypePre-Positioning Methodenamelling rangeCalendering CircuitSticking TypeBending Tool Modification Tempering Shape

Pickup TypeSkeleton TypeMould

Cut BackCutting - GrindingClippingInjection Process Varnish

Control method Support typeSupport positionmeasuring Pointsmeasuring tool positiontolerance

Dimensional modification CuttingBending

4.1.18.4.2 Description

Technical version Date of production beginning automatically created Date of the end of production automatically created (by the production beginning of the next TV)

4.1.18.4.3 TV traceability and follow-up

The TV is transmitted by ASN because it is a batch attribute. The TV remains unchanged during the transfers (inter or intra company). It is preserved until the parts either are delivered or consumed to produce another product.





The TV are only visible between SGS sites, and never for the customer.

Received products from a non-V2 site : No TV created on the receiving site. 4.1.18.5 Batch number

4.1.18.5.1 Definition

The batch number is an identifier given to goods manufactured during the same campaign, or a part of the same campaign.A batch number is created automatically during the creation of the campaign. It is used as soon as the declaration of the first product. It is possible to create a new batch number during a campaign. The parts are always identified in reference to their original campaign until they are possibly transformed into an other product.

4.1.18.5.2 Description and codification

Batch number Production line Facultative : Technical version (codification 2 digits from 00 to 99) Date of beginning of the production, automatically created. Date of end of the production, automatically created.

Codification :PPP + incremental number

4.1.18.5.3 Traceability and follow-up

The batch number is displayed on the Internal Label. The batch number is affected to a set of goods on the rack. If the goods are transferred from one rack to another rack, the batch number is preserved. The batch is also preserved for inter or intra company flows. Received products from a non-V2 site : If incoming products have a batch number (on the label), this number is used. If incoming products do not have a batch number, no batch number is created.

4.1.18.6 Traceability

A the link between consumed and manufactured products from bending plants to final customer will be available. 2 types of links will be used : internal links and external links.Internal link :

- Through the batch number- Through the label number- Through the production date

External link :- Through the Customer label

Through the shipping / reception document number





4.2 Country or customer specific - process flow and descriptionSame objectives as above but concerning eventual country specific process steps. Again, if the whole process is harmonized across all countries, this section is empty. This topic can be subdivided in different section to cover the different functional cases mentioned in §2.1.

4.2.1 Country specific process Flow – country-1

Scheme / diagramText - text - textText - text - text

4.2.2 Country specific process Flow – country-2

Scheme / diagramText - text - textText - text – text

5 Key elements of system implementation5.1 Core model – Key elements of system implementationDescribe the main SAP related elements supporting the processes and rules mentioned above, by step if relevant :

data to be initialized, impact on master data, customizing ground decisions

Those SAP implementation elements should be valid for all countries except the ones mentioned below. This topic can be subdivided in different section to cover the different functional cases mentioned in §2.1.

+Log the AIG references and whether they are accepted or rejected.

5.1.1 Change of material code initiated by CIM+

SAPTransaction

Movement type triggered in SAP

TIMN003

WMMBXY idocMB1B

309 Change of product code from ZPRO to FER1.

5.1.2 Cycle counting

Transaction Movement type triggered in SAP

Use

WMMBXY idoc, MB1A

701 Positive adjustment of unrestricted use stock : Cycle counting : 19

702 Negative adjustment of unrestricted use stock : Cycle counting : 19

703 Positive adjustment of quality inspection stock : Cycle counting : 19

704 Negative adjustment of quality inspection stock : Cycle counting : 19

707 Positive adjustment of blocked stock : Cycle counting : 19





708 Negative adjustment of blocked stock : Cycle counting : 19

5.1.3 Scrapping in CIM+

SAPTransaction


Use for materials managed in CIM+ : TINM007

MB1A, WMMBXY idoc

551+ reason code

Physical scrap from unrestricted use stock.Used to put a material into scrap from the unrestricted use stock, if it is a warehouse scrap (handling), or a scrap of obsolete stock.The quantity keyed is the quantity to be scrapped.

MB1A, WMMBXY idoc

552+ reason code

Cancellation for movement 551(quantity keyed – label current quantity) = quantity to be reversedNote : quantity keyed must be > label current quantity in order to trigger the reverse movement.

MB1A, WMMBXY idoc

553+ reason code

Physical scrap from quality inspection use stock.Used to put a material into scrap from the quality inspection stock, if it is a warehouse scrap (handling), or a scrap of obsolete stockThe quantity keyed is the quantity to be scrapped.

MB1A, WMMBXY idoc

554+ reason code


MB1A, WMMBXY idoc

555+ reason code

Physical scrap from blocked stockUsed to put a material into scrap from the blocked stock, if it is a warehouse scrap (handling), or a scrap of obsolete stock. The quantity keyed is the quantity to be scrapped.

MB1A, WMMBXY idoc

556+ reason code


MB1A, WMMBXY idoc

921+ reason code+ responsible plant

Scrap after physical return from external customer for unrestricted use stock Used to put a material into scrap from the unrestricted use stock, if it is scrap after an external customer return.The quantity keyed is the quantity to be scrapped.

MB1A, WMMBXY idoc



MB1A, WMMBXY idoc


Scrap after physical return from external customer for quality inspection stockUsed to put a material into scrap from the quality inspection stock, if it is scrap after an external customer return.The quantity keyed is the quantity to be scrapped.

MB1A, WMMBXY idoc

924+ reason code+ responsible

Cancellation for movement 923(quantity keyed – label current quantity) = quantity to be reversedNote : quantity keyed must be > label current quantity in order to trigger





plant the reverse movement.MB1A, WMMBXY idoc


Scrap after physical return from external customer for blocked stockUsed to put a material into scrap from the blocked stock, if it is scrap after an external customer return.The quantity keyed is the quantity to be scrapped.

MB1A, WMMBXY idoc



MB1A, WMMBXY idoc


Scrap after physical return from internal customer for unrestricted use stock Used to put a material into scrap from the unrestricted stock, if it is scrap after internal customer return.The quantity keyed is the quantity to be scrapped.

MB1A, WMMBXY idoc



MB1A, WMMBXY idoc


Scrap after physical return from internal customer for quality inspection stockUsed to put a material into scrap from the quality inspection stock, if it is scrap after internal customer return.The quantity keyed is the quantity to be scrapped.

MB1A, WMMBXY idoc



MB1A, WMMBXY idoc


Scrap after physical return from internal customer for blocked stockUsed to put a material into scrap from the blocked stock, if it is scrap after internal customer return.The quantity keyed is the quantity to be scrapped.

MB1A, WMMBXY idoc



5.1.4 Logistics scrap of components not managed in CIM+

SAPTransaction


Use for materials in General Warehouse storage location

MB1A 551 General warehouse scrap from unrestricted use stockUsed to put a component into scrap from the unrestricted use stock, if it is scrap for logistics deterioration (handling) or obsolescence.

5.1.5 Change of market initiated by CIM+

Transaction Movement type Use for FINISHED PRODUCTS TINM002





type in SAP triggered in SAPMB1B or WMMBXY idoc

311 Transfer from storage location to storage location – Unrestricted useUsed when we want to change materials in unrestricted use stock type, from one storage location to another one in the same plant.

Change of market on Unrestricted use stock in Logistics zone:M1 to M2, M1 to M3M2 to M1, M2 to M3M3 to M2, M3 to M1All the rack content is updated.

MB1B or WMMBXY idoc

312 Cancellation for movement 311Used to correct a transfer between two storage locations error.

Does not exist, all movements are described with 311.

MB1B or WMMBXY idoc

323 Transfer from storage location to storage location - quality inspection stock. Used when we want to change materials in quality inspection stock from one storage location to another one within the same plant.

Change of market on “Quality inspection” stock in Logistics zone :M1 to M2, M1 to M3M2 to M1, M2 to M3M3 to M2, M3 to M1All the rack content is updated.

MB1B or WMMBXY idoc

324 Cancellation for movement 323Used to correct a transfer between two storage location in quality inspection stock.


MB1B or WMMBXY idoc

325 Transfer from storage location to storage location - blocked stock.Used when we want to change materials in blocked stock from one storage location to another one within the same plant.

Change of market on Blocked stock in Logistics zone:M1 to M2, M1 to M3M2 to M1, M2 to M3M3 to M2, M3 to M1All the rack content is updated.

MB1B or WMMBXY idoc

326 Cancellation for movement 326Used to correct a transfer between two storage location in blocked stock.


No idoc No movement No transfer Change of market on Unrestricted use, Quality inspection or Blocked stock in Production zone:M1 to M2, M1 to M3M2 to M1, M2 to M3M3 to M2, M3 to M1

Cancellation movements do not exist in CIM+. So change status movements are never cancelled, it is just the way that changes.

5.1.6 Transfer of components to production zone before consumption

Transaction type in SAP


Description of movements TINM08

MB1B or WMMBXY idoc


Transfer of bases, semi-finished products and finished products to production.





5.1.7 Putaway and stock transfer initiated by CIM+



Description of movements TINM006 / TINM008

MB1B or WMMBXY idoc


Putaway or transfer from production to Logistic (TINM008 and TINM006).All the rack content is updated.

MB1B or WMMBXY idoc

312 Cancellation for movement 311Used to correct a transfer between two storage locations error.


MB1B or WMMBXY idoc

323 Transfer from storage location to storage location - quality inspection stock. Used when we want to change materials in quality inspection stock from one storage location to another one within the same plant.

Transfer from production to Logistic (TINM008).All the rack content is updated.

MB1B or WMMBXY idoc

324 Cancellation for movement 323Used to correct a transfer between two storage location in quality inspection stock.


MB1B or WMMBXY idoc

325 Transfer from storage location to storage location - blocked stock.Used when we want to change materials in blocked stock from one storage location to another one within the same plant.

Transfer from production to Logistic (TINM008).All the rack content is updated.

MB1B or WMMBXY idoc

326 Cancellation for movement 326Used to correct a transfer between two storage location in blocked stock.


5.1.8 Stock transfer of finished products initiated by CIM+



Use for FINISHED PRODUCTS TINM008

MB1B,WMMBXY idoc

631 Transfer from Unrestricted use stock to customer consignment :Movement initiated by CIM+ when the stock is transferred from Logistics zone to Sequencing zone : the inventory content status is updated to k.

Transfer to sequencing zone, or transfer to customer consignment.

5.1.9 Stock transfer of glass, PVB / PET initiated by CIM+



Use for Glass, PVB / PET TINM008

MB1B,WMMBXY idoc

411 Transfer from Logistics to Production :Movement initiated by CIM+ when the stock is transferred from consignment stock to own stock.

Transfer to production zone





5.1.10 Change of material status initiated by CIM+



Use for all products managed in CIM+ TINM001

MB1B WMMBXY idoc

321 Transfer from quality inspection stock to unrestricted use stockUsed when we want to change materials from quality inspection stock to unrestricted use stock, within the same storage location.

Transfer from quality inspection stock to unrestricted use stock :Transfer only within the same SAP storage location.

MB1B WMMBXY idoc

322 Cancellation for movement 321Used to : - Correct a transfer error from quality

inspection stock to unrestricted stock,- or to transfer materials from unrestricted

use to quality inspection stock, within the same storage location.

Transfer from Unrestricted use stock to Quality inspection stock :Transfer only within the same SAP storage location.

MB1B WMMBXY idoc

343 Transfer from blocked stock to unrestricted use stockUsed when we want to change materials from blocked stock to unrestricted use stock, within the same storage location or from one storage location to another one.

Transfer from Blocked stock to Unrestricted use stock :Transfer only within the same location.

MB1B WMMBXY idoc

344 Cancellation for movement 343Used to : - Correct a transfer error from blocked

stock to unrestricted stock,- or to transfer materials from unrestricted

use stock to blocked stock, within the same storage location or from one storage location to another one.

Transfer from Unrestricted use stock to Blocked stock :Transfer only within the same SAP storage location.

MB1B WMMBXY idoc

349 Transfer from blocked stock to quality inspection stockUsed when we want to change materials from blocked stock to quality inspection stock, within the same storage location or from one storage location to another one.

Transfer from Blocked stock to Quality inspection stock :Transfer only within the same SAP storage location.

MB1B WMMBXY idoc

350 Cancellation for movement 349Used to : - Correct a transfer error from blocked

stock to Quality inspection stock,- or to transfer materials from quality

inspection stock to blocked stock, within the same storage location or from one storage location to another one.

Transfer from Quality inspection stock to Blocked stock :All the rack content is updated. Transfer only within the same SAP storage location.

5.1.11 Consumption declaration in CIM+



Description and materials Accounting assignment





MF4U 261 Consumption of raw glass, manufactured products and PVB/PET rollsUsed when these materials are consumed in the production zone.

Cost collector

5.1.12 Consumption declaration in SAP



Description and materials Accounting assignment

MB1A WMMBXY idoc

291 Consumption of Silver paste, enamels, polymers

Cost object

MB1A WMMBXY idoc

291 Consumption of other components in BOM

Cost object

MB1AWMMBXY idoc

201 Consumption of components managed in stock but not in BOM

Cost center

5.2 Summary

6 Organizational roles and impacts

7 Application specific development requirements

Specific SAP transaction In Bound Interfaces Forms Job Aids (other : Excel,…)Modified SAP transaction Out Bound Interfaces EDI transactions Other

Modified SAP program (other) Reports Legacy Change Requirements



Date post:	20-Dec-2015
Category:	Documents
Upload:	jay-saji-kulathakal
View:	10 times
Download:	3 times

ACO MM TBP 45 Process Internal Moves- V3.1

Documents