Siebel Business Process & Functionality (MOSC)

MOSC Banner

Siebel Loyalty - Separate Instance

edited Aug 27, 2015 11:39PM in Siebel Business Process & Functionality (MOSC) 7 commentsAnswered

Hi All,

To give a Background we are Using Siebel 8.1.1.11 Version.

As part of we are using Siebel Sales& Order Management Module , Service and Loyalty Module.

As part of Loyalty we are getting Millions of transaction for Accrual for Different LOY Programs,Causing the DB Size to grow hugely and also Causing OM,other,etc transaction to Slow when Batch Engine Component Processes the Data.

So we are Decoupling the Loyalty into Separate Siebel Instance, and have Integration touch Points to fetch the data from the New Instance.

Please let us know's any Faces across this Situation and also share the Pro's and Con's of this Approach and best Practices to Consider.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

SBL Business Process Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center