PI Sheets for ManufacturingDocument Information

Note: All dates in this document should be using the format DD. Month YYYY (e.g. 21. May 2001).

Important Note: This guideline is still in draft form and several sections will be revised when Integration Testing 1 and 2 are completed.

GENERAL INFORMATION

REVIEW / APPROVAL

Function Dept. Approved by Date

Rev

iew Name:_______________________

Signature:_____________________

(Format DD. Month YYYY)

Ap

pro

val Name:_______________________

Signature:_____________________

(Format DD. Month YYYY)

Version Reason for Change Guideline Effective Date

Data Guideline Specification

DATA FIELD GUIDELINE

Description of the Data Field.The PPPI Process Instruction sheet in SAP requires the following configuration & master data objects:

- Master Recipe- Resource- Process Instructions- Production Supply Areas- Control Cycle Records- BOM- Control Recipe Destinations

Data Guideline Explanation The intention with this guideline is to assist the implementation team on the various Tokyo sites going live with EARTH Template version1 on how to structure the master data to create PI Sheets for consumption, receipts and confirmations.

Applicable SAP field(s)

REASON FOR DATA GUIDELINE

Reason for introduction of this Data Guideline.The current configuration for EARTH Template offers multiple options for batch and storage unit management of materials is fairly complex and requires a full understanding of the master data to generate PI Sheets with the appropriate facilities for material receipts, consumption and order confirmations.

This guideline gives an outline of the different options available for the PI Sheet and the master data needed for their generation. This guideline should be read in conjunction with the guideline for material consumption and warehouse storage locations.

DEPENDENCIES

Dependencies from.GT_Guideline_Storagelocation_Warehouse.docGT_15_PRD_Guideline_Matconsumption.docGT_15_PRD_PM_Guideline_PI_Sheet_MFLOW.doc

Dependencies to.

Table of Contents

1 Material Handling Options for Production_________________________________________6

1.1 Introduction____________________________________________________________________6

2 PI Sheets - General Facilities____________________________________________________8

2.1 PI Sheet - Use___________________________________________________________________8

2.2 PI Sheet - Header________________________________________________________________9

2.3 PI Sheet – General Structure_____________________________________________________10

2.4 PI Sheet – Calling Transactions___________________________________________________10

2.5 PI Sheet - Data Entry____________________________________________________________11

2.6 PI Sheet – Data Entry Validation__________________________________________________12

2.7 PI Sheet – Data Entry Copy details from SAP_______________________________________14

2.8 PI Sheet - Integrated Batch Management___________________________________________14

2.9 PI Sheet – Writing Data back into the PI Sheet______________________________________15

2.10 PI Sheet - Reporting Data________________________________________________________16

2.11 PI Sheet - Signature_____________________________________________________________17

3 Master Data & Configuration Objects____________________________________________18

3.1 Master Data Structure___________________________________________________________183.1.1 Material Handling_____________________________________________________________________183.1.2 Master Recipes_______________________________________________________________________183.1.3 Material Allocation____________________________________________________________________203.1.4 Material Staging______________________________________________________________________203.1.5 BOM Master Data - Sort Strings__________________________________________________________213.1.6 Sort string - values_____________________________________________________________________22

4 PI Sheets & Control Recipes____________________________________________________23

4.1 PI Sheets & Control Recipes______________________________________________________23

4.2 Control Recipe Monitor Transaction CO53_________________________________________24

4.3 PI Sheet - Control Recipe Destinations_____________________________________________24

4.4 PI Sheet - Transaction Execution Modes____________________________________________254.4.1 Direct call of SAP transactions___________________________________________________________254.4.2 Indirect call of SAP transactions__________________________________________________________25

5 Process Message Management__________________________________________________26

5.1 Process Messages Monitor_______________________________________________________26

5.2 Process Messages_______________________________________________________________27

6 Process Order Status Manager__________________________________________________28

7 PI SHEETS – Material Receipts________________________________________________29

7.1.1 CRD Y1: PI GR (Preferred)_____________________________________________________________297.1.2 CRD Y2: PI Sheet Receipt (Optional)______________________________________________________307.1.3 CRD Y3: PI Sheet Receipt (Mandatory for SU Materials)______________________________________307.1.4 CRD Y4: PI Sheet Receipt (Preferred for non Batch materials)__________________________________317.1.5 CRD Y5: No Goods Receipt on the PI Sheet________________________________________________317.1.6 Y6, Y7______________________________________________________________________________31

8 PI SHEETS – Material Consumption____________________________________________32

8.1 Sort String = Blank – Materials NOT ON the PI sheet________________________________32

8.2 Sort String = 1 – By Product Materials_____________________________________________32

8.3 Sort String = 2 – Materials ON the PI Sheet_________________________________________328.3.1 Back-flushed Components_______________________________________________________________328.3.2 Batch Managed Materials_______________________________________________________________32

8.4 Sort String = 3 – Materials Storage Unit Managed___________________________________34

8.5 Sort String = 6 – MFLOW_______________________________________________________34

8.6 Sort String = 4 – Consignment Stock________________________________________________34

1 Material Handling Options for Production

1.1 Introduction

The functionality provided by EARTH Template V1.5 for material handling are basically divided into two different packages, each with significantly different functionality. The factory will have to decide which one of the packages to use for material supply and receipts from production.

The criteria for selection of the package will depend upon how the factory wishes to make use of batch management and storage unit management for traceability and control of materials in production. Each function brings with it a level of business benefit, master data complexity. The factory must decide:

1) Where, when, and how materials will be moved, consumed or produced.

2) The level of recording online in SAP or off line through a combination of operational and 'back office' procedures

3) The level of detail required for batch management and traceability, by pallet, material and quantity.

4) What other systems that are already in place will need to be retained, replaced by SAP or modified to support the EARTH template implementation.

The EARTH template is scaleable and each package will be more or less appropriate for a given business requirement.

The first package enables the factory to make use of bar code scanning keyboard data entry functionality for material consumption through a custom EARTH materials-handling developed SAP front-end that can either be accessed through a SAP transaction code, or through a transaction call from the PI-sheet. This option requires the components to be staged to a storage type that has storage unit management active.

The second package is basically using standard SAP transactions and manual keyboard data entry for material consumption. Postings can either be manually triggered from the PI-sheet that indirectly sends process messages to SAP or directly through normal SAP transactions like MIGO like MIGO or through a ‘back-flush’ (only allowed for material like glue etc.) consumption posting triggered by a process order confirmation.

The third package is using Radio Frequency (RF) functionality to perform consumption and production declaration with an RF device. This is enabled for non SU materials and SU materials.

The three options discussed above should be carefully evaluated prior to go-live. If a factory choose a master data and configuration set up to support scanning you cannot process this component through normal SAP transactions and consequently if you choose a master data and configuration set up to use standard SAP transactions you cannot process this component using the front-end for scanning (This is mainly related if you want to use the same material in different ways for the same supply area).

Each package is mutually exclusive by material in that once configured and selected it will determine the options available and methods that MUST be adopted for materials issues, receipts and production confirmation. If the bar code scanning and storage unit management option is selected the SAP custom front end screens must be used for goods issue as the configured business processes block the use of SAP for goods issue using the transactions used for non storage unit managed materials.

PI Sheets have been developed that support both package one and two and are automatically generated according to the Master data that has been setup for the selected materials handling option on a material component basis. If the master data is not set-up correctly for the materials, factories may find it impossible to undertake the correct SAP transactions or generate PI Sheets.

2 PI Sheets - General Facilities

2.1 PI Sheet - Use

The Process Instruction Sheet, PI Sheet, enables an operator to undertake a limited set of transactions needed for the issue and receipt of materials and the creation/change of batch against a process order as their work activity takes place on a production line. The PI sheet enables a record of all operator activities to be recorded in a process message log, if the PI sheet triggered transactions are used.

The PI Sheet resembles a paper log that an operator would create as part of their work activity but additionally enables a user to undertake the business transactions as part of their daily production recording activities.

Operator can use the sheet as part of their production recording duties and at the same time report the information directly into SAP.

The Find PI Sheet transaction, CO60, allows the operator to call up a list of Process Instruction Sheets according to their set of selection criteria, making it easy for an operator to find the required PI sheet according to their individual needs, e.g. by order number, resource (usually line), material, date or control recipe destination etc. Most operators will use the control recipe destination as a search criteria for PI sheets.

The transaction returns a list of PI sheets that can be maintained or acted upon using the menu items.

PI Sheets can be printed to enable paper recording when computer equipment is not available. The PI sheet lists can be exported to Excel spreadsheets or E-Mailed from planning to production operations. They offer a replacement for paperwork systems without the overheads of using native SAP transactions but can be limited in their functionality for more complex recording and control

scenarios. The EARTH template supports a scaleable solution in this area for 'on line' production recording.

2.2 PI Sheet - Header

The PI Sheet header is common for all the generated PI sheets and includes the information an operator may need to know about the material being produced.

For example, as shown in the above diagram by opening or closing the header window. It should be noted that the information displayed is in the order units of measure. The default settings for the order UOM is the material master production units of measure for the material. The order quantity decimalization settings e.g. Comma or dot notation can be different from the USER profile settings if the user has changed them.

2.3 PI Sheet – General Structure

The master recipe for this material had two control recipe destinations defined, G1 and G2. The control recipe destination G1: was used for two operations, 100 and 200, each with two phases 110/120 and 210/220, hence four sections are shown. The process instructions generated are combined for the same control recipe destination.

2.4 PI Sheet – Calling Transactions

The PI Sheets offer push buttons to enable jumps to transaction screens where data is passed from the selected operation and phase. This enables the PI Sheet to limit the data entry required by the operator to only that which is required for the operational task. This simplifies the task of data entry for the operator and controls what may be done in transactions undertaken using this linkage mechanism.

Phase Label Information

Open Window

Closed Window

Time Ticket Confirmation TransactionCall Button

For example, all milestone operations will require a confirmation by the operator for production activities, e.g. running hours, labor hours and materials that will consequently trigger any back-flush goods issues required.

Phase long text

2.5 PI Sheet - Data Entry

Data Entry is made into the PI Sheet in tables, where each line is used to record the data for a single SAP transaction. Data from one table line can be copied to another table line to reduce data entry and errors. The diagram below illustrates an example.

A checkbox is marked for the

data to be sent. It carries

out some basic

validation functions

Icon deactivatesthe line if

dataare not to be

sent

Values from one table fieldcan be used to default intoanother table field, even

within a different table

The red star marks the mandatory

fields

Reversal tickbox to reverse a goods

movement

Transaction date may be different

from the actualdate

2.6 PI Sheet – Data Entry Validation

Data entry validation of the PI sheet table lines prior to initiating SAP transactions can be set up as part of customizing. This will help prevent errors prior to the execution of the SAP transaction. Any deviations can be noted by the operator and signed through their personal logon. Note this need not be the same as the logon used to open the PI Sheet.

In version 1.5, for certain process instructions validation functions are carried out when pressing the ‘entry ok’ checkbox.

Other Examples (next page):

The usage quantity now is higherthan the tolerance for the target

quantity:- the deviation is recorded- the wrong value can be rejected- A warning Flag is indicated- if approved, a signature is

required

Signature strategies can be customized

for the password check

2.7 PI Sheet – Data Entry Copy details from SAP

