Adjusting Customizing from Client 000 post SP Implementation?

[alejandro_navajas3]

Hello Everyone,

I have a new situation after I implemented a bunch of HR Support Packages. I checked the transport logs and I found on most packages warnings telling the following: XXXX table class is 'C'. Entries are only imported to client '000'

It didn't get my attention but then a functional user told me that customizing changes introduced by a note than he expected to see after support packages implementation were not into the customizing client in development system. We checked client 000 and changes were applied in this client.

I followed this wiki http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=217451127&bc=true to copy new customizing changes from client 000 to customizing client, but then when I tried to adjust using transaction SM31, the following message I got for every table:

The maintenance dialog for XXXX is incomplete or not defined.

So, I used transaction SE54 to check the maintenance dialog and indeed there was no maintenance dialog. When I try to create with button create … I have to insert the object key, so I have to register the table in Marketplace (MP) to get the key. Then I get transaction SE55 (Generate Maintence Dialog)  and I have to complete the function group, and I have no idea which one I should select. Really it seems this is not right way to adjust customizing entries between client 000 and our customizing client in development system. Anyway I'm confused and I believe there's other best practice when support packages are implemented on a customized environment.

I would like to hear from you what do you think and if you know a "best practice" for this situations because I never had a situation like this one when I implemented support packages on previous SAP systems.

Thanks in advance for any suggestion or advice.

I leave hear additional information about support packages and tables were customizing was imported in client 000 only:

SAPKGPHD70              SP 70 for EA-HR 6.00

SAPKGPHD71              SP 71 for EA-HR 6.00

SAPKGPHD72              SP 72 for EA-HR 6.00

SAPKGPHD73              SP 73 for EA-HR 6.00

SAPKGPHD74              SP 74 for EA-HR 6.00

SAPKGPHD75              SP 75 for EA-HR 6.00

SAPKGPHD76              SP 76 for EA-HR 6.00

SAPKGPHD77              SP 77 for EA-HR 6.00

SAPKGPHD78              SP 78 for EA-HR 6.00

SAPKGPHD79              SP 79 for EA-HR 6.00

SAPKGPHD80              SP 80 for EA-HR 6.00

SAPKGPHD81              SP 81 for EA-HR 6.00

SAPKGPHD82              SP 82 for EA-HR 6.00

SAPKGPHD83              SP 83 for EA-HR 6.00

SAPKGPHD84              SP 84 for EA-HR 6.00

SAPKGPHD85              SP 85 for EA-HR 6.00

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

TDDAT table class is 'G'. Only new entries are imported.#

Ale

[tomas_black]

Hello Alejandro,

The tables class 'C' needs to be cascade from client 000 to other working clients. Kindly cascade the entries from client 000 for all tables listed above to other working clients.

Best regards,

Tomas Black

[alejandro_navajas3]

Hi Tomas,

Thanks for your answer. Is there a procedure recommended by SAP to cascade the entries?

I find it complicated to do it in the way I explained it. I mean, why the SPAM does not generate a report with all tables that were updated with new entries in client 000? Imagine the situation when instead of a bunch of SP I have to implement a STACK, should I analyse each support package log looking for those warning were a class C table was updated? It would be painful! don't you think?

Regards!

AN