This section describes the person object.
Person Data Model
The following data model illustrates the person object.
Person Table Names
|
Data Model Name |
Table Name |
Generated Keys |
Object Validation Batch Control |
Referential Integrity Validation Batch Control |
Key Assignment Batch Control |
Insertion Batch Control |
|
Person |
Yes CI_PER_K |
CIPVPERK |
CIPVPERI |
|||
|
Name |
No. The key is PER_ID plus a sequence number. |
CIPVPNMV |
CIPVPNMI |
|||
|
Person / Person |
No. The key is PER_ID1, PER_ID2, relationship type and start date. |
CIPVPPEV |
CIPVPPEI |
|||
|
Phone |
No. The key is PER_ID plus phone type. |
CIPVPPHV |
CIPVPPHI |
|||
|
Identifier |
No. The key is PER_ID plus identifier type. |
CIPVPIDV |
CIPVPIDI |
|||
|
Characteristic |
No. The key is PER_ID plus an edate and a char type. |
CIPVPRCV |
CIPVPRCI |
|||
|
Miscellaneous Address |
No. The key is PER_ID plus a sequence number. |
CIPVPSAV |
CIPVPSAI |
Person Suggestions
A person must have at least one row on the name table and at least one of the names must be marked as being the primary name.
A person must have at least one row on the identity table and at least one of the identities must be marked as being the primary ID.
The country and state are only necessary if the person has an override mailing address.
This maintenance object includes a character large object field that your organization may be using to capture implementation specific data as defined by your business objects. For records of this type, the process to insert the records to the staging table is responsible for populating the data in this CLOB as per the record's business object schema.