You use this workflow to transform and send a message to a destination system (SAP ERP or SAP ME).
The following table describes fields requiring explanation:
Field | Description |
---|---|
| Identifies the type of message received in SAPMEINT, such as |
| Identifies a type of this workflow as |
| A path to the program that handles the workflow. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the workflow handler. |
| The number of times that the system tries to reprocess a message. |
| A path to the program that is used to enhance the incoming message before message transformation. |
| A comma separated name-value pair, which is passed as parameters to pre-XSLT transaction. |
| A path to the program, used to enhance the incoming message before message transformation takes place. If entered, this program takes precedence over the standard pre-XSLT transaction. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the partner pre-XSLT transaction. |
| A path to the program used to enhance the incoming message before message transformation takes place. If entered, this program takes precedence over the partner and standard pre-XSLT transactions. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the partner pre-XSLT transaction. |
| A path to the standard XSLT file that performs transformation of incoming message. |
| A path to the XSLT file that performs transformation of incoming message. This file takes precedence over the standard request XSLT address. |
| A path to the XSLT file that performs transformation of incoming message. This file takes precedence over the partner and standard request XSLT addresses. |
| A path to the standard program used to enhance the message payload after transformation takes place. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the post-XSLT transaction. |
| A path to the program used to enhance the message payload after transformation. If entered, this program takes precedence over the standard post XSLT transaction. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the partner post-XSLT transaction. |
| A path to the program used to enhance the message payload after transformation. If entered, this program takes precedence over the standard and partner post XSLT transactions. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the customer post-XSLT transaction. |
| A path to the standard program that sends the transformed message to the destination system to perform the intended action. For example, creating a material master in SAP ME or recording a yield confirmation in SAP ERP. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the service transaction. |
| A path to the program that sends the transformed message to the destination system to perform the intended action. If entered, this program takes precedence over the standard service transaction. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the partner service transaction. |
| A path to the program, which sends the transformed message to the destination system to perform the intended action. If entered, this program takes precedence over the standard and partner service transactions. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the customer service transaction. |
| A path to the standard XSLT file that performs transformation of the message received as a result of the service transaction. |
| A path to XSLT file that performs transformation of the message received as a result of service transaction. If entered, this file takes precedence over the standard response XSLT. |
| A path to XSLT file that performs transformation of the message received as a result of service transaction. If entered, this file takes precedence over the standard and customer response XSLT files. |
| A path to the standard program used to perform actions after the service transaction is successfully executed. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the pass handler transaction. |
| A path to the program used to perform actions after the service transaction is successfully executed. If entered, this program takes precedence over the standard pass handler transaction. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the partner pass handler transaction. |
| A path to the program used to perform actions after the service transaction is successfully executed. If entered, this program takes precedence over the standard and partner pass handler transactions. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the customer pass handler transaction |
| A path to the standard program used to perform actions after the service transaction fails. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the fail handler transaction. |
| A path to the program used to perform actions after the service transaction fails. If entered, this program takes precedence over the standard fail handler transaction. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the partner fail handler transaction. |
| A path to the program used to perform actions after the service transaction fails. If entered, this program takes precedence over the standard and partner fail handler transactions. |
| A set of one or more comma separated name-value pairs, which are passed as parameters to the customer fail handler transaction. |
| Allows you to save the |
| Allows you to save |