Troubleshooting Errors With Address Book Number Within EnterpriseOne (P01012)

Purpose of Document

This document provides troubleshooting frequently asked questions regarding errors with Address Book Numbers within EnterpriseOne.

Table of Contents

General Questions

Question 1: What are some common causes of skipping address book numbers?

Answer 1: This may occur as next number is updated as soon as it returns the biggest available number fetched from F0002. Skipping address book numbers is usually related to custom/add-on interactive applications. The Next Number is defined at DD level, when that DD item is requested the BSFN X0010 - X0010GetNextNumber (X0010 - Get Next Number) updates the table F0002 - Next Number - Automatic where F0002.NNSY='01'. If Mobile Sales is implemented the code of N0100041 - Address Book - MBF is not up to date.

Question 2: Is there any standard interactive application which makes use of DD level next numbering?

Answer 2: There should not be any standard application which may make use of DD level next numbering. Across EnterpriseOne system, Next Number will be disabled at Form Level as below.

Note - In most applications, AN8 is a hidden form control to enable the user to input it through search text . In case there is any standard interactive application which does not have 'Disable Next Number' at form level, it will be considered a bug
Currently X0010.c belongs to tools code and it merged into JDEKRNL.dll so they may not have valid code for this.

Question 3: Check if Next Numbers for address book are skipped through add-on interactive application

Answer 3: To list up all the DD items that use of NN(01|1) system code '01 - Address Book' with Index '1' can be verified through UTB or Query tools (any DD items WHERE F9210.NNIX = 1 AND F9210.NSY= 01) The user will have to check if there is any offending interactive application which may make Address Book Number jumps:

  1. List up all the DD Alias(or DD items) using NN(01|1) that return standard DD item or add-on DD item
  2. Run Cross Reference Facilities to check whether there is any object using the listed DD items
  3. Check tables make use of these DD items
  4. Check Business View (custom tables)
  5. Check Interactive application which makes use of these DD items

Note - DD Data Source is shared by multiple environments (DV, PY and PD). F0002 belongs to Control Table data source. If needed, remove next numbering with system code 01 and index 1 through P92001 - Data Dictionary Application

Question 4: How P01012 - Address Book Master sets F0101.AN8

Answer 4: Currently Address Book Number in F0101 - Address Book Master is to be handled by Address Book Master Business Function N0100041 - AddressBookMasterMBF (Address Book - MBF) for both Interactive application P01012 and R01010Z. Although the form W01012A contains AN8 as form control next numbering, it is disabled as it has to be handled through master BSFN in inserting data.

Note - Unlike other master files (e.g., F0901) it does not check/read F0101, which is to give flexibility of numering per Search type. That is, C - Customer can start with 1000000 and V - Vendor can start with 2000000 for example X0010 belongs to JDEKRNL which is system level code (Refer <>)

Question 5: How to check whether NN was updated through a BSFN or a DD trigger

Answer 5: Call stack of calling X0010 will be appeared as below:

Through Trigger
Calling Business function X0010GetNextNumber. Application Name [ ], Version [ ] (BSFNLevel = 1)
Not through Trigger
Calling Business function X0010GetNextNumber. Application Name [P01012 ], Version [ZJDE0001] (BSFNLevel = 3)
: If BSFN gets called through trigger Application Name and Version will be written as blank

Question 6: Are there any known issues with address book number errors?

Answer 6: Yes. See below list of some known issues:

To look at upcoming or archived Advisor Webcasts, please see Advisor Webcast Details <Document 1450327.1> If your topic is not currently scheduled, please suggest it.