Backgorund job that generated a workflow itemwith- the problem is solved :-)

JANSSENS Koenraad Koenraad.JANSSENS at swift.com
Mon Oct 11 07:12:06 EDT 2010


Indeed, documentation is generally the lowest of the priorities.
Anyway.. wouldn't it be better to add a step at the end of ANOTHER_BACKGROUND_JOB to launch MY_BACKGROUND_JOB if it is dependent of it?
You are never certain how long a job might run .....

Best Regards

K

>-----Original Message-----
>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Pokraka
>Sent: Monday, October 11, 2010 12:55 PM
>To: SAP Workflow Users' Group
>Subject: Re: Backgorund job that generated a workflow itemwith- the problem is solved :-)
>
>I know what you mean about external consultants and documentation, they
>keep me in business :-)
>
>However I would point out that it's not always their fault. On more than
>one occasion I have suggested doco towards the end of my engagement but
>been specifically asked to add more functionality or do other bits of
>work.
>
>Consultancies and projects have budgets that overrun and it's usually the
>doco that suffers.
>
>Cheers,
>Mike
>
>On Fri, October 8, 2010 8:53 am, Mintchev Alexander, Mag. wrote:
>>
>>  Dear Paul,
>>  Dear Keith,
>>
>> Dear Jimmy!
>>
>> Thank all of you for the valuable suggestions and help. I was able to
>> solve the problem, following in the last step the advice of Paul to search
>> for the where-used-list of other function modules that start a workflow -
>> namely in my case- SWW_WI_START.
>> Then based on the program name, that starts the worfkow, the basis team
>> determined the back ground job name that executed the program in the
>> night- let us call it - MY_BACKGROUND_JOB
>> It finally turned out, that MY_BACKGROUND_JOB was rescheduled very closely
>> after another background job- ANOTHER_BACKGROUND_JOB, so that actually the
>> result of MY_BACKGROUND_JOB were therefore jeopardised.
>>
>> The solution was simply to reschedule MY_BACKGROUND_JOB for a later start.
>>
>> @ Keith: Of course, it would be much easier to aks the author of the
>> workflow- but he is an external consultant, who is not more at the company
>> (and has not docuemnted his work) :-)))
>>
>>
>> Thank all of you and have a nice weekend!
>>
>>
>> Kind regards: Alexander
>>
>>
>> -----Urspr¨¹ngliche Nachricht-----
>> Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag
>> von Paul.Bakker at osr.treasury.qld.gov.au
>> Gesendet: Donnerstag, 07. Oktober 2010 01:08
>> An: SAP Workflow Users' Group
>> Betreff: Re: Backgorund job that generated a workflow itemwith
>> aparticularuser-how can I determine the job's name?
>>
>> Hey Alex,
>>
>> (1) There are other ways of starting workflows directly, besides
>> SAP_WAPI_START_WORKFLOW Try searching for function modules with the
>> pattern SW*START*. For example, SWW_WI_START.
>> But are you sure this workflow was started directly?
>>
>> (2) RFKK_MASS_ACT_SINGLE_JOBis a generic program for executing mass
>> activities in the background (such as clearing, dunning etc) So it will
>> always call another program, which then triggers the workflow.
>> (if applicable, have a look in transaction FKJOXTR to see which mass
>> activities are scheduled at 2am).
>>
>> (3) If you look at what your workflow does, and what data it uses, you can
>> probably work out what kind of mass activity started it (e.g., clearing,
>> correspondence,)
>>
>> (4) Finally, if this is a custom workflow being triggered from a SAP
>> program, you should probably look through BADis, enhancements, and perhaps
>> even FI-CA events (if applicable - see transaction FQEVENTS)
>>
>> hope this helps
>> Paul
>>
>>
>>
>>
>>
>>              "Mintchev
>>              Alexander, Mag."
>>              <Alexander.Mintch                                          To
>>              ev at biac.at>               "SAP Workflow Users' Group"
>>              Sent by:                  <sap-wug at mit.edu>
>>              sap-wug-bounces at m                                          cc
>>              it.edu
>>                                                                    Subject
>>                                        Backgorund job that generated a
>>              07/10/2010 02:28          workflow item with
>>              AM                        aparticularuser-how can I determine
>>                                        the job's name?
>>
>>              Please respond to
>>                "SAP Workflow
>>                Users' Group"
>>              <sap-wug at mit.edu>
>>
>>
>>
>>
>>
>>
>> Hello Jimmy!
>> Hello Keith!
>>
>> Thank both of you for the good advices.
>>
>> I ve tried the Jimmy's advice - namely to search for the where used list
>> of the fucntion module SAP_WAPI_START_WORKFLOW, but I found only results
>> from standard SAP programs or classes. (See the attached file
>> SAP_WAPI_START_WORKFLOW-where-used-list.HTM)
>>
>> I have meanwhile noticed that the workflow item I am interested in has
>> been created on 2 October 2010 at 02:50:08 by the user UC4BASIS, as shown
>> below:
>>
>> (Embedded image moved to file: pic32119.gif)
>>
>> As Keith Gardiner suggested, I have sought for all background jobs active
>> at the time my work item has been created ( using the transaction SM37),
>> and found out only 10 relevant background jobs:
>>
>> (Embedded image moved to file: pic20577.gif)
>>
>>
>> All these backgorund jobs actually execute one and the same program -
>> RFKK_MASS_ACT_SINGLE_JOB  - using different variants.  The stupid thing is
>> that the program RFKK_MASS_ACT_SINGLE_JOB is not presented in the attached
>> file SAP_WAPI_START_WORKFLOW-where-used-list.HTM, which means, that it
>> does not direclty start my workflow. Or am I wrong?
>>
>> Do you have any ideas how to proceed?
>>
>>
>> Thank you!
>>
>>
>> Kind regards: Alexander
>>
>>
>> Von: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] Im Auftrag
>> von Jimmy Sun
>> Gesendet: Mittwoch, 06. Oktober 2010 14:42
>> An: SAP Workflow Users' Group
>> Betreff: Re: Backgorund job that generated a workflow item with
>> aparticularuser-how can I determine the job's name?
>>
>> Alexander,
>> In you case, I'd suggest you do a where used search of function  module
>> SAP_WAPI_START_WORKFLOW. and hope a Z* report will come up. If so check if
>> the Z* report is scheduled in any JOB.
>>
>> Hope this helps.
>>
>> Jimmy
>>
>> On 10/6/10, Mintchev Alexander, Mag. <Alexander.Mintchev at biac.at> wrote:
>>   Hello Keith!
>>
>>   Thank you very much for your prompt and relevant reply.
>>   I already talked to your BASIS team - it is difficult for them to locate
>>   the right background job, cause we have many such jobs started by the
>>   same user UC4BASIS.
>>   You are right -  we have many "bespoke" FS-CM workflows that are
>>   triggered by BRF events.
>>
>>
>>   However, the particular workflow I am concerned in is not triggered by
>> an
>>   event (see the attached pictire). How can I find out which program
>> starts
>>   it? Poinitng on the "Workflow Started" step from its SWDD definition
>> and
>>   then clicking on the "Basic data" button just delivers me an emtpy
>> "Start
>>   events" tab,  an empty "Start forms" tab, everything (apart from
>>   tehcnical information tab and abbreviation) is empty.
>>
>>   Thank you very much once again!
>>
>>   Kind regards: Alexander
>>
>>
>>
>>   Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag
>>   von Gardiner,Keith (Insurance & Investor Services)
>>   Gesendet: Mittwoch, 06. Oktober 2010 12:39
>>   An: SAP Workflow Users' Group
>>   Betreff: RE: Backgorund job that generated a workflow item with a
>>   particularuser-how can I determine the job's name?
>>
>>
>>
>>   Hi Alexander,
>>
>>
>>
>>
>>
>>   If you look at the workflow definition WS90000049, you should be able to
>>   find the event that started the workflow. This may have been created
>> from
>>   BRF or from FM¡¯s SAP_WAPI_CREATE_EVENT or less likely
>>   SWW_WI_CREATE_VIA_EVENT.
>>
>>
>>
>>
>>
>>   As the workflow seems to be bespoke, you could look through the BRF
>>   actions to find a bespoke BRF Action that starts this workflow or if
>>   started by program, then look in bespoke programs for the above FM¡¯s
>> and
>>   see if you can find the one that uses this event.
>>
>>
>>
>>
>>
>>   Another alternative is to look at jobs in SM37 for user UC4BASIS if this
>>   is a background job, and see if they set the workflow going. Or just
>>   speak to your Basis team to see what user UC4BASIS is used for.
>>
>>
>>
>>
>>
>>   Hope this helps.
>>
>>
>>   Regards,
>>
>>
>>   ________________________________________________
>>
>>   Keith Gardiner
>>   P please don't print this e-mail unless you really need to.
>>
>>
>>
>>
>>
>>   From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
>>   Of Mintchev Alexander, Mag.
>>   Sent: 06 October 2010 11:03
>>   To: SAP Workflow Users' Group
>>   Subject: Backgorund job that generated a workflow item with a particular
>>   user-how can I determine the job's name?
>>
>>
>>
>>
>>
>>
>>
>>
>>   Dear SAP WUG Users!
>>
>>
>>   I am working as a workflow specialist in SAP FS-CM and I need your
>> advice
>>   in the following topic:
>>
>>
>>   How can I determine the job name of a programm that generated a workflow
>>   item out of the workflow pattern WS90000049 with the username UC4BASIS?
>>
>>
>>   Some hints I know about the job:
>>
>>   System / Mandt
>>   IAP (120)
>>   Claim:
>>   2802066859
>>
>>   The job has created a workflow item with ID
>>   4072344
>>   The job that created the workflow item on / at
>>    20101002,005,008.3792930
>>
>>   The job that created the workflow item with the text
>>   "Open items for claim"
>>
>>   The job that created the workflow item for the user
>>   ATDREU_M
>>
>>   Key address object
>>   USR30000000000065
>>
>>   Call Back Funtion module:
>>    SWP_CALLBACK_WI_DONE
>>
>>
>>
>>
>>
>>   (Embedded image moved to file: pic10737.gif)PBrush
>>
>>
>>
>>
>>
>>   Thank you very much!
>>
>>
>>
>>
>>
>>   Kind regards: Alexander Mintchev
>>   BIAC
>>   Vienna Insurance Group
>>
>>
>>   Obere Doanustrasse 63
>>   1020 Vienna
>>   Austria
>>
>>
>>
>>   This email has been scanned for all viruses by the MessageLabs SkyScan
>>   service.
>>
>>
>>
>>   This email and any attachment to it are confidential. Unless you are the
>>   intended recipient, you may not use, copy or disclose either the message
>>   or any information contained in the message. If you are not the intended
>>   recipient, you should delete this email and notify the sender
>>   immediately.
>>
>>   Any views or opinions expressed in this email are those of the sender
>>   only, unless otherwise stated. All copyright in any Capita material in
>>   this email is reserved.
>>
>>   All emails, incoming and outgoing, may be recorded by Capita and
>>   monitored for legitimate business purposes.
>>
>>   Capita exclude all liability for any loss or damage arising or resulting
>>   from the receipt, use or transmission of this email to the fullest
>> extent
>>   permitted by law.
>>
>>   _______________________________________________
>>   SAP-WUG mailing list
>>   SAP-WUG at mit.edu
>>   http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>>
>>
>>
>> --
>> ¡¸Money is gone, nothing is gone.£¨Ê§È¥Á˽ðåX£¬>]ÓÐʧȥʲüN£©£»
>>     Hope is gone, everything is gone.£¨Ê§È¥ÁËÏ£Íû£¬¾ÍʧȥÁËÈ«²¿£©¡£¡¹
>> [attachment "SAP_WAPI_START_WORKFLOW-where-used-list.HTM" deleted by Paul
>> Bakker/BNE/QOSR/QTreasury] _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>**********************************************************************************************************************
>********************************
>>
>> Only an individual or entity who is intended to be a recipient of this
>> e-mail may access or use the information contained in this e-mail or any
>> of its attachments.  Opinions contained in this e-mail or any of its
>> attachments do not necessarily reflect the opinions of Queensland
>> Treasury.
>>
>> The contents of this e-mail and any attachments are confidential and may
>> be legally privileged and the subject of copyright.  If you have received
>> this e-mail in error, please notify Queensland Treasury immediately and
>> erase all copies of the e-mail and the attachments.  Queensland Treasury
>> uses virus scanning software.  However, it is not liable for viruses
>> present in this e-mail or in any attachment.
>>
>>
>**********************************************************************************************************************
>********************************
>>
>>
>> _______________________________________________
>> 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




More information about the SAP-WUG mailing list