RE: unapplied/suspended payment applications
Leah,
If you are opening the payment application screen and using the PV list to look for that batch and it is not there then I suspect the batch was created but not released and then it was deleted. The deletion should have removed the application information from the original payment document but it appears it did not which suggests some of issue was encounter during the deletion of that payment application batch or someone with initialize mode rights went to the GL journal transaction screen, switched the module to AR and then deleted the batch on the GL side (which will remove it from GL but would not clear the fields in question.
So, now we have a situation where we need to clear those fields in the original payment documents and the only way to do that is with a SQL update statement. Once cleared, you would then be able to apply those payment documents. However, before doing that, we would want to make sure that no other pieces of that batch still exist in the system because those would also need to be cleared up.
So, there are going to be some SQL queries that need to be run by someone at your end that has rights to the SQL Management Tool. Do you have such a person?
Here are the queries that need to be run:
select * from artran where batnbr = '006530" we want this to come up with no records
select * from aradjust where adjbatnbr = '006530' we want this to come up with no records
select from batch where module = 'AR" and batnbr = '006530' we want this to come up with no records
if all 3 of the above come up empty then you can execute:
begin transaction
update ardoc set applamt = 0, applbatnbr = '' where applbatnbr = '006530'
note the number of records affected. it should be 2 based on what you have said here. If it is 2, execute the following:
commit transaction
if it is some other number, execute the following to rollback the change and we need to discuss:
rollback transaction