Dairy FarmersInformation Services

e*Gate Handover Manualfor IBM GSA

Issue Date: 30th November, 2004

Version 1.3

1. CURRENT INTERFACES......................................................................................................................3

2. E*GATE MONITOR.............................................................................................................................4

3. SQL MESSAGE VISIBILITY..............................................................................................................9

4. INTERFACE MONITORING UTILITY..........................................................................................15

5. TROUBLESHOOTING.......................................................................................................................18

IA Monitoring Utility.................................................................................................................................18E*Gate Monitor..........................................................................................................................................19

7. NORMAL SHUTDOWN.....................................................................................................................21

6.1 Shutting Down the Inbound eWays (eGate on DFLID12).............................................................216.2 Confirm Outbound Queues in eGate (DFLID12) are Empty.........................................................226.3 Shutdown All Other Modules and Programs..................................................................................236.4 Restart of eGate DFLID12 Server..................................................................................................24APPENDIX A............................................................................................................................................26APPENDIX B.............................................................................................................................................28APPENDIX C.............................................................................................................................................31APPENDIX D............................................................................................................................................36

1. Current Interfaces Below is a list of current interfaces going through e*Gate. When a User rings up he may only know the Description not the Interface name. The interface (1st column) is generally the prefix for the files flowing between the systems. I’ve highlighted the interfaces that generally get processed during the night, and of which users would ring up about a problem with. The SYSTEM shows which direction the file is going. This is generally the starting point of fixing any problems. What is the interface? Which direction is the file going?

INTERFACE DESCRIPTION SYSTEMRMBO ROUTE SETTLEMENT/BILLING RAMS - SAPRMTO LOAD CONFIRMATION RAMS – SAPRMMO RETURNS AND SCRAPING RAMS – SAPRMRO WEEKLY INVOICES RAMS – SAPSPCO CUSTOMER MASTER SAP – RAMSSPPO MATERIAL MASTER SAP – RAMSWINI WISE INVENTORY TRANSACTION WISE – SAPWWRI WISE/SAP TRANSACTION

RECONCILIATIONWISE – SAP

WWSI WISE/SAP STOCK BALANCE RECONCILIATION

WISE - SAP

WPSI CONFIRMED PICKING SLIPS WISE - SAPWRRO WISE RE-SUPPLY ORDERS/PURCHASE

ORDERSSAP-WISE

WSOO WISE SHOP ORDERS SAP – WISEWSCO SSCC EXPORT SAP-WISEWCOO WISE CUSTOMER ORDER &

RESUPPLYSAP - WISE

WLRO WISE CUSTOMER RETURNS SAP - WISEWCMO CUSTOMER MASTER SAP – WISEWIMO MATERIAL MASTER SAP – WISECPSI CLELLANDS CONFIRMED PICKING SLIPS CLELLANDS – SAPCSCO SSCC DOWNLOAD SAP – CLELLANDSCCOO CLELLANDS ORDERS SAP – CLELLANDSTPSI TDG CONFIRMED PICKING SLIP TDG - SAPTCOO TDG ORDERS SAP - TDGEDI ORDERS EDI ORDERS GEIS/ICAN-

RAMS/SAPEDI CONFIRMATION

EDI ORDER CONFIRMATION FROM SAP SAP - GEIS

CINV CCFA INVOICES CCFA-SAPCCNO CCFA CREDIT NOTES CCFA-SAPCIAJ CCFA INVENTORY ADJUSTMENTS CCFA-SAPCCMO CCFA MASTER DATA RECON FILE CCFA-SAPPPSI P&O PICKING SLIPS P&O-SAPPCOO P&O CUSTOMER ORDER & RESUPPLY SAP-P&OPCVO P&O ORDERS SAP-P&OPCRO P&O ORDERS RAMS-P&O

2. E*Gate Monitor

The e*Gate Monitor is used to monitor that all interfaces are up and running.

To start the e*Gate Monitor select the above icon as shown ORStart -> Programs -> eXchangeBusiness Suite -> eGate Monitor

When double-clicking on the eGate Enterprise Monitor icon the Logon screen appears.

Registry Host : DFLID12 (Production) User Name : OperationsPassword : STC (must be in capitals)

Select ‘Open’.

It will then ask which Schema to select. All interfaces are within the DairyFarmers schema. So select DairyFarmers and click ‘Open’.

The e*Gate Monitor screen can be seen above. It shows all the IQ managers, BOBs and eWays that are used for all interfaces in the Dairy Farmers environment.The above screen shows that bobFtpIn_WISE is not started (it is a RED colour) . A RED ALERT! Is flashing at the top of the screen indicating to the user that it needs to be started.

ALERT Signal Flashing

In the screen below, the ALERT signal is flashing indicating that something is wrong

eWay/BOB/IQ mgr has gone RED

Resolution This will require that the eWay be started by either :1. right-clicking on the eWay and selecting Start or,2. selecting the eWay, then selecting the Control Tab at the top of the screen. A command will appear at

the bottom of the screen whereby you select the Start command and then hit Run.

By starting the eWay /BOB/IQ mgr that has gone RED, automatically the Alert Notification will be Resolved. It will not require user intervention. If there is more than one notification for the same eWay/BOB/IQ only 1 notification will be resolved by fixing the problem. To stop the Alert Flashing, click on the ‘Alerts’ tab. At the top of the screen a Red Tick will appear. Click on the ‘Red Tick’ and Press ‘Yes’. The Alert will stop flashing.

ClickRed Tick to remove Flashing ALERT

eWay/BOB/IQ mgr NOT RED but Alert Signal Flashing

If none of the eWay/BOBs or IQ mgrs are RED then something else in e*Gate is wrong. Following are some of the Event Names that appear . This screen can be viewed by selecting the Control Broker DFLID12_cb on top left-hand of the screen, and selecting the Alert Tab.

Event Name Resolution CB Lost Connection To E*Gate Monitor Click on Observed and Resolved BOB Down Controlled Click on Observed and Resolved E*Way Down Controlled Click on Observed and Resolved External State Down IO failure Click on Observed and Resolved External State Unresponsive User Click on Observed and Resolved IQManager Down Controlled Click on Observed and Resolved Operational Non standard None Click on Observed and Resolved

Check SQL, and the Interface Monitoring Utility to make sure that everything is okay and files are flowing through e*Gate to SAP or Legacy systems (SQL is discussed in the next section). To Stop the ALERT flashing click on the Red Tick at the top of the screen (Alert Tab must be selected for the Red Tick to be available for selecting)

Alerts Tab

3. SQL Message Visibility

The SQL Message Visibility is used to inform particular business users and technical people of what files are flowing through e*Gate and if any problems have been encountered.

Every file that comes into e*Gate a record is created in the SQL database. And for each file, it goes through several status updates. It is this status that is used to determine whether further investigation is required.

The status’s that are possible are : ‘R’ - file has been received by e*Gate ‘I’ - file has been id’ed. E*Gate has determined what type of interface file it is. ‘T’ - e*Gate has performed some data translation to the file. The file coming into e*Gate may be in a particular format but the destination system may require the file in a different format. ‘S’ - the file is being sent to its destination system. ‘F’ - the file failed to process at the destination system. This may be because of technical issues or

business data issues. ‘P’ - the file succesfully processed at the destination system. ‘SF’ - in attempting to send the file to the destination system, the system could not be reached (maybe

timeout). ‘RR’ - the file has been specified to resend to the destination system. This status will occur for those

files that have ‘SF’ status. This is manually changed by Operations and is part of the SQL Query already defined. So every time the query gets executed, this update will automatically occur.

Connecting to the SQL database

To connect to the database through WINSQL, the following steps are to be performed :

1. Select the ‘Shortcut to Winsql’ icon from the desktop.

2. Select Data Source Name : eGate_DFLID12 UserID : sa

Password : farmers (lower case)

3. Open up an existing Query – EGATE_Prod_Query

4. The date range may need to be changed.There are 3 queries : the first displays all Non-EDI records that have come into the system for today, the second query displays all EDI records that have come into e*Gate. The third will reset any files that have status ‘SF’ and change it ‘RR’. Change the date to the current date.

5. Change the Query Viewing.From the Query menu select ‘Display Result in Grid’.

6. Execute the Query by pressing the Green Play button.If it seems the Query has locked and no data is coming up you can change the query selection time

select * from message where laststatustime > '2004-11-30 00:00:00' and ……….

You could change the time to ‘2004-11-30 15:00:00’ which means start the selection from 3pm on 30/11/04.

The above screen shows the results from the query executed.This particular query shows all files that have come into e*Gate.It shows the filename, the last status time, interface name, the source system, the destination system, and the time for each of the particular status sequence.

What to Look For ?

SQL query is used to make sure files are flowing consistently through e*Gate. During the night, the main interfaces that should be consistently going through e*Gate are :

