View source for EDI Setup and Processing

:

==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)           <br>
:EDI Common (EDI0001)                        <br>
:EDI Last Numbers (INS7050)                  <br>



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)                       <br>
:XF Resequence (XFM0011)                    <br>
:XF Monitor (XFM0020)                       <br>

==GENERAL EDI CODES – HEADER LEVEL==
{{:PFS0260 EDI}}			
			
==OWNER MAINTENANCE - EDI Inbound & Outbound (Client Specific EDI Configuration)==			



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



<center>[[File:Own-007.PNG|800x800px]]</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:'''                                                                                        <br>
: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.


<br>



<center>[[File:Own-003.PNG|800px]]</center>


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


<br>


<center>[[File:Own-008.PNG|800px]]</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"

<br>

==EDI LAST NUMBERS==
{{:INS7050}} 

==EDI COMMON MAINTENANCE==
{{:EDI0001}}

==EDI XF COMMAND ==
{{:XFM0012}}

==XF RESEQUENCE==
{{:XFM0011}}

==XF MONITOR==
{{:XFM0020}}


==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.

<br>

===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>

{| class="wikitable" 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
|}

<br>

==CONFIGURABLE EDI SETUP==
===Dynamic Inbound EDI Message Definition===

===System Registry (ULF0030)===
{{:ULF0030 EDI Setup}}


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

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

==Inbound Configurable Setup (Example)==



The 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) '''

{{:EDI0001}}


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

{{:XFM0012}}


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

{{:XFM0011}}


'''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===

{| class="wikitable" 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>

{| class="wikitable" 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.