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...

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

  • Fields in the cube

    Hi Experts
    Here client wants 200 fields in cube
    whether that is suggestable help me in this
    Regards
    Anand

    Hi,
    Its possible to have that many fields in the cube, but you have to consider what the reporting requirements are and how the data is connected, etc. You also have to consider how much data volume is going to be generated and at what level you are going to store the data in the cube. If your client is suggesting you to have line item level or granular data in your cube , suggest to them to have that in an ODS and provide jump queries from the cube to the ODS if necessary.
    If many of the fields are not going to be required for reporting at present or in the future, suggest to the client to have them in the ODS and a smaller subset of the fields in the cubes.
    Cheers,
    Kedar

  • Adding new fields to existing cube

    Hi all,
    We have a cube with data, now we added 2 new fields to the datasource. And want to add two more fields in the Cube to correspond to the new fields. What would be the impact on the data that is already there in the cube? Can I go ahead and add the fields in the cube and start extracting data? What I want to know is what would be the implications in such a scenario?
    Any insight or help would be appreciated and fully rewarded.
    Thanks,
    Mav

    Hi,
    At least from the experience I had there were no performance issues. The only issue would be in terms of the time taken to transport. The larger the amount of data ,longer the transport time.
    You can continue extraction of data for those 2 fields from that point on. No need to empty the data from the cube and reload again. Only thing is that the data in the past for these 2 fields may not be mapped to the existing data in the cube. If you want to do that dump the cube and reload. Otherwise the data will be mapped from the time you start extracting the new fields with the data in the cube.
    Cheers,
    Kedar

  • 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

  • User exit MM06E005 - Customer fields in purchasing document

    Hi,
    I am using user exit MM06E005 - Customer fields in purchasing document to validate the line items in PO and display the value at header level.
    My requirement is when the user enters the line items and press enter the validated value should get populated at header level.I had included a tab (customer tab) in that the value should get displayed.
    likewise for each and every line items the value should keep on changing.
    And
    I the field that i had added at header shows the value during the save but once we come out and enter again,it is not displaying the same.
    Regards
    Manoj

    Hi,
    Indeed the exit which you have specified MM06E005 comprises the enhancement for customizing fields and screens associated with it. may be you might not have activated the screen associated with the exit. the screen might have been created but missed while activating.
    Regards,
    Jagath

  • MM06E005 - Customer fields in purchasing document

    Hi,
    I am using user exit MM06E005 - Customer fields in purchasing document to validate the line items in PO and display the value at header level.
    My requirement is when the user enters the line items and press enter the validated value should get populated at header level.I had included a  tab (customer tab) in that the value should get displayed.
    likewise for each and every line items the value should keep on changing.
    And
    I the field that i had added at header shows the value during the save but once we come out and enter again,it is not displaying the same.
    Regards
    Manoj

    got my solution...

  • Missing fields in Purchasing View

    Dear all,
    We have got an issue like this.For our client we are using Workflow to
    create a material.For this we made a process like this .
    User1-Basic Data1&2
    User2-Sales Views
    User3 or User4-Purchasing Views.Both are having same roles in workflow.
    User5- MRP1,2,3&4 Views
    User6- Finance&Costing Views
    When we create a material,we are getting an issue in Purchasing View.
    In Purchasing View User 3 able to see all fields in Purchasing view.
    If User 4 tried to fill the data for this Purchasing View some fields
    are hidden,which we are not able to see.The missing fields are as
    follows.
    Purchasing Group,Plant-sp.matl status,Tax ind. f.
    material,Qual.f.FreeGoodsDis,Autom.PO,but both user3 and user4 share
    same roles in workflow.
    After that we had given SAP_ALL to User4 and tried to create a material
    using standard MM01,then also we are not able to see all fields in
    Purchasing View.But User 3 is able to see those fields through MM01 too.I have attached a document,please go through it.
    What would be the reason for this?Please suggest us possible
    solution,as soon as possible.
    Regards
    Ganesh.

    Hi,
    Option:1=>For user 3 and user 4 , problems in cretaion of material difference, Consult your Basis  Consultant.
    Option:2=>For hidden field,follow below steps( in user 3 , check and correct for user 4)
    1. Just click the tab ,(Which is hidden for user 4, in user 3 )and get the field name
    2.Go to T.Code: OMSR and enter that field name and get Selection Group in user 
    3.In USER 4,Go to T.code: OMS9 and select your material type and go to "overviews" .In the next screen, you can see your field selection Group, click that and you can make that field  required entry for User4 and save.
    Now try to create material in USER 4.
    Hope helpful to you and then reward.
    Regards,
    Biju K

  • 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

  • Addition of a field in a cube

    Hi
    I would like to know if I can add a field in a cube without deleting the data as I dont want previous data for this added field. I am just interested in the new data coming through Delta in the cube.
    Many Thanks.
    Kind Regards,
    Kate

    Hi Kate,
    You can proceed without deleting the data if you have the liberty of adding a new dimension and putting this char in the new dimension.
    If this is not possible then you can refer to the loopback process: create new cube > move data to the new cube > delete data from old cube > change and activate old cube > move data back to original cube.
    /people/dinesh.lalchand/blog/2006/02/07/loopback-process--follow-up
    Hope this helps...

  • ERS field in Purchase Order Line detail (Invoice Tab)

    Hi ... I was trying to figure out the priorities for ERS field in Purchase order ...
    What i could simulate is ...
    Case 1
    In case Vendor master has ERS = YES but in info record ( for vendor and material) NO ERS is defined.
    Then ERS field will get appeared in PO LINE detail with value NO (not set)
    Case 2
    In case Vendor master has ERS = No but in info record  (for vendor and material)  ERS is set.( NO ERS = not set)
    Then ERS field will not get appeared in PO LINE detail
    Case 3
    In case Vendor master has ERS = YES and in info record  (for vendor and material)  ERS is set.( NO ERS = not set)
    Then ERS field will get appeared in PO LINE detail with ERS = YES
    Here I am doubtful about case 2 .... I believe info record should always have priority over vendor , but system is not behaving as per expectation.
    Could u pls tell me the exact conditions when ERS field will not appeared and if appeared from where it will pick the default values in PO LINE details
    Regards
    SANDEEP

    the info record has precedence.
    The bad thing is, that this field is , contrary to other field that appear in vendor and info record,  has a  negative meaning.
    ERS field name in vendor is  auto eval GR settlement,
    while in info record it is : No ERS.
    lets do an example:
    V=vendor
    I = Info record
    P = purchase order
    X = box selected
    N = box not selected
    so we can have this 4 cases:
    VIP
    XNX
    XXN
    NXN
    NNN
    The 3rd  case NXN does not really make any sense.

  • Make short text field in Purchase order creation only display..

    Sir,
    Yeah my requirement is quite unusual, but such is the situation.
    I want to make the short text field in purchase order creation "only disply". what is happening is that user while creating PO is able to change the text of material in short text column. I want to make it only for display.
    Can it done on document type level, since for service type, and Text type of account assignment cat, only text field is filled up. so how to do it.
    Please assist...
    Rahul

    Dear Rahul,
    If you want to have the short text display only for standard item but not service item, you may check below customizing.
    Transaction SPRO:
    MM-PUR-PO
    -> Define screen layout at document level
    Field Selection group: Basic Data, Item
    Field Selection Key:  PT0F Standard item purchase order
    Field: Short text -> set as display
    Hope this help.
    Ian Wong Loke Foong

  • Significant of key field in Info cube table

    Hi,
    what is significant of key field in Info cube table?
    Best regards,
    dushyant.

    hi ,
          key figures are very important in tables, when it is in cube it act as dimensions
    for the reporting purpose see this scenario
    the table has following fields
    student no
    student name
    student attendance
    student mark
    in this scenario when we want report according to student no its normal we would get, but when we want according to attendance,marks we dont get report according to attendance and mark, so we put all those fields in key fields.
    So we could say that Key fields are the dimensions and according to this we get reports
    thank yu

  • Implementation Of Badi ME_GUI_PO_CUST for adding fields in Purchase Order

    Hi All
       I am implementing BADI ME_GUI_PO_CUST / ME_PROCESS_PO_CUST to add additional fields in Purchase Order.
    The implementation of the BADI ie the Subscreen of the fields to be added appears in  transaction ME23N but it does not appear in the transaction ME22N and ME21N.
    Can anyone help me on this.
    Thanx.
    Moderator message - Duplicate post locked
    Edited by: Rob Burbank on Jul 10, 2009 12:10 PM

    check the answer
    [New tabs added by Badi ME_GUI_PO_CUST not seen in ME21N and ME22N;
    bye

  • PR to be made mandatory field in Purchase Order

    Hello,
    PR to be made mandatory field in Purchase Order.
    How i can do this in SAP ?
    Regards
    Rahul

    Hi,
    First check your PO document type which you want to make PR number field as mandatory in ME21N.
    Then Goto -> SPRO- Material Management - Purchase order- define document type for Purchase order - E.g NB- check the field selection assignment ( NBF)
    Next,
    Goto - Define screen layout at document level ( t.code OMF4) SELECTION GROUP Reference data, item and under Field selection key as NBF.
    Field name - Purchase Requisition as Required entry with flagged check box.
    Now in purchase order for the choose document type NB=PO the PR field as required entries.
    System will allow to create PO only with reference to PR.
    Thanks
    Thiru

Maybe you are looking for

  • How can i set the page margin to be a different width on the first page than the rest in Pages?

    I am creating an ebook where I want the first page to be the cover, but don't want to have a margin round the edge. However the remaining pages I want a margin so the text looks good (as I am also exporting this as a PDF) Is there any way to do this

  • Ipod and itunes(especially itunes)will freeze while syncing

    i pod and itunes will freeze while syncing, all apps are there, but no music?Itunes says ipod has latest updates, I reinstalled  Itunes, powered off/ sleep  a couple times still not syncing any help? Thanks

  • DME - Duplicate File

    Hi Guys While running the RFFOUS_T program, there were some memory issue in our production system and it got cancelled. In the spool ( thru SM37) I see data of 2 employees with their bank and amount information. When we fixed the memory issue and re-

  • How to compare empty in oralce stored proceure..

    Hi how to compare empty in oralcle stored procedure But this code is not working properly..... please suggest me.. create or replace PROCEDURE ACHECK v_number in number IS output float; cursor no_cursor is select * from ATEST; BEGIN for value_cursor

  • XML dtabase option fro mrca 10.1.2.0.3

    Hello, I am trying to run the metadata repository creation assistant 10.1.2.0.3 against a 10.2.0.2.0 database. I get the following error: The Oracle XML Database option of the database is not configured. Please enable Oracle XML Database option and t