Output ABAP program page

The Output page ABAP Program tab constructs the properties and operations of an ABAP program.

This includes program generation (formerly done by using the Extraction Object dialog on the Access General page), editing, saving, and validation.

This page has the following components:

  • ABAP Program ID. Enter the program ID as you sequentially define required properties on the tabs on the Output page, from left to right. Otherwise, Program needs ID in ABAP Program Development Status message appears.
  • Generation Method includes three ways to create the ABAP program:
    • Build SQL query. This option (the default) lets you define the data to be extracted by constructing an SQL query. It uses the same SQL Builder interface as that of the other stages and causes Build dialog to open the Build Open SQL Query dialog. This process is described in Building SQL queries description.
    • Build extraction object. When you select this option, Build opens the Build Extraction Object dialog, which disables Options. This method gives you backward compatibility (the dialog is similar to the Extraction Object dialog in the former version). This dialog includes OK and Cancel. Generate ABAP/4 and Connect no longer exist. See Building Extraction objects for more information.
    • Enter program as text. If this option is selected, Build, Options, and Generate Program are disabled. In this case, you can open ABAP Editor (by using Edit Program) to create the program by hand. If you edit a generated program, Generation Method changes to Enter program as text.
  • Build. Opens a dialog to build an extraction object or SQL query, depending on the selection generation method.

    Click to open the Build Extraction Object dialog if Build extraction object is selected as the Generation Method. (Options is disabled.)

    The Build Extraction Object dialog is similar to the Extraction Object dialog in the former version, except it uses OK and Cancel (instead of merely Close), and Generate ABAP/4 and Connect no longer exist.

    Opens the Build Fully Generated Query dialog if Build SQL Query is selected as the Generation Method.

  • Options. Lets you further customize the generated ABAP by opening the Program Generation Options dialog. This option is only available if Build SQL Query is selected.
  • Load Method. Specifies how to load the ABAP program. The options depend on the data transfer method:
    • IBM® InfoSphere® DataStage® job loads the program. The program ready for runtime load message appears as status after program generation. This option will not be available if you have chosen the CTS load method.
    • Current user loads the program from this dialog box.
    • SAP administrator loads the program manually.
  • Delete the program from R/3 after it runs.
  • Run Method. Specifies how to run the ABAP program. Options depend on the data transfer and the load methods.
    • InfoSphere DataStage job runs the program. Selected by default. If the data transfer method is CPI-C, only this option appears. The same limitation applies if you select InfoSphere DataStage job runs the program as the load method.
    • SAP administrator runs the program manually. Appears if InfoSphere DataStage job loads the program option is not selected.
    Note: If you select the Run method DataStage job loads the program at runtime option and the Delete the program from R/3 after it runs option, the job will use the former, non-CTS load function. A message will be written to the log stating that the non-CTS load function is discouraged.
  • ABAP Program Development Status. Displays the following read-only status for the ABAP program you are developing so you know the next step. For example:
    • SQL query needs to be built. Appears when you specify an ID, but the selected Generation Method is Build SQL query, and you need to build the query.
    • Program not used for "Local File" data transfer method. Appears when you select Local File as the data transfer method (everything on this page is disabled).
    • Program needs to be generated. Appears when the program is not yet generated, or if the relevant stage properties differ since the last generation of the program (program generation formerly handled in the Extraction Object dialog).
    • Program needs to be loaded to R/3. Appears if you decline the system offer to load the program.
    • Program needs to be saved to a file. Appears if you decline the system offer to save the program.
    • Program loaded to R/3. Appears after you load the program to R/3.
    • Program saved to file <file path>. Appears after you save the program to a file.
    • Program ready for runtime load. Appears after program generation when Load Method is InfoSphere DataStage job loads the program.
    • Program needs ID. Appears if you need to provide ABAP Program ID.
  • Generate Program. Generates the ABAP program, disabling the button. Build and Options remain enabled if the Generation Method is Build SQL Query. If you click Build or Options, and if the system knows about any program edits since generation-time, you must click Clear Program to delete the existing edited program to use any changes to regenerate the program.

    After generating the program, you can load the program to R/3 or save it to a file, depending on the Load Method setting (unless the setting is InfoSphere DataStage job loads the program). If the program needs to be generated, the development status is Program needs to be generated.

    If you save or load the program, the development status is Program saved to file <file path> or Program loaded to R/3, as appropriate.

    The button is disabled after you generate the program, and all the previously disabled buttons are enabled, including Edit Program and Editor Options.

  • Load Program to R/3. Appears if you need to load the program to R/3.
  • ABAP Workbench. Opens the SAP GUI, replacing Launch SAP GUI on the General page in the former version.
  • Save Program as File. Clear Program, and Save Program as File are the other buttons you see, if appropriate.
  • Edit Program. Lets you edit the program and save the modifications.
  • Editor Options. Opens a dialog that lets you indicate which editor to use to edit the program.
  • Validate Program. Verifies the program syntax. If errors exist, the ABAP editor for the stage opens and highlights the error, similar to validation done from the editor.
  • ABAP Workbench invokes the SAP GUI, (replacing Launch SAP GUI on the General page in the previous version).
  • Load Program to R/3 with CTS. Specifies whether or not that the ABAP program is to be assigned to an SAP Change and Transport System (CTS) package and request before the program is uploaded to SAP.

    The Z_RFC_DS_SERVICE_CTS remote function module enables the ABAP program to be assigned to a CTS package and request. In addition, the Z_RFC_DS_SERVICE_CTS remote function module enforces stricter security by verifying that the SAP user is authorized to upload and run the ABAP program.

    When Load Program to R/3 with CTS is selected, you cannot select the DataStage job loads the program at runtime option or the Delete the program from R/3 after it runs option. If you select either theDataStage job loads the program at runtime option or the Delete the program from R/3 after it runs option, the ABAP stage uses the Z_RFC_DS_SERVICE remote function module at runtime to load the ABAP program to the SAP server.

    Note: When you save the ABAP program to R/3, you might receive a warning if a program with the same name already exists on the R/3 system. You can overwrite the program.

You can also click Load Program to R/3, Save Program as File, Clear program, Edit program, Editor options, or Validate program if appropriate.