All Workflows going into Error Status

Mike Pokraka wug at workflowconnections.com
Fri Dec 27 11:55:46 EST 2013


SGEN - usually Basis would run this after a major patch or upgrade.

Regards,
Mike

On Mon, December 23, 2013 11:01 pm, Lalitha Sankaran wrote:
> Hi Rick,
>
> If it happened to one or 2 objects, I understand, but for all objects ?
> Could it be due to the SP ? and shd we try to generate all the
> business objects using a universal program, or some tcode to avoid
> this issue ?
>
> Thank you
> Lalitha
>
> On 12/23/13, Rick Bakker <rbakker at gmail.com> wrote:
>> Hello,
>>
>> It could be that a transport changed a piece of shared code. When the
>> BOR
>> object was next accessed, it was regenerated.
>>
>> Regards
>> Rick Bakker
>>
>> On Monday, December 23, 2013, Lalitha Sankaran wrote:
>>
>>> Hi,
>>>
>>> The issue is resolved, after a few Business objects were regenerated.
>>> But we are seeing that most of the Business objects were regenerated
>>> by different user ID's.
>>> And these user ID's do not even have access to SWO1, so any idea why
>>> we have different ID's showing up as the last user ID to have
>>> generated the business object ?
>>>
>>> Any input would help.
>>>
>>> Thank you
>>> Lalitha
>>>
>>> On 12/19/13, Lalitha Sankaran <lalisan at gmail.com> wrote:
>>> > Hi,
>>> >
>>> > SAP came back and said that the ADDRESS Object was inconsistent and
>>> > they have regenerated it in our system (though I did this yesterday
>>> > and that did'nt help ). I tested by restarting one leave request WF
>>> > and it seemed to go thru, So have scheduled a job for the program
>>> > RSWP_RESTART_WORKFLOWS_GRID to restart any WF in error. Will update
>>> if
>>> > it works.
>>> >
>>> > Thanks
>>> > Lalitha
>>> >
>>> >
>>> > On 12/18/13, Goudham Vel <goudhamvel.88 at gmail.com> wrote:
>>> >> Hi lalitha,
>>> >> Check for agent assignment in basic data of workflow and send mail
>>> >> step.
>>> >> Execute swo2 once in prd sys...
>>> >>
>>> >> Regards
>>> >> Goudham
>>> >> On Dec 19, 2013 6:07 AM, "Lalitha Sankaran" <lalisan at gmail.com>
>>> wrote:
>>> >>
>>> >>> Hi Rick,
>>> >>>
>>> >>> It has SAP_ALL and SAP_NEW in both the systems.
>>> >>>
>>> >>> The WF that is failing in Production is working fine in QA system.
>>> >>>
>>> >>> Thanks
>>> >>> Lalitha
>>> >>>
>>> >>> On 12/18/13, Rick Bakker <rbakker at gmail.com> wrote:
>>> >>> > Hi Lalitha,
>>> >>> >
>>> >>> > I would compare WF-BATCH between Production and QA. Does it have
>>> >>> > SAP_ALL
>>> >>> > and SAP_NEW?
>>> >>> >
>>> >>> > regards
>>> >>> > Rick Bakker
>>> >>> >
>>> >>> >
>>> >>> > On Thu, Dec 19, 2013 at 10:50 AM, Lalitha Sankaran
>>> >>> > <lalisan at gmail.com>wrote:
>>> >>> >
>>> >>> >> Hi Rick,
>>> >>> >>
>>> >>> >> This is happening to all tasks , not just email tasks. That was
>>> >>> >> just
>>> >>> >> one example. Its happening for all WF's, which is complicating
>>> it
>>> >>> >> further.
>>> >>> >>
>>> >>> >> SWU3 looks fine, SWETYPV looks fine.
>>> >>> >>
>>> >>> >> Am having it tested in the QA system.
>>> >>> >>
>>> >>> >> Thank you
>>> >>> >> Lalitha
>>> >>> >>
>>> >>> >> On 12/18/13, Rick Bakker <rbakker at gmail.com> wrote:
>>> >>> >> > Hi Lalitha,
>>> >>> >> >
>>> >>> >> > It depends what version you're on. If it's working fine in QA
>>> >>> >> > then
>>> >>> >> > I
>>> >>> >> would
>>> >>> >> > leave it - but that depends on how well the SP was tested!
>>> >>> >> >
>>> >>> >> > You should check the workflow log for more details of that
>>> error
>>> >>> >> > message
>>> >>> >> > for the mail. Does it happen to every email from Workflow?
>>> >>> >> > Are emails sent to users or Positions or both? Does WF-BATCH
>>> >>> >> > have
>>> >>> >> > an
>>> >>> >> email
>>> >>> >> > address?
>>> >>> >> >
>>> >>> >> > regards
>>> >>> >> > Rick Bakker
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > On Thu, Dec 19, 2013 at 10:18 AM, Lalitha Sankaran
>>> >>> >> > <lalisan at gmail.com>wrote:
>>> >>> >> >
>>> >>> >> >> Hi Rick,
>>> >>> >> >>
>>> >>> >> >> I see that one of the Business Object has the Interface
>>> IFGOSASERV
>>> >>> >> >> ,
>>> >>> >> >> shd I replace this with IFGOSXSERV ?
>>> >>> >> >>
>>> >>> >> >> I can try that, but we never had any issues in the dev or QA
>>> >>> >> >> system,
>>> >>> >> >> but will have them test again.
>>> >>> >> >>
>>> >>> >> >> Also the email is going thru from SAP, I sent myself a test
>>> >>> >> >> email
>>> >>> >> >> and
>>> >>> >> >> received it too...
>>> >>>
>>
> _______________________________________________
> 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