Posting and Validating Data Collection Transactions

Your data collection solution uploads transaction data into the SyteLine data collection tables. Depending on options you set in the Data Collection Parameters form, the data is either automatically posted to the SyteLine database, or it remains in the error processing table until you manually validate and post the transactions through the appropriate Error Processing forms.

You can include jobs with co-product mixes in the data collection tables.  By-products are not supported for data collection solutions.

To post and validate data collection transactions, use these steps:

  1. Set up the data collection options on the General tab of the Data Collection Parameters form, including these settings:
  2. On the Background tab of the Data Collection Parameters form, for each selected Auto-Post option, click Background Queue. Set the frequency and starting/ending times for the background task to match your shift codes.

    Example: Set the frequency to Daily, with an interval of 5 minutes. Set the starting time one half hour before the start of your first shift, and the ending time one hour after the end of your last shift. For a 24 hour shop, set the starting time to 12:00:00 a.m. and ending time to 11:59:59 p.m. If your company has 2 shifts -- the first shift works 7:00 a.m. to 3:00 p.m. and second shift works 3:00 p.m. to 11:00 p.m. -- then set the starting time to 6:00 a.m. (or 6:30 a.m., depending on how early the employees start entering DC transactions) and the ending time to 11:59 p.m.
  3. Use a data collection solution to create data collection transactions and place them in the SyteLine data collection tables.
  4. Review and post the data collection transactions in the appropriate Error Processing form:

    NOTE: For transaction types that are set to Auto-Post and have background tasks defined through the Data Collection Parameters form, validated transactions are automatically posted to the appropriate SyteLine file, and the Post button is disabled on the Error Processing form. For these types of transactions, you can only view transactions that contain errors in the Error Processing forms. You can also check the Background Task History for problems that might have occurred during auto-posting.

    When you post the transactions from the Error Processing form, the system defaults to the current date. Specify the date through which to post transactions or accept the displayed date.

    NOTE: Transactions for items flagged obsolete or slow-moving may not post.

  5. In the Error Processing form, review any data collection transactions that did not post. An error message is displayed with each unposted transaction to indicate why the transaction did not post.

    If a transaction has an Unposted status after posting is performed, but there is no error associated with it, the end time is within the Job Grace Period specified on the Data Collection Parameters form, and the transaction can still be adjusted.

  6. Correct the errors. When you update the error transaction, the status changes to Pending.
  7. After all or most of the transactions that were in error have been corrected, run the Validate Data Collection Transactions utility, selecting the type of transactions that were corrected. The utility forces the same interactive validation as if the data were being entered for the first time. You can run the utility manually for specific types of transactions, or you can schedule it to run at certain times. The transaction will post during the next posting process.
  8. Fix any data collection transaction errors and repost the transactions.
  9. To delete any or all records in the Error Processing forms, use the corresponding Purge utility.

About Auto-Posting and Data Collection Background Tasks

On the Background Task Definitions form, you can see all of the available DCPost... tasks.  Notice that they all have Concurrency set to 1, which means that only one instance of this task can run at a time. Do not change that setting, because it prevents different instances of the same background posting tasks from  running simultaneously if you accidentally set the task run times to overlap.

To determine if a recurring data collection background task is set up to run, go to the Active Background Tasks form and look for these background tasks that are associated with the Auto-Post options:

Post Option Background Task
Auto-Post Receiving DCPostPurchaseOrderReceiving
Auto-Post Shipping DCPostCustomerOrderShipping
Auto-Post Cycle Count DCPostCycleCounting
Auto-Post Misc Issue/Receipt Qty Adjust DCPostMiscIssue/ReceiptandQuantityAdjust
Auto-Post Quantity Move DCPostQuantityMove
Auto-Post Job Material DCPostJobMaterial
Auto-Post Job Receipt DCPostJobReceipt
Auto-Post Transfer Ship DCPostTransferShip
Auto-Post Transfer Receipt DCPostTransferReceipt
Auto-Post Mfg Labor DCPostMfgLabor
Auto-Post Time/Attendance DCPostTime/Attendance
Auto-Post Production Schedule DCPostProductionSchedule
Auto-Post JIT DCPostJIT
Auto-Post Work Center Material DCPostWorkCenterMaterial

 

NOTE: The Auto-Post Job Transactions option does not have its own background task, since it is used to turn on more processing for the Auto-Post Manufacturing Labor task.

To find out the times and dates when the task is scheduled to run, look at the SQL job in the database.

Stopping Auto-Posting

To stop auto-posting (temporarily or permanently):

  1. In the Active Background Tasks form, select the appropriate DCPost... task and delete it.  
  2. In the Data Collection Parameters form, clear the check box next to the appropriate Auto-Posting option.

 

Related Topics

About the Error Processing Forms

About Data Collection Transaction Validation

About Co-Products and By-Products

About Machine Transactions (Data Collection)

About Multi-Job Transactions