webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Pip3A4_Buyer_Model:Send_PO_Request::** SERVICE EXECUTION FAI

  • 1.  Pip3A4_Buyer_Model:Send_PO_Request::** SERVICE EXECUTION FAI

    Posted Fri September 23, 2005 08:43 AM

    Hello,

           Here i'm facing the problem,when i'm trying to send a sample pip3a4 through RosettaNet adapter through admin page.I'm providing the DUNS numbers of  both sender and receivers.When I click Send PO button ,I'm getting the following error in the IS console.
    

    2004-09-22 13:41:01 EDT [PRT.0101.0375V2] (T4) (Pip3A4_Buyer) Pip3A4_Buyer_Model:Send_PO_Request
    2004-09-22 13:41:01 EDT [PRT.0101.0376V1] *** Error invoking step N6 (Pip3A4_Buyer_Model:Send_PO_Request): ip.cm.handlers:send(): Error trapped in service: wm.ip.cm.handlers:send
    Error:
    Error: Error while executing service wm.ip.trp.trputils:encodeNSend [ESIPRT.000000.000001] [ESIPRT.000000.000001] [ESIPRT.000000.000001]
    Error Message: In service wm.ip.rnif11.trp:trpPackage: Failed header validation.
    Reason:

    /ProcessControl/TransactionControl/ActionControl/PartnerRoute/fromPartner/PartnerDescription/BusinessDescription/GlobalBusinessIdentifier: DT-STR003 - [ISC.0082.9298] Value is longer than maximum length [ESRN11.000020.000033]
    Suggested Action:
    Level: Level:
    Service Call Stack:

    com.wm.ip.trp.TRPSendException: In service wm.ip.rnif11.trp:trpPackage: Failed header validation.
    Reason:

    /ProcessControl/TransactionControl/ActionControl/PartnerRoute/fromPartner/PartnerDescription/BusinessDescription/GlobalBusinessIdentifier: DT-STR003 - [ISC.0082.9298] Value is longer than maximum length [ESRN11.000020.000033]
    at com.wm.ip.rnif11.trp.RN11Transport.send(RN11Transport.java:125)
    at wm.ip.trp.trputils.encodeNSend(trputils.java:55)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:347)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:153)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:577)
    at com.wm.lang.flow.FlowState.step(FlowState.java:435)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1740)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:347)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:153)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:577)
    at com.wm.lang.flow.FlowState.step(FlowState.java:435)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1740)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:347)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:104)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:589)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:538)
    at com.wm.app.prt.IntegrationServer.invoke(IntegrationServer.java:55)
    at com.wm.app.prt.IntegrationServer.invokeWrapper(IntegrationServer.java:41)
    at com.wm.app.prt.StepDispatcherAgent.runStep(StepDispatcherAgent.java:486)
    at com.wm.app.prt.StepDispatcherAgent.execute(StepDispatcherAgent.java:395)
    at com.wm.app.prt.StepDispatcherAgent.synchRun(StepDispatcherAgent.java:75)
    at com.wm.app.prt.StepDispatcher.startStep(StepDispatcher.java:537)
    at com.wm.app.prt.StepDispatcher.dispatch(StepDispatcher.java:502)
    at com.wm.app.prt.StepDispatcher.handleTransition(StepDispatcher.java:102)
    at wm.prt.dispatch.handleTransition(dispatch.java:69)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:445)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:331)
    at com.wm.app.b2b.server.dispatcher.trigger.Trigger.invokeService(Trigger.java:298)
    at com.wm.app.b2b.server.dispatcher.trigger.Trigger.processMessage(Trigger.java:194)
    at com.wm.app.b2b.server.dispatcher.trigger.TriggerTask.processTask(TriggerTask.java:269)
    at com.wm.app.b2b.server.dispatcher.trigger.TriggerTask.run(TriggerTask.java:202)
    at com.wm.util.pool.PooledThread.run(PooledThread.java:105)
    at java.lang.Thread.run(Thread.java:498)

    Occured at: 2004/09/22 13:40:58.671
    Service Call Stack:
    wm.ip.cm.handlers:send

    2004-09-22 13:41:01 EDT [PRT.0101.0374V2] (T1) *** SERVICE EXECUTION FAILED ***
    2004-09-22 13:41:01 EDT [PRT.0101.0375V2] (T1) (Pip3A4_Buyer) Pip3A4_Buyer_Model:Send_PO_Request
    2004-09-22 13:41:01 EDT [PRT.0101.0376V1] *** Error invoking step N6 (Pip3A4_Buyer_Model:Send_PO_Request): ip.cm.handlers:send(): Error trapped in service: wm.ip.cm.handlers:send
    Error:
    Error: Error while executing service wm.ip.trp.trputils:encodeNSend [ESIPRT.000000.000001] [ESIPRT.000000.000001]
    Error Message: In service wm.ip.rnif11.trp:trpPackage: Failed header validation.
    Reason:

    /ProcessControl/TransactionControl/ActionControl/PartnerRoute/fromPartner/PartnerDescription/BusinessDescription/GlobalBusinessIdentifier: DT-STR003 - [ISC.0082.9298] Value is longer than maximum length [ESRN11.000020.000033]
    Suggested Action:
    Level: Level:
    Service Call Stack:

    com.wm.ip.trp.TRPSendException: In service wm.ip.rnif11.trp:trpPackage: Failed header validation.

    Please Help

    Thanx in advance
    Renuka


    #webMethods
    #Integration-Server-and-ESB
    #Adapters-and-E-Standards


  • 2.  RE: Pip3A4_Buyer_Model:Send_PO_Request::** SERVICE EXECUTION FAI

    Posted Fri September 23, 2005 10:19 AM

    Hi Renuka,
    Can you please make sure that your DUNS numbers are no longer than 9 digits long. That particular field has a limitation of 9 characters and it looks like it is receiving more than 9.
    Let me know if this fixes the issue. Also it would help if you checked the value of that particular field in the archived rno in the /packages/WmRNIF11TRP/pub/archive folder.
    Hope this helps.
    Raghu


    #Integration-Server-and-ESB
    #webMethods
    #Adapters-and-E-Standards


  • 3.  RE: Pip3A4_Buyer_Model:Send_PO_Request::** SERVICE EXECUTION FAI

    Posted Fri September 23, 2005 02:25 PM

    Hello Raghu,
    We have changed the DUNS numbers as you said before to exactly 9 characters.
    Now I am able to send the purcharce order to he concerned partner, but instead of receiving the ack, I am getting receipt ack exception.
    I could see the archive in /packages/WmRNIF11TRP/pub/archive folder.

    In the receipt ack exception doc I could see the following error:

    in /fromRole/PartnerRoleDescription/ContactInformation/telephoneNumber/CommunicationsNumber: DT-STR002 - [ISC.0082.9297] Value is shorter than minimum length

    Thank you
    Renuka


    #Integration-Server-and-ESB
    #webMethods
    #Adapters-and-E-Standards


  • 4.  RE: Pip3A4_Buyer_Model:Send_PO_Request::** SERVICE EXECUTION FAI

    Posted Fri September 23, 2005 02:38 PM

    Hi!
    Please open Developer (on the Seller side) and browse to the Pip3A4PurchaseOrderRequest document under the WmRNPips package and drill down to the location where the error is happening - “/fromRole/PartnerRoleDescription/ContactInformation/telephoneNumber/CommunicationsNumber”
    Under the properties for that string please check the min and max values that are allowed for that string. Please make sure that correct number of digits are present. This information is actually picked up from the Seller Profiles’ Contact Information tab in the TN console on the Buyer side.
    (My gut feel is that you have created a contact in the Seller’s Profile (on the buyer’s side) but not populated the telephone number field with any value.
    Once you do that you should be ok!
    Please let me know if this does not help!

    Raghu


    #Adapters-and-E-Standards
    #Integration-Server-and-ESB
    #webMethods


  • 5.  RE: Pip3A4_Buyer_Model:Send_PO_Request::** SERVICE EXECUTION FAI

    Posted Fri September 23, 2005 03:48 PM

    Hi Raghu,

       Thank you very much.We got the Output.It's working Fine.
    

    Renuka


    #Adapters-and-E-Standards
    #webMethods
    #Integration-Server-and-ESB