| Author | 
		  Message
		 | 
		
		  | timmy | 
		  
		    
			  
				 Posted: Wed Mar 12, 2003 6:09 am    Post subject: IDOC version 3 | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 12 Aug 2002 Posts: 24 Location: Torello 
  | 
		  
		    
			  
				Hi,
 
 
I'm using the SAP Link and the IDOC parser to get an IDOC from SAP. It works good when the IDOC is in Version 4 (with EDI_DC40 header), but when I have an IDOC in Version 3 (with ED_DC header) it puts on the DLQ.
 
 
I think that the problem is in the IDOC parser, but I'm not sure. 
 
 
Does anyone know what is happening? How can I get an IDOC in Version 3?
 
 
I'm working with WMQI 2.0.2 and NT.
 
 
Thanks in advance. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | lillo | 
		  
		    
			  
				 Posted: Wed Mar 12, 2003 6:25 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Master
 
 Joined: 11 Sep 2001 Posts: 224
  
  | 
		  
		    
			  
				If you are using supportpac IA0F, IDOC parser, you should know the parser only support version 4 format. The following lines are from the supportpac manual.
 
   
	| Quote: | 
   
  
	| add support for parsing of input messages and creation of output messages in the SAP IDoc Version 4 format. | 
   
 
 
 
Cheers, _________________ Lillo
 
IBM Certified Specialist - WebSphere MQ | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | timmy | 
		  
		    
			  
				 Posted: Wed Mar 12, 2003 6:43 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 12 Aug 2002 Posts: 24 Location: Torello 
  | 
		  
		    
			  
				Thanks for your help!
 
 
Any idea to get an IDOC with version 3 format? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | lillo | 
		  
		    
			  
				 Posted: Wed Mar 12, 2003 7:53 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Master
 
 Joined: 11 Sep 2001 Posts: 224
  
  | 
		  
		    
			  
				What about writing your own java plugin as an input node? I think this option would be easier than writing a parse in C.
 
 
cheers _________________ Lillo
 
IBM Certified Specialist - WebSphere MQ | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | timmy | 
		  
		    
			  
				 Posted: Fri Mar 14, 2003 1:19 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 12 Aug 2002 Posts: 24 Location: Torello 
  | 
		  
		    
			  
				Thanks a lot for your answers!
 
 
I've never written my own java plug in and I don't know how I can begin. Do you know where I can find any manuals or codes for this?
 
 
I've found a 'provisional' solution getting the IDOC as a BLOB, adding a NULL at the end and using a RCD node to convert it into a MRM (NULL terminated). Then I can work with a string and map the fields that I need using SUBSTRING. 
 
 
However I'd like to find another solution. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | lillo | 
		  
		    
			  
				 Posted: Fri Mar 14, 2003 2:16 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Master
 
 Joined: 11 Sep 2001 Posts: 224
  
  | 
		  
		    
			  
				Java nodes are only availabe in WMQI 2.1 and your are MQSI 2.0.2.
 
 
Cheers, _________________ Lillo
 
IBM Certified Specialist - WebSphere MQ | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | timmy | 
		  
		    
			  
				 Posted: Wed Apr 02, 2003 1:24 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 12 Aug 2002 Posts: 24 Location: Torello 
  | 
		  
		    
			  
				My 'provisional solution' doesn't work when the IDOC arrive directly from SAP. When I tried this for the first time I put the message in the queue using MQVisual Edit and it works. 
 
 
I think the difference is the 'MQMD.Format' value. In the first case it is 'IDOC' but if I use MQVisual Edit is 'MQSTR'.
 
 
I try to get the message as a BLOB, but it fails when I access to the data. I also use a RCD node to change the format and the domain before I access to the data, but it doesn't work.
 
 
Can I modify the IDOC parser code to solve this? How?
 
 
Another suggestion?
 
 
Thanks in advance. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |