Viewing Processing Information for Siebel Loyalty Transactions

You can use processing information for Siebel Loyalty transactions to solve problems with the application.

You can see whether or not a transaction has succeeded or the reason it has been rejected by viewing the transaction log. The log is useful while you are setting up and testing the product. It is also useful when are responding to member inquiries regarding how many points are accrued or redeemed for a given transaction or promotion. You can also create responsibilities that make the log visible to member service representatives, so they can see which promotions applied to a transaction, how many points each promotion gave, why a transaction was rejected, and so on.

You can view the transaction processing log in the Processing Info view, which enables you to view information about the promotions processed, listed one under another in a single text field.

To view the processing status of a transaction

1. Navigate to the Loyalty Transactions screen.

2. In the Transactions list, identify the transaction whose result you want to view and click the hyperlink in its Transaction Id field.

3. Click the Processing Info view tab. This view has the following fields:

   • Processed Date. The day on which the transaction was processed.

   • Transaction Status and Processing Substatus. These fields have the possible values described in the following table.

     Note: The Transaction Status field is in the Transaction form applet. The other fields are in the lower applet. You can display this information for both accrual items and redemption items.

   • Processing Error Info. This field has an error message on its first line. The rest of the information is context information that tells you when the error occurred; this information is available only if the error occurred in the context of an action or criterion. This field can contain generic or Loyalty-specific error messages. The Loyalty-specific error messages are described in Troubleshooting Siebel Loyalty Using Processing Information.

   • Promotions Processed. This field has information about which promotions were considered for the transaction and what each promotion resulted in. The information is available only if the transaction was processed successfully. First the promotions that qualified are listed with information about the actions being applied. Then the promotions that did not qualify are listed; promotions that did not qualify for the same reasons are grouped together.

Transaction Status	Processing Substatus	Description
Processed	Success	The transaction was processed successfully and some promotions qualified for it.
Processed	No Promotions Qualified	The transaction was processed without any errors, but there were no promotions that qualified. This status is not necessarily an error condition, but it might point to some incorrect configuration like inactive promotions.
Rejected - Engine	Insufficient Member Balance	The redemption transaction attempted to redeem points from the member when the member did not have a sufficient point balance.
Rejected - Engine	Insufficient Point Blocks	The accrual transaction attempted to accrue points for a member when there were not sufficient points in the partner point blocks. This status means that the promotion has run out of points and either needs to be made inactive or the partner needs to buy more point blocks.
Rejected - Engine	Program Inactive	The Program to which the transaction belongs is inactive and hence not loaded in the cache.
Rejected - Engine	Attribute Definition Inactive	The attribute definition that the criterion or action is looking for is not available in the context of the transaction being processed.
Rejected - Engine	Error	There was a generic error during transaction processing that is not specific to the Siebel Loyalty Engine. This error can happen when there is some problem in the Siebel runtime repository such as a field on the business component is not properly configured and the Siebel Loyalty Engine attempts to use that field.