Data at summary level

Hi All,
In my reports, we have to display both detail and summary level data.
Detail column - Director, Region, Employee, Application Id,product id, Decision date, Avg Qty
Summary Column - Director, Region , Employee, Avg Qty
Issue - Data in summary level is incorrect.
Approach - In summary level, when we pull product id and decision date we get correct results but data will split for each product& decision date. how do we achieve this in reports
Request inputs
Thanks,
Nithya
Edited by: 973422 on Mar 24, 2013 8:30 PM

Hi Nithya,
Would you please provide more information
"In summary level, when we pull product id and decision date we get correct results but data will split for each product& decision date."....Not Clear
Provide some sample data with Issue Explanation
Thanks
NK

Similar Messages

  • Can I summarize data from a line item ODS into a higher summary level?

    Hello friends,
    1) Can I summarize data from a line item ODS into a high summary level and store the results into another ODS?  If so, can you discuss the approach at a high level...i.e. whether or not a start up routine is needed?
    2) Once data is stored in an ODS, can a routine be written to update specific fields in the ODS after the data has already been loaded into the ODS.  As a simple example, is it possible to write a routine that simply multiplies "Field A" by "Field B" and stores the result in the ODS as "Field C"?  (Most of the time I would do this calculation in Bex, but in this one case, I have the need to calculate and store "Field C" in the ODS.)
    Thank you.

    1.- Yes, you can sumarize data in other ODS. Connect both ODS and use aditions for key figures intead of overwriting.
    2.- You can do it in load time, in update rules, is not necesary to wait for ODS was loaded

  • What is summary level concept in data warehousing?

    I am new to data warehousing.
    can anybody explain about the summary level and higher level concepts in data warehousing?

    If I understood your question:
    Data warehouses are intended for analytic processing (OLAP). Basically, It's based on queries that would take too long in OLTP (transactional processing). So you build a new Database, with a relatively denormalized model (you probably have heard about Star-Schema modeling, etc).
    Look for Bill Inmon (Building the Data Warehouse) and Ralph Kimball (The Data Warehouse Lifecycle Toolkit : Expert Methods for Designing, Developing, and Deploying Data Warehouses) Data warehousing concept books. Mr. Inmon and Mr. Kiball pretty much "created" the Data Warehousing concept. You'll also find a Book from Oracle Press, named "Oracle XX Datawarehousing Guide" (XX = DB Release).
    Also, you have plenty documentation about how to create a data warehouse in OTN. See thread below:
    OLAP and cubes tutorials
    Hope it's useful for you!
    Regards,
    Marcos

  • Ms project 2010 - grouping how to show the duration between dates at the summary level

    Hi we have a ms project plan where we have used grouping to present the task breakdown in a different structure.
    This works great we get at the summary level the start and finish dates correctly but the duration gives us only the Maximum value for the durations of the tasks within the group. (is it possible to change the maximum calculation?)
    We would like to be able to determine the duration at the summary level. Of note if we use functions such as projdatediff(start,finish) this only gives the result at the detail level and does not show at the summary level - even if we check the do the
    calculation for the task and group levels 'use formula' radio button.
    is this a bug???.
    If we use a numeric calculation such as finish-start we get a figure that allows  us to repeat the calculation at the group (summary) level. but firstly we do not actualy know what the numeric value represents. i.e (Finish-Start)*10000 for
    a duration of 0.5 hours = 208.33 ,1 hr= 416.67,1.5 hrs =625, but 8 hrs is giving 10833.33 which is 24 * the 1 hour figure
    duration  finish-start  start           finish
    0.5hrs     208.33    Tue 31/01/12 Tue 31/01/12
    1d          10833.33 Tue 31/01/12 Wed 01/02/12
    8 hrs      10833.33 Tue 31/01/12 Wed 01/02/12
    0.19d     625          Wed 01/02/12 Wed 01/02/12
    1.5 hrs   625          Wed 01/02/12 Wed 01/02/12
    0.13d     416.67     Wed 01/02/12 Wed 01/02/12
    1 hr        416.67     Wed 01/02/12 Wed 01/02/12
    Anyhow looking for suggestions on how to get a calculation of the difference in two dates as units (pref days) into the group level summary.
    Many thanks Mike

      Hi John ,
    This is better ..... Now the Text1  column is the correct duration .. Is it possible just to display the Text 1 Column instead of Duration Column ? is it a right practice in using Microsoft Project or scheduling ? This is an alternate solution
    ...Do you think that there is a solution to  that problem ?
    Task Name
    Text1
    Duration
    % Complete
    Start
    Finish
    F10E ( Level 10 )
    273
    40d
    0%
    10 Apr '12
    10 May '13
    Hospital Admin
    40
    40d
    0%
    10 Apr '12
    05 Jun '12
    Hospital Move- Vacate F10E
    40
    40 d
    0%
    10 Apr '12
    05 Jun '12
    Eastern/Kelson
    238
    40d
    0%
    30 May '12
    10 May '13
    Investigate Above Ceiling Conditions
    20
    20 d
    0%
    30 May '12
    26 Jun '12
    Hoardings
    5
    5 d
    0%
    06 Jun '12
    12 Jun '12
    Demolition (All)
    20
    20 d
    0%
    20 Jun '12
    18 Jul '12
    HVAC- main duct Work, Fire dampers
    40
    40 d
    0%
    19 Jul '12
    14 Sep '12
    Layout Partitions
    5
    5 d
    0%
    19 Jul '12
    25 Jul '12
    Steel stud Framing & Hollow Metal Frames
    30
    30 d
    0%
    17 Sep '12
    29 Oct '12
    Ceiling and Bulk Head Framing
    10
    10 d
    0%
    30 Oct '12
    12 Nov '12
    Mechanical Rough-In to Ceiling
    25
    25 d
    0%
    13 Nov '12
    17 Dec '12
    Taping,Drying & Sanding
    20
    20 d
    0%
    04 Dec '12
    03 Jan '13
    Ceiling and Bulk Head Drywall
    10
    10 d
    0%
    04 Dec '12
    17 Dec '12
    Painting
    15
    15 d
    0%
    04 Jan '13
    24 Jan '13
    T-Bar and Acoustic Ceiling Tile With Devices
    11
    11 d
    0%
    22 Jan '13
    05 Feb '13
    Head Walls system
    7
    7 d
    0%
    25 Jan '13
    04 Feb '13
    P-Lam Corridor Canopy Ceiling
    15
    15 d
    0%
    25 Jan '13
    14 Feb '13
    P-Lam Corridor and Room Canopy Ceiling
    10
    10 d
    0%
    25 Jan '13
    07 Feb '13
    Steel Doors, Wood Doors, Hardware
    15
    15 d
    0%
    08 Mar '13
    28 Mar '13

  • Query not able to Retrieve Summary Level Member

    Dear all,
    I have created a Planning application on BPC Netweaver 10.0.
    I am trying to retrieve the Planning Data via BEx Query in Dashboard.
    My Account dimension is hierarchical and I want the dashboard users to be able to select summary account when viewing the dashboard (Refer to Look.PNG)
    However, the limitation is that only bottom level members are available in the list.
    So I try to edit the query to summary level accounts available to choose from.
    Query.PNG is my existing design where I can use the filter and prompt for values.
    However, if I apply the setting in Query2.PNG, I can select SOME summary level account but the filter is not available anymore.
    Is there anyway to allow users to choose summary account they would like to see?
    Is the problem related to how the query was set in query designer? Why it drills down to bottom level automatically?
    Thanks,
    Winson

    Hi all,
    When I look back and think about why the query does not give summary level members, I realized that in BPC Microsoft Version, Summary level data are dynamically calculated and the data were not stored in the database. They are instead calculated every time we have to retrieve the data.
    Would that be the reason why the BEX query cannot return Summary level member?
    Anyone who has met this issue before can share how they solve the problem?
    Thanks,
    Winson

  • Tracking the project at Task Summary level

    I want to plan the Project detailed, but because the fact that resources often do not return actual work at the right tasks, I just want to enter the actual work at the summary Level. I do know that they are working in the right area, but not on a specific
    task. I can update the actual work, but if the tasks belonging to the summary task finished in a less work I am not able to update that. Then MSP will copy work into actual work. It seems that work and remaining work is locked. Is there any way that I can
    track my Project this way? For information, all tasks are fix duration. I need the right numbers to make a proper "earned work" report. Not cost, but work. (we do not use cost in Our Project plans) Somebody that have a good idea for me?
    Thanks, Knut fr

    Knut,
    When you say that "resources often do not return actual work at the right tasks", probably the update strategy for your plan should be revised or the decomposition of workpackages into activities in your schedule. Today you are updating assignments
    (actual and remaining work) so you have to use the Resource Usage or Task Usage view to do the updates using the assignment approach. Apply the work table in these views and include Baseline Work and Actual Work in the timesheet. Ok, fixed duration is the
    right type at this moment of the project.
    As Dale said, never update the summary task! The summary task, as the name already says, consolidates the data you provided in the activities.
    Alexandre Paiva, PMP, PMI-RMP, PMI-SP, MCTS, ITIL
    Project Manager +55 (21) 8887-3645 [email protected] www.gerentedeprojeto.net.br

  • Can we load data for all levels in ASO?

    Hi All,
    Im creating cube in ASO
    can i load data for all levels in ASO
    we can load data for all Levels In BSO but in ASO i need confirmation????
    and one more
    wat is the consider all levels option in ASO is used for ? wat is the purpose?
    Can any one help ,it would be appriciate.
    Thanks

    In an ASO cube you can only load to level zero
    The consider all levels if used for aggregation hints. It allows you to tell the aggregation optimizer to look at all levels when deciding if aggregation needs to be done on the dimension

  • Can we load data for all levels in ASO cube

    Hi All,
    Can we load data for all levels of members in ASO cube in 9.3.1.
    Regards

    Yes you can load data for all levels in an ASO cube in any version HOWEVER, none of the upper level data in any cube will be there when you look for it. You will get a warning message in the load because ASO cubes don't store data at upper levels. It is the same as loading data into dynamic calc members in BSO cube. It will do the load without compalints, but there will be no data there (At least you get the warning in ASO)

  • Report on delivery data in item level for list of po

    Dear all
             How to take Report on delivery data in item level for list of po
    regards
    M.Chandra mohan

    You can check any of the standard reports like ME2M with the selection variant as "PO where GR exists"

  • KE30 is not picking the data from summarization level

    Hi Techies,
    We are facing one issue in KE30 tcode.
    We are able to run the same report in our QLTY, its showing "Data is getting fetched the data from summarization level 33" and we can see the output within 5 mins, But if we use same parameters in PRO, its showing "Data is getting fetched from segment level".
    So we are not getting data in PRO, its throwing TIME_OUT error....
    Request you to suggest how we can map these summarization level to the particular report.
    *We have already rebuilt and refreshed the summarization levels, then also it is being picked from segment level.
    Thanks in advance,
    NIck Loy

    Hi,
       In KE30 right click on the report. Click on change. Go to the options tab. In the performnace block check if radio button "use a summarization level" is selected.
      If the customizing is correct then the select stamenet generated by the report may not be in sync with the summ level i.e. the chars in the selection of the report must be there in the summ level.
    regards
    Waman

  • BAPI to change data at operation level

    Hi,
    I have this requirement:
    I need to change data at operation level, more particularly Person No (PERNR) by using a BAPI.
    Is there any BAPI - in which I can pass the basic data (say Order data and Operation data) and change the PERNR for it.
    The name of the BAPI and its usage will help.
    Ankur

    Hello,
    Assuming you are talking about maintenance or service orders, you can use BAPI_ALM_ORDER_MAINTAIN. See function module documentation from SE37. The structure BAPI_ALM_ORDER_OPERATION contains PERS_NO field.
    -Paul
    Please use Enterprise Asset Management (EAM) forum for PM/CS specific topics
    Enterprise Asset Management (SAP EAM)

  • AR DATA FLOW (TABLE LEVEL) - ON ACCOUNT CREDITS & CASH RECEIPTS편

    제품 : FIN_AR
    작성날짜 : 2003-09-16
    AR DATA FLOW (TABLE LEVEL) - ON ACCOUNT CREDITS & CASH RECEIPTS편
    ================================================================
    PURPOSE
    이 문서에서는 AR table들에 대해 어떻게 data가 들어가는지에 대해
    설명한다.
    On Account와 Cash Receipt을 기준으로 설명한다.
    Explanation
    1. On Account Credits
    특정 Customer에 대한 Credit정보를 입력했으나, 아직 특정 Invoice에는 Apply되지 않은 정보를 "On Account" credit이라고 한다.
    Credit정보가 들어있기 때문에, Credit Memo와 유사하게 table에 저장된다.
    Credit Memo와 다른 점은 아래와 같다.
    o When first entered the payment schedule will be fully remaining.
    o When first entered no records are inserted into AR_RECEIVABLE_APPLI
    CATIONS_ALL.
    o The line records will have NULL values in
    PREVIOUS_CUSTOMER_TRX_ID
    PREVIOUS_CUSTOMER_TRX_LINE_ID
    o The distribution lines have to be typed in as there is no invoice
    to copy them from.
    "On Account"는 같은 Supplier상에서는 어떠한 invoice에 대해서 적용이 가능하다는 점에서,
    특정 invoice에만 apply가 가능한 Credit Memo와는 다르다.
    2. Cash Receipts
    Recipt정보가 입력되면, 아래의 table들에 insert된다.
    o AR_CASH_RECEIPTS_ALL
    o AR_CASH_RECEIPT_HISTORY_ALL
    o AR_PAYMENT_SCHEDULES_ALL
    o AR_RECEIVABLE_APPLICATIONS_ALL
    입력된 Receipt정보가 특정 invoice와 match되면, 추가 record가
    AR_RECEIVABLE_APPLICATIONS_ALL에 insert되고, AR_PAYMENT_SCHEDULE_ALL에는 update된다.
    | | | |
    | RECEIPT |------------------| PAYMENT |
    | | | SCHEDULE |
    | |
    | |
    ^ ^
    /|\ /|\
    | | | |
    | RECEIPT | |APPLICATIONS|
    | HISTORY | | |
    2.1 AR_CASH_RECEIPTS_ALL
    Receipt에 대한 기본정보가 insert된다. 한 receipt당 한줄이 insert된다.
    Key = CASH_RECEIPT_ID (from sequence AR_CASH_RECEIPTS_S)
    Important Fields
    AMOUNT - Value of receipt in entered currency
    RECEIPT_NUMBER - Payment Number entered by user.
    STATUS - (APP)lied, (UNAPP)lied, (REV)ersed Payment,
    (STOP) payment, (NSF) insufficient funds.
    It will only change to APP once the whole
    amount of the receipt is applied.
    REVERSAL_DATE - NULL unless receipt reversed
    PAY_FROM_CUSTOMER - Contains CUSTOMER_ID for RA_CUSTOMERS
    2.2 AR_CASH_RECEIPT_HISTORY_ALL
    Receipt하나당 한줄의 data가 insert되고, GL로 Posting된 정보가 들어간다.
    Receipt이 reverse되면, 새로운 row가 insert된다.
    Key = CASH_RECEIPT_HISTORY_ID (from sequence)
    Important Fields
    CASH_RECEIPT_ID - Foreign key to AR_CASH_RECEIPTS record.
    STATUS - CLEARED for manually input receipts.
    GL_DATE - Accounting date
    ACCOUNT_CODE_COMBINATION_ID - Key to GL_CODE_COMBINATIONS
    POSTING_CONTROL_ID - -3 if unposted
    REVERSAL_POSTING_CONTROL_ID - NULL unless payment reversed
    CURRENT_RECORD_FLAG - Y if this is latest record
    PRV_STAT_CASH_RECEIPT_HIST_ID - Key to previous receipt history record.
    2.3 AR_PAYMENT_SCHEDULES_ALL
    Invoice에 apply된 Total 금액정보가 저장된다.
    Key = PAYMENT_SCHEDULE_ID (from sequence)
    Important Fields
    CUSTOMER_TRX_ID - NULL
    CASH_RECEIPT_ID - Foreign key to AR_CASH_RECEIPTS record.
    AMOUNT_DUE_ORIGINAL - Total amount of receipt (usually negative)
    AMOUNT_DUE_REMAINING - Unapplied amount of receipt.
    AMOUNT_APPLIED - How much of this receipt is applied .
    STATUS - (OP)en or (CL)osed. Will only be closed if
    AMOUNT_DUE_REMAINING is zero.
    All of the fields holding LINE, TAX and FREIGHT amounts are NULL.
    2.4 AR_RECEIVABLE_APPLICATIONS
    Receipt이 처음 생성될때, 한줄의 data가 이 table에 insert되고,
    invoice에 대해 Apply혹은 Unapply가발생하면, 두줄씩 새롭게 생성된다.
    예를들면, 아래와 같다.
    Record 1 UNAPP 700
    { Record 2      UNAPP       -200
    { Record 3      APP          200      cross referenced to the Invoice
    { Record 4      UNAPP       -500
    { Record 5      APP          500      cross referenced to 2nd Invoice
    The sum of the amounts on records that have a particuar status should add up
    to the running totals on the payment schedulesi, but with the opposite sign.
    i.e. In the example above
    AR_PAYMENT_SCHEDULES.AMOUNT_DUE_ORIGINAL = -700
    AR_PAYMENT_SCHEDULES.AMOUNT_DUE_REMAINING = 0
    AR_PAYMENT_SCHEDULES.AMOUNT_APPLIED = -700
    UNAPP = 700 -200 -500 = 0
    APP = 200 + 500 = 700
    Statuses of these records can be:-
    UNAPP - Unapplied
    APP - Applied
    ACC - On Account
    UNID - Unidentified (Customer Not known)
    이러한 record내역은 invoice/credit/receipt에 있는 Transaction History form에서 확인할 수 있다.
    2.5 AR_PAYMENT_SCHEDULE (Invoice)
    Receipt이 특정 invoice에 apply되면, invoice에 대한 Payment Schedule record가 update된다.
    remaining amount field 값은 Payment금액만큼 줄어들게 된다.
    만약, remaining amount가 "0"가 되면, invoice Payment schedule은 closed상태가 된다.
    예를들어, Receipt금액 "200"이 "1175" invoice금액(Tax금액 175가 포함된)에 apply되었다면, Invoice의 Payment Schedule은 아래와 같이 조정된다.
    Before After
    AMOUNT_DUE_REMAINING 1175.00 975.00
    AMOUNT_LINE_ITEMS_REMAINING 1000.00 800.00
    TAX_REMAINING 175.00 175.00
    FREIGHT_REMAINING 0.00 0.00
    Note that receipts are applied in a fixed sequence:-
    1. Line Amounts
    2. Tax Amounts
    3. Freight Amounts
    ie The TAX_REMAINING figure will only start to decrease when the
    AMOUNT_LINE_ITEMS_REMAINING is zero.
    Reference Documents
    Note : 29277.1 & 29278.1

    Hi,
    This query works fine for me:
    SELECT CR.CASH_RECEIPT_ID,
                CR.RECEIPT_NUMBER,
                CR.RECEIPT_DATE,
                CR.CURRENCY_CODE,
                DECODE ( CR.TYPE, 'MISC', NULL, NVL (SUM (DECODE (RA.STATUS, 'ACC', NVL (RA.AMOUNT_APPLIED, 0), 0)), 0)) ON_ACCOUNT_AMOUNT
             FROM AR_RECEIVABLE_APPLICATIONS_ALL RA,
                AR_CASH_RECEIPTS_ALL CR,
                AR_RECEIPT_METHODS RM
          WHERE RA.CASH_RECEIPT_ID = CR.CASH_RECEIPT_ID
                AND CR.RECEIPT_METHOD_ID = RM.RECEIPT_METHOD_ID
                AND CR.ORG_ID = <org_id>
          GROUP BY CR.CASH_RECEIPT_ID,
                CR.RECEIPT_DATE,
                CR.RECEIPT_NUMBER,
                RM.NAME,
                CR.CURRENCY_CODE,
                CR.TYPE order by receipt_date desc
    Let me know if it worked.
    Octavio

  • AR DATA FLOW (TABLE LEVEL) - INVOICE편

    제품 : FIN_AR
    작성날짜 : 2003-09-16
    AR DATA FLOW (TABLE LEVEL) - INVOICE편
    =====================================
    PURPOSE
    이 문서에서는 AR table들에 대해 어떻게 data가 들어가는지에 대해
    설명한다.
    Invoice transaction을 기준으로 설명한다.
    Explanation
    1. Invoice
    User가 invoice를 입력하면, 아래의 table들에 data가 insert된다.
    o RA_CUSTOMER_TRX_ALL (Invoice Header)
    o RA_CUSTOMER_TRX_LINES_ALL (Line Details)
    o RA_CUST_TRX_LINE_GL_DIST_ALL (Information for posting to GL)
    o RA_CUST_TRX_LINES_SALESREPS_ALL (Sales Credit Information)
    일단, invoice가 "Complete"되면, 아래의 table에 한줄(혹은 그 이상)이
    추가로 Insert된다.
    o AR_PAYMENT_SCHEDULES_ALL (Running Totals for Invoice Amounts)
    대체로 하나의 invoice는 하나의 Payment schedule record를 가지지만,
    만약 할부(Installment)로 Pay처리되는 invoice라면, installment하나당
    하나의 Payment schedule record를 가진다.
    | | /| |
    | TRX |---------------<-| PAYMENT |
    | | \| SCHEDULE |
    | |
    | |
    ^ -------
    /|\ |
    ------------ |
    | | |
    | TRX_LINES | |
    _| | |
    / ------------ |
    | | | |
    \__/ | |
    ^ |
    /|\ |
    | |
    | GL_DIST |
    | |
    1.1 RA_CUSTOMER_TRX_ALL
    Invoice의 Header정보(Customer, Invoice Number, date.. etc)를 담고 있는 table이다.
    Invoice하나당 한줄의 정보가 Insert된다.
    Key = CUSTOMER_TRX_ID (generated from sequence RA_CUSTOMER_TRX_S)
    Important Fields
    TRX_NUMBER - User Entered Invoice Number
    CUST_TRX_TYPE_ID - Foreign key to RA_CUST_TRX_TYPES
    BILL_TO_CUSTOMER_ID - Foreign Key to RA_CUSTOMERS
    SHIP_TO_CUSTOMER_ID - Foreign key to RA_CUSTOMERS
    TRX_DATE - Invoice Date
    COMPLETE_FLAG - Y or N
    1.2 RA_CUSTOMER_TRX_LINES_ALL
    Invoice의 Line정보(수금 item및 금액, Tax등)가 insert되는 table이다.
    Invoice하나당 한줄이상을 가진다.
    Key = RA_CUSTOMER_TRX_LINE_ID (from sequence RA_CUSTOMER_TRX_LINES_S)
    Important Fields
    CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
    LINE_TYPE - LINE, TAX, FREIGHT
    QUANTITY_INVOICED - Line Quantity
    UNIT_SELLING_PRICE - Price per unit
    EXTENDED_AMOUNT - Quantity * Price
    LINK_TO_CUST_TRX_LINE_ID - Null for LINE, for TAX and FREIGHT lines
    contains the RA_CUSTOMER_TRX_LINE_ID of
    associated LINE record
    1.3 RA_CUST_TRX_LINE_GL_DIST_ALL
    GL로 Posting될 정보가 담겨져 있다.
    Invoice Line당 한줄 + Invoice Header 한줄로 이루어져 있다.
    (예를들어, Invoice의 Line이 총 3줄이라면, RA_CUST_TRX_LINE_GL_DIST_ALL table에는 총 4줄의 정보가 담기게 된다.)
    Key = CUST_TRX_LINE_GL_DIST_ID (from sequence)
    Important Fields
    CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
    CUSTOMER_TRX_LINE_ID - Foreign key to RA_CUSTOMER_TRX_LINES or
    Null if this relates to Invoice Header.
    AMOUNT - Value of distribution - entered currency
    ACCOUNTED_AMOUNT - Value of distribution - book currency
    CODE_COMBINATION_ID - Foreign key to GL_CODE_COMBINATIONS
    POSTING_CONTROL_ID - -3 if unposted
    GL_DATE - Accounting date.
    GL_POSTED_DATE - Date Invoice posted to GL.
    1.4 RA_CUST_TRX_LINE_SALESREPS_ALL
    해당 invoice가 입력될때 함께 입력된 Sales Person에 대한 정보가
    담겨져 있다.
    1.5 AR_PAYMENT_SCHEDULES_ALL
    해당 invoice에 대해서 Line, Tax, 운송비 등 각각의 항목에 대한 Total값과
    Remaining값을 담고 있다.
    대체로 Invoice당 한줄이 insert된다.
    Key = PAYMENT_SCHEDULE_ID (from sequence AR_PAYMENT_SCHEDULES_S)
    Important Fields
    CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
    STATUS - (OP)en or (CL)losed
    ACTUAL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise
    date payment schedule closed.
    GL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise the
    gl date of the closing transaction.
    AMOUNT_DUE_ORIGINAL - Invoice Total Amount
    AMOUNT_DUE_REMAINING - Total Amount outstanding for Invoice.
    AMOUNT_LINE_ITEMS_ORIGINAL - Sum of Invoice Line amounts.
    AMOUNT_LINE_ITEMS_REMAINING - Outstanding Line amounts.
    TAX_ORIGINAL - Total Tax for Invoice.
    TAX_REMAINING - Outstanding Tax for Invoice
    FREIGHT_ORIGINAL - Total Freight For Invoice
    FREIGHT_REMAINING - Outstanding Freight
    AMOUNT_APPLIED - Total payments applied to this Invoice.
    AMOUNT_CREDITED - Total Credit Memos applied.
    AMOUNT_ADJUSTED - Total value of adjustments.
    The payment schedule should balance within itself, ie the following
    calculations
    should be true:-
    AMOUNT_DUE_ORIGINAL = AMOUNT_LINE_ITEMS_ORIGINAL
    + TAX_ORIGINAL
    + FREIGHT_ORIGINAL
    AMOUNT_DUE_REMAINING = AMOUNT_LINE_ITEMS_REMAINING
    + TAX_REMAINING
    + FREIGHT_REMAINING
    AMOUNT_DUE_ORIGINAL = AMOUNT_DUE_REMAINING
    + AMOUNT_APPLIED
    - AMOUNT_CREDITED
    + AMOUNT_ADJUSTED
    Reference Documents
    Note : 29277.1

    Hello,
    The basic flow of data is
    ERP tables - source snapshots - source views (eg MRP_AP%) - staging tables (MSC_ST%) - ODS tables ( MSC%)
    Check out note 412375.1. This is the flow for sales order data for ASCP.
    regards
    Geert

  • Need help in copying Invoice date to lower level item in Sales order report

    Hello Experts,
    I am debugging into one Sales order report.I need little bit help.The report is displaying Invoice Date for
    Sales order Billing documents for Higher item in Bill of Material Structures.But as per user requirement,
    I am supposed to show the Invoice date for lower level items also.The field for Higher level item is 'UEPOS'.
    I want to copy the Invoice date for Higher level item to lower level item. Can you please guide me in the logic?
    Thanking you in anticipation.
    Best Regards,
    Harish

    Hi BreakPoint,
    Thanks for the information.
    I have applied the same way but it is showing only lower line items now.
    Invoice dates for Higher level items are not there.
    I am pasting the code here which I have applied.
    Then you can give me more guidence.
    This is to be done only for 'ZREP' sales orders.
    if w_vbak-auart EQ 'ZREP' and w_vbak-uepos is not INITIAL.
                          read table t_final into w_final_ZREP with key vbeln = w_vbak-vbeln
                                                                        posnr = w_vbak-uepos.
                             w_final-erdat_i = w_final_ZREP-erdat_i.
                             else.
                    if w_vbak-auart EQ 'ZREP' and w_vbak-uepos is INITIAL.
                      w_final-erdat_i = w_invdate.
                    endif.
                    endif.
    Can you please sugest me changes here?
    Best Regards,
    Harish
    Edited by: joshihaa on Jul 13, 2010 6:22 PM

  • Advice on inserting data at parent level

    Hi experts,
    I would need some advice on how can I enter data at parent level. As we cannot enter data at parent level I am figuring out different strategies to do so. The one I seem to like the most is to create members representing the parents where we can input the data. For example:
    - 2008.Total (Parent)
        + 2008.Generic (Leaf)
        + 2008.Jan (Leaf)
        + 2008.Feb (Leaf)
        + etc....
    I would need to do this in different dimensions in my application. So here are the questions:
    1) Is there anything wrong about doing this?
    2) Is there a better option? (what is the Best Practice in this case?)
    3) In the case of doing this for the TIME dimension, there are some properties which value is not easy to set for those members (TIMEID, YEAR and LEVEL). I don't really know where and how those properties are used and the help doesn't help me much (what is the "time format required for Analysis Services"?). So what values have you used in these properties for such members?
    Thank you very much,
    Rafael

    Hi Rafael,
    What purpose is your application designed for? In a legal consol application, would never mess with the standard time dimension setup, in particular the time dimension. The setup of the Time.Level and Time.Year properties are very sensitive in the operation of some of the business rules, particularly the opening balances & account transformation rules (where there's a time-period offset functionality). I always try to retain the standard time dimension setup there.
    This means, for example, using a seperate datasrc member (or members) if the customer insists on having "13th period" for year-end adjustments. If they don't go into December along with the standard December values, then the carry-forward opening balances for the following year can be very tricky to calculate.
    If your application is purely analytics, or for planning, then you should still understand what business rules features you want to use before deciding the time dimension design. When I've had year-total input data, I either
    1.) use a standard 12-month time dimension, and by practice always put total-year data in December. Set up input schedules appropriately, and train people appropriately. Use Dec not Jan, or else the year-total and periodic/YTD computations in the cube won't work correctly. And consider your Account.Acctype carefully.
    2.) If the data is for annual values that aren't directly part of the P&L or B/S, and are things like allocation drivers, tax rates, inflation rates, stuff like that -- which doesn't get added up along with the monthly values to come to a total-year "full picture" -- then I follow the structure from the old Outlooksoft demo. Create each of your years with the standard 12 months. Then create
    Input.Year
    xxxx Input.Quarter
    xxxxxxxx 2008.Input
    xxxxxxxx 2009.Input
    xxxxxxxx 2010.Input
    etc.
    Then set your YEAR = 2008,LEVEL=MONTH for 2008.Input, etc.
    This approach works well in logic *LOOKUPs and also keeps the dimension structure clean & intuitive for end users. If you put your 2008.Input under 2008.Q1 or 2008.Q4, then every time someone lays out or drills down in a report, they will curse the designer, since they now need to remove that extra column of the 2008.Input member.
    With the datasrc approach for the "13th month" you can control whether the year-end adjustments are there or not, for those few reports where you'll want to see them. And 99% of the time, your time dimension "looks" normal.
    I'm sure there are other approaches beyond what I've discussed, but I've never gotten into trouble using one or both of these two.
    Regards,
    Tim

Maybe you are looking for