Can Payment System Accounts Be Associated With Inventory Locations Using Routing Rules?
(Doc ID 1446965.1)
Last updated on JUNE 04, 2021
Applies to:Oracle Payments - Version 12.1.3 and later
Information in this document applies to any platform.
The client operates similarly to a retailer and as such has 138 locations. A payment system account has been setup for testing purposes, however, I need to create a payment system account for each location. Once I create the proper payment system account for each location, how do I assign it to the proper location in OM so that credit card transactions are captured at the correct retail location?
We need to have the ability to differentiate credit card transactions by location for authorization and settlement purposes. Without this flexibility all credit card transactions will appear to FDN as if they originated from one location.
The 138 locations are actually Inventory organizations in OM. They are retail locations and use one PRIMARY merchant account, and merchant ID's that identify each location. Normally we would use Routing Rules on the Payee screen in Payments to route transactions to the required payment system account. However the Organization ID's available from the routing rule criterion LOV are "operating units" as opposed to an "inventory organizations". Furthermore the inventory organizations are not available in the "Assign Organization Units" LOV in the Payee screen (this is due to the fact that this LOV shows operating units that exists in hr_operating_units and does not shown inventory organizations that exists in hr_locations and hr_organization_units).
How can the customer route credit card transactions to a location which is an inventory organization?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document