Skip to main content
Solved

[ProjectionName].ACCESS_FAILURE: Arguments used to execute current operation are not allowed

  • June 24, 2024
  • 1 reply
  • 478 views

rahalk
Sidekick
Forum|alt.badge.img+4

Getting a strange error when trying to use two INT REST APIs which are working fine through Aurena. But not working when I try to run it through Postman using basic authentication.

 

Could you kindly go through the below scenario and help me resolve the issue?

 

Below is the Scenario:

  • I am trying to deliver customer order lines using the available rest APIs from the documentation.
  • I am using IFS Apps 10 Update 16
  • I am trying to use REST API with basic authentication
  • REST API - https://[ifshost]/int/ifsapplications/projection/v1/DeliverCustomerOrderLines.svc/DeliverLines
  • Payload
    1{
    2 "OrderNo": "M1132",
    3 "LineNo": "1",
    4 "RelNo": "4",
    5 "LineItemNo": 0
    6}
  • Authentication - Basic
  • Projection DeliverCustomerOrderLines.svc is included in compatibility mode and permissions are properly set (the same user name and setup works fine for other REST APIs)

  • Error:

    1{
    2 "error": {
    3 "code": "DATABASE_ERROR",
    4 "message": "Database error occurred. Contact administrator.",
    5 "details": [
    6 {
    7 "code": 20181,
    8 "message": "ORA-20181: DeliverCustomerOrderLines.ACCESS_FAILURE: Arguments used to execute current operation are not allowed."
    9 }
    10 ]
    11 }
    12}
  • Screenshot of the documentation:

     

  • Same thing happens for another REST API as well
  • REST API - https://[ifshost]/int/ifsapplications/projection/v1/DeliverCustomerOrderLineWithDifferences.svc/DeliverNonInvLineWithDiff
  • Everything else is same and the Error will look like the following:
    1{
    2 "error": {
    3 "code": "DATABASE_ERROR",
    4 "message": "Database error occurred. Contact administrator.",
    5 "details": [
    6 {
    7 "code": 20181,
    8 "message": "ORA-20181: DeliverCustomerOrderLineWithDifferences.ACCESS_FAILURE: Arguments used to execute current operation are not allowed."
    9 }
    10 ]
    11 }
    12}
  • Screenshot of the documentation:

     

Best answer by rahalk

Finally cracked the issue! Thanks @izryShiran for your insights too!

  • The issue is due to my integration user doesn’t have access to the site where the data is from.
  • The error message is so generic it’s hard to guess that it could have been an issue with data access.
  • When I send only data that my integration user can access or if I give access to the site of the data I was testing, the issue disappeared! 😀 
  • Below are some screenshots of the db code related to this error;

 

 

Hope these findings will help understand this error better in the future 😅

 

 

View original
Did this topic help you find an answer to your question?

1 reply

rahalk
Sidekick
Forum|alt.badge.img+4
  • Author
  • Sidekick
  • 8 replies
  • Answer
  • June 25, 2024

Finally cracked the issue! Thanks @izryShiran for your insights too!

  • The issue is due to my integration user doesn’t have access to the site where the data is from.
  • The error message is so generic it’s hard to guess that it could have been an issue with data access.
  • When I send only data that my integration user can access or if I give access to the site of the data I was testing, the issue disappeared! 😀 
  • Below are some screenshots of the db code related to this error;

 

 

Hope these findings will help understand this error better in the future 😅

 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings