Addition of key figure in master data attributes.

Hi All,
I have a scenario to DPO (Days payable outstanding) amount in FI.
I need to calculate purchases amount From 2LIS_O3_BF Based on the given input dates from customer .The Company code wise ACCOUNT PAYABLE amount  to be calculated from OFI_AP_4.
There is no key link between this.
So i want to add one key figure in Company code attributes to calculate and store account payable amount using Routine. Then i will give this attribute as navigational  in ODS of 2LIS_03_BF .
Can i have key figure in attributes of masterdata. I need to load this daily to calculate amount.
Is there any other solution, how performance will be effected with this solution.
Thanks,
JO

Hi Joseph;
Yes, you can add a KF as one attribute of master data.
The other solution that I see is you create a DSO as a target of 2LIS_03_BF and then a transformation with company code. Direct link between DS and IO is not advise because one is delta and the other is full (you could have some problems).
But if it's my choice... enhance the 0COMP_CODE_ATTR.
Regards;
Ricardo

Similar Messages

  • Maintain key figure in master data attribute

    Hi,
    For some special requirement I have maintained  key figure in master data attribute but I am unable to use key figure attribute in infocube.  Please help.
    Thanks & regards,
    Goutam

    Hi,
    See in the below URL...under "Customer Exit Variables in BW/BI Reports", you can have all examples about Cust Exits and Replacement Path.
    http://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
    Thanks
    Reddy

  • Key figure in Master data

    Hello
    I have a key figure defined in the master data info object.
    Now the values of the key figure are not getting updated in the info object after running the DTP.any suggestions as to why this could be happening.
    One thing i noticed is that the length of the key figure is 9 digits and in the source field it is 15 digits. Does that make a difference at all.

    Hi,
    Even you can maintain key figure as an attribute for master data, it wont be a problme. Define your keyfigure as an attribute for master data info object and load the master data again.
    Regarding the length of the field between source and BW, it should get atleast 9 digits (I guesss).

  • How to  extract  master data  attribute from  r/3 to bw give steps details

    how to  extract  master data  attribute from  r/3 to bw give steps details screenshots

    Hi
    Go through the below process to extract Master Data Attribute from R/3
    Hi,
    Maintaining Generic DataSources
    Use
    Regardless of the application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any transparent table, database view or SAP Query InfoSet, or using a function module. This allows you to extract data generically.
    Procedure
    Creating Generic DataSources
    1. Select the DataSource type and specify a technical name.
    2. Choose Create.
    The screen for creating a generic DataSource appears.
    3. Choose the application component to which you want to assign the DataSource.
    4. Enter the descriptive texts. You can choose any text.
    5. Select the datasets from which you want to fill the generic DataSource.
    a. Choose Extraction from View if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
    After you generate the DataSource, you have a DataSource with an extraction structure that corresponds to the database view or transparent table.
    For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
    b. Choose Extraction from Query if you want to use a SAP Query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
    Notes on Extraction Using SAP Query
    After you generate the DataSource, you have a DataSource with an extraction structure that corresponds to the InfoSet.
    For more information about maintaining the InfoSet, see the System Administration documentation.
    c. Choose Extraction Using FM if you want to extract data using a function module. Enter the function module and extraction structure.
    The data must be transferred by the function module in an interface table E_T_DATA.
    Interface Description and Extraction Process
    For information about the function library, see the ABAP Workbench: Tools documentation.
    d. With texts you also have the option of extracting from fixed values for domains.
    6. Maintain the settings for delta transfer, as required.
    7. Choose Save.
    When performing extraction, note SAP Query: Assigning to a User Group.
    Note when extracting from a transparent table or view:
    If the extraction structure contains a key figure field that references a unit of measure or a currency unit field, this unit field has to be included in the same extraction structure as the key figure field.
    A screen appears on which you can edit the fields of the extraction structure.
    8. Edit the DataSource:
    ○ Selection
    When you schedule a data request in the BI scheduler, you can enter the selection criteria for the data transfer. For example, you can determine that data requests are only to apply to data from the previous month.
    If you set the Selection indicator for a field within the extraction structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
    ○ Hide field
    You set this indicator to exclude an extraction structure field from the data transfer. The field is no longer available in BI when you set the transfer rules or generate the transfer structure.
    ○ Inversion
    Reverse postings are possible for customer-defined key figures. Therefore inversion is only active for certain transaction data DataSources. These include DataSources that have a field that is marked as an inversion field, for example, the update mode field in DataSource 0FI_AP_3. If this field has a value, the data records are interpreted as reverse records in BI.
    If you want to carry out a reverse posting for a customer-defined field (key figure), set the Inversion indicator. The value of the key figure is transferred to BI in inverted form (multiplied by –1).
    ○ Field only known in exit
    You can enhance data by extending the extraction structure for a DataSource by adding fields in append structures.
    The Field Only Known in Exit indicator is set for the fields of an append structure; by default these fields are not passed to the extractor from the field list and selection table.
    Deselect the Field Only Known in Exit indicator to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list and in the selection table.
    9. Choose DataSource ® Generate.
    The DataSource is saved in the source system.
    Maintaining Generic DataSources
    ● Change DataSource
    To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
    You can change the assignment of a DataSource to an application component or change the texts of a DataSource. Double-click on the name of the table, view, InfoSet or extraction structure to get to the appropriate maintenance screen. Here you make the changes to add new fields. You can also completely swap transparent tables and database views, though this is not possible with InfoSets. Return to DataSource maintenance and choose Create. The screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource ® Generate.
    If you want to test extraction in the source system independently of a BI system, choose DataSource ® Test Extraction.
    ● Delta DataSource
    On the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the corresponding query. If you want to delete a DataSource, make sure it is not connected to a BI system.
    NR

  • Protect Master Data Attributes Netweaver 2004s BI 7.0

    Hi all,
    We have used 0EMPLOYEE in all of Human Resources Objects (DSOs and Cubes) and Finance Objects.
    0EMPLOYEE has many sensitive attriutes.
    We are currently able to protect key figures like Annual Salary and Characteristics like Social Secutiy Number.
    However, we cannot mark attributes like 'Mailing Address' etc as authorization relevant, and thus not able to protect them.
    Thus, we have decided to use a different InfoObject for e.g. ZEMPLOYEE (with only Non Sensitive attributes) in Finance
    objects.
    Is this a good solution? Is there a different way we can protect Master Data attributes in the report.
    Any comment will be appreiciated

    Since there is no way to protect sensitive attributes, it's a good solution... if ZEMPLOYEE refers to 0EMPLOYEE.

  • Master data, attributes, texts: ETL process

    Hi,
    I am new to SAP BW and have a question concerning the difference between master data attributes and texts. I am currently learning with the "sflight" example provided by SAP. There I have, e.g., a table like this:
    CARRID  CARRNAME          CURRCODE
    AA      American Airline   USD
    AB      Air Berlin         EUR
    AC      Air Canada         CAD
    These are my master data because these data won't change often - correct?
    What are then my attributes and texts?
    Thanks!

    Thanks Choudhary.
    I am Karthik, new to both, the community and SAP BI. I have a doubt similar to the main question, that goes like this.
    CARRID  CARRNAME          CURRCODE   TIME             COUNTRIES_OPERATION
    AA          American Airline     USD               9:00  AM       America
    AB          Air Berlin                EUR             10:00  AM       Germany
    AC          Air Canada             CAD             11:00  AM       Canada
    Similar to the above table, if suppose there are two other columns TIME and COUNTRIES_OPERATION,
    1.  Will TIME be included as "attributes" or "time characteristics" as TIME is an additional information of the master data key and there is  dimension table where we can define TIME ?
    2.  Will COUNTRIES_OPERATION be included as "attributes" or can this be included in "hierarchy"
    3. If not what can be used into "hierarchy" from the above table.
    Kindly excuse if my question is silly or if it does not make sense. I am very new to these terms and still in the learning curve.
    Thanking you in advance,
    Karthik.

  • Master data attributes with direct update...its very urgent

    Hi all,
    Could anyone tell me how to laod the master data attributes with direct update in the infopackge..
    provide steps to create master data attributes and how to load..
    Thanks,
    Manjula

    Hi Manjula,
    Flexible Uploading
    Transaction code RSA1—LEAD YOU TO MODELLING
    1. Creation of Info Objects
    • In left panel select info object
    • Create info area
    • Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
    • Create new characteristics and key figures under respective catalogs according to the project requirement
    • Create required info objects and Activate.
    2. Creation of Data Source
    • In the left panel select data sources
    • Create application component(AC)
    • Right click AC and create datasource
    • Specify data source name, source system, and data type ( Transaction data )
    • In general tab give short, medium, and long description.
    • In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
    • In proposal tab load example data and verify it.
    • In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
    • Activate data source and read preview data under preview tab.
    • Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
    3. Creation of data targets
    • In left panel select info provider
    • Select created info area and right click to create ODS( Data store object ) or Cube.
    • Specify name fro the ODS or cube and click create
    • From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
    • Click Activate.
    • Right click on ODS or Cube and select create transformation.
    • In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
    • Activate created transformation
    • Create Data transfer process (DTP) by right clicking the master data attributes
    • In extraction tab specify extraction mode ( full)
    • In update tab specify error handling ( request green)
    • Activate DTP and in execute tab click execute button to load data in data targets.
    4. Monitor
    Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used
    honor with points if this helps,
    Sudhakar

  • Error while loading to Master data attribute 0product

    Hi experts,
    While loading the data from 0material to 0product master data attribute i am getting a error ' 0MATERIAL : Data record 2421 (''300000072 '):Version '300000072 ' is not valid. I request u all to help me to solve this error.
    Diagnosis
        Data record 2421 & with the key '300000072 &' is invalid in value
        '300000072 &' of the attribute/characteristic 0MATERIAL &.
    System Response
        The system has recognized that the value mentioned above is invalid, and
        has processed this general error message. A subsequent message may give
        you more information on the error. This message refers to the same
        value, even though it does not state this explicitly.
    Procedure
        If this message appears during a data load, maintain the attribute in
        the PSA maintenance screens. If this message appears in the master data
        maintenance screens, leave the transaction and call it again. This
        allows you to maintain your master data.
    Please let me know what could be the problem....
    Regards,
    Prashanth
    Edited by: Prashanth Shetty on Jul 16, 2008 7:42 AM

    Hi,
       The issue is due to errorneous record.
    Delete the request in Master data and Try the following.
    1) Goto PSA --> filter the Status (Red or Green)
    Select the Red records and correct the data in which error is throwm.
    After correcting the data, save and Right click PSA and give Start update immediately.
    2) Load via Infopackage only to PSA and later update from PSA and check.
    Any one of the above 2 methods will solve the issue.
    Regards,
    Balaji V

  • Error while creating Data Source for master data attributes

    Hi BI Experts,
    Well its been some time for me that I have been part of Extraction in BI.I primarily handled reporting in my last assignments.
    I was trying extraction with flat files in SAP BI 7(new to sap bi 7 but very much familiar with BW3.5) but failed in the activity during master data attributes and text upload in infoobject (say IOSP_Mat).
    Here is the procedure that I did after creation of characteristic IOSP_Mat.I created a source system for flat file followed by data source for Master data attributes, i selected all the parameters correctly.i.e. csv file format, data seperator as   ,
    and other settings, now when i am trying to look at the proposed data in the next tab using Load example data.its not showing the desired result.The columns that I have maintained in Flat File is  MAT_NUMBER and MAT_NAME (with say 100 data in the file)
    same is the result when I am trying to load the text data too columns maintained are
    (LANGUAGE MAT_NUMBER Short Description)(same 100 data).
    now i used to rsa1old transaction  to upload the file using 3.5 version.i created info source for master data/text/hierarchies for  IOSP_Mat
    now when trying to upload it using info package for master and text data,I observe its(the data) not maintained in the characteristic IOSP_Mat.
    When I monitored ,I figured the data has not been even uploaded to the PSA level.
    Can you BI experts tell me the answer for this.
    Thanks,
    Srijith

    apologies to all of you for late response,
    was busy with some other activities.
    I don't remember the exact message,but I remember it was not loaded to even the PSA level.I will try it again and post the exact message.
    Thanks again for your quick response.
    Once again sorry to all of you for my late response
    Thanks,
    Sri

  • Map My Update Rule from a Master Data Attribute

    Hello experts,
    I haven't tried this scenario yet, hope you can help me, the Issue is this
    I have 2 InfoObjects ZPSCHRCHY and 0PROFIT_CTR from InfoCube WBS cost and allocations I want both the InfoObjects to be mapped to 0PROFIT_CTR attribute of 0WBS_ELEMT master data object, I have tried the Master Data Attribute but only 0PROFIT_CTR is an attribute of the Master Data.how can I mapped ZPSCHRCHY and 0PROFIT_CTR to 0PROFIT_CTR?, Is creating a start routine for it must be used? Thank you very much
    Regards and Thanks
    Chris

    PROGRAM UPDATE_ROUTINE.
    $$ begin of global - insert your declaration only below this line  -
    TYPES:
    BEGIN OF r_MD_WBS_ELEMENT,
       WBS_ELEMT  like /BI0/PWBS_ELEMT-WBS_ELEMT,
       OBJVERS    like /BI0/PWBS_ELEMT-OBJVERS,
       PROFIT_CTR like /BI0/PWBS_ELEMT-PROFIT_CTR,
    END of r_MD_WBS_ELEMENT.
    DATA: t_MD_WBS_ELEMENT  TYPE STANDARD TABLE OF r_MD_WBS_ELEMENT,
           wa_MD_WBS_ELEMENT TYPE r_MD_WBS_ELEMENT.
    $$ end of global - insert your declaration only before this line   -
    The follow definition is new in the BW3.x
    TYPES:
      BEGIN OF DATA_PACKAGE_STRUCTURE.
         INCLUDE STRUCTURE /BIC/CS8ZPSG030.
    TYPES:
         RECNO   LIKE sy-tabix,
      END OF DATA_PACKAGE_STRUCTURE.
    DATA:
      DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
           WITH HEADER LINE
           WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
    FORM startup
      TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
               MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
               DATA_PACKAGE STRUCTURE DATA_PACKAGE
      USING    RECORD_ALL LIKE SY-TABIX
               SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
      CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
    $$ begin of routine - insert your code only below this line        -
    fill the internal tables "MONITOR" and/or "MONITOR_RECNO",
    to make monitor entries
      REFRESH: t_MD_WBS_ELEMENT.
          SELECT WBS_ELEMT
                 OBJVERS
                 PROFIT_CTR
          INTO TABLE t_MD_WBS_ELEMENT
          FROM /BI0/PWBS_ELEMT
       FOR ALL ENTRIES IN DATA_PACKAGE
         WHERE WBS_ELEMT   = DATA_PACKAGE-WBS_ELEMT.
        IF sy-subrc EQ 0.
        Do nothing
        ENDIF.
    if abort is not equal zero, the update process will be canceled
      ABORT = 0.
    $$ end of routine - insert your code only before this line         -
    ENDFORM.

  • Ignore duplicate records for master data attributes

    dear  experts ,
                   how & where can i  enable "ignore duplicate records" when i am running my DTP to load data
                     to master data attributes.

    Hi Raj
    Suppose you are loading master data to InfoObject and in PSA you have more than one records for Key.
    Let's assume you are loading some attributes of Document NUmber ( 0DOC_NUMBER) and in PSA you have multiple records for same document number. In PSA this is not a problem, as Key for PSA table is technical key and which is different for every record in PSA. But this is a problem for InfoObject attribute table as more than  one records for primary key ( here 0DOC_NUMBER) will create Primary Key consraints in database.
    This issue can be easily avoided by selecting "Handle Duplicate Records" in DTP . You will find this option under *update" tab of DTP.
    Regards
    Anindya

  • Error in Master data attribute

    Hi Gurus,
    I Have got the following error while iam loading master data attribute
      Data record 5238 & with the key '000000000030022055 &' is invalid i
      value '4902430016629  &' of the attribute/characteristic 0EANUPC &.
    Regards

    Hi,
    Please perform the data load with the option via PSA (in infopackage). Right click on data source- > manage. Click on the request and edit the record in error.
    Hope this help. Let me know if you further queries.
    Viren

  • Pupulating Char with Master data attribute

    Hi,
    I need to populate the characteristic with a master data attribute value at the tranfer rules.
    Can anybody send me the code to do so.
    If it is at Update rules we have the option of Master data attribute of.
    But I need to do it at transfer rules.
    Thanks in advance.

    Hi Indira,
    It is difficult to give the exact code but, here is the pseudo code:
    In the start routine:
    select * from /bic/m<characteristic>
    into itab for all entries in datapak
    where ..............
    if sy-subrc = 0.
    sort itab by....
    endif.
    In the mapping for the info object, create a routine and the following code goes in there:
    read table itab with key ......
    if sy-subrc = 0.
    result = itab-********
    endif.
    Make sure you handle time dependencies if the master data attribute is time dependent.
    Hope this helps.
    Thanks and Regards
    Subray Hegde

  • No Master Data Attributes Value Loaded

    Hi
       I have a custom Master Data Info Object which gets it feed for a simple master data attribute data source.
        However none of the Master Data Attributes actually are populated though my request load is successful.
        I get 144913 records transferred but only 78596 added. Despite this I have not a single attributes value populated.
        Could the reason the data is dropping because I have 3 key fields in my datasource VIEW but only 1 Key defined in the Update Rule ? If yes, how can I change the Update Rule to include more Key Fields ?

    Hi Chris
    I request you to check the transforamtion between your data source and data target once again.
    When loading to data target, according to your transformation only the records will be updated to your data target. But all the records will get populated.
    Yes, Key fields are also one reason, if the duplicate rows being populated.
    Compare your data target data & RSA3 Extractor checker.Whether the duplicate records being added together or not
    Regards
    Saravanan.ar

  • Master Data Attributes issue in BEx

    Hi Everyone,
                            I have loaded Master Data Attributes and Texts for 0customer. 0Customer has one Display attribute. I add this into the Bex Query Designer.But the data for the display Attribute(SORT1) is not displayed in the Analyzer. I have maintained everything correctly. The Baclkend BI system has Data for the display attribute.
    Do we require to do any additional settings in Query Designer for the dat ato be shown when we drag the display attribute into Query Designer Panel. I have maintained the Display settings correctly in Query Designer
    Please Advise.
    Regards,
    Samir

    Hi,
    are you able to See no data in Field of Attribute(SORT1) or  are you not able to see field Attribute(SORT1) in report?
    if you are not able to see field Attribute(SORT1) in report, right click on 0Customer, select property and go to attribute tab. select Attribute(SORT1)  from left to right. click ok. you will get field Attribute(SORT1) in report.
    you are not able to See no data in Field of Attribute(SORT1). activate master data after maintaning master data and chech value is availble in attribute (SORT1)

Maybe you are looking for