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 Week: Work Center & Machine Locations

Anthony Etzel 0 35185 Article rating: 3.0

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.

Baan/LN Tip of the Week: SIC Planning for MRP/MPS Planned Items

Kathy Barthelt 0 54609 Article rating: 3.0

If you have a parts warehouse and prefer to use SIC for planning (re-order point) but need to use MRP/MPS planning for production, create a non-nettable warehouse for the parts warehouse and run the SIC plan against that warehouse.

When running the SIC plan, be sure to set the Order System to “MPS to MRP” for Baan IV and to “Planned to Planned” for Baan V and LN.

Using this method you keep the parts inventory out of the production planning and in the hands of the parts warehouse planner.

BPCS/LX Tip of the Week: Indirect Time Reporting

Anthony Etzel 0 37395 Article rating: No rating

In Infor LX, there are two ways to enter indirect labor. You can use either SFC600 or SFC650.

  • If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
  • If you use SFC650 and enter a reason code for the indirect, the reason code is not written to the labor Ticket file.

In either case, the reason code is not validated from the transaction file because there is no indirect transaction code. The indirect code that can be setup is machine downtime. If you need to validate and track indirect by reason and validate the reason code, then you may want to explore an MES solution that works with Infor LX.

RSS
First138139140141143145146147Last

Theme picker

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

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.

Print
46209 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

x

Categories