Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Executive

Infor LN & Baan Tips & Tricks for EXECUTIVES:

Operations: Copying EBOMs - Which copying method should I use?

To determine which copying method you must use, answer question 1 and follow the instructions.

Question 1: Is the source component a project item (that is, is a project defined in the first segment of the item code)?

  • If the answer is yes, proceed with question 3.
  • If the answer is no, proceed with question 2.


Question 2: Is the target component a project item?

  • If the answer is yes, select copy method NonProj Item to Proj Item.
  • If the answer is no, proceed with question 4.

Question 3: Is there a relationship with the same project?

  • If the answer is yes, select copy method EBOM to Production BOM Only.
  • If the answer is no, proceed with question 4.


Question 4: Is there a relationship with the target item?

  • If the answer is yes, proceed with question 5.
  • If the answer is no, select copy method No Copy Action.


Question 5: Does the item exist already?

  • If the answer is yes, select copy method EBOM to Production BOM Only.
  • If the answer is no, select copy method Copy E-Item to Item.

Technology: Using audit files in the Exchange module

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.

Finance: Problem Invoices

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.

Previous Article Infor LX / BPCS Tips & Tricks for Finance: Inventory Period Balance Freeze
Next Article Infor LN & Baan Tips & Tricks for Operations: Copying EBOMs - Which copying method should I use?
Print
49547 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Enhances purchase order efficiency by automatically calculating the Vendor Delivery Date based on user input.

  • When a purchase order line is created, the user enters the item, order quantity, and Due Date.

  • LX automatically calculates the Vendor Delivery Date, adding buffer time for quality control, testing, and inspection activities.

  • If the Due Date is revised, an informational message prompts the user to review and potentially update the Vendor Delivery Date.

Enhancements:

  • A new PUR820 system parameter enables automatic recalculation of the Vendor Delivery Date.

  • Instead of a manual reminder, PUR500 now issues a message: “Vendor Delivery Date recalculated,” showing the updated date.

Benefits:

  • Eliminates the need to manually review and update the Vendor Delivery Date.

  • Removes the need to delete and recreate PO lines to trigger automatic date calculation.

Read more

Enables integration between LX and Infor OS Federation Services (IFS) to automate user provisioning.

  • Bi-directional user synchronization between Infor OS and LX:

    • Infor OS user creation or changes automatically create or update users in LX.

    • IBM i user profiles can be created if needed.

    • Updates to SYS600 user data are reflected in Infor OS.

  • Security Role Integration:

    • LX Security Roles and Units are published as IFS Security Roles via SyncSecurityRoleMaster BODs.

    • LX receives inbound SyncSecurityUserMaster BODs from IFS to create or update user records in SYS600.

    • SYS600 Exit Points trigger ProcessSecurityUserMaster BODs to request user creation or updates in IFS on behalf of LX.

Available Versions: 8.3.5, 8.4.1, 8.4.2

Read more
FirstLast

Tips: LN | Baan

Categories