SLD configurations

Step 1 :

(a) Go to \usr\sap\\JC\j2ee\admin and run go. bat [in AS JAVA]

and :\usr\sap\\DV*\j2ee\admin and run go.bat [In ABAP+JAVA]

(b) Go to Instance-->Server-->Services-->SLD Data Supplier-->HTTP Settings

(c) Enter the details of Local SLD as per the screen shot given below



(d) Trigger the Data Supply by click on the blue color arrow at the top



Step 2:

(a) Go to \usr\sap\\JC\j2ee\admin and run go. bat
(b)Go to Instance--> Server-->Services-->SLD Data Supplier-->CIM Client Generation Settings tab
(c) Enter the details of SLDMain as per the screen shot given below




(e) Save the Settings and Trigger the Data Supply as done before


Step 3:

Go to the URL http://:50$$0/sld this is our Local SLD



(a) Go to the administration tabDataSuppliers






(b) Add a new SLD that is SLDMAIN in it with the data supplier userid/password



(c) This will trigger the data supply from Local SLD to SLDMain

(d) Go to the SLDMain URL : http://:50$$0/sld and check whether or not the data it receives from local SLD is true
(e) This SLD data flow is unidirectional


How to revert back the Changes?

To revert back the changes you just have to remove the above configurations you have made. In the Instance--> Server-->Services-->SLD Data Supplier-->HTTP Settings and Instance. Server-->Services-->SLD Data Supplier-->CIM Client Generation Settings tab of Visual Administrator mention Local SLD or SLDMain based on the team’s requirement. Also we have to
remove the SLDmain from the data supplier functionality given in administration tab of Local sld.

Generation of csmconf

Login to Solman with a user having basis authorization.

Run RZ21



Save in required location

Copy the csmconf file to:



Registration

















Create JCo RFC connections in Visual admin






Check for the system to be ONLINE (RZ21):-





Checking the SLD connection:-

An adjustment of ABAP Dictionary objects is carried out with transaction SPDD,

It must be performed as soon as you are prompted to carry out a modification

adjustment for ABAP Dictionary objects.

objects to adjusted are

a) Domains
b)Data elements
c) Tables (structures, transparent tables, pooled and
cluster tables including their technical settings, indexes of transparent tables).


Changes to other ABAP Dictionary objects such as type groups, table types,
views, search helps, match code objects, match code indexes and lock objects
cannot result in the loss of data. They are not done by transaction SPDD,
but by transaction SPAU (post upgrade activity).

In the adjustment procedure, ABAP Dictionary objects before the upgrade
(old version) are compared with objects after the upgrade (new version).

one must perform one of the following actions for all objects presented for adjustment:

a)Retain modification

Confirm that you want to adopt the modification or maintain the changes with the appropriate maintenance transaction.

Click the yellow traffic light in transaction SPDD to execute the data transfer reports.

b)Cancel modification

Choose Reset to original









when doing the modification and enhancements ,we have three options to choose from :-

a)With Modification Assistant 

Objects modified With the Modification Assistant are adjusted automatically or in the individual

ABAP Workbench tools using either corresponding dialog boxes or the split screen editor(SPAU Activity) .

we generally do not do direct maintenance of adjustment objects.

B)Without Modification Assistant

To adjust objects without the Modification Assistant we use version management .

When modifying objects where version management cannot be used, one need to document any changes that he/she make.

c)Deleted Objects

This node contains objects which are deleted in the newer version of SAP

and this node is to be left as it is.

pic(below):- select object



pic(below):- version management




pic(below):-current version already exist as previous version


pic(below):- reset to original








SPAU

The adjustment of Repository objects is carried out with transaction SPAU.

Only those objects that have been modified by you and are being redelivered by SAP

in an upgrade are presented for adjustment.

The system automatically recognizes during upgrade if modification adjustment is necessary.You are then prompted to perform the modification adjustmentYou must decide whether the objects contained in the adjustment list should retain your modifications or if they should be reset to original.

when Running SPAU :-

a) use any oter user than DDIc.

b)When an object is modified for the first time, a change request is created

where modifications should be recorded.

c)If several developers are involved in the modification adjustment process,

one can create a changeable transport request with several tasks before modification adjustment begins.

d)If each developer creates his or her own transport request during modification adjustment,

these requests must be consolidated into a single request. This single request which contains

all modification adjustment objects can be selected for transport to subsequent systems.

The major transactions for Trace Options in SAP are :-