Different Languge/Description Based on Dimension Level

Is it possible at all to have either short or long description be chosen through a function depending on a condition e.g. different level in cube?
Example. If Condition A is met than Long Description is used, Condition B is met than Short Description is used.
Edited by: user7853353 on Aug 14, 2012 2:36 PM

Not through Oracle OLAP alone. This is more of a Reporting issue and can be done via db view or using reporting tool features:
a) Mapping is restricted to a single column. So Long and Short Descriptions need to be mapped to a specific column in source table/view. If your condition is static or related to backend dimension attribute value conditions then you can define the logic in a source view and map both desc attributes to the special column.
define column green_ldesc_else_sdesc in dimension view....
case when product_alias.color = 'GREEN' then product_alias.long_desc else product_alias.short_desc end as green_ldesc_else_sdesc
Use this column to map to short_description/long_description attributes in olap aw dimension mapping.
b) In OBIEE Answers, you can expose the relevant fields in the reporting layer or Presentation layer of rpd and use it in a case statement to implement your logic.
E.g:
CASE WHEN "OLAP Presentation Layer Name"."Product"."Level Name" = 'CLASS' THEN "OLAP Presentation Layer Name"."Product"."Long Description" ELSE "OLAP Presentation Layer Name"."Product"."Short Description" END

Similar Messages

  • Dimension with 2 Hierarchies, Lowest Member w/ Different Long Descriptions

    I'm trying to create a dimension that would allow Discoverer For OLAP users to choose between different LONG DESCRIPTIONs, and I am trying to accomplish this by using multiple hierarchies.
    For example, when a user is trying to create a report and eventually stumbles upon the Dimensions part of the Workbook creation, he can choose a different description other than the default by choosing from the Hierarchy drop down list.
    The following is the dimension details:
    Dimension: TEST_DIM
    Hierarchy #1: HIER_NAME
    Levels: TOTAL_DIM_NAME
            TEST_LVL_NAME
    Hierarchy #2: HIER_CODE
    Levels: TOTAL_DIM_CODE
            TEST_LVL_CODE
    Dimension View: V_TEST_DIM
    Fields: TOTAL_DIMENSION_NAME_ID   ---mapped to-->  TOTAL_DIM_NAME
            TOTAL_DIMENSION_NAME_DESC ---mapped to-->  TOTAL_DIM_NAME_LONG_DESCRIPTION
            NAME_LEVEL_ID             ---mapped to-->  TEST_LVL_NAME
            NAME_LEVEL_DESC           ---mapped to-->  TEST_LVL_NAME_LONG_DESCRIPTION
            TOTAL_DIMENSION_CODE_ID   ---mapped to-->  TOTAL_DIM_CODE
            TOTAL_DIMENSION_CODE_DESC ---mapped to-->  TOTAL_DIM_CODE_LONG_DESCRIPTION
            CODE_LEVEL_ID             ---mapped to-->  TEST_LVL_CODE
            CODE_LEVEL_DESC           ---mapped to-->  TEST_LVL_CODE_LONG_DESCRIPTION
    Cube: TEST_CUBE
    Measure: TEST_MEASURE
    -----------------------------------------------------------------------------------------With the above dimension having 2 hierarchies, Discoverer users can choose between HIER_NAME or HIER_CODE. The problem with this setup is that for this to work, different fields must be mapped to the lowest levels of each hierarchy, because the values of NAME_LEVEL_ID and CODE_LEVEL_ID fields from the V_TEST_DIM dimension view are different from each other, even though they share the same set of records, which means they can be considered as one.
    The values of NAME_LEVEL_ID and CODE_LEVEL_ID must be different, because if they are not, I receive the following error during maintenance:
    ***Error Occured: Data for at least One of the Hierarchies for TEST_DIM.DIMENSION controdicts the Definition of such Hierarchy as Level
    Based.After making the NAME_LEVEL_ID and CODE_LEVEL_ID values different from each other, I tried mapping the fact table to the cube. Mapping details are as follows:
    Cube View: V_TEST_CUBE
    Fields: TEST_VALUE       --mapped to-->  TEST_MEASURE
            NAME_LEVEL_ID    --mapped to-->  TEST_DIM.TEST_LVL_NAME.NAME_LEVEL_ID
         CODE_LEVEL_ID    --mapped to-->  TEST_DIM.TEST_LVL_CODE.CODE_LEVEL_ID
    -----------------------------------------------------------------------------------------Unfortunately, the above mappings does not work, because I get the following error when I do so:
    Invalid Mapping:
    Levels in a dimension TEST_DIM have to be mapped to the same column for summary fact_tableBut despite the error(s) above, I've actually made this work, by leaving the one ID field (NAME_LEVEL_ID or CODE_LEVEL_ID) unmapped. Say, I map NAME_LEVEL_ID to TEST_DIM.TEST_LVL_NAME.NAME_LEVEL_ID but leave CODE_LEVEL_ID unmapped, then maintain to load data for TEST_DIM (HIER_NAME hierarchy). Then I unmap NAME_LEVEL_ID and map CODE_LEVEL_ID. I maintain the cube again to load data for the other hierarchy which is HIER_CODE.
    Now, if that works, why won't AWM let me map NAME_LEVEL_ID and CODE_LEVEL_ID at the same time?
    I tried running the following DML command to manually map the fields:
    call set_measure_key_expression('TEST_CUBE.MAPGROUP1.CUBEMAPGROUP',NA,'TEST_DIM.HIER_NAME.LEVEL\nTEST_DIM.HIER_CODE.LEVEL','VIEW_OWNER.V_TEST_DIM.NAME_LEVEL_ID\nVIEW_OWNER.V_TEST_DIM.CODE_LEVEL_ID',FALSE)I checked the mappings afterwards and the two fields are indeed mapped, but when I try to maintain, I got an error stating that 'VIEW_OWNER.V_TEST_DIM.NAME_LEVEL_ID\nVIEW_OWNER.V_TEST_DIM.CODE_LEVEL_ID' does not exits or something like that.
    Does any know a better way to implement this?
    Please help.

    I understand what you are trying to achieve, and technically it should be possible. In practice, however, Disco caches dimensional information as it is not expecting information such as descriptions to change from one query to the next.
    The complication is the description objects do not have any additional dimensionality beyond their base dimension, however, there is a language dimension that might be useful in this case. If you created an additional language with a formula that calls a program to set the underlying AWM language dimension you could assign this measure to the first worksheet in your workbook and allow users to swap between different versions of their long descriptions. However, this would be a session wide setting and not worksheet specific.
    In the AWM tree you will need to add additional languages to your AW which can then be used a placeholders for your different descriptions. This will affect all your dimensions so you will need to either use OLAP DML to copy the base language descriptions to all the other languages or using the mapping editor.
    In the dimension mapping tool you will now see multiple entry points for descriptions - English, French, German etc depending on which languages you picked. You can assign any column from your source view/table to these columns.
    Should work - I did something similar for another customer. It is not ideal, and does require the users to open/create a worksheet to switch the descriptions but it was all I could think of at the time.
    Keith Laker
    Oracle EMEA Consulting
    BI Blog: http://oraclebi.blogspot.com/
    DM Blog: http://oracledmt.blogspot.com/
    BI on Oracle: http://www.oracle.com/bi/
    BI on OTN: http://www.oracle.com/technology/products/bi/
    BI Samples: http://www.oracle.com/technology/products/bi/samples/
    Does that make sense?

  • Comparing facts of different dimension levels - drilldown problem.

    With our customer, we do a lot of comparisons of sales budgets vs. actual sales. The sales budgets are given per month, like this:
    Sales budgets: Jan 09: 40,000 EUR, Feb 09: 45,000 EUR, Mar 09: 20,000 EUR... and so on.
    There is a time dimension (year -> quarter -> month -> day). Since BI does not seem to allow binding facts to other dimension levels than the lowest one (day in my example), I used a trick and modelled these sales budgets as a fact table: (expected sales, last_day_of_month)
    So I have this:
    Sales budgets: 01/31/09: 40,000 EUR, 02/28/09: 45,000 EUR... and so on.
    This way, I can connect both actual sales and sales budgets to the same time dimension. With this, I can create an answers report that compares the two facts easily.
    The problem is now that the customer wants to drill down. This is no problem with year->quarter->month. But then, BI naturally allows to drill further to day, and in this case, BI compares the sales budget of 01/31/09 with the sales on 01/31/09, producing wrong values.
    I either need a solution to prevent BI from drilling down from the month level in this special answer report, or maybe I am making an error with my modelling. Are there any ideas on how to do this better?

    Hi,
    I'd model the repository differently, by modeling the actual sales fact on the lowest day level, and sales budget fact on monthly level. That's how I've understood the data really is defined, right? (Lowest level physical time table you already have but for sales budget you need to create also a physical time table which is on the month level. First define the correct physical joins. Then define the logical table sources in the BM layer accordingly.) In order to be able show the sales budget together with lowest level you can create the sales budget measure as a level based measure (fix the measure to the level month in the column properties-->Level in the Administration tool).
    If you just want to prevent users from drilling-down on a specific dashboard report you can go to properties of the column(s) in that report and set the interaction type for both title and values to "No interaction" in the second tab of the properties menu in the front-end.
    Hope this helps!
    Cheers,
    Ilmari

  • Logical column - Aggregation - based on dimensions

    Hi,
    Can anyone explain the working of the aggregation based on dimension functionality. I understand it is different from level - based measures.
    Thanks in advance.
    - Priti

    Hi priti,
    Aggregation based on dimension .
    Hav a look at this you get an idea http://gerardnico.com/wiki/dat/obiee/measure_level_based
    UPDATED POST
    Sorry i gave you the wrong link.This is what your looking for
    http://gerardnico.com/wiki/dat/obiee/aggregation_based_on_dimension
    follow this etiquette as your new http://forums.oracle.com/forums/ann.jspa?annID=939
    Cheers,
    KK
    Edited by: Kranthi on Feb 24, 2011 12:20 AM

  • How to define primary interaction based on hierarchy level

    I have a 3 level product dimension, such as brand, product type, and product. Now I want to define primary interaction based on the level. If click on brand or product type, it will be drill down. If click on product, it will be send master-detail. Since there is only one column for this dimension on the report when report is constructed, how can I apply different interaction based on the product level?
    Thanks

    iif you are trying to do a normal hierarchical drill down from brand down to product type down to product, and if they are defined so in your database, defining a normal hierarchy is suffice.
    iif you are trying to navigate to a different level in a hierarchy, do a pre-defined drill down.
    all the above options must be defiend in RPD.
    if your Q is not answered can you please elaborate further with the existing example.
    -bifacts
    http://www.obinotes.com

  • How to implement Dimension Level Security on Tabular?

    Not possible on SQL Server 2014 SSAS Tabular? How to work around?
    Kenny_I

    Hi Kenny_l,
    According to your description, you want to implement dimension security in SSAS 2014 tabular. Right?
    In Analysis Services Tabular mode, dimension level security (based on role permission) is not supported. This security can only used in Multi-dimension mode. In tabular mode, we can only use row-level security based on role permission.
    Please refer to links below:
    Implement Dynamic Security by Using Row Filters
    Reference:
    Comparing Tabular and Multidimensional Solutions (SSAS)
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou
    TechNet Community Support

  • Aggregation based on dimension

    Hi all,
    Can anyone help me in knowing the difference between normal aggregation set for a measure irrespective of dimensions and different aggregations set for the same measure based on dimension...

    hi User,
    Look at http://oraclebizint.wordpress.com/2007/12/03/oracle-bi-ee-101332-level-based-measures-lbms/
    thanks,
    Saichand.v

  • Preaggregation across value based hierarchy dimension in 11g

    Hi All,
    I have created a cube with 6 dimensions in olap 11g. One of those six dimensions has only one hierarchy which is value based hierarchy. I have chosen level based aggregation as I know at what levels exactly users are going to query. When I was going through the dimensions to choose levels to preaggregate I noticed there were no options available for my value based hierarchy dimension ( I could see "all" option for the same case in 10g) then I tried to look for definitions of underlying objects just to make sure it will preaggregate data across my value based hierarchy dimension.
    I found value set corresponding to my value based hierarchy dimension in <CUBE NAME>SOLVEAGGMAP object , which AWM uses to decide which dimension values to preaggregate but if I do rpr on that value set (rp r<CUBE NAME>SOLVE<DIMENSION NAME>_PVSET) it shows NA so my question is can I pre aggregate across value based hierarchy dimension in olap 11g?
    Olap Version: 11.2.0.1
    AWM version: 11.2.0.1
    Thanks

    Even if you know exactly which levels your users will query, percent based precompute (e.g. 30%) may still be faster in practice because queries are returned using 'sparse looping' instead of 'dense looping'. This was the single biggest performance advantage of 11g over 10g.
    But if you still want to use level based precompute, then you should look at the XML template for the cube (as saved by AWM, for example). In it you should find something called PrecomputeCondition. This defines the set of members that are precomputed. Here is an example I just created using the GLOBAL schema
    <PrecomputeCondition>
    <![CDATA[
      "TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
      CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
      CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
      PRODUCT LEVELS (PRODUCT.CLASS, PRODUCT.FAMILY, PRODUCT.ITEM)]]>
    </PrecomputeCondition>The PrecomputeCondition is also visible through the USER_CUBES view.
    SELECT PRECOMPUTE_CONDITION
    FROM USER_CUBES
    WHERE CUBE_NAME = 'MY_CUBE';You can hand modify this condition in the XML to specify an alternative 'non level based' precompute condition for any dimension. For example, if you define an attribute named 'SHOULD_PRECOMPUTE' on your PRODUCT dimension that is 1 for members to be precomputed and 0 for all others, then you can change the condition as follows.
    <PrecomputeCondition>
    <![CDATA[
      "TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
      CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
      CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
      PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
    </PrecomputeCondition>If you recreate the cube from the XML with this condition, then the PVSET valueset you discovered should contain all dimension members for which the attribute value is 1.   This gives you complete control over what is precomputed.   Note that AWM doesn't support this form of condition, so it won't show up if you go to the Precompute tab, but it is valid for the server.  The PL/SQL below will modify the PrecomputeCondition (for the cube named MYCUBE) without going through AWM.
    begin
      dbms_cube.import_xml(q'!
    <Metadata
      Version="1.3"
      MinimumDatabaseVersion="11.2.0.2">
      <Cube Name="MY_CUBE">
        <Organization>
          <AWCubeOrganization>
            <PrecomputeCondition>
              <![CDATA[
               "TIME" LEVELS ("TIME"."MONTH","TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
               CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL,CHANNEL.CHANNEL),
               CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT,CUSTOMER.REGION,CUSTOMER.SHIP_TO),
               PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
            </PrecomputeCondition>
          </AWCubeOrganization>
        </Organization>
      </Cube>
    </Metadata>
    end;
    /

  • Viewing in Answers descriptive information about a level

    Hi, I have a Customer dimension level in BI Admin with its logical level key CUST_NAME.
    I also have some further information about each customer, like address and phone number (stored in CUSTOMER Logical Table), how could I link them to the Customer and view these data in Answers?
    It's like a kind of descriptive level attribute I'd want to view in Answers associated to the level logical key...
    any suggestion would be appreciated very much!

    As in the 1st post, I'd want to associate address and phone number to my CUSTOMER level, in which I drill down using CUST_NAME as a logical level key.
    The only way to view these information is include their columns in my Answers query, I ask the forum if is there another way to, for example, click on the customer column just drilled-down and view customer address...
    In another way: which is the utility of having a level key if it isn't logical level key?
    for example in my CUSTOMER level now I have 2 level key: CUST_NAME, which is logical level key and drill-down enabled, and CUST_ADDRESS which is not logical level key (it has the blue icon). Which is the utility (if is there) of having in my level CUST_ADDRESS that is not a logical key?
    Edited by: battle84 on 1-dic-2009 9.29

  • OBI EE 10g: Bridge tables and Based on Dimensions Aggregation

    hi experts,
    i am working on OBI EE 10 g (10.1.3.4)
    The BM&M layer consist of:
    1) Logical fact table "Sale_Indicators"
    Fields: SALE_ID (PK, FK),
    D1_ID (FK),
    D2_ID (FK),
    Indicator1 (measure, level of granularity: SALE_ID),
    Indicator2 (measure, level of granularity: SALE_ID),
    Indicator3 (measure, level of granularity: SALE_ID)
    2) Logical dimension table
    "Sales" (PK: SALE_ID),
    "D1" (PK: D1_ID),
    "D2" (PK: D2_ID),
    "Customers" (PK: SALE_ID, CUST_ID) - bridge table!
    "Products" (PK: SALE_ID, PROD_ID) - bridge table!
    3) Dimensions: SalesDim, D1Dim, D2Dim, CustomersDim, ProductsDim
    If fact table is joined with bridge table, the number of rows in fact table is multiplied, for example:
    D1_ID | SALE_ID | CUST_ID | Indicator1
    777 | 1 | 14 | 10
    777 | 1 | 17 | 10
    777 | 2 | 15 | 12
    888 | 3 | 16 | 20
    888 | 3 | 17 | 20
    888 | 4 | 19 | 30
    I need to get report:
    D1_ID | Indicator1 (SUM)
    777 | 22
    888 | 50
    and with filter by customer, for example (CUST_ID = 17):
    D1_ID | Indicator1 (SUM)
    777 | 10
    888 | 20
    i am trying to use "based on dimension" aggregation, for example (Indicator1):
    Dimension Formula
    CustomersDim MIN
    ProductsDim MIN
    Others SUM
    The generated physical SQL performs joining EVERY dimension to the fact table, even though they are not included in the final result set.
    Is there any way to tweak logical or physical model in order to eliminate excessive joins?
    Thanks in advance!
    Edited by: 859688 on 31.10.2011 4:04
    Edited by: 859688 on 31.10.2011 4:06
    Edited by: 859688 on 31.10.2011 4:08

    I found this text on the help, but I didn't understand, because when I check the "based on dimensions" check box, I can choose aggregation rules for each dimension, not only the time dimension.
    Also, I found in the help menu:
    "In the Aggregation tab, select the Based on dimensions check box.
    The Browse dialog box automatically opens.
    In the Browse dialog box, click New, select a dimension over which you want to aggregate, and then click OK.
    In the Aggregation tab, from the Formula drop-down list, select a rule."
    I did the same steps suggested by the text above, but it didn't work.

  • Aggreation Based on Dimensions - Aggregation rule: Evaluate_Aggr

    Hello Experts,
    Can any of you explain to me how do you use the Logical Column Aggregation based on dimensions?. If you can set up a simple example would be great. Also, what is the definition of the aggregation rule : Evaluate_Aggr?, please give a simple example
    Thanks for your time
    Pablo.

    And it's not the same than a level based measure :
    The definition of a level based measure :
    http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/level_based_measure_calculations
    An example with evaluate (lag analytic function)
    http://gerardnico.com/wiki/dat/obiee/presentation_service/obiee_period_to_period_lag_lead_function
    Check the two and you will see the difference in the definition.

  • Based on Dimension Aggregation method - OBIEE 11G

    Hi,
    I have a fact table with one measure value and 3 dimensions (Time, Issue, status). Fact table is loaded monthly data for different issues and with status and a corresponding value.
    I want my report to show always issues that is latest of that period and then status of the same.
    Lets say:
    Fact table has data like this:
    31/Jan/2011 - Issue1 - Open - 10
    28/Feb/2011 - Issue1 - WIP - 20
    31/Mar/2011 - Issue1 - WIP - 30
    30/Apr/2011 - Issue1 -WIP - 40
    31/May/2011 - Issue1 -Closed - 50
    31/May/2011 - Issue2 -Open - 60
    31/May/2011 - Issue3 - Open - 20
    Now I want to see the report by status and value and it should show me the latest of that time period.
    For Quarter1 :
    WIP - 30
    For Quarter2:
    Open - 80
    Closed - 50
    If I take Year then it should show me :
    2011 - Open - 80
    2011 - Closed - 50
    I tried using aggregation "Based on dimension" option in BMM layer and put Others - Sum() and LAST against time dimension.
    But in that case it is giving me the results by status what is latest for the time period. So it is ding sum by other dimension first and then applying LAST method.
    In that case result of Quarter -1 will be :
    Open - 10
    WIP - 30
    If I can change the order of aggregation method like first apply LAST method and then do sum then I think desired result will come. But I am not able to change the order.
    Is there any other of doing this solution?
    Any help is highly appreciated.
    Thanks

    Hi,
    There will be multiple records for an entire month as there are many issues. For a particular Issue it will be one with one particular status for a particular month.
    The join is based on the date colum of fact table and the dimension table.
    Regards,
    SS

  • Aggregation mode along one dimension (product) different than along the time dimension

    Dear All,
    In IBP S&OP, Is it possible that the aggregation mode along one dimension (product) could be different than along the time dimension?
    For a demo, a customer has an input at the product family level (vehicle production) which we just “copy” for disaggregation purposes, to the product level (parts), see attached. So for aggregation we used average.
    However, time-wise, we need to sum it up.
    Thanks for your insight and help.
    Kind Regards,
    Omar

    Hi Omar,
    Yes it is possible.
    1. Create a new planning level (say PERPRODCUST1) which will be a copy of PERPRODCUST (you base planning level).
    2. In the PER section of PERPRODCUST1, do NOT mark any period attribute as root. In other words, the roots for this PL will only be PRDID and CUSTID.
    3. Now your KF calculations will be:
    VEHICLEPRODUCTION@PERPRODCUST1 = SUM(VEHICLEPRODUCTION@PERPRODCUST)
    VEHICLEPRODUCTION@REQUEST = AVG(VEHICLEPRODUCTION@PERPRODCUST1)
    Since your KF is editable, it is worth mentioning that, following the above steps has trade-offs. Since your KF is editable, you will have issues with disaggregation when you enter the values at an aggregated level of both time and other attributes. My recommendation (for your configuration) is that this will work fine as long you enter the values at the root level of you time attribute.
    Hope this helps,
    Chendur

  • Different material description in one language for single material

    Hi folks,
        Is it possible to maintain different material descriptions (In one language-english) for a single material.
    if it so how can u provide me steps.
    Thx in advance,
    Neelima.N

    Hi,
    For a single material code maintaining multiple text in the same language is not possible,
    this contradicts the basic principle of consistancy.
    Howevery you are free to do R&D, if sucessful please let me know.
    Regards
    Bikas

  • Display amount in ALV Grid with different Decimal Places based on Currency

    HI Experts,
    Working with ALV Report i have one Amount field NETWR which is having Length 15 and Decimal Places 2.
    we have two different types of currency's AED and KWD and AED having 2 decimal Places and KWD having 3 decimal places.
    im using FM: REUSE_ALV_GRID_DISPLAY for Display. value storing in Table was like this
    AED---22.56
    KWD---225.65
    i need to display values like AED : 22.56

    HI Experts,
    Working with ALV Report i have one Amount field NETWR which is having Length 15 and Decimal Places 2. we have two different types of currency's AED and KWD and AED having 2 decimal Places and KWD having 3 decimal places.
    im using FM: REUSE_ALV_GRID_DISPLAY for Display. value storing in Table was like this
    AED---22.56
    KWD---225.65 (converting this value to 22.565 using BAPI_CURRENCY_GETDECIMALS according to currency in my Report)
    i need to display values like AED : 22.56
                                             KWD---22.565 but here field is NETWR with 2 decimal.
    Need to Display amount in ALV Grid with different Decimal Places based on Currency
    Regards,
    Dileep Kumar Reddy

Maybe you are looking for

  • Multiple selection - VBA

    Hello All, first of all, I hope that my English will be understandable. Description: I must create a report for sales orders by planned deliver date. Most of info what I need are in VBAP, but there is no delivery date there, only in VBAK. I download

  • Intercompany Billing Error

    Dear All, I have configured intercompany billing. Intercompany billing types are two. 1 is Order related invoice. This is between Ordeingcompany to customer. 2nd invoice for Delivery related invoice. This is between Suplying company to Ordering Compa

  • 10.3.3 Agent Update Taking Weeks, Only Deploying to ~600 PCs

    We're having an issue where deploying the update to the 10.3.3 agent is taking a long time, only a few dozen a day and only about 600 workstations are currently assigned the task. We have a gigabit fiber WAN, so that's not an issue. We have one prima

  • Correcting Lens Distortion = 1:1 photos

    I need to take top down photos of objects and then convert the pictures to a CAD file. So far I am having trouble with lens distortion. Anyone know of a quick way to correct the distortion so that the image is 1:1? I am using a 30mm Macro lens - the

  • Message box in standard Transaction

    Hai Friends, Greetings. In Vl01N (standard transaction) i need to add the message box based upon the user entry... How to do that pls guide me Friends.. Regds. Vijay.