Create Simple Products

The following steps covers Simple product creation:

Creating a Product Record 
You enter products into the Siebel system by creating product records. The product record contains the product name and important information about the product, such as its product line name or part number.
Once a product record is created, it cannot be deleted. To prevent a product record from being displayed in pick lists and dialog boxes, edit the product record to deselect the Orderable, Sales Product, and Service Product check boxes. You can also control display of the product by setting Effective Start and Effective End dates.
You add a new product record by clicking the new button. This creates the new product without releasing it, and locks the workspace.
 To create a product record 

• Navigate to the Administration – Product screen, then the Products view.
• In the Products list, add a new record and complete the necessary fields.

 Associating a Product with Price Lists

 Products are not visible to customers unless they are associated with price lists that are assigned to the customers.
To associate a product with a price list

• Navigate to the Administration – Product screen, then the Products view.
• In the Products list, select the desired product.
• Click the Pricing view tab.
• In the Price Lists list, add a new record and select the desired price list.
• Complete the remaining fields as needed.  

Setting Up User Access To a Product 

You must set up user access to allow the user to select a product for a quote or to see the product in a catalog.
The catalog administrator creates product catalogs, which contain product categories. The catalog administrator sets up access controls by assigning access groups to the catalog and to the categories.
The product administrator assigns products to catalogs and categories. You can assign a product to more than one category, and thus more than one catalog.
Until you assign a product to at least one category, the product does not display in the following places:

• On eSales Web pages. When customers buy your products through the Web, they cannot see the product.
• While browsing catalogs. When salespeople click the Browse Catalog button to view products in catalogs, they cannot see the product.

NOTE:  For products with components, you must give users access to the product with components and all its components. To accomplish this, first assign the product with components and its components to the same product category or to categories that have the same access groups. Then assign users who will configure the product to these access groups. If the users in the access groups differ across components, these users will not be able to configure the product with components correctly.
The recommended method for assigning users to access groups is to assign the users to organizations and then assign the organizations to the access groups.
To set up user access

• Navigate to the Administration – Product screen, then the Products view.
• In the Products list, select the desired product.
• Click the Category view tab.
• Add a new record to the Category list.

A dialog box appears that lists all the currently defined categories.

• Select a category from the dialog box.
• Add all the categories needed to give users visibility to this product.  

Releasing a Simple Product 

Though simple products do not have a Versions list, they are versioned objects. A new version was created when you created the product, and you must release this version to make the product visible to users.
To release a simple product

• Navigate to the Administration – Product screen, then the Products view.
• In the Products list, select the simple product.
• Click Release.

Create VBC Steps

1. Create a new BC based on the Class CSSBCVExtern.
2. Do not associate any tables to this BC since VBC are not based on an underlying table but rather is based on a Business Service.
3. Create the fields associated with VBC.
4. The field names must exactly match the name of the columns of the table that this VBC will reference.
5. Do not specify column or type for the fields.
6. Under the Business Component / Business Component User Property, create a new entry:
  a. Name: Service Name
  b. Value: AAA Test Business Service
  c. The Value can be any name that will use to create your new Business Service.
  d. "Name" must be "Service "Name".
7. Create a new Business Service with the same name that you used in the Business Component User Property above.
8. Create the various methods for your Business Service.
Some examples are:
  a. Delete, Init, Insert, Preinsert, Query, Update
  b. The minimum that you should have is Init and Query.
  c. Sample codes are given below.
9. Now define the Business Service Method Arg that goes with each of the Methods.
10. Associate your new VBC to a Business Object.
11. Create a new applet based on your VBC.
12. The example here is a list applet.
13. Add the VBC columns to the list applet.
14. Create a new view based on your new applet that is based on your VBC.
15. Associate the new View to a screen.
16. Don't forget to add the view to Application / Views in the application.
17. Also, add the view to an appropriate responsibility.

Siebel Implementation Process

Siebel Implementation Process example.  Please suggest any modifications if any.

1. Stage SPA00 - Plan and Activate
2. Stage SRP00 - Release Planning
3. Stage SRQ00 - Requirements Definition
4. Stage SFA00 - Functional Analysis & Design
5. Stage STA00 - Technical Analysis & Design
6. Stage SCF00 - Configuration
7. Stage SDM00 - Data Migration
8. Stage STS00 - Testing
9. Stage SDP00 - Deployment
10. Stage SUT00 - User Training
11. Stage SCE00 - Control and End

Stage SRQ00 - Requirements Definition

Step
Tasks
Output

Step 0100 - Acquaint Project Team with Business


Task 010 - Prepare Siebel Application Demo
Task 020 - Demo Siebel to Business Community
Siebel Business Requirements Document
Step 0200 -
Conduct Siebel
Awareness Sessions



Step 0300 -
Identify Siebel Business
and Reporting Requirements

Task 010 - Capture Business Requirements
Task 020 - Capture Reporting Requirements
Siebel Business Requirements Document
Step 0400 -
Define Organizational
Structures & Positions /Responsibilities


Step 0500 - Prioritize and Establish Baseline Requirements





Stage SFA00 - Functional Analysis & Design

Step
Tasks
Output

Step 0100 -
Create Business Object
Model
Task M00 - Milestone SFA M00 –
Functional Analysis & Design Started
Task 010 - Define Business Processes
Task 020 - Map Business Processes to Business Objects
Task 030 - Create Business Object Model
Task 040 - Validate Business Object Model
Task M01 - Milestone SFA M01-Business Object Model Complete
Siebel Business Object Model
Step 0200 -
Develop High Level
Screen Design
Task 010 - Define Business Transactions
Task 020 - Identify Screens
Task 030 - Map Business Transactions to Screens
Task 040 - Create Transaction Groups
High Level Screen Design
Step 0300 -
Identify Required Views,
Applets and Reports
Task 010 - Identify Views
Task 020 - Identify Applets
Task 030 - Identify Reports
Task 040 - Consolidate Gap Analyses
Task 050 - Create Views/Applets/Reports Reusability
Matrix
Task 060 - Define Navigation Between Views
Task 070 - Assign Siebel Visibility Classes
High Level Screen Design
Siebel Screen Visibility Checklist
Siebel Screen Design Checklist
Siebel Screen Data Elements
Views/Applets/Reports Cross Reference Matrix
Step 0400 -
Create Business
Component Model
Task 010 - Extract Business Components from Views and Applets
Task 020 - Extract Business Components from Business Objects
Siebel Business Component Model
Step 0500 -
Refine Business
Component Model
Task 010 - Map Conceptual Business Components to Standard Siebel Business Components
Task 020 - Specify Changes to Standard Siebel Business Components
Task 030 - Map Data Elements to Business Components
Siebel Business Component Model
Step 0600 -
Design Views,
Applets and
Reports
Task 010 - Design Screen Layouts (Applets and Views)
Task 020 - Design Report Layouts
Siebel Screen Visibility Checklist
Siebel Screen Design Checklist
Siebel Screen Data Elements
Applet Design Specification
Report Design Specification
Step 0700 - Create and Review Functional Specification
Task 010 - Document Changes to Tables, Business Components, UI
Task 020 - Document Functional Specification
Task 030 - Conduct Functional Design Review (Internal)
Task M02 - Milestone SFA M02 -Functional Analysis & Design Finished
Functional Specification



Technical Analysis & Design

Step
Tasks
Output

Step 0100 -
Define Technical Architecture



Step 0200 -
Perform Capacity
Planning
Task 010 - Assess Network Bandwidth Requirements
Task 020 - Determine Database
Sizing and Tuning Requirements
Capacity Planning Documentation
Step 0300 -
Conduct Siebel Technical
Reviews
Task 010 - Conduct CapacityPlanning Review
Task 020 - Conduct InfrastructureStrategy Review
Task 030 - Conduct Data MappingReview
Siebel Review Results
Step 0400 -
Document Design
Specification and Procure
Components
Task 010 - Document DesignSpecification
Task 020 - Initiate Procurement
Task M01 - Milestone STA M01 -
Technical Analysis & Design Finished
Design Specification



Stage SCF00 - Configuration

Step
Tasks
Output

Step 0100 -
Set Up Development Environment

Task M00 - Milestone SCFM00 -Configuration Started
Task 010 - Set up Network Connectivity
Task 020 - Set Up Siebel File System
Task 030 - Install Siebel GatewayServer
Task 040 - Install Siebel Servers and Enterprise Server
Task 050 - Install Siebel Database Server
Task 060 - Install Web Server
Task 070 - Install Third Party Software
Task 080 - Install Siebel Client
Task 090 - Install Siebel Tools
Task 100 - Set Up Configurators
Task 110 - Create Database Extract for Configurators
Task 120 - Initialize Local Database
Environment Setup
Step 0200 -
Initiate Configuration
Task 010 - Assign Functional Areas to Configurators
Task 020 - Analyze and Refine Projects
Configuration Guidelines
Step 0300 - Implement Database Extensions
Task 010 - Implement Extensions
Task 020 - Test Extensions
Task 030 - Apply Changes to Master Database
Task 040 - Create Local Database Extract
Task 050 - Reinitialize Local Databases
Physical Database Schema
Step 0400 - Set Up Static Data
Task 010 - Set Up Positions and Responsibilities
Task 020 - Set Up LOV's
List of Values
User Settings
Step 0500 - Customize Siebel Business Objects
Task 010 - Create/Modify Business Objects and Components
Task 020 - Validate Siebel Configuration
Siebel Local Database
Step 0600 - Customize Siebel Presentation Objects
Task 010 - Configure Presentation Objects
Task 020 - Unit Test Configuration Objects
Siebel Local Database
Step 0700 - Create Siebel VisualBasic Scripts
Task 010 - Create Siebel Visual Basic Scripts
Task 020 - Unit Test Siebel VB Scripts
Siebel Local database
Siebel Repository File
Step 0800 - Conduct Quality Review
Task 010 - Conduct Quality Review and Fix Problems
Task 010 - Conduct Configuration Review (Siebel)
Configured Application
Step 900 - Evaluate Release
Modification Requests
Task 010 - Capture User Feedback
Task 020 - Prepare Estimates for Changes
Task 030 - Review and Prioritize Changes
Task M01 - Milestone SCF M01-Release is Complete

Project Management Plan
Step 1000 - Prepare for Deployment
Task 010 - Develop Operations Manual
Task 020 - Prepare Rollout Plan
Task 030 - Conduct Production Readiness Review
Task M02 - Milestone SCF M02 –
Release is Production-Ready
Approved Deployment Package



Data Migration

Step
Tasks
Output

Step 0100 –
Determine Data Migration Strategy

Task M00 - Milestone SDM M00 -
Data Migration Started
Task 010 - Inventory Data Sources
Task 020 - Acquire External Data
Task 030 - Assess Data Integrity
Task 040 - Determine Automated vs.Manual Migration Approach
Task 050 - Determine TransitionApproach
Task 060 - Determine Migration
Backup and Recovery Strategy
Task 070 - Develop Migration Tests
Task 080 - Finalize Data Migration Plan
Data Migration Plan
Step 0200 –
Design Migration Process
Task 010 - Design Data MigrationRoutines
Task 020 - Verify Siebel InterfaceData Mapping
Task 030 - Design Manual Processes
Siebel Data Migration Script Manual Entry Procedures
Step 0300 –
Construct Migration Process

Task 010 - Build Data ExtractionRoutines
Task 020 - Write Data Load Scripts
Task 030 - Create Batch Processes
Data Extraction Routines
Data Load Scripts
Batch Processes
Step 0400 –
Test Migration Routines
Task 010 - Unit Test MigrationRoutines
Task 020 - IntegrateTest FullMigration Process
Tested Data Migration Process
Step 0500 –
Perform and Verify Data Load
Task 010 - Execute Data ExtractionRoutines
Task 020 - Execute Data LoadRoutines
Task 030 - Verify Data Load
Task 040 - Reconcile Automatic DataMigration Routines
Task 050 - Conduct Manual DataConversion
Task M01 - Milestone SDM M01 -Data Migration Finished
Data Load



