METHOD if_mdg_se_bp_bulk_replrq_in~inbound_processing. DATA ls_user_setting TYPE mdg_user_proxy_setting. DATA lt_user_setting TYPE mdg_user_proxy_setting_t. DATA lv_crtype TYPE mdg_sup_change_req. if in-message_header-business_scope-id-content = 'BPM'. ls_user_setting-field_name = 'PROXY_PERSISTANCE'. ls_user_setting-field_value = '1'. APPEND ls_user_setting TO lt_user_setting. ls_user_setting-field_name = 'SUPPLIER_CHANGE'. SELECT SINGLE usmd_creq_type INTO lv_crtype FROM usmd1601 WHERE usmd_process = 'SUP1'. * ls_user_setting-field_value = lv_crtype. APPEND ls_user_setting TO lt_user_setting. CALL METHOD cl_mdg_bp_bupa_si_in=>if_mdg_upload_proxy~setup_for_file_upload EXPORTING iv_instance = 1 * IO_UPLOAD_DIALOG = it_user_setting = lt_user_setting. endif. ENDMETHOD. The code first checks the +scope-id+-element in the message header. The SAP Master Data Governance load will only continue if the +scope-id+-element is set to +BPM+. The proxy implementation of the inbound service uses the context of the SAP Master Data Governance-file-upload-framework to determine how the incoming data has to be processed. We use the enhancement spot to set the file upload framework context in such a way that the incoming data is stored in the SAP Master Data Governance staging area and a change request of type SUPPL01 (Create Supplier) is being created. If key-mapping information was send as part of the Web Service call, the key-mapping for the new supplier will automatically be updated. The ABAP code in the Enhancement Sport looks for the first process type +SUP1+ in table USMD1601 and takes the change request type from that line. In our example LRDEMO will be selected as change request type when the web service is called (refer to table USMD1601 in figure 4 below). You may have to adapt the ABAP code to ensure your custom change request type (as defined in the following section _ Customizing the governance process_) is correctly assigned in the Enhancement Spot. *Figure 4: Table USMD1601* An example XML document to test the web service is attached to this wiki. | !http://wiki.sdn.sap.com/wiki/images/icons/emoticons/information.gif|height=16|alt=|align=absMiddle|w...! | *Test your scenario – Inbound Web Service* You should now test if the implementation is working. Using a Web Service test tool such as the SAP Web Service Navigator you can call the Web Service. After successful execution you should find a new change request in the POWER -List (Personal Object Work Entity Repository). You can access the POWER-List via the supplier role in SAP Master Data Governance. | h3. Customizing the governance process Your Web Service is working? Good! Your inbound connection to SAP Master Data Governance is now ready. Next we need to establish the outbound connection to NetWeaver BPM. In our example we extend the governance process for create supplier by two additional SAP Business Workflow tasks. Each of the two tasks sends a message to NetWeaver BPM. Since we do not want to modify the SAP delivered workflow template and change request type, we first create a copies. Look up the id of the workflow template for +Create Supplier+: Open MDG IMG activity +Create Change Request Type+ and find the row with change request type SUPPL01 (Create Supplier). In the same row you find the workflow template id for this change request type. 0.1. Open the +Workflow Builder+ (transaction swdd) and create a copy of the SAP delivered workflow template for +Create Supplier+ (use the workflow template id from the previous step). Do not forget to save and activate you new workflow template. 0.1. In MDG IMG activity +Create Change Request Type+ create a copy of the SAP delivered change request type SUPPL01 (Create Supplier). Assign the new workflow template id from the previous step to the new change request. In our example we have created a custom change request type LRDEMO which is linked to workflow template WS99900008 (Firgure 5 below).