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: Inventory Transactions

Anthony Etzel 0 586 Article rating: No rating

Define Inventory transactions for issuing components to the shop and receiving finished items. See the Inventory help text for examples of transactions.

  • Transaction type I - Single Issue to Shop Order. Use this transaction type to issue one component at a time. Use this for high-value items that are marked as Must Single Issue on the Item Master file.
  • Transaction type M - Multiple Issue to Shop Order. Use this transaction type to issue all the components as listed in the Shop Order, in one transaction. Note that this transaction type does not issue Must Single Issue items.
  • Transaction type S - Receipt from shop. Use this transaction type to receive the finished item into stock and update the shop order accordingly. 

The Shop Order Lot/Location Allocation program is an alternative to using the above Inventory transactions. Use this when the item is finished, and you want to review exactly what was used to make it. You can review the components as allocated, make any changes, and finally accept the finished order.

Baan/LN Tip of the Day: Multi-Company Warehousing 10.4

Kathy Barthelt 0 435 Article rating: No rating

You can define internal trade relationships between enterprise units or individual warehouses of the same logistic company for the transfer of material, labor, or other costs between warehouses, and to generate invoices for these without using sales orders and purchase orders. For example, you can use this to transfer goods between warehouses in different countries.


You can define warehouse surcharges, which are added to the actual costs of the goods either when the goods are issued from a warehouse or when the goods are received.

BPCS/LX Tip of the Day: MRP/MPS Simulation in LX

Anthony Etzel 0 785 Article rating: No rating

The system allows you to manipulate and maintain a simulated MPS and MRP. You can copy the simulation from the existing first cut, or you can create a totally new schedule. You can also perform a simulation of the rough-cut capacity plan. This allows a quick visual inspection by inquiry or menu of needed work center

loads for the proposed MPS. After you choose a suitable MPS and rough-cut capacity, the system allows you to transfer the simulated MPS to the live Master Production Schedule.

Baan/LN Tip of the Week: Default Order Frequency

Kathy Barthelt 0 1943 Article rating: No rating

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In Infor LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.

BPCS/LX Tip of the Day: Cost Accounting – LX

Anthony Etzel 0 868 Article rating: No rating

The challenge in cost accounting is tracking your manufacturing to the levels needed for useful management information. You need feedback for corrective action; but, you need to minimize the cost of collection. Some parts of your operation require specific job-cost tracking while the Just-in-Time areas require

costing in terms of cost per process hour or day. Apply overhead in different ways to different processes and products. Segregate costs into enough detail

to provide management with an accurate picture of the contents of your product. Material, material overhead, labor, fixed overhead, variable overhead, outside processing, outside processing overhead, and so forth all have to be considered.

 

LX meets your cost accounting needs with the following functionality:

â–ª Four sets of costs: actual, standard, frozen standard, and simulated

â–ª Nine user-defined elements per set

â–ª Full and partial cost roll-up and simulation

â–ª Cumulative in-process cost tracking

â–ª Cost summaries by item

â–ª Cost definition tied to work centers or material type

â–ª Process hour costing

RSS
First143144145146148150151152Last

Theme picker

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.

12345678910Last

Theme picker

Tips: LN | Baan

How well does your ERP Serve your Manufacturing team?

Results from a survey of manufacturing professionals in the manufacturing vertical

Infor ERP Infographic

Previous Article Infor ERP Tip: Cyber Attacks
Next Article The Best Baan IV | Baan V | Infor LN Financial Reports to Analyze Company Performance
Print
35571 Rate this article:
5.0
Crossroads RMC

Crossroads RMCCrossroads RMC

Other posts by Crossroads RMC

Theme picker

Contact author

x

Categories