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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

In Baan IV, users define series and numbers in the Maintain First Free Numbers (tcmcs0147m000) session. In the Type of Number field, users must select the type of documents for which the series will be used. The generated document numbers are always numeric and can consist of up to six characters.

 

In LN, users must define number groups in the Number Groups (tcmcs0151m000) session and then in the First Free Numbers (tcmcs0150m000) session, define the series and numbers of each number group. Users assign the number groups to various purposes in the corresponding sessions. For example, in the Sales Order Parameters (tdsls0100s400) session, users can select the number group for sales orders and sales schedules. In the Sales Offices (tdsls0512m000) session, users can then select a series of that number group for the sales orders generated by a specific sales office. As the series codes can be alphanumeric, the generated document numbers can be alphanumeric and they can consist of up to nine characters.

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.
First141142143144146148149150Last

Theme picker

Categories