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 1

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

First let’s look at some key BPCS Master File data starting with the routing file.

How many routing steps (operations) are set up that reflect how the product is produced in the factory? If you take a short cut and set up only one operation for the entire process, then you will limit the information seen on the SO inquiry program. Set up the operation steps to reflect what you want to report back to from the factory floor.

Will each of the routing steps run in one work center, or in different work centers? To keep it simple you may want to set up work centers as departments. For example:

  • Assembly
  • Machine
  • Paint
  • Etc.

For each operation setup consider how you have set up the following:

  • Load Codes – for example a code 5 is used if reporting both setup time and run labor time. These codes are maintained in the work center file
  • Basis Code – typical codes are P for pieces per hour,  3 is used for hours per 1,000 pieces
  • Setup hours – if you set them up, you also want to report them
  • Run hours – Direct Labor
  • Machine hours

How you set up these fields will have an impact on how you report transactions and what is seen on the SO inquiry screen.

Previous Article Baan/LN Tip of the Week: ERP Setup - Pros & Cons
Next Article Crossroads RMC Maintains Preferred Partner Status With Honeywell / Intermec for 2016
Print
35200 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

If you do not wish to define a detailed mapping to various ledger accounts for specific integration transactions, you can map the corresponding integration document type to a default account. All the transactions of the integration document type for which an account cannot be determined based on the mapping scheme details, are posted to the default account.

 

The mapping of an integration document type to a default account is direct, without the need for element groups and mapping elements. No distinction is made on any of the transaction details.

 

Default accounts can be used in two ways:

  • Instead of a detailed mapping to various ledger accounts. All the transactions are posted to the same account. For example, all warehouse receipts are posted to the Inventory ledger account, without any distinction.
  • In addition to a detailed mapping. If a transaction cannot be mapped based on the detailed mapping scheme, it is posted to the default account.

A cluster is a group of one or more warehouses in a particular geographical area. You can plan an item by cluster (geographical area).

To enable this, you can set up multiple plan items for one item. You always define one plan item without a cluster indication and multiple plan items with a cluster indication. A plan item with a cluster is called a clustered plan item, and a plan item without cluster is called the non-clustered plan item.

The plan items in the clusters can be supplied not only by distribution, but also through purchase and production. In this way, you can, for example, plan local purchasing in a cluster (geographical area). You can also plan supply from multiple sources.

 

Optimize Your Manufacturing Today!

First9899100101103105106107Last

Theme picker

Categories