Duplicating Conditions in Schema

Hi All
I want to link a Delivery Cost Condition to the Discount Condition.
e.g.
Condition ZAB1 - Discount Condition - Percentage - Negative
Condition ZAB2 - Delivery Cost - Percnentage - Positive
I want to flow the Percentage of the Delivery Cost Condition automatically as of the Discount like if 3% is Discount then Delivery Costs should also be 3%
So In Calculation Schema the Sequence is like
10 PB00
20 ZAB1 10 10
30 ZAB2 20 20
For ZAB2 I could have used " From " - " To " as 10 10, but I want to link it to the ZAB1, so i used from - to as 20 20.
I maintained these conditions in MEK1 as ZAB1 - 3% and ZAB2 as 100 %
But while using this schema in PO, my Delivery Costs are getting negative as I linked this to the ZAB1 (negative Conditions).
How can overcome this. I want to maintain the changes to only one condition i.e. ZAB1 and other should flow wrt ZAB1 only.
Can anyone guide me on ?

Hi,
this is my suggestion. i haven't tried.
use negaive simple for delivery cost also anr try .
how the system calculate the delivery cost.
Condition ZAB1 - Discount Condition - Percentage - Negative
Condition ZAB2 - Delivery Cost - Percnentage - Negative
SAM

Similar Messages

Conditional Authorization Schemes?

Can you implement conditional authorization schemes? For example, I have an application that a handful of users will need to be able to edit and a handful of users will need to be able to look through the screens of the app, but not modify data. Can you have a default authorization scheme of say "read-only" where the page items are not editable, and if you belong to the "read-write" scheme, then the fields are editable? Is there an easier way?

Hi "Potter_geek",
unfortunately there is no such "read-only" authorization scheme which automatically switches your page items to read-only.
I see 3 possible workarounds:
1) Add code to the "Read-Only condition" for each item.
2) Add a condition/authorization just to your submit/create/... buttons, so that they are not displayed in case of read-only. All the items are still modifiable, but the user can't submit it.
3a) Just create an "Application Level Process" (before computation/validation) where you check if a user has write access, if not trow an error that he isn't allowed to change anything. => not so user friendly
3b) Create a page 0 region of type HTML with display point "After footer" and which has the authorization scheme read-only. It should contain a small javascript script which loops through all the INPUT/... elements of your page and set's them to readonly="readonly".
Just some thoughts...
Patrick
Check out my APEX-blog: http://inside-apex.blogspot.com
Check out the ApexLib Framework: http://apexlib.sourceforge.net

Enhancement: readonly condition - authorization scheme

I don't know where to file a enhancment request, so I file it here. I have authorization scheme for users, that are not allowed to edit anything. I use it successfully on the buttons, that they should not see (like SAVE, DELETE etc).
But currently I have to rewrite the logic into item's Readonly condition field every time a form item has to be readonly for them. It would be covienient, if I could select condition type to be Authorization Scheme and into Expression 1 text area write the name of the scheme...

Kaja,
We're working on enhancements like this to make the read-only version of a page easier to create declaratively. Thanks for your notes.
Scott

Duplicating Conditions...Is it possible?

I have a very complex condition in one of my receiver determinations and have the very same condition in another interface determination. I hate to maintain it in 2 different places. Is there a way to assign this condition to some type of variable and reuse it?

would it be an option to add an additional business service to represent the same receiver?
then you could use receiver determination instead of interface determination.
So now you have:
sender A -> receiver B, interface X
sender A -> receiver B, interface Y
you change this to
sender A -> receiver B1, interface X
sender A -> receiver B2, interface Y
but B1 and B2 represent the same system.

Pricing Conditions in Foreign Price Calulation Schema

How do we handle the duties and charges for foreing PO that are not known at the time of creation of PO. These costs are only confirmed after the material is delivered or invoice is received by vendors.

you can have conditions in schema for CVD, BCD, AED, Cesses etc, you can see standard condtions in m/06.
in the schema assign the account key and accural keys. in OBYC you will have to assign the corresponding GL
assign the CVd condtion to default values in SPRO LG tax on goods movement India default values.
in P.O put the percentage values. enter the custom vendor number by clicking open the condiditon in PO
when the material arrive, you can do MIRO for plan costs for the actual custom valuation amount.
while doing MIGO you can transfer the plan MIRO value by entering the MIRO doc number in the pop up

Conditions in Purchase Order - No scroll bar/Sales Tax value not in mmr

Hello,
I am stuck in a weird problem where I have created a Condition Calculation Schema, assigned it to Schema group and assigned that schema to vendor, but when i open my condition in the PO, it does not give me scroll bar i.e. I have calculation Schema with around 10+ conditions, but when I try to put all the conditions in PO at one time, the scroll bar doesnot come up and without it, I cannot view all my conditions in the PO. Its saving the conditions though as seen in report, but cannot display it in PO without the scroll bar. Any ideas?
Another assignment is that sales tax value and % should not increase the mmr value at time of GR, but when I do GR its adding the sales tax value to mmr value, my requirement is just Gross price be added to mmr, not sales tax value/%. I tried the Statistical checks in Calculation Schema, but to no vail, at GR the sales tax value is being added to the mmr record. Any ideas?
Lots of points awarded for answer/answers.
Any clue will help
Thank you/Afshad
Edited by: Afshad Irani on Jan 14, 2009 10:27 AM
Edited by: Afshad Irani on Jan 14, 2009 2:32 PM
Edited by: Afshad Irani on Jan 15, 2009 6:19 AM

Q Another assignment is that sales tax value and % should not increase the mmr value at time of GR.
Ans:
Dear Afshad,
Reference to your question, you need to do few settings in your Condition Type and Pricing Schema, if you need Sales Tax value & % not to include in your Material value.
1 - In SPRO, Check that in your condition type, Control data 2 tab, Accruals check box should not be selected.
2 - In your Calculation Schema, against your condition types for Sales Tax % and Sales Tax Value, select the check box for Manual & Statistics.
3 - Also in your Calculation Schema, you should not select any account key in AccKey (Account Key) and in Accruals colomns.
If any one of these setting is not defined, the valuation price for your material will be increased due to the fact that your settings for Condition type and Calculation Schema is allowing the same to hit the value of your material directly.
Hope it works for you.
Regards
Jibran

How to Avoid Duplicate Pricing Condition Types In Sales Order and Billing

Hi SAP Gurus
I have a requirement in Pricing (Sales and Distribution). We have issue duplicated condition types in Sales order and it causes wrong posting in to accounts.
I want make them inactive duplicated Condition type in Sales order and Billing Documents.
Please advice me how to make inactive status to duplicated Condition types
Thanks in Advance.
Ravikanth

Hi
You can use Exclusion Group
You can define 2 Groups and include 1 condition type in each
and define exlusion procedure
A   Best condition between condition types
B   Best condition within the condition type
C   Best condition between the two exclusion groups
D   Exclusive
E   Least favorable within the condition type
F   Least favorable betweent the two exclusion groups
you can use Exclusive to set your condition type or as per your requirement
Regards
Jitesh

Calculation Schema on Quotations...

Hi people, ... Question .. , What is the Conditions Calculation Schema used by default when creating a Quotation ? does it uses the Schema related to the standar purchase order ? thanks !

Hi,
These are the standard pricing schemas used in standard SAP.
1) RM0000 and RM1000
For POs, quotations, and scheduling agreements
2) RM0001 and RM1001 for Contracts
3) RM0002 and RM1002 for purchase inforecords
4) RM2000 for stock transport orders and stock transport scheduling agreements
5) RMMP00 for determining the market price which can be entered for each material
Thanks & egards
Anilkumar Dalai

How to set differnt Currency at header and conditions levels

