SBL-ISS-00120

Applies to:

Siebel eConfigurator - Version 7.7.2 [18325] and later
Siebel Pricer - Version 7.7.2 [18325] and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 8.0.1.6
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-2862939611. This is applicable to 8.x version as well.

Symptoms

SBL-ISS-00119, SBL-ISS-00120, SBL-ISS-00122, SBL-ORD-00103, SBL-ISS-00228

There is a strange behaviour with Product Configurator and Pricing details of which are given below.
When having 2 object managers running for the Standard Interactivity application, one for ENU(RIS users) and one for ENG(RUK users).
Steps to simulate the error for RIS users:
1. Go To Catalog screen => "Error occurred when getting 'Price List', please inform your administrator.(SBL-ISS-00228)" error comes on first click and after this, clicking 2nd time on the same screen Catalog view opens
2. Go To RICOH ONE Order Screen, create a new order => Click Browse Catalog button
3. Select a Product which can be customized and get the error "A major error was encountered while loading the Integration Object with the Siebel Adapter. Please contact your Siebel Administrator for more information.(SBL-ORD-00103)"
4. Clicking "Customize" button directly from the Catalogue view instead of going through the Order screen brings up proper view.
So 2 errors "Price List" and "Integration Object" errors
Action Step to simulate the error for RUK users:
1. Go to Catalog screen, select a Product which can be customized and clicking the "Customized" button brings up the error "<?>(SBL-ISS-00120)"
2.Go To RICOH ONE Order Screen, create a new order => Click Browse Catalog button
3.Performing the step 3 for RUK brings the same error "<?>(SBL-ISS-00120)"'
4.No Price List error in RUK application.

Cause

User interface definition for the product contained some LOV values that did not exist in LOV Type CFG_OBJ_ITEM_TYPES. 

 Relevant order types in LOV Type FS_ORDER_TYPE was missing in view Administration - Data > Order Types.

Solution

The log files revealed the following reasons for these three error messages.

(1) In the ENU application, when entering the RIS eSales Catalog Screen, RIS Product Catalog View (eSales), the application calls Business Service 'Shopping Service' method: 'SetShoppingCart'.

Among others this method retrieves the default price list and then verifies a custom column X_LSC_BU_ID. This verification fails, which leads to the error message:

ObjMgrSqlLog Detail 4 ... SELECT statement with ID: CE2A7A8

SELECT

:

FROM

SIEBEL.S_ORG_EXT T1,

SIEBEL.S_PARTY T2,

SIEBEL.S_ORG_EXT T3,

SIEBEL.S_PRI_LST T4

WHERE

T4.X_LSC_BU_ID = T3.PAR_ROW_ID (+) AND

T1.ROW_ID = :1 AND T4.X_LSC_BU_ID = T1.X_LSC_BU_ID AND

< --- Inner join, which apparently is not fulfilled

T1.ROW_ID = T2.ROW_ID AND

((T4.SUBTYPE_CD != 'COST LIST' AND T4.SUBTYPE_CD != 'RATE LIST') AND

(T4.NAME >= :2)) AND

(T4.ROW_ID = :3)

ORDER BY

T4.NAME, T4.SUBTYPE_CD

:

ObjMgrSqlCursorLog Trace 5 ... SQL Cursor with ID CE2A7A8 Fetch Rows: 0, Fetch All Time: 0.000 seconds.

:

ObjMgrBusServiceLog Error 1 ... (shopsvc.cpp (5056)) SBL-ISS-00228: Error occurred when getting 'Price List', please inform your administrator.

The customer was advised to check whether the application configuration should use an outer join on this custom column and whether the corresponding field in the default price list should have been filled.

While loading the configuration for the order line item the application finds an illegal order type:

ObjMgrSqlLog Detail 4 ... SELECT statement with ID: DA04A40

SELECT

:

FROM

SIEBEL.S_ORG_EXT T1,

SIEBEL.S_ORDER_TYPE T2,

SIEBEL.S_ORDER T3

WHERE

T3.ACCNT_ID = T1.PAR_ROW_ID (+) AND

T3.ORDER_TYPE_ID = T2.ROW_ID AND

< --- Inner join, which apparently is not fulfilled

(T3.ROW_ID = :1)

ORDER BY

T3.ORDER_NUM, T3.REV_NUM

:

ObjMgrSqlCursorLog Trace 5 ... SQL Cursor with ID DA04A40 Fetch Rows: 0, Fetch All Time: 0.000 seconds. :

ObjMgrLog Error 1 ... (cxobj.cpp (695)) SBL-ORD-00103: A major error was encountered while loading the Integration Object with the Siebel Adapter. Please contact your Siebel Administrator for more information.

The customer was advised to make sure that all relevant order types in LOV Type FS_ORDER_TYPE also exist in view Administration - Data > Order Types.

For more information about order types please refer to

Siebel Order Management Guide > Setting Up Order Management > Process of Setting Up Order Management > Setting Up Order Types

In the ENG application, when customizing a product in the product catalog, the application calls Business Service 'Shopping Service' invoke method: 'AddToCart', which in turn calls Business Service 'Cfg Web UI Service Loader' invoke method: 'LoadInstance'.

Among others this method retrieves the user interface definition for the product.

There were two errors in this definition:

1) SBL-ISS-00119: Inconsistent data is retrieved. Database record might be corrupted; List Of Values - CFG_OBJ_ITEM_TYPES; UI Group

2) SBL-ISS-00119: Inconsistent data is retrieved. Database record might be corrupted; UI Group Output trays and Finishers; UI Group Item - Output rays and Finishers; List Of Values CFG_OBJ_ITEM_TYPES; The value can not be resolved: Type - Relationship

This means that the user interface definition for the product contained some LOV values that did not exist in LOV Type CFG_OBJ_ITEM_TYPES.

The customer was advised to verify this LOV Type and make sure that all standard values and all further relevant values exist for both languages they are using:

-> English-American

- The English-American display values and language-independent codes should be the same.

-> English-British

- The English-British language-independent codes should be the same as the English-American language-independent codes.

Applying the three recommendations above eliminated the error messages.

Additional Keywords: Default Price List, PRICER_MASTER_PRICE_LIST_ID, Ordet Type, eConfigurator, Product UI Designer.

Applies to:

Siebel eConfigurator - Version 8.1 SIA [21039] to 8.1.1.3[21219] [Release V8]
Information in this document applies to any platform.

Symptoms

After applying the workaround from Doc Id 1085823.1 ("Product Definition Missing During Migration Of Promotion"), the following issues happen for promotions that have price adjustments:

Issue 1: when importing the same promotion with price adjustment for a subcomponent multiple times, the import creates more records with the same price adjustment for the subcomponent.

Steps:

1. Create a customizable product with a subcomponent.
2. Create a new bundle promotion just with this complex product and add a price adjustment on a subcomponent level;
3. Create a new workspace project with our promotion
4. Perform a (full structure) export, which was done successfully
5. Import the file to another environment. The following error occurs:
[1] Partial Import: ; [1] Cannot perform 'UpdateRecord' on the business component 'Product Promotions Relationship VBC'(SBL-EAI-04421); Data will be skipped(SBL-ISS-00120)
6. Apply the workaround from Doc ID 1085823.1 ("Product Definition Missing During Migration Of Promotion")
7. The import of the promotion is now successful, but when importing it the second time, the import created twice the same price adjustment for subcomponent with same data.


Issue 2: Price adjustments not working for imported promotions

The price adjustements don't work correctly for imported promotions, when the adjustment is set for the components of a customizable product inside a promotion.

The issue can be reproduced at will with the following steps:

Setup: activate dynamic pricing, set System Preferences - Enable AIA Comms - TRUE.

Environment 1:
1) Create a new Product AA_Component and release the product
2) Create a new Product AA_Root_Product add a relationship with the product AA_Component and release the product
3) Create a new Bundled Promotion AA_Promotion
4) Add AA_Root_Product with min. and max. cardinality = 1
5) Add price adjustment - Drilldown on AA_Root_Product product name,
create new adjustment with Adjustment Type=% Discount and Value =20
a. Screen Administration - Product, View Product Promotions -> Pricing (Components) - ISS Promotion Pricing Components List Applet - here is added an AA_Root_product
b. Drilldown on AA_Root_Product hyperlink - > View  ISS Promotion Structure Designer View (Pricing) -> Promotion Config Item List Applet here a price adjustment for component is created (these adjustments are
stored in the table S_PROM_PMTRX)
6) Release new version of promotion and Clear Cache
7) Create a new Workspace Project and add AA_Promotion
8) Export the Workspace Project

Environment 2:
1) Import the workspace project to another environment
2) Add the AA_Promotion, AA_Root_Product and AA_Component to Price List
3) Add AA_Promotion to Sales Order and check that the promotion price adjustment is not applied

Cause

These issues are caused by application defects.

• Issue number 1 is reported in the following Change Request: 10594423 Issue related to import of product promotions with price adjustment
• Issue number 2 is reported in the following Change Request: 10596964 Price adjustments not working for imported promotions

Solution

Both defects have been resolved in the 8.1.1.4 Fix Pack and it is planned to be included in 8.0.0.14 FP. There is also a quick fix for 8.1.1.3 release: 8.1.1.3[ 21219]QF0313 SBA BugID: SBA: 10056612, and a quick fix for 8.0.0.9: 20433 QF09AQ 13058292.

KEYWORDS: promotion, import, workspace, price adjustment

Applies to:

Siebel eConfigurator - Version: 7.7.2.3 SIA [18361] to 7.7.2.12 SIA[18393] - Release: V7 to V7
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2.3 [18361] Com/Med
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 5.8
Database Server OS: Sun Solaris 5.8

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

Symptoms

We are currently experiencing an error when importing products into our 7.7 environment. The error we receive is as follows:

Error occured during Import/Export operation - ImportProduct;

Data will be skipped - Input Property Set; Product; Data cannot be imported;

Err [1] The ability to delete records is not available in this screen or applet (SBL-DAT-00278)(SBL-ISS-00120)(SBL-ISS-00120)

I have been able to reproduce this error using a vanilla 7.7 srf.

Cause

Bug: 10474687

Not applicable for 7.8 and later.

Solution

There are 2 two business components (Cfg CX Prod Versions and  Cfg CXP Driving Drilldown BusComp (Pricing)) that still had the setting: No delete = TRUE'.
After changing these both to FALSE and on the latter BC set No Insert, No Update and No Merge to FALSE then compiled these two BC's and ran the dedicated client. The product import process then ran successfully.
There is a magic record in S_PROD_CFGVER with special id, don't pointing to any product records, used for cache synchronization: S_PROD_CFGVER.PRODUCT_ID = CFG_CACHE (same for CFG_CP_ROUTE for distributed caching file refresh)
Record is updated, every time user releases a product or requests cache update.
If the record is not there it will be created on first update request.
If duplicates are detected, we will try to clean up with Cfg CX Prod Versions BusComp (at very end of RequestObjectUpdate function); in such case an error will be generated because of NoDelete property on the BC. This will happen at the very end of the method - therefore actual request will steel be posted, despite the error.
In normal operations this will just pop-up annoying message without any bad consequences (release and update still happens correctly), but in case of import (or by other operation enclosed in a scope of transaction) will result in transaction cancellation.
This condition might happen, when on a fresh DB installation, two OM's are simultaneously triggering RequestObjectUpdate (by releasing a product or ordering cache refresh ); both will try to create magic record, on next update time duplicates will be detected, and described error generated.
Since all the other times we are not using this BusComp to delete, it is very hard to reproduce these issues.

Solutions:
1. Change NoDelete property to FALSE on that Cfg CX Prod Versions BusComp and recompile srf as you have already done.
2. Run a sql to remove the duplicate magic records (Technical Support does not provide the sql)
Bug 10474687 has been logged to address this defect.
One should not have more than 1000-2000 products in a 7.x CP model for performance/scalability/usability reasons more than these many items you will not able to put meaning full rules and get decent performance times.
Furthermore, I saw one past sr where the user has issues importing a product of just 7 MB and yours is 22 MB so it will have the behavior you have encountered.
Import is done inside of transaction - the size is usually limited by DB settings
Another limitation is a timeout on the server connection.
Cursor size might be a problem as well - release is in bidirectional query mode
I have searched SupportWeb and found the following postings related to your question:
Unpublished document Model Export utility (Doc ID 522113.1)
=> The Import/export performance is dependent on the memory of the user's machine.
Unpublished Service Request #: 2-214114 - Product XML Export/ Import => You can migrate products one at a time.
You can export and import products in groups that are manageable by the capacity of the system where you are running the Product Export and Product Import functions, one group of products at a time.
Please see also
Siebel Configurator Administration Server Settings for Optimized Performance and Scalability (Doc ID 477986.1)
After changing the DSMaxFetchArraySize parameter on the server to -1 this allowed the larger products to import successfully.

References

BUG:10474687 - [CR#12-KDLATB][FR#12-KDLATB+F] CP ADMIN: IMPORT OF CP FAILS IN 7.5.3.4
NOTE:477986.1 - Siebel Configurator Administration Server Settings for Optimized Performance and Scalability

Applies to:

Siebel eConfigurator - Version: 7.8.2.4 SIA [19224] to 7.8.2.4 SIA [19224] - Release: V7 to V7
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Professional)
Version: 7.8.2.4 [19224]
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9
Applicable to Siebel version 8.x as well.

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

Symptoms

Issue occurs while using products export option available in Vanilla Siebel. When creating multiple versions for a product, its required to move baselined Products version for testing. So when trying to export one of the prior versions. E.g. "Wireless Broadband" is one among the product where Version 9 trying to export (latest version for this product is 27). When trying to do so it throws up an error "Set of related Objects (Dynamic Model)". Below is the error log:

ObjMgrLog

Error  1 2007-01-23 17:01:28  (cfgobjbr.cpp (2299)) SBL-ISS-00120: Object Type ISS_PROD_DEF Name Version 8 Not derived from Class - VAS Email

ObjMgrBusServiceLog InvokeMethod 4 2007-01-23 17:01:28  Business Service 'ISS Authoring Import Export Service' invoke method 'ExportFullVOD' Execute Time: 267.193 seconds.

ObjMgrBusServiceLog InvokeMethod 4 2007-01-23 17:01:28  End: Business Service 'ISS Authoring Import Export Service' invoke method: 'ExportFullVOD' at 135e0d50

ProcessRequest ProcessRequestDetail 4 2007-01-23 17:01:28  SWE Action Manager - PostActionDone

ObjMgrBusServiceLog Delete  4 2007-01-23 17:01:28  Business Service 'ISS Authoring Import Export Service' was deleted at 135e0d50

Cause

As the recursive export of previous versions of products has not been followed, the error occurs.

Solution

The customer encountered an error when trying to export one of the prior versions of their product.When they tried to do so it was throwing up an error "Set of related Objects (Dynamic Model)".

The customer was exporting the prior version from the Administration - Product > Product Definition where all prior releases show.

The same error was reproduced using a sample product in the sample database.

On tracing the following error showed:

ObjMgrLog Error 1 2007-03-22 14:47:04 (cfgobjbr.cpp (2122)) SBL-ISS-00120: Data Collision; Version 5 != 4

ObjMgrBusServiceLog InvokeMethod 4 2007-03-22 14:47:04

Business Service 'ISS Authoring Import Export Service' invoke method 'ExportFullVOD' Execute Time: 0.031 seconds.

The error message above indicates Version 5 != 4 and so will not allow you to export.

The only way in getting around this is to click on the version in the lower applet that you want to export then click on Revert to Selected Version and release and then you can export this version.

However, exporting Full Structure of a product from Product Administration&quot > Product Definition > Versions is not recommended; you should not use it for data migration, dependencies are not controllable there as it was preserved only to allow quick export for analysis ie. to visually check your structure with xml editor.

However, it is advised to use the following method for recursive export of previous versions of products.

1) Determine what is the actual time, that you want to use to obtain your product's definition - based on your old version's "StartDate"/"EndDate" interval

2) Create a Workspace Project and include your product into it

3) Set "BaseDate" within the interval, you obtained in step 1; Do not check "Use Project" flag and export content as full structure.

During the Export, there is additional functionality attached to "Base Date"

1) If exporting from active JWS (flag "Use Project" is checked) all root objects, listed in the content, will pick-up workspace versions, all referenced objects (resolved trough dependencies) will pick up a published version effective for "Base Date".

2) If exporting from non-active JWS (flag "Use Project" is not checked) all root objects, listed in the content, will pick up a published version effective for "Base Date", all referenced objects (resolved trough dependencies) will pick up a published version effective for "Base Date".

3) If "Base Date" is not specified we will try to use the value of "Effective Start Date"; if "Effective Start Date" is empty as well - current time will be used.

Effective Start Date:

This date is used for publishing. If no Testing Date is entered, this value is the date that the system uses to determine what versions should be exported for dependent items when the user chooses to export the full structure of the items in the Workspace Project

Base Date: This date is used for temporarily setting arbitrary time mainly for testing and development when Workspace Project is activated. Enter the date used as the date for dependent items for full structure export. If both Effective Starting Date and Base Date are filled, Base Date is used.

 

 

 

Applies to:

Siebel CRM - Version: 8.0.0.6 SIA [20423] - Release: V8
Information in this document applies to any platform.

Symptoms

ISSUE
----------
When navigating to Sales Order > Catalog > Search, user can perform a search without problem.  However, if user is navigating to another View and then go back to the Catalog Search view, user will receive the error.  At this point, if user is trying to navigate to the Catalog Search view again, the same error will display.   User would have to logoff from the application and log back in to the application to be able to navigate to the Catalog Search view without seeing the error.  

SEQUENCE OF STEPS
--------------------------------
Steps to replicate the issue:
1. Navigate to Sales Order > Catalog > Search and do the search for a product.  Then click Reset button
2. Navigate to another view like the Line Items View and then go back to the Catalog > Search view, user will receive the error.

ERROR MESSAGES/EXPECTED BEHAVIOR
----------------------------------------------------------
The following error message is found in GUI:
Type - ISS_CLASS_DEF; The value is required; Identifier - (SBL-ISS-00120)

It is expected that users should be able to do the search on the Catalog Search view after navigating to another view and go back to the same view without the above error.


ENVIRONMENT
-----------------------
The above issue is replicated in version 8.0.0.6 SIA eCom application.

Cause

The root cause of the issue is due to the Code is not finding any valid entries on the 'ISS PS Direct Subclass' business component.  There is a Join on tables S_VOD_VER, S_ISS_OBJ_DEF and S_VOD) for this BusComp and field PARAM_SEARCH_FLG on table S_ISS_OBJ_DEF which was not set on any of product classes. 

CR 10583849/FR 12-1VR5LH9 was logged to address the above issue for version 8.0.0.6 SIA

Solution

The code solution is delivered in “8.0.0.6 [20423]QF0696 BugID: SBA: 9357411”.   Customer applied this QF0696 and the Error on the Catalog Search view is resolved.

References

BUG:10583849 - ATTRIBUTE SEARCH APPLET ERROR

 

 

 

 

Applies to:

Siebel eConfigurator - Version: 7.5.2.100 SIA [15252] and later   [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.2.100 [15252] Fin Svcs
Database: Oracle 8.1.7.4
Application Server OS: Sun Solaris 8
Database Server OS: HP-UX 11i

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

Symptoms

SBL-ISS-00120 We have been rebuilding a segment of our catalog to gain better performance. As part of this task we have had to add 255 rules to one product. (Specialty Open). The product is associated to a template. The rules in question are set at the product level. As we entered them we validated the UI occasionally without any failure. After the last batch of rules entered we start getting errors. Dialog box displaying "%1". We started disabling rules and found that Siebel behavior was fairly consistent with a few rules. We had rebuild these rules and when that was unsuccessful we built them from scratch then disabled the originals. Neither process has worked for us. The part we are not understanding is that several of the rules that are now failing had worked in prior validations.

Cause

"Internal Worker Error" and "%1" error message

Solution

Behavior:

After adding Set Preference rule which contained nested Requires rules, when user tried to validate in Product Administration, "Internal Worker Error" and "%1" error messages were invoked.

Resolution:

The Set Preference rules were based on attribute values which appeared first in the LOV in the selection page of eConfigurator and thus was causing the error messages. To eliminate the Internal Worker & %1 errors the following steps were taken:

1. An additional LOV called "Please Select a Value" was added to all the attributes & we made that value appear first in the LOV by setting the Order in Class Administration to 1. So when users enter the configurator, "Please Select a Value" appears first for all attributes.

2. In Class Administration removed all default values for all attributes so the Default field is left blank.

3. For the customizable product, in Product Administration, Dynamic Attribute tab/applet, ensured that no Default value was set for any of the attributes.

The above three steps eliminated the Internal Worker Error & "%1" error messages and the customizable product was behaving properly.