Fct_event Order Xml File Generation (Doc ID 886116.1)

Last updated on SEPTEMBER 30, 2009

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.0.0.0
This problem can occur on any platform.

Symptoms

-- Problem Statement:
We are using FCT_EventOrder Module in the Rating pipeline as shown below:
#--------------------------------------------------
# Event Order
#--------------------------------------------------
EventOrder
{
ModuleName = FCT_EventOrder
Module
{
Active = True
AccountDataModule = ifw.DataPool.CustomerData
PortalConfigDataModule = ifw.DataPool.PortalConfigDataModule
RerateDelayTolerance = 180
NumberOfAccountLimit = 1000
OutputDirectory = home/brpdev43/vpu/custom/ifw/ifw_batch_rating_db1_bre/data/ood
OutputPrefix = ood_
}
}

As per  BRM documentation (search for FCT_EventOrder --> About rerating events --> How Portal rerates out-of-order events)

Rerate-request file names use the following format:

outputPrefix_pipelineName_transactionID_sequenceNumber.xml
where:

outputPrefix is the prefix specified by the OutputPrefix entry in the FCT_EventOrder module
registry. The default is ood.

pipelineName is the name of the pipeline; in the following example, the name is ALL_RATE.

transactionID is the transaction ID.

sequenceNumber is the sequence number of the job.

For example:
ood_ALL_RATE_14_0.xml

But when we processed the CDR, the name of file created in ood directory do not follow the naming convention defined in the above documentation:

outputPrefix_pipelineName_transactionID_sequenceNumber.xml


The file is generated like:
outputPrefix_pipelineName_<CDR_NAME>_transactionID_sequenceNumber.xml

Since, we have implemented Pipeline Instances in registry using
Instances
{
ALL_RATE
{
NumberOfInstances = 2
InstanceSpecificRegistries
{


}
}
}

When we process a CDR file with Instance0 it generates the file:
ood_ALL_RATE0_00000115_1079_0.xml

When we process a CDR file with Instance1 it generates the file:
ood_ALL_RATE1_SORT1_RATE1_00000115.CDR1_1080_0.xml

So, the behavior is not the same for each instance, it should be the same behavior in all instances.

Cause

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