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

Infor LN & Baan Tip: Broadcast message to users

Kathy Barthelt 0 74625 Article rating: 5.0

Did you know that you can send a broadcast message to users on the system? This is especially useful if you need users to exit their sessions, or in the event of system maintenance.   

  • For Baan IV users, see KB 22869250
  • For LN users, see KB 1830758

Infor LX & BPCS Tip: Product interface list, SYS635D

George Moroses 0 30101 Article rating: 5.0

Did you know?  Product interface list, SYS635D

This program creates a report that contains all interface program call records that were created for the Infor LX programs specified in the range on this screen. The report contains a line for each record found. The line displays the following information:

  • The name of an Infor LX program that contains a user exit to an add-on program
  • The interface point in the Infor LX program, that is, an identifier of the point in the program code where the user exit is requested
  • The execution sequence number of the record, because more than one add-on program can exist that can run from the same interface point
  • The add-on program to call at the interface point. The Add-on Product Interface file, ZXI, stores the records.

Access: Menu SYS

Infor LX & BPCS Finance Tip of the Week: Invoice Level Inquiries – ACR300D7

George Moroses 0 33095 Article rating: 5.0

Use the Invoice Level Inquiries program, ACR300D7, to perform online customer account receivable inquiries and to perform write-off transactions on open invoices. The inquiries display customer master file and credit information, open and closed invoices, debits, credits, payments, and dunning statuses. Additional detail information is available, such as original prefix and document number, customer order number, customer purchase order number, reason codes, and currency.

You can view closed items for a period specified in Transaction History System Parameters, SYS824D-01.

Open items are aged in one of five user-defined aging periods as defined in Accounts Receivable Parameters, ACR820D-01.

Infor LN & Baan Manufacturing Tip: Performance Problems in Generate Order Planning (cprrp1210m000)

Kathy Barthelt 0 70903 Article rating: 5.0

When the Generate Order Planning (cprrp1210m000) session is run it can take minutes to days to finish the process.

The performance of this session depends on many settings, like the number of plan items, the number of orders, but it also depends on hardware and database setup.

Here are some guidelines on how performance can be improved...

Infor LX & BPCS Manufacturing Tip: Shop Calendar Maintenance – SFC140D1

George Moroses 0 28674 Article rating: 5.0

This program features multiple-level shop calendar maintenance. You can maintain a shop calendar at the global, facility, or work center level. Global level entries override default values found in Work Center Maintenance, CAP100D1, for any program that uses the shop calendar.

Facility overrides affect all work centers in a Facility and are exceptions to the global level. Exceptions defined at the Facility level apply to all work centers for the facility. Work Center calendar entries are the most specific. These entries apply....

Infor LX & BPCS Materials Tip: Over-Receipts

George Moroses 0 30568 Article rating: 5.0

If Infor LX is set up to prevent over-receipts, you cannot post a receipt quantity that is more than the remaining PO line quantity with the over-tolerance % added to it.

As an alternative, you can:

  • Receive the maximum, remaining line quantity plus over-tolerance percentage quantity, and reject the balance to quarantine or
  • Receive the full quantity into quarantine.


Note: Over-receipt checking applies only to receipts to stock.

Infor LN & Baan Tip of the Week: Limitations of Customer Defined Fields (CDFs)

Kathy Barthelt 0 75157 Article rating: 5.0

Customer Defined fields are fields that can be added to tables, screens, reports, and BODs. Validation and calculation logic can be defined around those fields. This gives you great added capability and flexibility… however, are you aware of the limitations of using CDFs?

  • You cannot define customer-defined fields for tables within Tools (the tl and tt packages).
  • External integrations.....
First4546474850525354Last

Tips:  LX | BPCS | M3

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

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

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.
Previous Article BPCS/LX Tip of the Week: How To Capture Re-Work Time (Part 1)
Next Article BPCS/LX Tip of the Week: Work Center & Machine Locations
Print
80515 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

Note: The Blocked Operations (tisfc0540m000) session displays the blocked operations.

Introduction

Sometimes a problem occurs that must be solved before an operation proceeds. Examples of such situations are:

  • The quality of an intermediate product must first be inspected.
  • A machine is in repair.
  • A supplier cannot deliver an essential component in time.
  • A customer is late with its payments.

In these situations the operation can get the operation status Blocked.

An operation can be blocked:

  • Manually.
  • Automatically by Quality.

Blocking reasons

Every blocked operation must have a blocking reason. The blocking reason of a blocked operation has two purposes:

  • To indicate why the operation is blocked.
  • To determine which actions you can no longer perform on the operation.

Types of blocking

The following actions can be blocked by means of a blocking reason:

  • Reporting a quantity completed.
  • Reporting a quantity rejected.
  • Reporting a quantity to be inspected.
  • Reporting an operation completed.

You normally carry out these actions in the Report Operations Completed (tisfc0130m000) session.

You can define blocking reasons in the Blocking Reasons (tisfc2100m000) session.

Manual blocking

Use the Report Operations Completed (tisfc0130m000) session to block an operation. When you block an operation, you must also enter a blocking reason. If Quality has already blocked the operation, you can only enter a blocking reason, which is more restrictive than the blocking reason of Quality.

Blocking by Quality Managem

Categories