Page tree
Skip to end of metadata
Go to start of metadata

This page helps you to troubleshoot issues related to the incomplete content after having packaged a SAP application.

For more information, refer to:

Applicable in CAST Version

8.2.x (tick)
8.1.x (tick)
8.0.x (tick)
7.3.x (tick)
Applicable RDBMS
Oracle Server N/A
Microsoft SQL Server N/A
Step by Step scenario
  1. Extract Data from the SAP extraction system without any errors or warnings.
  2. Examine the extraction results and notice issues during validation of the extraction results.
Action Plan

Perform the below actions

  1. Check to see if the non extracted packages have no programs
    1. In the Main SAP Page, go to the transaction se16:

    2. Go To the table TADIR :

    3. Fill the table like below : Object : Prog (for programs) and DEVCLASS = The name of the package:

    4. When run, then It will give the list of programs per packages

    5. Alternatively, check in the transaction se80 : From there you can check the content of the Package: 

  2. If the non-extracted packages have programs on SAP, then see if the package name starts with "_".
    1. If this is the case, conirm that the SAP BAPI files have become folders :
      1. The first folder is SAP_BAPI_, the second folder is the package name, and the xml file is created in the package folder.
        1. For instance, for the package _MAHLE_0028, the expected name for a file like SAP_BAPI__MXXXX_0028.xml, but instead it is SAP_BAPI/MXXXX/0028.xml

    2. If the files have become folders, then the solution is to manually rename the xml file as it is expected to be : SAP_BAPI_<PACKAGE_NAME>.xml and place it in the root of the package (where currently the SAP_BAPI folder is being created.

  3. If the above steps do not solve your issue contact Cast Technical Support with Relevant input from the other issues section in order to reproduce this issue

Ticket # 7728, #11450

Related Pages


  • No labels