| Author |
Message
|
| hellobond070 |
 Posted: Fri May 21, 2010 5:42 am Post subject: Sap Input Idoc Issue : Few fields missing |
 |
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
Hi,
I have configured a SAP input node to receive a IDOC type. I used to get all the fields properly from the IDOC to the queue.
But recently due to business need, the SAP team had to add 3 more fields in one segment. Now the issue is these 3 fileds are not appearing in the input IDOC which resides in a queue in Broker. The IDOC in SAP when viewed has all these fields. Rest of the fields from this segment are coming correctly.
Only the newly added 3 fields are missing. |
|
| Back to top |
|
 |
| hellobond070 |
| Posted: Fri May 21, 2010 5:48 am Post subject: |
|
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
Well let me add a few more details.
I have re-run the adpater and can see these fields in the message set created and I have redeployed the flow too.
Please let me know if anybody else has faced this issue. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Fri May 21, 2010 6:00 am Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| hellobond070 wrote: |
| Well let me add a few more details. |
What nodes sit between your SAP node and the queue?
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 21, 2010 6:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If you configure the flow to read the IDOC as a BLOB instead of parsing it, and write that to a queue, are the fields there? |
|
| Back to top |
|
|
| hellobond070 |
| Posted: Fri May 21, 2010 7:05 am Post subject: |
|
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
Hello,
My flow
SAP Input Node -> MQOutput(QUEUE)
Above is my flow. I am not doing any computing to the input message.
The IDOC seen in SAP
-A have chile B and C. A, B, C are segements. A, B has its own fields.
-C having D, E and F. D, E, F are fields.
A,B,C was coming properly. SAP team added D and E fields last week which is seen in the input message in the queue. Well F was added yesterday by SAP team to the segment C which is appearing in the message set created by the adapter wizard in the broker but when SAP triggers IDOC and the message lies in the our queue from the SAP input node, the message does not contain the field F.
Well, all the segments and its fields are coming properly. Not sure why the new field is giving a problem. This can be a issue on SAP end too. I have never faced such a problem before. Please help. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri May 21, 2010 11:27 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you are parsing the IDOC instead of doing a passthrough as mqjeff suggested, you need to go back to the design phase and adjust your message set every time the SAP team changes the structure of the IDOC.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 21, 2010 1:02 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
If you are parsing the IDOC instead of doing a passthrough as mqjeff suggested, you need to go back to the design phase and adjust your message set every time the SAP team changes the structure of the IDOC.
Have fun |
The only reason I suggested not parsing it was to attempt to confirm if SAP was actually *sending* the fields. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Mon May 24, 2010 2:02 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| mqjeff wrote: |
| The only reason I suggested not parsing it was to attempt to confirm if SAP was actually *sending* the fields. |
Absolutely, cos SAP has an annoying habit of caching stuff so you don't always get what you expect.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| hellobond070 |
| Posted: Wed May 26, 2010 7:32 am Post subject: |
|
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
This issue was at the SAP end. The rectified their code and the fields started appearing our message present in the queue. This is the first time I came across this scenario.
Thanks everyone for their inputs. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Wed May 26, 2010 7:47 am Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| hellobond070 wrote: |
| This issue was at the SAP end. |
From my experience it usually is 
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
|
|
