Document Text from Inventory Part not displaying on Analysis Results

Hi.  I found the following information which should help you with this -

Root Cause: Why the Document Text is Not Displaying

You have configured Output Type ("CoA") and Document 73 (Analysis Results) correctly. However, the reason the text does not appear on the report comes down to how the IFS Document Text framework links document codes to underlying business objects (Logical Units / LUs):

1. Document Code 73 is Linked to Quality Objects, Not Inventory Part Master:

   • When ANALYSIS_RESULT_REP (Document 73) executes, the report driver searches for Document Text attached specifically to Quality Management LUs—primarily Analysis and QmanControlPlan / QmanControlPlanLine.

   • It does not automatically query master data LUs like InventoryPart. Even if the Document Text on the Inventory Part uses Output Type CoA and Output Type CoA is attached to Document 73, Document 73 does not traverse up to the InventoryPart LU during report generation.

2. Master-to-Transaction Flow Limitations:

   • Document Text attached to InventoryPart is intended for inventory/supply chain documents (e.g., Purchase Orders, Customer Order Confirmations, Pick Lists).

   • It does not automatically copy down or inherit to Control Plan or Analysis transactional headers upon creation.

How to Fix / Work Around This Setup

Depending on your operational process, you have three options to make this text display on the Analysis Results report:

Option 1: Attach Document Text to the Control Plan (Recommended Standard Approach)

Instead of attaching the text to the InventoryPart master record:

1. Open the Control Plan - Inventory (or Manufacturing/Purchasing Control Plan) for the part.

2. Go to Document Text on the Control Plan Header (or Control Plan Line).

3. Add the inspection text and set the Output Type to CoA.

4. When an Analysis is created and completed from this Control Plan, ANALYSIS_RESULT_REP (Document 73) will fetch and print the Control Plan's Document Text on the Certificate of Analysis / Analysis Results report.

Option 2: Attach Document Text Directly to the Analysis Record

If the inspection text is specific to a particular lot or analysis instance:

1. Open the Analysis record.

2. Add Document Text directly to the Analysis Header or Analysis Line/Norm.

3. Assign Output Type CoA.

4. Print the Analysis Results report.

Option 3: Extend the Report / RDF (If Text MUST Live on Inventory Part Master)

If business rules mandate that the text must be managed at the central Inventory Part master level and automatically print on every Analysis Result:

• The report logic (ANALYSIS_RESULT_RPT / Analysis_Result_Rpk) or report view needs a minor custom extension to fetch Document_Text_API.Get_All_Notes() for LU = 'InventoryPart' using the Contract and PartNo from the analysis.

Additional Setup Checklists to Verify

If you test Options 1 or 2 and text still does not appear, verify the following:

• Language Matching: Ensure the Language Code of the Document Text is set to * (All Languages) or matches the Language Code of the Site/Customer/Report execution context.

• Document Text Status: Ensure the Document Text status is active/valid for the date of the analysis.

Setting Up Document Text on Control Plan: Lines vs. Headers

The key distinction is scope — header-level text applies to the entire Control Plan / all analyses run from it, while line-level text is tied to a specific characteristic/norm being measured.

Header-Level Document Text

Use when: The inspection note or customer-facing text applies to the entire part or analysis (e.g., general inspection instructions, certification statements, part-level quality notes).

Setup Steps:

1. Navigate to Quality Management > Control Plan > Control Plan - Inventory (or Manufacturing/Purchasing depending on your flow).

2. Search for and open the Control Plan for your Inventory Part (Part No, Revision, Site).

3. On the Control Plan Header record, locate the toolbar or right-click context menu and select Document Text.

4. In the Document Text window:

   • Output Type: Set to CoA (your custom Output Type connected to Document 73).

   • Language Code: Set to * for all languages, or specify the customer language if required.

   • Enter your inspection text in the text body.

5. Save the Document Text record.

6. When an Analysis is created from this Control Plan and the Analysis Results report (Document 73) is printed, the header text will appear on the report for every analysis tied to this Control Plan.

Line-Level Document Text

Use when: The text is specific to a particular characteristic, norm, or test parameter on the Control Plan (e.g., specific measurement method notes, tolerance rationale, instrument-specific instructions for a single inspection point).

Setup Steps:

1. From the same Control Plan - Inventory header, scroll down to or navigate to the Control Plan Lines tab/section.

2. Select the specific Control Plan Line (characteristic/norm) you want to annotate.

3. Right-click or use the toolbar to select Document Text on that individual line.

4. In the Document Text window:

   • Output Type: Set to CoA.

   • Language Code: * or customer-specific.

   • Enter the text specific to that characteristic or test step.

5. Save.

6. When the Analysis Results report prints, this text will appear adjacent to or beneath that specific norm/characteristic result row — keeping it contextually tied to the measurement rather than the whole analysis.

Header vs. Line: Side-by-Side Comparison

Important Behavior Notes

• Text Inheritance at Analysis Creation: IFS copies Document Text from the Control Plan to the Analysis record at the time the Analysis is created. This means:

  • Changes to Document Text on the Control Plan after an Analysis is already created will not retroactively update the printed text on that Analysis.

  • If your CoA text changes (e.g., revised inspection statement), you need to either update the text directly on the open Analysis record or create a new Analysis.

• Multiple Output Types: A single Control Plan Header or Line can carry Document Text records for multiple Output Types simultaneously (e.g., one entry for CoA, another for INTERNAL). Only the text matching the Output Type of the report execution context will print.

• Language Fallback: If a language-specific entry exists but the report runs in a different language, IFS falls back to the * (All Languages) entry — always keep a * entry as a safety net.

I hope this information helps you in setting this up.  Thanks!  Jane

​@Jane Perry it would benefit all users if IFS would document how the IFS Document Text framework links document codes to underlying business objects. In the ‘About’ documentation, create a table that explains that document text on Object A will appear only on Documents X and Y in positions 1, 2,….

​@Jane Perry  -  I appreciate your very well written and thorough response.  It’s almost like it was generated by CoPilot or some other AI system.  I have a “trust, but verify” policy when it comes to any AI generated solutions.  

Perhaps you could explain to me where the Document Text option is on the Control Plan - Inventory Header, or Control Plan Lines?  

Or the Analysis Results screen?

Hi ​@gamacg  I will review this and provide an update shortly.  Thanks!  Jane

Hi ​@gamacg   Under Documents - there is a ‘Document Phrase Support’ column.  Document 73 as well as some other Documents show that they are not supported.  They are not supported by Document Phrase.

You can’t add the Doc Text to the Inventoty Part and have it carry over to the Analysis Results.  You can manually enter the Doc Text on the line(s) of the Analysis Results.

In IFS Cloud / IFS Applications, if Document 73 (or a specific Document Code / Report ID) does not pull or display Document Phrases (or Document Text), it is typically due to one of the following setup or framework restrictions:

1. Document 73 is Not Connected to an Output Type

Document Phrases are governed by Document Text Output Types (e.g., ALL, PURCHASE, QUALITY).

• If Document 73 is not listed or checked under Output Type per Document Type in basic data, the reporting engine will not filter or pass phrases to that document layout.

2. The Report Data Method (RDF) Lacks Document Text Calls

For a document/report to support Document Phrases in IFS:

• The underlying business logic (RDF file / Report API) must explicitly execute Document_Text_API.Get_All_Notes() or Document_Phrase_API.

• Certain system-generated operational documents or specialized reports (such as Document 73) were not coded with native Document Text dataset hooks out of the box.

3. Phrase Status or Language Mismatch

• Status: Phrases must be in the Released state. Phrases set to Planned or Obsolete will not be pulled during document rendering.

• Language: If Document 73 is printed in a specific language (e.g., US, SE), the connected Document Phrase must either have a valid translation in that language or a default language rule configured.

4. Missing Object Linkage Rules

• Document Phrases attached to master records (such as Inventory Parts, Customers, or Suppliers) only carry over if the transaction process explicitly inherits document text onto the document object line.

If you would like, an enhancement request could be created to RnD to make Document 73 available so that you could enter Doc Text on the Inventory Part and have that flow through to the Analysis Results.

