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
28408 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

If it is necessary to pause sending and receiving of BOD messages on your IBM i during your month end process, it is best practice for the document flows that point to the IBM i to guarantee delivery of BOD messages. Once the month end process has been completed, you will need to Resume the ‘Receiving’ and ‘Sending’ Active Connection Points so your documents will continue to process.

Pausing Sending messages

To pause sending messages to ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be paused for sending messages.
  3. In the Sending Paused column, click Pause. The page is automatically refreshed and the Sending Paused checkbox is selected. A Resume button becomes available. 

Sending of messages by this connection point is stopped....

The database in LX 8.4 has undergone a significant change from previous versions. The database has been created using SQL DDL language instead of the old DDS language. The newer format allows for LX to take better advantage of advances in IBM database technologies as they move forward. Additionally, LX will be better able to make changes to tables (aka files) in the future without causing very large MR explosions to replace all programs that use a specific table. To ease the impact of this significant change, the LX tables (aka physical files) have new names that are the same as the previous version file names but with a “P” at the end, for example IIM is now IIMP. The old file names now belong to SQL views that looks just like the tables. This change made it easier to upgrade all the LX programs without changing every reference to every file. Many of the logical files remain although some have been replaced by SQL indexes to improve performance.

First6465666769717273Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories