You can develop your own software to fulfill specific requirements or provide features that are not included in SAP standard software. However, custom developments do not always meet the quality standards set by SAP or are not documented adequately. In many cases, there is no overview of how many custom developments exist and how or if they are used. It is important to know the type of implementation (extension, modification, or custom development) and how critical the implementation is.
In Solution Manager 7.2 data model is simplified (Custom Code Life Cycle Management (CCLM))
It allows;
1. Simplified setup for CCLM
2. System specific attributes
3. List of objects per system (System View)
4. List of identical objects in different systems (Object View)
5. Integration of SCMON (next generation UPL)
In 7.2, completely changed underlying tables, data set and structure of CCLM hence we require a migration. We also need to do some setup change due to the architectural change.
The major change in the setup is the activation for the data collection.
This is a two step approach; you have data in the managed system which has to be put in the BW of Solution Manager and it can be used by other applications such as Scope Analyzer and the second step is to collect the data into CCLM table.
The problem with this two step approach is that the two above mentioned steps are independent. Since this approach is complicated SAP decided to handle the setup.
First select the managed system from the Scope;
Click on Activate takes some time to load due to background processing; once the background processing is done the below screen will be shown;
Click on Select Data Collection Groups; the following screen will appear;
You can Choose decommissioning cockpit where the following will be performed.
The advantage is that you just have specific the system and we run the required steps; This makes like much easier. In use case point of SAP will take of the use case once it is setup.
------------------------------------------------------------------------------------------------------------------------------------
Now we go to the work center view
Overview View
Object View
In the above screen you can see system sepcfic and obect spectifc view; in 7.1 it was only object specific. But there are situations where customer needed system dependent attributes hence it is changed in 7.2.
The blow shows the system specific information;
Even if you go to the Object View it the same.
Go to Object Centric -> Apply->click on the object row; you can see system specific information of that object.
This is main changes in 7.2
By using the settings button you can change the columns
This was the major architectural change.
Now lets take a look at main application chnage the "Quality Cockpit"
This is second use case after demonizing. This is mainly for master check which performs ATC Checks every month. Now we have S/4 HANA we include HANA specific checks as well.
Go to projects by clicking on View List as below
This allows you to setup a project and check what's is going with project by clicking on the project
Drill down to Analysis report to get more information.
Decommissioning Cockpit
S/4 HANA and CCLM
Below ddiagram describes in details
In Solution Manager 7.2 data model is simplified (Custom Code Life Cycle Management (CCLM))
It allows;
1. Simplified setup for CCLM
2. System specific attributes
3. List of objects per system (System View)
4. List of identical objects in different systems (Object View)
5. Integration of SCMON (next generation UPL)
In 7.2, completely changed underlying tables, data set and structure of CCLM hence we require a migration. We also need to do some setup change due to the architectural change.
The major change in the setup is the activation for the data collection.
This is a two step approach; you have data in the managed system which has to be put in the BW of Solution Manager and it can be used by other applications such as Scope Analyzer and the second step is to collect the data into CCLM table.The problem with this two step approach is that the two above mentioned steps are independent. Since this approach is complicated SAP decided to handle the setup.
First select the managed system from the Scope;
Click on Activate takes some time to load due to background processing; once the background processing is done the below screen will be shown;
Click on Select Data Collection Groups; the following screen will appear;
You can Choose decommissioning cockpit where the following will be performed.The advantage is that you just have specific the system and we run the required steps; This makes like much easier. In use case point of SAP will take of the use case once it is setup.
------------------------------------------------------------------------------------------------------------------------------------
Now we go to the work center view
Overview View
Object View
In the above screen you can see system sepcfic and obect spectifc view; in 7.1 it was only object specific. But there are situations where customer needed system dependent attributes hence it is changed in 7.2.
The blow shows the system specific information;
Even if you go to the Object View it the same.
Go to Object Centric -> Apply->click on the object row; you can see system specific information of that object.
This is main changes in 7.2
By using the settings button you can change the columns
This was the major architectural change.
Now lets take a look at main application chnage the "Quality Cockpit"
This is second use case after demonizing. This is mainly for master check which performs ATC Checks every month. Now we have S/4 HANA we include HANA specific checks as well.
Go to projects by clicking on View List as below
This allows you to setup a project and check what's is going with project by clicking on the project
Drill down to Analysis report to get more information.
Decommissioning Cockpit
S/4 HANA and CCLM
Below ddiagram describes in details
- SAP Managed Tags:
3 Comments
