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

Infor LX & BPCS Materials Tip of the Week: 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 Infor LX & BPCS Finance Tip: AR Aging
Next Article Infor LN & Baan Materials Tip: Sales Quotations
Print
29774 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories