vimalg / zaplink

Automatically exported from code.google.com/p/zaplink
0 stars 0 forks source link

Unexpected message : Type xxx already exists #113

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Import Framework on SAP ECC (701 - SAPKB70103)

What is the expected output?
No Warning

What do you see instead?
Processing (INTF) ZAPLINK_CNX_EXT_CODE_SIGNATURE
Type TD_CHECKSUM already exists
Failed to import (INTF) ZAPLINK_CNX_EXT_CODE_SIGNATURE
Processing (INTF) ZAPLINK_CONNECTOR
Type TD_COMPEXISTS already exists
Type TD_COMPNAME already exists
Type TD_COMPTYPE already exists
Type TD_CONNCLASS already exists
Type TD_CONNEXISTS already exists
Type TD_CONNUUID already exists
Type TD_CONNVER already exists
Type TO_XML already exists
Type TS_BASE_ATTRIBUTS already exists
Type TS_CONNDATA already exists
Type TT_TYPES already exists
Failed to import (INTF) ZAPLINK_CONNECTOR

Original issue reported on code.google.com by taryck%b...@gtempaccount.com on 24 Dec 2010 at 10:16

GoogleCodeExporter commented 9 years ago
After analyse this warning message come from the following code :

* Patch SAP do not create type alias.
    DATA  intkey TYPE seoclskey.
    DATA  type   TYPE vseotype.
    FIELD-SYMBOLS <alias> LIKE LINE OF _d-aliases.

    LOOP AT _d-aliases ASSIGNING <alias>
            WHERE cmptype = seoo_cmptype_type.
      MOVE-CORRESPONDING <alias> TO type.
      type-alias = seox_true.
      type-state = seoc_state_implemented.
      CALL FUNCTION 'SEO_TYPE_CREATE_F_DATA'
        EXPORTING
          save   = seox_false
        CHANGING
          type   = type
        EXCEPTIONS
          OTHERS = 1.
      IF sy-subrc <> 0.
        CALL METHOD application_log->add_symsg
          EXPORTING
            id_msgty = 'W'.
      ENDIF.
    ENDLOOP.

This patch has been added because on some SAP system alias for type are lost.
Action : Correct this patch.

Original comment by taryck%b...@gtempaccount.com on 24 Dec 2010 at 10:17

GoogleCodeExporter commented 9 years ago
The message returned is 002(OO).

Original comment by taryck%b...@gtempaccount.com on 24 Dec 2010 at 10:18

GoogleCodeExporter commented 9 years ago
Issue fdixed with changeset : 
http://code.google.com/p/zaplink/source/detail?r=203c26d36cb92433c25b15d5bd396f3
8166b4165

Original comment by taryck%b...@gtempaccount.com on 27 Dec 2010 at 6:24