"This Batch Is Not Accessible" is an error you can sometimes receive when attempting an import from Fidesic into GP.
If you encounter the "This Batch Is Not Accessible" error after import into GP, the most likely cause is that the MEM Fidesic Scripts were not properly installed, or were lost in an update.
To Correct, follow the Fidesic MEM Installation Instructions.
After correcting this issue, you will need to clean up any imported transactions in the GP database to make sure they are accessible from the front end in GP. In the script below, make sure to set
SELECT 'PM_Trxent',p.BACHNUMB,'00001',0,0,0,0,'',0
where "00001" is a valid MEM entity GL value for the company database.
--CLEAN UP BROKEN TRANSACTIONS
insert into B3900900
SELECT 'PM_Trxent',p.BACHNUMB,'00001',0,0,0,0,'',0
from PM10000 p
left join B3900900 b on b.BACHNUMB = p.BACHNUMB
where b.BACHNUMB is null
group by p.BACHNUMB
insert into B3920000
SELECT 1, p.VCHNUMWK,b.BSSI_Facility_ID,'','',1,VADDCDPR,0
from PM10000 p
join B3900900 b on b.BACHNUMB = p.BACHNUMB
LEFT JOIN B3920000 B2 ON b2.VCHNUMWK = p.VCHNUMWK
where b2.VCHNUMWK is null
insert into SY00500
select ss.GLPOSTDT, ss.BCHSOURC, b.BACHNUMB, ss.SERIES, ss.MKDTOPST, ss.NUMOFTRX, ss.RECPSTGS, ss.DELBACH,
ss.MSCBDINC, ss.BACHFREQ, ss.RCLPSTDT, ss.NOFPSTGS, ss.BCHCOMNT, ss.BRKDNALL, ss.CHKSPRTD, ss.RVRSBACH, ss.USERID, ss.CHEKBKID, ss.BCHTOTAL, ss.BCHEMSG1, ss.BCHEMSG2,
ss.BACHDATE, ss.BCHSTRG1, ss.BCHSTRG2, ss.POSTTOGL, ss.MODIFDT, ss.CREATDDT, ss.NOTEINDX, ss.CURNCYID, ss.BCHSTTUS, ss.CNTRLTRX, ss.CNTRLTOT, ss.PETRXCNT, ss.APPROVL,
ss.APPRVLDT, ss.APRVLUSERID, ss.ORIGIN, ss.ERRSTATE, ss.GLBCHVAL, ss.Computer_Check_Doc_Date, ss.Sort_Checks_By, ss.SEPRMTNC, ss.REPRNTED, ss.CHKFRMTS,
ss.TRXSORCE, ss.PmtMethod, ss.EFTFileFormat, ss.Workflow_Approval_Status, ss.Workflow_Priority, ss.Workflow_Status, ss.TIME1,
ss.ClearRecAmts, ss.PurchasingPrepaymentBch, ss.CARDNAME
from B3900900 b
left join SY00500 s on b.BACHNUMB = s.BACHNUMB
join SY00500 ss on ss.BACHNUMB = 'A00 '
where s.BACHNUMB is null