SAP Business Workflow - SAP Workflow Send Mail Error Analysis
SAP Business Workflow - SAP Workflow Send Mail Error Analysis
▼
▼ 2016 (1)
SAP Workflow Send Mail Error Analysis ▼
▼ July (1)
SAP Workflow Send Mail Error Analysis
This blog helps you for analyzing the error message 'Document & could not be sent' at send mail
step in a SAP workflow. It also provides several scenarios where this error occurs and the
possible resolution.The scope of this blog is to the business object 'SELFITEM' and its method
'SENDTASKDESCRIPTION'. And also the error message is in scope is with the message class
'SO', Message Number '023' and Message Text ' Document & could not be sent'.
First, to initiate error analysis process display work item container data. For this call the
transaction code 'SWIA' , specify values to the selection criteria and execute. Then a list is
displayed with the list of work item and choose a particular work item in this case mail step whose
data to be displayed.Finally click the display container icon then a popup window is displayed
with the container elements and its values.
After displaying the container data, go through the below scenarios where each paragraph
describes one scenario and its possible cause to find the reason for the error.
If the container element 'AddressStrings' is empty,So this is the reason for the work item status
with 'ERROR'.Now check the below points to find out, why the container element 'AddressStrings'
is empty and take a corrective action.
1. Is the binding defined from workflow to send mail step for the container element
'AddressStrings'?
2. Is the correct workflow container element is mapped to 'AddressStrings' in the binding?
3. Send mail step receivers(agents) are determination or not? If not check the corresponding
business logic.
If the container element 'AddressStrings' is not empty and the container element 'TypeId' = 'U'.
This means the receiver type is E-Mail Address. So the container element 'AddressStrings'
contains one or more email addresses of receivers in the format '[email protected]' as per the
company email domain specifications.If this is not the case then system forces the work item into
the 'Error' with the error message 'Document <xxxxxxxxx> could not be sent'.
If the container element 'AddressStrings' is not empty and the container element 'TypeId' =
'B'.This means the receiver type is SAP User. So the container element 'AddressStrings' must
contains one or more userids of receivers in the format 'US<xxxxx>' .If this is not the case then
system forces the work item into the status 'Error' with the error message 'Document
<xxxxxxxxx> could not be sent'.
If the container element 'AddressStrings' is not empty and the container element 'TypeId' =
'G'.This means the receiver type is Organization Object/ID.Here the Organization Object can be a
position, user or organization unit. So the container element 'AddressStrings' must contains one
or more userids of receivers in the format '<org.unit type><xxxxx>' .If this is not the case then
system forces the work item into the status 'Error' with the error message 'Document
<xxxxxxxxx> could not be sent'.
If all the above are true but the user master doesn't have SOST paramater settings. Check the
SOST parameters in the respective user master record.
Labels: 023, Document & could not be sent, Document xxxxx could not be sent, SAP Business Workflow, SAP
Workflow, SELFITEM, Send Mail Step, SENDTASKDESCRIPTION, SO
No comments:
Post a Comment
sapworkflowerror.blogspot.com/2016/07/sap-workflow-send-mail-error-analysis.html 1/2
8/8/2019 SAP Business Workflow: SAP Workflow Send Mail Error Analysis
Home
sapworkflowerror.blogspot.com/2016/07/sap-workflow-send-mail-error-analysis.html 2/2