{"id":721,"date":"2013-10-08T13:38:57","date_gmt":"2013-10-08T12:38:57","guid":{"rendered":"http:\/\/oprsteny.cz\/?p=721"},"modified":"2013-10-08T13:51:12","modified_gmt":"2013-10-08T12:51:12","slug":"abap-class-based-exceptions","status":"publish","type":"post","link":"https:\/\/oprsteny.cz\/?p=721","title":{"rendered":"ABAP – Class based exceptions"},"content":{"rendered":"

\"SAP\"<\/a>There are several ways how to handle errors or warnings in ABAP and in this article I’ll try to present exceptions. Specifically – global class based exceptions in ABAP<\/p>\n

    \n
  1. The most elegant way how to handle exception messages is to have them all stored at one place – ideally in a message class. So the first step will be message class creation (if you don’t already have one) in SE91.
    \nIn this message class you can create your desired messages – you can use the most generic message<\/p>\n
    & & & &<\/pre>\n
    but\u00a0in our example we’ll use the following:<\/p>\n
    Material & does not exist<\/pre>\n
    \"Messages<\/a><\/p>\n<\/li>\n
  2. Now we can step forward to create the exception class itself:
    \nIn SE24 create new class of type “Exception” named i.e. ZCX_MY_EXCEPTION derived\/inherited (in most cases)\u00a0from CX_STATIC_CHECK and check the option “With Message Class”
    \n    \"Exception<\/a><\/li>\n
  3. Note: Step 1 and checking option “With message class” in step 2 can be ommited and\u00a0texts will be created and stored in the text management OTR. But it is not possible to combine both text variants in one exception class.<\/li>\n
  4. Because we have parameters in our exception messages we have to define these parameters in our exception class. The most generic would be standard MSGV1 – MSGV4
    \n    \"Exception<\/a><\/li>\n
  5. Now we extend our exception by adding new specific exception IDs. To do that, go to Texts tab and create new exception ID, i.e. MATERIAL_NOT_FOUND and assign it with message class, message number and bind any message attributes (& in the message text) to the corresponding exception attributes.
    \n    \"Exception<\/a><\/li>\n
  6. Note:<\/em> If you don’t specify Exception ID when raising the exception then the default exception ID (it has the same name as exception class) is used and it’s text is generated.<\/li>\n
  7. And that’s it!
    \nNow you can simply use your new exception class with specific exception IDs in your program like in the following code:<\/p>\n
    DATA\u00a0l_exc\u00a0TYPE REF TO zcx_my_exception.\r\n\r\nTRY.\r\n* Exception thrown\r\n  RAISE EXCEPTION TYPE zcx_my_exception\r\n    EXPORTING\r\n      textid = zcx_my_exception=>material_not_found\r\n      msgv1  = '1234567'.                     \"material number\r\nCATCH zcx_my_exception into l_exc.\r\n  message l_exc type 'E'.\r\nendtry.<\/pre>\n
    Your MESSAGE is displayed automatically, with the attribute values inserted. There are no calls to get_text() or get_longtext(), and no data declarations for the resulting message string.
    \n    \"Exception<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
    There are several ways how to handle errors or warnings in ABAP and in this article I’ll try to present exceptions. Specifically – global class based exceptions in ABAP<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[16,9],"tags":[446,146,194,195],"class_list":["post-721","post","type-post","status-publish","format-standard","hentry","category-abap","category-development","tag-abap","tag-class","tag-exceptions","tag-oo"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p3nYbe-bD","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/oprsteny.cz\/index.php?rest_route=\/wp\/v2\/posts\/721","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/oprsteny.cz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/oprsteny.cz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/oprsteny.cz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/oprsteny.cz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=721"}],"version-history":[{"count":5,"href":"https:\/\/oprsteny.cz\/index.php?rest_route=\/wp\/v2\/posts\/721\/revisions"}],"predecessor-version":[{"id":733,"href":"https:\/\/oprsteny.cz\/index.php?rest_route=\/wp\/v2\/posts\/721\/revisions\/733"}],"wp:attachment":[{"href":"https:\/\/oprsteny.cz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=721"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/oprsteny.cz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=721"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/oprsteny.cz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=721"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}