To copy a batch, the user can call a SAP R/3 transaction or report, select the data they wish to copy and then cut/paste it back into the table line. Use control 'Y' to mark the field, Control 'C' to copy the data and Control 'V' to paste it into the PI Sheet.

But in general terms the operator should always use the physical batch number and cross check in the system!

2.8 PI Sheet - Integrated Batch Management

The PI Sheet supports the automated batch number generation and validation according to material type. This enables operators to create an initial batch or change batch on a pallet by pallet basis. The call batch number function calls a batch number based on the EARTH format. Dependent on the configuration settings a changed value not according to the EARTH format can be accepted with a signature or is forced to get rejected so that only values according to the format are to be sent by the operator.

A button can be used to call another transaction

to view additional data to execute other steps

A new batch number is created according to plant-specific rules

This value was rejected:the line is now greyed and striked out

The production datemay be different fromthe actual date

Confirmed batch record data are nowreported:- a new batch record is created- the value is sent to the process order- the batch record also contains the production date

The default batch numbermay be changed or extended,it then is validated accordingto the plant-specific rules

2.9 PI Sheet – Writing Data back into the PI Sheet

The EARTH custom transactions for issuing and receiving storage unit managed materials report transactions back into the PI Sheet so that a complete history of operator activity is recorded.

The batch number defaultsautomatically into the nextinstruction for goods receipt

2.10PI Sheet - Reporting Data

Each consumption and production declaration line has a ‘+’ button at the end to jump to the goods movement report for detailed reporting.

2.11PI Sheet - Signature

Before an order can be technically completed all the open PI Sheets must be completed. Before the PI Sheet can be completed it must be signed by an authorized user. Comments can be made at this point and the PI Sheet completed.

The signature process at the end of the PI Sheet automatically triggers the completion of the PI sheet. Before entering the final signature step, all prior process instructions must either be completed or deactivated (no table lines must be open).

3 Master Data & Configuration Objects

3.1 Master Data Structure

3.1.1 Material Handling

More detailed information on the master data for materials handling for consumption can be found in the guideline GT_15_PRD_Guideline_Matconsumption.doc. This guideline will focus on how to set-up the PI Sheet Master data needed for the various options of storage unit and non storage unit material management.

For each process order raised the material components will be staged according to the predefined master data setup. The diagram illustrates the extent to which the different master data objects interact with WM material staging and the master recipe used to generate the PI sheet.

3.1.2 Master Recipes

The PI Sheet is generated from the process instructions contained in the control recipe of the process order. The master recipe defines the resources, operations and phases required to make the product. These are linked through the SAP master data and the EARTH template configuration to generate the correct PI Sheet for consumption and receipt.

Master RecipeOperations Resource Supply area

Phases BOM Materials Storage Type/BinCRD

Process Instructions PI Sheet

Process Order

110

Phase

X Y Z

BOM

Recipe ResourceProduction Supply Area

Control CycleRecordMat.X/Plant/PSA

Control CycleRecordGenericPlant/PSA

Control CycleRecordMat.Z/Plant/PSA

Storage Type140

Storage Type145

Storage Type140

Resource

StorageBIN

StorageBIN

StorageBIN

Control Cycle Record

SU Management level

Reference a References a

have an allocated are sourcedfrom a

Have a set ofare used togenerate a

Storage types

145: SU Managed140: not SU Managed141: not SU Managed

The following diagram illustrates a typical Master recipe that comprises three resources, three operations each with one or more phases.

In this case two PI Sheets will be generated, one for each destination. The Y5: PI Sheet will contain all the process instructions required for the production declaration the milestone confirmation and the signature for phase 230.

The Y5: PI Sheet will contain all the process instructions required for operation 100 and 200 that will include consumption and confirmation . It is important to remember that:

A process order will NOT be able to be technically completed before all sections of the PI Sheet have been completed.

The control recipe destinations must be selected with a knowledge of the material handling requirements of the produced or consumed material and the 'sort string' master data set-up appropriately in the material BOM.

