Slide 1Welcome to the Startup training Session on QCCommon SALEFA Database

Slide 2

Module overview

In this training session we will be covering an overview of the SALEFA DB table schema and its association withSome QOA and QCCommon pages

Slide 3

Some Prerequisites without which you will not be able to understand this session completely.Pl get back to the training sessions page and you will find recorded sessions of the pre-requisites.

Slide 4

Let me brush up some basic concepts which you would have learnt earlier..

Every order created by the user is referred as request .Request Id and Sales Order id, Quote id are same .Every Request/Order/Quote can have more than one product.. which means Request/Order/Quote can have more than one Service instance associated with it..

Slide 5

Some more background information on Ordering concepts..Like service instances are configured in GOI pages and EPC pages..Service instance is referred as prod envelope instance

Slide 6

We have different instances of Salefa for different environments. For Eg. Salefa D is used for Dev integration environment , Salefa E is used for System Testing environment and Salefa I is used for Application integration testing environment.

Slide 7

Here is a snap shot of the GOI Page that is maintained by QOA (quoting and Ordering application). This is the screen displayed when a user creates an Order.The Table that is used to persist data in this page is the QOA_SALES_ORDER_INFOPl notice the mapping between the Fields in the UI and Columns in the Db table.

Slide 8

The GOI page also updates the QOA_PRD_ENVLP_INSTANCE table . Pl notice the mapping between the Fields in the UI and Columns in the Db table.

Slide 9

Every Service Added (Product) will have an entry in QOA_PRD_ENVELOPE table and QOA_PRD_ENVLP_INSTANCE table for each request.Which means QOA_PRD_ENVELOPE_ID and QOA_PRD_ENVLP_INSTANCE_ID has a One to One relationship

Slide 10

This slide highlights the usage of some of the columns in QOA_PRD_ENVELOPE table.CONTEXT_CD as mentioned in the slide, can have different values as the order flows thro. A new row will be created in theQOA_PRD_ENVELOPE with the latest CONTEXT_CD attribute

STATUS_CD :- is used to persist the status of configuration. Its value can be VALID/INVALID

Slide 11

The snapshot shows the EPC page for a Product/Service instance, FRS.Clicking on Add Location in EPC page will open the Add Location Page, this is maintained by QOA.

Slide 12

Service Instance contains Component Groups, Components .One row is created for each Component Group in the QOA_SERVICE_ELEMENT with QOA_SERVC_ELMT_TYPE_CD as "CS"One row is created for each BTLD in the QOA_SERVICE_ELEMENT with QOA_SERVC_ELMT_TYPE_CD as "PS". The name of the Template is Available under TEMPLATE_NM field.These can be retrieved by using the qoa_prd_envlp_instance_id which can be obtained using the qoa_sales_orderidAll the Attributes within the CG/ BTLD can be retrieved QOA_SERVICE_ELEMENT table using the qoa_service_element_idComponents present within the Component Groups (CG) are stored in QOA_PRD_COMPONENT

Slide 13Contacts are stored in the CUSTOMER_CONTACT and CONTACT_XREF tables. These are maintained by QOA team.

Slide 14This Query will help you to retrieve the XML Representation of RQ. QCCommon�s Product build program retrieves the RQ XML from OES and stores it in the OES_PRODUCT_BUILD_XML. The XML representation of RQ (which contains the Product build) can be retrieved using this query

Slide 15

Here is the product config for PLS product. When an Order for with PLS is created and navigated thro EPC .The QOA_PRD_ENVELOPE table and QOA_PRD_ENVLP_INSTANCE will contain one row with indicates that an order for PLS is being created. The CONTEXT_CD indicates in which Mode the order is being created and STATUS_CD indicates the Validation Status.The LI CGs and LL CGs reference are created in the qoa_prd_component_grp table.All the Attributes under this CGs are available in the QOA_SERVICE_ELEMent table and attribute values are available in the qoa_service_element_attribute table.

Slide 16

A Sales order was created for INRS product which had a sales order id =54411Query 1 shows the entries in qoa_prd_envelope table. The results indicate that t

he Order is currently in PROV_MODE. Pl notice the CONTEXT_CD column. This order has gone through OA_MODE, CSO_MODE and is currently in PROV_MODE means being provisioned

Query 2 shows the entries in qoa_prd_envlp_instance table. The results indicate the following there are three versions for this order. Version 1 for OA_MODE, version 2 for CSO_MODE and version 3 for PROV_MODE. QOA_PROD_ENVELOPE_ID and qoa_prd_envlp_instance have a one to one mapping. But the QOA_PROD_ENVELOPE_ID is same when the order is in different modes.

Query 3 indicates the Component Groups(marked as CS) and Provisioning Elements (marked as PS) under the qoa_prd_envlp_instance_id 86442.

Slide 17

Query 4 indicates the service element attributes available under qoa_service_element_id = 213529.

To sum up, QCCommon uses qoa_prd_envelope, qoa_prd_envelope_instance, qoa_prd_component_grp, qoa_prd_component, qoa_service_element, qoa_service_element_attr tables for saving and retrieving the Product Information. Though the information provided in this Training session is very specific to NetworX Common program, it also holds good for SDP Common as well.If you have any doubts/Issues or suggestions, please do get back to QCCommon Development Lead I suggest you to try out the queries mentioned in this presentation to get a better picture of the DB model.Thanks for listening.