After Upgrade to SRM 7.0 EPH1 - Custom Process control workflow not trigger

[Former Member]

Hi SRM Experts,

Good morning.

In SRM 7.0, We have huge number of custom Badi's for SC, PO and Inv. Those are working fine in production system.

We are planning for upgrade and we made a system copy of all the SRM 7.0 objects and did the Upgrade of SRM 7.0 EPH1 in a new development system.

After the upgrade, SC custom workflows are not working. But I try to change with the SAP standard Badi's in the configuration and those are working fine. It's not working only for custom process level Badi's.

While we debug the custom process level workflow Badi's, we found that the SAP standard program not populating any value in MO_CURRENT_LEVEL and MO_FIRST_LEVEL in /SAPSRM/CL_WF_PROC and those entries are blank.

We're facing this issue for almost 2 weeks.

Please give your thoughts.

Thanks in Advance,

Best Regards,

Selvamuithu Natarajan

[alejandro_jimenez2 · Accepted solution]

Hi SELVAMUTHU NATARAJAN

really i donnot understand you.

do you have problem with the work flow or with the BADI?

if your problem es BADI , please check this sapnote: 1521903 regenerate all inconsistent BADI´s the runtime to this solution usually is slow { a couple to hours.}

now . if your problem is about work flow, remeber that, SRM have a diferente behavior about Workflow, you need chose the framework, to default, after the upgrade SRM7.0, the system proposefor default frame work for procces workflow, you need change this in SPRO>> SRM SERVER >>> Cross aplications setting >>> workflow >>> select workflow frame workflow.

Here you select the bussiness object ( for example bus2200, bus 2121) , execute with the check box (simulate), select the radio buttom APLICATION WORKFLOW and see the result.

After you execute the transaction , but this time, without the check box and the radio buttom APLICATION CONTROLED WORKFLOW.

with thIS SETTING you select the framework clasic, and your Workflows have a behavior like the version old.

regards-

[Former Member · Accepted solution]

Hi Alejandro,

Thanks for your reply.

SAP released a OSS note yesterday and that solves our issue. The OSS not no: 1613263

Thanks & Regards,

Selva