SAP MDM Training-SAP MDM Tutorials,SAP MDM Jobs,SAP MDM Resumes-SAP MDM

Enterprise Master Data Management - A cross-system master data process for supplier

2012-02-22T08:19:00.001-08:00

Applies to:

ERP 6 EhP5 – Master Data Governance for Supplier

Summary

This article provides implementation details for a simplified cross system Supplier On-boarding scenario leveraging SAP’s Enterprise Master Data Management portfolio consisting of SAP NetWeaver Master Data Management (available since 2004) and SAP Master Data Governance (currently in Ramp-Up). The overarching process is modeled using SAP NetWeaver Business Process Management.

Author(s):

Lars Rueter
Company :    SAP AG, Germany
Created on:    4. March 2011
Author(s) Bio
Mr. Rüter works at SAP in the area of SAP Master Data Governance. In the past 11 years at SAP he has held different positions in Asia Pacific and EMEA. He has extensive experience in SAP's Master Data Management product portfolio, Java Development and SAP NetWeaver Portal. Mr Rüter has been involved in a large number of SAP implementations worldwide.

Cross system create supplier process

In our example we will build a cross-system supplier self-service registration and approval process. A supplier registers via a website and enters some initial data such as company name, street, city and postal code. These global attributes are stored in NetWeaver MDM for further distribution to Non-SAP systems. When the supplier is approved by the master data specialist a change request is automatically generated in SAP Master Data Governance. A workflow in SAP Master Data governance ensures that all ERP specific attributes are maintained. After final approval in SAP Master Data Governance the new supplier is activated and distributed. After activation a notification is send to the original requester.

Figure 1: High-level process overview

In figure 2 below you see which systems are part of the process:

(A) SAP Master Data Governance – maintenance and distribution of ERP specific attributes
(B) SAP NetWeaver MDM - maintenance and distribution of global attributes
(C) NetWeaver CE – process runtime, process specific UIs, process worklist, web service consumption and provisioning
(D) NetWeaver Developer Studio – process designtime

Figure 2: System Landscape

As mentioned above the process was implemented using NetWeaver BPM for the design and execution of the cross-system process. But we also leverage the out-the-box governance process in Master Data Governance for maintenance of ERP specific attributes.

Figure 3: Technical process overview

The figure above provides a more technical process overview using the Business Process Modeling Notation (BPMN) notation from SAP NetWeaver BPM:

(1) The initial supplier registration web page triggers the start web-service of the BPM process
(2) The global attributes from the registration web-page are used to create a new supplier record in SAP NetWeaver MDM
(3) In this human interaction step a new supplier is being approved
(4) BPM calls a SAP Master Data Governance Web Service to create a change request with the initial supplier data. This also triggers a SAP Business Workflow in SAP Master Data Governance.
(5) This step in BPM is called an intermediate message event. The process waits for a message to come in from Master Data Governance before the flow commences. Early in the SAP Business Workflow process we have inserted a task to call BPM. In this call we transmit the ID of the change request.
(6) BPM uses the change request ID from SAP Master Data Governance to send an e-mail to the original requestor. The e-mail contains a link to the SAP Business Workflow log. Using this link the original requestor can monitor the status of the change request in MDG.
(7) After sending an e-mail the BPM process waits again for a message from SAP Master Data Governance. This time SAP Master Data Governance sends a message at the end of the SAP Business Workflow process and after the Supplier has been finally approved and activated. The message includes the final ID of the Business Partner in the primary persistence.
(8) The last step in the BPM process informs the original requestor that the new Business Partner has been created and activated.

Implementation Steps

Integration between NetWeaver MDM and BPM has already been sufficiently documented on SDN. In this section the focus is on the integration between SAP Master Data Governance and NetWeaver BPM. Therefore we look specifically at the three integration points numbered step 4, step 5 and step 7 in figure 3 above. In step 4 we show how the inbound communication to SAP Master Data Governance was realized using a standard Web Service. The steps 5 and 7 are technically very similar in the sense that they both use a web service client proxy to transmit process status information from the SAP Business Workflow back to SAP NetWeaver BPM.

Using the inbound Business Partner Web Service

The ESR Web Service used to create a Business Partner in our scenario is called BusinessPartnerSUITEBulkReplicateRequest_In. In order to leverage this Web Service to automatically create a change request and key-mapping in SAP Master Data Governance , the method INBOUND_PROCESSING of BAdI MDG_SE_BP_BULK_REPLRQ_IN in Enhancement Sport MDG_SE_SPOT_BPBUPA has to be implemented.

IF_MDG_SE_BP_BULK_REPLRQ_IN~INBOUND_PROCESSING

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.

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.

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.

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.

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).

Figure 5: IMG activity Create Change Request Type

In MDG IMG activity Define workflow step numbers create a copy of the rows from the SAP delivered workflow template for the create supplier workflow template. In your copied rows change the workflow template id to the id of your custom workflow template.

Figure 6: IMG activity Define Workflow Step Numbers

To ensure the receiver determination will work for your new change request type enhance the BRF+ table GET_AGENT. Start transaction BRF+ and search for MDG as shown in figure 7 below.

Figure 7: BRF+ Search

Navigate to the GET_AGENT table as shown in figure 8. Create one row in the table for each workflow step. In column CREQUEST_TYPE enter the name of your custom change request type. In columns OTYPE and OBJID enter the object type (eg. user / organization) and corresponding value respectively.

Figure 8: BRF+ table get_agent

Test your scenario – custom change request type

This a good point to test your new change request type and workflow template. From the supplier role menu in SAP Master Data Governance choose the Create Supplier menu item. You should see your custom change request type in the drop down box of the create supplier screen. Select your custom change request type. Enter the new business partner details and approve the individual workflow steps until activation. At the end of the workflow you should have created a new Business Partner in the primary persistence. You can check by doing a search for the business partner id. You may have to change the receiver determination in BRF+ to ensure you can approve all the workflow steps.

Test your scenario – inbound web service with custom change request type

If you have confirmed that your new change request type and workflow template are working, repeat the test using the BusinessPartnerSUITEBulkReplicateRequest_In web service. Verify that after calling the web service a change request is created and the associated custom workflow is started. You can use transaction swud to find the workflow instance.

Exchanging process context information between SAP Business Workflow and NetWeaver BPM

In our example we decided to implement the exchange of process context information between NetWeaver BPM and SAP Business Workflow using asynchronous web services. In particular for exchanging the MDG change request id and business partner id. In NetWeaver BPM two Trigger Events were created (wsdl1, wsdl2) for this purpose. The consumption side is technically realized by generating an ABAP proxy for each service and calling this proxy from a task in the SAP Business Workflow. In step 5 (figure 3) we are using the Web Service call to transfer the change request-id to the SAP NetWeaver BPM context. In step 7 (figure 3) we transfer the business partner id after activation in the back end. After transferring the change request id step 5 (figure 3) we can use the change request id in NetWeaver BPM to generate an URL to the SAP Business Workflow log for this change request. We use this URL in our BPM process to send an e-mail notification to the original requestor with the link to the workflow log.

Generating a SAP Business Workflow log URL from a change request id in SAP MDG

https:// <HOSTNAME> : <PORT> /sap/bc/webdynpro/sap/usmd_crequest_protocol2?SAP-CLIENT= <CLIENT> &SAP-LANGUAGE=EN&CREQUEST= <insert the change request number here>

For sending the change request id to NetWeaver BPM a task was added after the Set Initial Status of Change Request task at the beginning of the workflow (figure 9). In the object method section of the task maintenance screen (figure 10) a custom class and method is selected. The called method calls the web service proxy to transmit the change request id. To be able to select your custom class from the workflow task it must implement the interfaces BI_OBJECT, BI_PRESISTENT and IF_WORKFLOW (figure 13). You can find more information regarding ABAP OO for workflow in the references section at the bottom of the article.

Figure 9: Create business partner workflow with custom task

Figure 10: Custom task maintenance

After successful activation of the Business Partner we can send the Business Partner Id to NetWeaver BPM. A new task was created after the Set Status of Change Request close to the end of the process (figure 11). In the task maintenance (figure 12) we assign a custom method that in turn uses the web service proxy to call NetWeaver BPM.

Figure 11: Create business partner workflow with custom task

Figure 12: Custom task maintenance

Figure 13: Interface tab of the class that gets called from the custom workflow task

Test your scenario – complete process

You can now call the inbound SAP Master Data Governance web service. In turn a change request will be created. The change request id will be transmitted to NetWeaver BPM. After approval and activation of the Business Partner the Business Partner id is transmitted to NetWeaver BPM. You can use transaction sxi_monitor to view incoming and outgoing messages.

NetWeaver BPM implementation considerations

While the focus of this article is not so much on NetWeaver BPM, but more on the interfaces of SAP Master Data Governance one important aspect with regard to intermediate message events in NetWeaver BPM should be mentioned here. In NetWeaver BPM it is necessary to define a message correlation between the incoming messages from SAP Master Data Governance and the process instance in NetWeaver BPM. Any unique id (eg. process id) can be used for this purpose. The unique id can be send as part of the BusinessPartnerSUITEBulkReplicateRequest_In web service call, for example in the message header. Subsequent calls from SAP Master Data Governance to NetWeaver BPM can then transmit this unique id as part of the message payload. NetWeaver BPM uses the unique id to find the right process instance for the incoming message.

Summary

In this article it was shown how SAP Master Data Governance can be used as part of a NetWeaver BPM cross-system master data process. The article also highlights how the capabilities of the build in governance processes can be easily extended using SAP NetWeaver BPM. The combination of SAP Master Data Governance with SAP NetWeaver BPM and SAP NetWeaver Master Data Management addresses a wide range of scenarios in the area of Enterprise Master Data Management.

Search In a MDM Repository

2012-02-08T10:28:00.001-08:00

Following code snippet shows the step to search inside MDM repository. It searches the string inside field Vendors in the table Vendors under repository Vendor1 .

public class Connection {     private SimpleConnection simpleConnection;     private String serverName = " ";     private String repositoryName="Vendor1";     private String dbServerName = " ";     private DBMSType dbmsType = DBMSType.MS_SQL;     private RegionProperties dataRegion = new RegionProperties();     private String userSession;     private String repositorySession;     private String userName="Admin";     private String password="mdm";     private RepositorySchema schema;     private RepositoryIdentifier repositoryID;     public void getConnection() {         try {             if (simpleConnection == null) {                 simpleConnection =                     SimpleConnectionFactory.getInstance(serverName);             }         } catch (Exception e) {             //              }     }         public void closeConnection( )       {         //@@begin closeConnection()         try{             if(simpleConnection!=null){                 DestroySessionCommand destroySessionCommand=new DestroySessionCommand(simpleConnection);                 destroySessionCommand.setSession(userSession);                 destroySessionCommand.execute();                 userSession=null;                 simpleConnection.close();             }         }catch(Exception e){
//                    }         //@@end       }           public void getAuthenticatedUserSession( )       {         //@@begin getAuthenticatedUserSession()         /*             * Create and authenticate a new user session to an MDM repository             */            repositoryID=new RepositoryIdentifier(repositoryName,dbServerName,dbmsType);            CreateUserSessionCommand createUserSessionCommand=new CreateUserSessionCommand(simpleConnection);            createUserSessionCommand.setRepositoryIdentifier(repositoryID);            createUserSessionCommand.setDataRegion(dataRegion);            try {                createUserSessionCommand.execute();                    userSession=createUserSessionCommand.getUserSession();// Get the session identifier               /* Authenticate User Session */            TrustedUserSessionCommand trustedUserSessionCommand=new TrustedUserSessionCommand(simpleConnection);            trustedUserSessionCommand.setUserName(userName);                      trustedUserSessionCommand.setSession(userSession);            try {                trustedUserSessionCommand.execute();                userSession=trustedUserSessionCommand.getSession();            } catch (CommandException e1) {                /* Trusted Connection is not accepted */                AuthenticateUserSessionCommand authenticateUserSessionCommand=new AuthenticateUserSessionCommand(simpleConnection);                authenticateUserSessionCommand.setSession(userSession);                authenticateUserSessionCommand.setUserName(userName);                authenticateUserSessionCommand.setUserPassword(password);                authenticateUserSessionCommand.execute();                    }                   SetUnicodeNormalizationCommand unicodeNormalizationCommand=new SetUnicodeNormalizationCommand(simpleConnection);            unicodeNormalizationCommand.setSession(userSession);            unicodeNormalizationCommand.setNormalizationType(SetUnicodeNormalizationCommand.NORMALIZATION_COMPOSED);            unicodeNormalizationCommand.execute();            }catch (CommandException e2) {
//                         }       }           public void setRegionProperties( )       {         //@@begin setRegionProperties()         dataRegion.setRegionCode("engUSA");         // Set the locale on data region         dataRegion.setLocale(new Locale("en", "US"));         // Set the name of data region         dataRegion.setName("US");         //@@end       }     public void setRepositoryInfo( java.lang.String repositoryName, java.lang.String userID, java.lang.String password )      {        //@@begin setRepositoryInfo()        this.repositoryName=repositoryName;        this.userName=userID;        this.password=password;            //@@end      }           public void getAuthenticatedRepositorySession( )     {       //@@begin getAuthenticatedRepositorySession()           try{               CreateRepositorySessionCommand repositorySessionCommand=new CreateRepositorySessionCommand(simpleConnection);               repositorySessionCommand.setRepositoryIdentifier(repositoryID);               repositorySessionCommand.execute();               repositorySession=repositorySessionCommand.getRepositorySession();                       AuthenticateRepositorySessionCommand authenticatedRepositorySession=new AuthenticateRepositorySessionCommand(simpleConnection);               authenticatedRepositorySession.setSession(repositorySession);               authenticatedRepositorySession.setUserName(userName);               authenticatedRepositorySession.setUserPassword(password);               authenticatedRepositorySession.execute();                       GetRepositorySchemaCommand repositroySchemaCommand=new GetRepositorySchemaCommand(simpleConnection);               repositroySchemaCommand.setSession(repositorySession);               repositroySchemaCommand.execute();               schema=repositroySchemaCommand.getRepositorySchema();                           }catch(CommandException e){
//                        }catch(Exception e){
//                        }               //@@end     }         public com.sap.mdm.ids.FieldId getFieldID( java.lang.String tableName, java.lang.String fieldCode )       {         //@@begin getFieldID()             return schema.getField(tableName,fieldCode).getId();             //@@end       }           public com.sap.mdm.ids.TableId getTableID( java.lang.String tableName )       {         //@@begin getTableID()         return schema.getTable(tableName).getId();         //@@end       }           public void searchRepository() {             //@@begin searchRepository()             ResultDefinition resultDef =                 new ResultDefinition(schema.getTable("Vendors").getId());             resultDef.addSelectField(schema.getField("Vendors", "Name").getId());             //resultDef.addSelectField(new FieldId(15));             FieldSearchDimension searchDimension =                 new FieldSearchDimension(                     schema.getField("Vendors", "Name").getId());             TextSearchConstraint constraint =                 new TextSearchConstraint("ABC", TextSearchConstraint.CONTAINS);             Search search = new Search(schema.getTable("Vendors").getId());             //search.addSearchItem(searchDimension,constraint);             RetrieveLimitedRecordsCommand limitedRecordsCommand =                 new RetrieveLimitedRecordsCommand(simpleConnection);             limitedRecordsCommand.setSearch(search);             limitedRecordsCommand.setSession(userSession);             limitedRecordsCommand.setResultDefinition(resultDef);             try {                 limitedRecordsCommand.execute();             } catch (CommandException e) {                 //                          }             //return limitedRecordsCommand.getRecords();             RecordResultSet recordSet = limitedRecordsCommand.getRecords();             String recordAsString = null;             String fieldValue = null;             for (int i = 0; i < recordSet.getCount(); i++) {                 recordAsString = "";                 FieldId[] returnedFields = recordSet.getRecord(i).getFields();                 for (int j = 0; j < returnedFields.length; j++) {                     if (recordSet                         .getRecord(i)                         .getFieldValue(returnedFields[j])                         .isNull()) {                         fieldValue = " |";                     } else {                         fieldValue =                             recordSet.getRecord(i).getFieldValue(returnedFields[j])                                 + "|";                     }                                         recordAsString += fieldValue;                     System.out.println(recordAsString);                 }             }         }                 public static void main (String[] args)                 {             Connection test=new Connection();             test.getConnection();             test.setRegionProperties();             test.setRepositoryInfo("Vendor1","Admin","mdm");             test.getAuthenticatedUserSession();             test.getAuthenticatedRepositorySession();             test.searchRepository();             test.closeconnection();              }

}

Code to Get List of Validation in a Table

2012-02-08T10:25:00.003-08:00

Following code snippet finds out the list of Validation from a Table.

package com.sap.infosys.mdm.validationcheck;

import com.sap.mdm.commands.AuthenticateUserSessionCommand;
import com.sap.mdm.commands.CommandException;
import com.sap.mdm.commands.CreateUserSessionCommand;
import com.sap.mdm.commands.DestroySessionCommand;
import com.sap.mdm.commands.GetRepositoryRegionListCommand;
import com.sap.mdm.data.RegionProperties;
import com.sap.mdm.ids.TableId;
import com.sap.mdm.net.ConnectionException;
import com.sap.mdm.net.ConnectionPool;
import com.sap.mdm.net.ConnectionPoolFactory;
import com.sap.mdm.server.DBMSType;
import com.sap.mdm.server.RepositoryIdentifier;
import com.sap.mdm.validation.ValidationProperties;
import com.sap.mdm.validation.ValidationPropertiesResult;
import com.sap.mdm.validation.commands.RetrieveValidationsCommand;


public class GetListOfValidations {     public static void main(String[] args) {         // create connection pool to a MDM server         String serverName = " ";         ConnectionPool connections = null;         try {             connections = ConnectionPoolFactory.getInstance(serverName);         } catch (ConnectionException e) {             e.printStackTrace();             return;         }         // specify the repository to use         // alternatively, a repository identifier can be obtain from the GetMountedRepositoryListCommand         String repositoryName = "Vendor1";         String dbmsName = " ";         RepositoryIdentifier reposId =             new RepositoryIdentifier(repositoryName, dbmsName, DBMSType.MS_SQL);         // get list of available regions for the repository         GetRepositoryRegionListCommand regionListCommand =             new GetRepositoryRegionListCommand(connections);         regionListCommand.setRepositoryIdentifier(reposId);         try {             regionListCommand.execute();         } catch (CommandException e) {             e.printStackTrace();             return;         }         RegionProperties[] regions = regionListCommand.getRegions();         // create a user session         CreateUserSessionCommand sessionCommand =             new CreateUserSessionCommand(connections);         sessionCommand.setRepositoryIdentifier(reposId);         sessionCommand.setDataRegion(regions[0]); // use the first region         try {             sessionCommand.execute();         } catch (CommandException e) {             e.printStackTrace();             return;         }         String sessionId = sessionCommand.getUserSession();         // authenticate the user session         String userName = "Admin";         String userPassword = "mdm";         AuthenticateUserSessionCommand authCommand =             new AuthenticateUserSessionCommand(connections);         authCommand.setSession(sessionId);         authCommand.setUserName(userName);         authCommand.setUserPassword(userPassword);         try {             authCommand.execute();         } catch (CommandException e) {             e.printStackTrace();             return;         }         // the main table, hard-coded         TableId mainTableId = new TableId(1);         // Get the list of validations         RetrieveValidationsCommand objRtvVldCmd =             new RetrieveValidationsCommand(connections);         // set the user session         objRtvVldCmd.setSession(sessionId);         // get validation for the following tables.         objRtvVldCmd.setTableId(mainTableId);                 try {             objRtvVldCmd.execute();         } catch (CommandException e) {             e.printStackTrace();             return;         }         ValidationPropertiesResult objVldPropRslt =             objRtvVldCmd.getValidationPropertiesResult();         ValidationProperties[] validations = objVldPropRslt.getValidations();         //disply --> Validation ID | error/warning message | Validation Name         for (int i = 0; i < validations.length; i++) {             System.out.println(                 validations[i].getId()                     + " | "                     + validations[i].getMessage()                     + " | "                     + validations[i].getName());         }     }

}

A Class worth exploring for handling special characters in MDM

2012-02-08T10:25:00.001-08:00

While development was going at full pace ,a small hurdle in form of special characters turned out to be a real speed breaker.The situtaion was that in MDM repository some field say Name contained special chracters(Õ , û ,Û) in other language like Hungarian,German ,French etc.Problem was I logged into the Repository with english language with MDM JAVA API and API was retrieving undesired value(O??,u??,U??) from the data manager .Although the Name string seems absolutely fine in the Data Manager.In short -value in MDM Data Manager for field name was Õ û Û and output from API was O??u??U??

To my rescue came this class which is worth exploring when you have a situation like above

Class SetUnicodeNormalizationCommand

After you establish your connection to the server through API and Authenticate User Session ,you need to work with this class.

Connection to server would return an object of type ConnectionPool (call it connection)and UserSession authentication would return a string (call it session).Now write this piece of code

SetUnicodeNormalizationCommand cmd = new SetUnicodeNormalizationCommand(connection);

cmd.setSession(session);

cmd.setNormalizationType(SetUnicodeNormalizationCommand.NORMALIZATION_COMPOSED);

cmd.execute();

This class will keep the special characters retrieval intact.

SRM-MDM Catalog version compatibility

2012-02-08T10:12:00.001-08:00

Purpose

The main objective of this page is to explain the compatibility between SRM-MDM Catalog, Java API and MDM Server.

Overview

The application SRM-MDM Catalog is dependent on other two main applications or components, which are MDM Server and MDM Java API. The compatibility of these applications is informed in the SRM-MDM Release Notes available in SAP Service Marketplace (Software Download Center):

https://service.sap.com/swdc

This document will present how to check the versions of each of these applications and it will also explain how to correct the compatibility in case there is a version mismatch.

Identifying the versions of your applications

You can get this information by accessing the J2EE component info page (http://<J2EE_SERVER>:<PORT>/sap/monitoring/ComponentInfo).

The Component name of SRM-MDM is SRM_MDM_CAT and the Component name of MDM Java API is MDM_JAVA_API.

In order to get the information of your MDM Server, please follow the steps below:

1) Open the SRM MDM utilities:

http://<J2EE_SERVER>:<PORT>/webdynpro/dispatcher/sap.com/tc~mdm~srmcat~uiutil/Utilities

2) Choose "Connection Test"

3) Provide the host name or IP of your MDM server (MDM server)

4) Click on "Start Testing" button

Checking the compatibility of your applications

Find the latest release note according to your SRM-MDM Support Package (SP) and open this note.

You will find in the note the SRM-MDM Catalog SP and Patch as well as the MDM Server SP. The version of MDM Java API should be the same as MDM Server since they are distributed together, as part of the same release.

See the image below for more information:

If the version of these three components is not compatible then it is probable that you will face issues during the usage of SRM-MDM Catalog.

Example of compatible versions:

SAP Note 1505367 mention SRM-MDM Catalog 3.0 SP08 Patch 01 is compatible with MDM Server 7.1 SP05.

Your component versions:

SRM_MDM_CAT:3.0 SP8 (1000.3.0.8.123.123456789)

MDM_JAVA_API: 710 SP5 (1000.710.0.5.123.123456789)

MDM Server: MDM Server 7.1 SP5 (Check)

Example of incompatible versions:

SAP Note 1642907 mention SRM-MDM Catalog 3.0 SP11 Patch 01 is compatible with MDM Server 7.1 SP07.

Your component versions:

SRM_MDM_CAT:3.0 SP11 (1000.3.0.8.123.123456789)

MDM_JAVA_API: 710 SP4 (1000.710.0.4.123.123456789)

MDM Server: MDM Server 7.1 SP4 (Check)

Solving the incompatibility of your applications

In case you have a version mismatch you should update your applications according to the latest release note for SRM-MDM. In case you don’t want to update your MDM Server than use the latest release note according to your SRM-MDM SP. Note that some errors are corrected in higher releases so it is not guaranteed that your issue will be solved by updating to the latest release of your SP.

In order to update your application components go to Software Download Center, click on "Support Packages and Patches" (top menu) and then click on "Search for Support Packages and Patches" (left menu). Search for "SAP MDM CATALOG" and click on oyr SRM-MDM version. For more information please check note 1476694.

Code to Get List of Validation in a Table

2012-02-08T10:11:00.003-08:00

Following code snippet finds out the list of Validation from a Table.

package com.sap.infosys.mdm.validationcheck;

import com.sap.mdm.commands.AuthenticateUserSessionCommand;
import com.sap.mdm.commands.CommandException;
import com.sap.mdm.commands.CreateUserSessionCommand;
import com.sap.mdm.commands.DestroySessionCommand;
import com.sap.mdm.commands.GetRepositoryRegionListCommand;
import com.sap.mdm.data.RegionProperties;
import com.sap.mdm.ids.TableId;
import com.sap.mdm.net.ConnectionException;
import com.sap.mdm.net.ConnectionPool;
import com.sap.mdm.net.ConnectionPoolFactory;
import com.sap.mdm.server.DBMSType;
import com.sap.mdm.server.RepositoryIdentifier;
import com.sap.mdm.validation.ValidationProperties;
import com.sap.mdm.validation.ValidationPropertiesResult;
import com.sap.mdm.validation.commands.RetrieveValidationsCommand;


public class GetListOfValidations {     public static void main(String[] args) {         // create connection pool to a MDM server         String serverName = " ";         ConnectionPool connections = null;         try {             connections = ConnectionPoolFactory.getInstance(serverName);         } catch (ConnectionException e) {             e.printStackTrace();             return;         }         // specify the repository to use         // alternatively, a repository identifier can be obtain from the GetMountedRepositoryListCommand         String repositoryName = "Vendor1";         String dbmsName = " ";         RepositoryIdentifier reposId =             new RepositoryIdentifier(repositoryName, dbmsName, DBMSType.MS_SQL);         // get list of available regions for the repository         GetRepositoryRegionListCommand regionListCommand =             new GetRepositoryRegionListCommand(connections);         regionListCommand.setRepositoryIdentifier(reposId);         try {             regionListCommand.execute();         } catch (CommandException e) {             e.printStackTrace();             return;         }         RegionProperties[] regions = regionListCommand.getRegions();         // create a user session         CreateUserSessionCommand sessionCommand =             new CreateUserSessionCommand(connections);         sessionCommand.setRepositoryIdentifier(reposId);         sessionCommand.setDataRegion(regions[0]); // use the first region         try {             sessionCommand.execute();         } catch (CommandException e) {             e.printStackTrace();             return;         }         String sessionId = sessionCommand.getUserSession();         // authenticate the user session         String userName = "Admin";         String userPassword = "mdm";         AuthenticateUserSessionCommand authCommand =             new AuthenticateUserSessionCommand(connections);         authCommand.setSession(sessionId);         authCommand.setUserName(userName);         authCommand.setUserPassword(userPassword);         try {             authCommand.execute();         } catch (CommandException e) {             e.printStackTrace();             return;         }         // the main table, hard-coded         TableId mainTableId = new TableId(1);         // Get the list of validations         RetrieveValidationsCommand objRtvVldCmd =             new RetrieveValidationsCommand(connections);         // set the user session         objRtvVldCmd.setSession(sessionId);         // get validation for the following tables.         objRtvVldCmd.setTableId(mainTableId);                 try {             objRtvVldCmd.execute();         } catch (CommandException e) {             e.printStackTrace();             return;         }         ValidationPropertiesResult objVldPropRslt =             objRtvVldCmd.getValidationPropertiesResult();         ValidationProperties[] validations = objVldPropRslt.getValidations();         //disply --> Validation ID | error/warning message | Validation Name         for (int i = 0; i < validations.length; i++) {             System.out.println(                 validations[i].getId()                     + " | "                     + validations[i].getMessage()                     + " | "                     + validations[i].getName());         }     }

}

CreateRecordCommand Vs CreateRecordsCommand

2012-02-08T10:11:00.001-08:00

Given the shortcomings of Import Manager of rejecting a complete input excel spreadsheet, in case of even a single spurious record and lack of comprehensive error reporting to track reasons for file rejection or all errors. All these and more combined together, gave me a reason to develop a prototype, which overcomes shortcomings of using Import Manager to import data into MDM repository using Excel spreadsheets

In this blog I will discuss two important API classes, CreateRecordCommand and CreateRecordsCommand , and in following blogs will detail the complete design using which you can have your own customised Import Manager, capable of Importing data from excel spreadsheet into MDM repository with comprehensive error reporting.

Browsing through the MDM Java API documentation I found two classes for creating records in the repository:

CreateRecordCommand &
CreateRecordsCommand

While the first command is used to create individual records in the repository, the following CreateRecordsCommand is used for mass record creation.

It is a single Record Object which is a required parameter for CreateRecordCommand, we need to set an array of Record objects (records for mass creation) for CreateRecordsCommand.

Using CreateRecordCommand you can get 'recordId' of the newly created record but using CreateRecordsCommand the API provides us various methods to retrieve

FailedRecordMessages
Succeeded Record recordIds
Failed and Succeeded Record Arrays, containing corresponding indexes in the records array initially passed into CreateRecordsCommand
Array of all records passed into CreateRecordsCommand

Please use the link of MDM Java API javadoc link http://help.sap.com/javadocs/MDM/SP06P2/index.html to find out specific methods for CreateRecordsCommand, which can be used to retrieve specific information in order to generate better reports with exception/error messages.

Signing off for now....... till my next page in this series.

Search In a MDM Repository

2012-02-08T10:07:00.001-08:00

Following code snippet shows the step to search inside MDM repository. It searches the string inside field Vendors in the table Vendors under repository Vendor1 .

public class Connection {     private SimpleConnection simpleConnection;     private String serverName = " ";     private String repositoryName="Vendor1";     private String dbServerName = " ";     private DBMSType dbmsType = DBMSType.MS_SQL;     private RegionProperties dataRegion = new RegionProperties();     private String userSession;     private String repositorySession;     private String userName="Admin";     private String password="mdm";     private RepositorySchema schema;     private RepositoryIdentifier repositoryID;     public void getConnection() {         try {             if (simpleConnection == null) {                 simpleConnection =                     SimpleConnectionFactory.getInstance(serverName);             }         } catch (Exception e) {             //              }     }         public void closeConnection( )       {         //@@begin closeConnection()         try{             if(simpleConnection!=null){                 DestroySessionCommand destroySessionCommand=new DestroySessionCommand(simpleConnection);                 destroySessionCommand.setSession(userSession);                 destroySessionCommand.execute();                 userSession=null;                 simpleConnection.close();             }         }catch(Exception e){
//                    }         //@@end       }           public void getAuthenticatedUserSession( )       {         //@@begin getAuthenticatedUserSession()         /*             * Create and authenticate a new user session to an MDM repository             */            repositoryID=new RepositoryIdentifier(repositoryName,dbServerName,dbmsType);            CreateUserSessionCommand createUserSessionCommand=new CreateUserSessionCommand(simpleConnection);            createUserSessionCommand.setRepositoryIdentifier(repositoryID);            createUserSessionCommand.setDataRegion(dataRegion);            try {                createUserSessionCommand.execute();                    userSession=createUserSessionCommand.getUserSession();// Get the session identifier               /* Authenticate User Session */            TrustedUserSessionCommand trustedUserSessionCommand=new TrustedUserSessionCommand(simpleConnection);            trustedUserSessionCommand.setUserName(userName);                      trustedUserSessionCommand.setSession(userSession);            try {                trustedUserSessionCommand.execute();                userSession=trustedUserSessionCommand.getSession();            } catch (CommandException e1) {                /* Trusted Connection is not accepted */                AuthenticateUserSessionCommand authenticateUserSessionCommand=new AuthenticateUserSessionCommand(simpleConnection);                authenticateUserSessionCommand.setSession(userSession);                authenticateUserSessionCommand.setUserName(userName);                authenticateUserSessionCommand.setUserPassword(password);                authenticateUserSessionCommand.execute();                    }                   SetUnicodeNormalizationCommand unicodeNormalizationCommand=new SetUnicodeNormalizationCommand(simpleConnection);            unicodeNormalizationCommand.setSession(userSession);            unicodeNormalizationCommand.setNormalizationType(SetUnicodeNormalizationCommand.NORMALIZATION_COMPOSED);            unicodeNormalizationCommand.execute();            }catch (CommandException e2) {
//                         }       }           public void setRegionProperties( )       {         //@@begin setRegionProperties()         dataRegion.setRegionCode("engUSA");         // Set the locale on data region         dataRegion.setLocale(new Locale("en", "US"));         // Set the name of data region         dataRegion.setName("US");         //@@end       }     public void setRepositoryInfo( java.lang.String repositoryName, java.lang.String userID, java.lang.String password )      {        //@@begin setRepositoryInfo()        this.repositoryName=repositoryName;        this.userName=userID;        this.password=password;            //@@end      }           public void getAuthenticatedRepositorySession( )     {       //@@begin getAuthenticatedRepositorySession()           try{               CreateRepositorySessionCommand repositorySessionCommand=new CreateRepositorySessionCommand(simpleConnection);               repositorySessionCommand.setRepositoryIdentifier(repositoryID);               repositorySessionCommand.execute();               repositorySession=repositorySessionCommand.getRepositorySession();                       AuthenticateRepositorySessionCommand authenticatedRepositorySession=new AuthenticateRepositorySessionCommand(simpleConnection);               authenticatedRepositorySession.setSession(repositorySession);               authenticatedRepositorySession.setUserName(userName);               authenticatedRepositorySession.setUserPassword(password);               authenticatedRepositorySession.execute();                       GetRepositorySchemaCommand repositroySchemaCommand=new GetRepositorySchemaCommand(simpleConnection);               repositroySchemaCommand.setSession(repositorySession);               repositroySchemaCommand.execute();               schema=repositroySchemaCommand.getRepositorySchema();                           }catch(CommandException e){
//                        }catch(Exception e){
//                        }               //@@end     }         public com.sap.mdm.ids.FieldId getFieldID( java.lang.String tableName, java.lang.String fieldCode )       {         //@@begin getFieldID()             return schema.getField(tableName,fieldCode).getId();             //@@end       }           public com.sap.mdm.ids.TableId getTableID( java.lang.String tableName )       {         //@@begin getTableID()         return schema.getTable(tableName).getId();         //@@end       }           public void searchRepository() {             //@@begin searchRepository()             ResultDefinition resultDef =                 new ResultDefinition(schema.getTable("Vendors").getId());             resultDef.addSelectField(schema.getField("Vendors", "Name").getId());             //resultDef.addSelectField(new FieldId(15));             FieldSearchDimension searchDimension =                 new FieldSearchDimension(                     schema.getField("Vendors", "Name").getId());             TextSearchConstraint constraint =                 new TextSearchConstraint("ABC", TextSearchConstraint.CONTAINS);             Search search = new Search(schema.getTable("Vendors").getId());             //search.addSearchItem(searchDimension,constraint);             RetrieveLimitedRecordsCommand limitedRecordsCommand =                 new RetrieveLimitedRecordsCommand(simpleConnection);             limitedRecordsCommand.setSearch(search);             limitedRecordsCommand.setSession(userSession);             limitedRecordsCommand.setResultDefinition(resultDef);             try {                 limitedRecordsCommand.execute();             } catch (CommandException e) {                 //                          }             //return limitedRecordsCommand.getRecords();             RecordResultSet recordSet = limitedRecordsCommand.getRecords();             String recordAsString = null;             String fieldValue = null;             for (int i = 0; i < recordSet.getCount(); i++) {                 recordAsString = "";                 FieldId[] returnedFields = recordSet.getRecord(i).getFields();                 for (int j = 0; j < returnedFields.length; j++) {                     if (recordSet                         .getRecord(i)                         .getFieldValue(returnedFields[j])                         .isNull()) {                         fieldValue = " |";                     } else {                         fieldValue =                             recordSet.getRecord(i).getFieldValue(returnedFields[j])                                 + "|";                     }                                         recordAsString += fieldValue;                     System.out.println(recordAsString);                 }             }         }                 public static void main (String[] args)                 {             Connection test=new Connection();             test.getConnection();             test.setRegionProperties();             test.setRepositoryInfo("Vendor1","Admin","mdm");             test.getAuthenticatedUserSession();             test.getAuthenticatedRepositorySession();             test.searchRepository();             test.closeconnection();              }

}

A Class worth exploring for handling special characters in MDM

2012-02-08T10:06:00.001-08:00

To my rescue came this class which is worth exploring when you have a situation like above

Class SetUnicodeNormalizationCommand

After you establish your connection to the server through API and Authenticate User Session ,you need to work with this class.

Connection to server would return an object of type ConnectionPool (call it connection)and UserSession authentication would return a string (call it session).Now write this piece of code

SetUnicodeNormalizationCommand cmd = new SetUnicodeNormalizationCommand(connection);

cmd.setSession(session);

cmd.setNormalizationType(SetUnicodeNormalizationCommand.NORMALIZATION_COMPOSED);

cmd.execute();

This class will keep the special characters retrieval intact.

How do you implement a MDM Connection Help Class?

2012-02-08T09:54:00.001-08:00

In the exmaple Master Data Data Read class we used another class, ZCL_MDM_CONN_POOL_ROOT, to establish the connection to MDM. This is just a reusable utility class that caches the API connection and contains logic to map the SAP logon langauge to the MDM Language.
The complete source code of this class can be downloaded here.
Class Properties:
Class Private Types:
Class Attributes:
Class Methods:

GET_MDM_CONNECTION

METHOD get_mdm_connection.
*@78\QImporting@  LANGUAGE  TYPE SYLANGU  DEFAULT SY-LANGU
*@78\QImporting@  UNAME TYPE SYUNAME  DEFAULT SY-UNAME
*@78\QImporting@  REPOSITORY  TYPE MDM_LOG_OBJECT_NAME
*@78\QImporting@  USE_CONNECTION_POOL TYPE BOOLEAN  DEFAULT ABAP_TRUE
*@7B\QReturning@  VALUE( API )  TYPE REF TO CL_MDM_GENERIC_API
*@03\QException@  CX_MDM_MAIN_EXCEPTION

  IF use_connection_pool = abap_true.
    DATA wa_api LIKE LINE OF api_cache.
    READ TABLE api_cache INTO wa_api
     WITH KEY language = language
              uname    = uname
              repository = repository.
    IF sy-subrc = 0.
****Cached Connection Record is found, make sure the API reference is bound
      IF wa_api-api IS BOUND.
        api = wa_api-api.
        GET TIME STAMP FIELD wa_api-last_access.
        MODIFY TABLE api_cache FROM wa_api.
      ELSE.
****Not bound - Delete the Connection Record and Create a New Instance
        DELETE api_cache WHERE language   = language
                           AND uname      = uname
                           AND repository = repository.
        api = zcl_mdm_conn_pool_root=>create_mdm_connection(
             language            = language
             uname               = uname
             repository          = repository
             use_connection_pool = use_connection_pool ).
      ENDIF.
    ELSE.
****No Cached Record - Create a New Instance
      api = zcl_mdm_conn_pool_root=>create_mdm_connection(
           language            = language
           uname               = uname
           repository          = repository
           use_connection_pool = use_connection_pool ).
    ENDIF.
  ELSE.
****By Pass the Connection Pool and create a one-off Instance
    api = zcl_mdm_conn_pool_root=>create_mdm_connection(
         language            = language
         uname               = uname
         repository          = repository
         use_connection_pool = use_connection_pool ).
  ENDIF.

ENDMETHOD.

CREATE_MDM_CONNECTION

METHOD create_mdm_connection.
*@78\QImporting@  LANGUAGE  TYPE SYLANGU  DEFAULT SY-LANGU
*@78\QImporting@  UNAME TYPE SYUNAME  DEFAULT SY-UNAME
*@78\QImporting@  REPOSITORY  TYPE MDM_LOG_OBJECT_NAME
*@78\QImporting@  USE_CONNECTION_POOL TYPE BOOLEAN  DEFAULT ABAP_TRUE
*@7B\QReturning@  VALUE( API )  TYPE REF TO CL_MDM_GENERIC_API
*@03\QException@  CX_MDM_MAIN_EXCEPTION

  DATA mdm_language                 TYPE mdm_cdt_language_code.
  mdm_language =  zcl_mdm_conn_pool_root=>expand_mdm_language( language ).

**** Instantiate the API with our repository key from the dialog
  CREATE OBJECT api
    EXPORTING
      iv_log_object_name = repository.
****Connect to the Repository
  api->mo_accessor->connect( mdm_language ).

  IF use_connection_pool = abap_true.
    DATA wa_api LIKE LINE OF api_cache.
    wa_api-api = api.
    wa_api-language = language.
    wa_api-uname    = uname.
    wa_api-repository = repository.
    GET TIME STAMP FIELD wa_api-last_access.
    INSERT wa_api INTO TABLE api_cache.
  ENDIF.

ENDMETHOD.

EXPAND_MDM_LANGUAGE

METHOD expand_mdm_language.
*@78\QImporting@  LANGUAGE  TYPE SYLANGU  DEFAULT SY-LANGU  Language Key of Current Text Environment
*@7B\QReturning@  VALUE( MDM_LANGUAGE ) TYPE MDM_CDT_LANGUAGE_CODE  MDM: CDT language code

  CASE language.
    WHEN c_english.
      mdm_language-language = 'eng'.
      mdm_language-country  = 'US'.
      mdm_language-region   = 'USA'.
    when c_german.
      mdm_language-language = 'ger'.
      mdm_language-country  = 'DE'.
*     mdm_language-region   = 'USA'.
    WHEN OTHERS.
****Use the repository Default
      CLEAR mdm_language.
  ENDCASE.

ENDMETHOD.

How do you implement the processing for Master Data Read Class Parameters?

2012-02-08T09:53:00.001-08:00

In the example Master Data Read Class that we have been looking at, the processing is generic. In other words there is no statement in the application coding that specifies the MDM Repository, Table or Field name. The values are supplied via parameters so that this same class can be used for more than one Master Data Characteristic.
You can see the area where you can supply these parameters in the following screen shot. It is the field labeled Master Data Read Class Parameters:
Although this is a single field, it can hold more than one value. This is done by associating a data dictionary structure with the parameter inside the coding o the Master Data Read Class. For the purposes of MDM Integration, you probably want a structure something like the one used this example implementation:
This way when you click on the pencil icon next the parameter field, a dialog pops up with the individual field selections as defined by your structure. This even supports value input help for the individual fields.
So, how can this functionality be built into the Master Data Read Class? It requires the implementation of another interface in your class - IF_RSMD_RS_GENERIC. The sample Master Data Read Class, which can be downloaded here, contains an implementation of this interface for the purposes of processing the MDM Repository, Table and Field as parameters.
In the Method GET_STRUCTURE_NAME, you must specify the name of the data dictionary sturcture you are going to use:
```
method if_rsmd_rs_generic~get_structure_name.
  e_struct_name =  'ZRSMD_RS_S_MDM'.
endmethod.
```

But the most important processing are the GET and SET Methods. This is where you must supply the logic to map the data from the single parameter string into the individual fiels of your structure and vise versa:

method if_rsmd_rs_generic~get_parameter.
  field-symbols: <l_s_struc> type zrsmd_rs_s_mdm.
  assign e_r_struc->* to <l_s_struc>.
  <l_s_struc> = o_s_gendomain.
endmethod.

method if_rsmd_rs_generic~set_parameter.
  field-symbols: <l_s_struc> type zrsmd_rs_s_mdm.
  assign i_r_struc->* to <l_s_struc>.
  o_s_gendomain = <l_s_struc>.
endmethod.

method if_rsmd_rs_generic~get_parameterstring.
  data: l_parameterstring type rsmdrclpa.

*===Create the paramater string from the generic table structure===
  l_parameterstring+0(32)  = o_s_gendomain-object_name.
  l_parameterstring+32(34) = o_s_gendomain-table .
  l_parameterstring+66(34) = o_s_gendomain-query_field.

*===Export the parameter string====
  e_parameterstring = l_parameterstring.
endmethod.

method if_rsmd_rs_generic~set_parameterstring.
  data: l_parameterstring type rsmdrclpa.

  l_parameterstring = i_parameterstring.
*===Create the structure from the parameterstring===
  o_s_gendomain-object_name = l_parameterstring+0(32).
  o_s_gendomain-table       = l_parameterstring+32(34).
  o_s_gendomain-query_field = l_parameterstring+66(34).
endmethod.

How do you implement the Master Data Read Class?

2012-02-08T09:52:00.001-08:00

Master Data Read Classes have one basic requirement - They must implement the IF_RSMD_RS_ACCESS interface.
There are several examples of how implement a Master Data Read Class provided by SAP - like CL_RSMD_RS_GENERIC_DOMAIN and CL_RSMD_RS_GENERIC_TABLE. For creating your own custom Master Data Read Class, it probably makes sense to start by copying from one these existing classes and only adjusting for your specific processing.
The complete source code (in SAPlink format) for an example implementation of a Master Data Read Class that uses MDM and the MDM ABAP APIs can be downloaded from here.
Of all the methods in the sample class the most important from the standpoint of the MDM integration is the GET_TEXT method. The example implementation supports the retrieval of STRING or INTEGER based supporting values for a given key from MDM:

METHOD if_rsmd_rs_access~get_text.

  DATA: object_name    TYPE mdm_log_object_name,
        table          TYPE mdm_table_code,
        query_field    TYPE mdm_field_code,
        l_s_chavlinfo  TYPE rsdm_s_chavlinfo,
        l_not_assigned TYPE rs_txtlg,
        l_initial_val  TYPE rsd_chavl.

  object_name = o_s_gendomain-object_name.
  table       = o_s_gendomain-table.
  query_field = o_s_gendomain-query_field.


  DATA lt_result_set_definition TYPE mdm_field_list_table.
  DATA ls_result_set_definition LIKE LINE OF lt_result_set_definition.
  DATA lt_result_set            TYPE mdm_result_set_table.
  DATA ls_result_set            LIKE LINE OF lt_result_set.
  DATA lt_result_set2            TYPE mdm_result_set_table.
  DATA ls_result_set2            LIKE LINE OF lt_result_set2.
  DATA ls_remote_key_filter     TYPE mdm_client_system_key_query.
  DATA api                      TYPE REF TO cl_mdm_generic_api.
  DATA language                 TYPE mdm_cdt_language_code.
  DATA keys                     TYPE mdm_keys.
  DATA exception                TYPE REF TO cx_mdm_main_exception.
  FIELD-SYMBOLS <field_value>   TYPE ANY.
  FIELD-SYMBOLS: <wa_field>      TYPE mdm_cdt_text,
                 <wa_string>     TYPE string,
                 <wa_integer>    TYPE mdm_gdt_integervalue,
                 <wa_taxonomy>   TYPE mdm_taxonomy_entry,
                 <wa_int>        TYPE mdm_gdt_integervalue.
  TYPE-POOLS: mdmif.

  TRY.

    DATA wa_cache LIKE LINE OF me->data_cache.
    READ TABLE data_cache INTO wa_cache
     WITH KEY object_name = object_name
              table       = table
              query_field = query_field.
    IF sy-subrc = 0.
      keys          = wa_cache-keys.
      lt_result_set = wa_cache-lt_result_set.
    ELSE.

      api = zcl_mdm_conn_pool_root=>get_mdm_connection( repository = object_name ).

      DATA: result_set TYPE mdm_search_result_table.
      CALL METHOD api->mo_core_service->query
        EXPORTING
          iv_object_type_code = table
*         iv_hits_max         = 1
        IMPORTING
          et_result_set       = result_set.

****The results of a query only return the record keys - no details
****We then have to use a call to the method RETRIEVE to read
****the record details.
      DATA: result TYPE mdm_search_result.
      READ TABLE result_set INDEX 1 INTO result.
      IF sy-subrc = 0.
        keys = result-record_ids.
      ENDIF.

      CHECK keys IS NOT INITIAL.
****We only need the output field we are interested read from MDM
****By using the result_set_definition parameter, we can control this
****and only retrieve that single column
      ls_result_set_definition-field_name = query_field.
      APPEND ls_result_set_definition TO lt_result_set_definition.
      CALL METHOD api->mo_core_service->retrieve
        EXPORTING
          iv_object_type_code      = table
          it_result_set_definition = lt_result_set_definition
          it_keys                  = keys
        IMPORTING
          et_result_set            = lt_result_set.

      CLEAR wa_cache.
      wa_cache-object_name   = object_name.
      wa_cache-table         = table.
      wa_cache-query_field   = query_field.
      wa_cache-keys          = keys.
      wa_cache-lt_result_set = lt_result_set.
      APPEND wa_cache TO data_cache.
    ENDIF.

*===Get the Initial Value Text===
    CALL METHOD _textpool_read
      EXPORTING
        i_repid = 'SAPLRSDM'
        i_key   = '001'
      IMPORTING
        e_text  = l_not_assigned.

