EDI UBE - R47002C

rgepes · Mar 5, 2001

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A5A1.43B3FA00
Content-Type: text/plain;
charset="iso-8859-1"

List,

We are in the middle of our implementation and are having a problem running
the R47002C via Thin Client (WTS). We are running OneWorld Xe in an Unix
environment, Oracle DB. We have been told by JDE that this job will only
run from a Fat Client. To me this doesn't add up. This job should be run
on a scheduled basis, it's only funtion is to bring in an flat file into the
F47* tables. I wouldn't think that you would designate this job to run from
a fat client on a scheduled basis. Could anybody direct me on this? I
would appreciate it.

Thanks,
Rich

perotsystems/AdvanceWatch RichardW.Gepes
email:<mailto:[email protected]> Phone: 810.755.3000 ext. 223

------_=_NextPart_001_01C0A5A1.43B3FA00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>EDI UBE - R47002C</TITLE>
</HEAD>
<BODY>

List,


We are in the middle of our =
implementation and are having a problem running the R47002C via Thin =
Client (WTS). We are running OneWorld Xe in an Unix environment, =
Oracle DB. We have been told by JDE that this job will only run =
from a Fat Client. To me this doesn't add up. This job =
should be run on a scheduled basis, it's only funtion is to bring in an =
flat file into the F47* tables. I wouldn't think that you would =
designate this job to run from a fat client on a scheduled basis. =
Could anybody direct me on this? I would appreciate =
it.

Thanks,

Rich


perotsystems/AdvanceWatch =
 RichardW.Gepes

email:<<A =
HREF=3D"mailto:[email protected]">mailto:[email protected]</A>><=
/U> Phone: =
810.755.3000 ext. 223 =



</BODY>
</HTML>
------_=_NextPart_001_01C0A5A1.43B3FA00--

DBohner-(db) · Mar 5, 2001

Rich,

I guess the answer you don't want to hear is... JDE might be right. You're
gonna have to take into consideration where the flat file is - and how you
implementation of WTS works. Your WTS client might not be able to see the
folder (who's C:\ drive is it really on, the clients or the servers?) ....

If the WTS is configured with best practices in mind, then you shouldn't be
able to run the UBE.

Any other takers?

Daniel Bohner
www.existinglight.net

amwalshjde · Mar 6, 2001

I agree. The issue is most likely that WTS cant find or read the directory that you are reading from. How are you specifing which file to use. a UNC path, or dos style? if you are using dos style (ie x:\edi\data) then make sure the server that the job is being submitted to has that drive mapped.

If you have several servers thedrive maps would need to be set up all on (assumiong that any server might run that job).

does that help?

Aaron

mwilson · Mar 7, 2001

Unfortunately, JDE is correct. This job has to be run on a fat client. The reason is that the UBE uses an intermediate temporary file that is hardcoded to go to the C:\ drive on the client. We ran into the same issue here. We have a full deployment of OW on our EDI server and this UBE runs there. Also, be sure that when you setup your EDI Flat File cross reference (P47002) that you use the shared network address for the file (i.e., //servername/directory/filename.dat) and not the drive letter designation. Makes things much easier in the long run if you need to change which client the R47002C is run from.

Hope this helps,
Mark

B733 (Base), HP9000, NT, Oracle, WTS, Citrix
(Upgrading to Xe)

EDI UBE - R47002C

rgepes

Member

DBohner-(db)

Legendary Poster

amwalshjde

Well Known Member

mwilson

Member

Similar threads

We value your privacy