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

Kathy Barthelt

Infor LN & Baan Manufacturing Tip: All About Routings

The planning data for the method of manufacturing is defined in Routing. A routing consists of operations, with each operation identifying the last to be carried out in a work center and/or on a certain machine defined for a specific site.

Routings can be as follows:

  • Standard Routing - A generic routing that can be attached to multiple items
  • Item specific - A routing that is applied to one item
  • Network routing - A routing containing sequentially ordered operations and parallel operations
  • Order quantity dependent routing - A routing that is defined for a specific quantity of items

You use the Routing module to record routings for manufactured items. You can define the following:

â–ª Work centers - A work center is where production activities are performed. Resources, such as people and machines, are linked to a work center. A work center is a group of resource units used as a functional planning unit. The operation rate code, which is linked to the work center, is used to calculate the standard cost of an item or the estimated and actual costs. The capacity load on a work center is used in the planning of production. Work centers can be part of enterprise units used for multi-company modeling purposes.

â–ª Machines - Machines are linked to work centers and are used to plan operations. The rate defined for a machine is used to calculate the actual machine costs. The capacity load on a machine is used for production planning.

â–ª Reference operations - Classified according to the nature of the work performed, reference operations are used to describe activities that take place in the job shop. Reference operations are linked to operation rate codes, which are used to calculate the standard cost of an item or the estimated and actual costs. Reference operations are used in production planning.

â–ª Operations - The operation data for standard and customized manufactured items is maintained with operations. Operation data is stored and maintained for standard items and customized items. A series of operations are performed to manufacture an item. The sequence of operations is defined as a routing in operations. Yield and scrap are defined per operation.

â–ª Norm times - The run time and production rate of an operation are determined using norm tables. After a matrix is defined for two physical characteristics, such as length and width you can maintain a set of standard operation times for the X-Y coordinates. When tasks and routings are defined, the run time and production rate can be calculated by using a norm table.

â–ª Skills - Certain skills may be mandatory to perform a specific operation. To ensure employees assigned to an operation possess the necessary knowledge, skills are linked to both employees and operations.

Previous Article Infor LX & BPCS Manufacturing Tip: Backward Scheduling
Next Article Infor LN & Baan Finance Tip: What Can You Do in the Financial Statements Module?
Print
24598 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

123468910Last

Theme picker

Tips: LN | Baan

Compression

Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.
  • The destination financial company.
  • The transaction type and series.
  • The ledger account and dimensions.
  • The transaction currency.
  • The fiscal year and the financial period, the tax period, and the reporting period.
  • The integration document type and the Debit/Credit indicator.
  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

Order quantity-dependent routings

An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:

123468910Last

Theme picker

Categories