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
/ Categories: Infor LN & Baan Tips

Infor LN / Baan Tip of the Week: Deleting Records

To improve performance and reduce database growth, deleting records is highly effective. The disadvantage of deleting records is that data is no longer available. Usually, however, not all records need to be saved. For example, line activities are stored by warehouse. Normally, you do not need to keep these records. Therefore, after closing a warehouse order, line activities can be removed. The User's Guide for ERP LN Archiving describes several sessions you can use to delete old data. Other data such as items and business partners can be reviewed once in a while, after which you can delete the data you no longer need. For every order and contract table a session is available to archive and delete old orders. In these sessions, you can specify several characteristics to select the orders to be removed, such as date or status. Run these sessions on a regular basis.
Previous Article Explore your IDF programs
Next Article Infor LX / BPCS Tip of the Week: Optional Authority to Maintain Reason Codes
Print
46515 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

This enhancement provides the ability to copy order lines, quote lines, and RMA lines. During Order Entry, action 3=Copy is available to copy regular lines and special lines. The new line displays in the next available line number.  This enhancement reduces manual key entry and speeds up Order Entry. 

The programs or areas impacted include ORD700D2, Order Line Entry, Quote Line Entry, and RMA Line Entry.

This enhancement prevents over-allocations and resulting overshipments to customers. Attempted over-shipments can present an error message to the user, or there is an option to automatically adjust the user’s request to the allowed quantity.

Since over-shipments result from over-allocations, Infor LX provides an optional validation during the four processes where a user can attempt to over-allocate. Note: Infor LX never over-allocates or over-ships; this always results from a user’s action. This enhancement provides three options regarding over-allocations and over-shipments:

  • Continue current process with warning message.
  • Show error message.
  • Automatically change allocation quantity to match quantity available for shipment.

If the over-ship quantity change is acceptable, internal procedures may require that the order quantity be revised so that pricing, promotions, credit checking, load planning, and other processes reflect the actual quantity.

The programs or areas impacted include:

  • ORD820D, Order Entry System Parameters
  • ORD720D2, Order Allocations
  • ORD725D, Order Entry Allocations
  • ORD570D5, Pick Confirm Inventory Confirmation
  • ORD700D2 / ORD700DA / ORD710B, Order Line Validation
First5556575860626364Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories