Siebel Loyalty Administration Guide > Getting Started with Siebel Loyalty >

Viewing the Processing Status for Loyalty Transactions

You can see if a transaction has succeeded or the reason it has been rejected by using the Processing Info view. This is useful while you are setting up and testing the product. You can also create responsibilities that expose this view to member service representatives, so they can see why transactions were rejected by the application.

To view the result of a loyalty transaction

1. Navigate to the Transactions screen.
2. In the Transactions list, select the transaction whose result you want to view.
3. Click the Processing Info view tab.

   The values in the Status field of the Transaction record and Processing Substatus field of the Processing Info record specify the result of the transaction, as described in the following table.

   Status	Processing Substatus	Comments
   Processed	Success	The transaction was processed successfully and qualified for some promotions.
   Processed	No Promotions Qualified	The transaction was processed successfully, but it did not qualify for any promotions.
   Rejected - Engine	Insufficient Member Balance	The redemption transaction was rejected because the member did not have a large enough point balance.
   Rejected - Engine	Insufficient Point Blocks	The accrual transaction was rejected because there were not enough points in the partner point blocks.
   Rejected - Engine	Program Inactive	The transaction was rejected because the program to which the member belongs is inactive.
   Rejected - Engine	Attribute Definition Inactive	The transaction was rejected because it attempted to use a promotion whose criteria or action use an attribute definition that is not available for this transaction.
   Rejected - Engine	Error	The transaction was rejected because of a generic error that is not specific to Siebel Loyalty. For example, a field of the business component required for the transaction may not have been properly configured. This situation may occur when the customer has deployed a new SRF.