Jump to

Management of Quality (LABIN) analysis

Overview of PROSCHED

PROSCHED is a subsystem that manages the warehousing and factory activities in ITAS. Its' functionality is:

·     Intake from a purchase contract into the warehouse or Pile Stock e.g. a silo

·     Processing orders/execution (POs)  e.g. Wash, Roasting, Re-Packing, Pick/sorting

·     Movement of goods around the warehouse e.g. re-location, move from storage to processing area

·     Manufacture orders/execution (MOs)  e.g. raw materials and packaging to semi/finished product using a B.O.M

·     Storing of finished products in the warehouse

·     Delivery of goods to the customer, includes allocation process

The TRADE administration is supported by accounting entries in the WIP subsystem.

a) The Intake of new goods will result in the Inventory currency value being accrued from the Charter/WIP account (assigned to its' Purchase TRADE) with the new Inventory value being posted to a designated Stock x WIP account e.g. RMWHS.000. The cost of goods and their additional costs are translated (using Spot FXR rates) to Inventory Currency units.

b) Inventory that is moved to another location will result in value and weights being recorded  from RMWHS.000 to a designated TRANSFER.000 account. The completion of the transfer will result in accounting records from TRANSFER.000 to RMWHS.000; with the option of any weight-loss being directed to a desiginated PLR account (optional feature)

c) Inventory that is moved in the  warehouse for the purpose of production (MOs or POs) can be tracked into a PROCESS.000 account (optional)

d) The completion of a MO or PO will result in accounting entries from either RMWHS.000 or PROCESS.000 to the finished product account e.g. FPWHS.000.

e) Allocation of Inventory to a Sale will result in accounting entries from either RMWHS.000 or FPWHS.000 to the Transit-out account e.g. TRANSIT.000; the Transit-Out account is NOT designated as Inventory for control purposes.

f) Sales Invoicing  will move accounting from Transit-out to the P&L account either PLR or WIP, according to Company configuration

There is a sister procedure PROSTORE, that utilises the majority of the PROSCHED processes but is primarily designed to handle 3rd Party intakes/manufacture and distribution. The TRADE records are classified as 3rd party with no Financial value and the subsequent processes enable costs for execution of processes delivery-in, POs, MOs, delivery out to be administrated and subsequently invoiced using PINV. PROSTORE does enable intake of non 3rd Party packaging designated TRADE data for the purpose of MOs and POs to utilise those stock/inventory items.

Working with

PROSCHED is an order driven system, either from TRADED/EXPED or CLI/Deliveries.  Orders can only be viewed/processed in PROSCHED, if they have been created by either of these procedures (phys09 setup).  A key task in handling multiple sites (terminals) is to assign the actual terminal that the delivery-in (Intakes) and delivery-out (Sales) is to be processed through; this provides an element of the Viewing of orders.

The user selects (using the Options icon on task bar) which type of orders they wish to view and can restrict the terminal/site.  All orders are displayed in date sequence, with those dated most recent at the top of the view.  The date used for the view is the TRADE/ship status date; this results in the current PROSCHED active items being shown at the top and other dated items are shown subsequently in blocks with a blank line between. MPCO’s (multi-product customer orders) are listed at the end of the view with each MPCO separated by a blank line.   Note there is S01 configuration (ctrl50_a29order) to provide the order data as being strictly in descending sequence i.e. oldest items at the top . 

Action on the individual items is usually mouse right-click enabled, except for MPCO’s when the header row of the MPCO is enabled for all of it’s features and the individual lines are disabled.

The lines are colour coded so it is easy to see their status, such as call off, manufactured, delivered etc. The colour coding is achieved in the maintenance of PHYSCODES/Shipping Status and in specific S01 configuration settings.

Specific actions may be performed on each line according to their status. For example a called off purchase will have right click functions of Prepare intake, Intake and Mark as routed. These are detailed below. There are optional features to hook-in with 3rd Party Bar-Code subsytems e.g. SATO, BCSL (Hivedome product in conjunction with WORTH scanners).

Viewing Options

The display may be tailored to individual needs by:

·     Selecting to view purchases, sales, manufacturing and processing orders or all 3

·     Selecting the columns to display on each of the 4 views

·     Selecting to view the current production schedule or history. The production schedule shows all order items for today (ITAS date) regardless of status and all incomplete items with oldest items at the top e.g. late deliveries. The History view shows all items, both complete and incomplete, with latest items at the top. The user selects how many days of history to view.

In all cases the display can refresh automatically every 2 minutes (or by the interval selected by the user) to pick up latest call offs etc.

There is a 'View Stock Summary' from the +Other icon. This enables the view of ALL inventory that has not been marked as allocated to a Sale. There are drill downs available from the summary of Terminal/Warehouse/Commodity.  When viewing the individual Inventory items, the user can write-off, provide sample detail, can alter the Q.A. status...

Models for movement of goods through the system

1.     A Purchase order for some raw materials is called off in EXPED. This becomes a contract split and receives its unique release number.

2.     The purchase order appears in PROSCHED purchases.

3.     The shipping and haulage details are maintained in ‘Mark as routed’. This updates the Traffic details in TRADE

4.     The raw materials are taken into the warehouse and become a warehouse record.

5.     The barcode is created on the pallet

6.     The warehouse record is moved around the warehouse.

7.     The warehouse record is used in a manufacturing order to produce some finished goods.

8.     The finished goods are stored in the warehouse

9.     The finished goods are allocated to a sales order

1.     A purchase order for some raw materials is called off in EXPED. This becomes a contract split and receives its unique release number.

2.     The purchase order appears in PROSCHED purchases.

3.     The shipping and haulage details are maintained in ‘Mark as routed’.

4.     The raw materials are taken into a silo and theerby lose their traceability

5.     The raw material is used in a manufacturing order to produce some finished goods.

6.     The finished goods is stored in the warehouse

7.     The finished goods are allocated to a sales order

1.     A Purchase order for some raw materials is called off in EXPED. This becomes a contract split and receives its unique release number.

2.     Purchase order appears in PROSCHED purchases.

3.     The shipping and haulage details are maintained in ‘Mark as routed’.

4.     The raw materials are taken into a silo

5.     The raw material is allocated to a sales order

There are 2 production procedures enabled in PROSCHED. The Manufacture order can ONLY produce 1 out-turn. The Process order can produce multiply out-turns. Using the Manufacture procedure provides more weight gain/loss reporting whereas the Process procedure requires the user to specify the detail of loss/gains in direct entry of by-products

The task is to build a new product, applying a BOM (Commodity/Bill Of Materials) to determine in-turn products/services/packaging and quantities. There are several aids to enable the build of the Order i.e. a code 'Proc. Type' e.g. BLEND X can be setup with a standard out-turn product code which is assigned with a BOM

1.     The MO is entered in PROSCHED

2.     The raw materials and packaging are assigned to the MO

3.     The picking list (docdes) is printed to move the materials to the processing area

4.     The movement of goods to the processing area are confirmed back into the system

5.     The mixing sheet (docdes) can be printed

6.     MO preparation is done prior to the actual manufacturing, where the no. of pallets etc. are entered.

7.     The barcodes for the pallets can be produced

8.     The manufacturing is executed and finished goods receipted into the warehouse. Any additional materials/goods required will need to be   manually updated in the in-turn grid.

The task is to perform a factory procedure, e.g. unpack, re-pack, santitize, clean, on selected Inventory, thereby (optionally) creating different out-turn products.

There are several aids to enable the build of the Order i.e. a code 'Process Type' e.g. CLEANX can be setup with a standard out-turn product code (which can be assigned with a BOM) and upto 3 by-products can be suggested

1.     PO is created in PROSCHED

2.     the in-turn TRADE records are selected and their respective tonnage/pack units. Any subsequent additional materials/goods required will need to be   manually updated in the in-turn grid.

3.     when the order is completed, user will update out-turn grid to show results of the process

1.     A sales order for some raw materials is called off in EXPED. This becomes a contract split and receives its unique release number.

2.     The sales order appears in PROSCHED sales.

3.     The goods are sourced from a stock tank and the loaded weight is recorded

4.     The shipping and haulage details are maintained in ‘Mark as routed’.

5.     The delivery order (docdes) and other documentation is produced

6.     The sale is marked as delivered and its delivery details entered

1.     A sales order for some raw materials is called off in EXPED or CLI. This becomes a contract split and receives its unique release number.

2.     The sales order appears in PROSCHED sales.

3.     The sales order is allocated to stock in the warehouse

4.     The shipping and haulage details are maintained in ‘Mark as routed’.

5.     The delivery order (docdes) and other documentation is produced

6.     The sale is marked as delivered and its delivery details entered

Sales orders may be created singularly in EXPED/CLI or as a group known as an MPCO. In PROSCHED MPCOs are managed as a group with right click functions of Print DO/Packing List (docdes), enter delivered quantity, allocate and routing.

