Edit Std. IDoc Segments

Dear All,
Hope you guys are doing good.
I have a requirement where i have to change the field length of IDoc DELVRY05 segment E1EDL24 Release 700 for the field LGMNG from 15 to 9.
Can someone tell me how can i achieve this?
Regards,
Raj

Hi ,
Follow the steps for custom Idoc type creation .
1.Business Case
SAP R/3 systems send out data through IDoc (Intermediate Document), which in internally has segments and fields containing the data. But sometimes, these fields are not sufficient for a specific end-to-end business scenario as far as data transfer is concerned. So in such scenario, either few fields are to be added or subtracted, or completely new structure- IDoc needs to be created. This are called as Custom u2013 IDOC Types. Following blog gives out step-by-step approach for creation of the same.
2.Development of IDOC types
2.1 Creation of Segment Types
Run T-code u2018WE31u2019 to create segment type, which has fields to contain the data and are added to the segment type in the same transaction. The data stored contained into the segment mesh is finally stored in EDISEGMENT table.
Add your custom fields as per business scenario.
To make it available to other transactions, release the segment created.
Go to Edit -> Set Release
2.2 Creation of IDoc type
Run T-code u2018WE30u2019 to create custom IDoc type. Enter the name of custom IDoc you want to create and click on red box for creation.
Now, it takes you to following screen. Here you can add description for your IDoc type. Also you can specify name of existing IDoc for Copy or Successor mode.
Now, you can maintain attributes of the custom IDoc, which consists of attaching segment type created above to the IDoc type. Also specifying the details of frequency of these segments getting filled i.e. Maximum and Minimum number. Fill the necessary details and release this IDoc type as well.
2.3 Creation of logical message types
Run T-code u2018WE81u2019 to create the logical message types. Go to Edit mode and click New Entry to go to following screen.
Save the entered data.
2.4 Linking Message type and IDoc type.
Run T-Code u2018WE82u2019. Now we have to link these created IDoc types and Message types. Enter the message type name, Basic IDoc type (ZCUST_IDC) and release type to be linked. In the data transfer through ALE, these message types represent the IDOC structure.
Extension field above will be used as per the Extended IDoc type scenario i.e. in case of addition of few more fields into the existing IDoc type.
<<text removed>>
Thanks
Shambhu
Edited by: Matt on Jun 30, 2009 10:43 AM - don't ask for email addressses please.

Similar Messages

To allow to edit existing iDoc segments or to add new segments.

In order to re-process iDoc's there is necessary forst to manipulate the record. A custom transaction(WE19) is required to allow to edit existing iDoc segments or to add new segments without creatinga new idoc.
any clue..
Regrads,
Ramya

hi ramya,
In the test tool WE19 v can able to see the
copy and existing idoc.
create an idoc based on an idoc type.
create an idoc based on a message type.
but mostly v use the first option. Like modify the existing idoc to suit our requirement
Regards....
Arun.
Reward points if useful.

How to edit inbound idoc with data errors in multiple segments and reproces

Hi friends,
i have a requirement for error handling of inbound sales order(ORDERS04) without using WORKFLOW and WE19.
i have seen some function modules like edic_* ..
but my doubt is how to edit the error data(how can i identify the particular error fileds in the segments)and how to reprocess the same idoc.
Please help me...
Thanks in advance

Hi Narasimh,
Please find the following steps to edit IDOC segment after you find the error using WE02.
The example codes can be found in website
http://www.sapgenie.com/sapedi/idoc_abap.htm
STEP 1 - Open document to edit
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
       EXPORTING
            document_number               = t_docnum
       IMPORTING
            idoc_control                  = itab_edidc
       TABLES
            idoc_data                     = itab_edidd
       EXCEPTIONS
            document_foreign_lock         = 1
            document_not_exist            = 2
            document_not_open             = 3
            status_is_unable_for_changing = 4
            OTHERS                        = 5.
STEP 2 - Loop at itab_edidd and change data
LOOP AT itab_edidd WHERE segnam = 'E1EDKA1'.
e1edka1 = itab_edidd-sdata.
IF e1edka1-parvw = 'LF'.
    e1edka1-partn = t_eikto.
    itab_edidd-sdata = e1edka1.
    MODIFY itab_edidd.
    EXIT.
ENDIF.
ENDLOOP.
STEP 3 - Change data segments
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
           TABLES
                idoc_changed_data_range = itab_edidd
           EXCEPTIONS
                idoc_not_open           = 1
                data_record_not_exist   = 2
                 OTHERS                  = 3.
STEP 3a - Change control record
CALL FUNCTION 'EDI_CHANGE_CONTROL_RECORD'
       EXPORTING
            idoc_changed_control         = itab_edidc
       EXCEPTIONS
            idoc_not_open                = 1
            direction_change_not_allowed = 2
            OTHERS                       = 3.
STEP 4 - Close Idoc
Update IDoc status
CLEAR t_itab_edids40.
t_itab_edids40-docnum      = t_docnum.
t_itab_edids40-status      = '51'.
t_itab_edids40-repid       = sy-repid.
t_itab_edids40-tabnam      = 'EDI_DS'.
t_itab_edids40-mandt       = sy-mandt.
t_itab_edids40-stamqu      = 'SAP'.
t_itab_edids40-stamid      = 'B1'.
t_itab_edids40-stamno      = '999'.
t_itab_edids40-stapa1      = 'Sold to changed to '.
t_itab_edids40-stapa2      = t_new_kunnr.
t_itab_edids40-logdat      = sy-datum.
t_itab_edids40-logtim      = sy-uzeit.
APPEND t_itab_edids40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
       EXPORTING
            document_number = t_docnum
            do_commit        = 'X'
            do_update        = 'X'
            write_all_status = 'X'
       TABLES
            status_records   = t_itab_edids40
       EXCEPTIONS
            idoc_not_open    = 1
            db_error         = 2
            OTHERS           = 3.
Hope this will help.
Regards,
Ferry Lianto

Edited Idoc Segments

Hi
I edited some Idocs and reprocessed them after editing. Is there any way we can find after reprocessing what changes were made to Idoc.
Also another Idoc is showing an error, example company code does not exist.But the segments are not in red. Usually when there is an error in the idoc, the segments which have an error are in red. But in my case the segment are not red.
Responses will be highly appreciated and rewarded.
DC

Hi,
>>But the segments are not in red. Usually when there is an error in the idoc, the segments which have an error are in red. But in my case the segment are not red.
just to add what Sergio said
this is not a usuall case I'd say only very few IDocs provide the info
with red segments about where the error is
most of the standard IDocs never show that - but that's the beauty of it:)
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Unable to change the length of field in idoc segment

Dear all,
My requirement is to change the length of a field(Z field) in a segment (Z Segment). I tried the following but in vain
1)Tried to Cancel the release and then change the length of the domain. Unfortunately it is givin an error saying "Error while resetting release of segment ZC9DEMARA01".
I also tried cancelling hte release of extension and then cancelled the release of segment
2) Created a new version, but in new version the earlier fields are diabled. So I am unable to edit.
I have gone through some of the links available in SDN but I could not solve as I am unable to cancel the release in the first step.
[Idoc segment field length changes]
Could you please help me.
Thanks in advance!
regards,
Aravind

Hello Aravind,
I Have created one Segment type with some fields, changed the field length also its working.
just try to cancel the release and change the length of the filed and do it set release again.
Try it .
Thanks,
santhosh

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

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!

IDOC-Segment Created a idoc document against Billing document

Dear All,
Thanks in advance.
Already created a idoc document against Billing document and one of the IDOC segment is not in the IDOC document output segments(WE05) actually it missed the segment.
so i want to add the segment which it was missed during generation of IDOC document against billing document.
Example:
a) IDOC document misses one segment let suppose "Seg1".
b) In "Seg1" it have only one field let suppose "Field1".
c) But "Field1" does not have any value while generation of IDOC document so it doesn't create the respective segment in IDOC document.
d) so here, i want to edit the IDOC document to add the "Seg1" in the IDOC document and reprocessing the IDOC document.
Please help on this issue.
Regards,
Sridhar.

Hello,
          If your requirement is to have the Segment even with only 1 Field, you'll have to create an Idoc Extension in WE30.
         In order to populate the Custom Segment, Use the Customer Function '002' in the IDOC_OUTPUT_INVOIC which is EXIT_SAPLVEDF_002 where you can actually insert the Segment as a Child Segment of an Appropriate Segment.
        You can go for Custom segment with the IDoc Extension so that you dont have to manually insert the Segment again and again while reprocessing it.
