Rules for Deployment Optimization

Hi ,
While defining deployment profile, we have to define Fair Share and PD rules. Just wanted to know what is its' significance in Deployment Optimization. As far as I understand Deployment Optimization is done only on the basis of costs.
Reply needed urgently.
Thanks & regards
Kunal

user1073781 wrote:
What about the following rules for good SQL usage and query optimization imposed by tha DBA of my company?
My, where to begin? I assume this is for the World's Most Hopeless DBA competition?
>
1) Don't use referential integrity but implement it applicationally. This for easy tables administration
Because it is real easy to deal with logically corrupted data I guess.
>
2) Don't specify schema name in the queries, but only use table name. The table name must be unique on the entire Oracle instance.
It doesn't matter if it is unique you won't find it without the schema name, unless public synonyms are used and these should be avoided.
>
3) Don't use select *.
Sometimes valid, sometimes not.
>
4) Don't use ROWNUM in the where condition
Which will exclude being able to execute top-n or pagination queries, unless the intent is to return all, possibly billions of rows and throw away all except ten for example.
>
5) Don't create too much indexes because they make worse performance of the insert,update and delete operations
Define too much.
>
In my humble opinion the 1) is completely wrong: why use a relational dmbs without relationships between tables?
Agreed.
>
What do you think?
Most of the others make no sense either.

Similar Messages

Optimization profile for Deployment optimizer. 3.0 -- 5.1

To APO guru
we are going to 5.1 directly from 3.0. then I am in stcuk to setting up optimizer profile.
In the Deployment optimizer, one of field is optimizer profile which is customized setting we are using it.
After upgrade to 5.1, the field value didn't come through by transport.
When I try to set up for this value, I had supprised due to different totally even in attribute.
So, I am struggling to set it up, could you help anyone has field mapping between 3.0 and 5.1 for optimization profile.
Regards, Junu

Are you able to change it manually?
Or you may to right a customized program which will take care of your requiremnent.

Does Deployment Optimizer need a separate server?

We just finished blue-print and came to a conclusion to use SNP Heuristics and Deployment Optimizer. Since we are not using SNP Optimizer, my question is that should we need a separate server?
I did not find any quicksizer document for Deployment Optimizer however, I could see for SNP Optimizer though.
Any help would be appreciated.
Thanks,
C.A.

Any Optimiser (SNP / Deployment / PPDS / TPVS / CTM) will need Optimiser Server connection as the Optimiser Routines are .exe files requiring a Windows-based hardware with sufficient Main Memory (RAM).
Deployment Optimiser will be part of SNP Optimiser Engine.
Somnath

Deployment Optimizer - Equal weightage for all the locations in the network

Hello All,
I am having difficulty in assigning equal weightage for all the locations in the deployment network. My scenario is as described below:
Deployment Source location: LOC1
Destination locations: LOC2, LOC3
I am running Heuristics to plan LOC2, LOC3 & LOC1, followed by
a Deployment Optimizer run at LOC1 to deploy to LOC2 & LOC3.
ATD quantity at LOC1 is always calculated after saftisfying the requirements at LOC1 and the remainder is deployed to LOC2 & LOC3 based on the cost settings. This seems to be the case even if I don't run the heuristics at LOC1 and start deployment optimizer after running the heuristics at LOC2 and LOC3.
The need at this client place is that all three locations are equally important even though LOC1 is the only deploying source location.
This applies for all demand categories i.e. Sales orders, Forecast and forecast at all the three locations.
I would appreciate if anybody has done this kind of configuration before and let me know how to model this.
Thanks,
Venkat

Have you follow all this checking ?
If you think that you already follow all the steps, but the value is not as per your config, you can raise ticket to SAP about it.
But I suggest you to double check your computation.
To determine a vendor's price level, the system compares the vendor's effective price with the market price for the material.
   1. The system first checks whether the buyer has maintained a market price for the material or the material group.
   2. If not, the system calculates the market price which is equal to the average of the effective prices for all vendors supplying this material. Prices from purchase orders and prices for subcontracting are dealt with separately.
   3. The system then applies the effective price for the vendor from the conditions.
   4. The vendor's effective price is then compared with the market price and the percentage variance determined.
   5. The system then assigns a score to the variance in accordance with the settings made in Customizing.
   6. This score is valid for the material, that is, at info record level. Since the score the vendor receives for a subcriterion is based not on an individual material, but on the total of all the materials he supplies, the following steps are necessary:
   7. The system repeats the comparison between effective price and market price for each of the vendor's materials.
   8. The system calculates an average from the sum of the scores determined. This average represents the vendor's score for the subcriterion Price Level.
Edited by: w1n on Apr 19, 2010 2:35 PM

Deployment Optimizer - Modeling question

I am new to the Deployment/Optimizer area. I have modeled a scenario as described below.
And have a few questions on what I would like to happen during deployment.
Central DC: CDC1, Regional DCs: RDC1 & RDC2
Product gets deployed from Central CDC1 to RDC1 & RDC2. I have customer demand and forecasts at all the three locations.
I have defined ATD Receipts category group as just Stock on hand only (category CC) and ATD Issues includes AY, BH, BI,
BM, BR, EB etc. These two categories are assigned to the Location Master.
I have specified Fair Share Rule "A" in the Product master and location dependent penalty costs in SNP1 tab.
In the Deployment Optimizer profile I have mentioned that the Distribution is based on Lowest Costs for both Supply Shortage
and Supply Surplus. I have defined a Pull Depl. Horizon of 10 days, and blank for Push Deployment and SNP Checking Horizon.
When I run the deployment with all the three locations, what I notice is that the Customer orders and forecast of the Central DC are
satisfied before deploying anything to the Regional DCs.
My requirement is that the Central DC should deploy the available quantity at the Central equally among the Centrals and the Regional
DCs on a fair share basis for the Sales orders first, then the remainder of the stock should be deployed, again among Central and
Regional DCs on a fair share basis for the forecast and the safety stock is the last.
How can I achieve this equal deployment among central and regionals even though Central is the source location.
Could somebody let me know how to model this above requirement?
Thanks,
Venkat

Hi Venkat,
I am trying to model the exact scenario where the ATD quantity is not being equally split but the whole chunk is being sent to one of the destination locations. Can you please let me know how you have setup the cost models.
Regards

Differece between SNP Optimizer and Deployment Optimizer

Hi,
Can anyone please list down the difference in the planning method for a deployment optimizer and SNP Optimizer?
Thanks & Regards,
Sanjog Mishrikotkar

Hi Sanjog,
First of all if we understand the difference between SNP Heuristic Planning run which finds the 'Source' of Supply with dates and quantities and Deployment Planning run which CONFIRMs the Supply .... then it is easy to understand the difference between SNP & Deployment Optimizer.
The Optimizer as you know Optimizes based on Costs and Objectively tries to MINIMIZE it. Therefore while the SNP Optimizer finds the most cost effective way of finding the Source of Supply with dates and quantities, identifying where in SC it is better to Store or move the Product, while the Deployment Optimizer generates the Best way to CONFIRM whether the Supply can ACTUALLY be done for the next few days. Deployment precedes the TLB Run which after confirmation we put the Quantities on a Transport Load to build Orders for Execution (Shipping).
Both are Cost based & use the Same Costs Information ... however one Plans and the Other Confirms. During Deployment Optimization run, the Optimizer may decide to confirm the supply from a different source than what the SNP Optimizer planned based on the Available to Deploy Stock Quanties and the Cost of Confirming the Supply. The Deployment Optimizer will apply Fairshare & Push/Pull Rules and looks at the Push and Pull Deployment Horizons which SNP Optimizer cannot. The Difference is also in Planning Time Range. You plan SNP Supply for mid to long term time range. The Deployment looks at Confirming the supply in the next few days from TODAY.
So in short first understand the Difference between a SNP Heuristic and Deployment Heuristic and apply the same principle to a cost based optimization. This should tell you the difference between the two.
Try read this ... First para on Deployment Optimizer ...
http://help.sap.com/saphelp_scm50/helpdata/en/1c/4d7a375f0dbc7fe10000009b38f8cf/frameset.htm
Read the First Paragragraph as well as 'Distribution based on Lowest Costs' section
Hope you find this answer usefull. Reward Points if it is.
Regards,
Ambrish Mathur

