topic Re: packages: local objects only for developer himself? in Application Development and Automation Discussions

packages: local objects only for developer himself?

Former Member — Wed, 21 Nov 2007 10:45:35 GMT

Hi there,

I developed a program that uses a proxy to communicate with SAP XI.

For the input data I created a dynpro.

If I call this dynpro with my credentials everything works fine. Another user

received a dump while trying to send data.

I created all these objects (proxy, abap program, dynpro) in the local package

$tmp. Is this the reason the dump appears? I thought $tmp is like a normal package

but not transportable to other systems.

The dump says that the reference to the proxy classes is null.

Do I have to create a usual package that other user can access my objects?

thx

chris

Re: packages: local objects only for developer himself?

matt — Wed, 21 Nov 2007 10:52:46 GMT

Being in $TMP is, in my opinion, highly unlikely to be the cause of your dump. You should have the user debug, and see why he's not getting a reference to your proxy class. Could be authorisation or something.

matt

Re: packages: local objects only for developer himself?

former_member404244 — Wed, 21 Nov 2007 10:54:59 GMT

hi,

$TMP is not the cause of your dump.try to debug and see,may be due to authorization issue.

Regards,

Nagaraj

Re: packages: local objects only for developer himself?

Former Member — Wed, 21 Nov 2007 11:38:13 GMT

Thanks. It works. I always started the program out of se80. For other users

I defined a transaction code. The tcode directly started a dynpro without

inital the the variables.

Debbuging displays this error.

Thanks a lot.

greetz

a newbie