Segment Definition Name in IDOC

Hi Gurus,
   I am new to IDOCs.
   I need to create a new segment type in WE31.Its name should be say Z1TEST and I want to have the segment definition name to say Z2TEST.Currently the segment definition name is blank and disabled and when I save the segment type, the segment definition name, by default , comes as Z1TEST000(as per my example).
   Can u please suggest any ways of putting my own naming in the segment definition.
Thanx in advance.

hi,
Defining Segments
Use
This is where you define segments so that you can assign them.
Procedure
From the Commission System screen, choose Master Data -> Segment Assignment -> Segments -> Maintain.
Choose a segment type and an effective validity date.
Choose Save.
Result
You have created a representation of the commission calculation of relevant data from the external policy management system. You can now assign the segments.
A data segment contains a collection of fields from SAP tables. A data segment may hold master data or data from an application document. A segment is a collection of all the records of one type. A segment may contain data from a single SAP database table, or it may combine related data from multiple tables.
A checksum is basically a one-way hash of whatever data arguments you supply.
Regards,

Similar Messages

Segment definition in an IDOC type

Hi,
What does Maximum number and Minimum number stand for in an segment definition within an IDOC type? I think there are two options.
1. the occurence number of the segment type in an IDOC type defintion
2. the occurence number of the segment data of a special IDOC
1 or 2. Please suggest ... It will better if there is any example for me to understand it. Thanks.
Regards

Option 2 is correct from my observation.

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 - Get Segment Definition or Version in Code

I'm working on the ABAP-PI Port, created a FM based on FM OWN_FUNCTION now.
In my FM, there is a call to a function
CALL FUNCTION 'EDI_SEGMENTS_GET_ALL'
that retrieves all the segment data for a particular IDoc number.
However, it returns only the segment name EDIDD-SEGNAM and not the segment definition.
Example:
Value returned: "E1EDKA1" ( EDIDD-SEGNAM , 27 char long field)
I'm actually looking for the Segment Definition that goes up to 30 characters long.
Value I need to be returned: "E2EDKA1001" - has the extra 3 digits at the end that represents the Version.
If you go to WEDI, Development > IDoc Segments, You can see that the Segment definitions belong to a data type EDISEGDEF (30 characters long).
Does anyone know how I can get this programmatically?
The IDoc file downloaded by the FILE port stores the 30 char Segment Definition in the file
Using the ABAP-PI it only returns the segment name (27 char)

Hi all,
Thanks for your replies.
EDISDEF might be useful, but I'm not sure how to use it at the moment.
I am supplied in the code a structure of type EDIDC, which has the following values (not all are listed)
MANDT C 3 308
DOCNUM N 16 0000000000002050
DOCREL C 4 640
STATUS C 2 03
DOCTYP C 8
DIRECT C 1 1
RCVPOR C 10 SUBSYSABAP
RCVPRT C 2 B
The above represnets a particular IDoc being processed (see DOCNUM and DOCREL)
The default code then uses a FM to get the segment data based on the DOCNUM.
CALL FUNCTION 'EDI_SEGMENTS_GET_ALL'
 EXPORTING
 DOCUMENT_NUMBER = I_EDIDC-DOCNUM
 TABLES
 IDOC_CONTAINERS = I_EDIDD
 EXCEPTIONS
 DOCUMENT_NUMBER_INVALID = 1
 END_OF_DOCUMENT = 2
 OTHERS = 3.
Does anyone know of any FM that returns a EDID4 (has 30 char segment version) structure instead of a EDIDD structure (27 char seg def)?
And the value EDIDC-DOCREL (SAP Release for IDoc) e.g.
640
does not match up with values available in EDISDEF-RELEASED (IDoc development: Release of segment definition), e.g.
30F
40A
45A

How can I find if the segment definitions are
E2EDKA1 or
E2EDKA1001 or
E2EDKA1002 or
E2EDKA1003

IDOC - add new field in in existing segment definition

Hi,
For segement type say Z1MARA1 if we need to add a new field in segement definition say Z2MARA1 SAP is not allowing to add new field if we tried to cancelled the realsed 30E it not allowing since the SAP realease which we are working is 640 so only we can create new segement defination with version Z2MARA1001 with new field added but issues is that the partner Profile for outbound parameters the Segment release in IDOc Type is 31I so if we change this segment release in IDOC type to new version ie., 640 then it will pick all the new segement associated with it due to which the the format in which we pass the segements to third party will change so is there any way to use the existing segment definition which is release 30E & add addition field to it. Only one way I found is that when i try to cancel the released message is trigger so in the debug if I make it success it allows to add new field in existing segment definition but which is wrong way of doing is there any way we can used same segment definition & add new field without adding new version & new released.
Thanks in advance.
Rajeev

Varma,
I know that we can add new segement with new version my question is existing segement definition can we add a new filed because in partner profile we specified release 31i so even we create new segement type then version will be 640 so it will not pick the latest version.
Thanks
Rajeev

XI IDOC missing segment definition in type E1LFM1M

Hi experts,
we have recently upgraded our ERP system to NW 702 EH5. As aresult a new segment definition was added to our segment type E1LFM1M ( segment def. E2LFM1M007). The problem we are havign is that our XI system is still running on NW700 and it doesnt have this segment defintion. Since the upgrade we are getting an error in transaction RFC complaining about the new segment definition E2LFM1M007 everytime we try to send a vendor from ERP to SUS using BD14. Is there a way we can deactivate the new segment definition E2LFM1M007 in segment type E1LFM1M?
Thanks,
Abdul.

Hi Abdul,
Actually it does not matter what are your systems' versions, PI can always handle an IDoc properly. All you need to do is perform the following steps in your PI system:
1. Log on to ABAP stack, go to t-code idx2, find your ECC system and that particular IDoc (I believe this will be CREMAS) and delete its metadata.
2. Log on to Enterprise Services Repository, find your SWCV where the IDoc definition was loaded, and load it again from your ECC system, then activate the change.
3. If necessary, also adjust the message mapping to use/not use the new segment. Activate your changes.
Once you have these steps completed, you are ready to retest your scenario and say goodbye to the error.
Hope this helps,
Grzegorz

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

How to cancel the release of the current segment definition-WE31-IDOC?

Hi Experts,
Am trying to add a new field to a existing custom segment type/defination. This segment type is already using in the system.
So, went to WE31 and pressed the PENCIL button for changing/adding my new field, but am geting the below message,
(1)pls let me know that does it mean CANCEL the release (Menu>Edit>Cancel Release)? if so, Can I go ahead and use this CANCEL the release? do I need to take any pre-requisites as this segment is already relased?
(2)But, you know there is another option saying 'ADD VERSION-Shift+F5', if I choose this option, its also taking me to a screen where in I can add new fields so which is correct option for me is it either (1) or (2)?
Current segment definition Z_segment_defination can no longer be changed
Message no. EA666
Diagnosis
The current segment definition Z_segment_defination of segment type Zsegment_type is already released.
System Response
The segment definition cannot be changed.
Procedure
You can either add a new segment definition or cancel the release of the current segment definition.
Thank you

so i tried to CANCEL the release by goiong menu pathEdit-->Cancel the release, but am getting the below error, How to fix it to add my new field?
Error while resetting release of segment
Thank you

How to add an feild to a segment to an existing idoc sturucture?

how to add an feild to a segment to an existing idoc sturucture?
please help me out with the step step by process...
thnaks and regards,
anu

Hi
use the WE31 Tcode to edit the segment
see the following steps
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji

Flat File IDOC - ECC, segment defn x in IDoc type y CIM type do not exist

Hi,
I'm working on idoc flat file > sap scenario. Everything seems to be working up until the point where I get an error message:
EDISDEF: Port EDIPORT segment defn E2FINBU000 in IDoc type FIDCCP01 CIM type do not exist
I've loaded the meta data, and the file structure is fine. I believe the issue is related to PI not having the idoc I'm interested in listed in WE30. How do I reference the standard IDOC type FIDCCP01? Ideas I've had are around SWCV or transport from another system, the first I'm not sure which SWCV, the later seems a bit of a bodge and I dont like the idea.
Thanks
James.

