Workflow transported without containers

[tripurari_rai2]

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 · Accepted solution]

I hate to repeat myself but did you analyze the container elements of the workflow? You might be having just ONE invalid container element, and because of that reason PFTC dumps and SWDD gives you an empty container list in test system.

Check these:

1) I see from your dump that it is complaining about object reference to 'ZERO'. Is this some of your container elements? If yes, take a look into that, fix it, and then have a well-earned coffee break.

2)  Another more advanced option: Take a look to the dump. It mentions method CREATE_RH_TASK_CONTAINER (of class cl_swf_cnt_factory?). Put (or ask help from an ABAPer) a breakpoint there, execute PFTC and see if you can find out what is the problematic container element.

Regards,

Karri

[tripurari_rai2 · Accepted solution]

Thanks to all for lots suggestions.

Finally I recreated the whole new workflow & resend it in Quality system.

I am partially agreed with Karri that might be something missing in Workflow container which is not going through Quality after transport, but still its big issue to check all 70-80 Containers

I think SAP workflow team should use some exception by which we can found the exact error & get it resolve for containers kind of errors.

Thanks to All.

[srivijay_dinnimath]

Hi Tripurari Rai,

Check with below Note,

Regards,

Srivijay

[tripurari_rai2]

Thanks Srivijay.

Unfortunately this Note is not relevant to our system as we are already on basis component 740 .

Thanks

[paul_bakker2]

Hi,

Were there any errors in the original transport(s)?

cheers

Paul

[tripurari_rai2]

Hi Paul,

There is no error in original transport.

Thanks

Tripurari Rai

[Former Member]

Hello,

First try transporting a very simple workflow before you go re-creating the old one.

If that works then try copying the old one, deleting half the steps and transporting that.

regards

Rick

[tripurari_rai2]

Hi Rick,

We tried this. In fact I copied the & send it to Q system. Those containers which is in SWDD & not PFTC are getting generated & rest which are in PFTC not getting generated.

If I am trying to open the same workflow with PFTC  then getting dump (Screen shot is there in previouse post) & when I am opening the workflow in SWDD then workflow gets open with missing containers.

Thanks

Tripurari Rai

[Former Member]

Hello,

Ah, I think you may have run into a problem that I don't see mentioned often.

You should not try to add, change or delete container elements from PFTC because at that point you haven't determined the version yet. It's fine once you click on the 'Workflow Builder' button.

Is that what you did? It's an easy mistake to make. I used to do it and it gave loads of problems.

regards

Rick Bakker

[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

[I042439]

Hi Tripurari

1) Check SWU3 settings in Q - if errors are there - correct them and recheck

2) Refresh Buffers SWU_OBUF - check

3) Please execute FM SWD_WFD_REPLICATE_FROM_9999 in Quality -> SM37 -> provide the IM_TASK = WSxxxxxxx (your workflow number) - Execute -> go to PFTC and then Check

4) Execute FM RH_GET_PLVAR in DEV , get the active plan version ... this is the one in which the workflows were developed. Now execute the same in Q and see if it is the same. If not, check who changed the plan version and why

5) Still not resolved - can you share the DUMP screen shot?

Regards,

Modak

Message was edited by: Modak Gupta ........................ Found a few notes too.... 712226 - Workflow Builder: Short dump when you delete the container 882228 - Short dump in workflow container factory See if these are applicable to your system. If not, I guess you may have to raise an OSS message.

[tripurari_rai2]

Hi Modak,

Thanks for reply.

I implemented all the mentioned step as per your suggestion. But Still getting the dump & workflow having no container.

Please find the below dump screen shot.

[I042439]

Did you check for the notes too?

[tripurari_rai2]

Hi Modak,

I checked the notes. those note are not suitable for our system as out system having higher version component.

SAP_BASIS

740

0004

SAPKB74004

SAP Basis Component

Those notes are for 700 Basis component.

Thanks

[I042439]

Check what Karri has mentioned below..... if it still not helps...then please raise an OSS message.