Select the procedure steps to be packaged in the load module from the list of all the unpackaged procedure steps defined for the business system. You do not explicitly package action blocks. By adding procedure steps to the load module, all action blocks used by the procedure step are also included in the load module, as well as all action blocks used by the action blocks.
An application usually runs most efficiently when each load module contains procedure steps that are likely to be used together. Flow definitions are independent of packaging options. When you create a Dialog Flow Diagram you do not need to consider how the procedures will be packaged. Likewise, packaging is not dictated by the Dialog Flow.
Downstream Effects: When generating for remote installation, each load module becomes a separate remote file and is linked on the target system into a separate executable module. The Referential Integrity modules are packaged into a single remote file. The DDL associated with an application is packaged as a single remote file.
You can use the Filter feature to control the display of the unpackaged procedure steps.
|
Copyright © 2013 CA.
All rights reserved.
|
|