Enter a code that specifies the type of cost object and the type of editing. Types are stored in the Cost Object Types table (F1620) and can be added or modified using the Cost Object Types program (P1620). Enter a cost object and cost type to associate a flexible segment with the standard format segment.
Enter a code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.
Enter a user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. Oracle 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 Oracle and should not be changed:
P: Accounts Payable
R: Accounts Receivable
T: Payroll
I: Inventory
O: Purchase Order Processing
J: General Accounting/Joint Interest Billing
S: Sales Order Processing
Enter the ledger type (UDC 09/LT) that the system uses for dual currency when dual currency is activated. If you leave this processing option blank, the system uses the XA ledger type for dual currency.
Enter a user defined code (09/LT) that specifies the type of ledger, such as AA (Actual Amounts), BA (Budget Amount), or AU (Actual Units). You can set up multiple, concurrent accounting ledgers within the general ledger to establish an audit trail for all transactions.
Enter whether the system rolls up the remaining FIFO layers for year-end processing. For LIFO valuations, the system always rolls up all layers at the end of the year into a single layer for the opening balance for the next year. If you want the FIFO valuations to roll up into one layer, enter 1 in this option. Otherwise, the system does not roll up the FIFO valuations into one layer. Values are:
Blank: Do not roll up remaining FIFO layers.
1: Roll up remaining FIFO layers.
Enter a user defined code (00/ST) that is used with the Subledger field to identify the subledger type and how the system performs subledger editing. On the User Defined Codes form, the second line of the description controls how the system performs editing. This is either hard-coded or user defined. Values are:
A: Alphanumeric field, do not edit.
N: Numeric field, right justify and zero fill.
C: Alphanumeric field, right justify and blank fill.
Enter a three-character code that for tax purposes, identifies a type of transaction. To enter values for the Transaction Nature code, use the following convention: X.YY X defines the origin of the transaction (inbound or outbound). Values for X are:
1: Inbound, inside the state.
2: Inbound, other states.
3: Inbound, import.
5: Outbound, inside state.
6: Outbound, other states.
7: Outbound, export. YY defines the transaction as a whole, such as a sales transaction.
Examples of Transaction Nature codes: 511 In-state-sale 611 Out-of-state sale
Enter the version of the GL journal entry program that the system uses. If you leave this processing option blank, the system uses version ZJDE0001.
Enter a number from 1 to 10 that specifies how the system posts records from the Account Ledger table (F0911) to the Cost Analyzer Balances table (F1602). This number also specifies which managerial accounting posting code (PM01- PM10) in the F0911 table to update as posted. For example, if the view number is 1, then the system updates PM01 with P when the F0911 record is marked as being posted.