SBL-EAI-13011: Field '%1' in the integration component '%2' contains value '%3', which is longer than allowed length of %4 characters.


Applies to: Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Life Sci
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP 9000 Series HP-UX

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

SymptomsSBL-EAI-13011

When I create a Deployment Project of type "AssignGroup" I can export the Assignment Rules out of Siebel in a Deployment Session. However, when I attempt to reimport the rules using a Vanilla SRF, I get an error stating that the Party name exceeds 30 characters for one of the position candidates.

Error Message:
We detected an Error which may have occurred for one or more of the following reasons:
Field 'Party Name' in the integration component 'Assignment Group Position' contains value 'Salesrep1 - Hospital - AssgnMgr Test', which is longer than allowed length of 30 characters.(SBL-EAI-13011)

I've updated both the "UDA Assignment Rule Groups" and "UDA Assignment Rules" integration objects --> Assignment Group Position --> Party Name field's External Length property from "30" to "150". Note that the column it maps to is also 150 length, S_PARTY.NAME. After recompiling I was able to import the assignment rules as expected.

At your earliest convenience please confirm:
1) Was the "External Length" property set to "30" for any particular reason?
2) Is the workaround supported by Siebel?
3) Can I expect this repository change to be in a future Siebel release?

Thank you

SolutionMessage 1For the benefit of other readers:
Customer is using Application Deployment Manager (ADM) to import AssignGroup data using Deploy from file option and getting error
“Field 'Party Name' in the integration component 'Assignment Group Position' contains value 'Salesrep1 - Hospital - AssgnMgr Test', which is longer than allowed length of 30 characters.(SBL-EAI-13011)”

Resolution
Customer updated both the "UDA Assignment Rule Groups" and "UDA Assignment Rules" Integration Objects --> Assignment Group Position --> Party Name field's External Length property from "30" to "150". Note that the column it maps to is also 150 length, S_PARTY.NAME.
After doing the above changes and recompiling the changes the problem was resolved.
Similar problem was also found on Integration Object - UDA Assignment Rules and UDA Assignment Rule Groups
for Integration Components (IC) Assignment Group Organization for both the IO's. It is suggested to change the length from 30 to 150 for Party Name field for both the Integration Components.
A Change Request # 12-Q3KZZH was logged to address this Product Defect.

Thank you,

Siebel Technical Support
Keywords: ADM, ADM and AssignGroup, Application Deployment Manager, ADM and Assignment













Applies to: Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Microsoft SQL Server 2000 SP 2
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

SymptomsSBL-EAI-13011, SBL-EAI-04397

Hi,

The ADM tool was working well for migrating Views and Responsibilities untill we applied Siebel 7.7.2 patch. Here we are observing that View names with less than 50 characters have no issues but more than 50 characters are throwing out the attached error. Have included the XML files and screen shots of the error messages.

Thanks.

SolutionMessage 1For the benefit of other users, ADM uses vanilla "UDA View Access" Integration Object to deploy views. In 7.7.1 if you create a new view named "Siebel Account Invoice Adjustment Request Items View (eService)" in Tools, by using "Copy Record" on vanilla view named "Account Invoice Adjustment Request Items View (eService)". This view name is 62 characters (with spaces); you are able to deploy it successfully. After applying 7.7.2 patch, you are unable to deploy it.

In customer’s case, they got 2 different errors:

1. Single file import:

No use key can be used for the Integration Component instance 'Feature Access'.(SBL-EAI-04397)

2. Multiple files import through workflow process, a different error:

Field '<?>' in the integration component '<?>' contains value '<?>', which is longer than allowed length of '<?>' characters.(SBL-EAI-13011)

The problem is identified to be as follows:
=====
The problem is with the external length of the Name field of "Feature Access" Integration component. Should be set to column length of 75 instead of BC Text Length of 50.
=====

The Change Request CR# 10482048 has been logged to address this issue, and it has been fixed in Siebel 7.8.


...continued in next activity...

Message 2The workaround is the following:

In Siebel Tools:
1. Lock the project "EMT Objects".
2. Navigate to Integration Object > choose "UDA View Access" > Integration Component > choose "Feature Access" > Integration Component Field > choose "Name" field. Change "External Length" property from 50 to 75.
3. Recompile client srf, and copy the recompiled srf to Siebel Server side.

And after that, the import works fine on 7.7.2 for the view with name = 62 characters. This should be the only change required.

Another property for this Integration Component Field is "Length"; it can be left as 50. We don't need to change "Text Length" property on Name field of "Feature Access" Business Component either.


keyword search: SBL-EAI-13011





















Applies to: Siebel eConfigurator - Version: 7.8.2.4 [19224] - Release: V7

Information in this document applies to any platform.

GoalWhen entering more than 100 characters in a product attribute within the configurator the following error occurs:

Error:"Error invoking service "ISS Copy Service", method "StoreEAI" at step "Save Instance". (SBL-BPR-00162)
Field "Value" in the integration component "XA" contains value "Long Value.....", which is longer than allowed length of 00 characters. (SBL-EAI-13011)"

How to define a Product Attribute to store more than 100 characters?

SolutionFor the benefit of other readers,

Please note, 250 is the default size of the column definition in the database. Theoretically you can increase this definition as well as the definition of the according business components and integration objects. However, this may have adverse impact to your application. Therefore, in order to have more than 250 characters I strongly recommend to consult with Expert Services in order to find the best solution for your business needs.

Currently it is possible to increase the attribute text length up to 250 characters. For a detailed description how to achieve this, please refer to the following posting:

HOW TO: How can the size and the amount of text that can be entered into an attribute edit box within an eConfigurator selection page be adjusted? (Doc ID 477258.1)


The same change has to be done in the "XA" integration component of "7.7 Quote Integration Object" integration object.



recompile .srf

NOTE, similarly you may need to adjust some other Integration Objects as well in order to allow more characters per attribute for Orders and Assets.



Thank you,
Oracle Product Support


References


BUG:10547901 - PROVIDE COMMENT FIELD WITH 2000 CHARS LENGTH PER PRODUCT THAT IS EDITABLE IN CONFIGURATOR
NOTE:477258.1 - How can the size and the amount of text that can be entered into an attribute edit box within an eConfigurator selection page be adjusted?



















Applies to: Siebel CRM - Version: 7.5.3 SIA [16157] to 8.1 [21039] - Release: V7 to V8
Information in this document applies to any platform.

SymptomsWhen importing WSDL in Siebel Tools, the following error was generated:

Field 'Comments' in the integration component 'Repository Integration Component' contains value '(long line of comments)', which is longer than allowed length of 255 characters.(SBL-EAI-13011)

CauseThe Documentation data in a WSDL file or included XSD files is exceeding the Comments field in the Siebel Database Column which is limited by 255 chars.

SolutionIn order to avoid this error the Documentation data from WSDL or XSD must be reduced or eliminated.

This way Siebel will be able to import the WSDL without problems.
















Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

SymptomsI am seeing following error in log file while synching appointment from Siebel to Outlook.

1. ObjMgrLog Error 1 0 2007-06-01 06:55:42 (eaiobjinst.cpp (1732)) SBL-EAI-13011: Field 'Description' in the integration component 'Action' contains value 'Discus the plan of SSSE Component installation, ESM Tool Install and other related software on Track 2 ', which is longer than allowed length
of 100 characters.

From Bookshelf I expected PIMSI to truncate the data to enable it to sync.

SolutionMessage 1For the benefit of other readers:-

The customer was seeing the following error whiel syncing appointments:

ObjMgrLog Error 1 0 2007-06-01 06:55:42 (eaiobjinst.cpp (1732)) SBL-EAI-13011: Field 'Description' in the integration component 'Action' contains value 'Discus the plan of SSSE Component installation, ESM Tool Install and other related software on Track 2 ', which is longer than allowed length
of 100 characters.

It was determined that in Administration – PIM Server Integration> Siebel Domains, for the Siebel Calendar domain, the field Description had a length of 150. Once this was changed to 100 and the server restarted, SSSE truncated the description to 100 characters and EAI did not fail.

On the Action business component the description field has a length of 100, although the underlying database field has a length of 150. When the sync fields button is used the length was set to 150. This caused SSSE to present description with up to 150 characters, which fails the BC limit of 100. Changing the domain field length causes SSSE to truncate the description to a maximum of 100 characters which meets the BC limit.

Siebel Technical Support







Applies to: Siebel CRM - Version: 8.0.0.3 SIA [20416] - Release: V8

Information in this document applies to any platform.

Goal
When customer was trying to import a state model XML file into their application they were getting the following error message:


"Field 'Node Name' in the integration component 'Position' contains value 'SH CS,FeedbackMgmtFeedbackMgmt,Fulfillment&Selfcare Executive()', which is longer than allowed length of 50 characters.(SBL-EAI-13011)"

After investigation, they found that Siebel is updating ‘Node Name’ Filed of Position BC, which is a calculated field and is the concatenation of ‘Name’ and ‘Full Name’ with the ‘Text Length’ property is 50.

‘Name’ filed contains Position Name and this filed also has the ‘Text Length’ property set to 50.

Some of the positions used by the customer are of 49 and 50 Character length. When ‘Name’ and ‘Full Name’ are concatenated, text length of ‘Node Name’ goes beyond 50 and the import is getting failed.

So, they would like to know the following:

1. Can the ‘Text Length’ property of ‘Node Name’ filed be increased to 100 as they have a text length constraint on ‘Name’ Field.

2. Can the ‘Text Length’ property can be left blank for 'Node Name' as it is a calculated field?

SolutionDuring research found a Change Request related to this issue in both 7.8 and 8.0 as follows:

"12-RHY205 - Deploy session file for State Model causes an error when importing it."

As per this CR, the workaround to resolve this issue is, increase "Length" and "External Length" of the field "Node Name" in the integration component "Position".

This resolved the customer's problem.


Additionally, you may have to change the length in related integration objects.

TOOLS Changes for Quotes:
Integration Object: "SIS OM Quote"
Integration Component: "XA" (External Name Context=MACD Quote Item XA)
Component Field: "Value"
set Length=250
set External Length=250

Component Field: "Previous Value"
set Length=250
set External Length=250

תגובות

פוסטים פופולריים מהבלוג הזה

FINS Data Transfer Utilities

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Profile Attributes and Open UI