Search This Blog

SBL-DAT-00127: Required out argument '%1' not supplied for '%2' method in Business Service '%3'

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4

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

Symptoms

SBL-DAT-00127

Dear support,

We have an issue in a workflow based on the BO Action.

We would like to use the method GetServiceRegionId in the Business Service FS Service Region. Indeed, we would like to get the Service Region of a Postal Code.

So in the BS of the Workflow, the input is defined as following:
Input argument = Zip Code
Type = Business Component
Business Component Name = Action
Business Component Field = Primary Postal Code

The output is defined as following
Property Name = Service Region Id
Type = Output Argument
Output Argument = Service Region Id

So we have also the Service Region Id Process Property in order to contain the value.

Our Primary Postal Code is not empty but the call of the BS leads to an error. I attach you the log generated.

We try this workflow in simulation in Tools while connected in sadmin.

What can be the problem of this standard Business Service? The step that correspond to the BS call has yet always worked properly but since today, it does not work anymore and we do not understand why.

Thanks for your help and regards.

Vincent

Solution

Message 1

For the benefit of other readers, the customer uses method 'GetServiceRegionId' from Business Service 'FS Service Region' and received error below even if the parameters were correctly set.

Require out argument 'Service Region Id' not supplied for 'GetServiceRegionId' method in Business Service 'FS Service Region'(SBL-DAT-00127).

This was due to the license key used. The key for Scheduling option was temporary and expired.

On the other hand, change request #12-SGYDXI was created to have this BS documented.

No comments:

Post a Comment