JR34047: SRVC: IMPROVE THE CLARITY OF THE ERROR MESSAGE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • When a msgflow containing SAPRequest node (BAPI) with decimal
    fields built on 6103 of WMBT is deplyed onto the 6104 , the
    adapter fails the message and the following exception in snippet
    1 and snippet2 are thrown.
    
    In the snippet 1 , the error message is not clear , it basically
    says in execute method , but says Null,and also says error could
    be in metdata, data or both (which basically lists all
    possibilities) , and which is not quite helpful to debug.
    
    Also in snippet , it says the adapter failed during the
    conversion of a BIG decimal field, however it would be helpful
    to print out which field (attribute name) where the failure has
    happned.
    
    
    
    
    Following is the exception that gets logged first as in snippet1
    ,followed by the one in snippet2 :
    ******************************************
    
    Snippet1:
    ************
    -                   invokeBAPI
    file:F:\build\S610_P\src\DataFlowEngine\NativeTrace\ImbNativeTra
    ce.cpp
    line:158 message:3484.BIPv610 'MbLogHandler:SEVERE' ,
    'CWYAP2044:The
    Z_MM_MATERIAL_CREATE BAPI (without transaction) failed. Error:
    null
    Explanation=In the input BAPI business object, the data,
    metadata or
    both are incorrect.  UserAction=Refer to the exception message
    for more
    details.'
    2009-08-15 15:58:58.017845     4944                        >>
    UserTrace   BIP3484E: ''CWYAP2044:The Z_MM_MATERIAL_CREATE BAPI
    (without
    transaction) failed. Error: null  Explanation=In the input BAPI
    business
    object, the data, metadata or both are incorrect.
    UserAction=Refer to
    the exception message for more details.''
                                           An adapter component has
    written
    the diagnostic message included here.
                                           Refer to the appropriate
    WebSphere Adapters message in the WebSphere Brokers
    documentation.
    2009-08-15 15:58:58.017883     4944                        >>
    SapBAPIInvoker.invokeBAPI 'MbLogHandler:SEVERE' , 'CWYAP2044:The
    Z_MM_MATERIAL_CREATE BAPI (without transaction) failed. Error:
    null
    Explanation=In the input BAPI business object, the data,
    metadata or
    both are incorrect.  UserAction=Refer to the exception message
    for more
    details.'
    2009-08-15 15:58:58.017936     4944                        >>
    SapBAPIInvoker.invokeBAPI 'MbLogHandler:FINEST' , 'A simple
    BAPI,Z_MM_MATERIAL_CREATE(without transaction) failed'
    2009-08-15 15:58:58.021419     4944                        >>
    com.ibm.j2ca.sap.bapi.SapBAPIInvoker.execute()
    file:F:\build\S610_P\src\DataFlowEngine\NativeTrace\ImbNativeTra
    ce.cpp
    line:158 message:3484.BIPv610 'MbLogHandler:SEVERE' ,
    'CWYAP2017:A
    simple BAPI (without transaction) failed. Error: null
    Explanation=An
    error occurred while invoking a BAPI. Check the exception
    message.
    UserAction=Verify and correct the data in the input BAPI
    business
    object. See the exception message for more details.'
    2009-08-15 15:58:58.021419     4944                        >>
    UserTrace   BIP3484E: ''CWYAP2017:A simple BAPI (without
    transaction)
    failed. Error: null  Explanation=An error occurred while
    invoking a
    BAPI. Check the exception message.  UserAction=Verify and
    correct the
    data in the input BAPI business object. See the exception
    message for
    more details.''
                                           An adapter component has
    written
    the diagnostic message included here.
                                           Refer to the appropriate
    WebSphere Adapters message in the WebSphere Brokers
    documentation.
    2009-08-15 15:58:58.021465     4944                        >>
    com.ibm.j2ca.sap.bapi.SapBAPIInvoker.execute()
    'MbLogHandler:SEVERE' ,
    'CWYAP2017:A simple BAPI (without transaction) failed. Error:
    null
    Explanation=An error occurred while invoking a BAPI. Check the
    exception
    message.  UserAction=Verify and correct the data in the input
    BAPI
    business object. See the exception message for more details.'
    2009-08-15 15:58:58.021511     4944                        >>
    com.ibm.j2ca.sap.bapi.SapBAPIInvoker.execute()
    file:F:\build\S610_P\src\DataFlowEngine\NativeTrace\ImbNativeTra
    ce.cpp
    line:158 message:3484.BIPv610 'MbLogHandler:SEVERE' , 'Error in
    execute() Error Msg:nullnull'
    
    Snippet 2:
    ***********
     2009-08-15 15:58:58.063873     4944                        >>
    com.ibm.broker.adapter.deploy.MbAdapterAccess.execute 'throwing
    InternalException' , 'javax.resource.ResourceException:
    com.ibm.j2ca.sap.exception.SapBAPIException
      at
    com.ibm.j2ca.sap.SAPInteraction.handleException(SAPInteraction.j
    ava:1232
    )
      at
    com.ibm.j2ca.sap.SAPInteraction.execute(SAPInteraction.java:547)
      at
    com.ibm.broker.adapter.deploy.MbAdapterAccess.execute(MbAdapterA
    ccess.ja
    va:139)
      at
    com.ibm.broker.adapter.nodes.MbAdapterRequestNode.requestData(Mb
    AdapterR
    equestNode.java:370)
      at
    com.ibm.broker.plugin.MbRequestTemplateNode.requestData(MbReques
    tTemplat
    eNode.java:51)
     Caused by: com.ibm.j2ca.sap.exception.SapBAPIException
      at
    com.ibm.j2ca.sap.serializer.SAPBapiObjectSerializer.cursorToBapi
    Function
    (SAPBapiObjectSerializer.java:826)
      at
    com.ibm.j2ca.sap.serializer.SAPBapiObjectSerializer.cursorToBapi
    Function
    (SAPBapiObjectSerializer.java:729)
      at
    com.ibm.j2ca.sap.bapi.SapBAPIInvoker.invokeSimpleBAPI(SapBAPIInv
    oker.jav
    a:412)
      at
    com.ibm.j2ca.sap.bapi.SapBAPIInvoker.invokeBAPI(SapBAPIInvoker.j
    ava:158)
      at
    com.ibm.j2ca.sap.bapi.SapBAPIInvoker.execute(SapBAPIInvoker.java
    :549)
      at
    com.ibm.j2ca.sap.SAPInteraction.invokeBAPI(SAPInteraction.java:8
    01)
      at
    com.ibm.j2ca.sap.SAPInteraction.execute(SAPInteraction.java:374)
      ... 3 more
     Caused by: com.ibm.despi.exception.GetFailedException
      at
    com.ibm.broker.despi.MbInputAccessor.getBigDecimal(MbInputAccess
    or.java:
    764)
      at
    com.ibm.j2ca.sap.serializer.SAPBapiObjectSerializer.getAccessorD
    ata(SAPB
    apiObjectSerializer.java:996)
      at
    com.ibm.j2ca.sap.serializer.SAPBapiObjectSerializer.cursorToBapi
    Function
    (SAPBapiObjectSerializer.java:811)
    

Local fix

  • n/a
    

Problem summary

  • The BAPI executing fails indicating some problem with data in
    one of the fields.
    

Problem conclusion

  • The adapter code in v7 onwards displays the fieldname and exact
    error message as thrown by JCO
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR34047

  • Reported component name

    WEBS ADAPT SAP

  • Reported component ID

    5724L7900

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-20

  • Closed date

    2013-02-13

  • Last modified date

    2013-02-13

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS ADAPT SAP

  • Fixed component ID

    5724L7900

Applicable component levels

  • R700 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Adapters
Adapter for SAP

Software version:

6.1

Reference #:

JR34047

Modified date:

2013-02-13

Translate my page

Machine Translation

Content navigation