Enhance SPRO to add customized views

Objective:  

Enhance SPRO to add customized views to SPRO and make documentation of the relevant Z customization.  

Use in Projects:

The customized entries and documentation will be with in SPRO and understandable to everyone.  

• Entire Customization including ‘Z’ objects comes under one tree(SPRO)
• Reduces the time to become familiar with the system & processes.
• Easy to maintain.
• KT process becomes easier.  

Procedure:  

To add this maintenance in SPRO, we need to enhance SPRO.  

Run the TA : S_IMG_EXTENSION from the easy access:  

EDIT IMG STRUCTURE Screen:

  

Select the relevant IMG Structure from the F4 Button.  

In this case, the IMG structure is Sales.

  

  

Press F4 on Enhancement ID, It shows all the existing Enhancement ID’s. We can create our own enhancement ID.  

Cilck ‘ SAVE’ Button.  

Object directory entry screen is displayed. Give the package name. Workbench request gets created.

Once saved, Click on continue button

Now we can see the ZALU as enhancement ID Original List:

Double click ‘ZALU’  or set the cursor on ‘ZLAU’ Click on Continue.  

“ZALU” ‘ALU Enhancement ID’ gets filled at Enhancement ID.  

Now click on button Enhance Structure on the application bar.

Change IMG screen is displayed.

  

As we have selected IMG structure as SALES, we get all the sub nodes under sales.  

Now we are going to add a node as a sub node Under Sales:

Here 4 application bar buttons:

  

The above two buttons describes at which level (Parent node or Child node) to add the node.  

We are going to add ‘ALU Individual Customizing’ as Sub node to Sales,

So set the cursor on Sales and click on  

  

Pop up comes with asking for Node text: ‘Node text is given as  ‘ALU Individual Customizing’  

 

Click Continue.

Now the structure displayed like below:

Now set the cursor on ALU Individual Customizing and click on the button Activity:

  

Following screen is displayed.

Give IMG ID (Any Name) and document name and click on create:

Add the documentation:

Save and click on ‘BACK’ button. Will be directed to initial screen.

Click on SAVE button.

Workbench request gets created:

Now Click on the Attributes TAB:

Following screen is displayed:

  

Here is the list of ASAP Roadmap ID:

Selected 201 as ASAP Roadmap ID (Select the appropriate Roadmap ID, where this customization comes)

Mandatory/ Optional as “Optional”,

Critical/ Non_Critical as “Non Critical”.

Coming to the components on right side:

Press F4 on components, We get a list. Add the appropriate component.

Click on the SAVE button at the bottom:

Gets saved under workbench Request:  

Now click on the Tab: Maintain Objects:

Give the maintain Object ID and Name:

Assign the customizing Object Here:

In our example, the table name is ZEMPLY and the transaction code for the table maintenance:  

Click on the ‘SAVE’ Button:

Saved under workbench request and click on Back Button.

We are directed to Initial IMG Screen. And screen shows as below:

  

Click on SAVE button on the Top:

Changes logged under workbench Request:

  

Now Run the transaction SPRO:  

Now we can ZUNBU in the path

  

The documentation shown as below:  

When executed, it shows the Maintenance Screen,

  

Working with screen variants

Screen Variants

Screen variants allow you to simplify screen editing by:

• Providing default values on the screen fields
• Hiding and changing the ready for input status of fields
• Hiding and changing the attributes of table control columns

A screen variant contains field values and attribute for exactly one screen. A screen variant may be assigned to multiple transaction variants. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction. They can also be called at runtime by a program. The different possibilities for calling screen variants guarantee great flexibility of use.

Normally when we create sales order, we can change the “ship to party” which comes based on sold to party, now for the demo purpose, we would disable “ship to party” so that the end-user cant make changes to it.

Transaction code: SHD0.  

Enter the transaction code, for which you want the field to be disabled, give a transaction variant name, this transaction variant will be assigned to order type later.

Here in this case transaction code is ‘VA01’.

Click on Create button

Enter the order type and press enter.

If you want to hide a field in sales order, then in this screen you can make necessary changes, according to our scenario we are just going to make changes only to ship to party so do not make any changes in the screen, Click on enter

Click on enter

Click on enter until you get the below screen where you are going to make modifications to ship to party field

Check the ship to party checkbox in output only (means display purpose) as shown below.  

After checking the checkbox, just click on EXIT and SAVE button shown in the below screen shot.

Enter the short description

Click on save

Assign it to a package.

Assign it to a transport request, and click on enter, you may get the same package and transport request, just click on save and go on until you encounter with the last screen.

Now this is the final screen.

Now go to transaction VOV8.

After selecting the order type, either double click or click on details button, it will take you to the next screen where you have to maintain the variant name.

Now when you try to create a sales order using the same document type then you can see that the ship to party field is in display mode.  

Tracking the transaction codes of the IMG activities

Go to SPRO -> SAP Reference IMG  

Now click on “Additional Information” à Additional information à Display Key à IMG Activity

 

You would see the activity names on every transaction in IMG now (as shown below)

 

Note the corresponding activity.  

Now to transaction SE16 and enter the name CUS_IMGACH  

Enter the activity name as shown below:

 

Execute and you would get the transaction code