Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1826
  • Last Modified:

IDOCTYPE_READ_COMPLETE throws an exception OBJECT_UNKNOWN

When I use a user in SAP which has minimal permissions, every call to IDOCTYPE_READ_COMPLETE returns the error OBJECT_UNKNOWN. If I use a user which is an admin on SAP, IDOCTYPE_READ_COMPLETE functions correctly.
I was hoping someone here could let me know exactly what permissions are required for being able to successfully execute IDOCTYPE_READ_COMPLETE
0
muskad202
Asked:
muskad202
  • 2
  • 2
1 Solution
 
TwisteddkCommented:
Have you tried running transaction SU53 after the unsuccessfull attempt ? Normally this will give you details of the name of the authorization object that is missing. Simply add this object to a new authorization, or find an authorization that includes the object, and add it to the user that needs the permission.
Reading/processing IDOCs can be dangerous, so dont give this permission to just anyone. Basically, you can do ANYTHING with an IDOC you can do with a financial (and some logistical aswell) transaction in SAP.
0
 
muskad202Author Commented:
Hi!
The user I am using is a dialog user who does not have permission to log in through the SAP GUI, and hence I cannot use that user to access SU53. The user does have permissions to receive IDocs though. I am calling IDOCTYPE_READ_COMPLETE programmatically using the RFC SDK.
Thanks.
Mustansir
0
 
BACRCommented:
Hi!
Authorisation object S_IDOCDEFT, Fields:
EDI_TCD, value 'WE30'
ACTVT, value - 03 (display)
EDI_DOC, value - I-DOC type
EDI_CIM, value DUMMY (Not used)

Additional authorisations objects are required if extensions of I-DOC will be read.
Hope this helps.
BACR
 

0
 
muskad202Author Commented:
Thanks a lot BACR !! This is the first real response I have got. I'll pass this information to my SAP developer to try out ..
Meanwhile, can you let me know what authorization I would need for IDoc extensions too? From the souce code of EXTTYPE_AUTHORITY_CHECK, I'm assuming most of information is the same as above, exception that EDI_DOC is DUMMY, and EDI_CIM is the extension type. Is the authorisation object the same?
Thanks,
Mustansir
0
 
BACRCommented:
Hi!

Yes, that's correct, authorisations object for extensions is the same. The folowing authorisation object in profile should give you access to complete structure of I-DOC:
Authorisation object S_IDOCDEFT, Fields:
EDI_TCD, value 'WE30'
ACTVT, value - 03 (display)
EDI_DOC, value  *
EDI_CIM, value *

Hope this helps
BACR
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now