Transport in 2 SL in public cloud

[Shama321]

Hello, I do configurations on Test/Quality system of the 2 system landscape. How do I transport the configuration made in CBC and tested in Quality to Production? I am used to the 3SL but in the Export Customizing Transports app I am not able to do it in 2SL. 

Based on this document, I was able to find a button "Release Transport" from Quality to Production. What happens when I press it? I want to check what I am sending to the Production beforehand. I dont want to send something that should stay in the Quality system.
Is there any application where I can see and edit the transport content? Because in the 3SL you can go into more details and see tasks of the request in Export Customizing Transports.

[Jeremy_Deo]

Hello dear user,

And thank you for asking your question in the SAP Community blog.

You're right to be careful before releasing anything to Production in a 2-System Landscape (2SL) ;  it's a bit different from the 3-system setup you’re used to, and it can feel a little restrictive at first.

In 2SL, all your configuration work happens in the Test (Quality) system. Once you're done and happy with your setup, you use the "Release Transport" button to move the changes to Production. This process is managed through Central Business Configuration (CBC), and it's designed to be more controlled but that also means it's not as flexible as what you're probably used to in 3SL with the Transport Management System.

So what happens when you click "Release Transport"?

When you hit that button, the system takes all the completed configuration activities (from CBC), bundles them into a transport, and pushes them straight to Production. There's no export/import step and no option to open up the transport and look inside like in the classic SE09/SE10 style you're used to.

Can you check what's being transported beforehand?

Not exactly in the way you'd expect from a traditional system. There isn’t an app where you can open the transport and review or remove individual entries before releasing.

That said, here's what you can do:

• Check the CBC activity log — see what config activities were completed and might be included in the transport.
• Use the CBC “Change History” to get a list of what was changed recently.
• If something was only meant for testing and shouldn’t go to Production, you can reset or undo the CBC activity before releasing the transport.

So the key here is: only complete CBC activities when you're sure they’re ready to go to Production. Once they’re completed and you hit Release, they’ll be transported.

I hope this will help you answer your questions.

Best regards,

Jeremy