Peoplesoft FSCM 9.2无法查看申请单打印版本报错求助

Hey there! Let's break down how to troubleshoot this error you're hitting in PeopleSoft FSCM 9.2. That "First operand of . is NULL" error is a classic PeopleCode issue—it means your code is trying to access a property or method on an object that hasn’t been initialized (it’s null). Since you already have the trace file pointing to the error line, let’s walk through actionable steps to fix this:

1. Dig into the traced PeopleCode line #

Head straight to the exact line in your trace where the error is thrown. Look for code that uses a dot (.) to access something like &someObject.Property or &someObject.Method(). The "first operand" is the part before the dot—so that object (&someObject) is null here. Ask yourself:

• Was this object supposed to be populated from a record, component buffer, or a function call?
• For example, if it’s a requisition record object, did the code properly fetch data using GetRecord() or CreateRecord() before trying to access its fields?

2. Verify the worklist entry’s requisition context #

The worklist item links to a specific requisition, but maybe the requisition ID tied to that worklist entry is invalid, missing, or you don’t have permission to access it:

• Check the worklist record (likely WORKLIST or an FSCM-specific related record) to confirm key fields like REQUISITION_ID are correctly populated for the problematic entry.
• Test with a requisition you know exists and have full access to—does the printable version work for that one? If yes, the issue is isolated to specific worklist entries.

3. Check how the printable link passes parameters #

The "View printable version" link probably triggers a PeopleCode function or navigates to a component that generates the printable output (like a BI Publisher PDF or a print-optimized page):

• Make sure the link is passing all necessary requisition key fields from the worklist to the target component/function. Missing parameters often cause the target code to fail to find the requisition object, leading to the null error.

4. Validate the component buffer and data #

If the error is in component PeopleCode (like RowInit, FieldChange, or ComponentPostBuild):

• Check if the component buffer has the requisition record loaded. You can add temporary trace statements to confirm the object’s value before the dot operation, like:

  MessageBox(0, "", 0, 0, "Requisition Record Object: " & &requisitionRec);
  

  This will show you if the object is indeed null, helping you narrow down why it wasn’t initialized.

5. Check for known bugs or patches #

Sometimes this error is a documented issue in FSCM 9.2. Check the PeopleSoft support portal for patches related to requisition printable versions or worklist link functionality. Search using keywords like "First operand of . is NULL", FSCM 9.2, and requisition to find relevant fixes.

A quick note for new PeopleSoft devs: Always test changes in a non-production environment first, and don’t hesitate to enable more detailed tracing (like record buffer tracing) if you need to see exactly what data is being passed between components.

内容的提问来源于stack exchange，提问作者Nick