on 08-20-2007 2:16 PM
Hi Experts,
I urgently need your expertise in resolving some of my problems with workflow. My first question is, can there be two subtypes(ZBUS2012 and XBUS2012) from supertype BUS2012 and still delegated to BUS2012? I tried and an error message "Target key must be different from source key?" Can I not have a 2nd subtype (XBUS2012)and deletegated to one supertype BUS2012?
Your expert feedback is greatly appreciated.
Thanks for your valuable input.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, and it doesn't make sense to. If you could have multiple delegated subclasse each with a ZRELEASE method, which one does SUPERTYPE.ZRELEASE execute?
Edit:
Just to clarify after reading question again - multiple subtypes are fine, but only one delegate is possible for reasons above.
Message was edited by:
Mike Pokraka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike,
Although this message is closed, I would like to ask one last question.
The question is, if I have my own subtype(XBUS2012) from the super type BUS2012 and delegate it to BUS2012, what happens to the production environment? The production environment has ZBUS2012 delegated to BUS2012. My question is, what would happen to ZBUS2012 when I change the delegation to XBUS2012?
Thanks,
What do you <u>think</u> would happen? My guess is that your thinking will be correct, especially if you think you'll be in for some trouble
All of a sudden the methods/attributes/events you have defined for ZBUS2012 will no longer be available in the workflows where you are using object type BUS2012. Instead, the methods/attributes/events you have defined for XBUS2012 will be available.
Now, if you happen to define all the methods/attributes/events that exist in ZBUS2012 in XBUS2012 as well, everything may work out perfectly, perhaps... I would test it seriously in the QA environment first!
Hello,
That is one of the reasons why I wanted stay from changing the existing ZBUS2012. As complex as workflow is, I wanted to minimize the impact on the existing subtype. I guess I have no other way but to use the existing ZBUS2012 and add my own events and methods. Am i thinking correctly?
Thanks,
Replying to myself is not something I normally do, but I found OSS Note 1028191. Apparently you can now (basis release 700 and releases from 46C with corrections from note) delegate in two levels. I tested it, and it didn't work ... not until I re-generated the object types.
So I suppose what you can do if you want is to create your object type ZZBUS2012 and inherit from ZBUS2012, then register a delegation from ZBUS2012 to ZZBUS2012.
Hi Kjetil,
Thank you very much. Your input has been VERY helpful. Applying this note(or any oss note for that matter) is almost like crossing a mountain. We have VERY tedious and ridiculous processes to applying one little thing to the system.
Thanks again.
By the way, are you familiar with how inbound edi purchasing order acknowledgment triggers the workflow? Here is the scenario:
1) we receive inbound edi purchase order acknowledgement from the vendor
2) if the po acknowledgement processes successfully, then it is okay. However, if it fails, I need to determine what one of the values in the idoc is and need to trigger transactions like MM)3, ME22N, etc
3) currently, we have it so that if inbound po acknowledgement fails (for any reason) a work item is forwarded to inbox.
4) I have been looking 000008075 std task, task groups 20000011, 20000010 and still couldn't' figure out where/how I can do what I intent to do.
Your expert advise is greatly appreciated.
S.
No, I am not familiar with your EDI scenario (actually not really familiar with any EDI scenario), but 8075 looked like a good place to start to me. I assume you have your IDoc configuration in order - not that I am an expert in the area, but I believe your error handling is defined - or at least influenced by - the partner/message type configuration.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.