31) Tell me some report names and their table names in GL, AP, AR, and PO?
1) ra_customer_trx_all
customer_trx_id
trx_number (invoice no, debit memo no, credit memo no)
cust_trx_type_id
2) ra_customer_lines_all (details of invoice)
cutomer_trx_id
3) ar_payment_schdules_all
check_id
This table stores all transactions except adjustments and miscellaneous cash receipts. Oracle Receivables updates this table when activity occurs against an invoice, debit memo, chargeback, credit memo, on account credit, or receipt.
4) ra_cust_trx_types_all (invoice types)
cust_trx_type_id
5) ra_batches_all
Batch_id
This table stores information about each receipt batch that you create in
Oracle Receivables. Each row includes information about a specific batch such as batch source, status, batch type, control count, and control amount
6) ra_receivable_application_all
7) ra_adjustments_all
This table stores information about your invoice adjustments. Each row includes general information about the adjustment you are making such as activity name, amount, accounting information, reason, and type of adjustment. You need one row for each adjustment you are making to an invoice.
8) ra_cash_receiots_all
Cash_receipt_id
This table stores one record for each receipt that you enter. Oracle Receivables creates records concurrently in the AR_CASH_RECEIPT_HISTORY_ALL, AR_PAYMENT_SCHEDULES_ALL, and AR_RECEIVABLE_APPLICATIONS tables for invoice–related receipts.
1) ap_invoice_all
invoice_amount, base_amount, payment_status_flag(‘y’ –fully paid
‘n’—unpaid
‘p’ –partially paid)
2) ap_invoice_payments_all
invoice_id,
3) ap_invoice_distibutions_All
amount, base_amount, dist_code_combination_id, line_type_lookup_code
4) ap_payment_schdules
payment_status_flag(“ ‘’’’’”)
5) ap_payment_dustributions_all
6) ap_checks_all
check_id,
AP_CHECKS_ALL stores information about payments issued to suppliers or refunds received from suppliers. You need one row for each payment you issue to a supplier or refund received from a supplier. Your Oracle Payables application uses this information to record payments you make to suppliers or refunds you receive from suppliers.
7) ap_accounting_events_all
8) ap_bank_accounts_all
AP_BANK_ACCOUNTS_ALL contains information about your bank accounts. You need one row for each bank account you define. Each bank account must be affiliated with one bank branch. When you initiate an automatic payment batch, enter a manual check, or create a Quick payment, you can select a bank account that you define in this table.
9) ap_bank_accounts_uses_all
AP_BANK_ACCOUNT_USES_ALL stores information for the internal and external bank accounts you define in Oracle Payables and Oracle
Receivables applications.
1) po_vendors
2) po_vendors_sites_all
3) po_headers_all
po_header_id
4) po_lines_all
po_line_id
5) po_line_locations_All
6) po_distributions_all
po_distribution_id,
1) Gl_code_combinations
GL_CODE_COMBINATIONS stores valid account combinations for each Accounting Flexfield structure within your Oracle General Ledger application. Associated with each account are certain codes and flags, including whether the account is enabled, whether detail posting or detail budgeting is allowed, and others.
2) Gl_je_batches.
GL_JE_BATCHES stores journal entry batches.
3) Gl_je_headers
GL_JE_HEADERS stores journal entries. There is a one–to–many relationship between journal entry batches and journal entries. Each row in this table includes the associated batch ID, the journal entry name and description, and other information about the journal entry. This table corresponds to the Journals window of the Enter Journals form. STATUS is ’U’ for unposted, ’P’ for posted. Other statuses indicate that an error condition was found. A complete list is below.
4) Gl_je_lines.
GL_JE_LINES stores the journal entry lines that you enter in the Enter Journals form. There is a one–to–many relationship between journal entries and journal entry lines. Each row in this table stores the associated journal entry header ID, the line number, the associated code combination ID, and the debits or credits associated with the journal line. STATUS is ’U’ for unposted or ’P’ for posted
5) Gl_set of books
GL_SETS_OF_BOOKS stores information about the sets of books you define in your Oracle General Ledger application. Each row includes the set of books name, description, functional currency, and other information. This table corresponds to the Set of Books form.
6) Gl_periods
GL_PERIODS stores information about the accounting periods you define using the Accounting Calendar form. Each row includes the start date and end date of the period, the period type, the fiscal year, the period number, and other information. There is a one–to–many relationship between a row in the GL_PERIOD_SETS table and rows in this table.
1) OPEN-DEBIT MEMO REPORT?
This report shows all the open-debit memo transactions, based on customer number and dates.
Columns :- type, customer_no, trx_no, amt_due, remaining.
Parameter :- type, customer, from_date, to_date.
2) GENERATING POSITIVE PAY FILE FOR BANK REPORT?
Basically this report generates a flat file of all the payments in order to send in to the bank.
3) UPDATE POSITIVEPAY CHECKS REPORT?
This report which updates the data into the (AP) account payables system from the plot file, the file which is sent by bank
4) UPDATE POSITIVEPAY OUT STANDING CHECKS?
This report which shows the out standing checks
5) CUSTOMER PAYMENT DETAILS REPORT?
Which shows each customer original amount, amount pay and due amount based on transaction type (books, pens)
Transaction types in AR
Credit memo transaction types
Invoice, debit memo, and charge back transaction types
Commitment transaction types
Q) HOW DO YOU RECTIFY THE ERRORS IN INTERFACE TABLES?
Depending on the naming convention used, errors appear in either alphabetical order or by error code number.
31) How do u identity its name of report?
System administrator à concurrent à program à define
System administrator à concurrent à program àexecutable
32) Who information’s?
1) Created by
2) Creation date
3) Last _updated by
4) last_update_date
5) last_update_value
No comments:
Post a Comment