# Infor LN Report Designer: How to Build and Personalize Reports

> Source: https://netray.co/erp-help/infor-ln-report-designer-personalization-guide
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

Infor LN reports are designed in LN Studio's report designer, where a report is defined by its input fields, data selection through the session's tables and a layout of sections. To personalize a standard report, copy it into your customer VRC and edit the copy, never the standard object, so upgrades do not overwrite your work.

## Kind

how-to

## System

infor-ln

## Erp

Infor LN

## Module

Tools / LN Studio / Reports

## Query

infor ln report designer

## Alternate Queries

- infor ln report personalization
- infor ln report designer development guide
- infor ln soc report
- how to customize a report in infor ln

## Applies To

Infor LN 10.x with LN Studio. Session and menu names vary a little by version and tools level.

## Steps

### Personalize a standard LN report safely

**Items:**

- Identify the report code and the session that prints it. In the session, use the report selection to see which report is linked, and note the package and module.
- Open LN Studio and find the report object. Check which VRC (version, release, customer) currently supplies it.
- Copy the report into your customer VRC or the VRC your tools administrator designates. Work on the copy only.
- Open the copy in the report designer. Adjust layout sections (headers, details, footers), fields, fonts and any logo or label text.
- Add or remove input fields only if the print session also supplies them. A new input needs matching session logic.
- Use report script for formatting and calculated values. Keep it small, and move business logic to the session or DAL where possible.
- Compile or convert the report to its runtime form, then test with real print data and the print devices used in production.
- Document the change and keep it in your customization register for the next upgrade.

## Sections

### How an LN report is put together

**Body:**

A report in LN is not a freestanding file. It belongs to a package and module, is linked to a print session, and receives its data from the fields that session exposes. The designer arranges those fields into layouts: report header, page header, detail lines, group footers and report footer.

That structure explains a common frustration. If the value you want is not among the fields the session passes to the report, no amount of layout editing will add it. You need a session or script change to supply it.

### Personalizing without breaking upgrades

**Body:**

LN separates standard objects from customer objects with VRCs. Customizations placed in a customer VRC survive upgrades because the standard VRC is replaced while yours stays in the stack and takes precedence at runtime.

The rule is to copy, then change. Editing a standard report in place, or exporting and re-importing it over the standard VRC, is what causes lost modifications and unexplained behaviour after the next service pack.

### A note on 'SOC' reports

**Body:**

People searching for an 'LN SOC report' usually mean a sales order confirmation, the document sent to a customer after an order is entered. That report is printed from the Sales Control area, and the personalization steps above apply to it like any other: copy to your VRC, edit the layout, test.

If your organisation uses SOC to mean something else, such as a system or security report, the same designer applies, but identify the report code first rather than searching by acronym.

### A development workflow that scales

**Body:**

Keep a development environment where reports are changed and a test environment where users approve them. Move changes with the LN-supported export and import path rather than copying files by hand.

Version your report script in source control outside LN as well. The inside-LN copy is the running one, but an external copy gives you diffs and history.

**Code:**

Typical change record
Report: <code>   Session: <print session>   VRC: <customer VRC>
Change: add customer part number to detail line
Source field: supplied by session? yes/no
Tested on: <environment>, <printer or PDF>
Approved by: <name>, <date>

## Pitfalls

- Editing the standard VRC report directly, so the next upgrade silently replaces your change.
- Adding a field to the layout that the print session never supplies, producing blank output.
- Putting heavy business logic in report script, which slows printing and hides rules from developers.
- Testing only on screen preview and not on the production printer or PDF device.
- Not recording customizations, so nobody knows what to re-test after an upgrade.

## Ai Angle

Report requests are often really data questions, such as 'which open orders print late each week'. Netray's private assistant on Infor LN answers those in plain language over your data, read-only and on-prem, which removes many one-off report requests. When a true printed document is still needed, it can draft the change record and review report script, with a developer approving the change.

## Faq

### Where do I design reports in Infor LN?

**Answer:** In LN Studio, using its report designer. You open the report object, arrange layout sections and fields, and add script if needed. Reports are tied to a print session, which determines the data that is available to them.

### How do I customize a standard Infor LN report?

**Answer:** Copy the standard report into your customer VRC and edit the copy. The customer VRC takes precedence at runtime and survives upgrades, whereas edits to the standard object may be overwritten.

### Why is my new field blank on an LN report?

**Answer:** The report can only print fields the print session passes to it. If the field is not part of the session's report fields, add it in the session or its logic first, then place it on the layout.

### Can I move report changes between LN environments?

**Answer:** Yes, use the LN-supported export and import of customer VRC objects, then test in the target environment. Avoid manual file copying, which loses dependencies and makes the change hard to track.

## Search terms

infor ln report designer, infor ln report personalization, ln studio report, infor ln customize report, infor ln customer vrc, infor ln sales order confirmation report, infor ln report script, baan report designer

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