If you create a case, this could be reported to RnD for confirmation, (reference this conversation) and then once RnD confirms my findings, the enhancement request could be entered.  I hope this helps but please advise if there are other questions.  Thans!  Jane

I disagree with this.  A Document Phrase is intended to make a Phrase print on EVERY document of a certain type.  

It seems that this feature is poorly developed.  Why even list the Documents if the Document Text functions doesn’t work.  Either remove the non-functional Documents, or add the Document Text options to every projection that would impact printing one of the already configured Document types, and update the canned report to work properly.  

Hi.  I have continued this investigation and also did additional testing to confirm these findings -

The document text maintained on an Inventory Part does not print on an Analysis Result report because the Analysis Result transaction and report do not automatically inherit or expose Inventory Part document text as part of the Analysis Result data set. Based on the available Quality Management documentation, Analysis Results are linked to the part, lot/batch, and serial information used during quality processing, but there is no indication that Inventory Part document text is transferred to the Analysis Result or included in the standard report output. 

As a result, adding document text to the Inventory Part does not make that text available for printing on Analysis Result reports unless the report has been specifically modified to retrieve the text from the Inventory Part record. If the text is not available in the report data source, this is expected behavior rather than a reporting issue.

If there is a business requirement to include Inventory Part document text on Analysis Result reports, a report customization or product enhancement would likely be required to expose and print that information. 

Why doesn't the document text print?

• Document Text is stored against the Inventory Part master data.
• Analysis Results use their own Quality Management data structure.
• The standard Analysis Result report dataset does not appear to include Inventory Part Document Text. [IFS Cloud...ntrol 2025 | PowerPoint]
• Since the field is not exposed to the report, the report cannot print it.
• This should be considered expected behavior

If you would like, you can use all or part of the following to enter an enhanceet request.

Enhancement Request: Print Inventory Part Document Text on Analysis Result Reports

Title
Expose and Print Inventory Part Document Text on Analysis Result Reports

Product Area
Quality Management / Inventory Management / Reporting

Business Requirement
Customers maintain important quality, compliance, handling, testing, and certification information in the Document Text associated with an Inventory Part. When generating an Analysis Result report, users need this information to be included automatically in the report output so that quality personnel, customers, and auditors can view all relevant product information in a single document.

Current Limitation
The Inventory Part Document Text does not appear on or print from the standard Analysis Result report. Although Analysis Results are linked to the Inventory Part, the Document Text maintained on the part is not exposed within the Analysis Result reporting dataset and therefore cannot be included through standard report configuration. Based on the available Quality Management documentation reviewed, Analysis Results are associated with part, lot/batch, and serial information, but no standard functionality was identified that transfers or prints Inventory Part Document Text on Analysis Result reports.

Requested Enhancement
Provide standard support for Inventory Part Document Text within Analysis Result reporting by:

• Exposing Inventory Part Document Text in the Analysis Result report dataset.
• Making the text available as an attribute in Report Rules.
• Allowing the text to be included on standard Analysis Result reports and Certificates of Analysis.
• Providing an option to automatically include the latest active Document Text associated with the Inventory Part.

Business Value

• Reduces duplicate maintenance of quality-related text.
• Ensures consistent information between Inventory Parts and quality documentation.
• Improves customer-facing Certificates of Analysis and test reports.
• Supports regulatory and audit requirements.
• Eliminates the need for report customizations to retrieve standard Inventory Part information.
• Improves usability by allowing quality and product information to be maintained in a single location.

Expected Result

When an Analysis Result report is generated for an Inventory Part that has Document Text defined:

• The Inventory Part Document Text should be available in the report dataset.
• Administrators should be able to select the text through Report Rules.
• The Document Text should be printable on Analysis Result reports and related quality documents.

Current Workaround

Customers must maintain the same text separately within Quality Management processes or implement a custom report modification to retrieve the Document Text from the Inventory Part master record.

Priority Justification

Medium to High

This enhancement would improve the integration between Inventory Management and Quality Management, reduce administrative effort, and provide a standard solution for a common reporting requirement without requiring report customization.

Please advise if you have any questions.  Thanks!  Jane