2014 Aug 25 10:55 AM
Dear all,
I am using the FM BAPI_ALM_ORDER_MAINTAIN. This FM is a RFC. When I execute BAPI_ALM_ORDER_MAINTAIN, I have confirmed that the return information indicates success. When I execute the BAPI_TRANSACTION_COMMIT, the FM terminiates witha short dump
Error analysis
A RAISE statement in the program "SAPLCOZV" raised the excepti
condition "DUMP_STATUS_INCONSYSTENCY_FRE".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
Please let me know the solution for this problem,
Thanks in advance.
Regards,
Syed Taj
2014 Aug 25 11:22 AM
Hi Syed,
Notes:559463
Symptom
You save a maintenance order or service order and an update termination occurs.
Other Terms
DUMP_STATUS_INCONSYSTENCY_ERL
DUMP_STATUS_INCONSYSTENCY_ERO
DUMP_STATUS_INCONSYSTENCY_FRE
DUMP_COMMIT_WITHOUT_ORDER_DATA
IW31, IW32, IW34, IW36, IW38, SAPLCOZV, LCOZVU23, IW21, IW22, IW28,
CO_ZV_CONSISTENCY_CHECK, JOB_OPEN
Reason and Prerequisites
In addition to the program errors described in note 157070 or in the related notes, the most common cause is a COMMIT WORK in an SAP enhancement (BAdI, user exit, customer exit, modification).
Caution: The COMMIT WORK can also be executed implicitly via a function module (for example, via function module JOB_OPEN).
In general, it is not allowed to execute more than one COMIIT WORK in the order update because otherwise the data consistency is not always ensured!
Seems you don`t need call 'BAPI_TRANSACTION_COMMIT'. hope can help you.
regards,
Archer
2014 Aug 25 11:22 AM
Hi Syed,
Notes:559463
Symptom
You save a maintenance order or service order and an update termination occurs.
Other Terms
DUMP_STATUS_INCONSYSTENCY_ERL
DUMP_STATUS_INCONSYSTENCY_ERO
DUMP_STATUS_INCONSYSTENCY_FRE
DUMP_COMMIT_WITHOUT_ORDER_DATA
IW31, IW32, IW34, IW36, IW38, SAPLCOZV, LCOZVU23, IW21, IW22, IW28,
CO_ZV_CONSISTENCY_CHECK, JOB_OPEN
Reason and Prerequisites
In addition to the program errors described in note 157070 or in the related notes, the most common cause is a COMMIT WORK in an SAP enhancement (BAdI, user exit, customer exit, modification).
Caution: The COMMIT WORK can also be executed implicitly via a function module (for example, via function module JOB_OPEN).
In general, it is not allowed to execute more than one COMIIT WORK in the order update because otherwise the data consistency is not always ensured!
Seems you don`t need call 'BAPI_TRANSACTION_COMMIT'. hope can help you.
regards,
Archer
2014 Aug 25 2:35 PM
Dear Archer,
Issue resolved, COMMIT WORK is the problem.
Thank you very much,
Regards,
Syed Taj