How to extend Generated Idoc types?

I want to create Idoc type ZMRESCR01 as an Extension of Basic Idoc type MRESCR01.
I have created the Segments that I want to add to the Basic type using transaction WE31.
When I try to extend the Basic Idoc type with transaction WE30, the error message "Action is not possible for generated idoctypes" appears.
In Note 913901, I have read that I can extend this Basic type using transactions BDFG and BDBG, but I can't find any documentation about how to do it.
Can you point me to any documentation or show me how to extend Generated Idoc types?
Reward points are waiting for responses.

Hello,
I will answer my own question.
After sending an OSS note to SAP, this is what they answered (my words):
The error is not that in most recent releases extension of generated Idoctypes is not allowed. The error is that in previous versions it was possible to extend such Idoctypes!
In fact, Note 913901, corrected this error. So, what you have to do if you want to extend this Idoctype is:
1. Copy the BAPI of the method I want to extend (For me, it is BAPI_RESERVATION_CREATE) and modify it, adding the new fields.
2. Use transaction BDBG to create a new ALE interface. Then a new Idoctype, new Inbound and Outbound Function Modules and new Message will be created for my new BAPI.
This is the Note I created: 0001040039.
As for the documentation on transaction BDBG, they provided me a link to the Sap help:[http://help.sap.com/saphelp_nw70/helpdata/en/78/21740f51ce11d189570000e829fbbd/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/78/21740f51ce11d189570000e829fbbd/frameset.htm].
I hope this helps someone,
Narcís Abio

Similar Messages

How to extended Generated IDoc type of MRESCR01 (Material Reservation )

Hi Experts ,
My scenario : I am receiving Material reservation data from SAP PI team , There is some extra fields .
My approach 1 . I have to extended the basic idoc MRESCR01 , here is problem 'Action is not possible for generated IDoc types' .
I have seen many posts for the same but I did nt get proper post for the same .
and also how to create ALE -BAPI interface by using BDBG , Please help this scenario .
Thanks ,
Jay.

Solution : new Message Type (By reducing MATMAS)

How to extend Generated Idoc - HRCC1DNINORD01?

Hi Gurus,
I have a requirement add two custom fields to the Standard IDOC HRCC1DNINORD01. For this i am using IDOC Extension but system through Error like Extension is not possible for Generated IDOCs. So my self find that we cannot Enhance the Generated IDOCs,instead of that Enhance the BAPI by using BDBG Transaction. But i don't understand this BDBG Transaction corresponding Object Type, Method. Please guide me to full fill my requirement.
Thanks in advance.
Regards,
SR Krishna.

Hi,
Actually, BDBG is a transaction to be created the new custom idoc types and message types all those stuff.
BDBG transaction will create the automatically custom idoc type and message type.
As per your requirement, You would create the custom idoc type and accordingly you have configure in the Partner profile.
Because one of the scenario, my case CRESTA01 needs the extension but it is not possible to create the extension for that. So, We have checked with BDBG but, finally we have checked and seen that internally, It has to be creating custom idoc type and message.
Manually, you have to create the custom idoc type with contains to your structure.
I hope you understand the scenario.
Thanks,
Chandra

Extend generated Idocs

Hi,
I extended the MARA table with a new field. Now I want to export the article data including the new field via the IDOC-Type ARTMAS05. So I need to extend the IDOC-Type but thats not possible via WE30 because ARTMAS05 is a generated IDOC-Type (see SAP Note 91390). I couldn't find any clear documentation about how to extend generated IDOCs and add new fields.
So my questions are:
How can I extend the IDOC ARTMAS05?
How can I add new segments to the IDOC for my new field in the MARA table?
Hope somebody can help!
Mathias

Hi Mathias,
Try these linkss:
Extension of generated Idocs types
How to extend an existing IDOC!
Re: Modifiy a generated IDOC (basic) type - HOWTO REGENERATE IDOC?
In this link search for extended idoc type and search the Function module attached
idoc issue - canbe fixed with enhancement?
Thank you,
Thanks,
AMS

Pls send step by step procedure to create generated idoc type in ECC 6.0

Hi
pls send me the step by step procedure In ECC 6.0 Version
1) To create generated idoc type
2) To extended idoc type
3) How we can add structure to custom segments
thanks in advance