    FIELD-SYMBOLS: <wa_result> LIKE LINE OF lt_result_set.
    FIELD-SYMBOLS: <wa_pair>   TYPE mdm_name_value_pair,
                   <wa_key>    LIKE LINE OF keys.

*===Append the text values in c_t_chavlinfo===
    DATA: tabix TYPE sy-tabix.
    DATA  l_integer TYPE mdm_gdt_integervalue.
    FIELD-SYMBOLS: <l_s_chavlinfo> TYPE rsdm_s_chavlinfo.
    LOOP AT c_t_chavlinfo ASSIGNING <l_s_chavlinfo>
        WHERE i_read_mode = rsdm_c_read_mode-text.
      CLEAR <l_s_chavlinfo>-c_rc.
      IF <l_s_chavlinfo>-c_chavl IS INITIAL
         OR <l_s_chavlinfo>-c_chavl EQ rsd_c_initial
         OR <l_s_chavlinfo>-c_chavl < 1.
        <l_s_chavlinfo>-e_chatexts-txtsh = l_not_assigned.
        <l_s_chavlinfo>-e_chatexts-txtmd = l_not_assigned.
        <l_s_chavlinfo>-e_chatexts-txtlg = l_not_assigned.
      ELSE.
        l_integer = <l_s_chavlinfo>-c_chavl.
        READ TABLE keys ASSIGNING <wa_key> FROM l_integer.
        tabix = sy-tabix.
        READ TABLE lt_result_set ASSIGNING <wa_result> INDEX tabix.
        IF sy-subrc = 0.
          READ TABLE <wa_result>-name_value_pairs ASSIGNING <wa_pair>
            WITH KEY code = query_field.
          IF sy-subrc = 0.
****The data for the column could be one of various data types
****The value itself is returned as TYPE REF TO DATA and must
****be cast into a more specific data type before it can be processed.
            CASE <wa_pair>-type.
              WHEN 'STRING'.
                ASSIGN <wa_pair>-value->* TO <wa_string>.
                WRITE <wa_key> TO l_s_chavlinfo-c_chavl LEFT-JUSTIFIED.
                <l_s_chavlinfo>-e_chatexts-txtsh = <wa_string>.
                <l_s_chavlinfo>-e_chatexts-txtmd = <wa_string>.
                <l_s_chavlinfo>-e_chatexts-txtlg = <wa_string>.
              WHEN 'INTEGER'.
                ASSIGN <wa_pair>-value->* TO <wa_integer>.
                WRITE <wa_key> TO l_s_chavlinfo-c_chavl LEFT-JUSTIFIED.
                <l_s_chavlinfo>-e_chatexts-txtsh = <wa_integer>.
                <l_s_chavlinfo>-e_chatexts-txtmd = <wa_integer>.
                <l_s_chavlinfo>-e_chatexts-txtlg = <wa_integer>.
            ENDCASE.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDLOOP.
  ENDTRY.
ENDMETHOD.

Connectivity - BI-MDM Integration

2012-02-08T09:51:00.001-08:00

BI/MDM Frequently Asked Questions

General Questions

What types of BI/MDM Integration Scenarios are possible?
There are two main types of BI/MDM Integration Scenarios that are currently being rolled out to customers. The first scenario starts with existing data in BI and uses that as the starting point to generate and populate an MDM Repostiory. The second type is integration during the BI data staging.

How does the Data Staging scenario work?
There are actually two types of the data staging scenario. In each scenario, customers can use existing functionality with BI to access details from MDM to supplement the data that is being loaded into BI. An example might be a feed from an ERP system to a BI system. In this feed there might just be a master data key, like customer number. However using access to MDM, details about this customer, like their sales region, can be read and stored in the BI system or used at runtime inside BI queries.

What technology is necessary for the Data Staging Scenario?
The data staging scenario utilizes the MDM ABAP API to be able to read directly from MDM (in realtime) using ABAP coding. A good overview of the MDM ABAP API in general is a requirement for starting this scenario. Also anyone interested in implementing this scenario should study this video. The video shows the basics of setting up the MDM ABAP API all the way through implementing one of the data staging scenarios.

How do you use the MDM API during a Data Load?
For this situation you need to create an ABAP routine as the transformation rule type.

During the editing of the Rule Type, you can choose Routine. You then can custom code an ABAP Routine that reads data from MDM using the MDM ABAP API.

How do you use the MDM API for building a Remote Master Data Characteristic?
This scenario is a little less "free form" than the data loading routine. Here you use the existing BI functionality for master data characteristics and simply supply a custom implementation for the characteristic.
As you maintain the characteristic, from the Master data/texts tab, you can choose a Master Data Read Class. For this you create and then use a class special suited to reading the master data values from MDM.

Connectivity - BI-MDM Integration

2012-02-08T09:48:00.001-08:00

BI/MDM Frequently Asked Questions

General Questions

What types of BI/MDM Integration Scenarios are possible?
There are two main types of BI/MDM Integration Scenarios that are currently being rolled out to customers. The first scenario starts with existing data in BI and uses that as the starting point to generate and populate an MDM Repostiory. The second type is integration during the BI data staging.

How does the Data Staging scenario work?
There are actually two types of the data staging scenario. In each scenario, customers can use existing functionality with BI to access details from MDM to supplement the data that is being loaded into BI. An example might be a feed from an ERP system to a BI system. In this feed there might just be a master data key, like customer number. However using access to MDM, details about this customer, like their sales region, can be read and stored in the BI system or used at runtime inside BI queries.

What technology is necessary for the Data Staging Scenario?
The data staging scenario utilizes the MDM ABAP API to be able to read directly from MDM (in realtime) using ABAP coding. A good overview of the MDM ABAP API in general is a requirement for starting this scenario. Also anyone interested in implementing this scenario should study this video. The video shows the basics of setting up the MDM ABAP API all the way through implementing one of the data staging scenarios.

How do you use the MDM API during a Data Load?
For this situation you need to create an ABAP routine as the transformation rule type.

During the editing of the Rule Type, you can choose Routine. You then can custom code an ABAP Routine that reads data from MDM using the MDM ABAP API.

How do you use the MDM API for building a Remote Master Data Characteristic?
This scenario is a little less "free form" than the data loading routine. Here you use the existing BI functionality for master data characteristics and simply supply a custom implementation for the characteristic.
As you maintain the characteristic, from the Master data/texts tab, you can choose a Master Data Read Class. For this you create and then use a class special suited to reading the master data values from MDM.

What is the MDM ABAP API?

2012-02-08T09:44:00.001-08:00

What is the MDM ABAP API?

Historically most ERP based master data resides in existing ABAP Systems. Also the majority of the business logic in that is consuming the master data also resides in ABAP based systems. Therefore it makes sense to extend the accessiblity of SAP NetWeaver MDM to allow for easy accessiblity from ABAP.

That is the goal of the MDM ABAP API (MDM4A). MDM4A takes the same read, modify, search, and Administrative functionalities of the established COM and Java APIs (MDM4J) and brings them to the ABAP World.

By using MDM4A, ABAP developers do not have to learn the SAP NetWeaver MDM specific data types. MDM4A does the job of mapping all the data types and structures for the developer. It translates the structures such as data arrays into ABAP constructs like Internal Tables.

MDM also takes a different approach to passing language specific data. It might be important to note that all the data is passed through MDM4A via Unicode (UTF-8) regardless of the settings in the AS-ABAP system (Unicode vs. Non-Unicode). The MDM4A layers also do all the work of translating this data into the code page of the current system. Even on Unicode systems, a translation from UTF-8 to UTF-16 must occur.

What is the Architecture of MDM4A?

2012-02-08T09:43:00.001-08:00

What is the Architecture of MDM4A?

MDM4A is made up of three major parts:

Generic API
Provider Framework
C-Kernel

The Generic API is a release independent interface into the SAP NetWeaver MDM API. It is the only layer that application developers should ever directly interact with. It is comprised of publically available Function Modules and Classes.

The Provider Framework is the release specific implementation of the SAP NetWeaver MDM API. As new releases or support packages of MDM are released, new matching version fo the provider framework will be created.

However the features of the provider framework are always abastracted by the Generic API, causing the least amount of changes to the consuming applications as possible. This protects the application developer from changes within MDM breaking their applications. The Provider Framework is not intended for direct access by SAP's Customers or Partners. The MDM 5.5 SP4 class for the provider framework is CL_MDM_PROVIDER_SP4_PL00.

The Generic API and the Provider Framework are both delivered as part of a SAINT Package (SAP Add-on installed into the system via transaction SAINT).

Finally there are new Kernel Libraries written in C that are an integrated part of the ABAP stack that provide the low level communication interface to MDM. The C-Kernel is an integrated part of the AS-ABAP Kernel. The file dw_mdm.dll is part of the core disp+work package of the Kernel and is installed into /usr/sap/<SID>/DVEBMGS<Instance Number>/exe just like the rest of the Kernel

What Codepage is used by MDM4A?

2012-02-08T09:42:00.003-08:00

What Codepage is used by MDM4A?

MDM4A is always a Unicode based interface regardless of the codepage used by the ABAP system. Althought a Unicode ABAP system is UTF-16, the MDM4A interface is UTF-8. Therefore regardless of the ABAP system codepage, a codepage conversion must take place. The codepage conversion is done within the inner layers of the MDM4A. However on non-Unicode ABAP systems if you attempt to process characters from MDM that are outside your current codepage, this will produce a CX_SY_CONVERSION_CODEPAGE shortdump.

In non-Unicode ABAP systems, the best way to avoid such errors is to match the logon langauge of the ABAP system to the langauge used to connect to MDM.

DATA ls_language TYPE mdm_cdt_language_code.
ls_language-language = 'eng'.
ls_language-country  = 'US'.
ls_language-region   = 'USA'.
lr_api->mo_accessor->connect( ls_language ).

What causes the CRC Check Error?

2012-02-08T09:42:00.001-08:00

What does it mean when I receive the following error message:

Server return code 0x8002000E: File failed a crc check

This probably means that there is a mismatch between the release/patch level of the MDM Server and the ABAP API Add-In or Java API add-in (e.g MDMJAVAAPI04_0.sca).

Although a single ABAP system with the MDM API Add-In could potentially interface with multiple MDM Servers on different release levels, the ABAP MDM API Add-In release level/patch level must always match at least that of the most release level of any MDM Server it connects to. In other words, the ABAP side the MDM APIs (provided via an ABAP Add-In) is backwards compatible, but not forwards compatible.

Lets say for instance that you are running the MDM Server at 5.5 SP4 Patch 0. This would show up as something like 5.5.32.56 in the release level dialog on the MDM Server Console. Your ABAP system should have installed at least the same patch level. If you update your MDM Server to 5.5 SP4 Patch 1 (version 5.5.33.13), then patch one of the MDM ABAP API Add-on must be applied as well. Patches for the MDM ABAP API Add-on can be downloaded from the Service Marketplace.

You also need to make sure that your have configured the correct MDM Provider for your particular repository in the MDM Configuration with the ABAP System (Transaction MDMAPIC).

How do you use the Function Module-Based version of MDM4A?

2012-02-08T09:40:00.001-08:00

How do you use the Function Module-Based version of MDM4A?

There are function groups that map directly to the main Interfaces of the provider class. The processing logic is the same (the class-based interface is called from within the Function Modules). Several of the Key Function Modules are "Remote Enabled". Because they are remote enabled, they can also very quickly be generated into Web Services.

Function Group/Class Interface Mapping
FG_MDM_ACCESSOR = IF_MDM_ACCESSOR
FG_MDM_ADMIN_API = IF_MDM_ADMIN
FG_MDM_CONFIG_MONITOR = IF_MDM_API_CONFIG
FG_MDM_CORE_SERVICE_API = IF_MDM_CORE_SERVICES
FG_MDM_META_API = IF_MDM_META

How do you use the Class-Based version of MDM4A?

2012-02-08T09:39:00.001-08:00

How do you use the Class-Based version of MDM4A?

For all class-based access to MDM4A you only interact with the object CL_MDM_GENERIC_API. Internally the Abstract Provider will be instantiated with the release specific provider. All access to the functionality of MDM4A is done through the instances of the main group of Interfaces exposed by the Generic API

The object CL_MDM_GENERIC_API has attributes that hold object references to the 5 major parts of the API:

IF_MDM_ACCESSOR
This interface controls the opening and closing of a connection to a repository.
For many of the other API Methods, you must first have created a connection to a repository via this interface.

IF_MDM_ADMIN
This interface provides access to Admin functions similar to those available via the MDM Console. It includes User (creation, password set, role maintenance) and Repository (Mount or Load Repositories) Administration.

The IF_MDM_ADMIN interface poses an interesting situation. Many of the functions here could be automated and then batch scheduled using the local ABAP Scheduler or the Netweaver Central Scheduler by Redwood. It would also be quite easy to use IF_MDM_ADMIN to batch create users (based upon their existence or role assignment in AS-ABAP) for the MDM Server.

IF_MDM_API_CONFIG
This interface allows you to read the configuration entries from Transaction MDMAPIC for one repository or all of them at once. See the Data Dictionary structures MDM_REPOSITORY, MDM_CONNECTION, MDM_DBMS, and MDM_PROVIDER for the data supplied by this Interface.

IF_MDM_CORE_SERVICES
This is the main interface to directly manipulate the data within a repository.
It includes Check In/Out, Client System Keys, Update, Delete, Creation, and Query of data.

Many of the Core Services have a second method that ends in _SIMPLE. For instance there is UPDATE and UPDATE_SIMPLE. The "Simple" methods accept data dictionary structures that match the format of the repository table that you want to manipulate. This provides an easier interface into the API but requires the creation of a matching structure in the ABAP Data Dictionary.

The field names in the ABAP Data Dictionary Structure must be the same as the Name in the MDM Repository (case-sensitive). You are also restricted to only using the MDM API Data Types. Keep in mind that in ABAP there is no NULL state for a value. Any NULL value from MDM will be returned through the simple data types using the initial value for the underlying Data Dictionary Domain. Use of the specific methods instead of the SIMPLE ones will avoid this issue.

IF_MDM_META
This interface provides methods that allow you to change the metadata of a repository. Many of these methods require that the repository be unloaded before they can be performed.

How do you configure the connection to MDM from ABAP?

2012-02-08T09:38:00.003-08:00

How do you configure the connection to MDM from ABAP?

All Configuration is done from Transaction Code MDMAPIC and is broken into 5 main sections:

MDM Repositories
MDM Server Connections
MDM DBMS Hosts
ABAP Implementation for MDM Version Support
MDM API Trace Configuration

All access via MDM4A is always done for a particular repository. The class based API is instantiated for a particular repository. You can not switch to a different repository within an instance. You must create a separate instance to access a different repository.

In all calls to the function module based API, the repository must be passed in through the mandatory parameter IV_LOG_OBJECT_NAME. Therefore all the configuration in MDMAPIC really revolves around the repository as its central object. Although we will create Server and Database configuration entries it is the Repository entry that drives all configuration through the API.

Server Configuration

First define the TCP/IP communication settings for connection to the MDM Server. Then enter the Server Hostname and the Port for communications. Typically the MDM server runs on Port 20005. The name in the MDM Connection field is arbitrary and only know to the ABAP side of the interface.

Be careful when defining the host name for systems that may have more than one hostname alias. During the connection to the repository via MDM4A, a list of all repositories and their hostname according to the MDM Server will be retrieved. The local customizing will be checked against this list. If the hostnames do not match, then the connection will be rejected. Therefore the use of IP addresses for the hostname is technically possible, but will always lead to a configuration mismatch and rejection.

DBMS Configuration

Repositories may reside on a DBMS that is a different physical system than the MDM server itself, therefore it needs its own configuration entry. The Drop Down Box for DB Type will show all support DBMS types. The name in the MDM DBMS field is arbitrary and only know to ABAP, much like the server name field in the Server Configuration.

ABAP Implementation for MDM Version

Different releases of SAP NetWeaver MDM may require technical differences in the Low Level Provider Class. This configuration will allow you to assign a provider class to a set of repository configuration settings. You must select a class that is derived from the Abstract class CL_MDM_ABSTRACT_PROVIDER. The class provided for SP04 is CL_MDM_PROVIDER_SP04_PL00.

Remember as a developer you should only program against the Generic API and not this lower level provider framework. Otherwise incompatible changes may be introduced by SAP during version changes that break your application coding. The Generic API will use this configuration in order to call the correct logic for the version of MDM that it must connect with.

MDM Repository

We tie all our config. together by specifying for a repository what server, DBMS, and Provider it should use. The Object name is arbitrary and only know to ABAP - although it is used as the key to read all the configuration. The MDM Repository must be the real repository name as it is displayed from the MDM Console.

How do I connect to a Repository using the Class-Based MDM4A?

2012-02-08T09:38:00.001-08:00

How do I connect to a Repository using the Class-Based MDM4A?

This is a simple example that only focuses on a few things: Instantiating the MDM4A, making a connection to a repository and exception handling.

DATA api             TYPE REF TO cl_mdm_generic_api.
DATA log_object_name TYPE mdm_log_object_name.
DATA language        TYPE mdm_cdt_language_code.
DATA exception       TYPE REF TO cx_mdm_main_exception.

log_object_name = 'API_CRUD_1'.
language-language = 'eng'.
language-country  = 'US'.  language-region   = 'USA'.

TRY.
    CREATE OBJECT api
      EXPORTING
        iv_log_object_name = log_object_name.
    api->mo_accessor->connect( language ).
****Do Something
    api->mo_accessor->disconnect( ).

