cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Status mismatch for GOA approval

Former Member
0 Likes
534

Hello All,

Landscape SRM 4.0 connected with multiple backends R/3 4.7

Workflow WS90100022 for GOA BUS2000113.

In BBP_PD status is

HEADER I1015 Awaiting Approval

In Document display 'Approval Preview', I can see workflow started -> Result:Approved .

If I check the workitem under SWIA, I can see status 'completed'.

What could be the reason of this mismatch?

Pl give me pointers.

BR

Dinesh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Likes

Hello Dinesh

in bbp_pd BUS2000113 object id number

service objects

workflow overview

who is the last agent?

-


i dont see any this workflow WS90100022

-


BUS2000113 (Contract)

WS14000086 (Automatic approval)

WS14000088 (One-step approval)

WS10400022 (Contract alert)

WS14000148 (n-step approval

---

it is awkward situation .is it change version in GOA awaiting for approval?

---

however awaiting for approval means , we require to approve by some one .

did you try back end method swo1 - BUS2000113 - latest version change GOA guid- approved.

Muthu

Former Member
0 Likes

Thanks Muthu.

I am getting " Buffer table not update" for SWO1.

Any further input?

BR

Dinesh

Former Member
0 Likes

Hi Dinesh

There might be a data error in the GOA

-

do you have the same data in other environments?

what i used to

to trigger again approval

for eg:- ERROR IN PROCESS - GOA technical status

then i change some comments in the docuemnts . new version creates so i get approver eaily . ie. wf triggered.

then swo1 or appropriate approver asked him to approve .afater wards it becomes RELEASED>

Muthu

Former Member
0 Likes

It is very difficult to recreate this scenario

WF mess up with GOA status -some times.

It could be due to change version issue.

change version causes damage to the GOA.

I could not replicate this.

By misatke system creates a extra change version when MANGER approve the chage version GOA .i could see the log history new CHANGE version created by the APPROVER. it is very strange not by BUYER.

Muthu

Answers (0)