ISE 1.1.1 firewall rules distributed deployment

My question is in reference to the following link:
http://www.cisco.com/en/US/docs/security/ise/1.1.1/installation_guide/ise_app_e-ports.html
Basically I am struggling in some areas to work out my firewall rules for a distributed deployment. The referenced documentation is not entirely clear in my opinion. In some instances it is easy to work out what ports need to be opened eg Admin node TCP 22,80,443 for management from administrator hosts/ranges. In other instances it difficult to work out eg TCP 1521 Database listener and AQ is this for ISE nodes only or for access devices aswell
My question is whether there is a better document that details these requirements. What rules are meant to be ISE node - ISE node communications and which rules are for access device - ISE, or ISE - access device. One of the rules I am pretty confused about is the PSN CoA ports. SHould the rule be WLC - PSN on 1700 and 3799 or is it the otherway round or unidirectional?
I am pretty sure that the ports are meant to be ISE-ISE in most instances barring the PSN for Radius and CoA.

Try this for size.
In answer to the specific CoA question, I see no need for the WLC to send CoA to PSN, so just PSN to WLC as far as I can see.
You might be able to cut this list down, and you might have to add to it for any specific requirements.
From PSN to AD (potentially all AD nodes):
TCP 389, 3268, 445, 88, 464
UDP 389, 3268
From PSN to Monitoring nodes:
TCP 443
UDP 20514
PSN to Admin Nodes (2Way):
TCP 443, 1521
ICMP echo and reply (heartbeat)
WLC to PSN:
TCP 443, 8443, 80, 8080
UDP 1645, 1646, 1812, 1813, 1700, 3799, 161, 162, 9993, 67
PSN to other PSN’s (2 way)
UDP 30514, 45588, 45990
Endpoint (Laptop) to PSN (Guest laptops just need to get to external PSN’s, internal users just to internal PSN’s)
TCP 8443, 8905
UDP 8905
Admin/Sponsor to all ISE nodes:
TCP 22, 80, 443, 8080, 8443
UDP 161
PSN access to DNS servers:
TCP/UDP 53
PSN access to NTP servers:
UDP 123

Best practice for deploying the license server

Was wondering if there is a best practice guideline or a rule of thumb out there for deploying the license server. For instance, is it better to have one license server and all your products connect to that, dev, QA, prod. Or is it better to have a license server for each deployment, i.e. one for dev one for QA.. etc.

Was wondering if there is a best practice guideline or a rule of thumb out there for deploying the license server. For instance, is it better to have one license server and all your products connect to that, dev, QA, prod. Or is it better to have a license server for each deployment, i.e. one for dev one for QA.. etc.

Change in Deployment Optimization Profile

Currently in Deployment Optimization Profile--- Deployment Parameter View--- SNP Checking horizon is 4 days
If this Parameter (SNP Checking horizon) is changed to 7 days what will be its effects on the current scenario
--Advantages & Disadvantages.
Kindly highlight your views/ comment on above scenario.
Thanks & Regards
Shashikant Salunkhe

Pls go thru F1 of SNP Checking horizon. You can get the Answer for your question.

REMSH unix command issues when adding rule for port 514

