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 Manufacturing Tip: Performance Problems in Generate Order Planning (cprrp1210m000)

Kathy Barthelt 0 49096 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 23856 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 25561 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 48096 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 24053 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...

Infor LX & BPCS Manufacturing Tip of the Week: Backward Scheduling

George Moroses 0 24864 Article rating: 5.0

Operations are automatically backward scheduled at shop order release time. The backward scheduling algorithm starts with the shop order due date and schedules each operation based upon the standard move and queue times in the routings and the number of days the job is expected to run at standard. The system calculates and stores the operation scheduled start date. The dates may be modified by the shop order maintenance program. The number of days that a job is expected to run an operation is dependent upon the available capacity for that work center and the total hours scheduled for that operation.

The backward scheduling algorithm also considers...

First3334353638404142Last

Tips:  LX | BPCS | M3

This enhancement provides additional views, additional order and line details, improved navigation, and additional capabilities to the IDF Customer Order Inquiry cards and to customer order-related business objects such as Allocations, Customer Invoices, Inventory Transaction History, Promotions, Drop Shipments.

Enhanced Order views based on user roles such as customer service, warehouse/logistics, salesperson/commission, data analysis/management reporting

  • Improved sort, select and filter capabilities
  • Enhanced navigation, data organization and data display
  • Improved customer service access to all transactions throughout the entire customer order life cycle – from quote to order, related invoices, and any RMAs, return orders, related credit memos
  • Improved grouping of related fields
  • New cards to present additional order and order line details
  • Consolidation of cards and card details when appropriate
  • Enhanced Display and Maintain capabilities for drillback to related customer, ship-to, item, carrier, terms, and other master file details
  • Improved display of dates, times and applicable time zones when Region Code time zone support is implemented
  • Multi language Description, Name and Address fields displayed in user’s language, if defined, else in base language

This enhancement provides search capabilities on segment value description in Segment Value List window (WINGSVD).

Segment Value List (WINGSVD):

  • Converted to a standard subfile
  • New action code 10=Search

This makes it easier to locate segment values when defining segment values in Model Account Builder or Alias definition. In addition, WINGSVD has been redesigned as a subfile to enable WebTop grid capabilities.

Last

Tips: LN | Baan

[EasyDNNnews:IfExists:Event]
[EasyDNNnews:IfExists:EventRegistration][EasyDNNnews:EventRegistration:RegisterButton][EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:Payment][EasyDNNnews:Price][EasyDNNnews:EndIf:Payment] [EasyDNNnewsLocalizedText:Eventdate]: [EasyDNNnews:EventDate] [EasyDNNnewsLocalizedText:ExportEvent] [EasyDNNnews:IfExists:EventLocation]

[EasyDNNnewsLocalizedText:EventLocation]: [EasyDNNnews:EventLocation]

[EasyDNNnews:EndIf:EventLocation] [EasyDNNnews:IfExists:EventRegistration]
  • [EasyDNNnewsLocalizedText:NumberOfAttendants]: [EasyDNNnews:EventRegistration:NumberOfAttendants]
  • [EasyDNNnewsLocalizedText:MaxNumberOfTickets]: [EasyDNNnews:EventRegistration:MaxNumberOfTickets]
  • [EasyDNNnewsLocalizedText:NotUsedTickets]: [EasyDNNnews:EventRegistration:NotUsedTickets]
  • [EasyDNNnews:IfExists:Payment]
  • [EasyDNNnewsLocalizedText:Price]: [EasyDNNnews:Price]
  • [EasyDNNnews:EndIf:Payment]
[EasyDNNnews:EventRegistration:InfoMessage] [EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:EventSignUp]

[EasyDNNnewsLocalizedText:AreYouGoing]

[EasyDNNnews:SignUpActionBar]
[EasyDNNnews:EndIf:EventSignUp]
[EasyDNNnews:EndIf:Event]
George Moroses
/ [EasyDNNnewsLocalizedText:Categories]: [EasyDNNnews:Categories]

Infor LX & BPCS Tip: PowerLink

PowerLink is a Windows-based client for end-users within the Infor Development Framework (IDF). PowerLink allows exports/imports from/to the ERP database, but how much do you really know about it? Here is some helpful information about PowerLink.​

Why does PowerLink sometimes fail to export all records?
There's not a finite amount of records that PowerLink can export. However, PowerLink export was never intended to handle large volumes of data. It was designed as a quick snapshot of a fairly small subset and a simple view of the user's PowerLink card. 

What is the maximum amount of data that can be exported?
The maximum number of records is only limited by the system resource like memory, etc. When the system runs out of resources, an OutOfMemory error should occur. In previous testings, we have exported +1 million records, although the size of records differs greatly between business objects, the total size of the data could be an issue. For larger volumes of data, customers should investigate other tools such as the iSeries Access "Data Transfer from iSeries Server" feature to download directly to Excel.

How do I know if the size of the data is an issue?
1. When exporting to an external file (text, HTML) then importing to Excel: You can easily check the output (text, HTML) to see if the intermediate output has all the records. This can be done by visual inspection or through the use of column totals. Simply compare between the output and what you see in PowerLink. If the exported file has all the records, then the problem is definitely Excel.
2. When exporting to clipboard, then copy/paste to Excel: There is a clipboard export size limit that is controlled through client preferences. Check the exported data in the clipboard, and see if it contains all the records or only partial records due to the size limitation set in client preferences. If limited, change the client preferences using Customize from the Main browser > Preferences > Miscellaneous tab > Limit Clipboard Export, and try the export again. If the clipboard has all the records the problem is in Excel, which we don't have jurisdiction over.

Suggestions for improving the export process. 

  1. Reduce the number of columns seen in the view. This will serve to reduce the data being exported and may increase the number of records that can be exported. 
     
  2. Reduce the complexity of the view. If the view has one column that lives on a related object, then it has to build SQL behind the scenes to get that related record. If all of the columns come from a single business object, then the processing will be significantly faster.
     
  3. Export to HTML, which can be opened directly by Excel, Access, and many other programs. This reduces the processing of the export formatting because PowerLink needs only to put begin and end tags around each data element. This will also preserve column alignment when Excel or other programs open the file.
     
  4. Unless you are exporting a fairly small volume of data, export to a file, not clipboard. Clipboard is held in memory until the entire view is read, and records are written to the file as they are retrieved.
     

 Also see KB 1357068 for more information about testing your view.

Print
47056 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories