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
33352 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

I know a lot of our customers are considering virtualization projects. I came across this, and thought it might be useful:

The advantages of virtualization include the following:

• You get more out of your existing resources. Pool common infrastructure resources and break the legacy “one application to one server” model with server consolidation.

• You can reduce datacenter costs by reducing your physical infrastructure and improving your server to admin ratio. Fewer servers and related IT hardware means reduced real estate and reduced power and cooling requirements. With better management tools, you can improve your server to admin ratio so personnel requirements are reduced.

• You can increase the availability of hardware and applications for improved business continuity.

• Securely back up and migrate entire virtual environments with no service interruptions. Eliminate planned downtime and recover immediately from unplanned issues.

 

• Gain operational flexibility. Respond to market changes with dynamic resource management, faster server provisioning, and improved application deployment.

The disadvantages of virtualization include the following:

• Virtualization adds overhead to the CPU, memory, IO, and network.

• Virtualization adds an additional layer to the hardware and software stack. Therefore, additional complexity is introduced in the following circumstances:

  • When sizing the physical server.
  • When planning VM capacity.
  • When planning multiple VMs on the same physical server.
  • When investigating performance issues.

 

You can set up interest invoicing in Accounts Receivable and in the General Ledger.

To set up interest invoicing, use these sessions:

Invoice-to Business Partner (tccom4112s000)
For invoice-to business partners for which you want to raise interest invoices, select the Charge Interest checkbox.

Mapping Scheme (tfgld4573m000)
Use this session to define the mapping of the Interest Invoice / Revenues Analysis integration document type.

Interest Percentages (tfacr5102m000)
Use this session to define the interest percentages for each financial business-partner group, and for different periods of days.

Interest Invoice Related Data (tfacr5101s000)
Use this session to define whether interest must be calculated on unpaid invoices, partly paid invoices, interest invoices, and/or fully paid invoices. You can also indicate that LN must take advance payments, unallocated payments, and credit notes into account for the generation of interest invoices.

Optionally, set conditions
Example: LN only generates an interest invoice advice entry if these conditions are met: The total of all advice entries in one currency is higher than the allowed minimum amount of an interest invoice defined in the Minimum Amount for Interest Invoice field.

The invoice is overdue for a greater number of days than the number of days defined in the Minimum Days for Interest Invoice field.

First96979899101103104105Last

Theme picker

Categories