The Orders pricing and payment authorization happen in Oracle Commerce Cloud. The payment attributes are not mapped to any attribute on Order Management Cloud because the OMS does not need the payment information for fulfillment. For Orders which have a B2B flavor, the Order does have a Purchase Order number which are passed on to the OMS. The scope of this integration is restricted to the Order Management Cloud. There are processes beyond Order Fulfillment in Fusion Suite. The Order Management Cloud has integration with Account Receivables post fulfillment which is within fusion suite and is outside the scope of this integration.

Commerce Cloud currently expects the payment capture information to be updated by an external system. This assumption holds true for this integration as well. The Order would be Payment Authorized by Commerce Cloud with the payment gateways before the order is sent to Order Management for fulfillment. It is expected that the customer verifies if the order is ready to be shipped on Order Management and Captures the money against the authorization. This can be done by Integrating with the payment gateways and update the status back to Commerce as Captured/Settled. The payment group status would have to be updated once the transaction is captured on Commerce repository. This status unavailability hinders the return processing against an order.


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