Subhash Bhaskaran
Member
Hello Friends,
We are having this problem with Integrity Report R007021 when it comes to checking integrities between tables F0011 and F0911 for ‘N’ type batches. To apprise you of the details – we initially ran this report to find it absolutely clean. The, some item cost revisions were made vide P4105 pursuant to which the doc (type IB) batch type ‘N’ was created. The said batch was posted and we ran R007021 again to find no inconsistencies in it. Then, the entries were voided and before posting the same, we tried out once again the integrity report only to find the batch in question appearing this time with the error ‘Batch Header (F0011) Un-posted/ Details (F0911) posted’. We checked up in the relevant tables to find that the proper entries had been generated and both the tables were showing entries with un-posted status owing to the voiding thing. However, once we post the voided batch, the error disappears from the report. We are using One World Xe Release B7333 and the testing was made in the QA environment. We tried to replicate the same in Demo version but did not find any errors. Can anyone please provide a solution…
Thanking you in anticipation,
Subhash Bhaskaran
We are having this problem with Integrity Report R007021 when it comes to checking integrities between tables F0011 and F0911 for ‘N’ type batches. To apprise you of the details – we initially ran this report to find it absolutely clean. The, some item cost revisions were made vide P4105 pursuant to which the doc (type IB) batch type ‘N’ was created. The said batch was posted and we ran R007021 again to find no inconsistencies in it. Then, the entries were voided and before posting the same, we tried out once again the integrity report only to find the batch in question appearing this time with the error ‘Batch Header (F0011) Un-posted/ Details (F0911) posted’. We checked up in the relevant tables to find that the proper entries had been generated and both the tables were showing entries with un-posted status owing to the voiding thing. However, once we post the voided batch, the error disappears from the report. We are using One World Xe Release B7333 and the testing was made in the QA environment. We tried to replicate the same in Demo version but did not find any errors. Can anyone please provide a solution…
Thanking you in anticipation,
Subhash Bhaskaran
