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 Tips & Tricks for EXECUTIVES

TECHNICAL: Synchronize users from LX to SiM in batch

This enhancement improves performance by submitting to batch the automatic synchronization of changes from LX user maintenance (SYS600) to System i Manager (SiM). During LX user maintenance, there are now three possible approaches to synchronizing the LX user changes to SiM, controlled by system parameters. Synchronizing LX user changes to SiM in batch allows the person executing SYS600 to continue with additional maintenance or other transactions without waiting for the synchronization to finish.


FINANCE: Inventory Transaction History to Ledger Book Journal Line Relationship

This enhancement provides IDF relationships from Inventory Transaction History (ITH) to Ledger Book Subsystem Transaction (GXR) and from Ledger Book Subsystem Transaction (GXR) to Ledger Book Journal Line. To implement this enhancement, request and apply MR 81558.

This enhancement provided the following relationships:

  • Inventory Transaction History
  • Relationship to Ledger Book Subsystem Transaction (1 to Many) Default view ‘General’
  • Ledger Book Subsystem card Default view ‘Inventory Processing’
  • Default subset ‘Inventory Processing’

This enhancement provides users with complete traceability from inventory transactions (ITH) to ledger book journal lines (GLH), regardless of how many ledgers are used and journals created. Due to the bi-directional relationship, users can see the source ITH detail from the journal lines.

OPERATIONS: Infor Business Context (IBC) messages for INV500 

This enhancement adds publication of IBC messages to additional LX screens. While entering data on the primary screen for inventory transactions, IBC message are now published and available for use in Ming.le contextual applications.

Previous Article The Far-Reaching Impact of Disconnected Data
Next Article Improve Productivity & Agility with Modern ERP
Print
541 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 define simulated purchase prices for purchased items per site.

Field Information:

  • Cost Calculation Code - price calculation code
  • Item

The raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, and sold.

An item can also represent a set of items handled as one kit, or which exist in multiple product variants.

You can also define nonphysical items, which are not retained in inventory but can be used to post costs or to invoice services to customers. The examples of nonphysical items:

  • Cost items (for example, electricity)
  • Service items
  • Subcontracting services
  • List items (menus/options)
     
  • ​Site - The site for which the purchase price is simulated.
  • Purchase Currency - The currency of the simulated purchase price.
  • Simulated Price - Purchase price

The simulated purchase price and currency are recorded twice.

  • Simulated Price Multi Currency - The purchase price in multiple currencies.

The simulated purchase price and currency are recorded twice. The amount in this field is related to the price of the supplier.

  • Unit - Purchase price unit
  • Cost Component - The cost component that must be of the type Material Costs.

Note: The cost component specified in this field does not become part of the standard cost detail structure if it is part of the cost component scheme of the selected item. If calculations are performed with a calculation code not used for actualization (simulations only), the simulated purchase price is mapped to the cost component defined in the records for this session.

Categories