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

Beyond the Four Walls—Achieving Upstream and Downstream Inventory Visibility

Infor LX | BPCS | Infor LN | Baan | Infor M3

Crossroads RMC 0 22850 Article rating: 5.0

When an enterprise has many suppliers, dealers/distributors, and customers spread out across the globe, it becomes important that it gains better visibility into inventory outside of its direct ownership and control, on both the supply and demand side. On the supply side, the company has outstanding POs and needs reliable estimates of when those will ship, as well as early indications whenever there will be delays in shipment. Once shipped, updates on the estimated time of arrival (ETA) are important, particularly when there are delays.

This external visibility is even more important during times of disruption. Early visibility into disruptions in supply or rapid changes in demand is key to providing the intelligence to drive agility. By responding earlier, faster, and with more accurate intelligence, a company has more options, makes smarter decisions, and avoids catastrophes.

How do you get that visibility? Here are some options…

How often are you counting your inventory? Are inaccurate counts affecting your ability to satisfy customer orders?

Infor LX | BPCS | Infor LN | Baan

Crossroads RMC 0 22131 Article rating: 5.0

Crossroads RMC Cycle Counting Applications provide:

  • Increased inventory accuracy.
  • The ability to review & approve count before direct update of LN/Baan tables.
  • The elimination of unnecessary re-orders of items with current inventory.
  • Greater ability to satisfy customer orders due to accurate inventory levels.
  • Direct labor cost savings – less staff required for count.
  • Increased productivity during count – counts reduced from weeks to a day.


Learn more about Cycle Counting for Infor LX & BPCS> 

Learn more about Cycle Counting for Infor LN & Baan> 

RSS

Theme picker

Tips:  LX | BPCS | M3

You can integrate Accounts Payable (ACP) with Purchasing. ACP requires more detailed information in the Vendor file than Purchasing requires. Accounts Payable automatically checks for a valid purchase order when you

match invoices to POs and receipts. Enter any outstanding active purchase orders through PO Release, PUR500, before you can match invoices in Accounts Payable.

 

Accounts Payable can also update the Actual Cost fields in the Inventory Master file directly from vendor invoices. You must provide the following information in order for Accounts Payable to complete this update:

â–ª Define a type C inventory transaction.

â–ª Enter a valid purchase order on the Invoice Entry header screen, ACP500D2-01, or in the Next Purchase Order field on the Invoice Entry: PO Costing screen, ACP500D3-01.

â–ª Enter the information for the actual cost transaction on the appropriate lines.

First130131132133135137138139Last

Theme picker

Tips: LN | Baan

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:...


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value...


TECHNOLOGY: Infor LN Rest API
Frequently Asked Questions (KB2316174)

Compression

Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.
  • The destination financial company.
  • The transaction type and series.
  • The ledger account and dimensions.
  • The transaction currency.
  • The fiscal year and the financial period, the tax period, and the reporting period.
  • The integration document type and the Debit/Credit indicator.
  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

12345678910Last

Theme picker

Categories