ISSUE: the Association WO Is Not Created on One Specific WO but Created on Separate WO

ISSUE: The Association WO is not created on one specific WO but created on separate WO’s (due to the numbering sequence of the service types). Issue reported under enhancement SAR 4657464.

WHY: When associations are done in OneWorld, some server-database combinations read the sequence of secondary associations in the opposite manner than a different server-database combination might. For example, with five service types: (P100, P200, P300, P400, P500) on one asset, where the primary service is P500, one system may read the associations in this order: P100, P200, P300, and P400, while the other system may read them in the reverse order: P400, P300, P200, and P100.

The graphs below illustrate this. The Primary Association is listed on the top row. Below each column are the Secondary Associations related to that column’s Primary Association.

Naming Method 1:

Primary: / P100 (500 hrs) / P200 (400 hrs) / P300 (300 hrs) / P400 (200 hrs) / P500 (100 hrs)
Secondary: / P200 (400 hrs) / P300 (300 hrs) / P400 (200 hrs) / P500 (100 hrs)
Secondary: / P300 (300 hrs) / P400 (200 hrs) / P500 (100 hrs)
Secondary: / P400 (200 hrs) / P500 (100 hrs)
Secondary: / P500 (100 hrs)

Naming Method 2:

Primary: / P500 (500 hrs) / P400 (400 hrs) / P300 (300 hrs) / P200 (200 hrs) / P100 (100 hrs)
Secondary: / P400 (400 hrs) / P300 (300 hrs) / P200 (200 hrs) / P100 (100 hrs)
Secondary: / P300 (300 hrs) / P200 (200 hrs) / P100 (100 hrs)
Secondary: / P200 (200 hrs) / P100 (100 hrs)
Secondary: / P100 (100 hrs)

The preferred workaround method is to set the Data Sequencing on the R12807 similar to the following:

A different workaround would be to use the opposite naming method than what is currently used (per the above graphs), so P500 (the primary) would be renamed to P100 etc.