Dguniqueid Interface DirectionWINI* WIN Wise to SAPWPSI* WPS Wise to SAPRMTO* RMT RAMS to SAPRMMO* RMM RAMS to SAPRMBO* RMB RAMS to SAP (not consistently during night but should never

fail)

If the above files are not consistently going through e*Gate, or files are sitting in ‘R’, ‘I’, ‘T’ status for a prolonged period (say 20-30minutes) or the IA Monitoring Utility (see next section) is Red then action must be taken. The appropriate BOB/eWay will be required to be shutdown and restarted. See Appendix A.

Other times during the night, you should get a batch of files, this includes :Time Dguniqueid Interface Direction12:30am CINV* CIN CCFA to SAP12:55am date/time stamp COL SAP to Coles

If no files are received more than 20-30 minutes after the usual time as noted previously then the appropriate BOB/eWay will be required to be shutdown and restarted. See Appendix A.

RAMS and CCFA files should never fail (files have ‘F’ status). This includes RMMO*, RMTO*, RMBO*, CINV*, CCNO* and CIAJ*. If this occurs shutdown and restart ewToSAP, ewToSAP2, and ewToSAP6.These files that have failed will be needed to be reprocessed. See Appendix C. When reprocessed the status of the files in SQL will NOT change. They will stay as ‘F’. Any subsequent files should process and finish with a ‘P’ status.

WINI* and WPSI* files may fail. A Business person at Wetherill Park (plant that uses WISE) will automatically receive an email, and it is up to them to perform necessary tasks. Nightshifts only concern is that they got to SAP (whether it’s ‘F’ or ‘P’ status).

4. Interface Monitoring Utility The monitoring utility displays for all interfaces, when the last time a particular interface file was received by e*Gate. The utility also colour hightlights all the interfaces as to their status. Tolerance levels for each interface for each day has been setup, which will determine the colour status of the interface. The colour will determine what course of action, if any, is required.This utility will come in handy when business users ring up and say that no files are coming through. You can quickly check the utility to find out when the last file came in.

To Start the Monitoring Utility

From Start->Programs->Interface Monitoring Utility->Interface Monitoring Utility or from the shortcut on the desktop screen.

Then click on the ‘Start Timer’. The Utility screen will be refreshed every 15 minutes during the week and 30 minutes on weekends.

If you wish to do a refresh straight away, then click on ‘Stop Timer’ and then click on ‘Run Now’.

What does it show?

As can be seen above every interface is highlighted in colour. The colours mean : Cyan/Blue - a file was received in a normal time frame, and so does not require any further action. Yellow - a file has not been received in some time, but may not require any further action as yet. Red - a file has not been received for a lengthy time and further investigation is required.

Note: Those interfaces with ‘Not found’ have not been implemented and so you can ignore them.

For IBM doing the night shift, the interfaces that should never go RED and require investigation are :-

RAMS : RMBO, RMTO, RMMOWISE : WINI, WPSI, WCOOCCFA : CINV

By double-clicking on the interface name you can display the contents of the SQL record for the last record entry of that interface. Main things to note are :

- DGUniqueid – this is the filename- LastStatusTime : this is the last time the file was updated- Status : current status of the record (used to determine what course of action may be needed to

take place)

5. Troubleshooting

IA Monitoring Utility On the IA Monitoring Utility described in previous section, Only Red highlighted interfaces require further investigation. It does not necessarily mean there is something wrong with e*Gate or the interface, but some interfaces occur infrequently during the night and do not require investigation.

For IBM doing the night shift, the interfaces that should never go RED and require investigation are :-

RAMS : RMBO, RMTO, RMMOWISE : WINI, WPSI, WCOOCCFA : CINVEDI : This is for Saturday ONLY. See Appendix D for more.

What the following table shows is what direction the files go through e*Gate, and what interfaces go through e*Gate via the same path. Interfaces in e*Gate have been split into the direction it goes through e*Gate and from where the files are coming from.

Interface From To Other Related Interfaces

RMBO RAMS SAPRMTO RAMS SAP RMMORMMO RAMS SAP RMTOSPCO SAP RAMS SPPOSPPO SAP RAMS SPCOWINI WISE SAP WWRI, WWSI, WPSIWWRI WISE SAP WINI, WWSI, WPSIWWSI WISE SAP WINI, WWRI, WPSIWPSI WISE SAP WINI, WWRI, WWSIWRRO SAP WISE WSOO, WSCO,

