cancel
Showing results for 
Search instead for 
Did you mean: 

SOAMANAGER for PPS CPPR SOA

Former Member
0 Kudos

Hi SRM Experts,

SRM 7 EHP 1

ECC 6 EHP 5

Netweaver PI 7.0 EHP 2

We are trying to setup CPPR scenario for PPS.

Currently we need to setup the following SOA services in ECC & SRM (through SOAMANAGER) -

QueryCodeList

RFQRequestSUITERequest

RFQRequestSUITEAllowedBiddersByIdentifyingElementsQueryResponse

We get the following error on the consumer side -

SRT Framework exception: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:404Connection Failed

We do not have the WS adapter for Netweaver PI 7.0

Please provide pointers on the below -

1. Is Netweaver PI 7.1 required to configure the SOA services or can we configure using 7.0?

2. Is WS adapter mandatory?

Thanks & Regards,

Amish

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Experts,

Any pointers please.

Thanks & Regards,

Amish

former_member22425
Active Participant
0 Kudos

Hello Amish,

Kindly follow the SAP Notes 1263876 & 1268336 to configure the CPPR application and SOA services respectively.

Also regarding the error "SRT Framework exception: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:404Connection Failed" ; kindly check the corresponding SICF path as per the wsdl url in the system and activate that service. Usually this error message comes when the sicf service is not active in the system .

Activate the sicf and try to configure the service again with reference to the wsdl url copied from the consumer.

This should solve the issue here.

Best Regards,

Rahul

Former Member
0 Kudos

Hi Rahul,

Thanks for the reply.

We have already configured as per the OSS numbers mentioned.

Regarding the service in SICF it is already active.

Any other pointers please.

Regards,

Amish

former_member22425
Active Participant
0 Kudos

Hello Amish,

Kindly check for the SOA user credentials and authorizations here used in the service configuration.

The user should exists in the SRM system with type as service user.

Roles to be given here :

/SAPSRM/EMPLOYEE_EHP1

/SAPSRM/OP_PURCHASER_EHP1

/SAPSRM/ST_PURCHASER_EHP1

SAP_BC_WEBSERVICE_CONSUMER

Ensure that profiles are generated properly here and the user is integrated to the SRM org structure.

May be you can delete the binding service created in the srm system , and start configuration for the same from first step to avoid issues.

Best Regards,

Rahul

Former Member
0 Kudos

Thanks Rahul.

Closing the thread.

Regards,

Amish