General SAP Process Definitions (Mail)
The described process definitions provide the basis functions for mail and workflow capabilities in Redwood Finance Automation.
FCA_Basic_Mail
This process is of Type mail. It provides all parameters required to send a HTML mail with Attachments. It is mainly used indirectly from the Workflow process definitions.
Parameters
Mx_To Target email addresses (To:). Duplicates will be removed automatically.
MX_Cc Carbon Copy email addresses (Cc:). Duplicates will be removed automatically.
MX_BCc List with BCc addresses. Duplicates will be removed automatically.
MX_ReplyTo Reply To email addresses. Only the first address will be chosen.
Mx_Subject Subject of the email
MX_Urgent Defines urgency of the email
Mail_Attachments List with Attachments. The syntax for attachments is described in section Addressing files.
MX_Body Document containing the Body of the email
MX_Text Document reference containing the Text of the email. This can either contain a reference to a document (beginning with doc: ) or a text for the note which will inserted if the content of this parameter does not match doc: in the beginning
MergeRecord A merge record (for example from a RULE_RESULT parameter) inserted in this parameter creates a table with the columns specified in RecordColumnList.
The table generated from this merge record can be inserted into the MX_Text parameter or document using the ${RecordTable} tag.
RecordColumnList This parameter needs a comma separated list of column names. The amount of columns needs to match the number of fields per record set of the record specified in MergeRecord.
Message1 Variable that can be referenced in email text
Message2 Variable that can be referenced in email text
Message3 Variable that can be referenced in email text
Message4 Variable that can be referenced in email text
Message5 Variable that can be referenced in email text
OperatorMessage Message to be used for the Operator Message
OperatorReply Reply options for Operator Message (Example: ^Confirm|Abort$)
The syntax is:
^<Option1>|<Option2>(|<option x>)$
The result of the option selected will be stored in the parameter O_OMREPLY. This parameter can control other steps in the process with a precondition.
The option Abort will result in the workflow process to fail (status Error ).
All other options will result in the workflow process reaching status Completed.
MX_MailJob Mail process to use for sending the email.
FCA_BDC_Workflow
This process is an extension of the FCA_Workflow.
It is specifically designed for the use within BDC processing processes and offers 4 workflow options:
- Restart
- Ignore
- Abort
- Details
The Abort option will always cause the workflow to go on error state, Restart, Ignore and Continue allow a go-to step (for example Step 1) which will be executed once the workflow is replied to.
In order to activate the go-to step value on these parameters, the status handler of the process definition step needs to be set to a goto step (Usually the same step of the workflow) in order to be processed.
The email Body and Text can use the replacements of the solution. Additionally the message parameters can use replacements as well.
The BDC Workflow requires the process System_UserMessage_Notification which will be unique by partition.
Parameters
**Mx_To ** Target email addresses (To:). Duplicates will be removed automatically.
MX_Cc Carbon Copy email addresses (Cc:). Duplicates will be removed automatically.
MX_BCc List with BCc addresses. Duplicates will be removed automatically.
MX_ReplyTo Reply To email addresses. Only the first address will be chosen.
Mx_Subject Subject of the email
MX_Urgent Defines urgency of the email
Mail_Attachments List with Attachments. The syntax for attachments is described in section Addressing files.
Copy_Attachments Copy the attachments specified to this robot
MX_Body Document containing the Body of the email
MX_Text Document reference containing the Text of the email. This can either contain a reference to a document (beginning with doc: ) or a text for the note which will inserted if the content of this parameter does not match doc: in the beginning
MergeRecord A merge record (for example from a RULE_RESULT parameter) inserted in this parameter creates a table with the columns specified in RecordColumnList.
The table generated from this merge record can be inserted into the MX_Text parameter or document using the ${RecordTable} tag.
RecordColumnList This parameter needs a comma separated list of column names. The amount of columns needs to match the number of fields per record set of the record specified in MergeRecord.
Message1 Variable that can be referenced in email text
Message2 Variable that can be referenced in email text
Message3 Variable that can be referenced in email text
Message4 Variable that can be referenced in email text
Message5 Variable that can be referenced in email text
IN_UM_TEXT Define the text for the usermessage
IN_RESTART_STEP Define the step which will be run on choosing this reply. Syntax is
Step <step number>
IN_IGNORE_STEP Define the step which will be run on choosing this reply. Syntax is
Step <step number>
IN_ABORT_STEP Define the step which will be run on choosing this reply. Syntax is
Step <step number>
IN_DETAILS_STEP Define the step which will be run on choosing this reply. Syntax is
Step <step number>
TRAN This parameter can contain the transaction code of a transaction that is to be executed. Filling this field will automatically generate the execute button at the bottom of the mail.
**TRAN_PARM ** This parameter can contain the parameters which should be filled in the transaction. This can be a comma separate list.
Example: BUKRS=1000,KOKRS=1000
SAP_SYSTEMS This parameter can be set to override the SAP System that was selected for the process. If it is not set, the SAP System of the process will be selected. The transaction link for the TRAN parameter will be created based on the value of this parameter.
CLIENT This parameter can be set to override the SAP Client that was selected for the process. If it is not set, the SAP Client of the process will be selected. The transaction link for the TRAN parameter will be created based on the value of this parameter.
Each mail is delivered with 2 mail templates:
FCA_Mail_Body
FCA_Mail_Body_Webmail
The standard mail body uses css for mail layout and has been optimized for standard mail clients like Outlook.
The webmail body uses inline css and is optimized for webmail clients like gmail.
The notification box in a mail is defined in the Mail Body parameter and contains generic information like the task number, the SAP system and the failed SAP job.
The document note can contain the content of a document or a freely chosen text.
The transaction button (Execute xxxx) is different from the Base Workflow.
financeTopic