Unequal Distribution of Objects

We are trying to use Coherence for caching large amount of business data (500GB). We are using 64 cache-servers running on 8 Linux boxes, and have defined multiple distributed caches. When we try to find the number of instances of each object in various cache-server nodes using JMX, we notice that while most of the nodes have a fair number of objects (3600), about 8 of them have very few objects (700). These nodes contains very small number of objects for every cache that we have in the cluster. Why is it so? Our understanding is that Coherence distributes data evenly. We are using the default Unit-calculator.
Also, we are not able to find the which node is using which JMX port number. When we see that Node no 6 is caching very few objects, we want to examine its memory, but we can't figure which instance of cache-server is really Node 6. Fact that we are running 8 cache-servers per box makes it more difficult.

user5606651 wrote:
We are trying to use Coherence for caching large amount of business data (500GB). We are using 64 cache-servers running on 8 Linux boxes, and have defined multiple distributed caches. When we try to find the number of instances of each object in various cache-server nodes using JMX, we notice that while most of the nodes have a fair number of objects (3600), about 8 of them have very few objects (700). These nodes contains very small number of objects for every cache that we have in the cluster. Why is it so? Our understanding is that Coherence distributes data evenly. As Paul mentioned, Coherence does not distributed data evenly. It distributes partitions evenly.
The distribution of data (i.e. keys) to partition depends on your cache key objects, usually the binary form, but you can influence this by providing a KeyPartitioningStrategy where you can override the placement of a key to a partition. The algorithm for coming up with a partition id in KeyPartitioningStrategy for a key must take only the serializable state of the key into account.
Overriding this class would help altering the way your objects are distributed into partitions, as likely the distribution of your keys to partitions is not even.
What class do you actually use as cache key?
We are using the default Unit-calculator.
AFAIK, unit calculators have nothing to do with partition distribution. Coherence assumes that the distribution of entries to partitions comes up with evenly distributed partition sizes.
Also, we are not able to find the which node is using which JMX port number. When we see that Node no 6 is caching very few objects, we want to examine its memory, but we can't figure which instance of cache-server is really Node 6. Fact that we are running 8 cache-servers per box makes it more difficult.You can find out the process id of all nodes if you look at the Members attribute of the Coherence/Cluster MBean (it is referred to as process=... in the Member description). Starting from the process id you can find out what ports are used by which process by using netstat or lsof.
Best regards,
Robert

Similar Messages

Creation of Disctribution Model view using Distribution using object classe

Hi All ,
Can anybody tell me how to create distribution model through Distribution using object classes option in SALE transaction(Path : SALE - > Modelling and implementing Business processes - > master data Distribution - > Distribution using object classes).What is the difference between normal distribution model creation through BD64 and creating in the above way?
Please help me its urgent.Thanks in advance.
Regards,
Rakesh.

Hi All ,
Can anybody tell me how to create distribution model through Distribution using object classes option in SALE transaction(Path : SALE - > Modelling and implementing Business processes - > master data Distribution - > Distribution using object classes).What is the difference between normal distribution model creation through BD64 and creating in the above way?
Please help me its urgent.Thanks in advance.
Regards,
Rakesh.

Cache distribution - Java object cache

Hi.
I'm trying to use Oracle Java Object Cache (cache.jar), the one included in the 9iAS 9.0.3.
Everything works fine but the cache distribution between different JVM:s.
Anyone got this to work?
Regards
Jesper
package test;
import oracle.ias.cache.*;
* Singleton Cache class.
public class Cache {
     /** The singleton instance of the object. */
     private static Cache instance = null;
     /** The root region. */
     private final static String APP_NAME = "Test";
     * Protected constructor - Use <code>getInstance()</code>.
     * @throws Exception if error
     protected Cache() throws Exception {
          CacheAccess.defineRegion(APP_NAME);
     * Gets the singleton instance.
     * @return The instance of the Cache object.
     public static Cache getInstance() throws Exception {
          if (instance==null) {
               createInstance();
          return instance;
     * Creates the singleton instance in a thread-safe manner.
     synchronized private static void createInstance() throws Exception {
          if (instance==null) {
               instance = new Cache();
     * Put an object on the cache.
     * @param name The object name
     * @param subRegion The sub region
     * @param object The object to cache
     * @throws Exception if error
     public static void put(String name, String subRegion, Object object) throws Exception {
          CacheAccess appAcc = null;
          CacheAccess subAcc = null;
          try {
               appAcc = CacheAccess.getAccess(APP_NAME);
               // Create a group
               Attributes a = new Attributes();
               a.setFlags(Attributes.DISTRIBUTE);
               appAcc.defineSubRegion(subRegion, a);
               subAcc = appAcc.getSubRegion(subRegion);
               if (!subAcc.isPresent(name)) {
                    subAcc.put(name, a, object);
               } else {
                    subAcc.replace(name, object);
          } catch (CacheException ex){
               // handle exception
               System.out.println(ex.toString());
          } finally {
               if (subAcc != null) {
                    subAcc.close();
               if (appAcc != null) {
                    appAcc.close();
     * Gets a cached object from the specified sub region
     * @param name The object name
     * @param subRegion The sub region
     * @return The cached object
     * @throws Exception if requested object not in cache
     public static Object get(String name, String subRegion) throws Exception {
          CacheAccess appAcc = null;
          CacheAccess subAcc = null;
          Object result = null;
          try {
               appAcc = CacheAccess.getAccess(APP_NAME);
               subAcc = appAcc.getSubRegion(subRegion);
               // define an object and set its attributes
               result = (Object)subAcc.get(name);
          } catch (CacheException ex){
               // handle exception
               throw new Exception("Object '" + name + "' not in cache region '" + subAcc.getRegionName() + "'.");
          } finally {
               if (subAcc != null) {
                    subAcc.close();
               if (appAcc != null) {
                    appAcc.close();
          return result;
     * Invalidates all objects in all regions
     public static void invalidateAll() throws Exception {
          CacheAccess appAcc = CacheAccess.getAccess(APP_NAME);
          appAcc.invalidate(); // invalidate all objects
          appAcc.close(); // close the CacheAccess access
     // Main method for testing purposes.
     public static void main(String[] args) throws Exception {
          try {
               System.out.println(">> Caching object OBJ1 into region TEST1.");
               Cache.getInstance().put("OBJ1", "TEST1", "Object cached in TEST1.");
               System.out.println(">> Getting OBJ1 from cache region TEST1.");
               System.out.println(Cache.getInstance().get("OBJ1", "TEST1"));
          } catch (Exception ex) {
               System.out.println(ex.getMessage());
Contents of JAVACACHE.PROPERTIES:
# discoveryAddress is a list of cache servers and ports
discoveryAddress = host1.myserver.com:12345,host2.myserver.com:12345
logFileName = c:\javacache.log
logSeverity = DEBUG
distribute = true

I have same problem
Exist some reason?
I'm testing Cache with isDistributed() method and I still got false!
Thanx

Uneven Distribution of Objects Around a Circle

Hi,
I'm trying to figure out a way to distribute objects in a circle but make them uneven. Well, "uneven" in that the objects begin to space out more as they approach the top of the circle like the sample shown. I know how to distribute object evenly but I'm stumped on how to make this happen. Any ideas as to how this can be achieved? Blend and Spine? Transforms?

Maintaining Alignment/Distribution of Objects During Browser Scaling

Hello All,
I have been searching the forum for about two hours trying to
find the right code.
Basically, I want to have a site where the background scales
to the browser window proportionately and the buttons re-align
themselves around the perimeter. The content will be centered in
the middle of the browser.
I found the perfect piece of code for the background scaling.
What I want to have is a minimum flash size, say 500px. If
the browser window is scaled smaller then 500px, scroll bars
appear. There will be buttons along the top, bottom, and sides of
the stage. When the browser window is enlarged, the stage expands
with the buttons staying the same size and distribution between
each button on the stage is consistent. (more space between the
buttons when stage is expanded.) Also, the buttons will stay
position to the top, bottom, and sides of the browser.
I tried mixing other code from the forum with this scale code
below with bad results.
Any help would be great.
Thanks
Jessy

this works:
you can view it here http://cybermountainwebservices.com/fullBrowser/FullBrowserAS3.html
stage.align = StageAlign.TOP_LEFT;
stage.scaleMode = StageScaleMode.NO_SCALE;
var bmp:Tile = new Tile(35, 35);
var tile:BitmapData = new BitmapData(35, 35);
tile.draw(bmp);
shelter.x = stage.stageWidth /2;
shelter.y = stage.stageHeight /2;
function fillBG(evt:Event = null):void {
graphics.beginBitmapFill(tile);
graphics.moveTo(0, 0);
graphics.lineTo(stage.stageWidth, 0);
graphics.lineTo(stage.stageWidth, stage.stageHeight);
graphics.lineTo(0, stage.stageHeight);
graphics.lineTo(0, 0);
graphics.endFill();
shelter.x = stage.stageWidth /2;
shelter.y = stage.stageHeight /2;
fillBG();
stage.addEventListener(Event.RESIZE, fillBG);
in this case the fill is with a 35pxl x 35pxl gif file but you could just as easily use a color the item called shelter is the name of the jpg in the center.
when you do this be sure in your publish settings to set dimension to percent 100 x 100 if you cont want a border or scrollbars around the outside be sure to set this css rule in your html body {margin:0; padding:0; overflow:auto}

How would you do uneven distribution of objects?

I whish the Transform Each... tool had a feature allowing specified number of copies along with the Skew feature that is available in the Grid tool.
So far I've been doing this by using the Grid tool as a reference and manually arranging objects which is a big pain in the a**
Anyone knows a better way?
or another vector program, plug in, script, etc?
This is a piece of cake in most 3D programs which is a much more complex task for the 3D programmers and I can't believe that Illustrator still doesn't have such essential tool.

Emil,
Any brush approach wil lead to trouble in a case like this because they will either give you misalignment with the path or distortion.
A blend approach may do it.
In addition to what Steve just said (I had to leave while writing the following, and saw his new post #13):
Your grid approach (upper row) seems to lead to a strange decrease pattern (reduction in distance between pairs of vertical stroked paths),
The first decrease being 3.449 pt, the next three being 2.821, 2.823, and 2.822 (constant), then 3.507 and back to 2.822 again
The last five decreases being 0.314, 0.626, 0.631, 0.338, and 0.002.
Your blend approach (lower row) seems quite consistent with a decrease pattern (reduction in distance between (outer bounds of) pairs of squares) that has a constantly decreasing decrease (the change in the reduction to the next pair) of about 0.053 (with slight variations between 0.049 and 0.057, and leading to an intriguing end game where the reduction is actually increased.
The blend made by Steve seems to lead to an exponentially decreasing decrease (something like 1/1.1875, corresponding to an increasing increase from right to left by the factor 1.1875). I am afraid we should have to ask Teri what the exact relation between handle lengths and nature of decreasing decrease is; I believe it is somewhat complex with (at least) two different handle lengths.
As it appears, I believe your grid approach is less useful than it seems.
Depending on the desired nature of the decrease/increase (depending on which end you start with) you may do it in a few different ways, including the blends mentioned above.
If you wish to really control the decrease/increase, I am afraid you will have to use a more laborious blend approach, a bit similar to the one in this thread with a fake blend:
http://forums.adobe.com/thread/808345?tstart=30
Possible approach:
Using a blend to fill a full circle, be aware that you need to cut the circle where you wish the blend to start/stop, and that the first/last objects are on top of each other so you need one extra.
Preparing the contents of the fake blend:
If you want a specific exponentially decreasing/increasing decrease/increase, you may, using the Alt/Option+O+T+M shortcut (or something similar) to copy:
1) Create the basic object and the first copy, inserting the first distance;
2) For the next distance insert the percentage distance (110% for a 10% increasing increase, or similar) and copy the percentage distance;
3) For the following distances, until you have them all, insert the copied percentage distance instead of the current value (in this case you just get 110%);
If you want a specific constantly decreasing/increasing decrease/increase, you may, using the Alt/Option+O+T+M shortcut (or something similar) to copy:
1) Create the basic object and the first copy, inserting the first distance;
2) For the next distance add/subtract the constant change of distance (+2pt for a 2pt increasing increase, or similar) and copy the constant change of distance;
3) For the following distances, until you have them all, insert the constant change of distance after the current value (in this case you get the current value +2pt);
To create the fake blend, you may:
4) Object>Blend>Options set Spacing to Specified Steps with the value 1 and Orientation to Align to Path;
5) Select all objects and Object>Blend>Make, now you have surplus objects in between the desired objects, see 8).
To finish the work, you may:
6) Apply the blend to the (cut) circle;
7) Object>Blend>Expand;
8) Delete the surplus objects.
I hope this was not too easy (to understand).

Distribution Points properties changing permissions

Hi everybody!
How can we use RBA to lock down branch's admins DP properties changing permission....?
Branch admin's could change PXE properties and etc.....Could we let them work with DP object only in read mode?
In their role permission properties there are only "Read" and "Copy to DP" mark above "Distribution Point" object, but they still could change assigned to their scope DP's properties((

You've got to remove the Modify permission on the Site
object. In case you do want them to be able to modify other site settings, you can also create an additional scope configured to the specific distribution point. Then combine that scope and the role with less permissions on the site object together
on the administrative user and you achieved your goal.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

"Active Directory operation failed on DC " when assigning Send As permissions on a distribution group

I'm trying to give a mailbox user Send As right for a distribution group. But the cmdlet comes back with this:
Get-DistributionGroup MyGroup | Add-ADPermission -user albert -ExtendedRights Send-As
Active Directory operation failed on <DC fqdn>. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-03151E07, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
+ CategoryInfo : WriteError: (0:Int32) [Add-ADPermission], ADOperationException
+ FullyQualifiedErrorId : FE24751F,Microsoft.Exchange.Management.RecipientTasks.AddADPermission
What could be the problem, considering the items below :
- inheritance is not broken to the level of the distribution group object
- the account used to run the cmdlet is a member of the Organization Management group
- creating a new distribution group in the same OU and running the command works as expected; checking the permission for this group against MyGroup (using Get-DistributionGroup testgroup | Get-ADPermission | Sort-Object User,AccessRights | ft user,accessrights,extendedrights,properties)
shows no differences.
- adding the permission using ADUC results in the user being able to Send As the group, however I'm trying to find out the root cause of the Powershell cmdlet execution problem
- there is no Deny permission on the group's ACL
- the group didn't have the "Hide Membership" feature of Exchange 2003 applied, so there shouldn't be any non-canonical ACL issues

Anyone ever come up with a solution to this? I get something similar when Activesync tries to create objects on user containers.
Exchange ActiveSync doesn't have sufficient permissions to create the "CN=Test User,OU=Domain Users,DC=domain,DC=com" container under Active Directory user "Active Directory operation failed on DELL7S09.domain.com. This error is not retriable.
Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-03151E07, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
Make sure the user has inherited permission granted to domain\Exchange Servers to allow List, Create child, Delete child of object type "msExchActiveSyncDevices" and doesn't have any deny permissions that block such operations.
Details:%3
So...I get this after I introduced a MS Exchange 2010 SP3 RU8 server into my environment. You can find LOTS of people suggesting the same fix but I've not found anything that deviates from those fixes: check the "inherit permissions",
and give full permis to msExchActiveSync devices for the Exchange Servers security group, blah blah.
I got to this point by following a Migrate to Exch2010 paper by MS. I have no Win2k servers, my old Exchange server is Win2003r2SP2 with Exch2003SP2 fully patched. The Exch server is also a DC. I installed a new 2012r2 server and then patched
it. Installed Exch2010SP3Ru8 and all seems well.
The old Exch2003 server is still in production. My iPhone army connects remotely for mail, and all works great. I created a new Test User in AD, gave it a mailbox on the 2003 server, and waited a bit. It eventually shows up in the Server
Manager on the new 2010 Exch Server. I send it a bunch of emails, connect to it with an outook client on a Win7 machine, all works. I go to the SM on the 2010 box and migrate the mailbox to the new server. It works. I can connect with
outlook, send receive mail to other users in the org. I then try to connect with my iPhone and I get the message in Event Viewer over and over.
Went so far as to Promo the new 2012 server to a DC. seems to be fine. Now am wondering if I Demote the old Exch2003 server will it help...or cause a new crop of issues....

ALE distribution error - 0 communication IDOC

Hello,
We are getting 0 communication IDOC generated for message type DOCMAS error for ALE document distribution error. Please advice where to look for the error.
Anirudh

hi,
ani,
u check this,
If you want work items to be created when errors occur for the purpose of error handling, you need to assign the standard task TS40007915 PCROLL to a position or a workflow organizational unit.
Or
You can also distribute dependent objects manually for classes. You can use report program RCCLDIHI to distribute a complete class hierarchy including all classes characteristics, and characteristic values.
Only the message code (004 - change) is allowed for sending a document (message type DOCMAS). This function also creates the document in the target system.
You can control the sending of documents with the indicator Distribution lock. An object with this indicator in its status will not be distributed into other ALE systems.
You can set the indicator in Customizing Document Management System  Define document type  Define status. The distribution lock is read when a distribution automatically starts after a change pointer is set or for an Integrated Distributed PDM Solution (ID PDM).
You can ignore this setting by starting the distribution manually. When you set the indicator Ignore distribution lock in the initial screen, then all documents will be distributed overriding the previously set status.
You control the distribution of object links with the indicator You cannot maintain the object links via ALE and Object link unchanged in target system.
Information about object links are distributed through IDoc type DOLMAS01.
The data is transferred to the workstation application and to storage data in IDoc type DOCMAS04 if an original file exists to a document. The Remote Function Call interface protocol transfers the contents of the original file, for example text or design drawing.
You can determine whether you want originals of a certain document type to be distributed by ALE into another system under the setting Document Management System  Define document type  Define transport of originals for ALE. You can control distribution with various criteria.
You want to distribute all original files of the application WRD (Microsoft Word) for the document type R-1 (report) that are stored in vault VAULT1 (Vault for Office Applications). You do not want to distribute documents of the same document type for the application WWI (Winword 6.0).
You can process the status for the desired objects.
1. Select in Customizing Cross Applications Components  Distribution (ALE)  Standard ALE Business Processes  Logistics  Master Data Distribution  Integrated Distributed PDM Solution (ID PDM)  Object status (for example, Define BOM status).
2. Process the indicator Distribution lock
ben

How is Idoc MBGMCR triggered/Configured in SRM Extended classic scenario

Hello All,
In the existing scenario, when confirmation is created in SUS portal, corresponding confirmation gets created in EBP .
Once the confirmation in EBP gets approved ,we want corresponding confirmation creation in backend system (ECC) .
I thought of using the standard idoc of basic type MBGMCR01 and message type MBGMCR for the above requirement.
But I am unable to find how to configure the triggering of idoc MBGMCR during creation of confirmation in EBP.
If anybody has an idea of message control method in SRM or how is idoc MBGMCR gets triggered, please let me know.
Thanks in advance.

Hi Anuradha,
You would require to set up distribution model , tcode - BD64
SAP NetWeaver ->Application Server ->IDOC Interface / Application Link Enabling (ALE) -> Modeling and Implementing Business Processes ->Master Data Distribution ->Distribution Using Object Classes ->Model Distribution Using Classes.
Once the distribution model is set up you can assign the message type MBGMCR.
Hope this helps you.
Regards,
Ashish

Open item account line with flow type 0178 has to contain a partner

At the time of RERAPP Periodic posting getting the error msg
" Open item account line with flow type 0178 has to contain a partner"
    Message no. RERACA005
Please guide me on the same.

Hi,
As per your suggestion i have posted the setting for flow type
In Define Flow type
140     Security Deposit     S Debit Posting     ANRVCN     TRRVCN
Assign Reference Flow Types
10 Follow-Up Postings Due to Condition Increase     140     Security Deposit     140     Security Deposit
20 Follow-Up Postings Due to Condition Reduction     140     Security Deposit     140     Security Deposit
30 Distribution Postings (Object Transfers)     140     Security Deposit     140     Security Deposit
Please guide me

Powershell to get all the members in about 20 DynamicDistribution group in exchange 2010

I have about 20 DynamicDistribution groups in my exchange 2010 enviroment. I need to run a report to show all the members in each group. How can I accomplish this with powershell ? thanks for all the help

I assume you don't want the output of all 20 groups dumped into one single list. So, you'd just use this:
Use the Shell to preview the list of members of a dynamic distribution
group
This example returns the list of members for the dynamic distribution group Full Time Employees. The first command stores the dynamic distribution group object in the variable $FTE.
The second command uses the Get-Recipient cmdlet to list the recipients that match the criteria defined for the dynamic distribution group.
$FTE = Get-DynamicDistributionGroup "Full Time Employees"
Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter
For detailed syntax and parameter information, see Get-DynamicDistributionGroup and Get-Recipient.
Mike Crowley | MVP
My Blog --
Baseline Technologies

Performance with having tables in different schema's

Hi all,
We have a requirement to segregate tables into different schema's based on the sources. But everything is going to be on the same instance and database.
Is there a performance hit (querying between tables) by having tables in different schema as apposed to having them in the same schema?
Thanks
Narasimha

Most likely there is bit of performance impact if your application refers the tables from different schemas. You need to use database link to access the other schemas. Even you schemas may in instance but when you use database link the network also comes into picture. even queries on same instance will routed through network connect and get the data. Distributed transaction also have issues some time. So as far as possible the distribution of objects should be avoided into diffrent schemas.

Extraction program for EH&S (EH&S to XI scenario)

Dear Experts,
I am from the XI background and am new to EH&S. I would like to know whether there exists an extraction program to extract substance data from EH&S(ECC) and send it to XI. If yes then what is it? The EH&S team here doesn't know of any kind. They have only used Change pointers to extract data from one client to the another.
Please help.
Thanks,
Merrilly

Hello,
How to set up ALE for substances is described in the IMG / Customizing for EH&S.
For EH&S 2.7B on R/3 4.6C this is located under:
Environment, Health & Safety -> Product Safety -> Interfaces -> EH&S Application Link Enabling (ALE) -> ALE for Specification Management.
All necessary information should be found in 'Set up Distribution of Specification Data':
                                                                                Set Up Distribution of Specification Data
In this IMG activity you set up the distribution of data on
     specifications (see also Information About the Concept in EH&S
     Application Link Enabling (ALE)).
Requirements
1. Setting the Active Code Page
         To transfer the data using ALE, you must ensure that the active code
         pages are the same in the receiving system and sending system as
         follows:
-   You must select a code page for transfer (for example, SAP(ISO)
             code page 1100) that you set up on all SAP Systems that belong
             to your ALE distribution model.
-   In Customizing for Product Safety in the IMG activity Specify
             Environment Parameters using the environment parameter
             ALE_TRANSFER_LANGUAGE, you must specify a language of the
             previously selected code page as the transfer language in the
             sending system. This language controls which code page is active
             in the sending system during data transfer.
-   The RFC destinations of the target systems must be defined with
             the logon language that corresponds to the specified code page.
-   If data is to be transferred to different SAP(ISO) code pages,
             the operating systems of the sending and receiving systems must
             use the same character sets (ASCII or EBCDIC):
Sending system      Receiving system        Transfer possible
         AS400               AS400                   Yes
         UNIX                UNIX                    Yes
         NT                  NT                      Yes
         NT                  UNIX                    Yes
         UNIX                NT                      Yes
         AS400               NT                      No
         AS400               UNIX                    No
         NT                  AS400                   No
         UNIX                AS400                   No
For more information, see:
-   The IMG activity Specify Environment Parameters
-   The IMG activity Set Up EH&S Native Language Support
-   The Product Safety documentation in the section EH&S Native
             Language Support
2. Settings in Customizing for Distribution (ALE)
         You have made the necessary settings in Customizing for Distribution
         (ALE).
         Also maintain, for example, the sections
-   Basic Settings
-   Communication
3. Settings in the Product Safety Component
         Make sure that you have fulfilled the following prerequisites:
a) Maintain the environment variables for serialization
             Serialization collects the IDocs and makes sure that they are
             processed in the correct order. For more information, see
             section Serialized Distribution in Customizing for Distribution
             (ALE).
You specify the serialization number for the sending logical
             system in the IMG activity Specify Environment Parameters using
             the environment parameter ALE_SERIAL_ID. You specify one unique
             channel per logical system.
b) Specify specifications to be distributed
             If you want to distribute specification data manually, choose
             the specification directly from the hit list in specification
             management.
             For automatic distribution, the specifications must appear in a
             set of hits that is assigned to the distribution method. If a
             set of hits has not been assigned, all of the specifications are
             distributed, providing that you have not defined filters.
             Apart from standard filters (see below), you can use the
             following customer exits to define further restrictions and
             filters:
             - Specify Additional Table and Parameter Filter (1)
             - Specify Additional Table and Parameter Filter (2)
c) Ensure unique identification of specifications
             The specification object must have a unique specification key.
             In the standard system, identification is supported by the
             specification key.
             You can use the customer exit Develop Enhancement for
             Identification to enhance the identification, for example, to
             link with one or more identifiers.
d) Check authorizations
             For manual distribution and automatic scheduling, you must have
             the read authorization for all the specification data to be
             distributed.
             You also need the appropriate authorizations for inbound
             processing in the target system.
Activities
1. Maintain the Distribution Model in Distribution (ALE) Customizing
         In Customizing for Distribution, call the IMG activity Maintain
         Distribution Model.
         For more information, see the documentation for the IMG activity.
         To guarantee communication between systems during distribution, you
         must make the following entries in the IMG activity Maintain
         Distribution Model by choosing Add method:
Field             Entry
        Sender/client:    <Key for EH&S system>
        Receiver/server: <Key for target system>, for example,
                          Sales and Distribution system (SD), on which EH&S
                          is installed.
        Object name/interface:   Substance (substance(specification),
     BUS1077)
Method:           SavRepMul (save replicated specifications)
Note:
Message type SUBMAS is supported.
You can set the following filters:
-   Reducing specifications by determining recipients:
             You can reduce the specifications to be distributed by defining
             the following filters:
             - Specification type
             - Authorization group
             - Substance nature
             - Set of hits (external key of group object)
             You can enter several values for a filter field. Individual
             values are linked with OR, whereas the filter groups are linked
             with AND.
If no filters are entered, all specifications are distributed.
-   Reducing specifications using 'IDENTHEADER' filtering
             You define the identification category and identification type
             whose specifications are to be distributed.
-   Reducing data using 'PROPHEADER' filtering
             You specify the value assignment types for which specification
             data is to be distributed.
-   In Distribution (ALE) Customizing, you can use the IMG activity
             Set Up Segment Filtering to exclude further tables from
             distribution, for example:
             - Material assignment
             - Regulatory list assignment
             - Reference specification assignment
             - Usage
- Assessment
Then in Distribution (ALE) Customizing, you maintain the IMG
         activity Generate Partner Profiles.
2. Maintain Settings in the Sending and Recipient Systems
         The following tables must be maintained in the same way in the
         sending and recipient systems:
-   Value assignment type TCG01 and description TCG02 (system
             tables)
-   Table of names for the DDIC objects TCG03 (system table)
-   Table of names for the child DDIC objects TCG04 (system table)
-   Specify Value Assignment Types
             Value assignment type TCG11 and description TCG12
             Value assignment type - specification type assignment TCG13
-   Identification category TCG21 and description TCG22 (system
             tables)
-   Check Identification Types
             Identification type TCG23 and description TCG24
-   Check Identification Listing
             Identification listings TCG26 and description TCG27
             Definition of identification listings TCG28
-   Assign Characteristic-Specific Identification
             Overriding identification list definitions TCG29
-   Specify Specification Types
             Specification type TCG31 and description TCG32
-   Specify Authorization Groups
             Authorization object TCG36 and description TCG37
-   Specify Types for User-Defined Texts
            Value assignment text type TCG41 and description TCG42
-   Create Sources
            Source TCG46
-   Specify Source Types
            Source type TCG47 and description TCG48
-   Set Up Property Trees
            Property tree TCG51 and description TCG52
            Property tree - value assignment type assignment TCG53
-   Specify Data Origin
            Data origin TCG56
-   Specify Phrase Libraries and Phrase Groups
            Phrase library TCG61 and description TCG62
            Phrase group TCG63 and description TCG64
-   Specify Language Selection
            Phrase language (languages supported in phrase library) TCG65
-   Value assignment type class characteristic TCG66
            System table, filled using master data matchup
-   Check Value Assignments
            Value assignment assessment TCG71 and description TCG72
-   Specify Component Types for Compositions
            Component type TCG76 and description
-   Specify Regulatory Lists
            Regulatory list TCG81 and description TCG82
-   Specify Ratings
            Value assignment rating TCG86 and description TCG87
-   Specify Validity Areas
            Validity area TCG91 and description TCG92
-   Specify Usage Profiles
            Usage profile TCG96 and description TCG97
            Usage profile - rating - validity area assignment TCG98
-   Specify Exchange Profiles
            Exchange profile TCGC3 and description TCGC4
-   Specify Environment Parameters
            General environment parameters TCGENV
-   Protect Characteristics Within Namespace
            Namespaces for characteristics TCGK1
-   Manage User Exits
            User exit parameters from user exit management TCGUEEN
            User exits from user exit management with function module
            assignment TCGUEFU
            Language-dependent user exit names from user exit management
            TCGUENA
            User exit categories from user exit management TCGUETY
3. Check Master Data to Be Distributed
For the ALE process, the following master data must be distributed
         to all the relevant systems:
-   Phrases
-   Phrase sets (for systems, in which data is created)
-   Classes and characteristics
-   Materials (all material data that is required for
             material-specification assignment)
-   Change numbers
         Note:
Classes and characteristics are distributed via export and
             import. The help texts and phrase sets are also transferred to
             other systems along with the classes and characteristics.
             Classes and characteristics can also be distributed using ALE.
         Note:
         The required data providers must have been created manually in the
         Product Safety component under Tools -> Edit addresses -> Data
         provider before data is distributed in the recipient system. The
         data providers must be unique with regard to the following three
         fields:
         - Name (NAME1)
         - City (CITY1)
         - Country (COUNTRY)
         During distribution, the data providers of the specification to be
         sent are read and also distributed. When writing to the recipient
         system, the SAP System determines the corresponding address number
         for the data provider in the recipient system by comparing the three
         fields Name, City and Country for the address numbers that were
         sent, and then transfers this address number that was determined to
         the Data provider field (OWNID).
You can determine the address number of the data provider in
         Customizing for Product Safety in the IMG activity Specify
         Authorization Groups.
         To do this, call the input help for the Data prov. field in the IMG
         activity. You will find the value you require in the Addr. no.
         field.
         The address number is not displayed in address management in the
         Product Safety component.
4. Check Control Data to Be Distributed
         See above: "Maintain Settings in the Sending and Recipient Systems"
5. Check Consistency
         A consistency check can be performed for the settings in the
         distribution model and the partner profiles.
         To do this, in Distribution (ALE) Customizing, call the IMG activity
         Check Partner Profiles and Model Settings.
         The distribution model must have been distributed and the partner
         profiles must have been maintained in all relevant systems.
6. Error Handling
         As soon as an error occurs when an IDoc is processed, the whole IDoc
         is not updated. You can use a workflow to correct errors. IDocs can
         be modified manually (you can change the identifier, for example)
         and updated retrospectively.
General Procedure
1. In a customer reference model you define which data is to be
         distributed to which system. You use sets of hits to define the
         specifications that are to be distributed and specify filters with
         regard to specifications or specification data as required.
2. The first time you distribute specifications to the target systems,
         you do it manually, using the method REPLICATE according to the
         distribution model. Serialization must be switched off.
3. You activate serialization and switch on delta distribution as
         follows:
Activating Serialization
a) In Customizing for Product Safety, in the IMG activity Specify
             Environment Parameters specify the channel for the parameter
             ALE_SERIAL_ID through which the ALE data is to be distributed.
b) In Customizing for Distribution (ALE) choose Set Up Data
             Distribution -> Serialized Distribution -> Serialized
             Distribution Using Object Types -> Activate Inbound Object Types
             and specify the inbound object types for which serialization is
             to be performed.
c) Schedule a job (RBDAPP01) that posts the IDocs that arrive in
             series in the recipient system.
Switching On Delta Distribution
a) Activating change pointers for a message type
             Changes to master data objects are logged in the form of change
             pointers during master data distribution. To activate the
             writing of change pointers, in Customizing for Distribution
             (ALE) choose Set Up Data Distribution -> Master Data
             Distribution -> Activating Change Pointers -> Activate Change
             Pointers for Message Types and set the Active indicator for the
             message type for which you want to realize delta distribution.
b) Activating change pointers for each field
             From the SAP R/3 screen, choose Tools -> Business Framework ->
             ALE -> Development -> Master data -> Activate change pointer for
             each field and enter the message type for which you want to
             determine fields, for which the SAP System writes change
             pointers. All relevant data fields are delivered. If necessary,
             adjust the table to your requirements.
