This appendix discusses mapping fields in the following batch processing tables:
Voucher Transactions - Batch Upload (F0411Z1)
Journal Entry Transactions - Batch File (F0911Z1).
This section contains lists of fields in the F0411Z1 table that are either required, optional, or ignored. This section also contains lists of additional required fields for processing discounts and payments.
Required Fields
The following fields in the F0411Z1 table are required:
Field Name |
Alias |
Type |
Length |
Definition |
EDI - User ID |
VLEDUS |
Alpha |
10 |
Enter the user ID of the person who runs the voucher batch process or the person who receives the messages in the work center. This field, in conjunction with the transaction number (VLEDTN), the batch number (VLEDBT), and the line number (VLEDLN), uniquely identifies a specific voucher. |
EDI - Transaction Number |
VLEDTN |
Alpha |
22 |
Enter the document number of the source system so that the transaction can be cross-referenced. This field, in conjunction with the line number (VLEDLN), identifies each transaction. Each new transaction number indicates a new voucher. You cannot have more than one transaction with the same number in a batch unless the line number is different. If the number assigned already exists in the F0411 table, the system returns an error message. |
EDI - Line Number |
VLEDLN |
Number |
7 |
Enter the pay item number only if a transaction has multiple pay items. If a transaction has only one pay item, you can leave this field blank. This field is used in conjunction with the transaction number (VLEDTN) to identify each pay item of the voucher. |
EDI - Successfully Processed |
VLEDSP |
Alpha |
1 |
Leave this field blank. The system completes this field to indicate whether the transaction was successfully processed using the batch processor. Blank or 0 (zero) indicates that the transaction was not processed or was processed in error. After the transaction is successfully processed, the system changes the value of the field to 1. |
EDI - Transaction Action |
VLEDTC |
Alpha |
1 |
Enter A in this field. No other values are valid. |
EDI - Transaction Type |
VLEDTR |
Alpha |
1 |
Enter V (for vouchers) in this field. This field is a code that identifies a particular kind of transaction. |
EDI - Batch Number |
VLEDBT |
Alpha |
15 |
Enter a number to group transactions for processing. This value, in conjunction with the transaction number (VLEDTN), the user ID (VLEDUS), and the line number (VLEDLN), uniquely identifies a transaction within a specific batch. This field also serves as a level break and causes the assignment of a new JD Edwards EnterpriseOne batch number each time that the value changes. To increase performance, assign one batch number for each group of transactions that are processed at one time. |
Address Number |
VLAN8 |
Number |
8 |
Enter the address book number of the supplier that is associated with the voucher transaction. The number that you enter must exist in the F0101 table. |
G/L Date |
VLDGJ |
Date |
6 |
Enter the GL date in the format that your database accepts. Some databases allow you to enter the date in a Gregorian date format (mmddyy), while others might require a Julian date format. The Julian date format is cyyddd (where c = century). Enter 0 (zero) for transactions in the 20th century and enter 1 for transactions in the 21st century. For example, the date June 1, 1999 corresponds to the Julian date 099152, and the date June 1, 2000 corresponds to the Julian date 100153 (because the year 2000 has a leap day, February, 29, 2000). Alternatively, you can leave this field blank and complete the fields VLDGM (mm), VLDGD (dd), VLDGY (yy), and VLDG# (cc) in the month/day/year/century format. Enter the prefix of the year in the Century field (VLDG#). For example, enter 19 for 1999, or enter 20 for 2005. |
Company |
VLCO |
Alpha |
5 |
Enter the number of the company to which the voucher belongs. This number must exist in the F0010 table and must identify a reporting entity that has a complete balance sheet. |
G/L Offset |
VLGLC |
Alpha |
4 |
The value of this field, in conjunction with the company number (VLCO), determines the AP trade (offset) account to which the transaction is posted. The account established in the AAI item PCyyyy (where yyyy is the value in the G/L Offset field) is used in the post process. You can establish the AAI for each company or for company 00000 (as the default G/L Offset). You complete this field only to direct different transactions to different offset accounts. |
Gross Amount |
VLAG |
Number |
15 |
Enter the transaction amount in the format that your database accepts. Some databases accept a decimal identifier while others do not. If you enter the transaction in a foreign currency (Currency Mode F), leave this field blank and use the Currency Amount field (VLACR) instead. If you process transactions using Currency Mode 3, you must complete both the Gross Amount and Currency Amount fields. |
G/L Bank Account |
VLGLBA |
Number |
8 |
Enter the bank account from which the voucher should be paid. Enter the account number in BU/Obj/Sub format. If you leave this field blank, the system uses the account that is set up in the AAI item PB for the company that is specified. If the AAI item for the company is not found, the system uses the AAI for company 00000. Alternatively, enter the account ID (GMAID) of the bank account from which the voucher should be paid. The account ID is located in the F0901 table. |
Business Unit |
VLMCU |
Alpha |
12 |
Enter the business unit to which the voucher belongs. The value that you enter in this field must exist in the F0006 table. If you leave this field blank, the system uses the value in the Security Business Unit field (MCU) in the supplier's address book record. |
Additional Required Fields for Processing Discounts
The following fields in the F0411Z1 table are required for processing voucher discounts:
Field Name |
Alias |
Type |
Length |
Definition |
Payment Terms Code |
VLPTC |
Alpha |
3 |
Enter a payment terms code or leave this field blank. The value that you enter in this field is validated against an entry in the Payment Terms (F0014) table. If the payment term is defined to calculate a discount, the system updates the Discount Available (VLADSC), Discount Due Date (VLDDNJ), and Net Due Date (VLDDJ) fields in the F0401 table accordingly. If you leave this field blank and the supplier has a payment term in the F0401 table, the system uses the payment term from the Supplier Master table to determine the discount and the discount due date. |
Discount Available |
VLADSC |
Number |
15 |
Leave this field blank if you completed the Payment Terms Code field (VLPTC). The system calculates the discount amount and discount due date based on the value of the Payment Terms Code field (VLPTC). If the Payment Terms Code field is blank and the supplier has a payment term in the F0401 table, the system uses the payment term from the F0401 table to calculate the discount amount and the discount due date. If you did not enter a payment term code, enter the amount of the discount in a format that your database accepts. Some databases accept a decimal identifier while others do not. If you enter a discount amount, you must also enter a discount due date (VLDDNJ). You cannot enter the value in this field as a percent. For example, if you use USD currency, and you enter a value of .05, the system reads this as a five-cent discount. |
Net Due Date |
VLDDJ |
Date |
6 |
Leave this field blank if you completed the Payment Terms Code field (VLPTC). This field identifies the due date of the voucher regardless of whether a discount is available. The system automatically calculates the net due date when the voucher is processed. If you leave the Payment Terms Code field blank, and the supplier has a payment term in the F0401 table, the system uses the payment term from the F0401 table to determine the net due date (VLDDJ). If you do not use a payment term, enter the net due date in a format that your database accepts. Refer to the data item for G/L Date (VLDGJ) for more information. Alternatively, leave this field blank and complete the VLDDM (mm), VLDDD (dd), VLDDY (yy), and VLDD# (cc) fields in the month/day/year/century format. Enter the prefix of the year in the Century field (VLDD#). For example, enter 19 for 1999 and 20 or 2005. |
Discount Due Date |
VLDDNJ |
Date |
6 |
Leave this field blank if you completed the Payment Terms Code field (VLPTC). This field identifies the date through which a discount can be taken when the payment is issued. When vouchers are processed, this field is automatically populated based on the definition of the payment term. If you leave the Payment Terms Code field (VLPTC) blank, and the supplier has a payment term in the F0401 table, the system uses the payment term from the F0401 table to determine the Discount Available (VLADSC), Discount Due Date (VLDDNJ) and Net Due Date (VLDDJ) fields. If you do not use a payment term, but you use the discount available, enter a date in the format that your database accepts. Refer to the data item for G/L Date (VLDGJ) for more information. Alternatively, leave this field blank and complete the VLDDNM (mm), VLDDND (dd), VLDDNY (yy), and VLDDN# (cc) fields in the month/day/year/century format. Enter the prefix of the year in the Century field (VLDDN#). For example, enter 19 for 1999 and 20 for 2005. |
Batch File Discount Handling Flag |
VLEDDH |
Alpha |
1 |
Enter 1 in this field to process vouchers with discounts. |
Discount Taken |
VLADSA |
Number |
15 |
Leave this field blank. The system updates this field in the F0401 table when the payment is issued and the discount is taken. |
Additional Required Fields for Processing Payments
The following field is required for processing payments in the Voucher Transactions - Batch Upload table (F0411Z1).
You can process paid vouchers for the upload process if these vouchers meet two payment conditions:
Only one payment is allowed per voucher.
The payment amount must be for the total voucher amount.
Payment information is updated to the F0413 and F0414 tables.
Field Name |
Alias |
Type |
Length |
Definition |
Matching Document Number |
VLDOCM |
Number |
8 |
To process a paid voucher, enter the number of the payment that paid the voucher in full. |
Optional Fields for Processing Batch Vouchers
Some fields in the F0411Z1 table are optional for batch voucher processing and are used with the first two tables. You can use the fields to provide additional information about vouchers.
Leave these fields blank to have the system populate them:
Field Name |
Alias |
Type |
Length |
Definition |
EDI - Detail Lines Processed |
VLEDDL |
Number |
5 |
Specify the number of detail lines that are included in a specific transaction. This field is for user verification only. |
Document Number |
VLODOC |
Number |
8 |
Leave this field blank. If you leave this field blank, the system uses next numbers for system 04 to generate a document number that identifies the transaction in the F0411 table. If you enter a value in this field, the value cannot exist in the F0411 table, or the transaction is considered a duplicate and is not processed. If you enter a value in this field, you must enter the same value in the corresponding field in the F0911Z1 table. |
Document Type |
VLDCT |
Alpha |
2 |
Leave this field blank. If you leave this field blank, the value is determined by the processing options of the Voucher Entry MBF Processing Options program (P0400047), which specifies the type of transaction. If you enter a value in this field, the value must exist in both UDC 00/DT (Document Type - All Documents) and UDC 00/DV (Document Type - Vouchers Only) . If you enter a value in this field, you must enter the same value in the corresponding field in the F0911Z1 table. |
Document Company |
VLKCO |
Alpha |
5 |
Enter a code that identifies the company of the transaction. This field is used only to differentiate transaction numbers by company. If you leave this field blank, the system uses the value that you entered in the Company field (VLCO). If you enter a value in this field, the value must exist in the F0010 table. Any value that you enter in this field must also be entered into the corresponding field in the F0911Z1 table. |
Document Pay Item |
VLSFX |
Alpha |
3 |
Leave this field blank. If you leave this field blank, the system assigns the pay item beginning with 001 to indicate the pay item number of the voucher. Use the Line Number field (VLEDLN) to designate transactions that have multiple pay items. If the transaction number ) and the line number combination are duplicated, the system ignores the next and all subsequent transactions regardless of whether the Pay Item field is used. |
Pay Item Extension Number |
VLSFXE |
Number |
2 |
Leave this field blank. This field is updated by other systems that process records and store them in the F0411 table. |
Adjusting Document Type |
VLDCTA |
Alpha |
2 |
Leave this field blank. The system provides a code that is updated when processed vouchers are either changed or voided. |
Payee Address Number |
VLPYE |
Number |
8 |
Enter the address number that is used when a payee other than the supplier is paid. The value that you enter into this field must exist in the F0101 table. |
Approver Address Number |
VLSNTO |
Number |
8 |
Enter the address number that identifies the person who is authorized to approve a voucher for payment. The system uses this number in conjunction with payee approval; the Payee Approval field must contain a valid value. |
Invoice Date |
VLDIVJ |
Date |
6 |
Enter the invoice date in the format that your database accepts. If you leave this field blank, the system uses the GL date. Refer to the data item for G/L Date (VLDGJ) for examples. You can also leave this field blank and complete fields VLDIVM (mm), VLDIVD (dd), VLDIVY (yy), and VLDIV# (cc) in the month/date/year/century format. Enter the prefix of the year in the Century field (VLDIV#). For example, enter 19 for 1999 and 20 for 2005. |
Fiscal Year |
VLFY |
Number |
2 |
Leave this field blank. The system populates this field based on the GL date and the company to identify the fiscal year of the voucher. |
Century |
VLCTRY |
Number |
2 |
Leave this field blank. The system populates this field based on the GL date and the company to identify the century of the voucher. |
Period Number |
VLPN |
Number |
2 |
Leave this field blank. The system populates this field based on the GL date and the company to identify the fiscal period of the voucher. |
Batch Number |
VLICU |
Number |
8 |
Leave this field blank. If you leave this field blank, the system uses next numbers for system 00 to generate a batch number that it uses to group vouchers that are processed simultaneously. |
Batch Type |
VLICUT |
Alpha |
2 |
If you complete this field, you must enter V (voucher ) to designate that the transaction is for a voucher. If you leave this field blank, the system populates the field with V when processing the vouchers. |
Batch Date |
VLDICJ |
Date |
6 |
If you leave this field blank, the system uses the date that the batch process program is run to identify the date that the batch was processed. If you complete this field, enter the date in a format that your database accepts. Refer to the field definition for G/L Date (VLDGJ) for more information about formats. Alternatively, you can leave this field blank and complete the fields VLDICM (mm), VLDICD (dd), VLDICY (yy), and VLDIC# (cc) in the month/day/year/ century format. Enter the prefix of the year in the Century field (VLDIC#). For example, enter 19 for 1999, or enter 20 for 2005. |
Balanced - Journal Entries |
VLBALJ |
Alpha |
1 |
Leave this field blank. The system completes this field with a code that indicates whether the amounts of the journal entries that are associated with the transaction are in balance with the gross amount of the voucher. |
Pay Status Code |
VLPST |
Alpha |
1 |
If you leave this field blank, the system populates the field according to the value for the processing option for the Voucher Entry MBF Processing Options program (P0400047) to indicate whether the voucher is open, paid, or on hold. If you did not assign a value for the processing option, the system uses the default value of the data dictionary item PST. The value of this field must exist in UDC 00/PS (Pay Status). |
Amount Open |
VLAAP |
Number |
15 |
Leave this field blank. The system automatically updates the Amount Open field (VLAAP) with the value in the Gross Amount field (VLAG) to identify the open amount of the voucher. Processing partially paid vouchers is not supported by this application. If you enter a value in this field, you receive an error message, and the transaction is not processed. |
G/L Posted Code |
VLPOST |
Alpha |
1 |
Leave this field blank. The General Ledger Post program (R09801) updates this field with a code that identifies the posted status of the voucher. If you previously processed historical data as a journal entry, you should create an associated F0911Z1 table transaction and use the AP trade account as the GL distribution account. Then, when the system posts the transaction, accounting will not be affected. If you process posted voucher transactions out of balance (that is, without corresponding F0911Z1 table information), enter D in this field. However, by doing this, you compromise your ability to void these transactions in the future, and will create discrepancies on the AP batch integrity reports. |
Object Account |
VLOBJ |
Alpha |
6 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Subsidiary |
VLSUB |
Alpha |
8 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Subledger Type |
VLSBLT |
Alpha |
1 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Subledger |
VLSBL |
Alpha |
8 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Void Flag |
VLVOD |
Alpha |
1 |
Leave this field blank. The system populates this field with a code that identifies whether a voucher was voided when you void a voucher. |
Document Company (Original Order) |
VLOKCO |
Alpha |
8 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. If you leave this field blank, the system updates it with the value that is assigned to the Document Company field in the F0411 table. |
Document Type - Original |
VLODOC |
Alpha |
2 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. If you leave this field blank, the system updates it with the value that is assigned to the Document Type field in the F0411 table. |
Document - Original |
VLOKCO |
Alpha |
5 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. If you leave this field blank, the system updates it with the values that is assigned to the Document Type field from the F0411. |
Document Pay Item - Original |
VLOSFX |
Alpha |
3 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Payment Handling Code |
VLCRC |
Alpha |
3 |
Enter a value that exists in UDC 00/HC (Special Handling Code) to identify vouchers to segregate for payment processing or to provide additional information. |
Supplier Invoice Number |
VLVINV |
Alpha |
25 |
Enter a number to identify a supplier's invoice. Any value that you enter in this field passes to the corresponding F0411 table record. This field is not validated. |
Document Company (Purchase Order) |
VLPKCO |
Alpha |
5 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Purchase Order |
VLPO |
Alpha |
8 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Document Type - Purchase Order |
VLPDCT |
Alpha |
2 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Line Number |
VLLNID |
Number |
6 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Order Suffix |
VLSFXO |
Alpha |
3 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Reference |
VLVR01 |
Alpha |
25 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Unit |
VLUNIT |
Alpha |
8 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Business Unit 2 |
VLMCU2 |
Alpha |
12 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Name - Remark |
VLRMK |
Alpha |
30 |
A code that provides an explanation for a voucher. Depending on how your processing options are set, this field might be printed on the payment. |
Frequency - Recurring |
VLRF |
Alpha |
2 |
Complete this field with a code to indicate the frequency of a recurring voucher only if the voucher is a recurring voucher that will be recycled. Documents that are generated with recurring information have the Document Type RR. The value that you enter in the Frequency Recurring field must exist in UDC H00/RF (Recurring Frequency). |
Recurring Frequency # of Payments |
VLDRF |
Number |
3 |
Complete this field with a number that indicates how many times a recurring voucher will be recycled only if the voucher is a recurring voucher that will be recycled. Documents that are generated with recurring information have the document type RR. The value that you enter in the Frequency Recurring field must exist in UDC H00/RF (Recurring Frequency). If you enter 1, the system does not generate a new voucher. |
Units |
VLU |
Number |
15 |
The system does not validate this field. The system passes any value that you enter for the voucher into the F0411 table. |
Unit of Measure |
VLUM |
Alpha |
2 |
Enter a code to describe the type of units. The value that you enter must exist in UDC 00/UM (Unit of Measure). |
Payment Instrument |
VLRYIN |
Alpha |
1 |
Enter a code that indicates the type of payment with which to pay the voucher. The value that you enter in this field must exist in UDC 00/PY (Payment Instrument). If you leave this field blank, the system updates it with the corresponding value from the F0401 table when the voucher is processed. |
Category Code - Address Book 7 |
VLAC07 |
Alpha |
3 |
Enter a code to indicate the type of 1099 for which the voucher is eligible. The system uses this field to process 1099s. Any values that you enter should match the corresponding values on the 1099 form and exist in UDC 01/07. |
Flag for 1099 |
VLTNN |
Alpha |
1 |
Enter a code to indicate that the voucher is eligible for 1099 processing. This code is not used in JD Edwards EnterpriseOne software. |
Item Number - Short |
VLITM |
Number |
8 |
Enter a number to identify the inventory item. The system ignores any value that you enter in this field. The system does not validate values in this field. |
Transaction Originator |
VLTORG |
Alpha |
10 |
The system updates this field when the transaction is processed. Leave this field blank. |
User ID |
VLUSER |
Alpha |
10 |
The system updates this field when the transaction is processed. Leave this field blank. |
Program ID |
VLPID |
Alpha |
10 |
The system updates this field when the transaction is processed. Leave this field blank. |
Date Updated |
VLUPMJ |
Date |
6 |
The system updates this field when the transaction is processed. Leave this field blank. |
Time Last Updated |
VLUPMT |
Number |
6 |
The system updates this field when the transaction is processed. Leave this field blank. |
Work Station ID |
VLJOBN |
Alpha |
10 |
The system updates this field when the transaction is processed. Leave this field blank. |
Ignored Fields
These fields in the (F0411Z1 are ignored by the system:
Field Name |
Alias |
Type |
Length |
Type Record |
VLEDTY |
Alpha |
1 |
Record Sequence |
VLEDSQ |
Number |
2 |
EDI - Document Type |
VLEDCT |
Alpha |
2 |
EDI - Transaction Set Number |
VLEDTS |
Alpha |
6 |
EDI - Translation Format |
VLEDFT |
Alpha |
10 |
EDI - Transmission Date |
VLEDDT |
Date |
6 |
EDI - Send/Receive Indicator |
VLEDER |
Alpha |
1 |
Batch File Create G/L Record |
VLEDGL |
Alpha |
1 |
User Address Number |
VLEDAN |
Number |
8 |
Account ID |
VLAID2 |
Alpha |
8 |
Bank Transit Short ID |
VLBAID |
Number |
8 |
Sequence Number - Operations |
VLOPSQ |
Number |
5 |
Control/Statement Field |
VLCTL |
Alpha |
13 |
Closed Item - As Of Processing |
VLFNLP |
Alpha |
1 |
Tax Rate/ Area 3 - Withholding |
VLTXA3 |
Alpha |
10 |
Tax Expl Code 3 - Withholding |
VLEXR3 |
Alpha |
2 |
A/R - A/P Miscellaneous Code 1 |
VLRP1 |
Alpha |
1 |
A/R - A/P Miscellaneous Code 2 |
VLRP2 |
Alpha |
1 |
A/R - A/P Cash Rcpts/Inv Reg Code |
VLRP3 |
Alpha |
1 |
Historical Currency Conversion Rate |
VLHCRR |
Number |
15 |
Historical Date - Julian |
VLHDGJ |
Date |
6 |
Historical Date - MO |
VLHDGM |
Number |
2 |
Historical Date - DA |
VLHDGD |
Number |
2 |
Historical Date - YR |
VLHDGY |
Number |
2 |
Historical Date - CTRY |
VLHDG# |
Number |
2 |
Fields Reserved for Users
The following fields in the F0411Z1 table are reserved for users. These fields are not updated by any JD Edwards EnterpriseOne program, nor are they displayed on any form in the JD Edwards EnterpriseOne Accounts Payable system:
Field Name |
Alias |
Type |
Length |
Definition |
User Reserved Code |
VLURC1 |
Alpha |
3 |
Enter any alphanumeric value up to three characters in length. |
User Reserved Date |
VLURDT |
Date |
6 |
Enter any date in this field. Use a format that your database accepts. See the data item for G/L Date (VLDGJ) for more information about date formats. |
User Reserved Amount |
VLURAT |
Number |
15 |
Enter any amount in this field. Use a format that your database accepts. |
User Reserved Number |
VLURAB |
Number |
8 |
Enter any number up to eight digits in length. |
User Reserved Reference |
VLURRF |
Alpha |
15 |
Enter any alphanumeric value up to 15 characters in length. |
This section contains a list of the required fields in the F0911Z1 table that are required for processing batch vouchers, and a list of the required fields for using the JD Edwards EnterpriseOne Advanced Cost Accounting system.
Required Fields
This table identifies only the required fields that you must complete. The system populates the remaining required fields based on information in the F0411Z1 table for the transaction.
The values that you enter in these fields must exactly match the values that you entered in the corresponding fields in the F0411Z1 table:
Field Name |
Alias |
Type |
Length |
EDI - User ID |
VNEDUS |
Alpha |
10 |
EDI - Transaction Number |
VNEDTN |
Alpha |
22 |
EDI - Successfully Processed |
VNEDSP |
Alpha |
1 |
EDI - Transaction Action |
VNEDTC |
Alpha |
1 |
EDI - Transaction Type |
VNEDTR |
Alpha |
1 |
EDI - Batch Number |
VNEDBT |
Alpha |
15 |
EDI - Line Number |
VNEDLN |
Number |
7 |
Document Company |
VNKCO |
Alpha |
5 |
Document Type |
VNDCT |
Alpha |
2 |
Document Number |
VNDOC |
Number |
8 |
Batch Number |
VNICU |
Number |
8 |
Batch Type |
VNICUT |
Alpha |
1 |
G/L Date |
VNDGJ |
Date |
6 |
Account Number |
VNANI |
Number |
29 |
Account Mode |
VNAM |
Number |
1 |
Ledger Type |
VNLT |
Alpha |
2 |
Amount |
VNAA |
Number |
15 |
Required Fields for the Advanced Cost Accounting System
If you use the JD Edwards EnterpriseOne Advanced Cost Accounting system (system 16), you must complete these additional fields in the F0911Z1 table:
Field Name |
Alias |
Type |
Length |
Definition |
Cost Object Type 1-4 |
VNABT1 VNABT2 VNABT3 VNABT4 |
Alpha |
1 |
Enter up to four cost object types. The system uses these fields to edit the values that you enter in the corresponding cost object fields (VNABR1 - VNABR4). If you enter a value in one of the cost object type fields, you must enter a value in the corresponding cost object field. The values in the cost object type fields must exist in the F1620 table. |
Cost Object 1-4 |
VNABR1 VNABR2 VNABR3 VNABR4 |
Alpha |
12 |
Enter up to four cost objects. The value in each cost object field must adhere to the edit rules for the corresponding cost object type (VNABT1 - VNABT4). |
Posting Code 1-10 |
VNPM01 - VNPM10 |
Alpha |
1 |
Leave these fields blank. |
Item Number |
VNITM |
Number |
8 |
If you enter a value in this field, the system validates it against the F4101 table. |
See Also
Mapping Fields for Journal Entry Batch Processing