Last updated on AUGUST 01, 2017
Applies to:Siebel Loyalty Engine - Version 220.127.116.11 [IP2013] and later
Information in this document applies to any platform.
When processing a Redemption Transaction, it fails and the reported error is "The value entered in field Accrual Item Id of buscomp LOY Concurrency Redemption Item does not match any value in the bounded pick list LOY PickList Accrualed Value".
The log showed that it had hit the system limit of 10,000 records while reading the "LOY Redemption Accrual Item" business component:
ObjMgrSqlCursorLog Trace 5 0000000253e12dfc:0 2014-08-06 10:32:59 SQL Cursor with ID 267F2C28 Buscomp: LOY Redemption Accrual Item, Forward Only: 0, Fetch Rows: 10000, Fetch All Time: 2.598 seconds.
ObjMgrSqlCursorLog Close 5 0000000253e12dfc:0 2014-08-06 10:32:59 End: Close Sql Cursor at 267f2c28
ObjMgrBusCompLog Error 1 0000000253e12dfc:0 2014-08-06 10:32:59 There were more rows than could be returned. Please refine your query to bring back fewer rows
ObjMgrBusCompLog Warning 2 0000000253e12dfc:0 2014-08-06 10:32:59 (sqlobj.cpp (39602)) SBL-DAT-00500: There were more rows than could be returned. Please refine your query to bring back fewer rows
The "Accrual Item Id" on "LOY Concurrency Redemption Item" refers to the picklist "LOY PickList Accrualed Value".
Here the member had over 10,000 accruals.
The Maximum Cursor Size property on the "LOY Redemption Accrual Item" was used to try to enable more than 10,000 records to be read. However this had no affect.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms