Segment Release version issue - ECC6 to older ver.

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

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

Similar Messages

Why T-RFC Port canu2019t handle Partner Profile Segment Release Version.

Can TRFC Port handle the segment release of each of the segment if configured in Partner Profile.
As per sap, in Partner Profile, if we maintain the two field "Seg. Release in IDoc Type" and "Segment Application release" to a SAP Release lower than the current release version then all the segment populated by the IDoc adapter should be populated as per the lower release structure.
For test Purpose I have created two IDoc using File Port and TRFC port and for both of then I have maintained the Partner Profile Fields "Seg Release in IDoc Type" and "Segment Application Release" as 46C although the latest release is 701.
In the IDoc there is a custom segment ZE1PMX with two Version Release 46C & 701. 46C is having 7 Fields and 701 is having 9 fields.
Test using TRFC Port: Using TRFC port the IDoc that is getting generated are not having the segment structure of release 46C instead of that it is taking the segment structure of latest release 701 which is having 9 fields.
Test using File Port: Using File port the IDoc that is getting generated are having the segment structure of release 46C instead of latest release 701 which is having 7 fields which is desirable.
I have also done these testing in other SAP release like 700 and found that while saving the partner profile with a lower segment release number it throws an warning message as "Segment definitions missing for release 620/620" and IDocs are not getting generated with a error status Code 2 "Segment E1BPMEPOITEM1 is unknown in Release 620 /". But from release 701 sap allows us to save the Partner Profile without warning and also creates the IDoc without error but the segments takes the latest release structure instead of the release maintained in the Partner Profile.
If any one has already done some investigation on this issue please let me know why there is a difference in TRFC Port and File Port. Is there any other configuration that is missing for T-RFC Port.

