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

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 Tax Law Changes by the Numbers - Infor LX & BPCS Integration to Avalara
Next Article Infor LN & Baan Tip of the Week: Customer requested delivery date
Print
45882 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Understanding:

The Machine Master File


Machines are associated with a work center. For example, in the work center you may have multiple machines and each machine can have a unique machine ID. If there are several machines that perform the same function, they may operate at different speeds and efficiencies. Setting up the machine master can be a benefit for planning capacity and shop order throughput.

BPCS/LX Tip of the Week: SFC600

In addition to SFC650, this ERPLX program is also used to capture and post shop floor information.

The key difference between the two is that SFC600 only captures Labor (run time) reporting, machine time, downtime and indirect time.

If you use SFC600, then all shop order material receipts and issues would be captured using INV500.

Both Inventory and Shop Floor Transaction entry is keyboard dependent, unless you incorporate an automated method like an MES solution to capture the data.
First149150151152154156157158Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories