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

Baan/LN Tip of the Week: Old Porting Set

Kathy Barthelt 0 80435 Article rating: No rating

Here are some issues that you might run into if you stay on an old porting set too long:

  • Incompatibility because of operating system patches
  • Printing issues because of out-of-date libraries
  • Potential performance issues if binaries are not updated
  • Updating third-party products may not be possible because of dependencies
  • Limited support from Infor
  • Issues with updating database software/patches because of dependencies (if the database is also running on the same server as the application)

Need help getting on a newer porting set? Let us know! We’d be happy to help.

BPCS/LX Tip of the Week: Establish Costing For Purchased Items

Anthony Etzel 0 57383 Article rating: No rating

How Does Infor LX Establish Costing For Purchased Items?

In LX, you will establish a standard cost (you define the standard) that LX will use for the purchase items. You also need to establish in LX the Cost Type, the Cost Bucket, and the Cost Set needed for cost accounting.

Baan/LN Tip of the Week: Default Order Frequency

Kathy Barthelt 0 91177 Article rating: No rating

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In Infor LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.

Crossroads RMC Releases NextTrack Sales – Sales Analysis Tool for Baan, Infor LN and IBM i

Kathy Barthelt 0 35916 Article rating: No rating

Crossroads RMC is proud to announce the official release of NextTrack Sales – a sales analysis tool for Baan, LN, and IBM i. NextTrack Sales allows you to get the “big picture”, or get down into the finer details. The tool provides a sophisticated pivot grid and charting functionality, export to Excel, PDF printing, and emailing capabilities to bring your sales data to life. Analyze your Baan Sales data to examine trends, identify market opportunities, and much more. Click here for more details.

Mount Olive Pickle Chooses Crossroads RMC for BPCS Data Collection

Anthony Etzel 0 32270 Article rating: 5.0

Mount Olive Pickle, a leading producer of pickles, peppers, and relishes in the United States, has chosen Crossroads RMC as their solutions vendor for data collection and manufacturing production reporting. In the first phase of the project, the Crossroads team will implement the Inventory Visibility Data Collection software connected to BPCS. The transactions to be implemented include PO Receipts, Transfers, Component Issues, Cycle Counting, and Production Receipts.  

CROSSROADS RMC MEMBERSHIP IN COMMON USER GROUP / EXHIBIT AT COMMON CONFERENCE

Crossroads RMC 0 31150 Article rating: No rating

The  Annual Meeting is COMMON’s largest educational event of the year, with four full days of in-depth IBM i, AIX, and Linux-related education that includes all-day pre-conference workshops, open labs, and a wide variety of regular-length sessions. It is the annual meeting of the COMMON membership and the largest gathering of the Power Systems user community. Come see us in Booth 203.

 

Crossroads RMC is also proud to announce our membership in COMMON for 2016. We look forward to partnering with COMMON and providing valuable content to their user community and sharing in dialogue with users across the country.

Baan/LN Tip of the Week: Setting Up New Employees in LN

Kathy Barthelt 0 72869 Article rating: No rating

In LN, the People package is used to register the employee’s hours and expenses. To support the People package, the Employees – General (tccom0101m000) session only contains the general employee data.

The title of the Employees – General (tccom0101m000) session was changed to Employees – General (tccom0101m000).

From the Employees – General (tccom0101m000) session, users can start the following sessions to define the more specific employee data:

  • Employees – People (bpmdm0101m000).
  • Employees – Project (tppdm8101m000).
  • Employees – Service (tsmdm1140m000).
  • Skills by Employee (tcppl0120m000).
  • Employees by Team (tcppl0150m000).
  • Roles by Employee (tcppl0170m000).

After users define the employees, users can also start the listed sessions from the Employees Dashboard (bpmdm0101m100) session in People.

First115116117118120122123124Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE: Clear Rounding Differences for Documents with Period Change (tccri7214m000)

Use this session to adjust the rounding difference transactions, calculated during the internal conversion, for inter-period postings.

Inter-period postings are the postings made to the ledger accounts defined in the Finance Company Parameters (tfgld0503m000) session for fiscal and reporting period changes.

If inter-period postings exist, very big rounding differences are calculated . If you run this session, those rounding differences are replaced with values that properly deal with an observed period change.

If inter-period postings exist, during the internal conversion rounding differences can be calculated for the wrong period. If you run this session, those rounding differences are deleted and the rounding differences are created for the correct period.



OPERATIONS: Sales Contract Linked Documents (tdsls3506m000)

Use this session to view the documents linked to a sales contract. You can view these documents only when a sales order line or a sales schedule line is linked to a sales contract line.

Note: 

  • You can view this session only if the Contracts check box is selected in the Sales Parameters (tdsls0100s000) session.
  • You can use the Linked Document option from the References menu to view the details of a specific linked document.


Field Information

Contract: The code of the sales contract.

Description: The description of the sales contract

Line: The sequence number of the sales contract line.

Sales Office: The code of the sales office.

Description: The description of the Sales Office

Linked Document: The document type that is linked to the sales contract line.

Note: This field can be set to Sales Order Line or Sales Schedule Line only.

Linked Document Company: The company in which the document is linked to the sales contract line.

Linked Document: The code of the document that is linked to the sales contract line.

Note: 

  • The code of the sales order is defaulted from the Order Line field in Sales Order Lines (tdsls4101m000) session.
  • The code of the sales schedule is defaulted from the Schedule field in the Sales Schedule Lines (tdsls3107m000) session.

Linked Document Reference: The reference number of the linked document.

Note: 

  • The line number of the sales order line is defaulted from the Line field in the Sales Order Lines (tdsls4101m000) session.
  • The line number of the sales schedule line is defaulted from the Line field in the Sales Schedule Lines (tdsls3107m000) session.

Link Sequence: The sequence number of the linked document.


TECHNOLOGY: Audit Fields by Table (ttaud3125m000)

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.
     

Previous Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Load Audit Tables for Profile (ttaud3220s000)
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Clear Rounding Differences for Documents with Period Change (tccri7214m000)
Print
6867 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories