CONFIGURATION SERVICES ISSUES (CS OR BCS) ON APPS DB PRODUCTS SCHEMA

Wednesday, May 10, 2017

?Configuration Services are configurations that the customer can use modify to change the call behavior. For example, they can modify the call flow to play special prompts like "Back to School Special ...".

NOC and Production Managers don't really have a good understanding of the database layout.

For example, they will ask you to check the FIDELTIY configuration database. Fidelity is just a domain within the shared set of the Configuration Services (CS) set of tables.

Here is the list of CS tables under the PRODUCTS schema in all APPS DBs. The tables are 3-way Advance Replicated to TX, MA and WA.

CA is a read-only copy.

BODCS_APP

BODCS_APP_LOCALE

BODCS_APP_VERSION

BODCS_CONFIG_POINT_DEF

BODCS_CONFIG_POINT_ITEM

BODCS_CONFIG_POINT_ITEM_FILE

BODCS_CONFIG_POINT_ITEM_PARAM

BODCS_CONFIG_POINT_TYPE

BODCS_CONFIG_SET

BODCS_CONFIG_SET_ITEM

BODCS_CONFIG_SET_VERSION

BODCS_ENVIRONMENT

BODCS_FILE

BODCS_FILE_CONTENT

BODCS_LOCALE

BODCS_NOTIFICATION

BODCS_PROVIDER

BODCS_ROLE

DNM_ATTRIBUTE

DNM_ATTRIBUTE_INFO

DNM_CONFIG

DNM_DID

DNM_GROUP

#1 Sometimes you are asked what changes were made for a particular customers configurations:

select * from s4_synch.ncp_audit_events where upper(AUDIT_MESSAGE) like '%FID%';

To find FIDELITY audit of CS changes

To see the audits for NCP NVOD customers are in WA (DWH4 is their DWH)

The Tango customers would be in MA (DWH3 is there DWH)

#2 Sometimes you need to check for inconsistencies in the replication:

[oracle@npmadb001][APPS]$ pwd

/export/home/oracle/common/bcs_replication_check

[oracle@npmadb001][APPS]$ check_all_bcs_synch_general_mis.sh

==========================================================

Checking Table: PRODUCTS.BODCS_APP

==========================================================

Spooling to output/bsc_synch_general_mis_BODCS_APP.log

no rows selected

no rows selected

no rows selected

.

.

#3 Sometimes you need to look at the details of a particular Configuration set.

Note: all querries are run against APPS MA - but the these table are replicated: "Configuration Sets" have Version Numbers. Here is one for FIDELITY we were asked to research:

column LAST_MODIFIED_AUTHOR format a20

select     version_id, 

    creation_date_gmt, 

    last_modified_author, 

    app_version_id

from     products.bodcs_app_version 

where     version_id = '1.0.0.21';

VERSION_ID           CREATION_ LAST_MODIFIED_AUTHOR APP_VERSION_ID

-------------------- --------- -------------------- --------------

1.0.0.21             08-MAY-17 Mary_Thrasher                 81003

The key to mapping the configuration sets to the other tables is.

PRODUCTS.BODCS_APP_VERSION which contains the field VERSION_ID.Then columns APP_VERSION_ID and APP_ID can be used to join with other tables.

select     d.description, 

    v.config_point_value 

from     bodcs_config_point_item_param v, 

    bodcs_config_point_def d

where     v.config_point_def_id = d.config_point_def_id

and     v.app_version_id = '81003';

One example:

DESCRIPTION

--------------------------------------------------------------------------------

CONFIG_POINT_VALUE

--------------------------------------------------------------------------------

To force all callers down the B path, set the value to disabled To force all callers down the A path, set the value to 00-99"00-99 You can also see the history of what was done with this Configure Set version buy querring the NCP Audit table:

select     * 

from     s4_synch.ncp_audit_events 

where audit_message like '%1.0.0.21%';

Since FIDELITY is a NVOD customer (DWH4) and since ncp_audit_events are not replicated - this is run against APPS WA.