1.2 Source File List

This topic provides the systematic instructions on how to prepare a source file.

Prepare a text file with an absolute path.

If all the files are placed in one folder, dos commands (as shown below) can be used to generate the text file.

Z:\FLEXCUBE_Kernel\FCUBS_11.4.0\MAIN>Dir /b /s *_RAD.xml > D:\BulkGeneration\Console.txt

Figure 1-4 Source File list sample

Description of "Figure 1-4 Source File list sample"

Include Call form List

If the user is generating function IDs which has call forms attached to them, then the call form list should be included as a part of the source file list. If the call form is not included, then the generation fails.

If units for call form files are not required to be generated, then call form paths can be prefixed with a Double Hyphen (--). All lines starting with a double hyphen will not be taken up for the bulk generation.

As it is difficult to search and put each call form for individual screens, prepare a call form list upfront and add the files to be generated at the end of the call form list. Even if any of the call forms is repeated in the generation list it won’t affect the generation of that file.

For example, include call form to the source list, --Z:\FLEXCUBE_Kernel\FCUBS_11.4.0\MAIN\AM\RADXML\AMCPRPCL_RAD.xml

If the user is generating a complete RADXML from the baseline area, a call form list is not required.