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

Crossroads RMC Takes Polar to LX 8.3.4

Crossroads RMC 0 25941 Article rating: No rating

Polar Beverages, the largest independent soft drink bottler in the United States, went live on Infor LX 8.3.4 on January 16, 2017. Polar partnered with Crossroads RMC for this important technology initiative. Included in the implementation were the Finance Supply Chain and Manufacturing modules. Phase 2 will include Adirondack Beverages, a subsidiary of Polar. This project will begin in Q3 2017.

BPCS/LX Tip of the Week: Handwritten Inventory Tickets

Anthony Etzel 0 19104 Article rating: No rating

Are you still using handwritten tickets for your inventory?  This method of inventory tracking is slow and prone to human error.

Putting a simple barcode system in place speeds up the process of tracking inventory movements, reduces the likelihood of mistakes, and creates a recorded history of the who/what/where that can provide valuable insight to those who make critical business decisions for your business.

Not sure where to start? Contact us and we’d be happy to help you take the first step.

Baan/LN Tip of the Week: Ledger Default Account

Kathy Barthelt 0 31332 Article rating: No rating

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.

BPCS/LX Tip of the Week: Email Distribution Lists

Anthony Etzel 0 21867 Article rating: No rating

Email Distribution Lists are new in Infor LX Version 8.

With this feature, users can create groups to which they may add internal or external email addresses, and in turn, use the name of the group when sending out the email.

The email distribution list eliminates the need for a program change if recipients need to be added to or deleted from the group. 

Optimize Your Manufacturing Today!

RSS
First9495969799101102103Last

Theme picker

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

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE
Ledger Account Blocked Error
When attempting to post to a ledger account, users may occasionally encounter an error indicating that the ledger account is blocked. To resolve this issue, navigate to the Chart of Accounts session (tfgld0508m000) and select the Miscellaneous tab. Once there, review the Blocking field. The available settings are:

  1. Free
  2. Blocked for manual input (integration transactions and other automatic transactions can be posted with this setting)
  3. Blocked for all purposes.

OPERATIONS
Absorbing Cost Items into Projects
To absorb the cost of cost items into specific projects, you'll need to handle them as customized items. However, cost items cannot directly be defined as customized items. Customized items must be physical, either manufactured or purchased.

That said, it's still possible to absorb cost items into a project, although indirectly. Here's how:

  1. Set Up Ledger Account: First, create a new ledger account in session tfgld0508m000 and set the type to "PCS" (project) in the operations management integrations. This account will be used for matching and approving purchase orders for cost items.

  2. Create and Activate Projects: Ensure that the necessary projects are created and set to active status.

  3. Purchasing Cost Items:

    • If needed, create the cost items.
    • Create a purchase order for the cost items without referencing a project number.
  4. Matching PO to Costs:

    • When matching the purchase orders in session tfacp2107m000, select "Add Costs" from the specific menu on the toolbar (you'll need to be in the matching details to access this).
    • This will open session tfacp1133s000, where you will enter the previously specified ledger account number.
    • Once done, the "PCS Transactions" option on the toolbar becomes available. Selecting this brings up session tipcs3140m000 (General Actual Project Costs).
       
  5. Disbursing Costs to Projects: In session tipcs3140m000, the PO costs for the cost items can be disbursed to any open and active project.

Since these are cost items, they won't go into stock. The key is ensuring that the cost disbursement ("Add Costs") is correctly linked to the appropriate project, giving users visibility of the cost items as general project costs.


TECHNOLOGY
Adding a Timestamp to LN Standard Tables
Table Timestamp Definitions (ttadv4136m000)

Use this session to define timestamps for Infor LN tables. A timestamp is an additional column that stores the date and time of the last change for each record.

Timestamps are utilized by features like the extraction logic of CPM Enterprise Analytics. They enable CPM to perform incremental data extractions. For example, CPM can use the timestamps to extract records that were changed during the last week in a weekly extraction process.

To Create Timestamps:

  1. Enter the Tables: In this session, specify the tables for which you want to define timestamps.

  2. Convert and Reconfigure: Run the Convert to Runtime Data Dictionary (ttadv5215m000) session to convert the table definitions to the runtime data dictionary and reconfigure the tables.

  3. Restart Session: Log off and log back on to apply the changes.

IMPORTANT!
To avoid issues with locked tables, ensure that all users have logged off before starting the reconfiguration.

For more information, refer to the online help of the Convert to Runtime Data Dictionary (ttadv5215m000) session.

Previous Article Infor LN & Baan Tips & Tricks for FINANCE: Ledger Account Blocked Error
Next Article Infor LN & Baan Tips & Tricks for OPERATIONS: Absorbing Cost Items into Projects
Print
1141 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories