Correcting FCA/Chrysler/Stellantis Expendable Container ASNs for Euclid (Gentran/TCUX17)

Applies to: QAD 2014SE - Euclid Functional Area: QAD, EDI

Last Reviewed:

Reported Issue: Euclid ASNs for expendable containers need to be edited before being translated and sent to Stellantis. Otherwise the ASNs will fail.

Screenshot/Email Samples:

High-level steps:

Intercept the outbound file
Correct the outbound file
Put the file back into the outbound queue for translation

Steps to intercept, edit, verify, and replace the files are below.

Make sure there's a ticket. Open it. The ticket will have a description something like this:
Connect to TCUX17.
Change to /apps/gentran/gs60/ediprod/data/out
Run 2goec to check the time before the next run
Your goal is to intercept the files in /apps/gentran/gs60/ediprod/data/out before they get processed by Gentran. The next process time is approximately 10 minutes after the last time gsoutb.shl ran. You won't need long to move the files to your home directory but you'll need to wait for the plant to send the ASNs. If there are less than two minutes to the next transmission, I will have the plant hold off on sending ASNs until after gsoutb.shl processes again.
Tell the plant to send the (first) ASN. List the contents of the .../data/out directory to check for the plant file.You're looking for the newest PEM file.
When you see it, move it to your home directory immediately.
If the plant has more files to process, check 2goec again to see if you have enough time for the next file. If you do, have them send it and go to step 6 to check for the next file. If not, wait until gsoutb.shl processes again. This example shows just over a minute before the next run... too close for me.
Transfer the files to your machine to edit them. While you can edit them in Linux, transfering to your own machine makes it easier to add them to the ticket.
Once on your machine, make copies of the files so you can attach the originals and the updated files to the ticket.
Edit the files in your favorite text editor. You have two changes to make:
1. Delete the trailing record that has just "RC" in it
2. Globally replace "RCEXP " (five spaces) with "RC00000EXP" (five zeroes)
To confirm that you've made the change correctly, look for the shipper number on the lines starting with "30" (the 30 record). It should be in position 248:
If it is NOT in position 248 or if all the shipper numbers do not line up, you have made a mistake. Either start over or correct the mistake to make sure the shipper number is properly lined up in position 248 for every 30 record. Failure to do this will result in a failed ASN.
Once the changes are complete and correct, save the file and transfer it back to TCUX17. Note the different file sizes; your new file is smaller. When prompted, overwrite the file(s) on TCUX17.
From TCUX17, move the files back to /apps/gentran/gs60/ediprod/data/out from your home directory. Double-check the file permissions on the files you just moved back.
Run a final 2goec to check how long until the next iteration of gsoutb.shl.
Change to the archive/in directory to check for the 997s and 824s.
List the files in the directory. You're looking for dcx997em* and dcx824em* files.
Look at the 824 files to ensure they were accepted.
If it has not been accepted, you'll need to investigate why and deal with the issue. That is outside of the scope of this document.
Add the files to the ticket.

Root Cause: The SNF file contains incorrect info for the outbound ASN

RELATED DOCUMENTATION

Site

Location-Path

Document