SIEBEL ERROR CODES: SBL-DAT-00276: No association list is available in this applet.

Applies to:

Siebel Tools - Version: 7.5.3.3 SIA [16172] - Release: V7
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172] PTG Fin Svcs
Database: IBM DB2/390 V7
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: IBM zOS

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

""Checked for Relevance on 19-Jan-2010""

Symptoms

We are implementing (via eScript) a script that associates internal products (BC: Internal Product) to a campaign (BC: campaign) and when we run the GetAssocBusComp() instruction it gives the following error:

No association list is available in this applet.(SBL-DAT-00276)

We give here the function code:

function AssociateProductToCampaign(CampaignId, ProductId)
{
    var CampaignBO = TheApplication().GetBusObject('Campaign');
    var CampaignBC = CampaignBO.GetBusComp('Campaign');
    var ProductsBC = CampaignBO.GetBusComp('Internal Product');

    with (CampaignBC)
    {
        SetViewMode (SalesRepView);
        ActivateField('Product');
        ClearToQuery();
        SetSearchExpr("[Id] = '" + CampaignId + "'");
        ExecuteQuery(ForwardOnly);
        var IsRecord = FirstRecord();
    }

    if (IsRecord) {
        var oMvgBC = CampaignBC.GetMVGBusComp("Product");
        var oAssocBC = oMvgBC.GetAssocBusComp();

        with (oAssocBC)
        {
            SetSearchExpr("[Id] = '" + ProductId + "'");
            ExecuteQuery(ForwardOnly)
            if (FirstRecord)
                Associate(NewBefore);
        }
        oAssocBC = null
    }
    else{
        // erro: não encontrou a campanha em questão!!!
    }

    CampaignBC = null;
    ProductsBC = null;
    CampaignBO = null;
}

Cause

The cause of this error is the 'No Update' property of the standard 'Campaign' BC that is set to TRUE. Indeed if we change this property to FALSE, for testing purpose only, the error does not occur.

Bug 12-4LYMY3 has previously been logged asking for a better error message.

Please note that in standard Siebel application the campaigns are updateable only in the "Campaign Administration" screen. Indeed in this screen the views have their 'Admin Mode Flag' property set to TRUE and the 'No Update' BC property is ignored therefore.

Solution

The solution for the customer was to use the SetAdminMode method in order to replicate the behavior of the 'Admin Mode Flag' view property. The issue was resolved once the line of code below:

SetViewMode (SalesRepView);

was replaced by the following:

InvokeMethod("SetAdminMode", "TRUE");

For further information on the SetAdminMode method please refer to the Bookshelf:

Siebel Object Interfaces Reference
Interfaces Reference
Business Component Methods
InvokeMethod Methods
SetAdminMode

Additional information:
====
The following lines are not needed:

var ProductsBC = CampaignBO.GetBusComp('Internal Product');
...
ProductsBC = null;

However it is needed to destroy the instance of the MVG BC (oMvgBC = null)

References

BUG:12-4LYMY3 - VB CODE WHICH TRIES TO ASSOCIATE A NO UPDATE BC PRODUCES A MISSLEADING ERROR

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-DAT-00276, SBL-DAT-00402

We are trying to use the "Create Activity" button in List Management. We create our own template but when we select our template from the list and execute we get the following error: "No association list is available in this applet.(SBL-DAT-00276)".

Solution

Message 1

For the benefit of other readers,

Problem,

Login into Siebel Financial Services and navigate to "List Management" Screen and click on the "Create Activity" button in List Management.

Created a new custom template, which maps “List Mgmt List Member” as source BC, and "Action" as destination BC. In the data maps, map a single value field from source BC to a multivalue field in destination BC.

But when we select our template from the list and execute we get the following error: "No association list is available in this applet. (SBL-DAT-00276)".

Change Request (CR) 12-1F2F46O has been logged to address this product defect

Resolution

Quick Fix 12-1F2F477 has been provided to customer to resolve this behavior, In case you encountered this behavior then you can obtain Quick Fix for 7.7.2.6, by logging a new SR in Request Software Shipment Area with reference CR 12-1F2F46O/FR 12-1F2F477

Muneer Uddin
Oracle Technical Support

Keywords: SBL-DAT-00276,”No association list is available in this applet”

Applies to:

Siebel Email Response - Version: 7.7.2 [18325] and later [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms

Comments
--------
=== ODM Issue Clarification ===

I understand you are receiving the error message 'SBL-DAT-00276: No association list is available in this applet' in QA environment while creating the outbound activity related to the send acknowledgement step from the Email Response workflow. However you have noticed this same functionality is working fine in Dev environment with the same SRF.

Cause

Comments
--------
=== ODM Cause Determination ===

In case the same SRF has been deployed in the QA and Dev environment this issue could be related to settings like Scripting, workflows, State Model etc.

Comments
--------
=== ODM Cause Justification ===

Settings like Scripting, workflows, State Model could be affecting the CommOutboundMgr component while generating the outbound activity.

Solution

This issue has been caused because of the State Model settings. In the QA environment there were State Models configured for the Action BC, while in the Development environment there were none..

The State Model restricted updates when the status was set to Done in the Action BC. After unchecking the 'No Update' flag everything started working fine in QA environment.

This error happened when it was unable to save the base record while associating the Contact record to the Email - Outbound activity. In this case it was unable to save the Action record as it violated the State Model rules, when trying to associate a Contact.

References

BUG:12-QFXM0I - USE OF SERVICE REQUEST CONTACT RECIPIENT GROUP CAUSES OUTBOUND COMMUNICATIONS MANAGER TO HANG

Applies to:

Siebel Email Response - Version: 7.8.2.5 [19227] - Release: V7
Siebel eCommunications eMail Response
Sun Solaris SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.5 [19227]
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

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

Symptoms

We are unable to currently be able to get the CreateRequest Method on Outbound Communications Manager business service to create the outbound email activity record. We have set up a workflow to call the method (was done for version 7.5.3 with success). It uses a template that has the Create Activity flag checked.

The outbound email email gets sent without any issue, but the corresponding activity that was supposed to be created errors out. we get the "2007-05-01 18:13:22 1-1-01XRNW7: Sent 0 out of 0 messages (0.000) seconds. Value too long for field '<?>' (maximum size <?>).(SBL-DAT-00235) No association list is available in this applet.(SBL-DAT-00276)".

We've compiled onto the server srf, both the vanilla Service Request and Action buscomps to see if our custom buscomps were the issue. however, this caused on difference... the email is sent through the business service, but for some reason the server task errors out on the activity creation. i have attached the log file we get. Please help us... we've tried every scenario to fix this and cannot understand what the error message means. This workflow was working without issue on our previous 7.5.3 version.

Cause

This is a Product Defect, which has logged a Change Request 12-QFXM0I, to address it.

Solution

Message 1

Behavior:

Customer was using 7.8.2.5 [19227] SIA.
Customer had a custom workflow using the business service Outbound Communication Manager, method CreateRequest with the standard Recipient Group = Service Request Contact.

After running the workflow the business service failed with the message
Sent 0 out of 0 messages (0.000) seconds. Field 'Work Phone' does not exist in definition for business component 'Contact Relationship'.

This behavior was also reproducible in house.

Resolution:

This issue had been found in previous versions (7.7.1 [18306]). The change request(12-QFXM0I) was not implemented.

A workaround was provided.
for e.g., introduce a "Calculated" field (which PreDefaults the same value as "Work Phone #")

Add a calculated field 'Work Phone' and predefault it to receive the same value as the 'Work Phone #'.
Add in the 'Comm Contact' and 'Contact Relationship' BCs.

It was found that the repository from 7.5 to 7.7 had a change in the field â€˜Work Phoneâ€™ to â€˜Work Phone #â€™ from the business component Contact Relationship.

Keywords: CreateRequest, Service Request Contact, Work Phone, Work Phone #, Contact Relationship

Applies to:

Siebel Email Response - Version: 7.7.2 [18325] and later [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms

Cause

Solution

References

BUG:12-QFXM0I - USE OF SERVICE REQUEST CONTACT RECIPIENT GROUP CAUSES OUTBOUND COMMUNICATIONS MANAGER TO HANG

Applies to:

Symptoms

Cause

This is a Product Defect, which has logged a Change Request 12-QFXM0I, to address it.

SIEBEL ERROR CODES

Search This Blog

SBL-DAT-00276: No association list is available in this applet.

Applies to:

Symptoms

Cause

Solution

References

Applies to:

Symptoms

Solution

Message 1

Applies to:

Symptoms

Cause

Solution

References

Applies to:

Symptoms

Cause

Solution

Message 1

Applies to:

Symptoms

Cause

Solution

References

Applies to:

Symptoms

Cause

Solution

Message 1

No comments:

Post a Comment