This appendix contains these topics:
To successfully upload batch journal entries from outside sources such as PC data entry, third party or customer systems, or electronic data interfaces (EDI) to the Journal Entry Batch Input table (F0911Z1), you must enter data into certain fields.
Table 1 in this appendix lists the fields required by the Batch Input Journal Entry Processing program (P09110Z) for uploading. Tables 2 and 3 list optional fields that may be useful to you in organizing the data, but are not required by the program. Table 4 lists fields that the system ignores during the upload process. The functional server does not pass ignored fields to the JD Edwards World fields.
Each field in tables 1-3 is shown as required, conditional, or optional, as follows:
R = Required entry. You must enter data into this field to successfully upload the transactions to the F0911Z1 table.
C = Conditional entry. Under certain conditions, you must enter data into this field to successfully upload the transactions to the F0911Z1 table. The conditions are listed in the table under Explanation.
O = Optional entry. You can enter data in this field.
Other information in the tables include the following:
Value. The valid input value is edited. If no value is listed, you can enter any value that meets the field's alpha/numeric specifications.
If the UDC list shows DD as the value, the system uses valid values from the data dictionary specifications for the data item. The system may validate data dictionary specifications against user defined codes, allowed values, or upper/lower allowed values.
If a table or user defined code (xx/xx) is listed in the UDC list, the system validates the value you enter against that table or user defined code.
Default. The default value the system assigns if you leave the field blank. If no default is listed, the system uses the initialization value for the data item, with blanks for alpha fields and zeros for numeric fields. If DD is listed, the system uses the default value for the data item from the data dictionary. You can revise some of the defaults through the functional server processing options (XT0911Z1).
Formats. Julian date. The JD Edwards World Julian date format is CYYDDD, where C is the century (1900=0, 2000=1), YY is the year, and DDD is the day of the year.
Numeric amounts. The data dictionary shows amounts with a 0 data table decimals. The data item size includes the decimal values. For example, if the display decimals = 2, the table keeps 5.50 amount as 550. If display decimals = 0, the table keeps a 1000 amount as 1000.
Multi-currency. If you are working in a multi-currency environment, the system uses the company or account display decimals for ledger type AA (domestic), and the transaction currency code for ledger type CA (foreign).
Other special format considerations appear under Explanation for the specific field. If no format is listed, use the data dictionary specifications for the data item to enter the field.
The Batch Input Journal Entries program (P09110Z) requires the fields in this table for adding or deleting transactions.
As of release A7.1, all programs and tables use Julian dates instead of Gregorian dates (D/M/Y). You can continue to use the Gregorian date format in the G/L date field (DGM, DGD, DGY). If you decide to use Julian dates, you only need to load DGJ.
| Field | Description | R C O | Explanation | Value | Default |
|---|---|---|---|---|---|
| AA | Amount | R | Required to enter amounts in domestic mode (CRRM=D) | Calculated from ACR if working in multi-currency and foreign mode. | |
| ACR | Foreign Amount | R | Required to enter amounts in foreign mode (CRRM=F) | Calculated from AA if working in multi-currency and domestic mode. | |
| ANI | Account number | R | The system validates the account number, the posting edit code, and the business unit through the F0901 table. | F0901 | If you enter AN8, the default is F0101 (revenue or expense accounts.) |
| DCT | Document Type | R | Required to delete a transaction (EDTC=D) | F0005 00/DT | JE |
| DGJ or DG# DGM DGD DGY | G/L Date | R | Required to add a transaction (EDTC=A or blank) | Valid date | |
| DOC | Document Number | C | Required to delete a transaction (EDTC=D). If you leave this field blank when you add a transaction, the system uses Next Numbers to assign a document number. If you enter a document number, it must not already exist for an add. | F0911 Document | For an add, this is assigned by Next Numbers. |
| EDTC | Transaction action | R | Required to delete a transaction (EDTC=D). Enter only one line to indicate the JD Edwards World document and document type to be deleted. | A = Add
D = Delete |
A |
| EDTN | Transaction number | R | The user transaction, voucher number, or sequential number for batch processing. This field, or this field in combination with EDUS and EDBT, should contain unique identification for a specific A/R voucher transaction. | ||
| EXA | Explanation | R | Required to add a transaction (EDTC=A or blank). | ||
| ICU | Batch number | R | This field must be left blank. The system assigns the number through the Batch Edit/Update program. Each change in the EDBT field drives the creation of a new batch number. | Assigned by Next Numbers. | |
| MCU | Business unit | C | Required if business unit security is used | F0006 | Derived from ANI |
The fields in this table may be useful in processing and organizing batch data.
| Field | Description | R C O | Explanation | Value | Default |
|---|---|---|---|---|---|
| CRCD | Currency Code | O | If multi-currency is turned on, the system edits this field. You can use this field to control the currency calculations if you are working in a multi-currency environment. | F0013 | |
| CRR | Exchange rate | O | If multi-currency is turned on, the system edits this field. You can use this field to control the currency calculations if you are working in a multi-currency environment. | F0015 for CRCD if CRRM=F or D. Calculated from AA and ACR if CRRM=3 for both AA and ACR. | |
| CRRM | Mode of entry | O | If multi-currency is turned on, the system edits this field. You can use this field to control the currency calculations if you are working in a multi-currency environment. | D-domestic
F-foreign 3-pre-calculated |
DD |
| EDBT | User defined batch number | O | This field, in combination with EDTN and EDUS, uniquely identifies a specific journal entry. This field also acts as a level break and drives the assignment of a JD Edwards World batch number each time this value changes. | ||
| EDUS | User ID | O | User defined ID number. This field, in combination with EDTN and EDBT, uniquely identifies a specific journal entry. PC processing uses this field as the PC terminal ID number. | ||
| ICUT | Batch type | O | This field identifies the system the batch pertains to. For example::
G General Accounting V A/P journal entries I A/R journal entries |
98/IT | G |
| KCO | Document company | O | This field in combination with DOC and DCT uniquely identifies an original document. |
The fields in this table are optional. You can use them to provide additional information about the A/P transactions. Some of these fields are for future use with EDI processing.
The following fields also use the Julian date format:
Check Date
Service/Tax Date
Historical Date
Check Cleared Date
You may continue to use the Gregorian date format.
| Field | Description | R C O | Explanation | Value | Default |
|---|---|---|---|---|---|
| ALID | Outsider lease/well | O | |||
| ALT1 | Alternate G/L posting code | O | |||
| ALT2 | Alternate G/L posting code | O | |||
| ALT3 | Alternate G/L posting code | O | |||
| ALT4 | Alternate G/L posting code | O | |||
| ALT5 | Alternate G/L posting code | O | The program will not delete the journal entry if the value in this field is M (multi-currency) or T (tax). | ||
| ALT6 | Alternate G/L posting code | O | |||
| ALT7 | Alternate G/L posting code | O | |||
| ALT8 | Alternate G/L posting code | O | |||
| ALT9 | Alternate G/L posting code | O | |||
| ALT0 | O | Reserved for future use | |||
| ALTT | O | Reserved for future use | |||
| ALTU | O | Reserved for future use | |||
| ALTW | O | Reserved for future use | |||
| ALTX | O | Reserved for future use | |||
| ALTY | ID Type | O | |||
| ALTZ | O | Reserved for future use | |||
| AN8 | Address number | O | If ANI is blank, the system retrieves the default expense/revenue account for this address and enters it to ANI. | ||
| ASID | Serial number | O | Asset serial number. | F1201 | |
| ASM | Asset input code | O | |||
| BC | Bill code | C | Required if there is a value in the DOI field. | F0005 98/BC | |
| BRE | Batch rear end code | O | An asterisk (*) in this field indicates the transaction is to be treated like a posted record. | ||
| CFF1 | Client free-form field | O | |||
| CFF2 | Client free-form field | O | |||
| CN | Check number | O | |||
| CO | Company | O | F0010 | The default is derived from the ANI business unit. | |
| DCTO | Order type | C | Required if you enter a purchase order (PO). | F0005 00/DT | |
| DKC or DKCM DKCP DKCY DKC# | Check cleared date | O | |||
| DKJ or DK#, DKM DKD DKY | Check date | O
C O |
Required if the bill code (BC)=D. | ||
| DKJ or DK#, DKM DKD DKY | Check date | O
C O |
Required if the bill code (BC)=D. | ||
| DOI | DOI sub | O | Required if the bill code (BC)=D. | ||
| DSVJ or DSV# DSVM DSVD DSVY | Service/tax date | O
C O |
Valid date | DG date | |
| EDCT | Transaction (doc) type | O | Future EDI field. | ||
| EDDL | Number of detail lines | O | This number should reflect the number of detail lines included in the specific transaction. For user verification only. | ||
| EDDT | Transmission date | O | Valid calendar date | Date processed Format: Julian | |
| EDER | Send/receive indicator | O | Future EDI field. | DD | |
| EDFT | Translation Format | O | Additional information for use with EDI processing in the future. | A valid translation format set up through the 3rd party translators for EDI. | |
| EDGL | Create G/L record | O | Future use. | ||
| EDLN | Line number | O | This field may be useful to the user in identifying specific transaction lines. | ||
| EDSP | Processed (0/1) | O | The batch processing program bypasses transactions marked 1 (processed). | 0 = No 1 = Yes | 0 |
| EDSQ | Record sequence | O | Future EDI field. | ||
| EDTS | Transaction set | O | Additional information for use with EDI processing in the future. | A standard EDI set number. | |
| EDTR | Transaction type | O | Identifies the type of journal entry to be added or deleted. The journal entry batch processing program bypasses V and I types. If you do not have a transaction type, you cannot review your transactions on Batch Journal Entries before processing them into the General Accounting system. | J | J |
| EDTY | Record type | O | Future EDI field. | ||
| EXR | Explanation/ remark | O | |||
| EXTL | Line extension code | O | |||
| FNLP | Final payment code | O | |||
| FQ | Fiscal quarter | O | |||
| HCRR | Historical exchange rate | O | |||
| HDGM | Historical date month | O | |||
| HDGD | Historical date day | O | |||
| HDGY | Historical date year | O | |||
| HDG# | Historical date century | O | |||
| HDGJ | Historical Date - Julian | O | |||
| HMCU | Home business unit | O | |||
| IVD | Invoice date | O | |||
| JBCD | Job category | O | |||
| JBST | Job step | O | |||
| JELN | Line number | O | If you leave this field blank, the Batch/Edit Update program assigns a value. The program ignores this field for a transaction delete (EDTC=D). | Assigned | |
| LNID | Line number | O | |||
| LT | Ledger type | O | If you enter the units (U) field, the system modifies the ledger type with a U in the second position and validates the units ledger type against F0005 09/LT. | F0005 09/LT | If the functional server processing option is left blank, the system uses AA for domestic entry or CA for foreign entry. |
| ODCT | Original document type | O | |||
| ODOC | Original document | O | |||
| OKCO | Original document company | O | |||
| OPSQ | Operation sequence | O | |||
| PDCT | Order type | C | Required if PO not blank | 00/DT | DD if PO not blank. |
| PKCO | Order key company | C | Required if PO not blank | F0010 | CO if PO not blank. |
| PO | Purchase order | O | |||
| PRGE | Purge code | O | |||
| PSFX | Purchase order suffix | O | |||
| R1 | Reference 1 | O | |||
| R2 | Reference 2 | O | |||
| R3 | Reference 3 | O | |||
| RCND | Reconciled | O | |||
| RE | Reverse/void code | O | The value in this field cannot be V for voucher or invoice entry. | DD | DD |
| SBL | Subledger | C | Required if you enter a value in SBLT. The system edits against the user defined code for SBLT: F0005 00/ST. | Depends on the value you enter in SBLT. | Default exists only for work order SBLT. |
| SBLT | Subledger type | C | Required if the SBL field contains a value, or if the bill code (BC)=D. | A or C if bill code = D F0005 00/ST | DD |
| SFX | Pay item | O | If you leave this field blank, the Batch Edit/Update program assigns a value. Ignored for a Transaction Delete (EDTC=D). | Assigned | |
| SUMM | Summarized code | O | |||
| TNN | 1099 code | O | |||
| U | Units | O | |||
| UM | Units of Measure | O | Unit of measure in F0901 table for ANI account number. | If you enter (U), the default is the unit of measure in F0901 table for ANI account number. | |
| VINV | Supplier invoice number | O | |||
| WN | Fiscal year-weekly | O | |||
| WR01 | Phase code | O | F000500/WI | F4801 | |
| WY | Fiscal period - weekly | O |
If you enter data into these fields, the functional server does not pass it to the JD Edwards World fields. The Journal Entry Batch Input program (P09110Z) supplies blank, zero, or the default shown in the following table.
The following fields also use the Julian date format:
Batch Date
Batch System Date
Invoice Date
You may continue to use the Gregorian date format.
| Field | Description | Value | Default |
|---|---|---|---|
| AID | Account ID | ANI Account ID | |
| AM | Account mode | Derived from ANI input mode | |
| CTRY | Century | Derived from DG date | |
| DIC# DICM DICD DICY or DICJ | Batch Date | F0011 Batch Header | |
| DLNA | Delete Not Allowed | ||
| DSY# DSYM DSYD or DSYJ | Batch system date | F0011 Batch header | |
| EPAN | User Address | ||
| FY | Fiscal year | Derived from DG date | |
| GLC | G/L offset | ||
| IVD# | Invoice Date - Century | ||
| IVDJ | Invoice Date - Julian | ||
| IVDM | Invoice Date - Month | ||
| IVDD | Invoice Date - Day | ||
| IVDY | Invoice Date - Year | ||
| JOBN | Workstation ID | System | |
| OBJ | Object | Derived from ANI | |
| OSFX | Original pay item | ||
| PID | Program ID | System | |
| PN | G/L period | Derived from DG date | |
| POST | G/L posted code | ||
| PYID | Payment ID | ||
| REG# | Registration number | ||
| SUB | Subsidiary | Derived from ANI | |
| TICM TICU | Batch time | F0011 Batch header | |
| UPMJ | Date updated | System | |
| UPMT | Time last updated | System | |
| USER | User profile | System |