Hai indira,
check it out
 Compounding is used when the individual values of a char are not complete (in the business sense) all by themselves. eg. CostCenter is compounded to Controlling Area. This is required because the same costcenter value (eg C1001) maybe present in more than one Co_Area with different meaning. So, by compounding the values become self-explanatory as Co_Area1 / C1001 and Co_Area2 / C1001.
 Another example of compounding is Source System compounding. Thsi is used where you have multiple source systems and the data is not unique for each. eg. Mat1 from Source system 1 and source system 2 may refer to different materials, so by compounding 0SOURSYSTEM to 0MATERIAL, this ambiguity is taken care of.
Superior InfoObject (compound)
In this field, the higher-level InfoObject for a compounded characteristic appeared - meaning the InfoObjects, to which the characteristic is compounded.
By using compound InfoObjects, you can model the dependencies between InfoObjects. You can compound InfoObjects to map the data structure of a source system.
Example
you can only evaluate the characteristic 'storage location' in conjunction with a 'plant'. In this case, you define a characteristic compound 'storage location' to 'plant'.
An exceptional case for compounding is the option to compound characteristics to the source system ID. This can be necessary if there are identical characteristic values for the same characteristic in different source systems, that describe various objects. You can switch this compound on and off via the pushbutton 'local source system on/off', that is located using the list of the higher-level InfoObjects.
Note
Through the extensive use of compounded InfoObjects, in particular if you include a large number of InfoObjects in a compound, the performance can be affected. Try not to represent hierarchical relationships by compounds, rather use hierarchies for this instead.
Typically in a organization the employee id are allocated in serial like say 10001, 10002 and so on. Lets your Organization comes out with a new employee id scheme where the employee id for each location would start with 101. So the employee id starting for india would be india/101 and for US would be US/101. Now note that the employee india/101 and US/101 are different. Now if someone has to contact employee 101 he needs to know the location without which he cannot uniquely identify the employee. Hence in this case location is the compunding attribute.
compounding means to enhance the key of the master data tables by the compounding objects.
example:0customer,
key of the p-table is customer.
0cust_sales,
key of the p-table is sales_org, distr_chan, division and cust_sales whereas the first three object are compounding objects of cust_sales.
Additionally check the s- and the p-tables.
here is the scenario that can help u understand better
for example there r plants numbering from 1 to 10
and each plant has storage locations.
and for the plant 1 the storage locations r from 101 to 110.
and for the plant 2 the storage locations r from 101 to 110.
and so on
so here the storage locations r not unique .
so we make the plant and storage location as compounding infoobjects.
then the combination of these plant and storage location is unique
like 1101,1102 1103..... for plant1 storage locations,
and 2101,2102 .... plant 2 storage locations.
Asign points if helpfull............
regards
KP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.