Configuring Release value based discount

Hello All,
I would like to implement the discount based on release value in SRM 7.0 Central contract management. For this I have activated hierarchy for contract.
For this discount EBP condition type is mapped to ERP discount condition type. These dicount condition type has scales.
A contract is created for 10,000 Qyt and scales are defined for discont condition
0 to 1000  price is 100 USD
1001 to 5000 price is 90 USD
5001 to 10,000 price is 80 USD
This contract is distributed to backend system and system creates a backend contract.
Now when a release order is created and if the order quantity falls in the range as specied above 1000 the relevan price is taken.
For e.g. Release order 1, quantity is 1001 the price picked is 90 USD
Now the requirement is even if a second release order of one unit is created against this contract then system should pick the 90 USD price and not the 100 USD price.
System should check for all the order quantity for that relevant contract and based on that relvant discounted price should be picked.
Has anyone taken care of this fucntionality , is it a standard configuration or do we need an USER exit. None of the document specifies how this functionality can be achieved.
Thanks,
Yatin

HI ,
I think the function you want is related to scale.
Take a look on your customizing:
trx SPRO
> SAP Supplier Relationship Management
  > SRM Server
   > Cross-Application Basic Settings
    > Pricing
     > Process Condition Types
Open the condition you are using for contract, you are (like 01CT for
example) you are using Scale Type "BASE-SCALE".
"Max No. Dimens" from "No Scales" to "OneDimensional"
Clear "Group Key" field on both conditions
I hope this information will help you
Summer

Similar Messages

  • Value based Permit in maintainance order at release and Technical Completio

    Hi All,
      We have used value based permit in maintainance order at the time of release as well as technical completion, So presently if an order is having a planned cost of greater than 25000 say Rs 30000 , then at the time of release system is asking for permit.
    After execution and confirmation of order if the actual cost is same i.e Rs 30000 then at the time of technical completion the system is asking for permit again which is shouldnt happen, please check for example below,
    We have used classification in permit using table 'CSEVPERMIT' and field 'PKOSTEN' for planned cost of order and field 'IKOSTEN'
    for actual cost, Permit shall be called for planned cost and actual cost greater than 25000.
    EG :
    order 'A' Planned cost = Rs 30000 Permit is called at release  - (Correct)
    Same order 'A' Actual cost = Rs 30000 Permit is called at Technical Completion  - (Incorrect and to be avoided)
    Solution Expected :
    If for order 'A', once the permit is called at release then it should not call for Permit for the second time at Technical Completion if Planned and actual cost is same.
    Thanks in Advance,

    Hi,
    1. I would suggest you to use separate set of Permits for Planned costs and Actual costs ..
    For Actual cost permits in IPMD put Order completion as 02
    For Planned Cost permits in IPMD put Order release as 02
    2. If u have used same permits then in IPMD for Order Completion do not enter anything
    If ur looking something different then check User exit :-IWO10007 Maint.order: Customer enhancement - permits in the order
    regards
    pushpa

  • How to configure release procedure for rate contracts release

    Dear all,
    How to configure release procedure for rate  contract following are the requirements
    they are two release codes c1 & c2 <=100000,>=100000
                    if  c1 is not there c2 has to be approved
         Change in the value of the rate contract contract
         Change in the validity of the rate contract
         Addition of deletion of line items
    While using a non u2013 released rate contract in the PO an error message should shoot out.
    Also the logic should be changed while using the rate contract in the PO.
    The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
    It should be possible to refer existing valid rate contracts in purchase orders.
    Regards,
    bhaskar

    Hi,
    In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables  for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
    class in standard is the same FRG_EKKO, you can use the same for contract.
    To distinguish if it's a contract or PO, EKKO-BSART can be used.
    For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
    You can restrict the document type to set up the release strategy for only contract.
    Of cause, you can also create your own release class Z* for contract copying standard
    one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
    OLME:
    -> contract
    ->Release Procedure for Contracts
    ->Define Release Procedure for Contracts
    ->Release Groups
    If you have already created the PO release class.
    Assign a new chracteristic of Document Category -BSTYP
    Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
    http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES

  • PO Multilevel Release - Value Decreased

    Dear Gurus,
    I'm not familiar with PO release procedure.
    We have a scenario:
    Release is based on the price
    $5000 - $20000 release by FI
    >$20000 release by FI, then release by MG
    How to set it?
    Currently we create 2 strategy:
    FI  consist of FI
    MG consist of FI & MG
    For value $5000 - $20000, we assign FI strategy
    For value >$20000, we assign MG strategy
    The case is....
    1. PO created with value $25000 -> will triger release strategy MG, need FI & MG to release
    2. FI release, then MG release
    3. PO quantity is reduced, so that the PO value also reduce become $15000
    What happening in my system is, the PO release status is reset (block), and now it use strategy FI and required FI to release it again.
    By common sense, it doesn't seem right that FI had release/approve this PO earlier and now FI need to release it again.
    Is there a walk around (or is the current configuration incorrect?) so that in this scenario FI no need to release it for the second time.
    Thank you.

    Hi,
    The behaviour you are seeing is the standard behaviour and is correct.
    See Note 662993 for an explanation:
    When quantities or values are decreased, the system resets the release
    only if a different release strategy is determined for the lower
    quantity or the lower value.
    If no different release strategy is determined due to the quantity or
    the value decreasing, the system retains the releases that already
    exist.
    This is the desired standard system behavior.
    As the note also says: "This function can be changed only by a customer-specific modification.", there is no standard way
    to achieve any behaviour otherwise.
    Regards,
    Purnima.

  • PR created with a reference PR copied the reference material configuration( Characteristic Values).

    Hello,
    I have created a PR with reference to another PR. After adopting I changed the material and saved. After saving, when I checked the variant configuration at the line item level (Characteristic values), its showing the characteristic values of the material of the reference PR. It should be showing the details of the new material which I have used but, its showing the variant configuration of the material used in the PR which I used as reference.
    Ideally, these values has to be changed when I changed the material in the newly created PR.  What might have gone wrong here?
    Example:  PR- Purchase Requisition
                   Mat - Material.
    PR1 contains Mat1.
    I am adopting PR1 and creating PR2 with Mat2.
    After saving, when I check the variant configuration, classification values are from Mat1. I was expecting the values from Mat2 as I have Mat2 in PR2.
    Any suggestions would be of great help.
    Thanks in advance!
    Regards,
    Shaheen.

    Hi,
       Please check whether classification data has been maintained for the second material. If the configuration data doesnt exist for the second material, system cant redetermine and transfer. Refr the note: 588117 - FAQ: Configurable materials in purchasing Question number 5.
       If the configuration data exists and still the data is not changed, refer the note:  920648 - Error in the configuration when you copy PReq item  or 596994 - ME21N/ME51N: Configuration not determined again based on your release.
    Regards,
    AKPT

  • Problems with value-based hierarchies in Oracle 11gR2

    Hello,
    I have the following problem:
    I want to cereate a dimension with 2 hierarchies.
    These hierarchies have to be value-based.
    It's no problem to fill and display one of them, but when I fill both and try to display them, at the lowest level, the parent-child relevancy is now incorrect.
    Let's display this in OLAP Worksheet for Cube Type OLAP 11g :
    lcolwidth=20
    rpr down nim_2 w 25 NIM_2_PARENTREL
                              ------------------NIM_2_PARENTREL------------------
                              ------------------NIM_2_HIERLIST-------------------
    NIM_2                                KON                       AGT
    L1_Total_AGT_A            NA                        NA
    L1_Total_KONZ_K           NA                        NA
    L2_AGT_A_A                NA                        L1_Total_AGT_A
    L2_AGT_B_A                NA                        L1_Total_AGT_A
    L2_AGT_C_A                NA                        L1_Total_AGT_A
    L2_KONZ_1_K               L1_Total_KONZ_K           NA
    L2_KONZ_2_K               L1_Total_KONZ_K           NA
    L3_100_A                  NA                        L2_AGT_A_A
    L3_100_K                  L2_KONZ_1_K               NA
    L3_200_A                  NA                        L2_AGT_B_A
    L3_200_K                  L2_KONZ_1_K               NA
    L3_300_A                  NA                        L2_AGT_C_A
    L3_300_K                  L2_KONZ_2_K               NA
    L4_101_A                  NA                        L3_100_A
    L4_101_K                  L3_100_K                  NA
    L4_301_A                  NA                        L3_300_A
    L4_301_K                  L3_300_K                  NA
    L5_302_A                  NA                        L4_301_A
    L5_302_K                  L4_301_K                  NA
    100                       NA                        L3_100_A
    101                       L4_101_K                  NA
    102                       NA                        L4_101_A
    200                       NA                        L3_200_A
    201                       L3_200_K                  NA
    300                       L3_300_K                  NA
    301                       NA                        L4_301_A
    302                       NA                        L5_302_A
    303                       NA                        L5_302_A
    304                       NA                        L5_302_AAs you see, the lowest level items are only connectet with one of the hierachies, instead connected with both. (100, 101, e.g)
    If I build the same dimension in a 10g Cube, the result is now correct.
    Let's display this in OLAP Worksheet for Cube Type OLAP 10g :
    lcolwidth=20
    rpr down nim w 25 NIM_PARENTREL
                         -------------------NIM_PARENTREL-------------------
                         -------------------NIM_HIERLIST--------------------
    NIM                             AGT                       KON
    L1_Total_AGT_A       NA                        NA
    L1_Total_KONZ_K      NA                        NA
    L2_AGT_A_A           L1_Total_AGT_A            NA
    L2_AGT_B_A           L1_Total_AGT_A            NA
    L2_AGT_C_A           L1_Total_AGT_A            NA
    L2_KONZ_1_K          NA                        L1_Total_KONZ_K
    L2_KONZ_2_K          NA                        L1_Total_KONZ_K
    L3_100_A             L2_AGT_A_A                NA
    L3_100_K             NA                        L2_KONZ_1_K
    L3_200_A             L2_AGT_B_A                NA
    L3_200_K             NA                        L2_KONZ_1_K
    L3_300_A             L2_AGT_C_A                NA
    L3_300_K             NA                        L2_KONZ_2_K
    L4_101_A             L3_100_A                  NA
    L4_101_K             NA                        L3_100_K
    L4_301_A             L3_300_A                  NA
    L4_301_K             NA                        L3_300_K
    L5_302_A             L4_301_A                  NA
    L5_302_K             NA                        L4_301_K
    100                  L3_100_A                  L3_100_K
    101                  L4_101_A                  L4_101_K
    102                  L4_101_A                  L4_101_K
    200                  L3_200_A                  L3_200_K
    201                  L3_200_A                  L3_200_K
    300                  L3_300_A                  L3_300_K
    301                  L4_301_A                  L4_301_K
    303                  L5_302_A                  L5_302_K
    304                  L5_302_A                  L5_302_K
    302                  L5_302_A                  L5_302_K-----
    We are using the latest Version of AWM: Version 11.2.0.1.0A
    Database:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    PL/SQL Release 11.2.0.1.0 - Production
    "CORE     11.2.0.1.0     Production"
    TNS for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Production
    Thank you verry much for any help.

    11.2.0.2 for AIX was announced in October 2010. See DOC ID 1249584.1
    What is being announced?
    We are pleased announce the October 19, 2010 release of Oracle Database 11g Release 2 Patchset 1 (11.2.0.2) on HP-UX > Itanium and IBM AIX on POWER Systems.Patchset 10098816
    Description 11.2.0.2.0 PATCH SET FOR ORACLE DATABASE SERVER
    Product Oracle Database Family
    I have looked, but I cannot find a formal bug for this problem. My hunch is that it was fixed as a side effect of other changes, and I know there were several in this area. My simple test case did work in 11.2.0.2, so I hope it is all fixed. But feel free to enter an SR if you want. (If you mention my name in the SR then support should contact me.) You should certainly do this if moving on to 11.2.0.2 does not resolve the issue.

  • Timestamp data type on S[range C on E] constant value-based range windows

    Hello,
    My questiong is about how can we use timestamp value on S[range C on E] constant value-based range windows.
    I have a LotEvent which i should collect and sum lastQty data for last ten minutes of market time (sendDate)
    A normal [range 600] query does not work for me because i would like to use the exact time which data has been generated by the market (sendDate).
    Here is the event;
    public class LotEvent{
         private Double totalQty;
         private float lastQty;
         private String symbol;
         private String messageType;
         private Integer dataInterval;
         private String sendDate;
    send date is always in "MM-dd-yyyy HH:mm:ss" format.
    I have tried to use the following query but this gives an error;
    Invalid statement: "select symbol, sum(lastQty) as lastQty, 10 AS dataInterval
    +from lotInputChannel [range INTERVAL "0 0:0:15.0" DAY TO SECOND on >>sendDate<<]+
    group by symbol"
    Cause: Datatype char is not valid for value based windows
    Action: Use a valid datatype for value based windows>
    Here is the CQL;
    <?xml version="1.0" encoding="UTF-8"?>
    <wlevs:config xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application">
    <processor>
    <name>lotProcTenMin</name>
    <rules>
         <query id="tenMin"> <![CDATA[select symbol, sum(lastQty) as lastQty, 10 AS dataInterval 
                from lotInputChannel [range INTERVAL "0 00:10:00.0" DAY TO SECOND on sendDate]
    group by symbol]]> </query>
    </rules>
    </processor>
    </wlevs:config>
    i have tried this cql after changing the sendDate data type to long which is the time in milliseconds value but it did not work.
    select symbol, sum(lastQty) as lastQty, 10 AS dataInterval
    from lotInputChannel [range INTERVAL "0 00:10:00.0" DAY TO SECOND on to_timestamp(sendDate)]
    group by symbol
    The query above does not work also when sendDate is a String in "MM-dd-yyyy HH:mm:ss" format
    At last i tried the following query with sendDate as time in milliseconds (long) value. It works! but i still would like to know how to use timestamp in S[range C on E] queries
    select symbol, sum(lastQty) as lastQty, 10 AS dataInterval
    from lotInputChannel [range *600000* on sendDate]
    group by symbol
    public class LotEvent{
         private Double totalQty;
         private float lastQty;
         private String symbol;
         private String messageType;
         private Integer dataInterval;
         private long sendDate;
    Could anybody please help me with this issue?
    Edited by: user8830791 on 01-Aug-2011 06:39

    It seems that you should configure the channel "lotInputChannel" as an application timestamped channel.
    You can do that as follows -
    - Have "sendDate" as a long and let its unit be milliseconds
    - Use the following child elements of <channel> for the "lotInputChannel"
    <wlevs:application-timestamped is-total-order="true">
    <wlevs:expression>sendDate*1000*1000</wlevs:expression>
    </wlevs:application-timestamped>
    The multiplication by 10^6 is required since the units need to be converted into nanos
    With this, you could use the query -
    select symbol, sum(lastQty) as lastQty, 10 AS dataInterval
    from lotInputChannel [range 10 minutes]
    group by symbol
    Of course, for the above to work, a requirement is that the value of "sendDate" is non-decreasing.
    That is if e1 is before e2 in the "lotInputChannel" then e1.sendDate <= e2.sendDate
    Edited by: Anand Srinivasan on Aug 2, 2011 6:57 AM

  • PO release strategy based on effective price

    Hi
    We have PO release strategy based on net order value.
    If we make the release strategy based on effective price then what would be the impact? What r the risk factor involved?
    Regards
    sapmm1234

    Hi,
    Net order value is known ie we give value for the characteristicex: RS.100000 or 1 crore etc, but  effective price is unknown how can we mention that a charactristic value? I dont understand
    Regards

  • PO release strategy based on Material Group (CEKKO - MAKTL)

    Hi Experts,
    I have configure the Rel strategy based CEKKO-MATKL (material group) for purchase order, but when i raise the PO Rel strategy is not affecting, Can any body tell me why.
    Regards,
    Kumar

    You can set Release strategy based on Material group & other Line item specific fields..
    You better follow a suitable and hinder less process..
    For PR use Material group & Account Assignment based Release process..
    then for PO use a Release Process based on Header level fields like Doc type, Amount, pur Group etc..
    So that the approved PR line can be converted into PR and then the PO also subjected to Release before sending it to External Vendor..
    Even if you want you can make that the PO can not be created without referencing PR for SOme users or All users..
    based on your business requirement..

  • Billing value should not exceed contract(value based contract) value

    Hi,
    We are using value based contract and in item category we set E in incompletion rule which stops me to create relaease order where its value exceeds the contract value.
    But via release order we recognize revenue(service based revenue recognition) and we do billing directly through contract via milestone billing plan,
    At present i can bill more then my contract value.Now i want to system should not allow me to bill mre then contract value.
    I checked the option in VOV8 and VOV7 but all those are meant for release order not for bliing.
    Thanks in advance.

    Hi Satya
    You can set the billing amount in milestone billing plan itself. based on that value billing will done.

  • Release Value not Updated to Value Contract

    Hi,
    I'm trying to set up a value contract and subsequent sales order (release or call off orders).
    My document flow and copying control have been set up such that after I have created a value contract, I can create a sales order with reference to the contract. The contract data and items get copied over to the sales order. But after I have saved the sales order, the release value is not updated. Also the reference status in the contract item is 'Not reference'.
    Did I miss out any important configuration?
    Help would be greatly appreciated.
    Thanks,
    HweeLing Tay

    Hi,
    Yes the update document flow indicator has already been checked 'X'.
    The contract item category completion rule has already been set as 'E'. I have tried with C or D but still doesnt work.
    Any suggestion?
    Thanks,
    HweeLing Tay

  • OBIEE and Oracle OLAP Value Based Hierarchies

    Hi there...
    I have a value based dimension built on Oracle OLAP and want to map it on OBIEE Administration tool.
    I've been using the above link as reference:
    http://www.oracle.com/technology/obe/olap_biee/CreateBIEEMetadata.htm
    There's no option to import from Oracle Multi-dimensional Database. Either to import/configure the view created by OLAP as an Unballanced or Ragged Dimension.
    I also checked this example, but it uses ESSBASE as the multi-dimensional source....
    http://www.rittmanmead.com/2008/08/27/ragged-hierarchy-handling-in-obiee/
    How to map this Ragged Dimension created in OLAP workspace in OBIEE? Any suggestions or directions will be highly appreciated...
    Thanks in advance
    Marcos

    Mark and others,
    You can create OLAP_TABLE views with level columns on top of value-based hierarchies. BI Beans used to do that too behind the scenes in Discoverer Plus OLAP. If you trace the Discoverer session, where you are querying data from Value-based hierarchies, you will see that it also generates OLAP_TABLE views with level columns in it.
    So the question is how to do it. Internally, even for Value-based hierarchies Oracle OLAP keeps track of the "depth" of each value by using a structure called GID_DIMENSION (i.e., Grouping Dimension). Here is an example of a view on top of a value-based hierarchy (CFC_ACCT_GAPP) for RPT_ACCOUNT dimension. You have to know how "deep" your value-based hierarchy is.
    Similar kind of a thing is done by OLAP View Generator application, which I never use - since I always prefer to define my own OLAP_TABLE views.
    This kind of a view can then be used in the RPD of OBIEE.
    select *
    FROM table(OLAP_TABLE ('AW duration session',
    *'DIMENSION RPT_ACCT_ID FROM RPT_ACCOUNT WITH*
    HIERARCHY RPT_ACCOUNT_GAAP_PARENT   FROM RPT_ACCOUNT_PARENTREL(RPT_ACCOUNT_HIERLIST ''CFC_ACCT_GAAP'') INHIERARCHY RPT_ACCOUNT_INHIER
    HATTRIBUTE RPT_ACCOUNT_GAAP_LVL_NUM FROM RPT_ACCOUNT_DEPTHVAL
    FAMILYREL RPT_ACCOUNT_GAAP_LVL1,
    RPT_ACCOUNT_GAAP_LVL2,
    RPT_ACCOUNT_GAAP_LVL3,
    RPT_ACCOUNT_GAAP_LVL4,
    RPT_ACCOUNT_GAAP_LVL5,
    RPT_ACCOUNT_GAAP_LVL6,
    RPT_ACCOUNT_GAAP_LVL7,
    RPT_ACCOUNT_GAAP_LVL8
    FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
    FAMILYREL RPT_ACCOUNT_GAAP_LVL1_DSC,
    RPT_ACCOUNT_GAAP_LVL2_DSC,
    RPT_ACCOUNT_GAAP_LVL3_DSC,
    RPT_ACCOUNT_GAAP_LVL4_DSC,
    RPT_ACCOUNT_GAAP_LVL5_DSC,
    RPT_ACCOUNT_GAAP_LVL6_DSC,
    RPT_ACCOUNT_GAAP_LVL7_DSC,
    RPT_ACCOUNT_GAAP_LVL8_DSC
    FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
    RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
    LABEL RPT_ACCOUNT_LONG_DESCRIPTION
    ATTRIBUTE ACCOUNT_LDSC    FROM RPT_ACCOUNT_LONG_DESCRIPTION
    ATTRIBUTE ACCOUNT_SDSC    FROM RPT_ACCOUNT_SHORT_DESCRIPTION
    ATTRIBUTE ACCOUNT_TYPE    FROM RPT_ACCOUNT_TYPE
    ATTRIBUTE SOURCE_LEVEL    FROM RPT_ACCOUNT_LEVEL
    ATTRIBUTE CALCULATION     FROM RPT_ACCOUNT_CALCULATION
    ATTRIBUTE CALC_DATA       FROM RPT_ACCOUNT_CALC_DATA
    ATTRIBUTE GAAP_SORT_ORDER FROM RPT_ACCOUNT_GAAP_SORT_ORDER
    ATTRIBUTE RATIO           FROM RPT_ACCOUNT_RATIO
    ATTRIBUTE ACCOUNT_LEVEL   FROM RPT_ACCOUNT_LEVELREL'))

  • AWM 10.2.0.1 - I can not choosing Value Based hierarchy

    I have Oracle client 10.2.0.1 software with AWM 10.2.0.1 . I want to build a dimension with value-based hierarchy . In AWM I have hierarchy editor with the two radio buttons for choosing type of hierachy : Level Based hierarchy and Value Based hierarchy . But the secod one (Value Based hierarchy) is disabled - I can not choosing this type of hierarchy . Why this?
    Thanks in advance,
    Aurel

    Hi there,
    I really would not recommend that you work with the 10.2.0.1 version of AWM. This version is fairly old now and there have been a number of important bug fixes added to more recent releases.
    What version of the Oracle database are you running? And on what operating system?
    I suggest that you consult the following link and ensure that you are working with the versions of BOTH database and AWM that are recommended by Oracle:
    http://www.oracle.com/technology/products/bi/olap/collateral/olap_certification.html
    Thanks
    Stuart

  • How to sum up billing documents and provide scale based discounts

    Dear Gurus,
    Here is the client's requirement:
    Actually the client requires that after two weeks some of the customers are given discount based on the total quantity or value been sale.
    Invoice list seems a great option but issue is that its sums up the factor discount from all the billing documents.Although,the client requires that after the toal quntity or value been taken from the billing docuements a scale is applied at the level of invoice list.For example
    billing 1  value 10,000 discount 3 %   = 300
    billing  2 value  1,000  discount 3%    =30
    system response:
    invoice list  value 1100 discount =330
    client requirement
    invoice list value 1100
    scale  :  if value <= 500  discount 3%
                 if value >500 && value<2000  discount 4%
    required value : invoice value 1100 discount 400
    Kindly help , if there some better option availble in invoice lists or any other solution you may come up or suggest.
    Regards,
    Sam Ahmed

    Hello,
    you can create a discount condition type and add access sequence to it. If your client does not have access sequence as per your requirement create one with copying a standard access sequence for discounts.
    you can create a separate table to fulfill changes so that access could be made.
    regards,
    amol marathe

  • Value Based Status Profile

    Dear Gurus,
    I want to use status profile for setting the document status.
    I have scenario in which i need to use value based status.
    That means a user 1 should be able to set the status if the Net Value of the sales order has reached A amount
    If the Net Value is above A and upto B User 2 should be able to set the status. and so on.
    I am aware of the authorization key in the status profile, but do not know how to link it to a value.
    Your reply in this matter is highly appreciated.
    Thanks
    KS

    Not sure what kind of status you want but if you are looking for value based  credit release then it can be done through maintain authorization option in credit management section of basic functions.

Maybe you are looking for