Financial Report w/ Drill-Down

ismith

Active Member
Yo Listers, hope all is well at your site!

We have deployed a custom batch application, which is a financial report =
(income statement) that has dollar amounts sorted and level-breaks by BU =
Category Codes, Acct. Cat. Codes, and Object Accts. Everything works =
fine when I run the report locally in CRP. I have the Financial Report =
properties set to "no sign reversal." The report was promoted/deployed =
to production. I run it from the Terminal Server to run on the =
Enterprise Server and the Revenues come out positive (should be negative =
because they're credits). When I run it locally in PROD, from the =
pcAnywhere fat client (only access to fat client is through pcAnywhere), =
it runs correctly, just as it did in CRP, where I developed the report.

When I log in through the terminal server (remote desktop), I log in to =
PRD733, as opposed to WPRD733. Could it be that the OCM mappings are =
different, and that I should actually be logging in through WPRD733 =
instead of PRD733? I never realized until I saw some recent postings =
that this could be why there is two separate pathcodes (?).

My suspicion is that the Balance Auditor (interactive application, =
P83003, I think) program, which is called from within the financial =
report, that summarizes the dollar amounts for the drill-down function =
is somehow not mapped correctly. Or maybe the right version is not =
being called. Everything else on the report seems to work fine, except =
that I get the wrong sign.

Our config. is fairly unique. We are in U.S. with Deployment Server, =
Ent. Server, and fat clients in U.K. We just have access to terminal =
server (remote desktop), and two fat client machines via pcAnywhere and =
SnapShot.

So my work-around, for now, is to run locally via pcAnywhere. (I =
actually havn't tried logging in to WPRD and trying it in that pathcode, =
since I just thought of that.)

TIA for any help.

Regards,

Ian

B73.3.1, SP 16.1
SQL 7
W2000
Terminal Server (Remote Desktop)

Ian Smith
Senior Business Consultant
Capita Technologies, Inc.
[email protected] (webmail/isp e-mail)




Current Client Configuration:
OneWorld B73.3.1
Windows 2000, SQL 7
accessed via Remote Desktop (Terminal Server)
 
Have you tried submitting the report to the server from a fat client? Maybe the enterprise server specs are corrupt, you may want to deploy to the server again.

Jean Driscoll
CNC Administrator
Holiday Retirement Corp
[email protected]
AS/400 Co-existent Xe/Cum12
 
Back
Top