WMS - User contributions [en-gb]

NOMS

2019-05-21T10:24:03Z

Lwinchester:

{{comment|text=1. FUNCTIONAL OVERVIEW
1.1 Introduction
The purpose of this document is to provide the user with knowledge of how to setup, maintain and test the Stock Ordering Tool and its associated functionality.

For additional system information the generic user guides should be referenced.

2. MAINTENANCE SCREENS
Listed below are the steps to set up a new prison and plug it into the existing Stock Ordering Network.

2.1.1 Pre-requisites
Setup and enabled warehouse code (and associated configuration)

2.2 Stock Maintenance – (STKSTOC01B)
Stock Codes can be manually entered or uploaded via EDI

{| class="wikitable" border="1"
|-
! Key Fields !! Value / Comments
|-
| Stock Code & Description || As specified
|}

Product Range, Class, Category & Group Set as specified against the type of product.
Ambient, Fresh, Reception Packs etc.

|sign=[[User:Lwinchester]]|date=21/5/2019 10:51:16}}

NOMS

2019-05-21T10:16:24Z

Lwinchester:

{{comment|text=1. FUNCTIONAL OVERVIEW
1.1 Introduction
The purpose of this document is to provide the user with knowledge of how to setup, maintain and test the Stock Ordering Tool and its associated functionality.

For additional system information the generic user guides should be referenced.

2. MAINTENANCE SCREENS
Listed below are the steps to set up a new prison and plug it into the existing Stock Ordering Network.

2.1.1 Pre-requisites
Setup and enabled warehouse code (and associated configuration)

2.2 Stock Maintenance – (STKSTOC01B)
Stock Codes can be manually entered or uploaded via EDI

Key Fields Value / Comments
Stock Code & Description As specified
Product Range, Class, Category & Group Set as specified against the type of product.
Ambient, Fresh, Reception Packs etc.

|sign=[[User:Lwinchester]]|date=21/5/2019 10:51:16}}

NOMS

2019-05-21T10:04:17Z

Lwinchester: Created page with "{{comment|text=Your Comment Here |sign=User:Lwinchester|date=21/5/2019 10:51:16}}"

{{comment|text=Your Comment Here
|sign=[[User:Lwinchester]]|date=21/5/2019 10:51:16}}

Talk:NOMS

2019-05-21T10:01:35Z

Lwinchester: Created page with "1. FUNCTIONAL OVERVIEW 1.1 Introduction The purpose of this document is to provide the user with knowledge of how to setup, maintain and test the Stock Ordering Tool and its asso..."

1. FUNCTIONAL OVERVIEW
1.1 Introduction
The purpose of this document is to provide the user with knowledge of how to setup, maintain and test the Stock Ordering Tool and its associated functionality.

For additional system information the generic user guides should be referenced.

2. MAINTENANCE SCREENS
Listed below are the steps to set up a new prison and plug it into the existing Stock Ordering Network.

2.1.1 Pre-requisites
Setup and enabled warehouse code (and associated configuration)

2.2 Stock Maintenance – (STKSTOC01B)
Stock Codes can be manually entered or uploaded via EDI

Key Fields Value / Comments
Stock Code & Description As specified
Product Range, Class, Category & Group Set as specified against the type of product.
Ambient, Fresh, Reception Packs etc.

EDI Setup and Processing

2017-02-03T14:07:06Z

Lwinchester: /* OWNER MAINTENANCE - EDI Inbound & Outbound (Client Specific EDI Configuration) */

=='''IN PROGRESS'''==

'''To Add - '''

:Cancelling of held orders

:Directory structure on server

=='''INTRODUCTION'''==
This document describes the screens that are required to set up the control data for the EDI Processes in the warehouse. Other guides describe the set up of company, user, warehouse, owners etc.

This is a generic guide based on the version of the Calidus (3pl) system at the time of writing.

Note that fields marked ‘**’ are mandatory and are needed to ensure correct set up of the system.

=='''OVERVIEW'''==
Set up requirements for the use of EDI processes are done in two main stages:

1- Set up of the required general EDI codes for the company level common values (Existing codes are pre-entered when the WMS installed)

:General Codes (PFS0260 & PFS0261) 
:EDI Common (EDI0001) 
:EDI Last Numbers (INS7050) 

2- Addition of the Common records at Owner or Client level and the Configuration of the XF Monitor which is the main EDI engine

:XF Command (XFM0012) 
:XF Resequence (XFM0011) 
:XF Monitor (XFM0020) 

=='''GENERAL EDI CODES – HEADER LEVEL'''==

For each message, you need to set up an EDI code under the heading of ‘EDDI’ in general codes maintenance. These dictate the type of message and what the EDI control number starts with.

'''NB''' – These codes should be have been created when the base system is installed.

 

<center>[[Image:EDI-001a.png]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Type **||The code type you are entering details against ||Entry at this level will not be required as these will already have been set up on a company level||EDDI
|-
|Length **||The number of characters the sub code has to be||1 – 9999||10
|-
|Description **||A brief description of the type of code||100 character free text field||EDI Applications
|-
|Code Flag **||Is this code to be used by the system||Y or N – default is Y||Y
|-
|Info||The ability to enter extra information against the code (not migrated)||Blank ||Blank
|-
|'''Buttons'''
|-
|Extra Info||The ability to enter additional information, e.g. which screens use this, the purpose of the code etc||Entry at this level will not be required as these will already have been set up on a company level||N/A
|-
|Details||Takes you into the detail screens for individual entry of each required code||See following||Defined by system setup
|}

=='''General Codes – Detail Level'''==
For each EDI message required, the code value, description and short description need to be populated. The details to be populated will be described below dependant on the message type.

<center>[[Image:EDI-002.PNG]]</center>
{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Code Type||The code type the values entered refer to ||No entry required as the code type will come through from the header screen||EDDI
|-
|Code Value **||The unique identifier for the EDI message required||Defined by the hard coding of each EDI message. he size is determined by the length of the code type entered in the header screen. List of required values below.||See below
|-
|Description **||Description of the EDI message being created||100 character free text field||Defined by the client
|-
|Short Desc **||Will determine the first 3 characters of the control number||Defined by the hard coding of each EDI message||See below
|}

==='''General Codes – Code Types'''===

{| border="1"
!Code Value||Description||Short Description||Message Details
|-
|OCI||Outbound Commercial Invoice Upload||OCI ||An inbound message that updates orders with customs data (cost, country of origin etc)(Client Specific)
|-
|CII||Inbound Commercial Invoice Upload||CII||An inbound message that updates receipts with customs data (cost, country of origin etc)(Client Specific)
|-
|PACK||Kewill Carrier Upload||PKI||An inbound message that updates orders with carrier, weight and tracking number information (Client Specific)
|-
|SRI||Stock Reconciliation Upload||SRI||An inbound message that compares a client’s stockholding figures with the actual values held on the WMS (Client Specific) See below
|-
|PAI||Pre Advice Upload||PAI||An inbound message that uploads a receipt pre advice into the WMS
|-
|GRN||Pre Advice Upload||PAI||An inbound message that uploads a receipt pre advice into the WMS
|-
|PMI||Product Master Upload||PMI||An inbound message that creates stock codes on the WMS
|-
|STID||Product Master Upload||PMI||An inbound message that creates stock codes on the WMS
|-
|SOI||Sales Order Upload||SOI||An inbound message that uploads sales orders onto the WMS (Client Specific)
|-
|SOP||Sales Order Upload||SOI||An inbound message that uploads sales orders onto the WMS
|-
|HOLD||Hold Upload||Hold||An inbound message that will either hold or release stock quantities
|-
|WLE||Ware Location Upload||WLE||An inbound message that will create pallet records with associated stock details
|}

=='''OWNER MAINTENANCE - EDI Inbound & Outbound (Client Specific EDI Configuration)'''==

---IN PROGRESS---

'''The following section explains the generation of Sales Order Numbers when using the Sales Order message upload functionality'''

<center>[[Image:OW-001.PNG]]</center>

'''Prevent Duplicate Order Ref:'''

:‘Dup Ord Ref not on system’
:The whole file will be rejected if the order exists

:‘Duplicate Order Ref Allowed’
:The order will be uploaded – if a non-unique order is uploaded multiple times, errors will :occur.

:‘Upload All Recs Excluding Dups’
:All orders will be uploaded into the EDI transient table. However, the duplicate will be held :with errors.

'''System EDI S/O Number:''' 
:If Y – the system will generate a unique sequential reference to build the order number.
:If N – The system will use the ‘order reference’ received as part of the order to build the order number.

 

<center>[[Image:OW-002.PNG]]</center>

'''Sequence No. Generate:'''
:The normal is ‘Owner Range’

 

<center>[[Image:OW-003.PNG]]</center>

'''Order Number Without Owner Prefix:'''
:This may be Yes or No

If EITHER ‘Sequence No. Generate’ or ‘Order Number Without Owner Prefix’ are set to ‘Owner Range’ or ‘N’ respectively, the order number will be 20 characters long. Else it will be either a simply sequential reference or the order reference supplied.

'''NB''' Two new values have been added to Owner System Parameters (WHS0012) EDI Setting of Sales Order Number and EDI Sales Order Number Prefix

: Set EDI Setting of Sales Order Number to "Use Sellers order reference"

 

=='''EDI LAST NUMBERS'''==

EDI last numbers are used to increment each EDI control number by one. These are dictated by the entry in the EDI codes. These numbers are set automatically by the system, so there is no requirement for user configuration.