WCOO, WLRO, WCMO, WIMO

WSOO SAP WISE WRRO, WSCO, WCOO, WLRO, WCMO, WIMO

WSCO SAP WISE NOT USED AS YETWCOO SAP WISE WRRO, WSOO,

WSCO, WLRO, WCMO, WIMO

WLRO SAP WISE WRRO, WSOO, WCOO, WSCO, WCMO, WIMO

WCMO SAP WISE WRRO, WSOO, WSCO, WCOO, WLRO, WIMO

WIMO SAP WISE WRRO, WSOO, WSCO, WCOO, WLRO, WCMO

CIAJ CCFA SAP CCNO, CINVCCNO CCFA SAP CIAJ, CINVCINV CCFA SAP CIAJ, CCNOTPSI TDG SAP

TCOO SAP TDGPPSI P&O SAPPCVO SAP P&OPCRO RAMS P&OORDERS - EDI GEIS, ICAN RAMS/SAPCONFIRMATIONS SAP GEIS

For example, the WINI file. Other related interfaces are WPSI, WWSI and WWRI (See furthest right column). All these interface files come from WISE and go to SAP. They also go through the same path in e*Gate. If NO WINI files are going through e*Gate then NO WPSI, WWSI and WWRI files should be going through e*Gate either.

If a particular interface is Red then check in the ‘Other Related Interfaces’ column to see if those interfaces have received any files OR are also Red (use the time to check if the other interfaces have received files sooner or later than the interface that is showing Red). The Monitoring Utility shows when the last time a file was received in minutes based on the last refresh time..If an interface is Red and the other related interfaces have received files in the meantime, then there is nothing wrong with eGate. It could be that the system generating the files has something wrong.

E*Gate Monitor On the e*Gate Monitor, if eWay/BOB/IQ is RED (not active) then :

- right-click on the eWay/BOB/IQ and select ‘Start’.

If the Start fails (Errors message is something like ‘start failed’ or ‘unable to start’) then the eWay/BOB/IQ may actually be active (each eWay/BOB/IQ has a Process running when viewed in Task Manager). What needs to be done is to stop the eWay/BOB/IQ process ID manually. Then the eWay /BOB/IQ can be started. See Appendix B on how to manually stop the eWay/BOB/IQ Process.

Other Situations that may arise/ someone rings up with an interface problem

During the night, the main people ringing up will be from Wetherill Park – 90% of the time (this will be in regards to WISE interfaces or P&O interfaces).The first thing is to ask what system they are working on WISE, RAMS, or SAP, and what direction the files are going. – From WISE to SAP, RAMS to SAP, SAP to WISE, etc.If at all possible if they can give a filename prefix, for example WINI, WPSI, WCOO, RMTO etc, that would narrow down the troubleshooting options. The problems that may occur include :

1. Files are not being picked up from SAP or from Legacy System (which includes WISE, RAMS P&O, CCFA)- Check e*Gate Monitor to make sure that NO eWays/BOBs/IQs are RED. If so start it using

procedures already mentioned. After a few minutes files should then be processing in the destination system. Tell user to check in a few minutes and if not to ring back.

- Check Monitoring Utility to find out when the last file was received. Click on the Interface name e.g WPSI, RMTO etc. This will show when the last record was received. What is the Status of the record? This will determine what needs to be shutdown and restarted.

- Check SQL. See if you can find when the last file (using the prefix RMTO, WINI, etc) was received.

If files are not being picked up then shutdown and restart the correct eWays. See APPENDIX A.

2. Files are not coming into SAP Check Monitoring utility to find out when last file was received. Click on the Interface name e.g WPSI, RMTO etc.

If file has been received recently, then check the status of the file. In SQL query check if the file has ‘R’, ‘I’ or ‘T’ status OR no file has been received at all, then shutdown and restart the correct eWay. See APPENDIX A.

3. Files failing which are NOT RAMS and CCFA relatedDuring the night some files fail. E*Gate automatically sends an email to a nominated business person who fix and reprocess the files. Even when the business person has processed the file, the status of the file will remain ‘F’. Files that generally will fail include WPSI, TPSI, PPSI. It is only RAMS and CCFA files that should not fail.

4. RAMS and CCFA files are failing .Shutdown and restart the correct eWays. This includes ewToSAP, ewToSAP2 and ewToSAP6. For the RMBO, RMMO, RMTO, and CINV files that have failed they need to be reprocessed in SAP. To do this See APPENDIX C

5. Files are not coming from P&O – PPSI. P&O PPSI files are actually put on the e*Gate server by P&O. To check to see if any PPSI files are waiting to be picked up, Open Explorer and go to the following directory -> d:\PnO\prd\in\comm. If any files are sitting here, and have been here for some time then shutdown and restart the appropriate eWays. See APPENDIX A.If no files in the /comm directory and P&O/User has said files have been sent then check in the archive directory – d:\PnO\prd\in\arch, and see what time the last file was received. If no files for sometime, then let P&O/User know that we have not received any files since xx:xx:xx time. Last file was PPSIxxxxxx.If files are in /arch directory recently, then check SQL to see if any PPSI files are sitting in ‘R’, ‘I’, ‘T’, ‘S’ status. If so, then shutdown and restart the appropriate eWays/BOBs – See APPENDIX A.

6. EDI.On Saturday the only EDI we receive are Milk EDI orders.Please see APPENDIX D, for detailed description and troubleshooting.

7. Normal Shutdown Shutting the Interface Architecture is significantly more involved than starting the server and should only be under taken if emergency maintenance is required on the IA production server or under the direct instruction of one of the IA Administrators.

The following logical steps must be completed in order to shutdown the Interface Architecture. Due to the imprtance of e*Gate the following must be correctly performed in order :

Shutdown eGate on DFLID126.1 Shutdown all inbound ports to the IA.6.2 Confirm all outbound port queues are empty.6.3 Shutdown all other Modules and programs.

Reboot DFLID12 server.6.4 Reboot eGate DFLID12 server.

6.1 Shutting Down the Inbound eWays (eGate on DFLID12)

Shutdown the following Inbound eWays. ewMsgHopr ewMsgHopr_BW_Citibank ewMsgHopr_RAMS ewMsgHopr_RAMSBAfter 5 minutes shutdown the following : ewFromSAP ewFromSAP2 ewFromSAP3 ewFromSAP4 ewFromSAP6 ewFromGEIS ewFromSAP_ALE ewFtpIn ewFtpIn_BW_Citibank ewFtpIn_RAMS ewFtpIn_RAMSB

The above eWays must be successfully shut down before advancing to the next step.

To shutdown the inbound port either 1) right –click on the port name, it will bring up a list of options and then select Shutdown. or 2) On the Control Tab select the Shutdown command and press Run.It will then prompt you for confirmation of shutdown and then select ‘Yes’.If shutdown of the eWay does not occur in a couple of minutes, it can be killed (See Appendix B)

6.2 Confirm Outbound Queues in eGate (DFLID12) are Empty

When shutting down eGate we want no files to be going through eGate at the time. To check this execute the SQL query and check for any files that are not in a ‘F’, ‘S’ or ‘P’ status.

As you can see from the above SQL Query in the status column, there are a number of files that are not in ‘F’, ‘S’ or ‘P’ status. If you see this you should rerun the query (click on green play button) until all files have been processed.

The possible status’s that you should wait until they have been processed are :‘R’ File Received in eGate.‘I’ File IDed in eGate.‘T’ File Translated in eGate.

When all Files in the Query are sitting in ‘F’, ‘S’ or ‘P’ status then you can move onto the next step of shutting down all other Ports/eWays.

6.3 Shutdown All Other Modules and Programs

When all Inbound ports have been shutdown and no files are going through eGate, the next step is to shut down all remaining modules.

To shutdown all remaining modules you can either 1) right-click on the Control Broker (this is identified by DFLID12_cb at the top of the module tree) and selecting Shutdown All Modules. or 2) select the Control Tab and select Shutdown All Modules on the Command Line. Then press Run button.

It may take a few minutes for all modules to go RED. If after 5 minutes all Modules have NOT gone RED then goto Appendix B on how to shutdown those still remaining.

When all modules have gone RED effectively eGate is shutdown.

If you are shuttting down and rebooting the server then close all programs that may be open on the server and shut any Monitor screens that may be up (on DFLID12 server or on your local machine).

You Can Now Do a Reboot of the Server

6.4 Restart of eGate DFLID12 ServerWhen DFLID12 server has been rebooted, e*Gate will automatically restart itself after about 5 minutes.

When you can logon to DFLID12 through PcAnywhere, start the Monitor, SQL Query and IA Monitoring Utility.

If the Monitor screen does not connect (shown by a RED ‘X’ next to DFLID12_cb) then either 1) right-click on DFLID12_cb and select Connect, or 2) on the Control Tab select Connect from the Command Line and press run.

