Search This Blog

SBL-CFG-00147: While making a request, the Internal Configuration Engine encountered the following error:%1

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.2.216 [16084] Com/Med
Database: Oracle 9.2.0.2
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1029691988.

Symptoms

SBL-CFG-00147

When clicking on the Modify button from the Account Summary View or clicking on the customize button on the order entry - line item view for an exisiting order, we are getting either of the following error:

[1] While making a request, the Internal Configuration Engine encountered the following error: Internal Worker Error
[2] Error invoking service 'SIS OM PMT Service', method 'Reconfigure Product Instance' at step 'Reconfigure Product Instance'

[1] The Complex Object Root you are trying to get was not found. Pleas contact your Siebel Administrator for more information.
[2] Error invoking service 'SIS OM PMT Service', method 'Reconfigure Product Instance' at step 'Reconfigure Product Instance'

We went through FAQ 1859 which states that for maintainence release 7.5.2.200 SIA and above, we need Order_Item_Asset_Based.sif file to resolve a similar error.

Could you please confirm that this error is similar to that specified in FAQ 1859 and if so, we need the sif file at the earliest.

Thanks,

Solution

Message 1

For the benefit of other users:

Customer had upgraded from Siebel 99.6 to Siebel 7.5.2 and had assets transfered from their previous environment to the upgraded environment. When clicking 'Modify' on existing assets customer was receiving the error.

Technical Support to investigate suggested to inactivate the Configurator rules and 'Modify' was successful. Technical Support then suggested to implement Auto-Match functionality as detailed in 'Technical Note 318: Enabling Self-Healing for Complex Order Processing in Siebel eBusiness Industry Applications version 7.5.2.'.

Customer however had tried to implement Auto-Match and had encountered an error for which another Service Request had earlier been logged.Once the Auto-Match error was resolved and implemented the 'Modify' on existing Assets was successful. The error in Auto-Match was due to the steps 'Display Warning' & 'Set Warning Message' exceeding the length of 255. As customer did not want to display any message when the Assets where Auto-matched Technical Support recommended customer to remove the 2 steps.

Existing products and services that comprise a customer's service profile in releases prior to Siebel 7.x will typically not match the format and structure of the Siebel 7 customizable product used to validate them. A translation solution is required to handle the scenarios and the Technical Note 318 details the steps required.

No comments:

Post a Comment