Trace file not capturing info from Fluid page

Nan_123

We're on Peopletools 8.59.11

In new FSCM 9.2 PUM 44 eProcurement Fluid 'ScheduleDetails' page, I'm getting this error message and I don't know why.

So I turn on Trace - both Peoplesoft and SQL trace - and I can't find anything related to what I just did. Is this a Fluid issue?

The TRACE file is not tracking my input value - The FieldChange for the field is not being invoked at all per the trace file.

This is my issue -> the Trace file is not capturing anything helpful from the Fluid page. I can't tell which code it was trying to do which caused the issue.

Here is extra info:

1- Getting 15, 1 error "Cannot change current or history records unless in Correction mode". It doesn't make sense because I'm in Add mode. (which in ePro Fluid pages Add mode is not Add mode - it uses a flag in the component interface).

2- SQL trace value 3, Peoplesoft Trace (I've tried 4044 and 4060)

THANKS for ANY ideas!!!

Nancy

Nan_123

I should have made this a "Discussion". I can't see what is causing this system error ("correction mode") 15, 1 - in my trace file - even though I am getting a good trace file and I know how to get trace files etc.

I believe the New UI eProcurement system - which is using a Component Interface (CI) from the Old Component - is causing a problem with that.

I believe the Trace file issue I'm having is Because of trying to find out what that pesky CI is doing.

Thanks everyone for your help. :)

Velu Angusamy

Nancy - can you see if the trace is getting generated for any classic page?

Also can you check your TRACEPCmask value in psappsrv.cfg?

Similar issue reported ealier in epro but its fixed in image 38 and i see you are in image 44. can you double check your PS_MAINTENANCE_LOG if Bug 30923618 exist?

Error: "Cannot change current or history records unless in correction mode" While Adding Items From Favorites in Fluid eProcurement Requisition (Doc ID 2739298.1)

-Velu

Nan_123

We generate trace files all the time. I'll try a different page that is still Classic Plus.

We upgraded to Fluid eProcurement in May 2022. PUM 44 has major changes to the epro fluid pages.

In our psappsrv.cfg, we have:

TracePC=0

TracePCMask=4095

I checked the Doc ID - we are on PUM 44 in non-prod environment where my issue is happening. Also, I am not adding Favorites.

I checked ps_maintenance_log and I don't see UPDATE_ID of '30923618'.

select * from ps_maintenance_log where update_id like '30923%' order by dttm_imported desc;

select * from ps_maintenance_log where descrlong like '%30923618%' order by dttm_imported desc; - no rows found

Let me know what you think. THANKS!!

Nan_123

I found we do have that patch. 30923618.

My issue is on the new page that came with PUM 44. PV_MOB_855_DET_SBF. The error comes from a field that I added on the page from a work table PV_MOB_WRK.

Velu Angusamy

ok good. then lets step back to your trace issue.

Did you enable the trace for classic plus or classic and also from where you are enabling the trace?

Also i recommend to enable the trace as below in psappsrv.cfg file for testing.

TracePC=4044

TracePCMask=0

-Velu

Nan_123

We use the online Trace pages to set TracePC. Navigation is Menu /Peopletools / Utilities /Debug/ Set PeopleCode Trace Options. This sets the trace for only my session.

As far as TracePCMask = 4095, this is the recommended by Oracle value.

I can't just change our config file, because we have a lot of developers working now and I probably don't have write access to it anyway.

Abhiram Ch-Oracle

Hi,

Instead of Utilities -> Debug -> Peoplecode Trace Options page, did you try appending &Trace=Y on the PIA login page and select the required checkboxes for the Peoplecode? If you didn't test this, please give it a try and let us know.

Thanks

Abhiram

Nan_123

Hi Abhiram,

I don't see that flag on our sign on page. We use some utility to sign on with.

Perhaps I'm not clear, I am getting a Trace file but it isn't giving me enough information - and I thought it is due to it being a Fluid page/component and not a Classic one.

I guess I am just complaining that I can't get what I need to know why the error (15, 1) pops up.

oh well.

Thank you for your interest!!! :)

Nan_123

I should have made this a "Discussion". I can't see what is causing this system error ("correction mode") 15, 1 - in my trace file - even though I am getting a good trace file and I know how to get trace files etc.

I believe the New UI eProcurement system - which is using a Component Interface (CI) from the Old Component - is causing a problem with that.

I believe the Trace file issue I'm having is Because of trying to find out what that pesky CI is doing.

Thanks everyone for your help. :)