Skip to Content

How to transfer a configuration from Dev. to Test tenant in ByD?

Hi,

I created a new configuration (Payment File Structure) in ByD developer tenant.

How can I now transfer the configuration to another tenant (Test)?

Thank you.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

7 Answers

  • Aug 16, 2017 at 10:44 AM

    Hi Rudhra,

    Thank you for your reply.

    I am afraid the Payment File Structure is not created in SDK.

    That is created in ByD itself: work centre Business Configuration -> Implementation Projects ->

    There is no such item "Payment File Structure" in SDK.

    Best regards,

    Aleksei

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 16, 2017 at 07:49 AM

    Dear Aleksei,

    In Development tenant- Logon to SDK and create the Payment File Structure and try to Port the solution to required customer tenant.


    Note : Customer ID should be mapped in the development tenant.


    Regards

    Rudhra

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 11, 2017 at 01:51 PM

    Hi Alexsei

    your changes cannot be transported, if they only are done in your test tenant's business configuration. This format mapping you refer to, is part of this configuration.

    If you have done your changes as part of a change project and merged back the changes to production, then each new tenant using the solution profile, will have the configuration. (maybe some overhead ;-))

    If you want to fast get the configuration from dev to test -> do copy and paste

    Best regards

    Marlene

    Remark: ByDesigns solution is leading in the Production tenant, changes are recorded in change projects, which can be merged back. The concept Dev -> QAS -> Prod can be achieved with manual process, but it is not the designed way of working with ByD.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 11, 2017 at 06:45 PM

    Thank you, Marlene,

    In fact, we have already used the manual process (copy/past) to copy several Payment File Structures (we had to create five custom ones) firstly from the Dev tenant (EN) to the Test (Demo) tenant (EN). Besides that, we have one more Test tenant (CZ), and so we had to do the same manual copy/past process again. Finally, we will have to repeat the manual process to create the Payment File Structures in the Production tenant.

    I do not understand well enough what the merging back process means. As far as I understand we now have to ask SAP for copying from the Test tenant to the Production tenant every time when we change something in the project configuration. Or we have to repeat the configuration changes in the Production tenant manually. Maybe we should do all configuration changes just (and only) in the Production tenant?

    Please, could you explain to us what the right way to transfer configuration changes (such as Payment File Structures) to the Production tenant is?

    Thank you very much.

    Aleksei

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 14, 2017 at 10:03 AM

    Hi Aleksei,

    sorry for the late reply. The transport concept of ByD is different to SAP ERP with transport requests.

    ByD has a production system with configuration, data, reports, etc.

    When you e.g. want to adjust your configuration, then - depending on the impact and type of change - can do it directly in the production system (e.g. add a new US Tax Jurisdiction Code) or do it with a change project (e.g. add a new functions from scoping). For a change project you can decide that you would like to only bundle all changes in a change project w/o a separate change project or you request for your change project a new test tenant. There is in chapter 4.3. of the help for business configuration a description

    which might help you in understanding this concept.

    If you have your initial test tenant, then you request a production tenant (see help document). Then test and production are disconnected. You can now decided for further changes:

    1. Do the changes in a change project with a connected test tenant (new test tenant is required, in future you can connect new change projects to the same tenant then again)
    2. Do the changes directly in the configuration of your "old" test tenant and repeat the same in production (manual step).

    When you plan to do your changes in test first and move it to production, you have to use option 1. You create a new change project w/ a test tenant, then you do your changes there and when your result is as expected, then you merge back the project and have the changes in your production system.

    The nice thing here is that you can have multiple change projects with a test tenant each in parallel. Drawback is that you cannot have an easy concept of Dev -> QAS -> Production (as you might know from SAP ERP).

    Let me know, if you need further information.

    Best regards
    Marlene
    PS: I really like the CHange Project approach :)

    Add comment
    10|10000 characters needed characters exceeded

    • Dear Marlene,

      Thank you for your reply.

      I have read the chapter 4.3 of the help manual and I tried to understand the concept.

      I am afraid there is no different way to figure out the concept without doing all the things in ByD system by myself.

      As far as I could understand the possibility of several changes looks slightly like the branch concept in Java projects.

      Unfortunately, I do not have time catastrophically to investigate the things further. Probably I will have to use the more simple concept copy/past, at least, for now.

      Thank you very much.

      Aleksei

  • Nov 27, 2017 at 03:49 PM

    Hi Aleksei

    one good blog post I just found now :)

    https://blogs.sap.com/2015/09/08/change-project-faq-page/

    Here you see a brief overview of how to use change projects.

    Best regards

    Marlene

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 28, 2017 at 09:17 PM

    Dear Marlene,

    Thank you for the useful link.

    It is interesting things I have read. As far as understood we can use the change project feature in the production system only (at least together with it). I am afraid we are not working on the production system yet. We are somewhere about the go live moment.

    Yet there is a need to try the feature to understand well in which way we could use it.

    Many thanks,

    Aleksei

    Add comment
    10|10000 characters needed characters exceeded