EDI Matmas04 segment release

Hi,
We have just deployed EHP4 on our quality acceptance server and are testing it.
During our EDI tests we noticed that the segment numbering of message type MATMAS04 changed because of the change in release (from 700 to 701).
Actually the output change was quiet normal as we hadn't set a segment release in the parameters of our outbound partner profile and hence the newest release is always used.
So the solution was thought to be simple : just put release 700 in the partner profile and generate the EDI. But apparently it is not :
For most segments the situation under release 700 was indeed applied but segment MARAM stayed the same, meaning :
MARAM007 is always used whereas in our production environment (that is still running under release 700) MARAM006 is used ...
We know the release field in the partner profile works because when we set release 600, MARAM005 is used ... It seems that MARAM006 dissapeared with the Enhancement package sun .
Does anybody have/had a similar experience ?
with regards

Hello,
thanks for your reply. But in WE82, I can only see that the combination DESADV with DELVRY03 is valid since Release 46A, but the segment versions that are used when the IDoc is created are not those from 46A but the newest versions like version E2EDP19002 for segment E1EDP19. As E1EDP19 is included in DELVRY03, the system uses segment version E2EDP19002 when you are on ECC 6.00 and not E2EDP19001 which was valid before ECC.
Regards
Christian

Similar Messages

Error while using '*'in the NTE (EDI 850) Segment where '*' is also used as Data Element

Hi All,
I am facing below mentioned error while using '*'in the NTE (EDI 850) Segment where '*' is also used as Data Element
Error: 1 (Field level error)
SegmentID: NTE
Position in TS: 70
Data Element ID: NTE02
Position in Segment: 2
Data Value:
3: Too many data elements
For Eg: NTE*GEN*My Text *goes here
Here, NTE02 should be My Text *goes here. So, how can I use "*" here without changing anything in the EDI message?
Can it be done?
Thanks.

Sorry, no.
X12 does not support an escape character so whatever is used for delimiters become reserved characters.
If you want to allow '*' in the data, you will have to chooser a different Element delimiter. The receiver should read the from this from the ISA Segment so it's supposed to be dynamic but that's not always the case in practice.

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

How to use '*' as data Element in the NTE(Edi 850) Segment

Hi All,
I am facing a field level error while using '*' in EDI 850 (NTE segment). '*' is also used as Data Element.
For Eg: NTE*GEN*My Text *goes here
Here, NTE02 should be My Text *goes here. So, how can I use "*" here without changing anything in the EDI message?
I have asked this question before
http://social.msdn.microsoft.com/Forums/en-US/1668e8d8-ee99-4d79-961b-8d26f3a496f8/error-while-using-in-the-nte-edi-850-segment-where-is-also-used-as-data-element?forum=biztalkediandas2
The answer in the above forum was to ask client modify the EDI message.
Previously, our client was using a different technology (other than BizTalk) which was working fine with this format. So, they are insisting on this format only.
Thanks,

