| Purpose |
| Questions and Answers |
| Country Constant Questions |
| Question 1: Why is the country name not showing in the vendor address portion of accounts payable check? |
| Question 2: Why does the Formatted Address with Who's Who (B0100067) incorrectly formatting the Mailing Name to print after Address Line number 1? |
| Question 3: Which programs are impacted when changing the address format for a country in the Country Constants (P0070)? |
| Address Book User Defined Code (UDC) Questions |
| Question 1: What is the purpose of the special handling code in UDC 00/CN? |
| Question 2: How can UDC 00/S be used for states from different countries, if these states have the same abbreviation, e.g. AL is Alabama (US) but is also Alagoas (Brazil)? |
| Question 3: When an Address Book record contains a space in the Alpha Name, why is this space value included in the Description Compressed’ field (ABDC) in the Address Book Master (F0101)? |
| Question 4: Error: Why does the system trigger error ‘Not found in User Defined Code xx/xx’ for various Address Book UDC values although there is no value in the specified field? |
| Address Book Category Code Questions |
| Question 1: How can Category Codes in the Address Book be made mandatory for the user to input a value? |
| Question 2: Can Address Book Master Category Codes (P01012) be updated to the Customer Master Category Codes (P03013) after a customer AB record has been created? |
| Question 4: Is it possible increase the length of the category code fields? |
| Next Number Questions |
| Question 1: Why are Address Book Next Numbers Skipping Sporadically? Next Numbers by Company is not active and Check Digit functionality is not active. |
| Question 2: What happens when the maximum next number is reached in Address Book? |
| Audit Log Questions |
| Question 1: Is it possible to keep an audit trail log for the Address Book system to track changes? |
| Question 2: Does JD Edwards EnterpriseOne provide reports showing Address Book Audit Log information? |
| Question 3: When you have A/B interoperability activated in MBF P0100041 so that the system creates records in the F0101Z2 table, should the system be creating entries in the Subsystem Waiting Jobs? |
| Question 4: Can user-defined Transaction Types be used for outbound Address Book Audit Log functionality? |
| Question 5: When a phone number whose line ID is greater than 2 is changed, the changes are not recorded in interoperability table F0101Z2? |
| Question 8: When a change is made to an address book record in World, the system updates the F0101A table to reflect the changes. Why is this table not being updated in EnterpriseOne? |
| Question 9: What are the different types of Transaction Action codes (TNAC) used for Address Book or Customer Master Outbound Interoperability? |
| Question 10: Can Outbound Interoperability records be purged? |
| Effective Address Date Questions |
| Question 2: Why does the Update Effective Address UBE (R01840) produces a blank report (only the headers are printed)? |
| Question 3: Why is it necessary to run the Update Effective Address UBE (R01840) with data selection "Where effective date existence (F0116) is not equal to 1"? |
| Question 5: Does the Effective Date functionality work for name changes in the address book as well as address changes? |
| Question 6: Does the Update Effective Address UBE (R01840) automatically call R730101 to update invalid geocodes when vertex is being used? |
| Question 7: Why is the Update Effective Address UBE R01840 updating F42140 end date and expiring customer master commission records? |
| Question 8: Under what circumstances does the Update Effective Address (R01840) update the Tax Rate Area in the Customer or Supplier Master tables? |
| Address Book Word Search, Word Search Build (R01BDWRD) Questions |
| Question 1: What is User Defined Code (UDC) H95|SC used for? |
| Question 2: Which Business Functions (BSFNs) use UDC H95/SC? |
| Question 3: What settings are required to get expected results in the stripping of a string? |
| Question 4: During runtime, what kind of BSFNs make use of this settings? |
| Question 5: How is BSFN "B0100009 - CompressCharacterString strips special characters" defined in the Description001 column in UDC H95/SC? |
| Question 6: Can its definition change? Will there be any impact? |
| Question 7: Is there any batch application which can update F0101.ABDC and F0111.WWDC columns? |
| Question 8: Are there any other considerations when setting up Word Search? |
| Question 9: When searching by the first letter of the Alpha Name, why are not all records displayed? |
| Question 10: Which fields are included when running the Address Book Word Search Build (R01BDWRD)? |
| Address Book Word Search Common Errors |
| External Mail Questions |
| Question 2: Where can I store external e-mail addresses for contacts, such as suppliers and customers, within Address Book? |
This document provides answers to frequently asked questions about initial Address Book set up.
Answer 1: The issue may be caused by one of the following setup being incorrect:
Answer 2: The order in which the Mailing Name and Address Lines are formatted by the Formatted Address with Who's Who (B0100067) BSFN is determined by the Attention Placement (ATTP) field in the related Country Code's Country Constants (P0070). If you want the Mailing Name to print prior to the rest of the address, this field needs to be set to a 2. For more information on this business function and this set up, please see E1: BSFN: Information on Business Function B0100067-Formatted Address With Who's Who (Doc ID Information on Business Function B0100067-Formatted Address With Who's Who).
Answer 3: Please find below a list of programs that are impacted by the change:
Answer 1 The special handling codes in UDC 00/CN are the ISO 3166-1 numeric (or numeric-3) codes which are 3-digit country codes in the ISO 3166-1 standard to represent countries and dependent areas. They are published by the International Organization for Standardization (ISO) as part of its ISO 3166 standard, and correspond to the 3-digit country codes developed and maintained by the United Nations Statistics Division. See the following website for more information on the ISO 3166-1 standard: ISO - Maintenance Agency for ISO 3166 country codes.
Example: For Singapore the 3-digit code is set as 702. For United States it is 840. These special handling codes defined in 00/CN are hard coded and should not be amended. The system needs this information when validating for country specific bank accounts, tax accounts, etc. It is needed for the system to recognize which country specific algorithm to use.
Answer 2: This issue has been documented in the following enhancement bugs and may be considered in future releases:
Workaround: Since the System allows entering 3 characters, the UDC code can be defined in such a way that one distinguishes the other. Eg. AL is Alabama (US) and A.L Alagoas (Brazil),
Answer 3: For Example: Address Book record ‘Dominic Abbot’ is written in the Compressed field (ABDC) as ‘Dominic Abbot’ instead of ‘DominicAbbot’ (no spaces). The Address Book Master (F0101) Compressed field (ABDC) will contain spaces if UDC H95/SC does not have a space (blank) value as a special character. To correct this issue, add a space to the UDC table. Note – the UDC table is limited to 30 special characters; it may be necessary to delete one of the special characters to insert a space (blank) value. Alternatively, apply the two ESUs per the instructions of Knowledge Article Document 834004.1 E1: FDA: Spaces Being Included in Description Compressed Field (ABDC) in F0101 Table Cause Issues with Address Book Search, to correct the business function Create Compressed Description (B0100009), and to correct and add to UDC table H95|SC.
To correct existing F0101 records, you need to inquire on individual records and select them, then click OK.
To update the Description Compressed(ABDC) after changing the UDC H95/SC run the R01302 - F0101 Description Compressed Conversion.
Answer 4: The system may trigger this error if blank is not a valid value in the UDC table. Add blank to the UDC table to be the default value.
Answer 1: As with other User Defined Code (UDC) tables, many of the address book category code UDCs allow a blank value as a default. In order to make an entry mandatory for that Category Code the blank value should be deleted from the corresponding UDC table to force the user to select a valid value.
Answer 2: The Copy Category Codes to Customer Master (R01050) can be run to update the category codes for Customer Master records with changes that you make to Category Codes in the Address Book for existing records.
Answer 3: Global Category Code Update UBE (R01490) is delivered with Version XJDE0001 with 1 Medium Security for User Exclusive (EXCL) field. By definition, 1 Medium Security: Only the "Last Modified By" user can design, change processing option values, change detail values, check in, check out, or delete the version. Anyone can install, copy, transfer, or run the version.
Create a copy of the version XJDE0001 to modify the processing option or data selection.
Answer 4: As per knowledge articles "E1: DD: Impact of Changing the Size of a Standard Data Dictionary Item (Document 643221.1), and "E1: DD: UDC Values, Code Length and its Impact on How UDC Values are Stored, Displayed and Retrieved (Document 1153684.1), it is not recommended nor supported by GCS to change either the length of a UDC code or the size of a Standard DD item.
Answer 1: Unused Next Number values should not be deleted from the Next Numbers table (F0002). Numerous programs retrieve default numbers from the first position in Address Book Next Numbers (Line Number 01 of System Code 01) if the program cannot find a Next Number defined for the originating system code. Custom programs may also use the default if the appropriate Next Number value cannot be determined.
For example, if the Next Number value for Accounts Payable Debit Stmt Chk# (System Code 04, Line Number 04) is blank and debit statements are processed, the debit statements will be assigned the next available Address Book number. Address Book Next Numbers (System Code 01, Line Number 01) will be incremented.
Additionally if a Data Dictionary Item with a Next Number attached is used incorrectly on a form it may trigger a next number increment. A number of BUGs were raised for multiple applications were this was happening like those documented in:
E1: 01: Address Book Next Numbers Skip When the System Calls Parent/Child Program (P0150/W0150A/P0002) (Doc ID 1634340.1)
E1: 09: Address Book Next Numbers Skip When System Calls the Tax Revision Program (P0018/W0018C/P0002) (Doc ID 1634328.1)
E1: 04: Address Book Next Numbers Skip When System Calls P0411S/W0411SC AN8 (Doc ID 1632848.1)
PROCESS FOR RESOLUTION: Monitor the Next Numbers for Address Book (System Code 01) on a regular basis. Keep a log of the Address Book value in Next Numbers. If the Next Numbers value appears to skip substantially, take note of the new number and the time frame when the number advanced.
Determine which programs were executed during this time frame. Remember to review custom programs. Communication with other areas within the company, such as Accounting, Procurement or Fixed Assets, may be necessary. It will be important to know which programs were run and if the values skipped in the Address Book Next Numbers were assigned to documents in another area.
When the program(s), other than Address Book programs, using Address Book Next Numbers have been identified, set up a Next Number value for the corresponding system code and Next Number line within the system code.
Answer 2: If the maximum number is reached (99,999,999), the system will roll over to 1 and start using any unused number.
Answer 1: Within the Address Book system, JD Edwards EnterpriseOne provides functionality to keep track of actions such as Add, Change and Delete of Address Book records via outbound processing. By enabling the Outbound Processing Options in the Address Book Master Business Function (P0100041), the system will start storing "after" or "before and after" images of records into the Address Book - Interoperability table (F0101Z2). Similar functionality is available in other modules - see KM Doc 1275030.1 for more information.
Answer 2:JD Edwards EnterpriseOne does not provide a standard report that reads the information from the Address Book - Interoperability table (F0101Z2).
Answer 3: The A/B Audit Logging feature is designed to use the Subsystem Processing to create the 'before' and 'after' records. Whilst doing this, the system creates a 'W' status record in the F986113.
This may cause the F986113 to increase in size. If you do not use Subsystem Processing, it is safe to delete those records. Records need to be cleared manually. it is not recommend to use the R00460 UBE to delete these records: the reason you use R00460 is to call another UBE or 3rd party DLL automatically.
Answer 4: This functionality is currently unavailable. However, Enhancement Bug 10842548 has been entered and may be considered for future releases.
Answer 5: This is working as designed. Only the first two phone numbers for an Address Book are updated in F0101Z2 table. Please see Bug 10953745 for more details
Answer 6: Setup the outbound interoperability for JDEAB in P47002/G47261:
Answer 7: When F03012 data gets changed through Approval of workflow 'CREDLIMIT' the system does not write a records to the F03012Z1 table. Interoperability can be used for auditing as a workaround.
A. Interoperability
1. Click OK button on P03013 - Customer Master
2. Call N0100042 - Customer Master - MBF
3. If JDECM is defined at P0100042 for Customer Master MBF Version is defined then write F03012Z1
B. CREDLIMIT workflow
1. When a user change Credit Limit Amount in P03013 send workflow message to Approver
2. Approver clicks 'Approve' button
3. Call NER N03B0159 - F0301UpdateCreditLimitUpdateCreditLimit_Workflow which update table F03012 directly per Customer/Company combination. Since this process does not call P03013 (or N0100042) it is not responsible for writing information into F03012Z1
Answer 8: The F0101A table is no longer used in EnterpriseOne. Instead outbound interoperability is available to create a before and after image in the F0101Z2 table. To activate this functionality, you will need to set the interoperability processing option in the AB MBF P0100047 (in EnterpriseOne). For coexistence customers, the two tables are not linked and do not contain the same information. If a change is made to an address book record (F0101), the change can be seen on both sides. However, to find out who changed the record would require the users to check both audit tables.
It is recommended that clients make all changes either in world or EnterpriseOne to work with consistent audit data.
Answer 9: Following are the Transaction Action codes (TNAC) used for Address Book/Customer Master/Supplier Master Outbound Interoperability:
* 'A' - Add
* 'D' - Delete
* 'UA' - After Update
* 'UB' - Before Update
Answer 10: There is no specific report available to purge the Outbound Interoperability records, but you may consider to review and use Address Book Batch Purge program (R0101Z1P) in order to purge the records created via Outbound Interoperability. Please do note that the R0101Z1P report is generally used to purge the Inbound Interoperability records (records from third party or legacy) but can also be used to purge the Outbound Interoperability records.
Answer 1: The Address Book Master Business Function (P0100041) uses the Effective Date as part of the primary key to fetch corresponding records from the Address By Date table (F0116). Therefore, if an Address Book record is added to the system using an effective date, that date will be used to fetch the address information from the F0116 table for any subsequent inquiries.
To update the Address Book Record, follow the steps below:
a. Enable Address by Effective Date in Address Book in the Address Book Constants (P0000)
b. Clear the cache for the changes to become effective. To clear the cache: the JDE service needs to be restarted on the Enterprise Server, or all running call object kernel processes need to be recycled. See document E1: ENV: Frequently Asked Questions on Caching in EnterpriseOne (Doc ID 944015.1) for more information
c. Inquire on the Address Book record (P01012)
d. Scroll through existing addresses using the Effective Date 'Previous' and 'Next' buttons
e. Add an effective date for the 'new' address
f. Click OK to update record in the database
g. Run the Update Effective Address UBE (R01840)
Answer 2: The report is designed to only print addresses in error when performing the update.
Answer 3: The Update Effective Address UBE (R01840) updates the ALEFTF field with a "1" in the Address by Date table (F0116) for Address Book records that have become effective. The data selection ensures that only addresses that have not previously been processed, are considered by the UBE
Answer 4: The error may be caused by the ‘Date Beginning Effective’ (field EFTB) having a different value in the Address Book Master table (F0101) and the Address by Date table (F0116) for the same record.
The Business Function CheckDuplicateABRecords (B0100088) will perform the following validations:
a. Search the Address Book Master table (F0101) for all records where the ‘Description Compressed’ value (field ABDC) is starting with the ‘Description Compressed’ value of the record you want to update.
For example: The ABDC field for Address Book record 1001 is equal to ‘JDEdwards’ in the F0101 table. When you update Address Book record 1001, the system will search the entire F0101 table for all records where the ABDC field starts with ‘JDEdwards’ and it may find for instance ‘JDEdwards’ and 'JDEdwards EnterpriseOne'.
b. For each of the records retrieved in step a, the system will search the Address by Date table (F0116) for records with the same Address Book number (AN8) and Date Beginning Effective (EFTB). The error ‘Fetch from Table F0116 Failed’ (error number 078I) may be caused when an Address Book Master (F0101) record does not have a corresponding Date Beginning Effective (F0116) record. Usually, the Address Book Master record may have the Date Beginning Effective field (EFTB) set to 0, and no matching Address by Date table record exist. To resolve this issue, you should either update the record in the Address Book Master table (F0101) or the Address by Date table (F0116) so that the system will find the matching record.
Note: Each address number in the F0101 table can have multiple F0116 records for different effective dates. The system will search for the record where the F0101.EFTB is equal to the F0116.EFTB. In order to update the Address Book Effective date, you need to run the Effective Address Update UBE (R01840). This UBE sets the field ‘Effective Date Existence’ (field ALEFTF) to ‘1’ in the F0116 table if the ‘Date Beginning Effective’ (ALEFTB) has been passed. The field will remain blank if the effective date is in the future. Along with this field, the system updates the ABEFTB field in the Address Book Master (F0101) with the effective date for the current address.
Answer 5: No. The Address Book application does not store Alpha Name, Mailing Name, or Secondary Mailing Name changes by Effective Date. There is only one Mailing name and Alpha Name for an Address Number irrespective of the Effective Date and so past names cannot be referenced. The F0116 (Address By Date) table only stores the following details: Address Number, Effective date, Address Line 1, Address Line 2, Address Line 3, Address Line 4, City, State, Postal Code, Country, County and Audit details.
Answer 6: Although the Update Effective Address UBE (R01840) does validate the geocode for suppliers and customers when the address is updated, it does not call the R730101 UBE. The geocode is validated and updated within a business function called directly from the Update Effective Address UBE (R01840).
Answer 7: Whenever a sales team member is manually assigned to the customer, the Sales Team Override Flag has to be set. The Sales Team Override check box is present in Customer Master on the Additional Info form exit on the Customer Segmentation tab.On checking this flag, the sales team can be manually assigned to the customer. To remove the sales team from the customer this flag can be unchecked.
If this flag is set the issue will not duplicate (i.e. the expiration date will not be overridden with today's date). On un-checking this flag the expiry date will be set to system date.
Answer 8: The Tax Rate / Area gets verified when Vertex is On and the address gets changed for a customer/supplier. The report validates the geocode for all the customer and supplier records for which the “Date Beginning Effective”(EFTB)in (F0116) less than today’s date i.e on the date which report is run. The system uses VERTEX to determine if the current tax rate area for a customer/supplier is invalid (based on address and vertex set up) and if it should update it with the new geocode based on the new address provided. When the Update Effective Addresses (R01840) is run, it initially checks if the vertex is active and updates the customer/supplier for which the address is changed with the help of VERTEX.
This program adds GeoCodes to existing address book records. The system stores the GeoCode in the Tax Rate/Area field of either the Customer Master by Line of Business (F03012) or the Supplier Master (F0401) tables. When you run the Update Address Book GeoCodes program, the system updates the
Tax Rate/Area field with the appropriate GeoCode. The system does not update the field if any of these are true:
-The customer master or supplier master does not have a tax explanation code of E, U, or S.
- An address book record crosses multiple tax jurisdictions.
- Not enough information is available for the address in order to find a GeoCode.
-The country code on the address does not match the codes that are set up in the constants for the United States and Canada.
Answer 1. This UDC value will be used when processing an input string of ALPH - NameAlpha that contains any defined characters in the Word Search Build (R01BDWRD) or at runtime. 'Value to strip' is defined at column Description 01 (or if there are more than 30 characters defined Description 02 can be used). The Alpha Name stripped of the special characters is stored in the Address Book Master (F0101) in column Description Compressed (ABDC). And when searches are made by Alpha Name the system will strip the special characters from the search string and the search will be made over the ABDC column. NOTE: Default setting starts with A SPACE followed by ~!@#^&*()_+`-={}|[]\:";'< >?,.
Answer 2: The UDC(H95|SC) will be used mainly by:
Answer 3: This configuration is affected by the following settings
Answer 4: N0100061 - ScrubAddressNumberNER: Usually in distribution module the reason they implement NER is to call P0101SL (as C Code can't call Interactive application)
and B0100016 - ScrubAddressNumber: Except P4210/P4310 this C Code gets called but validation logic will be same
Answer 5: How it handles input value:
* Adding/Changing of F0101.ABDC will be handled by N0100041 which strip off any character define
* During runtime (for example, user has typed in "Cap~" and ~ is defined from UDC (H95|SC))
SQL> SELECT * FROM PRODDTA.F0101 WHERE ( ABDC LIKE 'CAP%' ) ORDER BY ABDC ASC
Answer 6: The definition can be changed. However, do not change value unless there are special instructions installing ESU, upgrading or your are using a special type of keyboard.
Answer 7: R01302 - F0101 Description Compressed Conversion will update column(s) after getting szDescriptionCompressed through B0100009.
Answer 8: If there is any change in UDC (H95|SC) run R01302 again to minimize possible inconsistency. Space in between words will be stripped for double byte language settings whereas it will be maintains when special handling code of UDC (01|LP) is not in (2 or 3)
NOTE: Though Unicode is double byte encoding it belongs to Case 2 implementation
Answer 9: If the first character in front of the first letter of the Alpha Name is a space, those records will not be displayed. The extra space before the Alpha Name needs to be removed for all records to be displayed.
Answer 10: The R01BDWRD UBE is driven by function B0100068 - Address Book Word Search Build. The function follows the processing options set for the UBE.
38 Columns in F0101 – Address Book Master
AN8, ALKY, ALPH, TAX, AT1, TX2, AC01, AC02, AC03, AC04, AC05, AC06, AC07, AC08, AC09, AC10, AC11, AC12, AC13, AC14, AC15, AC16, AC17, AC18, AC19, AC20, AC21, AC22, AC23, AC24, AC25, AC26, AC27, AC28, AC29, AC30, ALP1, EFTB
5 columns in F0115 - Address Book - Phone Numbers
AN8, IDLN, RCK7,AR1, PH1
4 columns in F0111 - Address Book - Who's Who
AN8, IDLN, MLNM, MLN1
11 columns in F0116 - Address by Date
AN8, EFTB, ADD1, ADD2, ADD3, ADD4, ADDZ, CTY1, ADDS, COUN, CTR
3 columns in F0150 - Address Organization Structure
OSTP, PA8, AN8
The above mentioned fields are use to build:
Answer 1: The alpha name in the header and QBE line performs slightly different searches:
The setup in User Defined Code (UDC) table H95/SC will determine how the Compressed field (ABDC) is populated in the Address Book Master table (F0101). UDC table H95/SC contains a list of special characters. For the purpose of this UDC, blank is considered a special character.
If blank is a valid value in UDC H95/SC, then the Address Book records are compressed in the Compressed field (ABDC) in the Address Book Master table (F0101). For example Denver County, will be written as DenverCounty.
If blank is not a valid value in UDC H95/SC, then the Address Book records are not compressed in the Compressed field (ABDC) in the Address Book Master table (F0101). For example Denver County will be written as Denver County.
When the Alpha Name field in the header of the form (P01012) is used to search for a record, Business Function (BSFN) Create Compressed Description (B0100009) will validate the compressed field and UDC H95/SC.
If you have both compressed and non-compressed records, the system will only show part of the record (depending on how UDC H95/SC is set up).
If you want to be able to search on special characters, add the special character to UDC H95/SC. If you have existing Address Book records containing this special character, go back into the Address Book Master record (P01012) and press OK without making any changes. This will write a new compressed description (ABDC) to the Address Book Master table (F0101), and you will now be able to search on this special character. Keep in mind you have to re-save every record you have with this special characters in order to search on it.
Answer 1: In addition to e-mail messages from workflow and submitted jobs, you may also get e-mail from Object Management Workbench (OMW). However, this option can be de-activated. See KM Document 1508543.1 for further information on setting up external e-mail.
Answer 2: E-mail addresses can be stored on the Email/Internet Revisions form (P01111) by selecting the individual’s record on the Who's Who form (P0111), and then selecting Email/Internet from the Row menu. Prior to 8.11 this field was called ‘Electronic Address’.
Note: For further information on Address Book set up please refer to Document 1508543.1 E1: 01: Overview and Set Up of Address Book (P0000, P0007, P0004A, P0002, P0117, P0100041, P0100042, P0100043, P01138, P95922, P01BDWRD, R01BDWRD.