cancel
Showing results for 
Search instead for 
Did you mean: 

Order of symbols in Symbol Tree - CG42

Former Member
0 Kudos

For CG42, editing report templates, has anyone ever had the order of symbols in the Symbol Tree not match the order of the corresponding characteristics in the class?

Example below...as you can see the order between the two do not match. The order in the symbol tree is alphabetical but typically that is not the case. This occurred recently after implementing SP11, SP12, SP13 and SP14 for EA_APPL and running the Adopt Standard Database config.

In CG42, order of symbols in Symbol Tree for Flash Point:

G1014009EP Pressure

G1014009GL GLP

G1014009ME Method

G1014009PP Accuracy

G1014009PR Accuracy

G1014009RE Remarks

G1014009TT Test type

G1014009VA Value

Order of characteristics in class for Flash Point:

SAP_EHS_1014_009_PREC Accuracy

SAP_EHS_1014_009_VALUE Value

SAP_EHS_1014_009_PRESSURE_PREC Accuracy

SAP_EHS_1014_009_EC_PRESSURE Pressure

SAP_EHS_1014_009_TEST_TYPE Test Type

SAP_EHS_1014_009_METHOD Method

SAP_EHS_1014_009_GLP GLP

SAP_EHS_1014_009_REMARK Remarks

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello

The order of symbols in symbol tree are arranged based alphabetically whereas those in property node depends on the way you assign them to class in class - characteristic assignment. As far as creation of template this issue will not create you a problem as there is a clear cut identifiable information on symbol, parameters and also descriptors.

Regards

sapehstrainer

Former Member
0 Kudos

Hi Robin,

the descriptor symbol key entry G10100001AB is made up as follows:

G.................

Letter G (stands for generation)

G1010.........

Four-digit cluster of class key

G1010001...

Class number

for parameter symbols, the nomenclature would be Tables in the SAP component specification management begin with EST (ESTRI, ESTVH). The symbol key for the IDENT field is thus GESTRIDENT (symbol key for identifier). The symbol keys for value assignment types consist of the first four characters of the class key and the first five characters of the characteristic key.

for characteristics keys, it would be like SAP_EHS_1010_001_STREET

Explanations:

SAP_EHS_1010_001..............

Corresponding class key

SAP_EHS_1010_001_STREET

SAP_EHS_1010_001_CONTACT_PART

SAP_EHS_1010_001_CONTACT_DATE

and so on

Specific characteristic component consisting of remaining 14 characters

Regards,

Keshav

Former Member
0 Kudos

Unfortunately that doesn't address the issue I had but SAP created a pilot note to address it, 1282280 (at this time it is still in German).