I. Circulation

This memo is circulated to Unifield stakeholders active in the supply functional domain.

  • Unifield supply referents for review
  • Unifield supply implementers for review
  • Unifield Deployment Managers for information

#Resources in charge of field supply tools maintenance and evolution in all OCs

II. Introduction to Supply System Documentation.

This document is designed to give an overview of Unifield Supply functionalities, concepts and flows. Where a specific feature has been developed I have tried to explain the rationale. This document aims to cover master data and each document in the Supply flow with an outline of specific functionalities. In addition, this document describes the configuration and set up of Supply in Unifield, and details how products pass through these locations and their impact on flows. This document is not intended to explain the full synchronisation mechanism as this will be explained in the IT Documentation. User rights will also not be included in this document as they are separate to Unifield Supply functionalities.

There are other systems which impact flows in Unifield, for Supply these include UniData and OCs and HQs’ Portal and ESC systems. This document lists where relevant the impact and interaction with these, but does not aim to include in its scope processes beyond those of UniField.

The targeted audience for this document is those who already have good knowledge of the system. This document does not aim to replace the User Manual, nor provide any step-by-step guidance. Its aim is to provide background information and rationale of why certain functionalities exist in their current form, and how they are structured beyond the user interface.

Finally this document will continue to evolve and be enriched due to:

  • Evolution of the tool and integration of new tickets;
  • Missing information raised by OCs.

III. Glossary

AD Analytic Distribution

AMC Average Monthly Consumption

BN Batch number Mandatory

BO Back Order

CC Cost Centre

CD Cross Docking (Location)

CP Central Platform

DB Data Base

DPO Direct Purchase Order

IKD In Kind Donation

IN Incoming Shipment

INT Internal Movement

IR Internal Request

KCL Kit Composition List

ESCEuropean Supply Centre

ED Expiry Date

FEFO First Expired First Out

FMC Forecasted Monthly Consumption

FO Field Order

HQ Headquarters

LT Lead Time

OC Operational Centre

OST Order Sourcing Tool

OUT Delivery Order

PL Purchase List

PO Purchase Order

PICK Picking Ticket

PPL Pre-Packing List

RAC Real Average Consumption

REF Reference

RFQ Request for Quotation

RR Replenishment Rules

RTS Ready To Ship

Qty Quantity

SHIP Shipment

SLL Status at Line Level

Sync Synchronisation

T Tender

UF Unifield

UoM Unit of Measure

PCE Piece

VI Vertical Integration

WAC Weighted Average Price

1. UniField – Introduction

For Supply, UniField is intended to be used in conjunction with Finance modules at field level; Coordo and Project. UniField is therefore based on the nuclear structure of having an HQ, Coordo and project. The synchronisation engine was developed in order for instances to communicate necessary data (see IT documentation for more detail on this). For Supply, the key master data is products which are necessary for every transaction. The type of product (product attributes) will affect how the product is treated and managed in the system. Products pass through the Supply flows of Ordering, Purchasing, Receptions, Deliveries and are managed through warehousing transactions. In addition this document describes the configuration and set up of Supply in Unifield, and details how products pass through these locations and how they affect the flows.

1.1  List of Supply System Master Data

  • Products
  • Product Nomenclatures
  • Batch numbers and expiry dates
  • Asset Forms
  • Theoretical Kit composition list
  • Partners (Suppliers / Customers / Manufacturers)
  • Packs
  • Units of measure
  • Categories of Unit of measure
  • Product lists
  • Supplier catalogues
  • Country Restrictions

For creation, please see synch rules in system documentation, and where manually created/updated please see relevant section in this document

 

Products