DBA Data[Home] [Help] [Dependency Information]


TABLE: PV.PV_PG_MEMBERSHIPS

Object Details
Object Name: PV_PG_MEMBERSHIPS
Object Type: TABLE
Owner: PV
FND Design Data: TablePV.PV_PG_MEMBERSHIPS
Subobject Name:
Status: VALID


PV_PG_MEMBERSHIPS table stores partner's program membership details. Once the enrollment request is approved by vendor, it gets converted to membership.
This table captures the membership specific data, like membership's active duration, and whether membership is still active or not.


Storage Details
Tablespace: TablespaceAPPS_TS_TX_DATA
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
PV_PG_MEMBERSHIPS_U1 NORMAL UNIQUE TablespaceAPPS_TS_TX_IDX ColumnMEMBERSHIP_ID
PV_PG_MEMBERSHIPS_U2 NORMAL UNIQUE TablespaceAPPS_TS_TX_IDX ColumnENRL_REQUEST_ID
PV_PG_MEMBERSHIPS_N1 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnPARTNER_ID
ColumnPROGRAM_ID
ColumnSTART_DATE
ColumnACTUAL_END_DATE
PV_PG_MEMBERSHIPS_N2 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnORIGINAL_END_DATE
PV_PG_MEMBERSHIPS_N3 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnPROGRAM_ID
Columns
Name Datatype Length Mandatory Comments
MEMBERSHIP_ID NUMBER
Yes Unique Identifier
OBJECT_VERSION_NUMBER NUMBER (9) Yes This column is used for locking purposes
PARTNER_ID NUMBER
Yes Foreign key to Partner Organization Relatiship Id for which membership is created
PROGRAM_ID NUMBER
Yes Foreign key to Program Id in which partner's membership is created.
START_DATE DATE
Yes Membership start date.
ORIGINAL_END_DATE DATE

Membership end date at the time of creation of membership
ACTUAL_END_DATE DATE

Membership actual end date
MEMBERSHIP_STATUS_CODE VARCHAR2 (30) Yes Membership Status - Lookup
STATUS_REASON_CODE VARCHAR2 (30)
Reason why membership status is changed - Lookup code
ENRL_REQUEST_ID NUMBER
Yes Foreign key to Enrollment Request Id that converted into membership
CREATED_BY NUMBER (15) Yes Standard WHO column
CREATION_DATE DATE
Yes Standard WHO column
LAST_UPDATED_BY NUMBER (15) Yes Standard WHO column
LAST_UPDATE_DATE DATE
Yes Standard WHO column
LAST_UPDATE_LOGIN NUMBER (15)
Standard WHO column
ATTRIBUTE1 VARCHAR2 (240)
Attribute
ATTRIBUTE2 VARCHAR2 (240)
Attribute
ATTRIBUTE3 VARCHAR2 (240)
Attribute
ATTRIBUTE4 VARCHAR2 (240)
Attribute
ATTRIBUTE5 VARCHAR2 (240)
Attribute
ATTRIBUTE6 VARCHAR2 (240)
Attribute
ATTRIBUTE7 VARCHAR2 (240)
Attribute
ATTRIBUTE8 VARCHAR2 (240)
Attribute
ATTRIBUTE9 VARCHAR2 (240)
Attribute
ATTRIBUTE10 VARCHAR2 (240)
Attribute
ATTRIBUTE11 VARCHAR2 (240)
Attribute
ATTRIBUTE12 VARCHAR2 (240)
Attribute
ATTRIBUTE13 VARCHAR2 (240)
Attribute
ATTRIBUTE14 VARCHAR2 (240)
Attribute
ATTRIBUTE15 VARCHAR2 (240)
Attribute
Query Text

Cut, paste (and edit) the following text to query this object:


SELECT MEMBERSHIP_ID
,      OBJECT_VERSION_NUMBER
,      PARTNER_ID
,      PROGRAM_ID
,      START_DATE
,      ORIGINAL_END_DATE
,      ACTUAL_END_DATE
,      MEMBERSHIP_STATUS_CODE
,      STATUS_REASON_CODE
,      ENRL_REQUEST_ID
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
FROM PV.PV_PG_MEMBERSHIPS;

Dependencies

[top of page]

PV.PV_PG_MEMBERSHIPS does not reference any database object

PV.PV_PG_MEMBERSHIPS is referenced by following:

SchemaAPPS
SynonymPV_PG_MEMBERSHIPS