hi,
check these likns...
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
regds,
paras

How to extend an IDOC in CRM

Hi,
Can we extend an IDOC in CRM, I am new to the era of CRM and I got a requirement to extend an IDOC TYPE and
when I try to extend the IDOC TYPE in CRM as how we do in R/3 the system displays message as "Action is not possible for generated IDOC types. Can any one suggest
what could be the problem.
or is there any alternative way to Extend IDOCS in CRM.
Thanks,
Venkat

You can do that. Go to transaction we30, create an extension to the Basic type. Create the segments. And you are done.
You can refer to help.sap.com for more information.
Award points if it helps you.
Regards,
- Prasenjit

Extending an IDoc Type or Creating Custom IDoc type

Hi Experts,
We need to modify IDoc Type "DESADV01" for adding extra fields. Should I extend this IDoc Type or Create a new Custom IDoc type with the extra fields? Which is the best practice? This is my first time with IDoc functionality. Please let me know.
Thanks for the help.

Hi Dev,
Simple solution man.
Try to create an extension for the Idoc you wanted to extend.
Steps would be as follows: -
1) Go to WE31, create the z-segments and make them ready
2) Go to WE30, give some name for the extension and select the radio button extension and click on create button
3) It will ask you necessary details like which idoc you wanted to extend...Give the details and add the z-segments and save it.
4) Release it
Thats it.
Hope this solves your problem.
Thanks,
Babu Kilari

Extension of generated Idocs types

hello,
does anybody knows why I can not create extension of generated (means in table EDBAS-GENERATED = 'X') idocs?
I tried to extend idoc BATMAS03 on R/3 Ecc 6 and got message:
message e099(b1) with
'Action is not possible for generated idoctypes'
In former version of R/3 4.6C it was possible to extend such IDoc BATMAS02 (generated one) without any problems.
Of course I found in program MSED5F02 in routine CREATE_EXT_STRUCTURE new (in comparison to 4.6C) extra check which protects against extension of generated IDocs, but I want to get to know what was behind that decision or how to workaround that problem.
Thanks in advance,
Marcin

Hi,
User Exits are used to populate data in new segments added and to read them
back which provides extension to existing idocs.
IDOC EXTENSIONS
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.
First, 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.
Pls reward helpful points.
Regards,
Ameet

How to Extend an IDOC !

I have an idoc for billing i.e INVOICE.
How will i extend it for credit memo ?

Hi,
in order to extend an IDOC goto WE30 tcode.
1) Give your basic IDOC type at the object name
2) select the Extension radio button
3) click on create button
4) it asks for 3 types of extension . so give the basic IDOC type over there
5) give description and click on continue button.
6) so at which segment level you want to add your segment, select that particular segment and click on create segment button and place your already created segment.
7) save and go back.
this is the procedure of extending an IDOC
and check this link,
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
regards,
Archana
Edited by: Archana Kumari on Aug 18, 2009 8:01 AM

Hi gurus how to extend the idoc

hi gurus how to extend the idoc

HI vasu,
in order to extend an IDOC goto WE30 tcode.
1) Give you basic IDOC type at the object name
2) select the Extension radio button
3) click on create button
4) it asks for 3 types of extension . so give the basic IDOC type over there
5) give description and click on continue button.
6) so at which segment level you want to add your segment, select that particular segment and click on create segment button and place your already created segment.
7) save and go back.
this the procedure of extending an IDOC.
Reward points if useful....
thanks,
satheesh.

How can I generate IDOC(WPUUMS) from XML file in POSDM or in SAP Retail

Hallo Retail expert,
I have following scenario,
I have Retail Store who send me their daily sales report through Wincor Nixdorf Point of sale. There i am using standard POSLOG2 to SEEBURGER(its a middleware which act as Converter) xml format and then i post that data first in POSDM and then with BAPI i transfer or book that data to SAP Retail.
Above is the one scenario which is working.
This is the Second scenario.......
I have some external Retail store, they dont have Wincor Nixdorf POS, so they send me their Sales Report through SEEBURGER(its a middle Hardware which act as Converter) and SEEBURGER Convert that Sales data to XML format. My question is....
How can i upload or Convert a XML File into IDOC (WPUUMS)in SAP or in POSDM?
any new suggestion are welcome.
Thank you all in advance.
regards,
Niel

