CostCentre in Purchasing Cube

Hi All,
    I am using a standard SAP Business content Cube 0PUR_C01.Extractor are 2LIS_02_ITM and 2LIS_02_SCL.We have got a new requirement to see CostCentres in this report.None of these extractors have 0COSTCENTER,instead there is an other extractor 2LIS_02_ACC which carries account assignment(CostCentres) with Purchase Orders.
     What would be the best design to get CostCentres into 0PUR_C01.
Any input is appreciated.Points assured.
Thanks
Neo

Hi Neo,
Did you resolve this issue?
Thanks

Similar Messages

  • Purchasing Cube

    Hi,
    Hi experts,
    I need to create a purchasing cube containing data at PO level.
    The data that client is after is coming from following datasources:
    2LIS_02_CGR
    2LIS_02_ACC
    2LIS_02_SGR
    I need to build cube bringing data from above datasources.
    Now what should be my approach for data model?
    If we don't have any standard cubes containing the line item, should I use the standard DSO as my first layer and build my own cube on top of it?
    Should it be 1 DSO 1 Cube and 1 Multiprovider?
    There is not any specific requirements from client in terms of reporting they just want the line item purchasing data in cube.
    Please advice,
    Thanks,
    Sajjad.

    Hi
    Why don't use Info source..?
    Load the data from 3 datasources to Info source.
    from here laod the required fields to DSO using transformations.
    Then build CUBE upon this DSO.
    Just my suggestion
    Hope this helps
    Regards,
    Venkatesh

  • Purchasing Cube re Initialization

    Hai Friends,
    I am going to re initialize the Purchasing Cube in BW side. Please tell What all are the steps will do in R/3 Side before re initialize the Cube in BW.
    Thank You
    Balajee Kannan

    Hello Balajee,
    If there is already a Init, then either you should delete that Init or you can create a new init without overlapping the time periods.
    Example : Init 1 : 01.01.2005 - 01.01.2007
    Then you cannot create another init with the date greater than 31.12.2004 and less than 02.01.2007.
    In the InfoPackage selection screen mention the date from and to date (in your case to date is 6/22/2007).
    If you don't want old init then delete the Init from the InfoPackage goto Schedule menu -> Init option for source system -> delete it
    Then load the Init data.
    Thanks
    Chandran

  • Stock in transit using purchasing cube

    Dear Friends ,
    I would like to create a key figure  Stock in transit based on My purchasing cube.
    DSO 0PUR_O02
    Cube 0PUR_C02
    Not dilivered qty. of open Purchase order is considered as stock in transit in our
    scenario.
    1) I would like to know how can we determine the open PO. According to me its simple
       open qty = PO qty - GR qty and if open qty is more then 0 then its should be considered
    open po. But in our case some time supplier give us some less qty and even we said po is
    closed. and somtime supplier give us more qty and we said po is closed.
    now please advice me how can we determine that PO is closed or not.
    regards,
    Malik

    Hi,
    You can do it, but you need to create the keyfigure, which will inclued Movement types or Process keys,
    You just see the 0TRANSSTOCK key figure in 0IC_C03 cube, which is non-cumulative keyfigure and internally having two keyfigures, so in that way first you analyze the concept behind that and do.
    Thanks
    Reddy

  • Fields in purchasing cube

    Hi experts,
    I am using the cube 0pur_c01 which is loaded from 3 datasources 2lis_02_itm, 2lis_02_scl, 2lis_02_s012.
    But there are only few fields in this standard cube. I want to add some more fields.
    Can anyone please suggest me what are the major fields for Purchasing data. So that i will include them into my infocube.
    Regards,
    Bhadri M.

    Hi,
    We have modified our cube to contain the following key figs and charracteristics.  These are available by modifying the standard datasource by changing it in LBWE and pulling in additional fields available for selection.
    1.  Characteristics which are of use are as follows:
    Calendar Day
    Calendar Year/Month
    Calendar Year/Week
    Fiscal year / period
    Fiscal year variant
    Calendar Year/Quarter
    Base Unit of Measure
    Local currency
    Country key
    Company code
    Number of purchasing info record
    Purchasing info record category
    Material
    Valuation type
    Product Description
    Material group
    Purchasing organization
    Indicator: Data to Be Canceled
    Vendor
    Version
    Value Type for Reporting
    Flag for Contracts
    Plant
    Storage location
    Supplying Plant
    PO Number
    PO Line Number
    Purchasing document type
    Puchasing document category
    "Delivery Completed" Indicator
    Item Category in Purchasing Document
    Reason for Ordering
    Acct Assignment Category
    Control indicator for purchasing document type
    Confirmation control key
    Tax on sales/purchases code
    Shipping conditions
    Purchasing group
    2.  Key Figures of use:
    Number of deliveries
    Delivery Date Variance 1
    Delivery Date Variance 2
    Delivery Date Variance 3
    Delivery Date Variance 4
    Delivery Date Variance 5
    Delivery quantity variance 1
    Delivery quantity variance 2
    Delivery quantity variance 3
    Delivery quantity variance 4
    Delivery quantity variance 5
    Invoice amount: Returns
    Weighted total delivery time
    Effective order value of returns
    Value of goods received in local currency
    Goods receipt value as at posting date
    Invoice Receipt Quantity as at Posting Date
    Invoice Amount as at Posting Date
    Actual goods receipt quantity
    Goods receipt quantity of returns
    Goods receipt qty in base unit (calculate wtd.delivery time)
    GR value: Returns as at posting date
    Invoiced amount
    Invoice receipt quantity of returns
    IR quantity: Returns as at posting date
    IR value: Returns as at posting date
    Invoice receipt quantity
    Effective purchase order value
    Target delivery quantity
    Order quantity (returns)
    Number of contract items
    Number of scheduling agreement schedule lines
    Number of purchase order schedule lines
    Number of purchase order items
    Order quantity
    Number of quotation items
    Number of request for quotation items
    Number of scheduling agreement items
    Total delivery time in days
    Net Purchase Order Value
    Purchase Main IV Value
    Cheers...

  • Purchasing cube designing, update rule mapping for 0calday

    Hi All,
       Iam designing cube for Purchasing module in BW. Iam having doubt in mapping for 0calday in update rules, is it with document date or scheduline date. I have searched in SAP cube 0PUR_C01, it is mapped with 0SCHED_DATE( schedule line date). How the difference comes when we choose document date and schedule line date.
      FYI, we are using only schedule line data source, which is giving relevant information.
    Thanks,
    Ram

    Hi Ram,
    Please note:
    0SCHED_DATE: The schedule line date is the day on which the scheduled quantity of the material is to be delivered.
    0DOC_DATE: The date on which document has been craeted.
    Use the first one for purchasing.
    Thanks...
    Shambhu

  • Purchasing Cube -- 0PUR_C01.. "Added record" is showing zero in request

    When i try to load the data to this cube, my trasfer record is showing values while Added Record is showing zero values. Whats the problem. Please advise !!

    Hi,
    Check whether do you have defined the industry sector in R/3. This has to be done before filling the setup table. search the forums with note no 353042.
    This is done with the help of Transaction MCB_ which you can find in the OLTP IMG for BW (Transaction SBIW) in your attached R/3 source system.
    Here you can choose your industry sector. 'Standard' and 'Consumer products' are for R/3 standard customers, whereas 'Retail' is intended for customers with R/3 Retail only.
    You can display the characteristics of the process key (R/3 field BWVORG, BW field 0PROCESSKEY) by using Transaction MCB0.
    If you have already set up historical data (for example for testing purposes) by using the setup transactions (Statistical Setup Programs) (for example: Purchasing: Tx OLI3BW, material movements: OLI1BW) into the provided setup tables (for example: MC02M_0SCLSETUP, MC03BF0SETUP), you unfortunately have to delete this data (Tx LBWG). After you have chosen the industry sector by using  MCB_, perform the setup again, so that the system fills a valid transaction key for each data record generated. Then load this data into your connected BW by using 'Full update' or 'Initialization of the delta process'. Check, whether the system updates data into the involved InfoCubes now.
    If all this is not successful, please see Note 315880, and set the application indicator 'BW' to active using Transaction 'BF11'.
    Regards,
    Anil Kumar Sharma .P

  • Fiscal year period quarter in purchasing cube

    *Dear friends,*
    *I want to make one query on the basis of fiscal year  Qurterly . So please what is infobject in purchasing data cube is useful for making this query. Please guide me*
    *Thanks and Regards*
    *Anil*

    Hi,
    due to the fact that you dont want to use the quarter of the calendar year, you should build up an appropriate one and add it to the cube. Also you should fill it by formula or routine.

  • Getting Double values in Purchasing cube

    hi experts,
    I m getting double values for 0po_items and ocontr_item in purchasing data cube 0pur_c01.
    i have also applied the test rule in routine ,that values are fine.
    but in cube values are getting double.
    please help..........

    Hi,
    It seems like you are loading data into cube using 2 DataSource  and there is no (consolidated) dso in between.
    If the KF say (qty) you are mapping from both the datasource to the cube, it is going to be doubled in report as 2 records will be found in cube.
    I suggest try to load a single valid record (PO and lien item) one by one into the cube and do check the values in cube for each process. You will get good idea how cube behave while loading data from diff. sources.
    Also try to bring in the one dso where you consolidate the data as per report requirement and then move that data into Cube, will give you required output.
    Thank-You.
    Vinod

  • Error while loading Purchasing Cube.

    Hi All,
    I am loading the data to Purchasing Group Cube "0PUR_C04" with the data source 2LIS_02_SCL. The laod fails saying that "The material MB0214363L does not exist or is not activated" When I checked the same material in R/3 I could see it as the deleted material. I am unable to load the data in BI even when in Error Handling I select "Update valid records". Please guide me in that, its very urgent. I will assign points.
    Thanks and Regards,
    Sangini.

    Select the option load even if master does not exists in the InfoPackage
    OR
    Load the master data for material and activate it
    Now reload the transaction data.

  • More records in Purchasing Cube than in PSA.

    Dear Folks,
    Right now i'm working on 0PUR_C01 Cube.In Quality server, i checked the data in Cube after executing the DTP and found that records are getting increased.Records in PSA(2152),but in Cube(2359),there are some routines in the Transformation checked them too they are ok.Transformation has 2 rule groups.And interestng thing is that we had the KF ZDCOUNT with rule type constant(1), and i found that for some records count=0.
    appreciate your quick reply.
    Regards,
    Rams.

    Hi
    As you have small no of records, run the DTP in Debud mode ( simulation mode) and check why you are getting 0 values from count key figure.
    If you have any end or Expert routine, you may get more records in target than source.
    Regards,
    Venkatesh

  • Net price aggregation in Purchase cube

    Hi,
    I have enhanced 0PUR_C01 cube to have Net price key figure, which I am getting from 2LIS_02_SCL. Problem I am facing over here is net price is getting aggregated in cube. Net price key figure is created with exception aggregation with Material as ref characteristic.
    Can anyone explain how to use price/rate figures can be used in such cases?
    regards,
    Vikram.

    Hellow Vikram
    Could i know, How did you solved.....?   I also facing the same problem.
    But for me i am using exception aggrgation as "Summation" only.
    Regards
    Raaju Saravanan

  • Discrepancy in Purchasing cube

    Hi Frndz,
    There is a problem in Invoice amount.Total invoice amount is coming differently in BW side compared to R/3.
    Even i am not able to get how they are calculating invoice amount as posting date.
    Please help me on this regard.

    How is total invoice amount being calculated in BW?By using a calculated key figure or by using some update rule?
    Compare the calculation method used in BW with the logic from R/3.
    Maybe some invoice posted in R/3 have got missed in delta data loads to BW.Often missed postings is the reason for such mismatch.
    cheers,
    Vishvesh

  • Cubes for Purchase

    Hi all,
    we want to shift our ABAP reports to BI. There are some purchase reports that are made up of using following tables:
            EKKO, " Purchasing Document Header
            EKPO, " Purchasing Document Item
            EIKP, " Foreign Trade: Export/Import Header Data
            KONV. " Conditions (Transaction Data)
    Are there any cubes in BI that capture data as these tables do?
    Please respond.
    Best Regards,
    AI.

    Hi,
    Purchasing cubes:
    0pur_C01: purchasing data
    0pur_C02: vendor evaluation
    0pur_C05: vendor evaluation data
    0pur_C04: purchasing groups
    0pur_C09 : service level- purchase orders
    Regards,
    Chendrasekhar

  • Combining Purchasing and AP data

    Trying to combine a bit of AP data with some Purchasing info.  The data mix would be about 75-80% Purchasing data to 20-25% AP data.  Multiproviders don't work unless the format is the same, and infosets are problematic.  We've got a cube built for each, but now are trying to figure out the best way to proceed.  We've hit upon 4 solutions so far, each of which have their own issues:
    1) Infoset solution 1 -- Infoset both cubes
    2) Infoset solution 2 -- Infoset the purchasing cube and outer join an AP DSO
    3) Build the AP cube out to mirror the format of the Purchasing cube (plus the added AP fields) and fill in the needed Purchasing data using an ABAP lookup in the transformation to fill the gaps of data from Purchasing.
    4)  Add the fields needed from AP to the Purchasing Cube and look up the data during Purchasing loads (similar to option 3).
    Any other solutions anyone else can come up with?  Thanks in advance.

    Did you figure out what is the best approach...bcoz I am having the same situation.
    could you pl throw some more light if you had any other issues using any of the sol
    mentioned above.

Maybe you are looking for