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
63518 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

If you setup the “From” and “To” Location fields in the Work Center file, this will determine the locations for material issue transactions and production reporting transactions.

The reporting of the transactions happen through production reporting, JIT600, or using the Shop Floor labor posting, SFC600, or Shop Floor Posting from SFC650.

Remember, any location used in the work center file must first be set up in the location master file. Using an MES solution by-passes the need to key any of the data to Infor LX.

Ok… so you want to know the status of a specific shop order that was released two days ago.

What do you do?

It’s a sure bet that you have a manager, supervisor, or planner who can walk the floor and find the order at whatever work center it happens to be at. He/she can then answer “what operations have been completed and how many were completed?” All this requires leg work, and of course, a fair amount of time.

Now, if you have set up your BPCS master files properly, and you report transaction activity, you should be able to get those shop order statuses much faster using the SFC300 Shop Order Inquiry Screen.

At your fingertips you can see:

  • Release date & due date
  • How many hours remain in total and at each operation
  • The quantity required, what was finished, and the remaining quantity
  • What components (materials) have been issued

Pretty basic information, right? Are you getting what you need to know? If not, then you may want to reexamine how your BPCS files are set up and what transactions along with their frequency are captured.

FirstLast

Tips: LN | Baan

Categories