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

George Moroses
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip: Capacity Planning – Resource Requirements Reports

Resource Requirements Report (CAP260D) generates five capacity reports:

  • Labor Resource Requirements
  • Machine Resource Requirements
  • Setup Resource Requirements
  • Setup and Labor Requirements
  • Setup and Machine Requirements

The Labor Resource Requirement report lists requirements that are calculated from the run hours on each routing and the MRP/MPS demand in the Capacity Requirements Detail File (LCR). The calculation does not consider crew size.

The Machine Resource Requirement report lists machine hour requirements based on routings and the MRP/MPS demand in the Capacity Requirements Detail File (LCR).

The Setup Resource Requirements report lists setup labor requirements based on routings and the MRP/MPS demand in the Capacity Requirements Detail File (LCR).

The last two reports combine setup hours with labor hours and setup hours with machine hours to provide two separate reports that summarize the requirements by work center with totals by department. The system computes requirements similarly to the way it computes them on the other reports.

Have questions on this process or need some help? Contact us! Our experienced consultants will be glad to assist you.

800.762.2077

Previous Article 6 Ways Disconnected Data is Harming Your Business
Next Article Infor LN & Baan Tip: What is the GRNI Reconciliation Process?
Print
10100 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

The Infor Development Framework (IDF) re-architects the way a user interacts with the application. IDF provides an efficient, task-oriented process to view application information that is contained within Infor LX. IDF enables users to configure their view of the application data without modifying the core application and its supportability.

The examples below describe how users can configure their display of data and maximize overall productivity:

  • Arrange application information into multiple groupings and sequences that make sense for the job.
  • Hide information that does not apply to a particular job or task.
  • Filter records to show only the information that applies to the job or task that the user is performing.
  • Customize the information for an individual user, for a group of users, or for all users.
     

Did you know?  Product interface list, SYS635D

This program creates a report that contains all interface program call records that were created for the Infor LX programs specified in the range on this screen. The report contains a line for each record found. The line displays the following information:

  • The name of an Infor LX program that contains a user exit to an add-on program
  • The interface point in the Infor LX program, that is, an identifier of the point in the program code where the user exit is requested
  • The execution sequence number of the record, because more than one add-on program can exist that can run from the same interface point
  • The add-on program to call at the interface point. The Add-on Product Interface file, ZXI, stores the records.

Access: Menu SYS

First3637383941434445Last

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:

1345678910Last

Theme picker

Categories