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

George Moroses
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip: Drop Shipments

Infor LX provides a tightly integrated drop shipment processing capability. The product supports the creation, tracking, and management of customer drop shipment orders via the Order Management, Purchasing, and Billing applications.

The order processing professional initiates drop shipments during customer order creation. You can designate any order line for drop shipment if it meets user-defined drop ship controls. If you designate a line as a drop ship line, the system automatically creates a drop ship request in purchase order processing.

When a buyer responds to a drop ship request and creates a purchase order, Infor LX notifies the order processing department and cross-references both the customer order and the purchase order. After vendor shipment confirmation, Infor LX automatically notifies the Billing application to initiate the invoice process. Infor LX supports constant communication between the order professional, the buyer, and the billing professional throughout the order cycle.

Note that Order Management performs soft allocations for drop shipments to allow the MPS/MRP application to net customer order drop ship demand against open purchase orders. Drop Ship Confirmation, BIL650, removes the soft allocation. Order Management does not allow hard allocations for drop ship items because the items are not physically received or issued from inventory.

Order Entry defaults to the Warehouse Master's Default Receiving Location for all drop ship lines to specify the profit center for inventory and general ledger transactions.

Previous Article Top 10 Things You Might Not Know About Crossroads RMC
Next Article Infor LN & Baan Tip: Pro Forma Invoice
Print
20888 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

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.

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

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/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.

It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Still have GRINYA questions you need answered?
Contact us. We’d be happy to help.

Optimize Your Manufacturing Today!
 

Project templates are useful because you can specify all of the information that you would normally want to include when creating a new project such as project structure, budget and so on.

In Baan IV/V, project templates do not exist, but you can set up a project template by creating a regular project, and setting the status to simulated or free. This is done so that the project does not create plans. Under this scenario, you can easily copy one project to another.

In LN, when you create a new project, a template can be used as the starting point. This is similar to copying a normal project, but unlike normal projects, no costs or revenues can be posted on a template.

Optimize Your Manufacturing Today!

 

First96979899101103104105Last

Theme picker

Categories