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

This enhancement simplifies access to LX programs that are available through System i Manager (SiM), as well as Workflow for System I (WFi). This provides an easy way to promote common WFi business processes from one LX environment (for example, test or environment) to another LX environment (for example, production). 

LX also provides a set of four-character task codes that can be used within SiM, System i Workspace (SiW), and WFi, for default programs in LX. These predefined LX task codes begin with 0,1,2,3, or 4. Users can specify task codes for their custom programs that are flagged as valid menu options in LX, but these task codes cannot begin with 0,1,2,3, or 4. Users can specify the task codes in Infor LX Object Master Maintenance, SYS625D. This enhancement provides simplified access to LX programs that are flagged as valid menu options in System i Manager and Workflow for System i environments. In SYS625D, The user can also specify task codes in SYS625D for customized programs that are flagged as valid menu options.

Users are no longer limited to backing up or saving files to a tape or diskette.They can now use a Save File (SAVF) to save data and objects. LX programs that perform saves and/or backups were modernized to add a new SAVF option.  

There were numerous places in LX where users are prompted to save a file or library. These screens have options for tape or diskette. Diskette refers to the old 8” diskettes used on System/38. These devices are outdated and virtually obsolete. The current means of saving objects on the IBM i, is through the use of a Save File (SAVF). This compresses the data into a single object that can be saved and is easily transferred between systems.

These objects were modified and/or created for this enhancement:

  • Backup Simulation (FOR630C, FOR630D, FOR630FM, FOR640HT, and FOR630HT)
  • Month End Close (INV903D, INV903FM, INV901C, and INV903HT)
  • Purge YTH/Restore Archived Lots (INV912C, INV912D, INV912DHT, and INV912FM)
  • Purge and Save ITH records (INV932C, INV932D, INV932FM, and INV932HT)
  • Labor Ticket Save (SFC905D, SFC905FM, SFC901C, and SFC905HT)
  • Backup Infor LX Files (SYS700C, SYS700D, SYS700FM, and SYS700HT)
  • Backup Infor LX Programs (SYS710C, SYS710D, SYS710FM, and SYS710HT)
  • Backup Infor LX Source (SYS740C, SYS740D, SYS740FM, and SYS740HT)
  • Save File Name Selection (SYS912D, SYS912FM, and SYS912HT)


Benefit

Use the Backup Simulation to copy a simulation file to a SAVF or tape. Users may want to do this to transfer simulation data from one system to another, from site to site, or to save the data before permanently deleting it from the system.

First6970717274767778Last

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