cancel
Showing results for 
Search instead for 
Did you mean: 

Standard Report in SAP

Former Member
0 Kudos

Hello Experts

We would like to have Some standard report to check whether Any standard schema or rule changed by Anyone (Consultants)

We want to target specifically for a country and standard schema and rules.

Any updates appreciated.

Regards

SK

Accepted Solutions (0)

Answers (5)

Answers (5)

venkateshorusu
Active Contributor
0 Kudos

We have an option SCU3 utilize it, more than that it is bit difficult to find out it.

Since we can not differentiate time management schema with country grouping the only way is naming convention's identify the schema and find out the details in SCU3.

Regards

Venkatesh

former_member193210
Active Contributor
0 Kudos

I don't think that there are any standard reports that include fields UNAME and UDATE of table PPE01, but you can get the information by looking at the Attributes of the schema through t-code pe01.

Former Member
0 Kudos

All

Thanks for the reply. Answer is RPUCTF00

Regards

SK

former_member193210
Active Contributor
0 Kudos

I tried that program, and I couldn't get it to report on when the changes were made.

Furthermore, it looks more like a program to change the schema's Attributes, an no documentation exists on that program (nor in EN, nor in FR).

venkateshorusu
Active Contributor
0 Kudos

I completely agree with you "Rémi Corriveau" program does not give what are all the changes made to schema only thing, what it does is it capture's the last changed by details, Apart from that it does not give any more details.

Further more to log those changes at table level, We have given an option RSTBHIST or SCU3.

Regards

Venkatesh

former_member193210
Active Contributor
0 Kudos

You should try to use t-code se10, and using the menu, look for Object Type PSCC (and identify your Standard Schema).  The report will list all transports with that object, and by whom.

Note that Object Type PCYC would report on PCRs.

0 Kudos

Hi,

One alternate way is to get the std.schema text from SAP documentation in a text file and compare it with the current std schema of your existing system (may be easy for finding changes in schema. But may be bit difficult to do this for finding changes in std rules,since there may be large text of rules exist).

Another way is to compare your existing standard schema with a std schema in a test system.

May also check your tickets raised to SAP for any schema related changes made by any of your consultants.

May also check the below link:

http://help.sap.com/saphelp_erp60_sp/helpdata/en/8f/9fe2539c70424de10000000a174cb4/content.htm

Best Regards,

A.P.Balasubramanian

jagan_gunja
Active Contributor
0 Kudos

1. T52C0 table contains the standard SAP delivered schema.  If a customer changes it, it is saved in T52C1 with the same name.

The transaction PE01 always brings the one from T52C1 (not from T52C0) when you next go to display / edit the changed standard schema.

However PE02 txn always stores a PCR in T52C5 irrespective of whether it is a standard SAP object or a custom object.

To see the standard schema, in txn SE16 or SE16N, you can display T52C0.

Or display it in client 000; usually this client access is not allowed for even SAP consultants normally.

In view of the above, it is not recommended in any case, even for changes from an OSS note, for a user to change the standard schema/PCR, in PE01/PE02 or other way except the processes used by Basis team - e.g., SPAD, SPAM. 

To make such changes in a standard object, it should be copied to a customer name range; then the copy should be changed and used wherever required.

Such changes in SAP objects (e.g., schemas, PCR's, Dev objects) should be documented for future reference, so that when the standard object is changed by SAP, the customized object can be changed as required.

2. To see which transport has changed such objects you can search table E071 for dev objects including schema and PCR; and E071K for tables.

However I am not sure if this is dependent on transports containing such changed objects.  Many times it has been observed that config consultants delete objects from a transport, before releasing it; this deletion may be because the change was saved in a wrong transport or whatever.  In such cases, these tables E071 & E071K may not contain these changed object entries.

Following are the tables in this subject:

E070     Change & Transport System: Header of Requests/Tasks

E070A     Change & Transport System: Attributes of a Request

E070C     CTS: Source/Target Client of Requests/Tasks

E070CREATE     Change & Transport System: Creation Date of Request

E070DEP     Change & Transport System: Dependencies of Requests

E070L     CTS: Index for Assigning Numbers to Requests/Tasks

E070M     CTS: Target Development Class/Layer for Requests

E070N     UNIX/SAP User Connection

E070P     Path under which a C correction is created

E070TC     Help Table for E070 for Client-Specific Imports

E070USE     Use of Current Requests by Users

E071     Change & Transport System: Object Entries of Requests/Tasks

E071C     Change & Transport System: Client-Specific Lock Flag

E071E     Lang. Transport: Positive List for Generic Object Selection

E071K     Change & Transport System: Key Entries of Requests/Tasks

E071KF     Change & Transport System: Nametab Information on Key Fields

E071KFINI     Change & Transport System: Nametab Information on Key Fields

E071L     Language Transport: Transport Information

E07T     Change & Transport System: Short Texts for Requests/Tasks

3. Provided the table is set for logging, you can use program RSTBHIST. to report change log for such SAP objects,   However, such setting for log should be in development system/cliernt. 

It is not recommended for production system/client.  Otherwise for each schema transport, the log database will be updated and this is a burden on production resources.

See link

Here’s something you probably don’t already know: Learn how to quickly & easily track & ana...

kmoore007
Active Contributor
0 Kudos

If you mean the standard schema/rules delivered by SAP, the original schemas/rules exist in client 000.  You can compare tables T52C1 and T52C5 from client 000 to your production client using transaction SCMP.