This error message due to security token is missing in the SOAP Header section. To solve this issue you have to enter the security token as follows:

1- Open SOAP project

2- put the following security token right after SOAP Header section of the request body

<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" mustUnderstand="1">
<wsse:UsernameToken>
<wsse:Username>YourUserName</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">YourPassword</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>

Note: You have to change both (YourUserName & YourPassword) to the appropriate username and password that is authenticated to call the webservice.

3- Save the project and call the service again.

Another easy way to do this is :

1- Open SOAP Project

2- Right click on the request body in any black space and choose “Add WSS Username Token“

3- Choose Password Text from the drop down list of Add WSS Username Token Field, then click OK.

4- this option will take the username and password automatically from Auth which you set earlier.

5- Save the project and test the issue again, it should be resolved.

Note: If you go for the second solution you should enter authentication first. 

Hi Marito,

Find below the query to get supplier bank details:

SELECT ASP.SEGMENT1 VENDOR_NUM
,ASP.VENDOR_NAME
,ASA.VENDOR_SITE_CODE
,HOU.NAME OU_NAME
,IEBA.COUNTRY_CODE
,CBBV.BANK_NAME
,IEBA.BANK_ACCOUNT_NAME_ALT
,CBBV.BANK_NUMBER
,CBBV.BANK_BRANCH_NAME
,CBBV.BRANCH_NUMBER
,CBBV.EFT_SWIFT_CODE
,IEBA.BANK_ACCOUNT_NUM
,IEBA.IBAN
,IEBA.CURRENCY_CODE
FROM AP_SUPPLIERS ASP
,AP_SUPPLIER_SITES_ALL ASA
,IBY_EXTERNAL_PAYEES_ALL IEPAYEES
,IBY_PMT_INSTR_USES_ALL IPIUA
,IBY_EXT_BANK_ACCOUNTS IEBA
,CE_BANK_BRANCHES_V CBBV
,IBY_ACCOUNT_OWNERS IAOWNERS
,HR_OPERATING_UNITS HOU
WHERE IAOWNERS.PRIMARY_FLAG = 'Y'
AND IAOWNERS.EXT_BANK_ACCOUNT_ID = IEBA.EXT_BANK_ACCOUNT_ID
AND IAOWNERS.EXT_BANK_ACCOUNT_ID = IPIUA.INSTRUMENT_ID
AND IEPAYEES.EXT_PAYEE_ID = IPIUA.EXT_PMT_PARTY_ID
AND IEPAYEES.PAYEE_PARTY_ID = IAOWNERS.ACCOUNT_OWNER_PARTY_ID
AND IEPAYEES.SUPPLIER_SITE_ID = ASA.VENDOR_SITE_ID
AND ASA.VENDOR_ID = ASP.VENDOR_ID
AND IEBA.BRANCH_ID = CBBV.BRANCH_PARTY_ID(+)
AND HOU.ORGANIZATION_ID = ASA.ORG_ID;

Above query will list all suppliers bank details:

Supplier Number, Name, Supplier Site Code, Operating unit that belong to supplier site, Country, Bank name, Bank alternative Name (like Arabic Name of the bank), Bank Number, Branch number and name, the swift code, the account number, IBAN, and currency code.

And the list is open to add any other column/s you prefer.

To find the application URL from the backend use one of the following queries :

SELECT HOME_URL FROM ICX_PARAMETERS;

Result

http://<host.domain:port>/OA_HTML/AppsLogin

OR

SELECT FPOV.PROFILE_OPTION_VALUE
FROM FND_PROFILE_OPTIONS FPO, FND_PROFILE_OPTION_VALUES FPOV
WHERE FPO.PROFILE_OPTION_ID = FPOV.PROFILE_OPTION_ID
AND PROFILE_OPTION_NAME = 'APPS_FRAMEWORK_AGENT'
AND LEVEL_VALUE = 0;

Result

http://<host.domain:port&gt;

Please make sure of the credentials, because this error is quite clear enough that either the username or password is incorrect.

Note : In Oracle 11g the credentials are CASE sensitive it’s a default feature of newly oracle 11g database creation.

Now if you want to make sure whether this feature is enabled or not you can go to sqlplus then execute the following SQL command.

SHOW PARAMETER SEC_CASE_SENSITIVE_LOGON

if you get ” TRUE ” value then the the password is case sensitive otherwise it isn’t.

you can also disable this feature by executing the following SQL command :

SQL> ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE;

System altered.

ORA-00054 referring to the table you are trying to update it is already locked by another session that made a query for an update on the same table and not committed or rolled back yet. It could be a form or another session.

The action you could take to solve the problem is to commit or roll back the changes from the other session, causing the lock before performing the current action. There is a query also to help you identify which session that causing the lock on your table so that you can kill the session immediately.

SELECT S.USERNAME
,S.SID
,S.SERIAL#
,T.USED_UBLK
,T.USED_UREC
,RS.SEGMENT_NAME
,R.RSSIZE
,R.STATUS
FROM V$TRANSACTION T
,V$SESSION S
,V$ROLLSTAT R
,DBA_ROLLBACK_SEGS RS
WHERE S.SADDR = T.SES_ADDR
AND T.XIDUSN = R.USN
AND RS.SEGMENT_ID = T.XIDUSN
ORDER BY T.USED_UBLK DESC;

Above query has been taken from oracle-base then from the output of above query you can use SID and SERIAL# to kill the session by executing the following statement.

alter system kill session 'sid,serial#' IMMEDIATE;