In this post, we will explore “SAP Cloud Platform Integration (CPI) Part 7 – Palette Functions 1“ and delve into the standard range of functions available in CPI. This will help you understand the various capabilities provided by the palette functions to enhance your integration scenarios.
Outline of this blog series:
- SAP CPI Introduction
- SAP BTP tools and features overview (BTP, Global Account, Sub-Account, Entitlements, Connectivity, Security)
- SAP CPI Web IDE overview
- Registering a trial account and enrolling to SAP CPI service
- Deep dive into Cloud Integration features with real world scenario example
- Use cases of palette functions
- Adapter configurations
- Using Cloud connector for connecting to backend SAP systems
- Overview on API Management & Open Connectors
- Integration using Open Connectors with real world example
In short, below is the content we will elaborate in this tutorial:
- Participants
- Process
- Events
- Connectors
- Delete
Today we are going to see about standard SAP offered palette functions in CPI.
- Participants
First palette function group we are going to see is the Participants group. In participants group, there are 2 palette functions:
Sender
Receiver
In the commonplace joining process, we can utilize numerous source and beneficiary. There are explicit properties that we can arrange in the shipper or collector member. When you interface the shipper or recipient to the beginning or any range (say, demand answer, send) you will be provoked to choose the connector.
2. Process:
There are 3 kinds of cycles accessible:
Reconciliation Cycle
Neighborhood Combination Interaction
Exemption Sub Cycle
Reconciliation Cycle:
This is the fundamental cycle that you will use for all the point of interaction improvements. It is required to have one incorporation cycle and one IFlow ought to contain just a single Primary mix process.
Neighborhood Coordination Interaction:
Neighborhood Coordination Interaction will be helpful when you have a complex IFlow or an IFlow where numerous (>25 or 35) ranges included. It is only utilized for parting primary coordination cycle to more modest lumps of cycles.
You can’t utilize Just nearby reconciliation process in IFlow, as having a fundamental mix process (as examined above) is an unquestionable requirement, You can have quite a few neighborhood joining process in an IFlow. You can call the nearby mix process in principal coordination process through another range capability, Cycle CALL.
In Cycle call range, you need to choose the neighborhood coordination process that you need to use in fundamental combination process. In Neighborhood coordination process, Shipper range can’t be utilized. Additionally Start or end message occasions can’t be utilized. In Nearby Coordination Cycle, just Beginning Occasion and End Occasion/Blunder End Occasion/End Occasion can be utilized.
The request for the above execution is: HTTPS Shipper – > Begin – > JSON to XML Converter – > Content Modifier 2 – > Interaction Call – > Begin occasion – > Content Modifier1 – > Message Planning – > End Occasion – > Back to deal with Call – > End Message.
Process call can be found in Call range bunch. Call – > Nearby Call – > Cycle Call.
Exemption Sub Interaction:
This is definitely not an obligatory cycle to be utilized in IFlow. As in the name recommends, it is utilized for catching the blunder messages and doing the important cycle from there on like mailing to business in regards to the disappointment. Like Nearby Reconciliation Interaction, we can’t have Source range and Begin message occasion. For Exemption sub process, we explicitly have Blunder Start Occasion and Mistake End Occasion/End Message.
Note: You can’t utilize Special case Sub Cycle independently in the curio supervisor as we accomplish for Nearby Coordination Cycle. It ought to be utilized inside the principal reconciliation stream or inside the nearby incorporation stream.
3. Events:
Occasions won’t be another subject, as we have seen them in the past segments. We have no particular design/properties to be arrangement if there should arise an occurrence of occasions (other than Start Clock occasion), rather every occasion has some particular trademark which must be utilized in specific condition as it were.
For e.g.: We can’t utilize Start and End message in Nearby Reconciliation Cycle and in Special case Sub Interaction.
There are 9 occasions in the Occasions range bunch:
Start Message
End Message
Start Event
End Event
Error Start
Error End
Start Timer
Terminate Message
Escalate End Event
Begin and End Message:
The Beginning Message and the End Message occasions are utilized when SAP Cloud Stage Combination gets a message from a Source and when SAP Cloud Stage Reconciliation makes an impression on a Beneficiary. Naturally, when you make a combination stream, the beginning and end message occasions are made accessible.
Blunder Start/End and Heightening End:
In the event of blunder end, the mistake reason isn’t sent back to source. The message simply flops in CPI. Though, if there should arise an occurrence of heightening end occasion, the mistake reason is sent back to source and the message goes to raised status in CPI. Blunder Start and Mistake End can be utilized exclusively inside a special case sub-process.
Begin and End occasion:
These two occasions can be just utilized in Nearby Combination Cycle.
End Message:
An End Message occasion stops further handling of a message. For instance, you have characterized explicit qualities on the payload. In the event that the payload doesn’t match those qualities, the cycle is ended. The message status showed in the message handling log is Finished, in light of the fact that it has ended the message effectively.
If you have any desire to show it as Mistake in CPI Message Checking logs, then rather than End Message occasion, supplant it with any of the underneath occasions:
Utilize a Mistake End occasion.
Utilize a Heightening End Occasion (sets a message status to Raised all things considered).
Clock:
Clock start is particularly helpful in situations where you have proceed to pull information from frameworks or need to set off Web administrations at determined time/stretches. The standard example of utilizing a clock is – A substance modifier followed by a clock. That is on the grounds that a clock doesn’t make payload ready to go. With a substance modifier, you can make the solicitation payload that can be shipped off the framework.
In the properties area, we have three choices:
Run Once – Each time you send the IFlow, the IFlow will get set off once.
Plan on Day – This choice will be helpful if you have any desire to plan on a particular day, each 10secs/1min/or any time.
Schedule to Recur – This option will enable user to schedule on daily/weekly/monthly basis.
4. Connectors:
Connectors are the arrow points which signifies the message stream in the any IFlow Reconciliation Cycle. Normally, we don’t involve Connectors in that frame of mind, rather we use it on tapping the range capability and hauling it to the objective range.
5. Delete:
Erase range is utilized when we need to erase any range that is inside any Coordination Interaction. As expressed before in Connectors, we ordinarily don’t erase from Range device bar, rather tapping on the range which you need to erase would toss us rundown of choices (like above screen capture) and tap on Erase.
I trust you have gained valuable insights today. In “SAP Cloud Platform Integration (CPI) Part 7 – Palette Functions 1,” we covered some key aspects of Palette functions. We will explore the remaining Palette functions in upcoming posts. Happy Learning!
YOU MAY BE INTERESTED IN
ABAP Applications for the Cloud: Modernizing for the Future
Mastering the Basics of SAP ABAP: A Comprehensive Guide
ABAP Development Environment in the Cloud
WhatsApp us