Condition on a characteristic
Hi
I have a report that I need to display only the latest created on date of a document, some documents have 10 created on dates and some have less.
Is it possible to create a condition on a characteristic, like the TOP N=1?
Any suggestions? This are exemples of my created on dates.
<Removed>
Sold-to party Created on
4501009 12/17/2008
8/28/2007
2/13/2006
6/14/2005
8/13/2004
9/25/2002
10/26/2001
8/28/2000
11/25/1999
8/21/1999
4501029 4/6/2009
9/11/2008
4/8/2008
Edited by: Arun Varadarajan on Apr 30, 2009 11:33 PM
Hi,
Just create a replacement path variable using date, and use it in calculated key figure, with agregation maximum. and use it in Query as a keyfigure.
Regards,
Similar Messages
-
How to restrict values and apply condition for a characteristic in a query.
Hi,
I have to add two customer class(characteristic) fields to my query which is available as a navigational attribute in my multiprovider ( from which my query is built ).
One field should give the values directly from master data. The values would be PV, CV, IT, OT. The other field should give only PV and CV based on the condition - Except CV, all others (ie. IT and OT) should be converted as PV.
I like this to be achieved in the query level since i dont want to disturb the underlying cubes in the multicube.
So i have two questions.
1. How to bring two fields in the query for the same characteristic.
2. How to achieve the condition in a characteristic for second customer class field mentioned above.
Could somebody help me in solving this?
Thanks in advance,
SomenathHi Somenath,
you are absolutely right;)
Besides the Third step
Try to add two new Selections to your Structure as
New Selection1 -> Set the Customer Class value to fix 'PV'
New Selection2 -> Set the Customer Class value to fix 'CV'
<b>you have to add</b>
New Selection3 -> Set the Customer Class value to fix 'IT'
New Selection4 -> Set the Customer Class value to fix 'OT'
Fourth step
Hide these four selections
Fifth step: Add a new formula to your Structure
(Customer Class == New Selection3)* New Selection1(Customer Class == New Selection4)* New Selection1(Customer Class == New Selection1)* New Selection2+Customer Class == New Selection2)* New Selection2
Hope it helps
Gabor
ps: experts maybe suggest easier way... -
Need to add new fields to the condition table
Hello All,
The requirement is to create the new condtion table for MM containing the following fields and maintain the entries in this table:
- client
- characteristic
- class
- internal characteristic.
THe condition tables are created via tcode M/03 or through the customizing path
Material Management > Purchasing > Conditions > Define Price Determination Process > Maintain Condition Table.
The problem which i am facing is as follows :
-SAP has the standard procedure for the generation of the condition tables . Selected fields are made available by SAP in the field catalog and we can select only from the those available fields. Once we select the required fields the condition table is automatically generated in the background.
-As the requirement is, we need to have 4 fields in the generated condition table (client, characteristic, class and internal characteristic), but the problem is that none of these fields are available in the field catalog which is provided by SAP (in tcode M/03, M/04 and M/05).
-Designing of the Z table wonu2019t be useful as we would not be able to use the Z table as the condition table.
Can you please suggest how can we add the desired field to the existing field catalog in M/03 or is there any other alternate solution to this ?
Thanks in advance for your help.>
Rinkesh Doshi wrote:
> Hello,
>
> The specific ABAP question which I have is :
>
> Is there any way in which we can enhance the existing field catalog in M/03 tcode to include the 4 new fields (client ,characteristic,class,internal characteristic) ?
>
> Thanks.
Please post your code which you developped until now and show us where the problem is. I cant see any ABAP related question. -
Pricing Condition is Duplicating on Changing the Variants in Quotation !
Hi,
I have a requirement, where the Pricing Condition (Custom Pricing Condition Specific to the Variant Pricing) is duplicating on changing the Variants in Quotation to be stopped or deleted. I suppose, the variant pricing condition should not be newly added to the pricing table each time, there is a change in the material variants as chosen by the business/user with the Quotation. Instead, I assume, the existing cost for the variant pricing condition should update each time, when the variant material is changed by the user. I am not sure, whether this issue can be controlled in the configuration? or Can I control the occurrence of the duplicate pricing condition inside any user exit by deleting the duplicate condition, but retaining the newly added ( Recently added pricing table entry for that condition)? I am not sure, what are the possibilities to fix this issue? Appreciate if you could provide me with a suitable solution.
Thanks for your time.
Thanks,
KannanHello Kannan.
I have the Same Problem. do you have a solution for the same?
i have written a pricing condition at the characteristic level using pricing Factors. however when i change the characteristic. it is duplicating the condition instead of refreshing it. -
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 -
Hi,
I would to apply a condition in a query with a structure row with selection characteristics for exclude the rows with blank values.
I want to apply this condition on all characteristic selection but during the creation of condition I must seletc once element of structure.
If I create one condition for every select characteristics it show only the totals.
Can you help me please?
Thanks
GiamarcoHello Gianmarco,
dont use conditions but the display setting to supress zeros.
You have to set it twice - once in query properties / rows/columns
and second is to demark the checkmark in the structures propoerties / display.
regards
Cornelia
dont forget to assign points -
BW 3.5: Filter Characteristic based on another Characteristic
Hi guys, I need your help.
I have created one query. In this query, there is 2 characteristic in filter condition. The first one is Consolidation Group (single variable and input come from user) and the second is partner unit (hardcode/ constant : A500, A700, A710, A720, A730, A740). The problem is user want dynamic filter condition for Partner Unit.
So I need to change the filter condition for this characteristic.User want this condition happen:
- If user input Consolidation Group = '10000' then partner unit will be filtered by : 'A500', 'A700'
- If user input Consolidation Group = '10130' then partner unit will be filtered by : 'A710','A720'
- If user input Consolidation Group = '10140' then partner unit will be filtered by : 'A730','A740'
When user want this condition happen, I think I must use hierarchy because there is possibility to add another partner unit in consolidation group (example: If user add partner unit 'A800' in consolidation group '10000' (in SAP system) then partner unit will be filtered automatically with 'A500', 'A700', and 'A800').
My question is:
1. Where do I need to create hierarchy? On characteristic Consolidation Group or Partner Unit?Because both infoobject don't have any hierarchy at all
2. How to create dynamic hierarchy filter condition? Because in this problem, static hierarchy filter condition can't solve the problem. What i mean dynamic in here is when user input consolidation group 10000 then Partner Unit will be restricted to node Cons Group 10000 and so on...
Thank you and Regards,
SatriaHi Satria,
If you use customer exit variable for partner. it may help you.
Please check here.....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/59069d90-0201-0010-fd81-d5e11994d8b5
Customer Exit for Query Variable
http://help.sap.com/saphelp_nw70/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/content.htm
http://sapbwneelam.blogspot.com/2007/10/how-to-create-populate-user-exit.html
http://www.scribd.com/doc/7477843/Five-Ways-to-Enhance-SAP-BI-Backend-Functionality-Using-ABAP
http://www.erpgenie.com/bw--km/1097-sap-bw-query-user-exit-rsr00001
Thnaks,
Vijay. -
Reg: bussiness object,condition object& customising object
Hi,
Can anybody help me out to know what is mean by Business Object,Condition Object & Customising object
Thanks & regards
DibyaA business object represents an actual object in the real business world. It describes an integral business context. This encapsulation leads to simplification, because the inner structuring of a business object remains hidden in additional nested objects. Business APIs as methods of business objects enable external systems to access R/3 System functions, via the Internet.
Condition Object: You assign preconditions and selection conditions to the characteristic or characteristic value to which the condition applies.
Customizing Object: A customizing object is an SAP component, to which a customizing object with the same contents in another component is assigned. The contents of the customizing objects have to be synchronized in different systems in a system landscape. -
Problem during material variant creation
Hi Guys,
I am trying to create material variant in MM01. I entered configurable material let's say DESKTOP. nOw i have partial variant scenario so instead of entering all 30 characteristics i need to enter only 3 characteristics.These 3 charcteristics based on which partial matching will happen in sale document.
My requirement is as out of 30 , TEN chars. are maintained as required entry. So system is asking me to enter all 10 required chars. in material master which my scnario don't want.But the same is required in Sales document.
How to remove this required entry in case of material master creation and keep required entry in sales order or quotation?
RegdsHi,
You can decide whether it is mandatory to assign a value to a characteristic on the basis of transaction code.
You must use [selection condition|http://help.sap.com/saphelp_erp60/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm] which calls the [user-defined function|http://help.sap.com/saphelp_erp60/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm]. In function you need to analyze sy-tcode and raise the predefined exception FAIL for those when you don't want to assign a value to a characteristic (e.g. mm01, mm02). Contact your ABAP team to create such a function.
Don't tick the characteristic as required entry in class definition but assign this selection condition to this characteristic in class.
Regards,
Alexander -
Hi guys am in need of help from u
am not so clear about the SD process flow
can anyone pls send me a PPT on SD process flow
to my email id:- (<REMOVED BY MODERATOR>).
thanking u in advance..
Regards
Jino.Sales Organization :
Responsible for:
Distribution of goods and services
Negotiating Sales Conditions
Product Liability and rights of recourse
A sales organization is uniquely assigned to a company code
Master datas are separately maintained for a sales organization
All items in the Sales and Distribution document belong to a sales organization
Distribution Channel:
Means through which products and services reach the customer
A distribution channel:
Defines responsibilities
Helps in achieve flexible pricing
Differentiate Sales statistics
Division:
A division is used to group products and services.
A division represents a product line.
Sales Area:
A Sales area is a combination of
Sales organization
Distribution Channel
Division
Each Sales and distribution document is assigned exactly to one sales area.
A sales area can belong to only one company code.
Sales Organization
Distribution Channel
Division
Sales Area
Plant and Storage Location:
A Plant is a location where stock is maintained
Plant and storage location are used by all logistic area of R/3 System
A Plant is uniquely assigned to a company code
Shipping point:
Shipping point is the highest level of organizational unit in shipping
Each outbound delivery is processed by one shipping point
Shipping points are assigned to a plant
More than one shipping point can be assigned to a plant
Sales and Distribution is SAP begins with establishing customer relationship and ends with invoicing for the delivery of goods or service provided to the customer .
A Standard sales transaction has the following flow:
Inquiry
Quotation
Order
Delivery
Billing
The customer order management cycle begins with pre-sales activities.
A standard order in SAP contains:
Customer and material info
Pricing conditions
Delivery dates and quantities
Shipping info
Billing Info
Inventory sourcing in SAP is taken care by
Availability check
Shipping in SAP supports
Outbound delivery creation
Picking
Packing
Post Goods Issue
Billing in SAP supports
Creating invoices for products and services
Creating credit and debit memo
Cancel previously posted billing documents
Automatically transferring billing documents to accounting
When a billing document is created for a sales order we
Credit the sales revenue account
Debit the customer receivables account
Sales Document
A sales document is grouped into three structures
Header
Item
Schedule Line
Outbound delivery
A delivery document is grouped into two structures
Header
Item
Several orders can be grouped into same outbound delivery if they have same
Shipping point
Delivery date
Ship-to- address
Picking
A transfer order is created for an outbound delivery
A transfer order is created for a warehouse number
Post Goods Issue
When PGI is done the system
Updates the quantity in inventory management and delivery requirements in materials planning
Generates additional documents for accounting
Adds the delivery to the billing due list
Updates status in sales documents
Billing
We can group deliveries into single billing document if the deliveries have same
Billing date
Payer
Destination Country
The effects of billing are
Debit on the customer receivables account and credit on sales revenue account is created
Sales information system
Sales statistics is updated
Master data in SAP
SAP SD has got the following main masters:
Customer master
Material master
Condition master
Output master
Customer material information master
Customer master
General Data Sales Area Data Company Code data
Tab pages Tab pages Tab pages
Address Order Accounting
Control data Shipping Payment
Payment terms Billing Correspondence
Marketing Partner functions Insurance
Unloading points
Export data
Contact persons
The chart above shows detail on three main areas of customer master and the tab pages found under each area.
Material Master is maintained in different views and important views of sales and distribution are
Basic data 1
Sales Org 1
Sales Org 2
Sales : Gen/Plant
Foreign Trade
Sales text
Sales document in Sales and distribution mainly controls:
Number range
Item No increment
Reference mandatory
Item division
Read info record
Document pricing procedure
Incomplete messages
Alternative sales documents
Delivery block
Billing block
Immediate delivery
Delivery type
Billing type
Proposed delivery date
Lead time for delivery
Proposed pricing date
Plant determination in Sales and distribution:
To determine the plant in an order the system checks the master in the following order:
a) Customer material info. record of the sold-to party
b) Customer master record of the ship-to-party
c) Material master record of the material
Shipping point determination
The following rule is used in determining shipping point in a sales order :
Plant + Shipping condition (Sold-to-Party) + Loading group Shipping point
Maintained in Material master Gen: Plant data
Route determination
Route determined using the following rule in Sales and Distribution (SAP)
Departure Zone of Shipping Point
+
Shipping condition (Sold-to-Party)
+
Transportation Group (Material master)
+
Transportation Zone (Ship-to-Party)
Route
Delivery scheduling:
As name denotes delivery scheduling is scheduling delivery for an order and it carries the following important dates:
Material availability date
Transportation planning date
Loading date
Goods Issue date
Delivery date
Availability Check in SAP:
Availability check is carried out at item level for a plant
Availability check is done on the material availability date
If material availability date is in the past the forward scheduling is done, if not backward scheduling is done.
Item category determination in the order:
Item category denotes the category to which the item belongs and the following rule is used for determination of item category. Item category controls the way in which item behaves in a sales document.
Sales document type
+
Item category group (Material master)
+
Item usage
+
Item category of higher level item
Item category of the item
Item category in a sales document mainly controls the following
Relevance for billing of an item
Billing block
Pricing relevance
Business data relevance item
Schedule line allowed
Item relevant for delivery
Returns
Determine cost
Credit active
Incompletion procedure
Partner determination procedure
Structure scope (relevant for bill of material explosion)
Value contract material
Contract release control
Schedule line category:
Every item which has a delivery will have a schedule line and the schedule line category is determined with the following rule:
Item category + MRP type(Material Master) Schedule line category
Schedule line category mainly controls:
Delivery Block
Movement type
Item relevant for delivery
Req/Assembly
Availability
Product Allocation
Copy Control:
Copy control is normally set for
Header
Item
Schedule line levels
To control copying procedure we have
Data transfer routines
Copying requirements
Switches
Pricing Procedure determination:
Pricing is an important component in SAP-SD. Once an order is entered taking into consideration some major factors, the pricing procedure for the particular order is determined.
The major factors taken into consideration for pricing procedure determination is:
Sales area
+
Customer Pricing procedure(Customer Master Sales area data)
+
Document Pricing Procedure(Sales Document Type)
Pricing Procedure
What are the components of pricing procedure?
How is that a person should work on Pricing Procedure?
To start with first
Define a Condition table:
What is a condition table?
A table where the key fields are data combinations for which messages are triggered (and offered for processing).
For each data combination, there is a condition record in the table. The data part contains the actual message.
As mentioned above a condition table is a table which carries key fields for picking up the prices.
Define Access Sequences
The access sequence is a search strategy which the SAP System uses to search for condition records valid for a condition type.
For example, you can define for a price that the SAP System first searches for a customer-specific price and then for a price list price.
Recommendation
If you define your own access sequences, the key should start with the letter Z since SAP reserves this letter for the standard system.
Do not change access sequences contained in the standard SAP R/3 System.
Actions
1. Check to what extent you can use the access sequences contained in the standard SAP R/3 System.
2. Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key which may have up to 4 digits and a textual description.
3. Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. With the sequence, you define the priority of the accesses. You can display combinations of key fields using possible entries.
4. Generating the accesses is no longer necessary as of 3.0, as this is carried out automatically. You can generate the accesses manually, if required, by choosing "Utilities".
Example
In pricing, you use a customer-material discount. The condition records you create are based on customer data from the document header and material data from each document item. The discount is only valid for 2% of your customers, however. Normally, this would mean that the system would needlessly search through every available item for 98% of your customers. In this case, pre step would improve system performance.
Define Condition Type
A characteristic of a condition. For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Price elements are represented in the SAP system by condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.
You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.
You specify an access sequence in every condition type. Thus, you define which fields the SAP system checks when searching for a valid condition record.
Note
The pricing procedure groups all condition types together which the SAP system is to automatically take into account during pricing for a business transaction (see the section "Define and assign pricing procedures").
Remember that you can only specify manually in a document those condition types which are contained in the pricing procedure.
You can change the outcome of pricing in the sales document manually. You can limit options for changing a condition type in this IMG step.
Recommendation
If you define your own condition types, the key should start with the letter Z since SAP reserves these letters for that purpose in the standard system.
Do not change the condition types which are contained in the standard SAP R/3 System.
Actions
1. Check to what extent you can use the condition types contained in the standard SAP R/3 System.
2. Create new condition types by copying a similar conditions type and changing it according to your requirements. One reason for creating a new condition type is you may require a calculation rule for a discount which is not available in the standard system.
Specify an alphanumeric key which can have up to 4 digits, and a textual description.
Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.
3. Maintain the detail screen of the condition type.
You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.
In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.
Define Pricing Procedures
The pricing procedure defines the conditions permitted for a document and the sequence in which the system takes these conditions into account during pricing.
A standard pricing procedure is defined in the standard SAP system. It contains conditions most commonly used. These include material prices, discounts, and surcharges, such as freight, or tax.
SAP Recommendation
Define your own pricing procedures which contain only those condition types which you use. Otherwise, the system makes un neccessary accesses to conditions.
Do not change the pricing procedures contained in the standard SAP R/3 System.
Actions
1. Create new pricing procedures by copying a similar pricing procedure.
o Specify a key with up to 6 characters and a description.
o For a procedure, specify the condition types in the sequence of their usage.
Maintain the lines of the pricing procedure
2. Afterwards define the customer determination procedures for determining the procedure.
3. Define the document pricing procedures for determining the procedure.
4. Assign the procedure to the sales document types and billing types.
5. To determine the procedure, define the allowed combinations of:
o Sales area
o Customer pricing procedure
o Document pricing procedure
o Pricing procedure
Shipping:
The basis for shipping is delivery.
Delivery document controls the following in deliveries
Number range
Item no increment
Storage location rule
Route determination
Text determination
Delivery split
Gen. packing material / item
Order required
Delivery item category controls:
Check min delivery
Availability check
Relevant for picking
Storage location required
Determine storage location
Automatic batch determination
Text determination procedure
Billing:
Billing is the last phase in the SD process .Billing is the phase where the major integration of SD and FI Module happens.
Billing document has got the following structure:
Header
Item
Billing documents mainly control:
No. range
Posting block (Controls posting to accounting)
Relevant for rebate
Account determination procedure
Account determination recon account
Account determination pay.cards
Output determination procedure
Account Determination in SAP
Account determination in SAP-SD happens with the following rule
Sales Organization
Chart of Accounts
Account assignment group Customer
Account assignment group-Material
Account Key
G/L account on which the postings has to happen.
CHeers!!! -
Automated Material Variant Creation
Is there an automated way to create material variants once a configuration is entered on a sales order, if one does not already exist?
Take an example, I have configurable material ComputerA which is a laptop computer. Say there are two possible configurations, 2GB of memory or 4GB of memory. Let's say that I have a material variant already for the 2GB configuration, and say that I called it ComputerA_2GB. If I were to create a sales order for ComputerA and configure it with 2GB of memory, then I could have my item category set to swap in the the material variant ComputerA_2GB automatically.
Now assume that I create an order for ComputerA but configure it with 4GB of memory. I have not previously created a material variant for this. Is there a way to have ECC dynamically create that material variant and swap it into my line? So the process would be: create line item for configured material, if material variant exists, swap in, if material variant does not exist, create the material master for the variant and then swap that material in. Is there any way to do this without custom code?Hi,
You can decide whether it is mandatory to assign a value to a characteristic on the basis of transaction code.
You must use [selection condition|http://help.sap.com/saphelp_erp60/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm] which calls the [user-defined function|http://help.sap.com/saphelp_erp60/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm]. In function you need to analyze sy-tcode and raise the predefined exception FAIL for those when you don't want to assign a value to a characteristic (e.g. mm01, mm02). Contact your ABAP team to create such a function.
Don't tick the characteristic as required entry in class definition but assign this selection condition to this characteristic in class.
Regards,
Alexander -
Hi guru's
I created varaints for selection screen (FBL5N) customer line items. My problem is tht i want these selection varaint to be come default depanding on specific user...Please tell me is it possible ??
Please help and if possible please let me know !!
Many thanks in advance..sure points
Regards
Inderdear friend
please try out with the following
VARIANT CONFIGURATIONS:
Slide 1: VARIANT CONFIGURATION OVERVIEW Prepared by Arun prasad C R *Please place your comments
Slide 2: Variant Configuration Introduction: Variant Configuration is useful if you have a large number of combination of parts that go into a product. It means different permutations and combinations of the parts for same material. If you maintain a unique material code for each possible combination of parts, you require a large number of material numbers. Usually involves Make to Order Production Process Variant Configuration Examples: A customer ordering a computer can choose different combinations of monitor, CPU, keyboard. A customer ordering a car can choose different combinations of accessories and color. In a business involving steel manufacturing, the customer may order steel involving different physical properties like tensile strength, diameter. Source: SAP
Slide 3: Industries for Configurable Products Variant Configuration Source: SAP
Slide 4: Cross Module Integration Variant configuration is integrated with the following applications: CA Classification LO Material Master PP Bill of Material PP Routings PP Material Requirements Planning (MRP) PP Production Orders PPPI Master Recipes Variant Configuration CO Costing SD Sales SD Conditions MM Purchasing Source: SAP
Slide 5: Overview of Terms Variant Configuration Source: SAP
Slide 6: Overview of Terms A configurable material has a special bill of material called the Super BOM in which all possible combinations are stored. The product is configured in the sales order by choosing the required Characteristic Values. The requirements are passed on Production Planning. On Explosion of the Bill of Material, the system selects the components assigned to the characteristics values in the order. Variant Configuration After production, the material is assigned as sales order stock for delivery to customer. Source: SAP
Slide 7: Sales Order Processing
Slide 8: IDES Demo Process Steps to be used in the demo: Creating a Sales Order Checking Requirements Using MRP Requirements Planning Converting the Planned Order into a Production Order Confirming the Production Order Checking the Production Order Settlement Variant Configuration Creating a Delivery Creating a Billing Document Source: SAP
Slide 9: Enterprise Structure used for demo Company Code 1000 Sales Org 100 Distribution Channel 12 Variant Configuration Division 00 Plant 1000 Storage Location 0001 Shipping Point 1000 Source: SAP
Slide 10: MTO Process Overview Make-To-Order Production With a Configurable Product: In this process, you create a sales order in SD and transfer the requirements to PP. The requirements are checked using MRP, before a production order is generated. This production order is created in PP. Shipping and billing both occur in SD. Finally, you check the costs and revenues in CO. Variant Configuration Source: SDN
Slide 11: Creating a Sales Order (T Code :VA01) After entering the sales data, a configuration screen pops up. Configure the material by selecting the characteristics. Note that the value of Variant Conditions changes as per selection. Variant Configuration Source: SAP
Slide 12: Creating a Sales Order (VA01) The system allows analysis of Object Dependencies and Variant Conditions. Item Category determined in Sales Order is TAC. Note the Material Availability Date and save the sales order (for test11048 and 11059). Variant Configuration Source: SAP
Slide 13: Configuration for VC
Slide 14: Configuration Details: Material Type OMS2: In definition of KMAT Material Type, indicator Material is Configurable is set Other material types like FERT (Finished Product) can also be used if the indicator is set in material master Variant Configuration Source: SAP
Slide 15: Configuration Details: Item Category in sales order VOV4: Item Category determination is set to determine item category TAC Variant Configuration VOV8: Item Category TAC Source: SAP
Slide 16: Configuration Details: Condition type for Pricing Condition types VA00 and VA01 (%) are available in Standard SAP for Variant Pricing Variant Configuration Source: SAP
Slide 17: Configuration Details: Requirement type KEK The requirement class controls the MRP and the requirements consumption strategy as well as the relevancy for planning, settlement profile for costing. Requirements type KEK is determined for strategy group 25 and also for item category TAC. Variant Configuration Source: SAP
Slide 18: Classification System: Characteristics Mayback 57 S Engine Color Rear wheel Seat Exhaust Antitheft device Variant Configuration Other Options Source: SAP
Slide 19: Classification System: Characteristics Variant Configuration Source: SAP
Slide 20: Classification System: Characteristics Variant Configuration Source: SAP
Slide 21: Classification System: Characteristics CT04: Create characteristics Data type can be CHAR, NUM, DATE, TIME, CURR Variant Configuration List of values and default value for characteristics can be stored in Value tab. Source: SAP
Slide 22: Reference Characteristics Reference characteristics are characteristics that refer to table fields. Variant Configuration Tables / Structures whose filed values can be changed by dependencies: SDCOM - Communication between SD and Variant Configuration VCSD_UPDATE - Table for Updating Sales Documents from the Configuration MMCOM, STPO, PLPO, PLFH, PLFL Tables / Structures whose filed values can be read by dependencies: VBAK, VBAP, VBKD, VBPA_AG, VBPA_WE, VBPA_RE, VBPA_RG VEDA, MAEPV, MAAPV Source: SAP
Slide 23: Classification System: Characteristics CT04: Create characteristics Object dependencies like pre conditions, selection condition, action, procedures can be created for characteristics Object dependencies like pre conditions, action, procedure can be created for characteristic values Variant Configuration Source: SAP
Slide 24: Classification System: Class CL01 /CL02: Create class under class type 300 for Variants Variant Configuration Assign the characteristics to the class. During Material Master creation for Super BoM, this class will be used in the Classification view. Source: SAP
Slide 25: Material Master of Super BoM (MM02) Basic Data 2 Screen: Set Material is Configurable Indicator To determine item category TAC in sales order, maintain a suitable item category group such as 0002 MRP 2 View: Procurement type E: In house Production MRP 3 View: Strategy Grp. 25: Make-to-order for configurable used for demo MRP3 View: Availability Check 02: Individual Requirement Classification view: Attach the variant class Variant Configuration Source: SAP
Slide 26: Bill of Materials (CS01 / CS02 / CS03) Variant Configuration Source: SAP
Slide 27: Object Dependency in BoM (CS02) Components in Production Order can be selected using Object Dependency type Selection Condition Variant Configuration Source: SAP
Slide 28: Routings (CA02) Operations in Production Order can be selected using Object Dependency type Selection Condition Variant Configuration Source: SAP
Slide 29: Configuration Profile: Process Planned/production Order; explosion indicator None (others Single level or Multiple level) The material has a BOM that is not relevant to the sales order. Only the characteristics that describe the variant are required. The components are determined later during material requirements planning or production, so there is no need to explode the BOM in the sales order. Sales order (SET): See next slide also In the sales order, sales-relevant components are shown as sub-items of the header material. Requirements are transferred and pricing is calculated at component level, not at header material level. Order BOM You create a sales order. In order BoM, you can insert extra items or delete items manually. The Variant Configuration changed BOM is stored as a separate BOM for the sales order. Source: SAP CU42
Slide 30: Configuration Profile: SET This processing form means that in the sales order you can only process sales-relevant BOM items. You can use the item category group like 0004 at configurable material level to define that requirements transfer and pricing are at component level. For example, a PC is made up of the components monitor, CPU, keyboard, and printer. These components are all salable materials that are manufactured separately. In the sales order, you want to see the individual components that make up the computer as order items, as well as the whole computer. In the sales order, these products are grouped together in a SET. For this reason, this type of processing is also referred to as set processing. Variant Configuration Source: SAP
Slide 31: Configuration Profile: Dependencies Dependencies like Actions and Procedure can be assigned to Configuration Profile. Variant Configuration Source: SAP
Slide 32: Configuration Profile: Variant Table Tables are used to store combinations of values for different characteristics A table HD_1300_COLOR_PR is created in CU62 transaction. It has 2 fields: HD_COLOR (key field) and SURCHARGE. The selected characteristic will be transferred to HD_COLOR and surcharge to SURCHARGE2. The table contents are given below (see transaction CU60) Variant Configuration VK30: Has description entries for the surcharge column listed above VK12: Will pick up pricing value based on condition type VA00 Source: SAP
Slide 33: Pricing Check definition of characteristic SURCHARGE2 Additional data tab -> reference table and field Variant Configuration Simple method to achieve Variant Pricing is given below: Create multiple value characteristic SURCHARGE2 referring to SDCOM-VKOND. Put this characteristic in the class HD-000 which was used for the configurable material Now go to CT04 and change the Characteristic HD_COLOR Go to values tab and select Red. Go to Extras-> Object Dependencies->Editor and then select Procedure. In front of 000010 Enter $self.surcharge2='HD-003_03'. Similarly Select Black to enter $self.surcharge2='HD-003_02. Same way 'HD-003_01 for Silver VK30: Has description entries for the surcharge column listed above VK12: Will pick up pricing value based on condition type VA00 Source: SAP
Slide 34: Pricing VK30: Maintain descriptions for variant price conditions (optional step; done while creating dependencies for surcharges; maintains consistencies of configuration) Variant Configuration VK11 / VK12: Maintain actual condition record for variant price surcharges Source: SAP
Slide 35: Pricing Factors Pricing factors can only be maintained on characteristic level. The syntax of pricing factors is as follows: $SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>) This expression contains the following information: The characteristic that refers to structure SDCOM, in which variant conditions are defined. The variant key used to infer the condition for a characteristic value. Variant Configuration The factor by which the surcharge increases. Source: SAP
Slide 36: Material Variant For variants that are required frequently, create material variants, which can be produced without a sales order and kept in stock. When a sales order is received, check whether the variant is in stock and deliver immediately. The material master record of a material variant is linked to the configurable material and configured using the characteristics of the configurable material. Variant Configuration Source: SAP
Slide 37: Material Variant in Sales Order On the value assignment screen, you can check whether the values assigned match the configuration of a material variant. Variant Configuration Source: SAP
Slide 38: Material Variant Replacement of configurable material by a material variant Variant Configuration Source: SAP
Slide 39: Material Variant Item category gets changed to TAN; Pricing will also change as per new MTS product. Variant Configuration Source: SAP
Slide 40: Summary of day 1 By now, you should be comfortable with the following topics: Explain what Variant Configuration is and its use in make to order scenario Using Variant Configuration during sales order processing Configuration details like item category and condition types Classification System - Characteristics and Classes Super BoM, Configuration Profile, Object Dependencies Pricing Surcharges in sales order processing Variant Configuration Using Material Variants for make to stock scenario Source: SAP
Slide 41: Day 2: Understanding Object Dependencies in detail
Slide 42: Dependency Types Variant Configuration Source: SAP
Slide 43: Pre Condition Variant Configuration Only if the model specified is racing, the bicycle can have 21 gears. 1. Create a precondition with the following source code: MODEL eq 'Racing' and Specified MODEL 2. Allocate the precondition to value 21 of characteristic GEARS Source: SAP
Slide 44: Selection Condition A selection condition is allocated to each component and each operation. This selection condition determines which components and operations are selected for a variant. Variant Configuration Source: SAP
Slide 45: Changing Master Data with Dependencies In variant configuration, you can use reference characteristics with dependencies to change field values of tables for bills of material (BOMs), task lists, and master recipes. Table names and fields are given below for reference. Table STPO field MENGE can be used to change component quantities of BoM. Table PLPOD field VGW01 can be used to change setup time of Operation. Variant Configuration Source: SAP
Slide 46: Procedures Procedures can set default values for a characteristic (can be overwritten by the user) Variant Configuration Source: SAP
Slide 47: Procedures Set default values: $SET_DEFAULT ($SELF, <characteristic>, <term>) For example: ( $SET_DEFAULT ($SELF, COLOR_CHAR, 'BLUE'), $SET_DEFAULT ($SELF, GLOSS_CHAR, 'NONE') ) IF $root.PC_CASING_CHAR = 'TOWER' Delete default values: $DEL_DEFAULT ($SELF, <characteristic>, <term>) Variant Configuration Produce a sum of the values for a characteristic in a multi-level configuration: $SUM_PARTS ($SELF, <characteristic>) It can be used to calculate the weight of components and transfer the same to structure VCSD_UPDATE, gross weight field BRGEW Add the components of a BOM together: $COUNT_PARTS (<$SELF>) Surcharge for variant conditions in Pricing: $SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>) Source: SAP
Slide 48: Constraints and Dependency Net The main purpose of a constraint is to monitor the consistency of a configuration. There are four sections in a constraint. 1. OBJECTS: Declaration of all classes and objects used. 2. CONDITION: Pre requisite for processing the constraint. 3. RESTRICTIONS: For interdependencies and consistency check; check and set values. 4. INFERENCES: Enter the characteristics for which characteristic values are to be inferred. Variant Configuration Constraints are grouped together in dependency nets. The dependency net can be allocated to a configuration profile. Example: The hard disk can only have the value 1620 for a tower, or 850 for a mini tower. OBJECTS: PC IS_A (300) PC RESTRICTIONS: PC.HARD_DISK = 1620 if PC.CASING = Tower, PC.HARD_DISK = 850 if PC.CASING = Mini tower. Source: SAP
Slide 49: Actions Actions can be used to infer values for characteristics. Actions can also be used to change field values in BOM items or operations in routings. Procedures can set default values for a characteristic, which can be overwritten by the user. The user cannot overwrite values that are set by an action. For new developments, use Procedures rather than Actions (to become obsolete) Variant Configuration Source: SAP
Slide 50: Object Variables used in Multi level configurations Variant Configuration Source: SAP
Slide 51: Allowed Dependency Types Preconditions are allowed for characteristics and characteristic values. Selection conditions are allowed for characteristics, BOM items, operations, and production resources/tools. Procedures & Actions are allowed for characteristics, characteristic values, BOM items, operations, and configuration profiles. Constraints can only be linked to a configuration profile via dependency nets. Variant Configuration Source: SAP
Slide 52: Processing Sequence for Dependencies Each time you enter a value for a characteristic on the value assignment screen and confirm the value, the system processes all the dependencies. The dependencies are processed in the following sequence: 1. All actions several times, until no more values can be inferred. 2. All procedures exactly once in the following sequence: a) Procedures for the configuration profile in the order you defined b) Procedures for characteristics Variant Configuration c) Procedures for characteristic values The procedures for each characteristic or value are processed in the order you defined. 3. Actions Values set by procedures can also trigger actions. For this reason, all actions are processed again. 4. Preconditions 5. Selection conditions for characteristics Constraints are processed in parallel with points 13, if all the objects in the OBJECTS section are present, and if all the conditions in the CONDITIONS section are fulfilled Source: SAP
Slide 53: Transfer to Production Planning (Demo)
Slide 54: 2. Checking Requirements Using MRP (T Code :MD04) Step1 to create sales order has already been discussed earlier. 2. Stock Requirements List: The sales order is displayed as a separate planning segment (sales order stock required on material availability date and sales order). Variant Configuration Source: SAP
Slide 55: 3. Requirements Planning (T Code :MD50) The sales order will now be converted into a planned order. Planned Orders represent the first step toward an actual production schedule for the Shop Floor. Variant Configuration Source: SAP
Slide 56: 4. Convert the Planned Order into a Production Order (MD04) Planned Orders are a result of MRP run and serve to provide an initial Production Schedule. Production Orders contain comprehensive information to support a shop floor schedule and provide a method to confirm operations performed. Production orders can be created with reference to a Planned Order. Variant Configuration Source: SAP
Slide 57: 4. Convert the Planned Order into a Production Order (MD04) Object Dependency: BoM Selection Condition ensures only necessary material components are taken. Variant Configuration Source: SAP
Slide 58: 4. Convert the Planned Order into a Production Order (MD04) Object Dependency: Routing Selection Condition ensures only necessary operations are taken. Variant Configuration Source: SAP
Slide 59: 4. Convert the Planned Order into a Production Order (MD04) Prior to release of order, it is not possible for anyone to enter confirmations for the operations in the order. Release the Order and Save it. Gantt chart. Graphic Display the operation scheduling overview, choose Goto Variant Configuration Source: SAP
Slide 60: 4. Convert the Planned Order into a Production Analysis Variant Costs Order (MD04) Display the planned costs, choose Goto Configuration Source: SAP
Slide 61: 5. Confirming Production Order (CO11N) Production Time Ticket Variant For Operation  Enter  Confirmation Control Configuration Source: SAP
Slide 62: 5. Confirming Production Order (CO11N) Back flushing (posting of an issue of components or material withdrawals) Storage of the finished product in the warehouse to sales order stock Goods Movements are posted (errors if any can be corrected in COGI) Actual costs are calculated Just in case, to close the order without yielding a product, perform Restrict Processing -> Technical Completion for Production Order in CO02. Variant Configuration Source: SAP
Slide 63: 5. Confirming Production Order (CO11N) Sample Material Document and FI document entries are shown below Variant Configuration Source: SAP
Slide 64: 6. Checking the Settlement of the Production Order  Settlement From the Production Control node, choose Period-End Closing Individual Processing (KO88) Perform order settlement to transfer the costs of the production order to sales order. Analyze the current cost situation for the Production Order Variant Configuration Source: SAP
Slide 65: 7. Creating a Delivery (VL10G for delivery due list, VL01N for single delivery) Assign a serial number to the material. Pick and post the goods issue. Movement type will be 601 E indicating delivery from sales order stock. Accounting document will be generated to capture the change in inventory. Variant Configuration Source: SAP
Slide 66: 8. Creating Billing Document (VF04/VF06 for due list, VF01 for single invoice) VF01: Create the invoice sample accounting entries (without tax) are shown below F-28: Receive the payment from the customer Variant Configuration Source: SAP
Slide 67: Other Information CRM: It is possible to have configurable products among your Online Store offerings using the IPC (Internet Pricing and Configurator). It allows customers to interactively choose product options via an easy-to-use interface. Customers can mix- and-match these options to build the exact product they wish to purchase. ECC 5.0: Single transaction PMEVC Modeling Environment for VC Variant Configuration Source: SAP
Slide 68: Summary By now, you should be comfortable with the object dependencies and the following topics: Pre conditions Selection conditions Procedures Actions Constraints and Dependency Net Variant Configuration Transfer of sales order requirements to PP Delivery from sales order stock Invoicing the customer Source: SAP
Slide 69: Variant Configuration
regards,
amlan -
Report designer - query alignment
Hi all,
In report designer I have 2 queries with a top 10 condition on a characteristic in the rows and 1 key figure in the column. The report designer shows these reports as dynamic sections.
Therefore I cannot place them horizontally next to each other, for layout purposes.
Does anyone know how I can achieve this?
thanksnot possible
-
what is the use of "selection condition" & "procedure" in Dependacy(transaction-CU01) of variant configurable material.
there are 4 types of dependencies:
1) selection
2) action
3)Procedure
4) precondition
1) Selection:
If a user select a particular characteristic value, then only the particular character is displayed
You can use selection conditions to ensure that all the objects relevant to a variant are selected:
Selection conditions determine which variants require a specific component or operation
Selection conditions determine when it is mandatory to assign a value to a characteristic
You can allocate selection conditions to the following objects:
Characteristics
BOM items
Operations in task lists
Sub-operations , seq. of operations, production resources/tools
Example: Selection Condition for a Characteristic
Requirement: For 3000cc engine, we must have to choose any color (mandatory) i.e. RED, WHITE etc.
Procedure
1. Create a Selection Condition
2. This Selection Condition has the following source code:
M_ZEN_ENG EQ 3000
3. Allocate the selection condition to characteristic M_ZEN_COL
Result
If you enter value 3000CC' for characteristic M_ZEN_ENG when you configure material M_CAR, you fulfill conditions:
The selection condition makes you assign a value to the characteristic.
If you do not assign a value to characteristic M_ZEN_COL, you automatically see the characteristic when you exit the configuration editor, so that you can assign a value.
You can only leave the configuration editor if you do one of the following:
Assign a value to the characteristic
Change the status of the configuration
Result: If u have not assign any value in the colour field, the system will not proceed further.
procedure:
Procedures are used to infer values for characteristic
You can assign procedures to the following objects:
The characteristic value that triggers the procedure
The characteristic that triggers the procedure
The configuration profile of the configurable object
Use
If you use a procedure to infer a value for a characteristic, you enter the variable $SELF before the characteristic.
The formula will be $self.M-zen_red = 'X'
Now pricing condition record at vk11 is maintained fro the variant X, not to the M-zen_red
Procedures can overwrite values that are set by other procedures.
Procedures are always used for pricing
I have here ecxplained the only two type of dependencies. If u need further clarifications, please post.
Hope it clears ur doubt.
Reward points if it is useful
Regards
Kaleeswaran B -
Condition type value updation using characteristic value in sales order
Hi Experts,
We are implementing SAP for one of our Spain client. In that one of the Legal requirements is, whenever they are selling the finished products to domestic customers who contain OIL as one of the component then, some additional cost needs to be calculated and collected from customer and which needs to be paid back to Spain Government every month on Region basis.
If OIL is not a component to produce the finished product then, not required to charge the customer additionally.
The OIL content used to produce every finished product will vary based on product characteristic value. Meaning, for some finished product the OIL used will be 2.2 KG and for some products it will be 3.5, 4.3 KG and etc.
Since various combinations of products are available for the client, during sales order creation we are planning to update some special characteristic which the data flow from u201CVariant Tableu201D. In the variant table we are going to maintain the OIL Quantity required making finished product.
But we are not sure how to activate a new condition type with the value fetched in the special characteristic. This new condition type needs to be activated based on this characteristic value and multiplied with total order quantity and price to charge from customer.
Example, the special characteristic fetched the value of 2.2 KG based on variant table. Total Order quantity is 10 PC and charge is 0.06 EURO per KG. in this case, (2.2 x 10 ) x 0.06 EURO = 1.32 EURO
I need the expert opinion how to activate the new condition type based on characteristic value and achieve the above requirement.
Thanks in advance.
Warm Regards,
VELHello,
I have replicated the whole requirememt in IDES and getting the price calculation as needed but the only issue with the Conversion factor for the condition type. Either you need to maintian the conv factor in material master or need to enter manually for the condition type in SO. Some how you have to maintain the conversion factor to calculate the price for the condition type in different unit.
For easy of understanding Lets make the whole requirement in 2 parts
Part - 1
Oil qty calculation. For convenience sake I have taken oil qty also in TO
1) Created a num char OIL_QTY1 with length 9 and decimal places 5 and UOM as TO
2) Created Variant table to infer the OIL qty in TO per piece of finished prod ( This oil qty data may be depends on various factors). For certain Finished products the oil qty may be 0 or blank
3) Created a REF char SO_QTY to pull the SO qty to configuration and add this char in class 300(Table:VBAP,Field :KWMENG)
4) Created another char SO_OIL_QTY (Num with length 9 and decimal places 5 and UOM as TO)
5) Created a PROCEDURE say PROC_SO_OIL_QTY with code
*$self.SO_OIL_QTY = $self.OIL_QTY1 * $self.SO_QTY*
6) Create another PROCEDURE as mentioned earlier with modified code
$SELF.A_VARCOND = 'TEST_001' if OIL_QTY1 specified,
$SET_PRICING_FACTOR ($SELF,A_VARCOND,'TEST_001', SO_OIL_QTY)
Note: Maintain proper seq of the procedures in profile. The Qty cal proc should be before the price related procedures.
PART-2
1) For the condition type maintained 60 EUR per TO (0.06 EUR per KG)
Now if you create SO for the Finished product of 10 PC
the Char values will be
OIL_QTY1 = 0.00022 TO (inferred from Variant table th proc)
SO_QTY = 10
SO_OIL_QTY = 0.0022 TO
Get into conditions tab
Here Condition type ZSIG will be displayed as error with Amount 60 EUR per TO and condition value will be blank. Just enter value 1 in the col NumC and CCon fields.
Now the Condition value will appear as 1.32 EUR.
Hope this gives some more clarity
Regards
Brahmaji D
Maybe you are looking for
-
I can not open itunes on my computer. It started when an upgrade appeared. Now I get a message that states This application has failed to start because MSVCR80.dll was not found. Re-installing the application may fix this problem. I tried to reinsall
-
Bug(?) Dropping a snippet which browses for SubVIs in not undo-able
Here is one that fortunately hadn't struck me yet, but is a bit of a pain. Situation: Interesting snippet on forum page. User has disdain for most MSoft products so refuses to use IE unless there is no other option and iPhone is discharged. Arrang
-
Anyone know the name of the small coax used for antennas on most WRT series routers?
I am looking for more information on the coax cable used on most WRT series routers. It has a clear jacket, approximately 1/8" thick. Only way to see is by opening your router, or looking inside the rubber part of antenna. I would appreciate any ex
-
Database Replication never fall back over MAPI Network in case of dedicate network outage
Hi All, Exchange 2010 SP3 RU4 and every time I have an outage on dedicated network the replication stop working and all Database looses sync (content Index) and I have to manually resync all as suggested on http://exchangeserverpro.com/cannot-activat
-
Why does my video's always stop and start?
Can't listen or watch a movie because it keeps stopping & starting. Hoping to find a solution.