Hmm.. some light for the situation. Seems that the segments imported are:
E1FINBU     E2FINBU     31I
E1FINBU     E2FINBU001     40A
E1FINBU     E2FINBU002     40B
E1FINBU     E2FINBU003     45A
E1FINBU     E2FINBU004     45B
E1FINBU     E2FINBU005     46A
E1FINBU     E2FINBU006     46C
Which indeed does not have E2FINBU000, which the IDOC is most definitely trying to pass. I can only guess that the middleware producting this IDOC is flawed, and that standard SAP ALE will accept this as E2FINBU (It works into another SAP system without XI).
Guess I've answered my own question, but feel free to offer light for points
Thanks,
James.

Need billing text field name for IDoc mapping

Hi Friends,
our users use CRM web application to send orders to SAP via IDocs. They want to have billing text (In German it is called Rechnungstext or Faktura text) so that they can enter some text here if they want to enter something. My question is, what is the field name and IDoc segment for billing text? We need this information to map in XI.
Br, Sats.

The solution is:
The standard Idoc text segment can be used for the text in sales order. From SD side the text types have to be customized. This is necessary for the XI mapping.
Regards,
Sats.

Add IT0006 custom fields for segment definition E1P0006 basic type HRMD_A06

Hello! I am am trying to determine how to bring in our custom fields from IT0006 into our IDOC's for message type HRMD_A basic type HRMD_A06 without performing a custom SAP modification. I was able to create a new segement definition called Z1P0006 and replace the SAP standard E1P0006 IDOC segment defintion in table T777D for infotyp 0006 to Z1P0006. However, I receive a message that I must not maintain this IDOC segment manually and instead you must maintain infotypes and their individual elements by using the transactions for processing infotypes: PPCI or PM01 (Infotype copy transaction for personnel administration).
Does anyone know of a way to bring in the new custom infotype fields from i.e. reimport the table structure for IT0006 into the segment definition without a custom SAP modificaiton? I would really appreciate any help on this topic!
Thanks!
Holly

unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that
are between the structures i must send in the other system sap.
Ok, I have never delt with Time data in HRMD_A. Probably this is the case then
Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems
all correct!!
By checking Filters I mean that confirm if you have added Time Infotypes there (just
making sure). If data is appearing in BDCP2 that means there is no problem in Change
pointer creation, Just ruling out possibility.
Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments)
is created without problems and in the BD21 no??? This is very strange
1) Well BD21 uses the Function module (TBDME for HRMD_A) which read change pointers and
create IDOCs. So now if you have extended Segment you have to add your population code
here somewhere.
2) PFAL is Push program, my assimption here is you have wriiten some piece of code to
populate Additinal segments data here? Otherwise IDOC will not be populated
automatically.
Let me know what you think.

Segment definition version

Hi,
We have generated IDOC for basic type MATMAS03
and following are some of the segments, their versions and release.
Segment type Version Release
E1MARAM 005 620
E1MARMM 002 620
For segment type E1MARAM and E1MARMM we want to use following version and release
keeping rest of the things same.
Segment type Version Release
E1MARAM 004 46C
E1MARMM 001 46A
Is it possible to create idoc with these versions for segment E1MARAM and E1MARMM.
I am using FM MASTER_IDOC_DISTRIBUTE.
Rgds,
Fattesingh

Hi all,
Thanks for your replies.
EDISDEF might be useful, but I'm not sure how to use it at the moment.
I am supplied in the code a structure of type EDIDC, which has the following values (not all are listed)
MANDT C 3 308
DOCNUM N 16 0000000000002050
DOCREL C 4 640
STATUS C 2 03
DOCTYP C 8
DIRECT C 1 1
RCVPOR C 10 SUBSYSABAP
RCVPRT C 2 B
The above represnets a particular IDoc being processed (see DOCNUM and DOCREL)
The default code then uses a FM to get the segment data based on the DOCNUM.
CALL FUNCTION 'EDI_SEGMENTS_GET_ALL'
 EXPORTING
 DOCUMENT_NUMBER = I_EDIDC-DOCNUM
 TABLES
 IDOC_CONTAINERS = I_EDIDD
 EXCEPTIONS
 DOCUMENT_NUMBER_INVALID = 1
 END_OF_DOCUMENT = 2
 OTHERS = 3.
Does anyone know of any FM that returns a EDID4 (has 30 char segment version) structure instead of a EDIDD structure (27 char seg def)?
And the value EDIDC-DOCREL (SAP Release for IDoc) e.g.
640
does not match up with values available in EDISDEF-RELEASED (IDoc development: Release of segment definition), e.g.
30F
40A
45A