Hi,
1. To get the required XML Schema, use transaction code WE60 to go to the IDoc documentation -> enter the IDoc type you want to use (WPUUMS01). Flag control and data record. Then display the XSD by choosing Documentation -> XML Schema from the menue bar. Now you can donwload the XSD for usage in Seeburger.
2. Create your mapping from the POS format into the IDoc XML format in Seeburger.
3. Create an XML File Port in ERP or POS DM using transaction code WE21.
3. To inbound the XML file from Seeburger into POS DM or SAP Retail Seeburger should trigger the function module EDI_DATA_INCOMING. Parameters for this FM are the Pathname to the XML file and the Portname you just created. Based on the port name the FM can derive the port type xml and the data will be handled as XML data.
Regards Carsten

How to see an IDOC type & FM, "WHERE USED LIST"?

Hi Experts,
I nned to create an IDOC of WMTCID01 and message type is WMTOCO.
I wanna to see that, Where Where this IDOC was used(especially, in "Z" objects) so that, I can get some idea abt. it and do my coding.
So, let me know that, How to see this IDOC & FM, "WHERE USED LIST"
thanq

hi go to the tcode...
1) Create Segment ( WE31)
2) Create Idoc Type ( WE30)
3) Create Message Type ( WE81)
4) Assign Idoc Type to Message Type ( WE82)
Tcode- we19 is for testing idoc
in the we42 the message type and the idoc function module is ataached by the process code..
this is a best example to understand the creation of idocs(z)..
http://www.****************/Tutorials/ALE/CustomIDOC/Create.htm

How to copy one IDoc type

Hi guys!
I need to copy one idoc type with Z extension to another R/3 system. How to do it?
Thank you!
Olian

Hi,
You can transport the IDoc Type to higher boxes.
But I could not able to find anything download and upload option.
a®

How to extend an IDOC step by step

Howto extend an IDOC step by step
Hello,
Waiting for become a blogger at sdn.sap.com, i post here a HOWTO for IDOC extension.
1)
/nWE31
Here will create the segments for extend our idocs.
Example: 'ZDUMMY'
-> Write a short description and field name.
-> Data element = CHAR1 (will create a new field in the idoc with 1 character extension)
-> Save (developer permissions needed)
2)
/nWE30
-> At development object select 'extension'
-> Write a name for object name (8 char extension). For MATMAS IDOC extension i create ZMATEX01. Click on 'create' button.
-> Now we will select the IDOC link. Select 'create new', and link to a basic type (MATMAS05 in our example). Don't forget to write a description (will be usefull in the future for identificate correspondances).
-> Select IDOC substructure where wich will be extended. Click on header and 'create segment' (you can paste from clipboard with 'insert' button).
-> Select ZDUMMY segment created before.
-> Save and fill package and transport order for this modification.
-> Release segment from toolbar (Utilities)
/nWE82
Add Message Type (MATMAS), Basic Type (MATMAS05), Extension (ZMATEX01) and Release.
Finish
All it's done! So now you can use your new IDOC. For SAP XI, must import again to your integration scenario. Check ZDUMMY field at the segment you have selected.
Best Regards,

This wasn't was an answer

How to extend the IDoc ORDERS05 and populate values?

Hi,
My requirement is to add few fields to the standard IDoc ORDERS05 and populate values to the newly added fields.
Please let me know how to extend the standard IDoc ORDERS05.
Regards,
Balaji. R

Hi balaji,
you can try to google for SAP R/3 IDoc Cookbook for EDI and Interfaces by Axel Angeli et.al.
Although Axel refers primarily to MATMAS Idoc the technique of extending IDOCs is explained very well.
Also very good is the search function here on SCN, I just found
[Some Experience on IDoc Enhancement|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3414900%29ID0711317150DB10743789739220747754End?blog=/pub/wlg/8285]
Blogs and Wikis here are the best source for general questions like yours, usually of much more value than forum answers
Regards,
Clemens

How to extend Generated Idoc types?

Similar Messages

Maybe you are looking for