Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

BPCS/LX Tip of the Day: Cycle Counting Part 2

Anthony Etzel 0 78148 Article rating: No rating

Understanding: The Cycle Count Alternative

The best way to cycle count is to count the same number of items each day and at the same time each day. The goal is to count your “A” items 4 times a year. The “A” items should be those item that are about 80% of the total inventory value and 20% of the total items. Consider creating your own cycle count schedule then instead of using the cycle count transaction, use the inventory adjustment transaction. The item balance is changed at the time the transaction is keyed. The transaction list can be used for the reconciliation process.

Baan/LN Tip of the Day: Company Calendar

Kathy Barthelt 0 110308 Article rating: 5.0

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

  • Master Production Scheduling
  • Material Requirements Planning
  • Capacity Requirements Planning
    (All three combined in a single planning module for Baan V and LN)
  • Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.

BPCS/LX Tip of the Week: Cycle Counting Part 1

Anthony Etzel 0 84937 Article rating: No rating

Understanding: The Cycle Count Transaction

If you rely on BPCS to provide you with a cycle count list, the number of items could vary from day to day from a few items to count, to several. So the person doing the cycle counting may spend a few minutes to a few hours counting items. After the cycle count is complete, the balances are not changed until the reconciliation is complete. This process could take some time before the balances are changed.

The cycle count transaction process is similar to the physical inventory transaction process.

Baan/LN Tip of the Week: GRINYA

Kathy Barthelt 0 150177 Article rating: 3.0
GRINYA is one of the more complex issues in ERP Finance. GRINYA is the tracking via ledger account of the value of items received on a purchase order that have not been matched to a supplier invoice.

Baan solutions for Baan IV and V were incomplete. To take full advantage of the current GRINYA reconciliation process, check Infor solution #107147, which contains the GRINYA user manual and a link to download the software for your version of Baan. For ERP LN, look at Document Code U8942C US.

It is called User Guide for Reconciliation and Analysis. If you are not running the latest GRINYA solutions, patching will require a good amount of time in filling the Interim tables this solution runs from. Infor has posted several procedural write ups, so check the Support Site and read up before tackling this for the first time.

BPCS/LX Tip of the Week: Work Center & Machine Locations

Anthony Etzel 0 84516 Article rating: No rating
For either file, you must specify a valid location code as defined in the Location Master File.

If the machine master locations are blank, then the work center locations are used. There are cases where you may want to do a combination between the two in defining the locations.

Let’s say the end item has one operation. The operation is at work center 510 and Machine A is in the work center. You have locations setup in both the Work center file and the Machine master File. You report 100 complete at the work center without specifying the machine.

In this case, the inventory will be processed based on the locations defined in the work center file. If the transaction included the machine number, then the locations in the machine file would be used.

BPCS/LX Tip of the Week: The Item Master Requirements Code

Anthony Etzel 0 80382 Article rating: No rating

In the Item Master File, the requirements code is used to specify the type of demand for the item. Planned order requirements are determined from the type of demand. If the requirements code is left blank, the planning systems treat the item as a sum code (3).
 

Other options for the field are:


1 = Dependent demand that is indirectly generated from the parent item requirements.

2 = Independent demand generated from customer orders and forecasts.

3 = The Sum of both independent and dependent demand.

First126127128129131133134135Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for FINANCE: Using Dimensions

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 MandatoryOptional, 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 ledger account is linked to only dimension type 1 (cost center). The other dimension types are not used for the ledger account.

For each dimension type, you can define one dimension with an empty dimension code. If the dimension type is Optional for a ledger account, LN posts transactions for which no dimension is specified to this dimension. In this way, differences between the ledger history and the dimension history can be avoided.

In the Cross Validation Rules (tfgld0151m000) session, you can define the ranges of allowed dimensions by ledger accounts. You cannot change the dimension range for a ledger account that occurs in an unfinalized batch.

You can create transactions for Financials from the integration with other LN packages. You can enter these transactions into ledger accounts and into dimensions. You can define the assignment to ledger accounts through the Mapping Scheme (tfgld4573m000) session.

You can use the dimensions to split the transactions on the customer and supplier control accounts by departments, persons responsible for the revenues, costs, properties, debts, and so on.

The dimensions also provide the basis for the cost allocation in the Cost Accounting module. In CAT, you can allocate the costs (and any revenues) within a dimension type from one dimension code to another and from one dimension type to another.

Previous Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Next Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: High Contrast Skin
Print
286 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories