ALE Workflow Issue

[Swathi_Devireddy]

Hi,
To insert a wait step i used the BO idocmatmas but i dont know the Inbound  IDOC number to do the binding.
Regards,
Swathi

________________________________________
From: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] On Behalf Of kaukabr at yahoo.com [kaukabr at yahoo.com]
Sent: Friday, July 18, 2008 9:49 PM
To: SAP Workflow Users' Group
Subject: Re: ALE Workflow Issue

Insert Wait set in your workflow.
Cheers.
--- Swathi_Devireddy <Swathi_Devireddy at satyam.com>
wrote:

> Hi,
>
> I have a requirement where I need to post matmas
> IDOC from client 110
> to 200 and workflow is running in 200.
>
> I have written code where I am executing BD10 in an
> rfc enabled FM with
> destination 100 and should post to 100.
>
> After this I am sending a mail on the confirmation
> to a user.
>
> This worked fine as in a background method I posted
> the IDOC and sent an
> e-mail.
>
> The problem now is the IDOC is not sent immediately
> but sent with some
> time intervals. But now my e-mail is going even
> before
>
> The idoc is posted to 100.
>
> In the e-mail step I need some details of material
> number etc  and
> details from my initial workflow
>
>
>
> Regards,
>
> Swathi.
>
>
>
>
>
>
>
> DISCLAIMER:
> This email (including any attachments) is intended
> for the sole use of the intended recipient/s and may
> contain material that is CONFIDENTIAL AND PRIVATE
> COMPANY INFORMATION. Any review or reliance by
> others or copying or distribution or forwarding of
> any or all of the contents in this message is
> STRICTLY PROHIBITED. If you are not the intended
> recipient, please contact the sender by email and
> delete all copies; your cooperation in this regard
> is appreciated.
> > _______________________________________________
> 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

DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.