HCL Workload Automation, Version 9.4

Importing ABAP/4 function modules into SAP R/3

How to generate, activate and commit new ABAP/4 modules to a SAP R/3 system.

About this task

This section describes the procedure to generate, activate, and commit new ABAP/4 function modules to your SAP R/3 system and several new internal tables. You do not modify any existing SAP R/3 system objects. For information about the supported SAP R/3 releases, see the System Requirements Document at https://workloadautomation.hcldoc.com/help/topic/com.hcl.wa.doc_9.4/distrDDguides.html.

The number of ABAP/4 modules that you install with the import process varies from release to release. The modules are installed in the TWS_home\methods directory and have the following file names and format:
  • K9000xx.TV1 (function modules for standard jobs scheduling extensions)
  • K9007xx.TV1 (function modules for IDoc monitoring and job throttling)
where x is a digit generated by the SAP system.

To import ABAP/4 function modules into SAP R/3:

Procedure

  1. Change to the following directory:
    cd /usr/sap/trans/bin
  2. Add the transport file to the buffer:
    tp addtobuffer transport sid
    where:
    transport
    The transport request file.
    sid
    The SAP R/3 system ID.
    For example, if the transport file in the TWS_home\methods directory is named K9000xxx.TV1, the transport request is tv1K9000xxx.
  3. Run the tp tst command to test the import:
    tp tst transport sid

    After running this command, examine the log files in the /user/sap/trans/log directory for error messages. Warnings of severity level 4 are normal.

    If there are errors, check with a person experienced in correction and transport, or try using unconditional modes to do the import.

  4. Run the following command to import all the files in the buffer:
    tp import transport sid

    This command generates the new ABAP/4 modules and commits them to the SAP R/3 database. They automatically become active.

    After running this command, examine the log files located in the /user/sap/trans/log directory for error messages. Warnings of severity level 4 are normal.

    If a problem is encountered, use unconditional mode when running this step:
    tp import transport sid U126
  5. When the import is complete, check the log files located in the /usr/sap/trans/log directory to verify that the ABAP/4 modules were imported successfully.
    If you apply the standard transport and the IDOC transport, 26 ABAP/4 modules are installed by the import process. For a list of the transport files to be used, refer to Importing ABAP/4 function modules into SAP R/3. Table 1 lists the ABAP modules installed.
    Table 1. ABAP/4 modules installed
    ABAP/4 module Installed?
    ENQUEUE_/IBMTWS/EQ_XAPPL
    DEQUEUE_/IBMTWS/EQ_XAPPL
    /IBMTWS/UNREGISTER_XAPPL
    /IBMTWS/GET_XAPPL_REGISTRATION
    /IBMTWS/MODIFY_JOB_CLASS
    /IBMTWS/REGISTER_XAPPL
    J_1O1_BDC_STATUS
    J_1O1_DATE_TIME
    J_1O1_IDOC_SELECT
    J_1O1_JOB_ADJUST_CLIENT
    J_1O1_JOB_FIND
    J_1O1_JOB_FINDALL
    J_1O1_JOB_HAS_EXTENDED_VARIANT
    J_1O1_JOB_LOG
    J_1O1_RAISE_EVENT
    J_1O1_REPORT_ALL_SELECTIONS
    J_1O1_REPORT_GET_TEXTPOOL
    J_1O1_VARIANT_COPY
    J_1O1_VARIANT_CREATE
    J_1O1_VARIANT_DELETE
    J_1O1_VARIANT_EXISTS
    J_1O1_VARIANT_GET_DEFINITION
    J_1O1_VARIANT_GET_HELP_VALUES
    J_1O1_VARIANT_MAINTAIN_CNT_TBL
    J_1O1_VARIANT_MAINTAIN_SEL_TBL
    J_1O1_VARIANT_MODIFY
    Table 2 shows the contents of the ABAP modules for the IDoc records and job throttling feature.
    Table 2. ABAP/4 modules contents
    Object Description Used by...
    /IBMTWS/ Type = Development Namespace. For HCL Workload Automation. Internal use only
    /IBMTWS/EQ_XAPPL Type = Lock Object. Synchronizes the job throttler instances and job interception collector jobs that are running against the same SAP system.

    Job throttling
    Job interception

    /IBMTWS/GET_
    XAPPL_REGISTRATION

    Type = Function Module. It is used to query for existing external application registration data in table IBMTWS/XAPPL, for example the registration data of a job throttler instance or job interception collector.

    Job throttling
    Job interception

    /IBMTWS/MODIFY_JOB_CLASS Type = Function Module. Modifies the job class of an intercepted job that is controlled by the job throttler. For details, see Step 3. Enabling job class inheritance.

    Job throttling
    Job interception

    /IBMTWS/REGISTER_XAPPL Type = Function Module. Registers an external application, for example the job throttler.

    Job throttling
    Job interception

    /IBMTWS/TWS4APPS Type = Function group. For HCL Workload Automation. Internal use only
    /IBMTWS/UNREGISTER_XAPPL Type = Function Module. Unregisters an external application, for example the job throttler.

    Job throttling
    Job interception

    /IBMTWS/XAPPL Type = Table. Stores the registration data of external applications. An external application can be a job throttler instance or a job interception collector.

    Job throttling
    Job interception

    J_1O1_IDOC_SELECT Type = Function Module. Selects IDoc records from SAP internal tables. For details, see Defining event rules based on IDoc records. IDoc event rules
    J_1O1_TWS_EDIDC Type = Data structure in FM interface Function module J_1O1_IDOC_SELECT

    J_1O1_TWS_IDOC_
    SELECTION

    Type = Data structure in FM interface Function module J_1O1_IDOC_SELECT

    J_1O1_TWS_STATE_
    SELECTION

    Type = Data structure in FM interface Function module J_1O1_IDOC_SELECT