Sorry, the answer is the same.
It doesn't matter what EDI platform either side is using, the '*' in the field content conflicts with the '*' that is the element delimiter. That is invalid EDI, there is no way around that short of writing a custom EDI parser.
It's not clear if you're sending or receiving this message. But again, it's really doesn't matter.
1. Change the Element Delimiter to something other than '*'. < or > are not uncommon.
2. If you are receiving the EDI, create a custom Pipeline Component that "handles" NTE02 either by replacing the '*' with a substitute char or deleting it.
3. If you are receiving, you could add extra elements to NTE to accommodate extra fields (since that's how the parser will see them). Then you can join them again in a Map.

EDI IDoc Segment Filtering Transactions

Hi All,
Is there any transaction for EDI IDoc segment filtering where partner profile is set up with partner type as 'customer' or 'vendor' (and not partner type as 'logical system' where ALE IDoc segment filtering transactions BD59 & BD64 can be used) ?
Thanks !

Thanks Lokeshwari.
Actually, a perticular field in an IDoc segment needs to be filtered. e.g. I dont want to send idocs with a perticular item category for ORDERS05 IDoc.
Is there any transaction to fulfill the same ?

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

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

EDI header segment E1EDK04 not populating

Hello,
We are currently using the intercompany EDI process to create vendor invoices based on an EDI output from a billing document.
This worked well for us, until we wanted to change our pricing procedure for tax condition type MWST print i.d. for condition line from "S" to "a".
Now when the iDoc is created it contains the correct tax values at the line item level in E1EDP04 but no segment is created for the header tax in E1EDK04.
Therefore, the iDoc fails with message 51.
SAP note 398414 (from 2001) suggets setting "S" in the print i.d.
It seems our options are to have a correct idoc output or a correct printed form for EU tax, but not both. This seems a limitation.
We are currently exploring a custom exit but I would like to know if anyone has a std SAP solution as being able to automate intercompany clearing does not seem a unique problem.
Generous points awarded.

Dear Roger,
would you please be more specific on how you resolved this? when use new pricing IDs for item-level relevancy E1EDP04 is not getting populated.
My requirement for printing is to show tax at item level, any header-relevant pricing ID incurres inconsistent processing of billing output.
I'm not seing any standard way to meet both requirements, please advice.
Dear All, any assistance on this topic would be highly appreciated.
Kind Regards,
Anastasia

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

Using IDOC MATMAS04 - Segment E1MLGNM

Hi all,
I'm using the Idoc Matmas04 to transfer material data between R/3 46C and ECC60.
In my sender system I don't use the Warehouse View, but I must create it in ECC60.
I try to use the BADI_MATMAS_ALE_IN to create the data for the table MLGN_UEB to pass the data in receving system, but the system doesn't create the Warehouse View.
I insert in the internal table MLGN_UEB only the Matnr and LGNUM.
In online transaction the system need only this data.
Can you help me to understand where I'm wrong ?
Thanks a lot
Barbara

Hi Ferry,
when I use the FM IDOC_INPUT_MATMAS01, I don't have the segment E1MLGNM, so the FM doesn't call the customer-exit.
The Idoc that I have is the follow :
MATMAS04                       Material Master
        E1MARAM                        Master material general data (MARA)
            E1MARA1                        Additional Fields for E1MARAM
            E1MAKTM                        Master material short texts (MAKT)
            E1MARCM                        Master material C segment (MARC)
            E1MARMM                        Master material units of measure (MARM)
            E1MBEWM                        Master material material valuation (MBEW)
            E1MVKEM                        Master material sales data (MVKE)
            E1MLANM                        Master material tax classification (MLAN)
            E1MTXHM                        Master material long text header
As ypu can see I don't have the segment E1mlgnm in input in my ECC.
Thanks
Barbara

Mapping EDI ISA06 segment to BPEL element

Hi
We have created a BPEL process for PO Inbound using X12 4010 EDI Version.
One of the trading partner send their EDI document and place them in B2B server.
B2B server has been setup to handle different partners.
One of our BPEL process will deQuee the messages from B2B server.
One of our requirement is to Map ISA06 segment value to BPEL one of element.
Where these values will be stored in this process and how can acchieve this requirement?
Regards
Kiran Akkiraju

Hi Kiran,
Actually If you see the EDI-XML generated by the B2B.The
<Internal-Properties>
<Data-Structure Name="Interchange">
<Lookup Name="InterchangeSenderID">SOME value </Lookup>
<>
section will have the value you are looking for i.e the ISA06 segment.
If you are using the 850.ecs and 850.xsd shipped with the product then the ISA segments are not there.
However the edi-xml generated by B2B has that value.
Now while doing the Mapping we have to extract the value from Internal properties->datastructure->lookup.
I hope these inputs would help you get started.
One more thing I wanted to know are you using XML Gateway from APPS Adapter
for invoking Oracle APPS.
Regards
Lalit

Changing IDoc Segment release

Hi ,
After upgrade from 4.6C to ECC 5.oo the idoc segement E1BP2017_GM_HEAD_01 is of 620 version for basic idoc MBGMCR01 .
I need to revert back to previous release for idoc type MBGMCR01, message type MBGMCR so that the existing program and application need not be changed.
If anyone has done the config changes related to same please let us know.
WE don't want to create a zidoc type with the previous release segment.
thx,
Pawan.

Hi Pawan,
GOTO WE31- And select the recent segment defination - GOTO EDIT BUTTON - Select - Cancel release. Then you can cancel the release and use the old version if you are allowed. I am not sure wether u can be allowed or not.
Otherwise Create the New version with reference to Old version and release it. Release is must.
Hope this information is helpful.Let me know if I can help you further.
Regards,
Siva

Error while resetting release of segment

Hi Experts,
We have one custom IDoc.I am trying to add new field to one of the segment.So i am trying to cancel release status of segment using we31.But i am getting error Error while resetting release of segment ZXXXXX Message no. EA259 .I checked many of SDN threads but no where exact solution is mentioned for this.Current release for the message type is 701.so we are on same version now also.I put a break-point in LEDIJF05 in form CHANGE_CLOSE_SEGDEF.i observed it is failing at line 625 and
can not unclose segment: release of last version is not SAP-version*.Can any body tell me what is the exact issue.
Thanks in advance,
Vijay

Hi Vijay,
If the SAP version and the version segment released last time is the same, then this problem should not occur. If you are still facing the issue, add a version to the existing segment. You should be able to add the new field then.
Regards,
Parthiban

Removinga field from the segment which is already released

Hi Folks,
I have created a custom segment & released it. But later when I want to remove a field from it I'm not able to do so. I tried to cancel the release of the segment & then make the required changes but while tried to cancel the release I'm getting an error saying "Error while resetting release of segment ZDATA_BASIC_SEG". Kindly let me know how could I remove the field from this segment. For your information the current release of our system is 700 & the release of segment is also 700.
Thanks & Regards,
santosh

Hi Santosh,
As you said, current release of your system is 700 & the release of segment is also 700.
I tried to test the possible errors during the release of the segment. Please have a breakpoint in the program LEDIJF05 in the form CHANGE_CLOSE_SEGDEF. The error could be mismatch with the previous definition of the segment, where the release is not equal to 700.
Message Id : EA, msg no 259.
Please check.
Hope this helps.
Regards,
Satish Kanteti

Idoc Segment Cancel release error

Hi all,
I have problem in cancelling the release of an Idoc Segment. I have a requirement to add new fields to the segment. When I try to do Edit->Cancel Release it is throwing below error.
"Error while resetting release of segment Z1PXXXX
Message no. EA259"
Could anyone tell me how to overcome this error or the root cause of this error?
Many Thanks,
Sri
Edited by: Arunsri on Nov 10, 2009 8:37 AM

Hello,
The reason that you are getting these errors is that you cannot cancel
the release of an extension made in previous version e.g. 4.6C. Instead you have to
create a new extension.
It is not possible to change a segment definition which is released in a
lower release. This is a basic concept of our release strategy to
guarantee compatibility between different releases.
You must create a new segment definition for the new release e.g. 620 with a new segment
field with the appropriate length. In transaction WE20, outbound parameters, you can specify
the "segment release in IDoc type" for the communication. Please read the F1 help of this field for further
information.
For your own segments you can define a new version of the segment via
transaction WE31 -> Add Version (Shift+F5).
Please review your online help for more information on this and related topics.
Hope this information helps.
Regards,
David

EDI Matmas04 segment release

Similar Messages

Maybe you are looking for