A Batch Input Setup

This appendix contains these topics:

To successfully upload address book records into the Address Book - Batch File (F0101Z1) from an outside source, such as PC data entry, a third-party system, or electronic data interchange (EDI), you must enter data into certain fields in the appropriate format.

The batch file consists of batch control fields and transaction fields. It is important to recognize the difference between these fields, as some fields (for example, batch number) seem to appear as both a batch control and a transaction field:

  • Batch control fields temporarily identify transactions in the batch file, because permanent identification has not yet been established. These fields are assigned by you and go no further than the batch file.

  • Transaction fields refer to the values that directly correlate with the fields in the JD Edwards World files. These fields are assigned by the system during batch processing and are passed on to the JD Edwards World files.

A.1 Batch Control Information

Batch control allows unique identification for each record in the address book batch input file. Batch control fields are temporary control fields which include the following:

  • User ID

  • User Batch Number

  • Transaction Number

  • Transaction Type

On the Batch File Revisions form, these fields are separated from the actual transaction fields.

While transactions exist in the batch input file, the system considers any records with the same combination of values in User ID, User Batch Number, and Transaction Number to be one transaction.

A.2 Transaction Information

Transaction information consists of those fields that exist in the Address Book Master file (F0101). The system provides default values for many of the optional fields that you leave blank.

The following fields are required to create an address. All other fields can be blank, because the system will assign default values:

  • Alpha Name

  • Mailing Name

  • Search Type

The following fields are required to delete an address. All other fields can be blank, and the system will use the appropriate values from the original address:

  • Transaction Action

  • Address Number

You cannot make changes to addresses that already exist in the Address Book Master file using batch input. You can make these changes using Address Book Revisions.

A.3 Technical Considerations

Batch files consist of batch control fields which are used by the batch file processing programs, followed by transaction fields which directly reflect the corresponding JD Edwards World file layout.

A.3.1 Preassigned Address Numbers

You can allow the batch processing program to assign the address number by using the JD Edwards World next numbers facility. You can also assign the address number in advance, in order to facilitate a smooth transition between two systems. If you enter an address number in the transaction field, the batch processing program will use this number when creating the new transaction record.

You can generate the address number by using a custom next number program. If you do, be aware that some numbers you assign may have already been used if you also enter addresses interactively.

You can also generate the address number by accessing the JD Edwards World next numbers facility, obtain and reserve a valid next number, and assign this number to the batch input transaction.

A.3.2 Override Address Book Functional Server Version

There are processing options associated with the functional servers utilized by the batch processing programs. You can specify which version of the functional server to use when processing. In most cases, you should not change this option since functional server options should be set throughout the system in a variety of programs.

A.4 DREAM Writer Considerations

A.4.1 Processing Options

Option Description
Proof or final mode Proof mode:

  • Prints the error/exception report with errors or warnings detected.

  • Does not perform file updates.

Final mode:

  • Can print both an update and an error/exception report.

  • Creates records in the Address Book Master file.

You should use proof mode to detect any errors and make corrections prior to running final mode. To correct errors, do one of the following:

  • Correct the batch file data at the source and regenerate the batch file on the AS/400.

  • Directly update the individual batch records already on the AS/400 through the Address Book Batch File Maintenance program (P0101Z1).

After making corrections, you must resubmit your version of batch file processing. Previously processed records are bypassed.
Purge processed records A processing option indicates if you want to purge after processing:

Blank – The system flags successfully processed records as Processed in the batch file.

1 – The system deletes transactions after they are successfully processed.

When transactions are not purged at processing time, you must use the Address Book Batch File Purge program (P00PURGE) to globally delete all processed addresses in the Address Book Batch Input file.
Error file In addition to printing an error/exception report, you might choose to write all errors and warnings to the PC Error file (F0040). This file can be used to download the error information to the PC after processing is complete.

A.4.2 Data Selection

You can use any criteria, such as user ID, a range of transaction numbers, and so on, to select transactions to be included in this batch.

A.4.3 Data Sequence

Do not change the data sequence. If you change the data sequence, processing will not run properly.

