Please Wait a Moment
X

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

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

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

Subscribe to newsletter

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Finance, Operations, Technology, Executive

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE: Can accounts receivable invoices be uploaded into LN using Excel?
Yes, this is possible, by following the steps below:

1. Maintain a batch

2. Maintain an invoice header, export it, add an additional invoice header to the Excel file, and import it

3. Maintain an invoice line for the first invoice, export it, add additional invoice lines to the Excel file and import it
 

Below the above steps are described in detail.

1a. Open the transactions (tfgld1101m000) session and create a batch.

1b. Insert a transaction type, used for creating sales invoices, like ACR, and open it.

2a. The Sales Invoices (tfacr1110s000) session starts. Maintain the invoice header and save it. For example sales invoice ACR 4497.

2b. In the Actions menu select Export and Import -> Advanced Export (fields: All tabs).

2c. In the excel file created during previous step, add the headers for the invoices to be uploaded. Notice if for the transaction type the Documents in Fixed Sequence checkbox is ticked in the Transaction Types (tfgld0511m000) session, the document number for the not-yet existing invoices to be imported in LN should be equal to the default series for this transaction type. Otherwise, so if the Documents in Fixed Sequence checkbox is not ticked, the desired document numbers can be maintained in the excel file.

2d. In the Sales Invoices (tfacr1110s000) session in the Actions menu select Export and Import -> Settings, and make sure the Import Only in This View checkbox is NOT ticked. Then select in the Actions menu select Export and Import -> Import, select the excel file as saved in the prior step, and import it. Afterwards the invoice headers should be visible in the Sales Invoices (tfacr1110s000) session.

3a. Navigate to the first invoice, select Lines. The Transactions (tfgld1102m300) session opens. Maintain at least 1 line and save it.

3b. Open the line created in the prior step. Notice the detailed version of the Transactions (tfgld1102m300) session opens.

3c. In the Actions menu select Export and Import -> Advanced Export (fields: All tabs).

3d. In the excel file created during previous step, add lines for the header invoice numbers as available in the Sales Invoices (tfacr1110s000) session (as per step 2d).

3e. In the detailed version of the Transactions (tfgld1102m300) session in the Actions menu select Export and Import -> Import, select the excel file as saved in the prior step, and import it.


OPERATIONS: MPS Planned vs. MRP Planned
When deciding what items should be MPS (Master Production Schedule) planned and what items should be MRP (Material Requirements Planning) planned, it's crucial to understand the nature of the items and their demand sources. Here's a breakdown:

  • Master Scheduled Items:

    • Master Scheduled Items are typically finished goods or service items.
    • These items receive their requirements from both Independent and Dependent demand sources.
       

  • Independent Demand:

    • Independent demand cannot be calculated from higher-level demand in the product structure.
    • It is driven by forecasts or actual customer orders, primarily applicable to Finished Goods or Service parts sold to customers.
       

  • Dependent Demand:

    • Dependent demand is derived from higher-level demand in the product structure.
    • It includes components, raw materials, and sub-assemblies.
    • Dependent demand items are not typically part of Master Production Scheduling (MPS).
       

  • Service Parts:

    • Service parts can have both independent demand from forecasts or customer orders and dependent demand from higher-level demand if they are used in sub-assemblies or other products.
       

  • Cumulative Lead Time:

    • Cumulative Lead Time is a concept used in MPS.
    • It combines the fixed lead time and variable lead time required to produce a product.
    • It represents the longest path through a Bill-of-Materials (BOM).
    • Your ERP system will calculate the cumulative lead time (Critical Path) based on MPS setup options.
       

  • Infor LN Approach:

    • Infor LN does not differentiate between MPS and MRP planning.
    • It uses Enterprise Planning (EP) with one set of planned orders.
    • While you can set up items and generate orders at plan levels, it's not always necessary.
    • In theory, you could treat plan level 1 similar to MPS items.
       

  • Defining Independent Demand in LN:

    • In LN terms, independent demand is demand not related to other planned items.
    • Dependent demand comes from related planned items higher up in the BOM structure.
       

  • COLT (Cumulative Order Lead Time):

    • COLT exists in the purchase and manufactured planned items.
    • It considers non-critical and critical lead times based on components marked as critical.
    • Once calculated, COLT can be used to update the order and planning horizons of a planned item.

Relevant Sessions:

In Baan IV:

  • Maintain Item Data (tiitm0101m000)
  • Generate MPS (timps3201m000)
  • Maintain Master Production Schedule (timps3101m000)
  • Display Planned Inventory Movements by Item (timrp1510m000)
  • Display Planned MRP Purchase Orders (timrp1521m000)

In Baan V:

  • Plan Item Data (cprpd1500m000)
  • Item Master Plan (cprmp2101m000)
  • Time-Phased Overview (cprrp0520m000)

In Infor LN:

  • Item – Planning (cprpd1100m000)
  • Item Master Plan (cprmp2101m000) - Same as Master MPS if used


TECHNOLOGY: Are you running the latest Infor components?
Always good to stay on top of new releases for your various Infor components. Here is a list of knowledge base articles that you can check for the components listed below:

For the last Infor LN, Infor Baan5, and Infor Baan4 porting set see KB 22923520

For the last BaanIVc 6.1c porting set see KB 22923521  No fixes are made based on the 6.1c porting set.

For the last Worktop set see KB 22881488 For the last BW set see KB 22881483 For the last EME set see KB 22866552 For the last Office integration set see KB 22867312 For the last Dynamic Form Editor see KB 22881485

For more information and assistance, you can contact Crossroads RMC at 800.762.2077 or via email at solutions@crossroadsrmc.com.

Previous Article Infor LX / BPCS Tips & Tricks for EXECUTIVES
Next Article Infor LN & Baan Tip & Tricks for TECHNOLOGY: Infor LN Rest API
Print
6537 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

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.

Read more

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.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

Who gets involved?
  1. Most commonly Engineering is involved in writing the rules, creating the bills and routings.
  2. Sales or Customer Service determines the questions and the order they are asked in.
  3. Sales or Customer Service determines the rules for the pricing.
  4. Sales, or Customer Service, and Engineering work together in determining the part number, description and text.

What are the steps?

  1. You must start by defining the features and options (questions and answers) and the order in which these are asked. We work this out first using sticky notes and large easel paper. Normally during the process we find that we want to move these questions around. Setting them down on paper makes the process of getting the data into Baan much more efficient. We also then have a record of what decisions were made prior to entering the data. This is normally a joint effort of Engineering and Sales. This is required and must be the first step.
  2. Constraints for features and options. These are the rules for determining what questions are asked and which options are allowed. This is generally done by Engineering or whoever is responsible for the configurator. This is required.
  3. Generic Bill of Material. All possible bill options are entered here and constraints are written to determine which options are selected based on the answers to the questions. This is generally done by Engineering or whoever is responsible for the configurator. This is a required step.
  4. Generic Routing. Similar to the bill of material, but used for generation of the routing steps. This is generally done by Engineering or whoever is responsible for the configurator. This is optional.
  5. Generic Item Data. This consists of creating custom item numbers, descriptions, text, material, size or standard fields in the custom item master. This is generally done by Engineering or whoever is responsible for the configurator though Sales may have some involvement. This is optional.
  6. Generic Pricing. This is used to calculate the selling price based on the answers to the questions. This is normally a responsibility of Sales or whoever determines the pricing. This group is also trained on writing the constraints for this section only. This is optional.
Read more
First150151152153155157158159Last

Theme picker

Categories