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: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Indirect Time Reporting

In Infor LX, there are two ways to enter indirect labor. You can use either SFC600 or SFC650.

  • If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
  • If you use SFC650 and enter a reason code for the indirect, the reason code is not written to the labor Ticket file.

In either case, the reason code is not validated from the transaction file because there is no indirect transaction code. The indirect code that can be setup is machine downtime. If you need to validate and track indirect by reason and validate the reason code, then you may want to explore an MES solution that works with Infor LX.

 

Previous Article Baan/LN Tip of the Week: Differences Between Constraint Planning in Baan IV and Enterprise Planning in LN
Next Article What You Don’t See Can Hurt You
Print
35991 Rate this article:
No rating
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