Hi Guys,
if we take USD Currency at header level for import Purchase orders, system automatically convert all the conditions(Price Schema's conditions in USD), while we want Price schema's condition in india Rupee. because all the customs,cess duties and CVD have to pay in Indian Rs. not In USD.
if we take INR at header Level, in this case Purchase order becomes in Rupee, while it should be in USD (for import Vendor)
Pls suggest the solution
Regards,
Ashish

Hi Ashish,
It cannot be changed in the PO level but can be done in Invoice Verification Level. Go to MIRO and before entering the reference documents (PO, Delivery Note, etc) go to DETAILS TAB and make the Exchange rate as 1.00 and hence 1 USD = 1 INR.
By this way only it can be done.
Hope this is useful. Kindly mention if so.
Regards,
Elanchezhian. K.C.

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:
1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

Conditional Display based on Function and Application Item?

I have a function within my DB that checks if the STAFF_ID (an application level item) is a "Super User" within my application. The function ("is_super-user") returns 1 if the STAFF_ID given is a Super User. (I am not using ApEx users/groups)
How would I call this function within the Conditional Display of a button?
I tried the following with no luck... (although it does not give me an error)
Conditional Type: PL/SQL
Expression 1: is_super_user(&STAFF_ID.)=1

Matt is that you? You're not makin it real easy to identify you by name...
The function ("is_super-user") returns 1...
That should be is_super_user (without quotes, of course).
Your previous attempt should have produced an error. But this should work:
Conditional Type: PL/SQL
Expression 1: is_super_user(:STAFF_ID)=1
...assuming the function has a varchar2 input parameter.
And then to make it secure, you'll want to make that application item Restricted so nobody can pass in a value from the page. This kind of condition is a good use of authorization schemes which you can name/create once and attach to all sorts of components throughout the app. Speaking of other components, you should protect DML processes using the same condition/authorization scheme because just because there is no button visible on the page doesn't mean someone can't put one there and submit the page anyway.
Scott

Schema import

Hello,
can I without conditions my Schema in Oracle 8i to Oracle 9i export. If yes, pleas how do i that in Datail.
Th schema is in Copmuter A Oracle 8i, i hav exported this schem in an File(200MB). I want to import thise File in another cpouter B with Oracle 9i.
I built a schma user with the same Name and password at this first in computer b and then, what muss i do?.
please help
Manar

Manar,
Check out this link: http://asktom.oracle.com/pls/ask/f?p=4950:8:11417304998526013939::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:376818221507
Hope it helps,
Regards,
Srinivas Nandavanam

Schema gruop vendor & purchasing schena group

Hi Experts,
what is meant by vendor schema and purchasing schema groups,
actually where they are stored?
in pricing procedure if we give the values for fields they are stored as records?
what are the fields in that condition table ?
please give in detail explanation,
it would be a great favour to new comers,
please do not send links,
in that only steps, and there are not clear explanations,
will give rewards,
it would be tons of guidence to others,
Regards

Hi,
Schema group vendor is a key used to denote the to which pricing procing proceedure the vendor is linked.
Purchasing schema group also denotes for the same purpose 'to which pricing procedure the purchase organisation linked'.
The above two key fields can be defined at spro-mm-purchasing-conditions-defin schema grouop.
The vendor schema group stores at LFM1-KALSK
the po schema group field is KALSE.
Infact the pricing proceedure is linked to vendor and purchase organisations via these keys in the path which is the prviosly told at 'Define schema determination'.
In the pricing procedure we are going to give the conditions types which are required for our individual price calculation and the calculation inorder to come to a final price like 'Gross price-fright-taxes etc = Net price.
All the components which we give in the pricing proceedure are going to sit in tables and when ever they are required they will be pulled in.
When you create a document the vendor,Pur ORG decides over the pricing proceedure and puulls your procedure to the document you are going to create.
Condition Table.
The access sequence in the PB00 condition type searches for a valid condition record in a condition table.
For each access in the table there will be a record for the combination of material,vendor inforecord or other combinations .Standard combinations can got from 'MAINTAIN CONDITION TABLE' transaction code in the same path.
For each record in the table you can maintain the record price at MEK1/MEKA transactions.
if you maintain this the data in the record will be pulled into the document as documnet price.
That is briefly about the pricing.
Regards,
Raghu.

Time Schema

Hi Everybody,
I would like to know if any way i can specify employees hire date in Time schema.
My requirement is When an employee is hired his holiday pay starts after 60 days of hire date.
I have to put this condition in schema.
Could somebody tell me how can i write a schema on this, Will it be ok if i get the Hire date from 0041 infotype or is there any other suggestion.
Appreciate any kind of help.
Thank you,
HR

Hi Prakash
Thank you for the reply and sorry for responding you late.
I was working on the HRS=YSAO in my schema.
I could partly change my schema but getting stuck at one place. Hope you can help me in that. This is really very urgent. Appreciate any kind of help.
My current schema looks like this:
                   D OUTWPMASSN
        D OUTWPSTAT2
3       D HRS=L9053 HRS?60
3*     HRS=L9053 ADDDB9053Z
       **3<      HRS=L9053 HRS+1     ADDDB9053
       99
The change that i made is to this schema is
                   D OUTWPMASSN
          D OUTWPSTAT2
3        D HRS=YSAO HRS?2
3*      HRS=L9053 ADDDB9053Z
      **3<       HRS=L9053 HRS+1     ADDDB9053
      99
above this whatever change i am trying to make the system is issuing syntax error.
I am new to this schemas and trying to learn it.
Could you please help me in this. Its really very urgent.
Thanks,
HR

Dynamically color to each column in Cross-tab report

Hello All,
I am a newbie in Crystal report,from last few weeks, i am working on cross tab crystal report.i have a requirement to show color dynamically for each column.i am adding an attachment how i want it. i tried dynamic coloring using object field formula but it is showing red color to all data.i want red color data when in 2nd cross tab report data is beyond upper or lower limit in first cross tab table. it will be very helpful if somebody will give me any clue on this.... i read so many articles now it seem like impossible for me..:(
i am using visual studio 2010 and sap crystal report version 13.0.0.99 for visual studio 2010.

Hello Manish,
I have attached a sample report that does this. You will need to remove the .txt extension from the attached file to open it as an .rpt file.
Please right click on one of the value fields of the first cross tab in the report > Format Field > Common > Suppress if Duplicated conditional formula.
The nested formula is as follows;
numbervar array l;
numbervar array u;
numbervar x:=CurrentColumnIndex;
if GridRowColumnValue ('@limit') = 'lower limit' then
(redim preserve l[x];
l[x]:= tonumber(CurrentFieldValue))
else if GridRowColumnValue ('@limit') = 'upper limit' then
(redim preserve u[x];
u[x]:= tonumber(CurrentFieldValue));
false
So it assigns each lower and upper limit value for each client (in the sample it is country) to an array using the cross tabs column index to index the array and it ends in False as we don't actually want it to suppress if duplicated. This nested formula is just used to generate the arrays of upper and lower values.
In the second cross tab if you again right click on one of the value fields > Format Field > Font > Color you will see the following conditional formula;
numbervar array l;
numbervar array u;
numbervar x;
if not(tonumber(CurrentFieldValue) in l[CurrentColumnIndex] to u[CurrentColumnIndex]) then
crred
else
crblack
So this compaes the current field value to range generated by the 2 arrays and assigns a color based on whether or not it is in the range.
Regards,
Graham

Duplicating Conditions in Schema

Similar Messages

Maybe you are looking for