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

No approvers displayed in the Approval Preview

Former Member
0 Likes
1,100

Hello,

We implemented the BAdI for n-step approval workflow for bid invitation. Before the document is fully approved, everything is working fine. The approvers were able to receive the workitem and approve the document. The approval preview also displays properly the approval step.

If the bid invitation is already fully approved, the approval preview is empty and displays the message "Approval step without ad-hoc capability.No preview possible" but did not do Add Approver/Reviewer.

I have debugged the n-step BAdI, but the APPROVAL_TABLE is properly filled.

Also in BBP_PD, when the document is fully approved, the workflow table is displaying User = X and node Description = Added Approval, but when the document is still in Awaiting Approval or Held status, it displays the correct approvers properly.

We are on SRM 5.0 , SP13.

Regards,

Kezia

Accepted Solutions (1)

Accepted Solutions (1)

SE12
Advisor
Advisor
0 Likes

Hello Kezia,

This error is very often caused by the information returned from the badi to determine the approvers.

Please check the workflow log, look at the container for the workflow at header level, if the approverlist is set to USX, then this means that there is a problem with what is returned from the badi, when the document is approved.

If you want to debug the approval, you can logon via the gui.

Set a breakpoint in your badi and then call transaction

bbp_bgrd_approval. Enter the following details:

User: approver e.g. manager1

Action: 0

Workitem ID: Get this from the workflow log SWI6/SWI1

I hope that this helps,

Kind regards,

Siobhan

Former Member
0 Likes

Hello,

We are facing the same problem, I checked the BAdi and and Made a small change in debugging but the details of the user update but Status and In process and Processed details are missing how to find them??

Answers (2)

Answers (2)

Former Member
0 Likes

An approver of the document lacks authorization in a function module used in the BAdI implementation. That's why the list of approvers in the approval preview is being cleared up after the approval.

Many thanks for your help.

Former Member
0 Likes

Hi Kezia,

Can you tell me what this authorisation was please as we have the same issue?

Thanks a lot,

Nick

former_member544585
Contributor
0 Likes

Hi Kezia,

Check your workflow for consistency. In transaction SWUD, enter your workflow, select Test Environment (flag "Including parts"), select Consistency check for components (flag "Including subworkflows").

Repeat the same consistency check in SWUD for all the sub-workflows of your workflow - one by one.

If SWUD shows error messages, you may need to repair your workflow (or sub-workflows).

Cheers,

Serguei

Former Member
0 Likes

Hi Serguei,

I have checked the workflow in SWUD, all tasks and workflow templates in green (OK) except for the sub-workflow n-step in yellow (warning), I believe that this is not a problem.

We only encounter this in production, and we do not have transports that are related to workflow.

Thank you,

Kezia

former_member544585
Contributor
0 Likes

OK, so you only have this problem in PROD, all other systems (DEV, QA) are fine... I assume you checked your BAdI transports in PROD as well... If all OK, that leads me to think there's nothing wrong with your custom code or transports.

SRM 5.0 is notorious for these kinds of issues where workflow templates work in one environment, but are erroneous in another (most times this is due to inactive status). That is why I asked you to check the workflow for consistency in SWUD.

From your answer, I did not understand whether you'd checked all the subworkflows separately in SWUD (not as part of the main workflow check). If you didn't do that, find all the subworkflows (and the subworkflows of the subworkflows where applicable) in SWDD by stepping through the main workflow, and then run the SWUD check on each of them separately.

Also, please check the Review workflow WS10000265. This particular workflow may not show in SWDD as a subworkflow, but actually is part of the process. If it's broken, you may encounter issues like you're describing.

Cheers,

Serguei