Shopping Cart remains in "Awating Approval" status for Auto Approval WF

[Former Member]

Hi Experts ,

We had activated Auto Approval ( ZERO Approval) for SRM Shopping Cart in SRM 7.0. i.e. activated BC set /SAPSRM/C_SC_600_000_SP04 (Shopping Cart Without Approval)

So When we order shopping Cart it automatically approved immidiatlay . It was working fine from long time.

But suddenly from yesterday , after ordering of Shooping Cart Shopping Cart remains in "Awating Approval" status a nd not creating Follow on document.

I Checked in SWETYPV ..but here these is no any differnce with the client which have no issue.....

Can anyone please suggest me what should be issue and solution on this ?

Thanks

NAP

[robin_janke · Accepted solution]

Also check SM50 to see if there is a process running that hogs all background update channels. If yes, kill it and all approvals will proceed.

Robin

[Former Member · Accepted solution]

Thanks Robin.

I found 2/4 entries in the SM50 in SRM having running ststus.....

25.10.2011

Dynamic List Display 1

-

---

-

---

No.

Ty.

PID

Status

Reasn

Start

Err

Sem

CPU

Time

Report

Cl.

User Names

Action

Table

-

---

1

DIA

2756

Running

Yes

SAPLTHFB

212

XXXX

12

BGD

3156

Running

Yes

29

SAPLBBP_PD

212

XXXX

Sequential Read

BBP_PDVIEW_IAP

0

DIA

4680

Waiting

Yes

2

DIA

4148

Waiting

Yes

3

DIA

4624

Waiting

Yes

4

DIA

4228

Waiting

Yes

5

DIA

768

Waiting

Yes

6

DIA

256

Waiting

Yes

7

DIA

5972

Waiting

Yes

8

DIA

4008

Waiting

Yes

9

DIA

4056

Waiting

Yes

10

UPD

6128

Waiting

Yes

11

ENQ

3300

Waiting

Yes

13

BGD

6056

Waiting

Yes

14

BGD

4788

Waiting

Yes

15

SPO

1448

Waiting

Yes

16

SPO

2388

Waiting

Yes

17

UP2

2000

Waiting

Yes

-

---

but I did not got exactly you meant "there is a process running that hogs all background update channels. If yes, kill it and all approvals will proceed."... .

Can you please suggest me exactly what I need to do......( please see my above reply also !) ?

Thanks

NAP

[robin_janke · Accepted solution]

Hi NAP,

My suggestion was more if the above answers weren't what you were looking for. SM50 is fine, so disregard my post. Setting a new password for WF-BATCH should be the solution.

If it continues to get locked you will have to do the automatic setting up of the workflow RFC in SPRO again (or change it in SM59 - Logical Destination WORKFLOW_LOCAL_<client>). This ensures that the rfc destination has the same password as what is being set in the WF-BATCH SU01 user.

[Former Member · Accepted solution]

Thanks Janke,

But still I am not cleared.....it seems user is not locking contioutly....

Initially I saw below error in SM58

"Password no longer possible- too many failed attempt"

then I unlocked WF-BATCH user and then created Shopping Cart...but still not approved..and gave below error in SM58

"Name or Password is incorrect ( repeat logon)"

Then we reset password as initXYZA for this WF-BATCH........but still issue is same..

Is in all cases, do I need to set this password in the SRM, SM59->Logical Connection->WORKFLOW_LOCAL_212->Logon & Security Tab.......whether it contious gets Locked or Not Locked .....it seems it is not locking now.... ?

Can you please suggest in details...

Thanks in advance

NAP

[Former Member · Accepted solution]

Thanks Janke,

But still I am not cleared.....it seems user is not locking contioutly....

Initially I saw below error in SM58

"Password no longer possible- too many failed attempt"

then I unlocked WF-BATCH user and then created Shopping Cart...but still not approved..and gave below error in SM58

"Name or Password is incorrect ( repeat logon)"

Then we reset password as initXYZA for this WF-BATCH........but still issue is same..

Is in all cases, do I need to set this password in the SRM, SM59->Logical Connection->WORKFLOW_LOCAL_212->Logon & Security Tab.......whether it contious gets Locked or Not Locked .....it seems it is not locking now.... ?

Can you please suggest in details...

Thanks in advance

NAP

[robin_janke · Accepted solution]

Hi,

when you unlock you get 3 attempts to provide the correct password, if you put in the wrong one the

"Name or Password is incorrect ( repeat logon)"

Appears,

after 3 attempts the user is locked:

"Password no longer possible- too many failed attempt"

Change the password in SM59 for the local_workflow_212 so it matches the new password in SU01 for user WF-BATCH.

Regards,

Robin

[Former Member · Accepted solution]

Thanks Robin.

I am checking this ... Basis team unable to go in change mode of this RFC destination.....

....but I wondered to see this RFC destination "Logical Connection->WORKFLOW_LOCAL_212" in SM59, in DEV system....Basis Team not craeted this.......who had created it and what should have the purpose of this ...since in all other client QA....there is no such RFC detination... and there is no such a issue at all ?

Can you/anyone please suggest me on above ?

Thanks

NAP

[robin_janke · Accepted solution]

Hi,

please check the customising in SPRO for the workflow in the relevant systems.

Regards,

Robin

[Former Member · Accepted solution]

Hi,

After you change the password for WF-BATCH in SU01 make sure you also synch it in SWU3 for "Configure RFC Destination" with the same password.

Thanks

Dibya

[Former Member]

yes, in SRM set password for WF-BATCH.

[Former Member]

In SRM system goto SM58 and check for the error message/log.... there must be an issue with WF-BATCH user ID. Check it's credentials. this needs to be proper for auto approval. Is workflow item being generated...? check in BBP_PD. If no, then check user id WF-BATCH and also test RFC connections in SM59

thanks and regards,

Sangmesh Hiremath

[Former Member]

Thank you so much. very useful info.

In SM58, in SRM , I saw below log.

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 20.10.2011 01:44:18 Password logon no longer possible - too many faile

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 20.10.2011 01:46:59 Password logon no longer possible - too many faile

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 20.10.2011 03:42:50 Password logon no longer possible - too many faile

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 20.10.2011 04:52:53 Password logon no longer possible - too many faile

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 20.10.2011 22:31:04 Password logon no longer possible - too many faile

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 21.10.2011 00:59:10 Password logon no longer possible - too many faile

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 21.10.2011 01:01:39 Password logon no longer possible - too many faile

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 23.10.2011 22:20:43 Password logon no longer possible - too many faile

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 24.10.2011 01:10:21 Password logon no longer possible - too many faile

WE-BATCH user in SRM was locked..I locked it and after that I craeted Shopping Cart...and now it is showing below error in SM58....

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 25.10.2011 02:51:52 Name or password is incorrect (repeat logon)

SWF_EVT_HANDLER_START_INTERNAL WORKFLOW_LOCAL_212 25.10.2011 05:33:05 Name or password is incorrect (repeat logon)

I asked Security Team to reset the password..they set XXX password...but where that need to set for user WF-BATCH in SRM ?

Can you please suggest me on it ?

Thanks

NAP

[Former Member]

HI,

Please check if at SWe2 the event linkage Ready_for _release is active. Sometime if you face any error on the time that system is releasing the document this set is deactivated.

Thanks,

Melina

[Former Member]

Hi Melina,

Thanks for reply. I checked this as well, but this is not the issue. The event linkage Ready_for _release is active and same like the QA system which is working fine.

Even I restarted the SRM server, but still not resolved.

one more thibng...this is happeing for all documents ..SC, Confirmation, Invoice in SRM...all are in "Awating Approval" status....although we set Aut approval; for all....

Can you/anyone please suggest what should be the issue suddenly ?

Thanks

NAP