Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Segment Release version issue - ECC6 to older ver.

praveen_pillai3
Explorer
0 Likes
1,247

Hi

Our system was recently upgraded from ECC5 to ECC6 and we are facing an issue with one of the interfaces that is connected directly to the R/3 System.

This issue is realted to an outbound interface and it used to work fine when we were on ECC5. The message we are sending is a bespoke extension based on basic type DELVRY03. The segment E1EDL24 have new fields added to them in the 701 release version compared to the 620 version which was the higest available on ECC5.

I tried reducing the IDOC segment release version to 620 and 46C in the partner profile, but the message received by the thirdparty still contains the new fields which is causing an issue at their end.

I would appreciate if you could provide me some guidanace on how to appraoch this issue.

Thanks & Regards

Praveen

6 REPLIES 6
Read only

Former Member
0 Likes
955

Hi Praveen

Ask you thirdparty to update the Basic idoc type Structure in their System

Thanks

Ramesh

Read only

0 Likes
955

Hello Guy's,

We have recenlyt upgraded our quality system to ECC6.

I am also facing the same issue, As per my unnderstadning if I put segment release in WE20 then in ALE communication Layer Idoc should remove the fileds which are not intended for the given release. For example E1EDP01 is having highest release 008 for 701 release. If I set 40A in partner profile the Idoc should generate with fileds only available in 40A release i.e. version 003,but SAP is filling all thefilds which are available in701 relase.

I don;t understand why SAP has given such a functionality though it actually not filter the data at communication layer!!.

Could you please let me know did any of you really see the difference when you use segment release in WE20 when using PI as receiver? I did sevaral test for MATMAS, ORDERS found this segment release is useless.

If you have applied any workarounds(other then updating receiver system mapping) please let me know. I think is there any modification in ECC6???

Edited by: Naresh Reddy K on Jun 7, 2010 3:30 PM

Read only

Former Member
0 Likes
955

Praveen,

I am not sure which thirdparty you are using, i worked with datastage, here they used to extract the idoc structure from SAP, so when they extracting the IDOc, they will also mention like versions..etc. In this away they only will have required fileds or currect version of IDOc/Segments.

If it is not possible for your case, go for Reduced message type.

--

Reddy

Read only

0 Likes
955

Hello VV Reddy,

we dont; have any issues for sending Idocs to File port, and SAP system. In both these cases SAP filters the additional fileds in communication layer. But for the IDocs sending to PI there is not filters done by SAP at communication layer; and for XML we don't have any option to set segment release in WE20.

For PI do they have any option to download the version based on the partner name?

Read only

0 Likes
955

Better go for reduced message type in this case.

sorry, I am unable to give answer for your second querry, I am not familiar with PI.

--

Reddy

Read only

0 Likes
955

Hello VV Reddy...

Thank you for your relpy. Reduced message type is not correct option here..