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

George Moroses

Infor LX/BPCS Tips & Tricks for EXECUTIVES

FINANCE: Release Holds from IDF Order Inquiry Host Job

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.

OPERATIONS: Order Entry Action Code / Function Key Security

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.

TECHNOLOGY: Library BMRTOOLS contains the following commands

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.

Previous Article 2026 is HERE: Is your Baan/LN strategy ready for the "2030 Countdown"?
Next Article Infor LX/BPCS Tips & Tricks for FINANCE: Release Holds from IDF Order Inquiry Host Job
Print
41 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

You use LN audit features to fully or partially log changes that users make to the LN database tables when they use LN sessions.

The audit functionality is based on the concept of audit profiles. In an audit profile, you define which tables and fields are audited and when, in the context of an audit profile. To bundle profiles in the same functional area, you can relate the profiles to audit categories. You can export and import audit profiles with various options to enable a quick configuration. The audit trail is stored in sequence files, which are generated for each combination of company and table.

Note: For some important parameter tables it is required that auditing is enabled.

You can view or print the history of modifications.

Categories