Product builder learning notes-Reports

This chapter describes several reports of the product generator module.
Composition Element
This report is used to print the content of the product model and to view the overview of the materials that can be modeled. Only product models in the active status are printed.
Operation path
Product Generator -> Reports -> Composition Element

As shown in, you can select to print the details of the product model, and choose whether to include verification rules, operations, and user configuration files. On the right side, you can select the material type and item number. Of course, you can select any condition in the form corresponding to the button.
you can print the Code in three ways:
1. untranslated code.
use the product builder> Settings> translation table to translate keywords in the code. For example, translate
ttsbegin into start transaction
select into fetch data from table.
however, I tested it. The printed code has a large granularity. I can only print the reference of pabsource to other methods (which will be shown later) without the translation of keywords, therefore, I am not very clear about how to create these things in this place. Wait for time to read the Source Code of this report and draw a conclusion.
2. translated code;
3. Description
Print the description about the modeling Tree node? No description can be defined anywhere.
in the preceding three methods, both BOM nodes and process route nodes in the modeling tree are referenced. The actual BOM and process route are printed at the end of the report.
the result of my test is: if the BOM is used as the root node, this print is OK, but if it is included in another node, for example, under an if node, it won't be printed out. This may be related to the code printing granularity, but the parameter controlling this granularity cannot be found in the system, I don't know whether my understanding is incorrect or the Code itself has no intention of implementing the designer. This can only be determined after the code of this report is analyzed. Mark it first.
the output result of the Report is shown in:

The printed results can only be like this for the time being, and the process route does not even have labels. Wait for time to study this report in detail.
Purpose
Operation path:
Product builder-> Report-> Purpose
This report is used to check whether the following elements are used in a product model:
1. specified product
2. Variables
3. Process
4. Work Center
5. Bom
6. Process Route
7. Default route
When you need to delete one of the preceding elements of a variable, you can use this report to check whether the model is referenced by the product model in the system.

User Configuration File
Operation path:
Product builder-> Report-> User Configuration File
You can print out the user configuration file and which users are associated with the user configuration file.