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

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

The package includes numerous reports and sessions to view the variances in a way that Finance can identify problems based on the Finance Integration Transactions in the General Ledger.

There are a few main sessions with many detailed sessions linked to them. The reports can be run from the main Print Production Order Variance Reports or in the individual detailed session.

Sessions included in the report package:

1. Print Finalized Trans – Variance Reports.

a. Financial Trans. by L/Acct – Prod. Order Variances - Recap

b. Financial Trans. by L/Acct – Prod. Order Variances – Details

2. Update Production Order Variances (updates special variance table).

3. Production Order Variance Overview – Main view

a. Production Order Variance Details

b. Price Variance Details – Material Variances

c. Price Variance Details – Operation Variances

d. Efficiency Variance Details – Material Variances

e. Efficiency Variance Details – Operation Variances

f. Efficiency Variance Details – Reject Variances

g. ACO Variance Details – Reject Variances

h. Accept Production Order Variances

i. Un-accept Production Order Variances

j. Finally Accept Production Order Variances

4. Print Production Order Variance Reports:

a. Production Order Variance – Overview

b. Production Order Price Variance – Material Revaluation

c. Production Order Price Variance – Operation Revaluation

d. Production Order Efficiency Variance – Material

e. Production Order Efficiency Variance – Operation

f. Production Order Efficiency Variance – Rejects

g. Production Order ACO Variance – Rejects-Additional Costs

5. Delete Production Order Variances (used to redo a month)

Contact Kathy Barthelt to learn more.

Graphical representation makes complex concepts—like the intricacies of an ERP system—more universal, relatable and easy to understand.

ERP dashboards gather and visualize critical metrics from across the organization, offering insight into the performance, outlook and interconnectivity of business processes.

By setting up ERP dashboards that illustrate key metrics and compellingly communicate operational performance, key stakeholders will have a clear picture of the health of the business—and make better, more informed business decisions as a result.

The Crossroads Analytics Dashboard has preconfigured views for all of the following:

 Infor LN & Baan
  • Accounts Payable
  • Accounts Receivable
  • Journal
  • Booked Sales
  • Invoiced Sales
  • Production
  • Receipts
  • Purchase Orders
  • Inventory

To learn more visit our Analytic Dashboard webpage.

First5455565759616263Last

Theme picker

Categories