While building an Inbound/Outbound interface, most of the time we may be in dilemma whether to use Application Engine (AE) or SQR. Here are the tips to build an efficient interface using either AE or SQR.
If we use Application Engine, below points are to be taken into account
- If the interface is INBOUND, its better to go for Application Engine
- If the program fails, we can make use of Restart Control to restart the program from the position where it abends
- PeopleSoft – Business Process related Validation will be taken care automatically when we go for AE/CI.
- Parallel Processing can be easily achieved using AE. This can be done by using Temporary Tables and State Records.
- Reusability of SQLs is very much easy when we go for AE.
- Bulk Insertion of data and Set Processing of data can be easily done in an AE
- COMMIT levels can be maintained either at SECTION or STEP levels
- Generation of Reports using File Layout, Workflow related batch interface can be easily developed using an AE
- XML related processing is quiet easy when we go for AE
- When we go for Upgrade of the Current PS System, Retrofitting of AE is done by easily identifying the impacted objects.
If we are going to use SQR, below points can be taken into account to build an interface
- Formatting of Reports is very much easy in SQR using Begin-Header, Begin-Footer and Begin-Setup commands.
- If we are going to consider the Performance of the Interface Program, its better to go for SQR.
- Better Performance can be achieved by using Load-Lookup Arrays and Dynamic SQL
- Reusability of SQLs can be achieved by creating either generic Procedures or SQCs