The method of receipts and consumption must be appropriate for the physical operation and availability of information.

3.1.3 Material Allocation

Material allocation to the correct phase is important and can be seen in the diagram below, one material – 10000035 and 10000037 is allocated at phase 220 and the others at phase 120.

It is important to ensure that the material is allocated at the correct phase/resource and its BOM sort string is correct, otherwise it may not be possible to issue the material from the PI Sheet.

3.1.4 Material Staging

The resource supply area must have a default control cycle record that defines a storage type and bin for the production supply area before a material can be issued. The configuration of the storage type also defines if the bin is to be storage unit managed or not. This information then enables the correct selection of Control Recipe Destination, and hence PI Sheet to be made.

The control cycle record for material 10000146 in the supply area MILKRECP identifies a storage type 141 and storage bin FAT-SNF for the source of material needed by phase 120.

Storage type 141 is non storage unit managed and manually staged, (indicator =4) and hence can be issued directly from the PI Sheet.

A default control cycle record can be configured by plant and supply area for all materials with a 'pick part' staging indicator =1.

In this case it is important to ensure that ALL materials allocated to phases on the PI sheet comply with the default storage type and their master data sort strings have been set up correctly, i.e. value =3

All materials must have a control cycle record unless staged using 'pick part' strategy. If materials are sourced from an alternative supply area to the default, they will need a specific control cycle record defining for each material. All materials that are staged to a supply area with storage unit management configured storage type, e.g. 145, will need to use the EARTH custom material handling development 'front-end' for goods issue and receipt.

3.1.5 BOM Master Data - Sort Strings

For each resource/material component master data must be maintained on the BOM to control the correct generation of process instructions that will be needed on the PI sheet for the material consumption, receipt and order confirmations. The 'Sort string' field on the BOM holds a value that is used by the SAP configuration process for generating the correct combination of process instructions needed on the PI Sheet. The Table line fields required for material issues, receipts and confirmations are automatically generated according to the value of the sort string.

Each operation is undertaken by a resource in one or more phases. Materials that are defined on the BOM are allocated to one or more phases. Each phase must be associated to a single control recipe destination. The sort strings for the material on the BOM are used to generate the process instructions needed and has a major influence on where, when and how the material consumption posting will be done in the PI Sheet environment. The diagram below illustrates the key master data objects to be maintained for the generation of the control recipe and PI Sheet. The sort string field on the BOM holds the EARTH custom master data that is used to generate the PI Sheet variants for Goods issue.

3.1.6 Sort string - values

The sort string does not influence where and how the components will be staged but it has a major impact on the preferred process for where, when and how the material consumption posting will be done in a PI-sheet environment. The current configuration in place for sort string functionality looks as follow. Sort String 'Blank' = To filter out components not to be issued from PI-sheet

Sort string 1 = To identify by-products within the PI-sheet.

Sort string 2 = Components issued from the PI Sheet using Process messages

Sort string 3 = To identify components to be issued from front end for scanning.

Sort string 6 = To be used for MFLOW (please refer to GT_15_PRD_PM_Guideline_PI_Sheet_MFLOW.doc Guideline) components stock.

Material 10000146 has a blank sort string value, it is not back flushed and not batch managed. We are now able to look at how the various combinations of this master data can be used to configure PI Sheets for a variety of production operations.

Its worth making the point here that the EARTH PI Sheet solution can be used in a variety of circumstances found in production operations, provided the master data is correct and maintained.

4 PI Sheets & Control Recipes

4.1 PI Sheets & Control Recipes

The Control Recipe and PI sheet are separate objects as far as SAP is concerned, each with their own status and monitor. It is important to understand these relationships so that recovery from errors in operational transactions or master data can be corrected.

It is important to remember that:

The PI Sheet is an object generated from the control recipe and is dependent upon the control recipe destination.

The Control recipe is automatically generated according to the EARTH template settings that are NOT changeable.

The changes to the process order will not be reflected in the control recipe after it has been generated.

The control recipe monitor is a technical interface as far as plant operation is concerned and should not normally be needed for the destinations Y1, Y2, Y3, Y4, Y5, Y6, or G7. The control recipe monitor is only needed for external interfaces and manually discarding a control recipe once a PI sheet has an 'in-process' status.

Process Order

EARTHTEMPLATE

Configuration

BOMMaster Data

Sort StringsValues = blank,1, 2,3 or 6

Master Recipe

Control Recipe Destination =Y1, Y2, Y3, Y4, Y5, Y6, Y7

Control Recipe

PI Sheet

Control Recipe Monitor

Transaction CO53Automatically GeneratedProcess Instructions

PI Sheet

Transaction CO60

4.2 Control Recipe Monitor Transaction CO53

The control recipe monitor transaction enable control recipes to be viewed according to selection criteria, e.g. Order number, control recipe destination, date etc.The monitors then display all the control recipes that meet the selection criteria. In the example,

two control recipes have been generated one for destination Y1 and another for destination Y3. It can be seen that one destination will be used for PI sheet Goods issue of non storage unit managed materials and the other for palletized materials.

4.3 PI Sheet - Control Recipe Destinations

Five generic PI Sheets have been configured that will be automatically generated according to the control recipe destination selected in the master recipe, Y0, Y1, Y2, Y3, Y4 Y5, Y6, Y7. The type of material receipt being used in production defines the destination that must be used. The options available are as shown in the table below.

Control Recipe Destinations for PI Sheet Goods Receipt

Y1: Y2: Y3: Y4: Y5 Y6 Y7

Batch Managed & non SU Managed

XPreferred

XOptional

Non Batch Managed &

Non SU Managed

XOptional

XPreferre

d

Batch Managed &

SU Managed

XMandatory

No GR XPI Sheet not used

for Goods Receipt

MFLOW X X

4.4 PI Sheet - Transaction Execution Modes

The PI sheet provides an environment for the process operator that enables them to carry out all the transactions needed to execute a process order. The transactions needed, will vary according to the business scenario adopted for materials handling. It is important to remember that the PI Sheet has two modes of transaction operation:

4.4.1 Direct call of SAP transactions

In this case the operator will be required to respond to any error messages that may occur and may also have to wait if other users are accessing SAP that block duplicate operation. This mode of operation is necessary where the complexity of the task needs to be undertaken directly in SAP and has not been delegated to the indirect call of a SAP transaction.

This mode is used for the following functions:

Process Order Confirmation Storage Unit Managed Material Receipts and Issues Access to SAP Reports

It can also be used for non storage unit managed material receipts using the MB31 SAP transaction.

4.4.2 Indirect call of SAP transactions

In this case the operator can use the PI sheet to enter data that is validated and checked for appropriateness before a process message is sent to initiate a SAP transaction. This mode of operation enables the operator to work without having to wait for the SAP transaction to execute. This has some advantages of allowing operators to enter data into the system in advance of its transaction processing. It also has a disadvantage that any errors of content are only reported back to the operator at the point of data entry if a validation is configured for the field.

This mode of operation is used for the following functions:

Issues and receipts of Non Storage Unit Managed materials Creation of a new material batch record Signature and completion of the PI Sheet

5 Process Message Management

Process message management is a key requirement for factories to check that all messages have been correctly processed and any failures are investigated and re-sent. The SAP process message monitor is used for this purpose.

5.1 Process Messages Monitor

Factories will need to establish procedures for checking that all the process messages generated by the PI Sheet have been successfully processed by SAP. Although most detectable errors are validated during data entry there are circumstances when they can fail and that will need some corrective action. For example, if an operator is consuming material using process measurements that consume more material than is available in the supply area. The Process message monitor, CO54 is the tool used for checking and resolving any message failures.