  CATCH cx_mdm_usage_error INTO exception.
****Other Exceptions...
  CLEANUP.
    TRY.
        api->mo_accessor->disconnect( ).
      CATCH cx_root.
    ENDTRY.
ENDTRY.

IF NOT exception IS INITIAL.
  MESSAGE exception TYPE 'E'.
ENDIF.

LOG_OBJECT_NAME is initialized with the key for our repository customizing (from Transaction MDMAPIC). That is only value you have to specify. All the other connection information will be looked up for you by the MDM4A.

We create the instance of the MDM4A by calling the CREATE OBJECT for our instance of CL_MDM_GENERIC_API. We only must pass in the configuration key. You could still have configuration, authorization, or trusting errors; but these exceptions will not be thrown until we connect to the repository in the next step.

Through the API we have access to instances of all 5 of the major interfaces (MO_ACCESSOR=IF_MDM_ACCESSOR, MO_CORE_SERVICE=IF_MDM_CORE_SERVICE, MO_ADMIN=IF_MDM_ADMIN, MO_META=IF_MDM_META, and MO_API_CONFIG=IF_MDM_API_CONFIG). We use api->mo_accessor to establish a connection to our repository. It is this point where the first communication connection is made.

First a list of repositories is retrieved from the MDM Server. This list is matched against our configuration settings to make sure the configuration is correct. Next a connection to the repository is made. The current AS-ABAP User (SY-UNAME) is passed through the interface call without specifying a password. At this point the Trusted Status of the AS-ABAP Server is also checked against the MDM Server allow.ip/deny.ip configuration files.

All processing logic is left out of this example. At the point marked "Do Something" you would place the specific logic.

Once finished with processing, you should disconnect from the MDM server explicitly with a call to the Accessor method DISCONNECT. If you end your application without disconnecting, the connection will remain open until it is cleaned up after its timeout. This will tie up system resources on the MDM Server unnecessarily.

All of our logic is placed within a single TRY...ENDTRY block. That way all errors will trigger into a single exception block. Only one Exception is shown here to save space. There is one super exception that can be caught to get all possible MDM4A specific exceptions - CX_MDM_MAIN_EXCEPTION. Inheriting from this exception are 5 more specific exceptions: CX_MDM_KERNEL (Exceptions within the Kernel layer for the MDM4A), CX_MDM_NOT_SUPPORTED (Exceptions if a method is called that isn't supported by the current release-specific provider that you are using), CX_MDM_PROVIDER (Exceptions generated within the Provider Layer of MDM4A), CX_MDM_SERVER_RC_CODE (Exceptions generated on the MDM Server. The MDM Server specific Return Code and explanatory text are passed back through this exception), and CX_MDM_USAGE_ERROR (Exceptions produced by incorrect usage of an MDM4A interface).

It is important to note the use of the CLEANUP event within the TRY...CATCH Block. Regardless of what type of exception occurred, processing can not continue. However we still want to be sure to close the interface connection and free up the resources allocated to it. Therefore we also call the Accessor DISCONNECT here. This logic path only occurs if an exception is caught. If errors occur within this Disconnect, there isn't really anything that can be done about it therefore the logic catches all exceptions (CX_ROOT) and ignores them.

Finally we process an error message with the text from the exception with the last block of coding.

How does Authentication work in MDM4A?

2012-02-08T09:37:00.001-08:00

How does Authentication work in MDM4A?

All authentication between the MDM server and the ABAP system via the MDM4A requires a Server Trust relationship. The SAP NetWeaver MDM Server(s) must trust their AS-ABAP counterparts. Trusting is configured via two files on the SAP NetWeaver MDM server - allow.ip and deny.ip This files contain the IP addresses of the AS-ABAP systems that you want to control access from.

The Files allow.ip and deny.ip should normally be placed directly into the same folder that holds your mds.ini (MDM Server Configuration) file. However if you need to place them in a different location (perhaps a centralized network share) you can configure their location in the mds.ini file. Use the entry TrustFiles Dir=<directory> to specify this location.

Allow.ip and deny.ip must be flat, text only files.

It is possible to wildcard the entries in allow.ip and deny.ip using the * character. You can NOT just specify * to allow all possible IP addresses. You must at least specify one subnet --ie. at least 10.*

Instead of listing each IP address directly, users will most likely take advantage of the wildcard. If you want to allow access from all but a few IP address you can combine the allow.ip and deny.ip entries. For instance you may wish to allow all servers from the 192.168.0.* range. However their may be a single "unsafe" machine in this subnet. You could then place the IP address of this "unsafe" machine within the deny.ip file. This can be useful to keep development or test servers from accidentally updating data in a production repository.

Any IP address not found in the allow.ip file (or if no allow.ip file can be read) will cause all requests will be refused.

Comments can be placed in the allow.ip and deny.ip files using the # character in the first column.

Once the server trust relationship is established, authentication is quite simple. Because there is a trusting relationship, no passwords must be passed through MDM4A. The AS-ABAP user identity (SY-UNAME) will automatically be passed through the MDM4A interface. A repository user with the same ID must exist on the SAP NetWeaver MDM server side for a role to be assigned to the request. Alternatively, User Mapping is possible using the LDAP Connectivity of the SAP NetWeaver MDM Server.

How can I change the timeout parameter?

2012-02-08T09:36:00.001-08:00

You have exceeded the MDM ABAP API Communication timeout and recieved an error message, however your process does indeed take longer than the default time.

The timeout parameter is set and controlled by the ABAP side of the communication. The default value of the timeout is 30000 milliseconds. The timeout parameter is controlled by the ABAP Profile Parameter mdm/network_timeout. For more details see OSS Note 968804.

TIP ~ MDM ABAP-API ~ Things to Remember (for Starters)

2012-02-08T09:35:00.001-08:00

This is something I found with MDM ABAP APIs and thought to share. It will be quite old and small thing for experts but I guess still a little good for starters.

1. The *Table code* is case sensitive in MDM ABAP API. If you add *CUSTOMERS* in your console, please use *CUSTOMERS* only in the ABAP API program. Please do not use *Customers* or *customers. Another example is *Customer_MDM* , so dont use *Customer_mdm* etc.*

Works - Only Code of Table is case-sensitive: not Table Name.

Not Works - Code needs to be exact, its case-sensitive.

2. The User-ID is always capital since ECC uses caps for user-Id. Please use *MDMUSER* as console and not *mdmuser. *mdmuser* will give exception that *User is not found.**

Works - Only Name of User is case-sensitive!

Not Works - Name needs to be in capital letters, its case-sensitive.

Same is true for Table Fields as well.

In the end, its also a tip that Please Use the ABAP API How to Guides provided. I must admit that they are really helpful and even helped me in solving a simple customer requirement. Cheers !

SAP MDM Training-SAP MDM Tutorials,SAP MDM Jobs,SAP MDM Resumes-SAP MDM

Enterprise Master Data Management - A cross-system master data process for supplier

Applies to:

Summary

Author(s):

Cross system create supplier process

Implementation Steps

Using the inbound Business Partner Web Service

Customizing the governance process

Exchanging process context information between SAP Business Workflow and NetWeaver BPM

NetWeaver BPM implementation considerations

Summary

Search In a MDM Repository

Code to Get List of Validation in a Table

A Class worth exploring for handling special characters in MDM

SRM-MDM Catalog version compatibility

Purpose

Overview

Identifying the versions of your applications

Checking the compatibility of your applications

Solving the incompatibility of your applications

Related Content

Related Documents

Related Notes

Code to Get List of Validation in a Table

CreateRecordCommand Vs CreateRecordsCommand

Search In a MDM Repository

A Class worth exploring for handling special characters in MDM

How do you implement a MDM Connection Help Class?

How do you implement the processing for Master Data Read Class Parameters?

How do you implement the Master Data Read Class?

Connectivity - BI-MDM Integration

BI/MDM Frequently Asked Questions

General Questions

Connectivity - BI-MDM Integration

BI/MDM Frequently Asked Questions

General Questions

What is the MDM ABAP API?

What is the MDM ABAP API?

What is the Architecture of MDM4A?

What is the Architecture of MDM4A?

What Codepage is used by MDM4A?

What Codepage is used by MDM4A?

What causes the CRC Check Error?

How do you use the Function Module-Based version of MDM4A?

How do you use the Function Module-Based version of MDM4A?

How do you use the Class-Based version of MDM4A?

How do you use the Class-Based version of MDM4A?

How do you configure the connection to MDM from ABAP?

How do you configure the connection to MDM from ABAP?

Server Configuration

DBMS Configuration

ABAP Implementation for MDM Version

MDM Repository

How do I connect to a Repository using the Class-Based MDM4A?

How do I connect to a Repository using the Class-Based MDM4A?

How does Authentication work in MDM4A?

How does Authentication work in MDM4A?

How can I change the timeout parameter?

TIP ~ MDM ABAP-API ~ Things to Remember (for Starters)