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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip of the Week: In Transit Inventory Report – LN 10.7

A new In Transit Inventory report can be printed in the Print In Transit Inventory (whinr1410m300) session. The report provides an overview of company inventory that is on the move and not stored in a warehouse. This concerns only inventory that is transferred from one warehouse to another. Items that are shipped to, for example, customers or projects, or items that are issued to production lines or service departments are excluded.

The report shows item inventory quantities and values on warehouse transfer orders which are issued at the origin warehouse but are not yet received in the destination warehouse. These open inter-warehouse transfer orders represent inventory that is loaded on trucks or other means of transport, or located at intermediate pooling points such as harbors and train stations.

The quantities and values are retrieved from the Item-Warehouse-Inventory Transactions and the Inventory Integration Transactions sessions.

In the Print In Transit Inventory (whinr1410m300) session, a range of warehouse valuation groups, warehouses, items, transaction dates, etc. can be specified. Additional print options are available that determine if only item quantities must be printed or if insight into both quantities and inventory value is required. Quantities and values can also be aggregated by site and destination or origin warehouse.

Previous Article At Crossroads RMC, we pride ourselves with being in the race for the “long haul”.
Next Article Infor LX & BPCS Tip of the Week: Item Deletion Option in IDF Enterprise Items
Print
19788 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

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.

In LN, you can differentiate between items at various suppliers:

  • Locations (warehouses),
  • Purpose (planning, purchase)
  • Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:
 
  • Items - Planning (cprpd1100m000)
  • Check Item Data by Warehouse (whwmd2210m000)
  • Item Supplier Plan (cpvmi0530m000)
These sessions define entities that have an n-to-1 relationship with the general item data.

 

First151152153154156158159160Last

Theme picker

Categories