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