<center>[[Image:EDI-0004.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Owner **||The owner code and sub code the message will be created for||Must have been created in owner maintenance or set to ‘+’ – will automatically create, so all will be set to the owner code of the message||‘+’
|-
|Message Type **||Based on the values created in EDI common maintenance – a record needs to exist here for each message required||Must have been set up in EDI common maintenance||Defined by the client
|-
|Last Number **||The starting number for each EDI message||0 – 99999 – will start at 0 for each new message||0
|}

 

=='''EDI COMMON MAINTENANCE'''==
EDI common is used to dictate for what company/warehouse/owner the EDI flows are for.

<center>[[Image:EDI-003.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Company Code **||Company code the user is setting up the EDI for||Must have been created in company maintenance||Defined by the client
|-
|Warehouse ID **||The warehouse code the user is setting up the EDI for||Must have been created in warehouse maintenance||Defined by the client
|-
|Message Type **||The message type of the EDI flow you are setting up||Defined by the hard coding of each EDI message – available message types listed below||See below
|-
|Key 1 **||If the database is to have multiple owners under one warehouse/company combination the owner code for each message will need to be set up here||Owner code of the owner otherwise ‘+’ if only one owner per warehouse using EDI. '''Advisable to always define the owner code.'''||Defined by the client
|-
|Key 2 **||If the database is to have multiple owners under one warehouse/company combination the owner sub code for each message will need to be set up here||Owner sub code otherwise ‘+’ if only one owner per warehouse using EDI.||Defined by the client
|-
|Company Code **||Company code the user is setting up the EDI for||Must have been created in company maintenance||Defined by the client
|-
|Warehouse Id **||The warehouse code the user is setting up the EDI for||Must have been created in warehouse maintenance||Defined by the client
|-
|Department **||The department code set up against the company||Must have been created in departments maintenance||Defined by the client
|-
|Ledger Code **||Determines which area of the system the message relates to||PL1 or SL1||See below
|-
|Branch Code **||The branch code set up against the company (not required)||Must have been set up in branch code maintenance or set to '+' ||+
|-
|Owner Code **||The owner code and sub code the message is being set up for||Must have been created in owner maintenance||Defined by the client
|-
|Stockist Code **(same as owner code)||The owner code and sub code the message is being set up for||Must have been created in owner maintenance||Defined by the client
|-
|Base Currency **||The default currency code being used by the owner||Must have been created in currency maintenance||Defined by the client
|}

=='''EDI XF COMMAND '''==

This screen is used to dictate which package is called for each flow. The package id field is user definable, but the ‘Package SQL Code’ is predetermined by the package format.

Once you have entered the package id and the package SQL code, you must then specify whether it is an inbound or outbound flow.

<center>[[Image:EDI-005a.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Package Id **||The unique identifier for this message type – note, you will need to remember this for further setup||10 character free text field||Defined by the client
|-
|Inbound/Outbound/Local **||Specifies whether the message is an inbound or an outbound flow (note, ‘local’ is not used for current WMS implementations)||Check box||Defined by the message type
|-
|Package SQL Code **||The programming instruction to determine which package the EDI will call||Defined by the hard coding of the program||Defined by the message type
|}

==='''Command Values'''===
Below is a table of the current commands

'''NB these will increase as new messages are added to the system as required'''

{| border="1" align="center"
!Package Id (User Definable)||Inbound or Outbound||Package SQL Statement
|-
|'''Standard Client Message Types'''
|-
|Despatch Message||Outbound||dp_edigen_out_pdp_conf.write_flat_file
|-
|Stock Master Upload||Inbound||dp_edigen_product_master_load.read_file_format
|-
|Sales Order Upload||Inbound||dp_edigen_sales_order_load.read_sales_order_file
|-
|GRMK – Receipt Message||Outbound||dp_edigen_out_receipt_confirm.process_out_recp_confirm
|-
|Pre Advice or ASN Message||Inbound||dp_edigen_pre_advice_load.read_file_format
|-
|Hold or Release Message||Inbound||dp_edigen_hold_load.read_file_format
|-
|Acknowledgement of Hold Release Message ||Outbound||dp_edigen_out_ack.write_flat_file
|-
|Purchase Ordering||Outbound||dp_edigen_out_pop.write_flat_file
|-
|Courier Returns and Collection||Outbound||dp_edigen_retcoll.write_file
|-
|Standard Stock Inventory Balance (Requires two packages to be run)||Outbound||dp_edigen_out_st_bal.generate_data (populates temporary tables) -dp_edigen_out_st_bal.write_flat_file (writes the file)
|-
|Stock inventory balance by Rotation Only requires one package||Outbound||dp_edigen_out_strot_bal.write_file (This writes a ‘SROL’ record, which is a single level rotation based snapshot)
|-
|Stock Snapshot (Include both customer and system rotations and SAP storage locations)(F/S 230465)||Outbound||Additional rotation level dp_edigen_out_st_bal.generate_detail_data dp_edigen_out_st_bal.write_flat_file_dtl This process writes a SD01 and SD02 lines – the SD02 record is a rotation level record.
|-
|}

 

'''Carrier Interface Messages'''

{| border="1"
!Package Id (User Definable)||Inbound or Outbound||Package SQL Statement
|-
|CANC – Cancelled Orders||Outbound||cim_outbound.write_canc_file
|-
|CICA – Post Allocation||Outbound||cim_outbound.write_cioc_cica_file
|-
|CICD – Pre – Allocation ||Inbound||dp_cim_inbound.read_cicd_file_format
|-
|CIOC – Order Entry Information||Outbound||cim_outbound.write_cioc_cica_file
|-
|CIPD – Packing Information||Outbound||cim_outbound.write_cipd_file
|-
|CITD – Despatch Confirmation||Inbound||dp_cim_inbound.read_file_format
|-
|PODC – IE Specific POD confirmation||Outbound||cim_outbound.write_podc_file
|-
|CARR – Carrier Collection Message||Outbound||dp_edigen_out_carr_conf.write_flat_file
|-
|}

 

'''Configurable EDI'''
'''Inbound'''

{| border="1"
!EDI Structure ||Description ||Package SQL Statement
|-
|CUSTOMER || Customer detail upload || dp_conf_edi_in.read_edi_cust_file_format
|-
|MED_TRANSLATION || (Client specific) - Medical and serial translation || dp_conf_edi_in.med_seq_xfm
|-
|OMS_POST_WHS||(Client specific) OMS Postcode/Warehouse Upload || dp_conf_edi_in_oms.load_oms_pc
|-
|STKBASEUPL || Stock Base Sell upload/update || dp_conf_edi_in.stk_base_sell_xfm
|-
|STK_LOCATION || Stock Location upload ||dp_conf_edi_in.stock_locations_xfm
|-
|STK_WAREHOUSE || Stock Warehouse||dp_conf_edi_in.stock_warehouse_xfm
|-
|STOCK|| Stock Upload||dp_conf_edi_in.read_edi_prod_mast_format
|-
|STOCK_REGION || Stock Region upload/update ||dp_conf_edi_in.stock_region_xfm
|-
|STOCK_UOM || Stock UOM upload|| dp_conf_edi_in.stk_uom_xfm
|-
|STOCK_UPDATE || Stock update || dp_conf_edi_in.stock_update_xfm
|-
|SUPPLIER || Supplier detail upload ||
|-
|WLE || Dynamic Stock Upload ||dp_conf_edi_in.read_edi_wle
|-
|WLE Held Stock || Dynamic Held Stock Upload ||dp_conf_edi_in.wle_held_stock_xfm
|-
|}

'''Outbound '''
{| border="1"
!EDI Structure ||Description ||Package SQL Statement
|-
|Adjustments ||Outbound||dp_conf_edi_out.produce_dyn_edi_files
|-
|Outbound Order Information||Outbound||?
|-
|Stock Inventory Balances||Outbound||?
|-

|}

'''FTP Packages'''
{| border="1"
!EDI Structure ||Description ||Package SQL Statement
|-
|FTP Inbound||Inbound||dp_process_control_xfm.ftp_inbound
|-
|FTP Outbound||Outbound||dp_process_control_xfm.ftp_outbound
|}

 

=='''XF RESEQUENCE'''==

The XF Re-sequence screen is used if you wish to call multiple packages under one package id. You then specify which package, and in what priority. For example to automatically ftp despatch messages on to a remote server you would set sequence one to run the DESP package and then sequence two would run the outbound ftp package.

<center>[[Image:EDI-006.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|'''Process Command **'''||Based on the package id set up in the previous screen – this will ensure the process calls the correct package||Must have been set up in xf process command||'''Defined by the client only for Outbound messages, see table below for inbound message naming formats'''
|-
|Process Description **||A brief description of what EDI message the process code relates to||50 character free text field||Defined by the client
|-
|Inbound/Outbound/Local **||Specifies whether the message is an inbound or an outbound flow (note, ‘local’ is not used for current WMS implementations )|| ||Defined by the message type
|-
|}

 

{| border="1"
!Buttons||Description
|-
|Add Package||Adds the selected package to the sequencing pool|| ||
|-
|Remove package||Removes the selected package from the sequencing pool|| ||
|-
|Select Up||Moves the packages up so the one you require is selected|| ||
|-
|Select Down||Moves the packages down so the one you require is selected|| ||
|-
|Re-sequence Up||If more than one selected package in the pool, re-sequences the priorities of the flows (upwards)|| ||
|-
|Re-sequence Down||If more than one selected package in the pool, re-sequences the priorities of the flows (down)|| ||
|}

 

=='''XF MONITOR'''==
For each EDI flow, you need to set up core information such as which package to run and at what time and frequency. There is also the requirement to enter directory and reporting parameters. These are configured in the XF monitor screen. There are multiple tabs to set up dependent on requirements.

==='''XF Monitor – Setup tab'''===

<center>[[Image:EDI-007.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Process Code **||Uses the process code as specified in xf command/resequence and adds the company, owner and warehouse||Must have been set up in xf command and xf resequence||'''Defined by the client, but dependent on message flow may require a defined code. See table below.'''
|-
|Process Description **||A description of the process code||60 character free text field||Defined by the client
|-
|Process Id||If using EDI running processes, gives the message a unique system generated process id||No entry required – generated by the system||N/A
|-
|Transfer Method **||How the EDI will be transmitted||EDI or Non-EDI||EDI
|-
|Transfer Type **||Specifies in what format the files will be generated||EDI Transfer / FTP Transfer / Unix Transfer or N/A||EDI or FTP dependent on whether the file will be picked up from a remote server or sent to a remote server.
|-
|Send/Receive **||Specifies whether the file is to be received or sent (inbound or outbound)||Send or Receive||Determined by the message
|-
|Process Type **||This is where you specify how you want the flow to run and when. If you set the process type to interval – you will need to put in an interval time in the Interval (mins) field – in the example above, this will run every 15 minutes. If you set this to Time (24hr) – you will then be asked for which days and what time. This will cause the flow to run, say every day at 21:00||Interval / Time (24hr) ||Defined by the client
|-
|Interval (mins)/Frequency||If set to Interval, the number of minutes before the process should start again. If set to Time, you will see a box for a time and every day of the week which can be checked to enable the run at a specific time for specific days||0 – 999999||Defined by the client
|-
|Process Command **||The package id as entered in the process code at header level||Must have been set up in xf command and xf resequence||Defined by the client
|-
|File Retention Days||If archiving, the number of days files that will be kept||N/A||N/A
|-
|UOM Flag (F/S 231470)||Used to allow the WMS system to work in a different UOM than the clients system.||N - No conversion required C - Convert units to cases U - Convert cases to units R - Convert units to cases round up N - No conversion required || Defined by Client
|-
|EDI File Separator||Specifies what delimiters the EDI files will be using, used for configurable messages.||‘/’ ‘;’ ‘|’ etc||Defined by the client
|-
|Reports Flag||Specifies whether you wish upload and exception reports to be produced||Yes / No||Defined by the client
|-
|Process State||Shows whether the EDI message is running on a process or not||Display only – Stopped, Running or Broken||N/A
|-
|Start Date||If you click the ‘Start Process’ button – this will display the date the process was started ||Display only||N/A
|-
|Started By||The user id of the person who has started the process running||Display only||N/A
|-
|Next Run||Calculates the date/time the next process will run based on the last run plus the interval||Display only||N/A
|-
|Inbound File Formats||The format of the incoming file||CSV / Fixed Length / Syspro / Attribute based XML || Defined by the client
|-
|Element based XML ||Defined by the client|| N/a || N/a
|-
|Format code || Defined by the client || N/a || N/a
|-
|}

 

{| border="1"
!Buttons||Description
|-
|Force Run||Enables a ‘one off’ EDI poll|| ||
|-
|Start Process||Begins the polling process that will trigger the message to be uploaded/sent at the relevant time.|| ||
|-
|Stop Process||Stops the frequency/interval from running|| ||
|}

'''NB: Generic EDI flows must have a Process Code (Within XFMonitor, XFM0020) that start with the following string of characters. '''

{| border="1"
!Process Command Must Begin With - ||Flow
|-
|SOP|| Sales Order
|-
|PRE_ADV || GRN Upload
|-
|PROD_LOAD ||Stock Upload
|-
|GEN_ALLOC || Outbound Sales Order Allocation Message
|-
|GEN_CANC || Outbound Order Cancellation Message
|-
|GEN_PICK ||Outbound Pick Message
|-
|GEN_DESP ||Outbound Despatch Message
|-
|GEN_RCPT || Outbound General Receipt
|-
|SADJ || Outbound Serial Number Adjustment
|-
|HOLD_LOAD|| Inbound Holds
|-
|ORDMGT ||Order Management
|}

'''NB: The process command can be any length within the screen limitation, but for i.e. sales orders the process command must be like ‘SOP’, ‘SOP1’ etc

‘1SOP’ will not be seen as a sales order upload.'''

 

==='''XF Monitor Parameters Tab'''===

The parameter tab controls the storage and the naming convention of the produced files. If the transfer type is set to FTP within the setup tab then the ftp control fields will be displayed.

<center>[[Image:EDI-008.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|File Directory **||This is the directory the WMS will search for the message file||This must be a valid directory set up on the Unix box||Defined by the client
|-
|File Pattern or Template id||File pattern is used for standard EDI messages. For an increased configurable file name then select Template id. Allows for the inclusion of user definable Date/Time stamps etc within the file name format.||File Pattern or Template id||Reference XFM0030 File name construction if template id selected
|-
|File Pattern **||The EDI package will upload any file starting with these characters, i.e. as above, anything starting with XXADESP_ ||The file pattern will be determined by the system architects who are creating the EDI files||Defined by the client
|-
|Archive Directory **||The directory that all processed files will move to||This must be a valid directory set up on the Unix box||Defined by the client
|-
|FTP Parameters
|-
|FTP Address **||The I.P. address of the target server||Must be a valid I.P. address that is accessible by the WMS server.||Defined by the client
|-
|FTP Username **||User or account name set up on the target server||Must be a valid user id set up on the target server.||Defined by the client
|-
|FTP Password **||Password for user or account on target server||Valid password for the username account.||Defined by the client
|-
|FTP Final Directory **||Directory where files are to be sent||Valid and accessible account (i.e. permissions must be set to allow files to be copied)||Defined by the client
|-
|FTP Put Directory||Temporary work directory on the target server||If required it must be valid and accessible.||Defined by the client
|-
|Log File Settings Directory **||Which directory all processed log files will be sent to||This must be a valid directory set up on the server||Defined by the client
|-
|Log File Settings Filename **||The name of the log file to be produced ||Can be any file name the user sets up||Defined by the client
|-
|Report Directory||Directory name and path where system produced reports will be stored||This must be a valid directory set up on the server||Defined by the client
|}

==='''XF Monitor - Tracking Tab'''===

An enquiry screen that shows the status of all files that have been processed via the XF Monitor. It also has the function to enquire on files which have failed to upload with the option to resolve errors via the relevant validation screen.

<center>[[Image:EDI-009.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Date Run||Date and Time stamp of when the process ran||Display Only||N/A
|-
|Process ID ||Unique Process identifier assigned when the EDI Process is started or ran using Force Run option.||Display Only||N/A
|-
|Login Id||User id of the person who ran the process||Display Only||N/A
|-
|I/O||Inbound or Outbound Indicator ||Display Only||N/A
|-
|Process Detail||Indicates whether the FTP process was called||Display Only||N/A
|-
|Run Time m/s||The process run time in milliseconds||Display Only||N/A
|-
|Files Processing||The number of files processed in that particular process run.||Display Only||NA
|-
|Transient Table Successful / Failed (Inbound Only)||Indicates whether the file was successfully loaded onto the working tables ready for upload into the WMS.(Process checks the physical characteristics of the file. I.E. record length.||Display Only||N/A
|-
|WMS Successful / Failed||Indicates whether the file was successfully loaded into the WMS. (Process checks mandatory data that is validated within the WMS, such as Owner code or Product code).||Display Only||N/A
|-
|'''Buttons'''
|-
|Control Numbers||Unique number for each file that is uploaded on to the Transient Table||Display Only – Only if the file has failed to upload onto the WMS will a control number be displayed||N/A
|-
|Filter Data – Show Errors Only / Show all Records / Exclude empty records||All records are displayed in the Tracking Form, the Show Errors button allows for files to be filtered down||Drop down box to make required selection||N/A
|-
|Date From||Gives the option to enter a past date for the search and retrieval of data up to the present date (system default is 7 days)||N/a || N/a
|-
|Refresh||To initiate the search||N/a || N/a
|-
|Errors||Button that will only be displayed if a process is highlighted which is at error. The button will call the relevant validation screen and record for resolution.||N/a || N/a
|}

 

==='''XF Monitor - Emails Tab'''===

Email maintenance screen, where you set up the email addresses of any users requiring reports and audit files to be emailed to them.

 

'''NB:''' For the successful production and emailing of reports the database and O/S on the server require the emailing function to be enabled.

Ensure the Reports tick box is enabled on the front tab and the report directories have been created and specified in the Parameters Tab.

Reports are only generated for Inbound Messages.

 

<center>[[Image:EDI-010.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|User Id||User id of the person who ran the process as held on the WMS||Must have been set up in user maintenance||Defined by the client
|-
|Full Names||Full Name of the recipient of the reports||Full name for information purposes||Defined by the client
|-
|Email Address||Email address where the reports are to be sent||Valid email address||Defined by the client
|-
|EDI Reports||Required report to be sent via Email||Report Options Include - No EDI Rpts Audit Statistics Rpt Only Critical Errors Rpt Only Data Errors Rpt Only Audit and Critical Errors Rpt Audit and Data Errors Rpt Critical and Data Errors Rpt All Three Rpts||Defined by the client
|}

 

In Addition to the above configuration the system requires additional parameters to be set at server level.

Within '''System Registry / Global / GeneralSettings''' the following values must be entered with the relevant data values.

* AppServerConnectString = sce/password@database name 
* AppServerFloc = /u02/oraapp/xxx/xxxdev/forms 
* AppServerPort = 7777 
* AppServerHost = 10.43.0.70 or 127.0.0.1 
* AppServerReportServer = repxxxdev 
* DefaultDirectory = /tmp 

 

==='''XF Monitor - Reports Tab'''===

Report parameter maintenance screen to specify what kind of reports are to be produced by the system if required and where they are to be sent to.

'''NB''' Reports are only generated for inbound messages.

<center>[[Image:EDI-011.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|'''Process Audit Report Settings'''
|-
|Transfer Type||Option to specify how and where the reports are to be sent. Depending on the option selected additional information will be prompted for.||FTP N/A Printer Unix File ||Defined by the client
|-
|'''Process Error Report Settings'''
|-
|Transfer Type||Option to specify how and where the reports are to be sent. Depending on the option selected additional information will be prompted for.||FTP N/A Printer Unix File ||Defined by the client
|}

 

=='''EDI Listings and Setup Matrix'''==

==='''Hard-coded EDI outbound messages'''===

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Acknowledgement of Hold Release Message || N/a ||ACK||User Definable || dp_edigen_out_ack.write_flat_file || -
|-
|Despatch message (Client Specific)||N/a ||DESP || Not required? ||dp_edi_out_desp_conf.write_flat_file || Not to be used in future implementations (Included for completness)
|-
|Generic Receipt Message|| N/a || RCPT_CONF1|| GEN_RCPT || dp_edigen_out_receipt_confirm.process_out_recp_confirm ||-
|-
|Returns and Collections|| N/a||N/a||RETCOLL|| dp_edigen_retcoll.write_file||-
|-
|Acknowledgement of Allocation || Yes user definable ||N/a || Must be same name as used in EDI Common || dp_edigen_out_ack.write_alloc_ack_file || -
|-
|Allocation Message || N/a || DESP1 || GEN_ALLOC || dp_edigen_out_pdp_conf.write_flat_file || -
|-
|Cancellation message ||N/a || DESP1 || GEN_CANC ||dp_edigen_out_pdp_conf.write_flat_file ||-
|-
|Order Details ||N/a || DESP1 || GEN_ORD || dp_edigen_out_pdp_conf.write_flat_file ||-
|-
|Generic Pick Message||N/a || DESP1 || GEN_PICK || dp_edigen_out_pdp_conf.write_flat_file ||-
|-
|Generic Hold Message ||N/a || DESP1 || GEN_HOLD || dp_edigen_out_pdp_conf.write_flat_file || Order at status 6 being placed on hold
|-
|Generic Pack Message || N/a || DESP1 || GEN_PACK || dp_edigen_out_pdp_conf.write_flat_file || Fully Packed Order
|-
|Generic Despatch|| N/a || DESP1 || GEN_DESP || dp_edigen_out_pdp_conf.write_flat_file ||-
|-
|Missing Universal Product Code (Barcode information, client specific)|| N/a || N/a || MISSING_UPC || dp_edigen_out_missing_upcs.write_flat_file || -
|-
|Outbound Purchase Ordering ||N/a || N/a || POP|| dp_edigen_out_pop.write_flat_file ||-
|-
|RDT Stock drip feed of updates|| N/a || N/a ||RDTSTK|| dp_rdt_stock_drip_feed.xf_monitor_send_message || -
|-
|}

 

==='''Stock Snapshot Formats'''===

 

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Generic Stock Snapshot ||SALES_BAL ||SALES GEN SALES_BAL ||User Definable || dp_edigen_out_st_bal.generate_data DP_EDIGEN_OUT_ST_BAL.write_flat_file
|| Requires two packages to be run in the sequence listed.
|-
|Stock Snapshot by Rotation ||SALES_BAL ||STROT_BAL ||User Definable || dp_edigen_out_strot_bal.write_file ||Requires only one package
|-
|Stock Snapshot at Detail Level ||SALES_BAL ||STKDTL_GEN STKDTL_WRT||User Definable ||dp_edigen_out_st_bal.write_flat_file_dtl dp_edigen_out_st_bal.write_flat_file_dtl ||Requires two packages to be run in the sequence listed.
|-
|Client Specific|| SALES_BAL ||STOCK_GEN STOCK_BAL ||User Definable || dp_edigen_out_st_bal.generate_data dp_edigen_out_st_bal.write_flat_file ||Requires two packages to be run in the sequence listed.
|-
|Client Specific, Serials || SERIAL ||STOCK_GEN STOCK_BAL || STOCK_BAL_NOV ||dp_edigen_out_st_bal.generate_data dp_edigen_out_st_bal.write_flat_file ||Requires two packages to be run in the sequence listed. Include the value 'NOV' in the format code field in XF Monitor
|-
|}

 

==='''Hard-coded EDI Inbound messages'''===
 

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Booking /Reference Number Update (Client Specific)|| BOOK || N/a || BOOK || dp_edigen_book_upd_load.read_file_format ||-
|-
|Hold/Release Process || HOLD_LOAD || N/a ||HOLD_LOAD || dp_edigen_hold_load.read_file_format || -
|-
|Pre-Advice or ASN || GEN_GRN || PRE_ADV || GEN_GRN || dp_edigen_pre_advice_load.read_file_format || -
|-
|Product Master Upload (Generic)|| PRODUCT || PROD_LOAD || User definable || dp_edigen_product_master_load.read_file_format || -
|-
|Sales Order Upload || GEN_SOP || SOP1 || SALES_ORDER || dp_edigen_sales_order_load.read_sales_order_file || '''VALUE''' must be GEN_SOP for standard order file uploads but for XML the system requires another value of SOP to be maintained in the EDI Common.-
|-
|Sales Kit Upload || User definable, though must be the same name as the Process command in XF Monitor
|| N/a || User definable, though must be the same name as in EDI Common|| dp_edigen_stk_kit_load.read_file_format ||-
|-
|}

 

==='''Configurable EDI Outbound messages'''===

 

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Adjustment Flow || N/a || N/a ||Same name as configurable process ||dp_conf_edi_out.produce_dyn_edi_files || -
|-
|Serial Adjustment Flow || SERIAL || N/a || Same name as configurable process ||dp_conf_edi_out.produce_dyn_edi_files || Same setup as above but include the EDI common name to produce serial numbering records.
|-
|}

 

==='''Configurable EDI Inbound Messages'''===

 

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|SW Average Cost Upload || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor ||N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_edigen_sw_upd_load.read_file_format || -
|-
|Supplier Upload|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.read_edi_supp_file_format || -
|-
|Customer Upload ||User definable, though must be the same name as the Configuration process and the Process command in XF Monitor ||N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.read_edi_cust_file_format||Option to either upload or amend existing customer records
|-
|Inbound Hold/Release Process|| HOLD_LOAD || N/a || HOLD_LOAD || dp_edigen_hold_load.read_file_format|| -
|-
|Configurable Serial and Translation Number Upload || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor || N/a|| User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.med_seq_xfm || -
|-
|Stocks Base Selling Price|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor ||N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stk_base_sell_xfm || -
|-
|Stock Region and Sales territory (Client Specific)|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor||N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stock_region_xfm || -
|-
|Stock, UOM and Barcode information|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a || User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stk_uom_xfm || -
|-
|Stock Warehouse ||User definable, though must be the same name as the Configuration process and the Process command in XF Monitor || N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stock_warehouse_xfm || Putaway anchor points and replenishment levels
|-
|Updating of existing stock records|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor || N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stock_update_xfm || -
|-
|Pallet upload (WLE) || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.read_edi_wle || -
|-
|Pallet upload of held stock || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.wle_held_stock_xfm || -
|-
|Stock Master Upload ||User definable, though must be the same name as the Configuration process and the Process command in XF Monitor ||N/a||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.read_edi_prod_mast_format || -
|-
|Configurable stock warehouse || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stock_locations_xfm || Putaway anchor points and replenishment levels
|-
|}

 

==='''Carrier EDI Messages'''===

 

{| border="1"
!Description || Direction || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Carrier Interface - Allocation ||Out||N/a||N/a||CICA||dp_cim_outbound.write_cioc_cica_file|| -
|-
|Carrier Interface - Order Confirmation||Out||N/a||N/a||CIOC||dp_cim_outbound.write_cioc_cica_file ||-
|-
|Carrier interface - Package details||Out|| N/a||N/a||CIPD||dp_cim_outbound.write_cipd_file || -
|-
|Manual cancelled orders ||Out||N/a||N/a||CANC||dp_cim_outbound.write_canc_file|| -
|-
|POD Confirmation (Ireland Specific)||Out||N/a||N/a ||PODC || dp_cim_outbound.write_podc_file || -
|-
|Carrier interface - Tracking Details||In||CITD||N/a||CITD||dp_cim_inbound.read_file_format ||-
|-
|Carrier Interface - Packing Information||In||CICD ||N/a||CICD|| dp_cim_inbound.read_cicd_file_format|| -
|-
|}

 

==='''Miscellaneous EDI Messages'''===

 

{| border="1"
!Description || Direction || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|DHL Labels EDI Generation||Out||DHEG|| N/a||DHEG ||dp_edigen_out_pack_label.write_dheg_file|| -
|-
|DHL Label Tracking Reference || In|| DHEG_UPL ||N/a || DHEG_UPL ||dp_edigen_dheg_upd_load.read_file_format || Will capture a tracking reference number and automatically create pack header records
|-
|}

 

==='''Local Processes'''===

 

{| border="1"
!Description || Direction || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Script to automatically allocate all orders in the well ||Local||ALLOC||N/a||ALLOC||dp_edigen_alloc.xf_monitor_allocate|| -
|-
|If the order is held in Metapack as status ‘Manifested’, ‘Tracking’ or ‘Complete’, then the EDI process will initiate the WMS despatch process, down-dating the stock and updating the order as despatched. || Local || META_DESP || N/a ||META_DESP || dp_edigen_out_metapack.despatch_check ||Client specific see [[MetaPack]] for setup details
|}

 

==='''FTP Processes'''===

 

{| border="1"
!Description || Direction || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|In bound FTP process||In||N/a || FTP_INBND ||User Definable||dp_process_control_xfm.ftp_inbound|| -
|-
|Out bound FTP process||Out|| N/a|| FTP_OUTB||User Definable||dp_process_control_xfm.ftp_outbound ||-
|-
|}

 

'''NB'''

'''EDI Common Name *''' As a general rule an EDI Common Name is required for all inbound messages but is not a requirement for outbound messages, though there are a couple of exceptions as noted above, i.e. Outbound Serial numbering functionality 

'''XF Command Screen (XFM0012)**''' These are all user definable, but depending on the system install there may be existing records, as noted above. 

'''Process Code (XFMonitor XFM0020)***''' As a rule outbound proceses require a specifed Process Code, the required values are listed above. 

 

=='''VALIDATION SCREENS'''==

For each inbound EDI flow, there is a validation screen. Errors are sequenced by a control number and are displayed in the validation screens where it is possible to rectify the data. Each of the validation screens will differ slightly dependent on the key fields for the message type being accessed.

Validation screens exist for the following processes: - 

:*GRN Pre- Advice 
:*Sales Order 
:*Product Master 
:*Inbound Holds 
:*Stock Reconciliation 
:*Order Management (Client Specific) 
:*Average Cost 
:*Stock Kit Validation 
:*Medical Sequence Validation (Client Specific)

The error records are held in the EDI transient tables until they are validated successfully and the relevant WMS record created at which point they are then cleared down.

==='''Validation Header Screen'''===

Taking the GRN Pre Advice Validation Screen as an example-

<center>[[Image:EDI-012.PNG]]</center>

First find the relevant Control Number (Control Numbers are only assigned to messages which have failed to upload)

There is then the option to either -

:'''Validate All''' This will re-submit the file to the system in an attempt to re-process it in its entirety . This is only relevant after all errors in the file have been addressed.
:'''Details''' will take you in to the body of the message allowing the user to identify the issue within the file and how to resolve it.

 

==='''Validation Detail Screen'''===

'''NB''' The number of tabs within the detail screen and the information displayed will depend on the type of the EDI flow being validated.

<center>[[Image:EDI-013.PNG]]</center>

The number of errors detected and their description will be displayed in the bottom portion of the form, these will then require resolving before the record can be validated and the record written to the WMS tables. Depending on the type of error this can be achieved by either adding or amending the data within the actual WMS system, or amending the data contained within the file by changing the values directly within the validation form.

Once the errors have been resolved it is then possible to re-submit the message, by selecting the '''Validate Button '''. This will only re-process a single record as a time, where if you select '''Main''' you will be returned to the top screen where the entire message can be re-submitted and validated.

 

=='''OUT BOUND RE-SEND SCREENS'''==

If messages have not been generated, have gone missing or require re-transmitting then it is possible to re-generate the message where it will wait for the next out bound ftp process.

Current resend screens: - 
:*Outbound GRN Confirmation Message 
:*Outbound Pack Confirmation Message 

==='''GRMK Re-send '''===

<center>[[Image:EDI-014.PNG]]</center>
Select the GRN number that requires resending, an LOV is available which will display all closed GRN’s.

Press the Resend button to generate the required message

===''' Packing Details Re-send '''===

<center>[[Image:EDI-015.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Owner ||Owner Code and Sub account id||Default from current user||Defined by the client
|-
|Select By ||Selection criteria for re-transmission||Orders or Despatch Date ||Defined by the client
|-
|Start Order No / End Order No||By Order Number||Order Number From / Order Number To||Defined by the client
|-
|Despatch Date From / Despatch Date To||By Despatch Date||Despatch Date From / Despatch To||Defined by the client
|}

 

=='''CONFIGURABLE EDI SETUP'''==

==='''Dynamic Inbound EDI Message Definition'''===

==='''System Registry (ULF0030)'''===

To produce log files to aid error resolution and to display tracking information within the XF Monitor Tracking page the following system registry setting must be entered at a Global Level ''''ConfEdiLogDisplay'''' with a value of ''''Y''''

<center>[[Image:EC-001.PNG | System Registry]]</center>

For a list of configurable EDI Messages see - [[#Configurable EDI Inbound Messages | Configurable EDI Inbound Messages ]]

 

=== '''XF Dynamic Inbound EDI Definition Screen (XFM0055)===

<center>[[Image:CON-001.PNG | Dynamic Inbund EDI Definition]]</center>

 

=='''Inbound Configurable Setup (Example)'''==

Following is a description on the steps required to setup an Inbound Configurable message for a Stock Warehouse update.

'''NB''' In the example below the process has been named '''STKWHSE''' the name is definable, but the same name must be used in the following screens -

* [[#EDI COMMON MAINTENANCE | EDI Common Maintenance (EDI0001)- Message Type ]]
* [[#XF Dynamic Inbound EDI Definition Screen (XFM0055)|Dynamic Inbound EDI Message Definition (XFM0055) - EDI Message ]]
* [[#XF MONITOR |XF Monitor (XFM0020) - Process Code ]]

See above for a detailed description of each of the forms.

'''EDI Common Record (EDI0001) '''

The common record for the message, is used to link the company code, warehouse, and owner to the records in the inbound file.

<center>[[Image:EC-002a.PNG | Common Record]]</center>

 

'''XF Command Screen (XFM0012) '''

The package id which is user definable and the database process that will validate and upload the file.

<center>[[Image:EC-003.PNG | Command Screen]]</center>

 

'''XF Re-sequence (XFM0011)'''

The linked process command that allows the system to run combined multiple packages if required.

<center>[[Image:EC-004.PNG | Re-Sequence]]</center>

 

'''XF Dynamic Inbound EDI Definition Screen (XFM0055) '''

The Configuration screen - where the EDI message name, type and individual message elements are specified.

* Ensure the EDI Message name is the same as the one entered in EDI Common.

<center>[[Image:EC-005.PNG | Configuration Screen]]</center>

 

'''Edit Level Data'''

Dependent on the chosen format type, ensure that the relevant Field No or Start Positions information is entered.

<center>[[Image:EC-006a.PNG | Configuration Screen - Data Elements ]]</center>

 

'''XF Monitor (XFM0020)'''

Create the XF Monitor record as detailed above.
'''NB''' Ensure the name created in the Process Code field is the same as created in EDI Common and the Dynamic Inbound EDI Definition screen.

<center>[[Image:EC-006.PNG | XF Monitor]]</center>

 

==='''Dynamic Outbound EDI Message Definition'''===

 

{| border="1"
!Field Name||Description ||
|-
|Adjustments || Positive and negative adjustments also hold and release
|-
|Inventory || Stock Balances
|-
|Orders || Order information
|-
|}

 

==='''Outbound EDI Message Definition'''===

Filename Construction is a template maintenance screen that allows outbound EDI files to be sent via ftp with a specific filename definition.

If the user defines a filename within the file template form (i.e. ‘IED40430.nnn’ in this case), the outbound ftp process will be altered to check for the existence of filenames of the type ‘IED40430*’. The filename string to search for will be constructed dynamically based on the user-defined elements entered for the template code in question. For this reason, the user will be expected to create template codes with at least one user-defined segment for filenames that are to be ftp’d.

<center>[[Image:EDI-016.PNG | File Construction]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Template Id||Unique name of template||LOV provided for existing templates||Defined by the client
|-
|File String||an example of how the filename will look ||Built up by the system as values are entered in the detail part of the form and then refreshed ||Defined by the client
|-
|Example||Actual Example of file name|| Built up by the system as values are entered in the detail part of the form and then refreshed|| Defined by the client
|-
|Seq||Sequence number within file string|| ||Defined by the client
|-
|Key Type||Individual file element ||Options include- Hard Code, Date, Extension, Separator, Sequence, Time, User Defined||Defined by the client
|-
|Value|| Data element to be displayed || Depending on the key type selected their will either be a relevant LOV or the option of entering free text ||Defined by the client
|-
|}

 

{| border="1"
!Buttons || Description
|-
|Add Key Before||Insert key into string in front of the selected value
|-
|Add Key After ||Insert key into string after the selected value
|-
|Delete Key||Delete the key or element from the string
|-
|Move Up||Move the element up in the string
|-
|Move Down||Move the element down in the string
|-
|Refresh String||Will populate the File String and Example filds
|}

 

=='''FTP SETUP'''==

FTP Inbound and outbound is executed via a database package the same way as the standard EDI processes. In addition to the calling of the data base packages there is the requirement to set the I.P. address and login details of the remote machine.

It is possible to run the FTP processes standalone or as part of another process.

<center>[[Image:EDI-017.PNG | XF Re Sequence]]</center>

In the above example the process command DESP1 will run consecutively the DESP1 package which will generate the Despatch Messages, followed upon completion by the FTP_OUT_WM package which will the ftp process to which will attempt to place the Despatch files onto the remote machine.

<center>[[Image:EDI-018.PNG | FTP Process]]</center>

Set the transfer type to – FTP Transfer

 

=='''EDI Reprocessing'''==

This change will apply to inbound EDI flows only as it refers to the processing of items placed in the transient tables because of a process validation issue.

The current EDI flows that will be included in this change are: 

* Sales Order 
* Hold / Release 
* Pre - Advice 
* Stock Upload 

<center>[[Image:EDI-088a.PNG | EDI Reprocessing]]</center>

 

The aim is to reduce the amount of user intervention required when issues like record locking occur during the original data load.

A new screen will list the EDI flows that are setup for the current Warehouse / Owner combination. These EDI flows will appear regardless of whether they are currently running, the screen will display the same flows that can be seen in the XF Monitor screen.

Within this screen there will be option to select each flow. Once a flow is selected, the user must enter the number of times they want each load to be reprocessed and the frequency in minutes between each reprocess run.

If the load reaches the maximum number of re-tries, then it will no longer process automatically but will be available in the usual validation screens for users to validate / update manually.

There will be the option within the screen to start and stop the automatic reprocessing.
The users will have to start the process running initially, and then have the option to stop it if required. There will be an indicator on the screen to show if it is currently running.

If the emailing of EDI error reports is set up for the flow, the selected reports will be emailed to the stated users if the load reaches the maximum number of retries.

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>08/03/2011</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>LBW</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

EDI Setup and Processing

2017-02-03T14:05:20Z

Lwinchester: /* OWNER MAINTENANCE - EDI Inbound & Outbound (Client Specific EDI Configuration) */

=='''IN PROGRESS'''==

'''To Add - '''

:Cancelling of held orders

:Directory structure on server

=='''INTRODUCTION'''==
This document describes the screens that are required to set up the control data for the EDI Processes in the warehouse. Other guides describe the set up of company, user, warehouse, owners etc.

This is a generic guide based on the version of the Calidus (3pl) system at the time of writing.

Note that fields marked ‘**’ are mandatory and are needed to ensure correct set up of the system.

=='''OVERVIEW'''==
Set up requirements for the use of EDI processes are done in two main stages:

1- Set up of the required general EDI codes for the company level common values (Existing codes are pre-entered when the WMS installed)

:General Codes (PFS0260 & PFS0261) 
:EDI Common (EDI0001) 
:EDI Last Numbers (INS7050) 

2- Addition of the Common records at Owner or Client level and the Configuration of the XF Monitor which is the main EDI engine

:XF Command (XFM0012) 
:XF Resequence (XFM0011) 
:XF Monitor (XFM0020) 

=='''GENERAL EDI CODES – HEADER LEVEL'''==

For each message, you need to set up an EDI code under the heading of ‘EDDI’ in general codes maintenance. These dictate the type of message and what the EDI control number starts with.

'''NB''' – These codes should be have been created when the base system is installed.

 

<center>[[Image:EDI-001a.png]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Type **||The code type you are entering details against ||Entry at this level will not be required as these will already have been set up on a company level||EDDI
|-
|Length **||The number of characters the sub code has to be||1 – 9999||10
|-
|Description **||A brief description of the type of code||100 character free text field||EDI Applications
|-
|Code Flag **||Is this code to be used by the system||Y or N – default is Y||Y
|-
|Info||The ability to enter extra information against the code (not migrated)||Blank ||Blank
|-
|'''Buttons'''
|-
|Extra Info||The ability to enter additional information, e.g. which screens use this, the purpose of the code etc||Entry at this level will not be required as these will already have been set up on a company level||N/A
|-
|Details||Takes you into the detail screens for individual entry of each required code||See following||Defined by system setup
|}

=='''General Codes – Detail Level'''==
For each EDI message required, the code value, description and short description need to be populated. The details to be populated will be described below dependant on the message type.

<center>[[Image:EDI-002.PNG]]</center>
{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Code Type||The code type the values entered refer to ||No entry required as the code type will come through from the header screen||EDDI
|-
|Code Value **||The unique identifier for the EDI message required||Defined by the hard coding of each EDI message. he size is determined by the length of the code type entered in the header screen. List of required values below.||See below
|-
|Description **||Description of the EDI message being created||100 character free text field||Defined by the client
|-
|Short Desc **||Will determine the first 3 characters of the control number||Defined by the hard coding of each EDI message||See below
|}

==='''General Codes – Code Types'''===

{| border="1"
!Code Value||Description||Short Description||Message Details
|-
|OCI||Outbound Commercial Invoice Upload||OCI ||An inbound message that updates orders with customs data (cost, country of origin etc)(Client Specific)
|-
|CII||Inbound Commercial Invoice Upload||CII||An inbound message that updates receipts with customs data (cost, country of origin etc)(Client Specific)
|-
|PACK||Kewill Carrier Upload||PKI||An inbound message that updates orders with carrier, weight and tracking number information (Client Specific)
|-
|SRI||Stock Reconciliation Upload||SRI||An inbound message that compares a client’s stockholding figures with the actual values held on the WMS (Client Specific) See below
|-
|PAI||Pre Advice Upload||PAI||An inbound message that uploads a receipt pre advice into the WMS
|-
|GRN||Pre Advice Upload||PAI||An inbound message that uploads a receipt pre advice into the WMS
|-
|PMI||Product Master Upload||PMI||An inbound message that creates stock codes on the WMS
|-
|STID||Product Master Upload||PMI||An inbound message that creates stock codes on the WMS
|-
|SOI||Sales Order Upload||SOI||An inbound message that uploads sales orders onto the WMS (Client Specific)
|-
|SOP||Sales Order Upload||SOI||An inbound message that uploads sales orders onto the WMS
|-
|HOLD||Hold Upload||Hold||An inbound message that will either hold or release stock quantities
|-
|WLE||Ware Location Upload||WLE||An inbound message that will create pallet records with associated stock details
|}

=='''OWNER MAINTENANCE - EDI Inbound & Outbound (Client Specific EDI Configuration)'''==

---IN PROGRESS---

'''The following section explains the generation of Sales Order Numbers when using the Sales Order message upload functionality'''

<center>[[Image:OW-001.PNG]]</center>

'''Prevent Duplicate Order Ref:'''

:‘Dup Ord Ref not on system’
:The whole file will be rejected if the order exists

:‘Duplicate Order Ref Allowed’
:The order will be uploaded – if a non-unique order is uploaded multiple times, errors will :occur.

:‘Upload All Recs Excluding Dups’
:All orders will be uploaded into the EDI transient table. However, the duplicate will be held :with errors.

'''System EDI S/O Number:''' 
:If Y – the system will generate a unique sequential reference to build the order number.
:If N – The system will use the ‘order reference’ received as part of the order to build the order number.

 

<center>[[Image:OW-002.PNG]]</center>

'''Sequence No. Generate:'''
:The normal is ‘Owner Range’

 

<center>[[Image:OW-003.PNG]]</center>

'''Order Number Without Owner Prefix:'''
:This may be Yes or No

If EITHER ‘Sequence No. Generate’ or ‘Order Number Without Owner Prefix’ are set to ‘Owner Range’ or ‘N’ respectively, the order number will be 20 characters long. Else it will be either a simply sequential reference or the order reference supplied.

'''NB''' Two new value have been added to Owner System Parameters (WHS0012) EDI Setting of Sales Order Number and EDI Sales Order Number Prefix

 

=='''EDI LAST NUMBERS'''==

EDI last numbers are used to increment each EDI control number by one. These are dictated by the entry in the EDI codes. These numbers are set automatically by the system, so there is no requirement for user configuration.

<center>[[Image:EDI-0004.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Owner **||The owner code and sub code the message will be created for||Must have been created in owner maintenance or set to ‘+’ – will automatically create, so all will be set to the owner code of the message||‘+’
|-
|Message Type **||Based on the values created in EDI common maintenance – a record needs to exist here for each message required||Must have been set up in EDI common maintenance||Defined by the client
|-
|Last Number **||The starting number for each EDI message||0 – 99999 – will start at 0 for each new message||0
|}

 

=='''EDI COMMON MAINTENANCE'''==
EDI common is used to dictate for what company/warehouse/owner the EDI flows are for.

<center>[[Image:EDI-003.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Company Code **||Company code the user is setting up the EDI for||Must have been created in company maintenance||Defined by the client
|-
|Warehouse ID **||The warehouse code the user is setting up the EDI for||Must have been created in warehouse maintenance||Defined by the client
|-
|Message Type **||The message type of the EDI flow you are setting up||Defined by the hard coding of each EDI message – available message types listed below||See below
|-
|Key 1 **||If the database is to have multiple owners under one warehouse/company combination the owner code for each message will need to be set up here||Owner code of the owner otherwise ‘+’ if only one owner per warehouse using EDI. '''Advisable to always define the owner code.'''||Defined by the client
|-
|Key 2 **||If the database is to have multiple owners under one warehouse/company combination the owner sub code for each message will need to be set up here||Owner sub code otherwise ‘+’ if only one owner per warehouse using EDI.||Defined by the client
|-
|Company Code **||Company code the user is setting up the EDI for||Must have been created in company maintenance||Defined by the client
|-
|Warehouse Id **||The warehouse code the user is setting up the EDI for||Must have been created in warehouse maintenance||Defined by the client
|-
|Department **||The department code set up against the company||Must have been created in departments maintenance||Defined by the client
|-
|Ledger Code **||Determines which area of the system the message relates to||PL1 or SL1||See below
|-
|Branch Code **||The branch code set up against the company (not required)||Must have been set up in branch code maintenance or set to '+' ||+
|-
|Owner Code **||The owner code and sub code the message is being set up for||Must have been created in owner maintenance||Defined by the client
|-
|Stockist Code **(same as owner code)||The owner code and sub code the message is being set up for||Must have been created in owner maintenance||Defined by the client
|-
|Base Currency **||The default currency code being used by the owner||Must have been created in currency maintenance||Defined by the client
|}

=='''EDI XF COMMAND '''==

This screen is used to dictate which package is called for each flow. The package id field is user definable, but the ‘Package SQL Code’ is predetermined by the package format.

Once you have entered the package id and the package SQL code, you must then specify whether it is an inbound or outbound flow.

<center>[[Image:EDI-005a.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Package Id **||The unique identifier for this message type – note, you will need to remember this for further setup||10 character free text field||Defined by the client
|-
|Inbound/Outbound/Local **||Specifies whether the message is an inbound or an outbound flow (note, ‘local’ is not used for current WMS implementations)||Check box||Defined by the message type
|-
|Package SQL Code **||The programming instruction to determine which package the EDI will call||Defined by the hard coding of the program||Defined by the message type
|}

==='''Command Values'''===
Below is a table of the current commands

'''NB these will increase as new messages are added to the system as required'''

{| border="1" align="center"
!Package Id (User Definable)||Inbound or Outbound||Package SQL Statement
|-
|'''Standard Client Message Types'''
|-
|Despatch Message||Outbound||dp_edigen_out_pdp_conf.write_flat_file
|-
|Stock Master Upload||Inbound||dp_edigen_product_master_load.read_file_format
|-
|Sales Order Upload||Inbound||dp_edigen_sales_order_load.read_sales_order_file
|-
|GRMK – Receipt Message||Outbound||dp_edigen_out_receipt_confirm.process_out_recp_confirm
|-
|Pre Advice or ASN Message||Inbound||dp_edigen_pre_advice_load.read_file_format
|-
|Hold or Release Message||Inbound||dp_edigen_hold_load.read_file_format
|-
|Acknowledgement of Hold Release Message ||Outbound||dp_edigen_out_ack.write_flat_file
|-
|Purchase Ordering||Outbound||dp_edigen_out_pop.write_flat_file
|-
|Courier Returns and Collection||Outbound||dp_edigen_retcoll.write_file
|-
|Standard Stock Inventory Balance (Requires two packages to be run)||Outbound||dp_edigen_out_st_bal.generate_data (populates temporary tables) -dp_edigen_out_st_bal.write_flat_file (writes the file)
|-
|Stock inventory balance by Rotation Only requires one package||Outbound||dp_edigen_out_strot_bal.write_file (This writes a ‘SROL’ record, which is a single level rotation based snapshot)
|-
|Stock Snapshot (Include both customer and system rotations and SAP storage locations)(F/S 230465)||Outbound||Additional rotation level dp_edigen_out_st_bal.generate_detail_data dp_edigen_out_st_bal.write_flat_file_dtl This process writes a SD01 and SD02 lines – the SD02 record is a rotation level record.
|-
|}

 

'''Carrier Interface Messages'''

{| border="1"
!Package Id (User Definable)||Inbound or Outbound||Package SQL Statement
|-
|CANC – Cancelled Orders||Outbound||cim_outbound.write_canc_file
|-
|CICA – Post Allocation||Outbound||cim_outbound.write_cioc_cica_file
|-
|CICD – Pre – Allocation ||Inbound||dp_cim_inbound.read_cicd_file_format
|-
|CIOC – Order Entry Information||Outbound||cim_outbound.write_cioc_cica_file
|-
|CIPD – Packing Information||Outbound||cim_outbound.write_cipd_file
|-
|CITD – Despatch Confirmation||Inbound||dp_cim_inbound.read_file_format
|-
|PODC – IE Specific POD confirmation||Outbound||cim_outbound.write_podc_file
|-
|CARR – Carrier Collection Message||Outbound||dp_edigen_out_carr_conf.write_flat_file
|-
|}

 

'''Configurable EDI'''
'''Inbound'''

{| border="1"
!EDI Structure ||Description ||Package SQL Statement
|-
|CUSTOMER || Customer detail upload || dp_conf_edi_in.read_edi_cust_file_format
|-
|MED_TRANSLATION || (Client specific) - Medical and serial translation || dp_conf_edi_in.med_seq_xfm
|-
|OMS_POST_WHS||(Client specific) OMS Postcode/Warehouse Upload || dp_conf_edi_in_oms.load_oms_pc
|-
|STKBASEUPL || Stock Base Sell upload/update || dp_conf_edi_in.stk_base_sell_xfm
|-
|STK_LOCATION || Stock Location upload ||dp_conf_edi_in.stock_locations_xfm
|-
|STK_WAREHOUSE || Stock Warehouse||dp_conf_edi_in.stock_warehouse_xfm
|-
|STOCK|| Stock Upload||dp_conf_edi_in.read_edi_prod_mast_format
|-
|STOCK_REGION || Stock Region upload/update ||dp_conf_edi_in.stock_region_xfm
|-
|STOCK_UOM || Stock UOM upload|| dp_conf_edi_in.stk_uom_xfm
|-
|STOCK_UPDATE || Stock update || dp_conf_edi_in.stock_update_xfm
|-
|SUPPLIER || Supplier detail upload ||
|-
|WLE || Dynamic Stock Upload ||dp_conf_edi_in.read_edi_wle
|-
|WLE Held Stock || Dynamic Held Stock Upload ||dp_conf_edi_in.wle_held_stock_xfm
|-
|}

'''Outbound '''
{| border="1"
!EDI Structure ||Description ||Package SQL Statement
|-
|Adjustments ||Outbound||dp_conf_edi_out.produce_dyn_edi_files
|-
|Outbound Order Information||Outbound||?
|-
|Stock Inventory Balances||Outbound||?
|-

|}

'''FTP Packages'''
{| border="1"
!EDI Structure ||Description ||Package SQL Statement
|-
|FTP Inbound||Inbound||dp_process_control_xfm.ftp_inbound
|-
|FTP Outbound||Outbound||dp_process_control_xfm.ftp_outbound
|}

 

=='''XF RESEQUENCE'''==

The XF Re-sequence screen is used if you wish to call multiple packages under one package id. You then specify which package, and in what priority. For example to automatically ftp despatch messages on to a remote server you would set sequence one to run the DESP package and then sequence two would run the outbound ftp package.

<center>[[Image:EDI-006.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|'''Process Command **'''||Based on the package id set up in the previous screen – this will ensure the process calls the correct package||Must have been set up in xf process command||'''Defined by the client only for Outbound messages, see table below for inbound message naming formats'''
|-
|Process Description **||A brief description of what EDI message the process code relates to||50 character free text field||Defined by the client
|-
|Inbound/Outbound/Local **||Specifies whether the message is an inbound or an outbound flow (note, ‘local’ is not used for current WMS implementations )|| ||Defined by the message type
|-
|}

 

{| border="1"
!Buttons||Description
|-
|Add Package||Adds the selected package to the sequencing pool|| ||
|-
|Remove package||Removes the selected package from the sequencing pool|| ||
|-
|Select Up||Moves the packages up so the one you require is selected|| ||
|-
|Select Down||Moves the packages down so the one you require is selected|| ||
|-
|Re-sequence Up||If more than one selected package in the pool, re-sequences the priorities of the flows (upwards)|| ||
|-
|Re-sequence Down||If more than one selected package in the pool, re-sequences the priorities of the flows (down)|| ||
|}

 

=='''XF MONITOR'''==
For each EDI flow, you need to set up core information such as which package to run and at what time and frequency. There is also the requirement to enter directory and reporting parameters. These are configured in the XF monitor screen. There are multiple tabs to set up dependent on requirements.

==='''XF Monitor – Setup tab'''===

<center>[[Image:EDI-007.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Process Code **||Uses the process code as specified in xf command/resequence and adds the company, owner and warehouse||Must have been set up in xf command and xf resequence||'''Defined by the client, but dependent on message flow may require a defined code. See table below.'''
|-
|Process Description **||A description of the process code||60 character free text field||Defined by the client
|-
|Process Id||If using EDI running processes, gives the message a unique system generated process id||No entry required – generated by the system||N/A
|-
|Transfer Method **||How the EDI will be transmitted||EDI or Non-EDI||EDI
|-
|Transfer Type **||Specifies in what format the files will be generated||EDI Transfer / FTP Transfer / Unix Transfer or N/A||EDI or FTP dependent on whether the file will be picked up from a remote server or sent to a remote server.
|-
|Send/Receive **||Specifies whether the file is to be received or sent (inbound or outbound)||Send or Receive||Determined by the message
|-
|Process Type **||This is where you specify how you want the flow to run and when. If you set the process type to interval – you will need to put in an interval time in the Interval (mins) field – in the example above, this will run every 15 minutes. If you set this to Time (24hr) – you will then be asked for which days and what time. This will cause the flow to run, say every day at 21:00||Interval / Time (24hr) ||Defined by the client
|-
|Interval (mins)/Frequency||If set to Interval, the number of minutes before the process should start again. If set to Time, you will see a box for a time and every day of the week which can be checked to enable the run at a specific time for specific days||0 – 999999||Defined by the client
|-
|Process Command **||The package id as entered in the process code at header level||Must have been set up in xf command and xf resequence||Defined by the client
|-
|File Retention Days||If archiving, the number of days files that will be kept||N/A||N/A
|-
|UOM Flag (F/S 231470)||Used to allow the WMS system to work in a different UOM than the clients system.||N - No conversion required C - Convert units to cases U - Convert cases to units R - Convert units to cases round up N - No conversion required || Defined by Client
|-
|EDI File Separator||Specifies what delimiters the EDI files will be using, used for configurable messages.||‘/’ ‘;’ ‘|’ etc||Defined by the client
|-
|Reports Flag||Specifies whether you wish upload and exception reports to be produced||Yes / No||Defined by the client
|-
|Process State||Shows whether the EDI message is running on a process or not||Display only – Stopped, Running or Broken||N/A
|-
|Start Date||If you click the ‘Start Process’ button – this will display the date the process was started ||Display only||N/A
|-
|Started By||The user id of the person who has started the process running||Display only||N/A
|-
|Next Run||Calculates the date/time the next process will run based on the last run plus the interval||Display only||N/A
|-
|Inbound File Formats||The format of the incoming file||CSV / Fixed Length / Syspro / Attribute based XML || Defined by the client
|-
|Element based XML ||Defined by the client|| N/a || N/a
|-
|Format code || Defined by the client || N/a || N/a
|-
|}

 

{| border="1"
!Buttons||Description
|-
|Force Run||Enables a ‘one off’ EDI poll|| ||
|-
|Start Process||Begins the polling process that will trigger the message to be uploaded/sent at the relevant time.|| ||
|-
|Stop Process||Stops the frequency/interval from running|| ||
|}

'''NB: Generic EDI flows must have a Process Code (Within XFMonitor, XFM0020) that start with the following string of characters. '''

{| border="1"
!Process Command Must Begin With - ||Flow
|-
|SOP|| Sales Order
|-
|PRE_ADV || GRN Upload
|-
|PROD_LOAD ||Stock Upload
|-
|GEN_ALLOC || Outbound Sales Order Allocation Message
|-
|GEN_CANC || Outbound Order Cancellation Message
|-
|GEN_PICK ||Outbound Pick Message
|-
|GEN_DESP ||Outbound Despatch Message
|-
|GEN_RCPT || Outbound General Receipt
|-
|SADJ || Outbound Serial Number Adjustment
|-
|HOLD_LOAD|| Inbound Holds
|-
|ORDMGT ||Order Management
|}

'''NB: The process command can be any length within the screen limitation, but for i.e. sales orders the process command must be like ‘SOP’, ‘SOP1’ etc

‘1SOP’ will not be seen as a sales order upload.'''

 

==='''XF Monitor Parameters Tab'''===

The parameter tab controls the storage and the naming convention of the produced files. If the transfer type is set to FTP within the setup tab then the ftp control fields will be displayed.

<center>[[Image:EDI-008.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|File Directory **||This is the directory the WMS will search for the message file||This must be a valid directory set up on the Unix box||Defined by the client
|-
|File Pattern or Template id||File pattern is used for standard EDI messages. For an increased configurable file name then select Template id. Allows for the inclusion of user definable Date/Time stamps etc within the file name format.||File Pattern or Template id||Reference XFM0030 File name construction if template id selected
|-
|File Pattern **||The EDI package will upload any file starting with these characters, i.e. as above, anything starting with XXADESP_ ||The file pattern will be determined by the system architects who are creating the EDI files||Defined by the client
|-
|Archive Directory **||The directory that all processed files will move to||This must be a valid directory set up on the Unix box||Defined by the client
|-
|FTP Parameters
|-
|FTP Address **||The I.P. address of the target server||Must be a valid I.P. address that is accessible by the WMS server.||Defined by the client
|-
|FTP Username **||User or account name set up on the target server||Must be a valid user id set up on the target server.||Defined by the client
|-
|FTP Password **||Password for user or account on target server||Valid password for the username account.||Defined by the client
|-
|FTP Final Directory **||Directory where files are to be sent||Valid and accessible account (i.e. permissions must be set to allow files to be copied)||Defined by the client
|-
|FTP Put Directory||Temporary work directory on the target server||If required it must be valid and accessible.||Defined by the client
|-
|Log File Settings Directory **||Which directory all processed log files will be sent to||This must be a valid directory set up on the server||Defined by the client
|-
|Log File Settings Filename **||The name of the log file to be produced ||Can be any file name the user sets up||Defined by the client
|-
|Report Directory||Directory name and path where system produced reports will be stored||This must be a valid directory set up on the server||Defined by the client
|}

==='''XF Monitor - Tracking Tab'''===

An enquiry screen that shows the status of all files that have been processed via the XF Monitor. It also has the function to enquire on files which have failed to upload with the option to resolve errors via the relevant validation screen.

<center>[[Image:EDI-009.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Date Run||Date and Time stamp of when the process ran||Display Only||N/A
|-
|Process ID ||Unique Process identifier assigned when the EDI Process is started or ran using Force Run option.||Display Only||N/A
|-
|Login Id||User id of the person who ran the process||Display Only||N/A
|-
|I/O||Inbound or Outbound Indicator ||Display Only||N/A
|-
|Process Detail||Indicates whether the FTP process was called||Display Only||N/A
|-
|Run Time m/s||The process run time in milliseconds||Display Only||N/A
|-
|Files Processing||The number of files processed in that particular process run.||Display Only||NA
|-
|Transient Table Successful / Failed (Inbound Only)||Indicates whether the file was successfully loaded onto the working tables ready for upload into the WMS.(Process checks the physical characteristics of the file. I.E. record length.||Display Only||N/A
|-
|WMS Successful / Failed||Indicates whether the file was successfully loaded into the WMS. (Process checks mandatory data that is validated within the WMS, such as Owner code or Product code).||Display Only||N/A
|-
|'''Buttons'''
|-
|Control Numbers||Unique number for each file that is uploaded on to the Transient Table||Display Only – Only if the file has failed to upload onto the WMS will a control number be displayed||N/A
|-
|Filter Data – Show Errors Only / Show all Records / Exclude empty records||All records are displayed in the Tracking Form, the Show Errors button allows for files to be filtered down||Drop down box to make required selection||N/A
|-
|Date From||Gives the option to enter a past date for the search and retrieval of data up to the present date (system default is 7 days)||N/a || N/a
|-
|Refresh||To initiate the search||N/a || N/a
|-
|Errors||Button that will only be displayed if a process is highlighted which is at error. The button will call the relevant validation screen and record for resolution.||N/a || N/a
|}

 

==='''XF Monitor - Emails Tab'''===

Email maintenance screen, where you set up the email addresses of any users requiring reports and audit files to be emailed to them.

 

'''NB:''' For the successful production and emailing of reports the database and O/S on the server require the emailing function to be enabled.

Ensure the Reports tick box is enabled on the front tab and the report directories have been created and specified in the Parameters Tab.

Reports are only generated for Inbound Messages.

 

<center>[[Image:EDI-010.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|User Id||User id of the person who ran the process as held on the WMS||Must have been set up in user maintenance||Defined by the client
|-
|Full Names||Full Name of the recipient of the reports||Full name for information purposes||Defined by the client
|-
|Email Address||Email address where the reports are to be sent||Valid email address||Defined by the client
|-
|EDI Reports||Required report to be sent via Email||Report Options Include - No EDI Rpts Audit Statistics Rpt Only Critical Errors Rpt Only Data Errors Rpt Only Audit and Critical Errors Rpt Audit and Data Errors Rpt Critical and Data Errors Rpt All Three Rpts||Defined by the client
|}

 

In Addition to the above configuration the system requires additional parameters to be set at server level.

Within '''System Registry / Global / GeneralSettings''' the following values must be entered with the relevant data values.

* AppServerConnectString = sce/password@database name 
* AppServerFloc = /u02/oraapp/xxx/xxxdev/forms 
* AppServerPort = 7777 
* AppServerHost = 10.43.0.70 or 127.0.0.1 
* AppServerReportServer = repxxxdev 
* DefaultDirectory = /tmp 

 

==='''XF Monitor - Reports Tab'''===

Report parameter maintenance screen to specify what kind of reports are to be produced by the system if required and where they are to be sent to.

'''NB''' Reports are only generated for inbound messages.

<center>[[Image:EDI-011.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|'''Process Audit Report Settings'''
|-
|Transfer Type||Option to specify how and where the reports are to be sent. Depending on the option selected additional information will be prompted for.||FTP N/A Printer Unix File ||Defined by the client
|-
|'''Process Error Report Settings'''
|-
|Transfer Type||Option to specify how and where the reports are to be sent. Depending on the option selected additional information will be prompted for.||FTP N/A Printer Unix File ||Defined by the client
|}

 

=='''EDI Listings and Setup Matrix'''==

==='''Hard-coded EDI outbound messages'''===

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Acknowledgement of Hold Release Message || N/a ||ACK||User Definable || dp_edigen_out_ack.write_flat_file || -
|-
|Despatch message (Client Specific)||N/a ||DESP || Not required? ||dp_edi_out_desp_conf.write_flat_file || Not to be used in future implementations (Included for completness)
|-
|Generic Receipt Message|| N/a || RCPT_CONF1|| GEN_RCPT || dp_edigen_out_receipt_confirm.process_out_recp_confirm ||-
|-
|Returns and Collections|| N/a||N/a||RETCOLL|| dp_edigen_retcoll.write_file||-
|-
|Acknowledgement of Allocation || Yes user definable ||N/a || Must be same name as used in EDI Common || dp_edigen_out_ack.write_alloc_ack_file || -
|-
|Allocation Message || N/a || DESP1 || GEN_ALLOC || dp_edigen_out_pdp_conf.write_flat_file || -
|-
|Cancellation message ||N/a || DESP1 || GEN_CANC ||dp_edigen_out_pdp_conf.write_flat_file ||-
|-
|Order Details ||N/a || DESP1 || GEN_ORD || dp_edigen_out_pdp_conf.write_flat_file ||-
|-
|Generic Pick Message||N/a || DESP1 || GEN_PICK || dp_edigen_out_pdp_conf.write_flat_file ||-
|-
|Generic Hold Message ||N/a || DESP1 || GEN_HOLD || dp_edigen_out_pdp_conf.write_flat_file || Order at status 6 being placed on hold
|-
|Generic Pack Message || N/a || DESP1 || GEN_PACK || dp_edigen_out_pdp_conf.write_flat_file || Fully Packed Order
|-
|Generic Despatch|| N/a || DESP1 || GEN_DESP || dp_edigen_out_pdp_conf.write_flat_file ||-
|-
|Missing Universal Product Code (Barcode information, client specific)|| N/a || N/a || MISSING_UPC || dp_edigen_out_missing_upcs.write_flat_file || -
|-
|Outbound Purchase Ordering ||N/a || N/a || POP|| dp_edigen_out_pop.write_flat_file ||-
|-
|RDT Stock drip feed of updates|| N/a || N/a ||RDTSTK|| dp_rdt_stock_drip_feed.xf_monitor_send_message || -
|-
|}

 

==='''Stock Snapshot Formats'''===

 

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Generic Stock Snapshot ||SALES_BAL ||SALES GEN SALES_BAL ||User Definable || dp_edigen_out_st_bal.generate_data DP_EDIGEN_OUT_ST_BAL.write_flat_file
|| Requires two packages to be run in the sequence listed.
|-
|Stock Snapshot by Rotation ||SALES_BAL ||STROT_BAL ||User Definable || dp_edigen_out_strot_bal.write_file ||Requires only one package
|-
|Stock Snapshot at Detail Level ||SALES_BAL ||STKDTL_GEN STKDTL_WRT||User Definable ||dp_edigen_out_st_bal.write_flat_file_dtl dp_edigen_out_st_bal.write_flat_file_dtl ||Requires two packages to be run in the sequence listed.
|-
|Client Specific|| SALES_BAL ||STOCK_GEN STOCK_BAL ||User Definable || dp_edigen_out_st_bal.generate_data dp_edigen_out_st_bal.write_flat_file ||Requires two packages to be run in the sequence listed.
|-
|Client Specific, Serials || SERIAL ||STOCK_GEN STOCK_BAL || STOCK_BAL_NOV ||dp_edigen_out_st_bal.generate_data dp_edigen_out_st_bal.write_flat_file ||Requires two packages to be run in the sequence listed. Include the value 'NOV' in the format code field in XF Monitor
|-
|}

 

==='''Hard-coded EDI Inbound messages'''===
 

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Booking /Reference Number Update (Client Specific)|| BOOK || N/a || BOOK || dp_edigen_book_upd_load.read_file_format ||-
|-
|Hold/Release Process || HOLD_LOAD || N/a ||HOLD_LOAD || dp_edigen_hold_load.read_file_format || -
|-
|Pre-Advice or ASN || GEN_GRN || PRE_ADV || GEN_GRN || dp_edigen_pre_advice_load.read_file_format || -
|-
|Product Master Upload (Generic)|| PRODUCT || PROD_LOAD || User definable || dp_edigen_product_master_load.read_file_format || -
|-
|Sales Order Upload || GEN_SOP || SOP1 || SALES_ORDER || dp_edigen_sales_order_load.read_sales_order_file || '''VALUE''' must be GEN_SOP for standard order file uploads but for XML the system requires another value of SOP to be maintained in the EDI Common.-
|-
|Sales Kit Upload || User definable, though must be the same name as the Process command in XF Monitor
|| N/a || User definable, though must be the same name as in EDI Common|| dp_edigen_stk_kit_load.read_file_format ||-
|-
|}

 

==='''Configurable EDI Outbound messages'''===

 

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Adjustment Flow || N/a || N/a ||Same name as configurable process ||dp_conf_edi_out.produce_dyn_edi_files || -
|-
|Serial Adjustment Flow || SERIAL || N/a || Same name as configurable process ||dp_conf_edi_out.produce_dyn_edi_files || Same setup as above but include the EDI common name to produce serial numbering records.
|-
|}

 

==='''Configurable EDI Inbound Messages'''===

 

{| border="1"
!Description || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|SW Average Cost Upload || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor ||N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_edigen_sw_upd_load.read_file_format || -
|-
|Supplier Upload|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.read_edi_supp_file_format || -
|-
|Customer Upload ||User definable, though must be the same name as the Configuration process and the Process command in XF Monitor ||N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.read_edi_cust_file_format||Option to either upload or amend existing customer records
|-
|Inbound Hold/Release Process|| HOLD_LOAD || N/a || HOLD_LOAD || dp_edigen_hold_load.read_file_format|| -
|-
|Configurable Serial and Translation Number Upload || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor || N/a|| User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.med_seq_xfm || -
|-
|Stocks Base Selling Price|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor ||N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stk_base_sell_xfm || -
|-
|Stock Region and Sales territory (Client Specific)|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor||N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stock_region_xfm || -
|-
|Stock, UOM and Barcode information|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a || User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stk_uom_xfm || -
|-
|Stock Warehouse ||User definable, though must be the same name as the Configuration process and the Process command in XF Monitor || N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stock_warehouse_xfm || Putaway anchor points and replenishment levels
|-
|Updating of existing stock records|| User definable, though must be the same name as the Configuration process and the Process command in XF Monitor || N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stock_update_xfm || -
|-
|Pallet upload (WLE) || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.read_edi_wle || -
|-
|Pallet upload of held stock || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.wle_held_stock_xfm || -
|-
|Stock Master Upload ||User definable, though must be the same name as the Configuration process and the Process command in XF Monitor ||N/a||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.read_edi_prod_mast_format || -
|-
|Configurable stock warehouse || User definable, though must be the same name as the Configuration process and the Process command in XF Monitor|| N/a ||User definable, though must be the same name as the Configuration process and the EDI Common record|| dp_conf_edi_in.stock_locations_xfm || Putaway anchor points and replenishment levels
|-
|}

 

==='''Carrier EDI Messages'''===

 

{| border="1"
!Description || Direction || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Carrier Interface - Allocation ||Out||N/a||N/a||CICA||dp_cim_outbound.write_cioc_cica_file|| -
|-
|Carrier Interface - Order Confirmation||Out||N/a||N/a||CIOC||dp_cim_outbound.write_cioc_cica_file ||-
|-
|Carrier interface - Package details||Out|| N/a||N/a||CIPD||dp_cim_outbound.write_cipd_file || -
|-
|Manual cancelled orders ||Out||N/a||N/a||CANC||dp_cim_outbound.write_canc_file|| -
|-
|POD Confirmation (Ireland Specific)||Out||N/a||N/a ||PODC || dp_cim_outbound.write_podc_file || -
|-
|Carrier interface - Tracking Details||In||CITD||N/a||CITD||dp_cim_inbound.read_file_format ||-
|-
|Carrier Interface - Packing Information||In||CICD ||N/a||CICD|| dp_cim_inbound.read_cicd_file_format|| -
|-
|}

 

==='''Miscellaneous EDI Messages'''===

 

{| border="1"
!Description || Direction || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|DHL Labels EDI Generation||Out||DHEG|| N/a||DHEG ||dp_edigen_out_pack_label.write_dheg_file|| -
|-
|DHL Label Tracking Reference || In|| DHEG_UPL ||N/a || DHEG_UPL ||dp_edigen_dheg_upd_load.read_file_format || Will capture a tracking reference number and automatically create pack header records
|-
|}

 

==='''Local Processes'''===

 

{| border="1"
!Description || Direction || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|Script to automatically allocate all orders in the well ||Local||ALLOC||N/a||ALLOC||dp_edigen_alloc.xf_monitor_allocate|| -
|-
|If the order is held in Metapack as status ‘Manifested’, ‘Tracking’ or ‘Complete’, then the EDI process will initiate the WMS despatch process, down-dating the stock and updating the order as despatched. || Local || META_DESP || N/a ||META_DESP || dp_edigen_out_metapack.despatch_check ||Client specific see [[MetaPack]] for setup details
|}

 

==='''FTP Processes'''===

 

{| border="1"
!Description || Direction || EDI Common Name* || XFM Command Screen** || Process Code***|| Database Package Name || Notes
|-
|In bound FTP process||In||N/a || FTP_INBND ||User Definable||dp_process_control_xfm.ftp_inbound|| -
|-
|Out bound FTP process||Out|| N/a|| FTP_OUTB||User Definable||dp_process_control_xfm.ftp_outbound ||-
|-
|}

 

'''NB'''

'''EDI Common Name *''' As a general rule an EDI Common Name is required for all inbound messages but is not a requirement for outbound messages, though there are a couple of exceptions as noted above, i.e. Outbound Serial numbering functionality 

'''XF Command Screen (XFM0012)**''' These are all user definable, but depending on the system install there may be existing records, as noted above. 

'''Process Code (XFMonitor XFM0020)***''' As a rule outbound proceses require a specifed Process Code, the required values are listed above. 

 

=='''VALIDATION SCREENS'''==

For each inbound EDI flow, there is a validation screen. Errors are sequenced by a control number and are displayed in the validation screens where it is possible to rectify the data. Each of the validation screens will differ slightly dependent on the key fields for the message type being accessed.

Validation screens exist for the following processes: - 

:*GRN Pre- Advice 
:*Sales Order 
:*Product Master 
:*Inbound Holds 
:*Stock Reconciliation 
:*Order Management (Client Specific) 
:*Average Cost 
:*Stock Kit Validation 
:*Medical Sequence Validation (Client Specific)

The error records are held in the EDI transient tables until they are validated successfully and the relevant WMS record created at which point they are then cleared down.

==='''Validation Header Screen'''===

Taking the GRN Pre Advice Validation Screen as an example-

<center>[[Image:EDI-012.PNG]]</center>

First find the relevant Control Number (Control Numbers are only assigned to messages which have failed to upload)

There is then the option to either -

:'''Validate All''' This will re-submit the file to the system in an attempt to re-process it in its entirety . This is only relevant after all errors in the file have been addressed.
:'''Details''' will take you in to the body of the message allowing the user to identify the issue within the file and how to resolve it.

 

==='''Validation Detail Screen'''===

'''NB''' The number of tabs within the detail screen and the information displayed will depend on the type of the EDI flow being validated.

<center>[[Image:EDI-013.PNG]]</center>

The number of errors detected and their description will be displayed in the bottom portion of the form, these will then require resolving before the record can be validated and the record written to the WMS tables. Depending on the type of error this can be achieved by either adding or amending the data within the actual WMS system, or amending the data contained within the file by changing the values directly within the validation form.

Once the errors have been resolved it is then possible to re-submit the message, by selecting the '''Validate Button '''. This will only re-process a single record as a time, where if you select '''Main''' you will be returned to the top screen where the entire message can be re-submitted and validated.

 

=='''OUT BOUND RE-SEND SCREENS'''==

If messages have not been generated, have gone missing or require re-transmitting then it is possible to re-generate the message where it will wait for the next out bound ftp process.

Current resend screens: - 
:*Outbound GRN Confirmation Message 
:*Outbound Pack Confirmation Message 

==='''GRMK Re-send '''===

<center>[[Image:EDI-014.PNG]]</center>
Select the GRN number that requires resending, an LOV is available which will display all closed GRN’s.

Press the Resend button to generate the required message

===''' Packing Details Re-send '''===

<center>[[Image:EDI-015.PNG]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Owner ||Owner Code and Sub account id||Default from current user||Defined by the client
|-
|Select By ||Selection criteria for re-transmission||Orders or Despatch Date ||Defined by the client
|-
|Start Order No / End Order No||By Order Number||Order Number From / Order Number To||Defined by the client
|-
|Despatch Date From / Despatch Date To||By Despatch Date||Despatch Date From / Despatch To||Defined by the client
|}

 

=='''CONFIGURABLE EDI SETUP'''==

==='''Dynamic Inbound EDI Message Definition'''===

==='''System Registry (ULF0030)'''===

To produce log files to aid error resolution and to display tracking information within the XF Monitor Tracking page the following system registry setting must be entered at a Global Level ''''ConfEdiLogDisplay'''' with a value of ''''Y''''

<center>[[Image:EC-001.PNG | System Registry]]</center>

For a list of configurable EDI Messages see - [[#Configurable EDI Inbound Messages | Configurable EDI Inbound Messages ]]

 

=== '''XF Dynamic Inbound EDI Definition Screen (XFM0055)===

<center>[[Image:CON-001.PNG | Dynamic Inbund EDI Definition]]</center>

 

=='''Inbound Configurable Setup (Example)'''==

Following is a description on the steps required to setup an Inbound Configurable message for a Stock Warehouse update.

'''NB''' In the example below the process has been named '''STKWHSE''' the name is definable, but the same name must be used in the following screens -

* [[#EDI COMMON MAINTENANCE | EDI Common Maintenance (EDI0001)- Message Type ]]
* [[#XF Dynamic Inbound EDI Definition Screen (XFM0055)|Dynamic Inbound EDI Message Definition (XFM0055) - EDI Message ]]
* [[#XF MONITOR |XF Monitor (XFM0020) - Process Code ]]

See above for a detailed description of each of the forms.

'''EDI Common Record (EDI0001) '''

The common record for the message, is used to link the company code, warehouse, and owner to the records in the inbound file.

<center>[[Image:EC-002a.PNG | Common Record]]</center>

 

'''XF Command Screen (XFM0012) '''

The package id which is user definable and the database process that will validate and upload the file.

<center>[[Image:EC-003.PNG | Command Screen]]</center>

 

'''XF Re-sequence (XFM0011)'''

The linked process command that allows the system to run combined multiple packages if required.

<center>[[Image:EC-004.PNG | Re-Sequence]]</center>

 

'''XF Dynamic Inbound EDI Definition Screen (XFM0055) '''

The Configuration screen - where the EDI message name, type and individual message elements are specified.

* Ensure the EDI Message name is the same as the one entered in EDI Common.

<center>[[Image:EC-005.PNG | Configuration Screen]]</center>

 

'''Edit Level Data'''

Dependent on the chosen format type, ensure that the relevant Field No or Start Positions information is entered.

<center>[[Image:EC-006a.PNG | Configuration Screen - Data Elements ]]</center>

 

'''XF Monitor (XFM0020)'''

Create the XF Monitor record as detailed above.
'''NB''' Ensure the name created in the Process Code field is the same as created in EDI Common and the Dynamic Inbound EDI Definition screen.

<center>[[Image:EC-006.PNG | XF Monitor]]</center>

 

==='''Dynamic Outbound EDI Message Definition'''===

 

{| border="1"
!Field Name||Description ||
|-
|Adjustments || Positive and negative adjustments also hold and release
|-
|Inventory || Stock Balances
|-
|Orders || Order information
|-
|}

 

==='''Outbound EDI Message Definition'''===

Filename Construction is a template maintenance screen that allows outbound EDI files to be sent via ftp with a specific filename definition.

If the user defines a filename within the file template form (i.e. ‘IED40430.nnn’ in this case), the outbound ftp process will be altered to check for the existence of filenames of the type ‘IED40430*’. The filename string to search for will be constructed dynamically based on the user-defined elements entered for the template code in question. For this reason, the user will be expected to create template codes with at least one user-defined segment for filenames that are to be ftp’d.

<center>[[Image:EDI-016.PNG | File Construction]]</center>

{| border="1"
!Field Name||Description||Options||Generic Value
|-
|Template Id||Unique name of template||LOV provided for existing templates||Defined by the client
|-
|File String||an example of how the filename will look ||Built up by the system as values are entered in the detail part of the form and then refreshed ||Defined by the client
|-
|Example||Actual Example of file name|| Built up by the system as values are entered in the detail part of the form and then refreshed|| Defined by the client
|-
|Seq||Sequence number within file string|| ||Defined by the client
|-
|Key Type||Individual file element ||Options include- Hard Code, Date, Extension, Separator, Sequence, Time, User Defined||Defined by the client
|-
|Value|| Data element to be displayed || Depending on the key type selected their will either be a relevant LOV or the option of entering free text ||Defined by the client
|-
|}

 

{| border="1"
!Buttons || Description
|-
|Add Key Before||Insert key into string in front of the selected value
|-
|Add Key After ||Insert key into string after the selected value
|-
|Delete Key||Delete the key or element from the string
|-
|Move Up||Move the element up in the string
|-
|Move Down||Move the element down in the string
|-
|Refresh String||Will populate the File String and Example filds
|}

 

=='''FTP SETUP'''==

FTP Inbound and outbound is executed via a database package the same way as the standard EDI processes. In addition to the calling of the data base packages there is the requirement to set the I.P. address and login details of the remote machine.

It is possible to run the FTP processes standalone or as part of another process.

<center>[[Image:EDI-017.PNG | XF Re Sequence]]</center>

In the above example the process command DESP1 will run consecutively the DESP1 package which will generate the Despatch Messages, followed upon completion by the FTP_OUT_WM package which will the ftp process to which will attempt to place the Despatch files onto the remote machine.

<center>[[Image:EDI-018.PNG | FTP Process]]</center>

Set the transfer type to – FTP Transfer

 

=='''EDI Reprocessing'''==

This change will apply to inbound EDI flows only as it refers to the processing of items placed in the transient tables because of a process validation issue.

The current EDI flows that will be included in this change are: 

* Sales Order 
* Hold / Release 
* Pre - Advice 
* Stock Upload 

<center>[[Image:EDI-088a.PNG | EDI Reprocessing]]</center>

 

The aim is to reduce the amount of user intervention required when issues like record locking occur during the original data load.

A new screen will list the EDI flows that are setup for the current Warehouse / Owner combination. These EDI flows will appear regardless of whether they are currently running, the screen will display the same flows that can be seen in the XF Monitor screen.

Within this screen there will be option to select each flow. Once a flow is selected, the user must enter the number of times they want each load to be reprocessed and the frequency in minutes between each reprocess run.

If the load reaches the maximum number of re-tries, then it will no longer process automatically but will be available in the usual validation screens for users to validate / update manually.

There will be the option within the screen to start and stop the automatic reprocessing.
The users will have to start the process running initially, and then have the option to stop it if required. There will be an indicator on the screen to show if it is currently running.

If the emailing of EDI error reports is set up for the flow, the selected reports will be emailed to the stated users if the load reaches the maximum number of retries.

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>08/03/2011</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>LBW</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Emailing Reports from ORS

2015-08-13T10:05:57Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS2a.PNG | XF Command Screen]]</center>

<center>[[image:ORS-1.PNG | XF Re-Sequence]]</center>

Within the Oracle Reporting suite create the report

<center>[[image:ORS3.PNG | ORS Reporting]]</center>

Note the name of the report that you have created. I.e. 'RECEIPT_SPD'

<center>[[image:ORS4.PNG | ORS Reporting]]</center>

'''NB''' If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate''-n'' for historic dates or sysdate''+n'' for dates running into the future.

The example above will report from a date range of 10 days in the past and up to 10 days in the future from the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the ''’+’ ''

'''EDI – XF Monitor

'''<center>[[image:ORS5.PNG | XF Monitor ]]</center>

Set up a Job in XF Monitor similar to the above

Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

'''<center>[[image:ORS6.PNG | XF Monitor - Directory Parameters ]]</center>

Set up your directories as per normal -

'''<center>[[image:ORS7.PNG | XF Monitor - Email Parameters ]]</center>

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories on the server.

File:ORS7.PNG

2015-08-13T10:05:09Z

Lwinchester:

Emailing Reports from ORS

2015-08-13T10:04:53Z

Lwinchester:

File:ORS6.PNG

2015-08-13T10:02:49Z

Lwinchester:

Emailing Reports from ORS

2015-08-13T10:02:31Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS2a.PNG | XF Command Screen]]</center>

<center>[[image:ORS-1.PNG | XF Re-Sequence]]</center>

Within the Oracle Reporting suite create the report

<center>[[image:ORS3.PNG | ORS Reporting]]</center>

Note the name of the report that you have created. I.e. 'RECEIPT_SPD'

<center>[[image:ORS4.PNG | ORS Reporting]]</center>

'''NB''' If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate''-n'' for historic dates or sysdate''+n'' for dates running into the future.

The example above will report from a date range of 10 days in the past and up to 10 days in the future from the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the ''’+’ ''

'''EDI – XF Monitor

'''<center>[[image:ORS5.PNG | XF Monitor ]]</center>

Set up a Job in XF Monitor similar to the above

Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

'''<center>[[image:ORS6.PNG | XF Monitor - Parameters ]]</center>

Set up your directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

File:ORS5.PNG

2015-08-13T09:58:42Z

Lwinchester:

Emailing Reports from ORS

2015-08-13T09:58:26Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS2a.PNG | XF Command Screen]]</center>

<center>[[image:ORS-1.PNG | XF Re-Sequence]]</center>

Within the Oracle Reporting suite create the report

<center>[[image:ORS3.PNG | ORS Reporting]]</center>

Note the name of the report that you have created. I.e. 'RECEIPT_SPD'

<center>[[image:ORS4.PNG | ORS Reporting]]</center>

'''NB''' If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate''-n'' for historic dates or sysdate''+n'' for dates running into the future.

The example above will report from a date range of 10 days in the past and up to 10 days in the future from the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the ''’+’ ''

EDI – XF Monitor

<center>[[image:ORS5.PNG | XF Monitor ]]</center>

Set up a Job in XF Monitor similar to the above
Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

Set up you directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

File:ORS4.PNG

2015-08-13T09:55:41Z

Lwinchester:

Emailing Reports from ORS

2015-08-13T09:55:24Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS2a.PNG | XF Command Screen]]</center>

<center>[[image:ORS-1.PNG | XF Re-Sequence]]</center>

Within the Oracle Reporting suite create the report

<center>[[image:ORS3.PNG | ORS Reporting]]</center>

Note the name of the report that you have created. I.e. 'RECEIPT_SPD'

<center>[[image:ORS4.PNG | ORS Reporting]]</center>

'''NB''' If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate''-n'' for historic dates or sysdate''+n'' for dates running into the future.

The example above will report from a date range of 10 days in the past and up to 10 days in the future from the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the ''’+’ ''

EDI – XF Monitor

Set up a Job in XF Monitor similar to the above
Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

Set up you directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

Emailing Reports from ORS

2015-08-13T09:48:40Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS2a.PNG | XF Command Screen]]</center>

<center>[[image:ORS-1.PNG | XF Re-Sequence]]</center>

Within the Oracle Reporting suite create the report

<center>[[image:ORS3.PNG | ORS Reporting]]</center>

Note the name of the report that you have created. I.e. 'RECEIPT_SPD'

'''NB''' If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate''-n'' for historic dates or sysdate''+n'' for dates running into the future.

The example above will report from a date range of 10 days in the past and up to 10 days in the future from the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the ''’+’ ''

EDI – XF Monitor

Set up a Job in XF Monitor similar to the above
Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

Set up you directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

Emailing Reports from ORS

2015-08-13T09:47:15Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS2a.PNG | XF Command Screen]]</center>

<center>[[image:ORS-1.PNG | XF Re-Sequence]]</center>

Within the Oracle Reporting suite create the report

<center>[[image:ORS3.PNG | ORS Reporting]]</center>

Note the name of the report that you have created. I.e. 'RECEIPT_SPD'

'''NB''' If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate''-n'' for historic dates or sysdate''+n'' for dates running into the future.

The example above will report from a date range of 10 days in the past up to the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the ''’+’ ''

EDI – XF Monitor

Set up a Job in XF Monitor similar to the above
Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

Set up you directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

Emailing Reports from ORS

2015-08-13T09:46:26Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS2a.PNG | XF Command Screen]]</center>

<center>[[image:ORS-1.PNG | XF Re-Sequence]]</center>

Within the Oracle Reporting suite create the report

<center>[[image:ORS3.PNG | ORS Reporting]]</center>

Note the name of the report that you have created.

'''NB''' If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate''-n'' for historic dates or sysdate''+n'' for dates running into the future.

The example above will report from a date range of 10 days in the past up to the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the ''’+’ ''

EDI – XF Monitor

Set up a Job in XF Monitor similar to the above
Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

Set up you directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

File:ORS3.PNG

2015-08-13T09:43:42Z

Lwinchester:

Emailing Reports from ORS

2015-08-13T09:43:20Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS2a.PNG | XF Command Screen]]</center>

<center>[[image:ORS-1.PNG | XF Re-Sequence]]</center>

Within the Oracle Reporting suite create the report

<center>[[image:ORS3.PNG | ORS Reporting]]</center>

Note the name of the report that you have created.

NB If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate-n for historic dates or sysdate+n for dates running into the future.

The example above will report from a date range of 10 days in the past up to the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the’+’

EDI – XF Monitor

Set up a Job in XF Monitor similar to the above
Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

Set up you directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

File:ORS2a.PNG

2015-08-13T09:34:13Z

Lwinchester:

Emailing Reports from ORS

2015-08-13T09:31:34Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS2a.PNG | XF Command Screen]]</center>

<center>[[image:ORS-1.PNG | XF Re-Sequence]]</center>

Within the Oracle Reporting suite create the report

Note the name of the report that you have created.

NB If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate-n for historic dates or sysdate+n for dates running into the future.

The example above will report from a date range of 10 days in the past up to the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the’+’

EDI – XF Monitor

Set up a Job in XF Monitor similar to the above
Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

Set up you directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

File:ORS-1.PNG

2015-06-19T13:33:56Z

Lwinchester:

Emailing Reports from ORS

2015-06-19T13:33:41Z

Lwinchester:

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

<center>[[image:ORS-1.PNG | Location Maintenance]]</center>

Within the Oracle Reporting suite create the report

Note the name of the report that you have created.

NB If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate-n for historic dates or sysdate+n for dates running into the future.

The example above will report from a date range of 10 days in the past up to the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the’+’

EDI – XF Monitor

Set up a Job in XF Monitor similar to the above
Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

Set up you directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

Emailing Reports from ORS

2015-06-19T13:25:53Z

Lwinchester: New page: The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted) Within the Oracle Reporting suite create the report Note ...

The ORS package requires setting up in the EDI screens XF Command and XF Re-sequence, (this may already be inserted)

Within the Oracle Reporting suite create the report

Note the name of the report that you have created.

NB If you need to restrict the data reported by a data range, enter sysdate for current date or sysdate-n for historic dates or sysdate+n for dates running into the future.

The example above will report from a date range of 10 days in the past up to the date the report is automatically generated.

If the report is to extract data with parameters of a future date then must ensure you place the’+’

EDI – XF Monitor

Set up a Job in XF Monitor similar to the above
Ensure the Process Command is set to ORS and the ORS Report value is the name of your saved Data Extract Report
The Process Code can be called anything

Set up you directories as per normal -

Enter the name and email address of the recipients and then start the job.

When the job runs a copy of the report will emailed out to the addresses on the email list and a copy will be placed in the specified directories.

Main Page

2015-06-19T13:24:15Z

Lwinchester:

===WMS Quick Guides===
----
<ul>
<li>[[Quick Standing Data Maintenance]]</li>
<li>[[Quick WMS Processing]]</li>
</ul>

=== WMS Process Guides ===
----
<ul>
<li>[[EDI Setup and Processing]]</li>
<li>[[WMS Processing]]</li>
<li>[[Owner Charging and Invoice Processing (Incl Basic Setup)]]</li>
<li>[[WMS Enquiries]]</li>
<li>[[WMS Reports]]</li>
<li>[[Oracle Reporting Suite]]</li>

</ul>

=== WMS Setup Guides ===
----

<ul>

<li>[[System Navigation Guide]]</li>

<li>[[Company Set Up]]</li>
<li>[[Warehouse Set Up]]</li>
<li>[[Owner Set Up]]</li>
<li>[[Customer & Supplier Setup]]</li>
<li>[[Stock Set Up]]</li>

<li>[[Menu Maintenance]]</li>
<li>[[WMS/RDT Control Maintenance]]</li>
<li>[[Owner Invoicing]]</li>
<li>[[Auto Putaway Set Up]]</li>
<li>[[Automatic Replenishment]]</li>

<li>[[Emailing Reports from ORS]]</li>
<li>[[Creating default damage and quarantine locations]]</li>
<li>[[Confirming an alternative pallet at Pick Confirmation]]</li>
<li>[[How to Hold Stock]]</li>
<li>[[Dynamic Email Setup]]</li>
</ul>

<ul>
<li>[[FAQ]]</li>
</ul>

===WMS Client Specific===
------
<ul>
<li>[[MetaPack]]</li>
<li>[[Order Management Layer]]</li>
<li>[[NOMS]]</li>
</ul>

=== WMS Programs ===
----
<ul>
<li>[[Program Listing]]</li>
</ul>

=== Releases ===
----
<ul>
<li>[[Recent Releases]]</li>
</ul>

Stock Take

2013-11-25T10:59:33Z

Lwinchester: /* Stock Take Cleardown (WHS0547) */

=='''Introduction'''==

This document describes the required screens to be used in the stock take configuration and process. Other guides describe the set up of company, user, warehouse, stock codes etc.

This is a generic guide based on the version of the Calidus system at the time of writing.

It can also be used by clients to specify their specific data values to aid initial system set up as well as for future reference.

Note that fields marked ‘**’ are mandatory and are needed to ensure correct set up of the system.

=='''Overview'''==

Before a stock take cycle can commence, it must be confirmed that all the products affected by the stock take comply with the following:

• GRN's must be completed. (If the GRN is at Pre-Advice status then the stock take cycle can be started. 
• Orders are completed. '''(If there is stock with status with status ‘Allocated’, the stock take will fail. If orders have status ‘1’ Committed, the stock take cycle can be started).''' 
• No outstanding Movements. 
• The stock selected is not already under a stock take cycle. 
• No system holds

'''Supporting Reports'''

'''It is advisable that the following reports are run before a stock take cycle is generated.'''

WHS1968 - GRN's Not Putaway Report 
SOS1170 - Order Status Report 
WHS1545 - Outstanding Movements Report 
WHS1970 - Unconfirmed Movements Report 
SOS1170 - Held Stock Status Report (Check for pallets on system holds suce as 85 Down Date at despatch and 90 Awaiting Putaway) 

'''Process Flow'''

Stock Take Template (WHS0552)(Optional) 
Stock Take Cycle Generation (WHS0541) 
Stock Take Report (WHS0543) or Stock Take Error Report (WHS0541A) 
Stock Take Count Input (WHS0544) 
Stock Take Variance Report (WHS0546) 
Stock Take Update (WHS0544) 
Stock Take Cleardown (WHS0547) 

== Stock Take Template (WHS0522) ==

This screen allows entry of a complete Warehouse Stock Take Template. At each main prompt, you may choose '''No''', or return to take the default value of '''‘ALL’''' or you may choose '''Yes''', this will allow entry of specified values.

<center>[[Image:ST-01.png | Stock Take Template]]</center>

{| border="1"
| '''Field Name''' || '''Description ''' || '''Options'''
|-
|Template Code **||Name of template – this name can be used for all future stock takes. A template name only needs to be created once and the details within that template can then be used for all future stock takes ||4 character free text field
|-
|Description ||Description of template ||30 character free text field
|-
|Area ||Allows selection by area – Y or N – N will default to ‘All’ || Must have been created in area codes maintenance – LOV available
|-
|Location ||Allows selection by location code. If yes is selected then the option to choose location by Odd and Even as well as Range and Level is given ||Must have been created in location codes maintenance – LOV available
|-
|Owner ||Allows selection by Owner code – Y or N – N will default to ‘All’ ||Must have been created in owner maintenance – LOV available
|-
|Product ||Allows selection by Product code – Y or N – N will default to ‘All’ || Must have been created in stock maintenance – LOV available
|-
|Rotation ||Allows selection by System Rotation – Y or N – N will default to ‘All’ ||Must exist on the wms
|-
|Range ||Allows selection by Product Range – Y or N – N will default to ‘All’ ||Must have been set up in product class maintenance – LOV available
|-
|Class || Allows selection by Product Class – Y or N – N will default to ‘All’|| Must have been set up in product class maintenance – LOV available
|-
|Category ||Allows selection by Product Category ||Must have been set up in product class maintenance – LOV available
|-
|Group ||Allows selection by Product Group ||Must have been set up in product class maintenance – LOV available
|-
|Prod. Type ||Allows selection by Product Type || Must have been set up in product type maintenance – LOV available
|-
|ABC ||Allows selection by ABC code ||The ABC flag must be set up in stock maintenance
|-
|Location Type ||Allows selection by Location Type ||Must have been created in location types maintenance – LOV available
|-
|Disp. Batch ||Do you wish system rotation to be shown on the counting check sheet || Y or N – will default to N
|-
|Count Option ||Full, Partial or Exception – The type of count will determine what information is required in the input screen. ||Full = all information including batch and quantity
Partial = only quantities will be prompted for
Exception = the system will default all values including the system quantities. If no changes are made, the count will accept the qty on the wms.
|-
|Count Units ||Which UOM to count the stock in ||Cases only
Units only
Cases and Units (normal option)
|-
|Rep. Empty Locns ||Do you wish the check sheet to report empty locations as well as those occupied ||Y or N
|-
|Rep. Seq. ||The sequence in which the check sheet will report the products to be counted ||Location sequence or Product code sequence
|-
|Change Reason ||If a qty is changed, do you wish a reason code to be entered (this will put the product on hold) ||Y or N
|-
|Allow Sell by Date Changes. ||Allows sell by dates to be changed ||Y or N
|}

 

==Stock Take Cycle Generation (WHS0541)==

On entry to this screen the cursor will be in the Stock Take No field and the screen will be in enquiry mode. This allows previous generated stock take cycles to be viewed.

If the user stops the enquiry mode then a message “All movements must be completed before running stock take cycle generation” is given.

The user can then enter either a template code, which will bring up the stock take details of that code, or start a new definition using the same fields as the template program (details below)

See details of stock take template (WHS0552) for field information.

<center>[[Image:ST-002.png | Stock Take Cycle Generation]]</center>

On entry of the stock take details and date/time the Generate Cycle button can be used to start the stock take. A message “Cycle to be submitted to batch. OK to continue?” is given and the user can select yes or no, if no is selected then nothing happens.

If yes is selected then a new stock take number will be automatically generated and displayed. The generate cycle procedure will take a precise snapshot record of the status of the selected stock in the warehouse, as known to the system at the specified date and time as entered on the screen.

Please note, all selected stock is ‘held’ when the snapshot is taken and only released after the completion of the stock take. This completion is done when either the stock take is confirmed, or rejected at Stock Take Update.

==Stock Take Report (WHS0543) ==

This screen generates the stock take report print, for the manual count and input. If RF is being utilised then the stock take cycle will have been sent to the WCS ready to be accessed by an RF device.

<center>[[Image:ST-003.png | Stock Take Report]]</center>

 

{| border="1"
!Field Name||Description || Options
|-
|Stock Take Cycle From ||Start Cycle for the report|| Must be a valid stock take cycle – LOV available
|-
|Stock Take Cycle To ||End Cycle for the report ||Must be a valid stock take cycle – LOV available
|-
|Print On-Hand Quantities|| Do you wish the system quantities to be printed on the report ||Y or N
|-
|'''Buttons ''' || '''Description'''
|-
|Report ||Generates the counting check sheet
|}

 

The stock take sheets will print differently depending on which type of stock take is run, e.g. Full, Check, Partial or Exception. The type selected will be in the header of the report and the example below is of a 'Full' stock take.

 

<center>[[Image:ST-004.png | Full Stock Take Sheet]]</center>

If the cycle number is not present in the drop down list then the cycle has failed and the error report (WHS0541A) should be ran instead.

 

==Stock Take Error Report (WHS0541A)==

If a Stock Take cycle fails (i.e. status ‘Cannot Complete’), this report provides the user with an explanation of why it happened. It can be used to correct those items that have caused the stock take to fail. Displayed details include allocated quantities, outstanding movements, system holds and overlapping stock take cycles. The stock take cycle will then have to be cancelled in the Stock Take Cleardown screen.

<center>[[Image:ST-051.png | Stock Take Error]]</center>

 

{| border="1"

!Field Name || Description || Options
|-
|Stock Take Cycle No.|| The stock take cycle number that is to be reported on ||Must be a valid cycle – LOV available – note, the status of each cycle will be displayed
|-
|'''Buttons''' || '''Description'''
|-
|Report || Generates the report
|}

 

<center>[[Image:ST-005.png | Stock Take Error Report]]</center>

 

= Stock Take Updates =

The stock take updates comprise of inputting the stock details, updating these to the system
and then clearing down the stock take.

==Stock Take Count Input (WHS0544)==

This screen allows the manually counted stock to be input against the locations of the stock take. If the stock take type is by Exception then the figures in the Cases/Units field will be automatically set to the system generated figures, these can then be changed as and when needed.

<center>[[Image:ST-050.png | Stock Take Count Input]]</center>

 

{| border="1"
!Field Name || Description || Options
|-
|Stock Take Cycle **|| Allows the user to enter the cycle to be entered into the system||Must be a valid cycle – LOV available – note, the status of each cycle will be displayed
|-
|First Location ||A start location to input from ||Must be a valid location – leaving the field blank will default to ‘All’
|-
|Date|| Date and time of the stock take||Display Only
|-
|Status|| Status of the Stock take|| Display Only
|-
|Count Option|| Count option of the stock take ||Display Only
|-
|By|| Count units of the stock take|| Display Only
|-
|Employee|| Enables the entry of an employee code ||Must have been created in employee maintenance – LOV available
|-
!Buttons || Description
|-
|Location Enquiry||Allows the enquiry of a specific location
|-
|Add Stock || Allows the addition of stock
|-
|Confirm||Confirms the input details for the given stock take
|}

 

==New Data Input (WHS0542)==

This screen allows the addition of new stock within a given location and for a given owner and stock code. In addition to the ‘normal’ data required for new stock a valid Reason Code and Employee Code must also be entered for auditing purposes.

<center>[[Image:ST-052.png | New Data Input]]</center>

 

{| border="1"
!Field Name|| Description|| Options
|-
|Stock Take Cycle ** ||The stock take cycle number the stock is to be added to||Must be a valid cycle – LOV available – note, the status of each cycle will be displayed
|-
|Date ** || The date the stock has been added ||Must be a valid date/time
|-
|Status|| The status of the cycle|| Display only
|-
|Pallet|| Is the stock to be stored on a pallet ||Y or N – default is Y
|-
|Bonded|| Is the product bonded ||Y or N – default is N
|-
|Location **|| The location code the stock is to be added into ||Must have been created in location codes maintenance – LOV available
|-
|Owner **|| The owner code of the stock to be added ||Will default to current
|-
|Stock **|| The stock code to be added ||Must exist in stock code maintenance – LOV available
|-
|Type ||The location type|| Must exist in location types maintenance – LOV available
|-
|Pallet Id || Pallet Id of the line being added || If left blank the system will generate a pallet id
|-
|Manu Date || Manufacture date of the pallet || If required must be a valid date
|-
|Rotation No || System rotation number for the pallet || Only required if set against the stock code
|-
|Sell by Date|| The sell by date of the product ||Must be a valid date
|-
|Cust Rotation No|| The customer rotation (batch) of the product || Only required if set against the owner and stock code
|-
|Reason Code|| If required, the reason code of the entry – will put the stock on hold||Must exist in reason codes maintenance – LOV available
|-
|Layers ||The no of layers entered (not migrated) ||N/A
|-
|Cases ||The quantity of cases to be added|| 0 -99999
|-
|Units ||The quantity of units to be added ||0 – 99999
|-
|Weight ||The weight of the product to be added ||0 – 99999.99
|-
|UOM ||The unit of measure the product is held in|| Dependant on the available stock UOM
|-
|UOS|| The unit of sale of the product ||i.e. weight, volume = set in stock UOM in stock maintenance
|-
|}

 

==Stock Take Variance Report (WHS0546==

This is also called the ‘Discrepancy report’ and will show the details of all locations for a specific stock take cycle. In particular it will show ‘on hand’ quantities (as recorded by the ‘snapshot’ taken in the ‘Stock Take Cycle Generation’ Procedure), the stock take quantities, quantity variances, the checker’s ID and date/time that the location was checked. Grand totals by owner and for each stock code are also printed.

'''NB. The On-Hand, Entered and Variance quantities will not be shown if the Counting units option for the stock take is set to Units only.'''

<center>[[Image:ST-053.png | Stock Take Variance]]</center>

 

{| border="1"
! Field Name || Description|| Options
|-
|Stock Cycle From No. **|| The starting stock take cycle number to report from|| Must be a valid cycle – LOV available – note, the status of each cycle will be displayed
|-
|Stock Cycle To No. ** ||The end stock take cycle number to report from|| Must be a valid cycle – LOV available – note, the status of each cycle will be displayed
|-
|Print Detail, Summary or Both ||Enables the printing of a detail report or just summary ||Detail, Summary, Both
|-
|Select Owner|| Allows printing to be by specific owner (takes current)|| Y or N
|-
!Buttons || Description
|-
|Report|| Generates the report
|}

 

'''Examples of Variance Reports'''

 

<center>[[Image:ST-054a.png | Stock Take Variance Report Detail]]</center>

<center>[[Image:ST-055.png | Stock Take Variance Report Summary]]</center>

 

==Stock Take Update (WHS0545)==

Each stock take cycle can be rechecked until the stock take supervisor is satisfied that the stock take is correct. At this time, the update screen can be used to accept or reject the stock take and revise the system details accordingly.

If a stock take count number is entered, only those discrepancies accepted by that stock count number would then be updated. This then allows a phased update of remaining discrepancies over several re-counts. Those pallets that are accepted are released for further processing within the warehouse operation.

<center>[[Image:ST-056.png | Stock Take Update]]</center>

{| border="1"
!Field Name || Description ||Options
|-
|Stock Take No. ||Stock Take Number ||Must be a valid cycle – LOV available – note, the status of each cycle will be displayed
|-
|Con/Rej/Part ||Type of Stock Take update|| ‘Con’ - This is used for a full and final confirmation of all stock take amendments made on this cycle number. When ‘Run Stock Take’ is pressed the updates are committed and audit records of type STTK are created to reflect the quantities , plus or minus, of each pallet of each stock item that has been altered or added This will always produce a Stock take variance report
‘Rej’ - This is used to totally reject the selected stock take cycle; no change will be made to the stock amounts. No audits records produced 
‘Part’ - This removes the temporary stock take records that have both old and new values that are equal. It leaves just the records that have been altered / added to be processed. If further stock checks are required, return to the Stock Take Count Input screen for further adjustments. ***
The user must eventually either Confirm or Reject the stock take cycle. Confirm is the only option that finally updates/adds location records and audit records
|-
|Run Date ||Date that the update is run|| Must be a valid date
|-
|Time|| Time that the update is run|| Must be a valid time HH:MM
|-
!Buttons || Description
|-
|Run Stock Take|| Runs the Stock Take Update
|-
|}

 

==Stock Take Cleardown (WHS0547)==

The stock take Cleardown is completed after the stock take cycle has been updated.

<center>[[Image:ST-057.png | Stock Take Cleardown]]</center>

 

{| border="1"
!Field Name || Description|| Options
|-
|Stock Take No. ||The stock take cycle number to be cleared down ||Must be a valid cycle – LOV available – note, the status of each cycle will be displayed
|-
|Run Date||Date that the update is run. ||Must be a valid date – will default to today
|-
|Time|| Time that the update is run. ||Must be a valid time HH:MM
|-
!Buttons || Description
|-
|Cleardown|| Initiates the stock take Cleardown.
|}

 

'''NB The Cleardown can be done on a range of Stock Take Cycles. Entry of the number of the highest cycle that is not at status pending, and all cycles at status rejected, confirmed and cannot complete will be deleted. Any cycles at status pending will be unaffected by the Cleardown.'''

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>08/03/2011</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>LBW</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Owner Charging and Invoice Processing (Incl Basic Setup)

2013-09-17T14:56:18Z

Lwinchester: /* Miscellanous Charges */

== Introduction ==
This is an Owner Maintenance and process guide based on the assumption that the company set up has been correctly implemented and maintained. For information on how to setup and maintain the company refer to the main user guide for Owner Invoicing which provides a more in depth explanation of the screens and requirements.

This document describes the screens that are required to set up the data for the charging of owners for warehouse services provided and the invoice generation process.

This guide is based on the current 7.70 version of the WMS system at the time of writing.

== Pre-Requisite ==

* Ensure that the flag SOP Invoicing is set to 'Y' 
* For Rent charges to be calculated and generated, the End of Day Process needs to be running.

== Functionality ==
There are three main mechanisms for charging available at owner level, these include the Receipt and Despatch process and also Rent for the time period to date. In addition it is also possible to apply manual or miscellaneous charges as required.

Once charges have been applied it is then possible to generate Invoices for a time cycle or period.

== Owner Setup ==
The Owner record requires a number of parameters to be set to enable the charging and invoicing functionality.

=== Invoice Address ===
For the owner Invoice Address to appear on the Invoice Note -

[[Image:OCI-001.png | Invoice Address]]

Within owner maintenance / Main Tab ensure that there is a linked Customer code, in the example there will be a customer id of X-001.

[[Image:OCI_002.PNG | Customer Invoice Address]]

Within Customer Wizard ensure that there is a INV (Invoice Type) address

=== SOP C/H ===
'''Within Owner Maintenance / SOP Charging - Ensure''' the SOP Invoice Required Flag is set to 'Yes'

<center>[[Image:OCI_003.png | Customer Invoice Address ]]</center>

By setting the SOP Invoice flag this will enable the production of Invoices

=== Charging ===
'''Within Owner Maintenance / Charging '''

<center>[[Image: OCI_004.png | Charging Parameters]]</center>

The Charging Tab controls how the owner/client will be charged - ''Refer to Owner Invoicing Guide for a full description of each of the fields ''

'''Required values - '''

In the Owner Maintenance, the charging tab must be filled in.

* The Invoice Type must be set to Invoice Cycle
* The Rent Mode must be set. For Rent you need to set up the invoice cycles which determine whether rent is charged in weekly, fortnightly, monthly cycles etc.

'''NB:''' Ensure that if charging for Orders that the level (Either Header or Well) match the level for the Charge.

== Rate Table ==
The Rate table is used to hold the price to be applied to any transaction which can be charged and then invoiced for.

<center>[[Image: OCI_006.PNG | Rate Table ]]</center>

Rate table - In the example above it is setup to charge 10p per case for a transaction

'''Key field Information - '''

'''Rate Id - '''Unique identifier''' '''

'''Date From / To - '''Effective date range that the Rate will be applied for

'''Min / Max charges - '''Optional lower and upper ranges that charges can be applied

'''Table Type - ''' what the charge is being applied against (Pallet, Case, Unit etc)

'''Breakpoint - '''Normally set to Standard

'''Variable Rate Calculation''' -

The detail part of the form can in effect be split into two parts, the left hand side will control breakpoints if set and will have precedent over Unit Qty and Rate settings.

== Charge Codes ==
Charge codes are used to track the revenue and cost of a transaction, each code will have an associated Rate Id for the calculation of the charge value, or can use an 'ad-hoc rate' when entered manually.

Each charge code can be applicable to a particular BUSINESS TYPE, i.e. Receipt, Despatch, Rent or miscellaneous for general use.

Each charge code can be applicable to a specific level within the Invoicing processes - namely COMPANY / WAREHOUSE / STOCKIST / STOCK or PRODUCT TYPE.

All active rate codes revolve around or are linked to a charge code for them to be effective.

<center>[[Image:OCI-007.png | Charge Code Table]]</center>

In the example above, a Despatch Charge will be applied to all stock despatched for the owner NTO from the warehouse NTW regardless of its Product type. The automatic cost that will be generated will be taken from the settings held against the Rate id 'D1'.

'''Key Field Information -'''

'''Charge Code''' - Unique Code

'''Descriptions''' - Meaningful description of the charge code

'''Rate Id''' - Valid rate id, supported by a LOV

'''Business Types - '''Valid types for the WMS are â€“ '''DES''' (Despatch) '''REC''' (Receipt) '''CYC''' (Rent) '''MIS''' (Miscellaneous)

'''Warehouse''' - Valid warehouse id, or can enter â€˜+â€™ sign for all warehouses

'''Owner - '''Valid owner id or can enter + sign for all owners

'''Product - '''Valid stock code or can enter + sign for all stock codes

'''Product Type''' - Valid stock code or can enter + sign for all stock codes

'''Charge Type RCB''' - Revenue, Cost or both (For charging it will always be revenue)

'''Charge Type - '''Set to Handling for despatch and receipt charges

'''Revenue Acc - '''Must enter a value, though at present does not link to any accounts package

'''Calculation Option - '''Defines how the system will generate charges,''' '''as a guide miscellaneous charges are normally set as Manual, Rent charges are set as Automatic and Receipt and Despatch charges are set as semi-automatic.

== Process ==
=== Goods Receipt ===
'''Rate Code'''

<center>[[Image: OCI_008.png | GRN Rate Code]]</center>

'''Key Field Information '''

The above rate code has been set to charge 10p per case for a transaction and will run from the 29th July to the 15th December.

Table Type - Case 
Multiplier - Case 
Unit Qty - 1 
Rate - 0.1000 

'''Charge Code '''

<center>[[Image:OCI_009.png | Charge Code Table]]</center>

Rate id - A0010
Business Type - REC (Charges generated at Receipt)
To be set against warehouse id XX1, Owner XXA, and any stock code that has a Product Type of 1
Charge Type RCB - Revenue
Charge Type - Handling
Level Indicator - Header

'''GRN Receipt -'''Stock is advised and receipted into the warehouse as per the standard process. Upon goods receipt confirmation the system will check all available charge codes and rate table to see what charges can be calculated and applied.

<center>[[Image:OCI_010.png | GRN Receipt]]</center>

A pallet is receipted into the warehouse for 10 cases -

<center>[[Image:OCI_011.png | GRN Handling Charges]]</center>

Upon Goods Receipt Confirmation a charge is automatically generated and the above screen is displayed.

The automatic pricing module has found the Charge Code A1, and the linked Rate Id A0010. The quantity received was 10 cases at 10p per case, multiplying out at a value of £1.

=== Despatch Confirmation ===
<center>[[Image:OCI_012.png | Despatch Charges]]</center>

A new charge code is created for the despatch process, for it to be used to generate Despatch Charges ensure that the Rate Id is current, (the rate id can be used for multiple charges) and that the Business Type is set to 'DES'.

'''Note: '''The charge code 'D1' also has a minimum charge of £3.50, meaning that if the total despatch charge is calculated to a cost of less than this minimum value set then it will automatically be rounded up to £3.50.

'''Despatch Confirmation''' - An order is placed for stock totalling of 12 cases, upon successful despatch confirmation the Detail handling Charges screen is displayed (See below)

[[Image:OCI_013.png | Despatch Confirmation]]

The automatic pricing module has fond the charge 'D1' which matches the selection criteria of a despatch transaction for the Warehouse XX1 and Owner XXA. Product Code and Type are not part of the selection. A Rate ID of A0010 is linked to the charge code

[[Image:OCI_014.png | Despatch Handling Charges]]

The final rate calculated is £3.50 as the 12 cases at 10p/case would come to a charge of £1.20 which is less than the minimum value.

== Miscellaneous Charges ==
It is also possible to add Miscellaneous or ad hoc charges to either a receipt or despacht transaction , for example if some extra work is involved that will incurr a cost that can be passed on to the owner, such as re-labelling or re stacking on new pallets.

[[Image:OCI_015.png | Rate table for miscellanous charges ]]

A rate table is created for the task; in this example 5p per case for re-labelling (an existing rate table could be used if already existing)

[[Image:OCI_016.png | Charge code for miscellaneous charges ]]

A Charge code is created to be applied for the task - 

'''Key Fields - ''' 
Business Type - MIS for miscellaneous charging 
Charge Type RCB - Revenue 
Charge Type - Miscellaneous 
Calculation Option - Must be set to '''Manual ''' 
Level Indicator - Header 

Upon despatch confirmation the Detail handling charges screen will be displayed and display any charges calculated. It is now possible to insert a manual charge for one off tasks -

[[Image:OCI_017.png | xxx]]

[[Image:OCI_018.png | xxx]]

Insert a new line and then call the LOV to select a relevant charge

[[Image:OCI_019.png | xxx]]

The value is calculated by multiplying the quantity against the value (15*0.05 to give 75p)

It is also possible to run off a Miscellaneous Invoice if required by ticking the selection box and then running the Miscellaneous Invoice button.

In addition it is also possible to apply miscellaneous charges directly to the customer by selecting the Customer Radio button in the header part of the screen.

== Rent Charges ==
If the owner is set to generate initial rent, then rent will be automatically generated from the receipt date up to, and including, the end of the fiscal cycle the receipt date is within (for the rent invoice cycle). The initial rent is generated as a background process with no visible affect on the goods receipt process.

Three different rent calculations are supported:

1 - The average of the goods in the warehouse at the start and the end of the period. 
2 - Goods in the warehouse at the start of the period plus all goods received during the period. 
3 - Goods in the warehouse at the end of the period plus all goods despatched during the period. 

* Rent charges are generated manually from a parameter screen for invoice cycle periods. (See below Owner maintenance, Charging tab)
* The invoices are created manually from a parameter screen for the current invoice cycle. All un-invoiced owner charges, rent, receipt and despatch, are generated onto an invoice.

[[Image:OCI_020ac.png | Owner Maintenance]]

'''Key Field Information - ''' 

Rent Mode - The point at which Rent will be generated 
Rent Cycle - Time Period or window for charging rent 
Free Days - Number of free days before rent will be charged 

[[Image:OCI_021a.png | Rate Table Maintenance]]

A Rate id is set up the Rent charges, in this example we will be charging 20p per case per day for the duration of the rent cycle.

[[Image:NEW_999.png | Charge Codes Table]]

A cycle code is now created to be applied for Rent charges -

'''Key Field Information - ''' 

Business Type - CYC 
Charge Type RCB - Revenue 
Charge Type - Rent 
Calculation Option - Automatic 
Level Indicator - Detail 

=== Generating Rent ===
For the system to calculate and generate rent charges, enter the required client the up to date and select Start Transactions.

[[Image:OCI_023.png | xxx]]

== Invoice Production ==
The invoice Production is a two part process, first the Invoice Preparation is required to be run -

[[Image:OCI-025.png | Invoice Preperation]]

Then the actual Invoice can be generated -

[[Image:OCI-026.png | Invoice Print]]

Invoice is generated -

[[Image:OCI-027r.png | Invoice Report]]

 

== Additional Rate Table Example ==

[[Image:OCI_040.png | Rate table with breakpoints]]

In addition to charging for a fixed quantity it is also possible to set breakpoints. In the example above if the received quantity if for 9 cases then a fixed rate of £7.50 would be generated. If 19 cases where generated then a fixed rate of £5.50 would be generated.

[[Image:OCI_041.png | Detail handling charges]]

In the above example 14 cases where receipted and a fixed charge of £6.5 was generated.

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>21/09/2011</center>
| <center>Completed</center>
| <center>User Guide</center>
| <center>LBW</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

File:1Stage 020.png

2013-08-06T14:04:35Z

Lwinchester:

Confirming an alternative pallet at Pick Confirmation

2013-05-15T13:27:22Z

Lwinchester: /* Holding Stock */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

=='''PROCESS'''==

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

Now save the record. A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

The pallet is now zeroed, meaning it cannot be allocated to future orders.

 

==='''Holding Stock'''===

If operationally the stock should not be adjusted and removed from the system the alternative is to place the pallet on hold with an applicable reason code, this will prevent the pallet and stock being allocated to the next order that is placed.

[[How to Hold Stock]]

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-15T13:27:00Z

Lwinchester: /* Holding Stock */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

=='''PROCESS'''==

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

Now save the record. A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

The pallet is now zeroed, meaning it cannot be allocated to future orders.

 

==='''Holding Stock'''===

If operationally the stock should not be adjusted and removed from the system the alternative is to place the place the pallet on hold with an applicable reason code, this will prevent the pallet and stock being allocated to the next order that is placed.

[[How to Hold Stock]]

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-15T13:24:51Z

Lwinchester: /* Holding Stock */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

=='''PROCESS'''==

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

Now save the record. A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

The pallet is now zeroed, meaning it cannot be allocated to future orders.

 

==='''Holding Stock'''===

[[How to Hold Stock]]

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-15T13:24:26Z

Lwinchester: /* Holding Stock */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

=='''PROCESS'''==

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

Now save the record. A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

The pallet is now zeroed, meaning it cannot be allocated to future orders.

 

==='''Holding Stock'''===

[[How to hold Stock]]

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-15T13:23:49Z

Lwinchester: /* Document History */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

=='''PROCESS'''==

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

Now save the record. A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

The pallet is now zeroed, meaning it cannot be allocated to future orders.

 

==='''Holding Stock'''===

[[Holding Stock]]

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-15T13:20:03Z

Lwinchester: /* Process */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

=='''PROCESS'''==

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

Now save the record. A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

The pallet is now zeroed, meaning it cannot be allocated to future orders.

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-15T13:19:45Z

Lwinchester: /* Process */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

=='''Process'''==

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

Now save the record. A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

The pallet is now zeroed, meaning it cannot be allocated to future orders.

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-15T13:19:09Z

Lwinchester: /* Stock Adjustment Screen */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

Now save the record. A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

The pallet is now zeroed, meaning it cannot be allocated to future orders.

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-15T13:17:56Z

Lwinchester: /* Stock Adjustment Screen */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

Now save the record. A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

The pallet is zeroed, meaning it cannot be allocated to future orders.

 

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T16:03:54Z

Lwinchester: /* Stock Adjustment Screen */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code and press Find. This will show you all the pallets for this stock code in the warehouse:

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T16:03:23Z

Lwinchester: /* Stock Adjustment Screen */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T16:03:03Z

Lwinchester: /* Stock Adjustment Screen */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustment Screen]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | Adjustment Screen]]</center>

 

<center>[[Image:papc014.png | Adjustment Screen]]</center>

 

<center>[[Image:papc015.png | Adjustment Screen]]</center>

 

<center>[[Image:papc016.png | Adjustment Screen]]</center>

 

<center>[[Image:papc017.png | Adjustment Screen]]</center>

 

<center>[[Image:papc018.png | Adjustment Screen]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T15:48:42Z

Lwinchester: /* Stock Adjustment Screen */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

 

<center>[[Image:papc011.png | Adjustments]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | vvvvvv]]</center>

 

<center>[[Image:papc014.png | vvvvvv]]</center>

 

<center>[[Image:papc015.png | vvvvvv]]</center>

 

<center>[[Image:papc016.png | vvvvvv]]</center>

 

<center>[[Image:papc017.png | vvvvvv]]</center>

 

<center>[[Image:papc018.png | vvvvvv]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T15:48:30Z

Lwinchester: /* Stock Adjustment Screen */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

 

To prevent the problem pallet being allocated to another order the stock must either be placed on hold or adjusted off the system.

<center>[[Image:papc011.png | Adjustments]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | vvvvvv]]</center>

 

<center>[[Image:papc014.png | vvvvvv]]</center>

 

<center>[[Image:papc015.png | vvvvvv]]</center>

 

<center>[[Image:papc016.png | vvvvvv]]</center>

 

<center>[[Image:papc017.png | vvvvvv]]</center>

 

<center>[[Image:papc018.png | vvvvvv]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T15:46:57Z

Lwinchester: /* Process */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

==='''Stock Adjustment Screen'''===

<center>[[Image:papc011.png | Adjustments]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | vvvvvv]]</center>

 

<center>[[Image:papc014.png | vvvvvv]]</center>

 

<center>[[Image:papc015.png | vvvvvv]]</center>

 

<center>[[Image:papc016.png | vvvvvv]]</center>

 

<center>[[Image:papc017.png | vvvvvv]]</center>

 

<center>[[Image:papc018.png | vvvvvv]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T15:46:16Z

Lwinchester: /* Run the Stock adjustments screen */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

<center>[[Image:papc011.png | Adjustments]]</center>

 

Run the Stock adjustments screen

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | vvvvvv]]</center>

 

<center>[[Image:papc014.png | vvvvvv]]</center>

 

<center>[[Image:papc015.png | vvvvvv]]</center>

 

<center>[[Image:papc016.png | vvvvvv]]</center>

 

<center>[[Image:papc017.png | vvvvvv]]</center>

 

<center>[[Image:papc018.png | vvvvvv]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T15:44:26Z

Lwinchester: /* Process */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quantity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

<center>[[Image:papc011.png | Adjustments]]</center>

 

===Run the Stock adjustments screen===

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | vvvvvv]]</center>

 

<center>[[Image:papc014.png | vvvvvv]]</center>

 

<center>[[Image:papc015.png | vvvvvv]]</center>

 

<center>[[Image:papc016.png | vvvvvv]]</center>

 

<center>[[Image:papc017.png | vvvvvv]]</center>

 

<center>[[Image:papc018.png | vvvvvv]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T15:43:53Z

Lwinchester: /* Process */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0, the pick quantity originally matched the allocated quanity.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

<center>[[Image:papc011.png | Adjustments]]</center>

 

===Run the Stock adjustments screen===

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | vvvvvv]]</center>

 

<center>[[Image:papc014.png | vvvvvv]]</center>

 

<center>[[Image:papc015.png | vvvvvv]]</center>

 

<center>[[Image:papc016.png | vvvvvv]]</center>

 

<center>[[Image:papc017.png | vvvvvv]]</center>

 

<center>[[Image:papc018.png | vvvvvv]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T15:42:08Z

Lwinchester: /* Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

<center>[[Image:papc011.png | Adjustments]]</center>

 

===Run the Stock adjustments screen===

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | vvvvvv]]</center>

 

<center>[[Image:papc014.png | vvvvvv]]</center>

 

<center>[[Image:papc015.png | vvvvvv]]</center>

 

<center>[[Image:papc016.png | vvvvvv]]</center>

 

<center>[[Image:papc017.png | vvvvvv]]</center>

 

<center>[[Image:papc018.png | vvvvvv]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T15:41:41Z

Lwinchester: /* Process */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet has been damaged. We need to use pallet 38894 in its place. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

==Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button==

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

<center>[[Image:papc011.png | Adjustments]]</center>

 

===Run the Stock adjustments screen===

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | vvvvvv]]</center>

 

<center>[[Image:papc014.png | vvvvvv]]</center>

 

<center>[[Image:papc015.png | vvvvvv]]</center>

 

<center>[[Image:papc016.png | vvvvvv]]</center>

 

<center>[[Image:papc017.png | vvvvvv]]</center>

 

<center>[[Image:papc018.png | vvvvvv]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Confirming an alternative pallet at Pick Confirmation

2013-05-14T15:15:21Z

Lwinchester: /* Process */

=='''INTRODUCTION'''==

Due to circumstances such as stock being damaged or inaccessible for whatever reason there will be a requirement to either short the order is send an alternative pallet out in its place.

==='''Process'''===

To change the original pallet and to amend on an alternative -
: 1. The order must first be called up in Pick Confirmation WHS1714
: 2. Drill down into the line details to find the pallet that requires removing from the order
: 3. Zero the original pallet
: 4. Amend a new pallet in its place
: 5. Either adjust the original pallet off the system or place on hold to stop it being allocated to another order

'''Example -'''
The order allocated against pallet 38893, but that pallet had already been picked for a different order. We need to use pallet 38894. How do we handle this in the Calidus-WMS system?

 

<center>[[Image:papc001.png | Pick Confirmation, Header ]]</center>

 

==Find the order in the pick confirmation screen, enter the picker and checker info, then press Options button==

<center>[[Image:papc002.png | Pick Confirmation, Header ]]</center>

 

Select the Detail Screen option

 

<center>[[Image:papc003.png | Pick Confirmation, Detail]]</center>

 

There was no pallet 38893 in location A0/01/2, so we set the pick quantity to 0.

 

<center>[[Image:papc004.png | Pick Confirmation, Detail]]</center>

 

Enter a reason code. A pop-up list of values is available.

 

<center>[[Image:papc005.png | Pick Confirmation, Detail]]</center>

 

Click on the next line, the line number and stockist code auto-populate.

 

<center>[[Image:papc006.png | Pick Confirmation, Detail]]</center>

 

Enter the stock code, and the pallet id which was actually picked. The location/rotation/etc should default in for you.

 

<center>[[Image:papc007.png | Pick Confirmation, Detail]]</center>

 

Enter the picked quantity for this pallet, normally the same as the allocated figure on the zeroed line.

 

<center>[[Image:papc008.png | Pick Confirmation, Detail]]</center>

 

Again you will need to enter a reason code.

 

<center>[[Image:papc009.png | Pick Confirmation, Detail]]</center>

 

Once all the lines in the detail screen are correct, press Confirm.

 

<center>[[Image:papc010.png | Pick Confirmation, Header ]]</center>

 

You will be returned to the main screen. If all the detail pages are confirmed now, the whole order will be marked as pick confirmed.

The pick confirmation screen has done the following: 
:* Confirmed zero cases from pallet 38893, so it is no longer used on this order
:* Allocated 10 cases from pallet 38894 so it cannot be used by a different order.
:* Pick confirmed the order ready for despatch.

Now you need to go into the stock adjustment screen and zero the original pallet:

 

<center>[[Image:papc011.png | Adjustments]]</center>

 

===Run the Stock adjustments screen===

 
<center>[[Image:papc012 .png | Adjustment Screen]]</center>

 

Enter the stock code and your employee code…

 

<center>[[Image:papc013.png | vvvvvv]]</center>

 

<center>[[Image:papc014.png | vvvvvv]]</center>

 

<center>[[Image:papc015.png | vvvvvv]]</center>

 

<center>[[Image:papc016.png | vvvvvv]]</center>

 

<center>[[Image:papc017.png | vvvvvv]]</center>

 

<center>[[Image:papc018.png | vvvvvv]]</center>

 

..and press Find. This will show you all the pallets for this stock code in the warehouse:

Scroll to the pallet you want to change.

This pallet is listed as having 10 cases. To zero it, type -10 in the top left box. This will reduce the quantity by 10 cases.

Click on the reason code field and enter the appropriate reason code. A pop-up list is available.

Now save the record.

A pop-up window will allow you to enter some notes about why the pallet quantities are being changed.
Save any comment and exit this screen.

The pallet is zeroed, meaning it cannot be allocated to future orders.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>13/05/2013</center>
| <center>In Progress</center>
| <center>User Guide</center>
| <center>JGP</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied