Skip to Content
avatar image
Former Member

Best Practices for Solman 7.1 Test Management

Our Solution Manager team is debating the best way to manage testing object changes. Some want all automated tests (CBTA) to be created and maintained in our Dev Solution Manager and then transported to Prod Solution Manager for execution. They want to continue to keep Prod locked from changes since it is used for ChaRM for many of our productive landscapes and they cannot pass a security audit otherwise.

Specifically in transaction SCC4 our productive Solman client is set for No Changes Allowed, No Changes to Repository and Cross-Client Customizing objs, Protection level 2: No overwriting, no external availability, and eCATT and CATT Not Allowed.

For a 2-tier or 3-tier Solution Manager landscape does SAP have a best practice for where CBTA scripts and other testing objects should be created and maintained?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 09, 2016 at 09:08 PM


    Usually you create and maintain your scripts on SM DEV, and then release the final scripts to SM PRD.

    This is not mandatory and has no technical impact.

    However it helps Test Engineers to know which scripts are available for execution, and which ones are still in the process of being built.

    Additionally this makes BW reporting easier and more accurate, in most cases.

    Regarding the SCC4 this should have no impact, except if you actually want to execute scripts on SM PRD itself (eg. tcode BP), since the "eCATT and CATT Not Allowed" prevents any script execution on SM PRD.

    Add comment
    10|10000 characters needed characters exceeded