Asset Lifecycle Management - PSFT (MOSC)

MOSC Banner

Why does AMIF1000 update MAX(CAP_SEQUENCE) on assets?

edited Nov 6, 2019 4:06AM in Asset Lifecycle Management - PSFT (MOSC) 2 commentsAnswered ✓

What is CAP_SEQUENCE and how is it used?

What changed between PI23 and PI32 that requires updating it on the asset record?  What new function is it or is there a bug fix?  I don't want to make changes until I know what this expensive step is trying to do.

We're implementing PeopleSoft Image 32 (PI32).  I tested the same inter-unit transfer of the same three assets in PI23 (current) and PI 32 (adoption).   AMIF1000 runs 40 seconds in the current region.  It requires 5 minutes in the 'improved' PI32. 

AMIF1000 has two SQL updating all assets CAP_SEQUENCE to the maximum CAP_SEQUENCE found on AMIF_IPA_TMP4.  Our max value is 0; the update updates all the assets from 0 to 0 - and takes five minutes to do it.  We have processes that use AMIF1000 for user-initiated updates.  People don't want to wait 5 minutes for the process to complete.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center