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

Baan/LN Tip of the Week: Default Order Frequency

Kathy Barthelt 0 85113 Article rating: No rating

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In Infor LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.

Crossroads RMC Releases NextTrack Sales – Sales Analysis Tool for Baan, Infor LN and IBM i

Kathy Barthelt 0 32956 Article rating: No rating

Crossroads RMC is proud to announce the official release of NextTrack Sales – a sales analysis tool for Baan, LN, and IBM i. NextTrack Sales allows you to get the “big picture”, or get down into the finer details. The tool provides a sophisticated pivot grid and charting functionality, export to Excel, PDF printing, and emailing capabilities to bring your sales data to life. Analyze your Baan Sales data to examine trends, identify market opportunities, and much more. Click here for more details.

Mount Olive Pickle Chooses Crossroads RMC for BPCS Data Collection

Anthony Etzel 0 29369 Article rating: 5.0

Mount Olive Pickle, a leading producer of pickles, peppers, and relishes in the United States, has chosen Crossroads RMC as their solutions vendor for data collection and manufacturing production reporting. In the first phase of the project, the Crossroads team will implement the Inventory Visibility Data Collection software connected to BPCS. The transactions to be implemented include PO Receipts, Transfers, Component Issues, Cycle Counting, and Production Receipts.  

CROSSROADS RMC MEMBERSHIP IN COMMON USER GROUP / EXHIBIT AT COMMON CONFERENCE

Crossroads RMC 0 28277 Article rating: No rating

The  Annual Meeting is COMMON’s largest educational event of the year, with four full days of in-depth IBM i, AIX, and Linux-related education that includes all-day pre-conference workshops, open labs, and a wide variety of regular-length sessions. It is the annual meeting of the COMMON membership and the largest gathering of the Power Systems user community. Come see us in Booth 203.

 

Crossroads RMC is also proud to announce our membership in COMMON for 2016. We look forward to partnering with COMMON and providing valuable content to their user community and sharing in dialogue with users across the country.

Baan/LN Tip of the Week: Setting Up New Employees in LN

Kathy Barthelt 0 66470 Article rating: No rating

In LN, the People package is used to register the employee’s hours and expenses. To support the People package, the Employees – General (tccom0101m000) session only contains the general employee data.

The title of the Employees – General (tccom0101m000) session was changed to Employees – General (tccom0101m000).

From the Employees – General (tccom0101m000) session, users can start the following sessions to define the more specific employee data:

  • Employees – People (bpmdm0101m000).
  • Employees – Project (tppdm8101m000).
  • Employees – Service (tsmdm1140m000).
  • Skills by Employee (tcppl0120m000).
  • Employees by Team (tcppl0150m000).
  • Roles by Employee (tcppl0170m000).

After users define the employees, users can also start the listed sessions from the Employees Dashboard (bpmdm0101m100) session in People.

Baan/LN Tip of the Week: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt 0 82004 Article rating: No rating

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

BPCS/LX Tip of the Week: Changing the Master Schedule

Anthony Etzel 0 54494 Article rating: No rating

You can change your master schedule by specifying the type of master schedule update to perform. You can run a Net Change or Regenerative Schedule.

You also have the ability to clear the lower level requirements out of the Planned and Firm-Planned Order file.

First108109110111113115116117Last

Tips:  LX | BPCS | M3

[EasyDNNnews:IfExists:Event]
[EasyDNNnews:IfExists:EventRegistration][EasyDNNnews:EventRegistration:RegisterButton][EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:Payment][EasyDNNnews:Price][EasyDNNnews:EndIf:Payment] [EasyDNNnewsLocalizedText:Eventdate]: [EasyDNNnews:EventDate] [EasyDNNnewsLocalizedText:ExportEvent] [EasyDNNnews:IfExists:EventLocation]

[EasyDNNnewsLocalizedText:EventLocation]: [EasyDNNnews:EventLocation]

[EasyDNNnews:EndIf:EventLocation] [EasyDNNnews:IfExists:EventRegistration]
  • [EasyDNNnewsLocalizedText:NumberOfAttendants]: [EasyDNNnews:EventRegistration:NumberOfAttendants]
  • [EasyDNNnewsLocalizedText:MaxNumberOfTickets]: [EasyDNNnews:EventRegistration:MaxNumberOfTickets]
  • [EasyDNNnewsLocalizedText:NotUsedTickets]: [EasyDNNnews:EventRegistration:NotUsedTickets]
  • [EasyDNNnews:IfExists:Payment]
  • [EasyDNNnewsLocalizedText:Price]: [EasyDNNnews:Price]
  • [EasyDNNnews:EndIf:Payment]
[EasyDNNnews:EventRegistration:InfoMessage] [EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:EventSignUp]

[EasyDNNnewsLocalizedText:AreYouGoing]

[EasyDNNnews:SignUpActionBar]
[EasyDNNnews:EndIf:EventSignUp]
[EasyDNNnews:EndIf:Event]
Anthony Etzel
/ [EasyDNNnewsLocalizedText:Categories]: [EasyDNNnews:Categories]

BPCS/LX Tip of the Week: Understanding What Goes On – Out on the Factory Floor

Ok… so you want to know the status of a specific shop order that was released two days ago.

What do you do?

It’s a sure bet that you have a manager, supervisor, or planner who can walk the floor and find the order at whatever work center it happens to be at. He/she can then answer “what operations have been completed and how many were completed?” All this requires leg work, and of course, a fair amount of time.

Now, if you have setup your BPCS master files properly, and you report transaction activity, you should be able to get those shop order statuses much faster using the SFC300 Shop Order Inquiry Screen.

At your fingertips you can see:

  • Release date & due date
  • How many hours remain in total and at each operation
  • The quantity required, what was finished and the remaining quantity
  • What components (materials) have been issued

Pretty basic information, right? Are you getting what you need to know? If not, then you may want to reexamine how your BPCS files are setup and what transactions along with their frequency are captured.

Optimize Your Manufacturing Today!

Previous Article BPCS/LX Tip of the Week: Role-Based Security
Next Article BPCS/LX Tip of the Week: Inventory Transaction Post to G/L by Cost Type
Print
29554 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories