The document describes three case studies demonstrating integration scenarios using SAP Cloud Platform Integration. The first case study involves sending a SOAP message containing a tweet to SAP CPI, filtering the tweet text, and sending it to an email. The second case study fetches employee data from an OData system, enriches it with product details, and transfers it to an FTP server. The third case study retrieves a text file from an FTP server, converts it to XML, routes it to either another FTP server or email depending on plant code values. All case studies successfully achieved their objectives of transferring and transforming data between different systems.

1. SAP CPI SPRINT-CASE
STUDY
NAME:- ARYAN SHARMA
EMPLOYEE ID:-
46294757
.

2. Business Case:- Send a SOAP message containing the Tweet to SAP CPI. SAP CPI will first
filter the message to extract the Tweet as text and then send it to the Mail.
Message Flow of the Interface:-
SOAP UI TOOL --->SAP CLOUD ---> FILTER ---> GROOVY SCRIPT ---> MAIL
PLATFORM
INTEGRATION
Pallets to implement the functionality
1. Sender Pallet:- The Sender Pallet is responsible for receiving data from the source system and initiating the
integration flow
2. Receiver Pallet:- The Receiver Pallet is responsible for sending the data to the destination system
2. Start Message and End Message :- The Start and End Message shapes are used to define the beginning and end of
an integration flow respectively.
3. Filter :- Extract information from an incoming message.
4. Groovy Script Pallet :- It is used to execute custom code written in the Groovy programming language for ex
Display PayLoad .
CASE STUDY 1 :- SOAP MESSAGE TO MAIL SCENARIO

3. Test Case
1. Sending the message from the SOAP UI:- The Tweet should reach to the required Mail in the
required format.
OUTPUT:-
CASE STUDY 1 :- SOAP MESSAGE TO MAIL SCENARIO
Result : - The SOAP message containing the Tweet is successfully delievered to
the mail.

4. Business Case:- Employee data of needs to be fetched from the OData system and put it on to the FTP server
Message Flow of the Interface:-
TIMER ---> SAP CLOUD ---> FETCH USER DATA ---> ENRICH USER DATA ---> FTP SERVER
PLATFORM FROM ODATA WITH PRODUCT DETAILS
INTEGRATION
Pallets to implement the functionality
1. Start Timer Pallet:- It is used to trigger an integration flow at a specific date and time.
2. Receiver Pallet:- The Receiver Pallet is responsible for sending the data to the destination system
3. Start Message and End Message : - The Start and End Message shapes are used to define the beginning and end of an integration flow
respectively.
4. Request Reply :- It is used to send a request to a destination system and wait for a response before proceeding with the integration flow
5. Message Mapping :- It is used to transform data from one format to another. It is a graphical tool that allows developers to create mapping rules
between different message formats.
6. Content Enricher : - It is used to enrich the content of a message by adding additional data from external sources.
7. Groovy Script Pallet : - It is used to execute custom code written in the Groovy programming language for ex Display PayLoad .
CASE STUDY 2 :- ODATA TO FTP SCENARIO

5. Test Case
1. The XML File should successfully reach the FTP Server containing all the Employee and product
details.
OUTPUT:-
CASE STUDY 2 :- ODATA TO FTP SCENARIO
Result : - The XML File containing the employee and product details is
successfully transferred to the FTP Server.

6. Business Case:- Fetch the text file containing Plantcode from FTP Server and transfer the file to appropriate
Location.
Message Flow of the Interface:-
FTP SERVER ---> SAP CLOUD ---> CONVERT DATA ---> CHECK CONDITION ---> MAIL OR
FTP SERVER
PLATFORM INTO XML FORMAT IN ROUTER
INTEGRATION
Pallets to implement the functionality
1. Start Timer Pallet:- It is used to trigger an integration flow at a specific date and time.
2. Receiver Pallet:- The Receiver Pallet is responsible for sending the data to the destination system
3. Start Message and End Message :- The Start and End Message shapes are used to define the beginning and end of an
integration flow respectively.
4. CSV TO XML CONVERTER :- This Pallet is used to convert text file into xml file.
5. Router :- The Router pallet is used to route incoming messages to different processing paths based on a set of conditions
CASE STUDY 3 :- FTP TO FTP,MAIL SCENARIO

7. Test Case
1. The Text File placed in the FTP Server should successfully be transferred into the required location
depending upon the Plantcode.
OUTPUT:-
CASE STUDY 3 :- FTP TO FTP,MAIL SCENARIO
Result : - The Text File containing the PlantCode is successfully
transferred to the appropriate Location.

8. With more than 190,000 people, Capgemini is present in over 40 countries and
celebrates its 50th Anniversary year in 2017. A global leader in consulting, technology
and outsourcing services, the Group reported 2016 global revenues of EUR 12.5 billion.
Together with its clients, Capgemini creates and delivers business, technology and
digital solutions that fit their needs, enabling them to achieve innovation and
competitiveness. A deeply multicultural organization, Capgemini has developed its own
way of working, the Collaborative Business Experience™, and draws on Rightshore®, its
worldwide delivery model.
About Capgemini
Learn more about us at
www.capgemini.com
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group.
Copyright © 2017 Capgemini. All rights reserved.
Rightshore® is a trademark belonging to Capgemini.
This message is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to
read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please
notify the sender immediately and delete all copies of this message.