Testing

Step
Tasks
Output

Step 0100 -
Set up Testing Environment
Task M00 - Milestone STS M00 -Testing Started
Task 010 - Set up Network Connectivity
Task 020 - Set Up Siebel File System
Task 030 - Install Siebel Gateway Server
Task 040 - Install Siebel Servers and
Enterprise Server
Task 050 - Install Siebel Database Server
Task 060 - Install Web Server
Task 070 - Install Third Party Software
Task 080 - Install Siebel Client
Task 090 - Set up Dialup Connectivity
Task 100 - Set up Internet Access

Step 0200 -
Prepare Testing Server
Task 010 - Build Testing Database
Task 020 - Confirm Data Migration
Task 030 - Set Up Users
Task 040 - Create Predefined Queries
Task 050 - Verify Positions and
Responsibilities
Task 060 - Verify LOV's
Task 070 - Define and Test Translations
Task 080 - Set Up Correspondence Templates
Task 090 - Establish Call Center Administration
Task 100 - Set Up Siebel Marketing
Encyclopedia
Task 110 - Create Database Extract for Remote Users

Step 0300 -
Develop Test Plans
Task 010 - Create User Acceptance
Test Plan & Cases
Task 020 - Create System Test Plan
Task 030 - Select and Procure Automated Testing Tool

Step 0400 -
Conduct Testing
Task 010 - Conduct User Acceptance Testing
Task 020 - Conduct System Performance Testing
Task M01 - Milestone STS M01-Testing Finished




Deployment

Step
Tasks
Output

Step 0100 -
Set Up Production Environment

Task M00 - Milestone SDP M00 -
Deployment Started
Task 010 - Set up NetworkConnectivity
Task 020 - Set Up Siebel File System
Task 030 - Install Siebel GatewayServer
Task 040 - Install Siebel Servers and Enterprise Server
Task 050 - Install Siebel DatabaseServer
Task 060 - Install Web Server
Task 070 - Install Third PartySoftware
Task 080 - Install Siebel Client
Task 090 - Set up Dialup Connectivity
Task 100 - Set up Internet Access
Environment Setup
Step 0200 -
Prepare Production Server

Task 010 - Build Database
Task 020 - Confirm Data Migration
Task 030 - Set Up Users
Task 040 - Create Predefined Queries
Task 050 - Verify Positions and Responsibilities
Task 060 - Verify LOV's
Task 070 - Define and TestTranslations
Task 080 - Set Up CorrespondenceTemplates
Task 090 - Establish Call Center Administration
Task 100 - Set Up Siebel Marketing
Encyclopedia
Task 110 - Create Database Extractfor Remote Users
Local Database Extract
Physical Database Schema
List of Values
User Settings
Queries
Translations
Correspondence Templates
Call Center Parameters
Populated Marketing Encyclopedia
Step 0300 -
Roll Out Release

Task 010 - Establish/Test ProductionSupport Infrastructure
Task 020 - Implement BackupProcedures
Task 030 - Deploy Application
Task 040 - Verify Connectivity toDatabase
Task M01 - Milestone SDP M01-Release Accepted
Deployed Release
Step 0400 -
Prepare for Next Release
Task 010 - Review Results of ReleaseRollout
Task 020 - Refine Release Strategy
Task M02 - Milestone SDP M02 -Next Release Go-Ahead
Project Management Plan

Debugging EDQ-CDS / Siebel Matching Issues

The attached document provided by Oracle itself and sharing the same for knowledge purpose only.


Link

Siebel Sales Application

Introduction:Sales Cycle plays a critical role in Customer Relationship Management (CRM). It is critical in a way because it is the initial point of contact for any customer. For any CRM application it is important to understand the Sales Cycle. The Sales Cycle starts from Prospecting and ends when a deal is closed and the revenue is realized.
There are various steps involved in an end-to-end Sales Cycle.
Prospecting --> Lead --> Opportunity --> Quote --> Order --> Closure
1) Prospecting: It involves creating the target database.
2) Lead Generation: A lead is an expressed interest shown by the prospects. It is used by a sales agent to determine whether there is a potential for some sales opportunity.
3) Opportunity Creation: Once a lead is qualified, an opportunity is created.
4) Quote Generation: Sales agent prepare quotes to communicate prices, discounts and special offers that are associated with a product/service which is part of a sale.
5) Order Creation: Once the quote is accepted it is converted into an order.
6) Closure: The deal is closed once the order is created.
The Sales Cycle may differ to some extent depending upon the type of business. But a typical sales cycle would follow the above mentioned steps.
Mapping the Sales Cycle with SIEBEL Sales Application
Following are the important business entities involved in Siebel Sales Application:
1) Accounts
2) Contacts
3) Opportunities
4) Quotes
The lead that is generated through various sources is captured in Accounts screen. It captures the details like - Account Name, Address, Status of the Account (i.e. whether the Account is active/inactive, Qualified, contract pending etc), Account Type (i.e. whether the Account holder is an existing customer, Business, Competitor or Vendor etc.) within the Account Screen.
The Accounts Screen is then linked to Opportunities, Contacts and Quotes.
The Opportunities Screen will have the details such as opportunity name, account name to which it is associated, revenue that could be generated from the opportunity, sales stage (prospecting, qualification, closing, lost), name of sales team, lead quality(excellent, very high, high, fair, poor) etc. The Contacts Screen will have details such as name of the person, phone number, job title, name of the account, address etc. The Quotes Screen will have details related to the quotes that have been generated for a particular order. The quotes may undergo some iteration if there is any negotiation between the two parties. A Quote Screen will typically have the Quote name & number, Revision, date of creation, name of the account to which it is associated, name of sales rep, Status (whether the quote is approved, accepted, in-progress, active etc.)
Advantages of Siebel Sales Application
Following are the advantages of Siebel Sales Application:
1) Siebel Sales simplifies and optimizes the task of planning and managing the sales process by providing complete visibility into the sales cycle, helping companies to plan and manage effective selling activities.
2) By bringing business activity information closer to the user, displayed in one place, sales people can find what they need to work on and then quickly navigate to that object within the application.
3) Each organization may use slightly or sometimes greatly different terminology. Often applications will use industry standard terminology that is not necessarily applicable to a particular organization. Customization allows each customer to use their own chosen terminology. This way it cuts down on time that is required to train users on what each field is for and thus allowing for a more seamless transition to a new application.

Oracle Enterprise Data Quality (OEDQ) - Auto Monitor CDS Jobs

Hi,

I came across one requirement to auto monitor EDQ jobs without manual intervention.


Requirement:
    We need to send auto alert message whenever EDQ Jobs are down or not running.

Solution:

I have implemented solution as follows:

Created Java program which will need to monitor Jobs and send alert message as accordingly.

File attached:

JMX Code Sample

    The attached files contains following files:

1.       JMX_Status.sh is unix file which calls the Java program. It passes the required parameters while calling java program.
2.       SystemConfigClient.class is compiled java program which needs to be placed in EDQ server.
3.       JMX_JAVA_CLASS.txt is java code.
4.       EDQ_Param.txt is parameter file.
 
 
         

Oracle Sales Cloud - GROOVY SCRIPT - Currency format

IMPLEMENTATION OF NUMBERFORMAT GROOVY SCRIPT:

Initially a temporary variable gets the value of the field that needs to be formatted. Assuming the current value is in the string format, the length of the value is calculated based on the decimal.

def tempValue = c_Value //e.g. $USD 9967644.09

def currentIndex = tempValue.indexOf('.')

def currencyValue

if(currentIndex<0)

currencyValue = tempValue

else

