Name: Configuring Events Setup - SAP Customer Data Platform
Uploaded: 2023-4-11
Duration: 535 s
Description: In this video, we are going to ingest Customer Data by setting up an Event in the SAP Customer Data Platform. You can view the documentation on the SAP Help Portal for more details:Configure Source Applications Events | SAP Help Portal

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div>In this video, we are going to ingest Customer Data by setting up an Event in the SAP Customer Data Platform.  <br><br><p>You can view the documentation on the SAP Help Portal for more details:<br><a href="https://help.sap.com/docs/customer-data-platform/main/configure-source-applications-events?q=data%20ingestion" rel="nofollow noopener noreferrer" target="_blank">Configure Source Applications Events | SAP Help Portal</a></p></div></div></div>

Configuring Events Setup - SAP Customer Data Platform

In this video, we are going to ingest customer data by setting up an event in the SAP Customer Data Platform  After logging in into SAP CDP, hover your mouse over the hamburger menu on the top-left side. Click on Sources under the Connect group. You’ll be presented with a list of Application Sources.  Click on the arrow next to one we created.  We’ll define two events for this source:  one to ingest bookstore profile data  and another to ingest bookstore viewed books data.  Let's start with the former.  Click on Create New Event,  and now you’ll be presented with a new screen for setting up the event.  Enter a name such as bookstore profile data ingestion.  In Data Type, select Offline Data,  and set both Required and Granted Processing Purposes as the previously created BookViewTrackingData.  You can select multiple processing purposes for these fields, but in this demo we’re using only this one.  Granted Processing Purposes defines which processing purposes are applied to the data imported by this event upon its first data ingestion.  Required Processing Purposes allows the data to be updated only if the ingested data is already granted with the processing purposes you selected in this field.  For Read File Path, type in sources as the name of the folder where our bookstore json files reside inside the S3 bucket.  In Filename Regex, enter the following expression which matches the previously explained filename template.  Note that this expression needs to match the filename 100%, including file extension, otherwise CDP skips the file while ingesting.  In ‘File Format to Read’, make sure json is selected as Format. Click next to proceed to the Model step.  Now, we’ll setup the schema used by our source json file contents to let SAP CDP know the format of the data we’re importing into the system. Click on Create Node. Under Name, enter firstName. Keep Type as String and click OK.  Click Create Node. Enter the lastName as Name.  For Type select String. Click OK.  Again, click on Create Node.  Enter primaryEmail for Name.  For Type, select String. Click on Validation.  Enable Validation and select e-mail in Format.  Click OK.  Click Create Node again and enter gender for Name. Click on Validation and add the values male, female, other.  Click OK.  Click Create Node  and enter masterDataID for Name.  Select String as Format.  Mark the check box ‘As Array’, then click OK.  We have our source bookstore profile schema defined. Click on next to move to the Mapping step.  We now need to map the source bookstore profile schema against the CDP customer profile schema.  We start first by mapping the ID attributes previously defined in the Matching Rules. From the left panel, drag and drop masterDataID into the right pane masterDataID that’s inside the Unified Customer Profile pane. Repeat the operation for primaryEmail.  If you also decide to have the same information in Contextual Profile, repeat the mapping for both masterDataId and primaryEmail in the Contextual Profile pane. Hit Next to move onto the Mapping screen of the remaining schema fields representing our profile data ingestion payload.  From the left pane, drag firstName into the right pane profile section firstName.  Repeat the operation for lastName, primaryEmail, masterDataID, and gender.  Click on Next to go to the final step. The last part allows you to schedule a poller that will fetch the source data in periodic intervals. In this demo, we’ll skip this step, so click Done.  Next, let's ingest some profile data from the bookstore system into SAP CDP.  In the Source Application page, you’ll see your newly created Event as a card.  Click on the three dots to bring up its context menu, then select Ingest Now.  A popup asking for the cut dates for the files to be ingested will appear. Select the cut date accordingly to the dates of your files containing customer data. You can also set an optional limit number of files to ingest.  Hit Start.  This triggers a manual data ingestion, which will fetch the data from the S3 bucket into the SAP CDP.  Click on the three dots again, then click on View Status.  This screen allows you to monitor and check your event executions.  You can see if the source data was ingested or not,  and possible error messages that could have prevented any data import operations. This ends the bookstore profile data ingestion.  Next, we’ll quickly repeat this setup. This time for book view data where the ingested data will get imported into the previously defined BookView activity storage. Let's quickly go through the steps to setup a second event to ingest book views transactional data from our bookstore system into SAP CDP.  This is just a fast go through of the necessary configurations so we can reinforce the learning of the previous two steps. You can always go back to the previous parts if you need to revisit any explanation about the settings that we’re about to perform. In Sources, Click on Create New Event. Enter a name such as bookstore viewed books data ingestion.  Select Offline Data for Data Type.  Select BookViewTrackingData for both Required and Granted Processing Purposes.  Set ‘Read File Path’ as sources.  Set the Filename as the following Regex.  Set ‘File Format to Read’ as json.  Click next.  In model, let's map the viewed books json file schema to make SAP CDP aware of its contents format.  For every new attribute, we need to click Create Node, set a name, type and add additional validation settings if needed.  Let's fast forward: primaryEmail is a String validated as e-mail, masterDataID is an array of Strings,  and viewedBooks is an array of objects, which creates a sublevel in our schema. The next fields will be defined inside viewedBooks.  Click on Create Node. CategoryID is String. When is a Date. And Channel is a String with three possible validation options: mobile, desktop, or other. Now click Next.  In Matching Rules Mapping, we need to map primaryEmail and masterDataID into the respective Unified Customer Profile and Contextual Profile fields.  Hit Next.  In Mapping,  Scroll down to find the BookView activity schema.  Map attributes categoryID,  when and channel.  The popup titled  Map Array Property To Activity is an alert that the source information is part of an object array.  That will create a new target record on each occurrence of a new value at the source. This is purely informational.  Click OK to dismiss it.  Map the remaining attributes and click next.  Click Done to skip the Scheduled Polling setup. Going back to the Source Application page, you’ll see your newly created Event as a card next to the one created previously.  Click on the three dots, then select Ingest Now to trigger its data ingestion.  Select the cut dates again for the files and hit Start.   Click on the three dots again, then click on View Status to check the book views ingestion you executed.  This ends the Events Setup demo.