# Infor LN Support Ticket Template for Faster Resolution

> Source: https://netray.co/tools/infor-ln-support-ticket-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Write an LN incident report that support can act on the first time: environment, session, steps, error and business impact.

## Category

infor-ln

## Erp

Infor LN

## Audience

- LN administrator
- Key user
- LN developer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Reported by

**Key:** reporter

**Type:** text

**Default:** A. Key user

#### Date

**Key:** date

**Type:** date

**Default:** 2026-10-19

#### Environment

**Key:** env

**Type:** select

**Options:**

- Production
- Test
- Development
- Acceptance

**Default:** Production

#### LN version and feature pack

**Key:** version

**Type:** text

**Default:** Infor LN 10.x, feature pack to be confirmed

#### Session code and name

**Key:** session

**Type:** text

**Default:** Example: tdsls4100m000 Sales Orders

#### Business impact

**Key:** severity

**Type:** select

**Options:**

- System down
- Process blocked
- Workaround exists
- Minor

**Default:** Process blocked

#### Steps to reproduce

**Key:** steps

**Type:** textarea

**Default:** 1. Open the session.
2. Create a new order for item X and partner Y.
3. Save the record.

#### Expected result

**Key:** expected

**Type:** textarea

**Default:** The order is saved and a delivery date is calculated.

#### Actual result and error text

**Key:** actual

**Type:** textarea

**Default:** An error message appears on save. Paste the exact text here.

#### Recent changes

**Key:** changes

**Type:** textarea

**Default:** Describe any patch, solution, customization or setup change in the last weeks.

**Blocks:**

#### LN Support Case

**Body:** Company: {{company}}
Reported by: {{reporter}}
Date: {{date}}
Environment: {{env}}
Version: {{version}}
Session: {{session}}
Business impact: {{severity}}

#### Steps to reproduce

**Body:** {{steps}}

#### Expected result

**Body:** {{expected}}

#### Actual result and error text

**Body:** {{actual}}

#### Recent changes

**Body:** {{changes}}

#### Attachments checklist

**Table:**

**Columns:**

- Item
- Attached

**Rows:**

**0:** Screenshot of the error

**0:** Exact error text or log extract

**0:** Session and form details

**0:** Data example (item, partner, order)

**0:** Custom solution or patch list

#### Reviewed by

**Signatures:**

- Reporter
- Internal LN lead

**Notes:** Check which portal and support route your agreement uses. Remove personal and customer data from attachments you share outside the company.

## Content

**Intro:** A support case with no version, no steps and a screenshot of a crop is a case that comes back with questions. This template collects what a support engineer needs in one pass.

**Sections:**

#### How to use the template

**Body:** Fill the fields while the problem is still on screen. Capture the exact error text rather than paraphrasing it, because messages often contain a code that identifies the cause. State the environment, because the same fault in test and production means different things. Export to PDF or Word and paste or attach it to the case in your support portal or send it to your partner consultant.

#### What support needs most

**Body:** The three most useful facts are the exact version and patch level, the session where it happened, and steps that reproduce it with named data. Without reproduction steps, support must guess, and each question costs a day. If you cannot reproduce it, say so and give the time it happened and the user, so logs can be matched. Also say what changed recently, because most new faults follow a patch, a setup change or a customization.

#### Setting business impact honestly

**Body:** Impact drives priority, so describe it in business terms: orders not shipping, invoices not posting, payroll or month end at risk. Calling everything urgent teaches vendors to discount your next urgent case. If a workaround exists, describe it, because it can lower the priority and keeps the business running while the fix is prepared.

#### Common mistakes

**Body:** Common faults are reporting the symptom without the session, pasting a screenshot with no text, mixing several problems in one case, and forgetting to say whether custom code runs in that area. One problem per case is easier to route and close.

**Cta:** If your team spends hours diagnosing LN errors before raising a case, we can help build a diagnostic assistant that reads logs and suggests where to look.

**Faq:**

#### Do I need the exact LN version?

**Answer:** Yes. The version and patch or feature pack level decide which known issues and solutions apply. Find it from the About information in LN, or ask your administrator.

#### Should I attach customization details?

**Answer:** Yes, if custom sessions, DAL hooks or extensions run in the affected area. Many faults come from the interaction between standard and custom code, and support will ask about it.

#### How do I report an intermittent fault?

**Answer:** Record when it happened, who was logged in, what data was involved and how often it occurs. Intermittent faults need timestamps so server logs can be checked.

#### Can I use this for a partner or internal ticket?

**Answer:** Yes. The structure works for internal helpdesks and consultants as well as the vendor. Adjust the fields to match your ticket tool.

## Search terms

infor ln support ticket, infor concierge case template, erp incident report template, baan bug report template, infor ln error report, erp support request template

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