on 04-04-2016 11:16 AM
Hi IDM Gurus,
I have done my configuration in IDM DEV environment and now preparing for production.
I have exported all packages to PRD but facing a problem while importing Active Directory package from DEV to PRD.
Also I have tried to import the Standard SAP delivered package which is absolutely fine.
Please look at the logs below :
Please suggest how this can be resolved.
Thanks
Peter Wong
Dear all,
Do you you have some workaround about this issue ?
I have the same problem when i try import standard SAP packages .
thanks and Regards.
Roberta.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Peter,
which changes did you do to the SAP-delivered package? Do you have Forms in the Package?
Greetings, Aydin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Lukasz,
there are some workarounds we use today for import problems:
- Delete all access controls of UI-Tasks (Forms)
- Delete all Filter Tasks/SQL-Statements etc. on Forms
- Use as less dependencies as possible on packages
- Patch to latest patchlevel (from 04.01.2016) which fixes dependency errors
Maybe follow these steps first.
Additionally there might be a problem with "Event Tasks" (look at the third log-entry), maybe you are referencing to an event which is not resolvable by the system. Better delete the event tasks and reassign them after the import.
Greetings, Aydin
Actually none of these worked for me, but i have found my own workaround.
I tested it on ABAP package. The transport from dev to pre-prod didn't work. So i tried to create a custom package to use it a transport to pre-prod. I copied Processes and Triggers to this package from ABAP package and tried to transport it.
The actual problem was the scripts within the processes. When i tried to open of of ABAP package scripts i was getting HTTP 404 error (the same as in the form issue).
Those processes which didn't use scripts from ABAP package were transportable, these which did have script from ABAP package were non-transportable.
My workaround was to unassign scripts from from processes in dev, transport the package to pre-prod and then reassign the scripts to package in pre-prod. It's not ideal, but it's working.
Lukasz
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.