Attaching URL using GOS with 2 key fields

Question

I found a program to attach URL using GOS. I tried the program using his sample Business object (BUS2012) and supplied a valid PO and the program works.
When I use the program using business object BUS1505 (Real Estate Contract) and put a valid contract number, the program didn't attached the URL. When I check the business object, I found out that the key fields are 2, Company Code and Contract Number. With this, how can attach it to the program.
Please help me on this. Thanks in advance.
Report  Z_RMTIWARI_ATTACH_DOC_TO_BO
Written By : Ram Manohar Tiwari
Function   : We need to maintain links between Business Object and
             the attachment.Attachment document is basiclally a
             business object of type 'MESSAGE'.In order to maintain
             links, first the attachment will be crated as Business
             Object of type 'MESSAGE' using Message.Create method.
             Need to check if we can also use FM
             'SO_DOC_INSERT_WITH_ORIG_API1' or SO_OBJECT_INSERT rather
             than using Message.Create method.
REPORT  Z_RMTIWARI_ATTACH_DOC_TO_BO             .
Include for BO macros
  INCLUDE : <cntn01>.
Load class.
  CLASS CL_BINARY_RELATION definition load.
  CLASS CL_OBL_OBJECT      definition load.
PARAMETERS:
Object_a
   P_BOTYPE LIKE obl_s_pbor-typeid DEFAULT 'BUS1505', " e.g. 'BUS2012'
   P_BO_ID  LIKE OBL_S_PBOR-INSTID DEFAULT '0000010000273',    " Key e.g. PO No.
Object_b
   P_DOCTY  LIKE obl_s_pbor-typeid DEFAULT 'MESSAGE' NO-DISPLAY,
   P_MSGTYP LIKE SOFM-DOCTP        DEFAULT 'URL'     NO-DISPLAY,
Relationship
   P_RELTYP  LIKE mdoblrel-reltype DEFAULT 'URL'.
  types: BEGIN OF TY_MESSAGE_KEY,
          FOLTP   TYPE SO_FOL_TP,
          FOLYR   TYPE SO_FOL_YR,
          FOLNO   TYPE SO_FOL_NO,
          DOCTP   TYPE SO_DOC_TP,
          DOCYR   TYPE SO_DOC_YR,
          DOCNO   TYPE SO_DOC_NO,
          FORTP   TYPE SO_FOR_TP,
          FORYR   TYPE SO_FOR_YR,
          FORNO   TYPE SO_FOR_NO,
         END OF TY_MESSAGE_KEY.
  DATA : LV_MESSAGE_KEY type TY_MESSAGE_KEY.
  DATA : LO_MESSAGE type SWC_OBJECT.
  DATA : LT_DOC_CONTENT type standard table of SOLI-LINE with header
line.
First derive the Attachment's ( MESSAGE )document type.
  P_DOCTY = 'MESSAGE'.
  CASE P_RELTYP.
  In case of URls
    WHEN 'URL'.
       P_MSGTYP = 'URL'.
  In case of Notes / Private Notes
    WHEN 'NOTE' OR 'PNOT'.
       P_MSGTYP = 'RAW'.
    WHEN 'ATTA'.
       P_MSGTYP = 'EXT'.
  Not implemented as yet...exit
     EXIT.
    WHEN OTHERS.
   ....exit
     EXIT.
    ENDCASE.
Create an initial instance of BO 'MESSAGE' - to call the
instance-independent method 'Create'.
  swc_create_object LO_MESSAGE 'MESSAGE' LV_MESSAGE_KEY.
define container to pass the parameter values to the method call
in next step.
  swc_container LT_MESSAGE_CONTAINER.
Populate container with parameters for method
  swc_set_element LT_MESSAGE_CONTAINER 'DOCUMENTTITLE' 'Title'.
  swc_set_element LT_MESSAGE_CONTAINER 'DOCUMENTLANGU' 'E'.
  swc_set_element LT_MESSAGE_CONTAINER 'NO_DIALOG'     'X'.
  swc_set_element LT_MESSAGE_CONTAINER 'DOCUMENTNAME' P_DOCTY.
  swc_set_element LT_MESSAGE_CONTAINER 'DOCUMENTTYPE'   P_MSGTYP.
'DocumentContent' is a multi-line element ( itab ).
In case of URLs..it should be concatenated with &KEY& in the begining.
  CASE P_MSGTYP.
    WHEN 'URL'.
      LT_DOC_CONTENT = '&KEY&http://intranet.corpoff' .
      append LT_DOC_CONTENT.
In case of Notes or Private Notes, get the data from files on appl
server or from wherever(? - remember background).
     WHEN 'RAW'.
       LT_DOC_CONTENT = 'Hi How r u?' .
       append LT_DOC_CONTENT.
In case of File attachments
     WHEN 'EXT'.
      Upload the file contents using open dataset in lt_doc_content .
      Some conversion ( Compress ) might be required.
      Not sure at this point
  ENDCASE.
  swc_set_element LT_MESSAGE_CONTAINER 'DocumentContent' LT_DOC_CONTENT.
  swc_call_method LO_MESSAGE 'CREATE' LT_MESSAGE_CONTAINER.
Refresh to get the reference of create 'MESSAGE' object for attachment
  swc_refresh_object LO_MESSAGE.
Get Key of new object
  swc_get_object_key LO_MESSAGE LV_MESSAGE_KEY.
Now we have attachment as a business object instance. We can now
attach it to our main business object instance.
Create main BO object_a
  data: LO_IS_OBJECT_A type SIBFLPORB.
  LO_IS_OBJECT_A-INSTID = P_BO_ID.
  LO_IS_OBJECT_A-TYPEID = P_BOTYPE.
  LO_IS_OBJECT_A-CATID  = 'BO'.
Create attachment BO object_b
  data: LO_IS_OBJECT_B type SIBFLPORB.
  LO_IS_OBJECT_B-INSTID = LV_MESSAGE_KEY.
  LO_IS_OBJECT_B-TYPEID = P_DOCTY.
  LO_IS_OBJECT_B-CATID  = 'BO'.
*TRY.
CALL METHOD CL_BINARY_RELATION=>CREATE_LINK
  EXPORTING
    IS_OBJECT_A            = LO_IS_OBJECT_A
   IP_LOGSYS_A            =
    IS_OBJECT_B            = LO_IS_OBJECT_B
   IP_LOGSYS_B            =
    IP_RELTYPE             = P_RELTYP
   IP_PROPNAM             =
   I_PROPERTY             =
IMPORTING
   EP_LINK_ID             =
   EO_PROPERTY            =
*CATCH CX_OBL_PARAMETER_ERROR .
*CATCH CX_OBL_MODEL_ERROR .
*CATCH CX_OBL_INTERNAL_ERROR .
*ENDTRY.
Check if everything OK...who cares!!
  commit work.

Answer 1

HI
You can look at object VBAP as an example.  It'sthe sales order item and has two keys - sales order number and item number. 
the key was created:
BEGIN OF KEY,
     SALESDOCUMENTNO LIKE VBAP-VBELN,
     ITEMNO LIKE VBAP-POSNR,
END OF KEY,
     MATERIAL TYPE SWC_OBJECT,
     SALESDOCUMENT TYPE SWC_OBJECT,
     _VBAP LIKE VBAP.
ND_DATA OBJECT. " Do not change.. DATA is generated
Here is a object instantiation - just build the key with the two fields - then when you call the macro - you pass the one field that already has both keys in it.
GET_PROPERTY SALESDOCUMENT CHANGING CONTAINER.
  SWC_CREATE_OBJECT
    OBJECT-SALESDOCUMENT 'VBAK' OBJECT-KEY-SALESDOCUMENTNO.
  SWC_SET_ELEMENT CONTAINER 'SalesDocument' OBJECT-SALESDOCUMENT.
END_PROPERTY.