Skip to Content

Missing CDESK_SRV_S_FDT_INST_CAD

Hi,

we have just installed ECTR plug-in in a S/4 Hana 1511 system with last SP available: SP6. We have several dump as:

Category ABAP programming error

Runtime Errors SYNTAX_ERROR

ABAP Program /DSCSAG/SAPLDOCUMENT2

Application Component PLM-ECC

Date and Time 06.12.2017 17:17:14

Short Text Syntax error in program "/DSCSAG/SAPLDOCUMENT2 ".

What happened?

Error in the ABAP application program.

The current ABAP program "/DSCSAG/SAPLFOLDER" had to be terminated because it found a statement that could not be executed. In include "/DSCSAG/LDOCUMENT2U24 ", in line 62 of program "/DSCSAG/SAPLDOCUMENT2 ", the following syntax errors have occurred: The type "CDESK_SRV_S_FDT_INST_CAD" is missing.

---------------------------------------------------------------------------------------------------- |Source Code Extract | ---------------------------------------------------------------------------------------------------- |Line |SourceCde | ---------------------------------------------------------------------------------------------------- | 97| MOVE-CORRESPONDING folderdata_in TO ls_folderdata_in. | | 98| | | 99| CALL METHOD /dscsag/utils=>timestamp | | 100| IMPORTING | | 101| time_char = ls_folderdata_in-checkin_date. | | 102| | | 103|*beg ins mika20170808 | | 104| | | 105| REFRESH: lt_characteristicvalues, lt_classallocations. | | 106| IF iv_copytopfolclass IS NOT INITIAL. | | 107| | | 108| ls_linked_doc_key = /dscsag/utils=>objkytodockey( objky = topfoldersapkey ). | | 109| | | 110| CALL FUNCTION 'BAPI_DOCUMENT_GETDETAIL2' | | 111| EXPORTING | | 112| documenttype = ls_linked_doc_key-documenttype | | 113| documentnumber = ls_linked_doc_key-documentnumber | | 114| documentpart = ls_linked_doc_key-documentpart | | 115| documentversion = ls_linked_doc_key-documentversion | | 116| getclassification = 'X' | | 117| IMPORTING | | 118| return = ls_return | | 119| TABLES | | 120| characteristicvalues = lt_characteristicvalues | | 121| classallocations = lt_classallocations. | | 122| | | 123| ENDIF. | | 124|*end ins mika20170808 | | 125| | | 126|* Folder Dokument anlegen | |>>>>>| CALL FUNCTION '/DSCSAG/DOC_CREATE2' | | 128| EXPORTING | | 129| documentdata = ls_folderdata_in | | 130| topfolder = topfoldersapkey "ws20091020 | | 131| iv_client_version = iv_client_version "bi20070627 | | 132| IMPORTING | | 133| return = return | | 134| documentdata_out = folderdata_out | | 135| TABLES | | 136| documentdescriptions = folderdescriptions | | 137| characteristicvalues = lt_characteristicvalues "mika20170808 | | 138| classallocations = lt_classallocations "mika20170808 | | 139| extensionin = extensionin | | 140| topfolder_returns = lt_topfolder_returns[]. "bi20130430 | | 141| | | 142| IF return-type CA 'EA'. | | 143| return-message_v4 = '/DSCSAG/DOC_CREATE2'. | | 144| EXIT. | | 145| ENDIF. | | 146| APPEND LINES OF lt_topfolder_returns TO et_topfolder_returns. "bi20160729 | ----------------------------------------------------------------------------------------------------


Have you got any idea?

Thank you.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Jan 03 at 12:16 PM

    Hi,

    thanks for the screenshot. Could you please check if there is a dump raised in the backend system in transaction ST22. Or it would help a lot if you make a syntax check for function module /DSCSAG/SAPLDOCUMENT2 and provide me the details shown in transaction SE37.

    In a similar issue the implementation of note 2270774 was useful to solve the issue.

    If you see the solution part of the note 2270774, in total a sequence of 7 notes are mentioned there with some of them being the UDO report for which you'll have to perform the manual steps.

    Kindly de-implement following notes:

    2392424

    2366212

    2270774

    and implement the following notes in the given sequence:

    2378539 - UDO report
    2355416
    2378570 - UDO report
    2270774
    2366212
    2392424
    2413274

    Don't miss out on pre-requisite notes and on following the manual steps in UDO reports.

    Best regards,

    Christoph

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Christoph,

      I implemented the notes mentioned by you in the sequence

      2378539 - UDO report
      2355416
      2378570 - UDO report
      2270774
      2366212
      2392424
      2413274

      But i am still getting the same error in ECTR. Please help me with the structure of this CDESK_SRV_S_FDT_INST_CAD or with note?

      Thanks

      Raja

  • Jan 04 at 08:00 AM

    Hi Raja,

    thanks for the additional details. With this data I found only note 2516622 which should implement this 'missing' type CDESK_SRV_S_FDT_INST_CAD.

    Please note that there are also some manual steps required during the implementation of these notes.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 02 at 10:04 AM

    Hi,

    based on this information I found the following SAP notes which should be considered:

    2366478
    2434459
    2358967
    2418488
    2516622

    For further more detailed suggestion please share a screenshot of the syntax error pop-up.

    Best regards,

    Christoph

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Christoph,

      I am facing below syntax error when i am executing my user ID specific folder from ECTR. Can you pleas help me on this error message?

      Thanks a lot in advance for your help.

      version details are below.

      ECTR 5.1
      API Transport: V 5.01.11.00 - 510 / 0011
      JARs Build: 0.1rc18 (27.10.2015 19:20:34)