Skip to Content

Disassemble file from etc\in to data and cofile. The files before disassemble could be like this: CSN0120061532_0015010.PAT / CSN0120061532_0015010.ATT Can be done in SPAM -> Utility -> Disassemble Package After assemble: the data/cofile are created: RD61011.SAP/KD61011 Then

TP addtobuffer SAPKD61011 QAS PF = tp_domain_qas.pfl

TP import SAPKD61011 QAS PF = tp_domain_qas.pfl

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Paul Tomlinson

    You make a good point that support packages are basically transports.  However – using this method skips important steps such as SPDD and SPAU.  Also I am not sure if it updates tables PAT01 and PAT03 which contain the list of imported support packages.

    Finally – in 12 years of SAP I’ve never had to do this.  I have had to reset the patch queue and re-apply them, but always managed to apply support packages with SPAM.

  2. Former Member
    Not every support package will be importable manually. Basis support packages are importable only in Tx SPAM (see note 1269395).
    Another problem, if you import a support package manually, the package level won’t updating. If you want to see the correct package level, you have to import the support package again in SPAM.
    Or, as a workaround you can insert the package information in table PAT03.

Leave a Reply