|
|
ARIDISPUTE FILE
Transaction Dispute Conversion
The AR Transaction Dispute Conversion record is used for conversion purposes.
Records in this file have been converted from an external source and will be
loaded into the Accounts Receivable system via AR506 (Dispute and Comment
Conversion). Once updated, the dispute file will contain the corresponding
field data, and data in this file will be deleted. Disputed records represent
an amount and reason for non-payment for an invoice or debit memo.
Note: One converted dispute record is allowed for an invoice or debit memo.
UPDATED BY
AR506
FIELD NAME DESCRIPTION/VALID VALUES UPDATED BY
IDU-COMPANY Numeric 4
Element: Company Required. Transaction company number.
IDU-CUSTOMER Alpha 9 (Right Justified)
Element: Customer Required. Transaction customer number
representing a unique customer.
IDU-TRANS-TYPE Alpha 1
Element: Transaction TyRequired. Transaction type of open item
in dispute Valid values are:
D = Debit Memo
I = Invoice
IDU-INVOICE Alpha 22
Element: Invoice NumberUsed to identify the invoice.
IDU-PAYMENT-SEQ Numeric 6
Element: Payment SequenRequired. Payment obligation sequence
number.
IDU-SEQ Numeric 3
Element: Sequence NumbeRequired. The dispute record sequence
number. Used for uniqueness.
IDU-DISPUTE-CD Alpha 2
Element: Dispute Code This is the reason that the dispute was
created. Required field.
IDU-ORIG-AMT Signed 15.2
Element: Original AmounThe disputed amount in transaction
currency. Required field.
IDU-DISPUTE-DATE Numeric 8 (yyyymmdd)
Element: Dispute Date This is the date that the dispute went
into effect. YYYYMMDD format. Required
field.
IDU-RESOLV-DATE Numeric 8 (yyyymmdd)
Element: Resolution DatDate of resolution of dispute record.
YYYYMMDD format.
IDU-DESC Alpha 30 (Lower Case)
Element: Description Text description of dispute reason.
ARIDISPUTE FILE INDEX
NAME KEY FIELDS DESCRIPTION / SUBSET CONDITION USED IN
IDUSET1 COMPANY The path is used to keep the records AR506
CUSTOMER unique.
TRANS-TYPE
INVOICE
PAYMENT-SEQ
SEQ
|
