Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Operations

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
Contact author

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.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

Tax reporting is part of the financial accounting and is restricted to one country. Therefore, the LN tax handling in a multi-company structure is similar to the tax handling in a single company environment.

Tax handling in LN includes the following:

· Tax registration

For tax registration, you define the various tax details for each country in the Taxation module. In the General Ledger module of Financials, you specify the ledger accounts for the tax amounts separately for each financial company. LN can post the tax amounts calculated for a tax code to different ledger accounts in the individual financial companies, for example, in a single logistic, multi-financial company structure.
Read more

The advantages of virtualization include the following:
 

• You get more out of your existing resources. Pool common infrastructure resources and break the legacy “one application to one server” model with server consolidation.

• You can reduce datacenter costs by reducing your physical infrastructure and improving your server to admin ratio. Fewer servers and related IT hardware means reduced real estate and reduced power and cooling requirements. With better management tools, you can improve your server to admin ratio so personnel requirements are reduced.

• You can increase the availability of hardware and applications for improved business continuity.

• Securely back up and migrate entire virtual environments with no service interruptions. Eliminate planned downtime and recover immediately from unplanned issues.

• Gain operational flexibility. Respond to market changes with dynamic resource management, faster server provisioning, and improved application deployment.

 

The disadvantages of virtualization include the following:

• Virtualization adds overhead to the CPU, memory, IO, and network.

• Virtualization adds an additional layer to the hardware and software stack. Therefore, additional complexity is introduced in the following circumstances:

Read more
First138139140141143145146147Last

Theme picker

Categories