A.5 Address Book Field Instructions

Table 1 in this appendix lists the fields required by the Batch Address Processing program for uploading records. Tables 2 and 3 list optional fields that might 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:

Code Description
R (Required) You must enter data in this field to successfully upload the records to the Address Book - Batch file.
C (Conditional) Under certain conditions, you must enter data into this field to successfully upload the records to the Address Book - Batch file. The conditions are listed in the table under Explanation.
O (Optional) You may enter data in this field.

Other information in the tables includes:

Information Description
Value The valid input value is edited. If no value is listed, you may enter any value that meets the field's alphanumeric specifications.

If the table shows DD as the value, the system takes valid values from the data dictionary specifications for the data item. The system can validate data dictionary specifications against user defined codes, allowed values, or upper/lower allowed values.

If a file or user defined code (xx/xx) is listed, the system validates the value you enter against that file or user defined code.
Default The default value that 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 (XT0101Z1).
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 0 data file decimals. The data item size includes the decimal values. For example, if the display decimals = 2, the file keeps $5.50 as 550. If display decimals = 0, the file keeps $1000 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.

A.6 Table 1 - Required or Conditionally Required Fields

The Address Book Batch Processing program (P01110Z) requires the fields in this table for adding or deleting address book records.

Field Description R C O Explanation Value Default
EDTN Transaction Number R The user transaction, address number, or sequential number for batch processing. This field, in combination with EDUS and EDBT, will uniquely identify an address book transaction. This field is required to add a record.    
EDBT Batch Number R User assigned for processing    
ALPH Alpha Name R Required to add a record.    
MLNM Mailing Name R Required to add a record.    
AT1 Search Type R Required to add a record. F0005 01/ST Search type security DD
MLN1 Mailing Name C Required to add a record in double byte systems. DD  
CRCA Amount Currency C Required if multi-currency is activated. F0013 DD
EDTC Transaction Action C Required to delete a record (EDTC = D). Enter only one line to indicate the JD Edwards World address number to be deleted. A = Add D = Delete Blank = Add Blank
AN8 Address Number C Required to delete a record (EDTC=D). If you leave this field blank when you add a record, the system uses Next Numbers to assign an address book number. If you enter an address number, it must not already exist for an add, but must exist for a delete. F0101 Address Number Next Numbers
DTAR A/R Model JE DCT C Required if document and company exist. F0005 00/DT DD
DCAR A/R Model JE Doc C Required if document type and company exist.    
KCOR A/R Model JE Company C Required if document and type exist. F0010  
DTAP A/P Model JE DCT C Required if document and company exist. F0005 00/DT DD
DCAP A/P Model JE Doc C Required if document type and company exist.    
KCOP A/P Model JE Company C Required if document and type exist. F0010  
MCUR CC - A/R Default C Required if OBAR is entered. F0006 DD
MCUP CC - A/P Default C Required if OBAP is entered. F0006XY DD

A.7 Table 2 - Optional Control Fields

The fields in this table might be useful in processing and organizing batch data.

Field Description R C O Explanation Value Default
EDUS User ID O User defined ID number. This field, in combination with EDTN and EDBT, uniquely identifies a specific address book entry. PC processing uses this field as the PC terminal ID number.    
EDAN User Address Number O A number that you assign in the address book record when the actual address number is to be assigned by next numbers during batch processing. This number can be used in A/R Invoices or A/P Vouchers to link the new address number to those transactions.    
CRCD Currency Code O If multi-currency is activated, the system edits this field. This is the default currency for customer entry and inquiry. F0013 DD
CRRP Currency Code O If multi-currency is activated, the system edits this field. This is the default currency for voucher entry and inquiry. F0013 DD
TAX Tax ID O   DD DD
TAXC Person/Corporation Code O   DD DD
EXR1 Tax Explanation Code O   F0005 00/EX DD
EXR2 Tax Explanation Code 2 O   F0005 00/EX DD
EXR3 Tax Explanation Code 3 O   F0005 00/EX DD
TXA1 Tax Rate/Area O If you enter a code here, the system performs tax calculations. DD DD
TXA2 Tax Rate/Area 2 O   DD DD
TXA3 Tax Rate/Area 3 O   DD DD
TX1 European Company Tax ID O     DD
TX2 European Individual Tax ID O     DD

A.8 Table 3 - Additional Fields

The fields in this table are optional. You can use them to provide additional information about the address book records. Some of these fields are for future use with EDI processing.

Field Description R C O Explanation Value Default
EDTY Record Type O      
EDSQ Record Sequence O      
EDCT Transaction Type O      
EDLN Line Number O      
EDST Transaction Set O Future EDI field. A standard EDI set number  
EDFT Translation Format O Future EDI field. A valid translation format set up through the third-party translators for EDI  
EDDT Transmission Date O   Valid calendar date Date processed.Format: YYMMDD
EDER Send/Receive Indicator O      
EDDL Number of Detail Lines O Number of detail lines in the specific transaction. For user verification only. For address book, this should always be 1. 1  
EDSP Processed (0/1) O If processed (1), this transaction will be bypassed for batch processing. 0 = No 1 = Yes 0
EDTR Transaction Type O Not used for address book.    
EDGL Create G/L Record O Future use.    
MCU Business Unit O   F0006 Business Unit 1
AR1 Area Code O   DD DD
PH1 Phone Number O     DD
AR2 Area Code 2 O   DD DD
PH2 Phone Number O      
AC01 Location or Branch O User defined reporting code. F0005 01/01  
AC02 Salesperson O User defined reporting code. F0005 01/02  
AC03 Sales Territory O User defined reporting code. F0005 01/03  
AC04 Category Code 4 O User defined reporting code. F0005 01/04  
AC05 Category Code 5 O User defined reporting code. F0005 01/05  
AC06 Category Code 6 O User defined reporting code. F0005 01/06  
AC07 Category Code 7 O User defined reporting code. F0005 01/07  
AC08 Category Code 8 O User defined reporting code. F0005 01/08  
AC09 Category Code 9 O User defined reporting code. F0005 01/09  
AC10 Category Code 10 O User defined reporting code. F0005 01/10  
AC11 Category Code 11 O User defined reporting code. F0005 01/11  
AC12 Category Code 12 O User defined reporting code. F0005 01/12  
AC13 Category Code 13 O User defined reporting code. F0005 01/13  
AC14 Category Code 14 O User defined reporting code. F0005 01/14  
AC15 Category Code 15 O User defined reporting code. F0005 01/15  
AC16 Category Code 16 O User defined reporting code. F0005 01/16  
AC17 Category Code 17 O User defined reporting code. F0005 01/17  
AC18 Category Code 18 O User defined reporting code. F0005 01/18  
AC19 Category Code 19 O User defined reporting code. F0005 01/19  
AC20 Category Code 20 O User defined reporting code. F0005 01/20  
AC21 Category Code 21 O User defined reporting code. F0005 01/21  
AC22 Category Code 22 O User defined reporting code. F0005 01/22  
AC23 Category Code 23 O User defined reporting code. F0005 01/23  
AC24 Category Code 24 O User defined reporting code. F0005 01/24  
AC25 Category Code 25 O User defined reporting code. F0005 01/25  
AC26 Category Code 26 O User defined reporting code. F0005 01/26  
AC27 Category Code 27 O User defined reporting code. F0005 01/27  
AC28 Category Code 28 O User defined reporting code. F0005 01/28  
AC29 Category Code 29 O User defined reporting code. F0005 01/29  
AC30 Category Code 30 O User defined reporting code. F0005 01/30  
ATE User Code 3 O   DD DD
ATR Receivable Y/N O   DD DD
ATP Payables Y/N/M O   DD DD
ATO Owner Y/N O   DD DD
ATPR User Code 4 O   DD DD
ADD1 Address Line 1 O   DD  
ADD2 Address Line 2 O   DD  
ADD3 Address Line 3 O   DD  
ADD4 Address Line 4 O   DD  
ADDZ Postal Code O   DD DD
ADDS State O F0005 00/S DD  
CTY1 City O DD    
COUN County O DD    
CTR Country O   F0005 00/CN F0070 DD
PA8 Parent Number O   F0150 AN8
AN81 Address Number 1 O   F0101 AN8
AN82 Address Number 2 O   F0101 AN8
AN83 Address Number 3 O   F0101 AN8
AN84 Address Number 4 O   F0101 AN8
AN85 Factor/Special Payee O   F0101 AN8
AN86 Address Number 5 O   F0101 AN8
APC A/P Class O   DD DD
HDPY Hold Payment O   DD DD
SCK Multiple Checks O   DD DD
FLD Float Days - Checks O      
ARC A/R Class O   DD DD
STMTS Print Statement O   DD DD
STTO Send Statement To O   DD DD
ABC1 ABC Code Sales O   DD DD
ABC2 ABC Code Margin O   DD DD
ABC3 ABC Code Average Days O   DD DD
TRAP Payment Terms - A/P O   F0014  
TRAR Payment Terms - A/R O   F0014  
AFC Apply Finance Charges O   DD DD
FD Apply Finance Charges Days O   DD DD
FP Percentage Factor O      
BO Balance Forward - Open O   DD DD
CM Flash Message O   F0005 00/CM DD
DLC Date Last Credit Review O   Valid date Format: Julian
SIC S.I.C. Code O   F0005 01/SC  
AIDP Subsidiary - A/P Default O   DD DD
AIDR Subsidiary - A/R Default O   DD DD
OBAP Object Account - A/P Default O   DD DD
OBAR Object Account - A/R Default O   DD DD
LNGP Language Preference O   F0005 01/LP DD
DNLT Delinquency Notice O   DD DD
ATCS Automatic Receipts O   DD DD
SITO Send Invoice To O   DD DD
SQNL Ledger Inquiry Sequence O   DD DD
ALGM Automatic Receipts Algorithm O   F0005 01/AA DD
HDAR Hold Invoices O   DD DD
CYCN Statement Cycle O     First Character of ALPH
TSTA Credit Alert O   F0005 00/CM DD
AB1 Pre-note Code O   DD DD
PYIN Payment Instrument O   F0005 00/PY DD
CMGR Credit Manager O   DD DD
CLMG Collection Manager O   DD DD
NBRR Number of Reminders Sent O   DD DD
COLL Collection Report O   DD DD
RYIN Payment Instrument O   F0005 00/PY DD
SNTO Sent To Address O   F0101  
TAWH Tax Authority O   F0101  
PCWH Percent Withholding O      
SBLI Subledger Inactive Code O   DD DD
ALP1 Secondary Alpha Name O      
ARPY Alternate Payor O   F0101 AN8
TXCT Cert Tax Exemption O      
ALKY Alternate Key O   F0101  
PHTP Phone Type O     DD
CRTE Carrier Route O     DD
BKML Bulk Mail O     DD

A.9 Table 4 - Ignored Fields

If you enter data into these fields, the functional server does not pass it to the JD Edwards World fields. The Address Book Batch Processing program (P01110Z) supplies blank, zero, or the default shown in the table below.

Field Description Value Default
IDLN Line ID in Who's Who    
RCK7 Line Number    
DSS5 Display Sequence    
IDLN Line ID    
EFTB Effective Date    
DC Description - Compressed    
AT2 AR/AP Netting    
AT3 Address Type 3    
AT4 Address Type 4    
AT5 Address Type 5    
CFCE Crt Fin Chg Entry    
CKHC Credit Check Handling    
RVNT Revenue Netted    
MNSC Min Check Code    
FOTC Foreign Owner    
WPTC WPT Ind/Non    
GLBA G/L Bank Code    
RMK Remark    
PTI Time Scheduled In    
PDI Date Scheduled In    
DAOJ Date Account Opened    
POPN Person Opening Account    
DSO Days Sales Outstanding    
AB2 Miscellaneous Code 2    
AB3 Miscellaneous Code 3    
UPMT Time Last Updated   System
USER User ID   System
PID Program ID   System
UPML Date Updated   System
JOBN Work Station ID   System