R/3-XI-MDM (Outbound Scenario)

R/3-XI-MDM (Outbound Scenario)

This article will show you how to integrate SAP R/3 and Master Data Management (MDM) using PI in short framework. We will be discussing Outbound process i.e. Outbound to the SAP R/3

Figure Outbound to R/3
MDM Configuration Steps:
Step One-->Create Client System
Follow the same steps to create client system. Also we can use the same client system.
Step Two-->Create Port for Client System
Follow the same steps to create inbound port.
The Port Name is SIEBEL_IB_CUS_SIEBELCUS01, Code SIEBEL_IB_CUS_SIEBELCUS01, and Type as Inbound. See the figures below.

Figure Port for Inbound
MDM Server Side Configuration
In the SAP MDM Server, Look at the server folder structure for the Inbound folder which we have created in the MDM Console.

Figure MDM Server Folder
FTP Server Side Configuration
Step Three-->FTP Server Configuration
Configure/Specify the file folder path for pulling the file in FTP Server. This is screen refers the FTP server configuration (WS_FTP server)

Figure FTP Server
SAP XI / PI Side Configuration
Step Four --> SAP PI Receiver Communication Channel

Figure Receiver CC
Outbound Process Flow:

Figure Outbound Process Flow
>>>Here, I will be discussing Outbound process, the above figure shows the entire process
Process step in R/3
In this IDoc triggers to outbound port.
Process step in PI
The IDoc Communication Channel picks up in the PI System and starts the PI Process. In the PI, transformation and conversion happens and sends to the File Adaptor. The file adaptor pushes the file to the specified path in MDM server folder.
Process step in MDM
The Import Manager picks up the file which the file placed in server folder and imports the file to MDM repository main table.

I hope this blog will be useful for real time while integrating the same.

Note: don't forget to read the weblog MDM-XI-R/3 Integration for better understanding.

SAP MDM  Training

 

Enhancing the email experience via MDM & XI

Enhancing the email experience via MDM & XI

Introduction 

We all know MDM has the capacity to send e-mails using MDM workflow engine and the Notify step. I faced some peculiar requirements, very logical and practical, but found it very difficult to address them using only MDM. We can decide the recipients using Roles and Users in Notify step but can we change them dynamically? We can get some dynamism in the body of email but is that dynamism sufficient? What about sending attachments in email or formatting the email body to more readable and automated format?

 

MDM Mail engine can send emails but does it have enough dynamism, automation, functionalities to cater to advance requirements?

Some of them are as mentioned below. 

Requirements

Dynamism in subject line

One of the requirement was that the subject line of email must contain some details about the material like Material number and status in which workflow is. The subject line must contain the status of workflow. For eg: Approved by the Project Manager or Rejected by Project Manager based on the approval decision.

The MDM workflow engine does not allow dynamic changes in the subject line of the mail nor can we add any fields in it.

Dynamism in addressee (To and CC)

The next requirement was a very business oriented one. As any organization, the client had User-Manager hierarchy. The request raised by a particular user must be directed only to his manager. For different users, different managers email address must be populated in the To field.

In the Notify step, we can either send the email to a particular user (static) or to a Role in which case the mail will be sent to all users allocated to that Role.

How do we go about dynamically assigning the email address in the To field?

Dynamism in content of the mail

The content of the mail must be decided on the decision taken by the manager. For eg: if the manager approves a request, then the mail should contain the link for next action page else if rejected, the mail should contain reason for rejection. Depending on the scenario, the contents of the email should change.

In the Notify step, though we can bring in some amount of dynamism by adding fields of the records in it, we cannot decide the contents based on decisions made in previous step.

Mail content styling & attachments

The next requirement was more on the aesthetic look and feel of the email. The contents of the mail must be arranged in a proper tabular format. Dynamic links to portal pages must be given in the body of the email so that users can directly click on it get diverted to the required page for actions. An excel attachment containing the details of material must be sent alongwith the mail.

All these are not possible using MDM. 

Solution

Leverage MDM-XI integration and use XI mail server to send mails!

 

This can be achieved as shown below

   
Design Steps

1. Define Validations and Assignments to dynamically assign email address to fields in main table based on the user and his manager
2. Instead of Notify Step, use a combination of Assign and Syndicate step in the Workflow
3. Design and configure a Syndication map which will generate the xml file containing all the fields required in the mail
4. Configure XI to pick-up the generated file from the Outbound folder of the port
5. Perform field mapping in the File to Mail scenario of XI to arrange the MDM fields
6. Configure the XI mail server to send email to the recipients

Output

The result is a user friendly, formatted mail generated dynamically as shown below.

 sap mdm training