1. Support Desk.
  2. Reports
  3. ERP Armor: Reports for ERP Cloud (OTBI)

What is Query 32: Receivables Transaction Types?

The table(s) covered in this query are described by Oracle as follows:
Each row includes AutoAccounting information as well as standard defaults for the transaction that results. The POST_TO_GL column stores Y or N to indicate if this transaction can post to your General Ledger. The ACCOUNTING_AFFECT_FLAG column stores Y or N to indicate if this transaction can update your open receivables balances. If the ACCOUNTING_AFFECT_FLAG column is Y, the transaction will appear in aging. The TYPE column contains values: INV for Invoice, CM for Credit Memo, and DM for Debit Memo. If AutoAccounting is based on transaction type, the GL_ID_REV, GL_ID_FREIGHT, and GL_ID_REC columns store the default revenue, freight, and receivables accounts. The STATUS and CREDIT_MEMO_TYPE_ID columns are required even though they are null allowed. The primary key for this table is CUST_TRX_TYPE_ID.

Sensitive Access Risk Rule ID:

Risk Description: Drives the coding of AR transactions - revenue accounts, post to GL, open receivable (post to subledger), payment term, creation sign, etc. Could cause out of balance between subledger and GL, inappropriate revenue GL accounts, payment terms on transactions not in compliance with corporate standards. Note transition type can be 'any sign' such that invoices can be negative.

Q32 AR Transaction Types_a copy

Q32 AR Transaction Types_b copy