It will say at the bottom of the screen ‘Connecting to DFLID12 CB on Port 5000’.

If it does not connect try again. E*Gate may still be starting up and not enough resources are being allocated to the Monitor. Once all the Processes have been started it will then be possible to re-connect the Monitor.

On reboot of DFLID12, check ALL Services are running on the ICAN Monitor (please see ICAN Monitoring and Troubleshooting Guide).

APPENDIX A

What this table shows is what eWays/BOBs need to be shutdown and restarted based on what area the problem is occurring. For example, if a user rings up and says NO files from WISE are going to SAP and you have determined that files have not been picked up from WISE you can shutdown and restart eWays related to WINI, WPSI, WWSI, WWRI files. In other words, ewFtp_Config, ewMsgHopr, and ewFtpIn eWay scan be shutdown and restarted. Within a few minutes files should be picked up, and go to SAP.Wait 5-10 seconds after a shutdown to make sure it has been shutdown – it should stay RED.

If for example, files have been picked up by e*Gate, but have not reached SAP. Checking SQL query reveals that RMBO files have a status ‘R’ (which means e*Gate has picked up the file but not processed it). To solve the problem, check RMBO interface, 3rd-column is for those interfaces with ‘R’ or ‘I’ status. You will be required to shutdown the bobRAMS_Billing and bobRAMS_Billing2 and restart them. After a minute or so the file should change status and go to SAP.

When is a KILL necessary ?If you shutdown an eWay/BOB/IQ and it goes RED and then Blue/Grey (looks like it has restarted itself) or hasn’t gone RED after 30 seconds, then right-click -> status to double-check to see if it is down. If it is NOT RED then Kill the process – See Appendix B. An eWay/BOB/IQ that has been shutdown should stay RED!!

Interface File not being Picked up by eGate (inbound) – No record in SQL

File picked up, but not being processed in eGate – File in Status ‘R’ or ‘I’

File not sending to SAP/Legacy through eGate (outbound) – File in Status ‘T’

RMBO EwFtp_Config_RAMSB, EwMsgHopr_RAMSB, ewFtpIn_RAMSB

BobRAMS_Billing,BobRAMS_Billing2

EwToSAP2

RMTO EwFtp_Config_RAMS, EwMsgHopr_RAMS, ewFtpIn_RAMS

BobRAMS_Others EwToSAP

RMMO EwFtp_Config_RAMS, EwMsgHopr_RAMS, ewFtpIn_RAMS

BobRAMS_Others EwToSAP

SPCO EwFromSAP BobRAMS_FromSAP EwLegacy_FtpOutSPPO EwFromSAP BobRAMS_FromSAP EwLegacy_FtpOutWINI EwFtp_Config, EwMsgHopr,

ewFtpInBobFtpIn_WISE EwToSAP3

WWRI EwFtp_Config, EwMsgHopr, ewFtpIn

BobFtpIn_WISE EwToSAP3

WWSI EwFtp_Config, EwMsgHopr, ewFtpIn

BobFtpIn_WISE EwToSAP3

WPSI EwFtp_Config, EwMsgHopr, ewFtpIn

BobFtpIn_WISE EwToSAP3

WRRO EwFromSAP2 BobWISE_FromSAP2 EwLegacy_FtpOutWSOO EwFromSAP2 BobWISE_FromSAP2 EwLegacy_FtpOutWSCO EwFromSAP2 BobWISE_FromSAP2 EwLegacy_FtpOutWCOO EwFromSAP2 BobWISE_FromSAP2 EwLegacy_FtpOutWLRO EwFromSAP2 BobWISE_FromSAP2 EwLegacy_FtpOutWCMO EwFromSAP2 BobWISE_FromSAP2 EwLegacy_FtpOutWIMO EwFromSAP2 BobWISE_FromSAP2 EwLegacy_FtpOutCIAJ EwFtp_Config, EwMsgHopr,

ewFtpInBobFrom_CCFA EwToSAP6

CCNO EwFtp_Config, EwMsgHopr, ewFtpIn

BobFrom_CCFA EwToSAP6

CINV EwFtp_Config, EwMsgHopr, ewFtpIn

BobFrom_CCFA EwToSAP6

TPSI EwFtp_Config, BobTDG_CLELANDS EwToSAP5

EwMsgHopr,ewFtpInTCOO EwFromSAP4 BobTDG_CLELANDS EwLegacy_FtpOutPPSI EwFtp_Config,

