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.
   

You can independently define dimensions and use them to prepare analyses of ledger account transactions and balances. You can use up to 12

dimension types. You can define a name and an entire structure of dimension codes for each of these dimension types. There is no relationship between the dimension types.

For example, you can set up these dimensions:

• Dimension Type 1 = Cost center
• Dimension Type 2 = Item group
• Dimension Type 3 = Business unit
• Dimension Type 4 = Geographical area
• Dimension Type 5 = Activities

You can separately define the dimension structure for each of these dimension types, in other words, you can set up a dimension structure for the cost centers, a structure for item groups, and so on.

You can define the number of dimension types that you use in the Group Company Parameters (tfgld0101s000) session. If you have several financial companies in a company group, the dimension types used apply to all the companies in the group.

You can name the dimension types and define linked objects in the Dimension Type Descriptions (tfgld0102m000) session. You can then define the dimension codes to be used in each company in the Dimensions (tfgld0510m000) session. You can also make multilevel dimension structures with totals and subtotals. You can build a dimension hierarchy of up to ten levels.

In the Dimensions (tfgld0510m000) session, you can define the dimensions for each dimension type, and link the dimensions to parent dimensions and child dimensions.

Dimensions are always used together with ledger accounts. For each ledger account, you can define which dimension type or types are linked to the ledger account in the Chart of Accounts (tfgld0508m000) session. For each dimension type, you must select whether the dimensions type is Mandatory, Optional, or Not Used by the ledger account.

When you enter a transaction, you must first state the ledger account. Then you must enter a dimension for each Mandatory dimension type that is linked to the ledger account, and you can enter a dimension for each Optional dimension type.

For example, the sales revenues ledger account is linked to dimension type 2 (item group) and dimension type 4 (area). The dimension type 1 (cost center) and dimension type 3 (business unit) are not used for the ledger account. The freight costs l

FINANCE: Using Dimensions

TECHNOLOGY: High Contrast Skin

OPERATIONS: Blocking Operations

Is your current Infor LX or BPCS system holding back your growth? It doesn't have to.

In 2026, staying competitive means moving beyond manual workflows and data silos. Crossroads RMC has partnered with Aleran and Avalara to provide an integrated, end-to-end solution designed specifically for manufacturers and distributors in the Infor LX and BPCS market.

Transform Your Operations from Quote to Cash

This powerful partnership enables you to maximize your existing ERP investment without the need for a total overhaul.

• Aleran: Modern B2B eCommerce
  • 24/7 Digital Catalog: Provide a fully branded shopping experience that connects directly to your LX/BPCS data.
  • Self-Service Portals: Empower customers and dealers with real-time access to inventory, quotes, and order history.
  • Streamlined CPQ: Simplify complex product configurations and pricing to accelerate sales cycles.
• Avalara: Automated Tax Compliance

This enhancement: 

• Provides an ability for LX to integrate with Infor Federation Services (IFS) to automate provisioning of users.
• Activates LX exit points during maintenance of LX business roles and business units to publish the SyncSecurityRoleMaster BOD which can be received by IFS as LX-specific roles in addition to the three IFS predefined LX-specific roles: LX-SystemAdministrator (corresponding to LX security type S = LX Security Officer); LX-SystemManager (corresponding to LX security type M = LX Security Manager); and LX-User (corresponding to LX security type U = LX User).
• Enables support for LX receiving an inbound SyncSecurityUserMaster BOD (sent from IFS) and creating or revising the associated LX user (or security manager or security officer). This enhancement also supports creating an IBMi user profile which can then be defined as an LX user (or security manager or security officer).
• Activates LX exit points during maintenance of LX users (and security managers and security officers) to send the ProcessSecurityUserMaster BOD to IFS requesting creation or revision of a user on behalf of LX.
• Automates sending revised LX user authorities to corresponding System i Manager (SiM) tasks which can then be uploaded to System i Workspace (SiW).