Confirmation done in EBP but SES not generated in backend

[former_member229388]

Hello Team,

Below is the scenarion (SRM 4.0 Classic)

1. Number of confirmation have been done for Limit SC

2. Some confirmation successfully generated SES(Service Entry Sheets) in backend

3. While few confirmations have not successfully generated SES in backend.

Can anyone advise what is the issue and how it can be traced / resolved...

Thanks,

Dhananjay

[Former Member]

just pass the GUID to BBP_PD_PROCDOC_TRANSFER in debug mode and see whats going wrong.

[Former Member]

Hi Dhananjay,

Are these confirmations posted to ECC via IDOCS? If so, can you check where these IDOCS are failing?

Regards,

Nikhil

[former_member229388]

Hello Nikhil,

Thanks for your response.

But the in this case, as its a Limit Service SC, Confirmation in EBP would be transferred as SES in backend via RFC.

Hence we can not find IDOCs etc....

Is there any way/ FM by which we can push these Confirmation to Backend again so that SES would be generated in backend.

Thanks,

Dhananjay

[former_member229388]

Hello All,

I found the FM: BBP_PD_CONF_TRANSFER_V2 which might be usefull in this case.

We need to pass GUID and IV_Action.

I have found GUID. But what is IV_Action? What value should be passed in this case?

Thanks,

Dhananjay

[Former Member]

Hi Dhananjay,

Can you try passing 'X' for IV_Action?

Also are you very sure that no IDOCS will be generated?

Regards,

Nikhil

[former_member229388]

Hello Nikhil,

Correct me if I am wrong.

In this case the confirmation in EBP is for Services, and hence in backend SES would get generated, and once this SES is approved/accepted, GR would get posted automatically.

Also, the confirmations, which are successful, I am not able to find any IDOCs.

I believe the SES is getting created via RFC.

Pls help me know, in this case can I make use of this FM BBP_PD_CONF_TRANSFER_V2?

Thanks,

DHananjay

[Former Member]

Hi,

BBP_PD_CONF_TRANSFER_V2 is usually used when you need to transfer failed IDOCS (of confirmation). These failed IDOCS are tracked under WE02/05.

Regards,

Nikhil