IDOC is not processed in WF

[Christian Behla (QDD)]

Michael,
1. cancel and restart the same Workflow: no, it doesn't work
   cancel first workflow and start second: yes, it does.
  (workflow, not workitem)
 
2. if have tried inputforeground, it does not work
 
3. right, the first step is custom stuff. Within this step we tried to close the read statement: error message says: nothing open.
 
cheers chris
 
-----Original Message-----
From: Michael Pokraka [mailto:MPokraka at samsungsemi.co.uk]
Sent: Montag, 11. Dezember 2000 18:19
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: IDOC is not processed in WF
 
 
So run this by me again - if you have a user decision in between the two
steps, cancel it & restart it from your inbox (purely for purpose of
interrupting the wflow), does that work?
 
Another thing to try: IDOCORDERS.INPUTFOREGROUND it may work (in which case
we've learnt little), or else you will have a lock 'online' and could check
up on it via SM12. (or you could do that if you can trap the lock in debug
mode - as it seems you've done). Anyhows, it may tell you a little more.....
 
Am I correct in assuming the first step is ABAP-based custom stuff?
 
Cheers
Michael
 
-----Original Message-----
From: Christian Behla (QDD) [mailto:Christian.Behla at edd.ericsson.se]
Sent: 11 December 2000 13:33
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: IDOC is not processed in WF
 
 
Michael,
thanks for your ideas.
I am shure now the first step does not create a lock. I can see in SM12 that
inputbackground is creating a lock for a short time after starting to
execute (2nd test), which is correct, then form IDOC_INPUT_OPEN called by
MV45AF0I_IDOC_INPUT_OPEN returns with "Document_foreign_lock", which isn't
correct.
 
After that I created an new single step workflow and started it. The IDOC
was executed as it should: status 53.
 
So you are right: somewhere in my workflow a lock entry is created and this
happens after the first step and only within my workflow.
 
any more ideas ?
 
regards
Chris
 
 
-----Original Message-----
From: Michael Pokraka [mailto:MPokraka at samsungsemi.co.uk]
Sent: Montag, 11. Dezember 2000 12:40
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: IDOC is not processed in WF
 
 
This may be off target but nevertheless:
Check that your first step doesn't perhaps do anything that will make the
IDOC inaccessible for the duration of the current execution. It may be
possible that a lock entry is created but not released whilst the workflow
is executing (i.e. remains into the next step if it's being executed
straight afterwards).
e.g. (2 tests to verify this):
 
 - insert a simple user decision (to 'pause' the W/F).
 - At user dec., cancel (so that it remains in your inbox).
 - Test your object by creating an instance of the IDOC in question, call
INPUTBACKGROUND.
This lot should work. Next test:
 
 - same as above, with user decision
 - after cancelling the decision, go back to inbox and execute it.
If it doesn't execute, so much for that plan.
If it does execute, then the first step possibly creates a lock on it.
 
Another possibility would be to check trans. SM12 for lock entries on the
IDOC, but timing might be a bit tricky.
HTH
Michael
 
 
-----Original Message-----
From: Christian Behla (QDD) [mailto:Christian.Behla at edd.ericsson.se]
Sent: 07 December 2000 12:45
To: SAP-WUG at MITVMA.MIT.EDU
Subject: IDOC is not processed in WF
 
 
Hi workflowers,
 
my 4.6B workflow ist triggered by IDOCORDERS / INPUTERROROCCURED.
After the first step (correcting data in background) i use method
INPUTBACKGROUND.
This returnes without errormessage but the IDOC is not processed and
IDOC-Status is 51: "Idoc ** could not be opened".
When i start the method in the workflow with a delay of 10 min, I still have
the problem.
 
When i test the method in SWUD it works.
In EDI I have no problem processing the IDOC.
 
My idea is that somehow the IDOC is blocked.
 
Thank you in advance for any input you can provide.
 
Christian Behla
 
 
-----------------------------------------------------------------------
 
The information contained in this email may be privileged, confidential
and protected from disclosure. The opinions expressed are those of the
individual and not Samsung Semiconductor Europe Ltd or Samsung
Electromechanics Ltd. Internet communications are not secure and
therefore Samsung Semiconductor Europe Ltd and Samsung
Electromechanics Ltd do not accept legal responsibility for the contents
of this message. If you think you have received this email in error please
notify the sender or mail "admin at samsungsemi.co.uk"  and delete any
copies of the mail.
 
 
-----------------------------------------------------------------------
 
The information contained in this email may be privileged, confidential
and protected from disclosure. The opinions expressed are those of the
individual and not Samsung Semiconductor Europe Ltd or Samsung
Electromechanics Ltd. Internet communications are not secure and
therefore Samsung Semiconductor Europe Ltd and Samsung
Electromechanics Ltd do not accept legal responsibility for the contents
of this message. If you think you have received this email in error please
notify the sender or mail "admin at samsungsemi.co.uk"  and delete any
copies of the mail.