Assigning New Property Tree to Specification Types
Business Scenario:
Here we are creating a Specification type and a property tree with new Value Assignment Type (VAT). The newly created property tree is then assigned to Specification Type.
Detailed configuration steps with screen shots are given below as per Business Requirement.
1. Create Specification Type.
Create a Specification Type to create a new specification.
|
IMG Menu |
Environment, Health & Safety – Basic Data and Tools – Specification Management – Specification Master – Specify Specification Types |
|
Transaction Code |
SPRO |
Copy the standard Specification Type Real_Sub as Real _Sub1. We need to assign the Real_sub1 to the specification category SUBSTANCE.
2. Create Characteristics and Class.
Create the Characteristics ”CLAS_SAMPLE” by using t_code CT04 and assign the below mentioned characteristics to it by using t_code CL02
|
Characteristics |
Description |
Data Type |
|---|---|---|
|
P_EHS_1021_001_PERIOD |
Storage Period |
NUM |
|
SAP_EHS_1021_001_TEMP |
Storage Temperature |
NUM |
|
SAP_EHS_1021_001_MOISTURE |
Storage Moisture |
CHAR |
|
SAP_EHS_1021_001_REMARK |
Remarks |
CHAR |
|
CHAR_SAMPLE |
Sample Name |
CHAR |
3. Create Value Assignment Type
|
IMG Menu |
Environment, Health & Safety – Basic Data and Tools – Specification Management – Specification Database Structure – Settings for Value Assignment – Specify Value Assignment Types |
|
Transaction Code |
SPRO |
Create VAT according to the data given below:
|
Value assign type |
Description |
Value ***. Cat |
|---|---|---|
|
Z_Storage |
Root |
E |
|
Z_Storage_Details |
Node (Without Class) |
E |
|
Z_Storage_Specification |
Normal Property (With Class) |
A |
Creation of VAT “Z_Storage” with Value Assignment Category as E.
Creation of VAT “Z_Storage_Details” with Value assignment category “E”
Creation of VAT “Z_Storage_Specification” with Value assignment category “A” and Class as “CLAS_SAMPLE”
4. Creation of Set up Table-Based Value Assignment
|
IMG Menu |
Environment, Health & Safety – Basic Data and Tools – Specification Management –Specification Database Structure – Settings for Value Assignment – Set up Table-Based Value Assignment |
|
Transaction Code |
SPRO |
In the IMG activity “Set Up Table-Based Value Assignment” you specify the fields of a value assignment type you want to be displayed as columns in the table.
5. Creation of Set up Property Tree
|
IMG Menu |
Environment, Health & Safety – Basic Data and Tools – Specification Management – Specification Database Structure – Settings for Value Assignment – Set Up Property Trees |
|
Transaction Code |
SPRO |
- Make the following entries:
|
Prop. tree |
Description of property tree |
Version |
|---|---|---|
|
Z_STA_SUB |
Standard Properties Substance |
ERP60 EHP4 |
2. Choose Z_STA_SUB then choose Value Assignment Type Assignment and make new entries:
|
ID |
level |
Comprlnd. |
Value Assignment type |
|---|---|---|---|
|
1000 |
1 |
|
Z_Storage |
|
1010 |
2 |
X |
Z_Storage_Details |
|
1020 |
3 |
X |
Z_Storage_Specification |
6. Assign Property Tree to Specific Specification Types
|
IMG Menu |
Environment, Health & Safety –Basic Data and Tools – Specification Management – Specification Master – Specify Specification Types |
|
Transaction Code |
SPRO |
On Specification Type – Property Tree Assignment tab screen select and enter Z_STA_SUB for the listed Specification Type:
Finally go the specification workbench and select the agent with agent type (Real Sub_1), here we need to select the property tree (Z_STA_SUB) from the list to enter the data.
Regards
John Zacharia
Dear John
very well done. Great job. Go on like that. 🙂 😎
Please extend your explanations for community to provide step by step process how the settings as shown by you will be "transported" from Dev to Prod and which pitfalls can happen (and there are many !)
By the way: your documentation contains one small "issue". Regarding Value Assignment Type "E" you need not to assign an "usage profile". Any usage profuile used must be present in customizing.
Please enhance the section of "property tree". The use of the "Comp" flag is not well understood but it is a very important flag.
Please make sure that audience understand that in your example only the "new" property tree is available for REAL_SUB1; you can not "switch" to different one.
If you have some time: The flags:
does have some impact in maintenance in EHS and as in your example the settings done will speed up maintenance. May be you could explain the use of the flags to the audience.
May be extent your documentation in such a way:
In CG02 if you click F1 on level of property you can get a "help" to the user. This help is prepared during the set up as shown by you. May be it could be of interest for the audience how this help can be created and maintained
C.B.
Hi John,
Excellent Preparation. Good Job!!!!!!!!!!!!!!!
Thanks Edward 🙂
Dear John
Good Job. Very useful and Key step in EH&S Pratice
Balajee
Nice work John!
Simple and useful!
Dear John,
Great Job. Very useful and Key step in EH&S Practice.
Naveenn
Hi John,
Thanks for the tutorial. I have a doubt, in my minisap, I don't have the option 'Specify Agent Types'. How do I get install that?
I would appreciate your help,
Thanks in advance,
Dear Dnaiel
if you have only "Minisap" then you have only ABAP basic functionality. You need a "IDES" system to use e.g. EHS, MM, SD etc.
C.B:
Hi Gurus,
I have created a new spec type and also added VAT and characteristics to it. Problem is, when user enters data and saves it, the data entered is getting disappeared. Please help here!
Hi Keerthi S B,
The problem is that , when you view the contents in the table TCLA, for class type(KLART) 100, which is for ESTVA, you will see that the column 'MUTLIPLE OBJS' is ticked or 'X' is filled. You will need to remove that 'X'. To do that, do the following steps:
(1) Click on row and click display.
(2) Start Debugger, by entering /h.
(3) Press enter and the debugger will start.
(4) Now, edit the value of the variable CODE. From 'show' to 'edit'.
(5) Now the table row will be editable, and you can remove the 'X' in the column 'MUTLIPLE OBJS'.
(6) Now all the disappeared values should reappear.
Regards,
Sandeep