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

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

Pros/Cons of Multi Finance / Single Logistic Company Set-Up


Pros
Each legal entity can have its own general ledger and balance sheet.
Income statements can be generated for the different enterprise units included in the logistics company.
Centralized operations – purchasing, sales, manufacturing, planning, warehousing, etc.
Logistics data visible to all logistics users – a pro if this is what is desired.
One BOM, Routing, and Cost for each item.

 

You may have started your setup of your ERP system one way, and have discovered over time that maybe it no longer fits how you need to do business. Here are some pros/cons to consider for a Single Finance / Multi-Logistic setup. 

 Pros
All accounting functions are centralized into one company.  One balance sheet is generated – even though multiple logistics sites are involved.  Income statements can be generated by logistic company via use of a Dimension to represent the logistic company.

Allows logistical functions to be decentralized within one legal entity – if this is what is desired.

Logistics data not visible across companies – pro if you do not want users to see other company’s data.

 

Cons

First125126127128130132133134Last

Theme picker

Categories