Thanks and Regards,
Venkat Phani Prasad Konduri

Adding field in standard IDOC Segment E1EDL24

Hello Friends,
I have an urgent requirement that I have to extend IDOC segment E1EDL24 with two fields PABNR and LFSNR.
When I tries to change the segment in WE31, it shows an error message that you can only modify the segments of customer namespace and cannot modify Standard IDOC Segments.
Can we modify the standard IDOC segments, and if yes, how can we modify the standard IDOC segments. Please clarify.
Points will be rewarded generously.
Regards,
Navin

Hi Naveen,
We cannot Modify the Standard segments. But we have to Create a new Segment and Add these fields.
Then Create an Extended Idoc type
Implement User Exits in Outbound And Inbound ..
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
Reward if Helpful

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

How to populate IDOC segments...

Hello Experts,
I was just tasked to add new fields in an IDOC segment. My question is, how do I populate
those newly created fields? The data will be coming from a purchase order.
Thank you guys and take care!

Hi,
U cannot edit the existing segment u have to create a zsegment with the fields and then under the main segment u have to add this new segment..also u have create a extended idoc in ur case...then only u can add this new segment..also once u create a segment u have to release it...
u have to write the code in the userexit only...
check the sample code which i have done for my requirement for sales order..
*& Include           ZXVEDU02
Program:        Function Module:EXIT_SAPLVEDC_002     Creation Date: 12-04-2006          *
Program Type : Outbound IDOC Enhancement                                                *
Program Description:OutBound IDOC Enhancement                                            *
Modification ID:001                                                                      *
Date         : 25-05-2006                                                                *
Description : 1.The sales organization master data needs to be sent as supplier party
                 details.New segment ZZSALORG is created and attached to the parent
                 segment E1EDK01
               2.Data required to be sent are:
                  1.NAME1- Sales organization name
                  2.STRAS- Address
                  3.TELFX- Fax number
                  4.TELF1- phone number.
               3.ZZSALORG is filled with the above information.
Modification ID:002                                                                      *
Date         : 09-06-2006                                                                *
Description : A new field zstceg added to the segment zzdochdr and it was populated     *
                by selecting stceg field from Kna1 table                                 *
Modification ID:001                                                                      *
Date         : 15-06-2006                                                                *
Description : 1.New segment ZZE1EDP01 is created and attached to the parent segment E1EDP01
               2.Data required to be sent are:
                  1.POSEX- Item number
                  2.UEBTO- Overdelivery tolerance
                  3.UNTTO- Underdelivery tolerance
               3.ZZE1EDP01 is filled with the above information.
*-- Data Declaration--
*-- Constant Declaration--
CONSTANTS: c_1(1)          TYPE c VALUE '1',
           c_langu         LIKE t005t-spras VALUE 'E',
           c_parvw         LIKE vbpa-parvw VALUE 'RG',
           c_e1edk01(7)    TYPE c VALUE 'E1EDK01',
           c_e1edk02(7)    TYPE c VALUE 'E1EDK02',
           c_e1edk17(7)    TYPE c VALUE 'E1EDK17',
           c_e1edka1(7)    TYPE c VALUE 'E1EDKA1',
           c_e1edk14(7)    TYPE c VALUE 'E1EDK14',
           c_004(3)        TYPE c VALUE '004',
           c_001(3)        TYPE c VALUE '001',
           c_002(3)        TYPE c VALUE '002',
           c_re(2)         TYPE c VALUE 'RE',
           c_we(2)         TYPE c VALUE 'WE',
           c_ag(2)         TYPE c VALUE 'AG',
           c_0010(4)       TYPE c VALUE '0010',
           c_zzdochdr(8)   TYPE c VALUE 'ZZDOCHDR',
           c_ze1edk02(8)   TYPE c VALUE 'ZE1EDK02',
           c_zze1edk17(9) TYPE c VALUE 'ZZE1EDK17',
           c_zze1edka1(9) TYPE c VALUE 'ZZE1EDKA1',
           c_pe(2)         TYPE c VALUE 'PE',
           c_y(1)          TYPE c VALUE 'Y',
           c_zze1email(9) TYPE c VALUE 'ZZE1EMAIL',
           c_zzsalorg(8)   TYPE c VALUE 'ZZSALORG',
           c_zze1edp01(9) TYPE c VALUE 'ZZE1EDP01',
           c_e1edp01(7)   TYPE c VALUE 'E1EDP01'.
*-- Variables Declaration--
DATA: lv_vbeln   LIKE vbak-vbeln,
      lv_country LIKE t005t-landx,
      lv_text1   LIKE t042z-text1,
      lv_vzskz   LIKE knb1-vzskz,
      lv_inco    LIKE tinct-bezei,
      lv_cadnr   LIKE akkp-cadnr,
      lv_pernr   LIKE pa0105-pernr,
      lv_parvw   LIKE tpar-parvw,
      lv_adrnr   LIKE tvko-adrnr,
      lv_zinso   LIKE t056z-zinso,
Begin of Mod-002
      lv_stceg   TYPE stceg.
End of Mod-002
Begin of MOD-003
     lv_min_tol TYPE KWMENG,
     lv_max_tol TYPE KWMENG.
End Of MOD-003
TYPES:BEGIN OF t_vbfa,
        vbelv LIKE vbfa-vbeln,
        erdat TYPE erdat,
      END OF t_vbfa.
DATA: i_akkp TYPE akkp.
*-- WorkArea Declaration--
DATA : wa_zdochdr   TYPE zzdochdr,
       wa_ze1edk02 TYPE zze1edk02,
       wa_ze1edk17 TYPE zze1edk17,
       wa_zze1email TYPE zze1email,
       wa_zzsalorg TYPE zzsalorg,
       wa_zze1edp01 TYPE zze1edp01,
       wa_e1edk02   TYPE e1edk02,
       wa_e1edk17   TYPE e1edk17,
       wa_e1edka1   TYPE e1edka1,
       wa_e1edk01   TYPE e1edk01,
       wa_e1edp01   TYPE e1edp01,
       wa_adrc      TYPE adrc,
       wa_pa0105    TYPE pa0105,
       wa_zze1edka1 TYPE zze1edka1,
       wa_zzdochdr TYPE zzdochdr,
       wa_vbfa      TYPE t_vbfa,
       wa_vbpa      TYPE vbpa.
*-- Move data to ZZDOCHDR Segment--
CASE int_edidd-segnam.
WHEN c_e1edk01.
    MOVE int_edidd-sdata TO wa_e1edk01.
*--Begin of MOD001+(Modification ID 001)--
*-- Filling of ZZSALORG segment--
    SELECT SINGLE adrnr
    FROM tvko
    INTO lv_adrnr
   WHERE vkorg EQ dxvbak-vkorg.
    IF sy-subrc EQ 0.
      SELECT SINGLE *
               FROM adrc
               INTO wa_adrc
              WHERE addrnumber EQ lv_adrnr.
      wa_zzsalorg-salorg = dxvbak-vkorg.
      wa_zzsalorg-name1   = wa_adrc-name1.
      wa_zzsalorg-name2   = wa_adrc-name2.
      wa_zzsalorg-stras   = wa_adrc-street.
      wa_zzsalorg-telf1   = wa_adrc-tel_number.
      wa_zzsalorg-telfx   = wa_adrc-fax_number.
      wa_zzsalorg-land1   = wa_adrc-country.
      wa_zzsalorg-strs2   = wa_adrc-str_suppl1.
      wa_zzsalorg-street2 = wa_adrc-str_suppl2.
      wa_zzsalorg-street3 = wa_adrc-str_suppl3.
      wa_zzsalorg-ort01   = wa_adrc-city1.
      wa_zzsalorg-pstlz   = wa_adrc-post_code1.
      wa_zzsalorg-regio   = wa_adrc-region.
      int_edidd-segnam = c_zzsalorg.
      CLEAR int_edidd-sdata.
      MOVE wa_zzsalorg TO int_edidd-sdata.
      APPEND int_edidd.
      CLEAR: wa_adrc,
             wa_zzsalorg.
    ENDIF.
*--End of MOD001+(Modification ID 001)--
    SELECT SINGLE text1
             FROM t042z
             INTO lv_text1
             WHERE land1 EQ dxvbpa-land1
               AND zlsch EQ dxvbkd-zlsch.
    READ TABLE dxvbpa INTO wa_vbpa WITH KEY vbeln = dxvbpa-vbeln
                                      parvw = c_parvw.
    IF sy-subrc EQ 0.
Begin of Mod-002
      SELECT SINGLE stceg
      FROM kna1
      INTO lv_stceg
       WHERE kunnr = wa_vbpa-kunnr.
End of Mod-002
      SELECT SINGLE vzskz
               FROM knb1
               INTO lv_vzskz
               WHERE kunnr EQ wa_vbpa-kunnr
                 AND bukrs EQ dxvbak-bukrs_vf.
      IF sy-subrc EQ 0.
        SELECT SINGLE zinso
                 FROM t056z
                 INTO lv_zinso
                 WHERE vzskz EQ lv_vzskz
                   AND waers EQ wa_e1edk01-curcy.
        wa_zzdochdr-zdoctitle = dobject-objky.
        wa_zzdochdr-zdate      = dobject-erdat.
        wa_zzdochdr-zmestyp    = dobject-kschl.
        wa_zzdochdr-zmedium    = dobject-nacha.
        wa_zzdochdr-zlang      = dobject-spras.
        wa_zzdochdr-zttype     = dxvbkd-kdkg1.
        wa_zzdochdr-zpaymethod = dxvbkd-zlsch.
        wa_zzdochdr-zpaytext   = lv_text1.
        wa_zzdochdr-zintonpymt = lv_zinso.
Begin of Mod-002
        wa_zzdochdr-zstceg     = lv_stceg.
End of Mod-002
        int_edidd-segnam = c_zzdochdr.
        CLEAR int_edidd-sdata.
        MOVE wa_zzdochdr TO int_edidd-sdata.
        APPEND int_edidd.
        CLEAR : wa_zzdochdr.
      ENDIF.
    ENDIF.
*-- Move data to ZZE1EDK02 Segment--
WHEN c_e1edk02.
    MOVE int_edidd-sdata TO wa_e1edk02.
    IF wa_e1edk02-qualf EQ c_004.
      SELECT SINGLE vbelv FROM vbfa INTO wa_vbfa
                         WHERE vbeln EQ lv_vbeln
                         AND   vbtyp_v EQ 'B'.
      IF sy-subrc EQ 0.
        SELECT SINGLE erdat FROM vbak INTO wa_vbfa
        WHERE vbeln EQ wa_vbfa-vbelv.
        int_edidd-segnam = c_ze1edk02.
        CLEAR int_edidd-sdata.
        MOVE wa_vbfa TO int_edidd-sdata.
        APPEND int_edidd.
        CLEAR wa_vbfa.
      ENDIF.
    ENDIF.                                  " IF ended for "IF wa_e1edk02-qualf = '004'" condition.
**-- Move data to ZZE1EDK17 Segment--
WHEN c_e1edk17.
    MOVE int_edidd-sdata TO wa_e1edk17.
    IF NOT dxvbkd-lcnum IS INITIAL.
      SELECT SINGLE inco1
                    inco2
               FROM akkp
               INTO i_akkp
              WHERE lcnum EQ dxvbkd-lcnum.
      IF sy-subrc EQ 0.
        IF wa_e1edk17-qualf EQ c_001.
          wa_ze1edk17-lkond = i_akkp-inco1.
          wa_ze1edk17-qualf = wa_e1edk17-qualf.
          SELECT SINGLE bezei
                   FROM tinct
                   INTO lv_inco
                  WHERE spras EQ 'E'
                    AND inco1 EQ i_akkp-inco1.
          IF sy-subrc EQ 0.
            wa_ze1edk17-lktext = lv_inco.
          ENDIF.
        ELSEIF wa_e1edk17-qualf EQ c_002.
          wa_ze1edk17-qualf = wa_e1edk17-qualf.
          wa_ze1edk17-lktext = i_akkp-inco2.
        ELSE.
        ENDIF.
        int_edidd-segnam = c_zze1edk17.
        CLEAR int_edidd-sdata.
        MOVE wa_ze1edk17 TO int_edidd-sdata.
        APPEND int_edidd.
        CLEAR wa_ze1edk17.
      ENDIF.
    ENDIF.                                       " IF ended for not initial condition.
*--Move data to zze1edka1 Segment--
WHEN c_e1edka1.
    MOVE int_edidd-sdata TO wa_e1edka1.
*--Checking the wa_e1edka1-parvw field for 'RE'--
    IF wa_e1edka1-parvw EQ c_re.
      IF NOT dxvbkd-lcnum IS INITIAL.
        SELECT SINGLE cadnr
         FROM akkp
         INTO lv_cadnr
        WHERE lcnum EQ dxvbkd-lcnum.
        IF sy-subrc EQ 0.
          SELECT SINGLE *
                   FROM adrc
                   INTO wa_adrc
                  WHERE addrnumber EQ lv_cadnr.
          wa_zze1edka1-parvw = wa_e1edka1-parvw.
          wa_zze1edka1-partn = wa_e1edka1-partn.
          wa_zze1edka1-land1 = wa_adrc-country.
          wa_zze1edka1-name1 = wa_adrc-name1.
          wa_zze1edka1-name2 = wa_adrc-name2.
          wa_zze1edka1-stras = wa_adrc-street.
          wa_zze1edka1-strs2 = wa_adrc-str_suppl1.
          wa_zze1edka1-ort01 = wa_adrc-city1.
          wa_zze1edka1-pstlz = wa_adrc-post_code1.
          wa_zze1edka1-regio = wa_adrc-region.
          int_edidd-segnam = c_zze1edka1.
          CLEAR int_edidd-sdata.
          MOVE wa_zze1edka1 TO int_edidd-sdata.
          APPEND int_edidd.
          CLEAR: wa_adrc,
                 wa_zze1edka1.
        ENDIF.
      ENDIF.
    ENDIF.                                               " IF ended for "IF wa_e1edka1-parvw EQ 'RE'" condition.
*--Checking the wa_e1edka1-parvw field for 'WE'--
    IF wa_e1edka1-parvw EQ c_we.
      IF NOT dxvbkd-lcnum IS INITIAL.
        SELECT SINGLE cadnr
          FROM akkp
          INTO lv_cadnr
         WHERE lcnum EQ dxvbkd-lcnum.
        IF sy-subrc EQ 0.
          SELECT SINGLE *
                   FROM adrc
                   INTO wa_adrc
                  WHERE addrnumber EQ lv_cadnr.
          wa_zze1edka1-parvw = wa_e1edka1-parvw.
          wa_zze1edka1-partn = wa_e1edka1-partn.
          wa_zze1edka1-land1 = wa_adrc-country.
          wa_zze1edka1-name1 = wa_adrc-name1.
          wa_zze1edka1-name2 = wa_adrc-name2.
          wa_zze1edka1-stras = wa_adrc-street.
          wa_zze1edka1-strs2 = wa_adrc-str_suppl1.
          wa_zze1edka1-ort01 = wa_adrc-city1.
          wa_zze1edka1-pstlz = wa_adrc-post_code1.
          wa_zze1edka1-regio = wa_adrc-region.
          int_edidd-segnam = c_zze1edka1.
          CLEAR int_edidd-sdata.
          MOVE wa_zze1edka1 TO int_edidd-sdata.
          APPEND int_edidd.
          CLEAR: wa_adrc,
                 wa_zze1edka1.
        ENDIF.
      ENDIF.
    ENDIF.                                             " IF ended for "IF wa_e1edka1-parvw EQ 'WE'" condition.
*--Checking the wa_e1edka1-parvw field for 'AG'--
    IF wa_e1edka1-parvw EQ c_ag.
      IF NOT dxvbkd-lcnum IS INITIAL.
        SELECT SINGLE cadnr
          FROM akkp
          INTO lv_cadnr
         WHERE lcnum EQ dxvbkd-lcnum.
        IF sy-subrc EQ 0.
          SELECT SINGLE *
                   FROM adrc
                   INTO wa_adrc
                  WHERE addrnumber EQ lv_cadnr.
          wa_zze1edka1-parvw = wa_e1edka1-parvw.
          wa_zze1edka1-partn = wa_e1edka1-partn.
          wa_zze1edka1-land1 = wa_adrc-country.
          wa_zze1edka1-name1 = wa_adrc-name1.
          wa_zze1edka1-name2 = wa_adrc-name2.
          wa_zze1edka1-stras = wa_adrc-street.
          wa_zze1edka1-strs2 = wa_adrc-str_suppl1.
          wa_zze1edka1-ort01 = wa_adrc-city1.
          wa_zze1edka1-pstlz = wa_adrc-post_code1.
          wa_zze1edka1-regio = wa_adrc-region.
          int_edidd-segnam = c_zze1edka1.
          CLEAR int_edidd-sdata.
          MOVE wa_zze1edka1 TO int_edidd-sdata.
          APPEND int_edidd.
          CLEAR: wa_adrc,
                 wa_zze1edka1.
        ENDIF.
      ENDIF.                                       " IF ended for "IF NOT dxvbkd-lcnum IS INITIAL" condition.
    ENDIF.                                         " IF ended for "IF wa_e1edka1-parvw EQ c_ag" condition.
