Best Practice unit of measurement usage in CONTRACT.

Hello All
I have a situation below
MATERIAL 1234 have two UOM Respectively Ordering unit as CAR and basic Uom as EA .
1 car = 10 EA
1 . I create a contract for
item 01 material 1234 with 100 USD CAR .
2. later vendor told us that they can not supply via CAR , they can supply via only EA DUE to their BUSINESS reasons.
3. should i change the item 01 material 10 USD EA ? OR should i lock 01 ITEM 1234 with 100 USD CAR? and add a new item below?
4. 02 ITEM 1234 10 USD EA.
Which one is allowed as per SAP standard.
APPRECIATE YOUR HELP.
Thanks
Muthu

system will create a contract with default Base Unit of Measure maintained in material master data.
The system will automatically do the conversion of CAR <--> EA as per what is maintained in the material master.
Thus, if your base unit of measure in material master is set as CAR, then you can create a contract for 1 Car to order 10 EA and vice versa.
it will be better to add a new line item for UOM as EA
Hope this helps you. let me know if this answers your query.
Regards,
Nikz
Edited by: Nikita... on Feb 18, 2010 4:59 AM

Similar Messages

Best practice for calc measures

Hi,
I read in one of the olap blog from experts which says that best practice for creating the calc measures is to have them in a seperate cube.
My question is that suppose I have two cubes in a AW of different dimensionality. Both the cubes has some calc measures to be created.
So can I create one more cube(dedicated to calc measures) considering all the available dimensions in the AW and create the calc measures for both the cube which has different dimensionality?
If I cannot do this then this means that if I have two cubes having different dimensionality then I would need two more cubes to create the calc measures for them? if yes then what would be the size implecation of the AW?
Thanks in advance.
Thanks
Brijesh

"Can I create one more cube(dedicated to calc measures) considering all the available dimensions in the AW and create the calc measures for both the cube which has different dimensionality?"
Yes, you can.
This is a pretty common thing to do. Store your base measures efficiently and then use calculated measures with the 'superset' dimensionality to bring different shaped measures together for the purposes of calculations or simply to get them all in one 'hypercube' to simplify access by SQL query tools and apps.
Kevin

Best practice followed on CONTRACT

Hello All
What are the best practice needs to be followed on changing the material data information ,
Step 1. created a contract for Material and PO released agains contract. later some times.
Step 2:- material master changes some important piece of data like order Unit/ Deletion or material group changes on MATERIAL.
step 3:- We do the same for the materials in the contract and deactivate the w.r.t line and create a new line item so that my new line item picks up from material master.
What are the other incidents material master team may do on material master so that i can inform the contract team to do the same.
What are the actions material master team may do on MATERIAL and which is relavant for contract data.so that i can alert CONTRACT and MATERIAL master team. so that communication will be seemless.so that every thing perfect and sync.
Muthu

Please check these answered links:
Contract best practices
good practices in SAP Value Contract
Best Practice while creating Contract, Purchase Requisition, Purchase Order
Best Practice unit of measurement usage in CONTRACT.

Best Practice Documents on Sourcefire

Hello,
May I know if there are any deployment best practice documents on IPS (covering Pre Processors settings etc), Network AMP and Fire AMP.
Thanks.
Regards,
Akhtar

Please check these answered links:
Contract best practices
good practices in SAP Value Contract
Best Practice while creating Contract, Purchase Requisition, Purchase Order
Best Practice unit of measurement usage in CONTRACT.

Best practice for CPU and memory usage?

I find my AIR application takes a lot of memory -- usually
>170M. And what is strange is that the memory usage is
increasing (about 4K/s) even when the application is simply sitting
there and do nothing. The CPU usage is supposed to be 0% when the
application is doing nothing, but it's not (usually ~5%). So I
wonder if there is any article about best practice on CPU/Memory
usage.

Those numbers indicate that your application is in fact doing
something. Perhaps you have a timer still running, or work being
done on an enterFrame event?

JSF - Best Practice For Using Managed Bean

I want to discuss what is the best practice for managed bean usage, especially using session scope or request scope to build database driven pages
---- Session Bean ----
- In the book Core Java Server Faces, the author mentioned that most of the cases session bean should be used, unless the processing is passed on to other handler. Since JSF can store the state on client side, i think storing everything in session is not a big memory concern. (can some expert confirm this is true?) Session objects are easy to manage and states can be shared across the pages. It can make programming easy.
In the case of a page binded to a resultset, the bean usually helds a java.util.List object for the result, which is intialized in the constructor by query the database first. However, this approach has a problem: when user navigates to other page and comes back, the data is not refreshed. You can of course solve the problem by issuing query everytime in your getXXX method. But you need to be very careful that you don't bind this XXX property too many times. In the case of querying in getXXX, setXXX is also tricky as you don't have a member to set. You usually don't want to persist the resultset changes in the setXXX as the changes may not be final, in stead, you want to handle in the actionlistener (like a save(actionevent)).
I would glad to see your thought on this.
--- Request Bean ---
request bean is initialized everytime a reuqest is made. It sometimes drove me nuts because JSF seems not to be every consistent in updating model values. Suppose you have a page showing parent-children a list of records from database, and you also allow user to change directly on the children. if I hbind the parent to a bean called #{Parent} and you bind the children to ADF table (value="#{Parent.children}" var="rowValue". If I set Parent as a request scope, the setChildren method is never called when I submit the form. Not sure if this is just for ADF or it is JSF problem. But if you change the bean to session scope, everything works fine.
I believe JSF doesn't update the bindings for all component attributes. It only update the input component value binding. Some one please verify this is true.
In many cases, i found request bean is very hard to work with if there are lots of updates. (I have lots of trouble with update the binding value for rendered attributes).
However, request bean is working fine for read only pages and simple binded forms. It definitely frees up memory quicker than session bean.
----- any comments or opinions are welcome!!! ------

I think it should be either Option 2 or Option 3.
Option 2 would be necessary if the bean data depends on some request parameters.
(Example: Getting customer bean for a particular customer id)
Otherwise Option 3 seems the reasonable approach.
But, I am also pondering on this issue. The above are just my initial thoughts.

Creating Billing Unit in CRM V1.2007 Best Practices C05

Hi,
in C05 (Org Model with HR Integration) for Best Practices V1.2007 I have to create a Billing Unit.
That means, I have to create a Corporate Account.
For Creation of the Corporate Account i need a Number Range and a Grouping.
My Question:
Maintaining Number Range and Grouping for Business Partners is described in C03.
In the Solution Builder C03 comes after C05.
So I have first to finish C03 manually via SPRO or at least I have to maintain a Number Range and a Grouping so that I´m able to create the Billing Unit as an Corporate Account and then proceed with C05?
Regards
Andreas

Hi Padma,
We are facing the same issue while installing Baseline Best practices.
"Transport numbers not fullfill the requirement"
We are trying to activate full solution.
I have already created a new work bench and customize request ,but stills its gvg "Transport numbers not fullfill the requirement".
Iam not able to find a solution for this on service market place.
Thanks & Regards,

Best Practice while creating Contract, Purchase Requisition, Purchase Order

Hi
What is the best practice with respect to Contract & Purchase Requisition?
IN T Code ME31K, there is a button Reference to PReq, meaning that we can create contract with using Purchase Requisition. (We have done the same)
While creating the Purchase Order using Contract, we could find Purchase Requisition reference in the Purchase Order; similarly when we created the Purchase Order using Purchase Requisition, we could find Contract reference in the Purchase Order.
I have done the following:
1. Create a Contract.
2. Create a Purchase Requisition
3. Assign Requisition and Create Purchase Order using T Code ME57.
4. Create Purchase Order
Here in this case we could find references of both Contract & Purchase Requisition.
I just want to know what Practice should we adopt / advise while creating Contract, Purchase Requisition. & Purchase Order?
Regards,

Hi,
In ME51N Screen, enter Contract number in the "AGREEMENT" TAB and if more items in the contract, you can mention the item number in the next TAB to the AGREEMENT TAB and then proceed with creating PR by entering other details. This TAB you can find in the 4th column from extreme right end of PR screen.
Regards,
Biju K
Edited by: Bijay Kumar Barik on Sep 10, 2009 2:23 PM

Best Practice: Usage of the ABAP Packages Concept?

Hi SDN folks,
I've just started on a new project - I have significant ABAP development experience (15 years+) - but one thing that I have never seen used correctly is the Package concept in ABAP - for any of the projects that I have worked on.
I would like to define some best practices - about when we should create packages - and about how they should be structured.
My understanding of the package concept is that they allow you to bundle all of the related objects of a piece of development work together. In previous projects - and almost every project I have ever worked on - we just have packages ZBASIS, ZMM, ZSD, ZFI and so on. But this to me is a very crude usage of packages, and really it seems that we have not moved on passed the 4.6 usage of the old development class concept - and it means that packages do not really add much value.
I read in the SAP PRESS Next Generation ABAP book (Thomas Ljung, Rich Hellman) (I only have the 1st edition) - that we should use packages for defining separation of concern for an application. So it seems there they are recommending that for each and every application we write - we define at the least 3 packages - one for Model, one for Controller and one for view based objects. It occurs to me that following this approach will lead to a tremendous number of packages over the life cycle of an implementation, which could potentially lead to confusion - and so also add little value. Is this really the best practice approach? Has anyone tried this approach across a full blown implementation?
As we are starting a new implementation - we will be running with 7 EHP2 and I would really like to get the most out of the functionality that is provided. I wonder what others have for experience in the definition of packages.
One possible usage occurs to me that you could define the packages as a mirror image of the application business object class hierarchy (see below). But perhaps this is overcomplicating their usage - and would lead to issues later in terms of transportation conflicts etc.:
                                      ZSD
                                        |
                ZSOrder    ZDelivery   ZBillingDoc
Does anyone have any good recommendations for the usage of the ABAP Package concept - from real life project experience?
All contributions are most welcome - although please refrain from sending links on how to create packages in SE80
Kind Regards,
Julian

Hi Julian,
I have struggled with the same questions you are addressing. On a previous project we tried to model based on packages, but during the course of the project we encountered some problems that grew overtime. The main problems were:
1. It is hard to enforce rules on package assignments
2. With multiple developers on the project and limited time we didn't have time to review package assignment
3. Devopelers would click away warnings that an object was already part of another project and just continue
4. After go-live the maintenance partner didn't care.
So, my experience is is that it is a nice feature, but only from a high level design point of view. In real life it will get messy and above all, it doesn't add much value to the development. On my neew assignment we are just working with packages based on functional area and that works just fine.
Roy

Best Practice - Changing description for Org Unit/Position or creating new?

Hello Freinds,
I just want to know from your experience what's normally practiced in your implementations for OM :-
For scenarios where there is a need to change the description of a particular org unit or position, do u
1. just change the description effective a particular date (to maintain history) or
2. put an end date to those objects and create new ones ?
Solution 1 is quick and easy, but in IT0001 the description displayed is as on start date of that infotype which is normally a date prior to the change in desc of those objects. As a result this infotype keeps displaying old description.
Is there any way to change this display to show the current description instead of the description as on start date of this infotype ???
Solution 2 calls for a lot of related activities, say if i create a new org unit and delemit the old one - then i have to move all the sub org units and positions into this new one ... which is quite time consuming and doesn't really seem practical.
How do u manage such scenarios ?
Thanks
Allen

We use option #1, although I am not sure this is best practice. Using option 1 for positions makes it challenging when it comes to reporting on length of time in position. We frequently have the scenario where a person is reorged not because they applied for another position, but just because the big wigs want to move around the chess pieces. In these cases we simply modify the position attributes and then run a PA action. Then if you run a query and use the standard delivered Length of time in position field, it appears as if the person has been in the same position for years (which they have), but their position has been retitled, re-graded, and re-orged numerous times. This makes it very difficult to get to an employee's length of time in their role.
This is a great discussion question I hope more people respond with what they do and why.

Best practice to use contract(ME31K) in reference a PR

Hi,
I create a PR(me51n) with service (the commitment is on the PR), next I create a contract(me31k) in reference with the PR. In the contract I do some change, I subdivide the service in two lines. After with ME57 I assign the contract with the PR.
When I want to create a PO (contract release ord), should I us the contract in reference or the PR. If I use the contract my commitment do not follow and if I use 50% for my PR the commitment is used at 100%.
What is the best practice?
Best regards

Hi,
If I use the entire PR it is true but if I use only 50% of it. The commitment of the PR disappears and the commitment of the PO is 50% of the PR. And I want to found a way to transfert only the % of the commiment used in the PO.
Best regards

Best practice for Extracting sales contracts from R/3

Hi Everyone,
We have a requirement to bring sales contract data from R/3 and most of the fields from table VEDA. 2lis_11_vaitm don't carry VEDA fields.
What are the best practices on brining VEDA fields into BW?
Thanks,
D. Eranezhath

New URLs are:
LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
Custom fields and BW extractors : Making a mixed marriage work! (Part-II)

Best Practices- Number of users in Contract Manager

What is the best practices for the number of users operating in Primavera Contract Manager? We currently have v13.0.3.0

There are no real limits to the number of users working in PCM, but your server(s) must be sized correctly to work effectively. I've seen PCM instances with hundreds of users. Sizing requirements is typically included with your installation materials; otherwise you may want to look at the knowledgebase for this document.

What are Microsoft- or other's-best practice or recommendation of Disk usage, CPU usage, memory usage monitoring to prevent system trouble ?

We use win2003,win2008,win2012 servers.
I heard somewhere that Microsoft recommendation threshold of disk usage monitoring is ( free disk space >= 15- 20 %) , if I remember correctly, but how about CPU usage and memory usage monitoring ?
What are Microsoft- or other's-best practice or recommendation of Disk usage, CPU usage, memory usage monitoring to prevent system trouble and improve availability ?

Hi,
You can refer the following Performance Tuning Guidelines,
Performance Tuning Guidelines for Windows Server 2003
http://download.microsoft.com/download/2/8/0/2800a518-7ac6-4aac-bd85-74d2c52e1ec6/tuning.doc
Performance Tuning Guidelines for Windows Server 2008 R2
http://blogs.technet.com/b/josebda/archive/2010/08/27/performance-tuning-guidelines-for-windows-server-2008-r2.aspx
WINDOWS SERVER 2012 - PERFORMANCE TUNING GUIDELINES
http://blogs.technet.com/b/itprocol/archive/2012/11/27/windows-server-2012-performance-tuning-guidelines.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Handling units management SAP Best Practices Document Links

Hi Friends
I would like know more about handling units management .
Could you please send me SAP Best Practices Document handling units management Links .
Thanks in Advance.
Thanks
SR

Might be useful:
[Click here|help.sap.com/bp_bblibrary/500/documentation/U43_BB_ConfigGuide_EN_IN.doc|weblink]
Thanks and Regards,
Naveen Dasari.

Best Practice unit of measurement usage in CONTRACT.

Similar Messages

Maybe you are looking for