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

Baan/LN Tip of the Week: Transaction Accounts – Commissions

Kathy Barthelt 0 39825 Article rating: No rating

In Baan IV, if a link with Financials exists for commissions and rebates, invoices are created directly in the Commission Control System (CMS) module and posted to Financials. As a result, users must specify the ledger accounts that are used for posting commissions and rebates in the Maintain Commission/Rebate Transaction Accounts (tdcms2101m000) session.

In LN, the Maintain Commission/Rebate Transaction Accounts (tdcms2101m000) session is removed from the Commission Control System (CMS) module, because invoices are no longer created directly in the Commission Control System module.

BPCS/LX Tip of the Week: Vendor Maintenance Security Option for Company or Program

Anthony Etzel 0 27772 Article rating: No rating

The Vendor Maintenance Security option is in the Purchasing System Parameters program(PUR820D). The purpose of this program is to provide an additional security option for VendorMaster Maintenance. To access this program, the user selects the Parameters Generation option from the System Functions menu, SYS500. The user can modify the Vendor Maintenance Security parameter from PUR820D-04 in the Purchasing System Parameters program.This feature provides an additional security parameter for Vendor Master Maintenance.

Optimize Your Manufacturing Today!

BPCS/LX Tip of the Week: 6 Powerful Steps to Win With Automation

Anthony Etzel 0 25732 Article rating: No rating

1. Eliminate paper shop packet and distribution of the paperwork to the shop floor.  

2. Eliminate manual (paper-based) recording activities and the need to key in the transactions.

3. Easy electronic scheduling by sequence and changing job priorities.

4. Evaluate differences using actual times compared to standards.

5. Improve data accuracy and eliminate the need to chase and fix errors.

6. Practice Real-Time data reporting to monitor efficiencies and identify problems as they occur.

Optimize Your Manufacturing Today!

Baan/LN Tip of the Week: GRINYA Reconciliation – What Could Go Wrong?

Kathy Barthelt 0 41459 Article rating: No rating

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error.

To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Optimize Your Manufacturing Today!

BPCS/LX Tip of the Week: Purchase Order Receive All Processing

Anthony Etzel 0 24130 Article rating: No rating

With this enhancement, the Purchase Receipts screens are optionally shown with the quantity and weight fields populated with the open value on the purchase order.

Previously the user had tomanually enter the quantity received or, for a dynamic weight and measure items, the weightreceived for each line on the purchase order.

Now the screens are populated with the open valueand if the open value is the same as the value received, the user can simply accept the line.

Optimize Your Manufacturing Today!

Baan/LN Tip of the Week: 4 Reasons You Need Timely & Accurate Data

Kathy Barthelt 0 40152 Article rating: No rating

Seems obvious – you want real time data and you want it to be accurate. Do you have the systems in place to allow for this?

Here are 4 reasons you need a data collection system:

  1. See the differences between actuals and standards
  2. Determine the source of project overruns
  3. Prevent mis-shipments to customers
  4. Avoid unnecessary reordering of parts

An automated data collection system will analyze your current data, allowing you to efficiently optimize your manufacturing and the benefits will be huge and far reaching.

Optimize Your Manufacturing Today!

RSS
First8384858688909192Last

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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Considerations for Release to Warehousing for a Cost Item

When there are two Cost Items, one with Release to Warehousing applied and the other with Release to Warehousing not applied, upon approval of the Sales Order, the Cost Item that is released to Warehousing will go straight to Staged status, pending Shipment confirmation, while the Cost Item that is not released to Warehousing will be up for Sales Deliveries.

Apart from this main difference in functionality between having and not having this option to release to Warehousing checked, there are other impacts to consider. Below is some information gathered from various KBs related to the impact of having release to Warehousing applied (or not). KBs used as reference are listed as “– REF: KB XYZ”. Editing the checkbox “Release to Warehousing” itself If there is a Sales Order (in status Free is enough) for a Cost Item, the check box is not editable. As soon as all the Sales Orders for which the Item is involved are Closed (or Canceled or Deleted) the check box becomes editable again. – REF: KB 1439313 & KB 1613780 Simultaneous/separate release to Warehousing with Physical Items In a scenario where a Cost Item (that is released to Warehousing) and a physical Item are released to Warehousing separately, then the shipment confirmation of each of these Items will occur separately. If they are released simultaneously, the shipment of the Cost Item will not be processed unless and until the physical Item is ready to be shipped. – REF: KB 1449001 Note: Ensure a Warehouse is added to Order Lines to ensure Release to Warehousing Activity is applicable. – REF: KB 2229767 Invoicing

To invoice them separately or together, factors to consider are:

  • Composing Criteria, a list of fields that need to match to have a single invoice created – REF: KB 717977
  • Invoicing Methods (tcmcs0555m000) in the General tab, select Combine, for example, Shipments, to combine different Shipments of the same Sales Order into one Invoice. This Invoicing Method is also defined in
  • Invoice-to role of a Business Partner (tccom4112s000) in the Invoicing tab. – REF: KB 812637
  • For a Return Order where a Cost Item and a Physical Item were originally invoiced together, to invoice them together again, consider using Original Document type = Invoice and link the original Invoice to the Return Order. – REF: KB 2072847 

Note: Consider solution in KB 2108605 if Composing Criteria is met, yet still Credit Notes are not combined for a Return Sales Order copied from original Sales Order for one Physical Item and one Cost Item without release to Warehousing. 

ASN ASN cannot be generated for Purchase Order Lines with Cost Item if not released to Warehousing. – REF: KB 1548301 & KB 2111341 Intercompany Trade Intercompany Trade can be applied for a Cost Item that is released to Warehousing, as Intercompany Trade needs a Warehouse and a Department. – REF: KB 2112430 Customs Value Cost Items that are released to Warehousing that are handled via normal Sales Order Lines are considered as delivered goods and will get the customs value assigned like other Items being subject to warehouse handling. Cost Items handled on Shipment Lines as "Additional Cost" are not considered as delivered goods but as pure costs. The customs value of these shipment lines gets defaulted with a zero amount and cannot be modified. The same applies to additional costs on sales order lines. – REF: KB 1600847 Freight  Cost Items cannot be used for Freight handling. – REF: KB 1830170 Additional Cost

  • For automatically generated Additional Costs in Sales Orders, Cost Items that are released to Warehousing are not released to Warehousing. This is because automatic Additional Costs are always generated with 0 quantity, therefore only the amount is filled for these Lines, which leads to the Delivery Type being set to Sales and not Warehouse. As a result, delivery must take place in Sales module. – REF: KB 1995781
  • For Additional Cost Lines added to Shipment for Cost Items, refer to KB 2236856.

Intrastat Record When using Cost Items without release to Warehousing, there is no shipping data within Invoicing. Therefore, the corresponding Intrastat record cannot be found during the printing of the Invoice. To get the Invoice data filled on the Intrastat record, Cost Items with release to warehousing should be used. Otherwise, session Update Intrastat Transactions with Invoicing Data (tccom7271m100) should be ran to update the Invoicing data in Intrastat. – REF: KB 2005482

Previous Article Infor LN & Baan Tip: What conditions must exist before changing an item's inventory unit?
Next Article Infor LN & Baan Tip: Cash Flow Functionality and Setup
Print
15508 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories