Advanced Benefits - PSFT (MOSC)

MOSC Banner

PYLOAD ABEND with Transaction Status stuck at X?

edited Mar 30, 2022 1:27PM in Advanced Benefits - PSFT (MOSC) 1 commentAnswered

Something has changed since PUM33 and the new Paysheet load enhancement.

In the past, when the PYLOAD process went to no Success, we would find the EE's with the bad data, mark the transaction Inactive, and reprocess the Load to success.

But we have Transactions with the PU_TXN_STATUS stuck at "X" and we can't pull them up on the "Update Paysheet Transactions" page to inactivate to fix it!

How do we recover?

We found Doc ID , 2679834.1 that describes a similar issue. We verified COBOL source code against what was delivered in PUM33. Is there another cause?

Tagged:

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

PSFT Benefits Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center