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

Infor LN & Baan Tip: Remove Posted Payment/Direct Debit Batches

The functionality of session Remove Posted payment batches tfcmg1259m000 and Remove posted Direct Debit batches tfcmg4259m000 is explained below:

1.These 2 sessions can be used to removed already posted payment/direct debit batches that have been processed through CMG Module. After the batches are changed to removed status they can be deleted also.

2. Only a superuser, defined in the Payment Authorizations (tfcmg1100m000) can delete the payment/direct debit batch.

3. A payment/direct debit batch once removed cannot be retrieved. The data gets removed only from payment advice tfcmg1609m000/direct debit batch tfcmg4609m000 and composed payments/direct debits.

4. The details of the invoices that were selected in the removed payment/direct debit batch can be seen in session anticipated payment/receipt tfcmg2504m000 and from here you go into the anticipated document details to see the list of invoices selected.

5. Remove payment batches does not impact the check master and the check details remain in the check master. 

6. The anticipated receipt/payment document can be reconciled as usual following the receipt/payment reconciliation process.

7. The anticipated payment/receipt document details are not removed from GLD and ACR sessions or tables and can be seen in document history and ACP/ACR open entries.

8. The direct debit batch number can be retrieved from session tfacr6500m000(receipt related document). And the payment advice batch number can be retrieved from payment-related document tfacp6500m000 or the check master if the payment has been done through checks.

Previous Article Understanding Taxability Rules Is Key To Sales Tax Compliance
Next Article Infor LX & BPCS Manufacturing Tip: Production Register Listing
Print
28069 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.

12345678910Last

Theme picker

Tips: LN | Baan

Two big sources of inefficiencies in manufacturing are paper and spreadsheets. I know that you love ‘em, but they are the cause of more problems than you probably realize. Think of how long it takes you to get paper based data into the hands of those who can do something valuable with the data.
  • Is the information captured correctly?
  • Can everyone access the information?
  • Is this an accurate representation of what’s going on across all operations?

Make your shop floor paperless and put systems in place that talk to one another and automatically pull and push data to and from your ERP so that you can look in one place for all the information you need to run your business effectively.

If you’re not doing this today, you might as well be burning money.
 
Optimize Your Manufacturing Today!

Administrators are able to restrict access in Baan in several ways – including Companies, Packages, Modules, Sessions, and Tables – using the Authorization capabilities of the system.

In Baan IV, access can be given or denied on a user by user basis.

In Baan V and LN, the Authorization Management System can provide or deny access based upon roles to which users are assigned.

First9495969799101102103Last

Theme picker

Categories