To Initiate an EDI 835 Process Format Manually: - EDI 835 EOB Processor - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - external

EDI 835 EOB Processor
Platform
OnBase
Product
EDI 835 EOB Processor
Release
Foundation 23.1
License
  1. Open the EDI 835 Queue.
    1. From the OnBase Client, click Processing | EDI.
    2. With the EDI Queue window open, select the EDI Formats queue.
      Note:

      If you double click the Process Format, the Parse File pane will display the import file(s) to be processed. The Parse File pane displays all files that will be processed. It will vary based on the process setup and the files that exist in the process directory. If the file(s) to process are not in the directory, nothing will be displayed. (Multiple parse files appear if a wildcard was used to identify the data in the EDI 835 Processor.)

    3. Highlight the Process Format to be used for processing and right-click to obtain the EDI 835 processing menu.
  2. To schedule the EDI 835 process to run at another time, select Schedule Format. For more information on scheduling a process, see Scheduling Overview.
    To initiate processing immediately, select EDI Processor. The EDI Processors dialog box. is displayed.

    Process Format Option

    Description

    Store Document Indices

    Stores the processed documents in the database, along with their keywords and document name. This option is selected by default.

    Store Document Data Files

    Moves the data file to the configured disk group at the completion of processing. This option is selected by default.

    This check box must be enabled for EDI 835 processing to occur.

    Store Import File

    Stores a copy of the EDI 835 import file in OnBase for archival purposes.

    Create Auto Folder

    As files are processed, they are stored in the auto folder currently assigned to the Document Type.

    Note:

    This option is only functional when foldering has been configured.

    Test Only

    Selecting this option will allow the process to run without actually creating any documents. A Verification Report is displayed, but the process occurs only in memory.

    Note:

    This option will not create EDI 835 documents in OnBase.

    Default Document Date

    Allows you to enter a date to be used as the Document Date for the documents that are imported via this process.

    Selecting this option will override any other configured Document Date, unless it is pulling the date from the file.

    Default Keywords

    Allows for the selection of Keyword Types and Values to be added to the batch name.

    Process

    Initiates the selected EDI 835 process.
  3. Set the desired processing options and click Process.
    When complete, the batch will appear in the Awaiting Commit queue. Each batch is given a batch number, starting at 101. The batch number is available when viewing a document's properties.
  4. Once processed, the batch is routed to one of several queues, depending upon the success of the process and if the batch has been committed:

    • Incomplete Process

    • Awaiting Commit

    • Incomplete Commit

    • Committed

    Queue

    Description

    EDI Formats

    Displays the currently configured EDI 835 Process Formats for selection. EDI 835 processing is initiated from this queue.

    Process Jobs

    Displays the currently configured Process Jobs (configured in any of the import processors). Process jobs are initiated from this queue.

    Incomplete Process

    Displays the batches that were not successfully processed. This queue is displayed only when a batch resides in it.

    Batches are routed to this queue if an error occurred during processing. Batches in this queue should be purged from OnBase.

    Awaiting Commit

    Displays the batches that have been processed and are waiting to be committed. This queue is displayed only when a batch resides in it.

    Batches in this queue can be committed or purged from OnBase.

    Incomplete Commit

    Displays the batches that were not successfully committed. This queue is displayed only when a batch resides in it.

    Batches are displayed in this queue if an error occurred during commit.

    Committed

    Displays the batches that were successfully processed and committed. Batches in this queue cannot be purged from OnBase.

    In Progress

    Displays batches that need to have additional external processing performed. Batches can only be routed to this queue from the Committed queue. Batches in the In Progress queue are locked, and are only available to the user who routed them to this queue.