SBL-UIF-00269

APPLIES TO:

Siebel Field Service - Version 8.1.1.7 SIA [21238] and later
Information in this document applies to any platform.

SYMPTOMS

We are seeing an issue in Order Line Item action regarding Shipping.
When we are trying to ship an order line item in Shipping screen, we enter invalid serial number to ship and we get an error and shipping is not complete.
But Siebel is creating an Order Line Item action with Ship action. This should not happen.
Here are the steps to reproduce the issue:

1. create an asset, associate a serializable product.
2. create a Service order, Type = Internal Order
3. create line item for the service order, pick a serializable product.
4. set source and destination in Fulfill
5. set asset number in Line Detail (optional)
6. click on 'fill all' in Line Items to generate pick ticket
7. drill down on pick ticket > shipping
8. drill down on pick ticket detail, 1 allocated line is displayed
9. click on New, enter Qty = 1
10. In Serial Numbers, pick Asset in step 1, click on Process Shipment, get
1s error:

Asset Number "A10" is not a valid asset from source inventory "Service
Inventory".(SBL-SFS-00246)


"allocated lines" becomes blank.

11. type bogus Serial# within Serial# field, try to step down, get 2nd error:


[1]Cannot locate record within view: Fs Shipping information from View
applet: FS Order Line Item Action Assets List Applet.(SBL-UIF-00269)
[2]Cannot locate record within view:applet:.(SBL-UIF-00269)


and application can't get out of the error. Need to end process to close the
application.
12. Go to Service Order->Line Item->Line Item action and you can see 'Ship'
action is created.

CAUSE

It is identified to be a new defect in the product.

The "allocated lines" should not become blank after getting the 1st error.
And the bogus Serial# should not result in killing the application in order to end the 2nd error.
 

SOLUTION

Create the new BUG 16608115 - SHIPPING LINE ACTION IS GETTING CREATED EVEN IF THERE IS A ERROR IN SHIPPING SCR
for fixing the defect in 8.1.1.7 QF.
The patch ID: 16762436, which is for 8.1.1.7 21238 SIA QF07DD is available for download in My Oracle Support > Patches & Updates.
Just enter 16762436 for Patch Number and click on Search to find it. It is available for Windows and Linux platforms.

In addition, it is fixed in 8.1.1.11FP, it is tracked by BUG 16538808.

The patch fixes 2 problems reported in steps 10 and 11: Applet becoming blank, and Unable to edit the serial number. The step 12, "Go to Service Order->Line Item->Line Item action and you can see 'ship' action is created."
wont be fixed since this is not a bug and it is how application is designed to work.

APPLIES TO:

Siebel Tools - Version 8.1.1.3[21219] and later
Information in this document applies to any platform.
""Checked for relevance on 02-SEP-2013""

SYMPTOMS

Siebel Version: 8.1.1.3

Statement Of Issue: Error thrown when trying to select a record from Popup Applet in Clinical Protocol Site Payment Exceptions List Applet.

Steps to Reproduce:
1. Click on Centre Management screen.
2. Go to Clinical Protocol Site Payment Exceptions Detail View.
3. Click on Copy FNB button on Clinical Protocol Site Payment Exceptions List Applet
4. In the Popup Applet, try to change the current record.

Error Thrown:

SBL-UIF-00313 An error happened during restoring the context for the requested location occurring when selecting a record in Popup Applet
SBL-UIF-00269: Cannot locate record within view: Clinical Protocol Site Payment Exceptions View applet: Clinical Protocol Site Payment Exceptions List Applet. - when trying to close the popup applet.

Business Impact:
Copying FNB is a very important functionality for business users. As they copy the final negotiated budgets to few other centres.

CAUSE

The issue is caused due to wrong configuration of Popup Applet.

The popup applets are configured for Detailed records in Master detail view. For example, Account Contact view, Popup applet can have records for the contacts for given account.
Customer is trying to configure a popup applet for Master record. It is not feasible to configure in that way.

In customer environment, the parent BC is Clinical Protocol Site and the pop up applet invoked on child applet is based on Parent BC which is not accepted.

SOLUTION

Make a copy of parent BC and use this BC for Popup Applet.

1. Copy the parent BC: Clinical Protocol Site and name it as ETR Select Centres.BC
2. Use ETR Select Centres.BC as the BC for ETR Select Centres Applet.
3. Add ETR Select Centres.BC to the Clinical Protocol Site Business Object with no link.
4. Compile all the changes and retest the issue

APPLIES TO:

Siebel Call Center - Version 8.1.1.9 [23016] to 8.1.1.11 SIA [23030] [Release V8]
Information in this document applies to any platform.

SYMPTOMS

On  8.1.1.9 Fix Pack when attempting to execute F9 integrated with MS Outlook from Service Request Detail Applet and with focus on a Service Request Attachment so the attachment file automatically get populated in MS Outlook client when F9 is invoked the MS Outlook Client pop up and is bring to front, but the attachment has only part of the original size and after that when going back to Siebel Application the following error occurs.

The problem start to happen after upgrade from 8.0.0.9 to 8.1.1.9.

The user can sucessfully download and open the attachment file from Service Request Attachment List Applet, the problem only happens when using F9 integrated with MS Outlook, the issue does not happens if user uses Siebel Email Client.

The problem can NOT be reproduce when using HTTP, only when using HTTPS (SSL) for Siebel Application URL. As part of upgrade the Web Server were also moved to IIS 7.5 from previous IIS/Apache versions.

The issue can be reproduced at will with the following steps:
1. Go to Service Request detail view w/attachments applet
2. Select an attachment record
3. Click F9 integrated with MS Outlook.
4. MS Outlook client pop up, it show the attachment, but the size is not the same of the original file.
5. Going back to Siebel Application and the pop up error above appear:

[1] Cannot locate record within view: Service Request detail view w/attachments applet: Service Request Attachment List Applet. (SBL-UIF-00269)
[2] An end of file error has occurred.
Please contact your system administrator to check your application configuration if the problem persists. (SBL-DAT-00393).

CAUSE

The beahvior could be reproduced internally using IIS 7.5 with HTTPS (SSL). Using IIS 6.0 the behavior does NOT occur.

Bug 17438761 - F9 WITH OUTLOOK FROM SIEBEL ATTACHMENT FAILS WITH IIS 7.5 AND HTTPS has been opened.

The behavior could be reproduce in internal Laboratories and Oracle Engineer confirmed Bug 17438761 - F9 WITH OUTLOOK FROM SIEBEL ATTACHMENT FAILS WITH IIS 7.5 AND HTTPS
 

SOLUTION

Bug 17438761 - F9 WITH OUTLOOK FROM SIEBEL ATTACHMENT FAILS WITH IIS 7.5 AND HTTPS has been fixed in:

8.1.1.9/8.2.2.2 Quick Fix 0001125 Patch Number 17838139 for 8.1.1.9 and  Patch Number 17838140 for 8.2.2.2.

8.1.1.10/8.2.2.3 Quick Fix 0002114 Patch Number 17830147 for 8.1.1.10 and  Patch Number 17830148 for 8.2.2.3.

BUG 17832993  has been opened requesting a fix for the next 8.1.1.11/8.2.2.4 PatchSet available too.

To apply the Quick Fix:

1. Download and review the readme and pre-requisites for Patch Number above.

2. Ensure that you have taken a backup of your system before applying the recommended patch.

3. Apply the patch in a test environment.

4. Retest the issue.

5. Migrate the solution as appropriate to other environments.

APPLIES TO:

Siebel Tools - Version 8.1.1.5 SIA [21229] and later
Information in this document applies to any platform.

SYMPTOMS

On : 8.1.1.5 SIA [21229] version, Configuration - General

Error when displaying eService view

ERROR
-----------------------
Cannot locate record within view: PUB GOV Contact Case List View (eService) applet: PUB GOV Contact Case List Applet (eService).(SBL-UIF-00269)

STEPS
-----------------------
User wants to allow eService Public Sector users to submit cases.
For that, they have added to the web layout of the PUB GOV eService Account Quick Links Applet, the out of the box control LinkNewCase, linking to the PUB GOV Contact Case List View (eService) view and applet PUB GOV Contact Case List Applet (eService) (specified by control user properties).

When trying to access the view, the following error is returned:
Cannot locate record within view: PUB GOV Contact Case List View (eService) applet: PUB GOV Contact Case List Applet (eService).(SBL-UIF-00269)

CAUSE

Bug: 14090993 was logged to address this issue.

Steps to replicate the issue:

1. Siebel Tools > Applet > PUB GOV eService Account Quick Links Applet.
2. Applet Web Template > Applet Web Template Item.
3. Add a control : LinkNewCase

Name: LinkNewCase
Control: LinkNewCase
Item Identifier: 1,304

5. This will link to the PUB GOV Contact Case List View (eService) view and applet PUB GOV Contact Case List Applet (eService) (specified by control user properties).
6. Compile the object.

7. Login to Siebel Public Sector eService (cfg file: psesrv.cfg)
8. On the My Account, we can see "Submit a case" control.
9. Click on Submit a case.

Error >>

Cannot locate record within view: PUB GOV Contact Case List View (eService) applet: PUB GOV Contact Case List Applet (eService).(SBL-UIF-00269)
Error Message: SBL-UIF-00269
 

SOLUTION

Following repository fix exists for this behavior.

Object Configuration 1:

1. Navigate to the Applet object and query for the Applet “PUB GOV eService Account Quick Links Applet”.
2. Navigate to the LinkNewCase control in the Control object.
3. Expand the Control object navigate to the Control User Prop object.
4. Change the value for the Applet User Property to "PUB GOV Submit Contact Case Form Applet (eService)".
5. Change the value for the View User Property to "PUB GOV Submit Contact Case View (eService)".
6. Navigate to the ImageNewCase control in the Control object.
7. Navigate to the Control User Prop object.
8. Change the value for the Applet User Property to "PUB GOV Submit Contact Case Form Applet (eService)".
9. Change the value for the View User Property to "PUB GOV Submit Contact Case View (eService)".
10. Save the changes.

Object Configuration 2:

1. Navigate to the Applet object and query for the Applet “PUB GOV Submit Contact Case Form Applet (eService)”.
2. Uncheck the No Insert property.
3. Save the changes.

Object Configuration 3:

1. Navigate to the View object and query "PUB GOV Submit Contact Case View (eService)".
2. Change the Bus Object property to "HLS Case".
3. Navigate to the View Web Template Item child object.
4. Set Inactive Property to true for both the Applets "PUB GOV Case Blank Salutation Applet (eService)" and "PUB GOV Contact Hidden Applet (eService)".
5. Save the changes.

Compile all the three objects changes to the Siebel SRF and launch the application. Now, when the user drill-down from the Submit Case link, it will navigate to the Case view with Edit mode where user can key in the value and submit the Case.

This is a sample configuration to create a new Case from eService. Please note that you can create new objects or modify existing objects to fit your requirement.

Key Note:
The view should be based on the HLS Case object and the first applet in the view should refer to the Case Applet which captures the input from the user.
 

APPLIES TO:

Siebel CRM - Version 8.0.0.5 SIA [20420] and later
Information in this document applies to any platform.
***Checked for relevance on 09-May-2012*** 

SYMPTOMS

Customized
=======
Customer has configured parent-child views , Association applet to add child records to the parent.

When a user selects more than 10 records in the association applet and clicks OK, the records are added successfully.

However, the field values in the parent applet are now all blank. And then when the user tries to select a record in the child applet, an error like this appears:

[1] Cannot locate record within view: Contact Relationships View applet: Contact Relationship List Applet. (SBL-UIF-00269)
[2] An end of file error has occurred.


Standard
======
This particular error was produced using the vanilla Siebel SRF on the Contact > Relationships View, by clicking the New button in the Relationships applet and adding 11 contacts from the "Add Contacts" applet.

CAUSE

This is product defect.

I have tested this issue in house and got the same error.

CR 10560501 has been created as product defect to address this issue. that the error pops up based on the HTML Number of Row Displayed Property of the Applet.

SOLUTION

The issue you are facing is a Product Defect and will be addressed in future release.For the workaround for this issue is - add less then 10 records and then another record in this way this will work fine.

Or select only first 10 record in pick applet then click Ok this is working fine.

the following scripting work around has been found to work:

Added to assoc applets preinvokemethod:

if (MethodName == "AddRecord") { var oBO = TheApplication().ActiveBusObject();
var oBC_Parent = oBO.GetBusComp(TheApplication().GetService("GS General Utilities").CurrentViewMainBC());
var oBC_Child = oBO.GetBusComp(this.BusComp().Name()); var oBC_Assoc = oBC_Child.GetAssocBusComp();
var iRecord = oBC_Assoc.FirstSelected();

while (iRecord)
{
try { oBC_Assoc.Associate(NewAfter); }
catch(e) { if (Clib.strstr(e.errText, "SBL-DAT-00357") == null) { throw e; } }
finally { iRecord = oBC_Assoc.NextSelected(); } } 

oBC_Child.InvokeMethod("RefreshRecord");
oBC_Child.FirstRecord();
oBC_Assoc = null; oBC_Child = null;
oBC_Parent = null; oBO = null;
this.InvokeMethod("CloseApplet");
return (CancelOperation); }

Added to GS General Utilities BS: function CurrentViewMainBC()

{ var sMainBC = ""; var sMainApplet = ""; var globalCache = TheApplication().GetSharedGlobal("ViewMainBC" + TheApplication().ActiveViewName());
if ((globalCache != "") && (globalCache != null))
{ sMainBC = globalCache; }
else
{ var repBO = TheApplication().GetBusObject("Repository View");
var repBC = repBO.GetBusComp("Repository View"); with (repBC) { ActivateField("Name"); ActivateField("Sector0 Applet"); SetViewMode(AllView); SetSearchSpec("Name", "\"" + TheApplication().ActiveViewName() + "\"");
ExecuteQuery(ForwardOnly); if(FirstRecord())
{ sMainApplet = GetFieldValue("Sector0 Applet"); } }
repBC = null; repBO = null;
repBO = TheApplication().GetBusObject("Repository Applet");
repBC = repBO.GetBusComp("Repository Applet");
with (repBC) { ActivateField("Name");
ActivateField("Business Component");
SetViewMode(AllView);
SetSearchSpec("Name", sMainApplet);
ExecuteQuery(ForwardOnly);
if(FirstRecord()) { sMainBC = GetFieldValue("Business Component"); } }
repBC = null; repBO = null; }

TheApplication().SetSharedGlobal("ViewMainBC" + TheApplication().ActiveViewName(),sMainBC); return (sMainBC); }

Also the CR has been fixed for 8.0.0.9 Fix Pack and 8.0.0.6 [20423]QF0624.