Skip to Content
avatar image
Former Member

SPAU - Logical Info Objects (Client Specific)

My experience with handling patching conflicts in SPAU is minimal. We currently have a conflict with 3 objects under the category of "Without Modification Assistant - HR Objects - Logical Info Objects (client specific)".

I have no idea what do to properly resolve this so that we can finish patching. I am sure this is a simple thing for experienced people.

Furthermore, being client specific it suggests that whatever needs to be done should be done in our config client. True or False?

I am looking for some practical advice to get me looking in the right place for resolving this matter.

Any practical real-life references to SPAU problem resolution would be appreciated.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Jan 28, 2008 at 12:29 PM

    Hi John,

    I believe when faced with patch conflict, best way is to start with note corrections listed in SPAU which generates a transport request used in subsequent systems.

    For objects under "Without the Modification Assistant", which I haven't encountered yet, SAP recommends use of versioning. Hope following link helps:

    Link:[Without the Modification Assistant|http://help.sap.com/saphelp_nw70/helpdata/en/83/7a1913de6e11d195460000e82de14a/frameset.htm]

    Please award points if found usefull.

    regards, Shantanu

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 01, 2011 at 02:57 PM

    These are SAP HR Documentation objects. Use transaction PDSY and compare the object in question manually with the non-upgraded environment to understand the conflicts. Unless a customer change is in conflict with new SAP changes, the object can be reset to original.

    - Saurabh

    Add comment
    10|10000 characters needed characters exceeded