SBL-DAT-00383: Field '%1' is defined more than once in business component definition '%2'.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Pub Sect
Database: Oracle 9i
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 9

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

Symptoms

SBL-DAT-00383

Hi,

I created two applets for Contacts and pasted them in the Visible Contact List View. When I tested just with List Applet it worked fine. When I tested it with both the List and Form Applets it gave me the following error. I inactivated the field, compiled and tested. It gave me the save error but with a different field. I inactivated a couple of fields. The point to be taken here is the fields come in the error have not been mapped to any Control/Column. I created an MVF. I inactivated and tested the MVF field created by me. But I still got the same error.

We detected an Error which may have occurred for one or more of the following reasons:


Field 'Personal Full Address' is defined more than once in business component definition 'Contact'. Please ask your systems administrator to check your application configuration.(SBL-DAT-00383)

The SBL-DAT-00383 error occurs when home page is trying to load. When I access the Contacts screen i get the following error:

We detected an Error which may have occurred for one or more of the following reasons:


An error has occurred creating business component 'Contact' used by business object 'Contact'. Please ask your systems administrator to check your application configuration.(SBL-DAT-00222)

Kindly advise.

Thanks

Regards
Vaishnavi

Solution

Message 1

For the benefit of other users:

After reviewing the customer Contact Business Component it has been determined that the error message was triggered by the Force Case property set to ForceUpper for both First Name and Last Name field’s objects.

Please kindly note that per the Object Types Reference guide > Siebel Object Types >
Field: the Force Case property that defined the case for the field value has only 3 Valid values: UPPER, LOWER, or FIRSTUPPER.

I tested and I found that when using the Standard application with the standard Contact Business component object and setting the Force Case property to ForceUpper for both the Last Name and First Name fields I could reproduce the same error message.

Customer confirmed that changing this Force case property value to a valid one resolved the issue.

The change request 12-10HS482 has been logged as the error message is misleading.

If there is any error message it should be similar to:
The Force Case property value is incorrect: it is currently set to “ForceUpper”

Field Force Case property that has only 3 Valid values: UPPER, LOWER, or FIRSTUPPER.

Thank you
Siebel Technical Support

Applies to:

Siebel Tools - Version: 8.0.0.2 [20412] - Release: V8
Information in this document applies to any platform.

Symptoms

Following errors encountered in Object Manager Log and JMS Component Log.

(objdef.cpp (17500)) SBL-DAT-00383: Field '(SLA 3) Organization.Organization Id' is defined more than once in business component definition 'Opportunity Product - CORE'. Please ask your systems administrator to check your application configuration.

Also, (objdef.cpp (17500)) SBL-DAT-00383: Field '(SLA 6) Organization.Organization Id' is defined more than once in business component definition 'Account Category'. Please ask your systems administrator to check your application configuration.

Cause

The error message SBL-DAT-00383 is also found in siebel.log when using dedicated client.

Business Components, 'Opportunity Product - CORE' and 'Account Category', are mentioned in the error message SBL-DAT-00383.

Review of 'Opportunity Product - CORE' and 'Account Category' shows one common point, both of them have the MVL Link “Organization” linking to Internal Division.

Compare Customer's Internal Division BC and Vanilla Internal Division BC shows that in Customer’s Internal Division BC, there are 2 join specification for the join “Organization”. The 2 join specifications are the same except for the Name.

Solution

Inactivate one of the join specification “Organization Id" and compile. Start the application and the error SBL-DAT-00383 was not found in the detail siebel.log anymore.

Hence, the issue is due to duplicate join specifications in the join child object “Organization” of Customer's Internal Division BC.

Please log a Service Request if there is any doubts or clarifications required regarding this.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.9 [16194]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Advanced Server SP 3

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

Symptoms

SBL-DAT-00383

We have almost completed our development upgrade to 7.8
We have completed a full compile, trying to launch a thin client session and getting the following error in the SWSE logs

Field '% Off MSRP' is defined more than once in business component definition 'Order Entry - Line Items'.

There is no duplicate field in this business component.
After inactivating this field & recompiling, it errors on some other field with the same error message.

Thanks
Mahesh

Solution

Message 1

Customer resolved this issue by compiling a new srf against the 7.8 out of box repository. Then connected to web client and set the log levels for the object manager and then found out another error in the object manager log -

'demoralization of a calculated field in a column is not allowed for price list id field'.

The order entry - line item bus comp field 'price list id', based on a column, had a value in the 'calculated value' field property, after clearing out this property value, it stopped giving the error -

Field '% Off MSRP' is defined more than once in business component definition 'Order Entry - Line Items'.

Regards,
Siebel Technical Support