Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Error while extending PROJECT01 IDoc with z-fields

Former Member
0 Kudos

Hi there,

I want to extend the PROJECT01 IDoc-Typ with a segment, that holds several Z-Fields. In transaction WE30 on Dynpro "create Extension" I choose "Create new" and for "linked basic type" PROJECT01.

On clicking the green button, I get the following error message:

"Action is not possible for generated idoctypes"

Does anyone know how to solve this problem?

Thanks!

15 REPLIES 15

Former Member
0 Kudos

Hi Mario Oertel,

Let say you have PROJECT01 with 3 z fields and you need to extend rite ?

First go to we31 to create a segment type what Zfields you need to extend.

Then go to we30 and in Obj.name enter PROJECT01 and select Extension radio button, then press create ...

a popup box with will appear in this select create new and give PROJECT01 in linked basic type. then

select the segment type what we have created.

Regards,

Suneel G

0 Kudos

Hi Suneel,

if I select create new and give PROJECT01 in linked basic type in the popup box in WE30

I receive the error mentioned above.

Regards.

Mario

0 Kudos

Hi Mario Oertel,

Have You solved your problem ???

Regards,

Suneel G

0 Kudos

Hi Suneel G,

no I have no solution so far. In Transaction SWO1 I created a subtyp of bus2054 and the saveReplica Method, where i added the structure with my values. After doing this I could generate a new MESSAGE Type ZPROJECT with IDoc Type ZPROJECT01. But when I substitute the distribution model WorkBreakdownStruct.SaveReplica with my copied one and execute the report RCJ_SEND_PROJECT_ALE I get the message: no receiver for project, ALE distibution not possible.

I also tried the following thread:

but it didn't help me anyway.

So do you understand what my problem exactly is, and have xou any other ideas to solve it?

Thank you so far.

Mario

Former Member
0 Kudos

Hi,

Check the Release of the Basic type PROJECT01 in we82 . If it is lower than the your current release you will see that error.

Change the Release to relevent to your current system (not sure which version ur system is ) and set to release again.

Then you try to extent it will work.

Rhea.

0 Kudos

Hi,

I tried to enter the current release version in WE82, but that did not change anything.

Any other ideas???

Mario

0 Kudos

Did u add the New entry with the extension and new release in we82?

Rhea.

0 Kudos

No, I changed the release of th existing entry.

Mario.

0 Kudos

Sorry for any confusion, Please add the entry with the new extension and new release.

Rhea.

0 Kudos

Sorry, but I can't add a new entry, because it says, that the extension does not exist.

But I cant creat the extension because of the mentioned error!?

Mario

0 Kudos

Ok , Do one thing cancel the release first for the Basic type then try to create the extension .

Rhea.

0 Kudos

I've read that PREOJECT01 is an generated idoc typ, and that those can't be extended.

Have you any idea about that?

Mario

0 Kudos

Hi Mario,

Check this thread.

Regards,

Soumya.

0 Kudos

Yes now i see acheck in the code(Include MSED5F02)

data: l_edbas type edbas.
     select single * from edbas into l_edbas
        where idoctyp eq edi_iapi01-idoctyp.
    if l_edbas-generated eq 'X'.
      message e099(b1) with
         'Action is not possible for generated idoctypes'.
    endif.

Rhea.

Former Member
0 Kudos

Hi Mario,

I have a similar requirement as yours to distribute the WBS hierarchy from one system to another, Also Z fields on the "Cusom" tab need to be distributed to the other system, Did you manage to do it, If so can u give me any documentation available???...

I was able to configure the ALE to create the IDOC of type PROJECT01 when saving the WBS element in the source system, but how does the receiving system process this IDOC and create

the WBS hierarchy???...

Many thanks...

regards

Mishan