Announcing new and updated Documentation for Oracle Cruise, Hotels, Food & Beverage, and Retail solutions

Announcing Key Functional White Papers for SIM and ReIM

Randy Kapelke
Director, Global Content

Oracle Retail has published two new documents on My Oracle Support (https://support.oracle.com)  that provide partners and retailers with deeper functional information about two products: Oracle Retail Store Inventory Management (SIM) and Oracle Retail Invoice Matching.

Oracle Retail Store Inventory Management Item Configuration White Paper (Doc ID 1507221.1)

There is functionality within the Store Inventory Management system
related to item configuration that spans across multiple concepts that apply to the application as a whole rather than
to a specific area. This white paper covers numerous topics
around item configuration including:

  • Item Transaction Levels
  • Item Long Description
  • Pack Size
  • Standard Unit of Measure
  • Standard Unit of Measure Conversion
  • Pack Items
  • Simple Pack Conversion Items (Notional Packs)
  • Ranging Items
  • Item Status
  • Non-Sellable Items
  • Type-2 Item Recognition
  • UPC-E Barcodes
  • Non-Inventory Items
  • Consignment and Concession Items
  • Quick Response Codes

Oracle Retail Invoice Matching Financial Transactions (Doc ID 1500209.1)

This document explains the financial transactions that are posted by Oracle Retail Invoice Matching (ReIM). The scope of the document is limited to ReIM transactions only, and does not explain Retail Merchandising System (RMS), Finance, or Account Receivable transactions.

ReIM follows the double-entry accounting standard, which works by recording the debit and credit of each financial transaction belonging to each party involved. Each transaction means a profit to one account (debit) and a loss to another account (credit).

Full invoice match processing is completed in ReIM with payment recommendations communicated to Oracle Accounts Payable. ReIM matches merchandise orders and receipts against merchandise invoices, performing automated and manual matching, as well as discrepancy-resolution processing. Matched invoices are posted to interface staging tables specifying the amount and date to pay, vendor, site ID, General Ledger Chart of Accounts (GL CoA) information, and payment terms. Other payables documents, including debit memos, credit memos and credit notes are also interfaced to Accounts Payable through the ReIM staging tables (IM_AP_STAGE_HEAD and IM_AP_STAGE_DETAIL). For information about how ReIM engages in this processing, see the latest Oracle Retail Invoice Matching Operations Guide. Certain ReIM transactions are not interfaced to Oracle Payables, but instead are interfaced to Oracle General Ledger through the IM_FINANCIAL_STAGE table. When analyzing transactions posted through the staging tables, retailers should note the transaction type, Standard/Credit, as well as the sign in the amount field. Technically, a negative sign on a credit transaction changes the transaction to a debit entry, and vice versa. This document is concerned about the financial meaning of the transactions, and will avoid a discussion of negative numbers in T-charts.





Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.