Transport Problems with Spokes that have BADIs

[Former Member]

What is the proper way to transport an infospoke that has a transformation?

Here is my problem. Maybe I am doing something wrong.

Situation -

1) I have an infospoke that has a BADI transformation.

2) I add two new infoobjects to the definition

3) I active and run the spoke.

First Problem - The new fields dont show up on the open hub table until I go back and add them manually to the target structure of the Transformation. However the only development class I can assign to the Target Structure after the changes are made is $TMP - Temporary Objects (never transported)

4) Now I release the transport of the spoke. However the transport fails when its sent to the target system because the target structure is not included.

Is this the way its supposed to work or am I doing something terribly wrong?

[Former Member · Accepted solution]

Hello Wardell,

When you enhance the system genertaed target structure, it will always get stored in $TMP and will not allow you to transport. There are two ways of handling this and you can choose one dpending on what stage of developemnt you are

1. In SE11 create a custom structure by copying the system generated target structure. Do all the required enhancements to the structure here and save it. Here it will allow you to store in your package. In Infospoke defeniton, replace system genertaed target structure with this custom structure.

2. If you have already created infospoke, BADI etc and don't want to change that. Transport it and let it fail in target system. Then you need to add the reuired fields in target struture manually. Then activate it.

First solution is a smooth one, but if you do not have much time to make those changes, then you can go for second one.

Hope it helps.

Regards,

Praveen

[Former Member]

Hi,

i have the same issue now,

can you please help me with '1) UNCHECK third party notify' where this check box will be available.

Thak you,

Vijay.

[Former Member]

Sorry Vijay,  we converted from Infospokes to Open Hub Destination since I had this problem.  Furthermore I am no longer on the BW team.

From what I remember though on the Infospoke definition there was a checkbox for "third party notify".  Unchecking that box solved the problem.    I have to admit though sometimes it worked, sometimes it didn't.

My advice is to convert to OH Destinations as soon as you can.

[Former Member]

See my comment on how to do this.

[Former Member]

I dont know the exact solution of this problem but we faced the similar situation and we did the changes directly in other systems.

-Ashish

[Former Member]

I found out the steps necessary to do this:

1) UNCHECK third party notify

2) Geneate the Implementation and Class

3) Activate the spoke

4) Transport - (The transport should only have 4 objects; the Spoke, the OH Dest, the Implementation, and the Class

5) CHECK third party notify - DO NOT CHANGE ANYTHING ELSE!!!!!

6) Transport - The transport MUST HAVE ONLY THE OHDEST object.

I worked out this process with SAP and after several failed approaches, the above process works every time.

The IMPORTANT thing is that on the second transport; ONLY THE OH DEST can be in that transport!!!!! <-- THIS IS THE SECRET!!!

You might also need to be aware that any subsequent changes to the spoke, i.e. filter, infoobjects, etc will REMOVE the BADI connection to the spoke. When that happens you have to start over from step 1 above.

Good Luck!!!

[Former Member]

Hi Wardell,

i have the same issue now,

can you please help me with '1) UNCHECK third party notify' where this check box will be available.

Thak you,

Vijay.