Why this matters

Inventory discrepancies are often identified, but not fully understood. Without clear visibility into where and why variances occur, teams are left reacting instead of improving processes.

What this solves

The Cycle Counting Variances session (whinh8352m000) provides a visual way to analyze inventory discrepancies, helping teams identify patterns and root causes across warehouses and counting activities.

How it works...

If your company already uses Avalara for tax compliance, you can integrate it directly with your Infor ERP system.

Crossroads RMC has developed integrations that connect Avalara’s automated tax calculation and compliance platform with Infor ERP environments, allowing tax calculations, reporting, and compliance processes to run seamlessly within your existing ERP workflows.

This integration helps eliminate manual tax processing, improve accuracy, and ensure tax compliance as your business grows.

If you’re already using Avalara and want to streamline tax automation within your ERP, Crossroads RMC can help you connect the two.

800.762.2077 | Contact Us

You use LN audit features to fully or partially log changes that users make to the LN database tables when they use LN sessions.

The audit functionality is based on the concept of audit profiles. In an audit profile, you define which tables and fields are audited and when, in the context of an audit profile. To bundle profiles in the same functional area, you can relate the profiles to audit categories. You can export and import audit profiles with various options to enable a quick configuration. The audit trail is stored in sequence files, which are generated for each combination of company and table.

Note: For some important parameter tables it is required that auditing is enabled.

You can view or print the history of modifications.

To avoid having to report quantities also at the order level, set the Post to Inventory when Reporting on Last Operation parameter to Yes in these sessions:

• Production Order Parameters (tisfc0100s000) > Planning tab
• Production Settings by Site (timfc0180m000) > Production Order tab

With regard to as-built handling, because JobControl acts as a reporting tool similar to the Machine Work List (tisfc4600m000) session, we recommend these settings in the Production Order Parameters (tisfc0100s000) session (Miscellaneous tab) and Production Settings by Site (timfc0180m000) session (Production Order tab):

• In the Serials section, set the Generate Serial Numbers parameter to On Printing Documents or On Release as the serial number that can be selected in JobControl to report completed or rejected products must have the Valid status in LN.
• In the Serials section, we recommend setting the As-Built Status Handling parameter to Manual as the serial number assignment is performed in JobControl.

When the invoice is copied, the status in the Invoice Status field in the Received Purchase Invoices (tfacp1500m000) session is set to Registered. The invoice cannot be copied again.

Note: If you have started this session using the browse arrow, you can only find and select a record.

Field Information

• Invoice-from Business Partner: The invoice-from business partner
• Document - The document number: The document number is a sequence number under which the invoice is temporarily recorded. When an invoice is registered officially, you must assign the invoice to a different number, in combination with a transaction type.
• Business Partner Invoice Number: The invoice-from business partner's invoice number is the invoice identification used in LN: This number is printed as the payment reference when the invoice is paid.
• Invoice Date: The date printed on the invoice. This date is used as a reference date for the term of credit allowed.
• Currency: The invoice currency
• Amount: The invoice amount

FINANCE: Copy Received Purchase Invoices (tfacp1210m000)

OPERATIONS: Production Order Parameters

TECHNOLOGY: Audit Configuration Management

Note: The Blocked Operations (tisfc0540m000) session displays the blocked operations.

Introduction

Sometimes a problem occurs that must be solved before an operation proceeds. Examples of such situations are:

• The quality of an intermediate product must first be inspected.
• A machine is in repair.
• A supplier cannot deliver an essential component in time.
• A customer is late with its payments.

In these situations the operation can get the operation status Blocked.

An operation can be blocked:

• Manually.
• Automatically by Quality.

Blocking reasons

Every blocked operation must have a blocking reason. The blocking reason of a blocked operation has two purposes:

• To indicate why the operation is blocked.
• To determine which actions you can no longer perform on the operation.

Types of blocking

The following actions can be blocked by means of a blocking reason:

• Reporting a quantity completed.
• Reporting a quantity rejected.
• Reporting a quantity to be inspected.
• Reporting an operation completed.

You normally carry out these actions in the Report Operations Completed (tisfc0130m000) session.

You can define blocking reasons in the Blocking Reasons (tisfc2100m000) session.

Manual blocking

Use the Report Operations Completed (tisfc0130m000) session to block an operation. When you block an operation, you must also enter a blocking reason. If Quality has already blocked the operation, you can only enter a blocking reason, which is more restrictive than the blocking reason of Quality.

Blocking by Quality Managem

The high contrast skin can be activated by users who experience low vision, color-blindness, or similar visual impairments.

If the high contrast skin is active, LN UI is colored so that all controls comply with the WCAG AA norms for accessibility.

Guideline 1.4.3 Contrast (Minimum)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. For level AA, these exceptions apply:

• Large text: large-scale text and images of large-scale text have a contrast ratio of at least 3:1.
• Incidental: the following text or images of text have no contrast requirement:
  • Text or images of text that are part of an inactive user interface component.
  • Text or images of text that are pure decoration.
  • Text or images of text that are not visible to anyone.
  • Text or images of text that are part of a picture that contains significant other visual content.
• Logotypes: text that is part of a logo or brand name has no minimum contrast requirement.