Changed jobs so inherited a BAANIVc4 AGS2 system, I am trying to lock down the user access on the baan system. Most people were running with super user status so I have created limited accounts for them and control their access via session authorisation. But users are unable to use the session tcedi7205m000 direct network communication. when they run it it looks like it has worked they don't get any error messages saying it has failed or that they are not authorised for the session. but the edi messages are not processed. Login with a user that has superuser rights and it works. What special requirements are needed for a regular user to run this session.

Dear Darren,

please check the followin packages / modules authorization which are called
by session tcedi7205m000 "Direct network communication":

Sessions used:
tcedi7220m000
tcedi7210m000
tcedi7220s000
tcedi7205s000

Program Objects / Tables:

tcedi (Tables) (tcedi700, tcedi701)
tcedi (functions) (tcedi0020)
tcedi (scripts)
tdpur (dll) (e.g. tdpurdll4280) (check session tcedi0150m000 -> objects used by message e.g. 850)
tdsls (dll)

Could be that user needs text permission ? (tt txt)

Possibly users needs file permission (command.fil // EDI files).

Regards,

Kozure

thanks you Kozure

I already granted the user access to the whole TC module and gave them update rights on the default text group and gave them full control on the EDI folder and all sub directories thats why I cannot understand why it doesn't work.

Check company authorizations. They need authorization for both sending and receiving companies.

it is external EDI sales schedules and deliveries incoming and ASN's out.

Thanks

Hello Darren,

Have you tried looking at the permissions of the actual EDI files on the server (ie. DELINS). The behaviour of the session is what happens when the files aren't physically there.

We have a very similar EDI setup to yours 4C4 ags0 and normal users are OK running the session. The only difference is that we generate our authorisations via DEM.

Cheers
Neal

Hi Neal
The users already had full control on all the EDI folders, but the problem appears to be with the share, in the maintain networks session the path uses the d$ share, by default the only users allowed access to a default share is an administrator. I am going to change all the shares and it should work.