Removing/Deleting Errored Confirmations from SRM 5.0 EC

[Former Member]

Hi,

I would like to know how people remove or delete SRM (5.0) Confirmations that end up failing (Error in Process) in the replication process.

We have scenarios where our end users will create multiple SRM Confirmations for the same reference document if the initial one fails in the transfer process. The if they canu2019t figure out why they are failing, will resort to ML81N in the backend system to complete the process.

The end result is we have multiple SRM u2018Error in Processu2019 confirmations for the PO that we would like to remove from the SRM system.

We havenu2019t found a standard way of removing them from the system, is there a method we could use to remove/delete them?

Thanks,

Jerry

[Former Member]

Hi

Try using the FM BBP_PD_CONF_DB_DELETE_MULTI. enter the GUID's of the confirmations to be deleted.

This will delete confirmations directly from database.

R/Reddy.

[Former Member]

Hi R/Reddy,

thank you for your suggestion.

I coded up a program using the function module and it can be used to delete Confirmations.

The thing that I'm unsure of and worried about is that if I delete the errored Confirmation from the system using this low level function module I'm bypassing application business logic that maintains the document integrity.

Have you used this technique to deal with this type of a problem or are you just saying that this function module is available to delete confirmations?

If these 'Errored' confirmations didn't create any documents/transactions in the backend system and since they appear to not be associated with the PO and item in the PO Item Follow-on Documents display, then are they nothing more that a document that is stuck in limbo due to it's errored status and have no relevant value to the process?

If yes, then is that the only place that the document needs to be deleted from?

Thanks,

Jerry

[Former Member]

Hi

error in process documents will not get transferred to backend. As you said, users manually created documents in backend, you can delete the errored conf's in SRM...

If you dont want DB delete in SRM, there is a FM BBP_PROCDOC_STATUS_CHANGE (called within FM BBP_PD_CONF_STATUS_CHANGE) that will allow you to change the status to deleted, or you can use your coded program to delete.

R/Reddy