Examples in this section assume an original filename of MYFILE.EDI.
Data submitted |
Filename created by Submit |
TI | |
entire
transaction
|
TI_TransmissionFileName.ext_TransmissionID_STID.txt Example: TI_MYFILE.EDI_12345_222.txt An audit 834 will submit the entire transaction (ST-SE). |
Document |
TI_TransmissionFileName.ext_ SubmitterIDr_DocID.txt Example: TI_MYFILE.EDI_CLM111_111.txt |
TAMS | |
User specifies filename and extension |
Filename_guid.ext Example - User types MYFILENEW.EDI when submitting: MYFILENEW_ 6f1301df-959f-44c8-be42-d0b24c9354a5.EDI |
User specified filaneme, no extension |
Filename_guid.txt Example - User types MYFILENEW when submitting: MYFILENEW_ 6f1301df-959f-44c8-be42-d0b24c9354a5.txt |
User does not specify filename |
TransmissionFileName_guid.OriginalExt Example - User does not type a filename when submitting: MYFILE_ 6f1301df-959f-44c8-be42-d0b24c9354a5.EDI |
Where:
TransmissionFileName
The
transmission’s original filename; for multiple documents, the top selected
document in the task list.
TransmissionID Unique number identifying the imported file. For TI internal use and not visible in the user interface.
SubmitterID Data from file; See ApplicationDocTables.PDF. This is the SubmitterID from the file as it was imported. If you change the SubmitterID data in the form (the CLM01, for example), and then submit, this new value will not be used in the filename.
STID Unique number identifying the application document. For TI internal use. Not visible in the user interface.
DocID Unique document ID. See Document ID Column.
guid Unique randomly-generated number for this specific submit action. If the filename already contains a guid, due to a previous submission, it is replaced with a new one.
Characters that are invalid for a Windows file name are replaced with a dash.