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 Tips & Tricks for EXECUTIVES:

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:

  • Select the Quantity-dependent Routing check box in the Item - Production (tiipd0101m000) session.

  • Enter the routing codes in the Item - Routings (tirou1101m000) session. Enter the maximum quantity for which a routing is valid in the Up to Quantity field.

Note: If multisite functionality is activated, the routings available may vary per site on the job shop bill of material selected. Differences in routings have an impact on the standard cost calculation.

Default routing

If the Quantity-dependent Routing check box is not selected, the default routing applies to an item. However, this default routing must also be linked to the item. To find out, LN checks the default routing code in the Default Routing field of the Job Shop Master Data Parameters (tirou0100m000) session. Next, LN checks whether the default routing code is linked to the item in the Item - Routings (tirou1101m000) session. If so, the default routing applies to the item. If the default routing is not linked to the item, no routing is used.


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.

  • The destination financial company.

  • The transaction type and series.

  • The ledger account and dimensions.

  • The transaction currency.

  • The fiscal year and the financial period, the tax period, and the reporting period.

  • The integration document type and the Debit/Credit indicator.

  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

 
TECHNOLOGY: Infor LN Rest API

Frequently Asked Questions (KB2316174)

For Infor LN a framework has been developed to support REST API-based services for lean integrations. This framework is now made available for the LN application. This KB answers some common questions you may have and procedures that are needed for using the LN Rest APIs.

More details on these topics can be found in the Infor LN REST API Administration Guide.

Previous Article Infor News You Can Use: Discover the Power of Advanced Planning & Scheduling with industry expert Greg Keating
Next Article Infor News You Can Use | Why Upgrade to Infor LX in the Cloud
Print
6734 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 simplifies access to LX programs that are available through System i Manager (SiM), as well as Workflow for System I (WFi). This provides an easy way to promote common WFi business processes from one LX environment (for example, test or environment) to another LX environment (for example, production). 

LX also provides a set of four-character task codes that can be used within SiM, System i Workspace (SiW), and WFi, for default programs in LX. These predefined LX task codes begin with 0,1,2,3, or 4. Users can specify task codes for their custom programs that are flagged as valid menu options in LX, but these task codes cannot begin with 0,1,2,3, or 4. Users can specify the task codes in Infor LX Object Master Maintenance, SYS625D. This enhancement provides simplified access to LX programs that are flagged as valid menu options in System i Manager and Workflow for System i environments. In SYS625D, The user can also specify task codes in SYS625D for customized programs that are flagged as valid menu options.

Users are no longer limited to backing up or saving files to a tape or diskette.They can now use a Save File (SAVF) to save data and objects. LX programs that perform saves and/or backups were modernized to add a new SAVF option.  

There were numerous places in LX where users are prompted to save a file or library. These screens have options for tape or diskette. Diskette refers to the old 8” diskettes used on System/38. These devices are outdated and virtually obsolete. The current means of saving objects on the IBM i, is through the use of a Save File (SAVF). This compresses the data into a single object that can be saved and is easily transferred between systems.

These objects were modified and/or created for this enhancement:

  • Backup Simulation (FOR630C, FOR630D, FOR630FM, FOR640HT, and FOR630HT)
  • Month End Close (INV903D, INV903FM, INV901C, and INV903HT)
  • Purge YTH/Restore Archived Lots (INV912C, INV912D, INV912DHT, and INV912FM)
  • Purge and Save ITH records (INV932C, INV932D, INV932FM, and INV932HT)
  • Labor Ticket Save (SFC905D, SFC905FM, SFC901C, and SFC905HT)
  • Backup Infor LX Files (SYS700C, SYS700D, SYS700FM, and SYS700HT)
  • Backup Infor LX Programs (SYS710C, SYS710D, SYS710FM, and SYS710HT)
  • Backup Infor LX Source (SYS740C, SYS740D, SYS740FM, and SYS740HT)
  • Save File Name Selection (SYS912D, SYS912FM, and SYS912HT)


Benefit

Use the Backup Simulation to copy a simulation file to a SAVF or tape. Users may want to do this to transfer simulation data from one system to another, from site to site, or to save the data before permanently deleting it from the system.

First6970717274767778Last

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:

1345678910Last

Theme picker

Categories