This page (revision-8) was last changed on 26-Nov-2021 10:22 by JMyers

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
8 26-Nov-2021 10:22 4 KB JMyers to previous
7 26-Nov-2021 10:22 4 KB JEscott to previous | to last
6 26-Nov-2021 10:22 4 KB JEscott to previous | to last
5 26-Nov-2021 10:22 4 KB JEscott to previous | to last
4 26-Nov-2021 10:22 3 KB JEscott to previous | to last
3 26-Nov-2021 10:22 3 KB JEscott to previous | to last
2 26-Nov-2021 10:22 1 KB JEscott to previous | to last
1 26-Nov-2021 10:22 1 KB JEscott to last

Page References

Incoming links Outgoing links
INF_CV_ENTITIES
INF_CV_ENTITIES

Version management

Difference between version and

At line 1 changed one line
!!!Alias: IVDEN
!!!Alias: [IVDEN]
At line 3 removed 2 lines
\\
Date sensitive details about an entity.
At line 4 added 5 lines
The INF_CV_ENTITIES table is used to import entity codes and their attendant data into the software data structures. The Entity Code is a user-defined code that uniquely identifies the entity. It is often an abbreviation of the name or initials, or an acronym by which the organization refers to itself.
Tables loaded:
*[P2K_CM_ENTITIES] (first record for each position code only)
*[P2K_CM_ENTITY_DETAILS] (first record and subsequent effective splits)
At line 8 changed 21 lines
||Column name||Data Type / Size||Domain||Mand.||Notes
|[ID]|Number(10)|[ID]| |
|[ENTITY_CODE]|Varchar2(16)|[CODE]|Y|
|[GL_COMPANY_CODE]|Varchar2(16)|[CODE]| |
|[PARENT_ENTITY]|Varchar2(16)|[CODE]| |
|[STANDING]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[EFFECTIVE]|Date()|[EFFECTIVE]| |
|[EXPIRY]|Date()|[EXPIRY]| |
|[CHANGE_CODE]|Varchar2(16)|[CODE]| |
|[ENTITY_NAME]|Varchar2(50)|[VARCHAR50|VARCHARnn]|Y|
|[LOCATION_CODE]|Varchar2(16)|[CODE]| |
|[INDUSTRY_CODE]|Varchar2(16)|[CODE]| |
|[LEGISLATION]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[LANGUAGE_CODE]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[CURRENCY]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[DUNS_NUMBER]|Varchar2(16)|[VARCHAR16|VARCHARnn]| |
|[WEB_ADDRESS]|Varchar2(200)|[VARCHAR200|VARCHARnn]| |
|[CREATE_DATE]|Date()|[DATE]| |
|[CREATE_USER]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[CHANGE_DATE]|Date()|[DATE]| |
|[CHANGE_USER]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
||Column name||Data Type / Size||Mand.||Notes
|[ID]|Number(10)| |Used internally to define a unique identification for the record. This field would not be loaded.
|[ENTITY_CODE]|Varchar2(16)|Y|Validation: Must be a unique entity code.
|[GL_COMPANY_CODE]|Varchar2(16)| |Validation: Must be a valid [GL_COMPANY_CODE] defined on [P2K_CM_GL_COMPANIES]. Derivation: Will be derived from the [GL_COMPANY_CODE] for the [PARENT_ENTITY|ENTITY_CODE], if a [PARENT_ENTITY|ENTITY_CODE] has been defined.
|[PARENT_ENTITY|ENTITY_CODE]|Varchar2(16)| |Validation: Must be a valid [ENTITY_CODE] previously defined on [P2K_CM_ENTITIES].
|[STANDING]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_STANDING]. Suggestion: Normally, you would only load active entities, so you could populate this field with a constant value of “A”.
|[EFFECTIVE]|Date()| |Validation: Must be a valid date format. Suggestion: If you are not loading multiple date-effective records for the same entity code, then populate this field with a constant ‘01-Jan-0001’ which represents the beginning of time.
|[EXPIRY]|Date()| |Validation: Must be a valid date format, with a date after the effective date. Suggestion: If you are not loading multiple date-effective records for the same entity code, then populate this field with a constant ‘31-Dec-3999’ which represents the end of time
|[CHANGE_CODE]|Varchar2(16)| |Validation: The Change Code provided must be defined on [P2K_CM_CHANGE_REASONS]
|[ENTITY_NAME]|Varchar2(50)|Y|
|[LOCATION_CODE]|Varchar2(16)| |Validation: Must be a valid [LOCATION_CODE] defined on [P2K_CM_LOCATIONS]. Derivation: Will be derived from the [LOCATION_CODE] for the [PARENT_ENTITY|ENTITY_CODE], if a [PARENT_ENTITY|ENTITY_CODE] has been defined.
|[INDUSTRY_CODE]|Varchar2(16)| |Validation: Must be a valid INDUSTRY_CODE defined on [P2K_CM_INDUSTRIES]. Derivation: Will be derived from the [INDUSTRY_CODE] for the [PARENT_ENTITY|ENTITY_CODE], if a [PARENT_ENTITY|ENTITY_CODE] has been defined.
|[LEGISLATION]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_LEGISLATION]. Derivation: Will be derived from the [LEGISLATION] for the [PARENT_ENTITY|ENTITY_CODE], if a [PARENT_ENTITY|ENTITY_CODE] has been defined. If you do not provide a value for this field, or a [PARENT_ENTITY|ENTITY_CODE], then a value of ‘00’ will be defaulted. Suggestion: Normally, you could populate this field with a constant value representing the legislation.
|[LANGUAGE_CODE]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description. Derivation: Will be derived from the [LANGUAGE_CODE] for the [PARENT_ENTITY|ENTITY_CODE], if a [PARENT_ENTITY|ENTITY_CODE] has been defined. Suggestion: Most users will load this field with “ENG” for English.
|[CURRENCY]|Varchar2(30)| |Validation: Must be either a valid lexicon code or a valid lexicon description from [X_CURRENCY]. Derivation: Will be derived from the [CURRENCY] for the [PARENT_ENTITY|ENTITY_CODE], if a [PARENT_ENTITY|ENTITY_CODE] has been defined.
|[DUNS_NUMBER]|Varchar2(16)| |
|[WEB_ADDRESS]|Varchar2(200)| |
|[CREATE_DATE]|Date()| |This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
|[CREATE_USER]|Varchar2(30)| |This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
|[CHANGE_DATE]|Date()| |This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
|[CHANGE_USER]|Varchar2(30)| | This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
----
![Notes|Edit:Internal.INF_CV_ENTITIES]
[{InsertPage page='Internal.INF_CV_ENTITIES' default='Click to create a new notes page'}]
This page (revision-8) was last changed on 26-Nov-2021 10:22 by JMyersTop