How can I find if the segment definitions are
E2EDKA1 or
E2EDKA1001 or
E2EDKA1002 or
E2EDKA1003

2 SEGMENTS ITEM NAME FORMAT을 1 SEGMENT ITEM NAME FORMAT로 변경 방법

제품 : MFG_INV
작성날짜 : 2005-05-06
2 SEGMENTS ITEM NAME FORMAT을 1 SEGMENT ITEM NAME FORMAT로 변경 방법
=====================================================================
PURPOSE
System Items Key Flexfield setup시 2 segments item name format을 이용하
였으나 이 후 business 변경에 따라 item name format이 변경되는 경우가
발생한다. 이런 경우 이 note를 참조하여 item name segment를 변경할 수
있다.
Problem Description
Inventory item name은 아래의 procedures에 따라 2 segment value에서 1
segment value로 변경될 수 있다.
1. Segment1에 prefix를 더하여 value를 변경하고, segment2를 null 시킨다.
using a sql script:
(example)
update mtl_system_items_b
set segment1 = concat(segment1,'.&suffix'),
segment2 = null
where segment2 = '&seg2value';
2. System items KFF segment definition에서 segment2를 delete하고 KFF를
recompile 한다.
Workaround
Solution Description
이 접근방법은 development로부터 확인받은 것이다.
1. Open Item Interface process는 item names update는 지원하지 않으므로
update script는 item name을 변경하기 위해 이용될 수 있다.
이 script를 이용하기 전에 아래의 내용을 확정한다.
-. Updating the segment1 with concat(segment1,',&suffix')
Client는 새로운 value가 segment1과 연관된 valueset을 만족시키는지
확인할 필요가 있다.
-. Segment2가 null이 되어도 문제가 없는지 확인해야 한다.
Item KFF definition에서 segment2가 현재 'Required'로 setting되어
있는지 점검한다.
2. mtl_system_items_b table에서 item 값을 update 한 후 systen item KFF
definition에서 segment2를 delete 후 KFF를 recompile 한다.
위 모든 변경 사항은 먼저 TEST instance에서 test 해야 한다.
TEST instance에서 성공적으로 test 된 후에야 TEST instance와 동일한 다른
instance에 적용할 수 있다.
Reference Documents
Note 282045.1

The Cost_of_sales_account & Sales_account as defined in the MTL_PARAMETERS are different from those in MTL_SYSTEM_ITEMS_B for the corresponding item. The values for these accounts in the interface tables are same as that in the MTL_SYSTEM_ITEMS_B table and hence not same as those defined in MTL_PARAMETERS.
Actually we have a Custom trigger on the MTL_SYSTEM_ITEMS_B table which updates these accounts, once the item is created in the Master Organization.
To verify this issue, I updated the accounts on the MTL_SYSTEM_ITEMS_INTERFACE table to match with that of MTL_PARAMETERS. Ran the 'Item Import', now those records are processed.
Does this means that, the Interface is validating the cost_of_sales_account & sales_account to match with that of the 'Organization' ??.
But we never had this issue in 11i. Is this a part of R12??

Port &1 segment defn &2 in IDoc type &3 CIM type &4 do not exist

Hello,
I've a question. We would send an standard IDOC from the 4.6C System to our SAP Xi 3.0. I customized the XI with TA IDX1 and IDX2. If we trigger the IDOC to XI I get the follow error message back:
Port SAPQ73 segment defn E2EDL20002 in IDoc type DELVRY03 CIM type &4 do not exist.
The IDOC Vers. is 4.6. In another system with IDOC Vers. 6.20 isn't a problem. So I think its a problem of the IDOC Version, or? So I checked the forum about this topic but I didn't find anything. So, I hope you can help me. Kind Regards Stephan

Hello,
I have exactly the same issue... We're currently upgrading our SAP system 4.7 to ECC6.0. We're also upgraded the system to an unicode system.
Before those change, the interface between SAP and Xi worked well. Since the upgrade, those idocs don't pass any more and get the same error message than Stephan.
I've checked the authorization of the RFC user and he has SAP_ALL and SAP_NEW. Partner profile, RFC connection, port and distribution model didn't changed.
Do someone have an idea why this can appear ?
Thanks in advance.

Segment Definition Name in IDOC

Similar Messages

Maybe you are looking for