Assigning value assignment types to prop tree

hi experts,
kindly explain what is comprind?
thank you,
niharika

Hi Niharika,
As Christoph explained, the flag is used to either show only the node in a tree (flag set), collapsed mode) or open the node to see all VATs underneath (flag not set). ComprInd stands for compression indicator.
While it is technically possible to set this flag both anode and on a normal VAT, the latter case of course has no impact on what you see.
Ralph

Similar Messages

Value assignment and value assignment type in the specification workbench

Hi all,
There is this section on the specification workbench called u201CProperty Treeu201D, this section contains all the value assignment type, I have two questions on this.
Question 1 u2013
What is exactly the value assignment type? The SAP help portal said it is a structure specification data and information. What exactly does it mean and its usage?
Question 2 u2013
May I know where is the SPRO configuration that actually causes the list of value assignment types appear on the property tree section for this particular specification type which I created.
In another word, I create this new specification with specification type u201CREAL_SUBu201C and specification category u201CSubstanceu201C in the specification workbench transaction. Next thing I know is that the property tree section for this particular specification consists of a list of value assignment type. How does the system assigned these list of value assignment types to this specification i created? Coz I didnu2019t do anything.
Where in SPRO and the logic link it up on this??
Thanks.
YY

Hello all
EH&S contains a number of submodules (PS, DG, IH etc.). Regarding each submodule a basic customizing is delivered by SAP. One example is the specification type. Usually you will find something like
REAL_SUB
LIST_SUB
etc. in the Customizing as discussed. Further more I believe with EH&S 2.7. the specification category come in place (SUBSTANCE as an example). You need to take care regarding this too.
An value assignment type can be grouped in a property tree and a property tree can be linked to a specification type and there are cases known that one specification type is linked only to one property tree (this is a decision regarding business needs and not an IT quesition). Using the EHS& surface you can change the property tree per specification if the set up is done in Customizing. Therefore the property tree is a "view" on the data linked to a specification. (identifeirs etc. are managed different)
A "property" is based on a value assigment type and in many cases on a related EH&S class and characteristic. You will find these types.
A => value assignment type to be used if you need characteristics
B => value assignment type to be used if you need specification listing
C => value assignment type to be used if you need composition
.. etc.
You can mix types. That means you can create a property of type "A" and "C" (take a look in SAP original tree; you will find examples how to do it).
A propetry tree is a "list" of assignment type related to a object (specification). Using the property tree you can maintain necessary data. Therefore ithe property tree itself contains per specification the list of "potential" data structures you can fill with data. I belive SAP Standard is delviering now something like 250 properties (valeu assignment types): To e.g. get an MSDS you need to maintain I would assume at least something like 20 up to 50 properties
The area of customizing regrading property tree, specification types etc. is the most crticial to have a sucessful EH&S project running; any wrong decision gives rise to a high cost later Therefore take your time to understand what effect does which customizing acitivity have later.
Based on the value assignemnt you will create later e.g. a WWI report (like MSDS).
Additionally if necessary you can create customer specific value assignment types by either do a copy from SAP original to "Z" (highly recommended to do so!) or starting from basic.
Starting with EH&S 2.7. you have now more options to "change" EH&S using standard EH&S functionality. Take a look in customizinjg (example: you could create you own "look and feel" of the workbench (you should'nt really do that but it is possible). You can design your own "tab strips" etc.
So once again: the "correct" set up of EH&S in the area of e.g. identifers, speficiation types, property trees etc. is the "core" activity in EH&S customizing and therefore think "twice" before you change the setup up (you need to understand what a change mean)
With best regards
C.B.

EHS - value assignment types

Hi Friends,
I'm not an EHS expert however I've received an EHS specific query, please help me to understand and how to proceed on below requirement:
In EHS module, create a new branch "regulatory information CLP" with 5 new properties and update old one to DSD/DPD.
For these changes, adds and changes will have to be done in customizing in "value assignment types" entry with different valorization type (branch and properties).
I can trace Value Assignments under property tree in SPRO but don't know how to go about.
Regards,
Yati

Hello Yati,
If I have understood correctly, you want to create / Edit a property tree. If so, thre are certain steps involved and it will not be possible to detailed it out here, but I will list out the requirements and steps involved;
Master data required:
1.Create characteristics for possible values to assign to the Value assignment type
2.Create class for the value assignment type and assign characteristics to the class
3.Create Phrase set
4.Create phrases and assign to the phrase set
Note: Step 3 &4 are required for phrase enable characteristics.
Perform following Customizing settings:
1.Basic Data and Tools -> Specification Management -> Specification Database Structure -> Settings for Value Assignment -> Specify Value Assignment Types
2.Basic Data and Tools -> Specification Management -> Specification Database Structure -> Settings for Value Assignment -> Set Up Table-Based Value Assignment
3.Basic Data and Tools -> Specification Management -> Specification Database Structure -> Settings for Value Assignment -> Set Up Property Tree
Request you to visit SAP help at : http://help.sap.com/saphelp_erp60_sp/helpdata/en/c1/eda0f591ec12408b25e7a1b369ca45/frameset.htm
and visit topic : Value Assignment under Basic Data and tools -> Specification Editing
Hope this information is helpful to you.
Regards,
Niraj

Value Assignment Type Setting

Dear Experts,
While creating the Value Assignment Type in SPRO
there are following check box... which are
CharCopy Active - Automatic Activation of Copied Value Assignments
New Val. actv - Automatic Activation of New Value Assignments
Change Active - Automatic Activation of Changed Value Assignments
I have read the help for each check box but still concept is NOT so clear...
Could you please elaborate me the significan of each check box...
also, couuld you tell me that As per Standerd / Regular Industry Practice, which of the above check boxes should be active and which should not
Please Guide..
Amol

Hello Amol
in some sense there is no "standard" how a company should/can use these check boxes. Both options have pros/cons.
In my opinion best practise is to "set them" (all three) and to prepare a user manual in which this "behaviour" of the system is explained.
From the point of view of "clicks" the number of clicks are nearly the same.
E.g.
if you not activate them you have to set the indicator and you must save the data records and
if you have activated and you would like to take some time to think once again about content of the data record you would remove the active indicator and save (later you must set them again to activate them and save them regarding MSDS etc.).
In any case: to my experience the end user training regarding how to use the usage and what does the active indicator means (as well as the relevancy indicator) is not an easy task.
By the way: there is to my knowledge no corresponding customizing activity in which you can handle how the "relevancy indicator" can be set or not. So in any case (because the existance of an activated relevancy indicator is "driving" change marks in WWI reports) end user need their "time" to understand how to use properly this usage.
Further on they should be familiar in how to use the output variants (because using them you can get an fast overview about there a active indicator is missing etc.)
With best regards
C.B.
PS: additionally: the usage on the level of the identifier is "special" in some sense. Keep in mind this (especially in WWI reports). The reason is that the usage on the identifier has been created with EH&S 2.7. So in principle: you need not to use the usage to print a identifier in a WWI report but you should do that (because by using the usage you can additionally control the access rights of users).
PPS: one "strong" pro in my opinion to use the "active" option is this:
If you enter e.g. a source or a user defined text in the data record this information is normally not used in a WWI report. Therefore if you haven't "activated" this in customizing the user must ! set the acitve indicator once again. This means: Any ! change in data record (together with save) will remove the active indicator by standard (without using the three check boxes).
Edited by: Christoph Bergemann on Mar 21, 2010 8:02 AM
Edited by: Christoph Bergemann on Mar 21, 2010 8:05 AM
Edited by: Christoph Bergemann on Mar 21, 2010 8:06 AM
Edited by: Christoph Bergemann on Mar 21, 2010 8:06 AM

Assessment in the value assignment type

Dear all,
May I know what is the usage on the following assessment in the value assignment type section:
0 Not Assessed
1 Valid w/o restriction
2 Valid with restriction
3 Invalid
4 Cannot Asseed.
Why we need those assessment for each of the VA instance, what is the usage?
Thanks
YY

Hi,
Assessment tab is used to comment on the quality of the data the VA holds, you can say it as "not assessed" if its not checked by anyone,cannot be assessed likewise use other options.

Sorting of value assignment types

Hi
Is there any way out for sorting already created custom value assignment types. As there is requirement to rearrange the tabs in Incident screen (CBIH82)
Currently value assignment types have been sorted alphabetically, and if we change the name of class and value assignment types for rearrangement, it may have larger impact because of its current assignments/usage.
Is there any other mechanism to sort them.
Regards
Vikram

Thanks Neeraj
But i am bit worried for changing the name of VAT, as existing VAT has been used in various custom programs. It may hamper/impact those programs.
I may have to look for some other work around or i have to do some impact analysis to find all the custom programs which can be affected due to change in name.
Regards and Thanks
Vikram

Inferring return value assignment types - ever seen this ?

Consider a class designed to hold arbitrary values defined at runtime. It is backed by a Map<String,Object> and values are stored and retrieved by a String identifier. Basic type checking is also performed.
Setting the values is straightforward: obj.set(name, value) but I have two candidates for syntax of getters.
First an example of the obvious approach, where getInteger(…) performs type checking, casting and explicitly returns an Integer:
Integer id = obj.getInteger("id") ;This is ok but I discovered a more consice syntax that works without without explicitly naming a type nor sacrificing type safety any further:
Integer id = obj.get("id") ;In this approach we use a generic method, where the return type is inferred and passed to the method. Here's how I do it:
// root method that is called by both approaches
private <K> K _get(String name, Class<K> clz) {
Object value = map.get(name) ;
// check for null, assignability, etc.
if (!clz.isAssignableFrom(value.getClass())) {
throw new RuntimeException(clz + " is not assignable from " + value.getClass()) ;
return (K) value ;
// method 1 - the obvious way
public Integer getInteger(String name) {
return _get(name, Integer.class) ;
// method 2
public <T> T get(String name, T...ts) {
if (ts.length > 0) throw new RuntimeException("Illegal usage...") ;
return (T) _get(name, ts.getClass().getComponentType()) ;
}This works becaues type T is used for both the var-arg array and the return value. Of course, it probably fails if you provide additional args - you're not supposed to. ts.getClass().getComponentType() returns the type you are assigning the return value to.
Not many languages can take this into consideration. In a way, it makes the return type part of the signature.
Advantages:
- Much smaller API
- Dynamic extension for use with a new datatype doesn't require adding a new getX() method
- Members can be treated uniformly, such a through iteration
Disadvantages:
- Involve the confusing zero-length var-args in the api that must be ignored
- Type is inferred to be Object when the return value is not assigned
At first you might think that the method 1 is more type-safe but in fact it is not. Using method 1 you have to align the method with the assignment type, but you can still exception at runtime. In method2 the datatype is simply inferred.
I'm interested in your thoughts on this teqnique. Please let me know if you have a way of concealing the var-args oddness. I think this technique could complement various patterns quite well, such as factory.
Thanks for your input.
Edited by: crackleOK on Jul 21, 2009 4:46 AM

crackleOK wrote:
JoachimSauer wrote:
The only redeeming quality is that it can be very nice to use such code.API's are to use (and often have ugly guts). Unfortunately true, but not a good reason to write ugly implementation code. If you only care about code quality up to the API, then you only care about the shiny coating of your car as well and don't mind the rust as long as you don't see it.
As I said: sometimes the tradeoff is worth it, but it should still be weighted.
Also: the ignorable varargs parameters are not needed in any way whatsoever.Please explain.From what I see you can replace this method:
public <T> T get(String name, T...ts)
// with
public <T> T get(String name)without any loss of functionality.

No error message when incorrect account assignment type K in PO

Hello,
When creating a PO with any raw materials, I can either enter K in the account assignment type, either let the field blank.
If there is no assignment the system will use key EIN to make the posting, if there is an assignment K (compulsory for services for instance), the system will use key VBR.
In this case (raw material), I do not want the users to be able to save their PO if the account assignment has been entered in the item (only blank account assignment type for materials dealt with in stock and value).
Does anyone have a solution?
Best regards,
Ronan

Hi,
This means ERS is active in your system.
What this means is that when you do a GRN, an ERS flag is activated in the PO header. The ERS is then settled using the PO data in SRM.
If you have not settled this (at least this is what is indicated from the message), then uncheck this flag in the PO header and then try and archive.
Cheers.

Notification Assignment Type Issue - SAP Work Manager 6.0

Hello Experts,
We are not able to download notifications on the device for header level work center that is assignment type = 5.
We have done the below configuration.
- added the user parameter for work center in user profile.
- changed assignment type to 5 in Notification MDO.
Same configuration is working properly in case of work orders only change is assignment type set to 8 and changed in client global value Wo.AssignmentType to 8.
There is no configuration guide available which explains notification assignment types in SAP Work Manager 6.0.
Any help would be appreciated.
Regards,
Abhishek
Tags edited by: Michael Appleby

Hi,
In the notification MDO data filter, you also need to add a filter to the WORK_CNTR field. It should be user parameter type, with value "VAP".
Also, from memory, I had to disable some other filters that were set out of the box. These were filtering out my data.
Hope that helps
Michael

Agentry Work Manager 6.0: BADI to enhance assignment type

Hi,
I have the requirement to more or less combine the work order assignment types 1 and 2. I have to fetch the operations based on its assigned personal number, but at the same time I have to fetch a work order and all the operations if the Agentry user is the work order header responsible.
Unfortunately this is a single value parameter so I set the assignment type to 2. Now I thought it would be really easy to fetch the work orders based on the assignment type 1 since there is a BADI available after each assignment call method:
WHEN '2'.                                           "Operation level
           me->get_assignment2(
             EXPORTING
                iref_rfc_oo_data = iref_rfc_oo_data
             IMPORTING
                et_return        = lt_return
                et_wo_object     = lt_wo_object ).
           IF NOT gref_badi_wo IS INITIAL.
             CALL BADI gref_badi_wo->get_assignment_type2
               EXPORTING
                 iref_mdo_data = me->oref_mdo_data
               CHANGING
                 ct_wo_object = lt_wo_object.
           ENDIF.
So inside the BADI gref_badi_wo->get_assignment_type2, I wanted to call the me->get_assignment1 method, and then join the 2 internal tables values.
But the problem is once the BADI is called it is not possible to call this method since we only have the OREF_MDO_DATA object which has the original class as a inaccessible private attribute. I could try to copy and adapt the me->get_assignment1 code but there are some attributes that are not accessible inside the BADI. Do you see a simple and elegant solution to this requirement?
I would like to avoid creating a new Z handler class inheriting from the standard one...
Thank you.
Tags edited by: Michael Appleby

Hi,
I just wanted to close this old thread since what I did long ago to solve the issue is to replicate the me->get_assignment1 inside the me->get_assignment2 BADI method code. It is not just a copy paste since from the BADI you don't have access to some MDO handler private data.
But it is possible to replicate all the fetch process except when doing a delta with exchange since I couldn't easily get the necessary data from the main MDO. But even if you get all the work orders ID's, after the BADI the standard code checks the exchange table again and rules out the unnecessary WO ID's.

Acount Assignment Type field on ME23N

Hi all,
As my understanding Account Assignment Type field (ORT_ACCIT-CO_KAAUF) is on Tcode ME23N.
Please let know how to see value of this field through Tcode ME23N.
Thanks,
Khanh

Hi Khanh,
You can see the values of Account Assignment Categories in Purchasing Document master data in T163K-KNTTP.
Related to PO Items this value is available in EKPO-KNTTP.
Regards,
Anil.

Query on Service Order Assignment Type in CRM Service Manager

Hi All,
This query is regarding the Service Order Assignment type in CRM Service Manager.
While fetching the service orders from SAP, the ServiceOrderFetchBAPI calls the ServiceOrderAssignmentTypeDelegateFactory class
ServiceOrderAssignmentTypeDelegateFactory class contains {
1. public static String ASSIGNMENT_TYPE_GLOBAL = "ServiceOrder.AssignmentType";
      public static String SECTION = "APPLICATION_CONFIG";
Question 1: Please explain about both the String values, Are these two values being fetched from the sap config panel ? If yes then please elaborate where can I check their respective values in SAP.
2. The method getAssignmentTypeDelegate compares each values and returns the respective assignmentTypes
public static ServiceOrderAssignmentTypeDelegate getAssignmentTypeDelegate(User user, SAPObject sapObject, BAPI bapi)
    throws Exception
    String assigmentType = user.getPropertyValue(SECTION, ASSIGNMENT_TYPE_GLOBAL);
    if (assigmentType.equalsIgnoreCase("1"))
      ServiceOrderAssignmentTypeDelegate assignmentTypeBAPI = new ServiceOrderByResourcePlanning(user, sapObject, bapi);
      return assignmentTypeBAPI;
    if (assigmentType.equalsIgnoreCase("2"))
      ServiceOrderAssignmentTypeDelegate assignmentTypeBAPI = new ServiceOrderByPartnerResponsible(user, sapObject, bapi);
      return assignmentTypeBAPI;
    if (assigmentType.equalsIgnoreCase("3"))
      ServiceOrderAssignmentTypeDelegate assignmentTypeBAPI = new ServiceOrderByMultiResourceScheduling(user, sapObject, bapi);
      return assignmentTypeBAPI;
    if (assigmentType.equalsIgnoreCase("4"))
      ServiceOrderAssignmentTypeDelegate assignmentTypeBAPI = new ServiceOrderByAccount(user, sapObject, bapi);
      return assignmentTypeBAPI;
Based on the values a new class is instantiated and it mentions their filter range to be set in BAPI
For ServiceOrderByResourcePlanning -
public void setParameters(SAPObject obj)
    throws Exception
    String partnerGUID = this._serviceOrderComponentManager.getPartnerGUID();
    this._bapi.setFilterRange("IT_LRP_RESOURCE_GUID_RA", "I", "EQ", partnerGUID, "");
For ServiceOrderByPartnerResponsible -
public void setParameters(SAPObject obj)
    throws Exception
    String partnerGUID = this._serviceOrderComponentManager.getPartnerGUID();
    this._bapi.setFilterRange("IT_PARTNER_GUID_RA", "I", "EQ", partnerGUID, "");
For ServiceOrderByMultiResourceScheduling -
public void setParameters(SAPObject obj)
    throws Exception
    String partnerGUID = this._serviceOrderComponentManager.getPartnerGUID();
    this._bapi.setFilterRange("IT_LRP_RESOURCE_GUID_RA", "I", "EQ", partnerGUID, "");
For ServiceOrderByAccount -
public void setParameters(SAPObject obj)
    throws Exception
    for (GUID object : this._accounts)
      String guid = object.getGUID();
      this._bapi.setFilterRange("IT_ACCOUNT_GUID_RA", "I", "EQ", guid, "");
Question 2 : Why the filter range in ServiceOrderByMultiResourceScheduling (MRS Scheduling engine ) is set as - this._bapi.setFilterRange("IT_LRP_RESOURCE_GUID_RA", "I", "EQ", partnerGUID, ""); ? If we see the ServiceOrderByResourcePlanning also has the same filter range - this._bapi.setFilterRange("IT_LRP_RESOURCE_GUID_RA", "I", "EQ", partnerGUID, "");
If these are two different scheduling engines then the table names should be different both in case of MRS and LRP ? Please clarify and explain
Please Explain
Thanks and Regards
Neha Mahanty

Neha,
Got these answers back from the programmer:
Answer 1: Yes, this is being
fetched from the Mobile application configuration parameters as shown below.
The value is configured by a rule to look up to the Service Order MDO
Assignment type filter.
Answer 2: Yes, MRS and LRP are
different scheduling engines, but since the client does not have all the user
information regarding MRS (i.e the resource information), we set the partner
GUID for both. SAP backend ABAP code will determine resource based on the
partner GUID and will call the respective handler for MRS and LRP to retrieve
the service order assignments. Currently Service Manager 4.0 code does not
support MRS with the provided add on.
Jason Latko - Senior Product Developer at SAP

SRM7 - Account Assignment Type

Hi,
We are finding the account assignment type field to be a bit problematic when creating the PO. First it defaults to "Unknown", even when we select cost centre. There is no default set in PPOMA_BBP,
We have to select it twice, then sometimes we cannot edit it at all and other times if we delete a line it still checks the value.
Anybody else experience this? I notice each time its changed it seems to run the CHANGE badi, can we disable this.
Thanks
Tony

Hi Tony,
If you are not using "Unknown" account assignment, it is better to grey it out through webdynpro development. Please check the following:
Webdynpro component: /SAPSRM/WDC_DODC_SC_I_LIM
Elements:
Regards,
Ravi Pachauri

How to dynamically assign type to a field-symbol?

Hi,
I have two fields in one table, one for field name and one for table name. These can be fields in different
tables. I need to fetch value of this field in that table. So the type of this variable can change dynamically.
I am trying to assign type of this field dynamically to a field-symbol. I have to use this field symbol in a
select statement. Currently it is showing a dumb, as the field type is dec7. For some other types it is
working fine.
Regards,
Sunil

Hi all,
I have the same problem.
I tried with your helps but i can't fix them.
A message is raised "Field <fs_bet> unknown" when i used code below
FIELD-SYMBOLS: <fs_bet> TYPE any.
DATA: c_bet TYPE string.
DATA it_0008 type STANDARD TABLE OF pa0008 WITH HEADER LINE.
DO 40 TIMES.
CONCATENATE 'BET0' index into c_bet.
ASSIGN (c_bet) to <fs_bet> CASTING TYPE pad_amt7s .
select * from pa0008 into it_0008
     where <fs_bet> = '1000'
     and pernr = 32.
     append it_0008.
ENDSELECT.
ENDDO.
Please help me to solve it.
Thanks so much,
Sophie Tran

Specify Account Assignment Types

Hi all...
Document split is active.
I am re-examing Account Assignment Types..
Additional Account Assignment Objects - Specify Account Assignment Types
So far I have only entered TT 100 for KOSTL for the relevant Depreciation areas
BUT retirement and depreciation transactions have all worked as expected despite not having TT entered.
IE TT 200 has not been entered in Specify Account Assignment Types but the Retirement transactions complete as expected.
So my question is whether it is necessary to enter all required TTs in the Specify Account Assignment Types?
If it is "correct" to enter them, how are the account assignments types used.
Would a rule of thumb be:
Balance Sheet accounts = APC Values Posting
Depreciation accounts = Depreciation Run.
Thanks...

Hi Thom,
no, you only need a generic transaction type " * ".
Example for KOSTL:
KOSTL Cost Center * Generic Trans. Type#Periodic Posting
KOSTL Cost Center * Generic Trans. Type#Account Assignment for Deprec
Regards Bernhard

Assigning value assignment types to prop tree

Similar Messages

Maybe you are looking for