Optional Integer DAP Response Parameter Causes the DAP2 Node to Fail when Missing (Doc ID 1929246.1)

Last updated on MAY 02, 2017

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.1 to 5.0.3 [Release 5.0]
Oracle Solaris on SPARC (64-bit)

Symptoms

In Network Charging and Control (NCC), Data Access Pack (DAP) is used to query Application Service Providers (ASPs) and to store any returned information into Profile Tags which can be used to determine logic paths through Control Plans.

The expected response parameters are configured in the DAP Operation template under the "Response" tab and have many different configurable options.  Two of which are:

The "Required" option determines whether the response parameter can be excluded from the overall response from the ASP or whether it's exclusion is treated as an error in the Feature Node (FN).

The "Profile Tag Type" is a drop down list of data types which the response parameter is expected to arrive in.  This option filters the available Profile Fields which can used by DAP to store the response in.

When a response is configured to be optional (ie. Required is unchecked) and of data type INTEGER, then the DAP2 node will exit out the "Parameter Problem" exit if the optional parameter is not in the response.

Changes

New or existing DAP template updated to include an optional integer response parameter.

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