Understanding the Labor Distribution Value Import and the Discrepancy Report

Note: Your Staff Manager configuration may not include this optional application. To add this application to your configuration, contact your Clinical Consultant or Client Advocate.

If you have marked an Effort Distribution field as Is Imported on the Field and Notifications Setup page, the code values for that field are populated and maintained with values received from the Labor Distribution Value Import. The Labor Distribution Value Import is a comma separated values file (.csv) that takes valid labor distribution accounting codes from a client-approved source and brings them into Staff Manager.

Staff Manager maintains valid values for the Effort Distribution interface through this import. As a result, there are times when a value saved as part of an Effort Distribution Value Set and connected to a Staff Manager task is updated or replaced. In addition to sending data to the Staff Manager database, the Labor Distribution Value Import also performs three validation tests in Staff Manager, as described below. If the import validation tests identify any data inconsistencies, the interface creates a Clairvia Discrepancy Report (CDR).

The Validation Tests

The first test checks that all values associated with tasks are still valid after the Labor Distribution Value Import updates them. For example, assume a task in Staff Manager has a Department Code value of 111 in its value set. Infor Labor Distribution then deletes the 111 Department Code value because it has expired. When the import runs and the interface cannot find the 111 Department Code, it flags the associated value set in the CDR.

The second test checks that the values within each defined value set are still valid for the duration of the effective date of the task association to its value set. Each task in a value set has effective dates. When the import updates the labor distribution values, it is possible that a value within the task set has expired with the date range of the task and its value set.

For example, assume your organization has a National Institutes of Health (NIH) grant. The NIH Neuro Grant Time task in Staff Manager has effective dates of January 1, 2014, to December 31, 2015. The task is also associated with the following values:

• GL Company-20345
• Posting Accounting Unit (PAU) - 5678
• Activity - 12345

The Activity value of 12345 also has an effective range of January 1, 2014, to December 31, 2015. Unfortunately, the NIH Neuro Grant team was unable to produce the expected results, so the project funding now ends on December 31, 2014. The Labor Distribution Value Import updates the effective date range for Activity 12345 to end on December 31, 2014. This conflicts with the task in Staff Manager, which as an associated value with the effective dates of January 1, 2014, to December 31, 2015. The CDR flags this task so that you can adjust the effective dates for the task.

The third test checks that tasks associated with an Effort Distribution value set used in the current or next bi-weekly payroll period are not scheduled outside that value set's effective dates. For example, the value set effective dates for our hypothetical NIH Neuro Grant task are January 1, 2014, to December 31, 2014. Dr. Goode is scheduled for this task on January 15, 2015, and January 18, 2014, after the value set effective date. When the import runs for the pay period prior to these dates, it flags Dr. Goode's scheduled tasks for action on the CDR. You can use the CDR to identify potential problems in the near future and to minimize the chance of sending task work hours with a value set that Infor Labor Distribution cannot accept.

When the interface finds errors, the CDR appears as in the following example:

If there are no issues detected during the validation run, the CDR displays the statement No Effort Distribution Value Issues detected during validation run.

Related Topics