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: Getting the Most Out of the Shop Order Inquiry Program – Part 2

Understanding: How many hours remain in total and at each operation?

Now let’s look at what information is being supplied from the shop floor.

It’s not uncommon for transaction reporting to be captured manually on the shop packet that was issued to the factory floor when the SO was released.

The big question is, is anything done with the data? Is it collected and keyed to a  spreadsheet and not shared, or is the transaction data keyed to SFC600? If it is being keyed, ask how often and by whom? Some companies use alternative methods to capture transaction data that do not require batch keying via a keyboard.

Not a lot of data is required to be keyed to SFC600 in order for the SO Inquiry to be useful. The data that should be reported for the transaction process is as follows:

  • The type of hours being reported – machine, run labor, setup labor
  • If reporting setup and run labor you want an employee clock number
  • The shop order and the operation that is being reported
  • Is the operation complete
  • How many good were produced at this operation
  • How many hours – the numbers of hours are critical. Do the employees estimate how many hours they worked, or do they track actual time started and stopped in order to calculate the actual number of hours.

Based on what is captured and how often will have an impact on the SO inquiry screen. Understanding the batch times as to when the transactions are keyed will provide you with the window as to the SO status at that point in time. Or, are they keyed as they happen in a near real time fashion so that you can have a more current view of the factory floor.

Previous Article Baan/LN Tip of the Week: ERP Setup - Pros & Cons
Next Article Downtime Tips
Print
34830 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

Enterprise General Ledger (EGL) provides audit attributes to track journal entry changes and approvals.

To implement this enhancement, you can request and apply MR 81026.

This enhancement provides audit attributes for the last maintained user, date, time, and approval user, and date, and time on the Financial Journal Entry and Financial Journal Entry Lines. This audit function provides visibility to who and when the journal was last maintained and to who and when the journal was approved.

The programs or areas impacted include:

  • Financial Event
  • Financial Journal Entry
  • Financial Journal Entry Line
  • Financial Journal Entry Detail Line
  • Post Multiple Events

Did you know CLD provides you with the following benefits?

▪ You can journalize and post-transaction data from any third-party application or Infor LX subsystem to the Configurable Ledger (CLD).

▪ You can generate multiple journal entries across different charts of accounts, ledgers, and books within the CLD from one transaction line.

▪ You can automatically post transaction amounts across different books using an appropriate exchange rate between the batch transaction currency and target book currency.

▪ You can use validation reports to identify validation errors within the files that contain batch transaction data and then you can make any necessary corrections before resubmission.

▪ You can use standard CEA grouping and summarization options for journals created during Batch Transaction Processing.

▪ You can interface GLD journal entries into CEA for the BPCD version of Infor LX. This allows data to be interfaced into CEA without changing the way data is processed through Infor LX subsystems.

First2223242527293031Last

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