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 LX & BPCS Tip: Product interface list, SYS635D

George Moroses 0 28810 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 32058 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 68408 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 27609 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 29462 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 72915 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.....

Infor LX & BPCS Tip of the Week: Credit Card Processing Within LX

George Moroses 0 27584 Article rating: 5.0

The Credit Card Data Area program, SYS045D, enables you to create and maintain a configuration file that provides a gateway to a third-party payment application. The information you set up with this program is required to allow Infor LX to communicate with the credit card processing application that passes credit card payment information between Infor LX and the credit card providers.

Access: SYS menu

  • Use the Credit Card Data Area screen, SYS045D-01, to...

First4142434446484950Last

Tips:  LX | BPCS | M3

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Handwritten Inventory Tickets

Are you still using handwritten tickets for your inventory?  This method of inventory tracking is slow, and prone to human error.

Putting a simple barcode system in place speeds up the process of tracking inventory movements, reduces the likelihood of mistakes, and creates a recorded history of the who/what/where that can provide valuable insight to those who make critical business decisions for your business.

Not sure where to start? Contact us and we’d be happy to help you take the first step.

Previous Article BPCS/LX Tip of the Week: Email Distribution Lists
Next Article BPCS/LX Tip of the Week: Transactions
Print
47109 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories