Skip to Content
avatar image
Former Member

standard transaction /cockpit/1 is checking auth. object ZEIC in 1 system but not in other

HI All,

Auth. object ZEIC for /cockpit/1 is not being checked in 1 system., although it is a standard tramsaction.In comparing both systems, it is found that table /COCKPIT/CAUTH (Ebydos Invoice Cockpit - Authorization object) is missing entry for ZEIC. The syste where /cockpit/1 is working correctly(i.e ZEIC is being checked), has entry ZEIC in the table /COCKPIT/CAUTH.

So, could anyone suggest if this entry in the table is required.If so, whether it should be done by ABAPer or Security Consultant.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 10, 2013 at 04:32 AM


    it is not a standard transaction. It is a solution from 3rd party vendor built on top of ECC. So I would try to check documentation from them to figure out meaning of this table. You might be lucky and somebody who is using this solution might be able to answer your question. Regarding your second question. I guess both of those professions should be able to add a config entry into a table. Is it's customizing table have you tried to check SCUL log to figure out who populated this table in one system?


    Add comment
    10|10000 characters needed characters exceeded