If your company already uses Avalara for tax compliance, you can integrate it directly with your Infor ERP system.

Crossroads RMC has developed integrations that connect Avalara’s automated tax calculation and compliance platform with Infor ERP environments, allowing tax calculations, reporting, and compliance processes to run seamlessly within your existing ERP workflows.

This integration helps eliminate manual tax processing, improve accuracy, and ensure tax compliance as your business grows.

If you’re already using Avalara and want to streamline tax automation within your ERP, Crossroads RMC can help you connect the two.

800.762.2077 | Contact Us

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.

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.

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.

FINANCE: Release Holds from IDF Order Inquiry Host Job

OPERATIONS: Order Entry Action Code / Function Key Security

TECHNOLOGY: Library BMRTOOLS contains the following commands
 

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).

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.

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.