on 02-03-2011 6:23 AM
Hi,
I have a HTML to Idoc scenario wherein due to various technical reasons, rather limitations, duplicate idocs have been observed to be sent to the R/3 system.
We are thinking of usage of proxy in place of the reciever idocs, so that we may be able to check for duplicacy before the generation of the idocs.
Is this a feasible solution? Any alternatives to this are also welcome.
Regards,
Diptee
> We are thinking of usage of proxy in place of the reciever idocs, so that we may be able to check for duplicacy before the generation of the idocs.
>
> Is this a feasible solution?
Yes, this is a feasible solution, when you know to program this in ABAP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am curious as to whether you are getting duplicate idocs all the time or is it occasional? Multiple duplicates or just single duplicates?
If it is occasional and just a single duplicate, depending on the application document that is posted, the IDOCs could be rejected. Unless your application has no means of identifying the duplicate? or you can code some logic in the customer exit to reject the duplicates?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kris,
We are having duplicates generated occasionally.
And the duplicate Idocs are landing up in error in the R/3 system, this is what the client does not want. Meaning the client would not like to see idocs in this kind of an error (duplicacy) in the system.
Thanks to all experts for their suggestions.
Regards,
Diptee
Hi,
Do you have a message mapping for converting HTML to IDOC?
If yes you can use RFC lookup function to check if the entries are already present in SAP tables or not.
It entries are present then you can raise and exceptiona and fail the messages in PI so that it doesnt reach SAP system.
Regards,
Deepak
Diptee,
>>We are thinking of usage of proxy in place of the reciever idocs, so that we may be able to check for duplicacy before the >>generation of the idocs. Is this a feasible solution?
As the expert Stefan mentioned it is possible, You can maintain a temp table and verify the duplicate values then you can go ahead and post it with help of ABAP prg
Thanks
Agasthuri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is this a feasible solution? Any alternatives to this are also welcome.
Yes, Proxy is the best choice and it will perfom better than Idocs.
Plus, We have flexibility to check for duplicacies that would avoid confusions and keep your inteface simple and elegant.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, this solution can help you while posting your inbound data.
As you know your Inbound ABAP program for ABAP Proxy. Do the necessary changes in that program to stop the duplicate entries.
Also you can take help of Custom ABAP Table for checking duplicate IDoc Entry.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.