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: Shop Order Control

Anthony Etzel 0 443 Article rating: No rating

To create and maintain shop orders use SFC500 Shop Order Entry Maintenance. These orders use the standard bill of material (BOM) as the base list of components. You can also set up standard routings, which list the operations,

or work steps, involved in manufacturing.

 

To release shop orders, use the Shop Order Release program, SFC505. Infor ERP LX groups shop orders by user ID for batch processing. Use Shop Packet Print, SFC520, to print the shop orders that you select. SFC530 allows you to create multi-level shop orders to link shop orders together with a common end item parent. Linking multiple shop orders together for a final assembly product provides support for make-to-order and engineer-to-order manufacturing environments which need to schedule these multiple orders together or as a vertical slice in the production schedule.

 

You can make changes to shop orders after you print them. Use Shop Order Entry/Maintenance, SFC500, to update the shop orders. Changes are immediately visible on the inquiry screens for SFC300 and SFC350. To reprint the shop packet, use Reprint Shop Packet, SFC560.

Baan/LN Tip of the Day: Multi-Company Service

Kathy Barthelt 0 240 Article rating: No rating

Service departments and warehouses that contain spare parts and components used for service and maintenance belong to enterprise units. To perform separate financial accounting for the service departments and their warehouses, you can assign service departments and warehouses to enterprise units that are linked to different financial companies.

 

If material, labor, or other costs are transferred between service departments and warehouses, or from one service department to another (in the case of internal subcontracting for depot repair), LN can perform the invoicing between these departments and warehouses. In the Enterprise Modeling Management module, you can define internal trade relationships with invoicing between various entities.

 

You can also record and process service operations in a multi-logistic company environment.

BPCS/LX Tip of the Day: Material Requirement Dates and Lead Time Offsets in MRP

Anthony Etzel 0 322 Article rating: No rating

The system automatically performs offsets for requirements dates for components in the MPS/MRP calculations. It also performs offsets for calculation of material need dates at the time that shop orders are released.


To calculate the offset, the system takes the parent lead time from the Item 
Master and adjusts it by the bill of materials offset (plus or minus) for the component. This gives the lead time days for that specific component. The system starts with the due date of the parent and backs up and skips all non-work days in the shop calendar.


Note that the offset calculation uses only calendar records that have a blank 
work center (the calendar record applies to all work centers). See the information for the Shop Calendar Maintenance program SFC140, in your Shop Floor Control documentation for shop calendar details.

Baan/LN Tip of the Day: Multi-Company Taxation – LN

Kathy Barthelt 0 278 Article rating: No rating
Tax reporting is part of the financial accounting and is restricted to one country. Therefore, the LN tax handling in a multi-company structure is similar to the tax handling in a single company environment.

Tax handling in LN includes the following:

· Tax registration

For tax registration, you define the various tax details for each country in the Taxation module. In the General Ledger module of Financials, you specify the ledger accounts for the tax amounts separately for each financial company. LN can post the tax amounts calculated for a tax code to different ledger accounts in the individual financial companies, for example, in a single logistic, multi-financial company structure.
RSS
First145146147148150152153154Last

Theme picker

Tips:  LX | BPCS | M3

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Plan Codes

In Baan IV, plan items exist within the context of a plan code. A plan code includes only items of the MPS Item item type. Planned orders are independent of a plan code. Users can compare plan codes by means of the Plan Code Performance Comparison (cprmp4504m000) session.

The scenario concept in Infor LN replaces the plan code concept in Baan IV.

In Infor LN, the basic data for plan items is the same for all scenarios. However, users maintain not only the master plan within a scenario, but the planned orders as well.

For example, for each scenario, Users can specify:

  • Special demand for an item.
  • The availability of resources (in the Scenario – Availabilities (cprpd4160m000) session).
  • The sourcing strategies and supply strategies.

Users can compare scenarios by means of the Performance Indicators (cprao2201s000) session.

Previous Article Baan/LN Tip of the Week: Data Sizing Moving to LN
Next Article Baan/LN Tip of the Week: Purchase Inquiry
Print
45138 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories