Skip to Content
Author's profile photo Jan Rauscher
Jan Rauscher
July 5, 2016 Less than a 1 minute read

MDG-S/C: removing authorizations for XK01 and XK02 and CVI

When applying an MDG system for vendor and/or customer, it’s recommend that end users should not have the authorizations for usage of transactions XK01, XK02, etc. anymore (otherwise they could deviate MDG and maintain the vendors/customers directly in the ERP system).

However this leads to the issue that CVI is no longer possible to create vendors/customers because it checks whether the end user has the relevant authorization. If this authorization is removed, the CVI throws an error message. (CVI is needed because MDG creates a business partner first and then via CVI a vendor/customer data set.)

To avoid this issue you can implemented the two BAdIs

  • VENDOR_EXTENSION_AUTH_CHECK and/or
  • CUSTOMER_EXTENSION_AUTH_CHECK

They offer a method AUTHORITY_CHECK_VEND_TRANSACT resp. AUTHORITY_CHECK_CUST_TRANSACT of interface IF_EX_VENDOR_EXTENSION_AUTH resp. IF_EX_CUSTOMER_EXTENSION_AUTH that allows to put source code avoiding that CVI executes the authority check. An example for such a coding:

SNAG-0025.png

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Leander Lams
      Leander Lams

      Thank you for this information, but do you call the AUTHORITY_CHECK_VEND_TRANSACT method before you call the api? after? during? where exactly? I can get my CV_NOCHECK to set to 'X' (which isn't that hard), but I still get the error "No authorization for XK01"