Idoc segement

Hi
I have BOMMAT idoc , where i have to repet MATNR value as many times as IDNRK and MENGE_C is having.
Bommat04 idoc
Segment 1 E1STZUM(1..1)>>E1MASTM(1..999)>> Field is MATNR(0:1)
Segment 2 E1STZUM(1..1)>>E1STPOM(0:99999)>> Field is IDNRK(0:1), MENGE_C(0:1)
Like
segment E1MASTM
MATNR = 1
Segment E1STPOM
IDNRK = 200
MENGE_C= 300
Segment E1STPOM
IDNRK = 201
MENGE_C= 301
So MATNR Shoud repet two times and give the results like 1,200,300 and 1,201,301.
Please suggest me the mapping to achive this.
regards
Laxmi Bhushan

I have got very simple solution for u...
Use graphical variable------- option available in PI 7.1
Right click on target structure say add variable and give MATNR name - Now map the source field MATNR with this field.
Now Go to ur target MATNR structure and drag that target variable and map it to target field..
u can refer this blog for more understanding.../people/william.li/blog/2008/02/13/sap-pi-71-mapping-enhancements-series-using-graphical-variable
I have tried that and It is working very fine for me...U can use that MATNR field as a constant...other mapping will be same -wat I mean is map E1STPOM to root target node....
chirag

Similar Messages

Reg. IDOC Segement E1IDB02 in IDOC basic type PEXR2001

Hi All,
This probelm is with the idoc segment definition release.
The IDOC segement defintion E2IDB02002 is not in release status.
Could you please let me know how to change the segment Status to Release.
Regards
Anil Kumar K

Hi Anil,
You can set and reset the release status in transaction WE30 (if I remember it right). You can switch (when at the SAP Menu tree) to the IDoc Menu by transaction WEDI. You will see the relevant transactions under the menu point "development".
Gunter

IDOC Segement Release vs IDOC Basic Type

Hi there,
we are in an upgrade project and are runing into a general question about idoc creation.
Here is our behavior:
1. We have an reduced IDOC Type in BD53 ZMATMAS based on Messagetype MATMASDI.
2. It has 2 Segements E1MARAM with fields MSGFN MATNR PSTAT and Subsegemnt E1MAKTM with fields MSGFN SPRAS MAKTX.
3. Done the things around (RFC, Partner Profile, distribution model, changepointer ..)
4. In Distribution Model in outbound parameters, added our ZMATMAS.
As parameters we have: Partner type: LS, Message Type: ZMATMAS, Basic Type MATMAS03! and Seg. release in IDOC Type 46B. The Partnersystem is an NoneSAP System.
We are using MATMAS03 because this interface exists since 46B.
Now we send an Material with BD10 and Message Type ZMATMAS.
The Master and Commuidoc are successfull created. In BD87 the commuidoc is an MATMAS03 and has the expected 2 segements E1MARAM and E1MAKTM.
But what we do not expect, if we look into the content of E1MARAM there are ALL Fields which exist for the E1MARAM in release 7.00. Not only our 3 fields MSGFN MATNR PSTAT, or as we second expect only the segemnts that had existed in the segemnt E1MARAM in release 46B of MATMAS03.
The additional fields were filled with the NODATA sign.
My question is: Is it correct that an IDOC with basic type MATMAS03 can have an segement E1MARAM which is formated like the segemntdefinition E2MARAM007 (Release 7.00 / 6.03)?
The difference is definatly the length of the field! 876 in 7.0 vs 757 in 4.6A.
Why is SAP using the highest available segemnt release regardles which basic type we choose?
Isnt this wrong?
Additional infos:
We know that it is not possible to have an IDOC with basic type MATMAS03 with an segement e.g. E1MARA1 which only exists in newer basic type MATMADI if segemnt release is set to 46B in our distribution model.
Failure is: Segment E1MARA1 is unknown in Release 46B/ (correct and expected behavior)
If we are using this scenario with not an reduced message type, we will only find the fields in E1MARAM which are filled with data. (Not all fields of the latest release with nodata)
I traced the MASTER_IDOC_CREATE_MATMAS and hit the function IDOC_REDUCTION_FIELD_REDUCE. As you can see in it, it first checks if the idoc is an reduced message type, and at the end, fills up all fields with the "empty_symbol" which have no data in it. Why is this only happening if it is an reduced message type?
Kind regards
Manuel

Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel

Issue with DEBMAS IDoc,not all fields are reflected in the IDoc Seg E1KNB1M

For IDoc type DEBMAS, there is a segment E1KNB1M. This segment is relate to the customer correspondence details (XD02 -> company code data -> Correspondence).
For any change to the customer master a DEBMAS IDoc is triggered which has data in segments including the E1KNB1M.
In my case for few customers, the not all fields in the segment E1KNB1M contain data. Few fields contain data but the rest are filled with u2018\u2019. This is happening only in the production system, for the same customer in the quality system the data is there as required.
I checked in debugging, and found that the data is correctly passed to the segment in program SAPLVV01 Include LVV01F01. And the segment contains data till the IDoc is triggered. I.e. the fields are not getting cleared at any point.
Can anyone suggest what is happening and how to fix this? Please note that the issue is only in the production system and not in the quality system ( for the same customer).

BTT... Need some help on the above

XI Unit Test Not Equal IDOC SEG

I have made a mapping change in XI. When I unit test, within XI only, on the test tab, my results are what I want, which includes an extra segment appended to the idoc.
However, my end-to-end test, meaning XI into SAP the additional segment is not being added to the incoming idoc?
Am I missing an additional config change somewhere, because I do not see why the added segment is not making it to the idoc.
Any suggestions are welcomed....Thank-You.

Hello Jin,
Actually I get the desired result - within XID only - by copying in the actual payload for this one file into the test tab as SRC in XID where my mapping change exists.
It creates the desired Tender segment in the Retail Line Item. Also, we currently create tender segments for other scenarios, just not this one. So I checked IDX2 anyway, and if course, as I expected it is there.
I just expect BW to receive this file with the tender segment added per my unit test in XID, but it is not there in BW when it picks up the file via FTP...Thank-You.

How to release the idoc segements version

I added some extra fields to an existing segment of an idoc. While saving it created a new version. Now there are two versions : one is released and another is not. First one has the older fields and in the second one new fields along with the old fields
how can I get only one version with the latest changes. Segment with the additional fields.
Please advice.

When I am trying to release that , it is saying 'A released version is already there for the segment'. So not able to release.
Can you please tell me how to release the changes.
Thanks

IDOC segement Problem....

Hi All
how can we remove unwanted segment from idoc output list
i am using standarad idoc
there is no need of customeization
plz send the solution
Thanks in advance

I didn't get any possible solution for this. waiting for the possible and exact solution for this query

Filed to identify the batch characterstics in MBGMCR02 (idoc seg.)?

Hi All....
As i am passinng some data to idoc segment MBGMCR02.
Along with this i have to also pass the Batch chacterstics with respect to the BATCH in order to satisfy the requirment. But the field through we can pass this batch charcterstics i am not able to find it out..
Please help to me solve this secnerio?

Hi,
Check this sample process
To get custom fields on IDOC you need to add custom segment on IDOC and for that you have to create a extension IDOC with reference to Basic IDOC.
You can do that as explain below.
Here for example you have basic idoc ORDERS05 and you want to add additional segments at header level - ZE1EDK01 and line item level ZE1EDP01
1. TCode - WE31 : Create custom segments ZE1EDK01 and ZE1EDP01 with the fields you want and release these segments.
2. TCode - WE30 : Create extension IDOC
In WE20 enter extension IDOC name - ZORDERS05, select "Extension" option and hit "create" button. When it gives pop-up, select "create new" and enterd linked basis type as "ORDERS05". Enter proper description and save.
3. On the next screen of WE30, select the segment under which you want to add your additional segment. Save everything.
4. TCode - WE82. Here you link extension idoc to basic idoc and message type.
Go into change mode. Hit "New entries button" Enter Message type = "ORDERS", basic type = "ORDERS05" and extension type = "ZORDERS05".
Regards,
Satish

IDOC to JDBC multimapping N:1

Hello,
I've the follow:
IDOC
segA
belnr = 1
segB
belnr = 2
segC
It's possible the segB is repeat (this is the problem):
IDOC
segA
belnr = 1
segB
belnr = 2
segB
belnr = 1
segC
The target is:
field1
field2
fieldN
the field2 value is
empty (if segA belnr <> segB belnr) or belnr (if segA belnr = segB belnr)
The problem is when come two segB, In this case the value of field2 must be belnr when segA belnr <> segB (first) belnr or
segA belnr <> segB (second) belnr
How can i do this?
Thanks

Hi,
Even though Segments of idoc gets repeated the exact data can be retrieved based on the qualifier..
for e.g. E1EDK02 of Orders idoc contains BELNR and qualifier 001(purchase order) and 009 (Invoice number)
so based on qualifiers data can be retrieved from segements...if occur multiple times
HTH
Rajesh

How to find standard function modules for IDOCs

Hi,
Can anyone tell me is there any way to find the standard function module for IDOC. I have checked BD60 but it's not available. For example Idoc type WPUBON01 and I need to know the function module. Can anyone tell me the way out.
Secondly, if anyone can provide me the code to map the file fields and idoc segements.
Regards

Use WE82 to find message type associated with Idoc type.
Then use this message type as a search string to find the FM.
The associated FMs are.
POSED_FILL_OVERVIEW_ENT_WPUBON
POSED_INIT_DATA_WPUBON
POSED_LOCK_DATA_WPUBON
POSED_OVERVIEW_ASSIGN_WPUBON
POSED_READ_DATA_FROM_DB_WPUBON
POSED_READ_TR_DATA_WPUBON
POSED_SAVE_DATA_WPUBON
POSED_SEARCH_STRING_WPUBON
POSED_STORE_DATA_WPUBON
POSED_UNLOCK_DATA_WPUBON
POSED_UPDATE_DATA_WPUBON
POSED_UPDATE_TR_DATA_WPUBON
Thanks,
Utsah Garg.

Repeat IDOC Segment in LSMW

Hi,
I want to migrate orders from our legacy system to SAP. I use IDOC SALESORDER_CREATEFROMDAT200. My Input files are order header and order items. I connect the two input files to the corresponding IDOC segements.
But how can I repeat an IDOC segment. I want to create the IDOC segment E1BPPARNR twice. One side for PARVW AG and on the other side for PARVW WE. Is it possible to repeat the IDOC segment without connecting it to an additonal file, which contains the partner data with the two records for AG and WE ?
thanks
Uli

In order to repeat a segment with different data coming from the same file, follow these steps:
Go to Field mapping and conversion rules
Click on "Extras" (menu bar) > Layout and check "Processing time"
At the end of your segment, you will see a field called "__END_OF_RECORD__" having the ABAP statement "transfer_record." After that code, you need to enter the mapping for each field of your second segment (you can copy-paste code from the previous fields and simply change the source field (the one from your flat file).
Add another "transfer_record." statement after your code.

IDOC TO HTTP Error ... Help

Hi Friends,
My scenario is sending custom IDOC's using an HTTP adapter to an external system.
there are few cases where some of the IDOC's have 25000 segment and in such cases my IDOC fails to reach the HTTP external system and it gives the below error in SXMB_MONI
I checked smq2 and the IDOC gets stuck in there and doesnt process the other small IDOC's in the same queue.
Error Message from SXMB_MONI
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client. Code 110 reason</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please let me know as to what could be the problem . I cant restrict my IDOC segements due the nature of the requirement.
Edited by: Vijay jothimani on May 16, 2009 2:02 AM

Hi,
there are few cases where some of the IDOC's have 25000 segment and in such cases my IDOC
fails to reach the HTTP external system and it gives the below error in SXMB_MONI
If you are sure that because of message size you are getting the error then you can check the tuning guidelines mentioned in section 3.2.9 of the below document:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2016a0b1-1780-2b10-97bd-be3ac62214c7
looking at the error log i would also recommend that you look at this discussion:
Error in Call Adapter
Regards,
Abhishek.

IDOC segment fields prefixing blank space with values

Hi Experts,
I am sending data through custom IDOC from SAP to XML which generates successfully but getting 2 problems in the data.
its having 3 level idoc segments:
SEGMENT1 with 1 field (field_name(20))
SEGMENT2 with 3 fields, (code_g(20), field_name(20), value(20))
SEGMENT3 with 4 fields, (code(20), field_name(20), Language(2) & text(20))
When i check the idoc in WE02,
1. i found that segment2-value field is prefixing some space along with the values.
    Eg: if the output is "0111" whihc is plant, in the output (WE02) it is giving "       0111"
2. Segment3-language is no where in the output and text which should come as "011" is coming like "       EN011" means it is concatinating language field value and displaying it with the text field value with prefixing space.
This is happening in PRD not in QA & DEV. I also checked the transport req and everything, Its same everywhere.
Can anyone please help me on this.
Regards,
Nik

Hi,
This issue happnes when u are moving the data to iDOC segement with offset.
to aviod this improper move instead of using offset statement use below mentioned code.
decalare a structure as
Data SEG1 type SEGMENT1 ,
        SEG2 type SEGMENT2,
       SEG3 type SEGMENT3.
then while moving
SEG2-code_g = 'XXXX'
SEG2-field_name = 'YYYY'
SEG3-value = 'ZZZZ'
here u are moving the segment values to idoc data (SDATA) and then append it.
move seg3 to idoc-sdata.
then append it to idoc.
hope this helps

IDOC Segment - wrong value in WE02

HI,
I am working on ECC 6.0. I have changed the value of idoc segement in user exit by modifying table t_idoc_data.User exit name is EXIT_SAPLMRMH_011.
Once the invoice is created, invoice contains the value which is chaned in the exit but idoc log ( we02) shows the unchanged value.
Say segment in e1edp04 filed mwskz was having value 'MAT'.
I am changing it to 'M' . Then invoice is having value as 'M' but log shows 'MAT'.
Any clue??
Regards,
Shweta

Shweta
Inbound IDOCs are created in the system first and then they are sent for processing through Inbound Process Code... You are doing modifications after creation of IDOC, so there is no way you will see modified data in the IDOC....
You may Update the IDOC Data, once you processed it with the Process Code...
Thanks
Amol Lohade

Idoc segment qualifiers

Is there a way to find out the segement qualifier definition in SAP system? Like
int_edidd-segnam = 'E1EDK02'.
IF ekko-bstyp = 'A'.
e1edk02-qualf = '003'.
ELSE.
e1edk02-qualf = '001'.
ENDIF.
When to use '003 and '001'.
Many idoc segement carrier different qualifiers codes...
Thanks
Alok

Hi,
You can find them in Idoc documtation of WE60 transatcion.
You can also find them by going to domian of the particaular idoc field and looking at
the 'Fixed values'.
Regards,
Shan

Idoc segement

Similar Messages

Maybe you are looking for