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
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip of the Week: Warehouse Blocking – LN 10.7

The functionality to block a warehouse for inbound or outbound transactions has been enhanced. A check for blocks is performed not only during receipt and shipment confirmation, but at multiple stages in the process. In addition, you can specify these blocking options for the inbound and outbound processes:

• No

• Yes

• Interactive

For example, if Blocked for Inbound is set to Yes, no inbound actions are allowed in the warehouse. Consequently, users cannot confirm receipts, generate and put away inbound advice or storage lists, and perform inbound inspections. 

If Interactive is set, during a non-automatic warehouse inbound procedure, warnings are displayed which offer the user a choice to either cancel the action or continue. Batch or automatic inbound processes continue, but the corresponding reports and logs make note of the blocking. However, in all scenarios, receipt confirmation is not allowed.

The same rules are applicable for the warehouse outbound procedure steps. The restriction for receipt confirmation also applies to shipment confirmation.

For warehouse transfer orders, not only the ship-from warehouse is checked for outbound process blocks, but also the ship-to warehouse. This prevents situations in which goods get stuck in transit due to inbound procedure blocks that apply to the destination warehouse. Now, the transfer process is already blocked during outbound.

Previous Article Partner News: Are you up to date on all of the sales tax changes that have gone into effect this year?
Next Article Consulting News: Are you familiar with your Infor LN / Baan System Log?
Print
38652 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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

1345678910Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

1345678910Last

Theme picker

Categories