cancel
Showing results for 
Search instead for 
Did you mean: 

BPC 7.5 : END ROUTINE BADI Transport

Former Member
0 Kudos

Hi,

I created ENDROOUTINE BADI. I can able to collect all (Enhancement Implementation, Class and Method) objects in BADI except

the BADI implementation.

Its not present in object directory entry table TRDIR and $TMP objects in SE80 but it is available in table BADI_IMPL.

If any one come across similar situation please suggest me how to capture the BADI implementation for transport.

Thanks

Prasad

Accepted Solutions (0)

Answers (1)

Answers (1)

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos

The BAdI implementation needs to be assigned to a transportable package, not $TMP. Assign to a package, and the system will ask you to addd it to a transport request.

Regards,

RIch Heilman

Former Member
0 Kudos

Thanks Rish for your reply.

I tried to capture this in SE03 by usiing object type SXCI and BADI implementation name but it is saying no object found.

Is there any way to capture $TMP BADI implementation (BPC 7.5 ENDROUTINE) object .

I created new (with different technical names) Enhancement implementation and BADI implementation and collected into a transport request but still objects Enhancement implementation and Class are present in the transport request BADI implementation object is not available.

I thnik BADI implementation should go If I transport the Enhancement implementation though it is not available in trasport request.

Please correct if I'm wrong.

Thanks

Prasad

Former Member
0 Kudos

Hi, here's a brief summary of how to transport a BADI from a Dev to Prod system

u2022 Search for the username that built the BADI in SE01, e.g. NCARTER

u2022 First release the base nodes; select them and click the u2018direct transportu2019 button (or F11)

u2022 Click refresh until that says it has successfully released, then jump into your target system (Prod in this case)

u2022 Then go to transaction STMS in Prod, then Transport queue option. Click refresh until it says u2018Import queue is openu2019 as the Prod status

u2022 After that, double click Prod, scroll to the bottom, and your transport should be there

u2022 Select it, and click Import Request option

u2022 Click refresh after youu2019ve set it importing, hopefully youu2019ll get a green light in the RC column

u2022 To check whether the BADI has successfully come into Prod, go to Prod system SE80 (ABAP Dev Workbench), click Class/Interface dropdown, then the triangle to search for your BADIu2019s technical name or description. Ours didnu2019t have a short description (blame the developer), so I used Z* on the tech name to find it

u2022 If you double click the tech name, then use the tree under u2018Methodsu2019 to drill down to the routine. Double click on that, to give you the code behind the BADI.

Thatu2019s about it really. That is how you transport the BADI, followed by checking whether the code is the same / present in the destination server.

Hope this is of some help,

Nick