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
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Ledger Default Account

If you do not wish to define a detailed mapping to various ledger accounts for specific integration transactions, you can map the corresponding integration document type to a default account. All the transactions of the integration document type for which an account cannot be determined based on the mapping scheme details, are posted to the default account.

 

The mapping of an integration document type to a default account is direct, without the need for element groups and mapping elements. No distinction is made on any of the transaction details.

 

Default accounts can be used in two ways:

  • Instead of a detailed mapping to various ledger accounts. All the transactions are posted to the same account. For example, all warehouse receipts are posted to the Inventory ledger account, without any distinction.
  • In addition to a detailed mapping. If a transaction cannot be mapped based on the detailed mapping scheme, it is posted to the default account.
Previous Article 2017 Top Ten Trends in Modern Demand-Driven Manufacturing
Next Article BPCS/LX Tip of the Week: Handwritten Inventory Tickets
Print
31357 Rate this article:
No rating
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 Baan IV, inventory valuation is done by standard costs, unless you use projects. If you use projects, it is based on estimated or actual costs.

In Baan V and LN, you have the choice of LIFO, FIFO and MAUC (Moving Average).

Sales Order Acknowledgements in Baan IV:
After a sales order is entered in Baan IV, users can print an order acknowledgement in Print Sales Order Acknowledgements/RMAs (tdsls4401m000), after which it can be sent to the customer.

Sales order acknowledgements in ERP LN:
In Infor LN, users can still use the Print Sales Order Acknowledgements/RMAs (tdsls4401m000) session to print order acknowledgements, however, the following functionality is added to this session:

  • In the Documents to Print field users can select whether to print order acknowledgments and/or return material authorizations.
  • With the Promotions check box users can indicate whether to print promotions on the order acknowledgement, if promotions apply to the order.
  • Users can control the printing of order acknowledgements based on the order amount and/or the delivery date.

These conditions only apply for order types that do not have the Print Sales Order Acknowledgements/RMAs (tdsls4401m000) linked as a mandatory activity to the order type in the Sales Order Type - Activities (tdsls0560m000) session.

First141142143144146148149150Last

Theme picker

Categories