SAP MII Transaction Extension
The MII_TRANS_EXT
activity invokes a custom transaction written in SAP MII. The call to SAP MII is made using the local EJB interface. As a result, the execution occurs within the existing SAP NetWeaver transaction context.
The MII_TRANS_EXT
activity can be assigned as an extension in Service Extension Maintenance
or as a hook point activity.
For more information, see Example: Writing, Configuring, and Executing a Service API Extension and Example: Writing, Configuring and Executing a Hook Extension.
Rules
The following table describes activity rule settings that you can change for this activity in Activity Maintenance
:
Rule | Setting |
|---|---|
| The name of SAP MII transaction input parameter that is used to pass the XML representation of the service API input DTO. The default value: |
| The name of SAP MII transaction output parameter that is used to return the XML representation of the service API output DTO. It is used when the SAP MII transaction needs to modify the input DTO. The default value: |
Options
The following table describes options that you can set in Service Extension Maintenance
to change the behavior of this activity:
Option | Description |
|---|---|
| Parameters that are passed to the SAP MII transaction. Each parameter assignment must be separated by a semicolon. For example, |
| The parent transaction folder name and the name of the SAP MII transaction. For example, |