This feature is only available IF a CMP/Privilege 'CREATEDO' has been S01 configured.  The user would need to be CMP accredited to use the feature.

Delivery orders are created in PROSCHED from existing sales call offs. In PROSCHED there is a group function of Print DO/Packing List (docdes). The individual call offs have the normal sale call-offs functions available e.g. allocate.   To recognize the DO's on the Sales grid, suggest that a distinct colour is assigned in S01/view/stocks/colours

Example for intake through production to sale

2 purchases of raw materials through to their manufacturing into a finished product.

1.     Create the BOM in PCC.

2.     Create 2 purchase contracts in TRADE of the different materials

3.     Call them off in EXPED. This creates contract splits which receive their unique release number. The purchase call-off/orders appear in PROSCHED purchases (Other…View Purchases)

4.     In PROSCHED, do a warehouse intake on the call-offs. The TRADE call-offs are marked as tolled out and become 2 warehouse records (usually with a distinct contract numbering e.g. 800000.000).

5.     Print the barcode for the 2 intakes

6.     The warehouse record may be moved around the warehouse either manually in ‘Move within Warehouse’ or automatically from a barcode reader system.

7.     Create a manufacturing order (MO) using the BOM and selecting the 2 warehouse records.

The MO will be visible (Other…View MOs)

8.     Print the mixing sheet

9.     Action Manufacturing preparation to record the out-turn details such as number of lots.

10.     Print the barcode for the out-turn pallets

11.     Use Receive finished Goods to record that the MO has been completed.

12.     The warehouse record of the finished goods may be moved around the warehouse either manually in ‘Move within Warehouse’ or automatically from a barcode reader system.

13.     The finished goods are allocated to a sales order from the sales side (Other…View Sales)

14.     The delivery order (DOCDES) and other documentation is produced from the sale

15.     The sale can be marked as delivered and its delivery details entered

16.     The sale is invoiced

Functions Overview

Scheduled Deliveries

Feature restricted to Purchase (intake) and Sales (delivery-out) and Internal Sales. Scheduling is available from the r/click menu on any call-off. The function has two purposes:

The Internal process actioned on the Sale will replicate the same call-off schedule for the Intake i.e. IP contract.

Available as: Right click function on purchase and sale call offs and MPCOs

Function: OPTIONAL, maintains shipment and haulage details

Output: Update TRADE/Traffic details as entered. Update TRADE Shipping status to R for Routed (defined in PHSCODES/Ship status)

Available as: Right click function on purchase call offs (non-pile stock only)

Function: Preliminary entry for a warehouse intake.

Output: Secures data for warehouse intake.

Available as: Right click function on purchase call offs

Function: Records the intake of the goods into the warehouse or silo

Output: In-turn ‘P’ contract is marked as tolled out. Out-turn ‘8’ contract is created as warehoused. It takes over the open position from the ‘P’ contract and absorbs the purchase price and costs.

For non-pile stock the user can split the out-turn into lots (pallets) and secure the data as sub-records of the ‘8’ contract; this additionally allows the printing of the barcode for the pallet.  When splitting the ‘8’, it is also possible to locate the stock in different sheds with different warehouse references. 

Creates IT document to move stock position from the purchase WIP a/c to the warehouse WIP a/c (RMWHS.000)

For pile stock the IT document moves the stock position from the purchase WIP a/c to the stock tank WIP a/c

There is a 'bulk intake' procedure (select from View menu) that enables the user to pick any number of Purchase call-offs for the selected Terminal and right-click on the grid to complete the process. A log is secured in itas/log/prosched_bulkintake.log.  Note that TRADEIMP can import a number of /CallOff records.

Available as: Right click function for  new inventory i.e. Purchase intakes, out-turn of MOs and POs.

Function: Sends data (1st 6 characters of contract number and Release Number) to a barcode system e.g. SATO (3rd Party system) or BCSL (a Hivedome service), which then prints the barcode labels to be attached to the inventory

Output: data sent to barcode system

Available as: Right click function on tolled out purchase call offs i.e. which have been intaken.

Function: Displays detail of Warehouse Intake screen. Provides option to reverse the intake

Output: None

Available as: Right click function on purchase call offs

Function: Splits a purchase contract

Output: Contract Splits

Available as: Right click function on Inventory tonnages i.e. which have been in-taken, warehoused purchases and executed MOs & POs.

Function: Records that the warehoused items are now Approved and may therefore be used in manufacturing or allocation to sales. This process is a simplified process for the full LABIN. This Approval process can be used for any situation where the goods need to be OK'd for use e.g. In-Bond to Out-of-Bond

Output: TRADE/Traffic/Goods code, QA flag updated

Available as: Right click function on warehoused purchases

Function: Records that the warehoused items have been moved to another location within the warehouse, also allows for weight adjustments.

Output: Shed ID updated. If moved into the processing area the WIP a/c will be updated to PROCESS.000 (S01 nomination) and the shipping status to WP (S01 nomination). An IT document is created to move stock position from the raw material WIP a/c (RMWHS.000) (S01 nomination) to the processing WIP a/c (PROCESS.000) (S01 nomination).

Available as: Right click feature on selected row

Available as: Button on the view intake screen

Function: Reverses a previous intake of goods into the warehouse or silo

Output: In-turn ‘P’ contract is un-marked as tolled out. Out-turn ‘8’ contract and its splits are deleted. Reverses the intake IT document.

Available: On the drop down menu from the Other button

Function: Creates the records for the MO as a quantity of out-turn finished product and the in-turns of raw materials and packaging.

Output: MO line to appear on the front screen and Shed ID updated. Records which raw materials need to be marshalled to processing for subsequent picking list

Available: Right click function on MOs

Function: Allows modification and deletion of the MO

Output: MO record updated or deleted

Available as: Button on the Edit MO screen.

Function: Deletes an existing MO

Output: The MO record is deleted.

Available: Right click function on MOs which have recorded the marshalling of goods is required

Function: Creates a document (Docdes) to instruct the warehouse staff to move the goods to the processing area

Output: Docdes document

Available: Right click function on MOs which have recorded the marshalling of goods is required.

Function: Records that the warehoused items have been moved to the processing area

Output: Shed ID updated, the WIP a/c updated to PROCESS.000 and the shipping status to WP. An IT document is created to move stock position from the raw material WIP a/c (RMWHS.000) to the processing WIP a/c (PROCESS.000). Updates the contracts as marshalling of goods is no longer required.

Available: Right click function on MOs

Function: Creates a document (Docdes) to instruct the warehouse staff to execute the manufacturing

Output: Docdes document

Available: Right click function on MOs

Function: Preliminary entry for receive finished goods, secures data for Bar-code print

Output: Secures data for MO and bar-code print

Available as: Right click function on MOs

Function: Records the consumption of the raw materials and packaging and the production of the finished product and its receipt into the warehouse.

Output: In-turn ‘8’ contracts marked as tolled out, in-turn stock tank levels reduced. Out-turn ‘M’ contract is created as warehoused. It takes over the open position from the in-turns and absorbs the purchase prices and costs. The out-turn contract is split into lots (pallets). Creates IT document to move stock position from the in-turns (stock WIPS, RMWHS.000 and PROCESS.00) to the finished product WIP A/c FPWHS.000 (S01 nomination)

Available as: Right click function on executed MOs

Function: Displays detail of MO create/edit screen i.e. the out-turn and the in-turns. Provides option to reverse the ‘Receive Finished Goods’

Output: None

Available as: Right click function on executed MOs

Function: Displays detail of MO ‘Receive Finished Goods’ screen i.e. date of manufacture, cypher no. etc. and the list of lots (pallets) created. Provides option to reverse the ‘Receive Finished Goods’

Output: None

Available as: Button on the view MO and view out-turns screens.

Function: Reverses a previous ‘Receive Finished Goods’ process

Output: In-turn ‘8’ contracts un-marked as tolled out, in-turn stock tank levels are increased. The out-turn ‘M’ contract is deleted. The previous IT document is reversed

Available as: Right click function on unallocated pile stock sale call offs

Function: Enters the loaded quantity and allocates the sale contract to the stock tank(s)

Output: Sale contract allocated to transit WIP. Loaded quantity and value moved from Stock tank to transit WIP

Available as: Right click function on unallocated non-pile stock sale call offs and MPCOs

Function: Allocates the sale contract to warehoused stock

Output: Sale contract and warehoused contract allocated to each other

It’s quite likely that more than one stock parcel is required to match the quantity of a single sales order. To avoid having to split the sales order, PROSCHED operates a many purchases to one sale allocation model. The purchase contract(s) are allocated to the sale, and the sale is allocated to the purchase contract’s WIP account. The details of the allocated purchases are stored on the completion details of the EXPED form on the sale.

Available as: Right click function on allocated sales and allocated MPCOs

Function: Displays detail of allocation screen. Provides option to reverse the allocation

Output: None

Available as: Button on the view Allocations screen.

Function: Reverses a previous allocation process

Output: Contracts un-allocated. For pile-stock the Loaded quantity and value moved back to the Stock tank from the transit WIP

Available as: Right click function on sale call offs

Function: Creates documents (Docdes)

Output: Docdes document

Available as: Right click function on allocated sale call offs and MPCOs

Function: Records the delivery details of the sale

Output: Delivery details recorded, contract(s) updated as delivered. Non-pile stock also moves the goods from the finished product WIP a/c to the Transit WIP a/c (S01 nomination).

Available: On the drop down menu from the Other button, when the CMP privilege 'CREATEDO' is S01 configured on the server

Function: Creates a DO from existing sales call offs

Output: The DO line to appear on the front screen with its composite call offs to be viewed by right-click on DO/View DO

Available as: Right click function on DOs

Function: Displays detail of DO. Provides option to delete the DO.

Output: None

Available as: Button on the view DO screen.

Function: Deletes an existing DO

Output: The DO record is deleted. The composite call offs are removed from the DO

Available: Right click function on DOs and MPCOs

Function: Creates a document (Docdes) for delivery/packing

Output: Docdes document

Available as: Right click function on MPCOs

Function: Displays detail of the MPCO. Provides option to delete the MPCO.

Output: None

Available as: Button on the view MPCO screen.

Function: Deletes an existing DO

Output: The MPCO record is deleted. The composite call offs are removed from the MPCO

Available: On the drop down menu from the Other button

Function: Facilitates the movement of goods from one terminal/depot - warehouse to another teminal/depot

Output: An internal contract (split) with the ‘to’ terminal buying from the ‘from’ terminal

Internal transfer requires entry of the from and to terminal, with optional from and to warehouses and the quantity and units being moved. Costs may also be entered e.g. transport charges.  An internal contract must exist already (TRADE) with the Sale setup with the from terminal and the Purchase with the to terminal. On save, splits of the internal contract are created and calls offs (phys09) are created as a Sale Order in the from terminal and a purchase order in the to terminal. Both call offs have the same release no. The Sale needs to be delivered-out of it's warehouse and is handled by the standard ‘Allocate’ and ‘Enter delivered quantity’ functions.  The delivery-in is handled by ‘Warehouse intake’ on the purchase. When in transit the contracts and accounting entries will be carried by the nominated ‘Terminal Transfer WIP Account’, and will be transferred back into the Raw materials or Finished goods WIP accounts after completion of the warehouse intake. Any costs entered will be posted to the Raw materials or Finished goods WIP accounts from their nominal ledger accounts after warehouse intake. On warehouse intake, a split is created for contract allocated to the IS and is a copy of it.

Scheduling is enabled on Internal Sale and the sub-calloff is replicated on the Internal Purchase; thereafter they are kept consistent; especially Routing data being entred on Sale. Undo of a scheduled calloff will similarly remove the Purchase side and return tonnage to its' header record.

Pile and Non-pile stock

Stock may be classified as pile and non-pile. Pile stock is pumped e.g. bulk sugar, molasses and is stored in a silo. Non-pile stock is handled e.g. bagged sugar, packaged ingredients and is stored in a warehouse.

Pile and non-pile stock are managed differently in PROSCHED.

Pile stock starts life in ITAS as a purchase contract, either forward or spot.

An expected delivery quantity is entered as a call off

This is then taken into a silo where it loses its identity as it’s mixed into the silo content.

From the silo, the pile stock may be used in a manufacturing process or delivered out to a customer in bulk.

Non-pile stock also starts as a contract and is then called off.

It is then taken into a warehouse where is maintains its identity and may be traced back to the delivery and purchase contract.

From the warehouse it will be used in a manufacturing process.

Sale contracts are entered in ITAS and are called off either individually or in a multi product customer order (MPCO). The sales call offs are allocated to warehouse stock, this can be finished products, raw materials or pile stock in a silo.

The sales are then delivered and invoiced.

Management of Non Warehoused Goods

PROSCHED functionality is oriented towards management of goods in a factory/warehouse (fixed location) and delivery of those goods out. It also works adequately for goods not stored in a warehouse such as those afloat, this allows a company to handle all sales through the same application i.e. PROSCHED.

These contracts are identified by having the nominated ‘Non Warehoused Stock Terminal’. As call offs they appear on the Prosched front screen under this terminal and may be allocated to sales also in this terminal. The only difference being instead of the allocation procedure only showing contracts with a warehoused status, it shows contracts which are called off, afloat etc. i.e. those statues nominated in ‘Non Warehoused Stock Statuses (AFI’s).  This is only an alternative to standard TRADE/allocation and is not mandatory to use.

Management of Quality (LABIN) analysis

The processes to create LABIN records for the out-turns is activated when the Operating Company is setup in S01 with a WareHouse Goods Status (ctrl50_whsegoodsstatus)  code that is assigned as QA approval needed (PHYSCODES/Goods Status).  If the out-turn product is setup in PHYSCODES with a Quality Portfolio, the relevant LABIN records are created and the out turn record is marked accordingly i.e. needs QA approval before use in another process or allocated to a Sale.

Liens -Process

Background

In various countries e.g. Philippines, the company deals with liens (aka quedans). A lien is not a physical good, but a letter of ownership. Farmers take their sugar to the mills and get a lien/quedan which is a letter of ownership. Agents/middle men can buy the quedans from the farmers. Some companies who process or export the sugar buy thousands of quedans at a time from the agents and will later take a delivery of sugar from a mill which is represented by a number of quedans.

Quedan Import

Quedans are imported into PROSCHED from an external system in a CSV format. This is done on the Warehouse Intake screen, selecting the “Import CSV…” option. The path for the CSV files is stored per terminal (ctrl51_intakepath)

The file can contain the following columns, in any order. The first row contains the column headings, which are case-insensitive:

·     Quantity. (Mandatory. Total must equal the call-off quantity)

·     Bags (If present, total must equal the call-off bags)

·     D.O.M (i.e. date of manufacture. Mandatory. Cannot be later than the date warehoused)

·     Warrant Ref (Mandatory. Must be numeric, and each entry must be unique)

·     Warrant Location (Mandatory. Validated against cmy75. All rows must have the same warrant location)

·     Lien (Mandatory. Must be numeric. The total lien must match the value of an amount cost on the call-off called “L-[terminal]”.)

phy01_lienprice.

·     Date Warehoused (Mandatory. Cannot be later than the current ITAS date)

·     LSR Number (Mandatory. All rows must have the same value.)  appended to the TRADE client reference

·     Quedan History (Mandatory)  phys01_bankref

·     Insurance (Mandatory. The total insurance must match the value of an amount cost on the call-off called “I-[terminal]”). This becomes a        memo cost on the out-turn splits, using ctrl07_insurance

·     Storage (Mandatory. The total storage must match the value of an amount cost on the call-off called “S-[terminal]”). This becomes a memo cost on the out-turn splits, using ctrl07_storage

The import will be rejected if any of the validations fail. Once the import is completed, the file is moved to an “old” folder.

Once the quedans are imported, the intake can be saved as normal, and they become splits of the out-turn contract. Note that even if there is only a single quedan, we still split the out-turn.

Note: division “PA”, an intake cannot be reversed if quedans have been swapped in TRADEGRP.

Allocation

Quedans cannot be split, so the allocation process works differently when dealing with quedan contracts. As the Philippines company deals with both quedan and normal stock, they differentiate between the two by using different allocation procedures – for quedans they use the “Allocate With Filter” option. This uses an HXENQ filter to fill the screen, and the use must select splits to allocate by ticking – the quantity cannot be adjusted. This logic only applies to division “PA” – Allocate With Filter works normally otherwise.

Manufacturing Orders

The company needs to distinguish between normal and quedan stock in the same way as allocations. Therefore, when dealing with quedans they use the “Filter/Default From Out-Turn BOM” button to populate the grid. When this option is chosen, the user has to tick splits to select, rather than entering quantities. This logic only applies to division “PA”, otherwise the button works normally.

Additionally, a running total of selected in-turn weights is displayed, in the company weight code.

GateKeeper Role

Users can be nominated (CMP) as either Road or Rail (or both) GateKeepers. Once nominated a User will be presented with a restricted* view when activating PROSTORE and functionality will be restricted to the following tasks:

* The layout of the screen (grid) will be created by an administrator before removing the SHOW/HIDE privilege

** The act of Receiving Into Compound involves confirming the Date and Time that the goods arrived at the gate and creating the associated documentation. Only confirming this document will trigger the completion of the request, which will result in the call-off being marked In Compound

Technical setup