Request clarification before answering.
Dear Sir,
This is clear message for duplicate record. Please check it.
Anil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi
i dont have access to system now but i have screenshot, im writing some lines from screenshot below, i will paste more detail tomorrow:
Information on where terminated
Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in "BAL_DB_INTERNAL_NO_UPDATE_TASK"
job name - long BI job name
Job initiator - ALEREMOTE
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in procedure
"BAL_DB_INTERNAL_NO_UPDATE_TASK"
Hi Shilpa,
This is very known dump occurs in production environment. This dump occurs when any transaction or job is trying to insert duplicate records in a table. You can find the table information, if any corresponding update record failed with the same reason. You can also find table information from this dump only in ST22.
Ask your ABAP team to go through the dump. They can resolve the issue.
Hope it helps.
Thanks,
Siva Kumar
Shilpa,
This is very common issue. Normally a transport has made a change and the code is actually trying to insert duplicate records. ST22 will help but the basis team should see update failures in SM13 that will also show the details on the table and line of code with the issue along with the actual record trying to be inserted with the key values.
Good Luck
Allan Stone
EMC Solutions Design Center
SAP Solutions Architect
| User | Count |
|---|---|
| 23 | |
| 15 | |
| 7 | |
| 5 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.