MSC_OP_REGIONS

This table is used by DOO-OP engine to store information about regions and zones that a party and party site lies with its hierarchy. For example party site lies in regions R1(coutry),R2(State) and zone Z1(North) so it will store these as 3 records with the levels of region and zones.

Details

  • Schema: FUSION

  • Object owner: MSC

  • Object type: TABLE

  • Tablespace: FUSION_TS_TX_DATA

Primary Key

Name Columns

MSC_OP_REGIONS_PK

PARTY_ID, PARTY_SITE_ID, REGION_ID, REGION_TYPE

Columns

Name Datatype Length Precision Not-null Comments
PARTY_ID NUMBER Yes PARTY_ID
CREATED_BY VARCHAR2 64 Yes Who column: indicates the user who created the row.
CREATION_DATE TIMESTAMP Yes Who column: indicates the date and time of the creation of the row.
PARTY_SITE_ID NUMBER Yes PARTY_SITE_ID
LAST_UPDATED_BY VARCHAR2 64 Yes Who column: indicates the user who last updated the row.
REGION_ID NUMBER Yes REGION_ID
REGION_TYPE NUMBER Yes REGION_TYPE
ZONE_FLAG VARCHAR2 1 Yes ZONE_FLAG
LAST_UPDATE_DATE TIMESTAMP Yes Who column: indicates the date and time of the last update of the row.
LAST_UPDATE_LOGIN VARCHAR2 32 Who column: indicates the session login associated to the user who last updated the row.
OBJECT_VERSION_NUMBER NUMBER 9 Yes Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.

Indexes

Index Uniqueness Tablespace Columns Status
MSC_OP_REGIONS_N1 Non Unique Default PARTY_ID, PARTY_SITE_ID Obsolete
MSC_OP_REGIONS_U1 Unique Default PARTY_ID, PARTY_SITE_ID, REGION_ID, REGION_TYPE