EwMsgHopr,ewFtpInCheck on DFLID12 D:\PnO\prd\in\comm for files

BobPandO EwToSAP5

PCVO EwFromSAP3 BobPandO EwLegacy_FtpOutPCRO EwFromSAP3 BobPandO EwLegacy_FtpOutMPSI EwFtp_Config, EwMsgHopr,

ewFtpInBobFrom_TDG EwToSAP5

CITIBANK EwFtp_Config_BW_Citibank, EwMsgHopr_BW_Citibank, ewFtpIn_BW_Citibank

BobCitibank (may be in ‘P’ status)

EwToSAP40, ewToSAP7, ewLegacy_FtpOut

ORDERS EwFromGEIS, ewFromICAN BobFromGEIS, bobFunctionAck, EwToSAP_ALEEwGEIS_ToRAMS

ORDERS – not reaching RAMS

Check on DFLID12 D:\PRDOEDIWRK and COM

D:\eGate\ICANint\FromICAN

If file in WRK then do --

If files with *.dat extension -

EwMsgVis_AckConfigEwMsgVis_AckSchedulerEwMsgVis_AckProcessor

EwFromICAN

CONFIRMATIONS/Coles/ERS

EwFromSAP_ALE bobToGEIS ewToGEIS

For the correct interface shutdown and restart the correct eWays. Either the inbound or the outbound eWays. Any problems in shutting down eWay/BOB, see Appendix B.

APPENDIX B

If for some reason you have shutdown an eWay/Bob etc, and it will not go RED after 30seconds or it goes RED then looks like it has started up again by itself (do a refresh on the eWay/Bob – right-click and update) then it may require to be manually stopped.

Logon to DFLID12 server through PC Anywhere (you are probably already logged onto DFLID12)

Go to MS-DOS Command Prompt and change to D:\ drive.

Right click on module that is not ending and select Status.

On the right side of the screen there is a field called ‘Process ID’. In the above example it has a value 684.

Go back to the MS-DOS Command prompt and on the d: drive type in kill 684. This will END the process that is controlling the module that will not end. After a few seconds the module on the monitor screen will go RED. You can do a right-click -> status to refresh the eWay/BOB/IQ.

Perform this scenario for any other modules that do not want to end.

APPENDIX C

As mentioned previously RAMS and CCFA files should not fail. These files if failed would be sitting in the error directory in SAP - /PRDISAPERR. Files in the error directory can be reprocessed within SAP.

From SAP Main Menu, select Logistics -> Interface menu.

Reprocess RAMS files in SAP

From the RAMS interface menu, select Reproc error files.

The screen allows the reprocessing of an individual file or ALL Rams files in the error directory.To reprocess all Rams files (which we want to do) in the error directory, change the Process All Files to ‘Y’, and select one filename from the drop-down (A file must be selected to reprocess all files). Then click execute.

Reprocess CCFA Files in SAP

From the CCFA interface menu, select Reproc error files.

The screen allows the reprocessing of an individual file or ALL CCFA files in the error directory.To reprocess all CCFA files in the error directory, change the Process All Files to ‘Y’, and select one filename from the drop-down (A file must be selected to reprocess all files). Then execute.

APPENDIX D

This section describes the EDI process.There are two processes for EDI. Milk EDI orders which go to RAMS system, and Dairy Food EDI orders which go to SAP. On Saturday the only EDI files are Milk EDI Orders. Only this will be explained below.

EDI – Milk EDI orders to RAMS.

How to distinguish?In SQL, they can be seen by :

Interface = ‘EDI’FromSystem = ‘GEIS’ or ‘ICAN’ToSystem = blank

Milk EDI orders will only ever reach status ‘I’.

Woolworths Milk EDI OrdersOn Saturday the main Milk Edi Orders come from Woolworths.

The process of how Woolworths Milk EDI orders are processed is :

Milk EDI orders come via AS2 (the Internet) into ICAN. ICAN will create the files on the e*Gate server (DFLID12) in d:\eGate\ICANInt\FromICAN with a file

extension *.dat. e*Gate will then pick up the files from the directory with eWay ewFromGEIS. The files in FromICAN

directory are then renamed with file extension *.~in. eWay ewFromGEIS in e*Gate will verify the EDI file. bobFromGEIS will then translate the EDI file. ewGEIS_ToRAMS will then create a text EDI file on the e*Gate server at d:\PRDOEDIWRK. ewAck_Processor will then move the file from d:\PRDOEDIWRK to d:\PRDOEDICOM. RAMS job CISEDIPP1 will pick up any files from d:\PRDOEDICOM every couple of minutes and

