Hierarchy lost for IDoc segments

The following has occured:
We have our own IDoc created (ZNAME_60) and put several non-mandatory segments in them, with a 3-level relation between them.
At one point we have builded a new version of this IDoc (ZNAME_80) and also with the same non-mandatory segments in them. However, we have named the segments a different name, their contents (fields and types) are identical.
Now by accident someone has runned a program that generates a massive amount of outgoing IDoc's (over 1 million) of the NEW defined type (ZNAME_80) but he has used as parameter the old type (ZNAME_60).
If we now use transaction WE02 to view the IDoc's, we get to see ALL segments in a flat list (the hierarchy of the IDoc seems to have disappeared).
Since these IDoc's have status 29 (first status 02 of syntax error) that there is a problem in the ALE layer, they will not be sent.
My question:
How does SAP determine the hierarchy of the segments with an IDoc (simply filling the fields SEGNUM and PSGNUM in the table EDID4 does not work)?
Regards,
Rob.

Hi Sriram,
When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system
Is it custom segments .
Regards,
Madhu.

Similar Messages

Data elements for IDoc Segments to non-SAP system

Hi,
I need to create IDocs for transferring data to non-SAP system. When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system? Because there are many fields where the field attributes of SAP system do not match the corresponding fields of receiving non-SAP system.
Thanks in advance!!
Regards,
Sriram

Hi Sriram,
When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system
Is it custom segments .
Regards,
Madhu.

Value for IDoc Segment field SEGMENT

Hello,
In the Integration Repository, while creating Message Mapping between a flat file (inbound) & an IDoc (outbound), I'm getting an error that not all target fields are mapped. In the target structure (IDoc), each segment has a field named SEGMENT. Can someone please tell me what value should go here. These are not part of the IDoc but seem to be a requirement in XI message mapping.
There is also a segment called BEGIN (Type - xsd:string) which is defined as required. Please write as to what should be populated in this segment.
Any help is greatly appreciated.
Thanx in advance.
Homiar.

My current scenario is
File Adapter -
> XI -
> SAP R/3 (Idoc Adapter).
I will be using FIDCPP2 IDOC.
1. For an instance following is the structure, in this case how can I achieve getting a set of data in one IDOC and another set in other IDOC based on document no.
CC Doc No. line items
UK01 456 1
UK01 456 2 -
> IDOC 1
UK03 456 3
UK04 450 1
UK04 450 2 -
> IDOC 2
UK04 450 3
i). Is there any way to create instances of idocs in XI or any alternative way out.
ii). Where/ how can I give the condition, that based on Document No. should create another IDOC instance.

Tcode for IDOC

Dear friends ,
can any one give me important Tcodes for IDOC & workflow
Reddy

Tcode list for ALE IDOC:
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
WE02     List Of All Idocs Created. (Default, Additional, EDI)
WE05     List Of Idocs Created.    (Standard, Additional)
WE06     Active Monitoring For Idoc Processing.
WE07     Idoc Statistics.
WE08     Display View u201CFile Statusu201D:Overview-Path Name.
WE09     Idoc Search For Business Contents (Database).
WE10     Idoc Search For Business Contents (Archive).
WE12     Modification Of Outbound File, Triggering Inbound Processing.
WE14     Process All Selected Idocs.
WE15     Selection Program For Issuing Output.
WE16     Trigger Inbound Processing.
WE17     Trigger Status Processing.
WE18     Generate Test Status File For Outbound Idocs.
WE19     Test Tool For Idoc Processing
WE20     Partner Profile.
WE21     Ports In Idoc Processing.
WE23     Display Test Catalog Test Idoc Interface.
WE24     Maintain Table View. Direction-1.(Outbound)
WE27     Maintain Table View. Direction-2.(Inbound)
WE30     Develop Idoc Type.
WE31     Develop Idoc Segments.
WE32     View Development.
WE33     Maintain Table Views.
WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
WE40     Display System Process Code.
WE41     Display View: Logical Msg Overview. For Outbund.
WE42     Display View: Logical Msg Overview. For Inbound.
WE43     Display Status Records.
WE44     Display Partner Types
WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
WE46     Global Parameter For Idoc Interface.
WE47     Status Maintenance.
WE50     Display Text For Process Code System.
WE54     Idoc Function Module For File Name
WE56     Display Status Process Code
WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
WE58     Text For Process Code Status.
WE60     Documentation For Idoc Type.
WE61     Documentation For Idoc Record Type.
WE62     Documentation For Idoc Segment Type.
WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
WE64     Process Code In Idoc Inbound And Outbound.
WE70     Conversion Table For Basic Types.
WE71     Conversion Table For Extensions.
WE72     Conversion Table For Field DOCTYP.
WE73     Conversion Table For Logical Message Type.
WE81          EDI:Logical Message Type.
WE82     Message Types And Assignment To Idoc Types.
WE84     Assignment Table Between Idoc And Application Field.
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
BD10     Send Material (Matmas)
BD11     Get Material.
BD12     Send Customer.
BD13     Get Customers
BD14     Send Vendor.
BD15     Get Vendor.
BD16     Send Cost Center. (Cosmas)
BD17     Request Cost Center.
BD18     Send G/L Accounts.
BD19     Get Master Data G/L Accounts.
BD20     Inbound Processing Of Idocs Ready For Transfer.
BD21     Creating Idoc Types For Change Pointers.
BD22     Delete Change Pointers.
BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
BD24     Send Cost Elements.
BD25     Send Activity Type (COAMAS)
BD26     Request Activity Type
BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
BD28     Cost Center/ Cost Elements: Send Control Records.
BD30     Material Bom Distribution. (Bommat).
BD31     Document Structure Distribution. (Bomdoc)
BD32     Plant Allocation To Material Boms Distribution.
BD33     Distribution Of Material Variants. (STTMAT)
BD34     Distribution Of Boms (BOMORD)
BD35     ALE: Send Business Process Group.
BD36     ALE: Send Business Process.
BD37     ALE: Send Business Process Price.
BD40     Generate Idocs For Serialization Group From Change Pointers.
BD41     Dispatch Of Idocs Of Serialization Group.
BD42     Check Dispatch Status Of Idocs Of Serialization Group.
BD43     Processing Inbound Idocs Of Serialization Group.
BD44     Change View u201CSerialization Groupu201D.
BD47     Dependence Between Methods.
BD48     Dependence Between Methods And Message Type.
BD50     Activate Change Pointers For Message Type.
BD51     Characteristics Of Inbound Function Module.
BD52     Determine Work Area.
BD53     Reduce Message Type.
BD54     Change View: Logical Systems
BD55     Idoc Conversion.
BD56     Maintain Idoc Segment Filters.
BD57     Link Type And Serialization Type Of Message Type.
BD58     Convert Organizational Unit.
BD59     Allocation Of Object Type.
BD60     Additional Data For Message Type.
BD61     Activate Change Pointers Generally.
BD62     Display Conversion Rule.
BD63     Transport Of Ale Tables For A Message Type.
BD64     Display Distribution Model.
BD65     Maintain Idoc Type Required Fields.
BD66     Change Idoc Fields.
BD67     Function Module For ALE/EDI Overview.
BD68     Maintain List.
BD69     Assignment Of Idoc Type To Message Type.
BD70     Cross-System Comparison Of Number Range Objects.
BD71     Attributes For Receiver Determination.
BD72     Active Events For ALE/EDI
BD73     Start Error Handling For Non-Posted Idocs.
BD75     Status Conversion With Trfc Execution.
BD77     Generate Transport Requests For Distributing ALE Customizing Data.
BD78     Monitoring Ale Customizing Data Transport
BD79     ALE IDOC Segments - Conversion Rule
BD81     Filter Objects For BAPI Parameter Filtering
BD82     Generating Partner Profile
BD83     Re-Processing Incorrect Outbound Odocs.
BD84     Re-Processing Of Idocs After ALE Input Error.
BD85     Consistency Check: Reassignment Between Two System.
BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
BD87     Select Idocs
BD89     Customizing Data Modeling For Distribution Model.
BD91     Distribute All Characteristics Via ALE.
BD92     Distribute Class Via ALE: Send Direct.
BD93     Distribution Of Classification Data Via ALE.
BD95     Ale Object View
BD96     Filter Object For Receiver Determination Of Methods.
BD97     Assign RFC Destination For Synchronous Method Calls.
BD98     Consistency Check With Workflow Link
BD99     Dependencies Between Message Types.
BD100     Display Serialized Idocs. (Serialization Using Object Types)
BD101     Serialization Using Object Types: Consistency Check.
BD102     Ale: Outbound Channel Registry.

Fill IDOC segment, E1IDBW1. For PEXR2002 Basic Type

Hello Team.
We send the IDOC for the Basic Type PEXR2002, Message Type PAYEXT.
This IDOC doesn't fill the Segment E1IDBW1 (IDoc header - special instructions (INP) )
I'm review some notes(1164524) and said to fill this segment it's neccesarie config the IHC.
But doesn't have this functionality.
It's possible fill the segment E1IDBW1 in a user exit or any other enhacement at creation idoc moment?
My idea is used the FM
CALL FUNCTION 'GET_SEGMENT_POS_FOR_INSERT'
    EXPORTING
      I_BASIS_TYPE            = ch_edidc-idoctp
      I_EXT_TYPE              = ch_edidc-cimtyp
      I_SEGMENT_TYPE          = 'E1IDBW1'
    IMPORTING
      E_INDEX                 = li_tabix
    TABLES
      IT_EDIDD                = t_edidd
    EXCEPTIONS
      BASIS_TYPE_NOT_FOUND    = 1
      EXTENSION_NOT_FOUND     = 2
      EXTENSION_ERROR         = 3
      INVALID_IDOC_DEFINITION = 4
      IDOC_ERROR              = 5
      INVALID_SEGMENT_TYPE    = 6
      INVALID_START_INDEX     = 7
      NO_MORE_POSITION        = 8
      TOO_MANY_SEGMENTS       = 9
      OTHERS                  = 10.
