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
23380 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

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

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

In LN, you can differentiate between items at various suppliers:

  • Locations (warehouses),
  • Purpose (planning, purchase)
  • Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:
 
  • Items - Planning (cprpd1100m000)
  • Check Item Data by Warehouse (whwmd2210m000)
  • Item Supplier Plan (cpvmi0530m000)
These sessions define entities that have an n-to-1 relationship with the general item data.

 

First151152153154156158159160Last

Theme picker

Categories