Embedded Files
Process
This job aid describes the naming conventions and configurations for CUST interface README files.
Correct Naming Conventions
All CUST files must follow the naming conventions displayed in the following examples but tailored for your specific division.
Example: CORE_FEGA_CUST_WQCDBILLING_202407111430.xls
The first “node” of the name will always be CORE.
The second will always be the department.
The third will always be CUST, and
The fourth will always be your division.
The fifth before the .xls will be where the time date stamp is entered. It must follow this convention: YYYYMMDDHHMM
Any additional characters before or after these entries or not adhering to the naming convention detailed above will result in the file not being recognized and not being processed. As entries with spaces in or before or after these nodes result in SFTP failure to CGI during the nightly cycle process, any entries found to be breaking these rules will be deleted with no further notification. Here is an example of a file name with this type of issue: CORE_FHCA_CUST_LAB202405150800 R.xls
Correct Tab Naming Conventions
The tab located in the spreadsheet itself must be named to match the 4th node (division) of the file name or the spreadsheet will not be recognized.
Correct Ordering of Columns on a CUST File
The columns must be ordered as follows for the system to process their contents correctly:
A- TYPE_CD
B- COMP_NM
C- AD_ID_PREFIX
D- STR_1_NM
E- STR_2_NM
F- CITY_NM
G- ST
H- ZIP
I- VOICE_PH_NO
J- EMAIL_AD
K- PRIN_CNTAC
L- BPRO_CD
M- DEPT_CD
N- UNIT_CD
O- EXT_ACT_NO
P- SPRS_RG_STMT_BILL
Q- SPRS_PDU_STMT_BILL
R- COLL_CYC_CD
Failure to do so will result in a file possibly not processing correctly or at all. A sample template (CORE_Fxxx_CUST_GROUP_YYYYMMDDHHMM.xls) is available for download if needed.
Correct Format to Use With a CUST file (xls, not xlsx)
All uploads must be in a .xls format. Submissions that are sent in a .xlsx format will not process so they will also be deleted with no further communication.
Acceptable Codes to Use for Submission (EXT_ACT_NO)
The entries in this field must not exceed 15 characters. Refrain from using these special characters if possible
Underscores
Hyphens
Do not use ampersands in the sheets or the file name. This is particularly important in the file name because an ampersand will error out the upload.
Duplicate Prevention
To ensure that no issues are encountered on a CUST upload, please ensure that there are no duplicate entries on a sheet. Also, please ensure that if you are replacing or updating an entry, you have confirmed it exists in CORE first.
Special Character Warnings/Invisible Character Warnings (Copy and Paste Issues)
Copying and pasting information from an outside document (i.e. PDF or Word document) may add additional special characters and characters that can’t be seen but add information that the mapper cannot process. The only way to safely pass this information from an outside document to your CUST spreadsheet would be to copy/paste it to a Notepad document, and then copy the information from the Notepad document to the CUST sheet. Special and invisible characters may prevent not only the affected sheet from processing but also all others that run after it.
Special and invisible characters may result in preventing not only the affected sheet from processing but all others that run after it.
Do Not Submit PDF Files
The ATS process is not set up to accept PDF files. Please do not submit them through the ATS upload process as they will not be processed and could slow down processing.
Page updated
Report abuse