Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

modification without assistance

Former Member
0 Likes
1,645

HI ..when we have done upgrade..in the upgraded version i am able to see some objects under modification with out assistance when i exevute the SPAU tcode..

there are three objects that are getting listed under modification without assistance.

They are nothing but View cluster maintenance... when i saw the tcode and the program name int he status bar..it showed SOBJ as the tocode and program as SAPMTOBJ,

now i was comparing the two programs SAPMTOBN in both versios but it says no difference.......

but ia m fidning the difference in the number of entries,,in the inital screen of SOBJ .when i got to tcode SOBJ and say display ther ae only 4300 entries in older version where as in newer version there are arounf 8400 entries..

now what is hat i have to do.........some one please advise me on this..

4 REPLIES 4
Read only

Former Member
0 Likes
1,191

Hi,

Please try to compare the two programs page by page. Then you will know why the difference in the lines.You can also use the split screen Tcode: SE39 to compare both of the programs.

Hope this helps.

Please reward if useful.

Thanks,

Srinivasa

Read only

Former Member
0 Likes
1,191

Hi Sudha,

I don't think you need to worry about the SOBJ objects. They are maintainace view related object. Someone might have made some change or just tried to make the change. I think you can just ignore it and store it to the newer version.

Regards,

Atish

Read only

Former Member
0 Likes
1,191

The SOBJ entries generally relate to how view maintenance is performed - this has mainly to do with items in the SPRO customising tree. The number of entries has changed because there is a lot more in SPRO in the newer version. The entry/entries in SPAU for SOBJ in your system most likely relate to a view maintenance that has been changed - this is generally done as a result of instructions supplied in SAP notes.

An example in FI is settings for maintenance of FSV (Financial Statement Versions). By default these are maintained in the DEV environment and transported to test and production. However there are SAP notes to change the relevant SOBJ settings to "Current Settings" so that the FSV can be maintained directly in Production. There are similar notes for changes relation to opening / closing financial periods.

For your SPAU entries, if it is not possible to identify what was changed and why it was changed, the safest option is to revert to SAP standard. If this causes an issue with maintenance of some view then it is a simple matter of finding the relevant SAP note and applying the changes again.

Andrew

Read only

varunbiswas
Explorer
0 Likes
1,191

I recently came across SOBJ. It contains objects that are modifiable without transports aka metadata/application tables in production. If there are customizable entries than as an organization you must decide weather to keep those objects customizable in production or revert to standards.