Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jabman
Starting Member
3 Posts |
 Posted - 2010-10-29 : 14:21:32
|
| I'm trying to correct an error that was somehow made during a payment posting session and it seems the only way to correct that is by making the correction through a SQL command. I'll try to explain the best I can in detail as to what specifically I'm trying to accomplish but please understand I do not know allot about SQL.During a payment posting session there was a payment posted and normally each payment has it's own batch id number, in this one case a payment posted but for two different customers using the same batch id number. I have tried to back the payment out using the program's "backout payment" option but I get an error message that says "Invalid Debt Id" for this customer. The two customers have different debt id numbers so I'm not sure how this could have happened, but I believe I can correct this if I know the correct SQL command. The field name is PMTB-ID and the table is PMT. Again, I'm not familiar enough with SQL to know what the exact command is, is there someone that can give me some assistance to help me correct an error that was somehow made during a payment posting session. |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-11-08 : 13:27:53
|
I would really say that you have to call the service guys which have developed / delivered the application because in an accounting program nobody knows anything about the side effects if you are going to change some values in the databases without knowing the internals of the software.And in general the given information isn't suitable to get a clue what you want to do in deatail.
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2010-11-08 : 13:46:20
|
| I agree with webfred. As we don't know the schema or the business rules of your application, it will be almost impossible for us to help unless we get a ton of detail. In general, what we would need is DDL (CREATE TABLE statements) for all tables involved, sample data to illustrate your issue, and what you expect the data to look like after the SQL command fixes the issue. As we don't have any of this information, we are unable to help.It may be unlikely that we can help even if given this information though. You really should start out with whoever developed this application as they should know what to do.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-11-08 : 14:14:09
|
As I said on your other post:quote:
Please remember we're all volunteers here. The more information that you give, the more likely it is that someone will help you. The more work that's necessary in figuring out a post, the more likely it is that people will just ignore it and go elsewhere.Try reading over what you posted and imagining that you know absolutely nothing about the background. Could you figure out what's been asked?
Also consider the legal implications of fiddling directly with the database behind a payment/accounting system. Mess up and you could be liable for huge amounts of money or worse.--Gail ShawSQL Server MVP |
|
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2010-11-11 : 15:20:07
|
| jabman, if you're just trying to get another opinion by posting duplicate threads then here's one:Absolutely under no circumstances should you make direct data changes to the table that underlie your accounting software. Find an expert in that software to tell you how to fix your situation. I would be surprised if you even have access to make direct changes to the tables.Be One with the OptimizerTG |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-11-11 : 15:58:00
|
| In addition, you still haven't posted anything even close to what we would need to help you, were this not an accounting system that probably shouldn't be tampered with. To even begin to help we would have needed at least the table structures (that you have not provided) an example of what the data looks like (which you have not provided) a description of what the data would look like after (which you have not provided). We're not mind readers, we can't see your screen.--Gail ShawSQL Server MVP |
|
|
|
fdtoo
Starting Member
28 Posts |
Posted - 2011-01-05 : 20:59:08
|
| Hi Jabman,does your system only allows 1 batch id for 1 customer? If yes, is your problem, is you have accidentally posted a payment to 2 different customer, thus leading to the error message of "Invalid Debt Id" while attempting to back out your payment? If your answer is Yes,my best advice, is not to meddle with the database, you would cause an unpredictable spiralling effect on your system. Ask your Accountant to reconcile the customer balance against gl balance, and filter out any discrepancy and highlight this to your software support vendor.Good Luck!accountingdes.com |
|
|
|
|
|
|
|
|
Posting error