Send Mail to Vendor

8/6/2019 Send Mail to Vendor

1/39

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

2009 SAP AG

A Step-by-Step guide on SMTPConfiguration and File to MailScenario Using ProcessIntegration Scenario in PI 7.1

Applies to:

SAP NetWeaver Process Integration 7.1

For more information, visit theSOA Management homepage.

Summary

This document gives complete step-by-step procedures for implementing and testing a File-to-Mail scenariofrom scratch using the Business Systems in the Integration Directory (ID). The document also provides some

basic idea and working knowledge on how to configure SMTP. Some insight on TCodes- Profile Parameters(Transaction RZ10), User Maintenance (Transaction SU01), maintain services and assigning a client(Transaction SICF), SAPconnect Administration (Transaction SCOT)

So, this document can be treated as a ready reference in real life situations when working with Mail scenario.

Author: Sandeep Sharma

Company: HCL Technology Noida

Created on: 21 October 2009

Author Bio

Sandeep Sharma is working as a SAP NetWeaver Consultant for HCL Technology Noida

INDIA. He is SAP PI 7.0 certified developer. He is having a good experience in ALE/IDOC

also.
https://www.sdn.sap.com/irj/sdn/soa-managementhttps://www.sdn.sap.com/irj/sdn/soa-managementhttps://www.sdn.sap.com/irj/sdn/soa-managementhttps://www.sdn.sap.com/irj/sdn/soa-management


2/39

A Step-by-Step guide on SMTPConfiguration and File to Mail Scenario Using Process Integration Scenario in PI 7.1


2009 SAP AG

Table of Contents

Introduction ......................................................................................................................................................... 3Basic Concepts and Overview ............................................................................................................................ 3

Requirement Study and Scope Identification .................................................................................................. 3Prerequisites ....................................................................................................................................................... 4

Knowledge Requirements ............................................................................................................................... 4System Requirements ..................................................................................................................................... 4

Implementation Build Solution ......................................................................................................................... 41 SMTP Configuration guide............................................................................................................................... 4

1.1 Purpose ..................................................................................................................................................... 41.2 Prerequisites ............................................................................................................................................. 41.3 Process Flow ............................................................................................................................................. 4

1.3.1 Settings for the Profile Parameters (Transaction RZ10)...................................................................................... 41.3.2. User Maintenance (Transaction SU01) .............................................................................................................. 71.3.3. Assigning the Clients (Transaction SICF) .......................................................................................................... 91.3.4. SAPconnect Administration (Transaction SCOT) ............................................................................................. 11

2-File to Mail Scenario ...................................................................................................................................... 14

2.1 Enterprise Service Repository (Designing) ............................................................................................. 14Design Objects: .......................................................................................................................................................... 14

2.2. Integration Directory (Configuration) ...................................................................................................... 23Directory Objects: ...................................................................................................................................................... 23

2.3. Testing the Scenario (SXMB_IFR) ......................................................................................................... 352.4. Testing the Scenario (SXMB_MONI) ..................................................................................................... 36

Related Content ................................................................................................................................................ 38Disclaimer and Liability Notice .......................................................................................................................... 39


3/39



2009 SAP AG

Introduction

This guide gives you a clear IDEA and complete step by step procedures to be followed while implementingFile to Mail scenario. There are many blogs and articles on SDN for XI and PI 7.0 for mail scenario. Thisguide is especially for PI 7.1 users and also for those who want to learn how to configure SMTP.It becomesvery difficult for any beginner and Intermediate XI aspirants to implement such a scenario in PI 7.1 fromscratch. Hence, I have tried to come up with a complete solution and How to guide document to provide allsteps required implementing such a scenario from the very beginning. Hope this document will help all PI

professionals as a ready reference in real life situation while working with File and Mail PI scenario in crosscompany environment.

Happy Learning

Basic Concepts and Overview

As per general thumb rule to implement any XI scenario (like File - XI - File) we need to implement thefollowing:

In SLD: Create Product and Software Components with/without dependencies, TechnicalSystem and Business System for each (Sender and Receiver)

Tip: If we dont have sufficient information to create a Business System in SLD for Sender orReceiver then we can use Business Service in ID (Cross Company Environment).

In ESR: Import Software Components that we have created in SLD, Create Namespaces thenunder Interface Object we have to create Data type, Message Type, Service Interface and actions foreach (Sender and Receiver). After this we have to create Massage Mapping and Operation Mappingfor the scenario under Mapping Objects. Finally we have to create one process integration scenarioand activate all these objects we have created in ESR.

In ID: Create Communication Channels for (Sender and Receiver), then apply model from ESR andimport your process integration scenario which you have designed in ESR. Again we have to activateall these objects in ID.

Requirement Study and Scope Identification

Create two third party Business System in SLD for Sender and Receiver Systems .If you dont have sufficient

authorization to create it then you can ask your Basis team to create these for you or you can use BusinessService in ID like in any Cross Company Environment


4/39


5/39



2009 SAP AG

Configure the following two profile parameters:

A) icm/server_port_ = PROT=SMTP,PORT=

(this parameter opens a TCP/IP port for receiving mails through SMTP)

here stands for the sequence number (starting from zero)of

frequently occurring parameters. the number of the port that is to be used ( cant yet be used by another program on this

host.)

In my case here value of * (sequence number) is 2 and PORT = 25000


6/39



2009 SAP AG

B) is/SMTP/virt_host_ = :,,...;

This parameter defines a virtual mail host for receiving mails.

Heredescribes the name of the host to which the incoming mails are addressed.

describes the number of the port to which the incoming mails are addressed.

Note:1- This parameter is not required If one single client of the SAP system is receiving and processing allincoming mails).2-Default value for this parameter is/SMTP/virt_host_0 = *:*;3-In case of multiple clients, a virtual host has to be created for each of these clients.

In my example I have used *:25000 here * is used because I want the mails to be sentindependently of the host being addressed and 25000 is the value of PORT.


7/39



2009 SAP AG

1.3.2. User Maintenance (Transaction SU01)

Create a service user to process incoming mails

Call transaction SU01 to create a user with type Service and assign the profile S_A.SCON to this user.


8/39



2009 SAP AG

Click on create


9/39



2009 SAP AG

User addresses

Assign the valid Internet mail address to your user (which is supposed to receive e-mails) in transactionSU01, under E-Mailon the tab page Address.

1.3.3. Assigning the Clients (Transaction SICF)

One SMTP server (SAPconnect) has already been created in transaction SICF and is delivered with every

SAP system. Now Use this to create the first client and then create another SMTP server for each additionalclient. Run tcode SICF and enter the following details:

Press F8 . In the next screen double click on SAP connect


10/39



2009 SAP AG

Host data tab

Enter the sequence number of a parameter is/SMTP/virt_host_from the profile. If you have onlycreated one client and therefore have not specified this parameter type, enter 0.As shown in the figure:

Enter *:* in host configuration information.

Handler list

Enter CL_SMTP_EXT_SAPCONNECT at position 1.


11/39



2009 SAP AG

1.3.4. SAPconnect Administration (Transaction SCOT)

In this step, Define SAPconnect settings for the client that is to be used for send processes.

Run tcode SCOT

Under SettingsDefault Domain, define the domain of the SAP system client.

Each client has an SMTP node. This node is created by the SAP system and cannot be deleted. Thefollowing steps need to be carried out to configure the node so that sending Internet mail is possible:

1. First confirm that you are in the Nodeview, and then double click on that node name.2. Choose Node in use.

3. In the Mail Hostand Mail Portfields, specify the mail server to which the outbound mails are to besent.In my case , Mail Host = smtp.rediffmailpro.com (or you can use IP address also ) and MailPort = 25.

4. Next to Internet, click on set button and Enter the address area of the recipient addresses that are tobe reached using this node. In general, * is used if all e-mails are to be sent using SMTP.

5. Enter the output format for SAP documents and Confirm your selection


12/39



2009 SAP AG

Note: If you also want to configure the node for sending text messages (pager/SMS) or faxes, please follow thereference link given at the end of this document.


13/39



2009 SAP AG

Send Job (shift +F7)

E-mails sent from an SAP application are first stored in a queue. A periodical background process, theSAPconnect send job, gets the e-mails from this queue and sends them over the Internet. To schedule this

job in SAPconnect: Administration, proceed as follows:

Press shift+F7 or click on the job button as shown in the figure below:

1. Choose ViewJobs.

2. If no other job has been scheduled, choose JobCreate.

3. Enter a job name ( for ex: MailSend)and confirm it.

4. Select the variant SAP&CONNECTALL by positioning the cursor on it.

5. Choose ScheduleJob. In the next window, Choose Scheduleperiodically. Select the interval yourequire, such as 10 minutes. Choose Create.


14/39



2009 SAP AG

2-File to Mail Scenario

2.1 Enterprise Service Repository (Designing)

The first scenario that I am explaining is sending the file to the receiver through mail. File adapter will pick upthe file from FTP, do the simple 1 to 1 transformation and send the file to the receiver through mail.

The mail adapter is using the transport protocol as SMTP

Design Objects:

Data Types:

Create the two Data Types, one for the source and other for the target side.

Source Data Type:

The source data type contains the following fields FROM, TO and CONTENT as shown below.

Fig1. Source Data Type

Target Data Type:

Fig2.Target Data Type

Message Types:

Create the Message Type for both the data types as shown below.


15/39



2009 SAP AG

Source Message Type:

Fig3. Source Message Type

Target Message Type:

Fig4. Target Message Type

Message Interfaces:

Create the Message Interfaces for the above message types as shown below.


16/39



2009 SAP AG

Outbound Message Interface:

Fig5. Outbound Service Interface


17/39



2009 SAP AG

Inbound Message Interface:

Fig6. Inbound Service Interface


18/39



2009 SAP AG

Message Mapping:

Create the Message Mapping between the source message type and the target message type as shownbelow.

Fig7. Message Mapping

Operation Mapping:

Create the Interface Mapping between the outbound and inbound interface as shown below.

Fig8. Operation Mapping


19/39



2009 SAP AG

Actions:

Create two actions for source service interface and the target service interface as shown below.

Fig9. Source action

Fig10. Target action


20/39



2009 SAP AG

Process Integration Scenario:

Create a process integration scenario as shown below

1. Right click and insert your sender component. In my example it is SAMPLE_TEST_SCENARIO 1.0

2. Again right click and insert your receiver component. In my example again it isSAMPLE_TEST_SCENARIO 1.0

3. Right click on first component and click on insert action. Here assign your sender action. In this

example it is FileSender. Or you may drag and drop this action.

4. Now right click on second component and click on insert action. Here assign your receiver action. Inthis example it is Mailreceiver. Or you may drag and drop this action.

5. Now click on sender action (FileSender) press shift button on keyboard and then click on receiveraction (Mail receiver) both will be highlighted. release shift button and then right click and selectoption create connection between selected actions

Fig11. Action connection


21/39



2009 SAP AG

Double click on the mid of arrow, a new window will open,


22/39



2009 SAP AG

Click on assign mapping and assign the mapping using drop down menu.

Save and activate all your objects. Your ESR part is completed


23/39



2009 SAP AG

2.2. Integration Directory (Configuration)

Directory Objects:

Create the Business Scenario and create the sender business service (MAIL_SND) and receiver businessservice (MAIL_RCV).Assign sender and receiver Interface to both service. Assign these services to yourbusiness scenario.

Sender Communication Channel:

Create the sender communication channel of Adapter type as File.

Select the Transport Protocol as FTP.


24/39



2009 SAP AG

Fi12. Sender Communication Channel


25/39



2009 SAP AG

Receiver Communication Channel:

Create the Receiver communication channel of Adapter type as MAIL.

Fig13. Receiver Communication Channel


26/39



2009 SAP AG

Now go to tools tab and apply model from ESR

Fig14. Apply ESR model

In the wizard, Fill the details of process integration scenario which you have created in ESR

Fig15. Wizard step1


27/39



2009 SAP AG

Click on continue

Fig16. Wizard step2

Click on finish

Fig17. Wizard finish

Click on close


28/39



2009 SAP AG

A new window will open

Fig18. Model Configurator


29/39



2009 SAP AG

Click on sender action (FileSender) and assign communication component

Fig19. Assign component in Model Configurator


30/39



2009 SAP AG

Again click on receiver action (MailReceiver) and assign communication component

Fig20. Assign component in Model Configurator


31/39



2009 SAP AG

Now click on the arrow connecting two actions and assign the communication channels.

Fig21. Assign channel in Model Configurator


32/39



2009 SAP AG

Click on simulation button (4th

button in the above screen shot) and select Generation Simulation radio button

Fig22. Simulation

Click on start

After simulation new window will popup close that and again click on the simulation button.


33/39



2009 SAP AG

This time select radio button Generation

Fig23. Simulation generation


34/39


35/39



2009 SAP AG

2.3. Testing the Scenario (SXMB_IFR)

1- Open RWB->component Monitoring->Display->Integration Engine->Test Message

Fill up the details as below and also take your payload from ESR message mapping with some testvalues. Paste that payload here in test message.

Fig25. Test RWB

Click on send message. Now you can check the message in SXMB_MONI.

2- Alternatively you can test the scenario by putting the file MAIL.TXT on your FTP. After some time file

will be deleted from FTP


36/39



2009 SAP AG

2.4. Testing the Scenario (SXMB_MONI)

To Test the scenario put the file MAIL.TXT on your FTP. After some time file will be deleted from FTP

Message in SXMB_MONI is shown below.

Fig26. Message in SXMB_MONI


37/39



2009 SAP AG

You will receive a mail in your box like the screenshot below:

Fig27. Message in Inbox


38/39



2009 SAP AG

Related Content

SMTP configure

http://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htm

http://help.sap.com/saphelp_nw04/Helpdata/EN/6b/4493404f673028e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htmhttp://help.sap.com/saphelp_nw04/Helpdata/EN/6b/4493404f673028e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_nw04/Helpdata/EN/6b/4493404f673028e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_nw04/Helpdata/EN/6b/4493404f673028e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/frameset.htm


39/39


Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.

Documents

Send Mail to Vendor