container elements not transporting

[ross_goodman]

Hi,

Using PFTC_CHG I have added an element to the container of my workflow template. This went in to a workbench transport request. I activated the workflow template and transported to QA . All reports as being healthy.

When I look in the containier in QA the new element is not there!!

AmI missing some extra step somewhere?

Cheers,

Ross

[Former Member · Accepted solution]

Hi,

maybe you can check, whether the workflow that being transport is in released status of released?!

or the task that contain container element is transport to a package?

then do the transport again.

thanks

[ross_goodman · Accepted solution]

That got it though it took me several goes to get the status to change to released!!

Thank you very much.

Ross

[ross_goodman]

Taking a few steps back and treating this as an exercidse in flow design rather than a development opportunity really did the trick. Thanks Rik for putting my brakes on

I had to develop a few new methods to handle flag creations in the main container outside the rule modules and once that was done the rest all came down to putting decisions in the right places in the flow.

Thank you all for your help. See my next question now on email being picky about who it will and will not send mails to

[ross_goodman]

TOO quick off the mark!

The 5 elements only show up the SECOND time the rule is called, the first time I can still only see 3 of the elements!

SO at inception (creation of workflow)the rule is called and only 3 elements are visible in ac_container.

After the latest end deadline is reached the rule is called again (same task) and this time all 5 elements can be seen in ac_container.

WTF?

[Former Member]

Calm down. SAP works just fine. If you have people creating local transports in QAS then you can expect all sorts of problems.

Who knows what else they've been doing.

I would start again from DEV with a fresh copy of whatever you are trying to do.

Let us know if there are any problems and exactly what they are.

Don't forget to do SWU_OBUF after every transport and make sure they're done in the right order and make sure they don't have any errors in their logs.

[ross_goodman]

Hi Rick,

It looks pretty much as I acannot achieve what they want to do with the currently modelled latest end outcome anyway. Which brings me to the point where I need to know this.....

The current latest end outcome is modelled to end the workitem and the obsolete line that it follows increases the escalation level and creates a new workitem for the new 'escalation' agent.

I need to stop this happening in a certain instance. So when the latest end deadline is reached I want to have the current model happen if it is agent A but if it is currently agent B I do not want to escalate in effect and more importantly I want the workitem to remain in the inbox of agent B.

So can I put a fork in the outcome of the latest end deadline and have the fork go to a non completion model when the agent is currently user B, but got to completion when other than user B?

Ross

[Former Member]

Hi Ross,

Keep it simple, just create a new workitem when the deadline expires and set the agent to whoever you want depending on who the agent is now (A -> escalation agent, B -> B).

regards

Rick Bakker

hanabi technology

[ross_goodman]

Latest changes not transporting and this time the status is definitely RELEASED

Last week after changing the status from "not defined" to "RELEASED" I got the changes to transport . It didn't work straight away which bothered me at the time BUT HEY IT WORKED ANYWAY. It was perhaps the 3rd transport of the released template that finally carried the changes into QA correctly.

However I have now added another field into the workflow template container and guess what! IT WON'T TRANSPORT.

The templates has status released. The object shows up perfectly in the transport but the workflow template has not changed in the receiving client. The workflow is activated and I generated a version before transporting.

THIS IS DRIVING ME NUTS! What to try next is the big question here ?

Ross

Edited by: Ross Goodman on Nov 28, 2010 10:34 AM

[Former Member]

SWU_OBUF?

[ross_goodman]

Hi Rick,

Something far simpler, a BA had made changes to the template IN QAS and had a local transport in that system. The transport ws failing due to lthe objects being locked in that transport. Consultant abused and transport removed!!

BUT how about this one now..

I have a rule that determines the invoice approver, uses a function module.

I have changed the rule container to contain two extra fields today so originally

A

B

now

A

B

C

D

anmd changed the bindings accordingly.

The changes have transported perfectly and are visible everywhere including the changed binding for the workflow container to rule container in QA.

However when I debug the function module and look at AC_CONTAINER this contains only elements A and B.

I have just done an SWU_OBUF but have yet to see the result, I would be surprised to see that affecting this problem though surely.

• UPDATE

After swu_obuf the 1st of the new fields is now available in the function module!! But not the 4th. Added another fIeld and even generated a new version of the workflow itself, transported to QAS accordingly. I still have only A, B and C showing in the function module though all elements show in the rule display and in the workflow display.

I HATE SAP!!! Have tried a few reruns of OBUF bit no improvement .

Edited by: Ross Goodman on Dec 2, 2010 1:57 AM

Edited by: Ross Goodman on Dec 2, 2010 3:09 AM

[Former Member]

Hi Ross,

Try to generate the template via SWU5 or SWU7, alternatively use PFTC or SWDD to generate a runtime version.

Then if a business object is involved generate this via SWO1.

If you made changes to the business object to include the new attributes, ensure they have been released.

Finally then run SWU_OBUF.

Good Luck

Thanks Simon

[ross_goodman]

Nothing I can do gets this to work!!

I even made a brand new rule with 5 elements in the container and replaced the existing rule with that.

Genreated a new version of the workflow and activated it.

Transported, refreshed buffers and the function module can still see the same 3 elements as yesterday!!!

I want to swear right now!!!

[ross_goodman]

ANSWER!!!

1] Delete every element in your rule

2] activate your workflow and generate version.

3] transport and SWU_OBUF in target client but not usre if this is actually necessary.

4] put elements back into rule

5] activate your workflow and generate version.

6] transport and SWU_OBUF in target client

All elements are now visible in the function module.

JHFC as they say!!

Thanks for your assistance guys they were all great ideas even if SAP didn't think so!!

Ross