Configuring a BAPI stage

The BAPI stage handles data input and output by using either links or files. The column schema of the links is created automatically while configuring the BAPI stage and is inferred from the schemas of the BAPI parameters.

About this task

Using links for both input and output is the recommended approach as it allows more freedom in designing the job. The file-based approach is supported for downward compatibility. The input link contains either the BAPI import or the input table parameters or both. The output link contains either the export parameters or the output table parameters or both.
Notes:
  • Legacy job design uses only an input or output link for BAPI (for example, BAPI->Peek). A file is used to pass the input parameters to BAPI (Input.txt). If no import parameters are used, the user still needs to created an empty file.
  • Active job design, with both input and output links for BAPI (for example, RowGen->BAPI->Peek) does not use the parameter file, input parameters are passed through input link. Similarly instead of just using log files, output goes to output link. This is the recommended job design.

Procedure

  1. Create a BAPI stage with one input link and one output link connected to other stages.
  2. Open the BAPI stage.
  3. Configure the BAPI stage properties.
  4. Review the column schema created from BAPI metadata.
    Note: If extracting non-Unicode data, see http://www.ibm.com/support/docview.wss?uid=swg21392917