This chapter describes the basic concepts and assumptions (or business rules) in the Oracle Communications Data Model.
This chapter is organized by subject area in the typical way you might feed data into Oracle Communications Data Model.
Oracle Communications Data Model is aligned with TM Forum's Information Framework (SID) Release 12. The TM Forum provides business-critical industry standards and expertise to enable the creation, delivery, and monetization of digital services. For more information on TM Forum, see
Most entity names conform to the TeleManagement Forum Shared Information Data (SID) model Business entities, to ease the mapping when dealing with TM Forum SID certified applications. In nearly all cases, the definitions exactly fit. Hence, several notions in the following can be reviewed and deepened by looking into the TM Forum SID documentation with their examples. From a content perspective however, they usually have more attributes specific to Oracle Communications Data Model.
General entities shown in Table B-1 should be filled upfront either manually (standard Geography hierarchy, Organization Business Units) or automatically (calendars and time of day, geography through Address Location or external data, Standard Organization Business hierarchy through Human Resource (HR) or Enterprise Resource Planing (ERP) system as input).
Table B-1 General Entities
Model Area | Description |
---|---|
Business Unit Code and Business Unit Type Code |
These attributes are leveraged for the ORGANIZATION flexible Hierarchy, related to the Organization subject area. Please do not remove and do not mix with ORGANIZATION BUSINESS UNIT CODE (or key). |
CALENDAR |
Calendars should be filled for 20 years starting with the "smallest" day for which Usage data (in aggregation) will be available (not customer data) and furthest day in the future. |
GEOGRAPHY |
The default geography of the country, for example, WORLD, REGION, COUNTRY, CITY should be defined upfront whenever possible. Create search functions to simplify the address validation (whether or not add a new CITY or COUNTY row when getting a new address). Addresses should be validated upfront in the source system or at the staging layer. Addresses are supposed to be correct and validated when in Oracle Communications Data Model. |
TIME |
Please fill the second, minutes, quarter of hours and hours. |
By default, TIME SLOT should correspond exactly to quarter of hours. You may extend this notion to a bigger time period (for customization), leveraging a time band. |
Table B-2 Product Offering and Specifications Entities
Entity | Description |
---|---|
Represents what is externally presented to the market for the market's use. A PRODUCT OFFERING can be assembled from a reusable PRODUCT SPECIFICATION (sometimes referred to as "product spec"). PRODUCT OFFERING is physically associated with DWR_PROD_OFR. Typical abbreviation for PRODUCT OFFERING is "Prod Offer" or "Product Offer" or "Prod Offering". |
|
Represent a tangible object or something intangible provided to customers, realized as a 'service' but not to be confused with a network service (TMF SID). Basically, a PRODUCT SPECIFICATION describes the characteristics of what the customer will be able to do once he purchases (the PRODUCT OFFERING is the market vision, while the PRODUCT SPECIFICATION is the effective Component description, from the perspective of a service provider, that are leveraged to compose the PRODUCT OFFERING). It is physically associated with DWR_PROD_SPECIt is physically associated with DWR_PROD_SPEC. |
|
A particular form or variety of a PRODUCT SPECIFICATION that is different from others or from the original. The form represents differences in properties that characterize a PRODUCT SPECIFICATION, that are not significant enough for creating a new PRODUCT SPECIFICATION. |
|
A PRODUCT SUBSCRIPTION represents an instance of a PRODUCT SPECIFICATION, typically available for sales or sold (before or after being subscribed to). A Product is an Instance of a PRODUCT SPECIFICATION associated with a PRODUCT OFFERING. In Oracle Communications Data Model, it would typically correspond to some hardware (prepaid card, cell phone, and so on) on the shelf (somewhere) with a specific Serial Number ready to be purchased and used. A PRODUCT SUBSCRIPTION would be the realization of a PRODUCT SPECIFICATION when a Service is associated with the PRODUCT SPECIFICATION (for example a GSM service). PRODUCT corresponds to DWR_PROD). |
|
Represents the subscription to a PRODUCT OFFERING by a PARTY playing a PARTY ROLE, such as a Customer. A PRODUCT SUBSCRIPTION is an instance of a PRODUCT SPECIFICATION associated with an ACCOUNT, and optionally (usually) with a service and an access method (same definition as PRODUCT otherwise). PRODUCT SUBSCRIPTION allows each part of a PRODUCT OFFERING (typically based on COMPOSITE PRODUCT SPECIFICATION) to be realized and instantiated separately, "atomic" product specification would be used to describe "trouble ticket" or "product subscription change", by atomic PRODUCT SPECIFICATION to allow actions such as trouble ticket or product subscription change against specific ones (and not just the composite Spec). This is also necessary if a PRODUCT OFFERING has a tariff (PRODUCT OFFERING PRICE) depending on the flexible characteristic associated to a PRODUCT SPECIFICATION. In Oracle Communications Data Model the PRODUCT SUBSCRIPTION will not carry the AGREEMENT nor its agreement details (AGREEMENT ITEM). AGREEMENT ITEM holds the Product subscription Key. Through AGREEMENT ITEM, one can find out the Agreement Key. As a consequence, a change in PRODUCT SUBSCRIPTION may imply a change in AGREEMENT ITEM (typically for postpaid but not only) but not in AGREEMENT. The attributes "Product Subscription Status code" and "Status code" should always be filled and equal. |
|
A method used to group related PRODUCT SPECIFICATIONs marketed by the same company that differ only in size or style. This strict definition (TMF SID) is in fact open for any definition that fits the Communications Service Provider (CSP). |
|
A method used to group a set of PRODUCT SPECIFICATIONs that are classified together because of common characteristics. This strict definition (TMF SID) is in fact open for any definition that fits the CSP. |
|
Plan Type |
The attribute Plan Type in PRODUCT OFFERING corresponds to either "Prepaid" or "Postpaid". It is used in the PRODUCT OFFERING Hierarchy. Possible extensions are "Hybrid" but should be carefully looked at, especially with respect to the implications on some critical intra-ETLs such as COUNT DAY DRVD, REVENUE DAY DRVD and others. |
SKU ITEM tracks physical inventory. Hence, there must be one row (that is one key) per concrete object. SKU ITEM can roll up to two hierarchies: ITEM SPECIFICATION and PRODUCT SPECIFICATION. Those two hierarchy attributes are present in SKU ITEM. |
|
These are a subset of SKU ITEM with fewer attributes and some unique attributes. Just like SKU ITEM, they can roll up to ITEM SPECIFICATION or PRODUCT SPECIFICATION. ACCESSORIES are always add-ons to a main item. For each instances of ACCESSORIES, EQUIPMENT and HANDSET MODEL (in their respective DWR_XXX_INSTNC tables), do the following:
|
|
In Oracle Communications Data Model, only Postpaid-related supplementary Services have been picked, leveraging any PRODUCT SPECIFICATIONs defined in DWR_SPLMNTR_SRVC. Note however that the supplementary service derived table only runs over PRODUCT SPECIFICATION, looking for specific Product Specification codes, instead of linking to DWR_SPLMNTR_SRVC, because the target attributes are fixed. |
|
VAS Service |
Value-Added Service VAS applies only to WIRELESS CALL EVENT: the following tables should be taken. The current Intra-ETL version for VAS Usage derived, only uses DWB_ISP_USG_EVT, DWB_MMS_EVT, DWB_UDR_EVT, and DWB_SMS_EVT.DWB_UMS_EVT, DWB_WRLS_CALL_EVT DWB_WRLS_CALL_EVT DWB_SMS_EVT DWB_MMS_EVT DWB_WRLS_CNTNT_DNLDG_EVT DWB_CNTNT_DLVRY_EVT DWB_GPRS_USG_EVT DWB_ISP_USG_EVT DWB_UMS_EVT DWB_WRLS_RMNG_EVT |
Table B-3 Party and Party Subtype Entities
Entity | Description |
---|---|
Customer has PROFILES and they have sub types of Individual and Business (termed as Organization). In addition Customer Contains PROSPECT also plus other related reference entities such as Customer Financial and Non Financial relationship (Accounts, Affiliation, Group, Occasion, Preference, Demography). Some of the "Named" Demography attributes are kept in CUSTOMER entity. |
|
PARTY and PARTY ROLE |
A party is an umbrella relationship across customer, vendor, employee and similar entities. For a given natural key, a Party ID ties up all these disparate entities and allows to leverage each other while maintaining their individual signatures. Remember PARTY as an after thought which enables you to tie together the disparate entities with a common ID based on same Natural key. By definition all these disparate entities are created at a different time frame with diverse OLTP systems but all of them would carry same natural key if the same party is defined in the system as a customer, an employee and a vendor as well. By default, only two types of PARTY are available in Oracle Communications Data Model: Individual and ORGANIZATION. This can be extended but consider extending and also updating the various tables associated with a PARTY ROLE such as CUSTOMER if they are impacted. The same party can play several party roles with respect to the CSP: A person could be customer, employee and dealer of the CSP at the same time. It would have the same party key. But for a given interaction or event, only one party role is typically used (unless he sells to himself a product offering, for example). Standard Party Roles like CUSTOMER, VENDOR, DEALER, EMPLOYEE, SALES CHANNEL REPRESENTATIVE are pre-defined in Oracle Communications Data Model with their sub-types. |
There are several types of events to distinguish in Oracle Communications Data Model:
About Business Interactions describes business interactions in general (as super type) and Party Interaction Events.
About Agreements describes agreements (as a subtype of Business Interaction but differing from Event Party Interaction).
About BSS/OSS Interaction Events describes events related to BSS or OSS systems that are neither Business Interactions nor Agreements, that is, not defined either of these.
About Usage Events (UDR Events) describes usage event, also called UDR Events, and their numerous subtypes.
Network related events like ResourceAlarm, Service Problems and Performance Measurement events. There is no specific section in this document as their definition (as in the TMF SID) immediately provides the scope of data to be used. Note that TROUBLE TICKET is a sub-type of BUSINESS INTERACTION that is (usually) related with one or more SERVICE PROBLEM(s) and one or more RESOURCE ALARM(s).
About Process Events describes process events (from an application perspective) and describes any process in the telecommunication world that needs to be monitored: Billing, Service Fulfillment, and so on. Such events are usually directly related with KPIs.
Business Interactions are related to the transactions stored into back office applications. Table B-4 describes business interactions.
Table B-4 Business Interactions
Entity | Description |
---|---|
and |
Maintain these entities as two identical entities with identical structure. BUSINESS INTERACTION is created once for a given interaction and should be subsequently updated with the latest status, whereas BUSINESS INTERACTION HISTORY always has a new record created for the same interaction with different status code (STAT_CD) and transaction date (TRX_DT). |
Use by default for all business interactions involving a PARTY, which are not AGREEMENT. |
|
This is when the CSP sends a purchase order to a VENDOR. It has nothing to do with Customers (stored in CUSTOMER ORDER). |
The following lists the tables that are sub-types of BUSINESS INTERACTION or related to business interactions.
Business Interaction Tables
DWB_AGRMNT_APRVL
DWB_AGRMNT_TERM
DWB_BSNS_INTRACN
DWB_BSNS_INTRACN_HIST
DWB_BSNS_INTRACN_ITEM
DWB_BSNS_INTRACN_ITEM_PRICE
DWB_BSNS_INTRACN_PYMT_ASGN
DWB_BSNS_INTRACN_RL
DWB_BSNS_INTRACN_VRSN
DWB_CNSEQ_PRFMNC_NTFCTN
DWB_CUST_ORDR
DWB_CUST_ORDR_LN_ITEM
DWB_INVC_ADJ
DWB_NP_RQST_HDR
DWB_NP_RQST_LN_ITEM
DWB_PCHSE_ORDR
DWB_PCHSE_ORDR_LN_ITEM
DWB_PCHSE_ORDR_LN_ITEM_STATE
DWB_PCHSE_ORDR_STATE
DWB_PRFMNC_NTFCTN
DWB_RSCE_BSNS_INTRACN_RL
DWB_RSCE_ORDR
DWB_RSCE_ORDR_ITEM
DWB_SRVC_ORDR
DWB_SRVC_ORDR_LN_ITEM
DWR_ACCT_BSNS_INTRACN_RL
DWR_AGRMNT
DWR_AGRMNT_ITEM
DWR_BSNS_INTRACN_CHAR_VAL
DWR_BSNS_INTRACN_LOC_ASGN
DWR_EQPMNT_RNTNG_AGRMNT
DWR_INSTLMNT_AGRMNT
DWR_PRTY_BSNS_INTRACN_RL
DWR_SRVC_LVL_AGRMNT
DWR_SRVC_LVL_AGRMNT_ITEM
DWR_VNDR_AGRMNT
Use the table DWB_BSNS_INTRACN for all business interaction cases not covered by EVENT PARTY INTERACTION or AGREEMENT.
The ITEM CODE in this entity is only a sequential number for business interaction detail. It has nothing to do with ITEM SPECIFICATION (DWR_ITEM_SPEC) or SKU ITEM. This also applied to AGREEMENT ITEM.
SEQ in Table B-5 means a number representing the rank in a series of objects is expected.
Table B-5 Business Interaction Items Tables
Table | Sequence Number |
---|---|
DWB_AGRMNT_TERM |
SEQ |
DWB_BSNS_INTRACN_ITEM |
SEQ |
DWB_BSNS_INTRACN_ITEM_PRICE |
SEQ |
DWB_CUST_FLD_SRVC_DTL |
SEQ |
DWB_CUST_ORDR_LN_ITEM |
SEQ |
DWB_EVT_PRTY_INTRACN_ITEM |
SEQ |
DWB_NP_RQST_LN_ITEM |
SEQ |
DWB_PCHSE_ORDR_LN_ITEM |
SEQ |
DWB_PCHSE_ORDR_LN_ITEM_STATE |
SEQ |
DWB_RSCE_ORDR_ITEM |
SEQ |
DWB_SRVC_ORDR_LN_ITEM |
SEQ |
DWB_TRBLE_TCKT_ITEM |
SEQ |
DWR_AGRMNT_ITEM |
SEQ |
DWR_SRVC_LVL_AGRMNT_ITEM |
SEQ |
DWR_BSNS_INTRACN_LOC_ASGN |
SEQ |
DWR_BSNS_INTRACN_CHAR_VAL |
SEQ |
The event party interactions stores all interactions with a party, whether by phone, letter or fax, on-site visit (whether a party enters a shop or gets the visit of a sales representative), chat on the web or simple web navigation.
The EVENT PARTY INTERACTION should be used by default for all business interactions involving a PARTY, which are not AGREEMENT.
The related EVENT PARTY INTERACTION ID should point to the first EVENT PARTY INTERACTION related to the same subject ("Thread"). Hence, to have the list of interaction related to each other, they will ALL have the same RLTD_INTRACN_ID except the 1st one (empty).
The assumed logical hierarchy is: EVENT => BUSINESS INTERACTION => EVENT PARTY INTERACTION.
When no specific table for a given EVENT PARTY INTERACTION is available in Oracle Communications Data Model,, use the generic EVENT PARTY INTERACTION.
When no specific tables for a given BUSINESS INTERACTION which is neither EVENT PARTY INTERACTION, AGREEMENT, or CUSTOMER ORDER, use generic BUSINESS INTERACTION.
When no specific tables for a given EVENT (see list in EVENT_BSNS_INTRACN_INFORMATION worksheet), use generic EVENT table (DWB_EVT).
The following lists shows the entities related to EVENT PARTY INTERACTION.
Event Party Interaction Tables
DWB_APNMNT
DWB_CUST_FLD_SRVC_ACTVTY
DWB_CUST_FLD_SRVC_DTL
DWB_EVT_PRTY_INTRACN
DWB_EVT_PRTY_INTRACN_CHAT_DTL
DWB_EVT_PRTY_INTRACN_ITEM
DWB_EVT_PRTY_INTRACN_PRTCPTN
DWB_INTRACN_NAVGTN_HIST
DWB_INTRACN_QUES_RESPN
DWB_INTRACN_TRNSFR_HIST
DWB_IVR_INTRACN_NAVGTN_HIST
DWB_PRTY_PRMTN_RESPN
DWB_SRVC_RQST
DWB_TRBLE_TCKT
DWB_TRBLE_TCKT_FLD_SPPRT_ASGN
DWB_TRBLE_TCKT_ITEM
DWB_WEB_INTRACN_NAVGTN_HIST
DWR_EVT_PRTY_INTRACN_CHAR_VAL
The trouble ticket is more the result of an interaction but, since it could be directly created by a third party or the customer itself (typical by support request systems).
EVENT PARTY INTERACTION ITEM is a subtype of BUSINESS INTERACTION ITEM (as EVENT PARTY INTERACTION is a subtype of BUSINESS INTERACTION).
If, for any reason, some entities related to the super-type (BUSINESS INTERACTION) are required to add information to EVENT PARTY INTERACTION that are not available otherwise, the creation of a row in BUSINESS INTERACTION is then required with EVENT CODE (EVT_CD) and INTERACTION ID (INTRACN_ID) in BUSINESS INTERACTION being copied from EVENT PARTY INTERACTION. Only the required keys shall be copied (and the Business Interaction type = "EVENT PARTY INTERACTION"). The hierarchy is EVENT => BUSINESS INTERACTION => EVENT PARTY INTERACTION. This duplication of information is only required to avoid customization and benefit, only where needed, of the super-type/subtype relationships.
Agreement (DWR_AGRMNT) shall be used by default for all agreements, prepaid (tacit or explicit), postpaid, interconnection and roaming, reseller, and so on.
Agreement KEY and INTERACTION ID should have identical value. The interaction ID field is just to ensure that it is a child of BUSINESS INTERACTION (similarly for AGREEMENT ITEM).
An invoice requires an agreement but an agreement may have 0 to n invoices related.
Any events which are not a Business interaction nor an AGREEMENT as such, shall be a subtype of EVENT. It could typically be a purely technical event (Activation, suspension, deactivation and so on).
For example, a EVENT PRODUCT SUBSCRIPTION WIRELESS (DWB_EVT_PROD_SBRP_WRLS) could be used to store information of the EVENT of activation, suspension and deactivation. It shall not prevent updating the status of the corresponding PRODUCT SUBSCRIPTION (DWR_PROD_SBRP).
Table B-6 lists the tables that would correspond to such an event with their sources (assumed). Please note that BLLG stands for Billing Application, TXN for Transaction, CRM for Customer Relationship Management Application, FIN for Finance Application (such as JD Edwards, ERP or other), and HR for Human Resource applications (like PeopleSoft or others). NTWK stands for Network Applications (typically the network monitoring or Server control applications).
Table B-6 BSS/OSS Interaction Event Tables
EVENT TABLES (HR/Billing/Financial/CRM) Transactions not result | Source TYPE |
---|---|
DWB_ACCT_BAL_IMPC |
BLLG TXN |
DWB_ACCT_PYMT |
BLLG TXN |
DWB_BLK_LST_HIST |
CRM TXN |
DWB_EMP_EXP_RPT |
HR/FIN TXN |
DWB_EMP_EXP_RPT_ITEM |
HR/FIN TXN |
DWB_EMP_EXP_RPT_STATE |
HR/FIN TXN |
DWB_EVT |
CRM TXN a priori |
DWB_EVT_ACCS_MTHD_ACTVTY |
CRM TXN |
DWB_EVT_ACCT |
CRM TXN |
DWB_EVT_AGRMNT |
CRM TXN |
DWB_EVT_CMPST_PROD_SPEC |
CRM TXN |
DWB_EVT_COST |
FIN TXN |
DWB_EVT_CRCUT_RNTL |
CRM TXN |
DWB_EVT_EMP_ACTVTY |
HR TXN |
DWB_EVT_EMP_PYRL |
HR TXN |
DWB_EVT_EQPMNT_INSTNC |
CRM TXN |
DWB_EVT_FINCL |
FIN TXN |
DWB_EVT_GEO |
CRM TXN |
DWB_EVT_LYLTY_PROG |
CRM TXN |
DWB_EVT_PROD_SBRP_WRLS |
CRM TXN |
DWB_EVT_PRPD_MBL |
CRM TXN |
DWB_EVT_PRTY_ASGN |
CRM TXN |
DWB_EVT_PRTY_PRFL |
CRM TXN |
DWB_EVT_SBRP_CHNG |
CRM TXN |
DWB_EVT_SIM_CARD |
CRM TXN |
DWB_EVT_STAT |
CRM TXN |
DWB_EXP_RPT_PRTY_ASGN |
HR/FIN TXN |
DWB_PRICE_EVT |
BLLG TXN |
DWB_PRPD_RCHRG |
BLLG TXN |
DWB_PTV_FULL_CHNL_ACTVTN |
CRM TXN |
DWB_SL_CMISN_DTL |
HR/FIN TXN |
DWB_SL_CMISN_PYRL |
HR/FIN TXN |
DWR_EVT_LOC |
CRM Reference |
DWR_ISP_USER |
NTWK Reference |
DWR_PRCE_EVT_PRODOFR_PRCE_ASGN |
BLLG Reference |
There are many pre-defined types of usage event data records. Call Data Records or any usage data records should be loaded into the corresponding UDR EVENT table (or any of its sub-entities that are more or less directly corresponding to the considered data record).
There are important assumptions for UDR Events:
A UDR shall be stored in one table only. It is not required to repeat it in the super entity.
It is recommended to create a sub-entity of UDR EVENT for each group of usage with their specific characteristics if they are not already pre-defined in Oracle Communications Data Model. Otherwise, use the corresponding tables. The Intra-ETL should be correspondingly expanded to take those new tables into account (where relevant).
A UDR EVENT shall be stored in daily partitions (or lower) leveraging the starting date of the usage event (EVT_STRT_DT). In particular, if late CDRs (like Roaming) are loaded, they have to be loaded in the older partitions!
The BILLING DATE field shall be used to flag WHEN the UDR EVENT was loaded to the Billing System (if any). It means "BILLING SYSTEM DATE". It is not the necessarily date at which the event has been billed (put to an invoice). Note that for Prepaid, BILLING SYSTEM DATE and EVT_STRT_DT should be very similar if not equal (or maybe equal to EVT_END_DT!).
For the Intra-ETL treatment in Oracle Communications Data Model, the current time windows considered applies on the EVENT START DATE. An alternative (customization) would be to use the UDR EVENT BILLING_DATE to determine which CDRs are to be considered.
Whenever a new type of usage data record is available, you have several choices:
Map it to an existing table that match the definition, adding as many missing fields as required (but knowing that those fields will not be considered by default by the intra ETLs).
Map what is possible to the UDR EVENT table (or any sub-table) to only keep track of its presence in Oracle Communications Data Model as well as the fields used by the Intra-ETL but do not extend the other fields (quickest way for out-of-the-box implementation of Oracle Communications Data Model, knowing the data will not allow detailed and complete analysis on fields that are not stored).
Create a subtype of the UDR Event table adding all the fields required and modifying the Intra ETLs to take it into account where required
The best alternative depends on the project condition. But keeping as much atomic information as possible is usually preferred unless the data amount or effort to load it is not worth the potential business value. In such case, a pre-processing in the staging area or through big data might be worth considering (for example, for network signaling data).
Table B-7 lists the pre-defined tables for UDR Events.
Table B-7 Predefined UDR Event Tables
UDR EVENT TABLES (Network Transactions) | Source TYPE |
---|---|
DWB_BRDBND_USG_EVT |
UDR EVT |
DWB_CNTNT_DLVRY_EVT |
UDR EVT |
DWB_DATA_SRVC_EVT |
UDR EVT |
DWB_ERRD_MDTD_CALL_EVT |
UDR EVT |
DWB_ERRD_RAW_WRLS_CALL_EVT |
UDR EVT |
DWB_ERRD_RTD_WRLS_CALL_EVT |
UDR EVT |
DWB_FIXED_LN_CALL_EVT |
UDR EVT |
DWB_GPRS_USG_EVT |
UDR EVT |
DWB_IDD_CALL_EVT |
UDR EVT |
DWB_INTRNT_ACCS_EVT |
UDR EVT |
DWB_ISP_USG_EVT |
UDR EVT |
DWB_MDTD_CALL_EVT |
UDR EVT |
DWB_MMS_EVT |
UDR EVT |
DWB_PTV_QPI_SRVC_EVT |
UDR EVT |
DWB_PTV_USG_EVT |
UDR EVT |
DWB_RAW_MMS_EVT |
UDR EVT |
DWB_RAW_WRLS_CALL_EVT |
UDR EVT |
DWB_RTD_UDR_EVT |
UDR EVT |
DWB_SMS_EVT |
UDR EVT |
DWB_TAP_IN_WRLS_RMNG_EVT |
UDR EVT |
DWB_TAP_OUT_WRLS_RMNG_EVT |
UDR EVT |
DWB_UDR_EVT |
UDR EVT |
DWB_UMS_EVT |
UDR EVT |
DWB_VOIP_CALL_EVT |
UDR EVT |
DWB_WRLS_CALL_EVT |
UDR EVT |
DWB_WRLS_CNTNT_DNLDG_EVT |
UDR EVT |
DWB_WRLS_RMNG_EVT |
UDR EVT |
Process events are meant to store and manage the various eTOM ("enhanced Telecommunications Operations Mapping") processes run in the Telecommunications industry, from a process perspective. Process events are mainly aimed to measure Operational Excellence.
A complete generalized model of processes has been created, with default parameters (such as Manual Indicator, Customer Type, Billing Cycle, and so on). You can use the default parameters and an open parameter list with "operators" (GREATER THAN, BETWEEN, LIKE...) and values to cover many changeable processes.
Similar to other areas, Oracle Communications Data Model uses a PROCESS (definition) and PROCESS SPECIFICATION (for the grouping of similar processes with similar characteristics), with their relationships. And an instance or run of a given process occurs through a PROCESS EVENT, referring to a PROCESS. PROCESS EVENT that are sequentially related should be stored in PROCESS EVENT ASSIGNMENT, normally illustrating the PROCESS RELATIONSHIP previously defined. However, since nothing runs necessarily fine forever, the PROCESS EVENT ASSIGNMENT allows relationships between PROCESS EVENTs that are normally not related. For example, after several tentative of automatic invoice recycling, a manual invoice review could take place. All those processes are expected to be stored and related through this entity.
Oracle Communications Data Model is not designed to act as a Process Management Tool. Oracle Communications Data Model shall only be the information collector to enable end-users to improve their daily tasks by providing them the relevant or right information at the right time in the breadth they need, and allowing them to deepen their analysis down to atomic level of any area they are entitled to search.
Oracle Communications Data Model provides an example and illustration for the following processes: the billing cycle from invoice generation and printing (issuing) to invoice dispatching.
PROCESSes also measure some of the TMF KPIs with respect to Billing Operational efficiency. For those specific measures in particular, one has to look into the generation process for all invoice-related processes that occurred in a given month.
One can create a specific subtype of process event table to make sure all the statistics related to the process is stored - if the default statistics are not sufficient. One must be aware however that the multiplication of sub-tables for processes may tend to confuse the reader or make the model hard to follow and keen to error (by forgetting to link or check one or the other sub-table). As always, it is a matter of balance.
With respect to the derived layer, do not mix INVOICE DAY DRVD (DWD_INVC_DAY) and PROCESS INVOICE DAY DRVD (DWD_INVC_PRCS_DAY). The first summarize the invoice information available at a given day (equal to BILLING DATE) while the other collects information about the end-to-end process, observed from the end-date of the Dispatching process. Recall that not only the invoice generation process but any type of process could be monitored if the information is fed to the process tables.
Oracle Communications Data Model defines a hierarchy between the ACCOUNT, AGREEMENT, and PRODUCT SUBSCRIPTION:
Account: The financial vision of a customer or the payer (in TMF SID, it corresponds to CustomerAccount). An account can have sub-accounts (through ACCOUNT RELATIONSHIP) if required.
AGREEMENT: an agreement must be associated with ACCOUNT. They must be defined for Postpaid (typically equivalent to contract) and can be defined for Prepaid (possibly as instance of a tacit pre-defined agreement). It is the implementor's choice (and a business decision). It is however expected in most Intra-ETLs that a dummy agreement is created with the main PRODUCT OFFERING associated for each Prepaid account.
Notes on data model entities.
Table B-8 Notes Table
Entity | Description |
---|---|
Invoice |
If Invoice Creation Date is not defined, BILLING DATE shall be used. Note that BILLING DATE must be present as it is used for several Intra-ETLs and several links. Outstanding Invoices are Invoices to be paid, not necessarily overdue, but at least dispatched. Overdue invoices are invoices not being paid by (end of) DUE DATE. |
Age On Net |
AGE_ON_NET can be defined for whatever "entity" (Agreement, customer, product subscription) one considers. By default, the creation date (CRT_DT) or start date (STRT_DT) shall be used and not worry too much about "holes" (approximation). The following lists the various "ages" Oracle Communications Data Model could consider (only the first choice is used by default):
The formula should then be: AGE_ON_NET (default in months) = CEIL(MONTHS_BETWEEN(SYSDATE,AGE_ON_NET_START_DATE) MINUS AGE_ON_NET_TOT_MISSINGMONTHS). To simplify this in Oracle Communications Data Model: AGE_ON_NET (default in months) = CEIL(MONTHS_BETWEEN(MIN(SYSDATE, nvl(CHRN_DT, to_date('20990101','yyyymmdd'))),CRT_DT) ) Please note the approximation that CUSTOMER effective start date is considered to be its CREATION date. Similarly, CONTRACT AGE (default in months) = MONTHS_BETWEEN(MIN(SYSDATE, nvl(END_DT, to_date('20990101','yyyymmdd'))), STRT_DT). |
Loyalty |
Loyalty is a specific subject area as such. In Oracle Communications Data Model the Loyalty program and balances are associated with a specific MEMBERSHIP ACCOUNT, which is only associated to customer (and not to ACCOUNT). Any event that could impact Loyalty points should be stored in EVENT LOYALTY PROGRAM (DWB_EVT_LYLTY_PROG) and from there, the ETL (not the intra-ETL!) should also feed DWB_ACCRUAL_EVT (points winning) and DWB_REDEM_EVT (redemption, expiration) ACCOUNT BALANCE IMPACT records with ACCT_BAL_TYP Like '%LYLTY%' should have a corresponding event created into DWB_LYLTY_PROG_EVT records. MEMBERSHIP ACCOUNT BALANCE HISTORY is a snapshot (similar to ACCOUNT BALANCE) The events that could feed EVENT LOYALTY PROGRAM as earning points should all come from Billing System, whatever their origin (usage, customer order, payment...). It is however possible to also link a pure retail transaction but this has to be done explicitly in Oracle Communications Data Model (Customization). The events that could feed LOYALTY PROGRAM EVENT as redemption are of 3 types:
Please not that the Derived Loyalty table is only at LOYALTY PROGRAM level. Table B-9 provides information on a Loyalty events |
Count Day |
The COUNT DAY DRVD stores all counts with respect to customer, account, agreement, product subscriptions, to be able to get at any day in time the effective count of the entity status at the end of a given day. Oracle Communications Data Model assumes that if either Customer Surrogate Key, Account Surrogate Key or Agreement Surrogate key changes, the associated product subscriptions (Product subscription key) shall also change. If for Customer and ACCOUNT, it is clear due to the (forced) links between account/customer and product subscription, this link is not compulsory between agreement and product subscription. (It could easily be made as customization). The link between agreement and Product subscription is only through AGREEMENT ITEM, and agreement can change in principle without impacting product subscription. |
Table B-9 Loyalty Event Additional Information
Physical Column NameIn DWB_EVT_LYLTY_PROG | Logical Column Name (and comments)In DWB_EVT_LYLTY_PROG | Redemption | Earning |
---|---|---|---|
ACCT_BAL_TYP _CD |
Account Balance Type Code |
RTL_TNDR_LI(retail receipt is not part of Invoice) => NULL/ CUST_ORDR => no INVC_CD => NULL Acct_Pymt. ACCT_BAL_TYP_CD |
ACCT_BAL_TYP_CD of ACCT_BAL_IMPC_BAL |
ACCT_KEY |
Account Key |
ACCT_KEY from all 3 transactions |
ACCT_KEY of ACCT_BAL_IMPC_BAL |
CRNCY_CD |
Currency Code |
Retail: ISO_CRNCY_CD CUST_ORDR: ISO_CRNCY_CD ACCT_PYMT: CRNCY_CD |
Not applicable. |
EVT_CD |
Event Code Code of the event that caused the impact to the loyalty points |
CUST_ORDR_NBR / RTL_TNDR_LI_TRX_NBR/ Acct_Pymt_CD |
whatever is in EVT_CD (+ acct_key+ acct_bal_typ_key) of ACCT_BAL_IMPC_BAL |
INVC_CD |
Invoice Code |
RTL_TNDR_LI( if retail receipt is not part of Invoice) => NULL CUST_ORDR => no INVC_CD => NULL Acct_Pymt.INVC_CD otherwise |
Only if relevant and available. |
LYLTY_PROG_EVT _TYP_CD |
Type of Event Number stored as text to give some flexibility in event type. You may add at least 999 different codes if required. |
'3000' or '3xxx' |
'2000' or '2XXX' |
PRMTN_KEY |
Promotion |
What is bought through redemption is always a Promotion: RTL_TNDR_LI: CPN_TNDR_PRMTN_KEY CUST_ORD : PRMTN_KEY ACCT_PYMT: PRMTN_KEY |
|
PRTY_LYLTY_PROG _PRTCPTN_KEY |
PARTY Participation to the Loyalty Program One can choose which party one wants to store here: The partner or the customer. |
Best way: access DWR_LYLTY_ACCT_IDNTFR table (through MEMBERSHIP ACCOUNT ACCOUNT IDENTIFIER = FREQ SHOPPR NBR for RETAIL and CUST ORDR and MEMBERSHIP ACCOUNT ACCOUNT IDENTIFIER for PAYMNT) + get LYLTY_PROG from this table Alternative: Use through CUST_KEY (PRTY_KEY) and find LYLTY_PROG in DWR_PRTY_LYLTY_PROG_PRTCPTN |
Similar as earning is not immediately available in the event. |
RDMPTN_TYP_CD |
Redemption Type Code |
RTL_tndr_LI & Cust ORDR => "Amount Redeemed" ACCT_PYMT=> ACCT_PYMT_RSN_TYP_CD |
null |
REDMD_AMT |
Redeemed Amount |
RTL_tndr_LI: TNDR_AMT Cust_ord: EXTND_AMT ACCT_PYMT:PYMT_AMT |
Not applicable. |
SL_CHNL_KEY |
Sales Channel Key |
RTL_tndr_LI: Use null or ORG_BSNS_UNIT_TYP_CD Cust_ord: SL_CHNL_KEY ACCT_PYMT:PYMT_CHNL_KEY |
Not applicable. |
SL_CHNL_RPRSTV _KEY |
Sales Channel Representative |
Retail: OPRTR_EMP_KEY CUST_ORDR: SL_CHNL_RPRSTV_KEY ACCT_PYMT: EMP_KEY |
Not applicable. |
TRX_DT |
Transaction Date |
CUSt_ordr. INTRACN_DT rtl_tndr_li: END_DT_TIME acctpymt: pymt_DT |
Event start date that caused the increase in loyalty points. |
The following describes the main entities related to some major or typical subject areas in Oracle Communications Data Model:
Note:
The entity-relationship figures of the major reference entities in those subject areas are available with the Oracle Communications Data Model IP Patch. The IP Patch includes additional documentation. To obtain the IP Patch and for the latest information about Oracle Communications Data Model patch sets, go to My Oracle Support at https://support.oracle.com
.
This section lists the entities associated with the subject area Account.
Entities of Subject Area: Account
ACCOUNT
ACCOUNT ACCOUNTING CYCLE HISTORY
ACCOUNT ADJUSTMENT REASON
ACCOUNT AGREEMENT RELATIONSHIP
ACCOUNT ASSIGNMENT
ACCOUNT ASSIGNMENT REASON
ACCOUNT ASSIGNMENT TYPE
ACCOUNT BALANCE
ACCOUNT BALANCE ADJUSTMENT TYPE
ACCOUNT BALANCE GROUP
ACCOUNT BALANCE IMPACT
ACCOUNT BALANCE TYPE
ACCOUNT BILLING CYCLE HISTORY
ACCOUNT BILLING FREQUENCY HISTORY
ACCOUNT BILLING OCCURRENCE
ACCOUNT BILLING PERIOD HISTORY
ACCOUNT MANAGEMENT HISTORY
ACCOUNT PARTY PRODUCT OFFERING RELATIONSHIP
ACCOUNT PAYMENT
ACCOUNT PAYMENT METHOD
ACCOUNT PAYMENT METHOD STATUS
ACCOUNT PAYMENT METHOD STATUS REASON
ACCOUNT PAYMENT METHOD STATUS TYPE
ACCOUNT PREFERRED INVOICE DELIVERY
ACCOUNT PRODUCT OFFERING PARTICIPATION HISTORY
ACCOUNT PROFILE
ACCOUNT ROLE TYPE
ACCOUNT SEGMENT
ACCOUNT SEGMENT ASSIGNMENT HISTORY
ACCOUNT SEGMENTATION MODEL
ACCOUNT STATUS HISTORY
ACCOUNT STATUS REASON
ACCOUNT STATUS TYPE
ACCOUNT TYPE
ACCOUNTING CYCLE
ADDRESS LOCATION
BANK DIRECT DEBIT CHANNEL
BILLING CYCLE
BILLING FREQUENCY
BILLING PERIOD
CREDIT CATEGORY
CURRENCY
CUSTOMER
INVOICE
INVOICE DELIVERY TYPE
LANGUAGE
ORGANIZATION BUSINESS UNIT
PARTY
PARTY ACCOUNT ASSIGNMENT
PARTY ACCOUNT ASSIGNMENT TYPE
PAYMENT METHOD TYPE
PRODUCT OFFERING
PRODUCT SUBSCRIPTION
SEGMENT CRITERIA
SEGMENT TYPE
UNIT OF MEASURE
This section lists the entities associated with the subject area Agreement.
Entities of Subject Area: Agreement
ACCOUNT
ACCOUNT AGREEMENT RELATIONSHIP
AGREEMENT
AGREEMENT APPROVAL
AGREEMENT APPROVAL ASSIGNMENT
AGREEMENT ASSIGNMENT
AGREEMENT ASSIGNMENT REASON
AGREEMENT ASSIGNMENT TYPE
AGREEMENT CHANGE INITIATOR TYPE
AGREEMENT CHANGE REASON
AGREEMENT CHANGE TYPE
AGREEMENT DOCUMENT
AGREEMENT INTENT
AGREEMENT ITEM
AGREEMENT PRODUCT SPECIFICATION ASSIGNMENT
AGREEMENT SLA RELATIONSHIP
AGREEMENT STATUS
AGREEMENT STATUS REASON
AGREEMENT STATUS TYPE
AGREEMENT TERM
AGREEMENT TERM TYPE
AGREEMENT TYPE
CUSTOMER
CUSTOMER DOCUMENT
CUSTOMER ORDER
DOCUMENT TYPE
EQUIPMENT RENTING AGREEMENT
EVENT AGREEMENT
INSTALLMENT AGREEMENT
INVOICE
INVOICE PAYMENT TERM TYPE
KEY PERFORMANCE INDICATOR SLS PARM
KEY QUALITY INDICATOR SLS PARM
LOOKUP
NEGOTIATED SERVICE LEVEL SPEC
PARTY AGREEMENT ASSIGNMENT
PARTY AGREEMENT ASSIGNMENT ROLE
PARTY AGREEMENT ASSIGNMENT TYPE
PRODUCT OFFERING
PRODUCT SPECIFICATION
PROMOTION
SERVICE LEVEL AGREEMENT
SERVICE LEVEL AGREEMENT ITEM
SERVICE LEVEL AGREEMENT RELATIONSHIP
SERVICE LEVEL AGREEMENT TYPE
SERVICE LEVEL AGREEMENT VIOLATION
SERVICE LEVEL OBJECTIVE
SERVICE LEVEL SPECIFICATION APPLICABILITY
SERVICE LEVEL SPECIFICATION CONSEQUENCE
SERVICE LEVEL SPECIFICATION PARAMETER
SERVICE LEVEL UNMET CONSEQUENCE TYPE
SERVICE SPECIFICATION
TARGET AGREEMENT
TEMPLATE SERVICE LEVEL SPEC
UNIT OF MEASURE
VENDOR AGREEMENT
This section lists the entities associated with the subject area Billing.
Entities of Subject Area: Billing
ACCESS METHOD
ACCOUNT
ACCOUNT BILLING CYCLE HISTORY
ACCOUNT BILLING FREQUENCY HISTORY
ACCOUNT BILLING OCCURRENCE
ACCOUNT BILLING PERIOD HISTORY
ACCOUNT PAYMENT
ACCOUNT PAYMENT METHOD
ACCOUNT PREFERRED INVOICE DELIVERY
AGREEMENT
BILLING CYCLE
BILLING FREQUENCY
BILLING OCCURRENCE TYPE
BILLING PERIOD
BILLING STATUS CATEGORY
BILLING STATUS REASON
BILLING STATUS TYPE
CURRENCY
CUSTOMER
EMPLOYEE
EMPLOYEE JOB ROLE ASSIGNMENT
EXTERNAL OPERATOR
INVOICE
INVOICE ADJUSTMENT
INVOICE ADJUSTMENT QUOTA
INVOICE ADJUSTMENT REASON
INVOICE ADJUSTMENT TYPE
INVOICE DELIVERY FORMAT
INVOICE DELIVERY TYPE
INVOICE DISCOUNT
INVOICE DISCOUNT REASON
INVOICE DISCOUNT TYPE
INVOICE GENERATION PROCESS
INVOICE ITEM
INVOICE ITEM DETAIL
INVOICE ITEM DETAIL TYPE
INVOICE ITEM RELATIONSHIP
INVOICE ITEM TYPE
INVOICE PAYMENT ASSIGNMENT
INVOICE PAYMENT TERM
INVOICE PAYMENT TERM TYPE
INVOICE PROCESS ASSIGNMENT
INVOICE STATUS
INVOICE STATUS HISTORY
INVOICE STATUS TYPE
INVOICE TAX ITEM
INVOICE TYPE
INVOLVEMENT ROLE
JOB ROLE
JOURNAL ENTRY LINE INVOICE ITEM ASSIGNMENT
LANGUAGE
ORGANIZATION BUSINESS UNIT
PRICE EVENT
PRICE TYPE
PROCESS INVOICE DISPATCHING EVENT
PROCESS INVOICE GENERATION EVENT
PROCESS INVOICE ISSUING EVENT
PRODUCT OFFERING PRICE
PRODUCT SPECIFICATION
PRODUCT SUBSCRIPTION
SERVICE
TAX CATEGORY
UNIT OF MEASURE
This section lists the entities associated with the subject area Business Interaction.
Entities of Subject Area: Business Interaction
ACCOUNT
ACCOUNT BUSINESS INTERACTION ROLE
AGREEMENT
AGREEMENT APPROVAL
APPOINTMENT
APPOINTMENT TYPE
BUSINESS INTERACTION
BUSINESS INTERACTION ASSIGNMENT
BUSINESS INTERACTION ASSIGNMENT TYPE
BUSINESS INTERACTION CHARACTERISTIC
BUSINESS INTERACTION CHARACTERISTIC TYPE
BUSINESS INTERACTION CHARACTERISTIC VALUE
BUSINESS INTERACTION HISTORY
BUSINESS INTERACTION ITEM
BUSINESS INTERACTION ITEM PRICE
BUSINESS INTERACTION ITEM SPECIFICATION
BUSINESS INTERACTION LOCATION ASSIGNMENT
BUSINESS INTERACTION PAYMENT ASSIGNMENT
BUSINESS INTERACTION ROLE
BUSINESS INTERACTION SPECIFICATION
BUSINESS INTERACTION STATUS REASON
BUSINESS INTERACTION VERSION
CUSTOMER
CUSTOMER ORDER
CUSTOMER ORDER LINE ITEM
NP REQUEST HEADER
NP REQUEST LINE ITEM
NP REQUEST LINE ITEM STATE HISTORY
NP REQUEST LINE ITEM STATE TYPE
NP REQUEST STATE HISTORY
NP REQUEST STATE TYPE
NP REQUEST TYPE
NP STEP
PARTY
PARTY BUSINESS INTERACTION ROLE
PRODUCT SPECIFICATION
PRODUCT SUBSCRIPTION
PURCHASE ORDER
PURCHASE ORDER LINE ITEM
RESOURCE
RESOURCE BUSINESS INTERACTION ROLE
RESOURCE ORDER
RESOURCE ORDER LINE ITEM
SERVICE
SERVICE ORDER
SERVICE ORDER LINE ITEM
VENDOR AGREEMENT
Entities of Subject Area: Click Stream
AGENT
CAMPAIGN
CLIENT
CLIENT HOST
CLIENT VERSION
DAY
DOMAIN
DOMAIN TYPE
EVENT
EVENT TYPE
GEOGRAPHY COUNTRY
GEOGRAPHY REGION
GEOGRAPHY SUB REGION
IMPRESSION
IMPRESSION EVENT TYPE
OPERATING SYSTEM
PAGE
PLATFORM
REFERRING CATEGORY
REFERRING CATEGORY LEVEL
REFERRING SITE
REFERRING URL
SEARCH
SECOND
SECURE HOLDER
SERVER
SERVER FARM
SERVER STATUS
SESSION
SESSION TYPE
SITE
SITE INTERFACE ROLE
SITE ROLE
SITE TYPE
VISITOR
VISITOR TYPE
WEBSITE
WEBSITE USER
Entities of Subject Area: Cost
This section lists the entities associated with the subject area Cost.
ACCOUNT
ACCOUNT COST
ACCOUNTING ITEM CATEGORY
CAMPAIGN COST
CELL SITE COST
CHANNEL COST
COST
COST CENTER
COST CENTER BUDGET
COST SUBTYPE
COST TYPE
COURIER COST
CUSTOMER COST
EMPLOYEE COST
EQUIPMENT CENTER COST
EVENT COST
GL ACCOUNT
GL COST CENTER SEGMENT
MEDIA OBJECT COST
ORGANIZATION BUSINESS UNIT COST
PARTY
PARTY COST ASSIGNMENT
PROCESS COST
PRODUCT OFFERING COST
PRODUCT SPECIFICATION
PRODUCT SPECIFICATION COST
PROJECT
PROMOTION COST
RESOURCE
RESOURCE COST
SERVICE
This section lists the entities associated with the subject area Customer.
ACCOUNT
ACCOUNT PAYMENT
ADDRESS LOCATION
AGREEMENT
ARPU BAND
BARING REASON
BLACK LIST HISTORY
CALENDAR MONTH
CREDIT SCORE PROVIDER
CUSTOMER
CUSTOMER ACCOUNT
CUSTOMER ADDRESS
CUSTOMER AFFILIATION
CUSTOMER CLASS
CUSTOMER CLASS ASSIGNMENT
CUSTOMER CLUSTER
CUSTOMER CLUSTER TYPE
CUSTOMER COMMUNITY
CUSTOMER COST
CUSTOMER DOCUMENT
CUSTOMER FACING SERVICE
CUSTOMER FACING SERVICE ROLE
CUSTOMER FACING SERVICE SPECIFICATION
CUSTOMER FACING SERVICE SPECIFICATION ATOMIC
CUSTOMER FACING SERVICE SPECIFICATION COMPOSITE
CUSTOMER FACING SERVICE SPECIFICATION ROLE
CUSTOMER FACING SERVICE SPECIFICATION VERSION
CUSTOMER FIELD SERVICE ACTIVITY
CUSTOMER FIELD SERVICE DETAIL
CUSTOMER GROUP
CUSTOMER GROUP ASSIGNMENT
CUSTOMER GROUP ITEM
CUSTOMER INDIVIDUAL
CUSTOMER OCCASION
CUSTOMER OCCASION TYPE
CUSTOMER ORDER
CUSTOMER ORDER DOCUMENT
CUSTOMER ORDER LINE ITEM
CUSTOMER ORDER LINE ITEM STATE ASSIGN
CUSTOMER ORDER PAYMENT
CUSTOMER ORDER PRIORITY TYPE
CUSTOMER ORDER STATE ASSIGNMENT
CUSTOMER ORDER STATE CHANGE REASON
CUSTOMER ORGANIZATION
CUSTOMER PREFERENCE
CUSTOMER RELATIONSHIP
CUSTOMER RELATIONSHIP TYPE
CUSTOMER RESTRICTED INFO
CUSTOMER REVENUE BAND
CUSTOMER REVENUE BAND ASSIGNMENT
CUSTOMER REVENUE TYPE
CUSTOMER SCORE
CUSTOMER SEGMENT
CUSTOMER SEGMENTATION MODEL
CUSTOMER SIC ASSIGNMENT
CUSTOMER SOURCE
CUSTOMER STATUS REASON
CUSTOMER TYPE
DERIVED VALUE
EDUCATION
EVENT PARTY INTERACTION
EXTERNAL CREDIT PROFILE
EXTERNAL CREDIT PROFILE ASSIGNMENT
EXTERNAL ORGANIZATION TYPE
GENDER
HOUSEHOLD
INITIATIVE RESULT TYPE
INITIATIVE TYPE
INVOICE
JOB
LANGUAGE
MARITAL STATUS
PARTY
PARTY PROMOTION RESPONSE
PARTY STATUS HISTORY
PROMOTION
PROSPECT
SEGMENT CRITERIA
SOC JOB
SOC JOB CATEGORY
SOC JOB GROUP
UNIT OF MEASURE
VALUE TYPE
Entities of Subject Area: Customer Field
This section lists the entities associated with the subject area Customer Field.
ACCOUNT MANAGEMENT HISTORY
AGREEMENT
CUSTOMER
CUSTOMER FIELD SERVICE ACTIVITY
CUSTOMER FIELD SERVICE DETAIL
CUSTOMER ORDER
CUSTOMER ORDER LINE ITEM
CUSTOMER ORDER PRIORITY TYPE
DEALER
EMPLOYEE
FIELD ACTIVITY RESULT TYPE
FIELD ACTIVITY TYPE
ORDER STATE
ORDER STATE TYPE
ORDER TYPE
ORGANIZATION BUSINESS UNIT
PRODUCT CATALOG
PRODUCT SPECIFICATION
SALES COMMISSION PLAN DETAIL
Entities of Subject Area: Employee
BUSINESS UNIT JOB ROLE
COST CENTER
CURRENCY
EMPLOYEE
EMPLOYEE ACTUAL LABOR HOURLY
EMPLOYEE COST
EMPLOYEE DESIGNATION
EMPLOYEE EXPENSE REPORT
EMPLOYEE EXPENSE REPORT ITEM
EMPLOYEE EXPENSE REPORT STATE
EMPLOYEE JOB ROLE ASSIGNMENT
EMPLOYEE JOB ROLE TYPE
EMPLOYEE LANGUAGE CAPABILITY
EMPLOYEE RESTRICTED INFO
EMPLOYEE SCHEDULE
EMPLOYEE TRAINING RECORD
EMPLOYEE TYPE
EVENT
EVENT EMPLOYEE PAYROLL
EVENT PARTY ASSIGNMENT
EXPENSE REPORT PARTY ASSIGNMENT
EXPENSE REPORT STATE TYPE
EXPENSE TYPE
GL ACCOUNT
JOB ROLE
ORGANIZATION BUSINESS UNIT
PARTY
PAYMENT METHOD TYPE
PRODUCT SPECIFICATION
Entities of Subject Area: Event
This section lists the entities associated with the subject area Event.
ACCOUNT EVENT TYPE
ADDRESS LOCATION
CAMPAIGN CHANNEL
CHANNEL
EVENT
EVENT ACCESS METHOD ACTIVITY
EVENT ACCOUNT
EVENT AGREEMENT
EVENT ASSIGNMENT
EVENT ASSIGNMENT REASON
EVENT ASSIGNMENT TYPE
EVENT CATEGORY
EVENT CIRCUIT RENTAL
EVENT CLASS
EVENT COMPOSITE PRODUCT SPECIFICATION
EVENT COST
EVENT EMIT DETAIL
EVENT EMPLOYEE ACTIVITY
EVENT EMPLOYEE PAYROLL
EVENT EQUIPMENT INSTANCE
EVENT FINANCIAL
EVENT GEOGRAPHY
EVENT LOCATION
EVENT LOYALTY PROGRAM
EVENT PARTY ASSIGNMENT
EVENT PARTY INTERACTION
EVENT PARTY INTERACTION CHARACTERISTIC VALUE
EVENT PARTY INTERACTION CHAT DETAIL
EVENT PARTY INTERACTION ITEM
EVENT PARTY INTERACTION PARTICIPATION
EVENT PARTY PROFILE
EVENT PARTY ROLE
EVENT PREPAID MOBILE
EVENT PRODUCT SUBSCRIPTION WIRELESS
EVENT REASON
EVENT REASON CATEGORY
EVENT RESOLUTION
EVENT RESPONSE REASON
EVENT RESULT
EVENT SIM CARD
EVENT STATUS
EVENT STATUS REASON
EVENT STATUS TYPE
EVENT SUBSCRIPTION CHANGE
EVENT TRIGGER DETAIL
EVENT TYPE
GL ACCOUNT
INVOICE
INVOICE DELIVERY TYPE
NETWORK
ORGANIZATION BUSINESS UNIT
PARTY
PARTY EVENT TYPE
PREPAID MOBILE EVENT TYPE
PRODUCT SPECIFICATION
PRODUCT SUBSCRIPTION
Entities of Subject Area: Financial GL Cost and Asset
This section lists the entities associated with the subject area Financial GL Cost and Asset.
ASSET
ASSET APPRAISAL HISTORY
ASSET CONDITION HISTORY
ASSET DEPRECIATION HISTORY
ASSET PARTY ASSOCIATION
ASSET SITE ASSIGNMENT
ASSET TYPE
BUSINESS ASSET
CHANNEL
COLLECTION TYPE
COST
COST CENTER
COST REASON
COST SUBTYPE
COST TYPE
CURRENCY
CUSTOMER ORDER
CUSTOMER ORDER LINE ITEM
EMPLOYEE
FISCAL QUARTER
FISCAL YEAR
GL ACCOUNT
GL ACCOUNT ASSIGNMENT
GL ACCOUNT SEGMENT
GL ACCOUNT TYPE
GL BALANCE
GL COST CENTER SEGMENT
GL JE LINE SUBLEDGER ASSIGNMENT
GL JOURNAL ENTRY
GL JOURNAL ENTRY BATCH
GL JOURNAL ENTRY CATEGORY
GL JOURNAL ENTRY LINE
GL LEDGER
GL LEDGER ACCOUNT ASSIGNMENT
GL ORGANIZATION BUSINESS UNIT SEGMENT
GL PERIOD
GL PRODUCT SPECIFICATION SEGMENT
GL PROJECT SEGMENT
GL REFERENCE
GL SEGMENT
GL SEGMENT TYPE
GL SUBLEDGER
GL SUBLEDGER JOURNAL ENTRY
GL SUBLEDGER JOURNAL ENTRY LINE
INVOICE ITEM
JOURNAL ENTRY LINE CUSTOMER ORDER ITEM ASSIGNMENT
JOURNAL ENTRY LINE INVOICE ITEM ASSIGNMENT
ORGANIZATION BUSINESS UNIT
PARTY
PARTY PROJECT PARTICIPATION
PRODUCT SPECIFICATION
PROJECT
PROJECT ELEMENT
SALES CHANNEL
SALES CHANNEL COMMISSION PLAN ASSIGNMENT
SALES COMMISSION DETAIL
SALES COMMISSION PLAN
SALES COMMISSION PLAN DETAIL
TASK
Entities of Subject Area: Flexible Characteristics
This section lists the entities associated with the subject area Flexible Characteristics.
BUSINESS INTERACTION CHARACTERISTIC
CAMPAIGN CHARACTERISTIC
COMP INTEL CHARACTERISTIC
COMP PROD CRRL CHARACTERISTIC
DEMOGRAPHIC CHARACTERISTIC
FLEXIBLE CHARACTERISTIC
FLEXIBLE CHARACTERISTIC ASSIGNMENT
FLEXIBLE CHARACTERISTIC ASSIGNMENT TYPE
FLEXIBLE CHARACTERISTIC RELATIONSHIP
FLEXIBLE CHARACTERISTIC TYPE
FLEXIBLE CHARACTERISTIC VALUE
FLEXIBLE CHARACTERISTIC VALUE ASSIGNMENT
FLEXIBLE CHARACTERISTIC VALUE RELATIONSHIP
MARKET SEGMENT CHARACTERISTIC
PARTY PROFILE TYPE CHARACTERISTIC
PIT CHARACTERISTIC
PRODUCT CATALOG CHARACTERISTIC
PRODUCT SPECIFICATION CHARACTERISTIC
RESOURCE CHARACTERISTIC
RESOURCE SPECIFICATION CHARACTERISTIC
SERVICE PROBLEM CHARACTERISTIC
SERVICE SPECIFICATION CHARACTERISTIC
UDR EVENT CHARACTERISTIC
UDR EVENT SPECIFICATION CHARACTERISTIC
Entities of Subject Area: Loyalty Program
This section lists the entities associated with the subject area Loyalty Program.
ACCOUNT
ACCRUAL EVENT
AGREEMENT
AGREEMENT PRODUCT SPECIFICATION ASSIGNMENT
AWARD LEVEL
CHANNEL
COMPENSATORY REASON
CUSTOMER
CUSTOMER RFMP SCORE
ENROLL CHANNEL
ENROLL TYPE
EVENT
EVENT LOYALTY PROGRAM
EXPIRY BASIS TYPE
ITEM SPECIFICATION
LOYALTY MEMBERSHIP ENROLL
LOYALTY PROGRAM
LOYALTY TIER
LOYALTY TIER CHANGE HISTORY
LOYALTY TIER CLASS
MEMBERSHIP ACCOUNT
MEMBERSHIP ACCOUNT BALANCE HISTORY
ORGANIZATION
ORGANIZATION BUSINESS UNIT
PARTY
POINT BLOCK
POINTS EXPIRY BASIS
PROMOTION
PROMOTION COST
REDEMPTION EVENT
REDEMPTION TYPE
RETAIL TRANSACTION LINE ITEM
SKU ITEM
TIER CARD TYPE
Entities of Subject Area: Number Porting
This section lists the entities associated with the subject area Number Porting.
ACCESS METHOD
ACCOUNT
AGREEMENT
AGREEMENT TYPE
CHANNEL
CUSTOMER
DEALER
EMPLOYEE
EXTERNAL OPERATOR
INITIATIVE TYPE
NP MOBILE MSISDN
NP REQUEST HEADER
NP REQUEST LINE ITEM
NP REQUEST LINE ITEM STATE HISTORY
NP REQUEST LINE ITEM STATE TYPE
NP REQUEST STATE HISTORY
NP REQUEST STATE REASON
NP REQUEST STATE TYPE
NP REQUEST TYPE
NP STEP
Entities of Subject Area: Party
This section lists the entities associated with the subject area Party.
ACCOUNT
ANZSIC CLASSIFICATION
BANK
BLACK LIST HISTORY
BUSINESS LEGAL STATUS
COLLECTION AGENCY
CONTACT ROLES
CONTENT PROVIDER
COST
COST CENTER
CUSTOMER
CUSTOMER OCCASION
CUSTOMER OCCASION TYPE
CUSTOMER ORGANIZATION
CUSTOMER SIC ASSIGNMENT
DEALER
DEMOGRAPHY ATTRIBUTE
DEMOGRAPHY GROUP
EMPLOYEE
EMPLOYEE JOB ROLE ASSIGNMENT
EVENT
EXTERNAL INFORMATION SOURCE
EXTERNAL OPERATOR
EXTERNAL ORGANIZATION TYPE
INDIVIDUAL DEMOGRAPHY VALUE
ISP
JOB ROLE
LANGUAGE
NAICS CLASSIFICATION
ORGANIZATION BUSINESS UNIT
PARTY
PARTY ADDRESS LOCATION ASSIGNMENT
PARTY ASSIGNMENT
PARTY ASSIGNMENT REASON
PARTY ASSIGNMENT TYPE
PARTY CONTACT INFORMATION
PARTY CONTACT INFORMATION TYPE
PARTY COST ASSIGNMENT
PARTY GEOGRAPHY ENTITY ASSIGNMENT
PARTY LOCATION REASON
PARTY LOCATION TYPE
PARTY ROLE
PARTY ROLE ASSIGNMENT
PARTY ROLE STATUS
PARTY STATUS CATEGORY
PARTY STATUS CHANGE REASON
PARTY STATUS HISTORY
PARTY STATUS HISTORY
PARTY TYPE
PROSPECT
SIC ASSIGNMENT
SIC ASSIGNMENT REASON
SIC CLASSIFICATION
SOURCE SYSTEM
SOURCE SYSTEM KEY MAPPING
TAX AUTHORITY
VENDOR
This section lists the entities associated with the subject area Party Partners Vendor Roaming Content.
ACCESS METHOD PORTING HISTORY
CONTENT
CONTENT DELIVERY EVENT
CONTENT PRICE
CONTENT PROVIDER
CONTENT TYPE
COURIER
DEAL
DEAL LINE ITEM
EXTERNAL OPERATOR
OPERATOR GROUP
OPERATOR TYPE
PARTNER PAYMENT
PARTNER PROMOTION PROGRAM
PARTY
PRODUCT SPECIFICATION
RESOURCE SPECIFICATION
SITE
TAP IN WIRELESS ROAMING EVENT
TAP OUT WIRELESS ROAMING EVENT
VENDOR
VENDOR AGREEMENT
VENDOR APPOINTMENT
VENDOR CLASS
VENDOR RATING
VENDOR SITE
VENDOR SITE COURIER ASSIGNMENT
WIRELESS ROAMING EVENT
WIRELESS ROAMING EVENT BATCH
Entities of Subject Area: Payment
This section lists the entities associated with the subject area Payment.
ACCOUNT
ACCOUNT BALANCE IMPACT
ACCOUNT BALANCE TYPE
ACCOUNT PAYMENT
ACCOUNT PAYMENT METHOD
ACCOUNT PAYMENT METHOD STATUS
ACCOUNT PAYMENT METHOD STATUS TYPE
ACCOUNT REFUND REASON
AGREEMENT
BANK
CURRENCY
CUSTOMER
EMPLOYEE
EVENT
INVOICE
INVOICE ADJUSTMENT
INVOICE PAYMENT ASSIGNMENT
INVOICE PAYMENT TERM TYPE
ORGANIZATION BUSINESS UNIT
PARTY ACCOUNT ASSIGNMENT
PARTY ACCOUNT ASSIGNMENT TYPE
PAYMENT CHANNEL
PAYMENT METHOD TYPE
PAYMENT TRANSACTION TYPE
Entities of Subject Area: Prepaid Balance and Voucher
This section lists the entities associated with the subject area Prepaid Balance and Voucher.
ACCOUNT
ACCOUNT BALANCE TYPE
ACCOUNT PAYMENT
EVENT
HOME SUBSCRIBER SERVER
IN PLATFORM
IN ROUTING DEVICE
ITEM SPECIFICATION
PARTY
PREPAID MOBILE EVENT TYPE
PREPAID RECHARGE
PREPAID VOUCHER
PREPAID VOUCHER BATCH
PREPAID VOUCHER RECHARGE OPTION
PREPAID VOUCHER SPECIFICATION
PRODUCT
PRODUCT SPECIFICATION
UNIT OF MEASURE
Entities of Subject Area: Problem
This section lists the entities associated with the subject area Problem.
ACCOUNT
ADDRESS LOCATION
CUSTOMER FACING SERVICE
CUSTOMER FIELD SERVICE ACTIVITY
EMPLOYEE
EVENT PARTY INTERACTION
FAULT RESOLUTION TYPE
FAULT TYPE
INTERACTION DIRECTION
INTERACTION RESULT TYPE
INTERACTION STATUS
INTERACTION TYPE
PROBLEM
PROBLEM COMMENTS
PROBLEM ESCALATION LEVEL
PROBLEM LOCATION ASSIGNMENT
PROBLEM RELATIONSHIP
PROBLEM RESOURCE ASSIGNMENT
PROBLEM SERVICE ASSIGNMENT
PROBLEM STATUS HISTORY
PROBLEM TRACKING RECORD ASSIGNMENT
PROBLEM TROUBLE TICKET ASSIGNMENT
PRODUCT SUBSCRIPTION
RESOURCE
RESOURCE FAULT ASSIGNMENT
SERVICE
SERVICE PROBLEM
SERVICE PROBLEM RESOURCE ALARM ASSIGNMENT
SERVICE PROBLEM SERVICE ASSIGNMENT
SERVICE PROBLEM SUBSCRIPTION ASSIGNMENT
TRACKING RECORD
TROUBLE TICKET
Entities of Subject Area: Process
This section lists the entities associated with the subject area Process.
COST
FLEXIBLE CHARACTERISTIC
FLEXIBLE CHARACTERISTIC VALUE ASSIGNMENT
INVOICE
INVOICE DELIVERY FORMAT
INVOICE DELIVERY TYPE
INVOICE PROCESS ASSIGNMENT
PROCESS
PROCESS COST
PROCESS EVENT
PROCESS EVENT ASSIGNMENT
PROCESS EVENT PARAMETER VALUE OPERATOR ASSIGNMENT
PROCESS INVOICE DISPATCHING EVENT
PROCESS INVOICE GENERATION EVENT
PROCESS INVOICE ISSUING EVENT
PROCESS PARAMETER
PROCESS PARAMETER ASSIGNMENT
PROCESS PARAMETER OPERATOR
PROCESS PARAMETER VALUE
PROCESS RELATIONSHIP
PROCESS RELATIONSHIP TYPE
PROCESS SPECIFICATION
PROCESS STATUS
PROCESS TYPE
Entities of Subject Area: Product Offering and Product Subscription
This section lists the entities associated with the subject area Product Offering and Product Subscription.
PRODUCT OFFERING
PRODUCT OFFERING ASSIGNMENT TYPE
PRODUCT OFFERING AVAILABILITY
PRODUCT OFFERING COST
PRODUCT OFFERING DOCUMENT REQUIREMENT
PRODUCT OFFERING GEOGRAPHY ASSIGNMENT
PRODUCT OFFERING GROUP
PRODUCT OFFERING GROUP ASSIGNMENT
PRODUCT OFFERING GROUP TYPE
PRODUCT OFFERING MANAGEMENT
PRODUCT OFFERING MARKET SEGMENT AVAILABILITY
PRODUCT OFFERING ORGANIZATION AVAILABILITY
PRODUCT OFFERING PRICE
PRODUCT OFFERING PRICE COMPONENT
PRODUCT OFFERING PRICE COMPOSITE
PRODUCT OFFERING PRICE POLICY ACTION
PRODUCT OFFERING PRICE POLICY CONDITION
PRODUCT OFFERING PRICE POLICY VALUE
PRODUCT OFFERING PRICE POLICY VARIABLE
PRODUCT OFFERING PRICE RECURRING
PRODUCT OFFERING PRICE RELATIONSHIP
PRODUCT OFFERING PRICE TYPE
PRODUCT OFFERING PRODUCT ASSIGNMENT
PRODUCT OFFERING PRODUCT OFFERING PRICE ASSIGNMENT
PRODUCT OFFERING RATING PLAN
PRODUCT OFFERING RATING PLAN DETAIL
PRODUCT OFFERING RELATIONSHIP
PRODUCT OFFERING RELATIONSHIP TYPE
PRODUCT OFFERING SUBSTITUTE BY DOC
PRODUCT OFFERING TERM
PRODUCT SPECIFICATION CHARACTERISTIC RESOURCE SPECIFICATION CHARACTERISTIC ASSIGNMENT
PRODUCT SPECIFICATION CHARACTERISTIC VAL RESOURCE CHARACTERISTIC VAL ASSIGNMENT
PRODUCT SPECIFICATION GROUP
PRODUCT SPECIFICATION GROUP TYPE
PRODUCT SPECIFICATION
PRODUCT SPECIFICATION ADDITIONAL TEXT
PRODUCT SPECIFICATION ASSIGNMENT REASON
PRODUCT SPECIFICATION CATEGORY
PRODUCT SPECIFICATION CHARACTERISTIC
PRODUCT SPECIFICATION CHARACTERISTIC CONFIGURABLE ASSIGNMENT
PRODUCT SPECIFICATION CHARACTERISTIC RELATIONSHIP
PRODUCT SPECIFICATION CHARACTERISTIC USE
PRODUCT SPECIFICATION CHARACTERISTIC VALUE
PRODUCT SPECIFICATION CHARACTERISTIC VALUE RELATIONSHIP
PRODUCT SPECIFICATION CHARACTERISTIC VALUE USE
PRODUCT SPECIFICATION COLUMN
PRODUCT SPECIFICATION COST
PRODUCT SPECIFICATION COVERAGE AREA TYPE
PRODUCT SPECIFICATION COVERAGE GEO DETAIL
PRODUCT SPECIFICATION GROUP ASSIGNMENT
PRODUCT SPECIFICATION HISTORY
PRODUCT SPECIFICATION MANAGEMENT HISTORY
PRODUCT SPECIFICATION MANAGEMENT REASON
PRODUCT SPECIFICATION MANAGEMENT ROLE
PRODUCT SPECIFICATION NETWORK ASSIGNMENT
PRODUCT SPECIFICATION RELATIONSHIP
PRODUCT SPECIFICATION STATUS HISTORY
PRODUCT SPECIFICATION STATUS TYPE
PRODUCT SPECIFICATION TYPE
PRODUCT SPECIFICATION VERSION
This section lists the entities associated with the subject area Product Subscription.
ACCESS METHOD PRODUCT SUBSCRIPTION ASSIGNMENT
ACCOUNT
AGREEMENT
ALLOWANCE SUBSCRIPTION PRICE ALTERNATION
CALL FORWARD
CALLER ID
CAMPAIGN CHANNEL
CHANNEL
COMPOSITE PRODUCT SPECIFICATION
COMPOSITE PRODUCT SUBSCRIPTION PRICE
CUSTOMER
CUSTOMER FACING SERVICE
DISCOUNT SUBSCRIPTION PRICE ALTERATION
EQUIPMENT INSTANCE
IDD
MUSIC DOWNLOAD
ORGANIZATION BUSINESS UNIT
PARTY
PARTY PRODUCT SUBSCRIPTION ASSIGNMENT
PARTY PRODUCT SUBSCRIPTION ROLE
PHYSICAL RESOURCE PRODUCT SUBSCRIPTION
PRODUCT
PRODUCT OFFERING
PRODUCT PRICE ALTERATION
PRODUCT PRICE COMPONENT
PRODUCT PRICE PARTY ROLE
PRODUCT SPECIFICATION
PRODUCT SUBSCRIPTION
PRODUCT SUBSCRIPTION ASSIGNMENT
PRODUCT SUBSCRIPTION ASSIGNMENT TYPE
PRODUCT SUBSCRIPTION PRICE
PRODUCT SUBSCRIPTION STATUS
PRODUCT SUBSCRIPTION STATUS CATEGORY
PRODUCT SUBSCRIPTION STATUS HISTORY
PRODUCT SUBSCRIPTION STATUS REASON
PRODUCT SUBSCRIPTION TERM TYPE
PRODUCT SUBSCRIPTION TYPE
RESOURCE ROLE
RINGTONE
SALES CHANNEL REPRESENTATIVE
SERVICE
SIM CARD PRODUCT SUBSCRIPTION ASSIGNMENT
SUBSCRIPTION RESOURCE ROLE ASSIGNMENT
SUBSCRIPTION SERVICE ASSIGNMENT
SUBSCRIPTION TERM VALUE
VAS SUBSCRIPTION
Entities of Subject Area: Product and Product Specification
This section lists the entities associated with the subject area Product and Product Specification.
ACCESSORIES
ADDITIONAL TEXT
BRAND
BROADBAND RATING PLAN
COMMUNICATION SERVICE
COMPOSITE PRODUCT SPECIFICATION
COMPOSITE PRODUCT SPECIFICATION ASSIGNMENT
COMPOSITE PRODUCT SPECIFICATION CHARGE TYPE
CONTENT
CURRENCY
CUSTOMER ORDER
DOCUMENT CONDITION TYPE
DOCUMENT TYPE
EQUIPMENT
EQUIPMENT FUNCTIONALITY
EQUIPMENT FUNCTIONALITY ASSIGNMENT
EQUIPMENT INSTANCE
EXTERNAL OPERATOR
FIXED LINE RATING PLAN
GEOGRAPHY ENTITY
HANDSET MODEL
INVENTORY ITEM STATE
ITEM SPECIFICATION
LANGUAGE
MARKET SEGMENT
NETWORK TOUCHPOINT
ORGANIZATION BUSINESS UNIT
ORGANIZATION ITEM SELLING PRICE
ORGANIZATION WAREHOUSE
PARTY
POLICY
POLICY RULE
POLICY SET
PREPAID VOUCHER
PREPAID VOUCHER SPECIFICATION
PRICE DERIVATION RULE
PRICE TYPE
PRICE TYPE RELATION REASON
PRICE TYPE RELATIONSHIP
PRODUCT
PRODUCT CATALOG
PRODUCT CATALOG GEOGRAPHY ASSIGNMENT
PRODUCT CATALOG PRESENTATION TYPE
PRODUCT CATALOG PRODUCT OFFERING ASSIGNMENT
PRODUCT CATALOG SALES CHANNEL ASSIGNMENT
PRODUCT CATALOG TYPE
PRODUCT COVERAGE AREA
PRODUCT FUNCTIONALITY DEPENDENCY
PRODUCT LINE
PRODUCT OFFERING
PRODUCT OFFERING ASSIGNMENT TYPE
PRODUCT OFFERING AVAILABILITY
PRODUCT OFFERING DOCUMENT REQUIREMENT
PRODUCT OFFERING GEOGRAPHY ASSIGNMENT
PRODUCT OFFERING GROUP
PRODUCT OFFERING GROUP ASSIGNMENT
PRODUCT OFFERING GROUP TYPE
PRODUCT OFFERING MARKET SEGMENT AVAILABILITY
PRODUCT OFFERING ORGANIZATION AVAILABILITY
PRODUCT OFFERING PRICE
PRODUCT OFFERING PRICE TYPE
PRODUCT OFFERING PRODUCT ASSIGNMENT
PRODUCT OFFERING PRODUCT SPECIFICATION ASSIGNMENT
PRODUCT OFFERING RELATIONSHIP
PRODUCT OFFERING RELATIONSHIP TYPE
PRODUCT OFFERING SUBSTITUTE BY DOC
PRODUCT OFFERING TERM
PRODUCT OFFERING TYPE
PRODUCT SPECIFICATION GROUP
PRODUCT SPECIFICATION GROUP TYPE
PRODUCT SPECIFICATION
PRODUCT SPECIFICATION ADDITIONAL TEXT
PRODUCT SPECIFICATION ASSIGNMENT REASON
PRODUCT SPECIFICATION CATEGORY
PRODUCT SPECIFICATION CHARACTERISTIC
PRODUCT SPECIFICATION CHARACTERISTIC RELATIONSHIP
PRODUCT SPECIFICATION CHARACTERISTIC USE
PRODUCT SPECIFICATION CHARACTERISTIC VALUE
PRODUCT SPECIFICATION CHARACTERISTIC VALUE RELATIONSHIP
PRODUCT SPECIFICATION CHARACTERISTIC VALUE USE
PRODUCT SPECIFICATION COVERAGE AREA TYPE
PRODUCT SPECIFICATION COVERAGE GEO DETAIL
PRODUCT SPECIFICATION GROUP ASSIGNMENT
PRODUCT SPECIFICATION MANAGEMENT HISTORY
PRODUCT SPECIFICATION MANAGEMENT REASON
PRODUCT SPECIFICATION MANAGEMENT ROLE
PRODUCT SPECIFICATION NETWORK ASSIGNMENT
PRODUCT SPECIFICATION RELATIONSHIP
PRODUCT SPECIFICATION STATUS HISTORY
PRODUCT SPECIFICATION STATUS TYPE
PRODUCT SPECIFICATION TYPE
PRODUCT SPECIFICATION VERSION
PRODUCT STATUS HISTORY
PRODUCT STATUS TYPE
RATING METHOD TYPE
SALES CHANNEL
SERVICE SPECIFICATION
SET TOP BOX MODEL
SIM CARD
SIM CARD HANDSET ASSIGNMENT
SMS RATING PLAN
TV CHANNEL
VALUE ADDED SERVICE
VENDOR
WIRELESS RATING PLAN
Entities of Subject Area: Promotion and Campaign
This section lists the entities associated with the subject area Promotion and Campaign.
CAMPAIGN
CAMPAIGN CHANNEL
CAMPAIGN CHANNEL ASSIGNMENT
CAMPAIGN CHANNEL TYPE
CAMPAIGN CHARACTERISTIC
CAMPAIGN CHARACTERISTIC VALUE
CAMPAIGN MANAGEMENT HISTORY
CAMPAIGN MESSAGE
CAMPAIGN MESSAGE CREATIVE
CAMPAIGN MESSAGE DEPICTION
CAMPAIGN RELATIONSHIP
CAMPAIGN STATUS
CAMPAIGN TERM VALUE
CAMPAIGN TYPE
CONTACT LIST
CONTACT LIST CHANGE REASON
CONTACT LIST RECURRENCE TYPE
CUSTOMER SEGMENT
EVENT PARTY INTERACTION
GEOGRAPHY ENTITY
INITIATIVE TYPE
MARKET AREA
MARKET SEGMENT
MARKET SEGMENT INCLUSION
MEDIA OBJECT
MEDIA OBJECT ASSIGNMENT
MEDIA OBJECT TYPE
ORGANIZATION BUSINESS UNIT
PARTNER PROMOTION PROGRAM
PARTY
PARTY CONTACT LIST PARTICIPATION
PARTY CONTACT LIST ROLE
PARTY MANAGEMENT ROLE
PARTY MARKET SEGMENT ASSIGNMENT
PARTY PROMOTION RESPONSE
PRODUCT
PROMOTION
PROMOTION CLUSTER USAGE
PROMOTION CONTACT LIST UTILIZATION
PROMOTION MANAGEMENT HISTORY
PROMOTION MESSAGE RENDERING
PROMOTION PRODUCT CATALOG ASSIGNMENT
PROMOTION PRODUCT OFFERING ASSIGNMENT
PROMOTION RELATIONSHIP
PROMOTION RESULT TYPE
PROMOTION SALES CHANNEL ASSIGNMENT
PROMOTION TERM TYPE
PROMOTION TERM VALUE
PROMOTION TYPE
PROPOSAL
PROPOSAL RELATIONSHIP
PROSPECT
PROSPECT PRIORITY TYPE
PROSPECT QUALITY SCORE TYPE
PROSPECT QUALITY SCORE VALUE
PROSPECT REJECT REASON
PUBLICATION
SALES CHANNEL
SOURCE SYSTEM
SOURCE SYSTEM TYPE
SURVEY
TARGET ACCESS METHOD
TARGET ACCOUNT
TARGET AGREEMENT
TARGET GEOGRAPHY AREA
TARGET MARKET SEGMENT
TARGET TYPE
Entities of Subject Area: QoS
This section lists the entities associated with the subject area Quality of Service (QoS).
802 SERVICE
AF SERVICE
CLASS BASE WEIGHTED FAIR QUEUE SERVICE
CLASSIFIER SERVICE
COMPOUND CONDITIONING ELEMENT
CUSTOM QUEUING SERVICE
DEFICIT ROUND ROBIN SCHEDULING SERVICE
DIFFSERV SERVICE
DROPPER SERVICE
EF SERVICE
FAIR QUEUING SERVICE
HEAD TAIL DROPPER SERVICE
MARKER POOL
MARKER SERVICE
MARKER SERVICE MARKER POOL ASSIGNMENT
MARKER TYPE
METER PROFILE
METER SERVICE
METER SERVICE PROFILE ASSIGNMENT
NETWORK FORWARDING SERVICE
POLICIER SERVICE
PREAMBLE MARKER SERVICE
PREAMBLE MARKING DETAILS ASSIGNMENT
PRIORITY QUEUING SERVICE
QOS SERVICE
QOS SERVICE RELATIONSHIP
QOS SERVICE SPECIFICATION TYPE
QUEUE SERVICE
RED DROPPER SERVICE
RED SERVICE ELEMENT
RESOURCE FACING SERVICE
ROUND ROBIN SCHEDULING SERVICE
SCHEDULING SERVICE
SCHEDULING SERVICE ATOMIC
SCHEDULING SERVICE COMPOSITE
SHAPER SERVICE
STANDARD MARKER SERVICE
STRICT SCHEDULING SERVICE
TOKEN BUCKET
TOS SERVICE
TRAFFIC CONDITIONING SERVICE
TRAFFIC IDENTIFICATION SERVICE
TRAFFIC MATCH CRITERIA
WEIGHTED FAIR QUEUING SERVICE
WEIGHTED ROUND ROBIN SCHEDULING SERVICE
Entities of Subject Area: Resource
This section lists the entities associated with the subject area Resource.
ACCESS METHOD
ADDRESS LOCATION
CABLE
CAPACITY
CARD
CELL SITE
CELL SITE TYPE
CIRCUIT CATEGORY
CIRCUIT COMPONENT
__TODEL_CIRCUIT RENTAL
CIRCUIT RENTAL EVENT TYPE
CIRCUIT TRAFFIC
CIRCUIT TYPE
COMPOUND RESOURCE
COMPOUND RESOURCE SPEC
CONNECTION
DEVICE INTERFACE
EMPLOYEE
EQUIPMENT CENTER
EQUIPMENT HOLDER
EVENT CIRCUIT RENTAL
EXTERNAL OPERATOR
FIXED LINE PORT
HARDWARE
IN PLATFORM
IN ROUTING DEVICE
LOCAL ADDRESS LOCATION
LOGICAL DEVICE
LOGICAL RESOURCE
LOGICAL RESOURCE PHYSICAL SUPPORT
MANAGED HARDWARE
MANAGED TRANSMISSION ENTITY
MOBILE SWITCHING CENTER
NETWORK
NETWORK ADDRESS
NETWORK ASSIGNMENT
NETWORK ASSIGNMENT TYPE
NETWORK CAPACITY
NETWORK ROUTE
NETWORK ROUTE POINT
NETWORK ROUTE POINT ASSIGNMENT
NETWORK SERVICE COVERAGE ASSIGNMENT
NETWORK SERVICE COVERAGE ASSIGNMENT
NETWORK TOUCHPOINT
NETWORK TOUCHPOINT CLASS
NETWORK TOUCHPOINT TYPE
NETWORK TYPE
OPERATING SYSTEM
PARTY
PHYSICAL COMPONENT
PHYSICAL CONNECTOR
PHYSICAL CONTAINER
PHYSICAL DEVICE
PHYSICAL EQUIPMENT
PHYSICAL LINK
PHYSICAL PORT
PHYSICAL RESOURCE
PHYSICAL RESOURCE SPECIFICATION
PIPE
PRODUCT SPECIFICATION
PROTOCOL
RESOURCE
RESOURCE PARTY ASSOCIATION
RESOURCE PARTY MANAGEMENT
RESOURCE RELATIONSHIP
RESOURCE RELATIONSHIP TYPE
RESOURCE ROLE
RESOURCE ROLE SPECIFICATION
RESOURCE SPECIFICATION CATEGORY
RESOURCE SPECIFICATION
RESOURCE STATE HISTORY
RESOURCE STATE REASON
RESOURCE STATE TYPE
ROUTER
SERVICE COVERAGE AREA
SERVICE COVERAGE AREA TYPE
SERVICE COVERAGE GEO DETAIL
SERVICE EQUIPMENT ASSIGNMENT
SITE
SITE TYPE
SOFTWARE
SPECTRUM COVERAGE AREA
SWITCH
SWITCH CAPABILITY
SWITCH CAPABILITY TYPE
SWITCH ROUTING DEVICE ASSIGNMENT
SWITCH TYPE
TECHNOLOGY
TECHNOLOGY TYPE
TERMINATION POINT
TRAIL
VENDOR
WIRELESS SPECTRUM
Entities of Subject Area: Service and Service Specification
This section lists the entities associated with the subject area Service and Service Specification.
ACCESS METHOD SERVICE ASSIGNMENT
ACCOUNT
ADDRESS LOCATION
BROADBAND SERVICE
BUSINESS INTERACTION
BUSINESS INTERACTION ITEM
COMPOSITE SERVICE
COMPOSITE SERVICE INCLUSION
COMPOSITE SERVICE TYPE INCLUSION
COST
CUSTOMER FACING SERVICE
CUSTOMER FACING SERVICE ROLE
CUSTOMER FACING SERVICE SPECIFICATION
CUSTOMER FACING SERVICE SPECIFICATION ATOMIC
CUSTOMER FACING SERVICE SPECIFICATION COMPOSITE
CUSTOMER FACING SERVICE SPECIFICATION ROLE
CUSTOMER FACING SERVICE SPECIFICATION VERSION
EMAIL SERVICE
FDA
FIXED LINE SERVICE
FSAM
GEOGRAPHY CITY
GPRS SERVICE
MMS SERVICE
NETWORK SITE
PARTY
PARTY SERVICE ASSIGNMENT
PARTY SERVICE ASSIGNMENT REASON
PARTY SERVICE ASSIGNMENT ROLE
PAY TV SERVICE
PRODUCT
PRODUCT SUBSCRIPTION
QOS SERVICE
QOS SERVICE SPECIFICATION TYPE
RESOURCE
RESOURCE FACING SERVICE
RESOURCE FACING SERVICE ROLE
RESOURCE FACING SERVICE SPECIFICATION VERSION
RESOURCE FACING SERVICE SPECIFICATION
RESOURCE FACING SERVICE SPECIFICATION ATOMIC
RESOURCE FACING SERVICE SPECIFICATION COMPOSITE
RESOURCE FACING SERVICE SPECIFICATION ROLE
RESOURCE SPECIFICATION
SERVICE
SERVICE BUNDLE
SERVICE BUNDLE SPECIFICATION
SERVICE BUNDLE SPECIFICATION ATOMIC
SERVICE BUNDLE SPECIFICATION COMPOSITE
SERVICE COVERAGE AREA
SERVICE COVERAGE AREA TYPE
SERVICE COVERAGE GEO DETAIL
SERVICE DEPENDENCY
SERVICE LR DEPENDENCY
SERVICE ORDER
SERVICE ORDER LINE ITEM
SERVICE PACKAGE
SERVICE PACKAGE SPECIFICATION
SERVICE PACKAGE SPECIFICATION ATOMIC
SERVICE PACKAGE SPECIFICATION COMPOSITE
SERVICE PR DEPENDENCY
SERVICE RESOURCE ASSIGNMENT
SERVICE ROLE
SERVICE SPECIFICATION
SERVICE SPECIFICATION ATOMIC
SERVICE SPECIFICATION CHARACTERISTIC
SERVICE SPECIFICATION CHARACTERISTIC VALUE
SERVICE SPECIFICATION COMPOSITE
SERVICE SPECIFICATION PRODUCT SPECIFICATION RELATIONSHIP
SERVICE SPECIFICATION RESOURCE SPECIFICATION RELATIONSHIP
SERVICE SPECIFICATION ROLE
SERVICE SPECIFICATION VERSION
SERVICE STATUS
SERVICE STATUS CATEGORY
SERVICE STATUS HISTORY
SERVICE STATUS REASON
SIM CARD
SMS SERVICE
UDR EVENT
VOICE MESSAGE SERVICE
VPN SERVICE
WIRELESS SERVICE
Entities of Subject Area: UDR Event
This section lists the entities associated with the subject area UDR Event.
ACCESS METHOD
ACCOUNT
ACCOUNT BALANCE GROUP
ACCOUNT BALANCE IMPACT
ACCOUNT BALANCE TYPE
BILLING STATUS CATEGORY
BILLING STATUS REASON
BILLING STATUS TYPE
BROADBAND USAGE EVENT
CALL DIRECTION
CALL OTHER TYPE
CALL RECYCLED REASON
CALL ROUTING TYPE
CALL SERVICE TYPE
CALL SOURCE DESTINATION
CALL SURCHARGE
CALL TERMINATION REASON
CELL SITE
CONTENT
CONTENT DELIVERY EVENT
CUSTOMER
DATA SERVICE EVENT
DISTANCE BAND
ERRORED MEDIATED CALL EVENT
ERRORED RATED WIRELESS CALL EVENT
ERRORED RAW WIRELESS CALL EVENT
EVENT
EXTERNAL OPERATOR
FIXED LINE CALL EVENT
FRAUD PROFILE CLASS
GL ACCOUNT
GPRS USAGE EVENT
IDD CALL EVENT
INTERNET ACCESS EVENT
INVOICE ITEM
ISP USAGE EVENT
MEDIATED CALL EVENT
MEDIATION STATUS CATEGORY
MEDIATION STATUS REASON
MEDIATION STATUS TYPE
MMS EVENT
ON OFF NET TYPE
PEAK OFFPEAK TIME
PRODUCT
PRODUCT OFFERING
PRODUCT SPECIFICATION
PRODUCT SUBSCRIPTION
PTV FULL CHANNEL ACTIVATION
PTV QPI SERVICE EVENT
PTV USAGE EVENT
RATABLE UNIT MEASUREMENT
RATED UDR EVENT
RAW MMS EVENT
RAW WIRELESS CALL EVENT
RESOURCE
ROAMING TYPE
SERVICE
SERVICE CLASS
SERVICE CLASS TYPE
SMS EVENT
TAP IN WIRELESS ROAMING EVENT
TAP OUT WIRELESS ROAMING EVENT
TV CHANNEL
UDR EVENT
UDR EVENT ASSIGNMENT
UDR EVENT STATUS
UDR EVENT TYPE
UDR EVENT TYPE VERSION
UMS EVENT
UNIT OF MEASURE
VOIP CALL EVENT
VOLUME BAND
WIRELESS CALL EVENT
WIRELESS CONTENT DOWNLOADING EVENT
WIRELESS ROAMING EVENT
WIRELESS ROAMING EVENT BATCH