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: SFC600

In addition to SFC650, this ERPLX program is also used to capture and post shop floor information.

The key difference between the two is that SFC600 only captures Labor (run time) reporting, machine time, downtime and indirect time.

If you use SFC600, then all shop order material receipts and issues would be captured using INV500.

Both Inventory and Shop Floor Transaction entry is keyboard dependent, unless you incorporate an automated method like an MES solution to capture the data.
Previous Article BPCS/LX Tip of the Week: Downtime Reasons
Next Article Baan/LN Tip of the Week: Aborted Finalization Run
Print
51316 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

You can integrate Accounts Payable (ACP) with Purchasing. ACP requires more detailed information in the Vendor file than Purchasing requires. Accounts Payable automatically checks for a valid purchase order when you

match invoices to POs and receipts. Enter any outstanding active purchase orders through PO Release, PUR500, before you can match invoices in Accounts Payable.

 

Accounts Payable can also update the Actual Cost fields in the Inventory Master file directly from vendor invoices. You must provide the following information in order for Accounts Payable to complete this update:

â–ª Define a type C inventory transaction.

â–ª Enter a valid purchase order on the Invoice Entry header screen, ACP500D2-01, or in the Next Purchase Order field on the Invoice Entry: PO Costing screen, ACP500D3-01.

â–ª Enter the information for the actual cost transaction on the appropriate lines.

First134135136137139141142143Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories