Hi Jigang,

Thanks for the very detailed blog on setting up the customizing fields for DCD cases.

Our requirement was to assign the existing fields in DCD such as Person Responsible, Approver 1, Approver 2

• For this I use BAdi : SCMG_CHNG_BFR_STR_C and this works completely fine for assignment during the automatic case creation from SD documents.
• Next we have a requirement to consider the validation of the above three approver fields based on a group user which we define using a custom maintenance table setup and this is also inline with the Approval setup for Credit Analyst based on the Open Credit amount threshold defined in standard customizing, So this validation triggers when user tries to edit attributes of the DCD case it checks if exists in the group user for Responsible, Approver1, Approver2 based on the requirement. Again we face no issue in setting up this validation through another BAdI : SCMG_VLDT_BFR_STR_C.

              TRY. "Check if changed?
                  IF im_case->is_changed( ) = abap_true.
  *          Check if current user is not in approval hierarchy group
              IF  ( lv_person_resp_grp IS NOT INITIAL
                AND sy-uname NOT IN lt_person_resp_grp ) " Person Responsible          
              OR ( lv_one_approver_grp IS NOT INITIAL
                AND sy-uname NOT IN lt_one_approver_grp )" Approver 1
              OR ( lv_two_approver_grp IS NOT INITIAL
               AND sy-uname NOT IN lt_two_approver_grp )." Approver 2
  
                ch_is_valid = if_srm=>false.
  
  *           Display message that user not authorized to save changes
                ls_messages-type = 'E'.
                ls_messages-id = 'SCMG_CASE'.
                ls_messages-number = '009'.
  
                CALL FUNCTION 'MESSAGE_TEXT_BUILD'
                  EXPORTING
                    msgid               = ls_messages-id
                    msgnr               = ls_messages-id
                  IMPORTING
                    message_text_output = ls_messages-message.
  
                APPEND ls_messages TO ch_messages.
  
                TRY.
  *                 Undo attribute changes if changed
                    im_case->undo_attribute_changes( ).
                  CATCH cx_srm_framework .
                ENDTRY.
  
              ENDIF.
                CATCH cx_srm_framework .
              ENDTRY.​

• Next when we try to release the document , SD release is successful and the notes are updated successfully but surprisingly the Document Status for the case is still in status Blocked - '1' and does not get updated.
• I tried to do analysis on this issue and find another strange observation while using this BAdI SCMG_VLDT_BFR_STR_C. When I avoid the usage of validation parameters CH_IS_VALID (Case validation flag), CH_MESSAGES (Message Structure) both provided by SAP to validate the DCD cases before Save the release status is updated without any issue and what's peculiar here is that when I just comment the usage of these parameters the release status is updated but in both the scenarios the control never would go inside my condition for a positive case and that is really strange. The below example is the same code as above but I just comment what is inside the validation condition and even if this condition does not satisfy whether commented or not it somehow seems to affect the release process because I have also tried extensive debugging to check the SD document release after this and there seems to be no difference there.

•             TRY. "Check if changed?*                IF im_case->is_changed( ) = abap_true.
  *          Check if current user is not in approval hierarchy group
              IF  ( lv_person_resp_grp IS NOT INITIAL
                AND sy-uname NOT IN lt_person_resp_grp ) " Person Responsible          
              OR ( lv_one_approver_grp IS NOT INITIAL
                AND sy-uname NOT IN lt_one_approver_grp )" Approver 1
              OR ( lv_two_approver_grp IS NOT INITIAL
               AND sy-uname NOT IN lt_two_approver_grp )." Approver 2
  
  *              ch_is_valid = if_srm=>false.
  
  **           Display message that user not authorized to save changes
  *              ls_messages-type = 'E'.
  *              ls_messages-id = 'SCMG_CASE'.
  *              ls_messages-number = '009'.
  *
  *              CALL FUNCTION 'MESSAGE_TEXT_BUILD'
  *                EXPORTING
  *                  msgid               = ls_messages-id
  *                  msgnr               = ls_messages-id
  *                IMPORTING
  *                  message_text_output = ls_messages-message.
  
  *              APPEND ls_messages TO ch_messages.
  
  *              TRY.
  *                 Undo attribute changes if changed
  *                  im_case->undo_attribute_changes( ).
  *                CATCH cx_srm_framework .
  *              ENDTRY.
  
              ENDIF.
                CATCH cx_srm_framework .
              ENDTRY.

•  I have then also tried to investigate how this field is getting updated and apparently in S4HANA release this gets updated by the generic workflow user (SAP_WFRT) to avoid the requirement of credit management authorization to a sales person . The event created for DCD for a blocked sales order is shown in below image. But the important question here is how can I possibly control the release through this or this is some kind of bug which SAP needs to know? I want to raise an OSS note describing this issue but really want to understand if something is missed from my side. Your thoughts on this problem are really appreciated!

Thanks & regards,

Noman