20110110 Reading Enhanced Data Source Fields For The Remote Cube

902 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
902
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
50
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

20110110 Reading Enhanced Data Source Fields For The Remote Cube

  1. 1. Reading Enhanced DataSource fields for the Remote CubeApplies to:SAP BI 7.0. For more information, visit the EDW homepage.SummarySAP Remote Cube does not display the enhanced fields in the data source. The system does not runCustomer exits and application extensions (customer exit, BTE, BAdI) for direct access to the source system.For reference click here. To overcome this shortcoming / limitation, the standard extractor should beenhanced at the Enhancement Point.Authors: Sujay V Koparde, Rajesh MichaelCompany: CapGemini India Pvt Ltd, Bangalore.Created on: 10 January 2011Author BioThe authors work for CapGemini India. Expertises include ABAP and SAP BI.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 1
  2. 2. Reading Enhanced DataSource fields for the Remote CubeTable of ContentIntroduction ......................................................................................................................................................... 3Scenario .............................................................................................................................................................. 3Remote Cube ...................................................................................................................................................... 3 Definition ......................................................................................................................................................... 3 Approach to Scenario...................................................................................................................................... 3 How to Implement ........................................................................................................................................... 3Enhancement Option .......................................................................................................................................... 3 Definition ......................................................................................................................................................... 3 Approach to Scenario...................................................................................................................................... 3 How to Implement ........................................................................................................................................... 3 Sample Code .................................................................................................................................................. 9 Output............................................................................................................................................................ 10Related Content ................................................................................................................................................ 11Disclaimer and Liability Notice .......................................................................................................................... 12SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 2
  3. 3. Reading Enhanced DataSource fields for the Remote CubeIntroductionSAP BI Remote Cube does not display the data for the fields which are enhanced in the Datasource. For theenhanced fields to be populated, Customer Exit has to be written using TCode CMOD. However incase ofRemote Cube, Customer Exit is not called and hence the enhanced fields are not populated.ScenarioWe have installed Reporting Financials (EhP3) from the Business Content in the module FinancialManagement & Controlling. According to the design there is a Multiprovider which has a Standard Cube andRemote Cube (On the same Datasource). The remote cube is used for Data Reconciliation. The Datasourcehas to be enhanced from different Tables as per the requirements. In case of Standard Cube, enhancedfields are populated using Customer Exits. However this does not work for Remote Cubes.In this document we will take an Example on the Datasource ‘0FI_AR_30’ which has been enhanced with thefields: ZZKUNN1 (Sold-to-party), ZMPFLAG (Multi Payer Flag), ZSUPCARR, ZBKTXT, 0LOGSYS,ZDUN_PROC.Remote CubeDefinitionA Remote InfoCube is a virtual InfoCube that does not physically store its own data in BW.Approach to ScenarioThe approach to scenario is by means of Implicit Enhancement Option explained next.How to ImplementThe scenario is implemented by means of Implicit Enhancement Option explained next.Enhancement OptionThe Enhancement Framework enables the customers to add functionality to standard SAP software withoutactually changing the original repository objects, and to organize these enhancements as effectively aspossible. One of the ways of enhancement is by means of enhancement points.DefinitionEnhancement Options/Points are lines of code which are executed in addition to the existing SAP standardcode. There are two types of Enhancement Points: Explicit enhancement points which are provided by SAPand the implicit enhancement points which are inherently available at the beginning or end of functionmodules and subroutines.Approach to ScenarioSince the SAP Remote Cube doesn’t call custom function modules (which are part of the enhancement‘RSAP0001’), we can overcome this issue by implementing the implicit enhancement options in the extractorfunction module. Here we will take an example of Customer Line Items Datasource ‘0FI_AR_30’ to explainthe process involved. The corresponding extractor function module in which we would be implementing theimplicit enhancement option is ‘SREP_FIAR_30’.How to ImplementStep 1: Goto TCode RSA2 and enter the Datasource NameSAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 3
  4. 4. Reading Enhanced DataSource fields for the Remote CubeStep 2: Go-to the extractor function module ‘SREP_FIAR_30’.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 4
  5. 5. Reading Enhanced DataSource fields for the Remote CubeStep 3: Choose the ‘Enhance Source Code’ optionStep 4: Identify the positions where implicit enhancement options are present.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 5
  6. 6. Reading Enhanced DataSource fields for the Remote CubeStep 5: This would highlight the places in the code where the implicit enhancement options are present.Step 6: Right click on the line displayed at the end of the function module and select Create Implementation.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 6
  7. 7. Reading Enhanced DataSource fields for the Remote CubeStep 7: Select ‘Code’ in the pop-up that comes up.Step 8: Give a name and short text to the enhancement implementation being created.Step 9: On saving the enhancement implementation in the appropriate package we get new lines as belowwith an empty line to insert the code. The code logic to fill the enhanced fields can be written here either bymeans of a separate include program or directly inserting the code between ENHANCEMENT 1ZIMP_FIAR_30 and ENDENHANCEMENT statements.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 7
  8. 8. Reading Enhanced DataSource fields for the Remote CubeStep 10: Once the code logic is written we have to activate the enhancement implementation.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 8
  9. 9. Reading Enhanced DataSource fields for the Remote CubeSample CodeThe code logic to fill the enhanced fields depends on the fields appended. This would be the same code thatwould have been written in any custom function module (part of the enhancement ‘RSAP0001’) for otherSAP Cubes.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 9
  10. 10. Reading Enhanced DataSource fields for the Remote CubeOutputThe Enhanced fields are populated as below:SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 10
  11. 11. Reading Enhanced DataSource fields for the Remote CubeRelated Content 1) For more information on BI, visit the Business Intelligence homepage. 2) For more information on Enhancement Points, visit Enhancement Framework page. 3) For more information related to virtual provider, visit Virtual Provider Page.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 11
  12. 12. Reading Enhanced DataSource fields for the Remote CubeDisclaimer and Liability NoticeThis document may discuss sample coding or other information that does not include SAP official interfacesand therefore is not supported by SAP. Changes made based on this information are not supported and canbe overwritten during an upgrade.SAP will not be held liable for any damages caused by using or misusing the information, code or methodssuggested in this document, and anyone using these methods does so at his/her own risk.SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content ofthis technical article or code sample, including any liability resulting from incompatibility between the contentwithin this document and the materials and services offered by SAP. You agree that you will not hold, orseek to hold, SAP responsible or liable with respect to the content of this document.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com© 2011 SAP AG 12

×