Process messages that are sent from the PI Sheet can be displayed using the Process message monitor transaction. Facilities exist for displaying or editing the data sent from the PI Sheet when a failure (destination error) occurs. These may be due to a number of reasons usually:

1) Deficit of Stock for a goods issue

2) Incorrectly generated PI Sheet for the BOM settings, i.e. using a non storage unit managed PI sheet setting for a storage unit managed material.

5.2 Process Messages

Y_CONS Used for reporting the consumption reporting of non batch managed material Y_CONS_B Used for reporting the consumption of batch managed material Y_CONS_R Used for consumption of By Products Y_CONS_S Used for Consignment stock Goods issues Y_CONS_C Used for Consumption Cancellations

Y_BATCH Used for creating a new batch record and updating the order details Y_PROD Used for reporting the production of non batch managed material Y_PROD_B Used for reporting the production of batch managed material SIGN Used for completing the PI Sheet. PI_CRST Used for changing the status of the control recipe and related PI Sheet

These messages are created by using the 'report' button in the header of the PI Sheet. There is no requirement in normal circumstances to manually create process messages, but if it is necessary then the process message transaction, CO57 is the tool that is needed to manually create messages.

It is not necessary to execute these steps manually as SAP background jobs are set up for:

sending the control recipe

sending the process messages

This tool may need to be used to change the status of a PI Sheet that has a status 'in progress' and needs to be discarded and a new one created because of incorrect master data. The standard SAP process does not allow the discard of a PI Sheet once it has a status 'in process'. However. if this should happen then the following 'non SAP recommended' procedure can be used. The procedure is:

1) Create and send a process message to discard the control recipe using CO57.

2) Use the find PI Sheet transaction CO60 menu item to discard the PI Sheet.

3) Change the process order COR2 menu path and delete generated process instructions.

4) Correct the Master data that is in error on the order, and later the Master recipe

5) Re-Generate a new control recipe and PI Sheet, the new one will NOT show the previously entered information.

6 Process Order Status Manager

New transaction to remove GT v1.0 functionality gap for the collective management of control recipes, Pi-sheets and process messagesSingle step to complete or discard of control recipes (including PI-Sheets)Collective display of all PI object statuses (control recipes, PI sheets, process messages)Integrated with existing PI transactions (control recipe monitor, find PI-Sheet, process messages monitor)Transaction: Process Order Status Management /glb/rgtes08_crmr

7 PI SHEETS – Material Receipts

7.1.1 CRD Y1: PI GR (Preferred)

Y1 is the normal control recipe destination for receipting materials that are batch managed and not storage unit managed. The call batch number function will generate a batch number which when validated will populate the table line for goods receipt and send a process message, Y_BATCH.This process message triggers two tasks:

1) Create the batch master record and update the production date. The product availability date in the batch master record is also updated based on material master settings.

2) Update the process order goods receipt batch, this is used to recall the current batch for receipt

If the PI Sheet is not used, then these additional tasks will have to be performed manually using standard SAP transactions.

After a batch has been generated a production receipt can be made. In this case the material 1000073 is a finished material and the batch number is appropriately generated and used for the process message for receipt, Y_PROD_B

PI Sheet Y1 is used for most production operations not involving pallets, e.g. Silos, Tanks and vessels that are not storage unit managed. It should be noted that the operator will not receive any direct feedback from this activity regarding message failures and should be aware that any errors will need later correction.

The Goods receipt is an indirect mode of operation.

7.1.2 CRD Y2: PI Sheet Receipt (Optional)

For example, materials that are not batch managed and not storage unit managed materials. have two options available for receiving, Y2 and Y4. If control recipe destination G2 is used then a direct function call to the SAP MB31 transaction is required for Goods receipt.

This means that the displayed PI Sheet for Y2 will have a push button displayed to call the MB31 transaction.

PI Sheet Y2 is used in those cases where factories prefer to undertake transactions using direct transactions in SAP. This has the merit of providing immediate feedback to the operator in the case of error. There is no relative merit in using this approach over recording results directly in the PI Sheet.

The Goods receipt is a direct mode of operation.

7.1.3 CRD Y3: PI Sheet Receipt (Mandatory for SU Materials)

Material Receipts for Storage Unit managed materials can only be undertaken using a EARTH custom development. In this case a push button is included to call the Material handling Custom front end transaction. Within the front-end you can create the batch according the Nestlé rules. The production shelf life expiration date is defaulted and can be changed by the operator at the beginning.

When the call WM function for GR button is pressed data is passed from the PI sheet to the materials handling front end. This also automatically fills in the data from the production order header for the batch and from the batch master record the production date. All the operator is required to do is fill in the quantity to be produced and press create when a pallet label will be printed.

This use of Y3 PI Sheet is mandatory for receiving and issuing storage unit managed materials.

The call WM function for GR push button calls a custom EARTH transaction that MUST be used as the standard SAP transactions do not allow the issue of materials to a process order from a SU managed bin. This function can be found in the materials handling guideline, GT_15_PRD_Guideline_Matconsumption.doc

The Goods receipt is a direct mode of operation.

7.1.4 CRD Y4: PI Sheet Receipt (Preferred for non Batch materials)

If control recipe destination G4 is used there is no batch field available on the PI Sheet and a process message is sent for goods receipt.

Machine/Labor confirmations are linked to the signature and receipt operation so you can also see a push button has been generated for this purpose.

The Goods receipt is an indirect mode of operation using a Y _PROD process message.

7.1.5 CRD Y5: No Goods Receipt on the PI Sheet

This CRD G5 allows the receipt product to be from the PI Sheet, for example, if SAP transactions or the Materials Handling front end development for Storage Unit Managed materials is going to be used. A confirmation is requirement is still generated.

NOTE: In other respects it is identical to Y3.

7.1.6 Y6, Y7

Please refer to guideline GT_15_PRD_PM_Guideline_PI_Sheet_MFLOW.doc.

8 PI SHEETS – Material Consumption

8.1 Sort String = Blank – Materials NOT ON the PI sheet

These materials will not appear on the PI Sheet

8.2 Sort String = 1 – By Product Materials

This is used for consumption of materials that are by products.

Material 10000155 has a sort string = 1 and will generate a Y_CONS_R process message for by Product consumption

8.3 Sort String = 2 – Materials ON the PI Sheet

8.3.1 Back-flushed Components

Back flushed components are shown on the PI sheet for information purposes. No data entry fields are generated.

8.3.2 Batch Managed Materials

For materials that will be consumed on the PI sheet The implication is that the materials cannot be sourced from a supply area that is storage unit managed.

Material 1000031 is batch managed and has sort string 2. In this case the process instruction used to generate the table line does includes a mandatory batch field and the process message Y_CONS_B will be generated.

8.4 Sort String = 3 – Materials Storage Unit Managed

When a sort string of 3 is used the PI Sheet is generated with a button to call the material handling front end. The Goods issue batch is written back into the PI Sheet detail after the Goods issue transaction has been completed and the user returns to the PI sheet.

Goods issue reversals can only be made by using the reverse button in the Material handling front end.

8.5 Sort String = 6 – MFLOW

When a sort string 6 is used, the Pi-Sheet generates a MFLOW instruction for the relevant component. By default, the MFLOW checkbox is ticked to enable a MFLOW consumption. The MFLOW source order needs to be maintained. For detailed information please refer to GT_15_PRD_PM_Guideline_PI_Sheet_MFLOW.doc .

8.6 Sort String = 4 – Consignment Stock

Template for 1.5 was designed this sort string was actually foreseen to be used for the consumption of non SU managed components from vendor consignment stock (special stock K). Unfortunately the 261 K movement is not compatible with the material ledger so the decision was not to use it anymore.