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.
#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:
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:
where audit_message like '%126.96.36.199%';
Since FIDELITY is a NVOD customer (DWH4) and since ncp_audit_events are not replicated - this is run against APPS WA.