Understanding Partitioning Values In BRM Data Dictionary (Doc ID 1618668.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Goal

Qn1:On BRM 7.5 PS6, upgrade path: 7.2.1 -> 7.3 -> 7.4 -> 7.5 -> 7.5 PS6

During upgrading from Portal 7.2.1 to BRM 7.5 PS6, have discovered some variations in the contents of dd_objects_t and dd_objects_fields_t that need to be explained to complete the upgrade safely.


1. Column "partition_mode" in dd_objects_t

a. What are the possible values for PARTITION_MODE in dd_objects and the implication of each value? From the user's understanding the partition_mode can be 0(Historic) , 1 (Finite) and -1 (??).

b. What is the relationship of the field PARTITION_MODE with IS_PARTITIONED? Is the value of PARTITION_MODE relevant if the value of IS_PARTITIONED is 0?

The above will help to understand the differences between 7.2 and 7.5 for the objects mentioned below:
partition_mode value in 7.2 = -1
partition_mode value in 7.5 = 1

/event/audit/collections
/event/audit/collections/action
/event/billing/finance_charge
/event/notification
and others.

Under 7.5, the following query result is shown:


thus, the question is what "1 -1" means.   Are they treated as by dm_oracle, finite or historic?



2. Column "permission" in dd_objects_fields_t

Please confirm if the changes in the values permission for the fields listed below are correct and are required for 7.5:

 

ObjectsField NameValue in 7.2Value in 7.5
/au_config/rtp/trim_flist PIN_FLD_EVENT_TYPE
2 1
/au_config/spec_impact_category PIN_FLD_TYPE_STR 2 1
/au_discount PIN_FLD_DISCOUNT_MODEL 1 2
/au_profile PIN_FLD_ACCOUNT_OBJ 1 2
/config/rtp/trim_flist
PIN_FLD_EVENT_TYPE 2 1
/config/spec_impact_category
PIN_FLD_TYPE_STR 2 1
/discount  PIN_FLD_DISCOUNT_MODEL 1 2
/event
PIN_FLD_SESSION_OBJ 66 2
 /event/billing/cycle/tax   PIN_FLD_TAX_CODE  65  1
 /event/billing/product   PIN_FLD_NODE_LOCATION  1  2
 /event/billing/product/fee/cycle   PIN_FLD_NODE_LOCATION  1  2
 /journal   PIN_FLD_GL_ID  1  65
 /profile   PIN_FLD_ACCOUNT_OBJ  65  1

 

 

 

 




               1








 
 
 

 

 

 

 

 

 

Qn2:

1. Can you confirm: NODE_LOCATION went from 1 (req/writable) to 2 (opt/writable) consistent with NODE_LOCATION no longer being generated for newly purchased products.

2. Can you confirm: GL_ID went from 1 (req/writable) to 65 (req/nowrite) consistent with the idea that journal objects should not be moved form one G/L ID to another. In other words, this looks like a fixup to ensure data integrity.

 
Qn3:What happens with the following PODL when deployed under 7.2.1:

STORABLE CLASS /event/custom/cc_history {

  READ_ACCESS = "Self";
  WRITE_ACCESS = "Self";
  IS_PARTITIONED = "1";
}

Would that results in IS_PARTITIONED = 1 and PARTITION_MODE = -1?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms