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

Kathy Barthelt

Infor LN & Baan Tip & Tricks for OPERATIONS: Best Practices for Purchase Order Archiving / Deleting

 Here are some best practices to follow if you are considering archiving or deleting purchase order data:

  • If Financials is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.
  • Purchase contracts must be archived before purchase orders can be archived.

You cannot delete a purchase order (line) if:

  • The linked warehouse order is closed but cannot be removed.
  • The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
  • A consignment replenishment order is not yet consumed completely.
  • The invoice is yet to be completely matched and approved.
  • The invoice amount is not yet inserted as turnover history.
  • The sales order or service order that's linked to the purchase order line, and for which an internal invoice must be sent from the purchas office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.

Previous Article Infor LN & Baan Tip & Tricks for TECHNOLOGY: Using Table Boosters to Speed Up Sessions & Processes
Next Article Infor LN / Baan Tips & Tricks for EXECUTIVES
Print
6357 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

For years, repetitive manufacturing industries have been applying many of the principles in Just-in-Time philosophy. They have established balanced production lines that depend on a steady flow of material to each work station. They schedule production in daily or weekly rates rather than in discrete shop order lots. They track finished inventory by work center rather than by job. They typically backflush stock balances (decrement stock balances upon completion of specific manufacturing steps rather than issued at the beginning of each production run).

 

Costing is typically based upon a daily rate or hourly rate rather than being associated with specific shop orders. 

 

Repetitive manufacturers use MRP II software adaptable to their environments

in the following key areas:


â–Ş Product definition

â–Ş Inventory tracking

â–Ş MRP/Master Scheduling

â–Ş Shop Floor Control

â–Ş Purchasing

â–Ş Costing

Just-in-Time (JIT) is a management philosophy that focuses on minimizing the resources necessary to add value to your products and to operate your factory in ways that eliminate waste. Resources are labor, materials, equipment, space, and time. Waste is anything that does not add value to your products. Moving work-in-process from place to place, stacking and sorting, investing capital in large work-in-process and raw material inventories, inspecting materials at your vendors' sites, and tying up warehouse space with finished goods are all activities that add cost, not value, to your products. 

JIT is a process that reduces lead time. JIT does not replace an MRP, an inventory program, a scheduling technique to bypass your Master Schedule, or a materials management project. JIT is the never-ending commitment of everyone, from top management to your workers on the floor, to maximize your effectiveness through continuous, incremental improvements.

First130131132133135137138139Last

Theme picker

Tips: LN | Baan

Table Timestamp Definitions (ttadv4136m000)

Use this session to define timestamps for Infor LN tables. A timestamp is an additional column that stores the date and time of the last change for each record.

Timestamps are utilized by features like the extraction logic of CPM Enterprise Analytics. They enable CPM to perform incremental data extractions. For example, CPM can use the timestamps to extract records that were changed during the last week in a weekly extraction process.

To Create Timestamps...

Operations: To absorb the cost of cost items into specific projects, you'll need to handle them as customized items. However, cost items cannot directly be defined as customized items. Customized items must be physical, either manufactured or purchased.

That said, it's still possible to absorb cost items into a project, although indirectly. Here's how:

  1. Set Up Ledger Account: First, create a new ledger account in session tfgld0508m000 and set the type to "PCS" (project) in the operations management integrations. This account will be used for matching and approving purchase orders for cost items.

  2. Create and Activate Projects: Ensure that the necessary projects are created and set to active status.

  3. Purchasing Cost Items...

12345678910Last

Theme picker

Categories