Extended WPUTAB01 idoc

Hello!!!
Those anyone know how or which User exits can i apply on this Inbound FM 'IDOC_WRITE_AND_START_INBOUND'.
I had a WPUTAB01 idoc and i need to insert extended data on some fields of E1WXX01 segment!!
How i do that??
Thanks.

Hi,
I am also having that problem.
Is there any solution?....
In my case in Dev an QA was operating OK.
In production some registers go to the good structure and the other go to the wrong strucutre that is at one level....
Thanks in advance,

Similar Messages

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

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 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

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

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

User exit to extend BD10 idoc

Hi all,
Please provide a user exit to extend BD10 idoc.
Thank you.

Hi,
Enhancement MGV00001.
Exit FM is EXIT_SAPLMV01_001 to fetch data from database.
Exit FM is EXIT_SAPLMV01_001 to post data.
You can use Badi BADI_MATMAS_ALE_CR also to fetch data from database and populate it to idoc for
Matmas.
Thanks,
Asit Purbey.

Extend a IDOC

Hi,
I need to extend an IDOC, how to get proceed
Regards
Ajay

Write your code in customer exit EXIT_CUSTOMER_FIELDS_FILL in MASTERIDOC_CREATE_COSMAS function module. You can use this exit to fill customer fields.
You will have to write a badi implementation for gd_user_exit->customer_fields_fill.
This function module is internally call in transaction BD16.

Extending an IDOC

Hi All,
I want to extend an IDOC, which is getting generated while executing the transaction BD16.
Details of the IDOC are given below:
Message Type = COSMAS
Basic type = COSMAS01
Basically a new custom field "ZZMFG_RLVNT" was added in the table CSKS. Requirement is to add this field in the new segment of IDOC which gets generated while executing the transaction BD16. I was able to make the neccessary configurations in WE31, WE30, WE81 and WE80.
Now i am struck at finding suitable user exit for writing code to support IDoc extension.
Please provide me ur inputs.
Regards,
Rajesh

Hi suresh,
According to my knowledge userexit is coomks01.
But badi is available in kbas package K_CCA_CUSTOMER_FIELD.
check above two options.
*reward points.

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.

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

Extending Basic Idoc's

Hi,
Please provide Step by step procedure to extend Basic Idoc's.
With Regards,
Nelson

Choose SAP Menu ® Tools ® Business Communications ® IDoc Basis ® Development ® IDoc types . The IDoc type editor is displayed.
If you have not already done so, create a transport request for your development objects (extension segments, extension, function exit and so on). You can access the Workbench Organizer from the editor by selecting Requests (Organizer). From there, select Request ® Create and reply to the questions which appear on screen. By selecting you can return to the IDoc type editor.
Name your extension in accordance with the customer namespace and choose Extension as the development object. Choose .
The name of your extension should be no more than 8 characters if you wish to use the extension to communicate with partners who are using SAP Releases prior to 4.0. You can only use extension names with more than 8 characters from Release 4.0 onwards.
Choose one of the following options:
Create New: Create the extension without a reference.
Create copy, which you can then change if necessary
Create as successor: Note that only one successor is allowed per release for each extension.
Select the basic type which is to be combined with your extension. Confirm your entries.
The basic type is displayed as a tree structure. See the color legend (Utilities ® Color legend).
Position the cursor on the segment where you wish to append the extension segments (the reference segment). Choose . You must now assign attributes for these child segments:
Mandatory segment (indicator): Must data be written to this segment in the IDoc?
Maximum and minimum frequency of use: How often may/must a segment occur in the IDoc?
You can add further children or "grandchildren" to this or any other reference segment in the basic type.
When the new extension is complete, you can save your entry.
You should keep the following factors in mind when dealing with extensions:
Segments must not explicitly occur more than once in the IDoc type - this means that the extension cannot have any segments which already exist in the basic type. This also means that a successor must not have any segments which already exist in the predecessor.
Parent segments of predecessors must remain parent segments in the case of successors.
Extension segments cannot be created from reference segments using the Cut and Paste functions and vice versa.
In the example call your extension Z1ORDERS . Append Z1TEST1 child segment to E1EDP19 reference segment in ORDERS01 basic type. The child segment can be used only once.

Extending the IDoc to cXML scenario

Hi Experts,
I have a scenario IDoc to cXML for sending ORDERS05 .
We got a requirement to develope a scenario by extending the Order header and line extention segements to include extra fields)of the IDoc used in the above scenario , hence I am doing the following
-Imported the extended IDoc into the Integration repository.
-Mapped the extra fields included to the target message.
-reloaded the IDoc Metada using IDX2.
As i am doing this as part of the other project please suggest on the following
--Explain the sections to be included in the Technical design document for XI configuration.
--configurations that I need to work on.
please do suggest any other things i need to work on to take the right approach.
Thanks in advance.
MK

Hi,
Nothing more u require in XI development when ever u are dealing with the Extended IDOC's.
Normal procedure as Standard IDOC's only.
If u are not able to view the extended IDOC's in the Repository means then u have to think the solution.
This problem is not there for u. so go a head with the normal procedure by importing those IDOC's in IR and do mapping as usual
Regards
Seshagiri

Error when trying to extend custom idoc

Hi ladies and gentlemen,
I am experiencing problems when I try to extand a custom idoc segment.
I created a custom idoc (ZBEVINBDEL) with 3 segments, generated it and have tested it successfully. Now the users have come back and requested additional fields. When I tried to modify the custom segment (after cancelling the segment and idoc status' from released status, I got the message 'Segment type Zxxxxx.. cannot be changed' (this is because the idoc segment type has been flagged as generated).
So I thought I'll create an extension to the corresponding segment. I've created the extension segment in WE31, but when I try to create the extension (ZBEVINBDELX02), and try to create as new to the linked type ZBEVINBDEL, I get another error message 'Action is not possible for generated idoctypes'.
Has anybody experienced this problem before, and could you give me an explanation on how to get around these problems, either for changing the segment or extending one. If the answer lies within BDBG, please explain in detail.
Cheers,
Steve

Reuben,
In the end, I didn't need to touch the extension. I was able to achieve my goal by adding the new fields in my custom structure in SE11, and the new fields came into the idoc automatically. Then I just had to add code to handle the new fields in my Function module.
Good Luck,
Steve

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)

Extended WPUTAB01 idoc

Similar Messages

Maybe you are looking for