Infor ERP Tips and Infor ERP News for Infor LX, BPCS, Infor ERP LX, Infor LN, Infor ERP LN, Baan, Infor M3, and Movex

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

Infor ERP LX / BPCS Expert Help Desk Service

George Moroses 0 400 Article rating: 5.0

Crossroads RMC has fine-tuned our Technical Help Desk Service to meet specific job requirements. Our service delivers product-level support and development assistance with significant cost savings compared to traditional models. Our Help Desk is a tailored service that provides a dedicated ERP LX/BPCS technical resource, ensuring our support precisely aligns with your needs for a more efficient and effective solution. 

Key Features:

  • Flexible Hours: Tailored to fit your budget and requirements.
  • Duration Options: Choose from 3, 6, 9, or 12-month agreements.
  • Remote Accessibility: Primarily remote support with on-site options for comprehensive assistance.
  • Expertise Spectrum: Includes RPG proficiency, robust documentation, design skills, IBM i system knowledge, job scheduling, SQL expertise, CL development, and more.
  • Scope: Focuses on technical support and development, with application support available upon request.
     

What's NEXT together.
Schedule a brief consultation with Crossroads RMC to discuss your technical support and development needs. We’ll help define the right scope, duration, and expertise to align with your goals and budget.

Let’s design a Help Desk solution that fits your business.
Contact Crossroads RMC at 800.762.2077 to get started.

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Library BMRTOOLS contains the following commands

George Moroses 0 789 Article rating: 5.0

INSTALLBMR

  • Installs BMR Explosions from *SAVF or *LIB
  • Installs objects after backing up replaced objects
  • Installs source after backing up replaced source
  • Installs Webtop Metadata
  • Installs /InforBMR subdirectories
  • Writes all activity to log file and spooled file report
  • Optionally runs DBUPDATE command

DBUPDATE

  • Installs new or updates existing database tables, views, indexes, triggers, procedures, logical files.
  • Installs source for above objects
  • Sets authorities to replaced objects based on previous object settings
  • Sets journalling on replaced objects based on previous object settings
  • Installs Priming Data
  • Installs SSAOVR updates
  • Installs message file updates for core message files
  • Installs message file updates for NLV message files if included in explosion

This enhancement reduces the time required to install BMR Explosions. There still may be manual steps required after the processing completes, but the overall time required is dramatically reduced.

Infor LX/BPCS Tips & Tricks for OPERATIONS: Order Entry Action Code / Function Key Security

George Moroses 0 813 Article rating: 5.0

Access to Order Entry/Maintenance has traditionally been controlled by using LX Program Security to grant or remove authority to ORD700. LX Company Security and LX Warehouse Security further control which transactions a user is allowed to create or maintain. A separate 8.4.2 enhancement allows security managers to control which types of transactions a user is allowed to create or maintain, through LX Order Type Security and LX Order Class Security. Building on these LX transaction security features, the Order Entry Action Code/Function Key Security enhancement allows security managers to further control what actions a user can take regarding an authorized transaction.

Security managers can now control the actions each user is allowed to be restricted from in the Order Entry job stream. The benefit is easily illustrated by some examples:

  • Regular users can be allowed to create and revise customer orders but are restricted from deleting an order.
  • Salespersons can be authorized to full authority with quotes and can be allowed to create customer orders but not to revise or delete them.
  • Or, salespersons could be restricted from 1=Create in Order Directory, with the result that they could only create an order by copying a quote, if they are authorized to 3=Copy in Quote Directory.
  • Only selected customer service users can be allowed to create RMAs, by controlling 1=Create in RMA Directory. A different group of customer service users who handle the actual returns can be authorized to create the return orders or credit memos from those RMAs, by controlling 3=Copy in RMA Directory.

Infor LX/BPCS Tips & Tricks for FINANCE: Release Holds from IDF Order Inquiry Host Job

George Moroses 0 428 Article rating: 5.0

This enhancement provides the ability for IDF Order Inquiry to release order holds via a host job.

LX IDF Order Inquiry displays numerous details about an order, order lines, special lines and related files. An Order Inquiry user can copy, modify or delete an order through WebTop calls to ORD700 Order Maintenance, if authorized. Among the many details Order Inquiry also lists the Hold Codes for customer hold, credit hold, user hold, margin hold, and credit card hold. This enhancement provides the capability to release holds through a host job function that executes ORD680B, Order Hold Mass Release.   Batch Hold Release host job has been added to IDF Order Inquiry. The Order Inquiry user must be authorized to ORD680 in LX program security, SYS600.

ORD680 has been modified to accept parameters for multiple executions by host job. The user can release holds for a single order, a range of orders, or for multiple individually selected orders.

The following hold releases can be requested:

  • Credit hold – orders on credit hold by the system (01) or by a user (02) are released from credit hold.
  • Customer hold – orders on customer hold are released.
  • User hold – orders on user hold are released.
  • Margin hold – ORD680 re-evaluates orders or order lines that are on margin hold.
245678910Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for TECHNOLOGY & FINANCE: Archiving Finalized Transactions

TECHNOLOGY & FINANCE: Archiving Finalized Transactions

To support correct archiving in a multicompany structure, the following rules apply:

  • Each company must have its own archive company. Companies cannot share an archive company.
  • The structure of archive companies must be an exact copy of the live environment.
  • A company must keep the same archive company until the end of its lifetime. Once data has been archived, you cannot change the archive company.

If extra archiving capacity is required, it is recommended that you set up a second archiving environment, which must also be an exact copy of the live environment. Define the companies of the second archive environment as the archive companies of the companies of the first archive environment. If necessary, a third and more archiving environments can be set up. You must then archive the data from each archive company to its archive company in the second archiving environment, and so on.

When you archive the data, LN builds an array with all the companies of the group and the archive company linked to each company. If any of the companies in the group does not have an archive company, LN reports an error and aborts the archiving process.

Batches and batch lines are only archived and/or deleted if you perform archiving and deletion in the company in which they exist. This is always the source company. Any intercompany documents and related finalized transactions that belong to the batch are not archived and/or deleted until the target company is archived.

If the batch has been deleted from the live environment, such intercompany documents and transactions will then temporarily exist without a batch in the live environment until the target company’s transactions are archived. Therefore, it is recommended to archive all the companies of a group within a short time.

Finalization runs are also archived. A finalization run can only be deleted from the live environment if all the attached batches have also been deleted.

Financial documents are archived and/or deleted if you perform archiving and deletion in the company in which they exist. For each document, LN searches whether a related intercompany document exists.

If the document’s transaction type indicates that the document numbering does not have to be in a fixed sequence, the document is not deleted from the live environment, to avoid duplicate document numbers.

A finalized transaction is not deleted from the live environment if the fiscal year of the transaction does not equal the fiscal year of the batch and the fiscal year of the transaction cannot yet be archived. If the Archive option is selected, the related batch, batch line, and document are copied to the archive company and retained in the live environment.

If a transaction is still referenced by open sales orders or purchase orders, it is marked as Deleted but not actually deleted. The related batch, batch line, and document are copied to the archive company and retained in the live environment. They are deleted when the referenced open transactions are closed and archived, for example, when you run the Archive/Delete Fully Paid Purchase Invoices (tfacp2250m000) session

If the transaction’s ledger account is a matchable account, any related matching data is also archived.

During the archiving process, the originating company of the finalized transaction is replaced with the originating company’s archive company. In this way, the archive environment will not contain references to the live environment.

During archiving, intercompany document relations are also copied to the archive environment. In the archive environment, these relations are updated in such a way, that each document in the relation refers to the environment in which the document actually exists. In the live environment, the document relation is retained until all related finalized transactions are deleted. For invoice-related transactions, this only occurs during the removal of fully-paid invoices. The document relation is also updated in the live environment, in order to refer to the archived document if all related finalized transactions have been removed from the live environment.

After the normal archiving process, an additional archiving step is performed in which all transactions and documents in the live company that arise from intercompany postings, are archived. During this step, intercompany relations are archived and/or deleted as described earlier.

Batches, batch lines, and documents that have the Deleted status are deleted from the live environment, unless the document’s transaction type indicates that the document numbering does not have to be in a fixed sequence. Such documents are not deleted from the live environment, to avoid duplicate document numbers.

Previous Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Next Article Infor LN & Baan Tips & Tricks for OPERATIONS: Simulated Purchase Prices (ticpr1170m000)
Print
1404 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories