2013 Oct 09 7:04 AM
Hi to All,
Please help me to resolve this issue or any another alternate of this BAPI.
this BAPI is working on our production server but not running on development client.
i checked the Patch level. Patch levels are different on both development & client so may be this is the reason.
Error in the ABAP Application Program
The current ABAP program "SAPLIBAPI_ALM_ORDER_SUBOBJECTS" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLIBAPI_ALM_ORDER_HEAD " in
include "LIBAPI_ALM_ORDER_HEADTOP " in
line 3:
"INCLUDE report "LIBAPI_HT01" not found"
" "
" "
" "
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLIBAPI_ALM_ORDER_SUBOBJECTS" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
2014 Mar 03 6:54 PM
Hi Pardeep
Were you able to resolve this? I saw at one of my clients that the missing include exists in their system since 2002 as per attachment:
and the following is the include that previously existed in our system.
The only notes I can find on this are these two that relate to incorrect version management of the object. But now it seems like SAP deleted the object?
1547780 - Incorrect version management for include LIBAPI_HT01
1540410 - Incorrect version management for include LIBAPI_HT01
*&---------------------------------------------------------------------*
*& Include LIBAPI_HT01 *
*&---------------------------------------------------------------------*
* structure that holds all relevant data for a technical object
types: begin of g_object,
bautl like caufvd-bautl,
equnr like caufvd-equnr,
tplnr like caufvd-tplnr,
serialnr like caufvd-serialnr,
sermat like caufvd-sermat,
equi like equi,
equz like equz,
iflo like iflo,
iloa like iloa,
riot like riot,
end of g_object.
* additional data structure for things like location work center
types: begin of caufvd_extended,
iaplz like caufvd-vaplz, "location data work center
net_vornr like afvgd-vornr, "superior network opr. num.
end of caufvd_extended.
** Update structure for CAUFVD data
* types: begin of iwo_caufvdx,
** some general data mainly set up via customizing but changeable
* plknz type bapiupdate,
* ilart type bapiupdate,
* kapversa type bapiupdate,
* terkz type bapiupdate, "should not be initial
* auterm type bapiupdate,
* aukbed type bapiupdate,
* breaks type bapiupdate,
* abkrs type bapiupdate,
* kalsm type bapiupdate,
* zschl type bapiupdate,
* abgsl type bapiupdate,
* ktext type bapiupdate,
* audisp type bapiupdate,
** estimated costs data on header level
* user4 type bapiupdate,
** workcenter, responsible plant
* vaplz type bapiupdate,
* vawrk type bapiupdate,
* ingpr type bapiupdate,
* anlzu type bapiupdate,
** technical object data
* tplnr type bapiupdate,
* equnr type bapiupdate,
* serialnr type bapiupdate,
* sermat type bapiupdate,
* bautl type bapiupdate,
* deviceid type bapiupdate,
** location data
* swerk type bapiupdate,
* stort type bapiupdate,
* msgrp type bapiupdate,
* beber type bapiupdate,
* iaplz type bapiupdate,
* abckz type bapiupdate,
* vkorg type bapiupdate,
* vtweg type bapiupdate,
* spart type bapiupdate,
* ibukrs type bapiupdate,
* anlnr type bapiupdate,
* anlun type bapiupdate,
* igsber type bapiupdate,
* kostl type bapiupdate,
* proid type bapiupdate,
* eqfnr type bapiupdate,
* daufn type bapiupdate,
* iaufnr type bapiupdate,
** additional data
* gsber type bapiupdate,
* prctr type bapiupdate,
* kostv type bapiupdate,
* func_area type bapiupdate,
* txjcd type bapiupdate,
** AIB data
* ivpro type bapiupdate,
* sizecl type bapiupdate,
* izwek type bapiupdate,
* umwkz type bapiupdate,
** sales document data
* kdauf_aufk type bapiupdate,
* kdpos_aufk type bapiupdate,
* bemot type bapiupdate,
** scheduling parameters
* priok type bapiupdate,
* revnr type bapiupdate,
** additional data (importing as scheduling is influenced here)
* pspel type bapiupdate,
* aufnt type bapiupdate,
* net_vornr type bapiupdate,
** scheduling date/time
* gstrp type bapiupdate,
* gltrp type bapiupdate,
* gsuzp type bapiupdate,
* gluzp type bapiupdate,
* end of iwo_caufvdx.
* Update structure for PMSDO data
* types: begin of IBAPI_PMSDO_UPD_INT,
* vkorg type bapiupdate,
* vtweg type bapiupdate,
* spart type bapiupdate,
* vkbur type bapiupdate,
* vkgrp type bapiupdate,
* matnr type bapiupdate,
* menge type bapiupdate,
* ffprf type bapiupdate,
* faktf type bapiupdate,
* bstdk type bapiupdate,
* bstkd type bapiupdate,
* end of IBAPI_PMSDO_UPD_INT.
2014 Apr 09 12:32 PM
Hi Pardeep,
Did you get the solution for this problem? I am facing the same issue. Please let me know how you solved this issue.
2014 Apr 09 12:58 PM
I managed to resolve this by getting an access key and recreating the SAP deleted include LIBAPI_HT01 (as per inline code above). Then it compiles and runs fine. Why SAP deleted their own include from their own Function Group, remains a mystery.. I've seen some strange things happen the past 6 months in HR - old versions of objects being restored and blocks of code that worked just disappearing..
2014 Apr 09 1:35 PM
Thank you Adrian for your prompt reply.
But when I try to create it through se38 it is throwing me error and does not ask for access key. Could you elaborate on how you managed to create the include. Your reply on this is much appreciated.
Thanks!
2014 Apr 10 7:02 AM
SAP Note 0001547780 Solved my problem. Thanks for your help.
2014 Apr 15 8:29 PM
It is exactly the same as I've done. Note 1547780 refers to notes 1541401 and 1540410. They all refer to version management which is incorrect. What actually happened was that the include was erroneously deleted by SAP and they simply show you in the note correction instructions how to restore their include. In your transport you will then see the content as Report Source Code LIMU REPS LIBAPI_ALM_ORDER_HEADTOP. I'm glad you were able to resolve this too.
2014 Apr 16 10:48 AM
Hi Pradeep,
Please goto t-code SE80.
give the program name and reactive it.
After reactivation it will work.
Regards,
Sanjeeb
2014 Apr 16 11:41 AM
Not true Sanjeeb. Please follow the thread to understand the problem. The include was deleted by a SAP patch. The notes mentioned describe how to restore the SAP include object. Only then will it compile.