oracle 发票剩余金额,发票余额为零， 无法结帐

系统中出现发票余额为零， 详细见附图

从资料中得到部分解释，如下，但不是很明白，请高手讲解，谢谢

ORA-ERP:发票余额为零,无法结帐

--------------------------------------------------------------------------------

来源：CSDN   发布会员：新书城收集整理   发布时间：2006-9-2   人气：54

很多时候,对发票进行过帐及核销的过程中,偶尔出现发票余额全为零的现象,其实,这是由于应收-ACCOUNTS DETAIL的数据丢失所置,要做的很简单,在下表添加一条记录就可以了

AR_PAYMENT_SCHEDULES_ALL

根据发票的customer_trx_id可以找到相关的数据.

PAYMENT_SCHEDULES_ID 从AR_PAYMENT_SCHEDULES_S 序列取.

其他相关资料:

AR_PAYMENT_SCHEDULES_ALL

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. Oracle Receivables groups different transactions by

the column CLASS. These classes include invoice (INV), debit memos

(DM), guarantees (GUAR), credit memos (CM), deposits (DEP),

chargebacks (CB), and receipts (PMT). Transaction classes determine

which columns in this table Oracle Receivables updates when a

transaction occurs, and whether a transaction relates to either the

RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALL

table. AR_PAYMENT_SCHEDULES_ALL joins to the

RA_CUSTOMER_TRX_ALL table for non–payment transaction entries

such as the creation of credit memos, debit memos, invoices,

chargebacks, or deposits. AR_PAYMENT_SCHEDULES_ALL uses the

foreign key CUSTOMER_TRX_ID to join to the

RA_CUSTOMER_TRX_ALL table for these transactions.

AR_PAYMENT_SCHEDULES_ALL joins to the

AR_CASH_RECEIPTS_ALL table for invoice–related payment

transactions using the foreign key CASH_RECEIPT_ID. When a receipt

is applied, Oracle Receivables updates AMOUNT_APPLIED, STATUS

and AMOUNT_DUE_REMAINING. STATUS changes from ’OP’ to ’CL’

for any transaction that has an AMOUNT_DUE_REMAINING value of

0. ACTUAL_DATE_CLOSED and GL_DATE_CLOSED are populated

with the date of the latest transaction. For a receipt, the amount due

remaining includes on account and unapplied amounts. Oracle

Receivables stores debit items such as invoices, debit memos,

chargebacks, deposits, and guarantees as positive numbers in the

AMOUNT_DUE_REMAINING and AMOUNT_DUE_ORIGINAL

columns. Credit items such as credit memos and receipts are stored as

negative numbers. In Release 10, receipts can be confirmed or not

confirmed as designated by the CONFIRMED_FLAG column. The sum

of the AMOUNT_DUE_REMAINING column for a customer for all

confirmed payment schedules reflects the current customer balance. If

this amount is negative, then this column indicates the credit balance

amount currently available for this customer. For invoices with split

terms, one record is created in RA_CUSTOMER_TRX_ALL and one

record is stored in AR_PAYMENT_SCHEDULES_ALL for each

installment. In AR_PAYMENT_SCHEDULES_ALL, DUE_DATE and

AMOUNT_DUE_REMAINING can differ for each installment of a split

term invoice. Each installment is differentiated by the

TERMS_SEQUENCE_NUMBER column. If you create a debit memo

reversal when you reverse a receipt, Oracle Receivables creates a new

payment schedule record for the debit memo and fills in

REVERSED_CASH_RECEIPT_ID with the CASH_RECEIPT_ID of the

receipt that was reversed. Oracle Receivables creates a new payment

schedule record when you create a chargeback in the Receipts window.

ASSOCIATED_CASH_RECEIPT_ID is the cash receipt of the payment

you entered when you created the chargeback in this window.

GL_DATE_CLOSED indicates the general ledger date on which your

transaction was closed. This column identifies which transactions

Oracle Receivables selects when it displays current and overdue debit

items in the aging reports. The aging reports also utilize the current

balances in AMOUNT_DUE_REMAINING to display outstanding

amounts for current and overdue debit items.

ACTUAL_DATE_CLOSED gives the date on which you applied a

payment or credit to an open transaction that set

AMOUNT_DUE_REMAINING to 0 for that transaction. Oracle

Receivables uses ACTUAL_DATE_CLOSED to determine which

transactions to include when you print statements. The primary key for

this table is PAYMENT_SCHEDULE_ID, which identifies the transaction

that created the row.

资料来源：http://www.newbooks.com.cn/info/52729.html