LOY_PROG_ORG
It is Loyalty Program Organization Intersection table.
Details
-
Schema: FUSION
-
Object owner: LOY
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
LOY_PROG_ORG_PK |
LOY_PROG_ORG_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| LOY_PROG_ORG_ID | NUMBER | 18 | Yes | Who Column: Primary Key. | |
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of 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. | |
| CONFLICT_ID | NUMBER | 18 | Yes | Disconnected Mobile: this value is used to guarantee the uniqueness of the row when duplicates are created in different databases (i.e. mobile databases or the server). | |
| ACRL_VALID_PD_LEN | NUMBER | The maximum time gap (after activity date) upto which a partner is allowed to send accruals | |||
| ACRL_VALID_UOM_CODE | VARCHAR2 | 30 | Accrual Validity UOM | ||
| ALLW_NEGATIVE_FLAG | VARCHAR2 | 1 | Yes | indicates if the partner is allowed to go negative | |
| BILLING_TYPE_CODE | VARCHAR2 | 30 | Indicates the Partner Billing Type. Possible values can be the codes for "Pre Paid" and Post Paid". | ||
| ENABLE_BILLING_FLAG | VARCHAR2 | 1 | Yes | Indicates if the Loyalty Program Partner should be billed. | |
| CREDIT_LIMIT | NUMBER | For partners that are allowed to go negative, this is the threshold of the points that they can go negative | |||
| MIN_ORDER_QTY | NUMBER | Minimum Order quantity | |||
| ORG_EXT_ID | NUMBER | 18 | Yes | Associated Loyalty Partner under the Loyalty Program | |
| PRECALC_ACRL_FLAG | VARCHAR2 | 1 | Yes | Determines whether partner sends precalcualted accruals or not | |
| PRICING_RULE_ID | NUMBER | 18 | Pricing Rule | ||
| PROGRAM_ID | NUMBER | 18 | Yes | Program Id | |
| REORDER_LIMIT | NUMBER | If the partners' available points fall below this level, reordering should be initiated | |||
| RET_BEFORE_DAYS | NUMBER | Denotes the number of days before which the Goods might be returned by the customer | |||
| SKIP_ACRL_VAL_FLAG | VARCHAR2 | 1 | Yes | Flag at the Prog Org level to force basic validations for transaction processing. | |
| VALDT_DISPUTE_USR | VARCHAR2 | 30 | Validate Dispute User Submit To Validate Dispute User Submit To | ||
| VALID_DISPUTE_FLAG | VARCHAR2 | 1 | Yes | In case of dipute lodged by member, this flag will determine whether partner validation is required or not |
Foreign Keys
| Table | Foreign Table | Foreign Key Column |
|---|---|---|
| LOY_PROG_ORG | loy_program | PROGRAM_ID |
| LOY_PROG_ORG | hz_parties | ORG_EXT_ID |
| loy_prog_partner_pnttype | loy_prog_org | PROG_PARTNER_ID |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| LOY_PROG_ORG_F2 | Non Unique | Default | ORG_EXT_ID |
| LOY_PROG_ORG_U1 | Unique | FUSION_TS_TX_DATA | LOY_PROG_ORG_ID |
| LOY_PROG_ORG_U2 | Unique | Default | PROGRAM_ID, ORG_EXT_ID, CONFLICT_ID |