tag:blogger.com,1999:blog-2954271788555007352024-03-18T11:33:22.534+05:30SAP HANA Central Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.comBlogger1508125tag:blogger.com,1999:blog-295427178855500735.post-56343351403928475622024-03-15T14:03:00.002+05:302024-03-15T14:03:17.603+05:30Effectively adopting Recurring Service process from S/4 HANA Service Management into your business<div>Regular maintenance aids in maintaining a customer's assets at their best performance levels while reducing the likelihood of breakdowns and the costs associated with repairs.</div><div><br /></div><div>Our preventive maintenance solution, designed to sustain customer assets, facilitates consistent production by mitigating unexpected breakdowns. This solution creates and executes orders at specified intervals/usage, drastically improving asset production efficiency and minimizing breakdowns. Notably, this solution also reduces maintenance costs and contributes to recurring service revenues for customers. It adeptly manages both commercial aspects through service orders, as per the service contract, and technical aspects through execution orders.</div><div><br /></div><div>There are different types of Maintenance Plans, namely: Single cycle plans based on time or performance, strategy plans, or multiple counter maintenance plans that are implemented on need basis . Once you create a maintenance plan, you can schedule the plan to generate call objects when the system is due for maintenance.<span><a name='more'></a></span></div><div><br /></div><div>The normal recurring service is the process that is more straightforward and is suitable for simple servicing scenarios and is inclusive of commercial aspects in the same document. The Service with Advanced Execution is a process that combines commercial aspects of service with maintenance management for tasks that require detailed planning and execution. Maintenance task lists help in planning and organizing maintenance work efficiently, saving time during scheduling. They're especially useful for frequent tasks requiring the same materials, and for recurring and one-time tasks. The service part handles the customer's needs, pricing, satisfaction, and profit, while the maintenance management part focuses on planning, understanding equipment technicalities, and carrying out the service. The process creates Execution Order Items, which can be part of a service order or a maintenance plan. These items generate a maintenance order, enabling the service's planning and execution.</div><div><br /></div><div>The information below explains how to differentiate between the two.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjuN5dcyAiW55byVdZwGze7rLf-qSfmpY48-DDzejQPZuyABWYphdfzYwRBmbnEI4pJGILaHWY1lD5McHVPr9gXJtqt8OST8XyEqxdYE9oDDVx6Nl0vJr6Hri3OPWxqV4-cgVMf8tg13xfa-K_pHs9mrkYypUVe5fT2jJWJXLjAYfo-zNsh4piCG9HUc9Qd/s1673/1.png" style="margin-left: 1em; margin-right: 1em;"><img alt="Effectively adopting Recurring Service process from S/4 HANA Service Management into your business" border="0" data-original-height="833" data-original-width="1673" height="199" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjuN5dcyAiW55byVdZwGze7rLf-qSfmpY48-DDzejQPZuyABWYphdfzYwRBmbnEI4pJGILaHWY1lD5McHVPr9gXJtqt8OST8XyEqxdYE9oDDVx6Nl0vJr6Hri3OPWxqV4-cgVMf8tg13xfa-K_pHs9mrkYypUVe5fT2jJWJXLjAYfo-zNsh4piCG9HUc9Qd/w400-h199/1.png" title="Effectively adopting Recurring Service process from S/4 HANA Service Management into your business" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Image 1 : Apps related to Recurring Service</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg0nSxpl4W9xlmXNsmgx652XonHaFcRMG-Ac09BNavMnDEqNERnsth9iq5E1TLp111a3gUC4lLGMses1UUjvyiae_pCOoSw3q-LPb8f45ld_Xt1A5Ujx18o2avEagh9Fe4gbFC3XRGDmc3vEwqCb7WtRV3SNRXry-UJDdERlBiZqObEc1snENr3xIP1z0rz/s1215/2.png" style="margin-left: 1em; margin-right: 1em;"><img alt="Effectively adopting Recurring Service process from S/4 HANA Service Management into your business" border="0" data-original-height="781" data-original-width="1215" height="258" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg0nSxpl4W9xlmXNsmgx652XonHaFcRMG-Ac09BNavMnDEqNERnsth9iq5E1TLp111a3gUC4lLGMses1UUjvyiae_pCOoSw3q-LPb8f45ld_Xt1A5Ujx18o2avEagh9Fe4gbFC3XRGDmc3vEwqCb7WtRV3SNRXry-UJDdERlBiZqObEc1snENr3xIP1z0rz/w400-h258/2.png" title="Effectively adopting Recurring Service process from S/4 HANA Service Management into your business" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><div class="separator" style="clear: both;">Image 2: Recurring Service with Advanced Execution</div></div><br /><table border="1" style="width: 100%;">
<tbody>
<tr>
<td style="width: 5%;"><b>S.I No </b></td>
<td style="width: 25%;"><b>Category</b></td>
<td style="width: 30%;"><b>Recurring Service</b></td>
<td style="width: 30%;">
<p><b>Recurring Service with Advanced Execution </b></p>
</td>
</tr>
<tr>
<td>1</td>
<td>Scenarios</td>
<td>Classic Recurring Service</td>
<td>Preventive Maintenance</td>
</tr>
<tr>
<td>2</td>
<td>
<p>ABAP Call Type Technical code</p>
</td>
<td>Maintenance Service Call Type '5' </td>
<td>Maintenance Service Call Type '6' </td>
</tr>
<tr>
<td>3</td>
<td>Types of MPLAN supported </td>
<td>Single Cycle (Time or Performance), Multiple-Counter </td>
<td>Single Cycle (Time or Performance), Multiple-Counter, Strategy Time Based. Strategy Performance Based </td>
</tr>
<tr>
<td>4</td>
<td>Preceding Document </td>
<td>Service Template </td>
<td>Service Contract</td>
</tr>
<tr>
<td>5</td>
<td>Mandatory Inputs for Scheduling </td>
<td>Service Template<br />Either Technical Object OR Service Contract<br />Call Object Type (Service Order or Service Quotation) </td>
<td>Service Contract<br />Work Centre<br />Planning Plant<br />Call Object Type (Service Order) </td>
</tr>
<tr>
<td>6</td>
<td>Output </td>
<td>Service Order or Service Quotation </td>
<td>
<p>Service Order with Execution Order</p>
<p> </p>
</td>
</tr>
<tr>
<td>7</td>
<td>Source of Service Transaction Items </td>
<td>Service Order Template </td>
<td>Service Contract Items</td>
</tr>
<tr>
<td>8</td>
<td>Task List </td>
<td>Table OISD (Service Product with Task List) </td>
<td>Directly from Maintenance Item, else from table OISD. </td>
</tr>
<tr>
<td>9</td>
<td>Supported Service Document Types </td>
<td>Service Order and Service Quotation</td>
<td>
<p>Service Order</p>
</td>
</tr>
<tr>
<td>10</td>
<td>Applications support and GUI support </td>
<td>
<p>Supports on Fiori Apps</p>
</td>
<td>GUI (TCODES: IP01/02/03 and IP10, etc) and Fiori Apps</td>
</tr>
</tbody>
</table><br /><div><div>The ABAP code flow for simple recurring service is as follows:</div><div><br /></div><div>FAELLIGE_MHIS_ORDER ( FM) -></div><div>PERFORM service_order_create -></div><div>CL_CRMS4_MPLAN_SCHEDULING-IF_CRMS4_MPLAN_SCHEDULING~CREATE_ORDER( ) -></div><div>CL_CRMS4_MPLAN_ORDER_CREATION-IF_CRMS4_MPLAN_ORDER_CREATION~CREATE_ORDER( )-></div><div>CL_CRMS4_MPLAN_ORDER_CREATION->CREATE_ORDER_FROM_TEMPLATE( )-></div><div>CL_CRMS4_MPLAN_ORDER_PREPARE-IF_CRMS4_MPLAN_ORDER_PREPARE~GET_DATA_FOR_CREATION ( )-></div><div>CRM_ORDER_MAINTAIN->( call back to FAELLIGE_MHIS_ORDER )-></div><div>PERFORM service_order_post_mhio (calling CRM_ORDER_SAVE).</div><div><br /></div><div>The ABAP code flow for recurring service with execution order item ( Advanced Execution ) is as follows:</div><div><br /></div><div>FAELLIGE_MHIS_ORDER (FM) ->PERFORM create_srvo_pmo-></div><div>SERVICE ORDER CREATION: PERFORM service_order_create -></div><div>CL_CRMS4_MPLAN_SCHEDULING-IF_CRMS4_MPLAN_SCHEDULING~CREATE_ORDER( ) -></div><div>CL_CRMS4_MPLAN_ORDER_CREATION-IF_CRMS4_MPLAN_ORDER_CREATION~CREATE_ORDER( )-></div><div>CL_CRMS4_MPLAN_ORDER_CREATION->CREATE_ORDER_FROM_CONTRACT( )</div><div>CL_CRMS4_MPLAN_ORDER_PREPARE-IF_CRMS4_MPLAN_ORDER_PREPARE~GET_DATA_FOR_CREATION ( )-></div><div>CRM_ORDER_MAINTAIN->(call back to PERFORM create_srvo_pmo )-></div><div>MAINTENANCE ORDER in BUFFER :</div><div>PERFORM order_create_f13 -> (call back to FAELLIGE_MHIS_ORDER)-></div><div>PERFORM update_srvo_pmo-></div><div>EXACT OBJECT ID of PLANT MAINTENANCE ORDER:</div><div>PERFORM order_update_f13->( call back to PERFORM update_srvo_pmo )-></div><div>(Logic for Creation of the DOCFLOW between Plant Maintenance Order and Service Order and vice versa).</div><div><br /></div><div>In conclusion, the distinction between normal Recurring service and Service with Advanced Execution lies in their complexity and scope. The decision to select one over the other depends on the specific needs and requirements of the business.</div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-35139073483707594802024-03-13T14:49:00.001+05:302024-03-13T14:49:16.595+05:30How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP<h3 style="text-align: left;"><b>Introduction</b></h3><div><br /></div><div>In this blog, we describe a method to attach document files to a Journal Entry (BKPF) instance within the same SAP S/4HANA Public Cloud using ABAP.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiB1rKQeBEr2RoiRuf9yzSlHohEzLqwl1paBbH5zHLtMlzY0MltP8d7ax14JIFxawuuLF23Ilwzd0v1JUkXYeEsnRvWrdiNlFvWbLCxMUOhbMr2OHlXuIt3YpUK1RpO6_ajD0TknpnT38OukTPqUwRCA6JTa3NBjIRNeBovWD-47sXEgpqTCDW5YyMZXrhg/s1468/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="390" data-original-width="1468" height="106" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiB1rKQeBEr2RoiRuf9yzSlHohEzLqwl1paBbH5zHLtMlzY0MltP8d7ax14JIFxawuuLF23Ilwzd0v1JUkXYeEsnRvWrdiNlFvWbLCxMUOhbMr2OHlXuIt3YpUK1RpO6_ajD0TknpnT38OukTPqUwRCA6JTa3NBjIRNeBovWD-47sXEgpqTCDW5YyMZXrhg/w400-h106/1.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">This requires us to expose and consume the Attachment API as described in the <b><a href="https://api.sap.com/api/API_CV_ATTACHMENT_SRV/overview" target="_blank">SAP Business Accelerator HUB - Attachments.</a></b></div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;">I believe this blog can be very useful since existing documentation primarily focuses on exposing the services, but we encounter conceptual problems when consuming them locally.<span><a name='more'></a></span></div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;">This method is also valid for a S/4HANA Private Cloud but has been implemented and tested only in S/4HANA Public Cloud.</div><div class="separator" style="clear: both;"><b><br /></b></div><h3 style="clear: both; text-align: left;"><b>Steps</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>1. Create the Outbound Service.</b> In Eclipse, and within your development package, follow these steps to create a new Outbound Service:</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxdMRchg4UFii2f-ZUBoedgk6PYBNQfUAqrM_4e8TF3uYHGlHrrwZYiwkLVNxy_jSWfrDcgSSTauEd-RgCshaRdfKyHD4hmtSj11rTbJ6vL2PkkuWhTtIW0E8muQSjBTu8vmR34ltKIg_8waHzDUEx8_N6O3q_-Tq9kGK1IuFUoRHoF6gflOWB4Go9hKmq/s684/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="469" data-original-width="684" height="274" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxdMRchg4UFii2f-ZUBoedgk6PYBNQfUAqrM_4e8TF3uYHGlHrrwZYiwkLVNxy_jSWfrDcgSSTauEd-RgCshaRdfKyHD4hmtSj11rTbJ6vL2PkkuWhTtIW0E8muQSjBTu8vmR34ltKIg_8waHzDUEx8_N6O3q_-Tq9kGK1IuFUoRHoF6gflOWB4Go9hKmq/w400-h274/2.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Add name and description.</div><div class="separator" style="clear: both;">◉ Select the type HTTP.</div><div class="separator" style="clear: both;">◉ Set the Default Path Prefix for the Attachment method <a href="https://api.sap.com/api/API_CV_ATTACHMENT_SRV/path/post_AttachmentContentSet" target="_blank">AttachmentContentSet</a>, as follows: "/sap/opu/odata/sap/API_CV_ATTACHMENT_SRV/AttachmentContentSet".</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjVFLoiBeJ5_-fZeaLg7de3ObVc7PblvWCP4DJtxQuUy8COyrVMQNBgbPlAjdcG10ZDZk2u9rVLWGuiB6ATooMcdTsC2yawzK0YYjDIfuSu0EgViKRBHpjxhlnad9IVqfFPIxUBglaYUyX9EySyAmBDbpo47kBhFLZFZZFb2Sb5jLmDqz6V1OoSQhqxG6bb/s757/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="308" data-original-width="757" height="163" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjVFLoiBeJ5_-fZeaLg7de3ObVc7PblvWCP4DJtxQuUy8COyrVMQNBgbPlAjdcG10ZDZk2u9rVLWGuiB6ATooMcdTsC2yawzK0YYjDIfuSu0EgViKRBHpjxhlnad9IVqfFPIxUBglaYUyX9EySyAmBDbpo47kBhFLZFZZFb2Sb5jLmDqz6V1OoSQhqxG6bb/w400-h163/3.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><b>2. Create the Communication Scenario.</b> Still in Eclipse and under your development package, create a new Communication Scenario as follows:</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEifRXa1TM3rj9mG2f6DagDkDx9a-47Jf2Es1-QA76qNr2Zw-5emiYtmKWqI9VdxjawwX0Rf4YcCc0UdGsZh4FtPNxleyMCzZ4KbWCiSX0kpfFG9s7pvoUUjXBKISOOlfK3oFwg1m4XDIDWJY45sXXxdcKf2VmcwhLLIjZtHN56QJXbIbCuhtEkxv9U3Rt6p/s684/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="469" data-original-width="684" height="274" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEifRXa1TM3rj9mG2f6DagDkDx9a-47Jf2Es1-QA76qNr2Zw-5emiYtmKWqI9VdxjawwX0Rf4YcCc0UdGsZh4FtPNxleyMCzZ4KbWCiSX0kpfFG9s7pvoUUjXBKISOOlfK3oFwg1m4XDIDWJY45sXXxdcKf2VmcwhLLIjZtHN56QJXbIbCuhtEkxv9U3Rt6p/w400-h274/4.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Add name and description.</div><div class="separator" style="clear: both;">◉ In the Outbound tab, add the previously created service.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1Rxu8k7RY_3uc6jZ5M1t6qUa6RnkQPftEEew4f3DjKePtYvtVOgEMFN5eYrvSB6EwjSb34mZ4p29MftTtgtzEEaQjS8zLDCWSLxWi-xsSwR-u9Z9N7uWT6l7IwRSidz96WGZ2-HL9KMRXsWopbDhekp0IWgjJxFdDKmXoOZs4NBB9cP86vxOn2XrNwS7W/s791/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="530" data-original-width="791" height="268" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1Rxu8k7RY_3uc6jZ5M1t6qUa6RnkQPftEEew4f3DjKePtYvtVOgEMFN5eYrvSB6EwjSb34mZ4p29MftTtgtzEEaQjS8zLDCWSLxWi-xsSwR-u9Z9N7uWT6l7IwRSidz96WGZ2-HL9KMRXsWopbDhekp0IWgjJxFdDKmXoOZs4NBB9cP86vxOn2XrNwS7W/w400-h268/5.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Use the top-right 'Publish Locally' button to publish the communication scenario.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>3. Create the Communication User.</b> Navigate to the Maintain Communication User app and create a new user. Remember to copy the username and password, as we will need them to configure the communication systems.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4hbMQKChgikAOEnhYIqHsl6UM0tEV-WtFynP5rPYMkBHKRlQb3fospA7wGnf4KbcvmvhoglExlNJievS5W5kaT2kUic9opBgE4SliNvvmQo6N7150RgEdzFiDbkYQlsB7KuqP3W0xBFG-TDgqcyhQ_OD3Rm2fBZNwXzfr29OzVGPbL3S9lpDdZ0-0Ds6t/s1904/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="297" data-original-width="1904" height="63" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4hbMQKChgikAOEnhYIqHsl6UM0tEV-WtFynP5rPYMkBHKRlQb3fospA7wGnf4KbcvmvhoglExlNJievS5W5kaT2kUic9opBgE4SliNvvmQo6N7150RgEdzFiDbkYQlsB7KuqP3W0xBFG-TDgqcyhQ_OD3Rm2fBZNwXzfr29OzVGPbL3S9lpDdZ0-0Ds6t/w400-h63/6.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiovT1KH527imouvoSDlJqw2w5kSf_6qEZJCJ56WF3pKZY1enV00P2iIn-ljQSLm6o5T5lTBNtAcuHmHHci9KeUh-pIStiuKuLNVQ_FVTaexwLAR-Uekjq_RHVFqIP07Bi7Ln39rAIU4S3vXYibZmGnNlbvgio7XMX6-N7-a3TTL9vg4Z5mAWupyEwoS93l/s1920/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="945" data-original-width="1920" height="198" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiovT1KH527imouvoSDlJqw2w5kSf_6qEZJCJ56WF3pKZY1enV00P2iIn-ljQSLm6o5T5lTBNtAcuHmHHci9KeUh-pIStiuKuLNVQ_FVTaexwLAR-Uekjq_RHVFqIP07Bi7Ln39rAIU4S3vXYibZmGnNlbvgio7XMX6-N7-a3TTL9vg4Z5mAWupyEwoS93l/w400-h198/7.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><b>4. Assign the new communication user to our local Communication System.</b> In the Communication System app, select our local system using the top button labeled "Own SAP Cloud System."</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6zbrUweHYbRjPKo8WPRrFLFtN6496Pc2pbd-EkJ5wuqbMb7CYRQWVkeG7nDWvlqsXetICMYqDDYWIlsFkrptymo8ZxWNjB8MmsVpu-dCLnruH9Yzs6AX_8ky97NA8fZIwtO7rVwMiM3xS-oMweqRR-h3kQWuAR0N1sIbHaKwEEV04FEy9uvhr-AI5JbuK/s1920/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="206" data-original-width="1920" height="34" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6zbrUweHYbRjPKo8WPRrFLFtN6496Pc2pbd-EkJ5wuqbMb7CYRQWVkeG7nDWvlqsXetICMYqDDYWIlsFkrptymo8ZxWNjB8MmsVpu-dCLnruH9Yzs6AX_8ky97NA8fZIwtO7rVwMiM3xS-oMweqRR-h3kQWuAR0N1sIbHaKwEEV04FEy9uvhr-AI5JbuK/s320/8.png" width="320" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiCbN3x-2yZ13A7_7EibPFrSHgwvk3_VQ2dAO4GbfY9HWkI3N043DaV45w7b2MWChHSuCg83L79u8wdsKc67Mn1VK7gCAngZC57rt3kyzh1Cqdq4D0hBLkk8U1Xf_Ly7dQi7SL90iMTMQAyL_RLtQA4HBytXG8oSV4fKnRu0aOdltoBU0FZNKJqi4IWw0IA/s1857/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="533" data-original-width="1857" height="115" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiCbN3x-2yZ13A7_7EibPFrSHgwvk3_VQ2dAO4GbfY9HWkI3N043DaV45w7b2MWChHSuCg83L79u8wdsKc67Mn1VK7gCAngZC57rt3kyzh1Cqdq4D0hBLkk8U1Xf_Ly7dQi7SL90iMTMQAyL_RLtQA4HBytXG8oSV4fKnRu0aOdltoBU0FZNKJqi4IWw0IA/w400-h115/9.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Copy the hostname, as it will be needed in the next step.</div><div class="separator" style="clear: both;">◉ In edit mode, assign the previously created user as the User for Inbound Communication and save.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlsuzmmR9eKi6h4cTbfePVpX1gdV_e7ocUnaMW3xR4ODi1-f_UcMWEFfDNamzg_IWvyX6GyqpN-zs8P9XKlnFrLTqQaiASaGyPOcf-m_gBuphD7q8sHgEDwZ6wXe_ywN6kOHECH0z1-VLiVLglOjYH-tRq7hvRrLf67G9ORz0yrSXeRychkrVG42iYe-Hj/s611/10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="205" data-original-width="611" height="134" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlsuzmmR9eKi6h4cTbfePVpX1gdV_e7ocUnaMW3xR4ODi1-f_UcMWEFfDNamzg_IWvyX6GyqpN-zs8P9XKlnFrLTqQaiASaGyPOcf-m_gBuphD7q8sHgEDwZ6wXe_ywN6kOHECH0z1-VLiVLglOjYH-tRq7hvRrLf67G9ORz0yrSXeRychkrVG42iYe-Hj/w400-h134/10.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><b>5. Create a Communication System to consume the service.</b> Go to the Communication Systems App, create a new system, fill the ID and description.</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh6h_5dwfIL720qH3WBamtkFwpqR8U9QST_1MdYtmKxe6UxyPxtZtq4cI3eIl_1HTq5n_pFHmiCqqtf12ktuB0D8hPni6yyxEKRUtB7AKsMK8Rra38FFFe1B-muDrHlY8NmJSsd50xE0ta9JHf6FyrSQysZRcUuk5RZiZlIj58HVPw3qENdLiCi3XO5slQt/s1905/11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="288" data-original-width="1905" height="60" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh6h_5dwfIL720qH3WBamtkFwpqR8U9QST_1MdYtmKxe6UxyPxtZtq4cI3eIl_1HTq5n_pFHmiCqqtf12ktuB0D8hPni6yyxEKRUtB7AKsMK8Rra38FFFe1B-muDrHlY8NmJSsd50xE0ta9JHf6FyrSQysZRcUuk5RZiZlIj58HVPw3qENdLiCi3XO5slQt/w400-h60/11.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhksj27kzfSzhMGHNwHWkky5_b03LiowJ3sqWjHu_OgK8Wz3FIb60VFuX6jR8mghjxvy32hZhYOW6QNkPtaapomH9SuMQDYawW6vShoqYE0ChJpgXe7Lyi8DvCei6eqP6tBkOLsKV_aWV3Muqg-NHtF95Lz9jqu-dQP5v0ZO4eH3JBvh9QGa58aH2PH_A7s/s557/12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="191" data-original-width="557" height="138" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhksj27kzfSzhMGHNwHWkky5_b03LiowJ3sqWjHu_OgK8Wz3FIb60VFuX6jR8mghjxvy32hZhYOW6QNkPtaapomH9SuMQDYawW6vShoqYE0ChJpgXe7Lyi8DvCei6eqP6tBkOLsKV_aWV3Muqg-NHtF95Lz9jqu-dQP5v0ZO4eH3JBvh9QGa58aH2PH_A7s/w400-h138/12.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Complete hostname field with the value obtained in the previous step (local hostname).</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhr74n-UmG2pJwPumk8m1l43Jo3DbYBE3GCWYdhICG12N6BK2V-1wxdtlkcvSkB3QKV2oajhML1lEbzyE9-WgEE-2hGo7FkdU275H1e7bW9Alr1ie3WKq59nOzyTyAyTHkeXFNAzzyHwlEJf0Fwp9fn3o7gBHUHkl2U7YMNeMYTdLm34NR24-4Rjo4uiu8o/s953/13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="322" data-original-width="953" height="135" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhr74n-UmG2pJwPumk8m1l43Jo3DbYBE3GCWYdhICG12N6BK2V-1wxdtlkcvSkB3QKV2oajhML1lEbzyE9-WgEE-2hGo7FkdU275H1e7bW9Alr1ie3WKq59nOzyTyAyTHkeXFNAzzyHwlEJf0Fwp9fn3o7gBHUHkl2U7YMNeMYTdLm34NR24-4Rjo4uiu8o/w400-h135/13.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Assign the previously created user as Outbound User, and save.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgaW8I_D9leF_lJBqnItmBhuNA7vG3222IDjapYMroAcSqu1f-3WLnJEtWTl39Xh5Bw4dXAVqAkLnhAxY69-Nzhw6Roh2JhcuZ9d5pNzTCEFqU6PL1OUFccYm7qR0TW6MuuE13l_ex08SNBbubIdy9ag1VwfApnvxvErd6w1-J5FbkyERVYFUFXDKDpiApz/s1855/14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="234" data-original-width="1855" height="50" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgaW8I_D9leF_lJBqnItmBhuNA7vG3222IDjapYMroAcSqu1f-3WLnJEtWTl39Xh5Bw4dXAVqAkLnhAxY69-Nzhw6Roh2JhcuZ9d5pNzTCEFqU6PL1OUFccYm7qR0TW6MuuE13l_ex08SNBbubIdy9ag1VwfApnvxvErd6w1-J5FbkyERVYFUFXDKDpiApz/w400-h50/14.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjq2udkYQ-KbjLeEPITn0Lytsv-Zisa0JRvSpoet4QCDkqKJ62pWetP0J26X-sb6lBYkMixeYLvdaV3I7LLbRs5ORHNfe_8FMve80ltYY75DH4VEMF40ztX2RLcZCGPfXl_thY_vVVSZxCkeYyXoP83nOAwicZgEmABtB7vxN0SOozHp0dPeOOX2MiCrNuJ/s621/15.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="274" data-original-width="621" height="176" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjq2udkYQ-KbjLeEPITn0Lytsv-Zisa0JRvSpoet4QCDkqKJ62pWetP0J26X-sb6lBYkMixeYLvdaV3I7LLbRs5ORHNfe_8FMve80ltYY75DH4VEMF40ztX2RLcZCGPfXl_thY_vVVSZxCkeYyXoP83nOAwicZgEmABtB7vxN0SOozHp0dPeOOX2MiCrNuJ/w400-h176/15.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>6. Create the Communication Arrangement to expose the service</b>. Navigate to the Communication Arrangement App, create a new one, or check if one exists, based on the Scenario SAP_COM_0002: Finance - Posting Integration. This scenario has sufficient permissions to attach document files to a Journal Entry instance.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjwCV0OWTaU-lGdxDqfjWs_uqkso53Iq-I-zcZZ0bLGnnTLVKjVEnN4iEXEfTjUFuHYdERemYLIelmnLAF0aS-rCcIDJ1bj-cVeqtqrC6nlgtYs0vlRqOlAmvMr6dlSTtA4WU-CDl6EAfs4u50lSPRvnu8jFxgAFUUA7ljk6ybz2Pg0UBKBlfna3PkvgpXy/s1910/16.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="281" data-original-width="1910" height="59" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjwCV0OWTaU-lGdxDqfjWs_uqkso53Iq-I-zcZZ0bLGnnTLVKjVEnN4iEXEfTjUFuHYdERemYLIelmnLAF0aS-rCcIDJ1bj-cVeqtqrC6nlgtYs0vlRqOlAmvMr6dlSTtA4WU-CDl6EAfs4u50lSPRvnu8jFxgAFUUA7ljk6ybz2Pg0UBKBlfna3PkvgpXy/w400-h59/16.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsxRkLJJ36k-OqIt7Aux-GH6f3wBoTauCyfycDBeZ3l885rNB-76B_STHChmAheDFuhQan212uWG6pJ2qahkCjtKNfLpZJWrQgitTAIbVdz9PccdMDkWprux2pa-1MAXyvnYkvwSU0FLfjS5oJcnNMwmO2G_A0M56SFmJtC1g_4WVj8UCwOJDbpDDlZcrU/s397/17.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="269" data-original-width="397" height="271" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsxRkLJJ36k-OqIt7Aux-GH6f3wBoTauCyfycDBeZ3l885rNB-76B_STHChmAheDFuhQan212uWG6pJ2qahkCjtKNfLpZJWrQgitTAIbVdz9PccdMDkWprux2pa-1MAXyvnYkvwSU0FLfjS5oJcnNMwmO2G_A0M56SFmJtC1g_4WVj8UCwOJDbpDDlZcrU/w400-h271/17.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ After selecting or creating the communication arrangement, ensure that the communication system is assigned to your local system. Also, add the created communication user as Inbound Communication User.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiI8DWWd9fu7UZ33LS4Lps2NVa6CCHbJzhtMtmrUIXKAkZM88zM7-CB43eQB8MWLpMbR74TV2GBnOIPFIpq2BkccCz3gZR7tNz2U_ndOzu2Pc4IWjcrqv4hyCvsbUyB8QCxBiKnFcsf87SuwoMGwxS83t7GRIyeYFhsX6_CEKytBl3cmaLVr8avyKRH07zy/s1902/18.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="515" data-original-width="1902" height="109" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiI8DWWd9fu7UZ33LS4Lps2NVa6CCHbJzhtMtmrUIXKAkZM88zM7-CB43eQB8MWLpMbR74TV2GBnOIPFIpq2BkccCz3gZR7tNz2U_ndOzu2Pc4IWjcrqv4hyCvsbUyB8QCxBiKnFcsf87SuwoMGwxS83t7GRIyeYFhsX6_CEKytBl3cmaLVr8avyKRH07zy/w400-h109/18.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ We don't need the Outbound Services of the Arrangement for this requirement, so unless necessary for other reasons, deactivate these services by unchecking the Active flag.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgHo6jILKmyKbrrA-SYc8tjSvCE8VvQAn3wrXAOSLiSCAe9NkKOod0FAiEyHwj67AUO54iOj2bUuy42GgDm7mHJwL6baL-pmFYjx5Px7wFC1EjoiktR7PpcRQDBoW7xanSZISlvsqgvbx-qVhCCyo__VB6S2nyOJtJCSp9oVnIvLO4r32nZeyBwsGT33nqe/s1765/19.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="663" data-original-width="1765" height="150" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgHo6jILKmyKbrrA-SYc8tjSvCE8VvQAn3wrXAOSLiSCAe9NkKOod0FAiEyHwj67AUO54iOj2bUuy42GgDm7mHJwL6baL-pmFYjx5Px7wFC1EjoiktR7PpcRQDBoW7xanSZISlvsqgvbx-qVhCCyo__VB6S2nyOJtJCSp9oVnIvLO4r32nZeyBwsGT33nqe/w400-h150/19.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>7. Create the Communication Arrangement to consume the service.</b> Create a new Communication Arrangement based on our scenario created in step 2, assign the communication system created and assign the outbound communication user.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzZ7MyXuk3mhzKefsuqKAeHWonDhCMKjNm5K1BG7T-MLHrOvlH0KXLY0FkXY3Myk47gQFbfiSZfINoWCY0NKdM5FwIMPn61KkF3Nu81aOXKfXFKBuVlCV5QUVLuGHRcy6iolra8Rd9p-s9awix_ucr_DXZojKANyhSb8pRcjDzGUJz7q-Z5nXUJ6MxKxiB/s395/20.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="275" data-original-width="395" height="279" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzZ7MyXuk3mhzKefsuqKAeHWonDhCMKjNm5K1BG7T-MLHrOvlH0KXLY0FkXY3Myk47gQFbfiSZfINoWCY0NKdM5FwIMPn61KkF3Nu81aOXKfXFKBuVlCV5QUVLuGHRcy6iolra8Rd9p-s9awix_ucr_DXZojKANyhSb8pRcjDzGUJz7q-Z5nXUJ6MxKxiB/w400-h279/20.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvy_tONzyaCZZwRndWcSNa4Zn7iKD6EWC2w0c88R5T4ne4ntYZt3i_2JC8lVnCfUy0fJ7te6VVNIUU-NtsexUQfiJRS9p7KNCMGJU76zMzQagGvgkcb449neLsU5W7yTEfIIyXqGw7LucLc-6K5KW_k8XbVHJNzeGySKuC33trUywO_t8Xh48eJmeAP5uC/s1920/21.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="945" data-original-width="1920" height="198" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvy_tONzyaCZZwRndWcSNa4Zn7iKD6EWC2w0c88R5T4ne4ntYZt3i_2JC8lVnCfUy0fJ7te6VVNIUU-NtsexUQfiJRS9p7KNCMGJU76zMzQagGvgkcb449neLsU5W7yTEfIIyXqGw7LucLc-6K5KW_k8XbVHJNzeGySKuC33trUywO_t8Xh48eJmeAP5uC/w400-h198/21.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">After saving, you can verify if the user/system relationship has been correctly configured using the Check Connection button.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhiYZmaAWDtzqv9a4W86R7l9DNoJ66lzfMq3A2AYjy-YVjOxU8jGd6Scl1d8Ey7B8Yg-5WL0ag1dYyl1jdPiXvEJluRNo304VoxF-dgF_vfcZ2hSuLoyDnUE7BRnV7gaWbY74PITI_aa15gTUvBg1HJ0EIZATHTwO2FW1THmCYBr5kk3z-Z1S9aUAs3TdtQ/s1846/22.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." border="0" data-original-height="297" data-original-width="1846" height="64" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhiYZmaAWDtzqv9a4W86R7l9DNoJ66lzfMq3A2AYjy-YVjOxU8jGd6Scl1d8Ey7B8Yg-5WL0ag1dYyl1jdPiXvEJluRNo304VoxF-dgF_vfcZ2hSuLoyDnUE7BRnV7gaWbY74PITI_aa15gTUvBg1HJ0EIZATHTwO2FW1THmCYBr5kk3z-Z1S9aUAs3TdtQ/w400-h64/22.png" title="How to attach documents to a Journal Entry within SAP S/4HANA Public Cloud from ABAP." width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">If you get an error, please check the Outbound User has the right password in Communication System.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>8. Consume the Attachment API from an ABAP Class.</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ You can consume the API using ABAP with the following code.</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;"> TRY.</div><div class="separator" style="clear: both;"> DATA(lo_destination) = cl_http_destination_provider=>create_by_comm_arrangement(</div><div class="separator" style="clear: both;"> comm_scenario = 'ZCS_ATTACHMENT' "Communication Arrangement</div><div class="separator" style="clear: both;"> service_id = 'ZOS_API_ATTACHMENT_REST' "Outbound Service).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> DATA(lo_http_client) = cl_web_http_client_manager=>create_by_http_destination( i_destination = lo_destination ).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> "Set CSRF Token</div><div class="separator" style="clear: both;"> lo_http_client->set_csrf_token( ).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> DATA(lo_request) = lo_http_client->get_http_request( ).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> lo_request->set_header_field( i_name = 'Slug' i_value = iv_filename )."Filename (with extension)</div><div class="separator" style="clear: both;"> lo_request->set_header_field( i_name = 'BusinessObjectTypeName' i_value = iv_bo_type ). "BKPF</div><div class="separator" style="clear: both;"> lo_request->set_header_field( i_name = 'LinkedSAPObjectKey' i_value = iv_bo_key ). "Journal Entry concatenate key fields.</div><div class="separator" style="clear: both;"> lo_request->set_content_type( content_type = iv_mimetype ). "Mimetype</div><div class="separator" style="clear: both;"> lo_request->set_binary( i_data = iv_attachment ). "File content in binary</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> DATA(lo_response) = lo_http_client->execute( i_method = if_web_http_client=>post ).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> DATA(ls_status) = lo_response->get_status( ).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> IF ls_status-code NE 201.</div><div class="separator" style="clear: both;"> "Catch error (the attachment hasn't be created)</div><div class="separator" style="clear: both;"> ENDIF.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> CATCH cx_web_message_error INTO DATA(lx_web).</div><div class="separator" style="clear: both;"> "Catch error (the service is misconfigured)</div><div class="separator" style="clear: both;"> ENDTRY.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><div class="separator" style="clear: both;">Please take a look to "iv_" variables and replace them with valid information. or include the code into a class method with these variables, all of them are strings.</div></div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-58362754725442728302024-03-11T14:57:00.003+05:302024-03-11T14:57:25.990+05:30SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA<p><b>Introduction –</b></p><p>As we know B systems contain a large volume of data that is only accessed rarely. The data is either never or rarely needed in Data Warehouse processes or for analysis. The main challenge of implementing a multi-temperature memory strategy is to seamlessly integrate the warm and cold memory areas and to make these areas invisible to the outside, in order to ensure that all required functions are applied to this data. SAP offers various solutions, which help to reduce TCO SAP IQ NLS is one of them to reduce load by cold data <span></span></p><a name='more'></a><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3sjbC6_QaDLL8QoZ9Q1ZgD6VXJDF9u5ki_l0lAsng8wZXIGo79d27dbNGhNGmpLssuVXy2qpbrxmd70rVuvnq28ga12JCerKDpLgMoxmPvdiENnkVR6RBp-ZNcMkUwjuMPY9A1m0PoL3YcG26OBmUHh2IE-ecCMsOrgvWXAB6PadTzMVaXTPPbDoKgauI/s960/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="393" data-original-width="960" height="164" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3sjbC6_QaDLL8QoZ9Q1ZgD6VXJDF9u5ki_l0lAsng8wZXIGo79d27dbNGhNGmpLssuVXy2qpbrxmd70rVuvnq28ga12JCerKDpLgMoxmPvdiENnkVR6RBp-ZNcMkUwjuMPY9A1m0PoL3YcG26OBmUHh2IE-ecCMsOrgvWXAB6PadTzMVaXTPPbDoKgauI/w400-h164/1.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">SAP IQ based Nearline storage can be used to offload the data and reduce main-memory data footprint further. Typically, the data is sliced based on the time dimensions or it can be completely moved into the cold storage DB. The read access to IQ NLS is in most cases much faster than READ access to the traditional databases. The unique advantage of such a native solution is that the performance of the BW query that requires the data from the Sybase IQ store can be optimized using HANA SDA (Smart Data Access). Smart data access enables remote data access as if they are local tables in HANA without copying data into HANA. It is highly optimized, high-performance and decision-support server designed specifically for mission-critical business intelligence, analytics, data warehousing and Component Integration Services within SAP .Sybase IQ provide direct access to relational and non-relational databases on mainframe, UNIX, or Windows server. SAP IQ (formerly known as SAP Sybase IQ or Sybase IQ; IQ for Intelligent Query) is a column-based, petabyte scale, relational database software system used for business intelligence, data warehousing, and data marts</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Its primary function is to analyze large amounts of data in a low-cost, highly available environment. SAP IQ is often credited with pioneering the commercialization of column-store technology. At the foundation of SAP IQ lies a column store technology that allows for speed compression and ad-hoc analysis. SAP IQ has an open interface approach towards its ecosystem. SAP IQ is also integrated with SAP's Business Intelligence portfolio of products to form an end-to-end business analytics software stack, and is an integral component of SAP's In-Memory Data Fabric Architecture and Data Management Platform.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Architecture :</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Below diagram is sap IQ data base Architecture -</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-qTtTl7zthghDlD0VXZdD4obd2MGdHxPv3f-fK_ZG5rP1Ny2VQeKoD3RZBPGw4AQMzhUiATyjzvLSlZzWX69-RcVaneVvMTFFycIeODmKhjssbBCt8ZM1kBLFftjkZuYB5zBw23qJnK-yYaRXI-R4TXc9F2VrPXnoMLnLyRROkiZ_coJgoJdT9AW2L7uk/s819/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="791" data-original-width="819" height="386" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-qTtTl7zthghDlD0VXZdD4obd2MGdHxPv3f-fK_ZG5rP1Ny2VQeKoD3RZBPGw4AQMzhUiATyjzvLSlZzWX69-RcVaneVvMTFFycIeODmKhjssbBCt8ZM1kBLFftjkZuYB5zBw23qJnK-yYaRXI-R4TXc9F2VrPXnoMLnLyRROkiZ_coJgoJdT9AW2L7uk/w400-h386/2.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Communication between BW and SAP IQ via NLS interface</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgK1nLOMdB-DjmlRJruCpy7FbPLEYzg4Pltw6F9Y8YGZ5wQLamp3callR_3-BbH4NZhEIEIJZNrVmhP3y0tiRkCPLbj-80TNmTJeyT6veIUAQFY9tx5lq_5r4twXQZREtTKJNQPzqhcAYGXuh88QHTn1XPboZ5I7Zv4BXyJEx0SgI9vZ_rkWD_VnQ_vQ5SM/s629/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="331" data-original-width="629" height="210" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgK1nLOMdB-DjmlRJruCpy7FbPLEYzg4Pltw6F9Y8YGZ5wQLamp3callR_3-BbH4NZhEIEIJZNrVmhP3y0tiRkCPLbj-80TNmTJeyT6veIUAQFY9tx5lq_5r4twXQZREtTKJNQPzqhcAYGXuh88QHTn1XPboZ5I7Zv4BXyJEx0SgI9vZ_rkWD_VnQ_vQ5SM/w400-h210/3.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Pre-installation Tasks:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>Check for Operating System Patches- check snote - 3060790</li><li>Increase the Swap Space- Recommended minimum swap space is 1 GB.</li><li>Check Port Availability for SAP IQ Cockpit - HTTP Port: 4282 HTTPS Port: 4283 ,RMI Port: 4992 ,TDS Port: 499</li><li>Verify Network Functionality- verify that the server where you plan to install SAP IQ can use TCP/IP to communicate with other devices on your network.</li><li>Disable HugePages - Remove the HugePages options from /etc/ sysctl.conf and restore the kernel to the default configuration</li><li>Transparent HugePages - Disable Transparent HugePages to avoid SAP IQ performance problems.</li><li>Set the Kernel Parameters-Set the number of available semaphore identifiers to at least 4096.</li><li>Create the SAP IQ Account</li><li>Download Installation Files login on sap market place and download require software based on you infrastructure</li></ul></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Installation -</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The below flowchart gives you an overview of the major tasks to install and implement a SAP IQ system on an Azure Linux VM. Some configuration and post steps need to be done by BW team.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgR5Ud8KrSKHsG2m42zCjIMWhkK5QwsJ1C33kAalamkZMCCLOZrTRK5HzLiesClzZdZ6VNFPRXLTXAZiXYJPgAMpqn9PzElsohL4GKhQJbKMEP7hEwiEX84kM87RV-UYnoyF9P-B-JYPIt5Jv2oWcL93S7bf3pVAlVOysOikf7b7dbcEiy2ftA27enQaBHq/s740/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="499" data-original-width="740" height="270" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgR5Ud8KrSKHsG2m42zCjIMWhkK5QwsJ1C33kAalamkZMCCLOZrTRK5HzLiesClzZdZ6VNFPRXLTXAZiXYJPgAMpqn9PzElsohL4GKhQJbKMEP7hEwiEX84kM87RV-UYnoyF9P-B-JYPIt5Jv2oWcL93S7bf3pVAlVOysOikf7b7dbcEiy2ftA27enQaBHq/w400-h270/4.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Install SySAM</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Given below are step to install SySAM</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_onjxfnUWf4yZdmjwGF_i_0Ur9fM13DDMPX_v3dmytqYdgg0qGOAxeNvj10PeX0i7J8YL4px8aGGmDNqDKI3QhLHd0XJi-kHd9eqrSEjB1bHfrKJku0OACdBGMdjxN6XZJKn4OTU6PBxBr_85DF1CB-pc0FdAfEWH0xnMNS7HrO7zupCrnfDBc2YF99Si/s973/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="420" data-original-width="973" height="173" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_onjxfnUWf4yZdmjwGF_i_0Ur9fM13DDMPX_v3dmytqYdgg0qGOAxeNvj10PeX0i7J8YL4px8aGGmDNqDKI3QhLHd0XJi-kHd9eqrSEjB1bHfrKJku0OACdBGMdjxN6XZJKn4OTU6PBxBr_85DF1CB-pc0FdAfEWH0xnMNS7HrO7zupCrnfDBc2YF99Si/w400-h173/5.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjZFzCJwm87n5WiVlya8S3t5Cp_trwxuZI96DoqYiyjCJVc0u_1037HIXiwXpSrr7T5HlmPmOp8IQNkAuLuVVBSYXsNwRdTpxJCnZ1x9-57m3nTh3eFmBHTChA5UMbi28MPYFVkSaWib4ma6ri82RQQ8-M-XJCnbxj-UvP1NXHJ6ivDq8iinL0kCg8fn8gt/s1021/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="622" data-original-width="1021" height="244" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjZFzCJwm87n5WiVlya8S3t5Cp_trwxuZI96DoqYiyjCJVc0u_1037HIXiwXpSrr7T5HlmPmOp8IQNkAuLuVVBSYXsNwRdTpxJCnZ1x9-57m3nTh3eFmBHTChA5UMbi28MPYFVkSaWib4ma6ri82RQQ8-M-XJCnbxj-UvP1NXHJ6ivDq8iinL0kCg8fn8gt/w400-h244/6.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Unselect un-relevant component and enter option 11 SySAM License server</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_uSX5sXboBZ_aop6Kr6U3kqYYVlWDuds2tZ-6rlDnLlO3mNWhNkvvlnWkVt_ySlDsmG7GZR3cR2npiu2gFlbrHwKL4Z1A8kTeU_5fEbPOu2iFcrbf0qOeIvdlRamhCspm3lQ-3_8FVk7wPugl2pZjDTi3Wblej5jhStBknB_CrGU-nVHhDyQnoz0UEJGL/s685/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="372" data-original-width="685" height="217" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_uSX5sXboBZ_aop6Kr6U3kqYYVlWDuds2tZ-6rlDnLlO3mNWhNkvvlnWkVt_ySlDsmG7GZR3cR2npiu2gFlbrHwKL4Z1A8kTeU_5fEbPOu2iFcrbf0qOeIvdlRamhCspm3lQ-3_8FVk7wPugl2pZjDTi3Wblej5jhStBknB_CrGU-nVHhDyQnoz0UEJGL/w400-h217/7.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Choose 1 Typical</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgbegReCNMcljMvC87oWmdKyOpcq7UejDHRntalYXTj2zoFQkx396GIUk8SZA8fPZjl9Pk3UJIWULQt37biV-jhXkI3_IKOFkFgCEC6MJHFsy8zDHJC5how98QWfVYZkmy7_5dYzOXvIg_Niv_3qc0MAmBUZgEutB-rMQWpgJ-zGo0eWPhf8QzT-QDGnKJB/s497/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="497" data-original-width="434" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgbegReCNMcljMvC87oWmdKyOpcq7UejDHRntalYXTj2zoFQkx396GIUk8SZA8fPZjl9Pk3UJIWULQt37biV-jhXkI3_IKOFkFgCEC6MJHFsy8zDHJC5how98QWfVYZkmy7_5dYzOXvIg_Niv_3qc0MAmBUZgEutB-rMQWpgJ-zGo0eWPhf8QzT-QDGnKJB/w349-h400/8.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="349" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFMVysPrUl53YFJfDaCdmgP3OFJ-k226ilJM0lHH2QqxYWD-cv3D_Eh7hPwuDiAGu_I8nAo5ejdYSrAU2RcOO-wzZhx1uwi3drFtK55bgJPtgIMZ1mW3VKK7IfvkJupxo5MTQPxLrVzWTYAMzNMv7PikTgtqQf5___5eQLqcTC-6dkvEtIJ8zHTDtL6RMX/s558/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="423" data-original-width="558" height="304" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFMVysPrUl53YFJfDaCdmgP3OFJ-k226ilJM0lHH2QqxYWD-cv3D_Eh7hPwuDiAGu_I8nAo5ejdYSrAU2RcOO-wzZhx1uwi3drFtK55bgJPtgIMZ1mW3VKK7IfvkJupxo5MTQPxLrVzWTYAMzNMv7PikTgtqQf5___5eQLqcTC-6dkvEtIJ8zHTDtL6RMX/w400-h304/9.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiW9CYqIOytS7MLublNkYCcY8TfER55r6mMhZQVOJoLgGtMv-CakAUNHU5HVxcE1KgevNHYiimwtpGdAnUDIjMu_vUOtTm4Tseai8uSahb_YFBu87sCRiypfVRWY4lM0QdiiHq6X_YIL_jxxoyepNXM7D5IVNCoKp3YbWEUHTOIyi91CrbAwipHrxvYDrum/s545/10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="149" data-original-width="545" height="109" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiW9CYqIOytS7MLublNkYCcY8TfER55r6mMhZQVOJoLgGtMv-CakAUNHU5HVxcE1KgevNHYiimwtpGdAnUDIjMu_vUOtTm4Tseai8uSahb_YFBu87sCRiypfVRWY4lM0QdiiHq6X_YIL_jxxoyepNXM7D5IVNCoKp3YbWEUHTOIyi91CrbAwipHrxvYDrum/w400-h109/10.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"> Now you can see below directory.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipGfoUy5RSzbnixPI42YuFcM5cRbbCzK5aVwP-y9Bv3dxvMYd3ni8IrunEOI2CWbKOqT4jhK3WzL-sD3a1ryREh7gK4F04BcGHk0xTs3r2P0F5JtZJw4ikV7PoqJM0P71jysNFSom-8Poa1-7pIfIrtZXElGt9orZ_L9HCPhibnVDj5p_WvAg1TlwzIyrq/s943/11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="322" data-original-width="943" height="136" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipGfoUy5RSzbnixPI42YuFcM5cRbbCzK5aVwP-y9Bv3dxvMYd3ni8IrunEOI2CWbKOqT4jhK3WzL-sD3a1ryREh7gK4F04BcGHk0xTs3r2P0F5JtZJw4ikV7PoqJM0P71jysNFSom-8Poa1-7pIfIrtZXElGt9orZ_L9HCPhibnVDj5p_WvAg1TlwzIyrq/w400-h136/11.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Install SAP IQ Server</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjP9n4_ruA3mNnupVuMcxaJOiMZoyx_bOIqhaybpm1PsKPHwaYXT9VV6H9FbYRecye7sjKMCrZhm0_yLKK-fNz4KBluIUjOnN2CBjMLldxwkIIcInKMgn4NfyzNBgw9NR8NEEhIrr6mIFUTfpveiTyfeNA2QvNWlJZq1SXc3TPWq0fBxdBo_bM2cuBE5z6_/s606/12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="460" data-original-width="606" height="304" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjP9n4_ruA3mNnupVuMcxaJOiMZoyx_bOIqhaybpm1PsKPHwaYXT9VV6H9FbYRecye7sjKMCrZhm0_yLKK-fNz4KBluIUjOnN2CBjMLldxwkIIcInKMgn4NfyzNBgw9NR8NEEhIrr6mIFUTfpveiTyfeNA2QvNWlJZq1SXc3TPWq0fBxdBo_bM2cuBE5z6_/w400-h304/12.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMNUj86R9bNrNUHqgM2uxCtLtTaIOnWp25GE_OiMwN9vdA7i6a2Pq103865b-R_qh7-VYdz1RbkoaViRnnWbz9RYmYAmpFb7VWWjro2FgTNY2LGfS6uU-pM4dQufkabk3cDxcfJ3G6ENSbm-tfeU7j0ymC6WtMdcv8dFwtuwPKzkWVS6FrZ3jVRngTPbww/s728/13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="642" data-original-width="728" height="353" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMNUj86R9bNrNUHqgM2uxCtLtTaIOnWp25GE_OiMwN9vdA7i6a2Pq103865b-R_qh7-VYdz1RbkoaViRnnWbz9RYmYAmpFb7VWWjro2FgTNY2LGfS6uU-pM4dQufkabk3cDxcfJ3G6ENSbm-tfeU7j0ymC6WtMdcv8dFwtuwPKzkWVS6FrZ3jVRngTPbww/w400-h353/13.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhpvgdJw3PifLHrB4EYvjMnAl5qQMydX5ibxlnmrUdl1OR2WHgNJ4dv-xhx_ttETxW6_O6XBmcZH5fxd8MM2FKIogU37KOeM8qANirMS6ktsga9ZuUXe_CGuejN2IeOqaIioNmC4WWCLOJl6XfSH5cenjYmr2r1zgiKF4yu3pZmwtYhsOZP39UbBLC0tmps/s893/14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="257" data-original-width="893" height="115" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhpvgdJw3PifLHrB4EYvjMnAl5qQMydX5ibxlnmrUdl1OR2WHgNJ4dv-xhx_ttETxW6_O6XBmcZH5fxd8MM2FKIogU37KOeM8qANirMS6ktsga9ZuUXe_CGuejN2IeOqaIioNmC4WWCLOJl6XfSH5cenjYmr2r1zgiKF4yu3pZmwtYhsOZP39UbBLC0tmps/w400-h115/14.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOjcIvVCITRATcUHUivHM5M5lF4tY_X5Wl7aTiMEBYJ-1rNhcaIN6-fatBpIqLo3CFAywmTDXpSADcfSHy71eNewjFXtPuK0Pj6OfNrHvPOdjqL09SnRfX6crL2qA6xU6_rii_18i4qj_rGq7nhYgIaKRemIp0yJ9DKMQxfAjjsueJW7PoHuvwurxDtBJS/s876/15.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="336" data-original-width="876" height="154" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOjcIvVCITRATcUHUivHM5M5lF4tY_X5Wl7aTiMEBYJ-1rNhcaIN6-fatBpIqLo3CFAywmTDXpSADcfSHy71eNewjFXtPuK0Pj6OfNrHvPOdjqL09SnRfX6crL2qA6xU6_rii_18i4qj_rGq7nhYgIaKRemIp0yJ9DKMQxfAjjsueJW7PoHuvwurxDtBJS/w400-h154/15.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhc_sORhKO2nh9YAyZhTb-1_0p3Pz4RoPXwzBTGSRUB4H7mWeHwVYy9A5QSevXsfrKe7ftuuA5zeSLW9_pIiifxWs7VMCSlBpmXYJw4r-T4PaLTcREc3tBJ-_kIDjpdx74DTn52ct55BH3zGeVd61LXMemSwqrq5MA-5R03hSDdMlFqfYGNIXX85znvpzQd/s669/16.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="669" data-original-width="664" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhc_sORhKO2nh9YAyZhTb-1_0p3Pz4RoPXwzBTGSRUB4H7mWeHwVYy9A5QSevXsfrKe7ftuuA5zeSLW9_pIiifxWs7VMCSlBpmXYJw4r-T4PaLTcREc3tBJ-_kIDjpdx74DTn52ct55BH3zGeVd61LXMemSwqrq5MA-5R03hSDdMlFqfYGNIXX85znvpzQd/w398-h400/16.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="398" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_uZ6ek0CxGVqzxtxJR5aOWV9jx2urIkninXvgUUWOWTcC96R0VqLEfaFLGM-IdoiUFLut_mr5odU6_eetaH4xmdq5J1MN_1ngPeb-fmsE6Oggk6vtnLhJjJ6cpqPwdcqYVK0zOox2n0eIDdiz59olfQwrWbP_guk1NFqsJzgHa1Ov10TBicVm_ooWWI29/s823/17.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="574" data-original-width="823" height="279" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_uZ6ek0CxGVqzxtxJR5aOWV9jx2urIkninXvgUUWOWTcC96R0VqLEfaFLGM-IdoiUFLut_mr5odU6_eetaH4xmdq5J1MN_1ngPeb-fmsE6Oggk6vtnLhJjJ6cpqPwdcqYVK0zOox2n0eIDdiz59olfQwrWbP_guk1NFqsJzgHa1Ov10TBicVm_ooWWI29/w400-h279/17.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipFp1TnF8muqOWqFH1hQfor6mBPzT7jW3c5kVgquPLcBsQJroXJ1U_RaG9-kQZ2vlfPzrLzIDWDhvykOPoKxZGl6GwaLUly9KmUKfSU5gt2Agcy9ixVhPE8YRo0oGGuDjclnErdsUXJ3yyatK970QL10ZfGseBgswcJLREeBZiAlLairkkJzMH4gD744Px/s868/18.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="632" data-original-width="868" height="291" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipFp1TnF8muqOWqFH1hQfor6mBPzT7jW3c5kVgquPLcBsQJroXJ1U_RaG9-kQZ2vlfPzrLzIDWDhvykOPoKxZGl6GwaLUly9KmUKfSU5gt2Agcy9ixVhPE8YRo0oGGuDjclnErdsUXJ3yyatK970QL10ZfGseBgswcJLREeBZiAlLairkkJzMH4gD744Px/w400-h291/18.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7JVqhsTBa4xdFIqPk4FjtdsqOSNUWE9q6JKrFXd-G66VrUu50oJ057ixGpNtAqZlxlF3PjrDyXF4vuHhSsWXmWzcV2Red9lixUKcVZY27o58EKNTjJMBNwcaYcmz-iwXHLGm9ZPB-RN9wmjf4_cj_w5r2ZTuwXKbmUGkrnVHwtOkke03tEDLxIrqrjF_j/s877/19.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="532" data-original-width="877" height="243" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7JVqhsTBa4xdFIqPk4FjtdsqOSNUWE9q6JKrFXd-G66VrUu50oJ057ixGpNtAqZlxlF3PjrDyXF4vuHhSsWXmWzcV2Red9lixUKcVZY27o58EKNTjJMBNwcaYcmz-iwXHLGm9ZPB-RN9wmjf4_cj_w5r2ZTuwXKbmUGkrnVHwtOkke03tEDLxIrqrjF_j/w400-h243/19.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEigRQCBrvow_Oi5gTW3TIFBcYn3EKGhT1WbbwPiFFXl-ECs0bGiD-d2PSMC82Wq0Eof344OVQe1ljLSs2A-RHsPU2eVHK6vgvXCZbot_a-21aGM_RkQWdu2VDHyZ1pI2M1X3DaM9qhy4ic8eiu63BVN2fVseWNXuQRLElzVJrtolDtxbaTvdrXDz4c3fV4-/s762/20.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="556" data-original-width="762" height="291" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEigRQCBrvow_Oi5gTW3TIFBcYn3EKGhT1WbbwPiFFXl-ECs0bGiD-d2PSMC82Wq0Eof344OVQe1ljLSs2A-RHsPU2eVHK6vgvXCZbot_a-21aGM_RkQWdu2VDHyZ1pI2M1X3DaM9qhy4ic8eiu63BVN2fVseWNXuQRLElzVJrtolDtxbaTvdrXDz4c3fV4-/w400-h291/20.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJD1x6LymO3rR3nbRkmkoSID9aOZ3hxvOwuM7H7ZdBebI7utdPNwDmt-4q84rLi6qHkhH1qSMjntJyblAj7C1cplGhfyL4tI8nlcwnv4L4P8Zvd1ooC0EXhmXgwGm7p-2kjH9hwunFbEmn-mynb1rkazFHT7tPkI1A5feUHOwqpfcQyVNCztnZM7uoBgwJ/s724/21.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="406" data-original-width="724" height="224" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJD1x6LymO3rR3nbRkmkoSID9aOZ3hxvOwuM7H7ZdBebI7utdPNwDmt-4q84rLi6qHkhH1qSMjntJyblAj7C1cplGhfyL4tI8nlcwnv4L4P8Zvd1ooC0EXhmXgwGm7p-2kjH9hwunFbEmn-mynb1rkazFHT7tPkI1A5feUHOwqpfcQyVNCztnZM7uoBgwJ/w400-h224/21.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQQ5toASWuxMQ5GuvJSw6H1XxY7DT8rjbhQOS5LVtRIXC98lflgS8uMNWTQENx4-LKJz9gR5TBnGQNkmNAxcnjOcXeDlc6Pb3w2K7L9MnCrwqeV5BxsY_ptXtyxvK1exqSm5WTAws0C7Q3KYEi5FmoC9Z_7XsmBAoPVqvlhjRYDOjT5Qw3Ef_DHvwRWahr/s723/22.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="544" data-original-width="723" height="301" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQQ5toASWuxMQ5GuvJSw6H1XxY7DT8rjbhQOS5LVtRIXC98lflgS8uMNWTQENx4-LKJz9gR5TBnGQNkmNAxcnjOcXeDlc6Pb3w2K7L9MnCrwqeV5BxsY_ptXtyxvK1exqSm5WTAws0C7Q3KYEi5FmoC9Z_7XsmBAoPVqvlhjRYDOjT5Qw3Ef_DHvwRWahr/w400-h301/22.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi8ovqgujKElM2TKaykHCGSdLPI9zboTzBTafYPWZloIkLkzt42-RfM-WJRv4QaqN81GruzEJ3VXAe6fzo3OpEtbrSj5UDzA7ROyrayKM742ELvtMziA2TmG5Ji5dgk4DOJtnRDNXoXE5F8JPeAbNAdgU2q81FRb3wHwcDKZxPUt0kbO34eLkp3L3SqYlKg/s926/23.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="719" data-original-width="926" height="310" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi8ovqgujKElM2TKaykHCGSdLPI9zboTzBTafYPWZloIkLkzt42-RfM-WJRv4QaqN81GruzEJ3VXAe6fzo3OpEtbrSj5UDzA7ROyrayKM742ELvtMziA2TmG5Ji5dgk4DOJtnRDNXoXE5F8JPeAbNAdgU2q81FRb3wHwcDKZxPUt0kbO34eLkp3L3SqYlKg/w400-h310/23.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgupjsR0ZXkOGNFejjUt28Gu5ju4Yy-i8AU4SVceeeBu0iW0vIcUJReZKFLnWDABw6ZvqbqyAOqUkLDpIDf26QEuJoTcELl0Spf3Jj3DPFMgZbYnlYH-OVydpEti6GG3saHeJV9_Ze8iJIBk9ZR-vcjYquckd87kzifHkcDrcoRIn2YTuuY2aQWPK6EuDKj/s718/24.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="574" data-original-width="718" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgupjsR0ZXkOGNFejjUt28Gu5ju4Yy-i8AU4SVceeeBu0iW0vIcUJReZKFLnWDABw6ZvqbqyAOqUkLDpIDf26QEuJoTcELl0Spf3Jj3DPFMgZbYnlYH-OVydpEti6GG3saHeJV9_Ze8iJIBk9ZR-vcjYquckd87kzifHkcDrcoRIn2YTuuY2aQWPK6EuDKj/w400-h320/24.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgE6RXZrOknZYUOhsoayWX85RsUoCIxPaYDCQ33fru5KbYBgwlz2uyexvrItTO1Iw0_-ezK1o3vTFziodS64OjU7hRL2UNBCurnOAUujGTAQaZablnfGkMrYqMwL9nc9Uz_ltuFlIii0Mpr0GaeYQu5HTAvDOYYMXnN2X1JJYGaw1bY8ko3w4njJ9fVm1Js/s700/25.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="232" data-original-width="700" height="133" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgE6RXZrOknZYUOhsoayWX85RsUoCIxPaYDCQ33fru5KbYBgwlz2uyexvrItTO1Iw0_-ezK1o3vTFziodS64OjU7hRL2UNBCurnOAUujGTAQaZablnfGkMrYqMwL9nc9Uz_ltuFlIii0Mpr0GaeYQu5HTAvDOYYMXnN2X1JJYGaw1bY8ko3w4njJ9fVm1Js/w400-h133/25.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7g_JzevfpEBUFu2hvZj3C5D2gdzHvs0xYZIWKn7TpW4k1gpFF2kUxl5fWf05-WXv9dUHe9T0_3NEV8TCpBa0EhF4JrF4UX5gJd0GofPsr8hGzWGKc2hTcm-0O6-V8IoG6sN25XfW6f2bfHTf-NuVk2Bdda2IjhtEQpKrjpn5LE49lKo1DvwYq6MA6H3y5/s734/26.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="529" data-original-width="734" height="289" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7g_JzevfpEBUFu2hvZj3C5D2gdzHvs0xYZIWKn7TpW4k1gpFF2kUxl5fWf05-WXv9dUHe9T0_3NEV8TCpBa0EhF4JrF4UX5gJd0GofPsr8hGzWGKc2hTcm-0O6-V8IoG6sN25XfW6f2bfHTf-NuVk2Bdda2IjhtEQpKrjpn5LE49lKo1DvwYq6MA6H3y5/w400-h289/26.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Start IQ</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Command : start_iq -n utility -x "tcpip{port=34238}" -su *****</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIrvnvuMWjXuGsVi35VCDynN0j17yzaIV8geK5iK3kjZY1ZY9Igv61v8dPB25JRxKCZWUkzqRGbIWdGqKV2OHLqWkxU-Zl_0S7_LWiM2MzXfbpQLVKVtuib1WDn04W7Vohv8TCiptkhs5HckLRmMiR7B5LVywkMlqQmbo1-M8y0A5bbzTNBZTtSQyrq5ex/s816/27.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="598" data-original-width="816" height="294" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIrvnvuMWjXuGsVi35VCDynN0j17yzaIV8geK5iK3kjZY1ZY9Igv61v8dPB25JRxKCZWUkzqRGbIWdGqKV2OHLqWkxU-Zl_0S7_LWiM2MzXfbpQLVKVtuib1WDn04W7Vohv8TCiptkhs5HckLRmMiR7B5LVywkMlqQmbo1-M8y0A5bbzTNBZTtSQyrq5ex/w400-h294/27.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQFvDbNQ7S-sn3wjHbPEe-xKTostMLUwElq3k_DUiu6P3V6pX7EwMgnrkMLUdUTfoMFSWRClZ0pGMn2Ro_pGOuY24oLC3Vzm6r8kQPHrhKvQF0z6enJme4zRc896iEwwmTCUXmfNeiGnkn9dj_8PlXcIilB7Y5dVUIoGZzIzffHzEQJpszwaDBb6zsNY3x/s1505/28.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="574" data-original-width="1505" height="153" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQFvDbNQ7S-sn3wjHbPEe-xKTostMLUwElq3k_DUiu6P3V6pX7EwMgnrkMLUdUTfoMFSWRClZ0pGMn2Ro_pGOuY24oLC3Vzm6r8kQPHrhKvQF0z6enJme4zRc896iEwwmTCUXmfNeiGnkn9dj_8PlXcIilB7Y5dVUIoGZzIzffHzEQJpszwaDBb6zsNY3x/w400-h153/28.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiuHj4E5mfYeYDcWQLjXJO3ir-v2bgvfjVrrujg7JpHHHQqYqOxq9YJGBxEaSBdU8A2AFmBGyIPL8RRbdj6YQKkHU04nmgq6F32h0gPW8Xm5nQS7yVMC3vn88S8YI-lB7BigY8pZHyHXl63wPeIQ1iSTxXC2xnUvY_IWP10dMl69x_ZIdnfWzN24W9Nrcyp/s848/29.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="757" data-original-width="848" height="358" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiuHj4E5mfYeYDcWQLjXJO3ir-v2bgvfjVrrujg7JpHHHQqYqOxq9YJGBxEaSBdU8A2AFmBGyIPL8RRbdj6YQKkHU04nmgq6F32h0gPW8Xm5nQS7yVMC3vn88S8YI-lB7BigY8pZHyHXl63wPeIQ1iSTxXC2xnUvY_IWP10dMl69x_ZIdnfWzN24W9Nrcyp/w400-h358/29.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzmSpwpv10HGjhPnOjRSktuKSYnpxCBvf-q37qdvTD_TIuLLkAV-5AIxIKZIhaPET4wi-NuWeqD_FEJ-lmhCvGa9lI-w_p_ikSkwvu8Ceox_bXfZGc1S6UpriCNuifGTHlQv4AyeQ3tC0DG9M9HxFGmgEDzeqYJaPVIDscu_IZ_Apfae5eZFFj1BHF-Qjn/s719/30.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="231" data-original-width="719" height="129" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzmSpwpv10HGjhPnOjRSktuKSYnpxCBvf-q37qdvTD_TIuLLkAV-5AIxIKZIhaPET4wi-NuWeqD_FEJ-lmhCvGa9lI-w_p_ikSkwvu8Ceox_bXfZGc1S6UpriCNuifGTHlQv4AyeQ3tC0DG9M9HxFGmgEDzeqYJaPVIDscu_IZ_Apfae5eZFFj1BHF-Qjn/w400-h129/30.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Installing client on BW dB and App server</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxsQwkwlOSBSIuzk_ZYBxew0uJORX8oLycjnCXci-lhLsq8FnPQCE23uCc8dC_jzdQkCw9Gg_li7oBmPjiwWraj30rguLK0KPA-t1k5YU7Db0HBZ1b394AEB2Zk11ZAHp0UIkP00TmqNXhNxB5Ymey8cndsZysDfxrODBBFxNPYcvvcY-22tsXPXYS7T62/s708/31.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="499" data-original-width="708" height="283" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxsQwkwlOSBSIuzk_ZYBxew0uJORX8oLycjnCXci-lhLsq8FnPQCE23uCc8dC_jzdQkCw9Gg_li7oBmPjiwWraj30rguLK0KPA-t1k5YU7Db0HBZ1b394AEB2Zk11ZAHp0UIkP00TmqNXhNxB5Ymey8cndsZysDfxrODBBFxNPYcvvcY-22tsXPXYS7T62/w400-h283/31.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEim2bvPmywTCG343sWUj89J8b3lC4BISfy8v6wfz4PsFqwRL1k_FojmaJvtuk190QWjPoZF49enwtppQm-BtmjpH9WuNi7bbUprvB3Bod688PboOvg0XD-oLJDS715l5EBiQnQbgX1fiy8cd37i5aqj3RdTG-94V8hJg-bmXlObMR0WAFO5pD2qYAePyD9m/s568/32.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="568" data-original-width="490" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEim2bvPmywTCG343sWUj89J8b3lC4BISfy8v6wfz4PsFqwRL1k_FojmaJvtuk190QWjPoZF49enwtppQm-BtmjpH9WuNi7bbUprvB3Bod688PboOvg0XD-oLJDS715l5EBiQnQbgX1fiy8cd37i5aqj3RdTG-94V8hJg-bmXlObMR0WAFO5pD2qYAePyD9m/w345-h400/32.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="345" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgc3RquI9YuKQCsyPqtI0kk4_IBoNfipHiWNmsxohprPTMngFs8b4CiCgAVlHUcag84NKZ47RM9jX2OmJ7Iw9Og7QgGHsIaUwuk90GRBvJ3zS3MPNC9riXFX8xhhquLi2b98Q6w01Y6cFBsghzsvtVsIm_xFmytHO91koNvWokypDy5h0CrX7unwAFaugGr/s595/33.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="595" data-original-width="454" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgc3RquI9YuKQCsyPqtI0kk4_IBoNfipHiWNmsxohprPTMngFs8b4CiCgAVlHUcag84NKZ47RM9jX2OmJ7Iw9Og7QgGHsIaUwuk90GRBvJ3zS3MPNC9riXFX8xhhquLi2b98Q6w01Y6cFBsghzsvtVsIm_xFmytHO91koNvWokypDy5h0CrX7unwAFaugGr/w305-h400/33.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="305" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjalZCpccvwVH8mkZwcDYXOiNmVRwe3DqvotvJ9_RocDWyCSRqulgzhpaUoVaz_QPIlx9xFZAWh5CA5N5w_EEKT3BNSErrSp8HyvipSM9jiHkfCXc1u4cxBgCbfAWqx6In-L7onUHCEgktgp_USFJMzk99yAPG3A0nQtRiHb-y40aFBrxeTi5GNQGy-hKcK/s737/34.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="693" data-original-width="737" height="376" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjalZCpccvwVH8mkZwcDYXOiNmVRwe3DqvotvJ9_RocDWyCSRqulgzhpaUoVaz_QPIlx9xFZAWh5CA5N5w_EEKT3BNSErrSp8HyvipSM9jiHkfCXc1u4cxBgCbfAWqx6In-L7onUHCEgktgp_USFJMzk99yAPG3A0nQtRiHb-y40aFBrxeTi5GNQGy-hKcK/w400-h376/34.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhyHQ-I_SRlXgsD_6AUXscyOOSGKbw5HNCDp3NG3mzOSW_AaKP1OOslDdwJXuDj46t4foKUEqLU95S_jfGgeoQU-uLKpgFeLybIsC4D0CQnCiqAsRPTY4HbPON4WRoIpiCMsWngf9rkvF5xkdBr0g_p7vI3qavPAQWiQZPcMUWOEfdCgl0y6q6vOAHr3up9/s636/35.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="388" data-original-width="636" height="244" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhyHQ-I_SRlXgsD_6AUXscyOOSGKbw5HNCDp3NG3mzOSW_AaKP1OOslDdwJXuDj46t4foKUEqLU95S_jfGgeoQU-uLKpgFeLybIsC4D0CQnCiqAsRPTY4HbPON4WRoIpiCMsWngf9rkvF5xkdBr0g_p7vI3qavPAQWiQZPcMUWOEfdCgl0y6q6vOAHr3up9/w400-h244/35.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Install SDA</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhVsbMvN8wxnwrzYEhltWh5ii3WKSBtLwjAO4w_L_bewqNv5ODh8qWFQGcCIUIs3Lsqk9nAyatYm3kSIzNOM6O2D86cDhzVwVNJbucsFRYGoMNSY03hnhwmqjdk4b_g5TPgCgafEyiq5Lf9jR6cVRl9EgTUmow_4ebHooznj0ifbXY4g_8Ahenc6xRaobZ0/s824/36.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="356" data-original-width="824" height="173" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhVsbMvN8wxnwrzYEhltWh5ii3WKSBtLwjAO4w_L_bewqNv5ODh8qWFQGcCIUIs3Lsqk9nAyatYm3kSIzNOM6O2D86cDhzVwVNJbucsFRYGoMNSY03hnhwmqjdk4b_g5TPgCgafEyiq5Lf9jR6cVRl9EgTUmow_4ebHooznj0ifbXY4g_8Ahenc6xRaobZ0/w400-h173/36.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Check all environment variable as per IQ installation document</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Configuration</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Logon to BW system and update RSADMIN table using report SAP_RSADMIN_MAINTAIN</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzB4sZwI9uthxATf9Ajka812lt_u2wKRpRysOsMyrmUKvpQDF8k1edWOM0Iwb3g1lRhCjUxt0TXm06giZcXiFbivoa-lGZAW1Geoi9rXi2fmR7CM5-Gh06tmnP3zvOWt2eH9A-fj7xZWQc9GiVE3Cv5RFeus05ZpNtwjACn6nmTPzT5qfi96SYRH8QReCH/s694/37.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="364" data-original-width="694" height="210" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzB4sZwI9uthxATf9Ajka812lt_u2wKRpRysOsMyrmUKvpQDF8k1edWOM0Iwb3g1lRhCjUxt0TXm06giZcXiFbivoa-lGZAW1Geoi9rXi2fmR7CM5-Gh06tmnP3zvOWt2eH9A-fj7xZWQc9GiVE3Cv5RFeus05ZpNtwjACn6nmTPzT5qfi96SYRH8QReCH/w400-h210/37.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgIztPUrsp_86dJaUEMtpGoF5pzZtAc5uvsmNld1PzK1P3oZBwzJ0L37Sfjogizd0biKNYFGzypSW6hVc1jGm3nMLE5Nlgc2gbAGV9JASgZvjcU6IWyGWDVbwtvUl0NyO0C3duzvKD05zwQiwBhNkSPdNz_HGueKjWazzGISVAvnpD4KR9HF9NObZhbrg43/s708/38.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="280" data-original-width="708" height="159" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgIztPUrsp_86dJaUEMtpGoF5pzZtAc5uvsmNld1PzK1P3oZBwzJ0L37Sfjogizd0biKNYFGzypSW6hVc1jGm3nMLE5Nlgc2gbAGV9JASgZvjcU6IWyGWDVbwtvUl0NyO0C3duzvKD05zwQiwBhNkSPdNz_HGueKjWazzGISVAvnpD4KR9HF9NObZhbrg43/w400-h159/38.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Create DBCO Connection</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBFabqW6seaEGcm_URC8TVhyV51ZyyIf6G4E_Zw7vKvqlwzqd7cwGfuWCXTCNoLaYePt1e-6EE-7865PN8T2Xn2B_IYLpcGmHvPL_IUfsoJqzIAyFAFsb0dvmbme2vIokUXIpDq7vZ2rFJZ96UEmzGYTfADWpCI_msicNR4baG9fetF3CXD3xbU8noi3rg/s760/39.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="343" data-original-width="760" height="180" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBFabqW6seaEGcm_URC8TVhyV51ZyyIf6G4E_Zw7vKvqlwzqd7cwGfuWCXTCNoLaYePt1e-6EE-7865PN8T2Xn2B_IYLpcGmHvPL_IUfsoJqzIAyFAFsb0dvmbme2vIokUXIpDq7vZ2rFJZ96UEmzGYTfADWpCI_msicNR4baG9fetF3CXD3xbU8noi3rg/w400-h180/39.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhqrICzG78H98KyRqOUXE5GO706qUTFInJaOWEbhIytr2deR4IzL9bvon_zoswaALx4MPYP6tjtteNo9jkMbRYHr6jhwlUwUjb_MxPtokY33CJerR78B99m3jb-8hNVy4n1xgWgmofkqyb7Qz-FLX6ADCds0SjSjF36_d_YiWoRoodq2P3xnmtbTs1Kj1pU/s639/40.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="250" data-original-width="639" height="156" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhqrICzG78H98KyRqOUXE5GO706qUTFInJaOWEbhIytr2deR4IzL9bvon_zoswaALx4MPYP6tjtteNo9jkMbRYHr6jhwlUwUjb_MxPtokY33CJerR78B99m3jb-8hNVy4n1xgWgmofkqyb7Qz-FLX6ADCds0SjSjF36_d_YiWoRoodq2P3xnmtbTs1Kj1pU/w400-h156/40.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGKmoV0cg0heOyBbJTvtTRc8dYHhFhb-gtEtNisoEjsFqrQwi1Xf4HoUOp2oMxM7DVFn8o5tkxhgJAlaM2RY9v1FvJ00CHZpMRRzR-WZOHDTT4Mw2JWZOfZf63qViKWCuQhUAt6DpAN7_MxA1gjd6o4pcHpkBpwXK3I5TUi1dO8o9Eh-kc_wJ2qDHioFeD/s666/41.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="204" data-original-width="666" height="122" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGKmoV0cg0heOyBbJTvtTRc8dYHhFhb-gtEtNisoEjsFqrQwi1Xf4HoUOp2oMxM7DVFn8o5tkxhgJAlaM2RY9v1FvJ00CHZpMRRzR-WZOHDTT4Mw2JWZOfZf63qViKWCuQhUAt6DpAN7_MxA1gjd6o4pcHpkBpwXK3I5TUi1dO8o9Eh-kc_wJ2qDHioFeD/w400-h122/41.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgqLFFSf5aiFL1XsJFnDqQob-X4o6JQQRGuVZJ-4jS6lNBgPavin-FFIP38o6A4gSrjtcegDYkKkcZEclymaOez32xGTQ-NvJ3wJZqIggu0FIJDq1OFk_-1yuElbkUctwp-GdiXBgvly7owiZGXfVEa7eKQyIg9aweXbMYeRgASGtmqTt3Vqnqii2VNqHqB/s766/42.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="532" data-original-width="766" height="278" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgqLFFSf5aiFL1XsJFnDqQob-X4o6JQQRGuVZJ-4jS6lNBgPavin-FFIP38o6A4gSrjtcegDYkKkcZEclymaOez32xGTQ-NvJ3wJZqIggu0FIJDq1OFk_-1yuElbkUctwp-GdiXBgvly7owiZGXfVEa7eKQyIg9aweXbMYeRgASGtmqTt3Vqnqii2VNqHqB/w400-h278/42.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEifC4oG-yI23ljBdj9_nDkK0EaIxjVlwyJHYOaBEIe3eOu-JH6nstjiBuBKV7u9x5fc-TOoyfQh1-sGZi4tQH2QrEWCenS5Yi69iDRkg7P7T0zPTqBtmQnxRKOU9T55GI-pLtkd7FSUl2iH81meZLJx9KUqfs9YfUhD3BgSvp2xMqrZAqO6ng5dsMF4M5iN/s750/43.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="472" data-original-width="750" height="251" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEifC4oG-yI23ljBdj9_nDkK0EaIxjVlwyJHYOaBEIe3eOu-JH6nstjiBuBKV7u9x5fc-TOoyfQh1-sGZi4tQH2QrEWCenS5Yi69iDRkg7P7T0zPTqBtmQnxRKOU9T55GI-pLtkd7FSUl2iH81meZLJx9KUqfs9YfUhD3BgSvp2xMqrZAqO6ng5dsMF4M5iN/w400-h251/43.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Transaction DBACOCKPIT</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhttktALydkIMCLuSmbPLn1wkky1dquqzyLGMWecYCMSObf24EUX5iRPbmK8VWiowe37CFi4PlXZUp3t93fPC9xYkDpALCP55laAqyPq1DvL2pce5UQ9haJAdYl_FQTMB-3D9C0Mu4Z22vw8yCeyrkrTpOp2U2bkFWnAlOCjFt8aOmNC8-x9UE4kkZLF55M/s757/44.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="282" data-original-width="757" height="149" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhttktALydkIMCLuSmbPLn1wkky1dquqzyLGMWecYCMSObf24EUX5iRPbmK8VWiowe37CFi4PlXZUp3t93fPC9xYkDpALCP55laAqyPq1DvL2pce5UQ9haJAdYl_FQTMB-3D9C0Mu4Z22vw8yCeyrkrTpOp2U2bkFWnAlOCjFt8aOmNC8-x9UE4kkZLF55M/w400-h149/44.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Add</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">And test connectivity</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3TUzp-_vBSjspWwDZ7l8CmcbKmSpLTNGkzTMXTSo489dR2D6GJ48gnGIUDIpnJ0gp89cpAKax7en4NOWnb7J2gTALcNZk4ziBjr6eBYduzuJzyj4WwA5gdQbFWHffVWI0bhLW5Tb-jKZrzNp1PF2_8O-ZZ8jVQiRmMfAca3-uN1HF6eIXV2admp-BeYLV/s736/45.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="82" data-original-width="736" height="45" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3TUzp-_vBSjspWwDZ7l8CmcbKmSpLTNGkzTMXTSo489dR2D6GJ48gnGIUDIpnJ0gp89cpAKax7en4NOWnb7J2gTALcNZk4ziBjr6eBYduzuJzyj4WwA5gdQbFWHffVWI0bhLW5Tb-jKZrzNp1PF2_8O-ZZ8jVQiRmMfAca3-uN1HF6eIXV2admp-BeYLV/w400-h45/45.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi9cghaDogB4YK-eLLNtpUwYWq2iwrHL9Tmze-TzhPNfdOenU6cZy3P1aNiOeK3uZQzJtcHYjYK8MnsTintbOfG8h89Gb9SL7ustl1oPY2ahZ2lQ4028wo_3Fh8uOhzIUek30kBaikeTGJTE4GrZA-TG3D6DaMwRrMA_f0raHeXC_p5aOUrk4DgVd48HRPh/s525/46.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" border="0" data-original-height="525" data-original-width="509" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi9cghaDogB4YK-eLLNtpUwYWq2iwrHL9Tmze-TzhPNfdOenU6cZy3P1aNiOeK3uZQzJtcHYjYK8MnsTintbOfG8h89Gb9SL7ustl1oPY2ahZ2lQ4028wo_3Fh8uOhzIUek30kBaikeTGJTE4GrZA-TG3D6DaMwRrMA_f0raHeXC_p5aOUrk4DgVd48HRPh/w388-h400/46.png" title="SAP IQ NLS-The Cold Storage Solution for SAP BW/4HANA" width="388" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-4730066300878575912024-03-08T12:53:00.003+05:302024-03-08T12:53:33.113+05:30Protecting Your SAP HANA Cloud and SAP HANA with Credential Rotation Best Practices<div>In today's cyber-threat landscape, prioritizing data security is more important than ever. Security is one of the key cornerstones of SAP BTP and SAP HANA Cloud strategies. </div><div><br /></div><div>SAP HANA Cloud takes a comprehensive approach to security, providing a layered defense system encompassing authentication, authorization, encryption, and auditing. </div><div><br /></div><div>At the heart of this security strategy lies strong credentials management practices, one of which is the credentials rotation. For example, organizations can significantly reduce the risk of unauthorized access and data breaches by enforcing regular password rotation.<span><a name='more'></a></span></div><div><br /></div><h3 style="text-align: left;"><b>Certificate-based credentials are the game-changer </b></h3><div><br /></div><div>While strong passwords and their rotation are a must, they're no longer enough. We recommend using certificate-based credentials, a robust security practice that adds an extra layer of protection and should be adopted by all SAP HANA users. </div><div><br /></div><div>Certificate-based credentials offer a far more robust solution. Here's what you get: </div><div><br /></div><div><ul style="text-align: left;"><li><b>Multi-factor Authentication (MFA):</b> Imagine needing both a certificate and a secondary factor (e.g., PIN, fingerprint) to access your HANA environment. MFA is typically done at identity provider and mainly in combination with short-lived SAML/JWT tokens for the actual database access. </li><li><b>Rotation:</b> Hackers adore static credentials, but with certificates, they expire regularly, rendering stolen ones useless, and you can no longer use them for login. It's like changing the locks on your house now and then, depending on how often you need it. The benefit of certificates is that you can have multiple certificates for an overlapping time range when changing them. </li><li><b>Reduced Attack Surface:</b> Fewer passwords to manage mean fewer potential entry points for attackers. It's like having fewer windows to climb through. </li></ul></div><div><br /></div><div>In case there is still the need to work with password-based authentication, there are a couple of password rotation tricks on how you can enhance your security and which HANA supports. </div><div><br /></div><h3 style="text-align: left;"><b>How Password Rotation Works in SAP HANA Cloud </b></h3><div><br /></div><div>Password rotation, also known as password aging, is a security protocol that mandates the periodic change of passwords for user accounts. This practice helps to mitigate the risk of unauthorized access if a password is compromised. </div><div><br /></div><div>In SAP HANA Cloud, password rotation is controlled by password policies that can be customized to meet specific organizational requirements. These policies can specify a <a href="https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-security-guide/password-policy-configuration-options" target="_blank">wide range of configuration options</a> like the minimum password length, the required character types, the minimum/maximum password lifetime, and the frequency with which passwords must be updated. </div><div><br /></div><div>The SAP Cloud HANA database comes with a default password policy. You can change the default password policy of the database in line with your organization’s security requirements. </div><div><br /></div><div>Disclaimer: from the HANA side there is no difference for password management between on-premise HANA and HANA Cloud. </div><div><br /></div><div><b>Scenario 1: "Zero down time password change" for database users </b></div><div><br /></div><div>In case your organisation needs to sustain changing passwords for HANA database users without experiencing any interruption in service or accessibility, or in other words, the HANA Cloud DB should remain fully functional and accessible while changing/updating passwords for those users – it is supported by the product. </div><div><br /></div><div>On the other hand, in case under “zero downtime password change” is also meant changing the password of a user in HANA without having to change the password used to connect to HANA at the same time in their application to avoid failed connect attempts (something like this can be achieved by allowing connect for one user with multiple passwords) – SAP HANA Cloud DB only supports a single password per user at a time. </div><div><br /></div><div>The proper way to avoid this issue is to use other means of authentication, typically <a href="https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-security-guide/x-509-certificate-based-user-authentication" target="_blank">X.509</a>. In that case you would only configure trust to the X.509 issuer in HANA and set a new X.509 certificate in the application before the current one expires. The same can be achieved if the application supports our <a href="https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-security-guide/single-sign-on-integration" target="_blank">SAML/JWT</a> authentication. </div><div><br /></div><div>As a short summary, this is not a limitation on the SAP HANA Cloud DB side but on the application side. </div><div><br /></div><div><b>Scenario 2: How to manage technical users with regards to password rotation and their authentication in general? </b></div><div><br /></div><div>For technical users, our recommendation remains the same: to use X.509 or SAML/JWT authentication when possible. If password-based authentication is used, this will require any potential password change to be performed simultaneously both in the HANA database and on all clients to avoid failed logins or locking of the technical user due to such failed logins. </div><div><br /></div><div>Moving all application access of the technical users to X.509-based authentication will also allow them to update the certificates of the services individually without having to coordinate this as it would be required for a central password change. </div><div><br /></div><div>Individual users could still authenticate using passwords, and this distinction would even allow to differentiate between service access and user access. On top of this, you can still rotate the passwords safely if anyone is leaving. </div><div><br /></div><div><b>Important:</b> it is recommended to use dedicated database users and not mix technical and named user access in case you have a technical user that is used by services to access the HANA DB, and they seem to also use that same database user for their real users to access the database. </div><div><br /></div><div>Additionally, what you can do for password change is to: </div><div><br /></div><div>1. Suspend the system during the change of the password.</div><div><br /></div><div>2. Disable on the HANA DB the user lock temporarily by setting <a href="https://help.sap.com/docs/SAP_HANA_PLATFORM/b3ee5778bc2e4a089d3299b82ec762a7/61662e3032ad4f8dbdb5063a21a7d706.html#user-lock-time" target="_blank">User Lock Time</a> to 0 when changing the password. Then, you have time to change the password on the database and the clients. </div><div><br /></div><div><b>Important:</b> However, there will almost be a timespan (change of password in user store and change of password on SAP HANA DB) where no application user can work on the system. </div><div><br /></div><div><b>Scenario 3: Several teams are working on a project and sharing the same HANA database user across the group</b></div><div><br /></div><div>If your concern is that if anyone leaves the project or company, they are still able to access the database through, for example, Database Explorer, or if they have an S-User ID, we recommend the following: </div><div><br /></div><div><ul style="text-align: left;"><li>Presumably, when someone leaves the company, their user will be removed from the identity provider and will no longer be able to log in. As for the database users, it might be possible to setup SSO with a mapping between the user used to sign into the identity provider and the database. In that way, once the user is removed from the identity provider, they would no longer be able to log in to the database. </li><li>Deletion of separate DB users for each person and make sure the DB user is deleted if a person moves off the project team or company. </li><li>Move away from password-based authentication, so another option would be to set up SSO or certificated-based authentication (e.g., X509 or JWT) for created users. Still, you need to delete the respective mapping after the user leaves the project to ensure it has no access like pointed out above for identity provider set up. </li><li>Perform a password rotation in the current setup (if possible) whenever a user is leaving the project if you decide to stay with password-based authentication: </li><li>You can use the 'ALTER USER <user> FORCE PASSWORD CHANGE' syntax to force a password rotation on the next login for any user (including SYSTEM);</li></ul></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-52352437795103626712024-03-06T14:02:00.001+05:302024-03-06T14:02:28.087+05:30Global Explanation Capabilities in SAP HANA Machine Learning<div>Machine learning (ML) has great potential for improving products and services across various industries. However, the explainability of ML models is crucial for their widespread adoption. First, explanation helps build trust and transparency between the users and the models. When users understand how ML model works, they are more likely to trust its results. Moreover, explainability allows for better debugging of complex models. By providing explanations for models’ decisions, researchers can gain insights into the underlying patterns, which helps identify potential biases or flaws. Furthermore, the explainability of models enables auditing, a prerequisite for its usage in regulated industries, such as finance and healthcare.<span><a name='more'></a></span></div><div><br /></div><div>To benefit from an explainable model, we introduced permutation feature importance as a global explanation method to SAP HANA Predictive Analysis Library (PAL) in the past several months. In this blog post, we will show how to use it in Python machine learning client for SAP HANA (hana-ml), which provides a friendly Python API for many algorithms from PAL.</div><div><br /></div><div>After reading this blog post, you will learn:</div><div><br /></div><div>◉ Permutation feature importance from its theory to usage</div><div>◉ Two alternative global explanation methods available and their comparison to permutation feature importance</div><div><br /></div><h3 style="text-align: left;"><b>Permutation feature importance</b></h3><div><br /></div><div>Permutation feature importance is a feature evaluation method that measures the decrease in the model score when we randomly shuffle the feature's values. It reveals the extent to which a specific feature contributes to the overall predictive power of the model by breaking the association between the feature and the true outcome.</div><div><br /></div><div>Behind the screen the permutation importance is calculated in the following steps:</div><div><br /></div><div>i. Initially, a reference score is evaluated on the original dataset.</div><div>ii. Next, a new dataset is generated by permuting the column of a specific feature, and the score is evaluated again.</div><div>iii. Then the permutation importance is defined as the difference between the reference score and the score obtained from permuted dataset.</div><div><br /></div><div>By repeating the second and third steps for each feature, we can get the importance scores for the entire dataset.</div><div><br /></div><div>Permutation importance provides highly compressed, global insight to gauge the relative importance of each feature, enabling data scientists and analysts to prioritize their efforts on the most influential variables when building and optimizing models. This approach is particularly useful for handling high-dimensional datasets, as it helps identify the most informative features amidst a vast number of possible predictors.</div><div><br /></div><div>Here we use the well-known Titanic dataset to illustrate the usage of permutation importance. In hana-ml, there is a class called DataSets that offers various public datasets. To load the dataset, we can utilize the load_titanic_data method.</div><div><br /></div><div>from hana_ml import dataframe</div><div>from hana_ml.algorithms.pal.utility import DataSets</div><div><br /></div><div>conn = dataframe.ConnectionContext(url, port, user, pwd)</div><div>titanic_full, _, _, _ = DataSets.load_titanic_data(conn)</div><div><br /></div><div>Titanic dataset describes the survival status of individual passengers on the RMS Titanic. The objective is to predict based on passenger data (i.e. name, age, gender, socio-economic class, etc.) whether a passenger can survive the shipwreck. In our dataset we have 12 columns, and the meaning of each column is below:</div><div><br /></div><div><ul style="text-align: left;"><li>PassengerId - Unique ID assigned to each passenger.</li><li>Pclass - Class of ticket purchased (1 = 1st class, 2 = 2nd class, 3 = 3rd class).</li><li>Name - Full name and title of the passenger.</li><li>**bleep** - Gender of the passenger.</li><li>Age - The Age of the passenger in years.</li><li>SibSp - Number of siblings and spouses associated with the passenger aboard.</li><li>Parch - Number of parents and children associated with the passenger aboard.</li><li>Ticket - Ticket number.</li><li>Fare - The fare of the ticket purchased by the passenger.</li><li>Cabin - The Cabin number that the passenger was assigned to. If NaN, this means they had no cabin and perhaps had not assigned one due to the cost of their ticket.</li><li>Embarked - Port of embarkation (S = Southampton, C = Cherbourg, Q = Queenstown).</li><li>Survived - Survival flag of passenger (0 = No, 1 = Yes), target variable.</li></ul></div><div><br /></div><div>To keep things simple and stay on track with our example, we will remove columns with a high number of null values and then build a predictive model to forecast survival status using the remaining features. We rely on PAL's built-in support in classification algorithm for handling other data preprocessing issues like missing values and dataset splitting.</div><div><br /></div><div>from hana_ml.algorithms.pal.unified_classification import UnifiedClassification</div><div><br /></div><div>rdt_params = dict(n_estimators=100,</div><div> max_depth=56,</div><div> min_samples_leaf=1,</div><div> split_threshold=1e-5,</div><div> random_state=1,</div><div> sample_fraction=1.0)</div><div>uc_rdt = UnifiedClassification(func = 'RandomDecisionTree', **rdt_params)</div><div><br /></div><div>features = ["PCLASS", "NAME", "**bleep**", "AGE", "SIBSP", "PARCH", "FARE", "EMBARKED"]</div><div>uc_rdt.fit(data=titanic_full, key='PASSENGER_ID', features=features, label='SURVIVED',</div><div> partition_method='stratified', stratified_column='SURVIVED', partition_random_state=1,</div><div> training_percent=0.7, output_partition_result=True,</div><div> ntiles=2, categorical_variable=['PCLASS','SURVIVED'], build_report=False,</div><div> permutation_importance=True, permutation_evaluation_metric='accuracy',</div><div> permutation_n_repeats=10, permutation_seed=1, permutation_n_samples=None)</div><div><br /></div><div>RandomDecisionTree has a practical method for estimating missing data. When it comes to training data, the method calculates the median of all values for numerical variable or the most frequent non-missing value for categorical variable in a certain class, and then uses that value to replace all missing values of that variable within that class. As for test data, the class label is absent, so one missing value is replicated for each class and filled with the corresponding class’s median or most frequent item.</div><div><br /></div><div>UnifiedClassification has a method for dataset splitting, so we can use it to randomly split our dataset, using 70% for training and leaving the rest for validating. In addition, RandomDecisionTree has built-in support for categorical variables; all we need to do is specify the parameter categorical_variable for variables that come in integer type.</div><div><br /></div><div>To enable the calculation of permutation feature importance, set permutation_importance to True. Additionally, use permutation_evaluation_metric to define the evaluation metric for importance calculation. For classification problems, options include accuracy, auc, kappa and mcc, while for regression problems, options are RMSE, MAE and MAPE. Set permutation_n_repeats to specify the number of times a feature is randomly shuffled. Because shuffling the feature introduces randomness, the results might vary greatly when the permutation is repeated. Averaging the importance measures over repetitions stabilizes the measure at the expense of increased computation time. Use permutation_seed to set the seed for randomly permuting a feature column, which ensures reproducible results across function calls. Moreover, set permutation_n_samples to determine the number of samples to draw in each repeat. While this option may result in less accurate importance estimates, it helps manage computational speed when evaluating feature importance on large datasets. By combining permutation_n_samples with permutation_n_repeats, we can control the trade-off between computational speed and statistical accuracy of this method.</div><div><br /></div><div>Permutation importance does not indicate the inherent predictive value of a feature but how important this feature is for a specific model. It is possible that features considered less important for a poorly performing model (with a low cross-validation score) could actually be highly significant for a well-performing model. Therefore it is crucial to assess the predictive power of a model using a held-out set prior to determining importances.</div><div><br /></div><div>uc_rdt.statistics_.collect()</div><div><br /></div><table border="1" style="width: 100%;">
<tbody>
<tr>
<td><b>STAT_NAME</b></td>
<td><b>STAT_VALUE</b></td>
<td><b>CLASS_NAME</b></td>
</tr>
<tr>
<td>AUC </td>
<td>0.7385321100917431 </td>
<td>None</td>
</tr>
<tr>
<td>RECALL </td>
<td>0.9674418604651163</td>
<td>0 </td>
</tr>
<tr>
<td>PRECISION </td>
<td>0.7247386759581882</td>
<td>0 </td>
</tr>
<tr>
<td>F1_SCORE </td>
<td>0.8286852589641435</td>
<td>0 </td>
</tr>
<tr>
<td>SUPPORT </td>
<td>215 </td>
<td>0</td>
</tr>
<tr>
<td>RECALL </td>
<td>0.29464285714285715</td>
<td>1 </td>
</tr>
<tr>
<td>PRECISION </td>
<td>0.825</td>
<td>1 </td>
</tr>
<tr>
<td>F1_SCORE </td>
<td>0.43421052631578944 </td>
<td>1 </td>
</tr>
<tr>
<td>SUPPORT </td>
<td>112 </td>
<td>1</td>
</tr>
<tr>
<td>ACCURACY </td>
<td>0.7370030581039755</td>
<td>None </td>
</tr>
<tr>
<td>KAPPA </td>
<td>0.3097879442371883</td>
<td>None </td>
</tr>
<tr>
<td>MCC </td>
<td>0.37957621849462986</td>
<td>None </td>
</tr>
</tbody>
</table><br /><div><div>We can check the model performance on validation set directly from fitted attribute statistics_. Its validation performance, measured via the accuracy score, is significantly larger than the chance level. This makes it possible to use permutation importance to probe the most predictive features.</div><div><br /></div><div>import matplotlib.pyplot as plt</div><div><br /></div><div>df_imp = uc_rdt.importance_.filter('IMPORTANCE >= 0').collect()</div><div>df_imp = df_imp.sort_values(by=['IMPORTANCE'], ascending=True)</div><div><br /></div><div>c_title = "Permutation Importance"</div><div>df_imp.plot(kind='barh', x='VARIABLE_NAME', y='IMPORTANCE', title=c_title, legend=False, fontsize=12)</div><div>plt.show()</div><div><br /></div><div>Feature importances are provided by the fitted attribute importances_. We can visually represent the feature contributions using a bar chart.</div></div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkCO6vsOyIa5A2bTkixH03RMhpFbmM8z55soMLBam7F8vJOBwNtZgqyDep2CnZQRXyAdDdImSEY7Im0ygN1m5kvdboN2OFH3L-ZJdeMQ2MLsv7eErn4D7jQu492QeZBdmvGxdc0VCRmSZMV_SNz8rvVHvG0MWtDI9q0t7_6nbe_lc1ifM_n_Ys3jJtPfpJ/s564/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Global Explanation Capabilities in SAP HANA Machine Learning" border="0" data-original-height="267" data-original-width="564" height="189" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkCO6vsOyIa5A2bTkixH03RMhpFbmM8z55soMLBam7F8vJOBwNtZgqyDep2CnZQRXyAdDdImSEY7Im0ygN1m5kvdboN2OFH3L-ZJdeMQ2MLsv7eErn4D7jQu492QeZBdmvGxdc0VCRmSZMV_SNz8rvVHvG0MWtDI9q0t7_6nbe_lc1ifM_n_Ys3jJtPfpJ/w400-h189/1.png" title="Global Explanation Capabilities in SAP HANA Machine Learning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">While there is some element of luck involved in surviving, it seems some groups of people were more likely to survive than others. The most important features for predicting survival status with a random forest are **bleep**, Pclass and fare, whereas passenger’s family relations or name are deemed less important.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">This is reasonable because women were given priority access to the lifeboats, so they were more likely to survive. Also, both Pclass and fare can be regarded as a proxy for socio-economic status (SES). People with higher SES may have had better access to information, resources, and connections to secure a spot on a lifeboat or be rescued more quickly. They may also possess more experience with navigating emergency situations and better access to survival skills and knowledge.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Compared to gender and SES, factors such as port of embarkation, family relations, or name played a limited role in survival. Because the chaotic and rapidly evolving nature of the sinking meant that all passengers were subject to the same evacuation protocols, these factors were less relevant in determining a passenger's likelihood of survival.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Apart from permutation feature importance, there are two additional techniques existing in PAL can be used to gain a global explanation. One is impurity-based feature importance computed on tree-based models and another is SHAP feature importance obtained by aggregating local Shapley values for individual predictions. We will delve into these methods individually through the subsequent two case studies.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Case Study: impurity-based feature importance</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Tree-based models provide an alternative measure of feature importance deriving from nodes’ splitting process.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Individual decision trees intrinsically perform feature selection by selecting appropriate split points. This information can be used to measure the importance of each feature; the basic idea is if a feature is frequently used in split points, it is considered more important. In practice, importance is calculated for a single decision tree by evaluating how much each attribute split point improves performance, weighted by the number of observations under each node. The performance measure may be the purity used to select the split points or another more specific error function.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">This notion of importance can be extended to decision tree ensembles by simply averaging the impurity-based feature importance of each tree. By averaging the estimates over several randomized trees, the variance of the estimate is reduced, making it suitable for feature selection. This is known as the mean decrease in impurity, or MDI.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Note that this computation of feature importance is based on the splitting criterion of the decision trees (such as Gini index), and it is distinct from permutation importance which is based on permutation of the features.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">We show the calculation of impurity-based importance on Titanic dataset. The calculation is incorporated in the fitting of RandomDecisionTree, as demonstrated in the code below.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">from hana_ml.algorithms.pal.unified_classification import UnifiedClassification</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">rdt_params = dict(n_estimators=100,</div><div class="separator" style="clear: both;"> max_depth=56,</div><div class="separator" style="clear: both;"> min_samples_leaf=1,</div><div class="separator" style="clear: both;"> split_threshold=1e-5,</div><div class="separator" style="clear: both;"> random_state=1,</div><div class="separator" style="clear: both;"> sample_fraction=1.0)</div><div class="separator" style="clear: both;">uc_rdt = UnifiedClassification(func = 'RandomDecisionTree', **rdt_params)</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">features = ["PCLASS", "NAME", "**bleep**", "AGE", "SIBSP", "PARCH", "FARE", "EMBARKED"]</div><div class="separator" style="clear: both;">uc_rdt.fit(data=titanic_full, key='PASSENGER_ID', features=features, label='SURVIVED',</div><div class="separator" style="clear: both;"> partition_method='stratified', stratified_column='SURVIVED', partition_random_state=1,</div><div class="separator" style="clear: both;"> training_percent=0.7, output_partition_result=True,</div><div class="separator" style="clear: both;"> ntiles=2, categorical_variable=['PCLASS','SURVIVED'], build_report=False</div><div class="separator" style="clear: both;"> )</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">uc_rdt.statistics_.collect()</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Prior to inspecting feature importance, it is important to ensure that the model predictive performance is high enough. Indeed, there is no point in analyzing the important features of a non-predictive model. Here we can observe that the validation accuracy is high, indicating that the model can generalize well thanks to the built-in bagging of random forests.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The feature importance scores of a fitted model can be accessed via the importance_ property. This dataframe has rows representing each feature, with positive values that add up to 1.0. Higher values indicate a greater contribution of the feature to the prediction function.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">import matplotlib.pyplot as plt</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">df_imp = uc_rdt.importance_.collect()</div><div class="separator" style="clear: both;">df_imp = df_imp.sort_values(by=['IMPORTANCE'], ascending=True)</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">c_title = "Impurity-based Importance"</div><div class="separator" style="clear: both;">df_imp.plot(kind='barh', x='VARIABLE_NAME', y='IMPORTANCE', title=c_title, legend=False, fontsize=12)</div><div class="separator" style="clear: both;">plt.show()</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">A bar chart is plotted to visualize the feature contributions.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg76Pkzb_0wSVHoIoYj9uKRuSVA7EYPNFsPN1frKC9Nd4VFer74ZuIteO14yLjZRe7Vt65wt_787gSgeSfZu1GQIS6PYWZ4WX__h_c3DfQCJiozoePvVRdk8eVm3v3XmPrr1AHMb6-16oBJOh5Np8nzIDZDAKcn8v6GDq1P-F-Jt9zr5fe7_fvL6-ueZT1N/s438/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Global Explanation Capabilities in SAP HANA Machine Learning" border="0" data-original-height="267" data-original-width="438" height="244" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg76Pkzb_0wSVHoIoYj9uKRuSVA7EYPNFsPN1frKC9Nd4VFer74ZuIteO14yLjZRe7Vt65wt_787gSgeSfZu1GQIS6PYWZ4WX__h_c3DfQCJiozoePvVRdk8eVm3v3XmPrr1AHMb6-16oBJOh5Np8nzIDZDAKcn8v6GDq1P-F-Jt9zr5fe7_fvL6-ueZT1N/w400-h244/2.png" title="Global Explanation Capabilities in SAP HANA Machine Learning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Oops! The non-predictive passenger’s name is ranked most important by the impurity-based method which contradicts the permutation method. However, the conclusions regarding the importance of the other features still hold true. The same three features are detected most important by both methods, although their relative importance may vary. The remaining features are less predictive.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">So, the only question is why impurity-based feature importance assigns high importance to variables that are not correlated with the target variable (survived).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">This stems from two limitations of impurity-based feature importance. First, impurity-based importance can inflate the importance of high cardinality features, that is features with many unique values (such as passenger’s name). Furthermore, impurity-based importance suffers from being computed on training set statistics and it cannot be evaluated on a separate set, therefore it may not reflect a feature’s usefulness for make predictions that generalize to unseen data (if the model has the capacity to use the feature for overfit).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The fact that we use training set statistics explains why passenger’s name has a non-null importance. And the bias towards high cardinality features explains further why the importance has such a large value.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">As shown in previous example, permutation feature importance does not suffer from the flaws of the impurity-based feature importance: it does not exhibit a bias toward high-cardinality features and can be computed on a left-out validation set (as we do in PAL). Using a held-out set makes it possible to identify the features that contribute the most to the generalization power of the inspected model. Features that are important on the training set but not on the held-out set might cause the model to overfit. Another key advantage of permutation feature importance is that it is model-agnostic, i.e. it can be used to analyze any model class, not just tree-based models.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">However, the computation for full permutation importance is more costly. There are situations that impurity-based importance is preferable. For example, if all features are numeric and we are only interested in representing the information acquired from the training set, limitations of impurity-based importance don’t matter. If these conditions are not met, permutation importance is recommended instead.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Now that we have completed our exploration of impurity-based importance, let's shift our focus to SHAP feature importance.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Case Study: SHAP feature importance</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">SHAP (SHapley Additive exPlanations) is a technique used to explain machine learning models. It has its foundations in coalitional game theory, specifically Shapley values. These values determine the contribution of each player in a coalition game. In the case of machine learning, the game is the prediction for a single instance, features act as players, and they collectively contribute to the model’s prediction outcome. SHAP assigns each feature a Shapley value and uses these values to explain the prediction made by the model.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The SHAP calculation can be invoked in the prediction method of UnifiedClassification. Once again, we show its application on Titanic dataset. The RandomDecisionTree model is trained as before. To ensure a more valid comparison to permutation importance, we deliberately employ SHAP on the validation set.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">uc_rdt.partition_.set_index("PASSENGER_ID")</div><div class="separator" style="clear: both;">titanic_full.set_index("PASSENGER_ID")</div><div class="separator" style="clear: both;">df_full = uc_rdt.partition_.join(titanic_full)</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">features = ["PCLASS", "NAME", "**bleep**", "AGE", "SIBSP", "PARCH", "FARE", "EMBARKED"]</div><div class="separator" style="clear: both;">pred_res = uc_rdt.predict(data=df_full.filter('TYPE = 2'), key='PASSENGER_ID', features=features, verbose=False,</div><div class="separator" style="clear: both;"> missing_replacement='feature_marginalized',</div><div class="separator" style="clear: both;"> top_k_attributions=10, attribution_method='tree-shap')</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">pred_res.select("PASSENGER_ID", "SCORE", "REASON_CODE").head(5).collect()</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">SHAP by itself is a local explanation method explains the predictions for individual instances. Since we run SHAP for every instance, we get a matrix of Shapley values. This matrix has one row per data instance and one column per feature. To get a global explanation, we need a rule to combine these Shapley values.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In practice, there are different ways to aggregate local explanations. For instance, we can assess feature importance by analyzing how frequently a feature appears among the top K features in the explanation or by calculating the average ranking for each feature in the explanation. In our case, we opt to use mean absolute Shapley values as an indicator of importance.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The idea behind this is simple: Features with large absolute Shapley values are considered important. Since we want the global importance, we average the absolute Shapley values for each feature across the data. We can then arrange the features in descending order of importance and present them in a plot, like what we have done before. Another simpler solution is to utilize the ShapleyExplainer module as a visualizer and let it handle the task.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">from hana_ml.visualizers.shap import ShapleyExplainer</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">features=["PCLASS", "NAME", "**bleep**", "AGE", "SIBSP", "PARCH", "FARE", "EMBARKED"]</div><div class="separator" style="clear: both;">shapley_explainer = ShapleyExplainer(feature_data=df_full.filter('TYPE = 2').select(features), </div><div class="separator" style="clear: both;"> reason_code_data=pred_res.select('REASON_CODE'))</div><div class="separator" style="clear: both;">shapley_explainer.summary_plot()</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjig7Rvv1fJPtqp4vnIaPopT4C_Tcrs2CgO-SMhDPDxGO9XWeIljU6ofC_XTNBmW83QObgO1ERFd6LTY4TOMG_FVgDE57vpnyAQOBRbSVH7Jltno262SNc2xToebeYAURPPtBaor-dIt7Cguqsa2RL0HT1sCqY6ypqg7ijnurQtfb5jczfW5x39qvEDMU5r/s2000/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Global Explanation Capabilities in SAP HANA Machine Learning" border="0" data-original-height="508" data-original-width="2000" height="101" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjig7Rvv1fJPtqp4vnIaPopT4C_Tcrs2CgO-SMhDPDxGO9XWeIljU6ofC_XTNBmW83QObgO1ERFd6LTY4TOMG_FVgDE57vpnyAQOBRbSVH7Jltno262SNc2xToebeYAURPPtBaor-dIt7Cguqsa2RL0HT1sCqY6ypqg7ijnurQtfb5jczfW5x39qvEDMU5r/w400-h101/3.png" title="Global Explanation Capabilities in SAP HANA Machine Learning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">There is a big difference between SHAP feature importance and permutation feature importance. Permutation feature importance is based on the decrease in model performance, while SHAP is based on magnitude of feature attributions. In other words, SHAP feature importance reflects how much the model’s prediction varies can be explained by a feature without considering its impact on performance. If changing a feature greatly changes the output, then it is considered important. As a result, SHAP importance gives higher importance to features that cause high variation in the prediction function.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Although model variance explained by the features and feature importance are strongly correlated when the model generalizes well (i.e. it does not overfit), this distinction becomes evident in cases where a model overfits. If a model overfits and includes irrelevant features (like the passenger’s name in this instance), the permutation feature importance would assign an importance of zero because this feature does not contribute to accurate predictions. SHAP importance measure, on the other hand, might assign high importance to the feature as the prediction can change significantly when the feature is altered.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Additionally, it is noteworthy that calculating SHAP can be computationally demanding, especially for models that are not based on trees. If you are only looking for a global explanation, it is suggested to use permutation importance.</div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-75313873462201391942024-03-04T14:58:00.002+05:302024-03-04T14:58:07.834+05:30Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA<div>SAP has released several prebuilt AI use cases in each of the process area. These are referred to as Basic AI providing out-of-the-box solutions. The base for this is of course SAP S/4HANA.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEil3MmG45O3RtRCdejTRxgh0F1vd2kr1t3AUSZ0AqjqveO93fWZBSoA8FJjeJ27vNm1Wpj9ZlXzgik1KEql6oWZ2olhlKL6sy4CxcXtc5PjnXmSCVAOsgklh4sCPZMg4fJHQBpvaWnwwpkMFBHTklRkmvBneNLGQfyKHore7ERrIlxoJlPFjRH6uXlwEHr3/s929/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="401" data-original-width="929" height="173" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEil3MmG45O3RtRCdejTRxgh0F1vd2kr1t3AUSZ0AqjqveO93fWZBSoA8FJjeJ27vNm1Wpj9ZlXzgik1KEql6oWZ2olhlKL6sy4CxcXtc5PjnXmSCVAOsgklh4sCPZMg4fJHQBpvaWnwwpkMFBHTklRkmvBneNLGQfyKHore7ERrIlxoJlPFjRH6uXlwEHr3/w400-h173/1.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">The graphic above provides a rough summary of what is available.<span><a name='more'></a></span></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In this blog we will learn how to <b>Create sales order- automatic extraction on your SAP S/4HANA Cloud available as of 2308+ *</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">First a quick summary of why one would activate:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>Complex documents require many mandatory fields to be filled in.</li><li>End users might put incorrect data or might not know the most appropriate information for the field.</li><li>Missing or wrong field values impact the successful processing of the document.</li></ul></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">And the business value for Sales order automation in <a href="https://www.hanaexam.com/p/certifications.html">SAP S/4HANA</a>:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>Enables faster completion to prevent delays in the sales order delivery.</li><li>Reduces redundant tasks to free time for users.</li><li>Reduces the risk of human errors in the process.</li></ul></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Let’s look at its process flow of what we are trying to achieve</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjEgAfi1w1YOZnlvm1JPxusErIewprh2bWBJ7g_4reqRCbncfDbx7X8xoDy3zFzCfovHCzUiSYHR94vLWNj9iTArHcW9NTSHflxO5klyAR2DrCcZKzfsda0nRIHcFI5pBiQ38zvLXiA6L1nGOFoBtD_vdgoLVC9PWizXGKeebHFOsaoegDfmR7ljDrgZvW7/s739/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="575" data-original-width="739" height="311" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjEgAfi1w1YOZnlvm1JPxusErIewprh2bWBJ7g_4reqRCbncfDbx7X8xoDy3zFzCfovHCzUiSYHR94vLWNj9iTArHcW9NTSHflxO5klyAR2DrCcZKzfsda0nRIHcFI5pBiQ38zvLXiA6L1nGOFoBtD_vdgoLVC9PWizXGKeebHFOsaoegDfmR7ljDrgZvW7/w400-h311/2.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">*graphic courtesy help.sap.com</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The scope item 4X9 (Create Sales Orders from Unstructured Data) has been set up for SAP S/4HANA Cloud</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To set this up follow the below steps</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Requesting Scope Item Activation and Related Configurations.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Raise a BCP ticket on component XX-S4C-OPR-SRV, to request SAP to activate scope item 4X9 and configure communication scenario SAP_COM_1129.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Deploying Intelligent Scenario in SAP S/4HANA Cloud.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Open the Intelligent Scenario Management app (business role SAP_BR_ANALYTICS_SPECIALIST), and search for intelligent scenario SO_AUTO_EXTRACTION.</div><div class="separator" style="clear: both;">◉ Within the intelligent scenario, choose the default version.</div><div class="separator" style="clear: both;">◉ On the Deployments tab, activate the default deployment for all.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Before you simulate order, creation or create a sales order, ensure that the sales organization in the sales order request has already been assigned to the company code specified during the file upload.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">On your home screen, then you should be able to see the app Create Sales Order as below.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNe8PRF_FtP-fhipH0YPttPVwunNtV2rLWz_lAdZjge1A9DwL3vXee6lbBvaZLZ-qa7CJUwyhBSAY76QX9Vb9HtDQdB-UGRP_2iFkYp6y7zVfLWP8KVdyVCy0dNqdmkzPTt2k7VJ9m794bAmPwiNGk_-C5CoIfBEvdkv9EHZz317Fq6DiPXF0QEc7kyybR/s940/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="394" data-original-width="940" height="168" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNe8PRF_FtP-fhipH0YPttPVwunNtV2rLWz_lAdZjge1A9DwL3vXee6lbBvaZLZ-qa7CJUwyhBSAY76QX9Vb9HtDQdB-UGRP_2iFkYp6y7zVfLWP8KVdyVCy0dNqdmkzPTt2k7VJ9m794bAmPwiNGk_-C5CoIfBEvdkv9EHZz317Fq6DiPXF0QEc7kyybR/w400-h168/3.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Before uploading a file, make sure that a company code has been entered.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-QbPxW3U0qfzdaaPZklFuNMvdFO1m0Jf-O4opmS3w14MAeKt7e4-b7UoJiOX3QSkrIyMXrOn8HlAaZ7f1wSZ9qKnKgUT3qM_UNZzgHLzA-F14YvIyiE-U1tejYiZcRR-jGjLYJO6J2i9LRzGFcJEKZFDHVguRTl1dVXZPkXHDpcqIcbLeGqOpbnM_np1O/s940/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="523" data-original-width="940" height="223" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-QbPxW3U0qfzdaaPZklFuNMvdFO1m0Jf-O4opmS3w14MAeKt7e4-b7UoJiOX3QSkrIyMXrOn8HlAaZ7f1wSZ9qKnKgUT3qM_UNZzgHLzA-F14YvIyiE-U1tejYiZcRR-jGjLYJO6J2i9LRzGFcJEKZFDHVguRTl1dVXZPkXHDpcqIcbLeGqOpbnM_np1O/w400-h223/4.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">You can upload purchase order files in English or German.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Note:</b> To prevent users from uploading the same file twice, key users can enable a duplicate check using the configuration activity Adapt Settings by Company Code.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-Uor5QD0wFR_AMlQL1JsRyU5s8HNxI9UKK_5p7JVTMd_FQZ7R7FMlQ1489SJySPdmN3RaSGbIQJdW9UkZKu7c6eVWS1W3FWUeoV_I0Dgo37RwlnsIeue5K67TZEhMNLrDn7GZgHj5fKy4aJnvze5m532_cex0Qmx9HEfHU2BYkGVxXGv0c37MSCtZoyfM/s940/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="531" data-original-width="940" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-Uor5QD0wFR_AMlQL1JsRyU5s8HNxI9UKK_5p7JVTMd_FQZ7R7FMlQ1489SJySPdmN3RaSGbIQJdW9UkZKu7c6eVWS1W3FWUeoV_I0Dgo37RwlnsIeue5K67TZEhMNLrDn7GZgHj5fKy4aJnvze5m532_cex0Qmx9HEfHU2BYkGVxXGv0c37MSCtZoyfM/w400-h226/5.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">After the file is uploaded, the system creates a sales order request (containing the uploaded file as an attachment) and starts data extraction. You need to wait some time to view the extraction result. You can retry if data extraction fails.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">After the purchase order information is extracted, the system proposes values for sales order request fields and checks the completeness of request data.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnK1oahquqgLwTkyphgbuHInmAWgvLXrIh9SaVmkG1fKn47zTykhcu0YpmbfEQLJSpvVSggGh01I6QgLGmPGK8h111SNb3KbTtMbK2u9SAzznhLHXj2MNV-33N3uN5kDgVC5lWUG_yTEx03uCnezF_98cLzC4Phn5LjFx3fVNS7vDFEdKj2x-fsT1untf9/s940/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="535" data-original-width="940" height="228" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnK1oahquqgLwTkyphgbuHInmAWgvLXrIh9SaVmkG1fKn47zTykhcu0YpmbfEQLJSpvVSggGh01I6QgLGmPGK8h111SNb3KbTtMbK2u9SAzznhLHXj2MNV-33N3uN5kDgVC5lWUG_yTEx03uCnezF_98cLzC4Phn5LjFx3fVNS7vDFEdKj2x-fsT1untf9/w400-h228/6.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEinLbOtzxMN46lHVrz3CQ-wgVtlnDYZgp2rWt5d4up7C3qa-ANCkZvHmrK4yFlFbvkl13dcxmBEmPa28KZlUZ7drjsM84cGkfLeJaKCK6IVvz_vWs2gDiLBpEBw2k6BHODp02vsD4-MBR9m2D2bjjZb94ioG4UeA5hI714t_8iPSyLGJ7XOV-12TsX8FzzL/s940/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="537" data-original-width="940" height="229" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEinLbOtzxMN46lHVrz3CQ-wgVtlnDYZgp2rWt5d4up7C3qa-ANCkZvHmrK4yFlFbvkl13dcxmBEmPa28KZlUZ7drjsM84cGkfLeJaKCK6IVvz_vWs2gDiLBpEBw2k6BHODp02vsD4-MBR9m2D2bjjZb94ioG4UeA5hI714t_8iPSyLGJ7XOV-12TsX8FzzL/w400-h229/7.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">If the creation has failed with errors, you are informed about the causes, which help you revise the sales order request.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXhf_aJac5ewJXWBmguePDDiCsxiH6m3W6B_hxCA1gBxIWkH5UBWKmrK-w3FLiZoURGmHAIbIqCFBYa2ma-ZFX5Bigt8FOY0Pzh8egArDp_fpOTWhrzKaEi7W6YchpkfQeSxZG4TWfav1U0RQo_Y8TQUUlIwZQNfmHctAoCF5sQfroGh8v860XcXD0jc1L/s940/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="538" data-original-width="940" height="229" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXhf_aJac5ewJXWBmguePDDiCsxiH6m3W6B_hxCA1gBxIWkH5UBWKmrK-w3FLiZoURGmHAIbIqCFBYa2ma-ZFX5Bigt8FOY0Pzh8egArDp_fpOTWhrzKaEi7W6YchpkfQeSxZG4TWfav1U0RQo_Y8TQUUlIwZQNfmHctAoCF5sQfroGh8v860XcXD0jc1L/w400-h229/8.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMfvWCMZke4kcZtJ7ZFHB2iLGOgnbXGt7JSINEMHEddy5ZOGYMLZnF9rE1VfDZMyAlkv5GvETjcoLhyphenhyphenbuPbgO_eNTxgfUVQ3pmovkpZOc7DK8shxZV2U1BSKKJK9S3darMcbJkUs0ZO2tooYaa-u06dxE_DnWh5Tpah4q-mqMk1l7-yux4xZ-OcxNzfKeM/s940/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="531" data-original-width="940" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMfvWCMZke4kcZtJ7ZFHB2iLGOgnbXGt7JSINEMHEddy5ZOGYMLZnF9rE1VfDZMyAlkv5GvETjcoLhyphenhyphenbuPbgO_eNTxgfUVQ3pmovkpZOc7DK8shxZV2U1BSKKJK9S3darMcbJkUs0ZO2tooYaa-u06dxE_DnWh5Tpah4q-mqMk1l7-yux4xZ-OcxNzfKeM/w400-h226/9.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">If request data is incomplete, you must edit it on the object page. If needed, you can open the purchase order file in an embedded pane or in a new window to verify purchasing details.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_H51RJGrhRy9FMjRWN-CDev06VL8NKDD-ImyP5kkADersgv39OuwUt0ay-O3Jjfab8FwCKe6yyjlWRi8O_Ftm7mkQprzA2s0ZT_AAzs964zQr-YG3n4LK5OPnMK5oWEX_3yWguz-jE_h8XQnP0MLYGAdVlfCXsvqWmc7p6tmD05Vg58mz6VRx3e7J-ljV/s940/10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="531" data-original-width="940" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_H51RJGrhRy9FMjRWN-CDev06VL8NKDD-ImyP5kkADersgv39OuwUt0ay-O3Jjfab8FwCKe6yyjlWRi8O_Ftm7mkQprzA2s0ZT_AAzs964zQr-YG3n4LK5OPnMK5oWEX_3yWguz-jE_h8XQnP0MLYGAdVlfCXsvqWmc7p6tmD05Vg58mz6VRx3e7J-ljV/w400-h226/10.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Once the data is rectified the sales order can then be created.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">PS: You can view the application log and change log of each sales order request:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Application log: Shows system processing details regarding data extraction, data proposal, and BAdI call. You can retrieve the records from the last 100 days.</div><div class="separator" style="clear: both;">◉ Change log: Records changes that have been made to sales order request fields, such as creation, editing, and deletion of field values.</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;">*Also available for SAP S/4HANA 2021 + (on Prem/RISE) though the configuration steps will be different.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Now that you have successfully created a sales order via automatic extraction, it is time to setup other embedded AI features. As such feel free to reach out to us via your SAP Account Executive or SAP CSP or Customer Success Manager for the same.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Additionally, here is a brief list of other embedded AI features available for your consumption.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGlflI1oujLScCE8btuCK8L7w9jbd6iRq4WZC3q94dVs39b7hnMeOR3r1QCltie-zZ0mR9B3Gea6UAowBLhsz8NxFpv6NjPvTbXo1C_jMrx-rQ74Jdyc69fU8SC7YBazWBPS8ycuKyLDmbSYa5K4kc0RAual32m7dfxgE3m2vEDyz9mO2iZJi1rQxkp9it/s1069/11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" border="0" data-original-height="783" data-original-width="1069" height="293" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGlflI1oujLScCE8btuCK8L7w9jbd6iRq4WZC3q94dVs39b7hnMeOR3r1QCltie-zZ0mR9B3Gea6UAowBLhsz8NxFpv6NjPvTbXo1C_jMrx-rQ74Jdyc69fU8SC7YBazWBPS8ycuKyLDmbSYa5K4kc0RAual32m7dfxgE3m2vEDyz9mO2iZJi1rQxkp9it/w400-h293/11.png" title="Create sales order automatic extraction -Maximize the value of SAP Business AI for SAP S/4HANA" width="400" /></a></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-37738591496676649272024-03-01T13:38:00.000+05:302024-03-01T13:38:06.829+05:30Clone SAP HANA Database Instance via Template based cloning<div>The cloning template essentially serves as a database backup, encompassing the schema and data of the clone while excluding its configuration details, such as the options chosen during provisioning. It's important to note that restoring a backup from a more recent SAP HANA version into an older version is not supported and results in an error.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQrzmdxUpnv2ZRtZqBGEmZI6ErazYHp2fAPPaV8fp4XWLScFdRvggUuS2fyUguKxotAfoJ3ubSW3BnWWsRFGFg0wsOgtjQSa-gl7SqEIlgkDpvA3RI8C6_5sE4leplEYXXHxzVAW9pQPOdYMUAIX6uoIXmuMaQ15V-Y3S6YgvWX5LeDq4wGJoz6FAxUk08/s1841/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="950" data-original-width="1841" height="206" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQrzmdxUpnv2ZRtZqBGEmZI6ErazYHp2fAPPaV8fp4XWLScFdRvggUuS2fyUguKxotAfoJ3ubSW3BnWWsRFGFg0wsOgtjQSa-gl7SqEIlgkDpvA3RI8C6_5sE4leplEYXXHxzVAW9pQPOdYMUAIX6uoIXmuMaQ15V-Y3S6YgvWX5LeDq4wGJoz6FAxUk08/w400-h206/1.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Cloning templates are stored in a template container within HANA Data Lake Files, specifically in the Files service of the data lake. To create a cloning template, and to create an instance based on a template, your subaccount must therefore have a data lake Files service; note, however, only data lake Files is required — without the additional option of the data lake relational engine.<span><a name='more'></a></span></div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Prerequisites</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>You must have an SAP HANA Cloud, data lake Files instance running in your subaccount; note, however, only data lake Files is required - without the additional option of the data lake Relational Engine.</li><li>You must have access to your data lake Files instance using the following:</li><ul><li>Client key</li><li>Client certificate</li><li>CA certificate</li></ul><li>Copy Files REST API Endpoint ( You will find the REST API endpoint of the data lake Files instance in SAP HANA Cloud Central or copied it to your clipboard by clicking (More) )</li></ul></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Note : </div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. The template is essentially a database backup which includes the schema and data of the clone but not its configuration information, such as the options selected during provisioning. ( E.g.. Memory Allocation ).</div><div class="separator" style="clear: both;">2. Data lake Files is required you can only clone a simple HANA Cloud instance; instances where data lake Relational Engine is attached cannot be cloned. This is because the underlying technology of the two systems is different. In HANA Cloud central the menu option Create Template to Clone Instance is not visible for HANA Cloud instances with data lake Relational Engine.</div><div class="separator" style="clear: both;">3. There should be no other backup process running when you create the backup template; if, for example, the daily backup for the instance is running an error message is returned.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Setting Up Access to HANA Cloud data lake Files</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Download <a href="https://www.openssl.org/source/" target="_blank">OpenSSL</a> </div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">HANA Data Lake Files oversees user security and access by utilizing certificates; thus, it is necessary to generate signed certificates for configuring user access. In the absence of access to a signing authority, you have the option to establish a Certificate Authority (CA) and generate a signed client certificate. Subsequently, you can update the HDL Files configuration following the outlined procedure.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Generate the CA using the OpenSSL command</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">openssl genrsa -out ca.key 2048</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Create the CA's public certificate (Valid for 200 days)</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">openssl req -x509 -new -key ca.key -days 200 -out ca.crt</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Create a signing request for the client certificate</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">openssl req -new -nodes -newkey rsa:2048 -out client.csr -keyout client.key</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Create the client certificate (Valid for 100 days)</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">openssl x509 -days 100 -req -in client.csr -CA ca.crt -CAkey ca.key -out client.crt</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Note: Make sure the fields are not all exactly the same between the CA and client certs, otherwise it is assumed to be a self-signed cert and the cert validation below will fail.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Verify the certificate was signed by a CA</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;">openssl verify -CAfile ca.crt client.crt</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;">You will need the above generated certificates and keys to configure the HANA Data Lake files.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Update the SAP HANA, Data Lake Trust Configuration</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Go to SAP HANA Cloud Central and choose "Manage Configuration" for the HDL instance.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKG_bF5KF3mw6EQN5lUTShG5E3m_owIRuDVpFQR898rRVGzzRFFgtHW_UEtVB11PIJdTP3DXB-iFBJ7Rfl1ITbNo0_6xIRNyHd7LlIthRr77f10tZ9gtx1fOlzPgVbuev09xM4ORKqnheOTp4owfJs1Nj4GjaHzXOaiIyiJOdc0dvUSLGwugvsvyMj81b3/s1860/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="888" data-original-width="1860" height="191" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKG_bF5KF3mw6EQN5lUTShG5E3m_owIRuDVpFQR898rRVGzzRFFgtHW_UEtVB11PIJdTP3DXB-iFBJ7Rfl1ITbNo0_6xIRNyHd7LlIthRr77f10tZ9gtx1fOlzPgVbuev09xM4ORKqnheOTp4owfJs1Nj4GjaHzXOaiIyiJOdc0dvUSLGwugvsvyMj81b3/w400-h191/2.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Click on "Data Lake Files"</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgYMcaidf4A7K083jfKJZ9wNCfV48pxqWaLu9UqAhNozEqkYTEMyx8PPQgykEKUbEmUkV5BL70XVAAZEGiU85IDLAYvlI7Od4i-U7G8xBiBIeiC9P0Y9a7VDo_Wz8PW2uo3BQOhboxOrGzraPZNi2bciQ7yL_40gxrSNIZM2nCRR9JrrrL6862ZFUd9hzqw/s1813/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="364" data-original-width="1813" height="80" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgYMcaidf4A7K083jfKJZ9wNCfV48pxqWaLu9UqAhNozEqkYTEMyx8PPQgykEKUbEmUkV5BL70XVAAZEGiU85IDLAYvlI7Od4i-U7G8xBiBIeiC9P0Y9a7VDo_Wz8PW2uo3BQOhboxOrGzraPZNi2bciQ7yL_40gxrSNIZM2nCRR9JrrrL6862ZFUd9hzqw/w400-h80/3.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Click on "Add" under Trusts configuration and hit on "Upload" file button and browse to the location where your ca. crt is located and upload that file and click on apply. The alias can be anything, but the certificate should be exactly what is in the generated ca.crt.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjnJ9hn-D3ZPY_s4srSP2w-SyKp6NdMLCfP8pYm8oKPy_lT65pNh4XDOAdFlymuTxiA_b-QU74fd6QQIkUQ2oz0RpETlxwFm3EGbr7f0EHherHIstXCXKoqUrlWCfURl_F1cCPfUw493GmFx70CbcvHEOYwxK-vUP0e2AA_st7qfTONW4kw1e1mH9kAq8mI/s1464/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="708" data-original-width="1464" height="194" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjnJ9hn-D3ZPY_s4srSP2w-SyKp6NdMLCfP8pYm8oKPy_lT65pNh4XDOAdFlymuTxiA_b-QU74fd6QQIkUQ2oz0RpETlxwFm3EGbr7f0EHherHIstXCXKoqUrlWCfURl_F1cCPfUw493GmFx70CbcvHEOYwxK-vUP0e2AA_st7qfTONW4kw1e1mH9kAq8mI/w400-h194/4.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgXdGHhjq0trdybq_4vG3pbE7SczIWh79iJSlrF7AU_hk2UWPfIqNVG8gXF9r9bp8uMlapOnpDGNnI94vt_brX8G2_c6N2qkCo4yu3SpTcVKnGQyrxPWYwBqNBjisXHuVR0CGQqMR4O1Y-iw5rEs1x49iXbYMrlK2rSRX81CIsfeUWu9hVjoR0xYNGU_bId/s628/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="428" data-original-width="628" height="272" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgXdGHhjq0trdybq_4vG3pbE7SczIWh79iJSlrF7AU_hk2UWPfIqNVG8gXF9r9bp8uMlapOnpDGNnI94vt_brX8G2_c6N2qkCo4yu3SpTcVKnGQyrxPWYwBqNBjisXHuVR0CGQqMR4O1Y-iw5rEs1x49iXbYMrlK2rSRX81CIsfeUWu9hVjoR0xYNGU_bId/w400-h272/5.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Click on "Add" under Authorizations and select the roles as "Admin" or "User" and then click on "Generate pattern" from the output of the following command. (exclude the "subject=" prefix)</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">openssl x509 -in client.crt -nameopt RFC2253 -subject -noout</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;">Alternatively, you can use the "Generate Pattern" option and similarly upload the client. crt file after clicking on the "Upload" file option. It will automatically generate a pattern like above.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhO4tKoD0v_24Hr7f9dcuZYPooFoAev6mCm4QZ_9hT6mi_3rAyGiHXNjvhHpFsP7tEY4zb7JggQzDvYC6sNnxpoIOzCVeihi368q2JIHoneKJnO3ffxzum9gC5EfSlIqUJiZN823igFyHoHOsz48MnJ67cq7_RsriaV1hGYUx8Mu7K0prOyOZOxnNAl2TVi/s1037/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="870" data-original-width="1037" height="335" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhO4tKoD0v_24Hr7f9dcuZYPooFoAev6mCm4QZ_9hT6mi_3rAyGiHXNjvhHpFsP7tEY4zb7JggQzDvYC6sNnxpoIOzCVeihi368q2JIHoneKJnO3ffxzum9gC5EfSlIqUJiZN823igFyHoHOsz48MnJ67cq7_RsriaV1hGYUx8Mu7K0prOyOZOxnNAl2TVi/w400-h335/6.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Click on "Review and Save".</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQ2sGr2PIS8eqevFSu1fU0DSlaDhahJXyaM-VVt5nKNHw0gqK229rOnay7MNe-VBweTUY_CIQLfO5GPWDGrgE9LeFEkbFl8rNvTMQNBqD4KMmOPIUyJGl6vnnozzUruAki9LOJrbRuHk6Tdzq-k2yC76qJ0ODNy2Sl7cZnPvf2HDJzpqkZVZ9t413pAOsV/s950/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="126" data-original-width="950" height="53" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQ2sGr2PIS8eqevFSu1fU0DSlaDhahJXyaM-VVt5nKNHw0gqK229rOnay7MNe-VBweTUY_CIQLfO5GPWDGrgE9LeFEkbFl8rNvTMQNBqD4KMmOPIUyJGl6vnnozzUruAki9LOJrbRuHk6Tdzq-k2yC76qJ0ODNy2Sl7cZnPvf2HDJzpqkZVZ9t413pAOsV/w400-h53/7.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Click "Save Changes" on the modal to confirm changes.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnRtUz_TGo5nqkK0jPu0yPF-MSXwLZZFAoXM5BeAvA5mPCwZXw25YQ4WtXtdnYtKBtD1gtdRqum2CLWvA_jc7PxkdDimPqCQ3EBwBnXKgzckwoZDO5Cu92EGKEzLg5yxGsBbQn9FZAPmv4oDq2XnwlW77DzIwta5yZ6_EnvySyg7Qu5ZztXfXwN2LiOcDf/s576/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="318" data-original-width="576" height="221" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnRtUz_TGo5nqkK0jPu0yPF-MSXwLZZFAoXM5BeAvA5mPCwZXw25YQ4WtXtdnYtKBtD1gtdRqum2CLWvA_jc7PxkdDimPqCQ3EBwBnXKgzckwoZDO5Cu92EGKEzLg5yxGsBbQn9FZAPmv4oDq2XnwlW77DzIwta5yZ6_EnvySyg7Qu5ZztXfXwN2LiOcDf/w400-h221/8.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><h3 style="clear: both; text-align: left;"><b>Check that a Connection can be Established from the HDLFSCLI</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In this step we will verify the configurations that was done in the previous steps by running the below command. The < Instance ID> and < REST API Endpoint > can be copied by clicking on the ellipses in SAP HANA Cloud Central.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">< PATH> is the path to the corresponding certificate. The following command lists out files in the root folder of the HDL files instance. Thus if the instance has no files, the command will not return anything.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><div class="separator" style="clear: both;">hdlfscli -cert <PATH>\client.crt -key <PATH>\client.key -cacert <PATH>\ca.crt -k -s https://<REST API Endpoint> -filecontainer <Instance ID> ls</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;">Now that we have all the necessary configurations done, we can go ahead and start with creating a cloning template.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Create a cloning template</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">On the All Instances page, select the SAP HANA database instance that you want to clone. Click D (More) Create Template to Clone Instance. This menu option is only visible for instances which do have the additional option of the data lake Relational Engine.</div></div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgLCx_jxUjK04bR2vc_ThBbbLcGbEs7wJsJgVuFCZpKIX_jBIRDWEB7Z9QL5xLmMDM16Lkim-gl-lS0-M9LKDpSWGkB90qjU-GMNZB_ofSQgNM8sgyWTnArWM7G7Jpb5gf0xbRbJqLmfuplRljbqvXsop_0vExfK2oAgH1Xk6fMSQS-J5O1LC9COlxnoZ-1/s1844/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="832" data-original-width="1844" height="180" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgLCx_jxUjK04bR2vc_ThBbbLcGbEs7wJsJgVuFCZpKIX_jBIRDWEB7Z9QL5xLmMDM16Lkim-gl-lS0-M9LKDpSWGkB90qjU-GMNZB_ofSQgNM8sgyWTnArWM7G7Jpb5gf0xbRbJqLmfuplRljbqvXsop_0vExfK2oAgH1Xk6fMSQS-J5O1LC9COlxnoZ-1/w400-h180/9.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">In the Create Template to Clone Instance wizard, choose a name for the template.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b><i>Note: Record the name of your template for later use when cloning an instance based on this template.</i></b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Enter the string for HDLFS REST Endpoint to be used for Template Storage. The content is validated — it is not necessary to add the hdlfs:// protocol. Upload the client key, client certificate, and CA certificate required to access the data lake Files instance where the template will be stored.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Create an encryption password for the template and click Create Template.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhhklQk0tkgATPU004jbpxMORlY5neRa-FTaTg42iIf8jf4MJtyCGmIO3i-jC8LjKFY8MutYqsq4b_K1rIVUM2rI3MyY5VQdee6EoCaIHRKmlfPPm6logkZp-yemOkn4kQnqDMx8p_nIB3kYWZ9NHHe6H32JCfvdQbB8KydNkPszs1m6v58qqtH3_W1eB6G/s1323/10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="1323" data-original-width="873" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhhklQk0tkgATPU004jbpxMORlY5neRa-FTaTg42iIf8jf4MJtyCGmIO3i-jC8LjKFY8MutYqsq4b_K1rIVUM2rI3MyY5VQdee6EoCaIHRKmlfPPm6logkZp-yemOkn4kQnqDMx8p_nIB3kYWZ9NHHe6H32JCfvdQbB8KydNkPszs1m6v58qqtH3_W1eB6G/w264-h400/10.png" title="Clone SAP HANA Database Instance via Template based cloning" width="264" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><h3 style="clear: both; text-align: left;"><b>Create an SAP HANA database instance via cloning template</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Go to SAP HANA Cloud Central. All Instances > Create Instance.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1Q51fPiXo6TYjJcWGYV2WE0sJRN532p_oiYk4oblIx-_L7S6yhEGY5bOBYUoodst8y9wVcqczD4LWGYlGpeuvYucc5RaQFV36eYzqG5Uj79mKIasBXGh6K3Wm8M5fbxIrnOQUVhnIDWWcXCt9ojbw12piXxQMWLRrq2Kine3-bftbVa6_seq8PtpxL-jf/s1852/11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="472" data-original-width="1852" height="103" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1Q51fPiXo6TYjJcWGYV2WE0sJRN532p_oiYk4oblIx-_L7S6yhEGY5bOBYUoodst8y9wVcqczD4LWGYlGpeuvYucc5RaQFV36eYzqG5Uj79mKIasBXGh6K3Wm8M5fbxIrnOQUVhnIDWWcXCt9ojbw12piXxQMWLRrq2Kine3-bftbVa6_seq8PtpxL-jf/w400-h103/11.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Choose (Cloned) SAP HANA Cloud, SAP HANA Database.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiOBu_ETpKcvPnkkHVLT9v2dPRTTR4JJMKbOx8__nOwQx7456B2QwLu2rrl6QjZs_spoDMVPRf0IM1IVZD5Ob3aHERo-6QeIkLqyu6AHCZxKKdBZ2Q__ruZoZ3b1WHHAjyXNU5_14PZELL2qjZblZhzvtWrpbKmyh08yUYDdCLmKQYMUSQ-1RqiuOo1vqP2/s1848/12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="840" data-original-width="1848" height="181" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiOBu_ETpKcvPnkkHVLT9v2dPRTTR4JJMKbOx8__nOwQx7456B2QwLu2rrl6QjZs_spoDMVPRf0IM1IVZD5Ob3aHERo-6QeIkLqyu6AHCZxKKdBZ2Q__ruZoZ3b1WHHAjyXNU5_14PZELL2qjZblZhzvtWrpbKmyh08yUYDdCLmKQYMUSQ-1RqiuOo1vqP2/w400-h181/12.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">In the next step, add all the necessary details such as the instance name & description. Set the password for DBADMIN</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiqt6MdCQT23oFSTPI9NJzcpro8Zx3sFnekstnCjJSzWyd-7CeOH2zHHNVFNB6rmLDf0Qg73l1XCVEfdEK3FCh6hi-FIO9NBH880Xp6GR-40Onj3sIYfbDrXwYgs05OIheOBgoOxckSouxOetPo-SvMEvL7c71sudFfKidzT_eysygwq7YnSBdqgqNEczy8/s1856/13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="772" data-original-width="1856" height="166" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiqt6MdCQT23oFSTPI9NJzcpro8Zx3sFnekstnCjJSzWyd-7CeOH2zHHNVFNB6rmLDf0Qg73l1XCVEfdEK3FCh6hi-FIO9NBH880Xp6GR-40Onj3sIYfbDrXwYgs05OIheOBgoOxckSouxOetPo-SvMEvL7c71sudFfKidzT_eysygwq7YnSBdqgqNEczy8/w400-h166/13.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Proceed through the provisioning wizard until you reach step 6: Cloning template.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Enter the name of the template that you created in the previous step and paste the REST API endpoint. Add the client key, client certificate, CA certificate and encryption password that was entered during creation of the template.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjR70xd924HAJ-7dFxjKAwVUO5G_eGPNYNBMYQBLMK9qFk555iCF0LXQ9fvzRxmPT7LCV0YOdBIBw4QpXagTH9Q1D9n2il8PfwqJmXbYZFnrX2dgBqUtz5HSfplplxyANkHc5VW9ep3Qzr2NxeSvV9MEFx2XrfEpXOm8WzDA-aqzV8t31iiN3alPYPyfuoI/s1862/14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Clone SAP HANA Database Instance via Template based cloning" border="0" data-original-height="1277" data-original-width="1862" height="274" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjR70xd924HAJ-7dFxjKAwVUO5G_eGPNYNBMYQBLMK9qFk555iCF0LXQ9fvzRxmPT7LCV0YOdBIBw4QpXagTH9Q1D9n2il8PfwqJmXbYZFnrX2dgBqUtz5HSfplplxyANkHc5VW9ep3Qzr2NxeSvV9MEFx2XrfEpXOm8WzDA-aqzV8t31iiN3alPYPyfuoI/w400-h274/14.png" title="Clone SAP HANA Database Instance via Template based cloning" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Click on "Review and Create".</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">You have created a cloning template that is stored in the specified data lake Files instance in your subaccount and have cloned an SAP HANA database instance using that template.</div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-81526243568237938422024-02-28T13:30:00.000+05:302024-02-28T13:30:20.101+05:30Cloud Integration - How to Manage Abnormally Large Files with SFTP Adapter and SAP HANA Database<div>This blog provides a comprehensive guide for users seeking a solution for processing large files from an SFTP source and transferring the data to a <b><a href="https://www.hanaexam.com/p/chanaimp18.html">HANA Database</a></b>. The solution outlined in this guide employs SAP Integration Suite. There have always been challenges associated with processing large files, which may include issues related to performance, memory usage, and overall efficiency. All of which are solved by the solution shared in this guide.</div><div><br /></div><h3 style="text-align: left;"><b>Background Information</b></h3><div><br /></div><div>During a recent migration project - we were challenged with designing a solution that eliminated a previously designed integration using Informatica Platform. Replacing it with SAP BTP Cloud Integration Suite, during the migration project a crucial task emerged: retrieving large files from an external SFTP and seamlessly loading the data into a HANA Database On-Premise table.<span><a name='more'></a></span></div><div><br /></div><h3 style="text-align: left;"><b>Systems and Platforms</b></h3><div><br /></div><div>◉ SAP BTP Integration Suite (Cloud Integration): Integration Platform.</div><div>◉ SAP HANA Database On-Premise: Target destination for the data.</div><div>◉ External SFTP (SSH File Transfer Protocol): Source location for the large files.</div><div><br /></div><h3 style="text-align: left;"><b>Business Requirement</b></h3><div><br /></div><div>Regularly monitor the external SFTP folder for incoming files, and upon detection, initiate the seamless transfer of data to the HANA Database On-Premise table through SAP Cloud Integration. The graphic below is a diagram the represents the solution we deployed.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg7pPFNBZWhziIE81Cq_KoUaupcMs0iJxr1DX90ZphHYFJwGXVhIKE2wbeQVQPz4Dr1osDskbM5-mLtRC1p768pY9urqhey6CarlspnBD2QhOTYd3865WwC4ZUD141qvC3pWBOnmrpsxRy2CqjSoshzCzSnKF_G1A5MJCqGls9jKPiTqIFt9DHhjj8e7zqE/s567/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Cloud Integration - How to Manage Abnormally Large Files with SFTP Adapter and SAP HANA Database" border="0" data-original-height="281" data-original-width="567" height="199" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg7pPFNBZWhziIE81Cq_KoUaupcMs0iJxr1DX90ZphHYFJwGXVhIKE2wbeQVQPz4Dr1osDskbM5-mLtRC1p768pY9urqhey6CarlspnBD2QhOTYd3865WwC4ZUD141qvC3pWBOnmrpsxRy2CqjSoshzCzSnKF_G1A5MJCqGls9jKPiTqIFt9DHhjj8e7zqE/w400-h199/1.png" title="Cloud Integration - How to Manage Abnormally Large Files with SFTP Adapter and SAP HANA Database" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><h3 style="clear: both; text-align: left;"><b>The Challenge with this Integration</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">While handling file processing within SAP Cloud Integration is generally straightforward and handled seamlessly by the platform. Challenges arise when dealing with large files, approximately 400MB or larger. Depending on the environment's capacity, unforeseen issues may occur, such as messages becoming stuck in processing status and being automatically aborted after 24 hours without completion.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Providing a specific recommendation on the maximum initial file size is challenging. Memory consumption varies significantly based on individual data content and processing step characteristics. Operations such as csv-to-xml conversion and message-mapping process the payload as a whole, resulting in considerable memory usage.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To address this, it is advisable to divide the input into manageable chunks for more efficient processing.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Solution Implemented</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The solution we implemented involves utilizing the General Splitter capability, where two instances of General Splitter were employed.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><div class="separator" style="clear: both;">The first one was responsible for breaking down the original input files into smaller pieces, while the second one facilitated sending the data to HANA in batches. This approach enables parallel processing with a defined number of concurrent processes, allowing the complete payload or data to be efficiently sent to HANA.</div></div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-yQngvBpOIcUcQgEuHHAqX70iiwTu1efQbuNgymVteqSgMK-N5ks-HZA33Qx7vccictcF011UF93aq6KDhIR4Z6KhNK8VmTYEFuultVNW9Fe8UQ03H8m42LF0uMfcxUHVOF5-jjjmcFLJ2A_vFY8jati4ynek_miWweuAbfelqIaQrmdZg2FxsLnowgCn/s480/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Cloud Integration - How to Manage Abnormally Large Files with SFTP Adapter and SAP HANA Database" border="0" data-original-height="378" data-original-width="480" height="315" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-yQngvBpOIcUcQgEuHHAqX70iiwTu1efQbuNgymVteqSgMK-N5ks-HZA33Qx7vccictcF011UF93aq6KDhIR4Z6KhNK8VmTYEFuultVNW9Fe8UQ03H8m42LF0uMfcxUHVOF5-jjjmcFLJ2A_vFY8jati4ynek_miWweuAbfelqIaQrmdZg2FxsLnowgCn/w400-h315/2.png" title="Cloud Integration - How to Manage Abnormally Large Files with SFTP Adapter and SAP HANA Database" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">1 - SFTP Sender to trigger the iFlow</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">2 - File General Splitter to process a quantity of records per time (for example, a file with 1.000.000 rows will be split in 10 branches of 100.000)</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1jjiTdp_omZO5K8yHHqTRpEUbwiQN0b3SPncyuRY-xnz_BerCsXEZENgWUh8iu_WLvtX_gXu4GaQU79G3SD4slBuoCz9zUtkfdAjD5IAAuZke3pwC8xGaSbrMaqvCSCLcAlSdyssTw3Ln61dPRr_jZbY6B-0tFTkFK7CULsWVQo4JaPPfr2QiDNILFpzH/s380/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Cloud Integration - How to Manage Abnormally Large Files with SFTP Adapter and SAP HANA Database" border="0" data-original-height="380" data-original-width="357" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1jjiTdp_omZO5K8yHHqTRpEUbwiQN0b3SPncyuRY-xnz_BerCsXEZENgWUh8iu_WLvtX_gXu4GaQU79G3SD4slBuoCz9zUtkfdAjD5IAAuZke3pwC8xGaSbrMaqvCSCLcAlSdyssTw3Ln61dPRr_jZbY6B-0tFTkFK7CULsWVQo4JaPPfr2QiDNILFpzH/w376-h400/3.png" title="Cloud Integration - How to Manage Abnormally Large Files with SFTP Adapter and SAP HANA Database" width="376" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Grouping: number of rows in each block</div><div class="separator" style="clear: both;">◉ Parallel Processing: to enable the parallel processing</div><div class="separator" style="clear: both;">◉ Number of Concurrent Processes: number of threads executing in parallel</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3 - Convert the original payload CSV to XML (using the standard function)</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">4 - Graphical mapping to create SQL XML payload to HANA (field transformation to meet HANA format)</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><div class="separator" style="clear: both;">5 - JDBC General Splitter to send to HANA a quantity of records per time (batches)</div></div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhvMbQbBHCfarvZ9duzgEZP7aozqRX1xsfLj2pXwGWnVvXOrHfMUA8KJwUn2AX7-s0fwDwbEDCNABVxrH0KuwFyv-trcopoixoRfnEECYxqtcD3n9DrrQFZ07X0cP6ntkbK4Wk9x3ujn0Q-_ZXBPbsH_m5arB7VzM1mFWFA6FuvYwhhh2F6VvEHq-kIDhDZ/s336/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Cloud Integration - How to Manage Abnormally Large Files with SFTP Adapter and SAP HANA Database" border="0" data-original-height="294" data-original-width="336" height="350" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhvMbQbBHCfarvZ9duzgEZP7aozqRX1xsfLj2pXwGWnVvXOrHfMUA8KJwUn2AX7-s0fwDwbEDCNABVxrH0KuwFyv-trcopoixoRfnEECYxqtcD3n9DrrQFZ07X0cP6ntkbK4Wk9x3ujn0Q-_ZXBPbsH_m5arB7VzM1mFWFA6FuvYwhhh2F6VvEHq-kIDhDZ/w400-h350/4.png" title="Cloud Integration - How to Manage Abnormally Large Files with SFTP Adapter and SAP HANA Database" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">6 - Send the data to HANA</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">7 - Gather to merge all the HANA responses</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">8 - Gather to merge all the records processed</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">9 - Exception Handling sending an alert email to a distribution list. Afterwards the escalation event is raised</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Benefits/Advantages of the implemented solution</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">This solution utilizes an approach that harnesses the strengths of SAP Cloud Integration while addressing common challenges associated with data processing and integration. The emphasis on parallelization, error prevention, and leveraging out-of-the-box capabilities contributes to the efficiency, reliability, and scalability of the overall solution.</div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-53774136464223413202024-02-26T14:09:00.002+05:302024-02-26T14:09:54.907+05:30SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake<h3 style="text-align: left;"><b>Introduction</b></h3><div><br /></div><div>SAP Datasphere has introduced a new feature, '<b><a href="https://www.hanaexam.com/p/chanatec18-sample-question-set-2.html">Replication Flows</a></b>.' This new capability (now available with Azure Data Lake) allows for the process of copying multiple tables from one source to another, offering a fast and seamless experience in data management. </div><div><br /></div><div>In this blog, we’ll provide a step-by-step tutorial on replicating data from SAP S/4HANA to Azure Data Lake, showcasing the practical application and efficiency of this new feature in real-world scenarios. </div><div><br /></div><div>Now, let's dive in. We'll walk you through each step necessary to effectively utilize 'Replication Flows' for transferring data from SAP S/4HANA to Azure Data Lake. <span><a name='more'></a></span></div><div><br /></div><div><b>Steps:</b></div><div><br /></div><div>1. To start, you will need to create a connection in your SAP Datasphere instance to Azure Data Lake. </div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgV17dHcNc3bC2gX0NBrz6PaQFRVJfufhyae9M0GgOJEW3Cz5U-aTeI3Hg64t03T9LlslyocTwzmPV44UuyTEVOZn5eBQJ05abLEy-hycKGC6wL0RP_i5gOOHhHppX1niFUOCpI65aj8boXsutbz-5xfxtPFF45HxFcPeQ0R9UK3W9Xq_HZqFGO6CvTpPXX/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="971" data-original-width="1600" height="243" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgV17dHcNc3bC2gX0NBrz6PaQFRVJfufhyae9M0GgOJEW3Cz5U-aTeI3Hg64t03T9LlslyocTwzmPV44UuyTEVOZn5eBQJ05abLEy-hycKGC6wL0RP_i5gOOHhHppX1niFUOCpI65aj8boXsutbz-5xfxtPFF45HxFcPeQ0R9UK3W9Xq_HZqFGO6CvTpPXX/w400-h243/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-1.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">2. Please ensure you have a Dataset in your Azure Data Lake that you would like to replicate the tables into.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3. Make sure you have a source connection. In this case, we will be using a S4/HANA On-Premise connection. You will need to create this connection in the ‘Connections’ tab in SAP Datasphere. </div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhH6o0_sILHZz-EjdZhBwRYR_BgWtecyZEesIiPkJS4GogybBMVi_qHOYceZ_waIDRox-moyEe43cnmheC4tLgNjzgQbLswYiWwGqh_nRuj__1fvOaOM6ttWUPQjLaalSo9MHUFK4CX8uOG_Yv0fcHjgTKUstKm5wWh28MkJgbAWZkYggBeXKLCi8KmfuoX/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="971" data-original-width="1600" height="243" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhH6o0_sILHZz-EjdZhBwRYR_BgWtecyZEesIiPkJS4GogybBMVi_qHOYceZ_waIDRox-moyEe43cnmheC4tLgNjzgQbLswYiWwGqh_nRuj__1fvOaOM6ttWUPQjLaalSo9MHUFK4CX8uOG_Yv0fcHjgTKUstKm5wWh28MkJgbAWZkYggBeXKLCi8KmfuoX/w400-h243/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-2.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">4. Navigate to SAP Datasphere and click on ‘Data Builder’ option on the left panel. Find and click the ‘New Replication Flow’ option.</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNzzbnOdHe5_2-pEUFn-qlKPdvUuuU3PbRWTfGlUJli1IgAyaT74q87gjxeQ080V_UitQnS86aumWAkjjAsysoNJj91r99tNoC4VB_42MLhtKyHX8GgpFMpWa4mUxSTqXpyqKUKZyO-LQ3tarpsSfU7HX7dUlyTK4UEpiNyLJYS9la7DVdYwema_p2Zt-d/s995/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="770" data-original-width="995" height="310" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNzzbnOdHe5_2-pEUFn-qlKPdvUuuU3PbRWTfGlUJli1IgAyaT74q87gjxeQ080V_UitQnS86aumWAkjjAsysoNJj91r99tNoC4VB_42MLhtKyHX8GgpFMpWa4mUxSTqXpyqKUKZyO-LQ3tarpsSfU7HX7dUlyTK4UEpiNyLJYS9la7DVdYwema_p2Zt-d/w400-h310/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-3.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">5. Click on ‘Select Source Connection’. </div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgewZRjE_6rfUIme97WZ9jlqz6L8zuzwZblSQ3ryW4SNa4yMpzsh6wsRadDFEMzVDpleo34Mk93RqMQPjNjkrJIEH2W9EfPzN23y0HjvATE4ZIF1yMoyvHkzgLUTC7u8CUx0wrZ7JaHoBzrTuMX167przT0H7HEFvZpZ40FdPdaFAp9KgCwmnUGRJhH39HR/s975/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="755" data-original-width="975" height="310" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgewZRjE_6rfUIme97WZ9jlqz6L8zuzwZblSQ3ryW4SNa4yMpzsh6wsRadDFEMzVDpleo34Mk93RqMQPjNjkrJIEH2W9EfPzN23y0HjvATE4ZIF1yMoyvHkzgLUTC7u8CUx0wrZ7JaHoBzrTuMX167przT0H7HEFvZpZ40FdPdaFAp9KgCwmnUGRJhH39HR/w400-h310/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-4.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">6. Choose the source connection you want. We will be choosing SAP S/4 HANA On-Premise. </div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">7. Click select Source Container. </div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgr8gpbhxTV_M_Okvj8K0kTAA73iYBXzV2GOsGVMo-v6bwP9jGLIDOa3HwI82mp1q1AV1_LjDkIPllsYTla89VvEmc4r45tqwI8YsV9JNfCGaG6f7tzltccCHKeAKaZ_NDm8YN5ITl3bfEbdehZeyRB_6L0WkcIZ8j65tW-isHsAb9wn50m6x22h42ZcYQ_/s975/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="755" data-original-width="975" height="310" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgr8gpbhxTV_M_Okvj8K0kTAA73iYBXzV2GOsGVMo-v6bwP9jGLIDOa3HwI82mp1q1AV1_LjDkIPllsYTla89VvEmc4r45tqwI8YsV9JNfCGaG6f7tzltccCHKeAKaZ_NDm8YN5ITl3bfEbdehZeyRB_6L0WkcIZ8j65tW-isHsAb9wn50m6x22h42ZcYQ_/w400-h310/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-5.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">8. Choose ‘CDS Views’ then click Select. </div></div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi24NjPO_ealwm-SPygz9Iz3xAterAhZ3Ahp8PIHp2xfzWFBuMadvesaFqe4sWEV3s7-2iddu0DYjEZTX03P3mRobeMAgitj2SAwWgSxjsaq2XLc4iIB0Yn5g1QLRUbtc-QWGG0bR9Mzsk9smjZMzvrwl8CRwvuo5vrVudNf3gFCJ9Fjhirelr4QN7H_dem/s380/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="380" data-original-width="316" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi24NjPO_ealwm-SPygz9Iz3xAterAhZ3Ahp8PIHp2xfzWFBuMadvesaFqe4sWEV3s7-2iddu0DYjEZTX03P3mRobeMAgitj2SAwWgSxjsaq2XLc4iIB0Yn5g1QLRUbtc-QWGG0bR9Mzsk9smjZMzvrwl8CRwvuo5vrVudNf3gFCJ9Fjhirelr4QN7H_dem/w333-h400/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-6.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="333" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">9. Click “Add Source Objects” and choose the views you want to replicate. You can choose multiple if needed. Once you finalize the objects, click add selection. <span> </span></div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxh4BNPFOSjI53GjMxVEXhRPq3BI1h0rBCUexTmvTB3zJwQ2iM1aPGGCY8A2Sjczt5xkkWHkXkeR8_2I2r1P_xTJEP1jmKP1Sk9qnpZN22IJSNsXUZfD9QM2gTrCxv42pJ-d5DxJiWvZTowtF1grz58dqCiSuGMwzGjYDpOD9948i8yuTiHuIT8-BBIJIG/s935/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="806" data-original-width="935" height="345" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxh4BNPFOSjI53GjMxVEXhRPq3BI1h0rBCUexTmvTB3zJwQ2iM1aPGGCY8A2Sjczt5xkkWHkXkeR8_2I2r1P_xTJEP1jmKP1Sk9qnpZN22IJSNsXUZfD9QM2gTrCxv42pJ-d5DxJiWvZTowtF1grz58dqCiSuGMwzGjYDpOD9948i8yuTiHuIT8-BBIJIG/w400-h345/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-7.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNnA6FvJfiYzwNpZ7fcY2OfzJI9znABpEA3R1uxKL3Wvpsd-MDMZf5rAX7OtJdxHhyjGzuCdZw3ewiyB0v0-lbl4fS6D9OTFwaHKgFlUp59LAcnupf9FMGiA1T09U3EhjWf66O5vW3NkzttFxHgnlyyAHn2gzzsONB3yXQrskNVkVfxKFGLBvbMvCnzxzL/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="971" data-original-width="1600" height="243" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNnA6FvJfiYzwNpZ7fcY2OfzJI9znABpEA3R1uxKL3Wvpsd-MDMZf5rAX7OtJdxHhyjGzuCdZw3ewiyB0v0-lbl4fS6D9OTFwaHKgFlUp59LAcnupf9FMGiA1T09U3EhjWf66O5vW3NkzttFxHgnlyyAHn2gzzsONB3yXQrskNVkVfxKFGLBvbMvCnzxzL/w400-h243/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-8.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxZdH5Nl736KfbXhcCGvpzibYkM26z9BtYtDxzPMnulo8v4aTZ165urNJGiFEup_ZrEnTzRI7CyY5qIXXFvrJy5GF-g565zZR5LDFY6C81-LvobPDASlQD_EBsdgZkY-KVR17Ov5zSjfOZzrZOmLEw2zx2EJ6mrDCrKwiYKFtDYFEfJbaagT3IH4BxzRSi/s975/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="592" data-original-width="975" height="243" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgxZdH5Nl736KfbXhcCGvpzibYkM26z9BtYtDxzPMnulo8v4aTZ165urNJGiFEup_ZrEnTzRI7CyY5qIXXFvrJy5GF-g565zZR5LDFY6C81-LvobPDASlQD_EBsdgZkY-KVR17Ov5zSjfOZzrZOmLEw2zx2EJ6mrDCrKwiYKFtDYFEfJbaagT3IH4BxzRSi/w400-h243/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-9.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">10. Now, we select our target connection. We will be choosing Azure Data Lake as our target. If you experience any errors during this step, please refer to the note at the end of this blog. </div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgYpSgg4xpQIhn6Af4LwkB0qcmW-ok-VII5d3yP7PViHi2IEHVyUkH9v7zv6GIqVI_owC4ErZfh-WVIboJaglHTi6k8uVsVxWCiScWZNTWBUHcIx1jMCuvQdu4OADhJTO9S9-ICBaZ8k01Iw0plQuQM2joeW4GZrL0Q28azkJCloXWuMngURhzHpV9ewgVm/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="864" data-original-width="1600" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgYpSgg4xpQIhn6Af4LwkB0qcmW-ok-VII5d3yP7PViHi2IEHVyUkH9v7zv6GIqVI_owC4ErZfh-WVIboJaglHTi6k8uVsVxWCiScWZNTWBUHcIx1jMCuvQdu4OADhJTO9S9-ICBaZ8k01Iw0plQuQM2joeW4GZrL0Q28azkJCloXWuMngURhzHpV9ewgVm/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-10.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWi8J-ihXDRp1mHQ1fEhpklie-UDs3jGrI_NLJejdu2wbt1glYdf3REdWM2Xq0lNshZayYFCt7D769enhuH44xaSqdmK8elhrnrTFh5Z3p56oa9C5GntWsPXG6sH91VILME4CUsHZYS9BK1TiRa_agJ-VjfpJDVv1ShDi-l6z_N-LTif77lEb9EFdglhHu/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="864" data-original-width="1600" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWi8J-ihXDRp1mHQ1fEhpklie-UDs3jGrI_NLJejdu2wbt1glYdf3REdWM2Xq0lNshZayYFCt7D769enhuH44xaSqdmK8elhrnrTFh5Z3p56oa9C5GntWsPXG6sH91VILME4CUsHZYS9BK1TiRa_agJ-VjfpJDVv1ShDi-l6z_N-LTif77lEb9EFdglhHu/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-11.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">11. Next, we choose the target container. Recall the dataset you created in Azure Data Lake earlier in step 2. This is the container you will choose here. </div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi7DkArNVtXLHqr7ravqu6h7JZeZapvpxOQFJnk3cnq8ZxvY6AM0upETQ5H8DV0dNVc6BJAyygZSgNlT9CaxwDOJVKYzCy209bTlyCDfYYRUrYw4sJK2ZCNieBwfNGbkn-7D-HTTI0EXAdsed18zWI4s0tHoBVArEzrVjeVZf5wqgrLLS0hryArZx5oGXgn/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="864" data-original-width="1600" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi7DkArNVtXLHqr7ravqu6h7JZeZapvpxOQFJnk3cnq8ZxvY6AM0upETQ5H8DV0dNVc6BJAyygZSgNlT9CaxwDOJVKYzCy209bTlyCDfYYRUrYw4sJK2ZCNieBwfNGbkn-7D-HTTI0EXAdsed18zWI4s0tHoBVArEzrVjeVZf5wqgrLLS0hryArZx5oGXgn/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-12.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhUAG4NkK72YjXtcyWZfL0LqvVOZqunxsj7pky-l66SQlnE6dN9kxgD1_aJjnpkq0kbxGeqcMc0yb-GHNKXZHVyctV0PLgPrAX73npK4GY7Yms15phgNga4lk40Fsgn_sMFnlYq2GOvha0Pu9fX_beLGMvTJwexHpGJvLFgIaU-H4Y236OXZP7PR-FheAxk/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="864" data-original-width="1600" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhUAG4NkK72YjXtcyWZfL0LqvVOZqunxsj7pky-l66SQlnE6dN9kxgD1_aJjnpkq0kbxGeqcMc0yb-GHNKXZHVyctV0PLgPrAX73npK4GY7Yms15phgNga4lk40Fsgn_sMFnlYq2GOvha0Pu9fX_beLGMvTJwexHpGJvLFgIaU-H4Y236OXZP7PR-FheAxk/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-13.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">12. In the middle selector, click ‘Settings’ and set your load type. ‘Initial Only’ means to load all selected data once. ‘Initial and Delta’ means that after the initial load, you want the system to check every 60 minutes for any changes (delta), and copy the changes to the target. </div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhq-F0Hx9GGQ5w6x0b-EgQkrr0URt4Uhcmj1DonC3y2VI6qepaOyIvjjCRxqNRpmRl_LGLsI0bBIIWlK520cmMdyh-hQCBNT3vKQbQBmI1RWvFLGn5lsZsu6vV0hmXOaimjE-M-fUZpOghLBSLqMmu0OeHNSFxBp68LnC-RFGRikgUNKymS1SbiTKdv3_Ac/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="864" data-original-width="1600" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhq-F0Hx9GGQ5w6x0b-EgQkrr0URt4Uhcmj1DonC3y2VI6qepaOyIvjjCRxqNRpmRl_LGLsI0bBIIWlK520cmMdyh-hQCBNT3vKQbQBmI1RWvFLGn5lsZsu6vV0hmXOaimjE-M-fUZpOghLBSLqMmu0OeHNSFxBp68LnC-RFGRikgUNKymS1SbiTKdv3_Ac/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-14.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">13. Once done, click on the ‘Edit’ projections icon on the top toolbar to set any filters and mapping.</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgbjr3rE_cGH2bLjjmT7CtJKFL1kJMMDa8jhAFMI2GB2CAJbKcL5QCBLrRwAqGkSjuE3fWQM6KM1XxSRU_LRsajG87eoEIV4DsEvDgCpJEoXbIpHZWQQLXr2-h-Mdz1WTKrQmuKqUEXJnUzgPRewQS6GNDoVaoBoFfo76nnX2S5J0A7wN2PEyV7senB0kVA/s556/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-15.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="152" data-original-width="556" height="109" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgbjr3rE_cGH2bLjjmT7CtJKFL1kJMMDa8jhAFMI2GB2CAJbKcL5QCBLrRwAqGkSjuE3fWQM6KM1XxSRU_LRsajG87eoEIV4DsEvDgCpJEoXbIpHZWQQLXr2-h-Mdz1WTKrQmuKqUEXJnUzgPRewQS6GNDoVaoBoFfo76nnX2S5J0A7wN2PEyV7senB0kVA/w400-h109/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-15.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">14. You also can change the write settings to your target through the settings icon next to the target connection name and container. </div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">15. Finally, rename the replication flow to the name of your choosing in the right details panel. Then, click on ‘Save’, ‘Deploy’ and ‘Run’ the replication flow through the top toolbar icons. You can monitor the run in the ‘Data integration monitor’ tab on the left panel in SAP Datasphere. </div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIqnXwfbsQB5qI8UMiR4Zm_qo7tTN_xav5EwmLoomNF8c-phBvj-UmbdGJ5G83Nvyz7b17AbilpK7TKIF66LDS2aGJhYEt1fNtmSoT3PBm4VE5QHny6PvbDdv0ZifUDWa1BNfXs1Amki01gLVTpl1MwaogNrY5vrtv_EuGUBHGOtZh_AL7tTn37SZYPQzx/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-16.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="864" data-original-width="1600" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIqnXwfbsQB5qI8UMiR4Zm_qo7tTN_xav5EwmLoomNF8c-phBvj-UmbdGJ5G83Nvyz7b17AbilpK7TKIF66LDS2aGJhYEt1fNtmSoT3PBm4VE5QHny6PvbDdv0ZifUDWa1BNfXs1Amki01gLVTpl1MwaogNrY5vrtv_EuGUBHGOtZh_AL7tTn37SZYPQzx/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-16.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6Ga5KkAtT83UvmV94zviMz3dHdO0RCB4L4B0fpbOzCpi4U4V-4Vbo27F1hh-PLXiYm4zfgM-lRlnk2Xi_p0bD_Gbwm6phYWSER6uj6P1dbNSt7ykzXv3ngSh5Z_frstN_pAcZIIu5EGNc5Sva79LtTK4Bua0O3kM37WF1ZL44-vy5xle7Gh8eXxACOvpG/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-17.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="864" data-original-width="1600" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6Ga5KkAtT83UvmV94zviMz3dHdO0RCB4L4B0fpbOzCpi4U4V-4Vbo27F1hh-PLXiYm4zfgM-lRlnk2Xi_p0bD_Gbwm6phYWSER6uj6P1dbNSt7ykzXv3ngSh5Z_frstN_pAcZIIu5EGNc5Sva79LtTK4Bua0O3kM37WF1ZL44-vy5xle7Gh8eXxACOvpG/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-17.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPGGk9j3TkIS8P1syG2JqBnpHlGuvgqE7x7Gn9-cknYu8R1BERZ4BzDAMJy_aaUkYgQ51PquoH_hjFBO0lrqsarFAorSbKtIWqis55FbCMfLeil5oyMaBLtPqwDaoSYyA1FITkTanc6PF7EaFFrZM5GbzgjvnhScgQZBOHhXg6YOb1zxDvB5lC9a5WWd1M/s1461/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-18.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="789" data-original-width="1461" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPGGk9j3TkIS8P1syG2JqBnpHlGuvgqE7x7Gn9-cknYu8R1BERZ4BzDAMJy_aaUkYgQ51PquoH_hjFBO0lrqsarFAorSbKtIWqis55FbCMfLeil5oyMaBLtPqwDaoSYyA1FITkTanc6PF7EaFFrZM5GbzgjvnhScgQZBOHhXg6YOb1zxDvB5lC9a5WWd1M/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-18.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlmvQNiu85QsLlVkosvGYNsi9DCXWkLD0GZnXN8rfTl6K-qwYOixmYXniTuoXV5-f_HBgdgRSx9R9X-D9mWh6T0Kt5dZBu9Ay3Iqn1enqfdUX7UCxIg2_INpTCXK8YvP9Bak_CYnm4fBuCpu5y4myzIRjt8snR6smpszA57gm6DPwKCyIyQ21-12P6iY72/s1600/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-19.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="864" data-original-width="1600" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlmvQNiu85QsLlVkosvGYNsi9DCXWkLD0GZnXN8rfTl6K-qwYOixmYXniTuoXV5-f_HBgdgRSx9R9X-D9mWh6T0Kt5dZBu9Ay3Iqn1enqfdUX7UCxIg2_INpTCXK8YvP9Bak_CYnm4fBuCpu5y4myzIRjt8snR6smpszA57gm6DPwKCyIyQ21-12P6iY72/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-19.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">16. When the replication flow is done, you should see the target tables in Azure Data Lake as such. It should be noted that every table will have 3 columns added from the replication flow to allow for delta capturing. These columns are ‘operation_flag’, ‘recordstamp’, and ‘is_deleted’. </div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhaBoWZmq9bNDuKd4OH5tygmgPk6yIdg5LHbhnJt_iUKwt4QutS6QrqWyRasmMlces8b-ZebytOz_eXjiV5UQZZSfTU9OFqTc8Abb5y3q7uvGsb9_ydRvDT3hDY6ETbfC9XxSikYEo06d0Y_iWBy_pDQKatOPfWCWuULsc6FA15YOldskr-tnwD21C_uANM/s1318/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-20.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="801" data-original-width="1318" height="243" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhaBoWZmq9bNDuKd4OH5tygmgPk6yIdg5LHbhnJt_iUKwt4QutS6QrqWyRasmMlces8b-ZebytOz_eXjiV5UQZZSfTU9OFqTc8Abb5y3q7uvGsb9_ydRvDT3hDY6ETbfC9XxSikYEo06d0Y_iWBy_pDQKatOPfWCWuULsc6FA15YOldskr-tnwD21C_uANM/w400-h243/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-20.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEglhajUf_-uHCP6Xq-uR1kf7eKv2C5Z8o57OazKY8xFno5Xdx5l_l5TEQohUO1Xv2gTaypKahxfP4_Q7iDjrL6uf_v4c3bMZK4cWmoC3k7P8oyUBVA2w1JGuA-ttyymxf4vkAB3xi04YuO4GiSWDx67HLOrKxG0mdYhyijoCnj8I3WiHifX8vkwLZzRZaAF/s1423/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-21.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="805" data-original-width="1423" height="226" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEglhajUf_-uHCP6Xq-uR1kf7eKv2C5Z8o57OazKY8xFno5Xdx5l_l5TEQohUO1Xv2gTaypKahxfP4_Q7iDjrL6uf_v4c3bMZK4cWmoC3k7P8oyUBVA2w1JGuA-ttyymxf4vkAB3xi04YuO4GiSWDx67HLOrKxG0mdYhyijoCnj8I3WiHifX8vkwLZzRZaAF/w400-h226/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-21.png" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Note: You may have to include Premium Outbound Integration block in your tenant to deploy the replication flow. </div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXTRxi2uEySUpVMWP_07-oE3pjZifMG92puoxoKTfY7Qmz3pbQvge7EG_30Jfi2gZEgLZeiogDSBJKbkv5n19McHLFEm-w1-iAZLGcBbc4SiJYB8jx9NC2rdMu5G7vTY5Zk6SKovwYgR1eO1gKhyphenhyphenaRtWml2moYLxPHlOLtfcHcpp9gI1xgPDtIHmqKVGdQ/s1429/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-22.jpeg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" border="0" data-original-height="773" data-original-width="1429" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXTRxi2uEySUpVMWP_07-oE3pjZifMG92puoxoKTfY7Qmz3pbQvge7EG_30Jfi2gZEgLZeiogDSBJKbkv5n19McHLFEm-w1-iAZLGcBbc4SiJYB8jx9NC2rdMu5G7vTY5Zk6SKovwYgR1eO1gKhyphenhyphenaRtWml2moYLxPHlOLtfcHcpp9gI1xgPDtIHmqKVGdQ/w400-h216/sap-datasphere-replication-flow-from-s-4hana-to-azure-data-lake-22.jpeg" title="SAP Datasphere Replication Flow from S/4HANA to Azure Data Lake" width="400" /></a></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-24333247560688742692024-02-21T14:37:00.000+05:302024-02-21T14:37:20.013+05:30SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)<h3 style="text-align: left;"><b>Introduction</b></h3><div><br /></div><div>Use SAP SQL Data Warehousing to build calculation views and other SAP HANA Cloud HDI objects directly in SAP Datasphere run-time database and then exchange data between HDI containers and SAP Datasphere spaces. SAP SQL Data Warehousing can be used to bring existing HDI objects into SAP Datasphere environment, and to allow users familiar with the HDI tools to leverage advanced SAP HANA Cloud features.<span><a name='more'></a></span></div><div><br /></div><h3 style="text-align: left;"><b>1. Gather the relevant information</b></h3><div><br /></div><div>To Enable HDI container on DWC in SAP Datasphere User must require below details:</div><div><br /></div><div><ul style="text-align: left;"><li>SAP Datasphere Tenant ID</li><li>SAP Business Technology Platform Org GUID</li><li>SAP Business Technology Platform Space GUID</li></ul></div><div><br /></div><div>Follow below Procedure to collect above details </div><div><br /></div><div><ul style="text-align: left;"><li>To collect the SAP Datasphere Tenant ID user should be part of any one of this roles DW Administrator, System Owner</li><ul><li>Go to Expand Navigation bar ==>System==> About==> Tenant</li></ul></ul><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhv4GWJEh2qmkXBoDavfWGRv8POPEe2hyOtVbKv-jWH2Xgvo-bNPdiLOVIs1DcefsIv5tPZNxF2eTnwIPf0TXef-2bVfcemg43zeM51jPSj0G6m45FH2L9EbubYA93WqOE7qXiaWlnG32Qm3_AxaMRCfa1b2Uu8gi0dLW1dhAPvZLdPjgZ-jvCip_kACTyt/s305/0.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="135" data-original-width="305" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhv4GWJEh2qmkXBoDavfWGRv8POPEe2hyOtVbKv-jWH2Xgvo-bNPdiLOVIs1DcefsIv5tPZNxF2eTnwIPf0TXef-2bVfcemg43zeM51jPSj0G6m45FH2L9EbubYA93WqOE7qXiaWlnG32Qm3_AxaMRCfa1b2Uu8gi0dLW1dhAPvZLdPjgZ-jvCip_kACTyt/s16000/0.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" /></a></div></div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhQMKYZxvwmPBbQKIv5JR4lg5GMQ_bGlI90hIm7knNznCKS6gCTgLJlnT0eNuDrNA8gCEVHB8epzjpne5lqSefTN6Zwpgd6RYsnwJkAdMelv6l6CC9X65oMkYeIvnSmZTpZgoPzGKNUWqgBOAgUMPbi6_D7Ss8TinpFwbCUTIcB6eBbCjTLEosj71164LeY/s380/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="238" data-original-width="380" height="250" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhQMKYZxvwmPBbQKIv5JR4lg5GMQ_bGlI90hIm7knNznCKS6gCTgLJlnT0eNuDrNA8gCEVHB8epzjpne5lqSefTN6Zwpgd6RYsnwJkAdMelv6l6CC9X65oMkYeIvnSmZTpZgoPzGKNUWqgBOAgUMPbi6_D7Ss8TinpFwbCUTIcB6eBbCjTLEosj71164LeY/w400-h250/1.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ To collect the SAP Datasphere Tenant ID & Space GUID user should be part of any one of this roles SAP HANA Cloud Administrator, Space Developer</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> ◉ Go to SAP BTP Cockpit==>Global account==>Subaccount==>SAP Datasphere Space</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFHI_jIt8Dv-4cCIxTXIs8JUsqny71zPZjDS-zWGFz_ULUv-EvKtXOqnLUYrMATuwxne74YUROs62rBRFX6X4knYioBJv7QYM_tD-gdUK8tPiRrV6d0NMtFUMoPnp2DSRBWGla1Sr03jTck08i9A_O9OuOQ4g2-8rAvczXe5L5BKEdIoAOXOdX9SAqBTIv/s965/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="431" data-original-width="965" height="179" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFHI_jIt8Dv-4cCIxTXIs8JUsqny71zPZjDS-zWGFz_ULUv-EvKtXOqnLUYrMATuwxne74YUROs62rBRFX6X4knYioBJv7QYM_tD-gdUK8tPiRrV6d0NMtFUMoPnp2DSRBWGla1Sr03jTck08i9A_O9OuOQ4g2-8rAvczXe5L5BKEdIoAOXOdX9SAqBTIv/w400-h179/2.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><h3 style="clear: both; text-align: left;"><b>2.Create SAP Support ticket to mapping/sharing DWC HANA Cloud to SAP Datasphere tenant space</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Create a Request to Product team under DS_SM category along with below details:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ SAP Datasphere Tenant ID :</div><div class="separator" style="clear: both;">◉ SAP Business Technology Platform Org GUID :</div><div class="separator" style="clear: both;">◉ SAP Business Technology Platform Space GUID:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In the Schema Access area, go to HDI Containers and click Enable Access. A pop-up window appears there is need to open a support ticket so Product team can map the HDI containers with SAP Datasphere space. Please add the above-mentioned details into that ticket.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Notification will be shared once the ticket has been Processed/Mapping is completed.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>3.Create a HDI service instance on SAP Cloud Platform (SCP) under SAP Datasphere space</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To create HDI Service instance on SCP user should be part of any one of this roles SAP HANA Cloud Administrator, Space Developer</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Go to SAP BTP Cockpit==>Global account==>Subaccount==>SAP Datasphere Space</div><div class="separator" style="clear: both;">◉ Under Instances Tab Click on Create button by selecting service instance type .</div><div class="separator" style="clear: both;">◉ Select the service type as an SAP HANA Schemas & HDI Containers & Plan is hdi-shared & Instance Name is name (ex: DSP_HDI_PLAY) of HDI Container. Click on NEXT and add here Schema name with JSON format (ex: {"schema":"DSP_HDI_PLAY"}) . This is how User can define HDI Container own Schema name again this is not an mandatory to add here Schema name if left with blank this field then that schema name will autogenerated number format one. Click NEXT and Click Create.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Now HDI Container getting creating like below with staring of the status</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijmSuXvYbFh2033puFlGHfyMX5Qc1bir_Qydz4ERRQT6a-a9K8F81pcZmvZyZfJLwkCFbF1JuHHSVcwfuFQDI3FEHPOWitSsky1hMBGZvUJaCIi8SGf1XxxWHxuhAtUktBwQJXirHcUvhU8bEC7Y08eTFcgpeMto0fYa39CnzhoTJltms-4oIfokAS0t0c/s167/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="38" data-original-width="167" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijmSuXvYbFh2033puFlGHfyMX5Qc1bir_Qydz4ERRQT6a-a9K8F81pcZmvZyZfJLwkCFbF1JuHHSVcwfuFQDI3FEHPOWitSsky1hMBGZvUJaCIi8SGf1XxxWHxuhAtUktBwQJXirHcUvhU8bEC7Y08eTFcgpeMto0fYa39CnzhoTJltms-4oIfokAS0t0c/s16000/3.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjm0U0IIuSFPaSvO1F1zAKgnIk1u3t_zeCgGcshdu7KopcAaO0fsBgS-4sEd9RyzzKnf-Ztgb2233Ikc2a0yCKRrrMk-7MhPeW_h6vAWaBqjg5k0AdyitSk3FsovzRuFMTqGvlbrBt_X5ErLJ7ZHnnoELV4wf8i2z_GBuaic2wVQlA1rNRwOaBGHAFaCkZA/s975/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="81" data-original-width="975" height="34" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjm0U0IIuSFPaSvO1F1zAKgnIk1u3t_zeCgGcshdu7KopcAaO0fsBgS-4sEd9RyzzKnf-Ztgb2233Ikc2a0yCKRrrMk-7MhPeW_h6vAWaBqjg5k0AdyitSk3FsovzRuFMTqGvlbrBt_X5ErLJ7ZHnnoELV4wf8i2z_GBuaic2wVQlA1rNRwOaBGHAFaCkZA/w400-h34/4.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">With this status now have successfully created HDI Container.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>4. Create roles on HDI container by using HANA Web IDE</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Create the required roles to allow SAP Datasphere to read from and, optionally, write to the container.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Must define the roles DWC_CONSUMPTION_ROLE and DWC_CONSUMPTION_ROLE# (with grant option) in the container to allow to add into DSP space and allow to exchange data between the container and the space. </div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ To Create this roles on HDI Container user should be part of this roles Business_Application_Studio_Developer on BTP Subaccount & Space Developer on BTP space.</div><div class="separator" style="clear: both;">◉ Login tot the Business Application Studio (BAS) and create Dev Space by selecting SAP HANA Native Application.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhZ4eNvWalaJYd24DVxJQIeXJA_uSXUqmTNDuhWRqewBQDAXngqW52FKWQkiUAyiD2ypGsevO82AgJwLnDnY1XOPw2HNvtMA55KlDIA8Gu6wyjE0Fkfpcw4P_Y9CYZwA5EI0oCru1c-wv5hMTSCETOkzn0oasXyrsr3ZA5IX-uhqPlkklDgBna3SNfxROYK/s975/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="445" data-original-width="975" height="183" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhZ4eNvWalaJYd24DVxJQIeXJA_uSXUqmTNDuhWRqewBQDAXngqW52FKWQkiUAyiD2ypGsevO82AgJwLnDnY1XOPw2HNvtMA55KlDIA8Gu6wyjE0Fkfpcw4P_Y9CYZwA5EI0oCru1c-wv5hMTSCETOkzn0oasXyrsr3ZA5IX-uhqPlkklDgBna3SNfxROYK/w400-h183/5.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Open Dev Workspace and Create one SAP HANA Database project</div><div class="separator" style="clear: both;">◉ Click on New Project from Template and select Create SAP HANA Database project click start.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhJJnK4I1fIlVaCC51FNjjla5P6ChNNZCLT0NUO5LayAFpr1_fFfJyw-ZjeXFu9GOnzo3YJlmZ2YEgMmobI9x0onsaCPRl2osCosNe7n9Mdek0yNZ23hWdmhnCP5QAqCpmRUEfQl0necMSS0j5CjnQGLual-bAuDlnqAQOzDv1jqNumoGv-4NGLGH2Lwl7q/s975/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="450" data-original-width="975" height="185" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhJJnK4I1fIlVaCC51FNjjla5P6ChNNZCLT0NUO5LayAFpr1_fFfJyw-ZjeXFu9GOnzo3YJlmZ2YEgMmobI9x0onsaCPRl2osCosNe7n9Mdek0yNZ23hWdmhnCP5QAqCpmRUEfQl0necMSS0j5CjnQGLual-bAuDlnqAQOzDv1jqNumoGv-4NGLGH2Lwl7q/w400-h185/6.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Enter the project name (ex: TEST) and SAP HANA Database Version should be an SAP HANA CLOUD</div><div class="separator" style="clear: both;">◉ Login to CF account by using credentials authentication method (By entering SAP Email and SAP Global Password) and then click Sign in</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjEC8rXFh_26ibQ0rsYQ-NKwANopI8t9f6LX-Bmnb5DPrtOdsa9EP_DuJfiNwNiRMmubWDOewMc0887y7CkzVzqMgyec2AXm3lNir7jFoE4rhxjlfCbtfUYiSB6tvjFD2-E20x3R11APm8DlXxsZcYt0s-sH2vuecYr-xjGLJNiyYzLROo8Vpm006isN2F/s808/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="378" data-original-width="808" height="188" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjEC8rXFh_26ibQ0rsYQ-NKwANopI8t9f6LX-Bmnb5DPrtOdsa9EP_DuJfiNwNiRMmubWDOewMc0887y7CkzVzqMgyec2AXm3lNir7jFoE4rhxjlfCbtfUYiSB6tvjFD2-E20x3R11APm8DlXxsZcYt0s-sH2vuecYr-xjGLJNiyYzLROo8Vpm006isN2F/w400-h188/7.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Select the CF target details Subaccount/organization and CF space</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWlHYlFPFkCqIXOeFrNq8Q8x7pEv9LMtuc1_-rjj0PxaB4Ec74ACvomTCxNrXe6PRKGbS7oGdDkjdzFLbjhxrar2Ya2xLSosHstoXYTNZhqmLKltpk595in1gIBpucoZf2mtXN48uJeZgc6Os71_ArrGsqAwdMTnW7KQGkPEFMqsqAIE8GIxOv4FquOYye/s727/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="381" data-original-width="727" height="210" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWlHYlFPFkCqIXOeFrNq8Q8x7pEv9LMtuc1_-rjj0PxaB4Ec74ACvomTCxNrXe6PRKGbS7oGdDkjdzFLbjhxrar2Ya2xLSosHstoXYTNZhqmLKltpk595in1gIBpucoZf2mtXN48uJeZgc6Os71_ArrGsqAwdMTnW7KQGkPEFMqsqAIE8GIxOv4FquOYye/w400-h210/8.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ And then Bind to HDI Container Service like below</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQ_gF2o7SZY68leac4jrwTzDOPn17OSg3IStJy7RNVEx34_g8ObHbCVT5Mm2rxJvHMS0ywoevatIgkhZSO7lHBrIR-m3gmGqExKYXRqjLqE26_ZN9uHgG_zc4tUU4-1Ie5a_upcWFWE2gd7o4sCAY3NE1JDaqSaSBpZltQn1GKGNMiEReZTHg3BLeYcABK/s405/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="405" data-original-width="394" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQ_gF2o7SZY68leac4jrwTzDOPn17OSg3IStJy7RNVEx34_g8ObHbCVT5Mm2rxJvHMS0ywoevatIgkhZSO7lHBrIR-m3gmGqExKYXRqjLqE26_ZN9uHgG_zc4tUU4-1Ie5a_upcWFWE2gd7o4sCAY3NE1JDaqSaSBpZltQn1GKGNMiEReZTHg3BLeYcABK/w389-h400/9.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="389" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Click on Finish Button and with this step User have successfully created SAP HANA Database Project.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Can also verify either User have connected to correct HDI container or not by checking the service key on HDI container.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Once Project get created it will also generate and Create one service key "SharedDevKey" for the Cloud Foundry service instance "<HDI Container_name>"</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Create a DWC_CONSUMPTION_ROLE and DWC_CONSUMPTION_ROLE# roles under this Project on BAS.</div><div class="separator" style="clear: both;">◉ Under db==>src folder User will have to create above two roles like below</div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>Role Name -1</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">DWC_CONSUMPTION_ROLE_WITH_GRANT.hdbrole</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzYI4CO55LnMtgKAkNUI7C8ZxdTHhbKr8VTzJgFs_Jvde_iZ59QwgCnDUg_JuqMCUVuKwr4NJs1Oi9zkgFRHtM7YzOIy_WWziYFvXtYEwRaYbd7a0uswntlKbV6hmiCksYINrSnp6-PHTFmbgQaWaQdUmbGitN0-mW5HomtoHT4fQNs_8AiWxCXeMIpEqY/s533/10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="213" data-original-width="533" height="160" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjzYI4CO55LnMtgKAkNUI7C8ZxdTHhbKr8VTzJgFs_Jvde_iZ59QwgCnDUg_JuqMCUVuKwr4NJs1Oi9zkgFRHtM7YzOIy_WWziYFvXtYEwRaYbd7a0uswntlKbV6hmiCksYINrSnp6-PHTFmbgQaWaQdUmbGitN0-mW5HomtoHT4fQNs_8AiWxCXeMIpEqY/w400-h160/10.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">{ "role": {"name": "DWC_CONSUMPTION_ROLE#",</div><div class="separator" style="clear: both;"> "schema_privileges": [{"privileges_with_grant_option":[ "SELECT","SELECT METADATA","EXECUTE" ]}]}}</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;"><b>Role Name -2</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">DWC_CONSUMPTION_ROLE.hdbrole</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhmFVTLvQgs2nQjQHspa6rSj34o-7sGiVghvIhilnwA2DXzAYIwjOAvg4EnJF-IQGMmDCqmoIjxmEJPEk1u3mKiFUllbkb_SJBG0XYv1jYzofXl9lVCxW4Sk9S42MhyGr14r07tbf9jagsSJDNMAURcxVllmc048qMlVlPVf9WaTnz8eiGRVo67nFBsz7Yr/s426/11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="215" data-original-width="426" height="162" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhmFVTLvQgs2nQjQHspa6rSj34o-7sGiVghvIhilnwA2DXzAYIwjOAvg4EnJF-IQGMmDCqmoIjxmEJPEk1u3mKiFUllbkb_SJBG0XYv1jYzofXl9lVCxW4Sk9S42MhyGr14r07tbf9jagsSJDNMAURcxVllmc048qMlVlPVf9WaTnz8eiGRVo67nFBsz7Yr/w320-h162/11.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="320" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">{ "role": {"name": "DWC_CONSUMPTION_ROLE",</div><div class="separator" style="clear: both;"> "schema_privileges": [{"privileges":[ "SELECT","SELECT METADATA","EXECUTE" ]}]}}</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;">Add HDI container info into mta.yaml file:</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgIpfSxcyHQpL7ZHgZrQRUpmXcDbKx_-Ixq_Hl3viB7UyyyzJwWfF4-k_MpVufyrPjLrkgpena0qbmYd2ZJyo5mW5TZsj8_0o_LMA63qvIyE4lyUpnaQWwM-2Fzh4_UPSJDAKoQgj4pickFkG9bVkWJMnI1gaPSPlKF5iQI-Xwdoqe-MDsZH8Howo3HLwzr/s553/12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="293" data-original-width="553" height="213" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgIpfSxcyHQpL7ZHgZrQRUpmXcDbKx_-Ixq_Hl3viB7UyyyzJwWfF4-k_MpVufyrPjLrkgpena0qbmYd2ZJyo5mW5TZsj8_0o_LMA63qvIyE4lyUpnaQWwM-2Fzh4_UPSJDAKoQgj4pickFkG9bVkWJMnI1gaPSPlKF5iQI-Xwdoqe-MDsZH8Howo3HLwzr/w400-h213/12.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">And then try deploy this into Database connection like below</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Under SAP HANA PROJECTS folder see all the files and then click on bind icon on project folder like below</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3EtB1vEeC3rt9PN9X6giChQmC7gcbAG_DX17w_bdtN06CiJWdk5Jsa2NFuPXXn0jV2h4pFo2x-PyOJjON0iNZcajYm8X01BpVp9_P-UQgWnIV8k-AJ_A0OWBX3Ujmit-4QZJlr41RbJnGhDFs1fl-Y7f3pIZiC_Hdwnf6rl-Rnz6gv1HinPT6izQMMsP8/s423/13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="298" data-original-width="423" height="281" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3EtB1vEeC3rt9PN9X6giChQmC7gcbAG_DX17w_bdtN06CiJWdk5Jsa2NFuPXXn0jV2h4pFo2x-PyOJjON0iNZcajYm8X01BpVp9_P-UQgWnIV8k-AJ_A0OWBX3Ujmit-4QZJlr41RbJnGhDFs1fl-Y7f3pIZiC_Hdwnf6rl-Rnz6gv1HinPT6izQMMsP8/w400-h281/13.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><i><b>Make succeeded (0 warnings): 2 files deployed (effective 2), 0 files undeployed (effective 0), 0 dependent files redeployed. Making... ok (0s 303ms)</b></i></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">With this now have successfully created roles into HDI Container.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>5. Add/Deploy HDI Container instance into SAP Datasphere</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To Deploy the HDI Container into SAP Datasphere Space user should be part of any one of this roles DW Administrator, System Owner, Space Owner</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Go to Expand Navigation bar ==>Space management==> <Select the space>==> Database Access ==>HDI Containers</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPkdOVKjRdgwirslqwqG_GgQCKjncKGAO90lBh4sCDN8SJCdWHhX7f3zS2m09SaIX1nFcdVw5yB0HukZey3N64er085cjUaXD9bvYqPx_ceq14jL_UmE6Fl6cShZUfL8Xg0PpP1u5nCWMBx5slCReeodI_Y_PVBFsSh2iG8kBrZc-Z7U9fuTVMtWgh6tWn/s975/14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="374" data-original-width="975" height="154" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPkdOVKjRdgwirslqwqG_GgQCKjncKGAO90lBh4sCDN8SJCdWHhX7f3zS2m09SaIX1nFcdVw5yB0HukZey3N64er085cjUaXD9bvYqPx_ceq14jL_UmE6Fl6cShZUfL8Xg0PpP1u5nCWMBx5slCReeodI_Y_PVBFsSh2iG8kBrZc-Z7U9fuTVMtWgh6tWn/w400-h154/14.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Select the HDI Container by click on +</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Deploy the space by Click on Deploy button.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">If deployment went successful then HDI container successfully added into SAP Datasphere space.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To verify this HDI container is deployed successfully or not check/test this HDI container is appearing under Data Builder application</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgT43JOUbjj963-cw9xQ67zIcHO_t0oUpuquQRwJwJeiR3Pwtt88TOj4w1tLkliCxhs5V1FPcZAg1QxVKANCQMg8CCBdmCUa_7tr2s0JirQtAiWTlxlMy9NYeYccqOC4aSKafm3WUXn5uS9JaE96ztUwyHu2dFB6tUKDX3O_Joot_SQ6nlceolHg5xDUuio/s659/15.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" border="0" data-original-height="381" data-original-width="659" height="231" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgT43JOUbjj963-cw9xQ67zIcHO_t0oUpuquQRwJwJeiR3Pwtt88TOj4w1tLkliCxhs5V1FPcZAg1QxVKANCQMg8CCBdmCUa_7tr2s0JirQtAiWTlxlMy9NYeYccqOC4aSKafm3WUXn5uS9JaE96ztUwyHu2dFB6tUKDX3O_Joot_SQ6nlceolHg5xDUuio/w400-h231/15.png" title="SAP Datasphere – Enable SAP HANA Development Infrastructure (HDI)" width="400" /></a></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-15903027587328201922024-02-19T14:06:00.002+05:302024-02-19T14:06:30.285+05:30S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service<div>In this article I will explain how these federated roles from S/4HANA assigned automatically to users in BTP via SAP Identity provision service without any manual intervention.</div><div><br /></div><div>To achieve this scenario, we should have below prerequisite: -</div><div><br /></div><div><ol style="text-align: left;"><li>SAP BTP cockpit, where we subscribe to the Cloud Identity Services connectivity plan in the subaccount.In SAP BTP Cockpit, open the subaccount and choose Service Marketplace Integration Suite- Cloud Identity Services and then choose for what type of tenant (test or productive) to use in the subaccount.</li><li>The Identity Provisioning section of SAP Cloud Identity Services administration console, where we configure the S/4Hana system and SAP IAS as provisioning system.</li><li>Content Federation has been setup and S/4HANA role content are federated and visible as role collection in BTP.<span><a name='more'></a></span></li></ol></div><div><br /></div><div>Below are the configuration Steps for automatic Federated role assignment in BTP Via SAP Identity provision service.</div><div><br /></div><div><b>1. Create a destination for S/4Hana as Application Server ABAP system.</b></div><div><br /></div><div>Open SAP BTP cockpit, and in the Identity Provisioning subaccount create a destination for the AS ABAP system. The destination configuration is required by the Identity Provisioning service to find the back-end system to be used for reading data. It also provides the credentials of the technical user (created in S/4Hana System), needed for the connection to the ABAP public API.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwUC2XYvAupXQHz24KHQhwxOix8Q1tJIVB0B5TzaaxMnBvZ1uqvl9Is1Fbaob_DEIGxvO3j2DCZMZrRkA31fvygd0Dm9DfWLOeifRfj3gMgG2pmsnRj9S6xhmE1_ag1xFdG1qOYjIHqr-ig434HLvq32Fzq4jpmcY9WtNK5q56ZZEnLk166LeIkHbSuayV/s628/1.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="207" data-original-width="628" height="131" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwUC2XYvAupXQHz24KHQhwxOix8Q1tJIVB0B5TzaaxMnBvZ1uqvl9Is1Fbaob_DEIGxvO3j2DCZMZrRkA31fvygd0Dm9DfWLOeifRfj3gMgG2pmsnRj9S6xhmE1_ag1xFdG1qOYjIHqr-ig434HLvq32Fzq4jpmcY9WtNK5q56ZZEnLk166LeIkHbSuayV/w400-h131/1.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>2. Create Source System as S/4HANA system.</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Access Identity Provisioning. Add SAP Application Server ABAP as a source system. From the Destination Name dropdown, choose the RFC destination we have created in Step 1.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgUaCXJkyj4rQeKS7U_gZp8MOt46-q-au7u6a6DvgTCAD-_zcNzwvOGzMRBWGRKeEQRvcgSdvHBCz-Gp9zgPJtTTmBi7uDhqptdoeNQ29iQFb77pDSexoLTPtXWOd_1nRYrIxns_YaqktVPCtwnwenV83LNXr_BvYcPQ8irZKvyBxcGUY4euwGu-5rXma7n/s607/2.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="285" data-original-width="607" height="188" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgUaCXJkyj4rQeKS7U_gZp8MOt46-q-au7u6a6DvgTCAD-_zcNzwvOGzMRBWGRKeEQRvcgSdvHBCz-Gp9zgPJtTTmBi7uDhqptdoeNQ29iQFb77pDSexoLTPtXWOd_1nRYrIxns_YaqktVPCtwnwenV83LNXr_BvYcPQ8irZKvyBxcGUY4euwGu-5rXma7n/w400-h188/2.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Read the users from Source S/4HANA based on the Federated Role assigned to users in S/4HANA system.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Add the Federated role in the User filter source system.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_5874OdQ7BP_jSGwlfkS5l48sgiUpZ2kyH5DgH8QL8VqXdGqnH8v6rBJrl9w84TIWCnevoypEa5fLDhfE2gN6l6JOE1GPxbiVrDLm6bIxFWFKua7UH4yNAPzEhjHGKD7elf0WqxRz9ycdDjLpPtA1R2aN6qs39KUo-Cbc_mHy_l_mCm6z5KXZcTr5ACV0/s659/3.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="236" data-original-width="659" height="144" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_5874OdQ7BP_jSGwlfkS5l48sgiUpZ2kyH5DgH8QL8VqXdGqnH8v6rBJrl9w84TIWCnevoypEa5fLDhfE2gN6l6JOE1GPxbiVrDLm6bIxFWFKua7UH4yNAPzEhjHGKD7elf0WqxRz9ycdDjLpPtA1R2aN6qs39KUo-Cbc_mHy_l_mCm6z5KXZcTr5ACV0/w400-h144/3.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>3. Create target system as SAP IAS</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Add Identity Authentication as a target system and keep source system the same as created in Step 2. Set up the communication between Identity Provisioning and Identity Authentication and configure the authentication method. I have used basic authentication.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">For basic authentication, provide a password. The user ID will be generated automatically when we set the password for the first time.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">a. Add system as administrator and provide the respective credentials. Make sure Manage Users and Manage Groups authorization roles are enabled for the technical user. This way, we can create, edit and delete users and groups in the Identity Authentication user store.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj3IgZRAhxsBsAe_Go5W-kvDrgbBSeTt3eIJgglRk8NYw3odTkssVds_LZ1tH2AsBFC4vrzhFdkKE_AoqEkBcqeONeDfAMRolK2ME7U5kvA5K49xiEHZN81j4IYtoIg_FDqQFAfhuvYr8V4awVJMJ92X58c133dqMFjmRDUDBROYWJctAMDEBb3TzxF_rHN/s661/4.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="243" data-original-width="661" height="148" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj3IgZRAhxsBsAe_Go5W-kvDrgbBSeTt3eIJgglRk8NYw3odTkssVds_LZ1tH2AsBFC4vrzhFdkKE_AoqEkBcqeONeDfAMRolK2ME7U5kvA5K49xiEHZN81j4IYtoIg_FDqQFAfhuvYr8V4awVJMJ92X58c133dqMFjmRDUDBROYWJctAMDEBb3TzxF_rHN/w400-h148/4.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Please put below mandatory property also other respective properties as required.</div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><table border="1" style="width: 100%;">
<tbody>
<tr>
<td>
<p>ias.user.unique.attribute</p>
</td>
<td>This property defines by which unique attribute(s) an existing user will be resolved in the event of conflicting users. Its value is set to emails[0].value, since we are using common attribute as email for user.</td>
</tr>
<tr>
<td>User </td>
<td>
<p>For BasicAuthentication Enter the Client ID of the Identity Authentication technical user created in step 3(a). For example: 1ab7c243-5de5-4530-8g14-1234h26373ab</p>
</td>
</tr>
<tr>
<td>Password </td>
<td>
<p>Enter the Client Secret of the Identity Authentication technical user. It is generated automatically for the administrator of type system, when choosing Secrets.</p>
</td>
</tr>
</tbody>
</table>
</div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNkq8O3MEsz_thFks_cXSWd2Iyn62VP694ad0Gow-HwH6lRhKOhLaC8rPsNDYSe0NkO2ONsBY0abuPer3-Lj_d79zoawFXAW7boXUKuI802e6GmjFM0adw_rKr2iUch-f2eg_VRpCVdDHUD8vF68uego6nuvn4EBwN5xnHQi5OHt_zMcYmbreXeRbgcaTn/s650/5.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="284" data-original-width="650" height="175" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNkq8O3MEsz_thFks_cXSWd2Iyn62VP694ad0Gow-HwH6lRhKOhLaC8rPsNDYSe0NkO2ONsBY0abuPer3-Lj_d79zoawFXAW7boXUKuI802e6GmjFM0adw_rKr2iUch-f2eg_VRpCVdDHUD8vF68uego6nuvn4EBwN5xnHQi5OHt_zMcYmbreXeRbgcaTn/w400-h175/5.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Note: </b>- In our case we have different login name in S/4 Hana and SAP IAS and same email address is maintained in both the applications. SAP IAS has existing user master record based on SuccessFactors.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In this case IPS jobs with patch operation will make sure no information of existing IAS user will get change and it will patch the login name in display name of the S/4HANA user in SAP IAS.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Add the below transformation to perform Patch operation based on email Id since username in IAS is different from the one in S/4HANA system, so email ID is used. S/4HANA Login name will be updated in display name field in IAS.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgb5629ufIkpxKa9uj3gjoIWr5i2Dv7BQ7uXYV3IB4fFlDQZPcg4IWOlWrh3wsGxTdshcB_OzcX7HSSHcbvlwh2ymb_dT-_xF8C-ljW38c8FfDkqoxMMhdVbfyxuu85hU3G83EtQfL4NDeR1oaOl_fxUyGf1a1DU0uuWnAjiclgmu7_ecJGCWbU04e91g3E/s407/6.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="269" data-original-width="407" height="264" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgb5629ufIkpxKa9uj3gjoIWr5i2Dv7BQ7uXYV3IB4fFlDQZPcg4IWOlWrh3wsGxTdshcB_OzcX7HSSHcbvlwh2ymb_dT-_xF8C-ljW38c8FfDkqoxMMhdVbfyxuu85hU3G83EtQfL4NDeR1oaOl_fxUyGf1a1DU0uuWnAjiclgmu7_ecJGCWbU04e91g3E/w400-h264/6.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>4. Create IAS group with same name as S/4 Hana Roles.</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Create User group in SAP IAS with the same name as S/4HANA roles. Since the same group name will be mapped to users based on the transformation scripts.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkorXZp24QcxIWYSraYRLDCetRPOZ14R5XIUUQ1AIeWrxBmHtSJR1HL-uy4Sp2U0xPcwicYESyCVeF9g9EJNMCjaX2ccwZUE3fXwu9EkZFl324kkQw-vldvh95lqvfjrK42tb_PhNxO-E3lwgMP4fjWDypik5WCQnkQumOM6kct7IV-RFDIONIO1x2VKCs/s650/7.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="202" data-original-width="650" height="124" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkorXZp24QcxIWYSraYRLDCetRPOZ14R5XIUUQ1AIeWrxBmHtSJR1HL-uy4Sp2U0xPcwicYESyCVeF9g9EJNMCjaX2ccwZUE3fXwu9EkZFl324kkQw-vldvh95lqvfjrK42tb_PhNxO-E3lwgMP4fjWDypik5WCQnkQumOM6kct7IV-RFDIONIO1x2VKCs/w400-h124/7.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>5. Map Role collection</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Once S/4Hana Fiori roles are federated to BTP, they are visible as BTP role Collection. Map these federated roles with IAS group created in step 4 in BTP trust configuration for the IAS configuration subaccount.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5NMjZpQjQv4DATi_RovwczjrMZX62dGdgrS8GSquTiyK5tMdlWXOKjzZtiggvTFoFjXjfgeDhjdtAxF3X_WoFmNyOLmBUPUhG2epA6jJ83PXpAZdIWIbOy1EN-yodd-Ho-QHtzvYSSRfYB7mfl10Z1LE0ACp5FJAKFWAaJK4UeSVzEr0rJVEIoyYQq1bn/s660/8.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="199" data-original-width="660" height="120" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5NMjZpQjQv4DATi_RovwczjrMZX62dGdgrS8GSquTiyK5tMdlWXOKjzZtiggvTFoFjXjfgeDhjdtAxF3X_WoFmNyOLmBUPUhG2epA6jJ83PXpAZdIWIbOy1EN-yodd-Ho-QHtzvYSSRfYB7mfl10Z1LE0ACp5FJAKFWAaJK4UeSVzEr0rJVEIoyYQq1bn/w400-h120/8.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>6. Run the IPS synchronization Job.</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Run the Read job for the Source S/4HANA created in Step 2. This job can be scheduled in regular interval to read the users from S/4Hana and write in SAP IAS.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj880FadSKR4koQLIz5Gc2XSFq1QbWAC-uiWMO3eic4faVk3oO9ZjwUpATYn8qOrjhK4Hb06aLHOfiC8eHbDLUloCaWz6N7sdJ3kwNVA5taOTjmH7lsvww6io9JxaO6jl-jxktyqamqW0gexplqZsv7G7oEmADVfSjHPzG8goc2yPp5_-dp65gMvrud9PSe/s656/9.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="300" data-original-width="656" height="183" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj880FadSKR4koQLIz5Gc2XSFq1QbWAC-uiWMO3eic4faVk3oO9ZjwUpATYn8qOrjhK4Hb06aLHOfiC8eHbDLUloCaWz6N7sdJ3kwNVA5taOTjmH7lsvww6io9JxaO6jl-jxktyqamqW0gexplqZsv7G7oEmADVfSjHPzG8goc2yPp5_-dp65gMvrud9PSe/w400-h183/9.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Job Logs will show the user and group – created/ updated/Deleted based on the source and target transformation scripts.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgT8Eou-QizqWLFllcVBjKcJql68CsoVvvFKR31y26-Sk0LibJEQtGsDhyphenhyphen4v0tPXrly7SsvQDLdlCj7V51qfZyHIv5RQ9Z9W40bnX3o2OQCul94XDbyPeeuHFN-SnkbMGmMubZCRO2SAKic8SBRnTWnldZqTTBpSzf37UOh9cLkXpDZV6H_IibKg2T_3Zkx/s650/10.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="256" data-original-width="650" height="158" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgT8Eou-QizqWLFllcVBjKcJql68CsoVvvFKR31y26-Sk0LibJEQtGsDhyphenhyphen4v0tPXrly7SsvQDLdlCj7V51qfZyHIv5RQ9Z9W40bnX3o2OQCul94XDbyPeeuHFN-SnkbMGmMubZCRO2SAKic8SBRnTWnldZqTTBpSzf37UOh9cLkXpDZV6H_IibKg2T_3Zkx/w400-h158/10.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>7. SAP IAS group assignment.</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In SAP IAS user will get the IAS group automatically assigned once the IPS synchronization job gets finished. User will be getting the groups assigned based on the role assigned in S/4Hana.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">a. Role Assigned in S/4HANA.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjsl1bzZrGyRjBDXlESvLyIYwSRNhse-vwh9KN9FehkTTP6sAZEd_y7EGz3FfYQeSDfbRvUQ2q_qdSnqKjr-_HYwYAeNRKh5L1le4BRwWyHr9qm_m0ZfV3wi-fJ0VmS1iJcyDVN2RtYPA9RMdVDIdhhMSLHJavMHHOpNhRNswX3dXralm4IAvDPOS8CiW5v/s627/11.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="229" data-original-width="627" height="146" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjsl1bzZrGyRjBDXlESvLyIYwSRNhse-vwh9KN9FehkTTP6sAZEd_y7EGz3FfYQeSDfbRvUQ2q_qdSnqKjr-_HYwYAeNRKh5L1le4BRwWyHr9qm_m0ZfV3wi-fJ0VmS1iJcyDVN2RtYPA9RMdVDIdhhMSLHJavMHHOpNhRNswX3dXralm4IAvDPOS8CiW5v/w400-h146/11.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">b. Same groups get assigned to user in SAP IAS automatically based on the Role assigned to user in S/4HANA in Step 7(a).</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiSYLuGqkZsAClNAiA0ZKS3uXqohxBIgUyF03uP96tMDs_63TN8QPL6EkeIDWueGPWgtZPlEmXX42emkBG_oDSagyzmlW_8nFfCZ4lIi7sEik4ETKCBAoJ8J2kpE7S-ufPRTDMkyy5cUsvAseyBy2-iWKbO_6Rfvdee1kVESOC58e8rl0AMW3RvBiqvp20C/s607/12.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="215" data-original-width="607" height="141" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiSYLuGqkZsAClNAiA0ZKS3uXqohxBIgUyF03uP96tMDs_63TN8QPL6EkeIDWueGPWgtZPlEmXX42emkBG_oDSagyzmlW_8nFfCZ4lIi7sEik4ETKCBAoJ8J2kpE7S-ufPRTDMkyy5cUsvAseyBy2-iWKbO_6Rfvdee1kVESOC58e8rl0AMW3RvBiqvp20C/w400-h141/12.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>8. Login with the same user id’s email in SAP BTP Work zone site.</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">User can login to work Zone site and access the application federated by S/4 HANA roles.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjAKeWBDd0W7E8hPywCSSN5PdI4dWWfjfl7s7mKQ8oyNLjvZjbgcMJsgQv7TcRweGyY8hmM8nYiMoMe5j5RyCk_BXy5MFKN8aOUpsW7UQ92AfGBdpUp-iXKRKbqCkygk9MHqLHrHWfyP2EsmcTyMYYPP7wiRnKGAPHvf5MuhBdFSHVtag6C6mHRErq_6jR/s630/13.png" style="margin-left: 1em; margin-right: 1em;"><img alt="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" border="0" data-original-height="244" data-original-width="630" height="155" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjAKeWBDd0W7E8hPywCSSN5PdI4dWWfjfl7s7mKQ8oyNLjvZjbgcMJsgQv7TcRweGyY8hmM8nYiMoMe5j5RyCk_BXy5MFKN8aOUpsW7UQ92AfGBdpUp-iXKRKbqCkygk9MHqLHrHWfyP2EsmcTyMYYPP7wiRnKGAPHvf5MuhBdFSHVtag6C6mHRErq_6jR/w400-h155/13.png" title="S/4HANA federated roles assignment to users in BTP via SAP Identity Provisioning Service" width="400" /></a></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-29678526483244597072024-02-16T13:55:00.006+05:302024-02-16T14:02:38.979+05:30Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud<div>In this blog post I will explain how SAP Cloud ALM integrates with the test automation tool for SAP S/4 HANA Cloud.</div><div><br /></div><div>SAP Cloud ALM provides (among other capabilities) test management, including manual testing as well as test automation integration.</div><div><br /></div><div>This simple picture gives an overview of the SAP Cloud ALM Test Orchestration capabilities:<span><a name='more'></a></span></div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEge6CEWLZwxE5ePDmsB9o2zZMNPQ2xgRaD4zwN4fmope92BhGDac6hG26DkZPG_J8HojXM0u1WzEK-jVPyudrbgX3p7Jyrg59C7mav5PJv6vUCR4YW6BIIBQBEXprF8KdHCNZt3xvqUNYZAO7jOrF_-w3UY9b_7N5ubdiUi6VIvfa1XkA8jDcVZC4AWGwB7/s808/1.png" style="margin-left: 1em; margin-right: 1em;"><img alt="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" border="0" data-original-height="808" data-original-width="702" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEge6CEWLZwxE5ePDmsB9o2zZMNPQ2xgRaD4zwN4fmope92BhGDac6hG26DkZPG_J8HojXM0u1WzEK-jVPyudrbgX3p7Jyrg59C7mav5PJv6vUCR4YW6BIIBQBEXprF8KdHCNZt3xvqUNYZAO7jOrF_-w3UY9b_7N5ubdiUi6VIvfa1XkA8jDcVZC4AWGwB7/w348-h400/1.png" title="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" width="348" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">As displayed our test automation framework approach will allow us to integrate with test automation providers.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">We have the plan to integrate with several cloud based test automation providers, Tricentis new cloud based product will be the first one from external companies but until then I am happy to announce that the integration of the test automation tool for SAP S/4 HANA has now been productive since May 2021.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">This integration is based on a set of versioned REST APIs, these APIs are officially published in the <b><a href="https://api.sap.com/api/CALM_TEST_AUTOMATION/overview" target="_blank">SAP Business API Hub</a></b>.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Here is an overview of the methods, but all the details should be checked online from the previously mentioned link.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgLvQFi817FNcq_zZCfwZMqPbbBguODncwgqZi6_24537z5zwEv-C5_8gNm3oYjZCDN6vXscMr1bAy4wp78fkuqFQ6s1Bmhdi7e3WH8E412yndhw-wjecaOgvLU3blO4skdsrBA3_EAoaopCyKpN9FKfTzc9PKOY-hvR4XXuQCmjgWpaVxBJBaAisqdmaYK/s967/2.png" style="margin-left: 1em; margin-right: 1em;"><img alt="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" border="0" data-original-height="435" data-original-width="967" height="180" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgLvQFi817FNcq_zZCfwZMqPbbBguODncwgqZi6_24537z5zwEv-C5_8gNm3oYjZCDN6vXscMr1bAy4wp78fkuqFQ6s1Bmhdi7e3WH8E412yndhw-wjecaOgvLU3blO4skdsrBA3_EAoaopCyKpN9FKfTzc9PKOY-hvR4XXuQCmjgWpaVxBJBaAisqdmaYK/w400-h180/2.png" title="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Automation API Methods</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Let's explore now how to setup the connectivity between <b><a href="https://www.hanaexam.com/p/certifications.html">SAP Cloud ALM</a></b> and the test automation tool for SAP S/4 HANA Cloud. You only need to create a cloud service and an end point in the SAP Cloud ALM Landscape Management application. The complete procedure is described in the help portal: <b><a href="https://help.sap.com/docs/cloud-alm/setup-administration/test-automation-tool-for-s4hana-cloud?locale=en-US" target="_blank">here</a></b>.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Once the configuration is complete you should have a similar end point in the landscape management application:</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDPifr_HBRxSc0wwj9UKm-5xkINujMkkdMfwZzU_OzFaYEFBJa1kWzybI-0nefGKIGYvQCWwQ3VVoFGWIggNwQ1Pmg3Q6-DP7TMJh9uZ3NMoGh9-RE-vxrMdZZQx3I6cI819I5_7KdRm5U1Y3miAZ9HU28zUy2fnVCAl3OYx_7BPqzCacFAQtfne7KN3CC/s800/3.png" style="margin-left: 1em; margin-right: 1em;"><img alt="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" border="0" data-original-height="638" data-original-width="800" height="319" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDPifr_HBRxSc0wwj9UKm-5xkINujMkkdMfwZzU_OzFaYEFBJa1kWzybI-0nefGKIGYvQCWwQ3VVoFGWIggNwQ1Pmg3Q6-DP7TMJh9uZ3NMoGh9-RE-vxrMdZZQx3I6cI819I5_7KdRm5U1Y3miAZ9HU28zUy2fnVCAl3OYx_7BPqzCacFAQtfne7KN3CC/w400-h319/3.png" title="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">End point</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">You can use the button "Check Connection" to ensure that your endpoint is correctly configured.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Once this is done, you are ready to synchronize automated test cases from the test automation tool for SAP S/4 HANA Cloud. It is as simple as that.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The automated test cases can be synchronized only for the solution processes from the solution scenario SAP Best Practices for SAP S/4 HANA Cloud, as shown here:</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg4GcCaimr9zZb6X8ZJStXP0-1juy7UlvsQAJ2bNPHjWGYPBtxn5YW4LHsa-gGLGLffopi_Bsqkp6vp6ec_0-tZP9F62kX6sM5KAdAaSmnlvUHScs6QDTa32afyGDrydHWJCGn-FZCbir2k1yHmlGvS7e5781BjRhbRzEg3s50r7W7U859mxM5rWv7_akfa/s413/4.png" style="margin-left: 1em; margin-right: 1em;"><img alt="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" border="0" data-original-height="195" data-original-width="413" height="189" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg4GcCaimr9zZb6X8ZJStXP0-1juy7UlvsQAJ2bNPHjWGYPBtxn5YW4LHsa-gGLGLffopi_Bsqkp6vp6ec_0-tZP9F62kX6sM5KAdAaSmnlvUHScs6QDTa32afyGDrydHWJCGn-FZCbir2k1yHmlGvS7e5781BjRhbRzEg3s50r7W7U859mxM5rWv7_akfa/w400-h189/4.png" title="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Solution Scenario: SAP Best Practices for SAP S/4 HANA Cloud</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">When you scope a solution process which has an automated test cases in the test automation tool, this automated test case will be automatically synchronized with SAP Cloud ALM as shown here:</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiMAlza85h6KXeUvh6J97G7FwQKIkbKJbJ9j4hJTQbR7k4ZYB8m5sIKZs-LSKyLb21PwvPR7FYyCUNOCFJYPXJ_7-pumf3G3H2YqWfJkae7T5IJTOnWdwZlDpdSGKeoCgjgpv0vTKjklQFiQAnazic51d9W0Wd96W4wItHMwpCkohAKrpn2Dm7Q6rneCTdd/s1140/5.png" style="margin-left: 1em; margin-right: 1em;"><img alt="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" border="0" data-original-height="557" data-original-width="1140" height="195" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiMAlza85h6KXeUvh6J97G7FwQKIkbKJbJ9j4hJTQbR7k4ZYB8m5sIKZs-LSKyLb21PwvPR7FYyCUNOCFJYPXJ_7-pumf3G3H2YqWfJkae7T5IJTOnWdwZlDpdSGKeoCgjgpv0vTKjklQFiQAnazic51d9W0Wd96W4wItHMwpCkohAKrpn2Dm7Q6rneCTdd/w400-h195/5.png" title="Integrating SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Synchronized Automated Test Cases</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">You can now navigate seamlessly between SAP Cloud ALM and the test automation tool for SAP S/4 HANA Cloud, adjust the automated test cases, release them for testing and execute them directly in SAP Cloud ALM.</div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-53851596759000317212024-02-14T13:39:00.001+05:302024-02-14T13:39:03.662+05:30BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA<div><b>Introduction:</b> In today's digital world, businesses are looking for ways to streamline their processes and enhance their customer experience. One way to achieve this is through the integration of different systems. In this blog post, we will explore how to integrate SAP C4C and S/4 HANA using BTP destinations and SAP Build apps.</div><div><br /></div><div>To integrate SAP C4C and S/4 HANA, we can use BTP (<a href="https://www.hanaexam.com/p/certifications.html">Business Technology Platform</a>) destinations and SAP Build Apps.<span><a name='more'></a></span></div><div><br /></div><div><b>BTP destinations</b> are endpoints that define how to connect to a remote system or service. BTP Destinations are typically used in cloud-based scenarios where different cloud services need to communicate with each other securely. They provide a way to define the connection details for target systems such as the endpoint URL, authentication credentials, and other settings. BTP Destinations can be created and maintained using the SAP Cloud Platform cockpit or SAP Cloud SDK. They can be used in various scenarios, such as connecting to remote data sources, invoking external web services, or sending notifications to third-party systems.</div><div><br /></div><div><b>SAP Build Apps</b> is a visual programming environment where citizen and professional developers can build enterprise-ready custom software without writing any code. It makes it easier for users to create engaging and functional SAP Fiori apps without the need for extensive technical expertise or coding knowledge. It provides a streamlined and collaborative design process that helps organizations deliver high-quality apps faster and more efficiently.</div><div><br /></div><div>You can sign up for a free trial of SAP Build to get hands-on experience with the tool. The trial account provides access to all the features and functionalities of SAP Build, allowing you to create and prototype your own SAP Fiori apps.</div><div><br /></div><div>Let us quickly get into our use case.</div><div><br /></div><div><b>Use Case:</b> An SAP Build App is embedded into the Agent desktop screen in C4C tenant where you will be able to view the S/4HANA transactions like Sales Orders, Customer Returns, Outbound Deliveries etc based on the Customer like below.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg38JM52EQsCTFdDYKDef4Ke9GULwHB6djw5QGbVUHXG17sN03PdXJBfBSLZK3WC_oBY0CQfTMh73Ikv75BXy0AFW8doCNvEoosuaIKqeNXueK_JVhSzme1-JPbmND741BXQ5EmCVffalYWh1pV-z-kNPN_Yi-63Azrt_MTJYSwioJy8krT4yNhidVjJRgC/s1920/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="942" data-original-width="1920" height="196" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg38JM52EQsCTFdDYKDef4Ke9GULwHB6djw5QGbVUHXG17sN03PdXJBfBSLZK3WC_oBY0CQfTMh73Ikv75BXy0AFW8doCNvEoosuaIKqeNXueK_JVhSzme1-JPbmND741BXQ5EmCVffalYWh1pV-z-kNPN_Yi-63Azrt_MTJYSwioJy8krT4yNhidVjJRgC/w400-h196/1.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Let’s take an example of integrating Sales orders from S/4HANA in to C4C screen.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Step 1: Set up the BTP Destination in the BTP Sub account.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">You can follow below steps:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Open the SAP Cloud Platform Cockpit and log in to your BTP sub-account.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Navigate to the "Destinations" page under the "Connectivity" tab.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjo0BSv-7qJwwxRQK_eieO5CAUQ7MLjISEhHygSmEfuHKaI2KWF7JYOAJyvxM4ivxsVy7lriJXvpB_IVhgrLbbnRi5aHGaib56EdhXbeidPyXNV4pNdOr8wMJPT1s0Vy81C2ztRmwinCxvRIu_ZJbY7QTJl6gVlDNwt0ts9IvkVw5NvA7szVUrD0As6YyRA/s1919/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="934" data-original-width="1919" height="195" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjo0BSv-7qJwwxRQK_eieO5CAUQ7MLjISEhHygSmEfuHKaI2KWF7JYOAJyvxM4ivxsVy7lriJXvpB_IVhgrLbbnRi5aHGaib56EdhXbeidPyXNV4pNdOr8wMJPT1s0Vy81C2ztRmwinCxvRIu_ZJbY7QTJl6gVlDNwt0ts9IvkVw5NvA7szVUrD0As6YyRA/w400-h195/2.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">◉ Click on the "New Destination" button to create a new destination.</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiwnLlR695wnnvyzFDQ8OOlD3cmO0dqpqouy34stk8VdS6ubzcFwAxbjUgDNRk1RGTmhlslj00HaGGCOTW66CBB6L1xGBtXDv20OV-Vgkb_ym9-1q7ZRhH7mWA-DyliZ3Mms0L-lMvAci1JhPtO7wu4jODu9Rj3Hk1mYGTI64f4YO_b8zKSsPGxk5wMw2lT/s903/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="439" data-original-width="903" height="195" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiwnLlR695wnnvyzFDQ8OOlD3cmO0dqpqouy34stk8VdS6ubzcFwAxbjUgDNRk1RGTmhlslj00HaGGCOTW66CBB6L1xGBtXDv20OV-Vgkb_ym9-1q7ZRhH7mWA-DyliZ3Mms0L-lMvAci1JhPtO7wu4jODu9Rj3Hk1mYGTI64f4YO_b8zKSsPGxk5wMw2lT/w400-h195/3.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ In the "Destination Name" field, enter a name for your destination.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ In the "Type" field, select "HTTP" as the destination type.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ In the "Description" field, enter a brief description of your destination.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ In the "URL" field, enter the URL of the S/4HANA Sales order API (https://myXXXXXX.s4hana.ondemand.com/sap/opu/odata/sap/API_SALES_ORDER_SRV)that you want to integrate.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ In the "Proxy Type" field, select "Internet" as the proxy type.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ In the "Authentication" section, select "BasicAuthentication" as the authentication method.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Enter the username and password credentials for the API service.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In the "Additional Properties" section, add the following key-value pairs:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> ◉ "WebIDEEnabled": "true"</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> ◉ “HTML5.DynamicDestination” :"true"</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> ◉ "AppgyverEnabled" :"true"</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2gcNVlwjd_NAPuFkUrNK8S1Zubg24k1n7NZHwKjM36yHwlzsfVR211PjEdS-3X4Qqyo3E0KzqjssQdSaYBP48B9KimPo4URFl8nE97j4x4KXQ25kGhG_OpNGF2unNRQVjC2WHtFA8JIkNzd4KFJVtGr9nXV2cFvlwcuhnza2-TK8tqBY9idqgcfq_-hP9/s1893/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="927" data-original-width="1893" height="196" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2gcNVlwjd_NAPuFkUrNK8S1Zubg24k1n7NZHwKjM36yHwlzsfVR211PjEdS-3X4Qqyo3E0KzqjssQdSaYBP48B9KimPo4URFl8nE97j4x4KXQ25kGhG_OpNGF2unNRQVjC2WHtFA8JIkNzd4KFJVtGr9nXV2cFvlwcuhnza2-TK8tqBY9idqgcfq_-hP9/w400-h196/4.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ These properties will allow you to access the API service using the SAP Web IDE.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Click on the "Save" button to save your destination.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Once you set up, you can click Check Connection to see if the Connection is Successful.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjY0NB1fSs1ICVwTbdelPqbhOOM8TGT3g8rw6Tq7-L993-oKHMYSsC6K86ey5q-CTmp-akuGZ0uvGIrO47kdpKUR9-LjpY3V3tl2_6aQW2RQYr4J_S6G21gSQc3E12Y7KpfuruuxuLfTH0PISkFJoHg0KNgu7I7A1l44DtOCeOGHI10gEM6nHJ1ySahqRxq/s903/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="436" data-original-width="903" height="194" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjY0NB1fSs1ICVwTbdelPqbhOOM8TGT3g8rw6Tq7-L993-oKHMYSsC6K86ey5q-CTmp-akuGZ0uvGIrO47kdpKUR9-LjpY3V3tl2_6aQW2RQYr4J_S6G21gSQc3E12Y7KpfuruuxuLfTH0PISkFJoHg0KNgu7I7A1l44DtOCeOGHI10gEM6nHJ1ySahqRxq/w400-h194/5.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Step 2: Create an Appgyver app with basic screens to display the values from the S/4HANA. Add a list view to the page to display the results and a page parameter to read the Account id and Query the Sales orders based on Account ID. Here are some steps to follow.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Create a new page in Appgyver by selecting "Create New Page" from the Pages menu.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Name the page and select a layout that will suit your needs.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEggrwhowDN-E0Lf0PXTuAwRxHqvUT2Cj-kBHTFa7yGh500zpeIZn1S_DQLPIrq6r6w7oCur6czuSKsKEQm-e9DmAHQY4twltxjWuVPdZm-WACDJg9kk3b3_VsEDHKnwlhjyptLvDXbZz8Oy0aE99fDXyGH6_fOBBN_hyphenhyphenMglEVyMilNT5QFzOwSP_jqWHqea/s903/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="438" data-original-width="903" height="194" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEggrwhowDN-E0Lf0PXTuAwRxHqvUT2Cj-kBHTFa7yGh500zpeIZn1S_DQLPIrq6r6w7oCur6czuSKsKEQm-e9DmAHQY4twltxjWuVPdZm-WACDJg9kk3b3_VsEDHKnwlhjyptLvDXbZz8Oy0aE99fDXyGH6_fOBBN_hyphenhyphenMglEVyMilNT5QFzOwSP_jqWHqea/w400-h194/6.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Add a container component to the page to hold the sales order query results.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwoQgNMZYqdRxruBa6v_hjI7AMc2mYQlUg_L81sVKFvSVSJ-h0HqAkLuhrCHiyNaEJHMclScZ42JZ6mU89l6r8fX2vaRoKSI1eb6yL-RaYyQWC9Eqgxtc-Ha4_eA6ih1l15i2L0qFSWh5xLCyP8UDtx52-gKMnhxHzdiVtjGmnGp3I8KDceLxpgQrVy1ul/s903/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="434" data-original-width="903" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwoQgNMZYqdRxruBa6v_hjI7AMc2mYQlUg_L81sVKFvSVSJ-h0HqAkLuhrCHiyNaEJHMclScZ42JZ6mU89l6r8fX2vaRoKSI1eb6yL-RaYyQWC9Eqgxtc-Ha4_eA6ih1l15i2L0qFSWh5xLCyP8UDtx52-gKMnhxHzdiVtjGmnGp3I8KDceLxpgQrVy1ul/w400-h193/7.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ You can create a page Parameter to read the Account id from the C4C Screen and pass that to S/4HANA system to query sales orders based on Account.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Next we have to enable BTP Authentication. click on the AUTH tab -> Enable Authentication</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXJ0DHq66DKV8sNvyOsP91001lZEbPI7nJl3goGCEmmUlA6EDpwVzKhQ0gn-D90mmr2zODCaC8pRmooo92uHOcz_IbL2WgUBrtAjkoETSQWkYeJ7jWLQGkKlrsorUS5MMCMpPQaaGtpNul7VuNgea25ylyL4nfnclHj2bBTwxltArzt4M9DnCakrKnFF_O/s1926/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="927" data-original-width="1926" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXJ0DHq66DKV8sNvyOsP91001lZEbPI7nJl3goGCEmmUlA6EDpwVzKhQ0gn-D90mmr2zODCaC8pRmooo92uHOcz_IbL2WgUBrtAjkoETSQWkYeJ7jWLQGkKlrsorUS5MMCMpPQaaGtpNul7VuNgea25ylyL4nfnclHj2bBTwxltArzt4M9DnCakrKnFF_O/w400-h193/8.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGhiCiM1LE3ghSwp5k23ClwAxXJ7I8Fi45KnKOLAvJzwGNTBsBGSZmBY6AN7CTFLP6h2s_TS2BgtC2972NJcUMiyJs2tTjTPPD3YzpxTiZN3G9K1GIppRORD0zITcIMd8R3leX9PRXZ1fCA7X0MVMsx8nZ5RA7fxFeg3dzYAIgTz7iEm4J1VzKcf0Q_EC2/s2001/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="928" data-original-width="2001" height="185" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGhiCiM1LE3ghSwp5k23ClwAxXJ7I8Fi45KnKOLAvJzwGNTBsBGSZmBY6AN7CTFLP6h2s_TS2BgtC2972NJcUMiyJs2tTjTPPD3YzpxTiZN3G9K1GIppRORD0zITcIMd8R3leX9PRXZ1fCA7X0MVMsx8nZ5RA7fxFeg3dzYAIgTz7iEm4J1VzKcf0Q_EC2/w400-h185/9.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEieq4mE1NFKHW8wSqzUbdOy2l6OHz-662HmbkhulILjVS_WS8tgZzrAQXYo9q1JCal4JxHhL7RRoHtQ_ZVf4VtmL1IjsEf5Bkb_J5uH7EqBS2vZcaJM6uRF7BrZw1CKhUt9Ntp5Q2YyPAoK5VXDt8anqPCvSWD_YXBWuey5wTeZ55XYEREF01UR9f9y4Dg_/s1890/10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="941" data-original-width="1890" height="199" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEieq4mE1NFKHW8wSqzUbdOy2l6OHz-662HmbkhulILjVS_WS8tgZzrAQXYo9q1JCal4JxHhL7RRoHtQ_ZVf4VtmL1IjsEf5Bkb_J5uH7EqBS2vZcaJM6uRF7BrZw1CKhUt9Ntp5Q2YyPAoK5VXDt8anqPCvSWD_YXBWuey5wTeZ55XYEREF01UR9f9y4Dg_/w400-h199/10.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Add the BTP destination created in the Previous step by clicking on the Data tab -> Add integration.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhmC4-uUvHsPr7efBaDTdgdPpZC-D54XIgjNrVlz2fkKx_3TQoeofadKWQPWbCWk4sW7OW_kJTkK5lksHrcZqG8J5h6KSdAPpxFCR6eG-FUfc1iNy61t1hUUptRoGcpPS790HtnYPjFG9LdPWR-cCbuy7YFu8rKDW3IqZ3nnaa2HogkI32RfW7BJuQH9dpj/s1917/11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="925" data-original-width="1917" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhmC4-uUvHsPr7efBaDTdgdPpZC-D54XIgjNrVlz2fkKx_3TQoeofadKWQPWbCWk4sW7OW_kJTkK5lksHrcZqG8J5h6KSdAPpxFCR6eG-FUfc1iNy61t1hUUptRoGcpPS790HtnYPjFG9LdPWR-cCbuy7YFu8rKDW3IqZ3nnaa2HogkI32RfW7BJuQH9dpj/w400-h193/11.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnrhSKYdn-hTJvTy1lFLmMmp5F-UK7zoSWKLePZE6Jo7KIpUeN9-DoyjCYLK9Dyha2qqdwZjm3weGvjKPl2ZimHDYQS15cQlwq1T98VpxRgD5GnSfCyOsLPk0PHONbKg9VyfQtYBLkCuRhEya1LxLLLsd3eX8yGYaH6DSdJ-jpHuYvjWk2Geius72qf8pk/s1913/12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="929" data-original-width="1913" height="194" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnrhSKYdn-hTJvTy1lFLmMmp5F-UK7zoSWKLePZE6Jo7KIpUeN9-DoyjCYLK9Dyha2qqdwZjm3weGvjKPl2ZimHDYQS15cQlwq1T98VpxRgD5GnSfCyOsLPk0PHONbKg9VyfQtYBLkCuRhEya1LxLLLsd3eX8yGYaH6DSdJ-jpHuYvjWk2Geius72qf8pk/w400-h194/12.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Then select the BTP Destination you have created.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnOdMgB3W1y9AGfIw3OxauAqDXkDWlUktLsHEhulQJX_v1mCr4rzjjCbv1Q6vk_djQveJDk1DTEPxDszvc_yeIWul2XTIvf449vfd-G85qyDNR70TacRwgNxjZ50b_PMzphxlaLCyVy4_lJaJxLnFnKGXvtlfwtbfqdtUg5qv-852j_99Eam-kOMBDQrex/s903/13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="433" data-original-width="903" height="191" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnOdMgB3W1y9AGfIw3OxauAqDXkDWlUktLsHEhulQJX_v1mCr4rzjjCbv1Q6vk_djQveJDk1DTEPxDszvc_yeIWul2XTIvf449vfd-G85qyDNR70TacRwgNxjZ50b_PMzphxlaLCyVy4_lJaJxLnFnKGXvtlfwtbfqdtUg5qv-852j_99Eam-kOMBDQrex/w400-h191/13.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Then do install Integration and enable Data entity and save it, then that Data resource will be added to your Project.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDxOxl6UslKg8VS6s6o41Dg-PyrKAbWBYwf87Wz2Kla02eoUptIkWk2nYEAveM86TwHyyFKy-O-G948edKintA87_nux-FZSabutNMXYffwGkbwboNF5_1SG-AHLFmHqcvMUlrXIqvxeqgjr8nl4NSgtDyuMULOIotaNo5jntFqgJNVBGorRXkDRag7QgF/s1919/14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="925" data-original-width="1919" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDxOxl6UslKg8VS6s6o41Dg-PyrKAbWBYwf87Wz2Kla02eoUptIkWk2nYEAveM86TwHyyFKy-O-G948edKintA87_nux-FZSabutNMXYffwGkbwboNF5_1SG-AHLFmHqcvMUlrXIqvxeqgjr8nl4NSgtDyuMULOIotaNo5jntFqgJNVBGorRXkDRag7QgF/w400-h193/14.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_FbEjDxnF5CZGkXxf7I6mwZYfvIxH3URIvAdo5v7Tzbq9bSXnwB1-ngs8vjMuVkwQDMfgOsJQ9zuCwKGAfoYh5Qrgd-O1CCOZ0QDuXf_SQlXoPqHH_xDwzAETuveW53q_n9eQWB6KZTnWnFl0_1PUFswAf72OMo3ISq7Dekmij9QndEnJ8B7R2UjU9VGI/s903/15.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="435" data-original-width="903" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_FbEjDxnF5CZGkXxf7I6mwZYfvIxH3URIvAdo5v7Tzbq9bSXnwB1-ngs8vjMuVkwQDMfgOsJQ9zuCwKGAfoYh5Qrgd-O1CCOZ0QDuXf_SQlXoPqHH_xDwzAETuveW53q_n9eQWB6KZTnWnFl0_1PUFswAf72OMo3ISq7Dekmij9QndEnJ8B7R2UjU9VGI/w400-h193/15.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Add a data variable to the page to store the query results. You can select the Sales Order Data resource you have added above.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiv_fUKMUvRAv1KPRwYgs49B1RMor81CJs6_Zn-KYNSabx0h14X_iDa7qV2keCz6XOPcDpQnksCinWylVCwFWHsQp95R34BmhymroRegrOP4AIFtUuuB32FWaUHekXtJRkICYwhhnpujEVn3UAaLcVoKpTtvfNXC8qXz2XPJ3pRcTBc-4QctYOeQUWc-MVc/s903/16.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="430" data-original-width="903" height="190" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiv_fUKMUvRAv1KPRwYgs49B1RMor81CJs6_Zn-KYNSabx0h14X_iDa7qV2keCz6XOPcDpQnksCinWylVCwFWHsQp95R34BmhymroRegrOP4AIFtUuuB32FWaUHekXtJRkICYwhhnpujEVn3UAaLcVoKpTtvfNXC8qXz2XPJ3pRcTBc-4QctYOeQUWc-MVc/w400-h190/16.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Bind the container component to the data variable using the "Repeat with" binding option. This will cause the container to display a list of items based on the data returned by the query.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkl71SVhGyJVt3a1ASIY-L41ExeLzQ8d5HOnaNaMqbviEROSsyGi6J62osVUJKj3tIATdA15Cha-_g2lUoSR2bbWWleHygC5Wo7Wfl7big1XYgxpGC8pg8igWTinqsZV2XRB7GkPW_DNgn1jKZTDpL_EIijlWKRwW_aywDeo4ZfBtOT3XsSRaCBKP7Z69b/s1910/17.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="928" data-original-width="1910" height="194" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkl71SVhGyJVt3a1ASIY-L41ExeLzQ8d5HOnaNaMqbviEROSsyGi6J62osVUJKj3tIATdA15Cha-_g2lUoSR2bbWWleHygC5Wo7Wfl7big1XYgxpGC8pg8igWTinqsZV2XRB7GkPW_DNgn1jKZTDpL_EIijlWKRwW_aywDeo4ZfBtOT3XsSRaCBKP7Z69b/w400-h194/17.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiFCV639ql48QJD3EJ1xkr7xi0wZ0Qlv8P19e0B0cQ8LUOlTEXvquhihpSURsW9_GuRwqLnb_EkrRvKDghk4ZqeGNxbybnPDV1IewFHuDx78I3z5L69N04cNgpxAKGWUZK3IKy5r5opwNLayOJ2vPzkRpZuTSU3_hO8e8H_MI3sOq5ULyu5UbQkjrWUEZfV/s1919/18.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="869" data-original-width="1919" height="181" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiFCV639ql48QJD3EJ1xkr7xi0wZ0Qlv8P19e0B0cQ8LUOlTEXvquhihpSURsW9_GuRwqLnb_EkrRvKDghk4ZqeGNxbybnPDV1IewFHuDx78I3z5L69N04cNgpxAKGWUZK3IKy5r5opwNLayOJ2vPzkRpZuTSU3_hO8e8H_MI3sOq5ULyu5UbQkjrWUEZfV/w400-h181/18.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ Customize the appearance of the container and its child components (e.g., text elements, buttons, etc.) to display the sales order data in a clear and intuitive way.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Test the page by previewing it in the Appgyver preview app or by deploying it to a test environment. If necessary, adjust the page and data variables until the desired results are achieved.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Deploy the app using then Open Build Service and add the Deployed URL as a Mash up in C4C Agent desktop Screen.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQ3Y6nBrV9B8h4DujwDrvg1o5xSrjpTIC9XNCxGQod8hJkAlbSQJF67npSyyd95yhvzvyZnFI2M_HtR1_zUYe1f7Gm7fZi3rRSYSEt9K2_hdlAhHr_yNS5GUgAnhVV1hSmthCYlYNbJb5hem3Sr1e9-DBA3gaiN4Xg3yrul04o9xpL7C48LeJaLWfJHkDA/s903/19.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="436" data-original-width="903" height="194" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQ3Y6nBrV9B8h4DujwDrvg1o5xSrjpTIC9XNCxGQod8hJkAlbSQJF67npSyyd95yhvzvyZnFI2M_HtR1_zUYe1f7Gm7fZi3rRSYSEt9K2_hdlAhHr_yNS5GUgAnhVV1hSmthCYlYNbJb5hem3Sr1e9-DBA3gaiN4Xg3yrul04o9xpL7C48LeJaLWfJHkDA/w400-h194/19.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ You can configure the Mash up in Agent Desktop as a tab or in the Account Screen as a tab by passing the Account ID.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhI1fqU6rh81WlFAfnpXUELMsA_FQm4rc9HzvfrVyleG2wrLvl7wK5OQuvtwwZ-mmzt7-vmx04sEs2-gOx63zyWREfWCFc-QLzz2onAd7J9CanA_UJomX1653IqyQ_qwDw7q6Fy1s5xBA438UWOYOWgXbahVEjsuA8zD1zQtIDOnU-y6S6UWWt6T24NKB6z/s903/20.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="439" data-original-width="903" height="195" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhI1fqU6rh81WlFAfnpXUELMsA_FQm4rc9HzvfrVyleG2wrLvl7wK5OQuvtwwZ-mmzt7-vmx04sEs2-gOx63zyWREfWCFc-QLzz2onAd7J9CanA_UJomX1653IqyQ_qwDw7q6Fy1s5xBA438UWOYOWgXbahVEjsuA8zD1zQtIDOnU-y6S6UWWt6T24NKB6z/w400-h195/20.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">◉ You can repeat the same steps to get any other S/4HANA transactional data like Customer returns, Outbound Deliveries, Credit Memo Requests etc.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGuEAws0U0fmztEzCDeBAezaFlVIQlAqUtR8kW2asprchXwzT70NdYWrSB6S2GaTZLvA10jwjObucakYetERFSYMNs_d_ZTJrKW8MoWP8POF83XnrNASxgGm175wTjZxKBfcjXwkTi_hGRHr_IOdcWfBxtMMflztszqfzqVsYsvcPAbxFyZuCNFOQyC1Fo/s1920/21.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" border="0" data-original-height="942" data-original-width="1920" height="196" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGuEAws0U0fmztEzCDeBAezaFlVIQlAqUtR8kW2asprchXwzT70NdYWrSB6S2GaTZLvA10jwjObucakYetERFSYMNs_d_ZTJrKW8MoWP8POF83XnrNASxgGm175wTjZxKBfcjXwkTi_hGRHr_IOdcWfBxtMMflztszqfzqVsYsvcPAbxFyZuCNFOQyC1Fo/w400-h196/21.png" title="BTP Destinations and SAP Build Apps to integrate SAP C4C & S/4HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">In conclusion, integrating SAP C4C and S/4 HANA using BTP destinations and SAP Build apps can provide businesses with a powerful solution to streamline their processes and improve their customer experience. By using BTP destinations to connect the two systems and SAP Build apps to create custom applications, businesses can read real-time data from S/4 HANA and display it in SAP C4C, allowing for better decision-making and enhanced efficiency.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Once you get more familiar with the SAP Build apps then it will become easier to build screens and play around and try different integration scenarios. Hope this blog may help you in your use cases.</div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-78607412756044487552024-02-07T14:18:00.000+05:302024-02-07T14:18:00.168+05:30Optimizing HANA Cloud: A Practical Exploration of Replication, Latency, and Availability Zones<h3 style="text-align: left;"><b>Introduction</b></h3><div><br /></div><div>In general crafting my blog posts, I usually avoid lengthy theoretical discussions. I find more value in exploring real-world scenarios, practical applications, and best practices. However, for this particular post, I'll make an exception. I'd like to start by briefly delving into some theoretical concepts you may already be acquainted with</div><div><br /></div><div>—Replica, Latency, and Availability Zones in <b><a href="https://www.hanaexam.com/p/chanatec19.html">Cloud Databases</a></b>. Allow me to provide a concise overview, accompanied by practical insights and optimization strategies. Together, we'll lay the groundwork for a resilient and high-performing system in HANA Cloud<span><a name='more'></a></span></div><div><br /></div><div>In the dynamic world of HANA Cloud, ensuring a robust and high-performing system is key for seamless operations. This blog post dives into two crucial aspects: understanding replication types and the impact of latency, as well as the significance of availability zones in BTP HANA Cloud. By strategically placing replicas and optimizing latency, users can design a resilient system that stands strong even in the face of potential data center failures. Additionally, exploring availability zones becomes essential for deploying applications with high availability and fault tolerance, providing continuous service availability, compliance with regulations, and an overall boost in system resilience. Let's embark on a journey to unravel the intricacies of these fundamental elements that shape the reliability of your HANA Cloud experience.</div><div><br /></div><h3 style="text-align: left;"><b>Replica</b></h3><div><br /></div><div>In the context of databases and data management, a replica is a copy of a database or a subset of its data. Replicas are often used to enhance performance, provide fault tolerance, and support distributed computing scenarios. </div><div><br /></div><div>In Database Replication involves creating and maintaining copies of data across different locations or servers. In HANA Cloud, replication is crucial for achieving high availability and fault tolerance by ensuring that data is redundantly stored.In the context of HANA Cloud BTP, having replicas can contribute to better data availability and performance by allowing applications to read from multiple copies of the data concurrently. It's essential for scenarios where high availability and scalability are crucial.</div><div><br /></div><div>Types of Replication:</div><div><br /></div><div><b>1. Synchronous Replication:</b></div><div><br /></div><div>◉ In this type, changes to the data are mirrored to replicas almost instantaneously.</div><div>◉ Ensures high data consistency but might introduce latency in write operations.</div><div><br /></div><div><b>2. Asynchronous Replication:</b></div><div><br /></div><div>◉ Changes to the data are replicated with a slight delay, offering more flexibility in terms of latency.</div><div>◉ Provides a trade-off between consistency and performance.</div><div><b><br /></b></div><h3 style="text-align: left;"><b>Latency</b></h3><div><br /></div><div>Latency, in the context of replica location, refers to the time delay or lag introduced by the physical distance between different replicas of a database or system.</div><div><br /></div><div>Latency is the time it takes for data changes made in one replica to be propagated or synchronized to other replicas in the distributed system.</div><div><br /></div><div>For example, if you have a primary database and one or more replicas located in different geographical regions, the latency would be the time it takes for changes made in the primary database to be reflected in the replicas. The physical distance between these replicas can result in delays in data synchronization.</div><div><br /></div><div>The location of replicas in a distributed system can impact latency, which is the time delay between the initiation and completion of a data transfer or operation. When replicas are geographically dispersed, there may be latency introduced due to the physical distance between them.</div><div><br /></div><div>If replicas are located far apart, it could result in increased latency for data synchronization and communication between the replicas. This latency can affect the speed at which data changes are propagated across replicas, potentially impacting the overall performance of applications relying on these replicas.</div><div><br /></div><div>In scenarios where low latency is critical, it's advisable to consider the geographical distribution of replicas carefully. Placing replicas closer to each other or strategically selecting their locations can help minimize latency and ensure better responsiveness in distributed systems.</div><div><br /></div><div>Latency refers to the delay or time lapse between the initiation of an action and its completion. In the context of replication, it signifies the time taken for changes in data at the source to be reflected in the replicas.</div><div><br /></div><div><b>Impact of Latency on Performance:</b></div><div><br /></div><div><b>◉ Increased Latency:</b> If replicas are located far apart, it could result in increased latency for data synchronization and communication between replicas.</div><div><b>◉ Performance Impact:</b> Latency can impact the speed at which data changes are propagated across replicas, potentially affecting the overall performance of applications relying on these replicas.</div><div><br /></div><div>Optimizing Replica Placement for Low Latency:</div><div><br /></div><div><b>◉ Geographical Distribution: </b>Carefully consider the geographical distribution of replicas.</div><div><b>◉ Proximity:</b> Placing replicas closer to each other helps minimize latency.</div><div><b>◉ Strategic Selection:</b> Strategically selecting replica locations can enhance responsiveness in distributed systems.</div><div><br /></div><div><b>Best Practices for Performance:</b></div><div><br /></div><div><b>◉ Same Availability Zone:</b> For optimal performance, it's advisable to place both the source and replica in the same availability zone.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMJOeVsebsKkRoyvwaWDqa6958z1kHHXy_4mRiYUm07WdCdXejbtUNCb6HAWLOReRznqnEgvyfrYXwp8abPUKxsZWRmvVokpBnSeHZOTAaU60xwOp-WFK85H7-0CI-unzqkTAn0pPtANvEz2zafZ7Ce6QXcrgRiSPBTRk6qYz5M6e_aZL8NhqD0QgPaz0x/s1919/1.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Optimizing HANA Cloud: A Practical Exploration of Replication, Latency, and Availability Zones" border="0" data-original-height="482" data-original-width="1919" height="100" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMJOeVsebsKkRoyvwaWDqa6958z1kHHXy_4mRiYUm07WdCdXejbtUNCb6HAWLOReRznqnEgvyfrYXwp8abPUKxsZWRmvVokpBnSeHZOTAaU60xwOp-WFK85H7-0CI-unzqkTAn0pPtANvEz2zafZ7Ce6QXcrgRiSPBTRk6qYz5M6e_aZL8NhqD0QgPaz0x/w400-h100/1.jpg" title="Optimizing HANA Cloud: A Practical Exploration of Replication, Latency, and Availability Zones" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">You may consider adding a second replica, but it should be in asynchronous mode and located in a different data center than the source.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjLIUy4zGzAtcJZSulLPA-IntymrP2hDzmM45cGpjMjjow0O9YAJUJZYkXqykB6dAdH9wJtZ86MYXUcVXQZ74zknNhSgBYqeS1A2biO1EEIJYk_Ze1AeejnmbvtD0QxWZxRuex-ffeisve_M1v4k4TYYBOTDaBOf996hzTwXYWNGvVlSWlBNK8Z7iUuI2WX/s1135/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Optimizing HANA Cloud: A Practical Exploration of Replication, Latency, and Availability Zones" border="0" data-original-height="234" data-original-width="1135" height="83" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjLIUy4zGzAtcJZSulLPA-IntymrP2hDzmM45cGpjMjjow0O9YAJUJZYkXqykB6dAdH9wJtZ86MYXUcVXQZ74zknNhSgBYqeS1A2biO1EEIJYk_Ze1AeejnmbvtD0QxWZxRuex-ffeisve_M1v4k4TYYBOTDaBOf996hzTwXYWNGvVlSWlBNK8Z7iUuI2WX/w400-h83/2.png" title="Optimizing HANA Cloud: A Practical Exploration of Replication, Latency, and Availability Zones" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>◉ Reduced Latency:</b> This configuration minimizes latency, ensuring faster data synchronization and better overall system responsiveness.</div><div class="separator" style="clear: both;"><b><br /></b></div><h3 style="clear: both; text-align: left;"><b>Availability Zones</b></h3></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEikeViUn-ItSJ_i4_AHOy68LXGPovCf_yUFjljuTUvSxwRIvvn43nTY6NSsM-iKu8aoS_zKgtf8c740zNcnv9RH0W-V4_NpjR9Ztg4lnDoPZB5LhCIBr_SSojZiZZS2yWfQAAFIVJvKmwYlTtDb__m520aMStG9c8ljkK2oEDUXWf0FNutztt0hic3Yh5Cq/s294/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Optimizing HANA Cloud: A Practical Exploration of Replication, Latency, and Availability Zones" border="0" data-original-height="215" data-original-width="294" height="293" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEikeViUn-ItSJ_i4_AHOy68LXGPovCf_yUFjljuTUvSxwRIvvn43nTY6NSsM-iKu8aoS_zKgtf8c740zNcnv9RH0W-V4_NpjR9Ztg4lnDoPZB5LhCIBr_SSojZiZZS2yWfQAAFIVJvKmwYlTtDb__m520aMStG9c8ljkK2oEDUXWf0FNutztt0hic3Yh5Cq/w400-h293/3.png" title="Optimizing HANA Cloud: A Practical Exploration of Replication, Latency, and Availability Zones" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Availability Zones (AZs) are distinct locations within a geographical region, each comprising one or more data centers i.e logically and physically separated data center facilities within a region that are designed to be independent of each other. The purpose of availability zones is to provide redundancy, fault tolerance, and high availability for applications and services hosted in a cloud environment.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Examples of Availability Zones in BTP HANA Cloud:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>1. Europe (Frankfurt):</b> Serving customers in the European region, this availability zone is located in Frankfurt, Germany. </div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Here are Virtual /Physical Availability Zones : eu-central-1a eu-central-1b eu-central-1c </div><div class="separator" style="clear: both;"><b>2. Americas (Ashburn):</b> Located in Ashburn, Virginia, USA, this availability zone caters to customers in the Americas region. </div><div class="separator" style="clear: both;">Here are Virtual /Physical Availability Zones : na-us-2a na-us-2b </div><div class="separator" style="clear: both;"><b>3. Asia/Pacific (Mumbai):</b> Serving the Asia-Pacific region, this availability zone is situated in Mumbai, </div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Here are Virtual /Physical Availability Zones : asia-south1-a</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">For example, for your reference : Regions and API Endpoints Available for the BTP Cloud Foundry Environment</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Please note that as an HANA Cloud customer in BTP, you don't have choices but to select the availability zone from the dropdown box listed when you create HANA Cloud instances in your BTP Account, based on the region.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>How do Availability Zones Work?</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>Each availability zone consists of multiple interconnected data centers to ensure redundancy and resiliency.</li><li>In case of an issue or outage in one data center, the workload can automatically failover to another data center within the same availability zone, minimizing downtime.</li><li>Multiple availability zones within a region allow customers to deploy applications across different zones for higher availability and resilience.</li></ul></div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>Connecting Availability Zones:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>Availability zones within a region are connected through low-latency links to facilitate seamless communication.</li><li>This interconnected setup ensures that users experience fast, reliable access to cloud services and resources.</li></ul></div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>Benefits of Availability Zones in BTP HANA Cloud:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>Compliance: Helps comply with regulatory and data residency requirements by storing data within specific geographic locations.</li><li>Resilience: Enhances system resilience by isolating failures within an availability zone and offering low-latency network connectivity to other zones.</li></ul></div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>Increasing HANA Cloud Availability</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">SAP HANA Cloud offers optional features to increase the availability and resilience of your database instances.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrkegQFkINggUpv2aVf0dGNa-VKDG0jk4BkNk3u8Uuz7tC7uoJbU2qT0Ct5fnaR_954S5V9wE-coURZyxvWIagvxCGIxERhrBi_Nq32U3cOuWcPrJdZp6OrcHUjUwIUgc8CxV6xt7-GuEAz31QpVbHyGvjl-yorJ07NxJZx5Gdf10Aq06M17tquH-phaEF/s993/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Optimizing HANA Cloud: A Practical Exploration of Replication, Latency, and Availability Zones" border="0" data-original-height="859" data-original-width="993" height="346" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrkegQFkINggUpv2aVf0dGNa-VKDG0jk4BkNk3u8Uuz7tC7uoJbU2qT0Ct5fnaR_954S5V9wE-coURZyxvWIagvxCGIxERhrBi_Nq32U3cOuWcPrJdZp6OrcHUjUwIUgc8CxV6xt7-GuEAz31QpVbHyGvjl-yorJ07NxJZx5Gdf10Aq06M17tquH-phaEF/w400-h346/4.png" title="Optimizing HANA Cloud: A Practical Exploration of Replication, Latency, and Availability Zones" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><b>Conclusion:</b> Understanding availability zones in BTP HANA Cloud is essential for deploying applications with high availability and fault tolerance. By leveraging multiple availability zones, users can ensure continuous service availability, comply with regulations, and enhance the overall resilience of their systems.Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-76561671090157472832024-02-02T13:07:00.002+05:302024-02-02T13:07:22.251+05:30Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)<h3 style="text-align: left;"><b>Requirement:</b></h3><div><br /></div><div>Establish trusted relationship/connectivity between source systems at client side to Azure APIM and from Azure APIM to S4HANA system via CI and cloud connector using short lived certificate i.e., principal propagation.</div><div><br /></div><div>More Info: <b><a href="https://www.hanaexam.com/p/chanatec19.html">C_HANATEC_19 Key Points</a></b></div><div><br /></div><h3 style="text-align: left;"><b>Overview</b></h3><div><br /></div><div>Principal propagation means the ability to forward the user context of a message unchanged from the sender to the receiver. It enables authentication of a message in the receiver system with the same user that issued the message in the corresponding sender system. Thus, the receiver application is virtually part of the sender application, and the permissions and audit functions of the receiver application can be applied to the original user of the sender application.<span><a name='more'></a></span></div><div><br /></div><div>Source system is authenticated at Azure APIM via OAuth token generated by the IDP. APIM will pass the source identity as header in the API call. Source identity is mapped to a connectivity service user in S4HANA. SAP CI, SAP connectivity service and SCC validate/authenticate the source identity and generate a short-lived certificate to access S4HANA API. Hence only the authorised system is allowed to access the S4HANA API.</div><div><br /></div><div>This blog illustrates how to apply the principal propagation to validate source technical system in S4HANA using SAP BTP CI and SAP BTP Connectivity service.</div><div><br /></div><div><h3 style="text-align: left;"><b>Solution:</b></h3><div><br /></div><div>The approach will be divided into 2 sections:</div><div><br /></div><div>1. BTP Configuration</div><div>2. Cloud Connector and S4HANA Configuration</div></div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEieH0c-TeA8fpOfpmZcpWOumKJcGyBW0bqqwSmwvsC63YghlgJMNojlzckRf_KT9pe6TFdquUqu36SguIsNvbt8qlzqC4Da_I3SiJCseSWda6_7__vLro93wCbLfA3Jht3afGi8jBxlUTvhm6uWqZZLoNk4e316wn6_A-T0YHIiLI5v0lU1Bqa3mfOopnFP/s2000/1.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="611" data-original-width="2000" height="122" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEieH0c-TeA8fpOfpmZcpWOumKJcGyBW0bqqwSmwvsC63YghlgJMNojlzckRf_KT9pe6TFdquUqu36SguIsNvbt8qlzqC4Da_I3SiJCseSWda6_7__vLro93wCbLfA3Jht3afGi8jBxlUTvhm6uWqZZLoNk4e316wn6_A-T0YHIiLI5v0lU1Bqa3mfOopnFP/w400-h122/1.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><h3 style="clear: both; text-align: left;"><b>Process flow steps: </b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ol style="text-align: left;"><li>OAuth Token generated in IDP service using client id and secret.</li><li>Invoking API resources published in Azure API Management platform using the OAuth token</li><li>Azure APIM to BTP CI: Client certificate-based authentication</li><li>Azure APIM will send the API request along with the Application ID as a header parameter to BTP CI</li><li>BTP CI integration flow step will do a VM table lookup to get the corresponding Client ID defined in respective Connectivity service.</li><li>BTP CI iFlow step will use the client ID and secret specific to the connectivity service to fetch the JWT token from the connectivity service.</li><li>BTP CI iFlow step will attach the fetched JWT token to the header “SAP-Connectivity-Technical-Authentication” and send the API request to SCC.</li><li>BTP CI -> SCC: It is through secure tunnel (one time trust activity)</li><li>SCC -> SAP S/4HANA is based on mTLS authentication (WD forwards the short-lived certificate for the system user from SCC to S/4)</li><li>SCC will evaluate the JWT token and generate a short-lived certificate specific to the client ID</li><li>In SAP S/4, API request with short-lived certificate is evaluated against the CERTRULE entries and corresponding SAP system user is validated.</li><li>SAP System user roles and authorization is checked, and OData/SOAP API is executed under the specific system user.</li></ol></div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>Section1: BTP Configuration</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">This section includes BTP Destination configuration, SAP CI configuration and Connectivity Service subscription and configuration.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>BTP Destination Configuration:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Create a destination for PP (Principle Propagation) as below</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhyhOpVjTI1K6UIeH1FI_THqaQ1RF-va2d6xMUUufQy5JiBPymW08uF-NggLLT4i7NVPeKgYFHtu4nMo5Wr5lXO6TewEn2uGpb51o5CqAlblHXau3LmMUPTOh2xupYe4jBt9rJ6E4yuxwjVNUpbn4KL4ovVs0ARJ3awZAEnwg853wipBAOQ1w41DxFX7aXK/s903/2.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="465" data-original-width="903" height="206" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhyhOpVjTI1K6UIeH1FI_THqaQ1RF-va2d6xMUUufQy5JiBPymW08uF-NggLLT4i7NVPeKgYFHtu4nMo5Wr5lXO6TewEn2uGpb51o5CqAlblHXau3LmMUPTOh2xupYe4jBt9rJ6E4yuxwjVNUpbn4KL4ovVs0ARJ3awZAEnwg853wipBAOQ1w41DxFX7aXK/w400-h206/2.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjwashYfbNTLmWzgLkDTVTccl5ejK9mZ4iSGpLiWwntHyip3MRLnFrA4A2jjEDRVXr4gGimIH2E7kbb4jhxXwvn911en9Whb8rLhcMCLijXBmnqMubt2hgufhhMBR_rJBnX9B49eWxAY3QKbYDUy4xAVVr61IeipieFKqSLBU_0DrRn_psw-wgA9N107x6f/s698/3.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="383" data-original-width="698" height="220" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjwashYfbNTLmWzgLkDTVTccl5ejK9mZ4iSGpLiWwntHyip3MRLnFrA4A2jjEDRVXr4gGimIH2E7kbb4jhxXwvn911en9Whb8rLhcMCLijXBmnqMubt2hgufhhMBR_rJBnX9B49eWxAY3QKbYDUy4xAVVr61IeipieFKqSLBU_0DrRn_psw-wgA9N107x6f/w400-h220/3.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>CONNECTIVITY SERVICE:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In the same subaccount of CI, subscribe “connectivity service” with plan “lite”.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">We need one service subscription for each source system as</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">◉ Each source system will be using different application id.</div><div class="separator" style="clear: both;">◉ Each application ID should correspond to one client ID of connectivity service.</div><div class="separator" style="clear: both;">◉ Client ID in the same connectivity service will be same even though we create multiple service keys.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjmtt9Wj9kl-2Reyyt_5oHz5uoBT641SjGI3pRvkiFBpIkbBavXMpBSBHvg4Ns09NC_N9hV2KVWtHTM7WUTV_Y4ZKIW-vldGAm7NonMnlWqWweqv2ydkZKAsOEwjYU_a6xwwvnxGakKL939Qox6_vssCG4hxuIlGz3_2K87lELEkrUMLT4KU3LufVPZXc8W/s903/4.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="93" data-original-width="903" height="41" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjmtt9Wj9kl-2Reyyt_5oHz5uoBT641SjGI3pRvkiFBpIkbBavXMpBSBHvg4Ns09NC_N9hV2KVWtHTM7WUTV_Y4ZKIW-vldGAm7NonMnlWqWweqv2ydkZKAsOEwjYU_a6xwwvnxGakKL939Qox6_vssCG4hxuIlGz3_2K87lELEkrUMLT4KU3LufVPZXc8W/w400-h41/4.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Now create service keys for both the connectivity service subscriptions.</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQeX5WC1lxtfFu3HynrdEcG-eDFZhZ2jjvQdwbgOstpy9f3I44vvA8wMmXtPnAjnw_yTcV7Egk6cE6nuTCH7i6vJPtxLKrwKdx__LjRQs4fzB1V30-IJCgrdOaXF6tUc8BZbUKK_9_gVrb0-cJ34NWQety6pJEQmhlvMwLZjQOa1uKXjJm0MDBAB1mYI1F/s820/5.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="189" data-original-width="820" height="93" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjQeX5WC1lxtfFu3HynrdEcG-eDFZhZ2jjvQdwbgOstpy9f3I44vvA8wMmXtPnAjnw_yTcV7Egk6cE6nuTCH7i6vJPtxLKrwKdx__LjRQs4fzB1V30-IJCgrdOaXF6tUc8BZbUKK_9_gVrb0-cJ34NWQety6pJEQmhlvMwLZjQOa1uKXjJm0MDBAB1mYI1F/w400-h93/5.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPMoEWRhht7MDyGfH4bFbX7k0DKB4TbE8jmy9hyphenhyphenzllTIeP9oJQn4iZwmmb2plGp5prCk15xmqMvuDYk-UFcLbQQiZTn7f_ihSQGeoz8ll7ekLyCaYU0t_IaL2uebmPlk7Gt6k1KKM0qM0mnxF1XAbVavRI0mgwlIT65ntnSqAbN2_xSg2oU9Kq0mqesDWO/s739/6.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="193" data-original-width="739" height="105" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPMoEWRhht7MDyGfH4bFbX7k0DKB4TbE8jmy9hyphenhyphenzllTIeP9oJQn4iZwmmb2plGp5prCk15xmqMvuDYk-UFcLbQQiZTn7f_ihSQGeoz8ll7ekLyCaYU0t_IaL2uebmPlk7Gt6k1KKM0qM0mnxF1XAbVavRI0mgwlIT65ntnSqAbN2_xSg2oU9Kq0mqesDWO/w400-h105/6.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>SAP CI:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">A VM table is maintained to get the corresponding Client ID defined in respective Connectivity service for the Application ID passed from source system. Below iflow depicts the configurations in CI iflow and value mapping table.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSHhZGzwk455OaMGXUr8_9IW_xkvIgfQkcJ3dHuTaoj7izrnw28-k31BiezeUMN-bUW5OiwkVtX8-8rHPpnT3-0EEtXTMU0NaOY0vHOL0z6p-lFyXHw8c1B0_gtRh-b-FxR-pUheA1KQjb3wLvOX6VJ3nPXsFKJT9cnwz4UdFILYJ2f7nWEV7YQO2C3i2T/s903/7.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="249" data-original-width="903" height="110" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSHhZGzwk455OaMGXUr8_9IW_xkvIgfQkcJ3dHuTaoj7izrnw28-k31BiezeUMN-bUW5OiwkVtX8-8rHPpnT3-0EEtXTMU0NaOY0vHOL0z6p-lFyXHw8c1B0_gtRh-b-FxR-pUheA1KQjb3wLvOX6VJ3nPXsFKJT9cnwz4UdFILYJ2f7nWEV7YQO2C3i2T/w400-h110/7.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEqaD0zGyn03uXruRzCoN5Bonw-AxcwhmAuZDGTGBAJPqCSl9Y1W0ZCe_C98Miiu-1AtG7IL3NMXbtcZEJKCljb8fW6bw6d0Rr_OyCTqnXcnoFgXR1LvkVzUyMNgDbp9XcN8yjNEYJ-ncytRR19JRm3euh1kIoBBg47z26lM-RG9j_DVcPhokwruaqRC43/s664/8.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="256" data-original-width="664" height="154" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEqaD0zGyn03uXruRzCoN5Bonw-AxcwhmAuZDGTGBAJPqCSl9Y1W0ZCe_C98Miiu-1AtG7IL3NMXbtcZEJKCljb8fW6bw6d0Rr_OyCTqnXcnoFgXR1LvkVzUyMNgDbp9XcN8yjNEYJ-ncytRR19JRm3euh1kIoBBg47z26lM-RG9j_DVcPhokwruaqRC43/w400-h154/8.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">The User shown below is the Connectivity service instance – Client-ID</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgVSLLKRhYwR1qcAtxaIVJEu5UQJrdY9HsLGOZy5px-GxPMzgqrwwE_xVmPxQqrse7IA7RYur_JhMCOoA2Qx9DzuxZKmcVZv3zX8yXzUQio-hFf1ztzMuQbqObTrd1XUcHOtPmAAoLCX2viwlu28W15t95Z9aOQOeCG2goGj9ZF5F2eiFyCAdCUrJPG3WaK/s728/9.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="257" data-original-width="728" height="141" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgVSLLKRhYwR1qcAtxaIVJEu5UQJrdY9HsLGOZy5px-GxPMzgqrwwE_xVmPxQqrse7IA7RYur_JhMCOoA2Qx9DzuxZKmcVZv3zX8yXzUQio-hFf1ztzMuQbqObTrd1XUcHOtPmAAoLCX2viwlu28W15t95Z9aOQOeCG2goGj9ZF5F2eiFyCAdCUrJPG3WaK/w400-h141/9.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJqIEujVRbrg6m8tDI_N471R9VHDbUtXZ7W63CdvoEq1u0tVHe-5ntWDN-kmRAWeidS_H_J38NLW-uK6UbPR7lw5Zw7eF8iCWaXpwpds_pHjeuyWWR9Tkzx7IGm3QTJzaQ8MAJiWMt6xuwrJmSVauhR1NH4gnHZO70vVXMh6IPTbNlHzBlFs9s2LZb4oR4/s903/10.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="379" data-original-width="903" height="168" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJqIEujVRbrg6m8tDI_N471R9VHDbUtXZ7W63CdvoEq1u0tVHe-5ntWDN-kmRAWeidS_H_J38NLW-uK6UbPR7lw5Zw7eF8iCWaXpwpds_pHjeuyWWR9Tkzx7IGm3QTJzaQ8MAJiWMt6xuwrJmSVauhR1NH4gnHZO70vVXMh6IPTbNlHzBlFs9s2LZb4oR4/w400-h168/10.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Step 1: HTTPs call with Application ID passed in header.</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiORzefr8Prpv7cn1JrBl6fSJyO40ELlAbkqb7RUEfReVNYDzSRY4ncKZ9zMMYTlh2OUEmpTuddMUXE9jNmGFtO2BKzzOnccFIEW2P5fh4FvRZpETJJxfN5jTQmiwyHNL5MxRyUFXXMPuIQHE3BsNzGqxMrlLO0dE2PqvGuyOMeyQvrlSK2aba_EWsZsMjN/s583/11.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="281" data-original-width="583" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiORzefr8Prpv7cn1JrBl6fSJyO40ELlAbkqb7RUEfReVNYDzSRY4ncKZ9zMMYTlh2OUEmpTuddMUXE9jNmGFtO2BKzzOnccFIEW2P5fh4FvRZpETJJxfN5jTQmiwyHNL5MxRyUFXXMPuIQHE3BsNzGqxMrlLO0dE2PqvGuyOMeyQvrlSK2aba_EWsZsMjN/w400-h193/11.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Step 2: Groovy script to fetch the connectivity service (TechnicalUser1) username maintained in SAP CI security material. </div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg7HJt94oCZvjUevF-zzbvkzo-_aEIQ_7jB3PEHmNYYmyh2qfSLWreEs_Lc2LNhAE1Jye_d7_qOjiv53fpzd1p8QiUEMt1uoGpxNun38HpZQmWrjpjJF8lHLopIPZ3vrIksUIbu9Dw-2FLkro446x0t2JFxRDNV-Veb8Y1H-J8Z2Xse2Fs-2d6UeFcf1Amb/s799/12.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="565" data-original-width="799" height="283" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg7HJt94oCZvjUevF-zzbvkzo-_aEIQ_7jB3PEHmNYYmyh2qfSLWreEs_Lc2LNhAE1Jye_d7_qOjiv53fpzd1p8QiUEMt1uoGpxNun38HpZQmWrjpjJF8lHLopIPZ3vrIksUIbu9Dw-2FLkro446x0t2JFxRDNV-Veb8Y1H-J8Z2Xse2Fs-2d6UeFcf1Amb/w400-h283/12.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Step 3: Routing condition to validate if the Application ID. </div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh6kFLWTiyTXiJKrNP9UNBSuQXqAPF_uvUflYCwTyLIsKBbr-3QhseiYyVbrIs7RszTjZab300wR8xAOiWa2xhx-iVrSxLSiVHWvPTs11P5muoEjPxg1cuBfC1HUC-FZYpjTYig6kWPC-YOyMRmeVzFkJ1_oB_W3J_jC24bvsIacjRrq2iJoLvi09fygf8t/s903/13.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="245" data-original-width="903" height="109" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh6kFLWTiyTXiJKrNP9UNBSuQXqAPF_uvUflYCwTyLIsKBbr-3QhseiYyVbrIs7RszTjZab300wR8xAOiWa2xhx-iVrSxLSiVHWvPTs11P5muoEjPxg1cuBfC1HUC-FZYpjTYig6kWPC-YOyMRmeVzFkJ1_oB_W3J_jC24bvsIacjRrq2iJoLvi09fygf8t/w400-h109/13.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Step 4: If the application ID is valid call Connectivity service to get the JWT token.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To get the connectivity service credentials create an instance and service key in BTP.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEghqzbUQmEDWdCtp8Qgz0J0ZiYr6TfX78PVDwvLqZ4ylKmTQDwi8TSj_Z3YSIwY8XZQXWxwilHTrv5HmDjEWWByjjnvLpAj9DSSYyyT0kC4JLmkDBI1hg2UtfOinNTyU7b1KDD8_m8hIK8WJmDr_qJ5w19CiTF0dBoFKR_jIMaSReFk79rCnEEvgatOvt7n/s858/14.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="609" data-original-width="858" height="284" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEghqzbUQmEDWdCtp8Qgz0J0ZiYr6TfX78PVDwvLqZ4ylKmTQDwi8TSj_Z3YSIwY8XZQXWxwilHTrv5HmDjEWWByjjnvLpAj9DSSYyyT0kC4JLmkDBI1hg2UtfOinNTyU7b1KDD8_m8hIK8WJmDr_qJ5w19CiTF0dBoFKR_jIMaSReFk79rCnEEvgatOvt7n/w400-h284/14.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Step 5: Get the access token from connectivity service call response and set the header parameter “SAP-Connectivity-Technical-Authentication”.</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5LUc5jZPLM0VpRAYmeq9bOe2-VkxKrn7Iw8US3j4GKtiLFaj6cW-SE1sus84Awj-1x6iOK4R0LHwXV6alXkOpepGP_4sfiI8F2QTGlAZfjQU9Np4jHPtb7kte5ffE6g1HsHxFNAzIwVIMBXKhONMMsu2qVq5X1qyj_QGxPIESX2hdKtrZKLQtEvRRnHJi/s616/15.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="296" data-original-width="616" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5LUc5jZPLM0VpRAYmeq9bOe2-VkxKrn7Iw8US3j4GKtiLFaj6cW-SE1sus84Awj-1x6iOK4R0LHwXV6alXkOpepGP_4sfiI8F2QTGlAZfjQU9Np4jHPtb7kte5ffE6g1HsHxFNAzIwVIMBXKhONMMsu2qVq5X1qyj_QGxPIESX2hdKtrZKLQtEvRRnHJi/w400-h193/15.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Step 6: Call the S4HANA OData API</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGgG2FiAa1ovSP49zin9zF4dsFfVBHcR5QyMiNlsn2yciCZFQOgiYLnCdUsY_FpmlzxN7Q0dis3KjaoTMqc1pINcU5aS63X_QePNNdkeM1dtMqOIV0TB1e9hFmz9oBdoXve5t8vZRuk-A43AZceBSIzMnD2xYx1D7YueBjLp-PCz6tOlMu-g-fctfJiod3/s903/16.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="348" data-original-width="903" height="154" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGgG2FiAa1ovSP49zin9zF4dsFfVBHcR5QyMiNlsn2yciCZFQOgiYLnCdUsY_FpmlzxN7Q0dis3KjaoTMqc1pINcU5aS63X_QePNNdkeM1dtMqOIV0TB1e9hFmz9oBdoXve5t8vZRuk-A43AZceBSIzMnD2xYx1D7YueBjLp-PCz6tOlMu-g-fctfJiod3/w400-h154/16.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Step 7: If the Application ID or the source system is invalid pass the error response to source system</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPfyRyjmyBi7apGaaA9xrVXjEo55dRpoTHFFRsh2pomPFcFrC7hyjXFCmvToIjfNc8ZaoY0dap6XgNL7uSKfs5PrZrgXuNrxX0COONTvwdhfLKrvL1rxMvEBKaNiEIzyl5RRuwFQk1xETqM8m856dORAImSwVaurtC9dbDcdaWbe0pZ6nGBAQpOmgSIDCS/s903/17.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="211" data-original-width="903" height="94" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPfyRyjmyBi7apGaaA9xrVXjEo55dRpoTHFFRsh2pomPFcFrC7hyjXFCmvToIjfNc8ZaoY0dap6XgNL7uSKfs5PrZrgXuNrxX0COONTvwdhfLKrvL1rxMvEBKaNiEIzyl5RRuwFQk1xETqM8m856dORAImSwVaurtC9dbDcdaWbe0pZ6nGBAQpOmgSIDCS/w400-h94/17.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Section-2: S4HANA side configuration:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Step 1: Login to cloud connector->Select the subaccount for CI</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">->Click on “Cloud to On-premise” connections</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">->Create a HTTPS connection to S4 system</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"> “Principal Type” set to “X.509 certificate.”</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Create “Access Control” entry for S4 Hana </div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgduDLMs28BKxmKVHCmFB5blOyb7pG0vp3SzuZFICAhZmypwWebN1AOtSnjrZprryaBi2GmyOHOw69l4bUu_BvV_JiyRZojHudOCLZG57iFMxUTDQulkPACF4mRiRJoiiKnx92fSP-5bMfC5tVuh8HfGcBQYaZDLDidKKwXQ25O2gyHaxmKrEXsWtHVgkXH/s639/18.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="573" data-original-width="639" height="359" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgduDLMs28BKxmKVHCmFB5blOyb7pG0vp3SzuZFICAhZmypwWebN1AOtSnjrZprryaBi2GmyOHOw69l4bUu_BvV_JiyRZojHudOCLZG57iFMxUTDQulkPACF4mRiRJoiiKnx92fSP-5bMfC5tVuh8HfGcBQYaZDLDidKKwXQ25O2gyHaxmKrEXsWtHVgkXH/w400-h359/18.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhsZVyCgm2TpaTfu9N3WHqPjY1ubNiFeNBtp6wf-AnmSNY_XchmBdBGlPcKfcM3IKUniapx3NWV8sf63Tqy_xcG3n7UQCTz5H_ja7WV0QNxhO4NqgPtRDfOA9YC1OqgS1ZaY-YJpF6TiM54QlLWqPmUr92FTFTC5Wse0i3ADaCS8r33UGaxkkEBr63-lbnn/s803/19.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="708" data-original-width="803" height="353" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhsZVyCgm2TpaTfu9N3WHqPjY1ubNiFeNBtp6wf-AnmSNY_XchmBdBGlPcKfcM3IKUniapx3NWV8sf63Tqy_xcG3n7UQCTz5H_ja7WV0QNxhO4NqgPtRDfOA9YC1OqgS1ZaY-YJpF6TiM54QlLWqPmUr92FTFTC5Wse0i3ADaCS8r33UGaxkkEBr63-lbnn/w400-h353/19.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEje2VmqFRssrlQfa_UmScJE9Y1yxrNq5YtGFjuQ_Z84WEI_IpeGR0V3fHnjnKis8Nx9q6AzyVZTohG74NBsxB2qy5pAw1ajJSw1GGlSjsC_fenlf5XheKwOzXYeIY5HKhYl8l9dcXFyE39JNKwo7AAQUgtMWmeHNaWLrK_eyyrZWjlxR2wWSiQGn9mR0Q1-/s903/20.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="120" data-original-width="903" height="54" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEje2VmqFRssrlQfa_UmScJE9Y1yxrNq5YtGFjuQ_Z84WEI_IpeGR0V3fHnjnKis8Nx9q6AzyVZTohG74NBsxB2qy5pAw1ajJSw1GGlSjsC_fenlf5XheKwOzXYeIY5HKhYl8l9dcXFyE39JNKwo7AAQUgtMWmeHNaWLrK_eyyrZWjlxR2wWSiQGn9mR0Q1-/w400-h54/20.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Step 2: Create its system certificate in SCC and Download the certificate.</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Goto Configurations->On-premise</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Get the signed key pair(p12) from certificate authority, then import the certificate.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3GflfgkipOJY8_d0KFntZW_zppfIPypLvgj1g39ci0mqAE1c1FuYjQz86Ve3zhXD7O_cnflw0tlqBmLmm5E0-1cxZlNNxs2AR_CYJJ4YKA1pjTbYjAQNmGunU-TcOuIDYkcQvWXMsPMFQrbr86Mk9BibouU7mLU_gbdjxKOIcRcS3qBhfbt1-mNEWpOen/s903/21.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="383" data-original-width="903" height="170" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3GflfgkipOJY8_d0KFntZW_zppfIPypLvgj1g39ci0mqAE1c1FuYjQz86Ve3zhXD7O_cnflw0tlqBmLmm5E0-1cxZlNNxs2AR_CYJJ4YKA1pjTbYjAQNmGunU-TcOuIDYkcQvWXMsPMFQrbr86Mk9BibouU7mLU_gbdjxKOIcRcS3qBhfbt1-mNEWpOen/w400-h170/21.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEglUARsZ9CMo3yapiDGJZ02EX-0_ixwTw7ua2mF5lyTRxCD2G2JOMFSo65EASNo6U3tbfySRAyZ9MrLmjMkfMI9-dWuS2oeHM96Im4d3O_WPRWKgdndv4WkMihbqMTimoIk17z1LoYTs6ZEoSg10IvEgiMktTYUUgZdo1Uqr-wWPaPtdym6TucW8gfAgvbR/s903/22.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="237" data-original-width="903" height="105" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEglUARsZ9CMo3yapiDGJZ02EX-0_ixwTw7ua2mF5lyTRxCD2G2JOMFSo65EASNo6U3tbfySRAyZ9MrLmjMkfMI9-dWuS2oeHM96Im4d3O_WPRWKgdndv4WkMihbqMTimoIk17z1LoYTs6ZEoSg10IvEgiMktTYUUgZdo1Uqr-wWPaPtdym6TucW8gfAgvbR/w400-h105/22.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Download the system cert public key from cloud connector</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">CA certificate:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Create self-signed CA certificate.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEikpQgbyRcW2b7MrvVxnt3ZJU0Yu_CkJ7LJoSQ0X2rIU0cCwISRJNDokXbVXHRuorsSiFMcHL_56jvcxFCRmsEVlrN9YPTGPhlCSzUu7829T2IPjxArg43GK-YwlYFDBaQ-gYaiveZKI3D4GrF8DD3MA-Jwd6LOyniiIubuO7UeDblIOZ_dgLJKoC3RF1Vn/s903/23.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="383" data-original-width="903" height="170" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEikpQgbyRcW2b7MrvVxnt3ZJU0Yu_CkJ7LJoSQ0X2rIU0cCwISRJNDokXbVXHRuorsSiFMcHL_56jvcxFCRmsEVlrN9YPTGPhlCSzUu7829T2IPjxArg43GK-YwlYFDBaQ-gYaiveZKI3D4GrF8DD3MA-Jwd6LOyniiIubuO7UeDblIOZ_dgLJKoC3RF1Vn/w400-h170/23.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPvHPuSmJ6XBWwUqA2SZDso-a-5SUXRhCLyc6YghWJpm3910Kxmg9N6sXdyMVC42L9gQEo_j-Uv3sQqf7xdJg135JJkwtF1RIM8Y4l1oJuvN5STTgl0ptJZ9XelImvsCH3uO9VQVg9rSuza0p3wBfUiMPiyPgWaoROfSDwUCE_mBn-cDM_Hdbs6sUnChJ0/s903/24.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="261" data-original-width="903" height="115" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPvHPuSmJ6XBWwUqA2SZDso-a-5SUXRhCLyc6YghWJpm3910Kxmg9N6sXdyMVC42L9gQEo_j-Uv3sQqf7xdJg135JJkwtF1RIM8Y4l1oJuvN5STTgl0ptJZ9XelImvsCH3uO9VQVg9rSuza0p3wBfUiMPiyPgWaoROfSDwUCE_mBn-cDM_Hdbs6sUnChJ0/w400-h115/24.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Use Subject patterns of principle propagation as CN=${name} as we are using client ids</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrGw2-aICnr5KMPLhXNVbGpt8WAacoy2alM4-eLaXHNjPbqm-_ESaUDxeFp5oAFRFQ_nfi56-q1axzCYCHMLA1cxlZSQv-1Oion4RVFPfVqjUd1xEOVAKVQky4jT8eJ-gaPhNWhpJPFK6ZXWfsaiUpIm0DzLggxWBrLbCHuGX7RGb8pi6B9Iczw1DBPosU/s903/25.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="257" data-original-width="903" height="114" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgrGw2-aICnr5KMPLhXNVbGpt8WAacoy2alM4-eLaXHNjPbqm-_ESaUDxeFp5oAFRFQ_nfi56-q1axzCYCHMLA1cxlZSQv-1Oion4RVFPfVqjUd1xEOVAKVQky4jT8eJ-gaPhNWhpJPFK6ZXWfsaiUpIm0DzLggxWBrLbCHuGX7RGb8pi6B9Iczw1DBPosU/w400-h114/25.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Step 3: Import Certificate to S4</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Import the SCC system certificate in S/4 HANA STRUST under SSL server standard at S4.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Step 4: Set Parameters in S/4</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Set Profile parameter icm/trusted_reverse_proxy to the SCC system certificate.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgc9rk4Th3TS9Ad3rk8n8B21bnWjLal8XSn6RhVd7VZj3Mwb15MCYUoCMRt7xXNVix-YfpdAriLolHWSxiQphX4nMn_Wvj2WIoo0J9hYdT6SWNuDsyu7w8sy2_xBKvi7nulhRpEJIxJXHaetYYu8VqttemmXCp8fSCRepMTcxVUKoXfefEvu8eU2pKftOwh/s903/26.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="323" data-original-width="903" height="143" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgc9rk4Th3TS9Ad3rk8n8B21bnWjLal8XSn6RhVd7VZj3Mwb15MCYUoCMRt7xXNVix-YfpdAriLolHWSxiQphX4nMn_Wvj2WIoo0J9hYdT6SWNuDsyu7w8sy2_xBKvi7nulhRpEJIxJXHaetYYu8VqttemmXCp8fSCRepMTcxVUKoXfefEvu8eU2pKftOwh/w400-h143/26.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6UlguoJnG9GmYvHr52Yaf-msJnLWPCrXS-YjgbHNBC52T9ujtjz_E2cCB6mvAFRN4B4O68I_3JmOveKFh3FAdRzMG3d2xytKK91dUKy8HEx74C-giddHyVqEg3CHt-j8QbBammZx711vCOQS3dTJBcRnEsGDL4yTHNqbxGOgI2NfshFLxT8wd1wFEn8ef/s903/27.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="356" data-original-width="903" height="158" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6UlguoJnG9GmYvHr52Yaf-msJnLWPCrXS-YjgbHNBC52T9ujtjz_E2cCB6mvAFRN4B4O68I_3JmOveKFh3FAdRzMG3d2xytKK91dUKy8HEx74C-giddHyVqEg3CHt-j8QbBammZx711vCOQS3dTJBcRnEsGDL4yTHNqbxGOgI2NfshFLxT8wd1wFEn8ef/w400-h158/27.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Step 5:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Set the profile parameter icm/HTTPS/verify_client = 1</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijnTL7RfzRAWGjRLHBPbGCk8xvGu2PeaSNtNFguYJiX4V9G52cf3hVcBTdN2Zn48NY8kgGX0BgrF-Npk8ITEaCiwkjjZKcApGjyJSJlhswaxlJUkFqc71GexV5LTQsRH6mCUT3E7JCtt52mrNaQIBL6v-b-oQ1pu1UpqIu6S3asPDIIsD8DTG64F08zH8O/s903/28.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="202" data-original-width="903" height="90" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijnTL7RfzRAWGjRLHBPbGCk8xvGu2PeaSNtNFguYJiX4V9G52cf3hVcBTdN2Zn48NY8kgGX0BgrF-Npk8ITEaCiwkjjZKcApGjyJSJlhswaxlJUkFqc71GexV5LTQsRH6mCUT3E7JCtt52mrNaQIBL6v-b-oQ1pu1UpqIu6S3asPDIIsD8DTG64F08zH8O/w400-h90/28.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Step 6: Certificate to user mapping in S4</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Map the SCC certificate to a system user with sufficient authorization via Transaction code CERTRULE.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">For Client certificate (Certificate based authentication), use sample certificate generated at SCC with client ID to s4 user</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In SCC, click on “create a sample certificate”.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg1s4UR-gcXiY7z-xIgrPkKN-Wrh1VgsqWU6I3-x0a74VGiXeH3k3xLBecbr9Lkoxjfv0-c_6XCz6KVxFLa0_Az9X2yHoifZWWOr1FinpbATBEvahCyCthA9bo7s166UCGCYF16rWWXvA8wl6_t7IoX1SiuUeW1y8pevICIyPPqlBFz7Mw4DDurocOiESYj/s903/29.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="388" data-original-width="903" height="171" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg1s4UR-gcXiY7z-xIgrPkKN-Wrh1VgsqWU6I3-x0a74VGiXeH3k3xLBecbr9Lkoxjfv0-c_6XCz6KVxFLa0_Az9X2yHoifZWWOr1FinpbATBEvahCyCthA9bo7s166UCGCYF16rWWXvA8wl6_t7IoX1SiuUeW1y8pevICIyPPqlBFz7Mw4DDurocOiESYj/w400-h171/29.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicyf3QMV3rUnmUNYyJOcLMleyAYVIlVFdKG0ipya0RQfJaIzh1_HR-F3Uq0b9LNn3ZxAmaP7ZIUqTrBr36g4D2D91gNZBaRBAPtKogbIFAj5GIbq6R9_Q5ym6NqKPWrLbqvdqCzigLK6tmkG_Hrty4imv02gkrYZoP4Y0VnV7XvVtWFHRQtxsj_bXRHgJx/s903/30.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="287" data-original-width="903" height="127" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicyf3QMV3rUnmUNYyJOcLMleyAYVIlVFdKG0ipya0RQfJaIzh1_HR-F3Uq0b9LNn3ZxAmaP7ZIUqTrBr36g4D2D91gNZBaRBAPtKogbIFAj5GIbq6R9_Q5ym6NqKPWrLbqvdqCzigLK6tmkG_Hrty4imv02gkrYZoP4Y0VnV7XvVtWFHRQtxsj_bXRHgJx/w400-h127/30.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Click on generate.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Use the downloaded certificate in S4 certrule to map for each client id.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjnBLFxCR6NyRV_DaBLi_CNvcHJ3n_lyl83GX6_ZogkQCyJwW1YUG9pSeukj9j5SEhPtIv-rxoxnNisT0Wwn_OUG8R2kI1U6SmDcL6WqS_G2tma2kWSxsPhrjjzTDVL0pt2CRdcJ_PtpH0MxWjFnFhB9IV_sgBtG7TYXtUWP5DLpEyVOeYcOfFUQKDl-e8w/s903/31.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="434" data-original-width="903" height="193" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjnBLFxCR6NyRV_DaBLi_CNvcHJ3n_lyl83GX6_ZogkQCyJwW1YUG9pSeukj9j5SEhPtIv-rxoxnNisT0Wwn_OUG8R2kI1U6SmDcL6WqS_G2tma2kWSxsPhrjjzTDVL0pt2CRdcJ_PtpH0MxWjFnFhB9IV_sgBtG7TYXtUWP5DLpEyVOeYcOfFUQKDl-e8w/w400-h193/31.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Use all mapping in “Explicit Mapping” in certrule.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">For mutual authentication we are mapping system certificate from cloud connector to S4 user (TU_SSO_PP). Connectivity service certificates are mapped to TU_SSO_PP1 and TU_SSO_PP2.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Step 7:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Set the profile parameter value to 1</div><div class="separator" style="clear: both;">login/certificate_mapping_rulebased=1</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Step 8: Adjust the login procedure list of ICF service S4</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Adjust the login procedure list for the ICF services which are to be invoked as a part of Integration. (SAP Note _ 2573379)</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The login procedure list should follow below sequence.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Basic Authentication</div><div class="separator" style="clear: both;">2. Logon using SSL Certificate</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi9Q91Kd1-QTsWhjM8h3U08WppE6R_uzCyfCfSQJBkT5V_wCsJMltOdcK6l_uzcfmeswvT5di4fz3dpiVur1riGNg3LCQ-4cXtxIpc2z9Hbr64-II15AtZjdfteXVfOfLo8vOH97qWlt5F1OzG3b3LiUelXQu5tjQaGR2SY_ig5HcdcQhjAbVNmvWlr8zQr/s514/32.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="130" data-original-width="514" height="101" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi9Q91Kd1-QTsWhjM8h3U08WppE6R_uzCyfCfSQJBkT5V_wCsJMltOdcK6l_uzcfmeswvT5di4fz3dpiVur1riGNg3LCQ-4cXtxIpc2z9Hbr64-II15AtZjdfteXVfOfLo8vOH97qWlt5F1OzG3b3LiUelXQu5tjQaGR2SY_ig5HcdcQhjAbVNmvWlr8zQr/w400-h101/32.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Step 9:</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Consider steps mentioned in link below needed to setup Certificate forwarding through Web dispatcher.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><a href="https://help.sap.com/docs/ABAP_PLATFORM_NEW/683d6a1797a34730a6e005d1e8de6f22/2a6cec67c50842aab1444f7dfd0257e1.html?version=201809.latest&locale=en-US" target="_blank">https://help.sap.com/docs/ABAP_PLATFORM_NEW/683d6a1797a34730a6e005d1e8de6f22/2a6cec67c50842aab1444f7...</a></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><h3 style="clear: both; text-align: left;"><b>Testing:</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Positive Test case: Valid User</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Trigger SAP CI API from postman with Application ID in header:</div></div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEirnoy3sM3DEt9rv_itNuUu0fokxVgJMRUgodStcP3r5Tt9sVyLX6c_jDIMnlHMjfeIW5F7UF1BnLj7SaqCozArocvIsS5MtA_lqnnLQ_j_TJse_qFiO5xCcapSiKl9LssoZqH_x6xaGc6XHghbg4bGMj7GOkip6z3LFm0nb_-MQouo5-aO9lU9yaijiMPS/s903/33.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="267" data-original-width="903" height="119" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEirnoy3sM3DEt9rv_itNuUu0fokxVgJMRUgodStcP3r5Tt9sVyLX6c_jDIMnlHMjfeIW5F7UF1BnLj7SaqCozArocvIsS5MtA_lqnnLQ_j_TJse_qFiO5xCcapSiKl9LssoZqH_x6xaGc6XHghbg4bGMj7GOkip6z3LFm0nb_-MQouo5-aO9lU9yaijiMPS/w400-h119/33.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Get the Connectivity service Client ID from Value mapping.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Fetch JWT Token from Connectivity service and pass it in “SAP-Connectivity-Technical-Authentication” header.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgugoVRoKHx-uIWfa-SNATvJAoT_ZSACbsLmfGN2Hb5dkjux4ngVgPW-Xsb9oZ67f4Ltvi-oTW34HTx0gGkRj7_-ooyp1rBTPvPvMC0zRWlLg3QjPoLdrzR4mpLouTajyKhkMOvuSmx7ZJFmtbDN5S6qyct9_gpvFLCp4z7IX1lI6hMruRnnT0yyn_-5f9K/s903/34.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="378" data-original-width="903" height="168" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgugoVRoKHx-uIWfa-SNATvJAoT_ZSACbsLmfGN2Hb5dkjux4ngVgPW-Xsb9oZ67f4Ltvi-oTW34HTx0gGkRj7_-ooyp1rBTPvPvMC0zRWlLg3QjPoLdrzR4mpLouTajyKhkMOvuSmx7ZJFmtbDN5S6qyct9_gpvFLCp4z7IX1lI6hMruRnnT0yyn_-5f9K/w400-h168/34.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Short lived certificate created in Cloud connector.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">User validated in S4HANA and response from S4HANA.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhSDJHz3b5dvoFO51dTfidRiaB_hb20yW2tuvbEdWaElwLlBPl60qiPfnuFP3QZiRa1fvhH7m3h566euRKCnI9e502h0tPPj_SsOIfBue_gglSt9aOgWIZNMGD4p3e7E6Ya5tgupNJcs2DGD3V6VLiST8j7XRS_-xIqqJb-VWKQx4-Nqd5sVcHBfmScjqjF/s903/35.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="82" data-original-width="903" height="36" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhSDJHz3b5dvoFO51dTfidRiaB_hb20yW2tuvbEdWaElwLlBPl60qiPfnuFP3QZiRa1fvhH7m3h566euRKCnI9e502h0tPPj_SsOIfBue_gglSt9aOgWIZNMGD4p3e7E6Ya5tgupNJcs2DGD3V6VLiST8j7XRS_-xIqqJb-VWKQx4-Nqd5sVcHBfmScjqjF/w400-h36/35.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">HTTP response 200 in postman</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgb8Jr6MLvVoiXQxelb1LUwIOvaj1pwVtqK7C2cild94IxkEVlqfuLahbmtxp7fJ3QgH0grZwYjqw8IEAokKB1V07QrHp4Pt2KtD7rhk1AOmmzMgOuwf3YQ7JOqktZq_z3qAxQEdycdfAnQZ91wmMc6rO2dUmqdOBI-A19fLMTAOrvpaBrTP9o5QR0UGOcv/s903/36.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="157" data-original-width="903" height="70" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgb8Jr6MLvVoiXQxelb1LUwIOvaj1pwVtqK7C2cild94IxkEVlqfuLahbmtxp7fJ3QgH0grZwYjqw8IEAokKB1V07QrHp4Pt2KtD7rhk1AOmmzMgOuwf3YQ7JOqktZq_z3qAxQEdycdfAnQZ91wmMc6rO2dUmqdOBI-A19fLMTAOrvpaBrTP9o5QR0UGOcv/w400-h70/36.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Negative Test case: InValid User</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Trigger SAP CI API from postman with Application ID in header:</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDNj4RKhqAMGfG8mPQu113dP_2smRVZ8wB8ik0270LOtacB3jkCIILrzxP2kGzw7xTjLSNIBgGT4IA3BOAOHJ-hPq5sq-JgoHZRou60P3_TKxGtFmGV1NutC_nD2Ec1lklmQR7W6gsApCCA4jMDOVQYICT3CCAJjD-9QFdv4A-TDgll2hf3pu6b8SrEx30/s903/37.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="286" data-original-width="903" height="126" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDNj4RKhqAMGfG8mPQu113dP_2smRVZ8wB8ik0270LOtacB3jkCIILrzxP2kGzw7xTjLSNIBgGT4IA3BOAOHJ-hPq5sq-JgoHZRou60P3_TKxGtFmGV1NutC_nD2Ec1lklmQR7W6gsApCCA4jMDOVQYICT3CCAJjD-9QFdv4A-TDgll2hf3pu6b8SrEx30/w400-h126/37.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">The Connectivity service Client ID not received from Value mapping.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Call fails due to invalid Application ID/user.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh00ciSUR6HSnjYDU3LkJEivQliMDZgOLjUQdg9FU2zlD7Ql98EAyXv5tF0yQmRinW1CMuFGeTvlRlL5fsGdx4vUh1M5kifmFnEHLVcLdeBpvOqYBSeM55w32NS-9r8hYUP8zeuINHpV4YULisd_Jg2uuTMWxBGGJvx4h8Jnz2WXNgtLhauSpKBKiLNvAa2/s903/38.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="374" data-original-width="903" height="166" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh00ciSUR6HSnjYDU3LkJEivQliMDZgOLjUQdg9FU2zlD7Ql98EAyXv5tF0yQmRinW1CMuFGeTvlRlL5fsGdx4vUh1M5kifmFnEHLVcLdeBpvOqYBSeM55w32NS-9r8hYUP8zeuINHpV4YULisd_Jg2uuTMWxBGGJvx4h8Jnz2WXNgtLhauSpKBKiLNvAa2/w400-h166/38.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">HTTP response 401 in postman</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3VeLZQ9mEIK0g5KcK9zqDzGg7g1qe4EDwpg5S3aVcsnQZ4JiGsq6IcKyNCTD4WB97TztUARLW36KYtJssbKL5zWuDyYUHo03cYg-UVAcLyWNu4t1HwHlox3Gf8jtMcXLFbvyQ7MKR7OXMJYbtjwXf1tPH1iITZlLH59fBsDeTf5c_CzCAxsmkvW0mXsVY/s903/39.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" border="0" data-original-height="131" data-original-width="903" height="58" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3VeLZQ9mEIK0g5KcK9zqDzGg7g1qe4EDwpg5S3aVcsnQZ4JiGsq6IcKyNCTD4WB97TztUARLW36KYtJssbKL5zWuDyYUHo03cYg-UVAcLyWNu4t1HwHlox3Gf8jtMcXLFbvyQ7MKR7OXMJYbtjwXf1tPH1iITZlLH59fBsDeTf5c_CzCAxsmkvW0mXsVY/w400-h58/39.jpg" title="Azure APIM TO S4HANA CONNECTIVITY VIA CI (Principal Propagation)" width="400" /></a></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-18622804942535229712024-01-31T12:57:00.002+05:302024-01-31T12:57:22.018+05:30Modeling an advanced Hierarchy with Directory in SAP DatasphereIn our <b><a href="https://www.hanaexam.com/2024/01/modeling-basic-hierarchy-with-directory.html">previous blog</a></b>, we covered the basics of creating a Hierarchy with Directory. Now, we're taking a step further in this blog by enhancing our model with an extra node type, language-dependent texts, and time-dependency, both for the hierarchies and node assignments. These advanced features are often seen in SAP S/4HANA or SAP BW hierarchies but are also applicable to non-SAP hierarchies. We continue to use a simplified data model with local data for clarity, making it easier to grasp these concepts before applying them to more complex, real-world data sources. The additions to the data model are pointed out in Figure 1, with the numbering corresponding to the section numbers in this blog post. The figure shows all views, and each view has a table with data underneath.<span><a name='more'></a></span><div><br /></div><div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRFHytn-4GtgGDhh-8B-DVyfYZlmEns0m1IgPWuKHbFsxsY_m8dA9XxS6yrmQwcXHfoxJ5i63bVydAAKwjHVdULs6kaNN_f3WT-6-3ReczI693_AWdwLIAm5SiCL38HVzcl7mvxO3QUb4Cfwus5Ipc8U-zmh3gRT1aEB2EOqCYj1DEjHb3K9167XA5vUU3/s936/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="524" data-original-width="936" height="224" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRFHytn-4GtgGDhh-8B-DVyfYZlmEns0m1IgPWuKHbFsxsY_m8dA9XxS6yrmQwcXHfoxJ5i63bVydAAKwjHVdULs6kaNN_f3WT-6-3ReczI693_AWdwLIAm5SiCL38HVzcl7mvxO3QUb4Cfwus5Ipc8U-zmh3gRT1aEB2EOqCYj1DEjHb3K9167XA5vUU3/w400-h224/1.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 1: In yellow all extensions to the views of the basic model</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>1. Adding another node type</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Until now, our node types included Product Category (an inner node type) and Product ID (the leaf node type). To demonstrate the use of multiple inner node types within a single hierarchy, we extend the model with a Department node type. The idea is that the company that sells these products, has different departments, each responsible for one or more product categories.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To incorporate this new node type, we'll make the following updates:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Expand the hierarchy table by adding a Department ID</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">2. Insert new entries into the hierarchy table to create a new hierarchy that includes department nodes. We highlight this in Figure 2 with an example, where you can traverse the hierarchy from leaf to root node, starting from the leaf node with Product ID OATMILK_1. The other hierarchies we leave untouched.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3. Add a new entry to the directory table to denote the new Department hierarchy (see Figure 3).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">4. Update the hierarchy view to include the new node type (see Figure 4).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">5. Add a few Product IDs and transactions to the data, to make the data preview richer.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBjIdeKq5_uX_7DzRQ3EwejwE5HsAyxOHn6BPCUM8aHP2w06z7NC7f-Y0oFQL55gqrCltcnwCPvFHFAQDuMu5ZbSbQfkMP7hY3fwaip32ptDJHXY5fEKl8YElXiNTiBGh1by5gaGHMDqkTeSv2M9jYLZ5JnERZa8BUyJjI-P7P_gGwMbsgHFr2KhrSpvl7/s936/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="632" data-original-width="936" height="270" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBjIdeKq5_uX_7DzRQ3EwejwE5HsAyxOHn6BPCUM8aHP2w06z7NC7f-Y0oFQL55gqrCltcnwCPvFHFAQDuMu5ZbSbQfkMP7hY3fwaip32ptDJHXY5fEKl8YElXiNTiBGh1by5gaGHMDqkTeSv2M9jYLZ5JnERZa8BUyJjI-P7P_gGwMbsgHFr2KhrSpvl7/w400-h270/2.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 2: Extending the hierarchy table with a Department ID column and new hierarchy entries</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbrQ7iXaaMWBbb2AodKonLYzlBtzH0p9WQ0MfUk5HCeD_uXxqOIJQQTIkuUtMGHOmbvwUP2KLYsk5YcOyPBIxgSUCe_oZhltYXvy0mEjlIE4jEaIVVABe0eL2Px4_6RsJkY5NQcSK9wRieGBe7rdyh73A6SIeVgNjOuRK1hmJR87lIRAv428WvIumb7_tJ/s636/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="162" data-original-width="636" height="103" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbrQ7iXaaMWBbb2AodKonLYzlBtzH0p9WQ0MfUk5HCeD_uXxqOIJQQTIkuUtMGHOmbvwUP2KLYsk5YcOyPBIxgSUCe_oZhltYXvy0mEjlIE4jEaIVVABe0eL2Px4_6RsJkY5NQcSK9wRieGBe7rdyh73A6SIeVgNjOuRK1hmJR87lIRAv428WvIumb7_tJ/w400-h103/3.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 3: Adding a new record to the Product Hierarchy Directory table</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBKJnM6HtRZhUb_nDYH1Jk-yAZCIerPT2VYLsW0RPd0qWMrn-g-AwpMoomn12BBdaKUnWZBe_lvjUS32WevXtOwOilpNOtP2faKi7xb-45dmI6nWKp-T2vL6yZa0KbS_AXXrN_HI_5QTDWi80rfGcxDpfjS5XR1cdG7g57j1kDmrL_-ceJ5NncBvDmgG_O/s936/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="730" data-original-width="936" height="313" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBKJnM6HtRZhUb_nDYH1Jk-yAZCIerPT2VYLsW0RPd0qWMrn-g-AwpMoomn12BBdaKUnWZBe_lvjUS32WevXtOwOilpNOtP2faKi7xb-45dmI6nWKp-T2vL6yZa0KbS_AXXrN_HI_5QTDWi80rfGcxDpfjS5XR1cdG7g57j1kDmrL_-ceJ5NncBvDmgG_O/w400-h313/4.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 4: Adding node type definition for Department in the Hierarchy view</div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">A new data preview shows then the new grouping into departments.</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjRdHxKIH-5n3faxhO7KQIl3Bq1Uh7KNWaFzcnsNE7ZHkFpLJB6JRs2gGB09w9AUDkCzkWhzrIx_pT7EPpQajwwPeyXTcPn70vd5RAqiHyKIG7XmY0vuee6roKNimJBihDchu9nuIoslJXcc09F6jksYa7l3Xxvk1sGYNKVdStHBLFGZiCCuadR6cUrCeoA/s720/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="688" data-original-width="720" height="383" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjRdHxKIH-5n3faxhO7KQIl3Bq1Uh7KNWaFzcnsNE7ZHkFpLJB6JRs2gGB09w9AUDkCzkWhzrIx_pT7EPpQajwwPeyXTcPn70vd5RAqiHyKIG7XmY0vuee6roKNimJBihDchu9nuIoslJXcc09F6jksYa7l3Xxvk1sGYNKVdStHBLFGZiCCuadR6cUrCeoA/w400-h383/5.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 5: OATMILK_1 now rolling up into Product Categories, and then into the new node type Department</div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>2. Adding dimensions with language-dependent texts to node types</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Previously, our inner nodes Product Category ID and Department ID were only defined as just text-based columns. However, these are perfect candidates to be defined as Dimensions. Once associated to the Hierarchy, you can utilize dimension features like text labels, language-dependent texts, and/or time-dependent texts, which are typical in SAP S/4HANA and SAP BW hierarchies.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To illustrate this, we created a Product Category dimension with language-dependent texts. The screenshot below illustrates the required new objects and their association with the Product Hierarchy.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgUJTk0xxsBjlSRJcxgIQ41LrU-Joxd693PUVuQsT3KN8sPUyDZygwdi-YMX62VLs_IzWK_us5cuO9-Q_3yE7jnDFYdAJo6XjdjeOJlxY7jH5_sK3QHm7ojVwXTpIIqK2zgl6vsB-BIqSXTwKYqjQ4z6ehnXZGTNH4S7YUzD8At6uvFu3Q60ORaBmFQPeyu/s936/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="380" data-original-width="936" height="163" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgUJTk0xxsBjlSRJcxgIQ41LrU-Joxd693PUVuQsT3KN8sPUyDZygwdi-YMX62VLs_IzWK_us5cuO9-Q_3yE7jnDFYdAJo6XjdjeOJlxY7jH5_sK3QHm7ojVwXTpIIqK2zgl6vsB-BIqSXTwKYqjQ4z6ehnXZGTNH4S7YUzD8At6uvFu3Q60ORaBmFQPeyu/w400-h163/6.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 6: New objects for Product Category dimension with language-dependent texts</div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">The following steps describe these changes in more detail:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Create a Product Category text table with columns for Language and Text.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">2. Add sample data to the table. We fill the table for language English (EN) and Dutch (NL) (see Figure 7).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3. Create a Product Category Text view with semantics configured for language and label (see Figure 8).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">4. Create Product Category table with key entries.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">5. Create a Product Category dimension view, consuming the table, with an association to the text view (see Figure 9).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">6. Create an association from the hierarchy view to the new dimension.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgWFl9KsDvlmu2P7UlMsS3gFuDZ85WrUjWtbRO5mgc6oDSggoTRxUyvwOs3QtDV1ARceneY_xV1Sci-4tITO2-Q8498ZOyjWFVTbO8mXo-4Xa_tGaBuPkj_ei2Ds_ttLOHRwWQm__nS_IbMa17qqQyDUlrMdwdq3ziAlcvkAbrDTTgxVWxrpCoXp7l7HCWZ/s936/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="440" data-original-width="936" height="188" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgWFl9KsDvlmu2P7UlMsS3gFuDZ85WrUjWtbRO5mgc6oDSggoTRxUyvwOs3QtDV1ARceneY_xV1Sci-4tITO2-Q8498ZOyjWFVTbO8mXo-4Xa_tGaBuPkj_ei2Ds_ttLOHRwWQm__nS_IbMa17qqQyDUlrMdwdq3ziAlcvkAbrDTTgxVWxrpCoXp7l7HCWZ/w400-h188/7.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 7: Sample data for Product Category text table</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5cgg1bq8rf5KMpPfF2MVLyonkJ_ibsY5isu_mn2MQkm99pve0_aFZdhbNXIngW5MP0CpqPcZRCEYnCbitTzlRcX0foXQvD6M0jr7jyinXXKCE8rypM4jJ9CtaXZGriFBNHl1pg6Fb_8r-MWVydnrbItNknbQuGHgmdhWK85yhOlRq1VRSDDSnDJyRPGZ3/s936/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="408" data-original-width="936" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5cgg1bq8rf5KMpPfF2MVLyonkJ_ibsY5isu_mn2MQkm99pve0_aFZdhbNXIngW5MP0CpqPcZRCEYnCbitTzlRcX0foXQvD6M0jr7jyinXXKCE8rypM4jJ9CtaXZGriFBNHl1pg6Fb_8r-MWVydnrbItNknbQuGHgmdhWK85yhOlRq1VRSDDSnDJyRPGZ3/w400-h174/8.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 8: Semantics definition for the Product Category text view</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiYbrMm555IxoVCFHe__Cba0i4BCDjiJtGd7le8fSXpruvf57JWzqmFX1hO7tV4zzuZfqDpjK_uPIjQrWdBMsaecUOEqnu6ykM2I2EOcKzlLUFRPGuXifcQN6VYUxYVIgPbetazQLyratysByV111r9LkJp0wotnmN5Wu4i3EdxS8-3_5LS9Cu_VTXzHXxW/s936/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="666" data-original-width="936" height="285" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiYbrMm555IxoVCFHe__Cba0i4BCDjiJtGd7le8fSXpruvf57JWzqmFX1hO7tV4zzuZfqDpjK_uPIjQrWdBMsaecUOEqnu6ykM2I2EOcKzlLUFRPGuXifcQN6VYUxYVIgPbetazQLyratysByV111r9LkJp0wotnmN5Wu4i3EdxS8-3_5LS9Cu_VTXzHXxW/w400-h285/9.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 9: The Product Category dimension view</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">When refreshing the data preview of the Analytic Model, you now have the option to display either the ID, the Descriptions, or both (Figure 10), after which the more readable labels show up for the product Category nodes (Figure 11).</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQnwB98GUYi0O0ay7-Oe3rwiJpy3n_N9yugUFx4UJSEEs5rbV2xEvwlry5OP-2Yl-xajsuG2A8OOBskuiWT75qk5xx2PaYdwk6BVO4voDRi9IUi-lMtqPkb3ZOaEKYJd_F8NxwBcsgbHSOW-fT5yzbnTmPDCeb736wmNWpbfxpFEVplTEXAHylqVdkf6hy/s720/10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="544" data-original-width="720" height="303" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQnwB98GUYi0O0ay7-Oe3rwiJpy3n_N9yugUFx4UJSEEs5rbV2xEvwlry5OP-2Yl-xajsuG2A8OOBskuiWT75qk5xx2PaYdwk6BVO4voDRi9IUi-lMtqPkb3ZOaEKYJd_F8NxwBcsgbHSOW-fT5yzbnTmPDCeb736wmNWpbfxpFEVplTEXAHylqVdkf6hy/w400-h303/10.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 10: Choosing ID, Description or both as the presentation mode</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtDN215zsOAhP8fT6cW4fXFPnGrDLvXw5IbOs5vFkJPQBDjAcQZlBCCCD7KYSiOhJi9RgDwIbkVfjY6VOiFiGjP5iAX2Qlwl_MvEvaV9JOJRiJhMaLMxvdiMlbsPq1itJ2ROJpeqwrp-BPic1_BjOfapmXz-ohN7ViZ4nKoPw5O-6jLBC43SjjhuSMdfRq/s688/11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="688" data-original-width="462" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtDN215zsOAhP8fT6cW4fXFPnGrDLvXw5IbOs5vFkJPQBDjAcQZlBCCCD7KYSiOhJi9RgDwIbkVfjY6VOiFiGjP5iAX2Qlwl_MvEvaV9JOJRiJhMaLMxvdiMlbsPq1itJ2ROJpeqwrp-BPic1_BjOfapmXz-ohN7ViZ4nKoPw5O-6jLBC43SjjhuSMdfRq/w269-h400/11.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="269" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 11: Product Category texts are now displayed</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Because we created a dimension with language-dependent texts, we can now switch the data language in the SAP Datasphere setting menu. In below screenshots, you can see that we change the language to Dutch, after which the Product Category nodes show the Dutch translation.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg1iLoGqDWAurx8NLcWhPzKYdOzE-4sWqy1qZldKmyGvAkkXLm4eXQkUwjDymk4eVJcRc6vjJAC8Ct_5PCbBQSkg0Vw9DRc62b03dsG1Daapf8Q6vrehWJcoi-oAwGb4BYJpfpPriHqzQ7o7U3c8uaNOWOsiBvw9riClrP-GDD3Bpl6MSrgRbRoWd786jnJ/s936/12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="750" data-original-width="936" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg1iLoGqDWAurx8NLcWhPzKYdOzE-4sWqy1qZldKmyGvAkkXLm4eXQkUwjDymk4eVJcRc6vjJAC8Ct_5PCbBQSkg0Vw9DRc62b03dsG1Daapf8Q6vrehWJcoi-oAwGb4BYJpfpPriHqzQ7o7U3c8uaNOWOsiBvw9riClrP-GDD3Bpl6MSrgRbRoWd786jnJ/w400-h320/12.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 12: Changing the Data Access Language</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiLntZQ5xAUpElY9GixnZVlyiPQiKZ5B5IxVwAV_v4jPd3NUpRzT-03lCwHeyaAShBT9UQniX6t7BlM9hUh8eRLcJZA95KlqVK_9B_FwuIoFwSO0DHJ0LWqlydrdAQhqSR-FjYH9kOX4Jf0g3IUKpkxQShlfTMTlsNB7oLKp7QZc0xI_LoAcNRPjn9YUcbI/s704/13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="704" data-original-width="512" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiLntZQ5xAUpElY9GixnZVlyiPQiKZ5B5IxVwAV_v4jPd3NUpRzT-03lCwHeyaAShBT9UQniX6t7BlM9hUh8eRLcJZA95KlqVK_9B_FwuIoFwSO0DHJ0LWqlydrdAQhqSR-FjYH9kOX4Jf0g3IUKpkxQShlfTMTlsNB7oLKp7QZc0xI_LoAcNRPjn9YUcbI/w291-h400/13.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="291" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 13: Product Category texts are now displayed in Dutch</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">We repeated the same exercise for Department by creating a new dimension with language-dependent texts and extended the Product dimension by adding language-dependent texts. The result is shown in below screenshot. Please note that to display the texts for leaf nodes, like our Product node, you don’t need to create an association from the hierarchy to the dimension. The existing association from the product dimension to the hierarchy is adequate. For inner nodes this is different, and you will have to create associations from the hierarchy to the dimension.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPx1kL57DltgbxZF1g_IGQrVwc5rQYxPjBZAa8tosG33exA9FjiTKQJ71WDtpLj98kCI6eePDha6AQ3lKXgX4pWoRKdXh2fML6ShuM4GRwMZ-CgbjmcBAREmDygHacTth4JFcXA13bsCuQHR7spSmEQ5zQPO_a52XU7xBNEoPP7Fc69-vVROcNC-Uhu-D_/s754/14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="754" data-original-width="574" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPx1kL57DltgbxZF1g_IGQrVwc5rQYxPjBZAa8tosG33exA9FjiTKQJ71WDtpLj98kCI6eePDha6AQ3lKXgX4pWoRKdXh2fML6ShuM4GRwMZ-CgbjmcBAREmDygHacTth4JFcXA13bsCuQHR7spSmEQ5zQPO_a52XU7xBNEoPP7Fc69-vVROcNC-Uhu-D_/w305-h400/14.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="305" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 14: All node types are now associated to dimensions with texts</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Please note that at time of writing, when texts have been added to a dimension, it is not possible anymore to display the technical name of the dimension. When selecting ID as presentation, the Child ID will show up instead. In our data model the Child ID is represented by the field Node ID. How this looks like is illustrated in the screenshot below.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg76qbgyRR_qLNkJeIWa9LVmeHRuhb2yJtQx9iOYHngGk81JREECuzQUUFSS1qb9EHBqZ35BT3J10GH3z-bAqRJo8WOPllpyqz2PaKsEmuV_6FgnuARuYKYUkwOIptAjC3KURwMfolDCYMnqi7xd15iLZoyqQKg39rDPMhfGEKAYMJ5shTozm8LyxfIwBtu/s936/15.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="804" data-original-width="936" height="344" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg76qbgyRR_qLNkJeIWa9LVmeHRuhb2yJtQx9iOYHngGk81JREECuzQUUFSS1qb9EHBqZ35BT3J10GH3z-bAqRJo8WOPllpyqz2PaKsEmuV_6FgnuARuYKYUkwOIptAjC3KURwMfolDCYMnqi7xd15iLZoyqQKg39rDPMhfGEKAYMJ5shTozm8LyxfIwBtu/w400-h344/15.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 15: Presentation mode ID or ID and Description will show the Child field as ID and not the technical name of the dimension</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Adding time-dependency to hierarchies, nodes, and texts</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Time-dependency is a common requirement in SAP S/4HANA and SAP BW hierarchies, manifesting in several ways:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Time-dependency of a hierarchy itself. Determined within the Hierarchy Directory, this aspect decides if and when a hierarchy is available.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">2. Time-dependency of node assignments. Defined in the Hierarchy with Directory view, this determines which node is assigned to a parent node within specific time intervals.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3. Time-dependency of dimension texts. Defined in the Text view using date intervals. While this feature was already accessible, it's now also applicable to a Hierarchy with Directory.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">We’ll run through setting up time-dependency for the hierarchy and node assignments.</div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>3. Time-dependency of hierarchies</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">A hierarchy can be considered active or not, based on an optional time-validity interval. This requires an extension to the previously modeled Product Hierarchy Directory, by adding a Valid From and Valid To field to the Hierarchy Directory table and adjusting the semantics in the Hierarchy Directory view to mark those fields as Business Date From and Business Date To. The below screenshots show the changes we made for the Product Hierarchy Directory table and view.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCLSW5h4Clbz_DsuvbaQGGXb6Dd0GQ2C6eFK3NTgUeqaln-YLHBtfg2y83t7HCam9XgbySroN5b0yNZKCbGgzaUyiduhbjxex1_dApYUr0FvERJbbApts4i9RA5yzohzhEdbjzVvrRaQ6RLK5iegRQuQL6mVYWS9zsKSHjqgRNVw_v_JLn1_Cpq7Tke-zN/s936/16.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="324" data-original-width="936" height="139" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCLSW5h4Clbz_DsuvbaQGGXb6Dd0GQ2C6eFK3NTgUeqaln-YLHBtfg2y83t7HCam9XgbySroN5b0yNZKCbGgzaUyiduhbjxex1_dApYUr0FvERJbbApts4i9RA5yzohzhEdbjzVvrRaQ6RLK5iegRQuQL6mVYWS9zsKSHjqgRNVw_v_JLn1_Cpq7Tke-zN/w400-h139/16.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 16: Adding time-interval fields to the Product Hierarchy Directory</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEirHugrsBWxuBU3EATbff_XnyCORyy6R1MuB55govI8b3ckvSPee-OpJYJ7_6Wq_of0_qwiIEUk8uvRNgkZ2PFi-sGSEGz2tWFcckMN4sUQOoTjOhNfgIFIWpnMlnA1Gf0idA2O3fTHUMqXlRvMfaGnbRovNbDEKcgXZfCORmhCIaCkauGrBoRI47NBkPxI/s936/17.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="156" data-original-width="936" height="66" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEirHugrsBWxuBU3EATbff_XnyCORyy6R1MuB55govI8b3ckvSPee-OpJYJ7_6Wq_of0_qwiIEUk8uvRNgkZ2PFi-sGSEGz2tWFcckMN4sUQOoTjOhNfgIFIWpnMlnA1Gf0idA2O3fTHUMqXlRvMfaGnbRovNbDEKcgXZfCORmhCIaCkauGrBoRI47NBkPxI/w400-h66/17.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 17: Configuring the semantics for the time-intervals in the Hierarchy Directory View</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">After making these changes, we could simply reopen the Analytic Model to use today’s date as the reference date to select active hierarchies. Instead, we add a Reference Date Variable to the Analytic Model, so that we can choose a reference date ourselves. In the below screenshots you can see how we add this date inside the main design screen of the Analytic Model. Then, we open the data preview again, choose January 1, 2024 as the reference date, and see the two hierarchies active at that date when prompted for a hierarchy selection.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDdekgtkZsiorZI8pDclMAdEMtx1iSy7tKy0xmUBxsIzsfaYPqD90kPGXWZmMhL-K6wdNX9epMvGKL9xLOt5cKjOK7im6hbOgv1Rgpl9dpfvuh-36ZEFiv1EblUz_gqxFdCpbHhGLbY9fQ4HjMoyCGNyDJsDmUshV4q-1OkpjV5qYb63au2KfdQKdkR_Ge/s536/18.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="226" data-original-width="536" height="169" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDdekgtkZsiorZI8pDclMAdEMtx1iSy7tKy0xmUBxsIzsfaYPqD90kPGXWZmMhL-K6wdNX9epMvGKL9xLOt5cKjOK7im6hbOgv1Rgpl9dpfvuh-36ZEFiv1EblUz_gqxFdCpbHhGLbY9fQ4HjMoyCGNyDJsDmUshV4q-1OkpjV5qYb63au2KfdQKdkR_Ge/w400-h169/18.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 18: Adding a reference date variable to the Analytic Model</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-2EKyF9yPqotxTqDyswzZM6hGR59WLEKAHPQ656n7ZyoefuWvEnzXli4b8OeP6Ca_g1NGMDA3knn07wJezJKa5utGWEkTAyK6N8V1BlmBXMZ-kkJEifGhiRA_W-tAwE-422NYCJWwMVGzwCqkK-jI6qZl3xohpo5ehm-mWCJnsFOZ5omfNlo0KPGUBmMj/s734/19.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="300" data-original-width="734" height="164" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-2EKyF9yPqotxTqDyswzZM6hGR59WLEKAHPQ656n7ZyoefuWvEnzXli4b8OeP6Ca_g1NGMDA3knn07wJezJKa5utGWEkTAyK6N8V1BlmBXMZ-kkJEifGhiRA_W-tAwE-422NYCJWwMVGzwCqkK-jI6qZl3xohpo5ehm-mWCJnsFOZ5omfNlo0KPGUBmMj/w400-h164/19.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 19: Choosing the reference date when previewing data in the Analytic Model</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhgq5ye6JnAwjlXid-980UMh92Y4clV7RPQeL53xenf7yRaq6YVkxivOQcIKwB0WKX4rPen_SRikoUUSwWMV31gOPl45cZus0ANYNiVrGvwB3MmuN4ZjRDFpC5WPySLz7SqvEOXXH9vyyoIt9sHbFzOAdaFfAePhX-vgpAid_ElTFPKD51_noK5vhnC3c4f/s936/20.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="340" data-original-width="936" height="145" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhgq5ye6JnAwjlXid-980UMh92Y4clV7RPQeL53xenf7yRaq6YVkxivOQcIKwB0WKX4rPen_SRikoUUSwWMV31gOPl45cZus0ANYNiVrGvwB3MmuN4ZjRDFpC5WPySLz7SqvEOXXH9vyyoIt9sHbFzOAdaFfAePhX-vgpAid_ElTFPKD51_noK5vhnC3c4f/w400-h145/20.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 20: The hierarchy selection after providing a 2024 reference date, shows only the two active hierarchies at that point in time</div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>4. Time-dependency of node assignments</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The validity of node assignments works in a similar fashion as for hierarchies themselves. As depicted in the figure below, we’ve extended the Product Hierarchy table and view with a validity interval and added specific dates to the data in the table. We configured the semantics that define the Valid From and Valid To fields as Business Date From and Business Date To, similarly as we did for the directory in Figure 17.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiE0SesMjpHbbYV4bhkgGJB5PPdjL24EtQnSTW9OKc2hT76EtrRbNWvkTyiE8NOXc2UxfxleJb3ZY0m2Y_VQUuu86BMUqKcqn3qhRNy_84REf3DqQJ55IuYKxFUvlgZy3ZP5gw8nCyDs8Wm0vBbh1RCVDLqUhaaPv2T6QdK6MNYBtRaSx7mpAUzI3Y70rtl/s936/21.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="138" data-original-width="936" height="59" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiE0SesMjpHbbYV4bhkgGJB5PPdjL24EtQnSTW9OKc2hT76EtrRbNWvkTyiE8NOXc2UxfxleJb3ZY0m2Y_VQUuu86BMUqKcqn3qhRNy_84REf3DqQJ55IuYKxFUvlgZy3ZP5gw8nCyDs8Wm0vBbh1RCVDLqUhaaPv2T6QdK6MNYBtRaSx7mpAUzI3Y70rtl/w400-h59/21.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 21: Time-interval added to the node assignments in the Product Hierarchy Directory view</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The data illustrates a notable change: the Sports department, initially aligned with the Non-food department until the end of 2023, shifts its association to the Food department starting in 2024. This transition is visible in the data preview for the year 2024, as shown in Figure 22.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_OGjXk91Br64rv1KIywqg0zNYOEL_coMyrAmLAPAJA6iTvO-JCBxcFMrMeQkUqVL46ib-hTtaOkxi2z3S6Pcw62z9XvtsaknEKInX1WV49cvolVlrHjMY4gHh16L9lJJEeJWNm3BnEGBCDO5LdvejFh5T76AhGEOKwAfzJ-f6_viOjAn11HCIOQEwFzwK/s750/22.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="750" data-original-width="568" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_OGjXk91Br64rv1KIywqg0zNYOEL_coMyrAmLAPAJA6iTvO-JCBxcFMrMeQkUqVL46ib-hTtaOkxi2z3S6Pcw62z9XvtsaknEKInX1WV49cvolVlrHjMY4gHh16L9lJJEeJWNm3BnEGBCDO5LdvejFh5T76AhGEOKwAfzJ-f6_viOjAn11HCIOQEwFzwK/w303-h400/22.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="303" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 22: Data preview with selection date January 1, 2024, where the sports departments changed assignment from the Non-food to Food department</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>5. Time-dependency of dimension texts</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">As mentioned before, time-dependency of dimension texts is supported as well for hierarchies and is defined in the Text view using date intervals, just like we outlined already for the time-dependency of hierarchies and hierarchy nodes. Applying the semantics works in the same fashion, by choosing a field for Business Date From and Business Date To. From the previous instructions, you should be able to build this yourself. A sample of the data, with both time-dependent as language-dependent texts, is displayed in the figure below.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1-I7gKR9N3MQqjzSViQ9uXN_wK3js6aI3xpng18qvnyvg7lFQVmX-hcrUBR_8KsJNcJ-AFNPFUquuAe77m3gACAWGX-_Qh81TmxUqRU5XPcA6SZB79Dsu7rx27PBS6UbL-fohPzPHPNnuh9zxUweOynTdBn2_1j6rDFLPoL8A_n47sJ3wOT4MCwvDq4De/s810/23.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling an advanced Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="236" data-original-width="810" height="116" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1-I7gKR9N3MQqjzSViQ9uXN_wK3js6aI3xpng18qvnyvg7lFQVmX-hcrUBR_8KsJNcJ-AFNPFUquuAe77m3gACAWGX-_Qh81TmxUqRU5XPcA6SZB79Dsu7rx27PBS6UbL-fohPzPHPNnuh9zxUweOynTdBn2_1j6rDFLPoL8A_n47sJ3wOT4MCwvDq4De/w400-h116/23.png" title="Modeling an advanced Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 23: Data sample of both language- and time-dependent texts</div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-33267962221782321832024-01-29T14:15:00.003+05:302024-01-29T14:15:20.861+05:30Modeling a basic Hierarchy with Directory in SAP Datasphere<b><a href="https://www.hanaexam.com/2024/01/an-introduction-to-hierarchy-with.html">In the previous blog</a></b>, we provided an overview of the new features introduced with the Hierarchy with Directory. In this blog, we'll guide you through creating a basic Hierarchy with Directory, starting from scratch and progressing to the data preview in an Analytic Model. Our focus is on simplicity, ensuring you grasp the fundamental concepts with minimal complexity. To keep it simple, we use data from local tables, before moving on to data from SAP S/4HANA or SAP BW in future posts. However, the model is complete and comes with a few lines of transaction and master data. In our upcoming blog, we'll enhance the model by introducing advanced elements such as language-dependent texts, additional node types, and time-dependency features.<span><a name='more'></a></span><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiufgAxuvMglpWmYUmylT-fy32ekHkPzJr8MnNtEiWaXVmcIQ_goo6U2-PvHQKO4I5PIr2dAxGmiA-A972PJANkCQjixi1MxQZvmUiMx0HeLoOJoHs4i08-tmy9FqZgMemkomgLwg2OrsO4rB_mM-kzgV11Mmc43hTiPyPdt5dHfT92sP2xHjvQZ-7RUylq/s436/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="436" data-original-width="434" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiufgAxuvMglpWmYUmylT-fy32ekHkPzJr8MnNtEiWaXVmcIQ_goo6U2-PvHQKO4I5PIr2dAxGmiA-A972PJANkCQjixi1MxQZvmUiMx0HeLoOJoHs4i08-tmy9FqZgMemkomgLwg2OrsO4rB_mM-kzgV11Mmc43hTiPyPdt5dHfT92sP2xHjvQZ-7RUylq/w399-h400/1.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="399" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 1: One of the hierarchies created in this blog post</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>The data model in its most basic form</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Our model showcases product sales within a product hierarchy. For this, we need to create at least four different views, as illustrated in Figure 2. We need views of the following Semantic Usage:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Fact (Transactions), with transactions of products sold.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">2. Dimension (Product), that lists the unique product instances.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3. Hierarchy with Directory (Product Hierarchy), which contains the parent-child relationships between the hierarchy nodes, and the definition of all hierarchy semantics.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">4. Hierarchy Directory (Product Hierarchy Directory), which lists all the hierarchies.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The figure below shows the associations between these four views, and the minimal column set that we need for the hierarchy to function. Each of the views need a data set underneath, which we provide using local tables and in which we entered manually a few records. Missing in the figure is the Analytic Model. We will need it when previewing the data, but for now we just want to focus on the core elements needed.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg42MsiX35Qw4NCJlFvmUElAJTpkJO9Bra55sYpHbxaXMc2BSEUjMJcm9vCWu7OTcay9VMLMs5D8l7jQUf700iuxvz4u6BnpxWzIv_hm_E0EbLEpf7oIMC11CnvtPlZ9Y1TSJupqMXtHe39nKpnj81UHMXL81tVV4ZHuMvpDjW3m1SXeykl2-SAKTYrv6US/s936/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="382" data-original-width="936" height="164" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg42MsiX35Qw4NCJlFvmUElAJTpkJO9Bra55sYpHbxaXMc2BSEUjMJcm9vCWu7OTcay9VMLMs5D8l7jQUf700iuxvz4u6BnpxWzIv_hm_E0EbLEpf7oIMC11CnvtPlZ9Y1TSJupqMXtHe39nKpnj81UHMXL81tVV4ZHuMvpDjW3m1SXeykl2-SAKTYrv6US/w400-h164/2.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 2: Minimum set of objects to showcase a Hierarchy with Directory</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>The sample data</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Each view reads from a local table with a few sample records. Figure 3 lists our sales transactions. Yes, we know, nine records are nothing close to reality, but it serves its purpose.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilqVn3H8z9My4yGE_Eh8wUc-HN3z7xqtOz498HPaVtchZYd2C_3EyoEepkdfnI7n4nW7nFMFiNM4h5wtNltVSn4dKTf0JEUlDQmVMqMzEff6BRjaJsgoOzPbIsuOUpmT5zzhB1vRy7g-kt97l6UgTBKbTI3BaBAzC9nsOVCVLLc8qljpYOHMQDa7swRj1u/s526/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="416" data-original-width="526" height="316" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilqVn3H8z9My4yGE_Eh8wUc-HN3z7xqtOz498HPaVtchZYd2C_3EyoEepkdfnI7n4nW7nFMFiNM4h5wtNltVSn4dKTf0JEUlDQmVMqMzEff6BRjaJsgoOzPbIsuOUpmT5zzhB1vRy7g-kt97l6UgTBKbTI3BaBAzC9nsOVCVLLc8qljpYOHMQDa7swRj1u/w400-h316/3.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 3: Sample transaction data of product sales</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Figure 4 lists the unique Product IDs. Usually, a product dimension would have all kinds of master data, but again, we keep it as simple as possible and therefore this table has just one column.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh0aLWgRJO3dns9tvrbrKxaG_lAUvGV-7j9_sS3Z4xNu8b8hyphenhyphenXZ98MDXb5we38oCdIUAbYb5HRJRrJDR9_t0UBdYm1Yphdf5XMhFx1-FxI2_D-Kv8ttSxnC9AMJ2wtXZClw3I292WIyrB2NlGQXQFa4I9U_v3a86LR4St4ppMFH4AArki9Ow39jRuuxDvj8/s282/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="282" data-original-width="164" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh0aLWgRJO3dns9tvrbrKxaG_lAUvGV-7j9_sS3Z4xNu8b8hyphenhyphenXZ98MDXb5we38oCdIUAbYb5HRJRrJDR9_t0UBdYm1Yphdf5XMhFx1-FxI2_D-Kv8ttSxnC9AMJ2wtXZClw3I292WIyrB2NlGQXQFa4I9U_v3a86LR4St4ppMFH4AArki9Ow39jRuuxDvj8/s16000/4.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 4: Minimal data set for Product dimension</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In this blog we will work with two data-driven hierarchies, which means that we add two entries to the Product Hierarchy Directory as displayed in Figure 5. If S/4HANA would be your source, you might have many more of these entries, with additional semantics such as date validity intervals. We come back on those additional semantics in the next post.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZO8RUArneqHtyI7fX0KilcRyU4Jh8IJpTN5pINQa7y_HRyu6ey4oqwtosVHnqLjb-L9Et4j4-DmLnJ8w0Qc8atVHI4zm-hXkd1ekRcFW_kZBw6fTBxyPVrhLDoF1trTbx9c0zoZy-vW-lXR8XJfALqePGdHKJrtyHeK-zNaY4-c5ar4VI6D3w7zWtwGL9/s632/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="128" data-original-width="632" height="81" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZO8RUArneqHtyI7fX0KilcRyU4Jh8IJpTN5pINQa7y_HRyu6ey4oqwtosVHnqLjb-L9Et4j4-DmLnJ8w0Qc8atVHI4zm-hXkd1ekRcFW_kZBw6fTBxyPVrhLDoF1trTbx9c0zoZy-vW-lXR8XJfALqePGdHKJrtyHeK-zNaY4-c5ar4VI6D3w7zWtwGL9/w400-h81/5.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 5: Minimal form of a Hierarchy Directory with two entries</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Figure 6 illustrates the hierarchy's sample data, detailing the parent-child node relationships for our two hierarchies. The data here is already organized according to how the Hierarchy with Directory will consume it, as we will see later.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">It is important to understand that there are two keys at play here:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>One key specifies the parent-child relationship. In our data model, this is field Node ID. It is the child of the parent-child relationship.</li><li>A second key to identify the respective node’s real In our data model, this is Product ID or Product Category ID. The Node Type field determines which of the two keys should be considered. Later, we will see that dimensions can be associated to this key, making them in fact dimension keys.</li></ul></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Study the below sample data, and take note of how a single product, like OATMILK_1, is categorized differently across two hierarchies, marked respectively green and purple. In the green hierarchy, called DRINKS_OR_NOT, the leaf node is of Node Type PRODUCT. Therefore, the Product ID determines the real key, OATMILK_1. In this hierarchy table its Node ID, the child, is 4. Its parent is Node ID 0, and as you can see, for that node the Node Type is PRODUCT_CATEGORY, and the real key therefore is Product Category ID.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEisrnJre7OJICCD8JrRdoO999Ehz8LfPiVb1o7DHxtMqwprPrXzgS3jkcHaxWW3k_9JWtA_985BN-vP4Mjsc9ww6-rptS95r4Spw5Dl-ZEnPqcN4pB8cpB1mgq9LzoMKFsATSz_7kpY6JQqNZ1aZ4FlNUInb0P975qcs5qeCG5fjIbo7QZQF7Ys_pJqsRla/s936/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="672" data-original-width="936" height="288" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEisrnJre7OJICCD8JrRdoO999Ehz8LfPiVb1o7DHxtMqwprPrXzgS3jkcHaxWW3k_9JWtA_985BN-vP4Mjsc9ww6-rptS95r4Spw5Dl-ZEnPqcN4pB8cpB1mgq9LzoMKFsATSz_7kpY6JQqNZ1aZ4FlNUInb0P975qcs5qeCG5fjIbo7QZQF7Ys_pJqsRla/w400-h288/6.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 6: The hierarchy node relationships for two different hierarchies</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b><br /></b></div><h3 style="clear: both; text-align: left;"><b>The views</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Finally, it is time to put the semantics in place by creating the views. The Transactions view is of type Fact, and the Product view is of type Dimension. We’re assuming no further explanation is needed on those views, so we continue here with the final two views.</div><div class="separator" style="clear: both;"><b><br /></b></div><h3 style="clear: both; text-align: left;"><b>Hierarchy Directory</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The hierarchy directory is, at its most basic, just a list of the different hierarchies with a label, modeled as a dimension. The dimension requires a key field and a label field. In our case this is Hierarchy Name and Hierarchy Label. You can choose the names of the field yourselves, but this dimension will always at least a key and a label field. Make sure the label field is configured as Text and assigned to the Hierarchy Name field, as you can see in Figure 7. This label will show up in our reporting tool when we want to select the active hierarchy.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">We create this directory dimension first, because we will need to refer to it when we build the hierarchy view.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlSBghb2uxrS0FiMOqDzZKYGLKDkOnKc0V1qsPfZrF3pE2BtNLs7eK2kfA5J7xgGYYvr9putDWKUaI2UwSptRtWJO7LldMdsOhnRq_-qWaRrG8sY9dAxslXSJd7wmaYyE1jmCK-PQybXUHRa7fRfcbAzK710B-8Ahr_NeF3pGEwI8302wLPJj3yiNyb40S/s936/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="138" data-original-width="936" height="59" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlSBghb2uxrS0FiMOqDzZKYGLKDkOnKc0V1qsPfZrF3pE2BtNLs7eK2kfA5J7xgGYYvr9putDWKUaI2UwSptRtWJO7LldMdsOhnRq_-qWaRrG8sY9dAxslXSJd7wmaYyE1jmCK-PQybXUHRa7fRfcbAzK710B-8Ahr_NeF3pGEwI8302wLPJj3yiNyb40S/w400-h59/7.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 7: Column semantics for Product Hierarchy Directory</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>The Hierarchy with Directory</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">And then it is time for the hierarchy itself, for which we follow these steps:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Create a view with “Hierarchy with Directory” as its Semantic Usage. In below figure you can see that we are using a SQL view, but you can use a graphical view as well.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">2. Consume the table with the parent-child relationships, in our case LT_NODES, of which the content was shown in Figure 6.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3. Create an association to the Product Hierarchy Directory between the Hierarchy Name field from the hierarchy itself to the hierarchy directory.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">4. Choose “Hierarchy with Directory Settings” as you can see in Figure 8. This opens up the settings dialog.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiLak57JehH9gVvLag447d23hY0T8Tz1jfn5s2BGHbm0-8kA6ppNGCz1OuDWjuF3t3xpiiZNVX4IEI3pcHea32HPmqiC-dD0pLV4uCpw7OiJhbb1AYxRYkP9uZbS0BBommGqLB9ht0AZRexLuLqAMck_DM0AFEUSnE4TBjWRMMTEz3UOClfhmu2ow8CyTxp/s936/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="558" data-original-width="936" height="239" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiLak57JehH9gVvLag447d23hY0T8Tz1jfn5s2BGHbm0-8kA6ppNGCz1OuDWjuF3t3xpiiZNVX4IEI3pcHea32HPmqiC-dD0pLV4uCpw7OiJhbb1AYxRYkP9uZbS0BBommGqLB9ht0AZRexLuLqAMck_DM0AFEUSnE4TBjWRMMTEz3UOClfhmu2ow8CyTxp/w400-h239/8.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 8: Selecting the settings for the Product Hierarchy</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In the settings dialog we do the following, according to the numbering in Figure 9:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Choose the parent field.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">2. Choose the child field.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3. Choose the Hierarchy Name column, which should be the column from which we created an association to the Product Directory View.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">4. The Hierarchy Directory Entity should now be displayed automatically.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">5. Choose the column that defines the Node Type.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">6. Our leaf node is of node type value PRODUCT, so we manually enter that value here.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">7. We choose the column that the Product ID is in. This will be the column showing up later as the node value.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">8. Choose “Set as Leaf” if not already set.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiacXWcOXe9ualiaRaUfs12eFeURjn5VLz9_xmXlVnHqSzbtIqimh2EpHPFrBnI1iV0LKXqmihhOW_1h5VM4veP2GQWdpDu-bLcbLa8GJCn5PgRu5KrRIbKwDku1vSLeYZ7weL64DEudsp3fvTa_lyz9Yv_Zy8pu-Eie7xIa6Ca6-YrMw2CU8oWBfh7UGd_/s936/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="726" data-original-width="936" height="310" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiacXWcOXe9ualiaRaUfs12eFeURjn5VLz9_xmXlVnHqSzbtIqimh2EpHPFrBnI1iV0LKXqmihhOW_1h5VM4veP2GQWdpDu-bLcbLa8GJCn5PgRu5KrRIbKwDku1vSLeYZ7weL64DEudsp3fvTa_lyz9Yv_Zy8pu-Eie7xIa6Ca6-YrMw2CU8oWBfh7UGd_/w400-h310/9.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Figure 9: The Hierarchy with Directory settings</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">9. Add another Node Type Value by clicking the “+” sign.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">10. Enter the Node Type Value</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">11. Choose Product Category ID as the Node Type Value</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwEcXWV7Mldv1tqOlhdPXCca0ucrTWxU6aYc0qZ5h-Kix5_A6bC7mW5GUJ6t6hmmbKrpYkivfEOxJguxEa_VqnnMWdhhlxxJR2zMK9tpPbkn20d9F8GBkU72UVHuaY_EkZlT0ST3OGvMpk96STUUvE4135ttmZ-Yz_bjIERA1_yUxlRVac5aD4XJtbFs3m/s936/10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="732" data-original-width="936" height="313" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwEcXWV7Mldv1tqOlhdPXCca0ucrTWxU6aYc0qZ5h-Kix5_A6bC7mW5GUJ6t6hmmbKrpYkivfEOxJguxEa_VqnnMWdhhlxxJR2zMK9tpPbkn20d9F8GBkU72UVHuaY_EkZlT0ST3OGvMpk96STUUvE4135ttmZ-Yz_bjIERA1_yUxlRVac5aD4XJtbFs3m/w400-h313/10.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 10: Adding the Product Category node type value</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">As you can see, it is also possible to add multiple columns to define the target fields for a node type. This allows you to use compound keys, which you will need for certain S/4 or BW hierarchies.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">That’s it for configuring the Product Hierarchy view. After deploying the Product Hierarchy, go to the Product dimension, and create an association of type Hierarchy with Directory to the Product Hierarchy view.</div><div class="separator" style="clear: both;"><b><br /></b></div><h3 style="clear: both; text-align: left;"><b>The Analytic Model</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To preview the transactions as part of the hierarchy, we need an Analytic Model to consume the created objects. This is straightforward:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Create a new Analytic Model, and drag the Transaction view in.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">2. Import the associations when you are prompted for it.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3. Select Amount as the required measure.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">This is all you need to do before previewing the data. Even when you’re just playing around, it’s helpful to save and deploy the Analytic Model. In general, whenever you make changes to any of the objects and you want to make sure all changes are properly propagated, just redeploy the Analytic Model. This will redeploy all related objects and ensure that the Analytic Model is aware of your change.</div><div class="separator" style="clear: both;"><b><br /></b></div><h3 style="clear: both; text-align: left;"><b>Data preview</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">To view your data in the Analytic Model, we simply follow these steps:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. Choose Preview to go to the preview screen.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">2. Insert Product ID into the rows, creating a straightforward list of sales per product.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">3. As outlined in Figure 11, hover over the Product ID entry in the Rows section, then choose Hierarchy, and then choose Select Hierarchy. A dialog pops up to choose the hierarchy (see Figure 12).</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">4. Change the display format to Description as shown in Figure 13, which will showcase the node text rather than the node ID.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">5. Take a moment to appreciate the final display.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgXMr_0YZeWPBcwIGviTKL2DihQxNPvsQBt9-aSoW_bcvdOfjPOs9bVV83zMwGaLMImgI2C-zlbiQLUIoMutd6LRFr23AxbSn3QtznDZA_RKZFRr36EzDgN_Q1i7iR2wTnzLowU5bN24OjEtQRVzMvgYcBKEkAFF6ZkQFHBEY-ub_Nfpad6Bs4X4hcA66S9/s936/11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="510" data-original-width="936" height="217" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgXMr_0YZeWPBcwIGviTKL2DihQxNPvsQBt9-aSoW_bcvdOfjPOs9bVV83zMwGaLMImgI2C-zlbiQLUIoMutd6LRFr23AxbSn3QtznDZA_RKZFRr36EzDgN_Q1i7iR2wTnzLowU5bN24OjEtQRVzMvgYcBKEkAFF6ZkQFHBEY-ub_Nfpad6Bs4X4hcA66S9/w400-h217/11.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 11: Selection of a hierarchy in data preview of an Analytic Model</span></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiuLRo2KNtPg5nIVJ0gtNqS4d7hoEhurO_YjvLJmyNia5rnHCpDyR8YBbVS0Tw4QTS1x4FzwM17AKpP64RvYb-VYkyVfhTUZ0hoFHap3N30XZ8L9dIIu5lDvLtmSDO0jRTsjtGlV49VHxvIURhKPpeRJWB78OzqehVhoECHjNxcbI5BDj9vUEBQfo4a11lX/s790/12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="342" data-original-width="790" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiuLRo2KNtPg5nIVJ0gtNqS4d7hoEhurO_YjvLJmyNia5rnHCpDyR8YBbVS0Tw4QTS1x4FzwM17AKpP64RvYb-VYkyVfhTUZ0hoFHap3N30XZ8L9dIIu5lDvLtmSDO0jRTsjtGlV49VHxvIURhKPpeRJWB78OzqehVhoECHjNxcbI5BDj9vUEBQfo4a11lX/w400-h174/12.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><div class="separator" style="clear: both;">Figure 12: Hierarchy selection</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjtJTzhkhZIR2pRIeZE6feI6_gzYwJFNJQY1z6BKMXaFjciPtsMMrZKTGYt4wZkh2AGUKVnGVva-WH6Sfsqo9q9dgkSJJnAIWvKtaK5S1zD9tZwJ-w5wXZLua9fX4CHbPxcLpcujhSibGNqMun6xt1cmLu1uIS46Vw9rchm_5oh83d04k92aO6aEyOKbrzA/s620/13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="446" data-original-width="620" height="288" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjtJTzhkhZIR2pRIeZE6feI6_gzYwJFNJQY1z6BKMXaFjciPtsMMrZKTGYt4wZkh2AGUKVnGVva-WH6Sfsqo9q9dgkSJJnAIWvKtaK5S1zD9tZwJ-w5wXZLua9fX4CHbPxcLpcujhSibGNqMun6xt1cmLu1uIS46Vw9rchm_5oh83d04k92aO6aEyOKbrzA/w400-h288/13.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 13: Change the hierarchy display</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Figure 14 and Figure 15 show the same transactions, aggregated in the two different hierarchies. Again, you could have a look at Product ID OATMILK_1 and its assignment according to the data in Figure 6.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgon7jiHZyGTt0MYuEf0gbVa7OVFOjljsDxxsEETlAlw9Vo7XfwQ32pB2ztYWlP6u-_GnGSHhgHBJCah0YNde_NmxGjBb6iHmhU5IlW2tAd4Am-UVD6qfW4tHG6FHtSzXVt_ODP9v5-uBHvQV7JjQOznNUovsb5UfaeYk4HG72k3T0B5LN2DQQAkDnHJD1B/s672/14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="346" data-original-width="672" height="206" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgon7jiHZyGTt0MYuEf0gbVa7OVFOjljsDxxsEETlAlw9Vo7XfwQ32pB2ztYWlP6u-_GnGSHhgHBJCah0YNde_NmxGjBb6iHmhU5IlW2tAd4Am-UVD6qfW4tHG6FHtSzXVt_ODP9v5-uBHvQV7JjQOznNUovsb5UfaeYk4HG72k3T0B5LN2DQQAkDnHJD1B/w400-h206/14.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 14: The Drinks or not hierarchy</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiMufNLE3M6rUgOGKF5fVx2O__hyhnbUcTGtBDduOyW1OaLqQJPTsV-qafIhyphenhyphen18evEJb_x9MU1EY-dlFEApWMzfMjnfE9iGNElbsc9VY0VRzIb6e0VcvNUN7z10nFPQFiE61tuI5B-XZwi6knFKA01FV-D4wpveoNNgy9FcDk9la8JZK0KJkjCAnOKo1lGv/s696/15.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Modeling a basic Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="412" data-original-width="696" height="236" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiMufNLE3M6rUgOGKF5fVx2O__hyhnbUcTGtBDduOyW1OaLqQJPTsV-qafIhyphenhyphen18evEJb_x9MU1EY-dlFEApWMzfMjnfE9iGNElbsc9VY0VRzIb6e0VcvNUN7z10nFPQFiE61tuI5B-XZwi6knFKA01FV-D4wpveoNNgy9FcDk9la8JZK0KJkjCAnOKo1lGv/w400-h236/15.png" title="Modeling a basic Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Figure 15: The More categories hierarchy</div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-29620126992521640582024-01-24T15:14:00.001+05:302024-01-24T15:14:04.210+05:30Field inventory management (FIM) in the Medical Device Industry – Create capitalized assets and fulfill demo requests orders from sales representatives<h3 style="text-align: left;"><b>Introduction:</b></h3><div><br /></div><div>This blog outlines the leading medical device industry business process steps to fulfill a customer request for demo of a capitalized equipment.</div><div><br /></div><div>A customer may request a particular product from your company to be demonstrated and evaluated before making a purchase decision. If the product is of high value, the company may treat the product as an asset when it is used for demo purposes. The below document will explain tracking, logistics support, and accountability of these products when they go out to the field from the company’s premises.<span><a name='more'></a></span></div><div><br /></div><h3 style="text-align: left;"><b>Asset Creation and Categorization</b></h3><div><br /></div><div><b>- Create capitalized assets during receipt into the designated Inventory pool.</b></div><div><br /></div><div>The company policy may set aside a sizable quantity of products for customer demonstration purposes to pursue sales or marketing opportunities. If these products are of high value, we should create a separate pool of inventory inside single or multiple warehouse locations, this should generally be created as valuated Assets in the Fixed Asset ledger, but remain in the company’s inventory at zero value, to avoid double counting in the balance sheet. Products intended for sale are not capitalized.</div><div><br /></div><div>This creation of assets in the system happens at the time of setting aside as a separate pool through the material document posting.</div><div><br /></div><div><b>- Create capitalized assets when the product is sent to the field.</b></div><div><br /></div><div>Due to supply and demand imbalances, companies may not always have a sufficient pool of inventory for demo purposes, in these cases, they may decide to send a product intended for sale to a customer demonstration. When a product intended for sale is sent to the field consigned to a customer for demonstration purposes a valuated asset needs to be created in the fixed asset ledger</div><div><br /></div><div><b>- Tracking & Depreciation</b></div><div><br /></div><div>Maintaining demo products in a separate pool in the warehouse and tracking products sent to the field as consignment for demo purposes enables the tracking of Assets and the posting of depreciation expenses over the life of the Asset while retaining the visibility of inventory in both Pools and Consignment</div><div><br /></div><h3 style="text-align: left;"><b>System Process Steps:</b></h3><div><br /></div><div><b>Create Assets and store them in a dedicated demo pool</b></div><div><br /></div><div>Capitalized assets should be created when goods are received or transferred into the dedicated capitalized inventory pool. This could be achieved either using a standard purchase order, intercompany purchase order, or a transfer posting in S4 Hana. Standard programs may need to be enhanced to achieve this function.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLNyG5GuQNgQC6UAeZDVBCoWPqHTcK3f0JX0O-v_zcxMy1U8t4Hr3wcvwQZThOxyhrpBexI1KhT8Z51RhUuWLFYwPCe2IgfNH2h8SuP82LccDyBZCmlzcGw9s21ijiEhZqx4XB7ANl6LBLXwEywFavHO-6o8_ROTc5mvFZXoIDQqea8-Qqp3xAHi4vSKPJ/s750/SAP%20HANA.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Field inventory management (FIM) in the Medical Device Industry – Create capitalized assets and fulfill demo requests orders from sales representatives" border="0" data-original-height="422" data-original-width="750" height="225" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLNyG5GuQNgQC6UAeZDVBCoWPqHTcK3f0JX0O-v_zcxMy1U8t4Hr3wcvwQZThOxyhrpBexI1KhT8Z51RhUuWLFYwPCe2IgfNH2h8SuP82LccDyBZCmlzcGw9s21ijiEhZqx4XB7ANl6LBLXwEywFavHO-6o8_ROTc5mvFZXoIDQqea8-Qqp3xAHi4vSKPJ/w400-h225/SAP%20HANA.jpg" title="Field inventory management (FIM) in the Medical Device Industry – Create capitalized assets and fulfill demo requests orders from sales representatives" width="400" /></a></div><div style="text-align: center;"><br /></div><div><b>Send a capitalized demo pool of products to customers for demonstration purposes.</b></div><div><br /></div><div>Based on customer demand, the need may arise to demonstrate products at customer premises for sales and marketing purposes. This could be achieved by leveraging the standard S4 Consignment process. The consignment process provides visibility, logistics support, and tracking of assets that leave your company premises but are still owned by the company. When demand comes for a demo product, we should prioritize delivery from the dedicated capitalized inventory pool. Standard programs may need to be enhanced to determine the demo storage location at the time of order entry to perform ATP.</div><div><br /></div><div><b>Send free stock to customers for demonstration purposes.</b></div><div><br /></div><div>As mentioned earlier due to the supply and demand balance we may have to send a free stock which was originally intended for sale for customer demo purposes. In this case, the product needs to be created as a capitalized asset at the time of delivery to the customer. This could be achieved by using a standard consignment process; however, the asset creation would be an enhancement to standard functionality at the time of the post-good issue.</div><div><br /></div><div>Based on order type, order reason, plant, storage location, and movement type in a BRF+ table could help determine when a particular logistics scenario would trigger asset creation and capitalization.</div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-38869804158721939292024-01-22T14:07:00.003+05:302024-01-22T14:07:58.483+05:30Converting Simple Date format to JSON date format with User Defined Functions (UDF)<div>As an SAP Integration Developer working with SAP S/4 HANA API’s with JSON Schema format, I encountered the necessity to adeptly convert simple date formats received from both SAP and non-SAP systems to JSON date format prior posting the payload to SAP S/4 HANA for required operations.</div><div><br /></div><div>In this case, if payload posted to S/4 HANA consists of simple date format (DD/MM/YYYY), it reverts with date-related errors that arise due to unrecognized formats by the system.</div><div><br /></div><div>To address this issue, I couldn’t find an existing guide, prompting me to share my approach with fellow Integration Consultants.<span><a name='more'></a></span></div><div><br /></div><div>Well recognizing the necessity for transformation, I opted to use Groovy script (UDF).</div><div><br /></div><h3 style="text-align: left;"><b>Scenario:</b></h3><div><br /></div><div>Our Integration layer receives data from various SAP as well as Non-SAP systems which requires to be posted to S/4 HANA system via API’s after required conversions based on business requirements.</div><div>The date format present in the data was simple format (i.e. “DD/MM/YYYY”) but S/4 HANA expects it in JSON date format (i.e. “/Date(478321400000)/”).</div><div><br /></div><h3 style="text-align: left;"><b>Resolution:</b></h3><div><br /></div><div>To handle the conversion, I have developed a simple groovy UDF and added it to the message mapping layer of SAP CPI.</div><div><br /></div><div>Steps to follow: </div><div><br /></div><div>1. Create your message mapping structure and select the relevant date fields which requires conversion.</div><div><br /></div><div>2. Select the create Functions tab (highlighted below) for creation of the UDF Groovy script and give it a relevant name. (Note: You can first add the script in references section of Integration flow and assign script from here as well, by clicking on the adjacent icon.)</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg9bN22tuW7D_KE_0UCMTmpUpH_sxZDYiUageIStGrV6yBghrsvcmLWEjME0zxTnqo-iAHSRY4VRB3yiDQoiS-QXRVk4gd4a79q1T8nnywBITE7yLYpuxe6dXSh8-E03vWpDSrWppSDPUx8jVI2Xv7utBv_Sk9FEsbOAo-kDCrkrVpvaePFe71Q0RUvfGF6/s1453/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Converting Simple Date format to JSON date format with User Defined Functions (UDF)" border="0" data-original-height="525" data-original-width="1453" height="145" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg9bN22tuW7D_KE_0UCMTmpUpH_sxZDYiUageIStGrV6yBghrsvcmLWEjME0zxTnqo-iAHSRY4VRB3yiDQoiS-QXRVk4gd4a79q1T8nnywBITE7yLYpuxe6dXSh8-E03vWpDSrWppSDPUx8jVI2Xv7utBv_Sk9FEsbOAo-kDCrkrVpvaePFe71Q0RUvfGF6/w400-h145/1.png" title="Converting Simple Date format to JSON date format with User Defined Functions (UDF)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">After naming, click ok to proceed further. </div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;">3. Paste the following Groovy function.(Note: You don’t need to do any modifications to the script apart from adjusting the date format based on the request payload input accordingly.)</div><div class="separator" style="clear: both;">import com.sap.it.api.mapping.*</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">def String JSONDateFormatting(String datefield) {</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;"> if (datefield && !datefield.isEmpty()) {</div><div class="separator" style="clear: both;"> // adjust simple date format based on input</div><div class="separator" style="clear: both;"> def dateformat = new java.text.SimpleDateFormat("dd/MM/yyyy")</div><div class="separator" style="clear: both;"> def date = dateformat.parse(datefield)</div><div class="separator" style="clear: both;"> def timestamp = date.time</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;"> def jsonDate = "/Date(${timestamp})/"</div><div class="separator" style="clear: both;"> return jsonDate</div><div class="separator" style="clear: both;"> </div><div class="separator" style="clear: both;"> } else {</div><div class="separator" style="clear: both;"> return null</div><div class="separator" style="clear: both;"> }</div><div class="separator" style="clear: both;">}</div><div class="separator" style="clear: both;"></div><div class="separator" style="clear: both;">4. Map the relevant field with the function pallet.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjZ3RsqiZtnrWnpI60Ll1-15O2uAFImS1O1gf1E9K6NkvVO0tsqmgWH9NBIaGtY4TJ5NuQjh0N-V8KipUpctJxxTsajiuUpaHH0v9YcOWv3cTEl4AHgWoqOA4jfRgxhqmctsPhbjdheLkdQ4CtPufH6UhWMh_5KrDfNEJCRMw_gVDBVb_dGSDLkkZZeX-JX/s1393/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Converting Simple Date format to JSON date format with User Defined Functions (UDF)" border="0" data-original-height="406" data-original-width="1393" height="116" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjZ3RsqiZtnrWnpI60Ll1-15O2uAFImS1O1gf1E9K6NkvVO0tsqmgWH9NBIaGtY4TJ5NuQjh0N-V8KipUpctJxxTsajiuUpaHH0v9YcOWv3cTEl4AHgWoqOA4jfRgxhqmctsPhbjdheLkdQ4CtPufH6UhWMh_5KrDfNEJCRMw_gVDBVb_dGSDLkkZZeX-JX/w400-h116/2.png" title="Converting Simple Date format to JSON date format with User Defined Functions (UDF)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Voila, you’re all set!</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Let’s test now to check how things go ahead.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Development Assessments:</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The request payload was triggered from an end system was passed through the message mapping structure for required transformation. </div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">(It’s an XML structure, I have internationally hid rest of the data apart from the date field.)</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiUdysA16wDq6dX_K07ywQMirK3c7_49B5jWp4codI_uwOyGxEwLKWWVhjUsBrVYvxbDGCyN13dHzq1Kb104BTtk-CgAf1t6L9QsN6LHSVX2MRXuqnBY55TrAEklt4NarOiXECUh2P7UX5AUx6zFk4uvAxlu9jvSLrvTCsRd90pgDHfQEcghS9uTcdfeEnz/s1045/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Converting Simple Date format to JSON date format with User Defined Functions (UDF)" border="0" data-original-height="678" data-original-width="1045" height="260" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiUdysA16wDq6dX_K07ywQMirK3c7_49B5jWp4codI_uwOyGxEwLKWWVhjUsBrVYvxbDGCyN13dHzq1Kb104BTtk-CgAf1t6L9QsN6LHSVX2MRXuqnBY55TrAEklt4NarOiXECUh2P7UX5AUx6zFk4uvAxlu9jvSLrvTCsRd90pgDHfQEcghS9uTcdfeEnz/w400-h260/3.png" title="Converting Simple Date format to JSON date format with User Defined Functions (UDF)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Prior to message mapping transformation.</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The date field with simple date format was likewise transformed to JSON date format using the UDF.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjPYYaraHFT7wSol7mqzbrz6cGVL205xD2n-ooPUF0_C0CFQVqwoUKtk6FWQXyTObTuldwdUKVLyHJR1dg8knDOyDUlVxsVOqTl2w50-x2TUwRdcSlKrXm-wgCTnbKZn7Mt8oV4JmKsRJvbIHF2DSdVfqV3T98ApudsXfKQtbgNljhwQ_kuTLP12em4MHfS/s1542/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Converting Simple Date format to JSON date format with User Defined Functions (UDF)" border="0" data-original-height="631" data-original-width="1542" height="164" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjPYYaraHFT7wSol7mqzbrz6cGVL205xD2n-ooPUF0_C0CFQVqwoUKtk6FWQXyTObTuldwdUKVLyHJR1dg8knDOyDUlVxsVOqTl2w50-x2TUwRdcSlKrXm-wgCTnbKZn7Mt8oV4JmKsRJvbIHF2DSdVfqV3T98ApudsXfKQtbgNljhwQ_kuTLP12em4MHfS/w400-h164/4.png" title="Converting Simple Date format to JSON date format with User Defined Functions (UDF)" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">After message mapping transformation.</div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-38202276540420435402024-01-19T13:25:00.000+05:302024-01-19T13:25:22.917+05:30SAP S/4HANA Business Partner – Address Management at Contact Persons<h3 style="text-align: left;"><b>Introduction</b></h3><div><br /></div><div>With introduction of Business Partner at SAP S/4HANA and CVI (Customer-Vendor-Integration) an additional object level in addition to old/known Customer and Contact Person concept has been implemented.</div><div><br /></div><div>Customer Master and Contact Person is using BAS (Business Address Service) for many years by using central address tables. Business Partner is using BAS as well with own address data sets. This makes whole address management complex.<span><a name='more'></a></span></div><div><br /></div><div>With this blog post I would like to bring some light into this topic.</div><div><br /></div><h3 style="text-align: left;"><b>Address Data Model</b></h3><div><br /></div><div>Below picture shows full set of objects and tables which are affected.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsZu575rm-7yDTozt7HSFZsibAwFjRTP-dmcxaQ4lH7Vm5pW2lWSNh1SH3ctnuN1QM_I6Nk-S4eFdTvEp7F8bBJZ0ctpsAdEBEgoQbNkL-Vy2gjBZKFVKf84zbg3n1EwP7r6rPdCxXyHnQsCgLuTpA1Y1PEsB6UYb4h3CpCxlITNCAv9dlCLIYxRgeqlG4/s2734/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP S/4HANA Business Partner – Address Management at Contact Persons" border="0" data-original-height="1240" data-original-width="2734" height="181" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgsZu575rm-7yDTozt7HSFZsibAwFjRTP-dmcxaQ4lH7Vm5pW2lWSNh1SH3ctnuN1QM_I6Nk-S4eFdTvEp7F8bBJZ0ctpsAdEBEgoQbNkL-Vy2gjBZKFVKf84zbg3n1EwP7r6rPdCxXyHnQsCgLuTpA1Y1PEsB6UYb4h3CpCxlITNCAv9dlCLIYxRgeqlG4/w400-h181/1.png" title="SAP S/4HANA Business Partner – Address Management at Contact Persons" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><h3 style="clear: both; text-align: left;"><b>Data Objects</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">As you can see, there are different mater data objects involved.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ol style="text-align: left;"><li>Business Partner</li><li>Business Partner Relationship</li><li>Customer Master</li><li>Contact Person</li></ol></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">I will get into more details now.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Business Partner</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In this case there are 2 Business Partners needed.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ol style="text-align: left;"><li>Business Partner with role FLVN00 or FLVN01 for customer</li><li>Business Partner with general Role 000000 for Contact Person</li></ol></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Business Partner for customer needs at least a customer role. This role will trigger CVI and takes care of synchronization of Business Partner data into “old” customer master.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Business Partner for Contact Person is just a needed object to create Relationship. For this Business Partner it’s enough to enter name and country as a minimum. Country is very important. This will trigger address segment creation at BAS address tables. Contact Person Business Partner has to be Business Partner Type of Person.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Business Partner Relationship</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Business Partner relationship is the connection of two Business Partners. In this case the main Business Partner and Contact Person Business Partner. For Contact Person synchronisation via CVI it is very important to use standard Relationship Type BUR001 – Contact Person Relationship.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Only this Relationship type triggers CVI for Contact Person Synchronization.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Another important point is to assign Company Address (of Customer BP) at Relationship with button</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTACIbqDSRBdkqaOkOtNzoUyPVy7EXMIftCpbloEm1zPGGVO28KCmGQ4xJv_AH9Dkbwyk5m9OdGcOZxpm_SS_1r8DtIBscEtkxjh1jdUOEBTvT9uF8Oi7PCwjP5HVMNY8adTSN367tVofePmOEUD-zT0Rx40FESGIsdvdfZNlzIOM_9P59PGw08s_V-1t7/s280/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP S/4HANA Business Partner – Address Management at Contact Persons" border="0" data-original-height="70" data-original-width="280" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTACIbqDSRBdkqaOkOtNzoUyPVy7EXMIftCpbloEm1zPGGVO28KCmGQ4xJv_AH9Dkbwyk5m9OdGcOZxpm_SS_1r8DtIBscEtkxjh1jdUOEBTvT9uF8Oi7PCwjP5HVMNY8adTSN367tVofePmOEUD-zT0Rx40FESGIsdvdfZNlzIOM_9P59PGw08s_V-1t7/s16000/2.png" title="SAP S/4HANA Business Partner – Address Management at Contact Persons" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Any other data at Relationship detail screen is relationship specific and is synchronized into “old” Contact Person data (table KNVK) by CVI. At conclusion each Contact Person Relationship represents an entry at table KNVK.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Customer Master</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">This is the “old” known Customer Master data at table KNA1, KNVV, KNxx. This data is used in sales processes and is the one and only place where customer role specific data is stored. CVI takes care that shared data like address and bank data is synchronized between Business Partner and Customer Master data.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Contact Person</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">This is the “old” Contact Person data mainly at table KNVK. This data is used in processes and other master data as you are used to in ECC. CVI takes care to synchronize data between Business Partner Relationship and “old” Contact Person data.</div><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>Master Data Tables</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Business Partner</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Following are main tables of Business Partner.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. BUT000 – Main General Business Partner</div><div class="separator" style="clear: both;">2. BUT020 – Business Partner Addresses</div><div class="separator" style="clear: both;">3. BUT021_FS – Business Partner Addresses for Time-Dependent Address Usages</div><div class="separator" style="clear: both;">4. …</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Relationship</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Following are main tables of Business Partner Relationship.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. BUT050 – Business Partner Relationships General Data</div><div class="separator" style="clear: both;">2. BUT052 – Business Partner Relationships Addresses</div><div class="separator" style="clear: both;">3. …</div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>CVI tables</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Following are main tables of CVI.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. CVI_CUST_LINK – Link table for Assignment Between Customer and Business Partner</div><div class="separator" style="clear: both;">2. CVI_CUST_CT_LINK – Link table for assignment of main Business Partner, Contact Person Business Partner and Contact Person (KNVK)</div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>Customer</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Following are main tables of Customer Master Data.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. KNA1 – General Data in Customer Master</div><div class="separator" style="clear: both;">2. KNVV – Customer Master Sales Data</div><div class="separator" style="clear: both;">3. …</div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>Contact Person</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Following are main tables of Contact Person.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. KNVK – Customer Master Contact Partner</div><div class="separator" style="clear: both;">2. …</div><div class="separator" style="clear: both;"><b><br /></b></div><div class="separator" style="clear: both;"><b>Business Address Service (BAS) tables</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">1. ADRC – Addresses (Main Address table)</div><div class="separator" style="clear: both;">2. ADR2, ADR3, … – Address tables for Phone, Fax, eMail, …</div><div class="separator" style="clear: both;">3. ADCP – Person/Address Assignment (Business Address Services)</div><div class="separator" style="clear: both;">4. ADRP – Persons (Data for Persons)</div><div class="separator" style="clear: both;"> </div><h3 style="clear: both; text-align: left;"><b>Data Structure</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Technically there are 5 objects:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Main Business Partner</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjcoYpEz0IguouBKbTeKmcEeQ06tn3wOkf_X8qg1MLRDdghA1BR3fxET3akrXfhfHt2gfE5rAS4flubIeba-jlEfAPxoo68BbRfjxYBHXencVamZ0VeitP0DQoSnu_O0WEwI9fXal-Yv5a3jpolKeDs1hcqvmjeU3OIqr5X0Z-fNXRuPqrCaWjO6icm5Mbp/s1270/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP S/4HANA Business Partner – Address Management at Contact Persons" border="0" data-original-height="292" data-original-width="1270" height="93" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjcoYpEz0IguouBKbTeKmcEeQ06tn3wOkf_X8qg1MLRDdghA1BR3fxET3akrXfhfHt2gfE5rAS4flubIeba-jlEfAPxoo68BbRfjxYBHXencVamZ0VeitP0DQoSnu_O0WEwI9fXal-Yv5a3jpolKeDs1hcqvmjeU3OIqr5X0Z-fNXRuPqrCaWjO6icm5Mbp/w400-h93/3.png" title="SAP S/4HANA Business Partner – Address Management at Contact Persons" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Contact Person Business Partner</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3Kw3tmaCiB-9pJnr2XnhShCXjE7mVlaCbVgfjEp34G55ZyPKhNAC4MDjbWiGMQbBrpel5LNaeGul2y3Qev3LrgKx8Z9RExDS5hpjMYfNBDRQzCMgpJ1il8V7iPaRpP8lCtcQ_awS6gAhOoPX4rjyq5V32_7-vecD9X69uonVg42cvsrx7MNGluGJS03L-/s1292/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP S/4HANA Business Partner – Address Management at Contact Persons" border="0" data-original-height="418" data-original-width="1292" height="130" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3Kw3tmaCiB-9pJnr2XnhShCXjE7mVlaCbVgfjEp34G55ZyPKhNAC4MDjbWiGMQbBrpel5LNaeGul2y3Qev3LrgKx8Z9RExDS5hpjMYfNBDRQzCMgpJ1il8V7iPaRpP8lCtcQ_awS6gAhOoPX4rjyq5V32_7-vecD9X69uonVg42cvsrx7MNGluGJS03L-/w400-h130/4.png" title="SAP S/4HANA Business Partner – Address Management at Contact Persons" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Business Partner Relationship</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiy_DVGsrNUiO7X_G9XkIMVafAT-EZnPHLsHSBTct9qlAD0I10lwbG5ESjKZTHTxXd-sY0H8DcMB2_SYLUxOOSMNbUJO0Onp8n81nr7cMWg5Rfbj-tQKXRai8hjG0RxApOWVLdUXKi4U0k-SOyaeuzV1t6boUC00Odl5wtuFaL3jCih4Xz1hk2x730UYnZk/s1270/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP S/4HANA Business Partner – Address Management at Contact Persons" border="0" data-original-height="362" data-original-width="1270" height="114" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiy_DVGsrNUiO7X_G9XkIMVafAT-EZnPHLsHSBTct9qlAD0I10lwbG5ESjKZTHTxXd-sY0H8DcMB2_SYLUxOOSMNbUJO0Onp8n81nr7cMWg5Rfbj-tQKXRai8hjG0RxApOWVLdUXKi4U0k-SOyaeuzV1t6boUC00Odl5wtuFaL3jCih4Xz1hk2x730UYnZk/w400-h114/5.png" title="SAP S/4HANA Business Partner – Address Management at Contact Persons" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Customer Master</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhvwVQFKWCzsa_GtqKShobgqaQJM7NkhJtT_E7uDKOmZr3LDcLpeQuQI7b066VYhRk3kjuNnUNrUSdPrB0wuyprshusSZYc8bxXZp9YZBvZryEZ7AHyp1SgnlvW-RomWRla7WU19P0NpwE7M4M7PP_6WpZEicBa2fCL5pGKmdxXKQnUqCqqNOhXMqSub47g/s1026/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP S/4HANA Business Partner – Address Management at Contact Persons" border="0" data-original-height="288" data-original-width="1026" height="113" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhvwVQFKWCzsa_GtqKShobgqaQJM7NkhJtT_E7uDKOmZr3LDcLpeQuQI7b066VYhRk3kjuNnUNrUSdPrB0wuyprshusSZYc8bxXZp9YZBvZryEZ7AHyp1SgnlvW-RomWRla7WU19P0NpwE7M4M7PP_6WpZEicBa2fCL5pGKmdxXKQnUqCqqNOhXMqSub47g/w400-h113/6.png" title="SAP S/4HANA Business Partner – Address Management at Contact Persons" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Contact Person</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhScyYJcdyPeWwyjlhPdCGco7PSN-12Ws53QYEJrXhA6z87PTqiBZwkSVzUqdR95Ew9XXvQDW8k_AqrogAGH6F6obnNn6sV1tC8N2jPWCmuMoTyUAxJ10c5Hxbiy8z3ohlg1PuB3YpF0qa_UttDV6mQE6Xv6v6mZUyrv2jzNsN5TEOxAg-WUAJV-ot729Gj/s872/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="SAP S/4HANA Business Partner – Address Management at Contact Persons" border="0" data-original-height="640" data-original-width="872" height="294" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhScyYJcdyPeWwyjlhPdCGco7PSN-12Ws53QYEJrXhA6z87PTqiBZwkSVzUqdR95Ew9XXvQDW8k_AqrogAGH6F6obnNn6sV1tC8N2jPWCmuMoTyUAxJ10c5Hxbiy8z3ohlg1PuB3YpF0qa_UttDV6mQE6Xv6v6mZUyrv2jzNsN5TEOxAg-WUAJV-ot729Gj/w400-h294/7.png" title="SAP S/4HANA Business Partner – Address Management at Contact Persons" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">If a Contact Person has a Business Address maintained an additional address segment (address number at field ADRND) is created beside Contact Person Address segment.</div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-10620779845953603912024-01-17T13:38:00.000+05:302024-01-17T13:38:40.840+05:30An Introduction to Hierarchy with Directory in SAP Datasphere<div>SAP Datasphere has rolled out a much-anticipated feature set with the Hierarchy with Directory. This feature set extends beyond directory capabilities, which we will explore in detail, to a host of other functionalities engineered to integrate smoothly with SAP S/4HANA and <a href="https://www.hanaexam.com/p/sap-hana-ehanaaw17.html"><b>SAP BW hierarchies</b></a>. The outcome is a more efficient experience in modeling these hierarchies within SAP Datasphere, with a richer end-user experience.</div><div><br /></div><div>This blog post kicks off a series dedicated to unpacking the Hierarchy with Directory bit by bit. We begin with an overview of the new features. Following that, we’ll detail the functionality across two posts, starting with constructing a simple data model to represent a product, and then expanding the hierarchy with additional capabilities. This approach ensures you gain a thorough grasp of the hierarchy features, setting the stage for in-depth guides on integrating specific S/4HANA hierarchies such as GL Account, Cost Center, and Profit Center. A screenshot of the end-result of a GL Account Hierarchy is illustrated in Figure 1.<span><a name='more'></a></span></div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEglNVeq1o1S9Rec1EV94VBiF0N4_2tx8aW_6UgstwKpPqF8Dhyphenhyphen86_HHw1jd0uA7mSBAz2YmhgWNeeQucRNnagR-FofYYIjX5N8vJe1NRhikYtRw1yUa-RQQ_DgzTPInl5W_Ap9ZV6yOKgexYf-6DfQAayXcTjsdIq3qzUi0szdi6Mp1-7DvsY7qWb9Cuwsg/s1180/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-1.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="An Introduction to Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="956" data-original-width="1180" height="324" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEglNVeq1o1S9Rec1EV94VBiF0N4_2tx8aW_6UgstwKpPqF8Dhyphenhyphen86_HHw1jd0uA7mSBAz2YmhgWNeeQucRNnagR-FofYYIjX5N8vJe1NRhikYtRw1yUa-RQQ_DgzTPInl5W_Ap9ZV6yOKgexYf-6DfQAayXcTjsdIq3qzUi0szdi6Mp1-7DvsY7qWb9Cuwsg/w400-h324/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-1.jpg" title="An Introduction to Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 1: Screenshot of a GL Account Hierarchy, created as Hierarchy with Directory</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><h3 style="clear: both; text-align: left;"><b>What’s new?</b></h3><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The Hierarchy with Directory is a new Semantic Usage inside a view, just like a Dimension or a Fact can be set as the Semantic Usage. Part of the feature set is configured inside that view, but the full feature set is leveraged by associating other views, such as Dimension or Text views. The below diagram shows an example of the objects required for a minimal data model that leverages a Hierarchy with Directory. The details of this are all explained in this and subsequent blogs.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv-H0ibMjFq8q0cYs0dMjhEQ769Mcf3u6Xxe7RRVrTkMSKqEpMUpLjMtql2p8qD3CWJ73Wcf-SzXpuOp3yMCriIt_9OfszDv7WaAPJbsN1rguSq7ckJJjPjFPXj2sHXnmd9DAQkSK_VOhYSDm0cuRTArhiAVcJYZdtNHHXghyphenhyphenyaVmna5g4nmwbUyyBwCC1/s936/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="An Introduction to Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="382" data-original-width="936" height="164" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv-H0ibMjFq8q0cYs0dMjhEQ769Mcf3u6Xxe7RRVrTkMSKqEpMUpLjMtql2p8qD3CWJ73Wcf-SzXpuOp3yMCriIt_9OfszDv7WaAPJbsN1rguSq7ckJJjPjFPXj2sHXnmd9DAQkSK_VOhYSDm0cuRTArhiAVcJYZdtNHHXghyphenhyphenyaVmna5g4nmwbUyyBwCC1/w400-h164/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-2.png" title="An Introduction to Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 2: The core view types for building a Hierarchy with Directory</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">In the upcoming sections, we’ll briefly discuss the new features. Our next blog explains how these features can be used, using a comprehensive deep-dive. However, to get the most out of it, we suggest familiarizing yourself with the features first.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Please note that the Hierarchy with Directory is a wholly new suite of functionalities. These exist in parallel with, yet separate from, the pre-existing hierarchy modeling features found within a Dimension, or with Semantic Usage Hierarchy.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Data-driven definition of parent-child hierarchies</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">A Hierarchy with Directory is designed to be data-driven. Create the view and its associations once—for instance, for a Product Hierarchy—and it’s ready to manage multiple hierarchies. These are all housed within a single dataset, each with a unique identifier allowing for straightforward selection in a front-end tool. Thus, updating hierarchies is as easy as modifying their underlying data. The directory functions as an index, consolidating all hierarchies in the dataset, akin to SAP S/4HANA and SAP BW practices. As illustrated in Figure 2, a Dimension is linked to the Hierarchy with Directory, acting as the directory itself, with Figure 3 showcasing a couple of example entries from a Product Hierarchy Directory.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHZGdabB3x7evFsqA7K1AgRAo-_vQJijhgnQEXxvnxX1SGAMEpIZfsGiH0SkOT502TBYmU2LSFnW4T1DuJEWChMhyphenhyphenrI5S-P4DUQkfxm_uUHauXM8cXGAegFl5OUTCRFAdd2DlAZt8pTxpd5h-D7MfVsUAaBW25v1K-K8vPC5B30X1gGOMxo1CGPSGAMafr/s572/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="An Introduction to Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="116" data-original-width="572" height="81" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHZGdabB3x7evFsqA7K1AgRAo-_vQJijhgnQEXxvnxX1SGAMEpIZfsGiH0SkOT502TBYmU2LSFnW4T1DuJEWChMhyphenhyphenrI5S-P4DUQkfxm_uUHauXM8cXGAegFl5OUTCRFAdd2DlAZt8pTxpd5h-D7MfVsUAaBW25v1K-K8vPC5B30X1gGOMxo1CGPSGAMafr/w400-h81/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-3.png" title="An Introduction to Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 3: Minimal form of a Hierarchy Directory with two entries</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>External hierarchy</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The Hierarchy with Directory is an external hierarchy. This means that it is independent and self-contained, holding its own data that outlines the node relationships. After its creation, it can be associated to various dimensions, so that any Fact data with those dimensions can be presented in a hierarchy structure. The relations between a Dimension and the Hierarchy with Directory are illustrated in Figure 2.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Nodes of different dimensions within the same hierarchy</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The leaf nodes of a Hierarchy with Directory are always of the type of the dimension that the hierarchy is associated with. For example, in a Product Hierarchy, the leaf nodes are of type product. However, in such a hierarchy, products can be grouped into other dimensions like product category, and these again can be grouped into a responsible department. Defining distinct dimensions for inner nodes is now supported, and Figure 4 provides an example of that.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-yLRtWsYJyX-lVdllgvck2ofq2IR2DCTQOjobBQch1aO4C_8rp9iLeGyDRQbLm00_nFuMrw5Ika7b2h8SFvyWLDpp92VRlpUxDjXW6eCHhWmco-8GakuLOXZanny5ZqC-67Ckync-Cmc_bVGs-dYezaP76MxkXKjz_M9W3ofV08JSHoy54wi3urWEAi_5/s702/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="An Introduction to Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="614" data-original-width="702" height="350" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-yLRtWsYJyX-lVdllgvck2ofq2IR2DCTQOjobBQch1aO4C_8rp9iLeGyDRQbLm00_nFuMrw5Ika7b2h8SFvyWLDpp92VRlpUxDjXW6eCHhWmco-8GakuLOXZanny5ZqC-67Ckync-Cmc_bVGs-dYezaP76MxkXKjz_M9W3ofV08JSHoy54wi3urWEAi_5/w400-h350/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-4.png" title="An Introduction to Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 4: A product hierarchy with different node types</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Language-dependent hierarchy descriptions</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Each hierarchy is defined in a Hierarchy Directory with a name and a label. The label is used for example when end-users choose a hierarchy from a list of available hierarchies. The label can be stored in multiple languages, and simply requires a language key field to be added to the Hierarchy Directory. SAP Datasphere allows you to select a Data Access Language, and based on the language selected in your settings, it will fetch the hierarchy label from the Hierarchy Directory.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-JstCKuwvexrzBUo9IlkrwwW9i7eb9Zme3-G0GTUP4rFvaYd3-J5mDQAyZC9Hj1HCM0jSI5NTGigIzIoFnfDJVWukUMHTJxqJ64UC3ewCj460JQq2n1TresEHxbw28P2t4xQIZ6DWaHJc0x86Mhsp2BfprTEgDdaOL955bqP9GYRIzl5VexamxChSXxhH/s802/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="An Introduction to Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="498" data-original-width="802" height="249" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-JstCKuwvexrzBUo9IlkrwwW9i7eb9Zme3-G0GTUP4rFvaYd3-J5mDQAyZC9Hj1HCM0jSI5NTGigIzIoFnfDJVWukUMHTJxqJ64UC3ewCj460JQq2n1TresEHxbw28P2t4xQIZ6DWaHJc0x86Mhsp2BfprTEgDdaOL955bqP9GYRIzl5VexamxChSXxhH/w400-h249/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-5.png" title="An Introduction to Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 5: Choosing the Data Access Language in SAP Datasphere</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Language-dependent node texts</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Like hierarchy descriptions, node texts now also support multiple languages, for both inner and leaf nodes. This is simply achieved through configuring Dimension views with their corresponding Text views, which is functionality that we already have for some time. What’s new is that once you associate those dimensions to the different node types in your hierarchy, these texts are available in your hierarchy display options as well. Again, if your texts have a language field defined, SAP Datasphere will fetch the language based on your Data Access Language.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhn8oP6ocXJCvOo6sxVcv6cmvnDnl46kIJc6yxE7oBd-8r6lJceRRSya2z75eyfmSIk_Y6o-PMvvOBEw12GMBtI9JC-VcIhH6zS7mqy-Z9xIZATw6IJ8HH8BS4Uypa6gsbm6lxom0FFGJGObBLr2Pr11wLmaLkr0N54CAM7JOKI2e44OAGEtW4vZj1pyRoU/s688/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="An Introduction to Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="346" data-original-width="688" height="201" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhn8oP6ocXJCvOo6sxVcv6cmvnDnl46kIJc6yxE7oBd-8r6lJceRRSya2z75eyfmSIk_Y6o-PMvvOBEw12GMBtI9JC-VcIhH6zS7mqy-Z9xIZATw6IJ8HH8BS4Uypa6gsbm6lxom0FFGJGObBLr2Pr11wLmaLkr0N54CAM7JOKI2e44OAGEtW4vZj1pyRoU/w400-h201/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-6.png" title="An Introduction to Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 6: Language-dependent node texts</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Time-dependent hierarchies</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Hierarchies can be configured for time-dependency, by adding a date validity interval to the Hierarchy Directory. This allows you to deactivate obsolete hierarchies or add hierarchies that only become active from a certain date, such as when a new book year starts. When selecting a hierarchy in the end-user tool, or in the data preview of the Analytic Model, only the hierarchies valid at that time show up. It’s also possible to configure a Reference Date Variable in the Analytic Model, so that the end-user can choose for which date the validity of hierarchies should be determined.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgB__38r8cKW5baz7kFJLLXEZx4RLKXRuZeqyhMhq6m23jUVFLDrFa9-51CMk8aAcvB-WjmGHQDG9c-2sqNZ_I4DiP1xumIxc6EAfoAIAWVd2lB5huE-ub63XaaiahWElfrgGC9b0vf9dqDr-zH4guzPzfWzxRdBOM8eF9i5zECbhUmFZ1FnK4csaVouSYx/s644/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="An Introduction to Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="448" data-original-width="644" height="279" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgB__38r8cKW5baz7kFJLLXEZx4RLKXRuZeqyhMhq6m23jUVFLDrFa9-51CMk8aAcvB-WjmGHQDG9c-2sqNZ_I4DiP1xumIxc6EAfoAIAWVd2lB5huE-ub63XaaiahWElfrgGC9b0vf9dqDr-zH4guzPzfWzxRdBOM8eF9i5zECbhUmFZ1FnK4csaVouSYx/w400-h279/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-7.png" title="An Introduction to Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><div class="separator" style="clear: both;">Figure 7: Choosing a Reference Date, e.g., to determine validity of hierarchies</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEix7cZfW09xgKx6z5Uend0Md7VCmgGp1qiXulGcZU6-upTOa8yKmwj8BKdj5Zoidc4tr7s-onK5opHLrJ3_GpuxG2uOfaEnsadbmhyphenhyphenGPPQPNK_VTx6zmgg0NAmcjAC_IvTLjFb6JCs74zBKEslH6f99dYEyvU6ycnVwJTuRuKnul_NUNZszH4Gw5XJI3A59/s628/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="An Introduction to Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="228" data-original-width="628" height="145" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEix7cZfW09xgKx6z5Uend0Md7VCmgGp1qiXulGcZU6-upTOa8yKmwj8BKdj5Zoidc4tr7s-onK5opHLrJ3_GpuxG2uOfaEnsadbmhyphenhyphenGPPQPNK_VTx6zmgg0NAmcjAC_IvTLjFb6JCs74zBKEslH6f99dYEyvU6ycnVwJTuRuKnul_NUNZszH4Gw5XJI3A59/w400-h145/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-8.png" title="An Introduction to Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 8: An end-user can only choose hierarchies active at that time, or at the set Reference Date</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Time-dependent hierarchy nodes</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The assignment of a child node to its parent node can also be made time-dependent, which for example is typical for employee structures when reporting lines change. The fields required for this are marked in the Product Hierarchy entity in Figure 9.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Time-dependent attributes of associated dimensions are also considered. For example, dimensions can have time-dependent texts. If such dimension is associated to a node type, such as the Product Category Text which is associated to Product Category in Figure 9, then the node text valid at that time, or determined using the Reference Date Variable, is displayed.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh227liOtVrYEdq-ATvLhfuNzYXtiyM8dmuhHy4qf2anxYa8_z9mCiIADMShj6pUzopP25Oi9hT-cv8O7rzAQ6N8ZcZug66gRk_7OGEdanY-pZQJPOsWv-2-iauyiZZF-x5cqJx5IkhQcbIxJUVswMuwZathiAAV7v5tThFiLJkqL7K4GzAQug_-Ip0vac4/s602/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="An Introduction to Hierarchy with Directory in SAP Datasphere" border="0" data-original-height="310" data-original-width="602" height="206" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh227liOtVrYEdq-ATvLhfuNzYXtiyM8dmuhHy4qf2anxYa8_z9mCiIADMShj6pUzopP25Oi9hT-cv8O7rzAQ6N8ZcZug66gRk_7OGEdanY-pZQJPOsWv-2-iauyiZZF-x5cqJx5IkhQcbIxJUVswMuwZathiAAV7v5tThFiLJkqL7K4GzAQug_-Ip0vac4/w400-h206/an-introduction-to-hierarchy-with-directory-in-sap-datasphere-9.png" title="An Introduction to Hierarchy with Directory in SAP Datasphere" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Figure 9: Date validity interval for Child (Node ID) – Parent assignments, and for Hierarchy Node Texts</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Feature differences classic SAP hierarchies</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The sections above have highlighted the new features. Those with a deep understanding of hierarchies in SAP S/4HANA or SAP BW will find these features familiar. Yet, it’s important to note what isn’t included or how these differ from the classic hierarchies. Here are the key distinctions:</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>For texts associated to the hierarchy nodes, you can choose between display of the Child ID or the Text, but you cannot display the technical key of the dimension.</li><li>Dimension values not used as hierarchy nodes won’t appear in the hierarchy; there’s no Unassigned nodes You can manually add these nodes by integrating them from the dimension into a custom unassigned node.</li><li>In SAP Datasphere, each Hierarchy with Directory holds its own data. A Product Hierarchy for example can contain multiple hierarchies, as they are data-driven as discussed before. But there is no central hierarchy table that stores all hierarchies of all different sorts.</li><li>There is no authorization functionality on hierarchy nodes, no sign-reversal functionality, and no support for ordering siblings according to nextid.</li><li>There’s no dedicated hierarchy data preview. Instead, you preview data using the Analytic Model, which necessitates both transaction and dimension data.</li></ul></div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-88058472809122904722024-01-15T14:39:00.005+05:302024-01-15T14:39:57.225+05:30Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA<h3 style="text-align: left;"><b>Introduction:</b></h3><div><br /></div><div>This blog outlines the leading industry business process steps to deliver critical medical instruments and consumables for surgery at the hospital promptly providing tracking and visibility to all stakeholders.</div><div><br /></div><div>When the Sales Rep is notified of surgery, a list of assets like medical Instrumentation Loaner Kits and implants/disposables needed for a particular surgery event is determined. This material then must be tracked, and delivered to the hospital or location where the surgery event takes place. After the Surgery event, the Instrumentation loaner kit is returned to the plant where the inspection is carried out. The consumed items are billed to the Customer through the invoicing process.<span><a name='more'></a></span></div><div><br /></div><div><b>Pre-requisite:</b></div><div><br /></div><div><ul style="text-align: left;"><li>Hospitals must be set up as customers and sales representatives as employees</li><li>Instruments and Consumables set up separate materials</li><li>Sales BOM creation to group instruments</li></ul></div><div><b><br /></b></div><h3 style="text-align: left;"><b>Setup Steps in S/4:</b></h3><div><br /></div><div><b>Configure new consignment document type: –</b></div><div><br /></div><div><b>Step 1: Define Consignment fill up, pick up, and Issue document types</b>, which is the return delivery of goods to an external vendor.</div><div><br /></div><div>SPRO – Sales and Distribution – Sales document- Sales document header – Define sales document type.</div><div><br /></div><div>Consignment Fill up. – To deliver medical instruments for the surgery</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGEDmbn3Hxlv8_v_nbSVWiYiK-3RSNFfU2Hevz_tfZjwBcYMXfvVnQtQesJFuWGMig51aJ6JT_z5Fxeq0nq_4Vt5Ys14TJmTRDi0cNQb_7_K01NjatEnINigG8m21ukinR_6b8PPqfhn84WZeRD28wsxB61JKwtw-C7kEZMaF8wNHdYBpV3RbIVyf82pF4/s637/1.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="203" data-original-width="637" height="127" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGEDmbn3Hxlv8_v_nbSVWiYiK-3RSNFfU2Hevz_tfZjwBcYMXfvVnQtQesJFuWGMig51aJ6JT_z5Fxeq0nq_4Vt5Ys14TJmTRDi0cNQb_7_K01NjatEnINigG8m21ukinR_6b8PPqfhn84WZeRD28wsxB61JKwtw-C7kEZMaF8wNHdYBpV3RbIVyf82pF4/w400-h127/1.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Consignment Pick up – To return medical instrument after surgery.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGsDUJ8_C6BnQTibV6lnJByJ7bo1Vs_qTJh9WBKcxJsmTCpkyKvkwReyQ-KQ87GH7JwUILO0dilsvqHjSVjB23KQRnptF4MZacKNaZPy8mCeSvn3jVDGHIbM1llN4fMebxPA6AzaO4-HJFZjSeee5IY5IGbLsQ6TFOBIJdNHoYFXA4PQM550NKZ6ZgFhvJ/s632/2.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="198" data-original-width="632" height="125" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGsDUJ8_C6BnQTibV6lnJByJ7bo1Vs_qTJh9WBKcxJsmTCpkyKvkwReyQ-KQ87GH7JwUILO0dilsvqHjSVjB23KQRnptF4MZacKNaZPy8mCeSvn3jVDGHIbM1llN4fMebxPA6AzaO4-HJFZjSeee5IY5IGbLsQ6TFOBIJdNHoYFXA4PQM550NKZ6ZgFhvJ/w400-h125/2.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Consignment Issue – Bill for the implants consumed in the surgery.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjU22MsPDuOyoc1_dC-AcoxWMTEcFLi8ELyBU2h3XAkzNXLpSWY6heR1ftCSqNj_dpbuRVkrldm4zAAsuylxW10AmPkYkHQ0UGLi8SVZYzh0s3qhL8p85HCnsYxHLL_Oo-W_cZlsYNdY-pE3yYblNglQm89wgauUQInPy-_tDEW0Drf15tjmE9idWtWyou4/s639/3.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="191" data-original-width="639" height="120" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjU22MsPDuOyoc1_dC-AcoxWMTEcFLi8ELyBU2h3XAkzNXLpSWY6heR1ftCSqNj_dpbuRVkrldm4zAAsuylxW10AmPkYkHQ0UGLi8SVZYzh0s3qhL8p85HCnsYxHLL_Oo-W_cZlsYNdY-pE3yYblNglQm89wgauUQInPy-_tDEW0Drf15tjmE9idWtWyou4/w400-h120/3.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Step 2: Define item categories.</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">SPRO – Sales and Distribution – Sales document- Sales document item – Define item categories</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Consignment Fill-up Item category.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgu5FKkB8WeMqukc1-J5B8ahsu8L_aGafYx4YpQrCLwBqFi176J0B-VS0-dS5AvOHAhF1HQMxRTcB9XgKOOWoBEh_E4kq0xA8SIPNEhuSDXXpAFf1CG5QsNDgGoOI6gbKqN2IwKyPucsV2s_8MgqB_FaAKgea4tWF8tK9Y6BhedE9Mi31ffzPX0d8ttDOBM/s691/4.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="184" data-original-width="691" height="106" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgu5FKkB8WeMqukc1-J5B8ahsu8L_aGafYx4YpQrCLwBqFi176J0B-VS0-dS5AvOHAhF1HQMxRTcB9XgKOOWoBEh_E4kq0xA8SIPNEhuSDXXpAFf1CG5QsNDgGoOI6gbKqN2IwKyPucsV2s_8MgqB_FaAKgea4tWF8tK9Y6BhedE9Mi31ffzPX0d8ttDOBM/w400-h106/4.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Consignment pick-up item category</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgt1MjxZH1NWV4B3BqVU27v-ZOpQ6zMenKTZUlQTxiQp7hMprB-a4sjfCPY0eAsmoUsUIxKvgJ9z7wSIfxttaMFNUtwj_Aa6cTFvUXEXXC0HKGdvpa_EOnWCvaXSVydXCFqR4iiRHVajiGqEEzM1IazG7FBpzZKoopYy9BUQLoo2ejubNIR25xEloEE84z1/s665/5.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="190" data-original-width="665" height="114" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgt1MjxZH1NWV4B3BqVU27v-ZOpQ6zMenKTZUlQTxiQp7hMprB-a4sjfCPY0eAsmoUsUIxKvgJ9z7wSIfxttaMFNUtwj_Aa6cTFvUXEXXC0HKGdvpa_EOnWCvaXSVydXCFqR4iiRHVajiGqEEzM1IazG7FBpzZKoopYy9BUQLoo2ejubNIR25xEloEE84z1/w400-h114/5.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Consignment Issue item category</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhaZtqTcyjqmuB3r-QcinU81Mq-pHuLZPmfYqkxapQJYLS1bUhyphenhyphenFIXVHHFyLjE1F7xJ_RddDl-y6oZXJPM68gbY9OxSzEMsiNr3SvF0VBD5mdj07uAfD354UiO8ww9Ad2actQ7Ln4PrmgmBN2p7yLkARTCdUnNl1_3lc85vIwfEIbkIN12HAsYzaPKu19ze/s664/6.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="176" data-original-width="664" height="106" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhaZtqTcyjqmuB3r-QcinU81Mq-pHuLZPmfYqkxapQJYLS1bUhyphenhyphenFIXVHHFyLjE1F7xJ_RddDl-y6oZXJPM68gbY9OxSzEMsiNr3SvF0VBD5mdj07uAfD354UiO8ww9Ad2actQ7Ln4PrmgmBN2p7yLkARTCdUnNl1_3lc85vIwfEIbkIN12HAsYzaPKu19ze/w400-h106/6.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Step 3: Schedule lines</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">SPRO – Sales and Distribution – Sales document- Schedule lines – Define schedule lines.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Consignment Fill up the schedule line</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiryAtuR5yPUI_LwdxeoCkw9_bq3t2n8E93jar_58am7_4sdXsvKD_0x4TufI-UMAaHYuQ8TqkNG0Kzg-yQY2VyINA1OHP-3FXfRd9krTSY9SlbrZv3IMBOZsZo2brlU_TIMw9R5DE2JA82Y5005aWSI0m9PHFrJNhTFPBCkVztGK0b6tZc5fVpkA2lgLYb/s585/7.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="229" data-original-width="585" height="156" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiryAtuR5yPUI_LwdxeoCkw9_bq3t2n8E93jar_58am7_4sdXsvKD_0x4TufI-UMAaHYuQ8TqkNG0Kzg-yQY2VyINA1OHP-3FXfRd9krTSY9SlbrZv3IMBOZsZo2brlU_TIMw9R5DE2JA82Y5005aWSI0m9PHFrJNhTFPBCkVztGK0b6tZc5fVpkA2lgLYb/w400-h156/7.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Consignment Pickup Schedule line.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFVSm4W5qg3aCnezaPRe0RgOdNa5ClbXudmnftGeghRqENWsNX8SHlADTyOOVewHJmP8kIxhaTMwgc2i0dxTLNNyx6CbZv32liR03wirBd2BkDaHlnACmDTG-FPR2x-v06Jub3xcXWmll4C9iBBnX9Rq2CLnpb2ULBs_JF1j7tKqn6EWv6Wy4pwvTsra9y/s651/8.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="228" data-original-width="651" height="140" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFVSm4W5qg3aCnezaPRe0RgOdNa5ClbXudmnftGeghRqENWsNX8SHlADTyOOVewHJmP8kIxhaTMwgc2i0dxTLNNyx6CbZv32liR03wirBd2BkDaHlnACmDTG-FPR2x-v06Jub3xcXWmll4C9iBBnX9Rq2CLnpb2ULBs_JF1j7tKqn6EWv6Wy4pwvTsra9y/w400-h140/8.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Consignment Issue schedule line</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_zJqNFmpBD1Vy1_B0TBWxPxUd0ghfNHRiIlktuw3ICFMez7dsQXpZ6KeHeydMPJAXCUcJWNaugFKofeucT6__Pak1BP6AyjgrYC0XSe_2koyZBaFfDeqSb-Soa39aKF_reV6zVfvXgHuUikvnq1ORL4xNH0SZqvblZGrnYsdiNg2fMPfUrDP-Cq_ZtRMo/s650/9.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="229" data-original-width="650" height="141" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_zJqNFmpBD1Vy1_B0TBWxPxUd0ghfNHRiIlktuw3ICFMez7dsQXpZ6KeHeydMPJAXCUcJWNaugFKofeucT6__Pak1BP6AyjgrYC0XSe_2koyZBaFfDeqSb-Soa39aKF_reV6zVfvXgHuUikvnq1ORL4xNH0SZqvblZGrnYsdiNg2fMPfUrDP-Cq_ZtRMo/w400-h141/9.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><b>Step 4: Assign document type to the sales area.</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">SPRO – Sales and Distribution – Sales document- Sales document header – Assign Sales Area to Sales Document Types</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Step 5: Assign Item Categories</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">SPRO – Sales and Distribution – Sales document- Sales document item – Assign Item Categories</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Step 6: Assign Schedule Line Categories</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">SPRO – Sales and Distribution – Sales document- Schedule lines – Assign Schedule Line Categories</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>Process steps: –</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Step 1. Create a Consignment fill-up (KB) order for a surgery event for the requested instrumentation loaner kits and implants/disposables.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQW2bbDGrZ34xw9vv74I_6qaC0xZDYbF1dG6uy33bR6PtZYPM-T3lsY85lu7QkCIHcLgGxhYKzyCwKV48-YPxNDKsEDow-wLh3dcybo1ZWHupZPLkDmNpH325vnCj_PBRxCaeeI6ixs3bkJOtOpXcIuIEvYiuFjUt4rteCyyf56XhzBh1ZuT_Duk-pXkjM/s1861/10.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="1234" data-original-width="1861" height="265" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQW2bbDGrZ34xw9vv74I_6qaC0xZDYbF1dG6uy33bR6PtZYPM-T3lsY85lu7QkCIHcLgGxhYKzyCwKV48-YPxNDKsEDow-wLh3dcybo1ZWHupZPLkDmNpH325vnCj_PBRxCaeeI6ixs3bkJOtOpXcIuIEvYiuFjUt4rteCyyf56XhzBh1ZuT_Duk-pXkjM/w400-h265/10.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Step 2: Create an outbound delivery with reference to the KB Order. Pick, pack, and Issue</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj82PA29JyZsH5B0jc8OuBKSKVYRkMJdxXJ7hMQI5JMy8ZX3WspQ23GLYeSMotrjLddb7ZLZsl1wNk14FuU4yZgz6UgIJ_cqy5n91ucZu-zzgmwWuMr_WG12A70U7j3L4eDHrU1_fO90hHb3-rXrRDdOcqou2ruXL0kibX0cC_2aLgSmrs2DZXNZGeiDOzA/s1737/11.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="657" data-original-width="1737" height="151" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj82PA29JyZsH5B0jc8OuBKSKVYRkMJdxXJ7hMQI5JMy8ZX3WspQ23GLYeSMotrjLddb7ZLZsl1wNk14FuU4yZgz6UgIJ_cqy5n91ucZu-zzgmwWuMr_WG12A70U7j3L4eDHrU1_fO90hHb3-rXrRDdOcqou2ruXL0kibX0cC_2aLgSmrs2DZXNZGeiDOzA/w400-h151/11.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Step 3: Bill the customer for the materials consumed during the surgery using the Consignment issue (KE)</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi9kz1odPgJhoSlbY9ozBWUe5CXlFiJDdvbZt-4PqQEL_oSGmljcRgaqhXAxThDXVh94131DB6uzC0E_3HcTwhnvmMhWDu2p22ZtPZJ2jU8CK4LB56r7JN0CZdyfnvgySS-dBbeRFGruGDx2UYqHxFGjWmzPxURX21sdzqfbquwBJc8rtQwAe94JOicxLMF/s1807/12.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="856" data-original-width="1807" height="190" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi9kz1odPgJhoSlbY9ozBWUe5CXlFiJDdvbZt-4PqQEL_oSGmljcRgaqhXAxThDXVh94131DB6uzC0E_3HcTwhnvmMhWDu2p22ZtPZJ2jU8CK4LB56r7JN0CZdyfnvgySS-dBbeRFGruGDx2UYqHxFGjWmzPxURX21sdzqfbquwBJc8rtQwAe94JOicxLMF/w400-h190/12.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Step 4: Create delivery and issue from consignment stock</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5NPlFiDO32unAseUDzry__gDYlAjc177kjzN42SS4nNeXUWm7AFdrN5ZnoxZI1bb7P1HqFzHU_fcctvlOTAZjk2NYDPFXvsCwh_xdjsLui0gkeXgvKtEX1PMMj8ZRwm38qARtfWMQ_7G5lWQ2Ow2uQ94xHGumw7VcnNP61Aj4Zj36DRnw_kRP-HQ8JEsl/s1884/13.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="603" data-original-width="1884" height="127" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5NPlFiDO32unAseUDzry__gDYlAjc177kjzN42SS4nNeXUWm7AFdrN5ZnoxZI1bb7P1HqFzHU_fcctvlOTAZjk2NYDPFXvsCwh_xdjsLui0gkeXgvKtEX1PMMj8ZRwm38qARtfWMQ_7G5lWQ2Ow2uQ94xHGumw7VcnNP61Aj4Zj36DRnw_kRP-HQ8JEsl/w400-h127/13.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Step 5: Invoice the customer for the amount consumed.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhpMh4LyKHskNlI1Zvw1lalW80oVDJbQMgjuj4fKV0kdScDGxNy8cpPc-eZpXYYVNDbOKRGE-qBj3tfZ-5DsvZmU2onnFdJE7UiFQYA0YTwSEtz0-phGMHBalLtcp8qlbooBBCYxsMbOPr5BrfBhVaGOs_OU2QHX6Bk9TdSm4F7wBPVYXamr6YfuJjUkOFl/s1804/14.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="645" data-original-width="1804" height="143" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhpMh4LyKHskNlI1Zvw1lalW80oVDJbQMgjuj4fKV0kdScDGxNy8cpPc-eZpXYYVNDbOKRGE-qBj3tfZ-5DsvZmU2onnFdJE7UiFQYA0YTwSEtz0-phGMHBalLtcp8qlbooBBCYxsMbOPr5BrfBhVaGOs_OU2QHX6Bk9TdSm4F7wBPVYXamr6YfuJjUkOFl/w400-h143/14.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Step 6: – Create a pick-up order (KA) for the unused implants and instrumentation loaner KITS used in the surgery.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyv4fWtpVC7Y4wvU3BIFXmeUQiY9hOcc3OFjXlKEertxbqV9OhUdmUK6ysrKnAZPYWof_nN1QOyAdeZrI4IUgYInIYn25U-8b3Cqbqr3z0qO_izav_dDtXLDbC9ef6nlDCN2atHTqbmlI4Fd0R8GYIBmjmCYx_iBTDiv69RJUFDvHZlDfS8uQVx4_BEloE/s1876/15.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="1207" data-original-width="1876" height="258" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyv4fWtpVC7Y4wvU3BIFXmeUQiY9hOcc3OFjXlKEertxbqV9OhUdmUK6ysrKnAZPYWof_nN1QOyAdeZrI4IUgYInIYn25U-8b3Cqbqr3z0qO_izav_dDtXLDbC9ef6nlDCN2atHTqbmlI4Fd0R8GYIBmjmCYx_iBTDiv69RJUFDvHZlDfS8uQVx4_BEloE/w400-h258/15.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Step 7: Create Inbound delivery and receive goods.</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEghEFvPNG7C0giQ-sSgrvt-MJ3Q4uc9xVxotIGEy4IdWX_W_yX4b6DtJnlMQjd68JMFEYyEZWWzTMJ0X9Y86C825UGnL1SKyBVYGPTzM5dar5f0TJLOLGmF9PVmBqR4pN7smZiIps_DlyTrC3thzFv5orJSQN8X8tMhrCsKBqilnLCZHj3iaNv-MichJV2S/s1749/16.jpg" style="margin-left: 1em; margin-right: 1em;"><img alt="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" border="0" data-original-height="550" data-original-width="1749" height="126" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEghEFvPNG7C0giQ-sSgrvt-MJ3Q4uc9xVxotIGEy4IdWX_W_yX4b6DtJnlMQjd68JMFEYyEZWWzTMJ0X9Y86C825UGnL1SKyBVYGPTzM5dar5f0TJLOLGmF9PVmBqR4pN7smZiIps_DlyTrC3thzFv5orJSQN8X8tMhrCsKBqilnLCZHj3iaNv-MichJV2S/w400-h126/16.jpg" title="Field Inventory Management (FIM) – Fulfillment of medical devices/instruments for a Surgery event in a hospital using S4 HANA" width="400" /></a></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-63599015428223248592024-01-12T16:06:00.009+05:302024-01-12T16:06:52.540+05:30Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline<div>For AMEX acquirer the requirement is to update the assignment field of the accounting document with the unique payment id (Merch ID) that will be sent through in the note to payee of the EBS while processing the FEBAN. This will update the SB document type assignment field with the unique payment id.</div><div><br /></div><div>Blackline is also expected to update the SA document type assignment field for matching transaction. This will help in auto clearing of such open items.</div><div><br /></div><div>Following are examples of note to payee wherein the highlighted information is the “Unique” payment id received from the acquirer<span><a name='more'></a></span></div><div><br /></div><div>Example Note to Payee: 1</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-Dye-Jt3d6Es3DmkAN2RI2-r-rtcVwq_nMm2Mwvc0qnLRxxuGL6OE3JV-7nDwhcHU2qfXDeISu8TJs5oDRjYHxkBXHLKsdz7m9ag0xKLJcWEZa9xSXAP1G9Xj1uaEx9xTzVB-0kdu3KLhIATgIzGzAA0YlvvgDvs2ja9UNlwBFplqncb9XVG7V6GHPQ0f/s624/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" border="0" data-original-height="220" data-original-width="624" height="141" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-Dye-Jt3d6Es3DmkAN2RI2-r-rtcVwq_nMm2Mwvc0qnLRxxuGL6OE3JV-7nDwhcHU2qfXDeISu8TJs5oDRjYHxkBXHLKsdz7m9ag0xKLJcWEZa9xSXAP1G9Xj1uaEx9xTzVB-0kdu3KLhIATgIzGzAA0YlvvgDvs2ja9UNlwBFplqncb9XVG7V6GHPQ0f/w400-h141/1.png" title="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Example Note to Payee: 2</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">AMEX with Company X E-COMM</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiuBIMTHUbs_hqdB6HzsHaN5mKln5vBlqay5NyCvd4z2mW_QBk-BL33dUhsRvLU4gS9ha3PBldp2NMw6j1sVa6rIsnduBleWtbuLgj5AAuH_1A21OHa9npq83Ith2SHICbw5kq2MkeSDcvsU0i35hZP_ZUyI8PVy8zy9kX7ixMIBYLf29lwYf9cN7F3vb9n/s624/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" border="0" data-original-height="225" data-original-width="624" height="144" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiuBIMTHUbs_hqdB6HzsHaN5mKln5vBlqay5NyCvd4z2mW_QBk-BL33dUhsRvLU4gS9ha3PBldp2NMw6j1sVa6rIsnduBleWtbuLgj5AAuH_1A21OHa9npq83Ith2SHICbw5kq2MkeSDcvsU0i35hZP_ZUyI8PVy8zy9kX7ixMIBYLf29lwYf9cN7F3vb9n/w400-h144/2.png" title="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Note to Payee example 2</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Search string configuration set up</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Configuration Menu Path</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Financial Accounting (New) –Bank Accounting– Business Transactions — Payment Transactions — Electronic Bank Statement –Define Search string for Electronic Bank Statement</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCPQkSRWn8ysGLQLdnRQQoHBrehJQKMXGoX4nYy96ye5ZRqzZ5E4FGCJ5qc_nmLJ5Dza-hOD8f7_HYEc_hST_evwkKE3PqbmR-mxj5OqmgtT6lyjMKas-JWm1kH6famJ2oFOC3diF9-rFVR8-J5y02CAdedJUvPtMx6TAWb_cK5LFyfJibV1ml5LAImPSB/s624/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" border="0" data-original-height="271" data-original-width="624" height="174" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCPQkSRWn8ysGLQLdnRQQoHBrehJQKMXGoX4nYy96ye5ZRqzZ5E4FGCJ5qc_nmLJ5Dza-hOD8f7_HYEc_hST_evwkKE3PqbmR-mxj5OqmgtT6lyjMKas-JWm1kH6famJ2oFOC3diF9-rFVR8-J5y02CAdedJUvPtMx6TAWb_cK5LFyfJibV1ml5LAImPSB/w400-h174/3.png" title="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">Explanation for configuration</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">The search strings are defined for the above as follows</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDB8x8OHKRVLsWvXzskjsrrwIc3hyphenhyphenmhyphenhyphenOmjCveb1wqrLpIPXOJ3OMQevwSUGGo2_y92nob4UloI_v23aBnXny-a20xVQimrGnqTK8KVdDoUuP0D_iBlDvw6Ja-y8wEWVGXrma6byyn_34n1ExQdZ47fR9MLLZ9tAj93ESFZ5nUSiVRYukC-gGigmH8810z/s936/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" border="0" data-original-height="197" data-original-width="936" height="84" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgDB8x8OHKRVLsWvXzskjsrrwIc3hyphenhyphenmhyphenhyphenOmjCveb1wqrLpIPXOJ3OMQevwSUGGo2_y92nob4UloI_v23aBnXny-a20xVQimrGnqTK8KVdDoUuP0D_iBlDvw6Ja-y8wEWVGXrma6byyn_34n1ExQdZ47fR9MLLZ9tAj93ESFZ5nUSiVRYukC-gGigmH8810z/w400-h84/4.png" title="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Search String config pic 1</div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjz_cEUjFxg-XyG2ENk4ZdGxoIyfY-swV-6uy4Vwn0FZDpVJmONor0zN_wfVcxAC9biTV4-aetMq-YVZhdYssfMMJYHB5wGiY4kxbwdh9NYjZCN7_5Ei5souCPJasVeqYN_D-hWUSiQPu-1eHkX-IMwOSEAwSxAGcw7grVO-YaUJIdWhY6krYPWQgi-Vxar/s936/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" border="0" data-original-height="205" data-original-width="936" height="88" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjz_cEUjFxg-XyG2ENk4ZdGxoIyfY-swV-6uy4Vwn0FZDpVJmONor0zN_wfVcxAC9biTV4-aetMq-YVZhdYssfMMJYHB5wGiY4kxbwdh9NYjZCN7_5Ei5souCPJasVeqYN_D-hWUSiQPu-1eHkX-IMwOSEAwSxAGcw7grVO-YaUJIdWhY6krYPWQgi-Vxar/w400-h88/5.png" title="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><div class="separator" style="clear: both;">Search String config Pic 2</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgWfBgqdB3gf4VZx7PTQfATNmjZVGraAvPqGiSuPSunWXbdM24eJT2UoT3F6BkavcuKP0n8nDTr1ZxgFghHpv4kn4R7zHgUZ2grIoeXfwmeWUSt6u0oz0kdTnxX9PhOmmj8TAIzd6QJXoI7Q_iPRiAJGpDv0B0ZBrT_PP6s3v9603rryZTT7qJQC1EvAbUZ/s624/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" border="0" data-original-height="86" data-original-width="624" height="55" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgWfBgqdB3gf4VZx7PTQfATNmjZVGraAvPqGiSuPSunWXbdM24eJT2UoT3F6BkavcuKP0n8nDTr1ZxgFghHpv4kn4R7zHgUZ2grIoeXfwmeWUSt6u0oz0kdTnxX9PhOmmj8TAIzd6QJXoI7Q_iPRiAJGpDv0B0ZBrT_PP6s3v9603rryZTT7qJQC1EvAbUZ/w400-h55/6.png" title="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;">Search String Configuration Pic 3</div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">FEBAN – processing of statement</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPjvDEryZkk-X11WG6zroiI75KIP5a2UvpW9lW6vSGX5z0GGti-a3pe8trg0H1eozvOP8Z_rya0qtY41CH2mNpOioeFE-G-iOlZ4THrnNK5SoLHASRS0EMV97DgyPtlNVVp88db08r7aSaHxjIQbwKi8e8qH3cIHptr8kWfF088l2pl5SQG9rMEtD9KIol/s1904/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" border="0" data-original-height="838" data-original-width="1904" height="176" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiPjvDEryZkk-X11WG6zroiI75KIP5a2UvpW9lW6vSGX5z0GGti-a3pe8trg0H1eozvOP8Z_rya0qtY41CH2mNpOioeFE-G-iOlZ4THrnNK5SoLHASRS0EMV97DgyPtlNVVp88db08r7aSaHxjIQbwKi8e8qH3cIHptr8kWfF088l2pl5SQG9rMEtD9KIol/w400-h176/7.png" title="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">FEBAN bank statement processing</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Bank file processed and document posted in SAP – check the highlight for the assignment field being populated with the Unique payment id</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjVxzAcNIUAxFV0h8uM0cscRZUmRxgfMy_58DQc8jj0WTGy8fViQquGUn1A2mNjN2Hy9oXqSC81zZcvQp8vcJ-phyw0AmynmhBLl5aHRBK_s9K9PeC5DxLNLK9ty25LC3CbYIPZAsGNtY4K4RV7yXTi2rwXv6jgDDL6CaMGyfI93eLqtMkAc6lFeIfdej2/s624/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" border="0" data-original-height="167" data-original-width="624" height="108" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjVxzAcNIUAxFV0h8uM0cscRZUmRxgfMy_58DQc8jj0WTGy8fViQquGUn1A2mNjN2Hy9oXqSC81zZcvQp8vcJ-phyw0AmynmhBLl5aHRBK_s9K9PeC5DxLNLK9ty25LC3CbYIPZAsGNtY4K4RV7yXTi2rwXv6jgDDL6CaMGyfI93eLqtMkAc6lFeIfdej2/w400-h108/8.png" title="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">SAP accounting document posting coping Unique payment id to assignment</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">Find below the update of acquirer information to the text field of the SAP Accounting document</div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEigdcTcNc_nSIfrhszPbzrJ0khlY4N7eyLwnDkycg20Y1q1AKFRyLuT223hC0nqKtL9qwT4ZpR8tN0DMI_cvNP92Yk06Y-ViwmM7YmqQ9tjtoq1ARJS2GGlY7mAdnGnAKUFGyl67vGRGo8B79yrHO15FLm5u0NC-E3Fq8ymMuFhwvNdR7HJWsXMTQYTdlIZ/s624/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" border="0" data-original-height="209" data-original-width="624" height="134" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEigdcTcNc_nSIfrhszPbzrJ0khlY4N7eyLwnDkycg20Y1q1AKFRyLuT223hC0nqKtL9qwT4ZpR8tN0DMI_cvNP92Yk06Y-ViwmM7YmqQ9tjtoq1ARJS2GGlY7mAdnGnAKUFGyl67vGRGo8B79yrHO15FLm5u0NC-E3Fq8ymMuFhwvNdR7HJWsXMTQYTdlIZ/w400-h134/9.png" title="Set up for Auto clearing through FEBAN for Acquirer related postings aligning with Blackline" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><div class="separator" style="clear: both;">Acquirer information copied to text field</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Through black line the SA document is also updated with the same unique payment id in the assignment field.</div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;">By setting up auto clearing job the system automatically clears the matching (same value in the assignment field) automatically.</div></div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-38363086268227900082024-01-08T15:25:00.006+05:302024-01-08T15:25:42.081+05:30HANA Prod tables access in Dev for CV nodes data preview<div>SAP HANA XS Advanced application developments are done using Web IDE for HANA and it is installed in Dev instance and not in QA/prod instance. It is because we don’t want any changes directly deployed in Prod. In that case, we can’t troubleshoot the CV nodes data preview in Prod.</div><div><br /></div><div>So we can configure the process below to access Dev and Prod tables interchangeably when required.<span><a name='more'></a></span></div><div><br /></div><div><b>Process:</b></div><div><br /></div><div>Create a SDA connection from HANA Prod to Dev instance –> Create the virtual tables for Prod tables –> Create UPS –> Create synonyms with the same table names of Dev instance.</div><div><br /></div><div>with that now we have 2 UPS, one for Dev tables and other one for Prod Virtual tables. Then synonyms can be switched to use either Prod or Dev tables. You can add the .txt extension to the files that are to be ignored by deployment.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg2X2L_wKebGQ3o7hA9xCFd00w0XkNGgQwUkI_tcIQSGjAvfsHFkVqMD3PUIvo-_eAn5Ba75X0z6_JxBGTnVIwmomkZWEeCzKxpXEWWdLOQjDf9v9-TAdabGkmkJE5UYRTjYpt19UiqXU622OqhYorOk3iqHz8jbmNAcVfrhSEK_vJq6LxUkvFVl6RUQnHI/s1036/UPS-1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="HANA Prod tables access in Dev for CV nodes data preview" border="0" data-original-height="636" data-original-width="1036" height="245" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg2X2L_wKebGQ3o7hA9xCFd00w0XkNGgQwUkI_tcIQSGjAvfsHFkVqMD3PUIvo-_eAn5Ba75X0z6_JxBGTnVIwmomkZWEeCzKxpXEWWdLOQjDf9v9-TAdabGkmkJE5UYRTjYpt19UiqXU622OqhYorOk3iqHz8jbmNAcVfrhSEK_vJq6LxUkvFVl6RUQnHI/w400-h245/UPS-1.png" title="HANA Prod tables access in Dev for CV nodes data preview" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;">Note: We can’t leverage the UPS to connect to a different HANA instance in this case HANA prod is a different instance. So SDA connection is the available option for accessing Prod.</div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0tag:blogger.com,1999:blog-295427178855500735.post-30858695351509794562024-01-05T15:29:00.000+05:302024-01-05T15:29:09.291+05:30Azure Monitor for SAP solutions One-stop-shop for SAP technical monitoring<div>Are you an SAP Customer/Partner/ISV seeking a seamless monitoring solution? In this blog, I introduce Microsoft’s latest Monitoring solution—Azure Monitor for SAP Solutions—a user-friendly and plug-and-play tool.</div><div><br /></div><div><ol style="text-align: left;"><li>What is Azure Monitor for SAP Solutions?</li><li>What is the architecture?</li><li>What can you monitor?</li><li>What are the other key capabilities of AMS?</li><li>What are pricing and regions available?<span><a name='more'></a></span></li></ol></div><div><br /></div><div><b>1. What is Azure Monitor for SAP Solutions?</b></div><div><br /></div><div>Azure Monitor for SAP solutions is a comprehensive technical monitoring tool tailored for businesses leveraging SAP applications on Microsoft Azure. This turnkey solution facilitates the collection of telemetry data from SAP NetWeaver, databases, Linux Pacemaker clusters, and Linux operating systems. Centralized within the Azure portal, this tool streamlines visual correlation and rapid troubleshooting, requiring just a few minutes for configuration without the need for customer infrastructure deployment or maintenance.</div><div><br /></div><div><b>2. What is the architecture?</b></div><div><br /></div><div>The following diagram shows, at a high level, how Azure Monitor for SAP solutions.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiO7etdxK6jVjZGWPBDrGM0u0AshEKTEkx3xEymfoLdD0xS5HyWrGypFSpuiKNGe5qYt5l4N7R6kD40zWHNxQjKjRgFdpiCptHVeE0ylyL4_Hu2vDpAzsJwn1F0Djajj5jqo28KxIIYb9HuLS4w-Oubss_ML1EkDeW4oPRnL5v0XolXaV3k98OY08kKzZ9X/s1492/1.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure Monitor for SAP solutions One-stop-shop for SAP technical monitoring" border="0" data-original-height="913" data-original-width="1492" height="245" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiO7etdxK6jVjZGWPBDrGM0u0AshEKTEkx3xEymfoLdD0xS5HyWrGypFSpuiKNGe5qYt5l4N7R6kD40zWHNxQjKjRgFdpiCptHVeE0ylyL4_Hu2vDpAzsJwn1F0Djajj5jqo28KxIIYb9HuLS4w-Oubss_ML1EkDeW4oPRnL5v0XolXaV3k98OY08kKzZ9X/w400-h245/1.jpg" title="Azure Monitor for SAP solutions One-stop-shop for SAP technical monitoring" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">AMS Architecture</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li><b>Monitoring SAP Systems:</b> Azure Monitor for SAP solutions allows monitoring of multiple components across various SAP systems in a virtual network.</li><li><b>Configurable Providers</b>: Configure providers for different components (e.g., HANA database, HA cluster, NetWeaver, DB2 and OS) to collect data.</li><li><b>Key Architecture Components:</b></li><ul><li>Azure Portal: Access point.</li><li>Monitor Resource: Displays monitoring data.</li><li>Managed Resource Group: Automatic deployment with Azure Functions, Key Vault, Log Analytics Workspace, and Storage Account.</li></ul><li><b>Visualization and Querying:</b></li><ul><li>Azure Monitor workbooks for customizable visualizations. Pin items to the Azure dashboard for auto-refresh (max every 30 minutes).</li><li>Use Kusto Query Language (KQL) for log queries in Log Analytics.</li><li>Detailed Architecture is available at <a href="https://learn.microsoft.com/en-us/azure/sap/monitor/about-azure-monitor-sap-solutions#what-is-the-architecture" target="_blank">What is Azure Monitor for SAP solutions?</a></li></ul></ul></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>3. What can you monitor?</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li><b>SAP HANA</b></li><ul><li>CPU, memory, disk, and network use</li><li>HANA system replication</li><li>HANA backup</li><li>HANA host status</li><li>Index server and name server roles</li><li>Database growth</li><li>Top tables</li><li>File system use</li></ul><li><b>SAP NetWeaver</b></li><ul><li>SAP system and application server availability, including instance process availability of:</li><ul><li>Dispatcher</li><li>ICM</li><li>Gateway</li><li>Message server</li><li>Enqueue server</li><li>IGS Watchdog</li></ul><li>Work process usage statistics and trends</li><li>Enqueue lock statistics and trends</li><li>Queue usage statistics and trends</li><li>SMON metrics (/SDF/SMON)</li><li>SWNC workload, memory, transaction, user, and RFC usage (St03n)</li><li>Short dumps (ST22)</li><li>Object lock (SM12)</li><li>Failed updates (SM13)</li><li>System log analysis (SM21)</li><li>Batch job statistics (SM37)</li><li>Outbound queues (SMQ1)</li><li>Inbound queues (SMQ2)</li><li>Transactional RFC (SM59)</li><li>STMS change transport system metrics (STMS)</li></ul><li><b>HA Pacemaker Cluster</b></li><ul><li>Node, resource, and SBD status</li><li>Pacemaker location constraints</li><li>Quorum votes and ring status</li><li>Also see the metrics specification for ha_cluster_exporter.</li></ul><li><b>OS (Linux)</b></li><ul><li>CPU use, fork count, running processes, and blocked processes.</li><li>Memory use and distribution among used, cached, and buffered.</li><li>Swap use, paging, and swap rate</li><li>File system usage, along with number of bytes read and written per block device.</li><li>Read/write latency per block device.</li><li>Ongoing I/O count and persistent memory read/write bytes.</li><li>Network packets in/out and network bytes in/out</li></ul><li><b>IBM Db2 & Microsoft SQL Server</b></li><ul><li>Database availability</li><li>Number of connections, logical reads, and physical reads</li><li>Waits and current locks.</li><li>CPU, memory, and disk use</li><li>Host name, SQL instance name, and SAP system ID</li><li>Batch requests, compilations, and page life expectancy over time</li><li>Top 10 most expensive SQL statements over time</li><li>Top 12 largest tables in the SAP system</li><li>Problems recorded in the SQL Server error log.</li><li>Blocking processes and SQL wait statistics over time.</li></ul></ul></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>4. What are the other key capabilities of AMS?</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li><b>The SAP Landscape Monitor</b> is a one-stop destination to learn about the health of your entire SAP landscape. You can create a group of SAP systems based on the environment (e.g., Development, Production, etc.), application (e.g., ERP), or criticality and see the health of these systems based on the alerts that have been raised. You can also check alerts triggered by a group or a specific SAP system.</li></ul></div></div><br /><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtW_Vjqx1VegSbQ98UStgcZUs7lW_TEou95cXQP78O-n6kBSlMbLNoO6ogi_R3MYZzmRc_MpNmbumemVYKj31b-fZ357KFpBDLjudCBHpqmDIAUdF9-ClH72C484USj7n2bMUBW6yVOkOde7jiqMT0EDCcfLBT9dmKlConRMygliL8pVdEhH1hC67stZDK/s2180/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img alt="Azure Monitor for SAP solutions One-stop-shop for SAP technical monitoring" border="0" data-original-height="1296" data-original-width="2180" height="238" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtW_Vjqx1VegSbQ98UStgcZUs7lW_TEou95cXQP78O-n6kBSlMbLNoO6ogi_R3MYZzmRc_MpNmbumemVYKj31b-fZ357KFpBDLjudCBHpqmDIAUdF9-ClH72C484USj7n2bMUBW6yVOkOde7jiqMT0EDCcfLBT9dmKlConRMygliL8pVdEhH1hC67stZDK/w400-h238/2.png" title="Azure Monitor for SAP solutions One-stop-shop for SAP technical monitoring" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><span style="text-align: left;">AMS Landscape Monitor</span></div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><b>5. What are Pricing and regions available</b></div><div class="separator" style="clear: both;"><br /></div><div class="separator" style="clear: both;"><ul style="text-align: left;"><li>There is no licensing fee for Azure Monitor for SAP solutions. Customers pay for the infrastructure components that are deployed as part of the managed Azure Resource Group. Standard Azure prices are applicable for Azure Functions (Premium Linux), Azure Log Analytics, Storage, Key Vault, alerts, and notification groups.</li><li>Azure Monitor for SAP solutions is available in East US, East US 2, West US, West US 2, West US 3, Central US, South Central US, North Central US, West Central US, West Europe, North Europe, Australia Central, Australia East, Australia Southeast, South India, Southeast Asia, and East Asia.</li></ul></div></div>Sabrina Pintohttp://www.blogger.com/profile/13417597244101738355noreply@blogger.com0