Cann't release segment type via we31 in IDES 6.0

Hi experts:
I cann't release segment type via we31 in IDES 6.0, when go to EDIT , there is no
' SET RELEASE' there, but when there is Edit----set release in our production system, Woudl you please give me a hint why it is like this?
Edited by: Sony Ericsson SAP Team on Jul 27, 2008 11:13 AM

First Cancel the Release and then Edit .
Once you finish the Editing , save it and then Release it.

Similar Messages

Error while adding new field in the Segment type thru WE31.

Hi All,
I want to add one field in the Z segment type using WE31.But i am getting the error message as
'Current segment definition <segment name> can no longer be changed and The current segment definition
is already released.You can either add a new segment definition or cancel the release of the current segment definition'.
The current segment defenition which i am trying to change got the SAP release of 45B. But the system has upgraded to Ecc6 recently.
I tried going to the edit menu and cancel the release, but still it is not allowing.
Whats the impact of the Add button(Add version) and creating a new version?.will it create a new version for ECC6?.
Points will be rewarded
regards,
neslin.

Hi
You can create a new version. This will not create any problems. You might not be able to cancel the release because of upgrade.
Thanks
Vijay

Error inALE service (Segment type not maintained in Message type) status:29

Hi all,
Need your help.
I have a added the a segment to the message type and which is linked in WE82( Message type:Debmas,basic type:debmas06 and extensionZxxx). And the segment is also set for release.It is an outbound senario. When i process it manually in WE19 using the basic type with the enhancement and via message type (with the message type and the extended type) I can process the idoc and the segment whic i have added with the following fields are displayed. But when i post the customer in BD12 with the message type I am getting the error in BD87 as " error in ale service Segment type ZXXX does not exist in message type DEBMAS".
PLease do the needful. Its since 2 days I am struck with the same and was trying but I could not get any. Hope you guys might help me.
Anything else to be refreshed or anything else to be done except we31.we30, we81
Thanks in advance.
Edited by: Farhy Farhy on Aug 2, 2010 12:29 PM

Thanks for your reply Mr. Das.
I have tried all the things and did not find any solution..
Posted after checking all the things and the procedure. I did not write any custom program. Earlier I created the extension type and deleted and created the new extension type. But now it is taking the same old extension type and giving the error as the extension type is not maintained in the message type.
I have deleted the old extension type completely but the old is onle getting reflected. Anything to be done to refresh.
Waiting for the reply.

Problem with creation of IDOC Segment Type

Hi,
I tried to create IDOC Segment Type Z1LFA1 but error
prompted "Structure Z1LFA1 already exist.".
I tried deleting it at se11 but prompted
"You cannot edit object R3TR TABL Z1LFA1 with the
standard editor"
and at sm30-TADIR, but prompted
with "Cannot delete object directory entry, object exists."
How will go about this??
Please help!
Thanks!

hi,
yup, tried doing that on we31 but the segment does not exist yet.
we're currently upgrading from 4.6 to ecc, I think the structure
was tranferred to our ecc client but the idoc segment and idoc type were not. I'll just have to transport it then.
Thanks!

IDOCS: Segment Definition and Segment Type

Hi Gurus,
We are working on IDOCs and trying to send a Location Master IDOCs to Third party system.
1. In the IDOC print preview we are in a position to see the IDOC segment type Ex: E1TPLOC but customer is asking for Segment definition E2TPLOC.
When we go through the documentation:
u2022     Segment Type consists of Segment definition with Version and Release.
u2022     Segment Definition will contain the Field names
u2022     E1TPLOC, E1TPDLH, E1KNVAM, E1TPTRM & E1TPSHH Segment types with concerned Segment definitions are
                     E2TPLOC,E2TPDLH, E2KNVAM
How to see the Segment definition types?

Hi,
You can see the documentation in the transaction WE60 by giving the IDOC Basic type and extension if you have any.
E1 and E2 are the same, when you see the definition of the segment the naming convention will be E2 and when populating the data it will be E1.
I believe he is asking the segment definition alone, you go to WE60 transaction and give the inputs and click the parser button and that will give you the definition of the idoc and which you can share it with your partner.
Thanks,
Mahesh.

IDOC Segment Definition received instead of Segment type

Hello Folks,
When i send a Z Idoc Segment from A to B System, It is successfull from A System, but in B System sometimes its erroringout because in the inbound idoc Segment Definition is coming instead of Segment type.
For Example
From A System I have sent Z1P0002 segment
B System I have received Z2P0002000(Which is the segment definition for Segment type Z1P0002)
Any inputs to above problem?

Hi,
The problem may be due to system B using a older release version of the IDoc. In those scenarios, even though your IDoc type is recognized, it may not be possible for the reciever to determine the right segment version of the reciever.
There are options in the WE20 partner profile configuration, Field Segment release in IDoc type and Segment Appl. rel. which enable the partner system preventing from erroring out.
BR/Yogesh
Edited by: Yogesh Surender on Jun 1, 2009 12:34 PM

Inbound side idoc segment defination is showing instead of segment type

Dear all,
i created z idoc ZMIGO961 and z segment ZJ1IW in both source and destination, when i send the idoc from the source to destination, in destination it is showing the segment defination i.e ZJ1IW000 in idoc instead of segment type ZJ1IW in my idoc.
plz help .
regards,
Edited by: manoj kv on Apr 4, 2010 9:18 PM

Hi manoj kv
segment defination : ZJ1IW000 indicates segment is ZJ1IW & version is 000
Go to T code we31 in Destination System
Enter the Segment Name and Check Defination Screen.....then you will see the segment defination : ZJ1IW000
Hope above info helps... you..
Thanks
Ramesh

Problem in viewing a field in Segment type

Hi All,
I have added a field to an existing segment type . Now the problem is that I am not able to see the field when an Idoc is created.I am able to see the fields that was previously added, but not the one which I have added..Can you plese suggest me how can I rectify that...
It will be very helpful if you can send me steps of doing it..
Thanks in advance.
Regards,
Asish Dash

If your other two checks are correct and only if you want to
know the program or function module please check following things.
1. Each Message type will having a posting program, genarally it will be a function module.
2. This function module will be attached to a Process code.
3. You can check the the process code name in the Partner profiles.
4. After knowing your process code, please check WE41 and WE 42 for the function module name.
5. From this you can debug and find out.
Points please if this info is helpful..............
Thanks,

Released Object Types must be transportable

Hi,
I am trying to release my BAPI and the BOs, but I am getting this error: "Released Object Types must be transportable"
Please suggest. Does it have anything to do with the function modules I created of its the BOs?
Thanks,
Apurv

Hi
Jawle Apurv and Vempalli.
Do like this copy Same Business Object to Another Name Save it in Transport Request and in Transportable Objects.
This is the Best way overcome from that error .
Regards,
Hiriyappa

Split Single IDOC into Multiple IDOC's Based on Segment Type

Hi Experts,
I have a scenario IDOC to FILE , Split Single IDOC into Multiple IDOC's based on Segment Type
Outbound:
ZIdocName
Control Record
Data Record
Segment 1
Segment 2
Segment 3
Status Record
I should get output like below
Inbound:
ZIdocName
Control Record
Data Record
Segment 1
Status Record
ZIdocName
Control Record
Data Record
Segment 2
Status Record
ZIdocName
Control Record
Data Record
Segment 3
Status Record
Please suggest me step by step process to achieve this task.
Thanks.

Thanks a lot Harish for reply.
I have small doubt. According to your reply , If we have N number of segments in single IDOC with same fields in all segments then for splitting Single IDOC into Multiple IDOC's based on Segment Type we need to duplicate N number of target IDOC tree structure.
Is that possible to Split single IDOC into Multiple IDOC's based on Segment Type using only one Target IDOC structure without duplicating the Target IDOC structure tree.

Create Individual Idocs Based on Parent and Child Segment type

Hi Experts,
I have a scenario IDOC to FILE , Split Single IDOC into Multiple IDOC's based on parent and child Segment Type
For example If 3 child segments are same and 1 segment is different under parent segment then 3 same child segments are clubbed and create single idoc under parent segments and 1 different child should create in individual idoc under parent segment.
Note : Same logic should work for N number of Parent Segments and Child Segments.
Outbound:
ZIdocName
Control Record
Data Record
Parent Segment A
   Child Segment 1
   Child Segment 1
   Child Segment 1
   Child Segment 2
Parent segment B
   Child Segment 3
Status Record
I should get output like below
Inbound:
ZIdocName
Control Record
Data Record
Parent segment A
Child Segment 1
Child Segment 1
Child Segment 1
Status Record
ZIdocName
Control Record
Data Record
Parent segment A
Child Segment 2
Status Record
ZIdocName
Control Record
Data Record
Parent Segment B
Child Segment 3
Status Record
Please suggest me step by step process to achieve this task.
Thanks.
Ram

Hello,
Segment won't hold any value, so filter criteria should be there on some field wich exist in Parent node and chile node?
Paste ur XML?
Try this(Assuming u have some fields in parent/child segment on which u want to define filter criteria):
Parent Field--UseOneAsMany----RC----
                                  ------------------Concat ----splitbyvalue(value change)--collapse context --- ZIdoc
Child field-- RC----------
Child field--RC--splitbyvalue(valuechange)--CC -Splitbyvalue(each value) -- ParentSegment
Child field--RC--splitbyvalue(valuechange)--- ChildSegment
RC -> Remove Context
CC - Collapse Context
Note - i haven't tested ur mapping, so make sure to adjust context in mapping
Thanks
Amit Srivastava
Message was edited by: Amit Srivastava

Is it mandatory to release segment?

Hi,
If I do not release a segment, do we get any error in IDoc or something like that?
Is it mandatory to release segment?

Hi,
Yes, it is mandatory to release segment.
Thanks,
Asit Purbey.

Error when release account plan via CRM_ACC_PL

Hi expert,
Getting error 'Overlapping validity periods for two condition records' when release account plan via CRM_ACC_PL.
Any idea what caused this error?
Cheers.

Hello,
could you please check notes 1311405, 1067232, 1044090, 1041830.
Hopefully they can help.
Regards,
Gerhard

Middleware initial load error on funcloc segment type (ADR2) does not exist

Hello,
We are doing initial loads of data into a new CRM 7.0 system.
So far all objects have been done except Functional locations (FUNCLOC).
During the initial load of the functional locations the various BDOCs all go into error state.
The error is the same everywhere: segment type adr2 does not exist.
If we deactivate the adr2 table In transaction R3AC1 and process again, we get the error message for the next table
(Like: segment type IFLOTX does not exist) and so on.
IS there any settings we can do to manage these 'segments' or would there be another wa to solve this?
Thanks.
Joram

Hello,
Take a look at note 1271465, it does not talk about the ADR2 segment but about segment errors in SMW01 for functional location download. It might be useful. Observe especially the constraint in ERP version number, it might be that your ERP system is out-of-date/incompatible for this scenario.
Second thing to check, go to SPRO>CRM>Master Data>Installed Base>Replication of technical objects from ERP
There you'll find a mandatory customizing activity for Functional location download.
And in the documentation of activity "Replication of Functional locations: Prerequisites and General information" you'll find all the necessairy actions to perform.
This helped me in setting up funcloc replication in CRM 7.0.
Hope this helps,
Kind regards,
Joost

Issue adding Auto-renewable in-app purchase type via App Loader

I have a Pro DPS account and a Multi-folio with iTunes subscription Newsstand app.
I'm attempting to add paid 6-month and 12-month subscription options to what has previously been a Free subscription app.
I also want to charge for back-issues, and add each back issue as a non-consumable in-app purchase.
I'm building a new version of the app to support the in-app subscriptions...
After the app is built in App Builder, I added the following auto-renewable in-app purchase types via iTunes connect for the subscription options...
com.appname.6mo
com.appname.1year
I also added the following in the App Loader for each of the back-issues....
com.appname.issuename
I understand that I now have to submit my app and the in-app purchases via the App Loader. But after adding all in-app purchases and choosing to "Deliver" through App Loader I get the following error.
Can anyone advise?

Yeah, created different subscription in-app purchases within the same family.
For non-consumables I used the same product ID for the published folio and in-app purchase. These were marked as FREE and Public at the time of submitting the in-app purchase, because I understood the in-app purchases would need to be approved before republishing those folios as PAID and public.

Cann't release segment type via we31 in IDES 6.0

Similar Messages

Maybe you are looking for