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
20634 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

FINANCE: Default Billing Reason Code from User Order Class
This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

TECHNOLOGY:  Security Manager
New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves, but are only allowed to access regular LX programs if granted authority by an LX security officer.

OPERATIONS: Track all order holds added & released
Enhancement: Order Hold Audit Functionality
This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves but are only allowed to access regular LX programs if granted authority by an LX security officer.

First2345791011Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

123457910Last

Theme picker

Categories