Has anyone experienced any issues with Unix systems when adding rules to WAAS for port 514? This is the port RCOPY uses and is not handled by WAAS by default. We created a rule for port 514 but when we implement any type of optimization (even TFO Only) we start having problems with REMSH. This is used in one of our production scripts that normally take 10 minutes to run. When we apply the rule for port 514 the time goes as high as 45 minutes.
We wrote a test script that uses just the REMSH command and with out the 514 rule works fine but with the 514 rule goes down the tubes.
Just to add a little more information, I do not see an entry under Monitor/ Connection Statistics with the servers in question when the test script is running so am not sure where to go from here. I know there is a way to do a TCP capture from the WAAS so figure that will be the next step to see what is causing the issues.
Thoughts?? Ideas?? Suggestions??

Well TAC came back with a answer. They found other people with the same issue.
"It was found that the applications always used the same source and destination TCP ports. WAAS has the first connection in a "WAIT-CLOSE" state so when the next packet comes in with the same ports it is dropped." , "A defect was opened for this issue, but has not been fixed yet."
He wanted us to do a packet capture but after finding these other tickets decided it would be a waste of time and only tell us we are having a similar issue as others.
Still waiting on a suggested work around or a patch, 4.15 is suppose to come out soon but haven't heard if it will fix the problem.
With the new information I don't think even putting 514 in pass-through will fix the issue.
I will let you know if I hear anything else.

How to manage transfer to OLTP system for deployment

hello experts,
Please could you suggest me how to solve this problem:
The rule is that only TLB results must be transferred to ECC
However, some Plants are not using TLB and I need to get the results of deployment sent to ECC for those plants.
I have set the checkbox TLB immediate transfer in SPRO (Configure transfer to OLTP system). I have also maintained all the plants in SPRO maintain distribution definition with external procurement. For deployment I ticked "no transfer"
I don't know whether it is possible to send results of deployment only for a couple of selected plants.
Is it possible without using CHange Pointers??
Thank you for your answers,
Best regards
EL

Hi,
this whole activity needs to be handled in two steps.
Step 1 - Run TLB for only those plants which need to have STOs. This can be done as a standard APO requirement. In the variant exclude the plants for which you do not want to run TLB
Step 2 - Once step 1 is completed publish Deployments orders (STRs) from APO to ECC using T.Code /sapapo/c5. Here in the varaint select the correct order type and locations for which you want to sent STRs.
Please run these in batch jobs ensuring to maintain the sequence, to avoid confusion.
Thanks,
Harsh

Deployment Optimizer - software developer

Dears,
could you, please, help me to find any documentation related to Deployment Optimizer's or simply Optimizer's mathematical engine? In case you have something, please, share. The only thing I heard that it was developed by iLog development company.
I need everything describing Optimzier's mathematics, mathematical algorithms, methods and so on.
Thank you in advance,
Regards,
Kirill Nepomnyashchiy
Edited by: Kirill Nepomnyashchiy on Mar 2, 2009 3:56 PM

Hi kirill,
Thanks for your confirmation. You can also make use of the below links
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzajq/rzajqjoinoptalg.htm
Optimisation algorithm
http://wiki.services.openoffice.org/wiki/Optimization_Solver
Optimisation solver
http://www.mosek.com/fileadmin/products/5_0/tools/doc/html/pyapi/node009.html#182968292776
Optimisers for problems
Hope these links will be very useful to you. Please confirm.
Regards
R. Senthil Mareeswaran.

Deployment Optimization

Hi experts,
We are trying to obtain a solution from deployment optimizer such that whenever a specific transportation lane is utilized (i.e. deployment stock transfer is observed on that specific transportation lane), a fixed transportation cost based on the distance traveled will be observed. This logic will be valid for all transportation lanes. The underlying reasoning behind this is that either a single phc or 1000 phcs is transported; the same transportation cost has to be incurred.
It would have been ideal if we could observe transportation costs dependent on the number of trucks that will be utilized on a specific transportation lane for a specific deployment stock transfer. However, since we do not know the number of trucks before running TLB, we cannot perform such an optimization within deployment. So, we decided to ignore the number of trucks and stay with a fixed cost based on the distance traveled for all units transferred.
We tried to utilize discrete optimization with a transportation cost function and means of transport cost. Yet, we cannot observe these transportation costs as a part of the total costs in the objective function. However, the input log for the optimizer includes the defined cost values.
We would appreciate any comments on this issue. Thanks in advance.
~isil

We decided to follow a different logic.

Advices & rules for package hierarchy

Hi,
I developing a new project and I'll use packages for the first time. (My company doesn't have rules for package)
I would like to know the gereral rules for creating a good hierarchy.
i'm thinking of something like:
com.mycompany.myproject.form
com.mycompany.myproject.dialog
com.mycompany.myproject.sql
com.mycompany.myproject.dataobjects
com.mycompany.myproject.table
com.mycompany.myproject.tree
Should I use also packages like com.mycompany.table for generals stuff like table models that could be of use for others projects ?
Is this a good idea ? Do you have any suggestions ?

I am not aware of any hard and fast rules for packaging. There are some things I keep in mind when I setup hierarchies though:
1) The "standard" (more common than standard) is your businesses internet address reversed. So for instance, if you are www.foo.com, your packages would start out with "com.foo". Some people leave off the "com" part as well, so you would have "foo". I don't like this however as more and more companies reserve "*.net" and "*.com" and "*.org" etc addresses. Leave the top level domain on there. This is mostly just for namespace sake, so you don't get two pieces of code from two different companies with the same name.
2) Is this the only product your company produces? OR will this be the only product your company produces? If the answer is no, you may want to put the product name next, so now we have "com.foo.product1". This will allow you to build nice, clash safe hierarchies.
3) Most products are broken down into a number of projects or modules. Sometimes its a good idea to divide the package structure with this information. So now we have "com.foo.product1.module1", "com.foo.product1.module2" etc.
4) If its an enterprise application (multitiered, J2EE, etc), I personally like to divide the code into tiers. It makes building easier and packaging for deployment much more intuitive. You might have web tier code, database tier code, application tier code, code common to all tiers etc. So now we have "com.foo.product1.module1.app" and "com.foo.product1.module1.web", etc. If its not an enterprise multi-tiered application, skip this step.
5) Now within the hierarchy we have built up, its pretty much up to you to logically divide your code.
6) It is now possible to "push" code up to certain levels to make it available to other projects/products/tiers. If you develop a nice data structure that you think might be useful to other products your company is developing, move the data structure up to an appropriate level to make it available to all products. For instance, "com.foo.structures.AwesomeStructure", instead of "com.foo.product1.structures.AwesomeStructure".
7) Products and projects should not import outside of their "scope". This prevents cross project dependency and cross product dependency. If another project or product needs to import something outside its scope then the code should be moved to a more common place to make it available.
Some will call this overly anal, but it has worked well for me for a few years. Hopefully others can provide you with more tips.
Hope this helps.

Deployment Optimizer - Is Category EF recommended to be in ATR?

Hi All,
We are using deployment optimizer. Our ATR category group does not include the distribution receipts confirmed (Category EF).
The deployment receipts planned within the deployment optimization are not considered further for deployment.
I need your help in finding out if other companies configure ATR in the same way? or is it a mistake from our design team.
Regards,
Zeeshan.

Hi,
Its depend on the business requirment. In your case I hope you are using TLB also. Actually you cant deploy products from one location to another location without any kind of stock, prod confirmed or TLB confirmed quantity. Now if you consider 'EF' as deployable quantity then you may face problem. Say you have a product of 100 quantity as 'EF' category at location 'B'. Now 'B' is supplied from Location 'A'. And another location 'C' receive goods from 'B'. Now can you supply all those 100 quantity from 'B' to 'C' ? You may not, because you may find that only 80 quantity was supplied from 'A' to location 'B' as TLB confirmed. So, actually you have 80 quantity at 'B' (received from 'A')
So, I think ATR is well configured ...
Thanks,
Satyajit
Edited by: Satyajit Patra on Jan 19, 2010 9:40 AM

Rules for Deployment Optimization

Similar Messages

Maybe you are looking for