c) Activating change pointers generally
             To generally activate master data distribution using change
             pointers, in Customizing for Distribution (ALE), choose Set Up
             Data Distribution -> Master Data Distribution -> Activating
             Change Pointers -> Activate Change Pointers (generally) and set
             the active indicator.
d) Scheduling delta distribution as a job
             You can perform delta distribution manually or schedule it as a
             job.
To perform delta distribution manually, from the SAP R/3 screen
             choose Tools -> Business Framework -> ALE -> Administration ->
             Periodic processing -> Process change pointers and enter the
             message type you require and choose Execute.
             To schedule delta distribution as a job, in Customizing for
             Distribution (ALE) choose Scheduling Periodic Processing ->
             Scheduling Generation of IDocs from Change Pointers -> Define
Variants and create a variant. Then in the IMG activity Schedule
             Jobs create a job (RBDMIDOC) for the variant. You can set the
             time at which distribution is performed, for example,
             immediately after a change or periodically.
The following applies when transferring data:
o   If a specification is not found in the target system, it is created
         with the specification key that is transferred.
o   If a specification is available in the target system, its data is
         updated.
o   When complete specification data is being sent, the specification is
         locked and no changes can be made to it. If this lock cannot be set,
         the specification cannot be processed. The IDoc is given the status
         with error and a work item is created.
Note:
In manual distribution, change pointers are not taken into account.
         In other words, the entire data record is distributed and delta
         distribution is not performed.
Note on Executing the Report Program RC1PHDEL:
         You must NOT schedule the report program RC1PHDEL (physical deletion
         of data) to run in the source system or manually run it between
         initial distribution and delta distribution, because the keys of
         logically deleted data records can no longer be read and distributed
         by delta distribution after the report program has been executed.
         Before initial distribution you can execute the report in the source
         system.
         In the target system you can execute the report program independent
         of distribution, as long as the target system does not serve as the
         source system for further distribution.
         If you want to execute the report program after the first delta
         distribution, you must first make sure that all change pointers
         created have been fully processed by the delta distribution and, if
         possible, that all IDocs (intermediate documents) created were also
         successfully posted in the target system. Otherwise, there is no
         guarantee that the source and target systems will be consistent.
Example
         The report program RC1PHDEL was executed in the source system so
         that the deletions of an identifier of the identification category
         NUM and the identification type CAS and a phrase item were not
         distributed.
         Then an identifier of the identification category NUM and
         identification type CAS with the identical value that was previously
         deleted and a phrase item for the same phrase in the previously
         deleted language are created. The following errors occur in the
         subsequent delta distribution:
-   The identifier cannot be created because the NUM-CAS value
             already exists. The IDoc cannot therefore be posted.
             Notes:
If you attempt to create duplicate identifiers in the dialog,
             the same error messages will be displayed as when posting using
             ALE.
If the NUM-CAS identifier was not identical to the previously
             deleted identifier, the IDoc would be posted successfully and
             the identifier would be created in addition.
-   The phrase item cannot be created, because only one phrase item
             is permitted for a phrase in each language. The old phrase item
must be deleted first before the IDoc can be posted.
The next section describes the solution for similar error cases. You
         should, however, try to avoid the need for this procedure by not
         executing the report program.
e) In the target system in the dialog, delete the EH&S objects
             (specifications, phrases, reports), for which you have already
             run delta distribution. These objects are internally marked with
             a deletion indicator.
             Caution:
             When you distribute reports, the report bodies are distributed.
             To delete these, you simply need to delete all report reference
             specifications. Deleting report bodies is not necessary and also
             not possible. If you cannot delete objects (such as
             specifications or phrases) owing to their where-used-list, it is
             sufficient to delete the 'deleted' detail data in the target
             system that has not been distributed. This may require more
             processing effort than if you delete all the objects using the
             hit list and distribute all the data again in full.
f) In the target system, set the Set missing deletion indicators
             and Delete physically indicators in the RC1PHDEL report program
             and execute the report program in the target system.
             This triggers the following actions:
             - The deletion indicator is set in the tables that depend on the
             header data to be deleted.
             - All data with deletion indicators is deleted physically.
             - The corresponding entries in the table ESTALE (conversion
             table for ALE) are deleted physically.
g) Deactivate the active serialization and the writing of change
             pointers and start initial distribution of all objects again.
h) You can now activate the writing of change pointers and
             serialization again and use delta distribution as usual.
         Note:
         If you still have IDocs in the source system or target system that
         were created before the deletion in your target system, but were not
         distributed or posted, ignore these IDocs and do not post them. You
         can do this by changing the channel before repeating the initial
         distribution by using the environment parameter ALE_SERIAL_ID (for
         more information on the environment parameter, see the IMG activity
         Set Up Distribution of Specification Data).
Return ->
     Application
Hope this helps
Mark

Difference between client system and logical system

Hi all
Can any one explain about the client system and logical system??
When this message type will comes in to picture at the time idoc processing??
Thanks and Regards
Arun Joseph

hi Arun,
I am giving the complete info on idoc.pls chk once.then ur issue will be solved.ok
and to know the diffrence between client and logical system very keenly go thru this link
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=abouttheclientsystemandlogicalsystem&adv=false&sortby=cm_rnd_rankvalue
IDOC Administration
Step 1: Tcode: WE 46
Setting the Global Parameter for IDOC Interface
Step 2: Maintaing a Logical System
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Define Logical systems
Go to Spro transaction
Step 3: Allocating Logical systems to the Client
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Assign Client to Logical systems
Go to Spro transaction
Step 4: Setting up an RFC destination
Tcode: SM 59
Path: From the ALE Customizing in IMG, choose Communication, Define RFC
Destination
You can also do the Advanced Settings in the RFC Destination
Step 5: The PORT definition
TCode: WE 21
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Systems in Network, Asynchronous Processing, Assign Ports, Define Port
Step 6: Generating Partner Profiles
TCode: BD 82
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, PArtner Profiles and Time of Processing, Generate Partner Profiles
Step 7: Distributing the Model
TCode: BD 64
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, Maintain Distribution Model and Distribute Views
Technques for Distributing the Master Data:
Technique 1: The Push Approach
Executing the Process:
TCode: BD 10
Path: from the ALE Main Menu, choose Material Data Distribution, Cross
Application, Material, Send
Technique 2: The Change Pointer Technique
Enable Change Pointers Globally
TCode: BD 61
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers
Enable Change Pointers Globally
TCode: BD 50
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers for Message Type
Specify the Fields for which Change Pointers are to be written
TCode: BD 52
Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define
Change-Relevant Fields
How the Classification system works:
Creating a Class Type
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Status for the Class Types:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classification Status:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classes:
TCode: CL 01 (it is zero)
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes
Allocating classes to the Logical Syatems
TCode: BD 68
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Assign classes
to Logical systems
Filering at the IDOC level:
Identify the Filter Object:
TCode: BD 59
Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects
Type to IDOC Field
Modify the Distribution model
How Segment Filtering Works:
Configuration:
Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered
TCode: BD 56
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments
The Reduced IDOC Type:
The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.
The System still needs the fields, but this has no effect on the recieving system because each field has a null value,
represented by a forward slash(/) in the field.
TCode: BD 53
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,
Create Reduced Message Type
IDOC:
Complete Documentaion on any IDOC using TCode: WE 60
IDOC Display Tool: TCode: WE 02 or WE 05
IDOC DEfinition components:
Segment Components:
1. Segment Type (E1, Z1)
2. Segment Definition(E2, Z2)
3. Segment Documentation(E3, Z3)
E- SAP Defined
z- Custom Defined
IDOC runtime componets:
control Record:
Data Record:
Staus Record:
First Create the Segments using TCode: WE 31
and then create the IDOC using TCode: We3 30
first release the segments and then IDOC.
Creating a new Basic IDOC Type:
STEP 1: Analyze the Data:
STEP 2: Create Data Elements:
STEP 3: Create Segments:
STEP 4: Create Basic IDOC Type:
1. Execute TCode: WE 30
2. Select the Create new option and enter a description for your basic IDOC type
3. click the IDOC name, and click the create icon.
Enter the segment type and its attributes.
4. Keep on adding the segments as in step 3.
5. Save the basic IDOC type
Step 5: Release the Segment Type and Basic IDOC Type
STEP 6: Transport the Segments and Basic IDOC Type
Extending a Basic IDOC type:
STEP 1: Analyze the Data:
STEP 2: Create Custom Segments:
STEP 3: Create the IDOC Type:
STEP 4: Release the custom Segment and IDOC Extension
Develop the function module for fteching the Data and then inserting the data into IDOC using
EDIDD(for control Record) and EDIDC table(for DATA Record)
Configuring the Systen for IDOCs
Configure an Outboubd Process that uses Message Control
Step 1: Create a new Message Type
TCode: We 81
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 2: link the IDOC type to the Message Type
TCode: We 82
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 3: Create a new Process Code
TCode: We 41
Path: From the Area menu of EDI, choose Control,Outbound Process COde
Step 4: Create or Change a Partner Profile
TCode: We 41
Path: From the Area menu of EDI, choose IDOC,Partner Profile
Configure an Outboubd Process for Stand-Alone Programs
1. Create a new message type
2. Link the IDOC type to the Message Type
3. Add the message to the ALE Distribution Model(use BD 64)
4. Create or change the Partner Profile
go through the following site to have screen shots.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
thanks
karthik
reward me points if usefull

Unequal Distribution of Objects

Similar Messages

Maybe you are looking for