Node names can be determined automatically via generation methods. As soon as a generation class is entered for the object type Header, the rule name will no longer be editable.
QPPD has a customizing table ( Specification types/item categories → Name generation ) that enables simple constructs to be mapped. 

SAP does not support a normal space as a separator between elements at this point: this is ignored and the different subparts of the name are concatenated without a space.

However, you can use a protected space (Alt-0160 ' ' ), alternatively, an underscore ( Alt-095 '_' ) to work around this problem.

The class /SCT/QP_CL_GEN_HDR can be used for this purpose. To be able to map more complex name structures, a custom generation class can be used (see Generation of Names and Descriptions (P))

To be able to generate a language-dependent rule description, a customer-specific generation class is necessary.

Example

For the DEMO_BASIC regulation type, the generation class /sct/qp_cl_gen_hdr is entered at the HEADER object type:

image-20240409-084133.png

The following entries have been made under Name Generation:

image-20240409-084156.png

That is, the regulation name is composed of (the order comes from the column 'No.')

  1. A constant 'DEMO-'

  2. The value (= VALUE column) of the DEMO_NAME element on the 'PROPERTIES' tab.

  3. A constant '-' 

  4. The value of the DEMO_DATE element on the 'PROPERTIES' tab

On the system, it looks like this:

image-20240606-064218.png

If 'GENERATION' is entered as the name and '25.12.2022' as the DEMO_DATE, the specification name will be generated automatically: "DEMO-GENERATION-20221225".

The name is then no longer ready for input because it is set by generation. 

The output of the values in the name is unconverted (the date is output in the regulation name as 20221225, but in the object type it is automatically converted in a user-friendly format: 25.12.2022).

Thus the generated content is language-independent.