I've only been working with soap webservices a few months, but In my experience you have to add these manually, the system doesn't come with predefined SOAP Webservices, unless those are included in a SEED folder or something like that, which I have not used. 

There are two types of webservices that can be added, object based web services which key off existing X3 Object/Window Definitions which will pull in all the necessary fields and apply the same business logic when interacting with the API.  As I have been warned, you have to be careful though as not all objects can be used with webservices (you'll have to find that out the hard way with trial and error, as I have not found any documentation on this). The other options is sub program web services where you have to write a script/subprogram to interact with X3 data, more complex and does not follow the same business logic unless you build that in the script. 

I've only been working with soap webservices a few months, but In my experience you have to add these manually, the system doesn't come with predefined SOAP Webservices, unless those are included in a SEED folder or something like that, which I have not used. 

There are two types of webservices that can be added, object based web services which key off existing X3 Object/Window Definitions which will pull in all the necessary fields and apply the same business logic when interacting with the API.  As I have been warned, you have to be careful though as not all objects can be used with webservices (you'll have to find that out the hard way with trial and error, as I have not found any documentation on this). The other options is sub program web services where you have to write a script/subprogram to interact with X3 data, more complex and does not follow the same business logic unless you build that in the script. 

Hello Daniel, thanks for the reply.  Actually, I have added object scripts for BPC, ITM, and SOH.  When testing in Classic SOAP Web services, they all return a similar error.  For example, if I invoke getDescription or query on BPC, I get the error "X3 subprogram (AWEB:RECUPHDAT) that reads web services [BPC] timestamp returned the status [Unknown web service (0)] and timestamp []."

Did you click the publication button after saving the webservice? 

I used the Global publication function each time I made a change.  I just went in and used Publication on each, but still get the same error messages.

If you are a Sage partner, please visit the Sage University (https://sageu.com/) and take the Integration Developer course.

Maybe show the Setup > web service setup used, the web service pool name set at Administration > Classic SOAP pools configuration, and the Invoke parameter used?

Maybe the SOAP pool is not turned on yet? If not, check the web service SOAP pool starter's user's web service access is granted at Setup > Users.

Hello CHUNHENG, thanks for your reply.

Maybe show the Setup > web service setup used

the web service pool name set at Administration > Classic SOAP pools configuration

the Invoke parameter used

Maybe the SOAP pool is not turned on yet?
I believe the SOAP pool is turned on, and it should be evident in the pool screenshot above.

Check your SOAP pool configuration's endpoint.

Each pool for each endpoint (except first one; that one please save for GraphQL and always set to production endpoint).

1.

2.

Check your SOAP pool configuration's endpoint.
I believe the endpoint is configured properly.  "FNPILOT01" which is our test folder.

Each pool for each endpoint (except first one; that one please save for GraphQL and always set to production endpoint).
We only have one pool setup, for our test folder.  We have yet to install, configure, or test GraphQL.

Regarding your screenshots...
1- Appears to show you invoking getDescription using a good pool, but an unconfigured script.  This results in an error.
2 - You setup and publish a script for BPC, then successfully invoke getDescription.
I believe my pool and scripts are setup correctly, but it's clear they may not be.