E1: 43: processPurchaseOrder Sets Error 037 The address number entered is not found in the Address Book Master file (F0101) (Doc ID 2255436.1)

Last updated on APRIL 14, 2017

Applies to:

JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.0 and later
Information in this document applies to any platform.

Symptoms

On : 9.1 version, BSSV

When attempting to create a purchase order via Procurement Manager BSSV(JP430000) the following error is set.
ERROR
-----------------------
CAUSE . . . . The address number entered is not found in the Address Book
  Master file (F0101).
RESOLUTION. . Enter a valid address number.

Steps to Duplicate:

1) P01012. For address book 6031 (BP 30) add an effective of 04/10/2017 and click OK. For address book 4343 (demo supplier) add an effective of 04/13/2017 and click OK.
 
2) Run the R01840 over both of the AB records. This will populate the F0101 with the effective dates. At this point there will be some extra records that need to be deleted in the F0116. This is because when the data was first added a F0116 record was created with no effective date. To mimic the effective date being entered when the data was first created you will need to delete all records with dates different than above using SQL developer.

3) P04012. For supplier 4343 go to the EDI tab and verify the Send Method is not equal to 5. A value of 5 is what is required to enable RTE outbound events.
 
4) P40040. Inquire on doc type OP and on the Procurement tab uncheck Publish Externally.
 
5) P90701A. Take the form exit to event activation and for RTSOOUT set the status to inactive. Clear cache on the enterprise server. At this point we have turned off RTE in all 3 relevant areas.
 
6) SoapUI. Create a payload for processPurchaseOrder JP430000 using BP 30 and supplier 4343 for a stock item. Submit. The following error is set.
CAUSE . . . . The address number entered is not found in the Address Book
  Master file (F0101).
RESOLUTION. . Enter a valid address number.
 
Review the debug logs and note PurchaseOrderRealTimeWrapper gets executed then goes through a bunch of AB logic where the error is set even though RTE is turned off. The error occurs because PurchaseOrderRealTimeWrapper calls GetAddressForOP which gets the effective date 04/10/2017 from the F0101 of AB 6031 for BP 30 then passes it back out to PurchaseOrderRealTimeWrapper which then calls GetAddressForOP again for the supplier 4343 and passes in 04/10/2017 as the effective date. GetAddressForOP then looks for 4343 in the F0116 where the effective date <= 04/10/2017 and since the effective date is 04/13/2017 it does not find the record and sets the error.

7) Repeat the above test in the 9.2 release and the error will not occur. Review the logs and note PurchaseOrderRealTimeWrapper gets executed then exits immediately without calling the addition AB logic as in 9.0.

-----------------------
The issue has the following business impact:
Due to this issue, users cannot create a PO via BSSV.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms