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 Baan/LN Tip of the Week: SIC Planning for MRP/MPS Planned Items
Print
37902 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

You can create new macros in the Infor LX Configurable Enterprise Financials CEA107. 

On the Macro Definition window, you define the source file and the field in which you perform an arithmetic or special operation. For example, you can create a macro to accrue sales commission based on revenue. Your source file and field are the Invoice Line History (SIL) file and the G/L revenue (ILREV) field. 

Select Functions to access the Macro Functions window, on which you define the arithmetic, character, or special operation to process against the defined source field. In the previous example of accrued sales commission, you enter an arithmetic operation of multiply (*) and an operand value for the percentage, such as 0.05 for five percent. 

Note:  Previously created user defined macros will have to be updated to include any expanded field sizes in V84. 

To utilize the Security Rules Optimization feature, a system administrator can assign security codes to 100 pre-defined user groups. User groups are created in the Group Security Maintenance (SYS603) program. All users assigned to this group possess the same level of security.   

A system administrator can assign security codes for up to 100 of the user groups. All user groups over 100 are still administered by all security reject/allow rules assigned to them but are not able to utilize the optimized process. 

Each of the security codes and access levels are assigned to user groups and are mapped to the account strings and stored in the Account Cross Reference (CEA106D1) file.   

Once security codes have been assigned, the system administrator must: 

  • Determine which level each group is allowed access.

  • Determine which segment values/account strings are assigned to which user groups.

  • Create security rules for specific segment values/account strings and assign these groups to the created rules.

  • Select the rules to be processed.  Processing can be done in either batch mode or interactively.

  • The Security Rules flag must be on in the CEA Control Parameters program before any rules are effective. 

123468910Last

Theme picker

Tips: LN | Baan

1. Archiving tipcs300

  • Using Session tipcs2260m000:
    • When archiving PCS projects, selecting the "Archive Financial data" option ensures that:
      • Records in tipcs300 are archived to the archiving company.
      • Records are deleted from the original company.
    • If records remain in tipcs300:
      • They may belong to projects that have not been archived.
      • The project may have been archived without selecting "Archive Financial data."
    • Verify there are no errors during the archiving process.
  • Using Session tipcs3500m001:
    • The session "Delete Financial Transactions by Project" can delete records from tipcs300.
    • Note: This session is not for archiving; it removes records without copying them to the archiving company.

2. Archiving ticst300

  • Using Session ticst0250m000:
    • The session "Archive Production Orders" allows:
      • Archiving and deleting records from the original company.
      • Only deleting records from the original company.
    • When executed:
      • Records in ticst300 associated with archived orders are removed.
      • Remaining records belong to unarchived orders.

Statistical Inventory Control (SIC) is an inventory-controlled order system designed to maintain stock levels based on predefined thresholds, rather than being demand-driven like EP (Enterprise Planning). Since SIC relies on inventory levels, it may lead to higher stock levels. To minimize financial risks, SIC is best suited for:

  • Low-cost items.
  • Items with predictable demand or short lead times.


Applications of SIC

  • Low-Cost Items: Particularly effective for inexpensive goods.
  • Predictable Demand or Short Lead Time: Suitable when demand patterns are stable or lead times are minimal.
  • Warehouse-Specific Planning: Useful for planning by warehouse rather than across the supply chain.
  • Trading Industries: Commonly employed in sectors like supermarkets.
  • Immediate Demands: Effective for items required immediately by customers.
  • Ease of Use: Simple to implement and manage.


Limitations of SIC

123468910Last

Theme picker

Categories