{

currencyValue =tempValue.substring(0,currentIndex)

}

def currencyLength = currencyValue.length()

After 3 digit formatting, the obtained values are added into a list.

def temp=0

def emptyList = []

if(currencyLength%3 !=0)

temp = currencyLength%3

if(temp!=0 && temp<=currencyLength ){

emptyList.add(currencyValue.substring(0,temp))

}

else

{

emptyList.add(currencyValue.substring(0,temp+3))

temp=temp+3

}

while(temp<currencyLength)

{

emptyList.add(currencyValue.substring(temp,temp+3))

temp=temp+3

}

• Finally all the values in the list are concatenated as comma separated string and returned as desired US currency format.

String finalCurrency = ""

int i

for(i=0;i<emptyList.size();i++)

{

finalCurrency+=emptyList[i]+','

}

return "\$"+finalCurrency.substring(0,finalCurrency.length()-1) //e.g. $9,967,644

The above code is defined as a global function formatCurrency which could be referred in the text formula field as below,

def currencyValue = OptyRevenue_c

def tempValue = currencyValue.toString()

def finalCurrency=adf.util.formatCurrency(tempValue)//has the formatted value

Oracle Sales Cloud - Creating Appointment - Sample Code

scenario:

when an Opportunity is modified e.g Field “Next Contact Date”  An appointment is created to schedule a meetings:

if (isAttributeChanged(‘NextContactDate_c’))

{
//define variables
def voAppointment = newView(‘AppointmentVO’)
def createAppt = voAppointment.createRow()
def currentDateTime = now()
def apptName = ‘TestGroovyScript’ + currentDateTime
//set the required values to a variable
createAppt.setAttribute(‘ActivityName’, apptName)
createAppt.setAttribute(‘SourceObjectId’,OptyId )
createAppt.setAttribute(‘SourceObjectCd’,’OPPORTUNITY’)
//insert a record in Appointment
voAppointment.insertRow(createAppt)
}

Oracle Sales Cloud - Enable Notifications

The following steps are required to enable notifications in Oracle Sales Cloud R10:

Enable Administrator Profile Values:

All Tasks > Manage Administrator Profile Values 

ZMM_ACTIVITY_DISABLE_EMAIL_APPT_NOTIF = No 
ZMM_ACTIVITY_DISABLE_EMAIL_TASK_NOTIF = No 
ZMM_ACTIVITY_TASK_NOTIF_EMAIL= Yes 
ZMM_ACTIVITY_APPT_NOTIF_EMAIL = Yes 

ZMM_ACTIVITY_EXTERNAL_NOTIFICATION = Yes

Please follow the steps bellow to enable the notification reminders for a user: 

-In the UI click the user name (aka first user) in the right top corner 
-Click Set Preferences... 
-Click Calendar and Appointment Preferences 
-On the Task section 'Notify me if changes are made by others' select the desired options (for example enable 'When I am the owner') 
-On the Task section 'Notify me by' select the the option 'Notification list' 
-Save and logout 
-Login in with another user 
-Create activity and set the owner to the first user 
-Logout and login with the first user 
-Verify that you will have a notification 

UCM Survivorship Rules On Custom Extension Columns(X_) of Base Tables

Here is the process to do:

1. Add a new column(X_TEST) to the table S_CONTACT(or any base table).
2. Added the field in the respective BC and IO.
3. Compile objects in to srf.
4. Now restart the siebel server and log in to application.
5. UCM>SurvivorshipRules>Attributegroup>
For the field name picklist without any join "Test"(extension field) will be visible.
6. Now create a Survivorship rule as per your business requirement.
Eg: Attribute group contains: First Name, Last Name and Test
Contact Default: Recent
and in the Attribute group Comparison Rule:History

7. Now using "Person Service" webservice create person operation, insert a record with the following details:

soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cus="http://xmlns.oracle.com/apps/mdm/customer" xmlns:swip="http://www.siebel.com/xml/SwiPersonIO">
<soapenv:Header/>
<soapenv:Body>
<cus:createPerson_Input>
<cus:RealtimePubSub>False</cus:RealtimePubSub>
<cus:_sblesc_lstValue_grt></cus:_sblesc_lstValue_grt>
<swip:ListOfSwiPersonIO ExternalSystemId="ExtSys1">
<swip:Contact operation="Insert" searchspec="" status="">
<swip:Id>1-123</swip:Id> 
<swip:FirstName>X_Recent</swip:FirstName>
<swip:LastName>1stTime</swip:LastName>
<swip:Test>ExtensionColumn</swip:Test>
<swip:EmailAddress>abc@abc.com</swip:EmailAddress> 
</swip:Contact>
</swip:ListOfSwiPersonIO>
<cus:Error_spcCode>?</cus:Error_spcCode>
<cus:Error_spcMessage>?</cus:Error_spcMessage>
</cus:createPerson_Input>
</soapenv:Body>
</soapenv:Envelope>


8. Now modified the message and inserted as below:

soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cus="http://xmlns.oracle.com/apps/mdm/customer" xmlns:swip="http://www.siebel.com/xml/SwiPersonIO">
<soapenv:Header/>
<soapenv:Body>
<cus:createPerson_Input>
<cus:RealtimePubSub>False</cus:RealtimePubSub>
<cus:_sblesc_lstValue_grt></cus:_sblesc_lstValue_grt>
<swip:ListOfSwiPersonIO ExternalSystemId="ExtSys1">
<swip:Contact operation="Insert" searchspec="" status="">
<swip:Id>1-123</swip:Id> 
<swip:FirstName>X1_Recent123</swip:FirstName>
<swip:LastName>1stTime</swip:LastName>
<swip:Test>ExtensionColumn123</swip:Test>
<swip:EmailAddress>abc@def.com</swip:EmailAddress> 
</swip:Contact>
</swip:ListOfSwiPersonIO>
<cus:Error_spcCode>?</cus:Error_spcCode>
<cus:Error_spcMessage>?</cus:Error_spcMessage>
</cus:createPerson_Input>
</soapenv:Body>
</soapenv:Envelope>

9. As per survivorship rules even though first name and extension column are modified they are not disturbed in the base table whereas Email Address is changed to the recent one since email address is not present in the attribute group.

10. Hence it is confirmed that survivorship rules will execute on extension columns as well. 

                                                                                                                                               (Its is only for education /knowledge purpose)

EDQ Sequence Generator Processors

As per the requirement, I need to generate the Sequence in EDQ.

The following is the processor, which will generate the sequence.  

"Add Message Id "

OCH (Siebel UCM) - OEDQ Real-Time Matching Process

- In real time, when a new record(driving record) come to UCM, Siebel calls EDQ web services to      generate cluster keys for the new record
- EDQ generate the cluster keys and its send back to Siebel
- Siebel stores these new keys and then looks up all records that share any key with the driving record- Once Siebel find a matching key, it submits driving and candidate records to the matching service
- Driver record and all candidate records are send back to EDQ, to be ranked by Match score
- Siebel then pop-up the Matching record with the match score and user can select 'pick' or 'ignore' to commit the record.
Cluster keys are stored in S_DQ_xxx_KEY tables; 


Accounts: S_DQ_ORG_KEY
Contact:    S_DQ_CON_KEY 

Prospects:  S_DQ_PRSP_KEY

Monitor-OEDQ-Webservice-with-Siebel

Monitor Oracle Enterprise Data Quality (OEDQ) web service when connected with Siebel instance. 

The post will explain, how to visualize the data running through EDQ process:

Here we have two options:

1. Based on process:

 a). Temporary: cancel real-time process from the Director application user     
      interface and select the match processor, the rules hit, data in and data out etc.,related output tabs can view on results browser.

 b). Permanent: we can used writer processor to write output of match processor.


2. EDQ Web service Tester:

   Launchpad -> web Service Tester, by using this we can easily identify the whether the web service is            working as expected or not (for more details please refer the Oracle documentation).