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
46196 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

This is a simple way to go from the customer order to making the order and shipping the order. It involves a few simple steps:

  1. Receive and enter the customer order
  2. Automatic credit review
  3. Automatic release of the shop order tied to the customer order
  4. Issue material, report labor to the production order receipt
  5. Pick the order, ship the order, invoice the customer


With lean, you can skip processing the demand through MRP. You can go directly from the customer order to the shop order creation.

Define Inventory transactions for issuing components to the shop and receiving finished items. See the Inventory help text for examples of transactions.

  • Transaction type I - Single Issue to Shop Order. Use this transaction type to issue one component at a time. Use this for high-value items that are marked as Must Single Issue on the Item Master file.
  • Transaction type M - Multiple Issue to Shop Order. Use this transaction type to issue all the components as listed in the Shop Order, in one transaction. Note that this transaction type does not issue Must Single Issue items.
  • Transaction type S - Receipt from shop. Use this transaction type to receive the finished item into stock and update the shop order accordingly. 

The Shop Order Lot/Location Allocation program is an alternative to using the above Inventory transactions. Use this when the item is finished, and you want to review exactly what was used to make it. You can review the components as allocated, make any changes, and finally accept the finished order.

First132133134135137139140141Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

1345678910Last

Theme picker

Categories