cancel
Showing results for 
Search instead for 
Did you mean: 

SES Release Strategy not invoked in Backend from SRM confirmation posting

Former Member
0 Kudos

Hi,

I have configured a SES release strategy based on vendor number in R/3. When a SES is created in R/3 via ML81N the release strategy is invoked as expected. However, when a confirmation is entered in SRM for that vendor, the SES that is created in the backend system is created in accepted status and the release strategy is not invoked.

Can anyone advise how to get this to work the same way as ML81N?

I would expect that the SES would be created in the backend from the confirmation without acceptance and the release procedure to be the same as ML81N.

thanks,

Michelle.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

The SRM confirmation in EBP is the goods receipt(MIGO) and not the service entry sheet entry (ML81N) as we do in Materials management.

As per my understanding there is no provision of service entry sheet entry in SRM 5.0 as of now and SRM 7.0 has this option coming up :

In SRM 7.0 ,

"Supplier-maintained confirmation (service entry sheet) for services performed based on the service items within a purchase order

Confirmation supporting hierarchical structure of service items"

are added.

Look for this information in the thread which speaks about SRM 7.0

which gives the info in slide 11, Delta SRM 7.0, Service procurement -2

Best regards,

Sridhar.