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

Anthony Etzel
/ Categories: ERP News, Event / News, IDF

IDF: Defining the Attributes for a New Object

Attributes are the fields you define in your System i file.

You can begin by building your attribute list in Integrator by synchronizing the object with the host. This process reads the file definition from the System i and builds your list of attributes. The synchronize process will automatically run and read the definitions for the first occurrence of this file name within the library list. You can repeat this process manually multiple times if you change the file definition on the host by using the ‘Synchronize with Host’ option. However, the synchronization process will not recognize changed field names.

Non on key field attributes: The integrator requires a unique key for each object. If the host file already has a key, the synchronization process will automatically identify fields as part of the key as well as add a sequence number to multiple key parts. If the file does not have a unique key, you must either create a keyed logical file or identify the key manually. Key fields are the default sort order for all list views for an object.

Previous Article Why do you need OTTO? Let’s let our customers tell you…
Next Article Infor and Crossroads RMC Partner to Drive Success at Ridewell
Print
25171 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Here are 5 ways you can motivate your employees to give their best every day:

1. Train Your Employees

2. Give Your Employees the Right Tools

3. Automate Processes

4. Give Your Employees Real-Time Feedback

5. Provide Incentives to Do More

Optimize Your Manufacturing Today!

Previously, Material Requirements Planning (MRP) preferred practices meant that the component’s due date was the same as the parent’s shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The user is now able change how the due date is determined for multi-level shop orders. If the Due Date of Children parameter is set to 1=Yes, the due date of the child components is the same as the release date of the parent. If the parameter is set to 0=No, the due date is the day before the release date of the parent.

Optimize Your Manufacturing Today!

First7980818284868788Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories