on 02-15-2010 10:35 AM
Hi SAP gurus,
Presently we are having a scenario, While creating a sales order through EDI we are presently getting an error
Status - 51 "Update Error, Transaction VA01".
When I again reprocess the idoc, It is creating order successfully.
This is a rare occrance and we are not able to get a concrete clue because out of 50 edi order only 2 orders are
having this kind of issue. .
T code - WE02 :
When I click on the message information, it gives the below mentioned details :
Message - No 00377 "Update error, transaction VA01"
Diagnosis:
An error occured in CALL TRANSACTION USING or CALL DIALOG USING during the synchronous update.
The error is caused y the transaction VA01.
*T code - SM13 *
In SM13 - system gives the Error (no entry) in
Functional module "RV_SALES_DOCUMENT_ADD".
ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC
Status : Update was terminated
Could you please provide some inputs for to fix the issue
Thanks in advance
Thanks&Regards,
Pugal Stalin.
Check note
a) 1076259 or
b) 426533
thanks
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lakshmipati,
Thank you so much..
I have referred the two notes
*OSS note - 1076259 - ("00377: Update error, T code - IW32")
OSS note - 426533 - ("Update error, T code - CJ9FS" )
T code - IW32 is related to internal order
T code - CJ9FS is related to controlling.
Simillarly, May I know is there any chance of getting OSS note which is related to our scenario - Sales order.
("00377: Update error, T code - VA01")
May I know what it could be reason that system is currently having this kind of issue.
Please Advise..
Thanks & Regards,
Pugal Stalin
Hi Yadav,
Our main concern is "It is a rare occurrance" . Initially We think that it was happening for EDI order and presently It's happening for standard order "OR" which are created manually by Users.
We would like to know two things:
What is the root cause of this occurance
May I know is there any fix through ABAP approch
Note : ABAPers wants a replicatable scenario but here the issue is rare occurance.It is not advisable to directly debugg in production also..
Could you please understand the situation and suggest the approach
Thanks & Regards,
Pugal Stalin
Hi
check your short dumps (ST22) and post the coding part
so we can see which table insert cause the crash,
Ralf
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hI,
It's mentioned below :
Information on where terminated
Termination occurred in the ABAP program "SAPLV05I" - in "SD_PARTNER_UPDATE".
The main program was "RSM13000 ".
In the source code you have the termination point in line 480
of the (Include) program "LV05IU15".
The program "SAPLV05I" was started in the update system.
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "SD_PARTNER_UPDATE" "(FUNCTION)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLV05I "; its source code begins in line
1 of the (Include program "LV05IU15 ".
Source Code Extract
POSNR = I_XVBPA-POSNR
PARVW = I_XVBPA-PARVW.
IF I_YVBPA-STCD1 <> I_XVBPA-STCD1 OR
I_YVBPA-STCD2 <> I_XVBPA-STCD2 OR
I_YVBPA-STCD3 <> I_XVBPA-STCD3 OR
I_YVBPA-STCD4 <> I_XVBPA-STCD4 OR
I_YVBPA-STCDT <> I_XVBPA-STCDT OR
I_YVBPA-STKZN <> I_XVBPA-STKZN OR
I_YVBPA-J_1KFREPRE <> I_XVBPA-J_1KFREPRE OR
I_YVBPA-J_1KFTBUS <> I_XVBPA-J_1KFTBUS OR
I_YVBPA-J_1KFTIND <> I_XVBPA-J_1KFTIND.
MOVE-CORRESPONDING I_XVBPA TO WA_XVBPA3I.
APPEND WA_XVBPA3I TO DA_XVBPA3I.
ENDIF.
ENDIF.
ENDIF.
WHEN UPDKZ_OLD.
IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD OR
DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
YADR-ADRNR = DA_VBPA-ADRNR. COLLECT YADR.
ENDIF.
IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD OR
DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
XADR-ADRNR = DA_VBPA-ADRNR. COLLECT XADR.
ENDIF.
ENDCASE.
ENDLOOP.
UPDATE (OBJECT) FROM TABLE DA_XVBPAU.
UPDATE VBPA3 FROM TABLE DA_XVBPA3U.
INSERT (OBJECT) FROM TABLE DA_XVBPAI.
INSERT VBPA3 FROM TABLE DA_XVBPA3I.
IF SY-SUBRC > 0.
MESSAGE A700 WITH OBJECT SY-SUBRC DA_XVBPAI(21).
ENDIF.
Sonderfall neue VBPA (VBPA2) für Rollen AA und AW
LOOP AT I_XVBPA2.
DA_VBPA2 = I_XVBPA2.
CASE DA_VBPA2-UPDKZ.
WHEN UPDKZ_NEW.
IF DA_VBPA2-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD OR
DA_VBPA2-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
XADR-ADRNR = DA_VBPA2-ADRNR. COLLECT XADR.
ENDIF.
I_XVBPA-MANDT = SY-MANDT.
IF I_XVBPA2-VBELN IS INITIAL.
I_XVBPA2-VBELN = F_VBELN.
ENDIF.
Thanks in Advance
Thanks & Regards,
Pugal
Edited by: Pugal Stalin on Feb 15, 2010 1:17 PM
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.