on 09-04-2014 1:32 PM
Hello Experts.
i saw a new issue with the PO release strategy that, for certain PO's When the po is successfully released automatically PO CHAGNE and PO REJECTED workflows are getting triggered.
This is happening with only few PO's Not all.
If it is related to Event raise of CHANGE nd REJECT , for every PO release they should trigger ryt.
But only for certain po's its happening. And user says they never changed or rejected the PO'S and they are successfully released.
I Verified to some extent but no use
Can you suggest.
Regards
Prasad CH.
Hi Prasad
You said CHANGE and REJECTED "Workflows" are triggered - for certain types. Is it that the "EVENT" is triggered for ALL types and only for certain types the workflow is started by that event?
If yes, then there should be a start condition / check function module.
But the main issue is why the events are triggered. Correct me if Iam wrong.
How is the release happening? SBWP?
Is it just one WF getting triggered on CREATED, CHANGE and REJECTED events or there are individual workflows for each activity?
What is the design of your workflow(s)? What are the triggering events?
Are these events being triggered by standard? Or is there any additional development for explicitly triggering these - like SWEC or Enhancements?
"I Verified to some extent but no use" - what did you verify?
Regards,
Modak
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Modak.
Please help me with this.
When ever change event is triggering, reject event is also triggering it seems.
When i see the trace SWEL i see some thing like this.
Reject event has receiver type as WORKITEM and also template.
EVENT RECEIVERTYPE
----------------------------------------------
CHANGED <WORKFLOW #>
REJECT WORKITEM
<WORKFLOW #>
For reject only i see WORKITEM & WORKLFLOW , but for change event only workflow.
How to work with this.
Please advice.
Hi Prasad
Are you/or someone REJECTING a PO?
If yes, then one entry for REJECTED is ending a waiting workitem (waiting for approval) and ofcourse, REJECTION is also a "Change" and hence it is triggering a CHANGED Event.
How is your workflow designed to start? Which Events are triggering events?
Where in that WF, the REJECTED event is being waited for?
How is the rejection happening, from the workitem (from SBWP) or outside the WF?
What is the username behind the REJECTED event in SWEL?
PS: please make sure you first answer the questions asked and then put up further questions. I asked a few questions earlier, to which your response is entirely different. It's difficult to help resolve the issue in this manner. There are specific reasons we ask these question!
Regards,
Modak
Yeah modak.
I'm sorry i forgot to answer your previous questions.
How is the release happening? SBWP?----- Yes , from there they will go to ME54N
Is it just one WF getting triggered on CREATED, CHANGE and REJECTED events or there are individual workflows for each activity?--- DIFFRENT WORKFLOWS FOR EACH ACTIVITY
What is the design of your workflow(s)? What are the triggering events?---RELEASE STEP CREATED.
Are these events being triggered by standard?--STANDARD
Here in SWEL i see the reject event crator is the one who started the workflow and change evnt is also crated by him.infact he did not reject but he changed only.But unfortunately REJECT event is also getting triggered.
its a WORKITEM and also a template is aggigned to this evnt and hence it is starting this template.
Please post if you need any.
Cheers.
Prasad CH.
Hi Prasad
What did the user "change" which triggered the event? What do you see in the header and item changes at that time for that user?
Can you also pelase check the config for REJECTED?
Check SWEC as to what are the triggering change events mentioned for REJECTED and is there any restriction condition.
Did someone change the config?
Regards,
Modak
Hello Modak.
I did verify this SWEC
for change event no field restrictions are made and for rejection
i see there is some thing in EVENT CONTAINER.
AND filed restrictions are as follwos, with that helps us. What is this event container.
EKKO_FRGZU_OLD NE SPACE
EKKO_FRGZU_NEW EQ SPACE.
Cheers
Prasad ch
Hi Prasad
The field restrictions for REJECTED seems to check if the release step was changed.
But did you check the change logs as to WHAT all the user has changed when the REJECTED event was fired? Does these fields show in the change log of the PO (in ME23N)? (You still manage to skip this question in your reply)
If yes, ask the user what all he/she "Changed" -> there can be a config/enhancement which changes the release (rejects) it based on what the user may have changed.
Regards,
modak
Hello Modak.
This is want happend in event trace. PO was changed on 1/1 and Change event is raised on 18/8
I wanted to know what does this EVENT DATA & TRACEDATA in swel(after double clicking on the event in swel)
Issue is, for a workflow event trace, it says EVENT CREATED ON 1/1/2014 (in event data) and EVENT TRACE DATE/TIME 18/8/2014(trace data).
Here in 1/1/2014 there is an event created CHANGED.but the worklfow did not start then.
It was started on 18/8/2014. By that time the actual release of PO completed and this workflow again started saying PO changed.
If i verify event trace by date for 1/1/14 and 18/8/14 it shows the same
I verified both the CDHDR and CDPOS and see the entries are changed on 1/1/2014 only.
How can this happen???
What does this EVENT TRACE DATE/TIME mean??
The event even created on 1/1/2014 the workflow starts on 18/8/2014 as per the EVNTTRACE DATE.
Please Advice.
Cheers
Prasad CH.
Hi Prasad
You have already posted a separate thread for this. This seems to be diffrent from what you have been asking in this thread .... this thread is about User CHANGED, but REJECTED was also fired.....
Hence, lets please stick to one thread at a time and not mix two of them.
Please do let me know if you are still interested to solve the original issue and if Yes, kindly make sure that you answer all the questions asked. I will not be able to reply otherwise.... beacuse you do not provide the info required to help you further.
regards,
Modak
Hey i deleted that thread before sticking to your workds Modak.
I'm sorry and correct me if iam wrong.
Unknowingly i created another thread and then deleted it.
Iám talking about the same issue.
Iám very new to workflows hardly days.. after verfying i found this issue.
When the PO release is initiated, they may release it through some tcode ryt, there an event called and CREATED and RELEASED also triggred.
In swel i see EVENT CREATED (both) are on 1/1/14 and TRACEDATA says 18/8/14.
I see the user changed the release indicator,currency and hence the rejection event is fired , but it was fired after 8 months and a workflow is started. Same with Change a workflow started.
I even verified in event queue that 1 lakh events to be delivered. Is this the problem?
Please be noted that is the same issue iam talking about.
I always value experts suggestions.
Cheers
Prasad
Hi Prasad
Check SWE2 for these Events and see if event is delivered by an event queue - is there a checkbox for that in SWE2?
If yes, check SWEQADM and see if the event queue job is scheduled. There can be something wrong with this job - that the events are delivered to the queue but no job was running to pick them from the queue. Find out who scheduled the job last time and ask them why they did it? Was it not running earlier?
regards,
Modak
Yeah Modak i verified,
For these two evnts Changed & Rejected, event linkage and event queue are checked.
Regarding the event queue as you said some thing seems to be wrong, they are(in lakhs to be processed.). Tried who scheduled and how it is done , i see the event queue is active,background queue is active, and all other settings are acitive. Background job is made dynamic not at regular intervals. I hope this issue is because of this only.
No body here knows any other information. .
Can you conclude some thing from this.How to get rid of this because in future other issues may arise and create a big trouble.
Cheers
Prasad CH.
Hi Prasad
Well..... this workflow was meant to start via a queue..... and no one scheduled the job to clear the queue!!! So they kept accumulating in the queue, without an "out" door. One fine day someone realizes this and triggers the queue job (opens the door).... meanwhile the actual POs were processed manually.
So you need to logically delete (cancel and not actual deletion) these items. Check with business owners and then select which ones are relevant and which are not.
regards,
Modak
Hello,
Check in the event trace which events were created and when. The time of creation should give you a clue.
As for what the users say: "Trust but confirm"
regards
Rick Bakker
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prasad,
Provide screenshots of workflow trace where you observed that PO CHANGE & REJECTED workflows are triggered and the workflow log of successfully released PO.
Regards,
Murali Krishna.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.