Search This Blog

SBL-BPR-00181: Output argument '%2' in step '%1' contains data that cannot be passed to string type property '%3'.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Fin Svcs
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Microsoft Windows 2000 Server

This document was previously published as Siebel SR 38-1175712581.

Symptoms

SBL-EAI-04012

Hi,

We are in the process of developing an eAI workflow process to send Call Report File Attachments to an external application.

While developing the same we are getting the error
'[1] Service Method arguments property set has no children - expected a child of type 'SiebelMessage' (SBL-EAI-04012)
[2] Error invoking service 'EAI MIME Doc Converter', method 'MimePropSetToMimeDoc' at step 'New Business Service1'.(SBL-BPR-00162).

Attached is the details of the workflow process. Could you please help us with the same?

Thanks and Regards

Solution

Message 1

[1 / 2]

For the benefits of other readers,

Customer would like to query the database, convert the integration object and its attachments into a MIME hierarchy, and then create a MIME document to send to the File Transport within a workflow process. When invoking the Transcode Service business service to convert from Binary data to String data between the EAI MIME Hierarchy Converter and the EAI MIME DOC Converter business services, following error occurred:

'[1] Service Method arguments property set has no children - expected a child of type 'SiebelMessage' (SBL-EAI-04012)
[2] Error invoking service 'EAI MIME Doc Converter', method 'MimePropSetToMimeDoc' at step 'New Business Service1'.(SBL-BPR-00162).

Resolution:

When customer invokes the Transcode Service business service, the input data should not be hierarchical data. If the input data is hierarchical data such as MIME Hierarchy, the output of the business service could be empty. This was why the customer received the reported error message when invoking the EAIM MIME Doc Converter.

If they would like to convert from Binary data to String data in this scenario, they can consider define the MIMEMsg process property of data type Binary instead of String in the workflow process. Finally, they removed the step to invoke the Transcode Service and changed the data type of the MIMEMsg process property from String to Binary. Then, the reported behavior could be resolved.

(Cont) ...

Message 2

[2 / 2]

There is a sample workflow process in Siebel Bookshelf, Integration Platform Technologies: Siebel eBusiness Application Integration Volume II > Siebel eAI and File Attachments > Using MIME Messages to Exchange Attachments > Creating Workflow Processes Examples. However, please note that when invoking the EAI MIME Doc Converter within the example workflow process, following error occurs:

Output argument '<Value>' in step 'MIME DOC' contains data that cannot be passed to string type property 'MIMEMsg'. Data type: 'MEMBLOCK'; String representation of data body: 'MIME-Version: 1.0Content-Type: multipa'(SBL-BPR-00181)

This is because the data type for the MIMEMsg process property is defined as String data type. In order for the workflow process to be executed successfully, the data type for the process property should be changed to Binary.

Change Request 12-JGIQBW has been logged to address this documentation defect.

Kind Regards,

Siebel Technical Support


No comments:

Post a Comment