Last updated on JUNE 28, 2017

Applies to:

Symptoms

On : 12.2.4 version, Legacy Data Collections

ACTUAL BEHAVIOR
---------------

The Pre-Processor assigns the shift_num and seq_num. The seq num should not be changed. The result is the work-day patterns days on and off get re-ordered. The ODS Load then loads the incorrect workday patterns.

Note, this customer was using ODBC direct connect from a DB2 database.


Example:
For Calendar AAAAA, Shift BBBBBB,

When looking at MSC_ST_WORKDAY_PATTERN table:
SEQ_NUM | DAYS_ON | DAYS_OFF
1       |   1     |    0
2       |   1     |    0
3       |   1     |    0
4       |   1     |    0
5       |   1     |    0
6       |   0     |    1
7       |   0     |    1

When looking at the MSC_WORKDAY_PATTERNS table:
SEQ_NUM | DAYS_ON | DAYS_OFF
4       |   1     |    0
5       |   1     |    0
6       |   0     |    1
58      |   1     |    0
59      |   1     |    0
60      |   1     |    0
61      |   0     |    1

Customer tried loading as support recommended.

For Calendar DDDDD, Shift EEEEEE
When looking at MSC_ST_WORKDAY_PATTERN table:
SEQ_NUM | DAYS_ON | DAYS_OFF
12      |   0     |    1
13      |   5     |    1

When looking at the MSC_WORKDAY_PATTERNS table:
SEQ_NUM | DAYS_ON | DAYS_OFF
1       |   5     |    1
15      |   0     |    1



EXPECTED BEHAVIOR
-----------------------
Work-day pattern days on and off do not get re-ordered after the Pre-Processor runs.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Load legacy Workday pattern
2. Run Pre-Processor

Cause