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: Business Partner Structures

Kathy Barthelt 0 98897 Article rating: No rating

In ERP LN, users can define a distributed business partner organization by defining parent business partners to link the business partners with different roles.

In Baan IV, users can define a distributed business partner organization in the Maintain Concern Structure of Trade Relations (tccom3101m000) session.

Harsco Rail Goes Live With the RMC3 Data Collection Solution

Crossroads RMC 0 39620 Article rating: No rating

Harsco Rail, an industry leader in the railway track maintenance, has completed the first phase of their implementation of the Crossroads RMC Data Collection Solution for Baan V. The initial implementation included receiving and putaway. Harsco’s data collection project manager reports, “When I ask them (the users) how it’s going, they smile. I have had nothing but very positive feedback. It’s been very uplifting for me to work on this project and have it so well received.” The next phase of the implementation will include Report Operations Complete, Inventory Transfers, and Stock Inquiry.

Baan/LN Tip of the Week: Tax Exemption Certificates

Kathy Barthelt 0 89034 Article rating: No rating

In Baan IV, tax exemption processing is supported only on sales orders for non-tax provider users.

In Infor LN, tax exemption certificate processing is also performed for purchase orders, and for sales orders if users use a tax provider.

Users can define tax-exemption certificates in the following sessions:

  • Tax Exemptions for Sales (tcmcs1142m000)
  • Tax Exemptions for Purchasing (tcmcs1560m000)
  • Register Warehouse for Tax Exemptions (tcmcs1561m000)

 

BPCS/LX Tip of the Week: The Machine Master Part 1

Anthony Etzel 0 86021 Article rating: No rating
Understanding:

The Machine Master File


Machines are associated with a work center. For example, in the work center you may have multiple machines and each machine can have a unique machine ID. If there are several machines that perform the same function, they may operate at different speeds and efficiencies. Setting up the machine master can be a benefit for planning capacity and shop order throughput.

Baan/LN Tip of the Week: Aborted Finalization Run

Kathy Barthelt 0 79986 Article rating: No rating
When a finalization run is aborted and in the batches selected for this finalization run are transaction types having the update mode finalization, you must use the Restart Finalization Run session. This session can be found in the Transaction Processing menu of the General Ledger Module of the Finance Package.

BPCS/LX Tip of the Week: SFC600

Anthony Etzel 0 83322 Article rating: No rating
In addition to SFC650, this ERPLX program is also used to capture and post shop floor information.

The key difference between the two is that SFC600 only captures Labor (run time) reporting, machine time, downtime and indirect time.

If you use SFC600, then all shop order material receipts and issues would be captured using INV500.

Both Inventory and Shop Floor Transaction entry is keyboard dependent, unless you incorporate an automated method like an MES solution to capture the data.

BPCS/LX Tip of the Week: Downtime Reasons

Anthony Etzel 0 81926 Article rating: No rating

Using SFC600 to enter downtime.

You are tracking downtime and using SFC600 to enter the downtime, but you don’t know where to go to setup downtime reasons. You can set up the downtime reason codes in the INV application by selecting the reason code maintenance program INV140D1.

Once you are in the reason code maintenance program, position to the transaction effect code “D”. Using the transaction effect code “D” you can now setup as many downtime reason codes as needed. The reason code field is alpha numeric, so be creative with your reason code assignments.

Baan/LN Tip of the Week: Restricted User Access

Kathy Barthelt 0 76829 Article rating: No rating
Administrators are able to restrict access in Baan in several ways – including Companies, Packages, Modules, Sessions, and Tables – using the Authorization capabilities of the system.

In Baan IV, access can be given or denied on a user by user basis.

In Baan V and LN, the Authorization Management System can provide or deny access based upon roles to which users are assigned.

First130131132133135137138139

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
1406 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories