Siebel Business Process & Functionality (MOSC)

MOSC Banner

Using Eligibility\Compatability rules from an external application

edited Dec 16, 2016 12:14AM in Siebel Business Process & Functionality (MOSC) 1 commentAnswered
Hello All,

I have been working on an SR where customer has applied ACR 331 and they expected to have all the operations for the Product Configurator Web Services when they actually only had 3 of them

Imported with ACR 331

/////////////////////////////////

Module Name : Configurator

Web Service : ProductConfigurator

Operations :
GetCfgObjectStructure
GetCfgObjectGroupItems
GetCfgObjectDefaultGroupItems

/////////////////////////////////


They do not get BeginConfiguration, EndConfiguration or UpdateConfiguration and this is by design.

The customer has now asked me the following:


/////////////////////////////////

Could you please provide your feedback on how it is possible to expose configurator functionalities (compatibility/eligibility rules, etc) to external systems from Siebel 7.8.2.5 using Siebel 7.8.2.5 native features?

The external system is an order entry system (web application).

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center