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

BPCS/LX Tip of the Day: Cycle Counting Part 2

Anthony Etzel 0 75165 Article rating: No rating

Understanding: The Cycle Count Alternative

The best way to cycle count is to count the same number of items each day and at the same time each day. The goal is to count your “A” items 4 times a year. The “A” items should be those item that are about 80% of the total inventory value and 20% of the total items. Consider creating your own cycle count schedule then instead of using the cycle count transaction, use the inventory adjustment transaction. The item balance is changed at the time the transaction is keyed. The transaction list can be used for the reconciliation process.

Baan/LN Tip of the Day: Company Calendar

Kathy Barthelt 0 103450 Article rating: 5.0

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

  • Master Production Scheduling
  • Material Requirements Planning
  • Capacity Requirements Planning
    (All three combined in a single planning module for Baan V and LN)
  • Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.

BPCS/LX Tip of the Week: Cycle Counting Part 1

Anthony Etzel 0 82006 Article rating: No rating

Understanding: The Cycle Count Transaction

If you rely on BPCS to provide you with a cycle count list, the number of items could vary from day to day from a few items to count, to several. So the person doing the cycle counting may spend a few minutes to a few hours counting items. After the cycle count is complete, the balances are not changed until the reconciliation is complete. This process could take some time before the balances are changed.

The cycle count transaction process is similar to the physical inventory transaction process.

Baan/LN Tip of the Week: GRINYA

Kathy Barthelt 0 109443 Article rating: 3.0
GRINYA is one of the more complex issues in ERP Finance. GRINYA is the tracking via ledger account of the value of items received on a purchase order that have not been matched to a supplier invoice.

Baan solutions for Baan IV and V were incomplete. To take full advantage of the current GRINYA reconciliation process, check Infor solution #107147, which contains the GRINYA user manual and a link to download the software for your version of Baan. For ERP LN, look at Document Code U8942C US.

It is called User Guide for Reconciliation and Analysis. If you are not running the latest GRINYA solutions, patching will require a good amount of time in filling the Interim tables this solution runs from. Infor has posted several procedural write ups, so check the Support Site and read up before tackling this for the first time.

BPCS/LX Tip of the Week: Work Center & Machine Locations

Anthony Etzel 0 81547 Article rating: No rating
For either file, you must specify a valid location code as defined in the Location Master File.

If the machine master locations are blank, then the work center locations are used. There are cases where you may want to do a combination between the two in defining the locations.

Let’s say the end item has one operation. The operation is at work center 510 and Machine A is in the work center. You have locations setup in both the Work center file and the Machine master File. You report 100 complete at the work center without specifying the machine.

In this case, the inventory will be processed based on the locations defined in the work center file. If the transaction included the machine number, then the locations in the machine file would be used.

BPCS/LX Tip of the Week: The Item Master Requirements Code

Anthony Etzel 0 76141 Article rating: No rating

In the Item Master File, the requirements code is used to specify the type of demand for the item. Planned order requirements are determined from the type of demand. If the requirements code is left blank, the planning systems treat the item as a sum code (3).
 

Other options for the field are:


1 = Dependent demand that is indirectly generated from the parent item requirements.

2 = Independent demand generated from customer orders and forecasts.

3 = The Sum of both independent and dependent demand.

First117118119120122124125126Last

Tips:  LX | BPCS | M3

Anthony Etzel

Infor LX & BPCS Tip of the Week: ION Tip – Pausing Receiving and Sending of Messages

If it is necessary to pause sending and receiving of BOD messages on your IBM i during your month-end process, it is best practice for the document flows that point to the IBM i to guarantee delivery of BOD messages. Once the month-end process has been completed, you will need to Resume the ‘Receiving’ and ‘Sending’ Active Connection Points so your documents will continue to process.

Pausing Sending messages

To pause sending messages to ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be paused for sending messages.
  3. In the Sending Paused column, click Pause. The page is automatically refreshed and the Sending Paused checkbox is selected. A Resume button becomes available. 

Sending of messages by this connection point is stopped. No new messages are picked up from the source application's outbox. The connection point still processes messages that were already picked up from the outbox. This action can take some time in the background even though the sending status of the connection point is already changed to Paused. Any new message, that was published from an application after the sending of its connection point is paused, has not yet entered ION and is not yet available in ION OneView.

Pausing Receiving messages

To pause receiving messages from ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be paused for receiving messages.
  3. In the Receiving Paused column, click Pause. The page is automatically refreshed and the Receiving Paused checkbox is selected. A Resume button becomes available.

Receiving messages by the connection point is paused.  No new messages are delivered to the destination application's inbox. All new incoming messages to this application are parked in its incoming pending messages queue inside ION.  The connection point still processes messages that were already picked up from the incoming pending messages queue. This action may take some time in the background even though the receiving status of the connection point is already changed to Paused.

Resuming sending / receiving messages

To resume sending or receiving messages from ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be resumed for message processing.
  3. Select one of these actions:
    1. To resume the pickup of messages from an application outbox, click Resume in the Sending Paused column.
    2. To resume the delivery of messages to an application inbox, click Resume in the Receiving Paused column.

The page is automatically refreshed and, depending on the selected action, the Sending Paused checkbox or the Receiving Paused checkbox is cleared. A Pause button is now available.

Previous Article Infor LX & BPCS Tip of the Week: LX 8.4 Database
Next Article Infor LX / BPCS Tip of the Week: Pre-assigned lot numbers for multi-level SO release
Print
71700 Rate this article:
5.0

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

Categories