This chapter contains instructions on creating Oracle BI Publisher reports on data in the OAAM database schema.
You may want to refer to the Oracle Adaptive Access Manager Database Schema chapter in the Oracle Fusion Middleware Reference for Oracle Identity Management. It describes the OAAM schema, which is useful when building custom reports. This section discusses advanced report creation.
This chapter contains the following sections:
Refer to the following sections to create OAAM reports from the Oracle Adaptive Access Manager database. In code listings OAAM table and field names are bold and italic.
For instructions on creating a new report, see Oracle Business Intelligence Publisher Report Designer's Guide.
Several fields in many tables are numeric type codes, which correspond to OAAM User Defined Enums. For more information about OAAM User Defined Enums, see Chapter 7, "Using the OAAM Extensions Shared Library to Customize OAAM." Information on how to map those type codes to readable names is presented in this section.
There are two methods for resolving these names, and the one to choose depends on whether you must display English only or you must display internationalized strings.
To display a readable string rather than a type code value in the report output, the report writer will need to add a join to the tables that hold the User Defined Enums, and then add the field to the select clause.
The following SQL code shows how to add the join criteria to the query:
SELECT …
FROM …
LEFT OUTER JOIN (
SELECT enumElement.num_value, enumElement.label
FROM v_b_enum enum
INNER JOIN v_b_enum_elmnt enumElement ON on enum.enum_id =
enum_element.enum_id
WHERE enum.prop_name = 'enum name') alias
ON table.type_field = alias.num_value
…
In this code, table.type_field is the field containing a type code value that you want to replace with a string. Alias is the name you are giving the inner select clause. Finally, enum_name is the property name of the User Defined Enum.
To display in the report, you must add alias.label to the select clause.
The following SQL code shows how to add the join criteria to the query:
SELECT …
FROM …
LEFT OUTER JOIN (
SELECT t0.config_value, element.num_value
FROM v_b_config_rb t0
INNER JOIN (
SELECT enum_element.num_value, enum_element.str_value, enum.prop_name
FROM v_b_enum enum
INNER JOIN v_b_enum_elmnt enum_element ON enum.enum_id =
enum_element.enum_id
WHERE enum.prop_name = 'enum name') element
ON t0.config_name=element.prop_name || '.' || element.str_value ||
'.name'
WHERE t0.locale_id = (
SELECT locale_id FROM v_b_locale
WHERE language = substr(:xdo_user_ui_locale, 1, 2)
AND country = substr(:xdo_user_ui_locale, 4, 2)
AND (substr(:xdo_user_ui_locale, 1, 2) in ('de', 'en', 'es',
'fr', 'it', 'ja', 'ko')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'pt' AND
substr(:xdo_user_ui_locale, 4, 2) = 'BR')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'zh' AND
substr(:xdo_user_ui_locale, 4, 2) IN ('CN', 'TW')))
UNION SELECT locale_id FROM v_b_locale
WHERE language = substr(:xdo_user_ui_locale, 1, 2)
AND NOT EXISTS(SELECT locale_id FROM v_b_locale
WHERE language = substr(:xdo_user_ui_locale, 1, 2)
AND country = substr(:xdo_user_ui_locale, 4, 2))
AND country IS NULL
AND (substr(:xdo_user_ui_locale, 1, 2) in ('de', 'en',
'es', 'fr', 'it', 'ja', 'ko')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'pt' AND
substr(:xdo_user_ui_locale, 4, 2) = 'BR')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'zh' AND
substr(:xdo_user_ui_locale, 4, 2) IN ('CN', 'TW')))
UNION SELECT locale_id FROM v_b_locale
WHERE language = 'en'
AND NOT (substr(:xdo_user_ui_locale, 1, 2) in ('de', 'en',
'es', 'fr', 'it', 'ja', 'ko')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'pt' AND
substr(:xdo_user_ui_locale, 4, 2) = 'BR')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'zh' AND
substr(:xdo_user_ui_locale, 4, 2) IN ('CN', 'TW'))))
ORDER BY t0.config_name) alias
ON table.type_field = alias.num_value
…
In this code, table.type_field is the field containing a type code value that you want to replace with a string. Alias is the name you want to give the inner select clause. Finally, enum_name is the property name of the User Defined Enum.
To display in the report, you must add alias.config_value to the select clause.
Add parameters to your report definition to enable your users to interact with the report and specify the data of interest from the data set.
To allow a user to select from a list of readable strings representing type codes, the report writer will need to create a List of Values (LOV) from a query on the User Defined Enums tables, filtered by the enum name.
The following listing shows how to write the query to populate the list of values.
SELECT enumElement.label, enumElement.num_value
FROM v_b_enum enum
INNER JOIN v_b_enum_elmnt enumElement ON on enum.enum_id =
enumElement.enum_id
WHERE enum.prop_name = 'enum name'
ORDER BY enumElement.label
The following listing shows how to filter the report based on this LOV.
WHERE … AND (:parameter IS NULL OR :parameter = table.type_field)
In these listings, enum_name is the property name of the User Defined Enum, table.type_field is the field containing a type code value that you want to replace with a string, and parameter is the named parameter. Review the Oracle BI Publisher User's Guide for information about creating and setting up report parameters.
The following listing shows how to write the query to populate the list of values.
SELECT t0.config_value, element.num_value
FROM v_b_config_rb t0
INNER JOIN (
SELECT enum_element.num_value, enum_element.str_value, enum.prop_name
FROM v_b_enum enum
INNER JOIN v_b_enum_elmnt enum_element ON enum.enum_id =
enum_element.enum_id
WHERE enum.prop_name = 'enum name') element
ON t0.config_name=element.prop_name || '.' || element.str_value || '.name'
WHERE t0.locale_id = (
SELECT locale_id FROM v_b_locale
WHERE language = substr(:xdo_user_ui_locale, 1, 2)
AND country = substr(:xdo_user_ui_locale, 4, 2)
AND (substr(:xdo_user_ui_locale, 1, 2) in ('de', 'en', 'es', 'fr',
'it', 'ja', 'ko')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'pt' AND substr
(:xdo_user_ui_locale, 4, 2) = 'BR')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'zh' AND substr(:xdo_
user_ui_locale, 4, 2) IN ('CN', 'TW')))
UNION SELECT locale_id FROM v_b_locale
WHERE language = substr(:xdo_user_ui_locale, 1, 2)
AND NOT EXISTS(SELECT locale_id FROM v_b_locale
WHERE language = substr(:xdo_user_ui_locale, 1, 2)
AND country = substr(:xdo_user_ui_locale, 4, 2))
AND country IS NULL
AND (substr(:xdo_user_ui_locale, 1, 2) in ('de', 'en', 'es',
'fr', 'it', 'ja', 'ko')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'pt' AND
substr(:xdo_user_ui_locale, 4, 2) = 'BR')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'zh' AND
substr(:xdo_user_ui_locale, 4, 2) IN ('CN', 'TW')))
UNION SELECT locale_id FROM v_b_locale
WHERE language = 'en'
AND NOT (substr(:xdo_user_ui_locale, 1, 2) in ('de', 'en', 'es',
'fr', 'it', 'ja', 'ko')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'pt' AND substr(:xdo_
user_ui_locale, 4, 2) = 'BR')
OR (substr(:xdo_user_ui_locale, 1, 2) = 'zh' AND substr(:xdo_
user_ui_locale, 4, 2) IN ('CN', 'TW'))))
ORDER BY t0.config_name
The filtering is performed in the same manner as the English Only version.
The OAAM database schema includes tables that map IP address ranges to location data including city, state, and country. The relevant tables are VCRYPT_IP_LOCATION_MAP, VCRYPT_CITY, VCRYPT_STATE, and VCRYPT_COUNTRY. Many tables contain IP addresses, and VCRYPT_IP_LOCATION_MAP contains foreign keys to each of VCRYPT_CITY, VCRYPT_STATE, and VCRYPT_COUNTRY.
In OAAM, IP addresses are stored as long numerals. The following listing shows how join a table containing an IP address to the VCRYPT_IP_LOCATION_MAP.
SELECT ... FROM vcrypt_tracker_usernode_logs logs INNER JOIN vcrypt_ip_location_map loc ON ( logs.remote_ip_addr >= loc.from_ip_addr AND logs.remote_ip_addr <= loc.from_ip_addr )
For user input and display purposes, you will typically want to use the standard four-part IP address. The following listing shows how to display a numeric IP address as a standard IP, where ipField is the field or parameter containing the numeric IP address you want to display.
…
to_char(to_number(substr(to_char(ipField, 'XXXXXXXX'), 1, 3), 'XX')) || '.' ||
to_char(to_number(substr(to_char(ipField, 'XXXXXXXX'), 4, 2), 'XX')) || '.'
||
to_char(to_number(substr(to_char(ipField, 'XXXXXXXX'), 6, 2), 'XX')) || '.'
||
to_char(to_number(substr(to_char(ipField, 'XXXXXXXX'), 8, 2), 'XX'))
...
The following listing shows how to convert a standard IP address to the long numeric format.
… to_number(substr(ipField, 1, instr(ipField, '.')-1))*16777216 + to_number(substr(ipField, instr(ipField, '.', 1, 1)+1, instr(ipField, '.', 1, 2)-instr(ipField, '.', 1, 1)-1))*65536 + to_number(substr(ipField, instr(ipField, '.', 1, 2)+1, instr(ipField, '.', 1, 3)-instr(ipField, '.', 1, 2)-1))*256 + to_number(substr(ipField, instr(ipField, '.', 1, 3)+1))
Sessions and alerts exist in the VCRYPT_TRACKER_USERNODE_LOGS and VCRYPT_ALERT tables, respectively. They join to each other through the REQUEST_ID field, and they each join to the geolocation data through the VCRYPT_IP_LOCATION_MAP table through the BASE_IP_ADDR field.
The session table and the alert table have several type code fields that may be translated into readable text by following the instructions to look up the user defined enums by name.
Table 23-1 lists the type code fields and the names of the user defined enum in VCRYPT_TRACKER_USERNODE_LOGS.
Table 23-1 VCRYPT_TRACKER_USERNODE_LOGS
| Field Name | User Defined Enum Name |
|---|---|
|
AUTH_STATUS |
auth.status.enum |
|
AUTH_CLIENT_TYPE_CODE |
auth.client.type.enum |
Table 23-2 lists the type code fields and the name of the user defined enums in VCRYPT_ALERT.
This report will show a list of sessions, with user id, login id, auth status, and location. To start with, you will need to create two date parameters, fromDate and toDate. The query will look like the following:
SELECT s.request_id, s.user_id, s.user_login_id, auth.label, country.country_name, state.state_name, city.city_name FROM vcrypt_tracker_usernode_logs s INNER JOIN vcrypt_ip_location_map loc ON s.base_ip_addr = loc.base_ip_addr INNER JOIN vcrypt_country country ON loc.country_id = country.country_id INNER JOIN vcrypt_state loc ON loc.state_id = country.state_id INNER JOIN vcrypt_city city ON loc.city_id = city.city_id LEFT OUTER JOIN ( SELECT enumElement.num_value, enumElement.label FROM v_b_enum enum INNER JOIN v_b_enum_elmnt enumElement ON on enum.enum_id = enum_element.enum_id WHERE enum.prop_name = 'auth.status.enum') auth ON s.auth_status = auth.num_value WHERE (:fromDate IS NULL OR s.create_time >= :fromDate) AND (:toDate IS NULL OR s.create_time <= :toDate) ORDER BY s.create_time DESC
BI Publisher offers several options for designing templates for your reports. For instructions on designing templates, see Oracle Business Intelligence Publisher Report Designer's Guide.
This section explains how you can build transaction reports. It contains the following topics:
To get the Transaction Definition key and Entity Definition keys, follow these steps:
Log in to OAAM Admin and navigate to the Transactions menu and search for the transaction definitions you are interested in.
Go to the General tab and write down the Definition Key of the transaction. This is the "Transaction Definition Key" of the transaction.
Go to the Entities tab of the transaction and write down the distinct list Entity Name.
Choose the Entities menu option to search for Entities and note the Key of each of those entities. That is the "Entity Definition Key" of the entities.
To discover entity data mapping information that you will need to create your report, follow the procedures in this section.
For your reference, number data types are listed in Table 23-3.
Table 23-3 Information about Data Types
| Data Type | Description |
|---|---|
|
1 |
Represents String data |
|
2 |
Represents Numeric data. Data stored is equal to (Original value * 1000). |
|
3 |
Date type data. Store the data in "'YYYY-MM-DD HH24:MI:SS TZH:TZM" format and also retrieve it using same format. |
|
4 |
Boolean data. Stored as strings. "True" represents TRUE and "False" represents FALSE |
To get the entity data details that you will need to construct your report, follow these steps:
Get the Entity Definition Key by looking at the entity definition using the OAAM Admin Console.
Get details of how entity data is mapped using the SQL Query:
SELECT label,
data_row,
data_col,
data_type
FROM vt_data_def_elem
WHERE status =1
AND data_def_id =
(SELECT data_def_id
FROM vt_data_def_map
WHERE relation_type ='data'
AND parent_obj_type =3
AND parent_object_id IN
(SELECT entity_def_id
FROM vt_entity_def
WHERE entity_def_key=<Entity Definition Key>
AND status =1
)
)
ORDER BY data_row ASC,
data_col ASC;
The preceding SQL query gives a list of data fields of the entity with data type and row, column position. Using that information, build a SQL query based on the following information that represents data of the given entity. It is also recommended to create/build a view based on this SQL query that represents data of the given entity.
Note:
EntityRowN represents an entity data row. If your entity has 3 distinctdata_row values from the preceding query then you would have 3 EntityRows, name the aliases as EntityRow1, EntityRow2, and so on, and similarly take care of the corresponding joins as shown.
SELECT ent.ENTITY_ID,
ent.EXT_ENTITY_ID,
ent.ENTITYNAME,
ent.ENTITY_KEY,
ent.ENTITY_TYPE,
EntityRowN<row>.DATA<col> <column_name>,
(EntityRowN<row>.NUM_DATA<col>/ 1000.0) <numeric_column_name>,
to_timestamp_tz(EntityRowN<row>.DATA<col>, 'YYYY-MM-DD HH24:MI:SS TZH:TZM')
<date_column_name>,
ent.CREATE_TIME,
ent.UPDATE_TIME,
ent.EXPIRY_TIME,
ent.RENEW_TIME
FROM
VT_ENTITY_DEF entDef,
VT_ENTITY_ONE ent
LEFT OUTER JOIN VT_ENTITY_ONE_PROFILE EntityRowN
ON (EntityRowN.ENTITY_ID = ent.ENTITY_ID
AND EntityRowN.ROW_ORDER = <row>
AND EntityRowN.EXPIRE_TIME IS NULL)
LEFT OUTER JOIN VT_ENTITY_ONE_PROFILE EntityRowN+1
ON (EntityRowN+1.ENTITY_ID = ent.ENTITY_ID
AND EntityRowN+1.ROW_ORDER = <row+1>
AND row1.EXPIRE_TIME IS NULL)
WHERE
ent.ENTITY_DEF_ID = entDef.ENTITY_DEF_ID and
entDef.ENTITY_DEF_KEY=<Entity Definition Key>
To discover transaction data mapping information that you will need to create your report, follow the procedures in this section.
To get entity data details you will need to construct your report, follow these steps:
Get list of transaction to entity definition mapping Ids using the following SQL:
SELECT map_id
FROM
vt_trx_ent_defs_map,
vt_trx_def
WHERE
vt_trx_ent_defs_map.trx_def_id = vt_trx_def.trx_def_id
AND vt_trx_def.trx_def_key =<Transaction Definition Key>
Use the following SQL query to get details of all transaction data fields, their data type and their row, column mapping:
SELECT label,
data_row,
data_col,
data_type
FROM vt_data_def_elem
WHERE status =1
AND data_def_id =
(SELECT data_def_id
FROM vt_data_def_map
WHERE relation_type ='data'
AND parent_obj_type =1
AND parent_object_id IN
(SELECT trx_def_id
FROM vt_trx_def
WHERE trx_def_key='mayo_pat_rec_acc'
AND status =1
)
)
ORDER BY data_row ASC,
data_col ASC;
Use the information from the previous section and build a SQL query that represents transaction data based on the following:
Note: It is recommended to build a view based on this Query so that it is easier to build reports. Information on creating a view for entities and transactions is provided in Section 23.2.5, "Generating a Database View of Entities and Transactions."
SELECT trx.LOG_ID,
trx.USER_ID,
trx.REQUEST_ID,
trx.EXT_TRX_ID,
trx.TRX_TYPE,
trx.STATUS,
trx.SCORE,
trx.RULE_ACTION,
trx.TRX_FLAG,
trx.POST_PROCESS_STATUS,
trx.POST_PROCESS_RESULT,
TxnDataRowN<row>.DATA<col> <data_column_name>,
(TxnDataRowN<row>.NUM_DATA<col>/ 1000.0) <numeric_column_name>,
to_timestamp_tz(TxnDataRowN<row>.DATA<col>, 'YYYY-MM-DD HH24:MI:SS TZH:TZM')
<date_column_name>,
(SELECT entTrxMap.MAP_OBJ_ID
FROM VT_ENT_TRX_MAP entTrxMap
WHERE entTrxMap.DEF_MAP_ID = <Transaction to Entity Mapping Id of
Entity1_Name>
AND entTrxMap.TRX_ID = trx.LOG_ID
) <EntityN_Name>,
(SELECT entTrxMap.MAP_OBJ_ID
FROM VT_ENT_TRX_MAP entTrxMap
WHERE entTrxMap.DEF_MAP_ID = <Transaction to Entity Mapping Id of
Entity2_Name>
AND entTrxMap.TRX_ID = trx.LOG_ID
) <EntityN+1_Name>,
trx.CREATE_TIME,
trx.UPDATE_TIME,
TRUNC(trx.create_time, 'HH24') created_hour,
TRUNC(trx.create_time, 'DDD') created_day,
TRUNC(trx.create_time, 'DAY') created_week,
TRUNC(trx.create_time, 'MM') created_month,
TRUNC(trx.create_time, 'YYYY') created_year
FROM VT_TRX_DEF trxDef,
VT_TRX_LOGS trx
LEFT OUTER JOIN VT_TRX_DATA TransactionDataRowN
ON (TransactionDataRowN.TRX_ID = trx.LOG_ID
AND TransactionDataRowN.ROW_ORDER = <rowN>)
LEFT OUTER JOIN VT_TRX_DATA TransactionDataRowN+1
ON (TransactionDataRowN+1.TRX_ID = trx.LOG_ID
AND TransactionDataRowN+1.ROW_ORDER = <rowN+1>)
WHERE trx.TRX_DEF_ID = trxDef.TRX_DEF_ID and
trxDef.TRX_DEF_KEY=<Transaction Definition Key>
Follow the instructions in this section to build reports for entities and transactions.
Use the SQL Queries or Views built using the information mentioned in Section 23.2.2.3, "Build Entity Data SQL Queries and Views."
Use the SQL Queries or Views built using the information mentioned in Section 23.2.3.2, "Build Transaction Data SQL Queries and Views."
OAAM persists entity and transaction data in the database. OAAM provides a command line tool to generate the SQL script file which contains SQL statements to create views for entities and transactions in OAAM.
These views help you view the transaction and entity related data in the database in an easier way as compared to querying specific tables for every detail since they provide a comprehensive picture of the entities and transactions currently available in the database along with information about their relationships (transaction-entity, entity-entity).
The generateTrxEntityViewsSQL script creates a SQL file which upon execution create database views for existing transaction and entity related definitions and data in the database.
The script generates a SQL script on the basis of transaction and entity definitions present in the database.
Before running the script, ensure the OAAM CLI environment is set up. For instructions on setting up the CLI environment, see Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.
The following must be added to the CSF/Credential Store using Oracle Enterprise Manager Fusion Middleware Control (<host>:<port>/em).
OAAM database User Name and Password with oaam_db_key as the keyname under the map oaam.
Table 23-4 shows the properties that must be set in the oaam_cli.properties file before you can generate the view.
To generate the SQL script file, run the generateTrxEntityViewsSQL script from the OAAM CLI folder.
The default file generated is createTrxEntityViews.sql and contains some create or update queries to create or update views for each transaction and entity definition.
Follow the subsequent steps to create database views for entities and transactions stored in the OAAM database.
Log in to the database as a OAAM database schema user.
Grant the OAAM database schema user the Grant Create View privilege.
Connect to the database using the OAAM database schema user.
For example, sqlplus DEV_OAAM/PASSWORD
Run createTrxEntityViews.sql.
The script creates database views of each entity and transaction defined in the OAAM database.
For each entity defined in OAAM, one view will be created with the name oaam_ent_entity_key. The entity_key will be replaced by the key of the entity as defined in OAAM. The created view will contain one column for each data defined in the entity. In addition to the data columns, the created view will contain the following columns:
ENTITY_ID: Unique identifier of the entity instance
CREATE_TIME: Time the entity was created
UPDATE_TIME: Time of last update of the entity
For each transaction defined in OAAM, one view will be created with the name oaam_trx_transaction_key. The transaction_key will be replaced by the key of the transaction as defined in OAAM. The created view will contain one column for each data defined in the transaction.
The created view will contain one column for each entity referenced in the transaction to store the entity_id of the referenced entity. For example, the entity_id column in the oaam_ent_entity_key view. Spaces in the instance names will be replaced with an underscore in the column names.
LOG_ID: Unique identifier for the transaction
USER_ID: User who performed the transaction
REQUEST_ID: Session in which this transaction was performed
EX_TRX_ID: External ID of this transaction
STATUS: Status of the transaction
CREATE_TIME: Time the entity was created
UPDATE_TIME: Time of last update of the entity
CREATED_HOUR: Create time truncated to the nearest hour
CREATED_DAY: Create time truncated to the nearest day
CREATED_WEEK: Create time truncated to the nearest week
CREATED_MONTH: Create time truncated to the nearest month
CREATED_YEAR: Create time truncated to the nearest year
Oracle database limits the length of identifiers such as table, view and column names to 30 characters. To ensure that the views created by the script comply for this requirement, limit the name of entity, transaction, and datafield names to the following identifiers:
entity: 21 (view names will be "oaam_ent_" + <entity_key>)
transaction: 21 (view names will be "oaam_trx_" + <transaction_key>)
datafield: 28 (column name will be "d_" + <data_element_name>)
entity-ref: 20 (column name will be <relationship_name> + "_entity_id")
If the script finds any names longer than the above limits, the script will trim the identifier. Look for such trimmed column/view names while writing SQL queries on the created views.
Space, dash ("-") and period (".") characters in the names will be replaced with an underscore.
A typical SQL query to create a view based on an Entity definition "Address" is shown as follows. oaam_ent_ADDRESS is the view that is created from the SQL query.
create or replace
force view oaam_ent_ADDRESS
as
(select
(ent.ENTITY_ID, ent.EXT_ENTITY_ID, ent.ENTITYNAME, ent.ENTITY_KEY,
ent.ENTITY_TYPE,ent.CREATE_TIME, ent.UPDATE_TIME, ent.EXPIRY_TIME,
ent.RENEW_TIME
from
VT_ENTITY_DEF entDef, VT_ENTITY_ONE ent left outer join
VT_ENTITY_ONE_PROFILE row0 on
(row0.ENTITY_ID = ent.ENTITY_ID
and row0.ROW_ORDER = 0
and row0.EXPIRE_TIME is null)
where entDef.ENTITY_DEF_KEY='Address'
and ent.ENTITY_DEF_ID = entDef.ENTITY_DEF_ID);
The tables used for the view are listed in Table 23-5.
Table 23-5 Entity Tables in the Entity View
| Table | Description |
|---|---|
|
VT_ENTITY_DEF |
This table has definitions of all the different Entities. |
|
VT_ENTITY_ONE |
This table has the Entity Key, name, a unique ID and expiry. |
|
VT_ENTITY_ONE_PROFILE |
This table has the Entity data stored in it. |
The view provides to you a single view which contains the entire information about the particular transaction/entity definition and all the data associated with that definition. Once the script is run, you can choose to see the data in the view whenever needed. This view provides to you a consolidated view of data in one place instead of mapping data from various tables. The oaam_ent_ADDRESS view is shown in Table 23-6.
| Field Name | DB Type | Description |
|---|---|---|
|
ENTITY_ID |
BIGINT |
ID of the entity |
|
EXT_ENTITY_ID |
VARCHAR |
External entity ID (supplied by client) |
|
ENTITYNAME |
TEXT |
Name of the entity (generated name of the entity by the namegen Scheme according to the entity definition). |
|
ENTITY_KEY |
TEXT |
Key for the entity (generated key for the entity by the keygen scheme according to the entity definition). This key is used to perform the lookup whether this entity exists in the DB. |
|
ENTITY_TYPE |
INT |
Type of the entity |
|
CREATE_TIME |
DATETIME |
Date/Time when this object was created |
|
UPDATE_TIME |
TIMESTAMP |
Date value |
|
EXPIRY_TIME |
DATETIME |
Expiry date value. Set according to preconfigured property, number of days from the request time. |
|
RENEW_TIME |
DATETIME |
Renew date value. After this time, if this entity is being used, the expiry is extended as well as the renew_time. |
|
ROW_ORDER |
INT |
Row order (starts with 0 to accommodate any number of data. Once 10 columns are exhausted, another record with row_order 1 would be inserted and so on.) |
|
EXPIRE_TIME |
DATETIME |
Date/time when this profile expires |
|
ENTITY_DEF_KEY |
TEXT |
Key of the entity. For example, address, merchant, and so on. |
|
ENTITY_DEF_ID |
BIGINT |
ID for the entity definition |