then update RAMS. When files have been picked by RAMS, the files in d:\PRDOEDICOM will be deleted.

What can go wrong with Woolworths Milk EDI Orders and how to resolve?

Check SQL.In Resultset #2, check to see if any records with :

Interface = ‘EDI’FromSystem = ‘GEIS’ or ‘ICAN’ToSystem = blank

If none, then NO Milk EDI files have been picked up. Check the following points.

1. Milk EDI orders not received Firstly check on the e*Gate server (DFLID12) directory d:\eGate\ICANInt\FromICAN to see if there are any current files in it.If there are files with extension .dat then shutdown in eGate ewFromICAN and then restart. e*Gate should then pick up the files and rename to *.~in.

If there are files already with extension *.~in then e*Gate has already picked up the files.

2. Milk EDI orders received but nothing in SQL. If there are current files in d:\eGate\ICANInt\FromICAN with file extension *.~in then eGate has picked up Milk EDI files. BUT if no records can be seen in SQL then : shutdown ewFromGEIS.

When shutdown (is in RED), do a status on the ewFromGEIS (right-click on ewFromGEIS and select status), and make a note of the PID (Process ID).

Open up CMD line on e*Gate server, go to D:\ drive and type in kill xxxx, where xxx is the PID number from the status.

Start ewFromGEIS.You should now start to see records in SQL for Interface ‘EDI’ appearing.

3. Milk EDI orders received but not reaching RAMS. Check SQL. If you see records in Resultset #2 with status ‘R’ then shutdown bobFromGEIS. When RED,

start bobFromGEIS. (May require a kill). If you see records in Resultset #2 with status ‘I’ , then check on the e*Gate server :

D:\PRDOEDIWRK. If text files have been sitting there for some time, then shutdown the following :

ewMsgVis_AckProcessorewMsgVis_AckSchedulerewMsgVis_AckConfig

When all are RED, start them in same sequence as above. After a couple of minutes the files should move from d:\PRDOEDIWRK to d:\PRDOEDICOM.

If files are sitting in d:\PRDOEDICOM for sometime, check RAMS.Do a WRKACTJOB. On CIS subsystem, check the job CISEDIPP1 for any messages.

Franklins Milk EDI OrdersOn Saturday we get some EDI Orders from Franklins.

The process of how Franklins Milk EDI orders are processed is :

Milk EDI orders come via a third-party mailbox into e*Gate. (Note: ICAN is not involved). e*Gate will pick up the files from mailbox with eWay ewFromGEIS. eWay ewFromGEIS in e*Gate will verify the EDI file. bobFromGEIS will then translate the EDI file. ewGEIS_ToRAMS will then create a text EDI file on the e*Gate server at d:\PRDOEDIWRK. ewAck_Processor will then move the file from d:\PRDOEDIWRK to d:\PRDOEDICOM. RAMS job CISEDIPP1 will pick up any files from d:\PRDOEDICOM every couple of minutes and

then update RAMS. When files have been picked by RAMS, the files in d:\PRDOEDICOM will be deleted.

What can go wrong with Franklins Milk EDI Orders and how to resolve?

Check SQL.In Resultset #2, check to see if any records with :

Interface = ‘EDI’FromSystem = ‘GEIS’ (will only be GEIS NOT ICAN)

If none, then NO Milk EDI files have been picked up. Check the following points.

1. Milk EDI orders not received Check SQL.If no records, shutdown ewFromGEIS and then restart ewFromGEIS (may require a kill).

2. Milk EDI orders received but not reaching RAMS. Check SQL. If you see records in Resultset #2 with status ‘R’ then shutdown bobFromGEIS. When RED,

start bobFromGEIS. (May require a kill). If you see records in Resultset #2 with status ‘I’ , then check on the e*Gate server :

D:\PRDOEDIWRK. If text files have been sitting there for some time, then shutdown the following :

ewMsgVis_AckProcessorewMsgVis_AckSchedulerewMsgVis_AckConfig

When all are RED, start them in same sequence as above. After a couple of minutes the files should move from d:\PRDOEDIWRK to d:\PRDOEDICOM.

If files are sitting in d:\PRDOEDICOM for sometime, check RAMS.Do a WRKACTJOB. On CIS subsystem, check the job CISEDIPP1 for any messages.