Workflow transported without containers

[#1]

Hi SAP Workflow Guru's

I am facing a strange issue related to one custom workflow. Custom Workflow is working perfectly fine in development. Then we transported it to Quality server. After successful transport, I checked the workflow in PFTC. I got a dump with runtime error "OBJECTS_OBJREF_NOT_ASSIGNED_NO". Then I tried to open the workflow through SWDD & was shocked to see that whole workflow is there without any container (Even Standard Containers not present for there).

I tried to send the same workflow with new transport & faced same issue again.

Then I copied the workflow & created new copy workflow. But issue still the same in Quality server.

Please help.

[Former Member]

Have you done changes to the container elements (I assume that you have done some changes to the workflow since you are transporting it to test)?

Could it be possible that you have created container elements referring to some Z-objects (data elements?) that have not been transported to test yet. Or have you changed some properties of some data element that you are referring?

Take also a critical look to all changes (tasks and their containers etc.) that you did for the workflow template, and see if they are referring to something that perhaps is not yet transported to test system.

Regards,

Karri

[Former Member]

...and also check if you can run the syntax check for the workflow template in test (in workflow builder SWDD). Perhaps it will tell what is wrong unless you are getting the dump while accessing the template...

Kind regards,

Karri

[tripurari_rai2]

Hi Karri/Modak,

find the below screen shot of custom workflow in dev serve.

After transport to Q System

As you can even standard container not present in Q system. Only few containers are there.

Please suggest,

[Former Member]

Wow, that is a one monster workflow!

Unfortunately your screenshots do not help solving this problem. Are you able to run the syntax check in test? What does it tell?

You still need to analyze the changes. Check the transport that was transported to test, and see which objects were transported with that. Start your analysis with those objects. Compare them in developmentt and test.

Regards,

Karri

[tripurari_rai2]

Hi Karri,

while syntax check its showing 403 errors. All related to the containers missing.

Can you please tell me, is there any way by which we can transport the containers from one Dev to Quality?

Its wearied behave of Workflow. Till now I just save the workflow & get the transport number. After successful import of Transport, we get all the component including containers in Q & P systems.

The similar kind of 7-8 workflows I have send in  the same system landscape from Dev to Quality.

Don't know what went wrong with this one.

[Former Member]

Hello,

Do other workflows work properly in the QA system? When is the last time you transported a workflow from Dev to QA?

You could try creating a very simple workflow in Dev and transporting i, see if that works.

If so, try making a copy of your mega workflow and transporting that.

Please keep us informed.

regards

Rick Bakker

[tripurari_rai2]

Hi Rick,

We have developed around 10 other workflows in the same landscape. All are working fine except this one.

Regarding the Copy workflow trick, that I have already implemented. Original workflow was WS99900016 which we send first.Then the problem arises i n Q system for this particular workflow. Then saved all the components of this workflow again with new transport & send it to Q. Again we faced same issue. Then I copied the workflow & created  new copy workflow WS99900026 & send it to Q. But still same problem is there in Q system.

Now I am planning to recreate whole whole workflow in Dev as I have no options left