Questions on Opened_t Update of G/L And ITEM_T with 7.4 MPS2 Upgrade (Doc ID 2150713.1)

Last updated on MARCH 19, 2019

Applies to:

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

Purpose

This article is to clarify some detailed questions about upgrade process of 7.4 MPS2.

The user is trying to upgrade from 7.4 PS10 (<Patch 13518161>) to 7.4MPS2 (<Patch 19626042>) and need more information on the update to the G/L stored procedures, data patch update to ITEM_T.OPENED_T and UseActualBilledTimeForGLReport parameter in billing business params.

The questions are based on the patch installation document for 7.4MPS2 which discusses about the following changes:
(1). A new parameter UseActualBilledTimeForGLReport is introduced in billing business params to report previously billed based on actual billing date (OPENED_T).
(2). The data patch fix_items_with_zero_opened_t.source to set OPENED_T on items whose effective_t is greater than or equal to a user-provided cut off date.
(3). Dropping and recreating the index i_item_glseg_eff__id Index that takes an expression to include OPENED_T in the composite index

Questions and Answers

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Questions and Answers

Can you please specify which ones from the 3 steps above are mandatory?

In 7.4PS10, how the G/L procedures determine when an item is billed? EFFECTIVE_T or OPENED_T?

Can we skip both steps (1) and (2) in the upgrade process? If so, will the G/L continue to work correctly after the upgrade in the same way as it does today with PS10?

Assuming (1) and (2) can be skipped, is recreating the index i_item_glseg_eff__id mandatory still? If not, are there any performance impacts expected?

If NONE of these 3 steps are performed, will the new G/L stored procedures under 7.4 MPS2 continue to use EFFECTIVE_T for billed date?

If the above is true, is it correct to say that the G/L procedures under 7.4MPS2 refer the configuration setting for UseActualBilledTimeForGLReport before determining which one to choose i.e., if disabled then EFFECTIVE_T, if enabled then OPENED_T?

Would it be a good idea to consider updating the index i_item_glseg_eff__id even if we choose skip the other two steps? Or do you recommend the approach of doing either all three or none at all?

If all 3 steps can be skipped, the update to index i_item_glseg_eff__id in step (3) will also be skipped. It is a schema change, and it is likely to be carried over to future versions like 7.5 (correct?).
To ask the question in another way, do you see a problem if we skip (1) and (2) but NOT skip step (3)?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.