SBL-DAT-00398: Field '%1' does not exist in definition for business component '%2'.

Applies to:

Siebel System Software - Version: 7.8.2 SIA [19213] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213] CHS Com/Med
Database: Oracle 9.2.0.7
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

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

Symptoms

In the Sample Database of Siebel ,Create an integration object (IO) named 'Product Definition to Background System'
Include integration components (ICs) :

• 'Internal Product - ISS Admin'
• 'ISS Product Attribute VBC'
• 'Price List Item'
  
• 'Cost List Item'   
  

In Business Service Simulator simulate Business Service(BS) EAI Siebel Adapter using method  Query to get Product information out.

The following error is observed :

Method 'Execute' of business component 'ISS Product Attribute VBC' (integration component 'ISS Product Attribute VBC') returned the following error:"Field 'VOD Object Num' does not exist in definition for business component 'ISS Product VOD BusComp'.
Please ask your systems administrator to check your application configuration.(SBL-DAT-00398)"(SBL-EAI-04376) (0x562f)

Cause

EAI cannot be used to retrieve versioned seed data information.
Enhancement Request 12-17911AG has been logged to include information on this.

Solution

EAI cannot be used to retrieve versioned seed data information.
Enhancement Request 12-17911AG has been logged to include information on this.

To retrieve them, please use the provided Import/Export functionality in the workspace product.

For details on the use of Import/Export functionalities, please refer to Product Administration Guide > Releasing Products and Other Versioned Objects > Migrating Products Among Environments.

References

BUG:12-17911AG - EAI CANNOT BE USED TO RETRIEVE PRODUCT VERSIONED DATA

Applies to:

Siebel Tools - Version: 7.7.2 [18325] and later   [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2.1 [18353] FRA
Database: Oracle 9.2.0.1
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

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

""Checked for Relevance on 08-Sep-2010""

Symptoms

We have an issue with activities created in the Calendar screen. We do not reproduce the behavior in other screens where activities can be created. To reproduce the defect, here is what we do.

- Select the Calendar Screen tab to display the default calendar view (standard and not configured)
- Click on the 'New' button on the Daily Calendar applet, to create a new record. This navigates the user to the 'eCalendar Detail View' (almost not configured). Open the Employees MVG, select an employee in the associate applet and click the Add button to add the record in the MVG applet.

This triggers the following error message:
- - -
Le champ '' est introuvable dans la definition du Business Component 'Action'...(SBL-DAT-00398)
- - -

This message can be found in the siebel.log file, followed by the message:
- - -
SBL-DAT-00398: Le champ 'Appt PIM Flag' est introuvable dans la definition du Business Component 'Action (Busy Free Time)'. Veuillez demander a l'administrateur systeme de verifier la configuration de l'application.
- - -

What is the 'Appt PIM Flag' field? What does trigger its update? Where do we have to check?

Cause

This issue was triggered by a new MVF exposed on applet 'eCalendar Detail Applet' in view 'eCalendar Detail View'. This one was based on a new MVL added in BC 'Action' and similar to the standard MVL 'Employee'. This new MVL was based on a copy of the standard link used by MVL 'Employee' namely 'Action/Employee'. The intersection table involved was therefore the same for both links: S_ACT_EMP.

NOTE: The requirement was to have 2 different M:M relationships between activities and employees depending on the employee type (field 'Employee Type Code'). A search specification had been added on the links and on the MVG applets involved to filter the employees.

The error was due to the 'Primary ID Field' property of the new MVL that was set to blank. The issue was resolved once a primary ID field (a custom field) was configured for this MVL.

Note that the standard MVL 'Employee' has "Primary Owner Id" as primary ID field. This BC is involved in the visibility settings of BC 'Action' (BusComp View Mode "Personal"). The new MVF was not however involved in the visibility setting of the BC and a primary ID field was therefore not required (even if it is recommended for performance reason). Also the behavior was only observed in the Calendar which is a very specialized feature of Siebel application.

Note also that this behavior is reproducible using Siebel application version 7.7.2 (SEA) by performing the steps below:

# Using Tools:

1. In BC 'Action' create a new MVL by copying standard MVL 'Employee'.
2. Clear the property 'Primary ID Field' for the new MVL.
3. Create a new MVF based on the new MVL.
4. Expose this MVF on 'applet eCalendar Detail Applet' ("Edit" applet view web template).

# Using Siebel application:

1. In "Calendar" screen click the "New" button to create a new activity.
2. In view 'eCalendar Detail View' open the "Employees" MVG applet.
3. Associate a new employee using the "Add >" button:
> The employee will be correctly associated but the following error will occur (in ENU language):
- - -
Field '' does not exist in definition for business component 'Action'.

Please ask your systems administrator to check your application configuration.(SBL-DAT-00398)
- - -

This behavior is not reproducible in other views where activities are created, for example in "Activities" screen. It has also not been reproduced in versions 7.7.2 SIA, 7.8.2 (SEA and SIA) and 7.5.3 (SEA and SIA).

Bug 12-1AZHAQG has been logged to address the unexpected behavior observed in version 7.7.2 SEA.

# Additional information:

The error message below is only a warning, also generated by the standard Siebel application, and is not involved in the issue encountered by the customer:
- - -
SBL-DAT-00398: Field 'Appt PIM Flag' does not exist in definition for business component 'Action (Busy Free Time)'.
- - -

Solution

The issue was resolved once a primary ID field (a custom field) was configured for the new MVL.

References

BUG:12-1AZHAQG - ERROR SBL-DAT-00398 IN CALENDAR - ACTION BC AND NEW EMPLOYEE MVL WITHOUT PRIMARY ID FIELD

Applies to:

Siebel Tools - Version: 8.0.0.5 SIA [20420] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Why is the "Field 'FileSrcType' does not exist in definition for business component 'Service Request Attachment'" error message appears when an invalid value for "KeyFieldName" argument is entered in CreateFile method? This is not appropriate.

In regards to the "Field 'FileSrcType' does not exist in definition for business component 'Service Request Attachment'" error message, it does appear inappropriate to indicate that "FileSrcType" being missing when in fact an invalid value has been passed into "KeyFieldName" argument of "CreateFile" method. The value which "KeyFieldName" argument is expecting is the field name that contains the file name. In this case, it should be "ActivityFileName".

Cause

It is caused by the Product Defect of Siebel version 8.0.0.5 SIA

Solution

For the benefit of other users:

Change request 12-1SEPOIB "In appropriate error message for wrong value of KeyFieldName arg in CreateFile" has been logged to request for a more appropriate and meaningful error message.

References

BUG:12-1SEPOIB - IN APPROPRIATE ERROR MESSAGE FOR WRONG VALUE OF KEYFIELDNAME ARG IN CREATEFILE

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 7.5.3

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00398: Field '%1' does not exist in definition for business component '%2'. Please ask your systems administrator to check your application configuration.

Scope

This document is informational and intended for any user.

SBL-DAT-00398: Field '%1' does not exist in definition for business component '%2'. Please ask your systems administrator to check your application configuration.

Explanation

The field being accessed is not defined in the buscomp definition. The application may be trying to access the field through any of the following channels: accessing a view, running a PDQ, through scripting, attempting to set a Pick Map, through the Synonym property on the business component, through a join or multi-value link.

This error may also occur during an upgrade process if new fields were not added to a business component.

Corrective Action

Determine which field the application is trying to access by spooling SQL and checking log files. Deactivating scripting and removing default PDQs can help pinpoint what process is triggering the error. Once the field is identified, check the buscomp configuration in the repository and ensure that the field is defined and active.

If the error is occurring during an upgrade process, compare the properties of the copied buscomp with the standard buscomp, and check the Upgrade Ancestor property of the copied buscomp.

If the buscomp in question uses a special class, ensure that you have not inactivated, deleted, or renamed any fields. For more details on working with special classes, refer to Siebel Bookshelf version 7.5.3 > Configuration Guidelines > Creating and Modifying Objects > Creating Specialized Objects > Cloning Specialized Objects.

For more details on troubleshooting techniques to diagnose this error message, refer to Troubleshooting Steps 23, which is available on SupportWeb.

Applies to:

Siebel Tools - Version: 7.8.2.3 [19221] - Release: V7

Information in this document applies to any platform.

Symptoms

When creating a new opportunity the attached error message appears:
Field 'Opportunity Row Status' does not exist in definition for business component 'Opportunity - Personal - VisMvgSqlBCDef'.
Please ask your system administrator to check your application configuration. (SBL-DAT-00398)

Cause

Product defect CR 12-1SOST29 - "Two view modes with the same owner type are causing an error when a new Opportunity is created"

1) In Siebel Tools:
- make a copy of the "Opportunity/Position" link, name it "Opportunity/Position1"
- change the new record on S_ACCNT_POSTN inter table (for test purpose only) and Inter Parent Record to OU_EXT_ID
In BC Opportunity:
- copy "Position" MVL and name the new record "Position1"
- copy "Sales Rep" MVF and call it "Sales Rep1" and base it on the new MVL "Position1"
- copy "Seles Rep" view mode and name it Personal and base it on MVL "Position1" and MVF "Sales Rep1"
Now reverse the name, MVF and MVL of the two view modes in order for the Personal view mode to be older then the standard Sales Rep view mode.

2) In Siebel Call Center navigate to Opportunity screen in My Opportunities view and create a new opportunity. The error popup:
---------------------------
Field 'Opportunity Row Status' does not exist in definition for business component 'Opportunity - Personal - VisMvgSqlBCDef'.

Please ask your systems administrator to check your application configuration.(SBL-DAT-00398)
---------------------------
The error is not preventing the record from being created.

Workaround - revert the order of the two view modes in order for the standard one (having a correspondence Opportunity Status Field in Position BC) to be the first evaluated.

Solution

Switch the two view modes names, MVL and MVF.
This workaround has successfully been tested in standard.

References

BUG:12-1SOST29 - TWO VIEW MODES WITH THE SAME OWNER TYPE ARE CAUSING AN ERROR WHEN A NEW OPPORTUNITY IS CREATED

Applies to:

Siebel Consumer Sector Call Center - Version: 8.1.1 SIA [21111] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

After applying 8.1.1.1 FP on an environment that originally had 8.1.1 and ACR 480 installed the 'Baseline' button on the Promotions Screen is throwing the following error:  

"Field 'Est Variable Spend Per Unit' does not exist in definition for business component 'CPG Plan Account Promotion Product'.  Please ask your systems administrator to check your application configuration.(SBL-DAT-00398)"

Cause

The following System Preference is missing in the application for product version 8.1.1.1 after applying ACR 480:

Trade Promotion Extended = True

This System Preference setting is described in the Release Notes for Product Version 8.1.1.x

Solution

1) Create the following System Preference setting
Name: Trade Promotion Extended
Value: True

2) Restart the server and application

References

NOTE:880452.1 - Siebel Maintenance Release Guide, Version 8.1.1.x