1. Outbound Files Ready for downloading display when you open File Registry.

Ready outbound files have not been downloaded or exported to your system. Files already downloaded or e-mailed from a Distribution List have a status of Complete.

Note:  Reports requested online with a Delivery Type of E-mail Notification or File Registry are considered Outbound files.  Online reports too large to send as an E-Mail Attachment (2MB) are found under Outbound.

2. If desired, enter search criteria to find specific files.

For example:

1. • Select Complete to list files that have finished initial processing, including exports and files e-mailed from a Distribution List.

1. • Enter a File Registration Date Range in which the file was processed for export from or import into Park City Group.

   • Select a File Transfer Method based on whether the file was e-mailed or sent directly via AS2, FTP, or held for download.

Note:  All files not physically e-mailed can be found under the Direct File Transfer option.  This includes files for which you received an e-mail notice stating the file size was too large to send.

1. • Select Inbound to list files imported into Park City Group.

   • For other options, see the Advanced Search Criteria listed below.

3. If search criteria was entered, click Find.

4. Choose from the steps under Work with your Files.

• Outbound

Also called "Exports", these are files generated by Park City Group for the end user.  Outbound files include:

Files ready to download, including batch reports, error logs, and pricebook files.

Exports sent to the client via AS2 or FTP.

Reports requested online with a Delivery Type of E-mail Notification or File Registry.  Online reports too large to send as an E-mail Attachment (2MB) can also be found under Outbound.

• Inbound

Also called "Imports", these are sent by a client for processing into Park City Group.  For example, item or cost data, deliveries, sales.  Inbound files include:

Files sent to Park City Group via AS2 or FTP.

Files uploaded online.

• Include Subordinate Business Units

Displays only if your Business Unit (BU) has "Child" or subordinate BUs, and you are logged in as the "Parent" BU. For example, a Parent headquarters and its Child divisions. Select this to include files associated with the subordinates.

• Title

Enter part of the file's report name, using asterisks as wild cards.  For example, *cost report*.  The Title field and other fields are NOT case sensitive.  You can enter *cost* or *Cost*.

• File Name

Enter part of the filename, using asterisks as wild cards.  For example, cst* or *.csv.

• Containing Text

Enter any alpha-numeric data contained within the file(s).  Use percent signs % as wild cards (NOT asterisks).  For example, search for a store name such as %Mayberry% or an EDI control number.  This field is not case sensitive.

Important Note:  This option will search up to 100 files.  If the search criteria is too broad, meaning it would display more than 100 results, the message Error!  Please refine your search criteria appears.  Enter a Date Range, part of a report Title, or other criteria to narrow down the search.

• Request Number

The job ID generated by Park City Group to track batch-processed files can be used as search criteria.  This can be found in batch processing logs and other reports.  The number must be entered exactly.  Wild cards cannot be used.

• File Registration Date Range

Enter the date range in which the file was generated or the report ran.  For inbound files, this is the date it was imported into Park City Group.

If you leave the To field blank, all files created on or after the first date are listed.  Enter dates as MMDDYY or MM/DD/YYYY.

• File Status:  Ready   Complete   Failed   Expired

Search by whether files have completed initial processing, such as to see EDI 852s that have exported or files awaiting download.

Ready:  Files ready for the next step in processing.  These include:

-- Outbound files ready for export via AS2 or FTP.  

-- Outbound files ready to be downloaded.

-- Inbound files received into Park City Group and awaiting processing.

Complete:  Files that have finished initial processing.  These include:

-- Files exported via AS2 or FTP.

-- Files (usually reports) e-mailed to a Distribution list.  

-- Files that have been downloaded at least once (but can be downloaded again).

Failed:  Files that did not complete processing.  For example, a file that failed to post to an FTP site.  Note that e-mailed files sent to out-of-date e-mail addresses will show as Complete, not Failed.

Expired:  Files older than the retention rate set for your Business Unit.  The default is 20 days.  These files can still be downloaded.  

• File Size (Bytes)

You can include or exclude files in your search by entering a file size in bytes (characters).  Use the >= and <= options to select whether the file is greater than (or equal to) or less than (or equal to) the size you enter.

For example, to search for a report file that was placed on File Registry because it was over 2 MB, select >= and enter 2000000 (six zeros).  EDI Functional Acknowledgements (997s) are usually 200 to 300 bytes.  Sales or Delivery files are generally over 1000 bytes.

• File Transfer Method

Select whether the file was e-mailed or sent directly via AS2 or FTP.  All files not physically e-mailed can be found under Direct File Transfer.  This includes files for which you received notice that the file size was too large to send, as well as files held for download.

• Order By

Use this drop-down before clicking Find to sort the results.  The default is by date, most recent files first (Descending).

• Output Limit

Select how many files (rows) to display in a single page on-screen.