cancel
Showing results for 
Search instead for 
Did you mean: 

Fiori Approve PO: Release strategy getting deleted

former_member193808
Active Contributor
0 Kudos

Hi Experts,

We have an issue with Approve PO Apps.

The release strategy is getting deleted while approving at the final level.

i.e, if there are 4 levels, Fiori app works fine with all 3 levels. At 4th (final) level, app shows "Purchase order is approved" and clears from fiori list.

When go back and check in ECC backend, the release strategy is missing. This is getting deleted.

The functionality in backend works proper without any issue. The issue is only when final release is done through Fiori. all the previous levels works fine with Fiori app.

In case of Approve PR, this issue is not there. After the final level, PR release strategy remains.

Can anybody help?

Screenshot change document after final PO release (from fiori) is as below:

the release strategy has gone blank here.

Thanks,

Prem

Accepted Solutions (0)

Answers (2)

Answers (2)

sanchal
Explorer
0 Kudos

Hello Prem,

Can u please provide more details of your business case, if you have customized standard PO Fiori app. Are you changing any input before approving PO?

Regards,

Sachal J.

former_member193808
Active Contributor
0 Kudos

Dear Sachal,

We are using standard features only. There's no BadI customizations done on Fiori PO app.

We are getting this error only in case of final approval. the same works fine with ecc backend

Thanks,

Prem

former_member193808
Active Contributor
0 Kudos

Could you please help Masayuki Sekihara

masa_139
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Prem,

You can set external break points in the approve method and find the root cause.

Probably you use custom workflow and custom task.

Regards, Masa

SAP Customer Experience Group - CEG

former_member193808
Active Contributor
0 Kudos

Dear Masayuki,

We did the debug and found that there is no customization involved in process.

If we do a final release from backend system (without fiori), the below happens:

release status updates with one more level (X added), indicator B to R (Released) and value from 03 to 05. The Tcode is ME29N. This is as shown below:

When we do the same from Fiori, it doesn't trigger ME29N T-code.

The relesae status becoming blank, document status changes from 03 to 02, Indicator changes from B to blank.

Are we missing any sap note? Apart from this, there's no customization.

Thanks,

Prem

masa_139
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Prem,

What is the workflow template ID and approve task ID?

Regards, Masa

SAP Customer Experience Group - CEG

former_member193808
Active Contributor
0 Kudos

Dear Masayuki,

The workflow ID is WS99900009 and Task IDs are TS20000168(Release of purchase order effected), TS20000166 ( Release of purchase order), TS20000167(Release of purchase order cancelled)

Thanks,

Prem

former_member193808
Active Contributor
0 Kudos

Dear Masayuki,

We have tried with workflow ID WS20000075 as well. The other workflow was a copy of original WS20000075, which we removed now.

Task IDs are as mentioned above.

Thanks,

Prem

masa_139
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Prem,

If you get same issue with SAP standard workflow template, please create an incident.

I think MM side issue.

Regards, Masa

SAP Customer Experience Group - CEG

former_member193808
Active Contributor
0 Kudos

Hi,

The issue is resolved.

We have a user exit in which T-code name check were set. As Fiori doesn't have T-code it was skipping the exit. The issue is fixed by modifying the exit program.

Thanks,

Prem