Kontakt

Ansicht
Dokumentation

CTO_ORDERS_GET_AIM_META_DATA - Get AIM meta data for a set of transport requests

CTO_ORDERS_GET_AIM_META_DATA - Get AIM meta data for a set of transport requests

Vendor Master (General Section)   rdisp/max_wprun_time - Maximum work process run time  
Diese Dokumentation steht unter dem Copyright der SAP AG.
SAP E-Book

Funktionalität

The function module receives a set of transport requests as input (IT_REQUESTS). From these requests, it extracts the set of XPRAs and transport objects triggering an after-import-method (AIM). It then calls the AIM repository to find out which tables are read and written by the AIMs and XPRAs triggered by the transport requests.
The set of accessed tables is returned in parameter ET_TABLES.

Importing Parameters:

  • IT_REQUESTS: Set of transport requests to be inspected. The transport requests must exist in the tables E070, E071, E071K.
  • IT_SKIP_METHODS: A set of after import methods that shall be ignored. I.e. the tables accessed by these after import methods will not be returned. Only the columns METHOD and METHOD_FB of the parameter table must be filled. All other columns will be ignored.
  • IV_IS_UPGRADE: Usually, this module is called by upgrade or update procedures. Sometimes, the set of tables accessed by an AIM or XPRA depends on whether the AIM or XPRA is executed within an exchange upgrade or any othe type of update. If it is called by an exchange upgrade, then this parameter shall be ABAP_TRUE.
  • IT_START_RELEASES: Whether an AIM or XPRA is enabled for zero-downtime-upgrades or -updates can depend on the start release of the upgrade/update. If the module is called by an upgrade or update procedure, then this parameter shall contain the start release vector of the upgrade or update.
  • IV_CHECK_START_RELEASES: Indicates whether the function module shall check if after-import-methods or XPRAS are enabled for the start release given in parameter IT_START_RELEASES. If the parameter is ABAP_FALSE then IT_START_RELEASES will be ignored.
  • IV_ADJ_LOCK_MODE_TO_START_REL: If an AIM or XPRA is not ZDO enabled for a certain start release given in IT_START_RELEASES then the module will report this AIM or XPRA as not enabled for zero-downtime upgrades. This will cause an upgrade or update procedure to stop with an error message.
    If IV_ADJ_LOCK_MODE_TO_START_REL is ABAP_TRUE, however, AIMs and XPRAS that are not enabled for the start release given in IT_START_RELEASES will be reported as ZDO-enabled. But the LOCK_MODE values of all tabes accessed by these AIMs or XPRAs will be changed to X (write access to the complete table is blocked on the production subsystem, i.e. the bridge or the blue system).
  • IT_FORCED_XPRAS: A set of XPRAs that are not contained in the transport requests given in IT_REQUESTS but which shall be inspected anyway.
  • IV_IGNORE_TP7_AIMS: There are AIMs that are executed in the TP7 step. These AIMs are not ZDO enabled. If this parameter is ABAP_TRUE, then the module will ignore these AIMs and wll not report an error even though the AIMs are not ZDO enabled.

Exporting Parameters

  • ET_TABLES: Set of tables read- or write-accessed by the AIMs or XPRAs contained in the transports given in IT_REQUESTS. For each table, an ACCESS_TYPE and a LOCK_MODE is returned.
  • ET_TABLES_ERR: Tables that will be accessed by AIMs or XPRAs but which have contradicting LOCK_MODE values in the AIM repository. If this parameter is not empty, this should be considered an error that causes an upgrade or update procedure to stop with an error message..
  • ET_MESSAGES: Error messages collected during the processing of module.
  • ET_HDI_CONTAINERS: HDI containers that are updated by an AIM or XPRA.
  • ET_METHODS_BRDGE, ET_XPRAS_BRIDGE: ZDO enabled AIMs and XPRAs. These can be executed on the upgrade server of ZDO or on the green system of SOI or VZDO.
  • ET_METHODS_PORT_PROC, ET_XPRAS_POST_PROC: Non-ZDO-enabled AIMs or XPRAs that must be executed in post processing. Since usually no AIM/XPRA execution is allowed in post processing, it should be considered an error if one of these parameters is not empty.
  • ET_METHODS_SHADOW, ET_XPRAS_SHADOW: AIMs or XPRAs that can already b executed in the shadow phase of a ZDO upgrade.
  • ET_METHODS_DOWNTIME, ET_XPRAS_DOWNTIME: Non-ZDO-enabled AIMs or XPRAs that must be executed in the downtime. Since usually no AIM/XPRA execution is allowed in the downtime, it should be considered an error if one of these parameters is not empty.

Beispiel

Hinweise

Weiterführende Informationen





Parameter

ET_HDI_CONTAINERS
ET_MESSAGES
ET_METHODS_BRIDGE
ET_METHODS_DOWNTIME
ET_METHODS_POST_PROC
ET_METHODS_SHADOW
ET_TABLES
ET_TABLES_ERR
ET_TAB_METHS_BRIDGE
ET_TAB_XPRAS
ET_XPRAS_BRIDGE
ET_XPRAS_DOWNTIME
ET_XPRAS_POST_PROC
ET_XPRAS_SHADOW
IT_FORCED_XPRAS
IT_REQUESTS
IT_SKIP_METHODS
IT_START_RELEASES
IV_ADJ_LOCK_MODE_TO_START_REL
IV_CHECK_START_RELEASES
IV_IGNORE_TP7_AIMS
IV_IS_UPGRADE

Ausnahmen

Funktionsgruppe

SCTO

CPI1466 during Backup   General Data in Customer Master  
Diese Dokumentation steht unter dem Copyright der SAP AG.

Length: 5506 Date: 20240523 Time: 150420     sap01-206 ( 109 ms )