\"object\" is null

, ,
1

I’m running Pip3B2 using 4.6 version, and encounter a problem.

I checked the “Content” of “Transaction Analysis” in TN 4.6, it did show xmldata:

<?xml version="1.0"?>

  
    
      
        
          
            
              KTCFV
            
            197819683
				.
				.
				.
				.
.

BUT

  1. with “Validate Output” set “Yes” in “Set Additional Settings” of Conversation Script, the error message shows in “Conversation” in TN 4.6:

The Send Document step failed on attempt 1 of 4. The service was wm.ip.cm.handlers:send, and the error message was com.wm.lang.flow.FlowException: ip.cm.handlers:send(): Error trapped in service wm.ip.util:validatePayload
[ESIPRT.000000.000020] Error: [B2BSERV.0062.9021] “object” is null
[ESIPRT.000000.000027] Occured at: 2006/01/06 17:37:22.656
[ESIPRT.000000.000021] Occured at: {0}
[ESIPRT.000000.000021] wm.ip.util:validatePayload
wm.ip.cm.handlers:send

  1. with “Validate Output” set “No” in “Set Additional Settings” of Conversation Script, the error message shows in “Conversation” in TN 4.6:

The Send Document step failed on attempt 1 of 4. The service was wm.ip.cm.handlers:send, and the error message was com.wm.lang.flow.FlowException: ip.cm.handlers:send(): Error trapped in service wm.ip.util:addXMLheader
[ESIPRT.000000.000020] Error: [B2BSERV.0062.9001] Service record argument in RecordToDocument is null
[ESIPRT.000000.000027] Occured at: 2006/01/09 09:51:17.703
[ESIPRT.000000.000021] Occured at: {0}
[ESIPRT.000000.000021] wm.ip.util:addXMLheader
wm.ip.cm.handlers:send

Thank you,

2

Please check to ensure that you have not dropped the “Object” in the outbound map service. That is a classic reason why you would see this error during outbound validation.

3

Thank you for your reply. I’ve found what caused the error message: I didn’t map record 3B2Pip to record document -->payload–>3B2Pip, instead mapped record 3B2Pip directly to record 3B2Pip.