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

Kathy Barthelt

Infor LN & Baan Tips & Tricks for FINANCE: Integration Transactions - Compression

Compression

Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.
  • The destination financial company.
  • The transaction type and series.
  • The ledger account and dimensions.
  • The transaction currency.
  • The fiscal year and the financial period, the tax period, and the reporting period.
  • The integration document type and the Debit/Credit indicator.
  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

Previous Article Infor LX/BPCS Tips & Tricks for FINANCE: Default Billing Reason Code from User Order Class
Next Article VJES (Visual Job Execution Software) for Infor LN & Baan
Print
2356 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

In previous releases of LN, the Assembly Control Bill of Material (BOM) offered limited flexibility. For each end item configuration, users were required to create unique Engineering Modules, which are used to determine the assembly parts that are consumed in a specific Line Station during a specific operation.

If LN is integrated with Design Studio, previously called Infor CPQ, BOM structures can be maintained in Design Studio for Assembly Control. These structures can include non-configurable parts that are directly linked to configurable items. When communicating these structures to LN using the Assembly Control, Product Variant Structure (tiapl3510m000) session, the structures were rejected because non-configurable parts were not supported by the session logic.

In this release, BOM structures that include non-configurable parts can now be accepted in LN. Consequently, if LN is integrated with Design Studio, it is no longer required to use the Engineering Module. Using the Engineering Module has become optional.

First4950515254565758Last

Theme picker

Categories