SBL-SVC-00253





Applies to:


Siebel Sales Enterprise - Version: 8.0.0.4 [20417] to 8.1 [21039] - Release: V8 to V8
Information in this document applies to any platform.



Goal


When creating a deployment filter using PDQ for LOV it is created with a "dot" that cannot be validated correctly.

By
removing the "dot" from the deployment filter, the filter validates
works fine. However, no rows are returned in the deployment file.

Also,  as soon as you remove the dot from the filter the PDQ disappears and its necessary to identify how ADM works with LOVs.





Solution



PDQ retrieved from application UI is:

[.Description] LIKE "LOV*" AND [.Type] LIKE "FIN_ACCOUNT_STATUS*"

Click on Validate button under Deployment Filter, get this error:

[1] The Filter 'Data Filter' is invalid. Please review the filter syntax and/or Field name.(SBL-SVC-00253)
[2]
Information about integration component "not found. Check query
specification and output integration object definition.(SBL-EAI-04176)

Remove the "." from the above, so it becomes:
[Description] LIKE "LOV*" AND [Type] LIKE "FIN_ACCOUNT_STATUS*"

Click
on Validate button under Deployment Filter, no more error but got this
message which can't be used as a filter because it retrieves 0 row:

The
Deployment filter(s) for "LOV" returns no rows and will not allow any
data to be deployed to the target system. Please revise the Deployment
Filter.(SBL-SVC-00254)

Description and Type are valid fields,
they are validated against "List Of Values Parent (UDA)" integration
component of "UDA List Of Values" integration object, which is the
primary business component of the IO. 

For the Deployment filter
to work correctly to return the equivalent results as the application
UI, it has to be modified to be as the following:

[List Of Values Child (UDA).Description] LIKE "LOV*" AND [Value] LIKE "FIN_ACCOUNT_STATUS*"

or

[List Of Values Child (UDA).Description] = 'LOV' AND [Value] = 'FIN_ACCOUNT_STATUS'

The Documentation Enhancement Request Bug# 10557771 has been entered to document the above in Siebel Application Deployment Manager Guide.








Applies to:


Siebel eCommunications - Version: 8.1.1.1 SIA [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.



Goal



Unable to created ADM project for PDQ's. The following error is encountered when using the deployment filter [Name]='xyz':



[1] The Filter 'Data Filter' is invalid. Please review the filter syntax and/or Field name.(SBL-SVC-00253)

[2] Information about integration component field 'Name' not found.
 Check query specification and fields defined for integration component
'Query List' (SBL-EAI-04177)



How can we resolve this problem?



Solution



The deployment filter is wrong. The integration component "Query
List" does not have a "Name" field. The field is called "Description".
Please change your deployment filter as follows to resolve the error
message:



[Description]='xyz'

תגובות

הוסף רשומת תגובה

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

FINS Data Transfer Utilities

תמונה
The best thing while working on siebel is you are never short of options. Recently we had requirement of updating a Service request from contact. Finally we did that using "EAI Siebel Adapter" business service. However during that time i came across another business service "FINS Data Transfer Utilities" popularly known as DTU business service. As i was not having prior knowledge of it going by the rule of not learning swimming lessons while drowning i decided not to go for it. Lately i have tried to explore this service and trust me it can do wonders. Here is a sample example update of Service Request from contact. We need to follow below steps in order to understand strength of this business service. 1 - Navigate to Site Map. Go to Administration - Application -> Data Map Administration tab. Create a new Record with following options: Name: Service Request Test Source Business Object: Contact Destination Business Object: Service Request Here the source business
המשך לקרוא

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

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima
המשך לקרוא

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of
המשך לקרוא