Receipt of payments through ION API

If you use a third-party retail management system or point of sale (POS) system, you can integrate your system with Distribution SX.e to manage orders, payments, and refunds. Transactions are recorded in Distribution SX.e, and provide you with order management, transaction balancing, general ledger updating, and inventory management.

You can take an order in your retail management system or POS system. The header, line, and tendering data is sent through the ION API call, sxapiOEFullOrderMntV6, which creates an order in Distribution SX.e. The call sends back the order number, totals, and inventory information to your retail management system or POS system. The call enables your customer to use multiple payment types on one order, such as cash, check, and credit card.

The ION API call, sxapiOEFullOrderMntV6, permits a Counter Sale (CS). CS orders are automatically set to Shipped stage, but can be maintained in Sales Order Entry. If the order is created from a CS, and a backorder is required, the backorder is converted to a Stock Order (SO). If a counter sale is over-tendered, that order will not invoice and must be maintained manually to reverse tendering.

The ION API call, sxapiOEFullOrderMntV6, uses a journal logic that permits one journal per day for each post date. In the GL Journal Inquiry-Journal view, the Batch Name is displayed as oeetapi. A new Set # is assigned for each order transaction created through the ION API call, enabling you to view or group payments by order in Sales Order Inquiry and GL Journal Inquiry.

This feature also uses the ION API call, sxapiOEOrderChange, to handle changes in ordered lines, payments, additional payments, returns, and refunds. Your customer can make multiple payments on an order, make a payment to an existing order, and receive a refund. A miscellaneous credit is only created at invoicing if you do not tender the refund. That is, the customer made a return for more than was purchased and was not refunded the money at the time of the return.

If your workflow enables customers to order online and pick up products at a nearby store, your retail management system or POS interface you can specify a disposition recognized by Distribution SX.e, such as Tag and Hold or Will Call. A disposition is only required to keep the order from being picked and shipped within Distribution SX.e if the order is a Stock Order. If the order is a Counter Sale, no disposition is required.

If your customer's credit card payments are to be handled and authorized by the retail management system or POS system, then you must specify certain settings:

First, you should clear any credit card settings for a processor from the typical setup functions; for example, SA Credit Card Processor Setup, SA Table Code Value Setup, and Customer Credit Card Setup. However, we do recommend that you set up a SA Table Code Value Setup-Payment Type with a prefix indicating what system processed the payment, such as, rms-CreditCard.
Next, ensure the option, Payment Type is a Credit Card, is cleared. Be aware that, with this kind of implementation, the credit card number is masked by the retail management system or POS system, and no credit card history details are available in Distribution SX.e.
For this kind of implementation, we also recommend that you set up a SA Table Code Value Setup-Payment Type with a prefix indicating other accepted payment types: rms-Cash, rms-Check. These Payment Description values are displayed in the Sales Order Inquiry grid.

If you implement this feature, we recommend you monitor Electronic Transaction Control Center (ETCC) frequently throughout the day. Ensure that any exceptions or errors that result from sales order creation are addressed immediately, especially if your customer is in the store. Monitor ETCC for these messages:

Warning: Invalid OE Type - Valid Types are SO, FO, QU, CS, CR, BL, DO, RM (8756)
Payment Not Applied to order; Not Allowed for a {QU or BL} Order
If an invalid payment type is used, the message, Invalid pay type received from input file, is displayed and the order is placed on e-Hold.

You must ensure ION API calls are configured correctly to integrate with your retail management system or POS. You can with your Infor Consulting Services representative or third-party application provider to modify any external applications that send or receive the updated API calls.

See the Infor CloudSuite Distribution Configuration Guide or Infor Distribution SX.e Configuration Guide for Infor Operating Service for information about configuring the ION API.