Idoc SHP_IBDLV_SAVE_REPLICA generated twice within few seconds

[Former Member]

Hello,

i am looking the cause of double idocs generated after that a DESADV created an inbound delivery.

Very randomly and maybe 1 time every week.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

| IDoc no.  |Release|Status|Directn|Created on|Time        |Message Type                                     |Serialization       |

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

|114360371|702       |53      |2         |29.07.2015|20:30:04  |DESADV                                             |20150729200111|

|114360379|702       |03      |1         |29.07.2015|20:30:14  |SHP_IBDLV_SAVE_REPLICA              |20150729203013|

|114348861|702       |03      |1         |29.07.2015|20:30:20  |SHP_IBDLV_SAVE_REPLICA              |20150729203019|

|114575901|702       |53      |2         |03.08.2015|08:46:24  |SHP_IBDLV_CONFIRM_DECENTRAL |20150803084622|

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

114348861 is the double.

the delivery got only 100 items.

checked WE20 with nothing special.

Nearly always the same vendor.

if any one can give me some hints to search some where.

thanks in advance.

P.

[mihailo_sundic]

Go to your delivery number, click on Service menu => Relationships.

It should contain in your case 2 IDOCs of save_replica. See what else is in there, should be 1 DESADV.

Then take your both IDOCs of type CONF_DEC and inspect them - compare for any differences and post them here / see if you can find something suspicious.

If they are the same, then it's most probably a tech. problem. Either on the sender or the receiver side, you need to check everything that is related to IB_DLV_SAVE_REPLICA...
What is your current sstem set-up, which type of interfaces are you using, anything changed and not using standard, well a lot of questions could arise...

Regards,
Mihailo

[MANIS]

it is very difficult to suggest without analyzing as you have only one or two case however I will suggest to check the change log for the deliver and the change pointer to trigger the Idoc. Might be that your change pointer is set that if any change in quantity in delivery then trigger the IDoc and that is the case for those delivery where you see second idoc