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 Week: Is Lot Control Necessary?

Anthony Etzel 0 75115 Article rating: No rating

Certain industries require lot control, where others may find it an option based on how they want to trace the material used in a product in the event of a defect, or recall.

LX provides tight lot controls and flexibility with lot number assignments. Shop orders can have a pre-assigned lot number, or a lot number can be automatically assigned when the item is produced. You can also assign a specific lot number for the entire shop order, or for each item/quantity reported against a shop order.

Baan/LN Tip of the Week: Default Order Frequency

Kathy Barthelt 0 81624 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 ERP 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.

Crossroads RMC to Exhibit at COMMON Conference, April 26-29

Crossroads RMC 0 32738 Article rating: No rating

The Annual Meeting is COMMON’s largest educational event of the year, with four full days of in-depth IBM i, AIX, and Linux-related education that includes all-day pre-conference workshops, open labs and a wide variety of regular-length sessions. It is the annual meeting of the COMMON membership and the largest gathering of the Power Systems user community. Come see us in Booth 316.

BPCS/LX Tip of the Week: Batch Allocation

Anthony Etzel 0 68710 Article rating: 5.0

Thinking of moving from your old BPCS Version to LX?

There are numerous reasons to consider moving to Infor LX. It is a proven migration and it is easy to get there.

An area of interest may be allocations. Allocations can be difficult to manage, but with Infor LX, there is a new selection of ranges for Batch Allocations:

    • Sold To Customer
    • Ship To Number
    • Order Class
    • Order Number
    • Item Number
    • Request Date
    • Schedule Date

Baan/LN Tip of the Week: Safety Time

Kathy Barthelt 0 103128 Article rating: No rating

You can add safety time in the item master for the item. This will add the number of days safety time to the order lead time thus bringing the order in x number of days early. (x is the safety time).

The safety time is on form 4 of the item master in Baan IV and in Item Ordering Data – Generation I tab in Baan V and LN.

Baan/LN Tip of the Week: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt 0 98166 Article rating: No rating

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

 

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

BPCS/LX Tip of the Week: Product Routing

Anthony Etzel 0 71763 Article rating: No rating

Defining the Product Routing first requires the items to be setup in the Item Master file. Other master files also need to be defined prior to creating the routing.
These include:

  • The Facility defined with a SYS program
  • The Warehouses defined with an INV program
  • Locations defined with an INV program
  • The Machines (required if using capacity planning or an MES interface) defined with an MDM program

After the above data is set up, the Department file and Work Center files can be setup in MDM. Now you are ready to define a product route.

First123124125126128130131132Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to define simulated purchase prices for purchased items per site.

Field Information:

  • Cost Calculation Code - price calculation code
  • Item

The raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, and sold.

An item can also represent a set of items handled as one kit, or which exist in multiple product variants.

You can also define nonphysical items, which are not retained in inventory but can be used to post costs or to invoice services to customers. The examples of nonphysical items:

  • Cost items (for example, electricity)
  • Service items
  • Subcontracting services
  • List items (menus/options)
     
  • ​Site - The site for which the purchase price is simulated.
  • Purchase Currency - The currency of the simulated purchase price.
  • Simulated Price - Purchase price

The simulated purchase price and currency are recorded twice.

  • Simulated Price Multi Currency - The purchase price in multiple currencies.

The simulated purchase price and currency are recorded twice. The amount in this field is related to the price of the supplier.

  • Unit - Purchase price unit
  • Cost Component - The cost component that must be of the type Material Costs.

Note: The cost component specified in this field does not become part of the standard cost detail structure if it is part of the cost component scheme of the selected item. If calculations are performed with a calculation code not used for actualization (simulations only), the simulated purchase price is mapped to the cost component defined in the records for this session.

Categories