The following procedure explains how to add transaction codes and source member names after packaging at least one load module. You can use the Complete option to provide source member names and transaction codes automatically. However, the naming scheme used by the Complete option may not provide the best transaction code names for the application.
Follow these steps:
This displays a list of business systems in the model.
This displays the list of packaged load modules in this business system. If you receive an error message indicating that no such objects exist in the model, none of the procedure steps have been packaged into load modules.
Detail information appears in the Load Module Detail window.
The Trancode Maintenance window appears. If no transaction codes have been specified this list is blank. You will need to add a transaction code for each procedure step within this load module, and any that you know you will package later.
Note: This action creates a list of transaction codes for this load module only. It does not assign the created transaction codes to the procedure step(s) packaged in the load module. That is done in a step that appears later in this procedure. You must create a transaction code list for each load module in the business system.
|
Copyright © 2013 CA.
All rights reserved.
|
|