How to...Create a Characteristic Relationship type SQL-script Applicable Releases: SAP NetWeaver BW 7.40, SP5 and higher; Note 2396898 SAP HANA 1.0 Version 1.0 December 2016© Copyright 2026 SAP AG. All rights reserved. ‘No part of this publication may be reproduced or transmitted in any form or for any purpose without the ‘express permission of SAP AG, The information contained herein may be changed without prior notice. Some software produets marketed by SAP AG and its stributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DBa, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, $/390, AS/400, 08/290, 08/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tall, Informix, ig/0S, POWER, POWERS, OpenPower and PowerPC are trademarks or registered trademarks of IBM Coxporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe ‘Systems Incorporated in the United States and/or other countries, Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, ‘WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java isa registered trademark of Sun Microsystems, Tne. ‘JavaScript isa registered trademark of Sun Microsystems, Ine,, used under license for technology invented and implemented by Netscape. ‘MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP ‘NetWeaver, and other SAP products and services ‘mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world, All other product and service names mentioned are the trademarks oftheir respective companies. Data contained in this document serves informational purposes only. tional product specifications may vary “These materials are subject to change without notice. ‘These materials are provided by SAP AG and its afiiated companies ‘SAP Group") for informational purposes only, ‘without representation or warranty of any'kind, and SAP Group shall not he able for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such, products and services, if any. Nothing herein should be construed as constituting an adltional warranty ‘These materials are provided “as is" without a warranty of ‘any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including ‘without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, test, graphics, links or other items contained ‘within these materials. SAP has no control aver the {information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty ‘whatsoever relating to tid party web pages SAP NetWeaver “How-to” Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, itis not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or ‘support, please refer to SAP Consulting Any software coding and/or code lines / strings (“Code”) {included in this documentation are only examples and are not intended to be used in a productive system ‘environment. The Code is only intended better explain and visualize the emntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of ‘he Code given herein, and SAP shall not be liable for errors or damages eaused by the usage ofthe Code, except ifsuch damages were caused by SAP intentionally or arossly negligent, Disclaimer Some components ofthis product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation ofthese components Any Java™ Source Code delivered with this product is only tobe used by SAP's Support Services and may not be modified or altered in any way.Document History Document Version Description 1.00 First official release of this guide THE BEST-Typographic Conventions Type Style Example Text Example text Example Example text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options Cross-references to other documentation Emphasized words or phrases in body text, graphic titles, and table titles File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentatio Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system, Keys on the keyboard, for example, F2 of ENTER, Description Caution Note or Important Example Recommendation or TipHow to...Create a Characteristic Relationship type SQL-script Table of Contents 4. Scenario. 2. General Description of the Solution .. 3. Step by Step Solution.. 3.1 Create an ABAP Class Implementing the Characteristic Relationships in ABAP_ 3.2 Create the Characteristic Relationships in Transaction RSPLAN...... 3.3 Concepts of SQL-script based Relationships... 3.4 Create the Parameter Structure ... evenness 3.5 Use Script Tool to Enhance the ABAP CLASS with SQL-script 36 Fill the Parameters. . 3.7 Implement the Business Logic in the AMDPs 3.7.1. Check Method. 3.7.2 Create Method 3.7.3 Derive Method. 3.8 Test your Characteristic Relationship... 4. Coding Example... December 2016How to...Create a Characteristic Relationship type SQL-script Ey 1. Scenario In almost every planning project in SAP BPC 10.1 Embedded model (or PAK) it is necessary to use characteristic relationships to control the consistency of the data in the system. And quite often it is necessary to use exits for those relationships as the special relationships cannot be modeled in hierarchies, attributes, or DSO's, Now when you are using ABAP exits for the characteristic relationships unfortunately the system cannot evaluate the relationships in HANA and thus the execution of the entire planning application will be forced to ABAP (see note 1637199). In this paper we describe how this behavior can be changed by using SQL-script coding for the characteristic relationships. 2. General Description of the Solution Before we go into detail and describe how you implement your characteristic relationships in SQL- seript we want to remind you of an option how you stil can use your ABAP exits without forcing the system to do all the work in ABAP. In some cases it is necessary to use an exit in order to futfil the business requirements but the number of records retumed from the ABAP exit is reasonably small. In this case the system reads all the necessary data into ABAP, executes the ABAP exit for the relationship, and sends the result as a table to HANA. Then this table is used to perform the actual relationship on HANA. Now how can you force the system to execute the described behavior? You simply have to add the interface TF_RSELS_CR_EXIT_HDE to your class the relationships are based on, implement the two methods Inthe interface (F_RSPLS_CR_EXTT_KDB~GET_SOLSCRIFT_INFO and IF_RSELS_CR_SKIT_HDB~GET_SQLSCRIPT_PARAMBTERS) but leave the implementations empty. ‘The systern will detect that situation and will show the above behavior. This ‘ABAP fallback’ will in many cases allow you to simply continue using your ABAP implementations of the characteristic relationships without the need to do any SQL-script programming. You will find more information on this approach in SAP note 1956085 containing also more detailed information in which cases this fallback will lead to good results and a further implementation in SQL-script is not necessary. So when you already have an ABAP exit implementation simply have a look at the prerequisites and try out the ABAP fallback. If the performance is good then you are fine and do not have to dig deeper into SQL- script programming, If not — or provided you are just curious to learn how you can do the implementation in SQL-script ~ then please enjoy the rest of this How to paper. ‘We want to illustrate the way to proceed with a simple system example. Let us assume we use a characteristic for material group and a characteristic for material. Obviously each material is contained in exactly one material group. We could simply model the relationship between the two characteristics. by an attribute or a DSO but in our case we want to use this simple example for illustrating the techniques for SQL-script based characteristic relationships. December 2016How to...Create a Characteristic Relationship type SQL-script Ey 3. Step by Step Solution 3.1 Create an ABAP Class Implementing the Characteristic Relationships in ABAP Well this might come as a complete surprise to you. Didn't you want to learn about the implementation of characteristic relationships in SQL-script? Well ~ yes. But there are several reasons you should start with the implementation in ABAP: = When you execute certain planning functions (ABAP exit or planning functions with several conditions, see note 1637199) the system switches from in-memory execution to ABAP execution. In these cases the same checks must be performed as in the case of an in-memory execution. ~ When creating and checking (visibie) cells in input enabled queries the system still uses ABAP coding and thus the information about the valid combinations must be available in ABAP. When an automatic disaggregation is executed in a query the system calls the SQL-script mothods (if available). = When you are not yet on BW 7.50 SP4 then the create method is not yet available in HANA and must be implemented in ABAP anyway. - You need an ABAP wrapper class to implement the SQL-script logic. This is similar to the case of planning functions with SQL-script exits (see How to... Use SQL Script for Planning unctions in PAK). This class will hold the ABAP implementation of the relationship as well as a function module retuming the name of the SQL-script methods. Even if these methods could be implemented in HANA directly it definitely makes sense to implement the SQL-script coding in'an AMDP (ABAP managed database procedure) contained in your ABAP class. For more information on AMOP's please have a look at the system documentation, at the blog How to debug ABAP Managed Database Procedures using ADT — Basics, or at the paper How To...Use Data from Another Aggregation Level in a PAK SQL-Script Procedure - Implemented as an AMDP Exam ‘The easiest way to implement such an ABAP class for a characteristic relationship is to open and copy the shipped class CL_RSPLS_CR_EXI7_BASE. It contains all necessary interfaces (for the ABAP. implementation) and (empty) methods. You just have to implement your business logic in the check, create, and derive methods in your class. You can find a simple example in our sample class in chapter 4. Remark: In our sample coding we have adopted the coding of the delivered class a bit. In the delivered class we use an ‘internal’ buffer. With note 1067433 we have introduced the ‘external’ buffering which we use in our sample coding. So we have adopted the list of attributes of our class and have deleted the coding for the internal buffering at the end of the constructor. 3.2 Create the Characteristic Relationships in Transaction RSPLAN Open the transaction ‘r=plan’ and go to the InfoProvider maintenance. Change to the tab ‘Characteristic Rels’ and create your relationship. Press the ‘Create’ button, select the check box ‘with derivation’, selact the type ‘Exit’ from the drop down box, and enter the name of your exit class. December 2016How to...Create a Characteristic Relationship type SQL-script Ey lel Now specify the source and target characteristics of the relationship. In our case we use the material as source and the material group as target. E i Save your settings. You can now test your characteristic relationship ~ either by creating a manual step in a planning sequence, a planning function, or a query. 3.3 Concepts of SQL-script based Relationships Before we start to implement our SQL-script methods we have to understand the concepts. In ABAP. you create a class the implements the interface ‘IF_RSPLS_CR METHODS’ and implementiits methods ‘CHECK’, ‘DERIVE’, and ‘CREATE’. Now when you look at the interface you will find additional methods ~ ‘CHECK _HBD’, ‘DERIVZ_HBD”, and ‘CREATS_HEO’ . One might be tempted to implement these methods and call some SQL-script methods from there. This is unfortunately the wrong approach. These methods are NOT used to implement custom logic of SQL-script based characteristic relationships. Instead you have to implement the interface *1F_# contains two methods: ‘S=T_sgLSCRIPT_INFO", and *GET_so! In the method *GeT_SQLSCRIPT_INFO" you return the names of the SQL-script methods implementing the check, the derive, and the create, The actual business logic is then contained in the SQL-script methods themselves which will be called by the system when needed. You can implement the methods directly in HANA but most probably you want to implement them as AMDPs directly in your ABAP class. In order to come up with the correct results in your SQL-script methods you might need additional information in SQL-script. You can define your own parameters when defining the SQL-script methods. But what should be filled into those parameters? This is up to you ~ when the system calls the SQL-script methods it will first call the (ABAP) method ‘czT_soLSCRTPT_PaRAM=TSRS’. You can fil your information into the parameters and the system will make sure that the SQL-script methods receive this information. If you do not need any parameters then an empty implementation of this method will be enough. In this paper we will use an example with additional parameters. We will elaborate where you have to deviate from our example if you do not need parameters. SPLS_CR_EXIT_HDS’ in your class. This interface IPT_PARAMETERS’ . December 2016How to...Create a Characteristic Relationship type SQL-script oy 3.4 Create the Parameter Structure Obviously this step is only necessary if you want to use parameters. In order to define the technical types of the parameters you will have to create a structure in the ABAP dictionary. Open transaction ==11 and enter name for your structure (as Data type). Press ‘Create’. ADAP Deionery Intel Bowen Fee SO ae) ore | owen) On the popup choose ‘Structure’. Enter a name for the structure. Now you can decide how many parameters you will need in your SQL- script methods — each component of the structure will be one parameter in the SQL-script method. In ‘our example we need only one parameter and thus one component. As we want to transmit a ‘selection (that will result in a where clause) we calll the parameter ‘T_WHERE’ and use the data type “STRING” Remark: in your structure you can only use elementary data types (no tables). The SQL-seript method will receive a list of elementary parameters. In order to be able to use the built-in type you have to click on the corresponding button first. (Pictener: Cone ste PO APS BET necorbey Ane seus suave nanee tae ARTE eerie | Geena AMDP CHECK". AMDP_DERIVE". e procedure name derive = 'ZCL DEMO CR= Now go ahead, locate the different AMDP methods in your class and implement the SQL-script coding directly in there. There is no need to program the methods netively in HANA. Please keep in mind that when you return a combination no field value for a characteristic value is allowed to be "NULL (this is the special marker the data base uses for a data value that does not exist ‘on the data base). ABAP does not know this concept and all values have to contain the correct but potentially initial value ~ matching the definition of the characteristic. For most characteristics (all characteristics of type character string) the correct initial value is ° ("blank"). For characteristics that are based on integers (especially the time characteristics) the initial value consists of a correct number of 0’, for example: December 2016How to...Create a Characteristic Relationship type SQL-script Ey Characteristic Type Initial Value OFISCPER3 NUM, length 3 000 OCALYEAR NUMG, length 4 0000 OFISCPER, NUNC, length 7 0000000 OCOSTCENTER CHAR, length 10 (blank, not NULL) 3.7.1 Check Method In ABAP exit the check method just receives one combination and has to retum the information whether the record is ok or not, In SQL-script we do not want to have such single calls as this would be harmful for the performance but the check method receives a list of all records that ere to be checked and has to return a list ofall allowed records, So the simplest implementation would be to just retum all received records — that means all records are regarded as valid: et chas - select * it _chas; In our example we have a different approach — we build up a (hard coded) lst ofall allowed records. Please note that the returning table =_t_chas has to be filled by a select statement. As you cannot insert records into the table ©_t_chas with some ‘insert’ statement we use a trick by selecting from the system defined table “cummy”: lect ~ Feorai01002" as "000000100" as ” union select *COPALO2302" "000000100" as * Lele 3.7.2 Create Method This method is quite similar to the method in the ABAP exit. You have to return a list of all possible combinations. There is currently one difference between the ABAP and the HANA implementation: in ABAP you are not allowed to return combinations that lie outside the selection. In SQL-seript exits this is possible but does not really make sense. Thus you should rather use the filter in your create method in order to restrict the combinations to the selection. Have a look at our example in chapter 4 how you can use the parameter that we have filled in order to fiter the result by the selection. Remark: As also noted in our documentation you should make sure that the different methods of the characteristic relationships return consistent results: every records that is regarded as valid in the check method should also be created by the create methods and derived accordingly in the derive method. If this is not the case (‘asymmetric relationships’) the system cannot guarantee that relationships coded in ABAP will always lead to the same results as relationships coded in SQL-script. We have to admit that our example is quite simple and not optimal in such respect as it first creates combinations and later deletes the ones not in the selection. In a real scenario you would probably have many more records and thus would use the filter in order to make sure that unnecessary combinations are not created in the first place. Here is the way how we can easily fier a table by the selection we have filled into the parameter: December 2016How to...Create a Characteristic Relationship type SQL-script oy =_t_chas = apply filter(:1_t_chas, +i_where| 3.7.3 Derive Method Here we again have a different behavior from the ABAP exits. Whereas the ABAP exit is called for each single combination and you have to fill in the missing characteristics in SQL-script exits you have to retum a list comprising all incoming combinations but with filled target characteristics. Our sample coding is again very similar our check-method, 3.8Test your Characteristic Relationship Finally you can go ahead and test your characteristic relationship. In most cases itis simpler to test your characteristic relationships using the test environment provided by a planning sequence. You cen create a formula or a planning function type generate combination in order to test the different methods. It also makes sense to insert some steps of type ‘manual input’ so you can check the created records. The reason winy planning functions are more apt for first testis that is easier to see (and control) whether the ABAP or SQL-script implementation is used. Remember a query uses ABAP in certain situations and SQL-script in others (see above). if you have created a planning function that can run in-memory (see note 1637199) you can simply execute it in your test sequence in order to execute the SQL-script implementation (transaction rsplan). Now if you want to test the ABAP methods you can just execute your planning function step in trace. mode as this mode is always executed in ABAP. HE AASeep 5 suo Tone (ete) wl” Agua tnlSereten) Ry (Oncend Rn Peary ncn Oct) (anual pat TELSOAI2TELSDAIZ ‘eiwr2 Teiori2 2° Ponneg icon TEXDAI2 _TE120AI2 Tenorio Te1aoFi2—Teia0ri2_Te!30e12 3 Merwal pat TEGOAIS_TEI2OA12 essori3Teis0r.3 At the bottom of the screen you can see some system messages — either that the planning functions was executed successfully or if not the information that some records did not comply with the characteristic relationships. December 2016 10How to...Create a Characteristic Relationship type SQL-script oy O28 F55o82 Step Te Tipe (Oecton) Level Aageton Level (Dexcoton)] kere (Debten) Function Panning Functn (Descoton) i Mawaliout —TEISDAI2TELSOALZ TELA TEROFL2 2 Pannng Furebon TELIDAI2 _TELSOALZ yeuora Tenor2—TeLaoni2 TEL ‘S Mamalipit —TEIMDAI TEISDALD yen Tenor 2 Pennng Funcbon TEI3DAI3 _TELSOAI3 Tenor Teo —TeLDOCIZ_TeRDC? Hopefully your characteristic relationships work the way you expect. But how can you search for errors in your code? In ABAP this is simple — just set a break-point in the method you want to debug (session break-point if you run your tests from transaction rspian, external break-point if you test for exemple in a query in an Analysis for Office workbook). But what about the AMPDs? When you are on SAP NetWeaver 7.50 or higher then luckily debugging AMDPs is nearly as simple as debugging normal ABAP methods (see also How to debug ABAP Managed Database Procedures. using ADT — Basics). But you have to use the eclipse based ABAP modelling tools. Start the ABAP modelling tool and log on to your ABAP system. Navigate to your class and to the method you want to debug, Foe FRee RO and call the context menu. Choose Toggle Breakpoint’. This will automatically activate the AMDP debugger and an (external) break-point. December 2016 "1How to...Create a Characteristic Relationship type SQL-script oy ame You can go back to transaction ‘:=p1an’ or say to an Analysis for Office workbook and perform your test. The system will automatically stop in the AMDP debugger. Here you can have a look at all the Parameters and tables in the AMDP and can go through the method step by step. © Loatng cain scr. soaaaoores" aa */800/29 eruaRe™ coon ay “Topneoois0" ae */aze/e0_gar" (ob cas| Carat el Tpe Lc Te Cz on ed] Mac Dicenle Altos | MIM LTH 22 Tew Fors © 4 Groeten Nene RAD MAT CIO TL If you are using an older version of SAP NetWeaver debugging in SQL-script is also possible but more complicated. When an AMDP is executed for the first time a SQL-script procedure is created in HANA. ‘You can use standard debugging in HANA studio to check how yaur SQL-script methods work (see ‘Tutorial: How to Debug an ABAP Managed Database Procedure), December 2016How to...Create a Characteristic Relationship type SQL-script oy 4. Coding Example CLASS zel_demo_cr DEFINITION PUBLIC CREATE PROTECTED . one f class CL_RSPLS_CR EXIT BASE lude ¢ source files here!!! PUBLIC SECTION. TYPE-FOOLS abap TYPE-BOOLS red . INTERFACE if_rspls_cr_types LOAD . INTERFACES if_repls_char_relation . INTERFACES if reple_cr_methods . INTERFACES if_rspls_cr_types - INTERFACES if rsple cr exit . INTERFACES if_amdp marker_hdb . INTERFACES if repl2_cr_exit_hdb . ALIASES n_is_derive FOR if_repls_char_relation~n_is_derive . ALIASES nt POR if Feple cher xelation-n te chas TYPES: BEGIN OF tn_s_chas, Meic/2d_mat TYPE /bic/oizd_mat, /bic/zd_mtlgrp TYPE /bic/oizd_mtlgrp, END OF tn_e_cha! rere: tn_t_chae TYPE STANDARD TABLE OF tn_s_ches WITH DEFAULT KEY. DATA n_basic_prov TYPE reinfoprov READ-ONLY . DATA nostep TYPE rapls_step READ-ONLY . DATA n_dateto TYPE rspls_cz_dateto READ-ONLY . METHODS amdp_check IMPORTING VALUE (i_t_chas) TYPE tn_t_chas VALUE (i_whexe) TYPE string EXPORTING VALI et chas) TYPE tn_t_chas. METHODS amdp_create IMPORTING December 2016 3How to...Create a Characteristic Relationship type SQL-script oy VALUE (i_where) TYPE string EXPORTING VALUE (@_t_chas) TYPE tn_t_chas. METHODS amdp_derive IMPORTING VALUE (i_t_chas) TYPE tn_t_chas VALUE (i_where) TYPE string EXPORTING VALUE (@_t_chas) TYPE tn_t_chas. METHODS constructor IMPORTING 1i_basic_prov TYPE rsinfoprov H_etep TYPE if_reple_cr_types—>tn_step !iis derive TYPE ra_bool lite cha_role TYPE if raple_cr_type: Hi dateto TYPE repls_cr_dateto RAISING cx_reple failed . PROTECTED SECTION. tn_ta_cha_role DATA o_r_strucdescr TYPE REF TO cl_abap_structdescr DATA n_tex_seldr TYPE rsdd_tex_seldr. CLASS-METHODS get_instance_o IMPORTING li basic prov TYPE rsinfoprov 1a step TYPE if_reple_cr_types->tn_step 1iis_derive TYPE rs_bool lite cha role TYPE if reple_cr_types=>tn_ts che role lidateto TYPE repls_cr_dateto Hi_elename TYPE seoclaname OPTIONAL RETURNING VALUE (r_r_instance) TYPE REF TO if_rspls_char_relation RAISING cx_rspls_failed . METHODS geldz_to_range IMPORTING !i_tex_seldr TYPE rsdd_tex_seldr XPORTING December 2016 14How to...Create a Characteristic Relationship type SQL-script oy fet_range TYPE rsdri_t_range . PRIVATE SECTION. 4* private components of class Ch_RSPLS_CR_EXIT_BASE ¥"* do not include other source files here!!! Tyee: BEGIN OF tp_sx_instance, basic prov TYPE reinfoprov, ts_cha_role TYPE if_repls_char_relation~tn_ts_cha_role, z_inetance TYPE REF T0 if repls_char_relation, END OF tp_sx_instance . Tyee: ~~ tp_tex_inetance TYPE SORTED TABLE OF tp_sx instance WITH NON-UNIQUE KEY basic _prov INITIAL SIZE 0 . CLASS-DATA p_tex_instance TYPE tp_tsx_instance . ENDCLASS. CLASS ZCL_DEMO_CR IMPLEMENTATION. * — ‘2CL_DEMO_CR->AMDP_CHECK T_T CHAS TYPE TN_T_CHAS TwHERE TveE STRING ET CHAS TNT CHAS METHOD amdp_check BY DATABASE PROCEDURE FOR HDB LANGUAGE SQLSCRIPT OPTIONS READ-ONLY. * using . * implemont something meaningful s t_chas = select ‘COPAIO1002" a= "/BIC/ZD MAT" , "000000100" as "/BIC/ZD_MTTGRE" fom dummy union select "COpA102302" as "/EIC/zD_MAT" , "000000100" as "/BIC/ZD_MILGRE" from dummy union select "COPASO0101" as "/BIC/ZD_MAT" , "000000101" as "/BIC/2D_MTLGRE" December 2016 15How to...Create a Characteristic Relationship type SQL-script oy from dummy union select “CoPAS00100" as "/BIC/20_MAT™ , "900000101" as #/e1c/20 since" from dummy union select "COPASO0122" as "/BIC/ZD_MAT" , "000000102" as "/BrC/zD_MTLGRE" from dummy union select *COPAS00120" as "/BIC/ZD_MAT" , *000000102' as "/BIC/ZD_MTLGRE" from dummy; ENDMBTHOD. DEMQ_CR->AMDP_CREATE METHOD amp create BY DATABASE PROCEDURE FOR HDB LANGUAGE SQLSCRIFT OPTIONS READ-ONLY. * using . mething meaningful APPLY_FIETER( :i_t_chas, i_t_chas - select "COPA101002" as "/BIC/ZD_MAT" , 000000100" as "/BIC/ZD_MTLGRE" fzom dummy union select *cOpA102302" as "/EIC/zD_MAT" , *000000100' as "/BIC/ZD_MTTGRE" from dummy * implement s tet chas | where ); union select "COPASOOLOL" as "/BIC/ZD_MAT" , "000000101" as "/BIC/2D_MTLGRE* from dummy December 2016How to...Create a Characteristic Relationship type SQL-script oy union select *COPASOOLO0" as "/BIC/ZD_MAT" , "000000101" as */erc/2p_MrzGRe* from dummy union select *COPAS00122" as "/BIC/ZD_MAT" , *o00000102" as "/BIC/ZD_MTLGRE" from dummy union select "COpAS00120" as "/EIC/zD_MAT" , "000000102" as "/BIC/ZD MILGRE" from dummy; et ches apply_filter(:1_t_chas, :i_where); tet chas = * from :1_t_chas; ENDMETHOD. + - * | Instance Public Method ZCL_DEMO_CR->AMDP_DERIVE METHOD amdp derive BY DATABASE PROCEDURE OR HDB LANGUAGE SQLSCRIPT OPTIONS READ-ONLY. using . implement something meaningful @_t_chas = select *COPALO1002" az "/BIC/ZD_MAT" , *oo0000100" as "/BIC/ZD_MTLGRE" from dummy union select "COPA102302" as "/BIC/ZD_MAT" , "000000100" as "/src/z2_wrrGRE” from dummy union select *COPASOO1OL" as "/BIC/ZD_MAT™ , "000000101" as "/BIC/ZD_MTIGRE" from dummy December 2016 7How to...Create a Characteristic Relationship type SQL-script oy union select "COPA500100" as "/BIC/zD_MAT™ , *o00000101" as "/BIC/ZD_MTLGRE" feom dummy union select "COPAS00122" as "/BIC/ZD_MAT" , "000000102" as "/BIC/zD_MTLGRP" from dummy union select *COPAS00120" as "/BIC/ZD MAT" , ‘ooog00102" as "/BIC/ZD_MTLGRE" from dumy? ENDMBTHOD. + od ZCk_DEMO_CR->CONSTRUCTOR * | Instance Public me TYPE RSINFOPROV vee IE RSPLS CR TYPES->TH STEP i rePE Rs_Boon ALE >) 1_75_CHA_ROLE TvPE IE RSPLS CR TYPES->TW_TS CHA ROLE - a Oo + | (===>) LDATETO Tyee RSPLS_CR_DATETO * | [1CK!] CX_RSPL: he FAILED METHOD constructor. * => ibasic prov basis infoprovider + -> istep step of characteristic relation * -> iis derive flag, derive or only check combination * > its cha_role haracteristics and their role + -> idatero date: valid to ( or char. relationsships) DATA: 1_s_cha_role TYPE if_repls_char_relation=>tn_s_cha_role, le ches ‘TYPE if reple char relation->tn_s chas, Ar che_prop TYPE REF 70 if _red_cha_prop, itlcomp = TYPE cl_abap_structdescr->component_table, 1s comp ‘TYPE cl_abap_atructdescr=>component, December 2016 18How to...Create a Characteristic Relationship type SQL-script oy i_ts_chanm TYPE red_ts_chanm, lizstruc TYPE REF 70 cl_abap_structdescr, ide TYEE i, a ts_chanm_s TYPE red_ts_chanm. BIELD-SYMBOLS: TYPE any, TYPE charl, TYPE if repls_cr_types~>tn_s mesg. if_repls_char_relation~ basic prov - i_basic prov. n_basic_prov - i_basic prov. istep. i_is_derive. i dateto. n_is_derive + £111 internal view of characteristics for characteristic relat * and create a data structure containing these characteristics LOOP AT i_ts_cha_role INTO 1_s_cha_role. 1s chag-idbjnm = 1_¢ cha role-dobjnm. 1s_chas-role 1is_cha_role-role. * we want characteristic values in internal format + > leave field "is sid’ of 1 chas empty tz cha_prop = elured_iobj_prop_cache->get_che( 1_¢_chas-iobjam ). * 1 cha prop contains the meta data for ¢! + arn od GET FIELD NAME contains the fieldnane of BW * generated data structures, e.g. for reference characteristics + the names used in master data tables may be different ! actual infoobject: 1_s_chas-fieldnn = 11 cha_prop->get_field_name( ). HISERT 1s chas TNT TABIE if reple_char_relation-n_te_chas. + create the data structure at run time using the data element: 1s comp-nane = 1_5 chas-fieldam. gos comp-cyrs = 1 = cha peop--get_aatadesez( ). ABPEND 1s comp 70 1_t_comp. * fill key of buffer table: INSERT 1_s_chas-fieldnm INTO TABLE 1_ts_chann. IF 1s chas-role ~ 's". inset 1s ches-fieldnm INTO TABLE 1_ts_chanm_s. suDrF. ENDLOOP. * now a type description of the data records can be created: o_¥ strucdeser = cl_abap_structdeser=>get ( p_componente = 1_t_comp postrict ~ abap_false ). tuse external buffering IE_RSPLS_CHAR_RELATION-N_USE_EXTERNAL_BUFFER = ABAP_TRUE. ENDMBTHOD. December 2016 19How to...Create a Characteristic Relationship type SQL-script oy * — | Static Protected Method 2CL_DEMO_CR->GET_INSTANCE 0 TYPE RSINFOPROV TYPE TF_RSPLS_CR_TYPES->TN_STEP TvPE RS_BOOL >] 8 CHA ROLE TYPE IF_RSPLS_CR_TYPES=>TN TS CHA ROLE “I >] T_DATETO TvPE RSPLS_CR_DATETO oa >) TCLSNAME TPE SEOCLSNAME (opt-iona1) ede 0] R_R_INSTANCE TYPE REF 0 IF_RSPLS_CHAR_RETATION + | [ICK!] cx_RSPDS_PATDED METHOD get_instance_o. + => ibasic prov basis infoprovider + => Lestep step of characteristic relation + > ids derive flag, derive or only check combination + => Dts cha role characteristics and their role + > Laateto Gator valid to ( or char. relationships) + <5 Dolsnane Glass nane, used for subclasses + <-rpinstence existing of new instance DATA: exists TYEE abep_bool, 1lsx_instance TYE tp_s%_ instance, ilelenane YEE seoclanane, Lorex TYPE REF TO ox_tepls_failed. FISLD-SYMBOLS: <1_ex_instance> TYPE tp_sx_instance. + the instance table is sorted by basic prov evant records by ts_cha role * scan the Lexists = abap_false. LOOP AT p tex instance ASSIGNING <1_ex instance> WHERE basic_prov = 4 basic prov. IF <1_sx_instance>-ta_cha_role = i te cha role. Lexiets - abap_true. zy instance = <1_sx_instance>-r_instance. EXIT. ENDIF. ENDLOOB. IP l_exists = abap_falae. 1_Sx_inetance-basic_prov - i_basic_prov. 1_sx_inetance-ts_cha_role = i ts cha role. December 2016How to...Create a Characteristic Relationship type SQL-script oy TRY. IF i_clename IS INITIAL. 1_Glename = 'CL_RSPLS CR EXIT BASE". ELSE. l_clename = i_clename. ENDIF. CREATE OBJECT 1_ax_in! nce-r_instance TYPE (1_clenama) EXPORTING ibasic prov = 1_sx_instance basic prov i_step - iste iis derive = iis derive its cha_role = 1_sx_instance-ts_cha_role i dat: = idstero. CATCH ex_raple failed To 1_z ex. BAISE EXCEPTION 1 z ex. ENDTRY. INSERT 1_sx_instance INTO TABLE p_tsx_instance. er instance = 1 ex _instance-r instance. ENDIF. stance Public Method ZCL_DEMO_CR~ >IE_RSPLS_CHAR_RELATION~CREATE DATA REF TYPE REF TO DATA MeTHOD if _rspls_char_relaticn~create data_ref. rchas structure with infoobjects an * as defined in table n_ts chas fieldnames CREATE DATA x_r_chas TYPE HANDLE o_r_strucdescr. ENDMBTHOD. + ~ + | mstance Public Method 2Ch_DEMO_CR- December 2016 2How to...Create a Characteristic Relationship type SQL-script oy >IF_RSPLS_CHAR_RELATION~SET SELECTION >] I_T8X_SELDR >] T_PREFETCH TYPE RSDD_TSX_SELDR RS_BOOL (optional) METHOD if_rspls_char_relation~set_selection. + I_TSX_SELDR contains information about the selection in the current * context of a planning query or a planning function; this method can * bo helpful to prefetch data nesded in the relation * I PREFETCH contains @ hint that a prefetch of resources might * improve performance, e.g. to a avoid a record based DB access n_tex_seldr - i_tex_seldr. ENDMBTHOD. * + + | Instance Public Method 2Ci_DEMO_CR- >IF_RSPLS_CR_EXIT HDB~GET SQLSCRIPT_INFO * E_DB_SCHEMA_NAME TePE STRING + E_PROCEDURE_NAME_CHECK TvPE STRING * E_PROCEDURE_NAME_DERTVE TYPE STRING + E_PROCEDURE_NAME_CREATE TvPE STRING . -] E_PARAMETER_ NAME TYPE ‘TYPENAME, METHOD if_reple_cr_exit_hdb-get_sqlscript_info. fe procedure nane_create = '2CE. DEMO CR-SAMDP CREATE". elprocedure-nane_check = ‘ZCL_DEMO_GR->AMDP_GHECK" elprocedure_name_derive - 'ZCE_DEMO_CR->AMDP_DERIVE". + here you can return a name of a DDIC 5! = amoters to the $0L-script fe paraneter_nane = 'CROBHOSTRUC" ENDHETHOD. cture in which you can pass par + - + * | Instance Public Method Ci_DEMO_CR~ >IF_RSPLS_CR_EXTT_HDB~GRT_SQLSCRIPT PARAMETERS te | [<---) ES _PARAMETER TvPE ANY December 2016 22How to...Create a Characteristic Relationship type SQL-script oy sqlscript_parameters. n_tax_seldr to calculate a where to be used in the apply filter HANA Pur 1 Lwhere 1 TYPE string, TYPE , " with component i whore 1 = "" = ' AND "-i_where_1 = 1_where_1. ONDING 1_9 TO 2 ¢ parameter. DATA: 1_e ordemostruc THFE crdemostruc. DATA: 1_t_range TYPE rsdri_t_zange, 1s range LIKE LINE OF 1 t_range, limark TYPE ce CALL METHOD me->seldr PORTING i_tex_seldr - n_tex_seldr IMEORTING »_range _range. @ we just use single val * first insert the selection for material; we as: LOOP AT 1_¢ yange INTO 1_¢ range WHERE chanm = 'aD_MAT' CHECK 1s range-sign = 'I' AND 1s _range-compop = 'EQ'. IF 1_s_crdemostruc-i_where IS INITIAL. 12 @xdemostruc-i where = ' ('. ELSE, CONCATENATE 1_¢_erdemostruc-i where ' OR ' INTO 1_¢ erdemostruc~ i_where DIF. CONCATENATE 1_s_crdemostruc-i_where © "/BIC/ZD_MAT™ = '~ 1s _range-low ~ INTO 1_s_crdemostruc-i_where. ENDLOOP. IE 1_s crdemostruc-i_where IS NOT INITIAL. CONCATENATE 1_s_crdemostruc-i_where ' ) ' INTO 1_s_crdemostruc~ iwhere. ENDIF. LOOP AT 1_t_range INTO 1_s_range WHERE chanm - 'ZD_MTLGRP CHECK 1_¢ yange-sign = 'I' AND 1_g range-compop = 'EQ". IF 1_s_crdemostruc-i_where IS INITIAL. 12 Grdemostruc-i_where = ' ('. ELSE. IF l_mark IS INITIAL. mark = "x". December 2016 23How to...Create a Characteristic Relationship type SQL-script oy CONCATENATE 1_s_crdemostruc- i.where ' AND ( ' INTO 1_s crdemostruc-i_where. ELSE. CONCATENATE 1_s_crdemostruc-i_where ' OR ' INTO 1_s_crdemostruc— i where. ENDIF. ENDIF. CONCATENATE 1_s_crdemostruc-i_where * "/BIC/ZD_MTLGRP' 1a vange-low *"* INTO 1s erdemostruc-i_where. ENDLOOP. IF 1_¢ crdemostruc-i_where IS INITIAL. 1_8_Grdemostruc-i_where ELSE. CONCATENATE 1 where. ENDIE. s_exdemostruc-i_where ') ' INTO 1s erdemostruc- MOVE-CORRESPONDING 1_¢ crdemostruc 70 ¢_¢ parameter. ENDMETHOD. + ~ * | Static Public Method 2CL_DEMO_CR=->IF_RSPLS_CR_EXIT~GET_INSTANCE TvPE RSINFOPROV TyPE IF_RSPLS_CR_TYPES=>7N_STEP TYPE RS_BOOL >) T75_CHA_ROLE TYPE ‘TF_RSPLS_CR_TYPES->TN_TS_CHA_ ROLE * | [---3] L_parero TVPE RSPLS_CR_DATETO +) f=) Lcnswame TYPE SEOCLSNAME (optional) ete 0] R_R_INSTANCE TYPE REF 0 IF_RSPLS_CHAR RELATION + | [ICR] CX_RSPLS_PAILED he - METHOD if_rspls_cr_exit~get_instance. * > ibasic prov basis infoprovider * -> i step step of characteristic relation * -> iis derive flag, derive or only check combination * > ite cha role characteristics and their role * > idateto date: valid to ( or char. relationsships) + > iclsname class name, used for subclasses December 2016 24How to...Create a Characteristic Relationship type SQL-script oy -- rpinstance existing or new instance DATA: 1_x_ex TYPE REF 70 cx_reple_failed. TRY. CALL METHOD get_instance_o EXPORTING basic prov = i_basie prov astep - ilstep dis derive = iis derive cha _role - i te cha role i dateto i_clename RECEIVING instance - z_r_instence. CATCH cx_zepls_failed INTO 1x ex. RAISE EXCEPTION 1_r_ex. ENDTRY. ENDMETHOD. + ~ rveE aNy his -] ET_Mesa rvPE IE_RSPLS_CR_TYPES=>1N_T MESG | [<---) EIS VALID Tyee RS_BOOL METHOD if_rspls_cr_methods~check. jaracteristics combination J messages valid flag, record is valid CLEAR © t_mesg. FIELD-SYMBOLS: ‘TYPE any, «matgrp> TYPE any. ASSIGN COMPONENT */BIC/ZD_MAT' OF STRUCTURE i. _chas TO . ASSIGN COMPONENT */BIC/ZD_MPLGRP' OF STRUCTURE i; cha T0 . December 2016 25How to...Create a Characteristic Relationship type SQL-script oy IF = 'COPAL01002' AND = '000000100" oR = 'COPA102302" AND = '000000100" oR «mat> = 'COPASO0101" AND = '000000101' oR = 'COPAS00100" AND - "000000101" OR = 'COPASO0122" AND = 1000000102" on = ‘COPAS00120" AND = '000000102". eis valid = rs_c_true. ELSE. eis valid = rs_¢ false. ENDIF. ENDMETHOD. * — Tyee ‘TREXT_LOOKUPATTRIBUTE TvPE IE_RSPLS_CR_TYPES=>1N_T MESG METHOD if _reple_er_methods~check_hdb. RAISE EXCEPTION TYPE cx_rsr_x message EXPORTING cext - 'IF_RSPLS_CR_METHODS~CHECK HDB-01- ENDMETHOD. * — “1 TYPE, RSDD_TSX_SELDR a >) T7S_cRANM TYPE RSD_TS_CHANM (optional) vl -] B_T_MESG TYPE ‘IF_RSPLS_CR_TYPES->TN_T_MESG +) Pen] BH cHas Tere HASHED TABLE * | (10x!) CK_RSPLS_FATLED MaTHOD if_reple_cr_methods~create. > i_tex_seldr selection criteria December 2016How to...Create a Characteristic Relationship type SQL-script oy + ce t mag jessages valid combinations exception DATA: 1_¢ struct TYPE REF 70 deta. FIsup-siMB0zs: TYPS any, cuat> TYPE any, cnatgsp> THEE any. CREATE DATA l_r_struct LIKE LINE OF eth chas. ASSIGN 1_r_struct->* TO . ASSIGN COMPONENT '/BIC/20_MAT' OF STRUCTURE TO . ASSIGN COMPONENT '/BIC/20_MTLGRE' OF STRUCTURE 10 . = *COPA101002". «matgzp> = "009000100" INSERT INTO TABLE e_th_chas. = 'COPAL02302 = "000000100 INSERT INTO TABLE e_th_chas. «mat> = 'COPASO0101 «matgzp> = "000000101 INSERT INTO TABLE e th_chas. = ‘COPASO0100". = '000000101". INSERT INTO TABLE e th chas. «mat> = 'COPAS00122" = "000000102 INSER? INTO TABLE ¢ th chas. = ‘COPA500120". = '000000102". INSERT INTO TABLE ¢_th_chas. ENDMBTHOD. + ~ * | Instance Publi _DEMO_CR->IF_RSPLS_CI ¢_METHODS~CREATE_HDB December 2016How to...Create a Characteristic Relationship type SQL-script oy [---9] 118x_senor TvPE RSDD_TSX_SELDR vie >] 175_cHan TyPE RSD_?S_CHANM (optional) ae -] E_T_MESG TYPE IF_RSPLS_CR_TYPES->1N_T_MESG a ] E_TH CHAS TvPE HASHED TABLE \ J E_INDEX_ID TYPE TREXD_INDEX_ID I ] EvIEw_1D TVPE ‘TREXD_PLAN_VIEW ! ] ET NAME MAP TYPE TREXT_PE_WAME_MAP_SET ' ] BT QUERY ENTRY TYPE ‘REX QUERY ENTRIES * | (10x!) CK_RSPLS_FATLED METHOD if yeple_cr_methods~create_hdb. RAISE EXCEPTION TYPE cx_rer_x message PORTING ext ~ ‘IE _RSPLS CR METHODS~CREATE HDB-O1, ENDMETHOD. + - * | Instance Public Method ZCL_DEMO_CR->IF_RSPLS_CR METHODS~DERIVE * Ls -] BT Mesa TvPE * | [<-->] CS _cHas # | Pex!) ox RSPLS_FAILED METHOD if xspls_cr_methods~derive. + se t mesg messages + <> @9 chas characteristic combination: source and target * fields included; do not change the source * fields < rspls failed exception CLEAR © t_mesg. FIELD-SYMBOLS: ‘TYPE any, «matgrp> TYPE any. ASSIGN COMPONENT */BIC/ZD_MAT' OF STRUCTURE ¢_s_chas TO . ASSIGN COMPONENT */BIC/ZD_MPLGRP' OF STRUCTURE ¢_s_chas TO . CASE . December 2016 28How to...Create a Characteristic Relationship type SQL-script oy WHEN ‘COPALO1002". = '000000100". WHEN ‘COPA102302". = "000000100". WHEN ‘COPASOOLOL'. = "000000101". WHEN ‘COPASOOLDO'. - 000000101". WHEN ‘COPASGO122". «matgrp> = '000000102" WHEN ‘COPASOO120". = "000000102". ENDCASE. ENDMETHOD. + ~ + | [<--] BT _LOORUP_ATTRIBUTE TvPE ‘TREXT_LOOKUPATTRIBUTE ao -] Et MEsG TyPE IF_RSPLS_CR_TYPES=>7N_T_MESG ey TICKED ox METHOD if_repls_cr_methods~derive_hdb. RAISE EXCEPTION TYPE cx_rer_x message PORTING text = 'IF_RSPLS_CR_METHODS~DERIVE_#DB-01-". ENDMETHOD. + SELDR_TO_RANGE TYPE RSDD_TSX_SELDR | [<---] ET_RANGE Tepe RSDRI_T_RANGE December 2016How to...Create a Characteristic Relationship type SQL-script METHOD seldr_to_range. + => 1 tex_seldr selection table (contains here only cart. product . selection with CHAVLs but in complex OLAP format) + < et range selection table in simple range table format DATA: 1_¢ range TYPE redri_e range, lis_rng TYPE rrrangesid. FISLD-SYMBOLS: <1_ex_seldr> TYPE rsdd_sx_seldr. CLEAR e_t_range. LOOP AT i tex seldr ASSIGNING <1_sx_seldr>. 1_s_zange-chanm = <1_sx_seldr>~chanm. LOOP AT <1_ex_geldr>-range-range INTO 1_¢ rng. Ls_range-sign = 1_s_rng-sian. ia _range-compop = 1s xng-opt. lis range-low = - 1_s_zng-low. Ais_range-high = 1_s_rng-high. ABEEND 1_¢ range TO € t range. ENDLOOP. ENDLOOP. ENDMETHOD. ENDCLASS. December 2016THE BEST-RUN BUSINESSES RUN SAP~ SARA