Information Systems:Electronic Sales Orders (POS Ordering) - Revision history

Norwinu: Norwinu moved page Information Systems:Electronic Sales Orders to Information Systems:Electronic Sales Orders (POS Ordering)

2017-01-05T19:44:21Z

Norwinu moved page Information Systems:Electronic Sales Orders to Information Systems:Electronic Sales Orders (POS Ordering)

Norwinu: /* Email */

2017-01-05T19:26:57Z

Norwinu: /* Email */

2017-01-05T19:25:03Z

Norwinu at 19:50, 26 July 2016

2016-07-26T19:50:10Z

New page

=Electronic Orders=

Stores have POS (point of sales) computers that can generate orders, then either email or FTP them to us. It appears that these orders can be created as sales are made, or based on a predefined order point.

We don’t support these devices, but they have access to our FTP server.

For information on what the store has to do, see ‘POS file specs and examples / Order Invoice Interface Specs.pdf’. Also in this folder are sample files, and layouts.

==History==

Before the Unity project, uniPHARM supplied stores with a PC application called the EOB, or electronic order book. Each store had a three digit 'EOB number' to identify them, which was included in the order emailed to uniPHARM. When we converted the customer and supplier file into ASW, new customer numbers were assigned, and the EOB numbers were put into a cross reference file (IMPXRFP). Orders sent from stores' POS still use that same number.

We had problems every time we started receiving orders from a new POS - trying to explain why there had to be an account number that was different from the one used on invoices, statements, and Web Orders.

So the beginning of 2012, we changed the process to allow 5 digit EOB numbers, and put the ASW partner number into IMPXRF. Then at the beginning of 2016, we changed the process to look in SRONAM (ASW Partner File) if the number isn't in IMPXRF (EOB cross reference file).

==Email==

They can be emailed to us, in X12, which will be processed by [[IMS Description|IMS]], [[IMP Description|IMP]], then [[IOP Description|IOP]]. The type of POS ('source') that sent the order is identified (in programs IMSNEP01 and IMPPAR01) by the subject. The 'source' is used to set the handler in ASW (in programs IOPASW01 and IOPRAW01), which is used to separate sales by the different POS types.

'''subject''' '''source''' '''handler'''
X12 PO ARI EDI-ARI
X12 PO ARI EDI-ARI
INPHARM PO (POS#999999) TRI-POS EDI-TRIPOS
INPHARM PO (RX#999999) TRI-RX EDI-TRIRX
PT PO 999999 POSITEC EDI-POSITE

Where 999999 is the actual PO number.

==FTP==

KROLL EDI-KROLL

Note that this was originally used to receive orders from Prairie Supply Co-op, and was called ‘Alberta Integration’, so the name prefix is ‘AI’.

The user ID and passwords that stores have for our FTP server only allow them access to one folder - /FTPOrders/99999 (where 99999 is their partner number). Within that folder there can be two more; one for orders and one for invoices. If a store is sending orders from, or wants invoices sent to, more than one P.O.S. system, they can either have more sub folders under 99999, or they can have a new folder with an appended name; for example 99999K.

To see what has been setup, go to Unity / Start uniPharm Extensions / VA Company (PRODUCTION) / Work with UWD IT Tools / FTP Connections / Sales Orders FTP Configuration.

This calls DFU on file AIINTFP. This file is used to connect to the FTP server, search for order files, and upload them to the i. If a store is not setup in this file, we will not process their orders! The ‘FTP directory’ is what counts; the ‘Name’ and ‘Description’ are just to let us know which store it is. 'Customer # Type' is also a left over from Prairie Supply Co-op days; It indicates whether the customer number in the file is for PSC or UWD. 'Extensions' indicates the file layout, and tells program AIRUP020 which routine to use to translate them.

WORK WITH DATA IN A FILE Mode . . . . : CHANGE
Format . . . . : AIINTFR File . . . . : AIINTFP

Name: Cust10702
Description: Tumbler Ridge Pharmacy
FTP Server: mail.unipharm.com
FTP User ID: ftporders
FTP Password: **********
FTP Directory: 10702/orders
FTP Archive Directory: archive
M=Move D=Delete N=None: M
Transmission Source: FTP
Customer # Type: UWD
Ext 1: KRO
Ext 2: ___
Ext 3: ___

After an order has been successfully moved from our FTP server to the i, it is moved to an ‘archive’ folder that has been setup within the ‘orders’ folder. Although it is optional, it is best to archive the file. If we delete it and there are problems, we won’t be able to figure out what happened. If we do nothing, we will pick up that order every time the interface is run.

Order files from different P.O.S. vendors can have different formats. We determine the format by the file extensions.

This is the job that does this. It is started by EOD, and runs all day, every day.

Work with Active Jobs BART
08/28/14 10:03:15
CPU %: 23.9 Elapsed time: 00:08:21 Active jobs: 573

Type options, press Enter.
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
8=Work with spooled files 13=Disconnect ...
Current
Opt Subsystem/Job User Type CPU % Function Status
MONITOR2 QSYS SBS .0 DEQW
FTP_ORDERS EODJOB BCH .6 PGM-AICUP010 SELW

Parameters or command
===>

The orders are formatted and added to the IOP files. To see what happens next, look at [[IOP - Inbound Order Processing]].

==Add New Source==

Based on the source, set the handler (ie ‘EDI-TRIPOS’) in programs IOPASW01 (IOP -- Take an IOP order and create ASW EDi record), and IOPRAW01 (IOP -- Read an IMS order and create IOP records).

Add this handler to the Signature table in ASW. This should start with ‘EDI-‘ so that it will be recognized as an EDI order.

[[Category: ASW: Sales]]
[[Category: Ordering]]
[[Category: FTP]]

Jeremym at 21:52, 17 June 2016

2016-06-17T21:52:33Z

Sheilav: /* FTP */

2016-02-25T00:43:43Z

FTP

Sheilav: /* Email */

2016-02-24T22:51:22Z

Sheilav: /* Email */

2016-02-24T22:46:06Z

Sheilav: /* History */

2016-02-24T22:44:35Z

History

Sheilav: /* History */

2015-12-01T20:58:30Z

History

@@ Line 28: / Line 28: @@
 Where 999999 is the actual PO number.
-For more on email orders, [[Information Systems: POS Email Orders | check this page]].
+For more on email orders, [[Information Systems: POS Ordering (Email)| check this page]].
 ==FTP==

← Older revision		Revision as of 19:25, 5 January 2017
Line 27:		Line 27:

	Where 999999 is the actual PO number.		Where 999999 is the actual PO number.
		+
		+	For more on email orders, [[Information Systems: POS Email Orders \| check this page]].

	==FTP==		==FTP==

← Older revision		Revision as of 21:52, 17 June 2016
Line 88:		Line 88:

	Add this handler to the Signature table in ASW. This should start with ‘EDI-‘ so that it will be recognized as an EDI order.		Add this handler to the Signature table in ASW. This should start with ‘EDI-‘ so that it will be recognized as an EDI order.
		+
		+	[[Category:ASW: Sales]]

← Older revision	Revision as of 19:44, 5 January 2017
(No difference)

@@ Line 77: / Line 77: @@
  Parameters or command
  ===>
 The orders are formatted and added to the IOP files.  To see what happens next, look at [[IOP - Inbound Order Processing]].

@@ Line 26: / Line 26: @@
  PT PO 999999                POSITEC      EDI-POSITE
-Where 999999 is tha actual PO number.
+Where 999999 is the actual PO number.
 ==FTP==

@@ Line 25: / Line 25: @@
  INPHARM PO (RX#999999)      TRI-RX       EDI-TRIRX
  PT PO 999999                POSITEC      EDI-POSITE
 ==FTP==

@@ Line 13: / Line 13: @@
 We had problems every time we started receiving orders from a new POS - trying to explain why there had to be an account number that was different from the one used on invoices, statements, and Web Orders.
-So the beginning of 2012, we changed the process to allow 5 digit EOB numbers, and put the ASW partner number into IMPXRF.
+So the beginning of 2012, we changed the process to allow 5 digit EOB numbers, and put the ASW partner number into IMPXRF.  Then at the beginning of 2016, we changed the process to look in SRONAM (ASW Partner File) if the number isn't in IMPXRF (EOB cross reference file).
 ==Email==

@@ Line 9: / Line 9: @@
 ==History==
-Before the Unity project, uniPHARM supplied stores with a PC application called the EOB, or electronic order book.  Each store had a three digit 'EOB number' to identify them, which was included on the order emailed to uniPHARM.  Orders sent from stores' POS still use that same number.  When we converted the customer and supplier file into ASW, new customer numbers were assigned, and the EOB numbers were put into a cross reference file ().
+Before the Unity project, uniPHARM supplied stores with a PC application called the EOB, or electronic order book.  Each store had a three digit 'EOB number' to identify them, which was included in the order emailed to uniPHARM.  When we converted the customer and supplier file into ASW, new customer numbers were assigned, and the EOB numbers were put into a cross reference file (IMPXRFP).  Orders sent from stores' POS still use that same number.
 ==Email==