Dynamics Community Forum Thread Details

GP v10 RM20101 and RM20201 tables

We use web-services to pass invoices and associated credit card payments into the sop module at time of sale. Are there scenarios that result in a record existing in the rm20201 table without a corresponding record in the rm20101 table and if so, is it a temporary status, i.e., it is resolved by posting, etc?

Not really. Those are the open (posted) AR tables which get updated by the posting process and no records are temporary.

When you integrate into SOP as you describe you are creating records in the SOP10100/10200 tables (and others) for the invoice and the SOP10103 table for the payment information. All the web service code does is enter the transaction into GP as if you had done it yourself manually. You then post the transaction with the standard logic and it works or it doesn't but it would be extremely unlikely that integration is the source of your apply issues (I'd give it zero percent).

That said, I see an occasional issue where a phantom record in RM20201 crops up. On occasion if a payment is voided in GP, totals on the records in RM20101 are updated, but the record in RM20201 is not deleted. Also, if a user un-applies a payment from invoice and applies it to another it seems that occasionally the apply table will not delete the first record. I'd say I see this a couple times a year on average and we do a bazillion transactions.

We find these when the summary trail balance numbers do not match the historical detail trail balance numbers for a selected date. It's a pain to deal with. I'm thinking your issue is probably similar in that the apply table has bogus records or the open table's current trx amount does not match the total of the apply records and is more linked to how GP allows non transaction state updates to these tables rather than anything you're doing in your integration.

Best

Tim

Quick Links