When the order is submitted, the total of the order’s price overrides and manual adjustments can be verified against a preset appeasement limit. If the appeasement surpasses the limit, an approval is required to continue the order submission.

The approval system for Commerce Service Center is based on the ATG platform approval process, and provides the process for submitting new orders that have appeasement discounts. The system consists of processes that determine:

For detailed information on the ATG platform approval process, refer to the ATG Commerce Programming Guide.

The Commerce Service Center approval system generates instances of atg.commerce.csr.approvals.
class to create an Order Approval object that is verified by the /atg/commerce/custsvc/
, which is the ApprovalHandler that processes order approvals. The pipeline CheckIfOrderApprovalRequired processor calls into the ApprovalHandler to determine if the approval is required.

The atg.commerce.csr.approvals.ApprovalsManager class calls other classes that create new approval objects and repository items, determine if an approval is required, save or load approval objects to or from their corresponding repository items, query the approvals repository and approve or reject an approval item. The ApprovalManager also maintains the state of the approval, which can be PENDING, APPROVED, or REJECTED. The ApprovalsManager uses the ApprovalType property of the Approval object to determine which ApprovalHandler to use. The ApprovalHandler determines if approval is required. If approval is required, the object will be saved in the approvals repository. Refer to the Commerce Service Center Order Approval Tables for information on the repository files.

Agent access to the approvals process is granted through the cmcApprovals access right, which is incorporated into the CSR-Manager role. For additional information on access rights, refer to Setting Up Internal Access Control.

The OrderApprovalHandler checks to see if the agent placing the order does not require approval by checking that they have the cmcApprovals access right. Then the handler checks that an appeasement limit exists by first checking the agent’s appeasement for the currency in question and then checking the default appeasement limit for the currency in question. Finally the handler totals the price overrides and manual adjustments and compares them with the appeasement limit.

After the order has been sent through the approval process, an e-mail is generated using the e-mail address associated with the approval record and e-mail templates OrderApprovalAcceptedTemplate and OrderApprovalRejectedTemplate. The sendConfirmationEmailmethod of CSRAgentTools creates the e-mail. If there is no e-mail address associated with the approval record, e-mail will not be sent.

Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices