REFERENCED BY
| AC14.6 | AC51.1 |
| AC13.1 | AC13.7 | AC13.8 | AC135 | AC213 | AC300 |
| AC510 | AC560 | MX202 |
| FIELD NAME | DESCRIPTION/VALID VALUES | UPDATED BY | ||||||
|---|---|---|---|---|---|---|---|---|
| MXD-OBJ-ID Element: Obj Id | Numeric 12 This is the object identifier. It is used to relate commitments or posted transactions back to the originating subsystems. Each subsystem record that is updated as a commitment or posted transaction is assigned an object identifier. The object identifier is maintained in the subsystem files and in the Activity Commitments Detail and Activity Transaction files. The object identifier is a unique key used to drill back from Activity Management to the subsystems. |
|
||||||
| MXD-MATRIX-CAT Element: Matrix Cat | Alpha 12 Attribute name assigned to an object (like accounting unit) to track additional information. Attribute values may then be used in selection and sorting for report and analysis. |
|
||||||
| MXD-MX-VALUE Element: Mx Value | Alpha 32 The attribute value. |
|
||||||
| MXD-EFFECTIVE-DATE Element: Effective Date | Numeric 8 (yyyymmdd) The date a vendor's prices will be in effect. |
|
| NAME | KEY FIELDS | DESCRIPTION / SUBSET CONDITION | USED IN | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MXDSET1 |
OBJ-ID MATRIX-CAT EFFECTIVE-DATE |
|
| ||||||||||||||||
| MXDSET2 |
MATRIX-CAT EFFECTIVE-DATE OBJ-ID |
|
| ||||||||||||||||
| MXDSET4 |
OBJ-ID MATRIX-CAT EFFECTIVE-DATE* |
|
| ||||||||||||||||
All trademarks and registered trademarks are the property of their
respective owners.