SCM To SOACS Calls Getting InvalidSecurity Error (Doc ID 2826167.1)

Last updated on SEPTEMBER 24, 2023

Applies to:

SOA on Marketplace - Version N/A and later
Information in this document applies to any platform.

Goal

While doing the regression/performance testing for Oracle SR "3-27449685121 : Proactive one off" in our UAT environment we observed the inbound calls from SCM to our SOACS environment are creating instances with no data and with a error message "{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}InvalidSecurity"

We had close to 3700 such errors. The service throwing this error and to check in logs are:
OrderStatusNotificationBAS
SalesOrderDS

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

SCM To SOACS Calls Getting InvalidSecurity Error (Doc ID 2826167.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!