Update termination message in F110 after system refresh

[bhakti2]

hi,

When we create payment in F110, this is BCM related payment . the payment is created and then environment - cross payment run payment medium  - Create Payment Medium  is done. That time following update termination is received. This error

started in quality system after recent refresh from production system. earlier to this refresh it was working fine.

Express document Update was terminated

Update was terminated
System ID....   EXX
Client.......   210
User.....   AXXX
Transaction..
Update key...   0241B1E1880FF114A3EE00155DCB29FB
Generated....   08.06.2012, 09:07:38
Completed....   08.06.2012, 09:07:38
Error Info...   Batch Header record with batch No 0000001096 not inserted.

kindly provide some clue.....

thanks

B

[former_member536436]

Dear All,

I faced this issue in Quality system after system refresh was done in Quality. You can resolve the issue with the below steps.

You can understand this issue by seeing the screenshots attached in the this same chain above.

If your issue is also same where the 2 tables are not matching.

You implement the Note with the help of Technical consultant : 1910000. Move the changes to Quality system and Run the report in Quality. The Report name is already given in the note.

After you run the report compare the table it will now match. Now continue your BCM process this error will be no more.

Regards,

Sarfaraz

[aotto]

The number in DFPM_NUMB-BNKCOM has to be higher than the highest number in BNK_BATCH_HEADER-BATCH_NO. That is the reason.

[raymond_giuseppi]

Could be caused by a duplicate key (check via SM13 and SM21) - If yes, adjust number ranges in refreshed QA environment.

Regards,

Raymond

[bhakti2]

hi

could you pl tell how to see if its caused by duplicate key ? (im trying to figure out from sm13 and sm21 )

thanks

[raymond_giuseppi]

"Batch Header record with batch No 0000001096 not inserted." look like the standar error message generated by update task function module when a duplicate key is generated during an INSERT into database table.

So Call transaction SM13, and check the parameters received by the FM in error. If you can identify the value, and the database table, find the actual last generated number, and the range number associated (transaction SNRO)

Try also to identify the exact message id : Is it BNK_COM_CORE 001 in FM BNK_DB_BATCH_INSERT, would be strange to get a duplicate key with a GUID key, so look also at transaction SM21 to get exact system/sql error message raised in the FM.

Regards,

Raymond