Difference between revisions of "Information Systems:IOP - Inbound Order Processing"
| Line 19: | Line 19: | ||
[[Category: Extensions]] |
[[Category: Extensions]] |
||
| + | [[Category: Ordering]] |
||
Latest revision as of 09:48, 30 June 2016
Overview
Job IOPPOSTPRD, which is program IOPNEP01CL (IOP-Generate orders into ASW (NEP Driver)), runs all day in subsystem IOPSUBPRD.
RPG program IOPNEP01 reads unposted orders in IMPOHDP, then calls IOPRAW01 (IOP -- Read an IMS order and create IOP records) to add them to IOPHDRP (IOP - Order headers to be posted to ASW) and IOPLINP (IOP - Order lines to be posted to ASW).
If they are valid, IOPPOS00 (IOP -- Run all prechecks and post to ASW) is called. This moves sales orders into ASW's EDI files, then uses base programs to process them.
Other Processes Using IOP
Web Orders
UW_ORDER copies lines from the cart into the IOP files, then calls WSPOSTORD to run IOPPOS00, and IOPMIN02 (IOP -- call IOPMIN03 to release held orders) in case a store with held orders is now over their daily order minimum.
Miscellaneous Billing
This is co-op fees and vendor debits from contracts. CXBILL03 () will add records to IOPHDRP and IOPLINP, then call IOPPOS00.
FTP orders
Job FTP_ORDERS, which is program AICUP010 (AI -- Background monitor), runs all day in subsystem MONITOR2. RPG program AIRUP010 gets FTP’ed orders off of mail.unipharm.com, then calls AIRUP020, which interprets them and writes to the IOP files. IOPPOS00 (IOP -- Run all prechecks and post to ASW) is called to move sales orders into ASW's EDI files, then use base programs to process them. (This was originally AIP – Alberta Integration Project, after we took over Prairie Supply Coop (PSC). Now we are getting more and more stores using FTP, and fewer using email.)