RPGLE program will chain out to VAI's S2K table of VXCODETL for each 856 detail line. Using the backordered amount we will determine if any item was short shipped. With this determination, we will populate the SLN segment with the backordered amount and backordered status code

RPGLE program will chain out to VAI's S2K table of VXCODETL for each 856 detail line. Using the backordered amount we will determine if any item was short shipped. With this determination, we will populate the SLN segment with the backordered amount and backordered status code

RPGLE program will chain out to VAI's S2K table of VXCODETL for each 855 detail line. Using the backordered amount we will determine if any item was short shipped. With this determination, we will populate the BAK segment accordingly.

SQLRPGLE program will be called as an EEI Exit Point. Using the long parm list, EXTOL calls the program at 'EL' (Enveloping). SQLRPGLE PGM will review a header record to determine the carrier. If the carrier is for UPS we will call 5 SQL Insert statements to copy data to 5 unique DB2 tables..

RPGLE program will be called as an EEI Exit Point. Using the long parm list, EXTOL calls the program at 'TE' (Translation End). RPGLE PGM will review each detail line (F47012) of purchase order to determine if ITEM number needs to be updated. If item number is updated, a notes record is added to F4714.

RPGLE External Call, using the long parm list, EXTOL calls the RPGLE program at BAK02 element. PGM will review each detail line (F47027) of purchase order against order ack data to determine if any differences exsist between Ordering Price vs. Sales Price; Ordering UOM vs. Sales UOM; Ordering Quantity vs. Shipped Quantity

RPGLE program can be called before purge CMD:DLTDTA is called. DLTAPP will delete records out of EXLLAPP if the the status code (LAALPN) IS 'H'. These records would be considered outbound generated errors. This program would be called before the EXTOL Purge PGM:DLTDTA.

CLP will execute PRTACKTP two separate times to report late FAs (997s) in the past 24 hours and rejected FAs in the past 24 hours.

CLP will execute PRTACKTP and PRTCNNSEL. In addition to the EXTOL commands, we will execute custom queries via STRQMQRY.

CLP will execute PRTGRPLOG and PRTLOMAR 2 separate times to report late FAs (997s) in the past 24 hours and rejected FAs in the past 24 hours.

By running this program, from the IBM Job Scheduler, we will do a recap of the number of outbound invoices that have been acknowledged in the past 24 hours.

Inbound 830 report to email to end user. Called by EXTOL Trading Partner Message Class (TPMC) Exit Point CL.

Execute program by creating an external call (short parm list> to create check digit for License Plate number on ASN

Inbound 824 report to email to end user. Called by EXTOL Trading Partner Message Class (TPMC) Exit Point CL.

By running this program, from the IBM Job Scheduler, we can determine the number of outbound invoices and ASNs have been sent, or not, in the past 24 hours. A unique email will be sent out per document type.

RPGLE Program scans EXTOL file: EXLLIQL2 to then call EXTOL CMD: EXPNWRDTA and then AS400 CMD: CPYTOSTTMF.

In the CL that submits the jobs to run CRTAPPDTA, we can monitor the job and query EXLLCRL1 to determine status of EXTOL connection.

In the EXTOL map, use the 'short' parameter list to pass From/To UOM to program to have F41002 determine if quantity evenly divides into new UOM.

In the EXTOL map, use the 'long' parameter list to pass multiple variables to form an email to send to a trading partner.

In the EXTOL map, use the 'long' parameter list to create F4104 record if data is received in x12 data however the data is not found in F4104 table.

In the EXTOL map, use the 'short' parameter list to check following files: F4104_14 -> F4101_2 -> F03012_3 -> F4094LC -> F4106LC for pricing.

In the EXTOL trading partner exit point, use the 'long' parameter list to send email to used defined as a constant inthe respective map.

Check for 810 records to process. If records exist, the generate 810 x12 data via EXTOL CMD:CRTAPPDTAB

Using EXTOL trading partner exit point long parm list, create readable 864 report.

CL provides hook between EXTOL Secure Exchange (ESX) and EXTOL EDI Integrator (EEI). By copying/modifying CL, users can route data to multiple EEI environments.

From an outbound EXTOL /JDE map, query F47047 to summarize freight charges.

Use an EXTOL formula to add messages to the EXTOL Connection MSGQ.

Use an EXTOL formula to send an email using a defined constant in an EXTOL map.

Use an EXTOL formula to send an email using a defined constant in an EXTOL map. The email would be sent if if the x12 850 is not an Original PO.

There might be times that a PO might come in via fax and then via EDI. If the manual order is entered, we want to prevent the EDI order from coming into the F42 files.

There might be times that a PO might come in via fax and then via EDI. If the manual order is entered, we want to prevent the EDI order from coming into the F47 files.

Users can use the 204 header and 204 detail file to construct an outbound EDI 204 map. For more information on the outbound EDI map, Click here for XLS >

Users can use the 204 header and 204 detail file to construct an outbound EDI 204 map. For more information on the outbound EDI mapping, Click here for XLS >

Users can use the 210 header and 210 detail file to construct an inbound EDI 210 map. For more information on the outbound EDI map, Click here for XLS >

Users can use the 210 header and 210 detail file to construct an inbound EDI 210 map. For more information on the outbound EDI map, Click here for XLS >

Users can use the 855 header and 855 detail file to construct an inbound/outbound x12 EDI 855 map. For more information on the inbound EDI map, Click here for XLS >

Users can use the 855 header and 855 detail file to construct an inbound/outbound x12 EDI 855 map. For more information on the inbound EDI map, Click here for XLS >

Users can use the 810 header and 810 detail file to construct an inbound/outbound x12 EDI 810 map. For more information on the inbound EDI map, Click here for XLS >

Users can use the 810 header and 810 detail file to construct an inbound/outbound x12 EDI 810 map. For more information on the inbound EDI map, Click here for XLS >

Users can use the 856 Shipment, Order, Pack, Item DDS specs to construct an inbound/outbound x12 EDI 856 map. For more information on the outbound 856 EDI map, Click here for XLS >

Users can use the inbound and outbound DDS specs to capture MSG/MTX comments.

Users can use the inbound and outbound DDS specs to capture ship-to, ship-from, remit-to address locations.

Users can use the 850 header and 850 detail file to construct an inbound/outbound x12 EDI 850 map. For more information on the inbound EDI map, Click here for XLS >

Users can use the 850 header and 850 detail file to construct an inbound/outbound x12 EDI 850 map. For more information on the inbound EDI map, Click here for XLS >