Workflow and BAPI_GOODSMVT_CREATE

[Susan Keohan]

Hi Jerry, Phil,
 
Thank you both for your helpful messages.  As it turns out, it was
incorrect code in the FM that calls the BAPI.   :-[
 
I greatly appreciate your help,
Sue
 
Martinek, Jerry wrote:
 
>Hi Susan, when all else fails,.......check the ABAP. All of the items that
>have been mentioned to date seem to indicate that it's not the obvious.
>
>Have you checked OSS for existing notes or have you thought about creating a
>new one?
>
>Have you checked the SAP system log and dumps?
>
>Are you sure that your current version of MB01 (SAPMM07M ) doesn't have any
>active field exits, user exits or etc.. that could be interfering with your
>current processing goal? If it works with any of the other movement codes
>but it doesn't work with '01', then check the ABAP code.
>
>If you haven't altered WF_BATCH's authorizations, I doubt that it's an
>authorization problem since SAP_ALL can do almost anything.
>
>Have you tried ST01 for WF_BATCH?
>
>Regards,
>Jerry
>                -----Original Message-----
>                From:   Susan Keohan [mailto:skeohan at mit.edu]
>                Sent:   Wednesday, October 16, 2002 1:07 PM
>                To:     SAP-WUG at MITVMA.MIT.EDU
>                Subject:        Re: Workflow and BAPI_GOODSMVT_CREATE
>
>                Hi Michael,
>
>                Thanks for the hints, but I had already tried those.  Most
>frustrating
>                is the fact that I can have a workflow task which runs this
>same BAPI,
>                only using a different Goods Movement Code.  This GM code
>tells the BAPI
>                to process as if  it's MB01.
>
>                I appreciate having a new transaction to add to my
>repertoire (SM13).
>                 Thanks!
>                Sue
>
>                Pokraka, Michael wrote:
>
>                >Hmmm, I haven't quite thought about bagging groceries, but
>becoming a barman
>                >has entered my thoughts once or twice :-)
>                >Anyway, I don't know much about that particular BAPI, but
>from what you
>                >describe it would be worthwhile to check the database
>updates (SM13) and RFC
>                >calls (SM58). More likely option 1, as a late stage update
>failure can cause
>                >the scenario where a document no. is assigned and returned,
>but sometime
>                >during the update something else goes wrong and the whole
>transaction is
>                >rolled back.
>                >
>                >HTH
>                >Michael
>                >
>                >-----Original Message-----
>                >From: Susan Keohan [mailto:skeohan at mit.edu]
>                >Sent: 16 October 2002 17:04
>                >To: SAP-WUG at MITVMA.MIT.EDU
>                >Subject: Workflow and BAPI_GOODSMVT_CREATE
>                >
>                >
>                >Greetings Workflow-ers,
>                >
>                >I am on a 4.6c environment.  I have written a FM to call
>                >BAPI_GOODSMVT_CREATE, using Goods Movement Code 01.  This
>FM works fine.
>                > I have incorporated this FM into an object method (object
>ZBUS100106,
>                >an  extension of BUS1001006).  I can test this method and
>it works fine.
>                > I have created a standard task to call this method and
>incorporated it
>                >into a single step workflow.  It seems to work fine, that
>is, a goods
>                >movement document is returned to the task container, but
>the document
>                >does not actually exist.  The goods movement has not
>actually been
>                >completed.
>                >
>                >In my FM, I am doing a BAPI_TRANSACTION_COMMIT.
>                >
>                >I have tested and tested, and the bindings are, believe it
>or not, correct.
>                >
>                >I have written a report to run the function module in the
>background,
>                >and it can create the goods movement document.
>                >
>                >I can also call this BAPI to do a different Goods Movement
>Code (04) and
>                >the workflow and the task all work perfectly.
>                >
>                >I am stuck with thinking
>                >a) That GM Code 01 is not supposed to work from within a
>workflow task
>                >b) That the database commit is not happening, even though I
>am calling
>                >the BAPI_TRANSACTION_COMMIT
>                >c) That there is something wrong with the WF-BATCH id, even
>though it
>                >can complete other tasks normally, including other calls to
>this BAPI
>                >or
>                >d) I should hang it up and go bag groceries for a living
>                >
>                >Has anyone had any experience, positive or negative, with
>using this
>                >BAPI from a workflow task, for a Goods Movement code 01 ?
>                >
>                >Thanks in advance,
>                >Sue
>                >
>
>>---------------------------------------------------------------------------
>>
>---
>                >This e-mail is intended for the use of the addressee(s)
>only and may contain privileged, confidential, or proprietary information
>that is exempt from disclosure under law.  If you have received this message
>in error, please inform us promptly by reply e-mail, then delete the e-mail
>and destroy any printed copy.   Thank you.
>                >
>
>>===========================================================================
>>
>===
>                >
>