To Fill 2 constants in this segment.
Do you have any other idea?
Thanks
Edited by: David Lezama Gonzalez on Sep 1, 2011 2:51 PM

Hi,
Basically the segment E1IDBW1 will always be filled via user exit.
If you work with the IHC (In-House-Cash) application you have to fill
the E1IDBW1 segment as described in note 626577.
If you don't work in an IHC environment the following conditions must
be fulfilled:
1. The payment program has to fill certain fields (e. g. REGUH-DTAWS,
REGUH-DTWS1 - REGUH-DTWS4).
2. If this is fulfilled the payment data (REGUH, REGUP tables) will
be filled. The instruction keys will be moved to IDOC segment
E1IDKU3.
3. In user exit EXIT_SAPLIEDP_002 you can take over the instruction
keys from segment E1IDKU3 into E1IDBW1.
You may also read note 496663, this note explains about user exit
EXIT_SAPLIEDP_002 to populate this field in the idoc.
Also, you can check the note:
580321 - RFFOEDI1: BTE process 00002441 (Change IDoc)
REgards,
Cristiano

IDOC Segments for an External FI system

Hi,
Can someone please tell me the IDoc segments (need structure) that are used to bring data into SAP from an external FI system.
Thanks
Salim

Hi,
As for as i know EANs are not relevant to unit conversion. This is a number which uniquely identifies a material for a particular UoM.
And regarding the numerator and denominator, check whether any logic is added in the corresponding segment which overwrites the value

IDOC segment for VBKD-BSTKD_E

Hi,
I am using ORDERS04 as basic type for order creation from iDOC.
For one of my requirment I need the iDOC segment for VBKD-BSTKD_E field. The field is in purchase order data at header > Ship to party view > Purchase order no.
Thanks
Sanjay

Hi,
you have to fill the segment E1EDK02 with:
E1EDK02-QUALF (qualifier) = '044' (purchase order number consignee)
E1EDK02-BELNR = Purchase Order Number
E1EDk02-DATUM = Purchase Order Date
Kind Regards.
Andrea

How to generate multiple files for each segment in the IDOC

Hi,
I have a IDOC with multiple segments, for each segment, a file needs to be generated,
There is only one target structure. Please let me know as to how do we handle this requirement in XI.
Regards,
Younus

Use multimapping in message mapping. Then map the Idoc node to the Message Type of File.
Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure
Regards,
Prateek

Populating value in idoc segment E1EDP02 for INVOIC01- incoming invoice

Hi Friends,
I am working to get the incoming freight invoice posted to MIRO, using
IDOC : INVOIC01
message type: INVOIC
process code: INVL
function module : IDOC_INPUT_INVOIC_MRM
Vendor does not send the PO number only send the bill of lading number(shipment number). So i have customised the IDOC with one segment for getting bill of lading number. My requirement is get bill of lading number and then get PO no and populate into segment E1EDP02. I am not able to populate this field and hence each time the IDOC fails with message :
Required field BELNR(001) is missing in segment E1EDP02
Required field ZEILE(001) is missing in segment E1EDP02
Please tell me how to get this field populated and get the issue resolved. I have been trying to figure out for couple of days but no success OR My approach is incorrect for posting invoice to MIRO with populating field segment.
Please suggest.
Thanks
Deepak

Thanks everyone for getting the issue resolved. I have implemented implicit enhanencement and before the function module strarts procesing, I loop over segments and fill up the PO number to E1EDP02 for bill of lading number. There was also a case of error handling for IDOC. That is to check if the amount sent by vendor is correct as compared to the amount on the shipment cost docuemnt, if they dont match then I need to send an email to the business informing them for bill of lading number and amount. There is also another check to find out if the bill of lading number has already been invoiced, if invoiced I again need to inform the business user.
So keep all the requirements in mind I went with Implicit enhancement, thus populating the required segment and if the validations fail for amount or invoice document already generated, then I send the mail to business with bill of lading number and reason of failure. In such case IDOC is not executed and after sending the mail, the logic exits out of function module.
I

Idoc segment for shpmnt notification for idoc type shpmnt02

Hi gurus,
I have to find the idoc segment for shipment notification,idoc type which we are going to use is shpmnt02 or shpmnt01,Can any one of you please tell me the idoc segments for this idoc type with fields and table name?.Thanks in advance.

Hi Nagarathinam
You can use transaction WE60 for documentation on IDOCs
Best regards,
Chris

TAX ASSESSMENT BASIS MISSING IN SEGMENT E1EDK04 FOR IDOC INVOIC

Hello,
Tax assesment basis is missing in segment E1EDK04 for IDOC INVOIC. In EDI messages,Tax assesment basis has to be sent in TAX segment together with VAT rate. When there is only one VAT rate this is not a problem as tax assessment basis is the total net amount (And we have it in the IDOC). On the other hand when there is more than one VAT rate in the invoice, we don't have in the IDOC the Tax assesment basis of each VAT rate.
Did someone experience this issue ? How did you handle it ?
Regards.
Eric.

Dear Eric
The latest pack available now for these components are (for PI 7.1)
SAP BASIS 7.11 support package 6
SAP HR 6.04 with Support Package 44
If you are in PI 7.0 then I suggest you download the latest patch from marketplace.
Sourabh

Node function to use for relating two idoc segments from source in mesmapp

Hi Sap All.
here i have got a requirement to do a graphical mapping between Souce Idoc Structure to target file structure .
here i have got aspecific requirement from the Functional saying that they want
for a segment from source idoc with name E1EDL24-NTGEW should be mapped with shipment_detail-nett_weight
and the conditon here is There should be a corresponding entry in E1EDL24 for each E1EDL44?(other) segment type.
can nay body help me in guiding how and what node functions do i need to use here to ge the solution.
regards.
Varma

Varma,
If you could give a sample that would be great!
raj.

SEGMENT FOR WITHOLDING TAX DATA FOR IDOC CREMAS03

Hi all!
Is there any segment for withholding tax data when creating creditor master data with IDoc CREMAS03? I need an other IDoc for this purpose?
Thanks in advance
Zapla

Dear Atul,
In function module AC_DOCUMENT_CREATE there is the structure
T_ACCWT to pass the calculated tax items. In the
BAPI_ACC_DOCUMENT_POST the corresponding BAPI structure has been added
with release 6.0. For older releases it is posssible to pass the
withholding tax items in structure EXTENSION1 and map it to T_ACCWT
using a customer exit or the Business Transaction Event RWBAPI01.
For the corresponding IDOC ACC_DOCUMENT the same holds.
From release 6.0 on there is the IDOC segment E1BPACWT09 for
passing WT information, in older releases E1BPPAREX
can be used to pass the extension data, see note 487722.
I hope this can help You.
Mauri

Idoc segment for updating Sales order item dates

Hi All,
I would ike to update the sales order item dates (loading date, Goods Issuance date etc) from an IDOC.
please let me know the Idoc segment and fields that need to be filled in?
Thanks in advance.
Regards,
Zeeshan.

Hi,
Here are some details of the segments in the idocs -
SEGNAM Segment Name E1EDL20
VBELN Sales and Distribution Documen 180001539
SEGNAM Segment Name E1EDL18
QUALF IDOC Qualifier: Control (Deliv PIC : Picking with flow records (inbound)
SEGNAM Segment Name E1EDL18
QUALF IDOC Qualifier: Control (Deliv PGI : Post delivery goods issue (inbound)
SEGNAM Segment Name E1EDT13
QUALF IDOC Qualifier: Date (Delivery 010 : Picking
NTANF Constraint for activity start 20090808
ISDD Actual start: Execution (date) 20090808
SEGNAM Segment Name E1EDL24
POSNR Item number of the SD document 10
MATNR Material Number 1112
WERKS Plant SG01
KDMAT Material belonging to the cust 1112
LFIMG Actual quantity delivered (in 55
VRKME Sales unit EA
POSEX External item number 10
ORMNG Original Quantity of Delivery 55
SEGNAM Segment Name E1EDL41
QUALI Qualifier for Reference Data o 001 : Purchase order data of customer
BSTNR Customer purchase order number 4500004668
BSTDT Customer purchase order date 10
POSEX Item Number of the Underlying 10
SEGNAM Segment Name E1EDL37
Regards,
Shamma

The IDOC-SDATA for the segment E1EDP01 does not have the whole value passed

HI
I am triggring the ORDERS05 Idoc from TCode - WE19 .
In the E1EDP01 segment I have populated the quantity field , UOM field , currency field and the plant field.
I am facing the issue
1) It is not updating the plant field in R/3 orders that are created .
2) I debugged the code and found that the data for the currency field and the plant field is not being pulled in the IDOC-SDATA for the segment E1EDP01 .
Any idea why is this happening
Thanks
Nikhil

HI
I got the answer for it.
This has to be delt in the E1EDP02 segment with the qualifier value as 083 and the document value as the plant
Thanks
Nikhil

Hierarchy lost for IDoc segments

Similar Messages

Maybe you are looking for