PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

How to stop Handler CI messages from going into the Message Log

edited Jun 20, 2019 10:25AM in PeopleTools and Lifecycle Management - PSFT (MOSC) 10 commentsAnswered

The Message Log page for IB handlers is limited to 50 rows.   I am using a CI that is throwing a lot of info in there and I want to supress most if that.

I tried using &oSession.PSMessagesMode = 0 to no use.   I also tried to purge all the messages via &oSession.PSMessages.DeleteAll() immediately after the failed .Get() or .Save()

Example:

1) I cannot seem to stop generic errors like "No rows exist for the specified keys. "  on a Failed .Get() from being written to the Message Log regardless of what I do. 

2) The CI (HR - Job Data) is throwing informational Warnings out that I want to supress as well.   I know to customizie the code/warnigns by wrap it around %CompIntfcName - but I don't want to customized delivered objects just for this.

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