My Oracle Support Banner

E1: 17: When R17024 Equipment Master Update Is Run Against an Asset That Is Being Reshipped To Different Site/Customer, Installation Date Is Not Being Updated to the Date when the UBE Run Was (Doc ID 2832917.1)

Last updated on JANUARY 10, 2022

Applies to:

JD Edwards EnterpriseOne Capital Asset Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When R17024 Equipment Master Update is run against an asset that is being reshipped to different site/customer, Installation Date is not being updated to the date when the UBE run was.

STEPS

  1. In P1701 create an equipment with an associated inventory item. They will have the same serial number (=80991). Notice the Site Number [ALKY](=200) , Customer Number [ALKY](=200) and Date Acquired [DAJ](=01/01/20), Installation Date [JCD](=01/01/20).
  2. In P4210, create a new SO for the inventory item and choose the location with the serial (=80991) to a different customer (=4245).
  3. In P4205, ship confirm the SO (so the stock will be deducted).
  4. Be sure to set the PO of R17024 in the Defaults tab to match the P1702 Accounting tab of the equipment. Run R17024 over the SO# (and CO).
  5. Check P1701/P1702 and notice: the Site Number [ALKY](=4245) , Customer Number [ALKY](=4245) have been updated but Date Acquired [DAJ](=01/01/20), Installation Date [JCD](=01/01/20) were not updated.

Note: Some information on the dates can be found in the form ->Locations ->Address Book - >Inquiry (P1704 Work with Equipment Locations) (the Begin Date [EFTB] = 29/01/20 has been updated). This is coming from F1731 table.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.