Overview of Oracle Customer Hub

on Monday, May 27, 2013

Oracle Customer Data Hub provides a comprehensive set of  services, utilities and applications to create and maintain a trusted  master customer identity across the enterprise
It consolidates customer data from heterogeneous  systems into a central location and establishing enterprise-wide data quality and integrity at the lowest possible cost. Utilizing  comprehensive integration services, the master customer identity created and maintained within the Hub is shared in real-time with operational and analytical systems so that all channels and lines of business operate in a consistent, well-informed manner, thereby improving customer satisfaction and loyalty.
Customer Hub also known as Siebel Universal Customer Master or Siebel UCM) is Oracle’s lead Customer Data integration (CDI) solution.
The Oracle Customer Hub(OCH) data model is an enhanced version of the Siebel Party model (as used in Siebel CRM).
OCH comprehensive functionality enables an enterprise to manage customer data over the full customer lifecycle.
 
  1. Capturing Customer Data
  2. Standardization
  3. Correction of name and Addresses
  4. Identification and merging of duplicate records
  5. Enrichment if customer profile
  6. Enforcement of compliance and risk policies
  7. Distribution of Single Source of Truth.
 

  1. Trusted Customer Data is held in a central MDM schema
  2. Consolidation services manage the movement of master data into the central store.
  3. Cleansing services deduplicate, standardize and augment the master data.
  4. Governance services control access, retrieval, privacy, audit  and Change management rules.
  5. Sharing services include integration, web services, event propagation and global standards based synchronization.
These pillars utilize generic services from the MDM Foundation layer them with business entity specific services and vertical extensions.
Oracle has provided Web Services Interface to access the customer hub , as well as provide few Pre-build Integration with operation application using AIA(Application Integration Architecture).
 

Fund Transfer Work in R12

on Sunday, May 26, 2013

Fund transfers are supported directly in Oracle Cash management; this feature allows you to create account transfers between internal bank accounts manually or automatically through physical cash pools. 
The related cash flows are stored in Oracle Cash Management for reporting purposes and are reflected in positioning. Payment processing and accounting is managed using Oracle Payments and Oracle Subledger accounting. 
Funds transfer basically can be done in 2 ways  
When you do not require payment document to be generated. 
This is used when the transfer has been made by the bank and you just have to record the same into the system. For this purpose, you can go to the bank account transfer window and select the option "Settle through Oracle payments" as "No". Fill in the rest of the fields and validate the the transfer. This will create a transfer transaction with the status as "Settled".
You can also provide a standing instruction to the bank to make the bank transfer and would be know about the transfer through the bank statement. You can create the bank statement line as a sweep in or sweep out line and record the bank account transfer.
When a payment document is required. 
This is used when for example you draw a check to make the bank transfer or any other payment document. For this purpose, select the option "Settle through Oracle payments" as "Yes". Fill in the rest of the fields and validate the the transfer. 
This will create a transfer transaction with the status as "Settlement in Process". 
After this you need to go to the funds disbursement process manager and issue the payment document. Process similar to the batch payment in AP.
The bank account transfer can also be initiated through cash positioning by using Physical Cash pool.
Please note that this require the intercompany or intracompany rule to be set in the ledger depending on the type of transfer you are making.

Workflow Notifications to Users/Roles

on Sunday, May 19, 2013

Workflow Notifications are sent to the Users/Roles for which setup has been done through Oracle Apps.
Its possible to create Users/Roles using workflow API and all this information is stored in below Oracle
Database tables

FND_USERS
stores the Oracle application user data that is setup through System administrator>User. It links
employee id to the User id, along with email id



WF_USERS/WF_LOCAL_USERS
stores User data along with email id to which Notification is to be sent. When A new user is
defined in oracle apps along with fnd_user table a new record is inserted into this table.

WF_ROLES/WF_LOCAL_ROLES
store roles information

WF_USER_ROLES
Associations of users with the roles

To sent a notification to a particular User following steps need to be performed
1. Add a Notification node to the workflow process
2. Create a attribute of type ROLE in workflow and at the node just before sending the notification
   setup the value of attribute using below api

            wf_engine.SetItemAttrText
                (itemtype        => x_item_type
                ,itemkey        => x_item_key
                ,aname            => 'MAIN_USER'
            ,avalue            => x_user);

Here x_user is user_name/name fetched from fnd_users/wf_users table for that person




3. Open the Notification node in the process and on 'Node' tab select the Performer as the
   Type "Item Attribute" and value as attribute.
  
Whenever the workflow process is initiated and notification is sent, the table WF_NOTIFICATIONS
is populated with RECIPIENT_ROLE as X_USER


Notification to multiple Users
In workflow if you need to send a Notification at once to different Users, you need
to create a role using below API.
-- Create adhoc role
wf_directory.createadhocrole
    (role_name             => x_role_name
    ,role_display_name        => x_role_name
    ,LANGUAGE                       => NULL
    ,territory                      => NULL
    ,role_description               => 'MAIN_ROLE'
    ,notification_preference    => 'MAILHTML'
    ,role_users                    => NULL
    ,email_address                    => NULL
    ,fax                        => NULL
    ,status                => 'ACTIVE'
    ,expiration_date        => SYSDATE+ 60
    ,parent_orig_system         => 'WF_LOCAL_ROLES'
    ,parent_orig_system_id        => 0
    ,owner_tag            => NULL);


Once role is created now add Users to Role using below API. In below API the parameter
role_users is passed with list of USER_NAME separated by space.
--Add Users to Role
wf_directory.AddUsersToAdHocRole
    (role_name     =>x_role_name,
     role_users     =>'Username1 Username2 Username3');

To verify the details please check with below queries

--Check the Role name
select * from wf_roles where name like x_role_name;

--Check the User associated with the Role
select * from wf_user_roles where role_name like x_role_name;