- SAP Managed Tags
Friendly Reminder: This is a technical blogpost and you should work with your Business Application Studio experts in performing the steps provided below to successfully do Source to Model Entity replication via Flowgraph |
In SAP Profitability and Performance Management Cloud’s Universal Model (SAP PAPM Cloud UM) release in 2023 with a purpose of supporting transactional processing, we cannot avoid discussing if there are possibilities to do Data Replication.
What is Data Replication?
To those that are new to this terminology, let me explain in the easiest form --- Data Replication is the cloning or copying of data from an external source table to a replica table to ensure that you always have the most accurate and latest data in your system locally for transactional processing without being too dependent to the external source’s availability. This means that even if the source becomes unavailable or the connection got intermittent, business’ transactional processing is not to suffer or get affected by this unavailability as the same data needed from the external source is already accessible via the replica tables.
Still vague? Let me show you via visual representation. Imagine Live Connection….
In live connection, the system relies heavily on Source and Connection availability
This means if the source or connection suddenly becomes unavailable, processing will also get interrupted due to missing information needed.
This type of issue is usually being realized in transactional processing since data is heavily accessed more often due to more frequent process execution. As a solution to this dilemma, Data Replication has always been a disaster recovery plan for such situations and challenges.
In data replication mode, while the source is up, replication or fetching of data happens Realtime or Batch (scheduled) from the external source to safeguard information all the time in the Replica Table (which is locally available).
This helps in case the source or connection is down, transactional processing can still happen via the locally available replica table.
I hope my explanation above helped you visualize Data Replication. But to know more about Data Replication in HANA Cloud, see SAP HANA Cloud’s Data Replication Guide. You may also follow this useful developer’s guide from SAP concerning Remote Table Replication.
Fast forward to now that you already know how to do SAP HANA Cloud Data Replication, let us proceed with doing a more sophisticated Data Replication process. Our mission together in this blogpost is to consume data from an external HANA 2.0 Database (via Smart Data Integration) or HANA Cloud Database (Smart Data Access), then create a replication process. However, this time we use SAP PAPM UM’s Model Entity as a Replica Table. Sounds great and useful right? Imagine that your Model Entity is getting populated automatically on a regular basis.
Since this mission is to replicate information in an existing table (SAP PAPM UM’s Model Entity), normal replication process via Remote Table Replication is not to work as we need to respect the fields available in the Model Entity including its technical fields (_FIELDS) so it will be read by SAP PAPM Universal Model solution as an artifact. Let me show you what I meant.
If we are to use the normal replication option, you will see that our Model Entity Table looks something like this upon SAP PAPM Cloud UM activation
As a normal replication process, you will need to then perform below SQL commands in your SAP PAPM Cloud UM database in order for the replication to kick in
-- TO CREATE A REMOTE SUBSCRIPTION
CREATE REMOTE SUBSCRIPTION <REMOTESUBSCRIPTIONNAME> ON <VIRTUALTABLENAME> TARGET TABLE <TARGETTABLENAME>;
-- TO START THE REPLICATION PROCESS
ALTER REMOTE SUBSCRIPTION <REMOTESUBSCRIPTIONNAME> DISTRIBUTE;
You can see that the original table got updated and the _FIELDS were all removed by this replication process.
Since this step will cause a structure change to the generated Model Entity Table, it is unfortunately will lead to possible corruption of the table with respect to using it in SAP PAPM Cloud UM's show screen for example
So what if I want to ensure that the fields of the Model Entity stays as is, and still be able to do replication even if my source fields are not 1:1 with my Model Entity? How can we handle that situation? We will use another approach of replication with the help of Flowgraph.
I am introducing lots of things in this blogpost, am I not? (^^,) . Let me explain to you what is Flowgraph
What is Flowgraph?
In the most simplest form, FlowGraph is a HANA development functionality that can be accessed via Business Application Studio which then helps HANA developers to perform data transformation and replication with visual representation.
Here is an example on how to create a flowgraph via Business Application Studio
Here is an example of a very simple Data Source > Data Target Flowgraph creation
I hope by now you are convinced that it is pretty easy to use. And since flowgraph only performs pushing without adjusting your target table, this is the best replication method we can use to populate directly the datarecords in our Model Entity.
Just to straighten expectations, definitely there is more to Flowgraph that I will not be covering in this blogpost. For the meantime let us focus on using this to replicate source information directly to Model Entity of Universal Model in a form of UPSERT and in a form of scheduled replication.
As this is very technical, let us divide our topics into 3 chapters to avoid confusion:
- Installation and Subscription
- Authorization Grants
- Replication via Flowgraph using simple data
A) Installation and Subscription
Just to help, I placed here all the important prerequisites to be able to use Flowgraph successfully. In case you already have an established systems and BAS setup, feel free to skip this chapter and proceed with B) Authorization Grants
A1) Create Subaccount
Ensure to have a commercial (non-trial) global account where you can create a subaccount on.
Once the subaccount subscription has been completed, do not forget to assign the BTP roles related to subaccount administration so you can perform the next subscription processes.
A2) Subscribe to SAP HANA Cloud (Plan: Tool)
Subscribe to SAP HANA Cloud: Tool to be able to subscribe completely to a standalone SAP HANA Cloud.
Upon subscribing to SAP HANA Cloud Tool, below roles will be introduced. Do not forget to assign these BTP roles related to SAP HANA Cloud to perform the HANA Cloud Database subscription and database administration
A3) Subscribe to SAP HANA Cloud (Plan: hana)
Since we need to use BAS, as a prerequisite, a standalone or subscribed SAP HANA Cloud is important to be sitting in the same Subaccount. It is important to understand that this is NOT the same as the runtime database of SAP PAPM Cloud.
A4) Subscribe to SAP PAPM Cloud (Plan: Default or BYOD)
Since our goal is to write or clone data directly to SAP PAPM UM’s Model Entity, a SAP PAPM Cloud subscription with activated SAP PAPM Cloud UM is obviously needed.
After subscription, and in case you want to follow through the simple example below --
create an environment with at least one Model entity in your SAP PAPM UM
For example
ENVIRONMENT ID | FLOWGRAPH |
FIELD1 | CUSTOMER, Characteristic - String |
FIELD2 | PRODUCT, Characteristic - String |
FIELD3 | QUANTITY, Keyfigure - Integer |
FIELD4 | AMOUNT, Keyfigure - Integer |
FUNCTION ID | FG_ME |
FUNCTION FIELDS | CUSTOMER (KEY), PRODUCT, QUANTITY, AMOUNT |
Disclaimer: The Model Entity can have more fields, for the meantime I use a simple one with a sole purpose of showing you how to replicate data from external source to the model entity directly
A5) Subscribe to Business Application Studio (Standard Edition)
BAS will serve as the application to create flowgraph in a specific HDI Container. Do not forget to assign the BTP roles related to BAS to perform HANA Development via BAS
A6) Establish Connection between BAS and SAP HANA Cloud
As this is a full course, I will skip showing the step-by-step procedure for this. But to summarize you need to make sure that you perform below steps while watching the SAP Academy Video.
- Dev Space Creation, SAP HANA Native Application
- HANA DB Project Creation
- Establish HANA DB Connection + Create HANA shared-HDI container
- Create HANA Service Instance
- Hdbgrant and yaml file creation
VERY IMPORTANT NOTE:
It is mandatory that you are comfortable in working at Business Application Studio (BAS) as almost all steps that you are to encounter in C) Create Flowgraph using Simple Data are to be done in BAS.
A7) Create Remote Source in SAP HANA Cloud
In the BAS linked SAP HANA Cloud, create multiple remote sources to connect to your On-Premise or Cloud databases. Imagine that these sources are the connections that would be used by flowgraph to pull data from Source tables via Smart Data Access (SDA) or Smart Data Integration (SDI).
B) Authorization Grants
Now that we are done with A) Installation and Subscription, it is now time to update some database authorization for smooth connectivity and data consumption. In this chapter we are to give proper authorization to the HDI Container users to read external artifacts, as well as giving HDI Container administrative rights to the Service Instance user.
Note: In case you are not familiar of these users, I really suggest that you revisit the BAS training in Chapter A6) Establish Connection between BAS and SAP HANA Cloud to understand who is the HDI Container user as well as the ServiceInstance user. These users play a very important role in creating artifacts in the database including the flowgraph.
B1) ServiceInstance user to have Admin rights to the BAS HDI Container
In the BAS connected database, execute the following SQL Commands to give the Service Instance user access to the HDI container to create artifacts if need be.
In the HANA SQL script below:
- DBADMIN is the BAS related Instance User
- FGRAPH_BYOD_HDI_DB_1 is the BAS related HDI Container
--Login as any user such as DBADMIN or HDI Container Owner
--option 1: choose which privilege to give
CREATE LOCAL TEMPORARY COLUMN TABLE #PRIVILEGES LIKE _SYS_DI.TT_SCHEMA_PRIVILEGES;
INSERT INTO #PRIVILEGES ( PRIVILEGE_NAME, PRINCIPAL_SCHEMA_NAME, PRINCIPAL_NAME ) VALUES ( 'CREATE ANY', '', 'DBADMIN' );
INSERT INTO #PRIVILEGES ( PRIVILEGE_NAME, PRINCIPAL_SCHEMA_NAME, PRINCIPAL_NAME ) VALUES ( 'SELECT', '', 'DBADMIN' );
INSERT INTO #PRIVILEGES ( PRIVILEGE_NAME, PRINCIPAL_SCHEMA_NAME, PRINCIPAL_NAME ) VALUES ( 'UPDATE', '', 'DBADMIN' );
CALL FGRAPH_BYOD_HDI_DB_1#DI.GRANT_CONTAINER_SCHEMA_PRIVILEGES( #PRIVILEGES, _SYS_DI.T_NO_PARAMETERS, ?, ?, ?);
DROP TABLE #PRIVILEGES;
--option 2: this is full administrator rights in the specific HDI Container
CREATE LOCAL TEMPORARY TABLE #PRIVILEGES LIKE _SYS_DI.TT_API_PRIVILEGES;
INSERT INTO #PRIVILEGES (PRINCIPAL_NAME, PRIVILEGE_NAME, OBJECT_NAME) SELECT 'DBADMIN', PRIVILEGE_NAME, OBJECT_NAME FROM _SYS_DI.T_DEFAULT_DI_ADMIN_PRIVILEGES;
CALL FGRAPH_BYOD_HDI_DB_1#_DI.GRANT_CONTAINER_SCHEMA_PRIVILEGES( #PRIVILEGES, _SYS_DI.T_NO_PARAMETERS, ?, ?, ?);
CALL _SYS_DI.GRANT_CONTAINER_GROUP_API_PRIVILEGES('SYS_DI', #PRIVILEGES, _SYS_DI.T_NO_PARAMETERS, ?, ?, ?);
DROP TABLE #PRIVILEGES;
B2) ServiceInstance user to have rights to adjust SAP_PAPM_UM.Z table
This granting is only needed if your SAP PAPM Cloud is on BYOD mode. This means that the database of your SAP PAPM Cloud UM and the BAS connected database are the same and you want to give your serviceinstance user an access to write to SAP PAPM UM table.
If you are using a SAP PAPM Cloud on Runtime mode, you must skip this step.
--login as SAP_PAPM_ADMIN like user and perform below step
GRANT "<UM SCHEMA>"."external_access_role#" TO DBADMIN;
B3) HDI Container user to have access to other schemas’ artifacts
Below is just an example where HDI Container gets access to information coming from other schema, in this case DBADMIN.
In the HANA SQL script below:
- DBADMIN schema is the artifact owner
- FGRAPH_BYOD_HDI_DB_1 users are all related BAS’ HDI container
--execute commands as schema owner, in this case DBADMIN
GRANT ALL PRIVILEGES ON SCHEMA DBADMIN TO FGRAPH_BYOD_HDI_DB_1;
GRANT ALL PRIVILEGES ON SCHEMA DBADMIN TO FGRAPH_BYOD_HDI_DB_1#DI;
GRANT ALL PRIVILEGES ON SCHEMA DBADMIN TO FGRAPH_BYOD_HDI_DB_1#OO;
GRANT ALL PRIVILEGES ON SCHEMA DBADMIN TO FGRAPH_BYOD_HDI_DB_1_xxxxxxxx_DT;
GRANT ALL PRIVILEGES ON SCHEMA DBADMIN TO FGRAPH_BYOD_HDI_DB_1_xxxxxxxx_RT;
B4) HDI Container user to have access to SAP PAPM UM Model Entity
This granting is only needed if your SAP PAPM Cloud is on BYOD mode. This means that the database of your SAP PAPM Cloud UM and the BAS connected database are the same and you want to give your HDI Container access to SAP PAPM UM table.
This is basically important so the HDI Container user can create synonym linked to SAP PAPM UM artifacts
In the HANA SQL script below:
- FGRAPH_BYOD_HDI_DB_1 users are all related BAS’ HDI container
--execute commands as DBADMIN or the ServiceInstance user that has access to SAP_PAPM_UM schema
GRANT ALL PRIVILEGES ON "<SAP_PAPM_UM>"."Z_FLOWGRAPH_FG_ME" TO FGRAPH_BYOD_HDI_DB_1;
GRANT ALL PRIVILEGES ON "<SAP_PAPM_UM>"."Z_FLOWGRAPH_FG_ME" TO FGRAPH_BYOD_HDI_DB_1#DI;
GRANT ALL PRIVILEGES ON "<SAP_PAPM_UM>"."Z_FLOWGRAPH_FG_ME" TO FGRAPH_BYOD_HDI_DB_1#OO;
GRANT ALL PRIVILEGES ON "<SAP_PAPM_UM>"."Z_FLOWGRAPH_FG_ME" TO FGRAPH_BYOD_HDI_DB_1_xxxxxxxx_DT;
GRANT ALL PRIVILEGES ON "<SAP_PAPM_UM>"."Z_FLOWGRAPH_FG_ME" TO FGRAPH_BYOD_HDI_DB_1_xxxxxxxx_RT;
Alright now we are fully set!!!
Let us proceed with the final Chapter and the main point of this blogpost, FLOWGRAPH…
C) Create Flowgraph using simple Data
In the near future (latest Q1 or Q2 2025) there will be two productive plans available for SAP PAPM Cloud such as Default (Runtime Database) and BYOD (Bring your own database). Since these two databases have different administration rights, the steps to perform the replication would also be different.
I will share with you both, so you have options in the future.
C1) OP Replicating to Runtime UM
Below steps are just example of how you can setup to push information from your On-premise database directly to your Model Entity. In here we will be using a flowgraph execution on batch mode, which we will eventually schedule to run “almost” real-time via Cronjob to fetch and store data to the model entity. Let us proceed!
C1.1) In the target (runtime db) perform below statements
The goal of this script is to prepare and know if SAP_PAPM_ADMIN user actually has enough privilege to write to the Model Entity. If this fails, ensure to provide proper authorization prior performing the succeeding steps, else your flowgraph procedure will fail.
CONNECT SAP_PAPM_ADMIN PASSWORD <password>;
-- ensure that SAP_PAPM_ADMIN has enough rights to manage the UM model entity
--insert records to the model entity table
INSERT INTO "SAP_PAPM_UM"."Z_FLOWGRAPH_FG_ME" (CUSTOMER, PRODUCT, QUANTITY, AMOUNT) VALUES ('TEST', 'TEST', 0, 0);
--check result of the model entity table
SELECT * FROM "SAP_PAPM_UM"."Z_FLOWGRAPH_FG_ME";
--delete record inserted to clear up the model entity table
DELETE FROM "SAP_PAPM_UM"."Z_FLOWGRAPH_FG_ME" WHERE CUSTOMER = 'TEST';
--check result of the model entity table
SELECT * FROM "SAP_PAPM_UM"."Z_FLOWGRAPH_FG_ME";
Note: By default, all the steps should be ok as SAP_PAPM_ADMIN has proper rights to manage SAP PAPM UM Z tables.
C1.2) From the BAS linked Database, create a remote source
The BAS linked database will act as a middleman between source and target tables. In Chapter A.7. Create Remote Source in SAP HANA Cloud we created multiple Remote sources to establish connection on the source tables; this time we are to create a remote source to establish connection to the target table (Model Entity of Universal Model).
This remote source example below should point to the PAPM Runtime Database to be able to replicate data directly to the Model Entity. It is also important or advisable that you use SAP_PAPM_ADMIN as Remote Source Technical User to avoid extra authorization issue.
C1.3) From BAS, update the hdbgrant file to include the created remote source
Add the remote source (in this case PAPMRUNTIME) in both Object Owner and Application User Tabs of the hdbgrant file with atleast CREATE VIRTUAL TABLE privilege.
This will give your BAS application enough authorization to create virtual table from the said remote source.
C1.4) From BAS, create a VT pointing to SAP_PAPM_UM > Z_FLOWGRAPH_FG_ME
It is possible to create the VT (Virtual Table) outside the HDI container, but I suggest creating the VT directly in the HDI container via BAS to avoid extra steps such as synonyms creation and additional unnecessary authorization grants.
C1.5) From BAS, create Flowgraph FG_RT01
As you can see in the image, the Flowgraph created was very simple.
It only has Data Source pointing to the Virtual Table linked to the source database, in this case it is On-Premise database. And a Data Target pointing to the Virtual table linked to the Model Entity of SAP PAPM UM (writing option used is UPSERT). To be guided how to create flowgraph, revisit What is Flowgraph? section
C1.6) From BAS, execute and check Result
Perform a test run to ensure that the Flowgraph configuration is as you intended. You will know if it is successful if you see the result or information from your On-Premise database to your Model Entity. The model entity result can be checked via HANA Cloud database of your SAP PAPM UM, or via Show Screen Application.
C1.7) From BAS, Build a HANA JobScheduler
As the setup we performed uses manual execution, a cronjob or scheduled job is necessary to execute C1.6 automatically in a periodic manner which can also be called as BATCH processing.
Before you can create a JobScheduler, you will need to know which procedure you are to call in periodically. Since a flowgraph is creating a procedure, we need to find first the procedure link to a flowgraph. Below is an example on how you can find the procedure
Once you know the procedure, you can proceed with creating the JobScheduler
Below is an example of a Cronjob scheduled to run every 30 seconds.
| Note: The scheduling of cron should be evaluated by your database administrator. As this is just a demo, I used 30seconds. In reality, you would want to schedule this every 15minutes or every hour depending on how frequent your source table is being updated, and how much datarecords the table has. |
C1.8) Perform some live checks
Now that you are all set, you might want to do some live check to see if the full flow works from pulling of information to writing it to your model Entity.
For example, I used simple statements like below to see if the data from source if updated will be reflected to the Model Entity
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
--Insert one liner of record
INSERT INTO "SOURCESCHEMA"."O_PECINPUT_WKEY" VALUES ('C007_DEMO', 'P007_DEMO', 100, 100);
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
--As the jobscheduler is running almost real-time, it reflects right away in showscreen
--from the added record, update a line to ensure that UPDATE is working properly. This feature can only work if you have a primary key, in this case customer
UPDATE "SOURCESCHEMA"."O_PECINPUT_WKEY" SET AMOUNT = 999 WHERE CUSTOMER = 'C007_DEMO';
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
--showing that deletion command from source, will not trigger deletion from repliciation table
DELETE FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" WHERE CUSTOMER = 'C007_DEMO';
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
| Note: The setup we performed is not meant to delete information from the Model Entity. As being imagined that this will be used as financial application or table, deletion of data record is not advisable. |
--optionally, redo for another set of records, to ensure stability
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
INSERT INTO "SOURCESCHEMA"."O_PECINPUT_WKEY" VALUES ('C008_DEMO', 'P008_DEMO', 100, 100);
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
UPDATE "SOURCESCHEMA"."O_PECINPUT_WKEY" SET AMOUNT = 999 WHERE CUSTOMER = 'C008_DEMO';
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
DELETE FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" WHERE CUSTOMER = 'C008_DEMO';
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
C2) OP Replicating to BYOD UM
Now that we are done with replication to SAP PAPM Cloud, Default. Let us setup the replication in SAP PAPM Cloud, BYOD.
In the next steps, the assumption is that the database of SAP PAPM Cloud UM is the same as with the BAS linked Database which will give you less steps to perform and avoid remote sourcing to target tables.
C2.1) In the target (BYOD db) perform below statements
In the BAS linked database, login as the HANA DB Service User and perform below HANA SQL commands to ensure that your ServiceInstance user has enough privilege to maintain SAP PAPM UM Model Entity. Shall you encounter any privilege issue, revisit Chapter B.2 ServiceInstance user to have rights to adjust SAP_PAPM_UM.Z table
--insert a dummy data to ensure that the InstanceService user has enough rights to insert records
INSERT INTO "<SAP_PAPM_UM>"." Z_FLOWGRAPH_FG_ME" (CUSTOMER, PRODUCT, QUANTITY, AMOUNT) VALUES ('TEST', 'TEST', 0, 0);
--check result
SELECT * FROM "<SAP_PAPM_UM>"."Z_FLOWGRAPH_FG_ME";
--delete record inserted to clear up the table
DELETE FROM "<SAP_PAPM_UM>"."Z_FLOWGRAPH_FG_ME" WHERE CUSTOMER = 'TEST';
--check result
SELECT * FROM "<SAP_PAPM_UM>"."Z_FLOWGRAPH_FG_ME";
C2.2) From BAS, create Synonym for the ME Table
Since the target table is outside the HDI container, it is important to create in BAS a synonym for this Model Entity table.
Take note though that an issue could occur like below if you skipped performing the steps under B4) HDI Container user to have access to SAP PAPM UM Model Entity
C2.3) From BAS, create Flowgraph FG_BYOD01
Same steps as with the flowgraph creation in C1.5) From BAS, create flowgraph FG_RT01. The only difference is the target table where we are pointing to replicate the source information. In BYOD, the Model Entity table is not a virtual table unlike in the runtime database approach, since the BAS linked database is the same as with SAP PAPM UM's database
C2.4) From BAS, Build a JobScheduler
Same as with the job scheduler creation in C1.7) From BAS, Build a JobScheduler. Just this time I used 5 seconds to test a different frequency. As a friendly reminder, same note still applies.
| Note: The scheduling of cron should be evaluated by your database administrator. As this is just a demo, I used 5seconds. In reality, you would want to schedule this every 15minutes or every hour depending on how frequent your source table is being updated, and how much datarecords the table has. |
C2.5) Perform some live checks
Same as with the flowgraph creation in C1.8 Perform some live checks. I will always advise you to check with small amout of data if you can insert, update, and if deletion is not happening.
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
INSERT INTO "SOURCESCHEMA"."O_PECINPUT_WKEY" VALUES ('C007_DEMO', 'P007_DEMO', 100, 100);
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
UPDATE "SOURCESCHEMA"."O_PECINPUT_WKEY" SET AMOUNT = 999 WHERE CUSTOMER = 'C007_DEMO';
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
DELETE FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" WHERE CUSTOMER = 'C007_DEMO';
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
INSERT INTO "SOURCESCHEMA"."O_PECINPUT_WKEY" VALUES ('C008_DEMO', 'P008_DEMO', 100, 100);
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
UPDATE "SOURCESCHEMA"."O_PECINPUT_WKEY" SET AMOUNT = 999 WHERE CUSTOMER = 'C008_DEMO';
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
DELETE FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" WHERE CUSTOMER = 'C008_DEMO';
SELECT * FROM "SOURCESCHEMA"."O_PECINPUT_WKEY" ORDER BY CUSTOMER ASC;
That's all it. Mission completed! (^^,)
I hope this blogpost helped you get new technical knowledge related to Business Application Studio, Flowgraph, and ofcourse Data Replication straight to your SAP PAPM UM's Model Entity!
Until we meet again for another technical blogpost!
Have a wonderful data replication moment and modeling time in the cloud!
| User | Count |
|---|---|
| 9 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
