How is DEFAULT_PROFILE_SW Populated?
(Doc ID 644725.1)
Last updated on JULY 27, 2017
Applies to:PeopleSoft Enterprise FIN Asset Management - Version 8.4 to 9.2 [Release 8.4 to 9]
Information in this document applies to any platform.
***Checked for relevance on 23-APR-2013***
When AMIF1000 was traced, it was discovered that in the procedure 'Check-Default-Profile-ALL', the dynamic WHERE clause ($WHERE_FIXED) for the first iteration, had a blank value. The 'where-clause' ($WHERE_FIXED) is being assigned a value in the procedure Append-Where, which is invoked after the processing of 'Check-Default-Profile-ALL'. When system source changes, the where clause ($WHERE_FIXED) carries the values which belong to the last interface type of the previous system source. This creates an issue as the FAD has a value for DEFAULT_PROFILE_SW of 'Y' and the subsequent RET has a DEFAULT_PROFILE_SW of 'N'.
What happens if the default profile switch is not the same for a system source? This is imperative for a customized program that has been designed as the batch add program would set the profile flag to 'Y' when the assets are added without ACCUM and the same switch would be set to 'N' when assets are added with ACCUM. The issue is that the system source and the interface type for both types of assets loaded would be the same.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!