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).

This enhancement provides a robust RMA Inquiry capability. The base RMA Inquiry application delivers role-based functionality to support customer service, sales, pricing and business analysis functions.

The IDF RMA Inquiry presentation enhances a number of customer service and data analysis functions.

• RMA List provides filters that allow sorting and sequencing by any displayed data field, such as RMA number, customer number, Total RMA amount, request date, good thru date, Customer reason code, Disposition reason code, Q/C reason code.
• RMA Line List provides filters that allow sorting and sequencing by any displayed data field, such as item number, request date, extended amount, net price, Customer reason code, Disposition reason code, Q/C reason code.
• RMA detail cards provide additional details about the RMA, as well as about any orders that will result from the RMA.

IDF RMA Inquiry provides significant enhancement to several business roles:

Customer service personnel, customer service managers responsible for handling customer complaints and negotiating return conditions with the customer Warehouse personnel, warehouse manager at the return warehouse. Billing personnel, billing managers responsible for processing credits to the customer and handling questions related to the RMA, return and eventual credit.

Managers responsible for analysis of returns related to reasons for returns, resulting replacement orders, recommendations for improving pricing or internal processes to reduce returns.

Infor LX now stores the Net Price for a deleted line, so that the information is available for later analysis.

If an order line is canceled, LX stores the current Net Price in a new Net Price Archive field. The Net Price Archive field is updated whether the line is deleted through Line Entry (ORD700D2) or Fast Line Entry (ORD700DA), or the entire transaction is deleted through Order, Quote or RMA Directory (ORD700D1).

The Net Price Archive field can be useful when analyzing the reasons for canceled order lines. Users can define Cancellation Reason Codes related to pricing. Review of the archived Net Price, along with other values from canceled order lines such as Order Quantity and Selling Unit of Measure, Cancellation Reason Code, Request Date, Price Book Date, Item Number and Customer Number, can lead to adjustments to pricing structures, promotion qualifiers or other actions that can avoid loss of revenue on future orders, or follow-up actions to recover the canceled line.

FINANCE: Archive Net Price for Deleted Lines

OPERATIONS: IDF RMA Inquiry

TECHNOLOGY: User Provisioning