Can incoming Transport Request be Trapped?

Question

Hi Experts,
The problem may look weird for you. Is there a way where we can trap incoming Transport Request.
We actually are updating some of the tables' data and are registering the modified data in Transport Request. While modifying data, we also refresh Shared Memory.
But now, when this Transport Request is released to target system, we want to refresh Shared memory in Target system also which can be only possible when can track incoming Transport Request in target system and based on contents of Transport Request, we refresh the shared memory.
Is it possible?
Thanks and Regards,
Gopal

Answer 1

From your message text I found message TR855 (please provide this next time).
Long text is indeed strange, the where-used list did not provide a hit.
Message class TR is in package SCTS_REQ.
I then looked for string "855" in package SCTS_REQ and found following interesting code in function module TRINT_INTERNAL_RELEASE:
*---SAP internal: is XPRA in request approved?
    if   system_type             = 'SAP'
    and  cs_request-h-trfunction = sctsc_type_workbench.
      read table cs_request-objects transporting no fields
                         with key pgmid = 'R3TR'
                                  object = 'XPRA'.
      if sy-subrc = 0.
        select single * from te07f into ls_te07f
                                   where korrnum = cs_request-h-trkorr.
        if sy-subrc ne 0.
          message e855(tr) with cs_request-h-trkorr
                           raising no_authorization.
        endif.
      endif.
    endif.
System type "SAP"? Are you not working in a customer environment (system type = "CUSTOMER") ?
Check with your system administration, RZ11 parameter "transport/systemtype" might be wrongly set.
The code also tells that by adding your transport number to table TE07F (via SM30) you might be able to work around the problem.
Thomas