Wait Step for Unknown Object

Wed Apr 7 15:10:41 EDT 2010

IT WORKS!!!!
IT ACTUALLY WORKS!!!!
IT REALLY ACTUALLY WORKS!!!!

Thanks to Paul and sap-wug-bounce.  Y'all are the bomb-diggity!

Just some further info (in case anyone else has this problem and so this 
email isn't pure spam)
1. Had to subtype BUS2013 to my Z_BUS2013 and add an attribute of type 
EKPO-MATNR.  SAP auto generated the "SELECT SINGLE ..." code that filled 
the attribute with a material from 1 line item from the SA (no problem, 
all our SA's only ever reference 1 material, we just change the SLOC). 
Only a couple of minor mods to the generated code.
2. The OSS note you mentioned is not applied in our systems, but the 
workaround included in the note got the wait step working.  This is 
critical because in my case, the workflow broke at the process control 
step - even though the problem was really in the wait step.  Once I did 
the workaround everything worked as expected, but confusing at first.
3. I had not seen the second link Paul references, but that is the key. It 
is very thorough (a couple of errors and assumptions, but figure-outable).
4. Tested the positive case (created an SA referencing the material) as 
well as the negative case (created an SA not referencing the material) - 
only the positive test case triggered the wait step.

I can't thank you enough for taking the time to answer my question.  This 
workflow would have been a no-go without your help.  Whoot!!!!

Michael McLey 
MBUSI - IT Parts & Administration 
Mercedes-Benz US International, Inc. 
1 Mercedes Drive 
Vance, AL 35490 
PHONE:  (205) 462 - 5239 
EMAIL:   michael.mcley at daimler.com   

wug at workflowconnections.com 
Sent by: sap-wug-bounces at mit.edu
04/07/2010 03:41 AM
Please respond to
sap-wug at mit.edu

To
sap-wug at mit.edu
cc

Subject
Re: Wait Step for Unknown Object

Agree with Paul, that's exactly what correlations are designed for. What
may throw a spanner in the works is that the materials are at item level,
so you may need to work with a Scheduling Agreemeent item object. A less
elegant alternative is raise an event for each material when a scheduling
agreement is created.

On Tue, April 6, 2010 10:42 pm, Paul.Bakker at osr.treasury.qld.gov.au wrote:
> Michael,
>
> Yep, this sounds like a good opportunity to use correlations. It's a bit
> hard to get them to work the first time, but they are magic.
>
> It will only work in your case if the 'scheduling agreement' (that you 
are
> waiting for), can be identified by some (combination of) field values
> inside it
> (in your case, the material number(s)).
>
> I would suggest you read the related SAP Help and  blogs in SDN (if you
> haven't done so already):
>
> 
http://help.sap.com/erp2005_ehp_04/helpdata/EN/8d/25f07b454311d189430000e829fbbd/frameset.htm

> http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/6976
> http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14136
>
> You may also need to implement OSS note 1335009.
>
> Give that a go, and if you have any specific issues getting it off the
> ground, please post them here.
>
> cheers
> Paul Bakker
>
>
>
>
>              michael.mcley at dai
>              mler.com
>              Sent by: To
>              sap-wug-bounces at m         sap-wug at mit.edu
>              it.edu cc
>
> Subject
>              07/04/2010 06:17          Wait Step for Unknown Object
>              AM
>
>
>              Please respond to
>                "SAP Workflow
>                Users' Group"
>              <sap-wug at mit.edu>
>
>
>
>
>
>
>
> Hey All,
>
> I have tried posting to this user group 1 time before with this 
question,
> but but I wasn't a member at the time and I get a "bad confirmation
> string"
> when I check the bounce.  It's been > 3 days so I'm guessing the first
> mail
> is gone.  I hope I'm not double-posting or causing problems by trying
> again.
> -----------------------------
> Anyhoo...
> I am working on a "new materials" workflow that has several (let's call
> them) processes.
>
> The first process is that a new material master record is created and 
some
> work items go out to various users to adjust the material with some
> specific information.  No problem here.
>
> As a second process, I would like to wait for a scheduling agreement
> (purchase order) for this new material to be created and some more work
> items sent out to adjust the scheduling agreement and a few other things
> associated with the material.  This is where I have my problem.  At the
> time the wait step is created, I do not have an object in the container 
to
> represent the scheduling agreement (because it isn't created yet).
> Further, I believe the key for any scheduling agreement event uses the
> document number and does not include the material.  So how would I 
create
> some kind of wait step for something like this?
>
> The scheduling agreement references material numbers in each line item,
> but
> a wait step seems to need the key of a scheduling agreement in order to
> know that a specific event is meant for a specific workflow instance.
>
> The users are definitely not looking for a general scheduling agreement
> workflow (that would affect all new scheduling agreements) - only
> scheduling agreements for new materials.
>
> I have looked into something called a "correlation", but so far I have 
not
> gotten it to work, and I'm not sure if it even will.
>
> Any suggestions?
>
> ... or maybe this doesn't make sense to anyone...
>
>
> Michael McLey
> MBUSI - IT Parts & Administration
> Mercedes-Benz US International, Inc.
> 1 Mercedes Drive
> Vance, AL 35490
> PHONE:  (205) 462 - 5239
> EMAIL:   michael.mcley at daimler.com
> If you are not the intended addressee, please inform us immediately that
> you have received this e-mail in error, and delete it. We thank you for
> your cooperation. _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
>
>
> 
******************************************************************************************************************************************************
>
> Only an individual or entity who is intended to be a recipient of this
> e-mail may access or use the information contained in this e-mail or any
> of its attachments.  Opinions contained in this e-mail or any of its
> attachments do not necessarily reflect the opinions of Queensland
> Treasury.
>
> The contents of this e-mail and any attachments are confidential and may
> be legally privileged and the subject of copyright.  If you have 
received
> this e-mail in error, please notify Queensland Treasury immediately and
> erase all copies of the e-mail and the attachments.  Queensland Treasury
> uses virus scanning software.  However, it is not liable for viruses
> present in this e-mail or in any attachment.
>
> 
******************************************************************************************************************************************************
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100407/1191963f/attachment.htm