*--Checking the wa_e1edka1-parvw field for 'Y'--
    IF wa_e1edka1-parvw+0(1) EQ c_y.
      SELECT SINGLE parvw
              FROM tpar
              INTO lv_parvw
              WHERE parvw EQ wa_e1edka1-parvw
                AND nrart EQ c_pe.
      IF sy-subrc EQ 0.
        SELECT SINGLE pernr
          FROM vbpa
          INTO lv_pernr
          WHERE vbeln EQ dxvbpa-vbeln
          AND   parvw EQ lv_parvw.
        IF sy-subrc EQ 0.
          SELECT SINGLE usrid_long
           FROM pa0105
           INTO wa_pa0105-usrid_long
           WHERE pernr EQ lv_pernr
             AND usrty EQ c_0010.    " communication type email
          wa_zze1email-zparvw = wa_e1edka1-parvw.
          wa_zze1email-zname   = wa_e1edka1-name1.
          wa_zze1email-zemail = wa_pa0105-usrid_long.
          int_edidd-segnam = c_zze1email.
          CLEAR int_edidd-sdata.
          MOVE wa_zze1email TO int_edidd-sdata.
          APPEND int_edidd.
          CLEAR: wa_adrc,
                 wa_zze1email,
                 wa_pa0105.
        ENDIF.
      ENDIF.
    ENDIF.                              " IF ended for "IF wa_e1edka1-parvw EQ 'Y'" condition.
*--Begin of MOD003 (Modification ID 003)--
*-- Move data to ZZE1EDP01 Segment--
WHEN c_e1edp01.
    MOVE int_edidd-sdata TO wa_e1edp01.
    wa_zze1edp01-posex = wa_e1edp01-posex.
     wa_zze1edp01-uebto = dxvbap-kwmeng + ( dxvbap-kwmeng * dxvbap-uebto / 100 ).
     wa_zze1edp01-untto = dxvbap-kwmeng - ( dxvbap-kwmeng * dxvbap-untto / 100 ).
    wa_zze1edp01-uebto = dxvbap-uebto.
    wa_zze1edp01-untto = dxvbap-untto.
    int_edidd-segnam = c_zze1edp01.
    CLEAR int_edidd-sdata.
    MOVE wa_zze1edp01 TO int_edidd-sdata.
    APPEND int_edidd.
    CLEAR: wa_zze1edp01.
*--End of MOD003 (Modification ID 003)--
WHEN OTHERS.
ENDCASE.
Regards,
Nagaraj

How To Edit Failed IDocs Through Report ?

Hi
I have the requirement of editing (Modifying) IDocs through a report program..
( My program displays the content of a specified segment of failed IDocs in the ALV format..
Then the changes made to those fields in ALV have to be updated in those failed IDocs.. So that i can reprocess the IDocs.. )
Is there any BAPI or BADI or Any other solution to edit IDocs through a report....??
I dont want to use BDC as the report program is meant for editing huge number of failed IDocs..
Please help me..
Thanks a lot,
Raj

There is a similar POST open in DATA TRANSFER FORUM...

Idoc segment limit

Good morning:
I have read that the idocs segment maximum length is 1000 characters, but i need to generate an idoc with more length at least 1600 characters, i would like to use idocs for having all the standard status process for control it, does anybody know any alternative or procedure?
Points will be rewarded for value answers of course
Thanks in advance
Regards

Hi,
If you are creating your own idoc then its better to create the segments each of length 1000 characters.
If you want to use the standard one thne you have to extend the idoc by adding child segments to the existing segments.
Its not the space b/n segments,
It means each segment can contain fileds each of lenght 1000.
There is no space concept b/n segments.
Regards,
sasi
Edited by: sasidhar yalamanchili on Apr 16, 2008 4:25 PM

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

IDoc segment issue

Hi,
I have file to Idoc scenario, where my input file structure like below and need to create Idoc segments in SAP.
Input Structure:
Record (1--Unbounded)
Header (1-1)
Item_Details (1- Unbounded)
Child_ItemsInfo (1 -Unbounded)
Item_1 (1--1)
abc
def
Item_2 (1--1)
abc
def
Item_3 (1--1)
abc
def
Now..I need to generate an Idoc segment "Z1ABCD", as many as child Item segments(Item_1,Item_2,Item_3) occurs in my input structure. I have used duplicate subtree on Idoc segment "Z1ABCD" and copied 2 more times.Now I have 3 "Z1ABCD" segments in my IDoc.
Lets say, if my input structure have 2 Child_ItemsInfo, then I need to generate 6 "Z1ABCD" segments in Idoc. I'm able generate these segments.
My code generating all the Item_1 segments then Item_2 segments like that...But I'm expecting a "Z1ABCD" segment at Item_details node level...like Item1,2,3 and then Item1,2,3....Please help me out!
Note: My mapping looks like this;
Item_1 ->remove context>Split by value(each) ->CollapseContext->Z1ABCD
Item_2 ->remove context>Split by value(each) ->CollapseContext->Z1ABCD
Item_3 ->remove context>Split by value(each) ->CollapseContext->Z1ABCD
the target structure which I'm lookin for like below...(for 2 Child_ItemsInfo from my input structure)
1.Z1ABCD (Item_1 info)
2.Z1ABCD (Item_2 info)
3.Z1ABCD (Item_3 info)
4.Z1ABCD (Item_1 info)
5.Z1ABCD (Item_2 info)
6.Z1ABCD (Item_3 info)
But my code generating the segments like below;
1.Z1ABCD (Item_1 info)
2.Z1ABCD (Item_1 info)
3.Z1ABCD (Item_2 info)
4.Z1ABCD (Item_2 info)
5.Z1ABCD (Item_3 info)
6.Z1ABCD (Item_3 info)
Esha
Edited by: esha nadh on Mar 9, 2011 9:14 PM

I am bit confused .
Why are you using this ...
remove context-->Split by value(each) --->CollapseContext
Do Direct assignment like below
even the context should not change . it shoule be default .,
Item_1 - > Z1ABCD
Item_2 - > Z1ABCD
Item_3 - > Z1ABCD
isnt it working fine ??????
actually it should ..
In your case .
IZ1ABCD for Item_1 coming together because . you Used removeContext So Both Item_1 comest together .. and then you doing transformation .. so the result are coming together...
Try Like Direct assignment . I hoping it should work fine
regds
PS

Regarding EDI: Syntax error in IDoc (segment cannot be identified)

Hi,
My requirement is that I was adding two diffrent field values under two diffrent segments as "E1EDKA1" and "E1EDK02" in outbound invoice IDOCS, INVOIC02 (process code: SD09 - IDOC_OUTPUT_INVOIC).
I am getting the IDOC number through Tcode "VF02". Can any body give me idea how to check that syntax error in debug mode.
Please find the following error details using TCODE "WE02".
*EDI: Syntax error in IDoc (segment cannot be identified)*
*Message no. E0 078*
*Diagnosis*
*The segment E1EDKA1 does not occur at the current level of the basic type INVOIC02 (extension ).*
*This error can have several reasons:*
*The segment E1EDKA1 is assigned to a group whose header segment does not occur.*
*The segment E1EDKA1 does not exist in the syntax description of the basic type INVOIC02 (extension ).*
*The sequence of segments in the group in which the segment appears is incorrect.*
*Previous errors ('mandatory' segment or group missing) may be due to this error.*
Please help me to resolve this problem. <REMOVED BY MODERATOR>
Regards,
Skumar.
Edited by: Alvaro Tejada Galindo on Apr 28, 2008 1:09 PM

It seems that you added segment E1EDKA1 at a place where it is not supposed to be. That's where this error is coming from. The structure of every IDOC is definded by SAP standard and you cannot change the sequence or the level of standard segments. If you require a certain field at a certain level you have to add that field to a Z-segment and then add that Z-segment where appropriate in your extension.
Hope that helps,
Michael

Edit Std. IDoc Segments

Similar Messages

Maybe you are looking for