Hi Dennis
This forum is focused on [SAP NetWeaver Gateway|http://www.sdn.sap.com/irj/sdn/gateway], i.e. the (relatively) new OData/REST-orientated mechanism to expose ERP data and functions.
You're talking about the ('classic') Gateway i.e. the service that runs on port 33<SYSNR>. As a result, you are better off posting in the forum that covers that Gateway, i.e. [Application Server Infrastructure|SAP NetWeaver Application Server;
The names do make it confusing, for sure.
Good luck!
dj

IDoc segment version issue in ECC upgrade from 5.0 to 6.0

Hi experts,
we are in the process of upgrading our ECC environment from 5.0 to 6.0. We have quite a few interfaces which use ORDERS/Invoice Idocs in customised form. In ECC5.0 environment, we had developed a Z segment in the ORDERS Idoc and the segment release was set as 640. Everything worked fine in ECC5.0.
In upgraded environment, SAP has released new version of some segments. one of those is E1EDP01. This segment has 2 new versions in ECC6.0 environment - 007 and 008. This change in the version changes the data in the IDoc and hence interface goes in error at the EDI provider.
We have tried to use 640 as the IDoc segment release in the partner profile of the IDocs. This still gives us an issue because the 007 version of the segment E1EDP01 has release 620 and hence the Idoc picks up 007 version instead of 006 version as desired. When we change the partner profile with Segment release in the IDoc type as 46C, it gives us an issue in the Z segment saying that the IDoc segment is not released in 46C and the Idoc goes in error.
has any one faces such situation in the past? if yes, please throw some light.
Thanks in advance.

Please let me know if your issue was resolved. I have similar issue now.
Thanks,
Sailaja

Segment release cancellation error

When I attempted to perform "Cancel Release" on segment type ZE1MARAM in ECC6.0, I encountered the following error message: "Error while resetting release of segment ZE1MARAM" I didn't have the problem when I performed the same action in 4.6c. Our Basis team investigated the issue and concluded that this is not a security-related error? Does anybody here have seen this error before? What was the cause and fix?
Thanks,
Ning

Hi,
If you want add a new field..in the menu..segment -> add version..
now you can add a new field...
Thanks
Naren

Idoc segment release

Hi,
I wish to change one of the field's length in an idoc segment. It doesn't allow me to change it as the version is already released.
However, I cannot cancel the release too, as the released version belongs to an earlier version of SAP (4.7).
The current/existing version of the segment is of release 620. The current release is 710, so no change seems to be possible.
I can't create another version too, as it doesn't allow change of the earlier field definitions.
Could someone pls help.
Thanks!
Arthi

Hi,
We have similar issue. In the ORDERS05 IDOC, we had made changes to the segment E1EDP19 to repeat 99 times. Then IDOC extension ZORDERS05 was created. Due to new enhancement pack, the attributes of E1EDP19 were changed to repeat 5 times as per standard SAP.
This did not work for us because segment E1EDP19 should repeat 99 times. So we ran program to update the attributes of this segment. Now E1EDP19 can repeat 99 times.
But when we are processing ZORDERS05, the chagnes are not reflected. The reason could be, even though E1EDP19 was changed, it will not reflect in IDOC extension. For this to reflect, we are trying to cancel release ZORDERS05 once and release again.
I am not able to do this activity. Any pointers to this will be helpful. My requirement is to just cancel release once and release it again. Also while doing so, SAP message pointed me to 844899.
Regards,
Shahu

My macbook pro early 2012 won't install release version of yosemite after being in the beta test

my macbook pro early 2012 won't install release version of yosemite after being in the beta test, anyone else having any issues with this?

Received an email from apple saying thank you for being in the beta test and they tell you to download the release version from the mac app store and install it. Done this twice and it says installed successfully after rebooting twice and doing the usual install of a new OS. However when it boots up and opens your desktop it still has the Feedback assistant installed and continuity and all the new features do not work at all. Making me assume that the final release has not installed at all. Spoke to apple on the Phone and they Don't know how to solve it. Except for doing a fresh OS Install. Which i would rather not do, but might have too. currently backing up my Mac as we spec to do it

Country Version in ECC6.0

Hi,
We are in process of evaluating all SAP Country versions in ECC6.0.
We have gone through SAP solution browser but it did not give much detials.
Where we can get the delta functionality in SAP ECC6.0 from SAP 4.7 Enterprise for country versions.
Thanks in advance.
Best regards,
Jatin

Hi,
First, please review SAP note 602901, which describes, which countries
have country specific versions.
For the countries that there is some Country-Specific Documentation,
it is updated at SAP Help Portal for our standard country versions:
http://help.sap.com, choose Documentation, and select your release
SAP ERP > SAP ERP Central Component:
SAP ERP 6.0
-> English
   -> SAP ERP Central Component
     -> SAP ERP
       -> Cross-Application Functions
        -> Cross-Application Components
         -> Country Versions
Regards,
Aidan

Memory leak while debugging but not in release version

I have an Adobe AIR application that must load and unload multiple external swfs, and it must run for hours.
I had an issue where there was a memory leak. I tried all kinds of fixes, including rolling back SDKs and Adobe Runtime,
but every time I tested in Flashbuilder, the memory would climb, and with each unload a FlexLoader would stay in memory.
Finally I tried creating a release build, and low and behold the memory did not climb. It stayed the same even under stress testing.
So evidently, the memory leak had to do with debug version, and once it was a release version, the leak disappeared.

UPDATE: The problem was with the external swfs being loaded into the main application.
If I compiled them in debug, they leaked. In release version they did not.

Released Version: NI 5640R Installer; Please update

Released Version: NI 5640R Installer; Please update!
The software for the NI PCI-54640R IF-RIO is now released. Before asking about any issues in programming the NI 5640R, please upgrade to the released version. This will also make it easier to look at example code if there is an issue.
Please download the new installer file (“ni-5640r100rc1.zip”) from the following location:
http://digital.ni.com/softlib.nsf/websearch/199D73629DD50CDB86257116005160B6?opendocument&node=13206...
1. Remove your NI 5640R modules from the computer.
2. Un-install the version of NI 5640R currently on the computer.
3. At this time, it is recommended to un-install pre-release versions of LabVIEW 8.0, LabVIEW FPGA 8.0, and NI-RIO 2.0 and re-install the released versions.
4. Install the released version of the NI 5640R software.
5. Re-install the NI 5640R module.
Note: This new version of the driver handles the NI 5640R VIs differently from previous versions. Previous to version B5, different projects would use common NI 5640R VIs that were saved in the LabVIEW/instr.lib directory. This method prevents multiple projects from being open due to the Bind to Typedef option on the FPGA Target VI.
The new method saves copies of all NI 5640R VIs to a directory in the project. This allows different projects, with different typedefs to use the same VIs at the same time.
This will result in projects saved in the previous method from not finding the NI 5640R VIs. The easiest method to convert to the new method is to resave the NI 5640R Template example directory, and copy the changes from the previous VIs to the new VI. Ensure that you use the NI 5640R VIs that are part of the new project.

A new version of NI-RIO for Real-Time OS/Windows 2000/XP has released.
If installing the ni5640r software for the first time, please install NI-RIO Version 2.1 before installing the ni5640r software.
If you are re-installing the ni5640r software and you have NI-RIO 2.0 installed, please uninstall both the ni5640r software and NI-RIO version 2.0. Then install NI-RIO version 2.1, followed by the ni5640r software version 1.0.
Note: Updating NI-RIO from version 2.0 to 2.1 is a recommendation, it is not required. If you are already reinstalling the ni5640r software, it is a good time to keep up to date with the latest released drivers.
The current version of the NI-RIO driver (2.1) can be downloaded from this location:
http://digital.ni.com/softlib.nsf/websearch/8FBECA88CF87D34F862571C600566283?opendocument&node=13206...

Setup Central Contract Management SRM 7.01 with differing release versions

Hello experts,
OSS note 1268821 explains how to configure the central contract management between a SRM 7.0 and an ERP 6.04. So far so good, but how should it be handled if there are differing release versions such as ERP 6.04 and ERP 6.03? I guess that a technical split (xml services/ ALE distribution) is necessary?
Assuming that there are some backends with differing release versions and in some cases with differing master data (not supported by central master data client) would you always go via PI? Independent of release version, technology and master data.
Could you give some further detailed informations how to configure such a scenario? What has to be done to transfer existing contracts from an ERP 6.04 into SRM CM component (migration concept)?
Thanks!!!
KR Thorsten

Hi Thorsten
The minimal ECC version is 6.0 EHP4, Central Contracts require certain business functions in ECC to be activated and as these are included within ECC EHP4 you won't have these available in lower version. Therefore you won't be able to operate central contracts in such an ECC system.
You would either have to go with patching these systems or go with GOA's for these systems.
Operating central contracts via PI or SOA i believe provide almost similar functionality. SOA however requires an SRM EHP1 system and ECC EHP5 back-end to operate whilst central contracts configured via PI can be operated onwards from an SRM 7.0 and EHP4 system.
I can't help you on your migration issue, maybe someone else can.
Kind regards,
Tim

I had an older version of Firefox on older Mac OS 10.3.9. Tried to update. Crashed the Mac. Lost things saved on my desktop and Firefox that I had benn using for years is gone. Is there an older version I can reinstall?

I had an older version of Firefox on older Mac OS 10.3.9. Tried to update. Crashed the Mac. Lost things saved on my desktop and Firefox that I had benn using for years is gone. Is there an older version I can reinstall?

Hello kc9agz,
Thank you for contacting Mozilla Support. Did you back up your bookmarks before you moved to the new computer? You can find more information about backing up and restoring bookmarks in this article.
[[Restore bookmarks from backup or move them to another computer]]
Please let us know if this solves your issue.
Cheers,
Patrick

Qmaster not using all computers in cluster, is it a version issue?

hi i'm new to cluster compressing. I just set up a cluster and a compressor batch. the batch is running fine, however it's only using two of the three computers in the cluster. I rechecked the qmaster settings on the offedning computer and they are correct. It shows up on the qadminstrator of the controlling computer as well, but always remains idle. the computer that it's not using is an older version of compressor (and presumably qmaster). is it a version issue I'm experiencing? I'd love to get this 3rd computer working on the cluster as is has the fastest processor of the bunch.

Hi Gordon,
Thanks for your response. Actually I have already asked my work buddies not to use manager for a while so I can address the problem.
BTW, I also want to know if there is a way to monitor that kind of session in SAP. I will post it in another thread.
Thanks,
Lan

Action Automation Tool(AAT) plugins do not work in Release version InDesign CC 2014.2

Hi,
I was glad to notice that there is a black-box testing tool mentioned in the InDesign CC SDK. But i tried many times in my environment, the plugins cannot be loaded successfully.
I followed the steps in the documentation from SDK, copied shared libraries, plugins and qa folder to required locations. But when i launch release version of InDesign CC, it pops up messages as following for some plugins.
I tried on Win32 version, Win64 version and Mac version. The InDesign CC version is 2014.2, and i also tried the 10.0 SDK and 10.2 SDK. The message is the same.
Did i miss anything to make it work?
Thanks.

I found that on Windows, the (XXX Resources)/XXX/ are all empty, on Mac, XXX.InDesignPlugin/Resources and XXX.InDesignPlugin/Versions are empty too.
I'm not sure either the AAT plugins are not supported anymore in InDesign CC 2014 or they are supported but not included correctly in SDK.
So bad. BTW, i found there are many typo and format issues in the sdk documentation of InDesign CC2014. It looks like not professional enough. On Windows, the search function in html format documentation is not as good as before in CS6 with chm.

Loading dynamic images for Ipa version - issue solved?

Hello all,
I am facing the same issue reported in the thread below about loading images dinamically in iOS apps:
http://forums.adobe.com/thread/868630
In debug mode (using the Fast Method), images can be loaded dinamically in the iPad application. But when the final app IPA version is generated, images cannot be loaded dinamically. Just embedded images are shown.
Can anyone inform if this issue has been solved or if there is any workaround for it?
Thanks
Inacio.

Hi
Does the following Flex code cover your use case? I have mailed a .zip to [email protected] that has a flex project loads a png like below.
<?xml version="1.0" encoding="utf-8"?>
<s:View xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark" title="HomeView">
<fx:Script>
<![CDATA[
[Bindable]
private var url:String ="http://www.messersmith.name/wordpress/wp-content/png-national-emblem.png"
]]>
</fx:Script>
<s:Image id="ImgLogo" horizontalCenter="0" verticalCenter="0" source="{url}"/>
</s:View>
Are you by any chance using another swf file that supplies the url. No external swf can be loaded in the release version. So if your code is arranged in a way that the url for the png is part of some other swf file then you need to refactor your code to have a single swf file.

Improper Photoshop CS6 beta uninstall prevents Photoshop CS6 release version install

I installed Photoshop CS6 beta on my Mac, OS 10.6.8. Once I purchased and went to install CS6, the installer informed me to uninstall the beta version of Photoshop, but didn't say how, or that there was a catch. I went and uninstalled Photoshop CS6 beta bny dragging it to the trash. OOPS! - now the release version won't install, and I can't find anyhting on the Adobe website other than private messages from Adobe employees to specific users with the same problem as to how to rectify the issue.
Aside from venting my frustration at a situation I (and others have found ourselves in that could have been prevented by a little better planning and installer design, I'd really appreciate help in rectifying this state of affairs. It looks from other Forum posts like there is a tool or procedure that cvan be used to make the install work. Thanks in advance -
Michael Bade

Look for, download and run the CSClean Script from the Adobe site.
http://www.adobe.com/support/contact/cscleanertool.html

Segment Release version issue - ECC6 to older ver.

Similar Messages

Maybe you are looking for