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 29148 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 32274 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 69002 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 27851 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 29638 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 73457 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 27768 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

Tips: LN | Baan

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Day: LX Inventory Pallet Status Flow

Four fields in the Item/Warehouse record (IIW file) affect the disposition of the

pallet status.

 

1.  Goods Receiving Code: You define these codes in Goods Receiving Maintenance (WHM130). The codes control whether or not the stock passes through inspection, what percentage, or quantity of a delivery to inspect, and the number of quarantine days, if any.

 

2.  Inspection Zone/Inspection Location: Either the Inspection Zone or the Inspection Location must be entered on the Item/Warehouse Master Maintenance screen WHM150D2-01.

 

3.  Default Inventory Status: If the status is 0 (Received) or 1 (Inspection), the item moves from the receiving location to the inspection location in inspection status. If the pallet status is not 0 or 1 (that is, 4 (Available) or 9 (Rejected)), the pallet moves to the inspection location with the default status, but the pallet will not proceed from the Inspection location to the Putaway location. You must manually move the stock.

 

4.  Pallet Status Codes: 0 (Received), 1 (Inspection), 4 (Available), and 9 (Rejected) are the only pallet status codes reserved by the system to update and advance inventory/pallet status. To do this Warehouse Management uses the following rules:

 

·    Rejected inventory goes from receiving to a Reject (type 9) Location with a Location Type A (Rejected) in the Location Extension file (ILE) record. All inventory received into a reject location is set to a pallet/inventory status of Reject (9).

·    Inventory received by Goods Receiving (WHM510) into a Receiving Location takes on the Default Inventory Status that is in the Item Warehouse file (IIW) record.

·    If the Default Inventory Status is 0 (Received), the system places the pallet status at 0 (Received) in the Receiving Location, I (Inspection) in the Inspection Location, and 4 (Available) if moved from Inspection to any palletized location other than rejection. If moved to rejection the Default Inventory Status changes to 9 (Rejected).

Print
51305 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Categories