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: Archive Net Price for Deleted Lines

Infor LX now stores the Net Price for a deleted line, so that the information is available for later analysis.

If an order line is canceled, LX stores the current Net Price in a new Net Price Archive field. The Net Price Archive field is updated whether the line is deleted through Line Entry (ORD700D2) or Fast Line Entry (ORD700DA), or the entire transaction is deleted through Order, Quote or RMA Directory (ORD700D1).

The Net Price Archive field can be useful when analyzing the reasons for canceled order lines. Users can define Cancellation Reason Codes related to pricing. Review of the archived Net Price, along with other values from canceled order lines such as Order Quantity and Selling Unit of Measure, Cancellation Reason Code, Request Date, Price Book Date, Item Number and Customer Number, can lead to adjustments to pricing structures, promotion qualifiers or other actions that can avoid loss of revenue on future orders, or follow-up actions to recover the canceled line.


OPERATIONS: IDF RMA Inquiry

This enhancement provides a robust RMA Inquiry capability. The base RMA Inquiry application delivers role-based functionality to support customer service, sales, pricing and business analysis functions.

The IDF RMA Inquiry presentation enhances a number of customer service and data analysis functions.

  • RMA List provides filters that allow sorting and sequencing by any displayed data field, such as RMA number, customer number, Total RMA amount, request date, good thru date, Customer reason code, Disposition reason code, Q/C reason code.
  • RMA Line List provides filters that allow sorting and sequencing by any displayed data field, such as item number, request date, extended amount, net price, Customer reason code, Disposition reason code, Q/C reason code.
  • RMA detail cards provide additional details about the RMA, as well as about any orders that will result from the RMA.


IDF RMA Inquiry provides significant enhancement to several business roles:

Customer service personnel, customer service managers responsible for handling customer complaints and negotiating return conditions with the customer Warehouse personnel, warehouse manager at the return warehouse. Billing personnel, billing managers responsible for processing credits to the customer and handling questions related to the RMA, return and eventual credit.

Managers responsible for analysis of returns related to reasons for returns, resulting replacement orders, recommendations for improving pricing or internal processes to reduce returns.
 

TECHNOLOGY: User Provisioning

This enhancement: 

  • Provides an ability for LX to integrate with Infor Federation Services (IFS) to automate provisioning of users.
  • Activates LX exit points during maintenance of LX business roles and business units to publish the SyncSecurityRoleMaster BOD which can be received by IFS as LX-specific roles in addition to the three IFS predefined LX-specific roles: LX-SystemAdministrator (corresponding to LX security type S = LX Security Officer); LX-SystemManager (corresponding to LX security type M = LX Security Manager); and LX-User (corresponding to LX security type U = LX User).
  • Enables support for LX receiving an inbound SyncSecurityUserMaster BOD (sent from IFS) and creating or revising the associated LX user (or security manager or security officer). This enhancement also supports creating an IBMi user profile which can then be defined as an LX user (or security manager or security officer).
  • Activates LX exit points during maintenance of LX users (and security managers and security officers) to send the ProcessSecurityUserMaster BOD to IFS requesting creation or revision of a user on behalf of LX.
  • Automates sending revised LX user authorities to corresponding System i Manager (SiM) tasks which can then be uploaded to System i Workspace (SiW).
     
Previous Article Is your team still manually entering UPS and FedEx information into your Baan or Infor LN system?
Next Article Infor LX/BPCS Tips & Tricks for FINANCE: Archive Net Price for Deleted Lines
Print
128 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

Note: The Blocked Operations (tisfc0540m000) session displays the blocked operations.

Introduction

Sometimes a problem occurs that must be solved before an operation proceeds. Examples of such situations are:

  • The quality of an intermediate product must first be inspected.
  • A machine is in repair.
  • A supplier cannot deliver an essential component in time.
  • A customer is late with its payments.

In these situations the operation can get the operation status Blocked.

An operation can be blocked:

  • Manually.
  • Automatically by Quality.

Blocking reasons

Every blocked operation must have a blocking reason. The blocking reason of a blocked operation has two purposes:

  • To indicate why the operation is blocked.
  • To determine which actions you can no longer perform on the operation.

Types of blocking

The following actions can be blocked by means of a blocking reason:

  • Reporting a quantity completed.
  • Reporting a quantity rejected.
  • Reporting a quantity to be inspected.
  • Reporting an operation completed.

You normally carry out these actions in the Report Operations Completed (tisfc0130m000) session.

You can define blocking reasons in the Blocking Reasons (tisfc2100m000) session.

Manual blocking

Use the Report Operations Completed (tisfc0130m000) session to block an operation. When you block an operation, you must also enter a blocking reason. If Quality has already blocked the operation, you can only enter a blocking reason, which is more restrictive than the blocking reason of Quality.

Blocking by Quality Managem

Categories