4. User Interface Functionalities
4.1 Ergonomics
All Supply objects are presented in a similar format; At header level, there is generic top line information relevant to the object, and at line level, there are details relating to the product lines.
Fields displayed in blue for a new document denote the field is mandatory, and fields with a magnifying glass denote user may select a value from the master data.
For the majority of objects there are several ways to add products, namely individually (New button), or several together via import, or add multiple button which allows user to add selecting from catalogue, list or other product criteria. The add multiple lines and delete multiple lines functionality is available in the following transactions:
1)Product list
2)Product sub list
3)Theoretical kit composition
4)PO lines
5)RfQ lines
6)Tender lines
7)Claim Products
8)FO lines
9)IR lines
10)Supplier catalogues lines
11)manual IN lines
12)INT lines
13)manual Delivery Order lines
14) Replenishment Rule Segment
15)Physical Inventories
16)Initial Stock Inventory
17)Real Consumption Report
18)Monthly Consumption Report
4.2 Track Changes
This functionality exists for the following documents:
IR, PO, FO, Incoming Shipment, and registers and displays changes made at header and line level together with date/time and user. This action is found in the action menu of the object.
Please note that the “Track change” feature is also available for master data such as Products and Partners ( and most probably other ones will be developed following requests).
4.3 Imports
In Annex there will be all import formats. These may relate to lines or whole transactions. In general to create a transaction, header information must be created manually and lines (products) may be imported or added manually. It is not possible to create a whole transaction (including header) via import – however, there are 2 exceptions to this rule with the Theoretical Kit Composition and the “Import from IR template” (developed to match EasyMED – even though the IR reference still needs to be manually created first).
Some more elaborated imports have been developed as well as part of the Vertical Integration (linked to ESC partners) for PO and IN documents. They have some additional checks at header level as well (see details in relevant chapters below).
4.4 Naming conventions for document references
The most complex naming conventions are for POs and FOs:
Purchase Orders
15/CH/KG101/PO00023
YY/OC/CCXX/POXXXX
Year (2015), OC code (according to proprietary instance config – CH), Cost Centre for instance, PO, then sequential number in this instance
Field Orders
15/CH/KG101/FO00018
YY/OC/CCXX/FOXX
Year (2015), OC code (according to proprietary instance config), Cost Centre for instance, FO, then sequential number of FO in this instance
For most other documents, the reference is composed of an identifier of that transaction and a sequential number. The exception is Initial Stock Inventory, which has a free text field. Please see fields-by-fields documents.
4.5 Order Dates Mechanism
IR:
Creation Date (CD) – Ordered Date: Date of Creation of the document
Requested Date (RDD): manually entered (mandatory) – will be carried out to the following document in flow (PO/OUT…)
Date of Stock Take (DST): manually entered (not mandatory) – Will be carried out to PO (mandatory for PO with Supplier ESC).
FO:
Creation Date CD– Ordered Date : Date of Creation of the document
Delivery Requested Date RDD: (if FO created from scratch): Creation date + Default customer lead time; (if FO created from synch) Corresponding PO Delivery requested date
Delivery Confirmed Date CDD:
(if sourced from stock) date of the confirmation of the FO + shipment lead time + estimated transport lead time
(if sourced on order) CDD of the PO + preparation lead time + shipment lead time + estimated transport lead time
Date of Stock Take (DST): manually entered (not mandatory) – Will be carried out to PO ( mandatory for PO with Supplier ESC).
Ready to Ship Date RTS: RDD – estimated transport LT – Shipment lead time
Shipment Date: Date of first SHIP/OUT processed
PO:
Creation Date (CD): Date of Creation of the document
Delivery Requested Date (DRD): Creation date + Default supplier lead time (field greyed out after PO line validation – used for pipeline calculation)
Delivery Requested Date (modified): manually updated after PO line Validation up to PO confirmation (will be greyed out after PO confirmation – used for pipeline calculation if there is no CDD)
Delivery Confirmed Date (CDD): manually updated or will be via synch for internal supplier (used for pipeline calculation – once line Confirmed can only be modified by VI import and will only update INs – ie no previous doc will be updated)
Date of Stock Take (DST): manually entered (mandatory only for ESC supplier) or can be automatically populated from IR/FO flow
OST:
Requested Delivery Date (RDD) : coming from the IR “Requested Date” or the “Delivery Requested Date” from the FO
Estimated Delivery date (Estimated DD): Today’s date + Supplier Lead time
Incoming Shipment
Creation Date: Date of Creation of the document (Confirmation of PO)
Expected Receipt Date: Confirmed Delivery Date of PO (can be updated following VI import at PO level)
Actual Receipt Date: Date of Reception in the system (when IN is actually set to Closed)
Physical Reception Date: Used for reporting purpose; by default same as Actual Receipt Date and automatically populated at IN processing but can be overwritten by user (when in Available/ Available shipped status).
Delivery Order:
Creation Date: Date of Creation of the document
Expected Shipped Date: RTS date of FO
Actual Shipped Date: Date when OUT is processed
Picking Ticket:
Creation Date: Date of Creation of the document
Expected Pick Date: RTS date of FO
Actual Pick Date: Date processed
PPL:
Creation Date: Date of Creation of the document
Expected Pack Date: RTS date of FO
Actual Pack Date: Date processed
Shipment:
Creation Date: Date of Creation of the document
Expected Ship Date: RTS date of FO
Actual Ship Date: Date processed
