Nov 16 2018


Published by under Uncategorized

NC students are showing withdrawn from university in certain terms in time status.  Investigating this showed the message was coming from a combimation of shrlgpa and shrtmst.  NC courses give 0 hours earned and 0 hours attempted

No responses yet

Apr 24 2017

Indirect cost encumbrance

Published by under Uncategorized

Temp table that posting uses is fgtidce

No responses yet

Nov 06 2015

Tracking down reason why no approval queue

Published by under Uncategorized

You need rule class to get the rule group on the record. FTVRGRC is xwalk table.

You need document type number on record which you can get from forappl.lis

Look in table FORAQRC which has doc type and rule group

No responses yet

Jan 22 2015

Payroll encumbrance feed

Published by under Uncategorized

Got a call from SOU wanting to know why an encumbrance jv was stuck at Incomplete and wouldn’t post.  The was no seqno marked as an error in FGAJVCD so I had them complete it and then ran approvals.  No issues there so I ran posting. The posting list file gave the following error:

Document V0007872 , item 0 , sequence 872 – WARNING : Budget is exceeded
Document V0007872 , item 0 , sequence 873 attempted to post to an Encumbrance with a non-matching accounting Distribution.
Document V0007872 , item 0 , sequence 873 attempted to post to an Encumbrance with a non-matching accounting Distribution.
Error occurred on document, posting rolled back and document reset.


We tried to just delete that seqno but then just got another error.  Investigating we noticed it was an adjustment rule code but there was no initial rule code entry for that fopal, encd_item, encd_num combo.  We looked in the payroll feed table nhrdist and found the missing initial entry tied to a jv that existed in payroll but not in finance.  No reason why as far as we could determine.  We ran a script to post the missing jv to finance thinking the other would feed after the missing jv posted.  Instead we ran into the same error.  Investigating I compared nhrdist and fpbjvcd for that encumbrance number and looked for any jvs on nhrdist missing from fgbjvcd.  I found 6.


At this point we decided to clear payroll encumbrances for the year and re-do them.  We had a script to clear them on the payroll side but still had to clear them out of finance.  It turns out that the process is well documented by the HRIS Fiscal Year-End Processing document that OUS sends to the Payroll people before year-end.  Section A liquidates the encumbrances and Section B verifies that they have been removed.  Short version:

Section A: Run PWPEREM (in Update mode) with PR15 as the Encumbrance prefix.  Then run FWRLQPE. Then FGRTRNI, Then FGRTRNR.  Fix errors.  Post the file.

Section B: Run FWRPDIF.  Results should be zero.  Directions say to run either FGIENCB, query on PR15, or run FWRINZE, results should be zero.


We re-ran the encumbrance process and ended up with the same posting error but this time we were down to 3 different record pairs causing an issue.  They had the same foap, encd_num, encd_item, and encd_seqno but different account codes with the record above them.  Posting coulldn’t handle this.  The encd_seqno should not be the same for both records. We tracked down the cursor in nhpfin1 which set the account code and I found that for the ecls and bdca codes for the bad record was indeed returning the correct account code.  I was able to get nhrdist_posn and then the ecls from nbbposn.  The encd_seqno for the bad record in the pair had to be set up wrong in payroll.  Indeed the earnings code for the individual and labor distribution were mismatched.  Earnings was set up for classified but labor distribution was set up for faculty.  Once they fixed the 3 individuals, everything fed.

No responses yet

Oct 16 2014

Finance 8.10 Upgrade Notes

Published by under Uncategorized

FGRTRNI modified with 2 new parameters.  Feed scripts have to be modified to reflect the new parameters.  There is seed data that can be added to ftvsdat to bypass whatever choice is selected for the two parameters but you still need to put something in response.


OUS mods:

















No responses yet

Jul 10 2014


Published by under Uncategorized

WOU’s process to close POs failed leaving them unable to post the affected POs

I had to :

delete fpreoca where fpreoca_code like ‘%0002xxx’;

delete fpbeocd where fpbeocd_code like ‘%0002xxx’;

delete fpreocd where fpreocd_code like ‘%0002xxx’;

Then they were able to process POs individually.  About 160 affected.



No responses yet

Jul 08 2014

Bypassing approvals for problem Z docs

Published by under Uncategorized

Insert record into fobappd

Delete record from fobuapp

update fabinvh to set approval ind to Y

run posting

No responses yet

Jun 12 2014

AP Check Issue

Published by under ACH

FABCHKA was giving the error:

ORA-01400: cannot insert NULL into (“FIMSMGR”.”FOBAPPD”.”FOBAPPD_DOC_NUM”)
WRN-ORACERR: Error occurred in file “fabchka.pc” at line 1,040
WRN-ERRSTMT: Following statement was last statement parsed:
insert into fobappd (fobappd_seq_code,fobappd_doc_num,fobappd_bank_num
fabchka terminated with error.

I wrote some print statements so I could figure out which field was null.  Turned out to be the rpt_doc_code but rpt_inv_code was fine.   Figured out the check num field in fatckin and fatckdt was null when there should of been values in there.  I thought this got populated during fwpdird so I checked the output file for fwpdird and found it empty.  Figured they used the wrong date in the parameters. Had them run it again and this time the file looked good.  After that they were able to run FABCHKA without any error.

No responses yet

Jun 12 2014

Payroll check

Published by under Uncategorized

Got a call that shared services could not print two checks running pwpchkp.

Check print ind on table pwrchck for the two doc codes which I got from table pwrcnpb.  Print ind was set to Y so they had to use reprint parameter in pwpchkp along with the doc code range.

No responses yet

May 01 2014


Published by under Uncategorized

Here is what is on the DBEU FAQ for Phase II:

Phase Two will be executed as part of the installation of the Banner XE applications such as Catalog, Schedule,  Faculty Grade Entry etc. This phase of the Database Extension Utility will ”enable” 2 of the columns added in Phase 1 (SURROGATE_ID and VERSION) and will only do this for tables that are associated with the Banner XE application being installed. Enabling the columns will consist of populating each column with a default value and updating each column to be NOT NULL. Triggers to populate these columns will also be added at this phase.


I was able to create a junk table with two not null columns temp1 and temp2.

I then created the following trigger:







:NEW.temp2 := ‘test2’;




Then the following worked:

B8TST> insert into junk (temp1) values (‘test’);


1 row created.


B8TST> select * from junk;


TEMP1      TEMP2

———- ———-

test       test2

No responses yet

Next »