F48229AuditTrail
F48229 Create Audit Trail Record
Minor Business Rule
Object Name: N48S0680
Parent DLL: CCRIN
Location: Client/Server
Language: NER
This function will insert records in the F48229 Delete Invoice Audit Table. If deleting the entire batch a record will be inserted for each invoice in the
batch or if deleting a specific invoice a record will be inserted for that invoice. The record will be updated with the following fields: Invoice Number, Invoice
Type, Invoice Company, Batch Number, Contract Number, Contract Type, Contract Company, Application Number, Adjustment Number, Application Date,
GL Date, Program ID and Audit Information: User ID, Workstation ID, Date Updated and Time Updated.
^
Data Structure
D48S0680 - F48229 Audit Trail Record
DOCZMnInvoice Number I N
DCTISzInvoice Document Type I N
KCOISzInvoice Document Comp IN
ICUMnBatch Number IY
DOCOMnContract NumberIN
DCTOSzContract Type I N
KCOOSzContract CompanyIN
APPLMnApplication NumberIN
ADJNMnAdjustment NumberIN
APDTJdApplication DateIN
DGLJdGL Date IN
PIDSzProgram ID IY
USERSzUser ID IN
JOBNSzWorkstation ID IN
^
Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
mnInvoiceNumber | DOCZ | MATH_NUMERIC | OPT | INPUT |
The original document number. This can be a voucher, an invoice, unapplied cash, a journal entry number, etc. Matching document
numbers are also used to identify related documents in the Accounts Receivable and Accounts Payable systems. See matching document
(DOCM). This document number (DOCO) is always the original document number, and the matching document number (DOCM) is the check,
adjustment, or credit to be applied against the original document.
For example:
A/P Automated/Manual Payment: Original (DOCO) - Voucher;
Matching Document (DOCM) - Payment
A/R Original Invoice: Original (DOCO) - Invoice
Receipt Application: Original (DOCO) - Invoice; Matching
Document (DOCM) - Receipt
Credit Memo/Adjustment: Original (DOCO) - Invoice; Matching Document (DOCM) -Credit Memo
Unapplied
Case: Original (DOCO) - Receipt |
szInvoiceDocType | DCTI | char | OPT | INPUT |
A user defined (00/DI) document type for invoice entry. Any document type set up for invoice-only entry should begin with the letter R
(receivables). The default is RI, RR, or RM. Reserved document types have been defined for vouchers, invoices, receipts, and time sheets.
The
reserved document types are:
P_
Accounts Payable Documents R_Accounts Receivable Documents
T_
Payroll Documents I_Inventory
Documents
O_
Order Processing Documents
Note: Verify that the default document type for invoices is set up in both UDC 00/DT and UDC 00/DI.
|
szInvoiceDocCompany | KCOI | char | OPT | INPUT |
Invoice Document Company. |
mnBatchNumber | ICU | MATH_NUMERIC | REQ | INPUT |
A number that identifies a group of transactions that the system processes and balances as a unit. When you enter a batch, you can either
assign a batch number or let the system assign it using the Next Numbers program. |
mnContractNumbr | DOCO | MATH_NUMERIC | OPT | INPUT |
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on. |
szContractType | DCTO | char | OPT | INPUT |
A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has
reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post
program. (These entries are not self-balancing when you originally enter them.)
The following document types are defined by J.D. Edwards and
should not be changed:
P
Accounts Payable documents
R
Accounts Receivable documents
T
Payroll documents
I
Inventory documents
O
Purchase Order Processing documents
J
General Accounting/Joint Interest Billing documents
S
Sales Order Processing documents
|
szContractCompany | KCOO | char | OPT | INPUT |
A number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a
sales order, and so on).
If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (X0010) uses the
order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order
type, the order company lets you locate the desired document.
If you use the regular Next Numbers facility, the order company is not used to
assign a next number. In this case, you probably would not use the order company to locate the document. |
mnAplicationNumber | APPL | MATH_NUMERIC | OPT | INPUT |
The last or current application number for the specified contract. (The system assigns a new application number each time an invoice is
issued for the contract.)
|
mnAdjustmentNumber | ADJN | MATH_NUMERIC | OPT | INPUT |
A number used to control changes to closed applications. Closed applications represent invoices that have been sent. This number is
always zero unless you reopen a previous application. |
jdApplicatnDate | APDT | JDEDATE | OPT | INPUT |
The date of the last or current application. (An application is assigned each time an invoice is issued for the contract.) |
jdGLDate | DGL | JDEDATE | OPT | INPUT |
A date that identifies the financial period to which the transaction is to be posted.
The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
|
szProgramId | PID | char | REQ | INPUT |
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry
interactive program is P4210, and the number of the Print Invoices batch process report is R42565.
The program ID is a variable length value.
It is assigned according to a structured syntax in the form TSSXXX, where:
T
The first character of the number is alphabetic and identifies the
type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a
program.
SS
The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210
indicates that this program belongs to system 42, which is the Sales Order Processing system.
XXX
The remaining characters of the numer are
numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry
program.
|