Question Re: Implementing OSS note correction in Technology Q&A

Implementing OSS note correction

Former Member — Fri, 09 Jan 2009 19:46:56 GMT

Hi,

I am implementing a SAP Note (1288878).

This note says implement .sar in the note. Appply this file to client 000 of your system then cascade the entries to the appropirate Customizing client(s).

What I have done is , un-car'd the .sar file

copied the two files to transport directories

imported the transport to client000

But I am not sure about the part which says cascading entries to the customizing client.

Can some please explain this part,

Thanks,

Re: Implementing OSS note correction

Former Member — Fri, 09 Jan 2009 20:21:07 GMT

Hai,

Cascading means Transporting the changes to other client of the system.

Since it is customising it is client specific, you have transported into client 000 and it will affect only client 000.

So you have to Transport into the client where you need it.

Regards,

Yoganand.V

Re: Implementing OSS note correction

Former Member — Fri, 09 Jan 2009 21:39:01 GMT

Thanks for the reply,

If I try to import it to other client (not 000) I get following message:

T5UGE table class is 'C'. Entries are only imported to client '000'.

T5UGF table class is 'C'. Entries are only imported to client '000'.

Can you please provide some guidelines.

Basically this note creates entries in the above two tables

Thanks,

Re: Implementing OSS note correction

Former Member — Sat, 10 Jan 2009 00:13:53 GMT

Hai,

Transport should have failed with the error you mentioned right?

Behavior during Installation, Upgrade and Language Import

The behavior of client-dependent tables differs from that of

cross-client tables.

Client-Dependent Tables

Class A and C: Data is only imported into client 000. Existing

data records are overwritten.

Cross-Client Tables

Classes A, L and C: No data is imported

So you need not to bother about the message.

If at all you need these in the client other than 000 then you can use Unconditional mode to transport the request which will force the transport according to the mode you select.

Regards,

Yoganand.V

Re: Implementing OSS note correction

Former Member — Sat, 10 Jan 2009 01:02:24 GMT

Thanks once again for the reply.

By unconditional mode of transport request, do you mean selecting the check box which says Ignore Permitted Table Class in STMS?

Also can we transaction SCC1 for cascading or will that too give the same error.

What is the correct approach to implement this type of corrections.

Thank you,

Re: Implementing OSS note correction

Former Member — Sat, 10 Jan 2009 17:45:00 GMT

Hai,

Yes you can select the option Ignore Permitted Table Class, if you want to transport through OS level look into the below link.....

http://help.sap.com/saphelp_sm40/helpdata/en/3d/ad5b814ebc11d182bf0000e829fbfe/content.htm

Remember using these option will force the Transport and overwrite the exisiting table.

As per the message

T5UGE table class is 'C'. Entries are only imported to client '000'.

T5UGF table class is 'C'. Entries are only imported to client '000'.

it is not necessary to transport the changes into other clients, but still you can use the above options to do the transports.

Good luck.

Regards,

Yoganand.V

Edited by: Yoganand Vedagiri on Jan 10, 2009 6:45 PM

Re: Implementing OSS note correction

Former Member — Mon, 12 Jan 2009 13:53:04 GMT

Thanks for the reply,

I am bit confused here,

Basically this note created entries in HR Tables T5UGE and T5UGF.

In the note it says:

"Apply this file to client 000 of your system, then cascade the entries to the appropriate Customizing client(s)".

These entries are required in the customized client (in our case 300). So what should be the correct approach to bring these entries to the customizing client.

Thanks,

Re: Implementing OSS note correction

Former Member — Tue, 25 Jan 2011 20:09:03 GMT

I am working on the same problem, and I would also like to know the correct approach to bring these entries to the customizing client.