SRM 5/SupportPack18 - Runtime object cannot be created, etc

Wed Oct 7 10:20:10 EDT 2009

Update: This issue is definitely related to the persistence of the workflow container.

When I switch the container from XML persistence to Compatibility Mode, the workflow is able to start normally when a shopping cart is created via SRM Gui.
ECC issues later in the flow have all been resolved (thank you, Master Data) and the flow completes as expected.

When I switch the container back to XML persistence, and create a shopping cart from the SRM Gui - that is when the nasty 'Container (runtime object) cannot be created' message is generated.

So, my understanding of using XML persistence is that it is supposed to use less table space and run faster.  The standard SAP-Delivered Workflow for SC Release (WS14000044) uses 'Compatibility Mode' in its' container profile.  And, I know in older ECC releases - it was often possible to raise an event and start a workflow before the object was created in theDB - typically a FIPP doc.
In this scenario - I am wondering if the same thing isn't happening in our SRM system - the workflow is started, the object can't be instantiated at the time, the workflow fails.

Thoughts?  I know there are lots of 'container gurus' out there!

----
Susan R. Keohan
SAP Workflow Specialist
Enterprise Applications
Information Services Department
MIT Lincoln Laboratory
244 Wood Street, LI-200
Lexington, MA. 02420
781-981-3561
keohan at LL.MIT.EDU

________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Keohan, Susan - 1140 - MITLL
Sent: Tuesday, October 06, 2009 11:24 AM
To: SAP Workflow Users' Group
Subject: RE: SRM 5/SupportPack18 - Runtime object cannot be created, etc

Sorry - Fat Fingers on Keyboard sent this out before I was really finished.
If I manually start the workflow - it will abend later on when reaching across to ECC system - so that's to be investigated later.
If I change the container persistence to 'Compatibility Mode' - the workflow can start, and then fails on reaching across to ECC.

I have deleted and re-created the binding from event to workflow - no joy.

I have double-clicked and drilled into each container object to get to the DDIC definitions - no joy.

I've done my due diligence in SAP-WUG, SDN, and OSS searches for the initial error - which is SWF_CNT_001004 - Container (runtime object) cannot be created.

Any tips would be greatly appreciated!
Thanks
Sue
----
Susan R. Keohan
SAP Workflow Specialist
Enterprise Applications
Information Services Department
MIT Lincoln Laboratory
244 Wood Street, LI-200
Lexington, MA. 02420
781-981-3561
keohan at LL.MIT.EDU

________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Keohan, Susan - 1140 - MITLL
Sent: Tuesday, October 06, 2009 10:48 AM
To: SAP Workflow Users' Group
Subject: SRM 5/SupportPack18 - Runtime object cannot be created, etc

All,

We are in Sandbox, a copy of our production system  (SRM 5, support pack SAPKA70008) - and sandbox has had support packs up to SAPKA70018 applied.
Standard workflow customizing, block corrections, etc. have all been carried out.

We have 5 main workflows in this system (SC, PO, PO-CV, Bid, Contract).  So far we are only testing SC and PO.

The creation of new SC workflows error out  at  the very start with the following errors:
[cid:image001.jpg at 01CA4737.5CC44360]

These are errors SWF_CNT_001004 and WL826 respectively.

There is no data in the WF container.  Surprisingly, I changed the container persistence from XML to compatibility mode, and the workflow was able to start - although later errored at another step.  I have deleted and re-created the binding from the event BUS2121 SAVED to the workflow

Even more surprisingly - the PO Workflow can start and complete with no issues.

OSS makes no reference to SWF_CNT_001004 - but note 939489 seems relevant although we are not concerned with previously started workflows *yet* - so I have manually checked each WF Container object in the SC workflows.  All the DDIC objects exist and are activated.

Susan R. Keohan
SAP Workflow Specialist
Enterprise Applications
Information Services Department
MIT Lincoln Laboratory
244 Wood Street, LI-200
Lexington, MA. 02420
781-981-3561
keohan at LL.MIT.EDU

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20091007/f80ac497/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 27488 bytes
Desc: image001.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20091007/f80ac497/attachment.jpg