reprocessing idocs that are linked to workflows (solution)

Bakker, Paul Paul.Bakker at qr.com.au
Mon May 31 03:01:35 EDT 2004


Hi,
=0D
A while ago I posted the following question:
=0D
        "How do you reprocess an idoc that triggers a workflow?"
=0D
Inexplicably, you cannot do this via BD87, nor via WE19. The error
message is:
=0D
        No function module for input process code xxxx=0D
        Message no. B1 033=0D
=0D
.. which seems to suggest that BD87/WE19 do not recognize that some
idocs are
_not_ handled by function modules.
=0D
We need this facility in the cases where the workflow originally kicked
off by the idoc
terminates, but does not produce the desired result. (because of a
workflow design flaw).
=0D
After a lot of mucking around, I think I have hit upon a solution. I can
trigger a new=0D
workflow to process an idoc using the function module
IDOC_WORKITEM_INBOUND_CREATE.
You just have to plug in the workflow id, the idoc number and the
userid/org unit. For example:
=0D
      CALL FUNCTION 'IDOC_WORKITEM_INBOUND_CREATE'               =0D
           EXPORTING                                             =0D
                pi_task_number   =3D 'WS90000010
                pi_idoc_number   =3D '0000000000300863'
                pi_called_online =3D '' =0D
                pi_org_unit      =3D 'USO002222'         =0D
                succ_show_flag   =3D ''
=0D
I called this via SE37. It's an ugly workaround, but it will do until we
fix the workflow.
=0D
cheers,
Paul
=0D
 
 =0D
 
=0D
 
 
**********************************************************************
This email and any files transmitted with it are confidential and intended=
 solely for the use of the individual or entity to whom they are addressed.=
 If you have received this email in error please notify the system manager=
 of QR.
 
This message has been scanned for the presence of computer viruses. No=
 warranty is given that this message upon its receipt is
virus free and no liability is accepted by the sender in this respect.
 
This email is a message only; does not constitute advice and should not be=
 relied upon as such.
**********************************************************************
 


More information about the SAP-WUG mailing list