The bubble number is maintained at the component level for each component defined on the Bill of Material. It is an extra user-defined reference number that you can use to re-sequence the maintenance screen display or bills of material listings.

In Infor LX, the system displays the bubble number for the existing child items. Engineering drawings often use a bubble number at the component level on the drawing so that same bubble number can be used on the Bill of Material for a link of the component to the drawing. Alternatively, you may use it simply as a method to sequence the BOM.

Be careful of how you assign the number. It is a good idea to assign the number with a consecutive count by 10 leaving room to allow for component additions to the Bill of Material.

If you setup the “From” and “To” Location fields in the Work Center file, this will determine the locations for material issue transactions and production reporting transactions.

The reporting of the transactions happen through production reporting, JIT600, or using the Shop Floor labor posting, SFC600, or Shop Floor Posting from SFC650.

Remember, any location used in the work center file must first be set up in the location master file. Using an MES solution by-passes the need to key any of the data to Infor LX.

You can use a problem code to indicate that a problem exists for a sales invoice. If the invoice-to business partner notifies you about a problem with the invoice and does not pay it, you can link a problem code to the invoice.

In the direct debits procedure, problem invoices are automatically discarded. For each problem code, you can set an option to prevent linked invoices from being selected on reminder letters.

The audit server logs all database actions that change the contents of a table in so-called audit files. The Exchange module can use these audit files, which are useful in a multisite environment because the databases on all sites must have identical data. These audit files can also be used in data conversions.

Only the updates in a specific period are exchanged, which leads to an improvement in performance. Specify this period in the Export Data (Non-Regular) (daxch0233m000) and Export Data (on a Regular Basis) (daxch0234m000) sessions. Changes such as insert, update, and delete are processed and written into the ASCII files. Actions such as drop, clear, and create tables are ignored.

Audit control data is added to the resulting ASCII file. This data consists of a batchline ID, transaction ID, sequence ID, and an indicator. The control data is added at the beginning of each line and is formatted like other data fields such as the enclosing and separator characters.

An update writes two lines to the ASCII file. One line contains the key fields and old values of the updated fields. The other line contains the new values of the key fields and updated fields, even if a key field does not change.

The batchline ID is used for recognition when processing the ASCII files. The transaction and sequence IDs are used to ensure that the transactions are replayed in the same order as on the exporting site. The indicator defines the type of action that is executed on the table. Use the letter I to insert; use the letter D to delete; use the letter U to update with old values; and use the letter N to update with new values.