Record Invalid error in PO Match.

SADIQUE

Member
Hi List

I am getting the 'Record Invalid' error when I do PO match, by putting G/L date 2018. If I change the G/L date to 2017, it works. Below is the error description.

Record Invalid
A form level error has occurred.
CAUSE: The record being processed either already exists for an 'ADD'
function or does not exist for an 'INQUIRY', 'CHANGE' or
'DELETE' function.
RESOLUTION: If you are attempting to inquire, change or delete a record you
previously added, there may be data base problems in your
production library. You should notify your data processing
department.

The error does not appear for some POs. I have been trying to solve it for the last two days, I have gone through all the possible ways I know, I have compared with the POs which does not have the error, but I could not find a solution. Please shed some lights.
 

ajit_nadgouda

Active Member
Hi List

I am getting the 'Record Invalid' error when I do PO match, by putting G/L date 2018. If I change the G/L date to 2017, it works. Below is the error description.



The error does not appear for some POs. I have been trying to solve it for the last two days, I have gone through all the possible ways I know, I have compared with the POs which does not have the error, but I could not find a solution. Please shed some lights.

It is possible that the OV number that is getting generated is already present in GL (F0911). Check next number (NN) setup for OV docs for year 2018 for that company. Also check the latest OV number recorded in GL. The NN set up should provide the next number that is not already used before.
 
Call Orchestrations From Excel – The Easy Way to Make the Orchestrator Work for You.
Top