In an IDoc passthrough outbound scenario, the following exception is thrown - "Value ' ' cannot be converted to NUM type at field PSGNUM".
The information contained in this document has been moved to developerWorks Answers located here. This technote will be archived in 60 days. Please bookmark the new location.
The problem occurs when converting or setting the PSGNUM field type, and is being fixed with APAR JR36095. You can find further details and a workaround below.
Problem emerges with WebSphere Adapter for SAP Software 6.1 or 7 on WebSphere Message Broker.
Diagnosing the problem
While the problem might look similar to APARs JR30775 and JR34739, they do not apply here.
Resolving the problem
The error message below can be seen in the service trace on a debug level:
"com.ibm.broker.adapter.deploy.MbAdapterAccess.execute 'throwing InternalException' , 'javax.resource.ResourceException: com.ibm.j2ca.sap.exception.SapAleOutboundException: Value ' ' cannot be converted to NUM type at field PSGNUM at com.ibm.j2ca.sap.SAPInteraction.handleException ...
com.ibm.j2ca.sap.exception.SapAleOutboundException: Value ' ' cannot be converted to NUM type at field PSGNUM
Caused by: com.sap.mw.jco.JCO$ConversionException: (122)
JCO_ERROR_CONVERSION: Value ' ' cannot be converted to NUM type at field PSGNUM
The root cause of the problem is that the PSGNUM field received a character that cannot be
converted into a NUM type. In the logs, the following exception further indicates the character being set for the PSGNUM field:
"CWYBS0011E: The Resource Bundle com.ibm.j2ca.sap.LogMessages using Locale en_US does not contain any text for key PSGNUM : ."
The problem is fixed with APAR JR36095: USING ALE PASSTHROUGH FOR OUTBOUND MESSAGES GOING TO SAP, SAP THROWS AN ERROR.
It is possible that you see above error message with another value than ' ', for instance:
... Caused by: com.sap.mw.jco.JCO$ConversionException: (122)
JCO_ERROR_CONVERSION: Value ' 0D' cannot be converted to NUM type at field PSGNUM ...
Note that the PSGNUM parameter does need to consist of exactly 6 numeric characters. If you should see an error message like that immediately above please check your application, respective flow, and the source data on whether they are correct.
A workaround is always to edit the input data for the PSGNUM field to "000000".
Review the latest recommended fixpack for the adapter to verify whether the APAR JR36095 is included: http://www.ibm.com/support/docview.wss?uid=swg27010397
Please contact IBM Support for any upcoming questions or concerns.