Replication of SRM PO to ECC

[Former Member]

Hi ,

In my case, SRM PO is not replicating to ECC.In BBP_PD message is displayed as

" Type conflict when calling a function module.

BBP_PD_PO_TRANSFER_EXEC (Transfer Failed (E.Sys.) "

When I checked in transaction message is displayed as

" Purc: method BBP_ANALYZE_PO_APPLIC is not released"It displays that class for this method is 'BBP_PO_APPLIC'.

But I am not able to find such class or method present in SRM system.

I am using SRM with extended classic scenario.

Please advice.

Regards,

Amit R.

[Former Member]

Dear Amit,

I am also facing the same issue while posting PO to ECC6.0.

System shows error asPurc: method/ BBP_ANALYZE_PO_APPLIC is not released.

Please let me know what you have done in R/3 to fix this issue.Ours is SRM4.0 Extended Classic Scenario.

Your urgent help is requested.

Regards

Bhupendra

[Former Member]

Hi,

In my case,I found some short dump in backend while replicating PO to ECC. I fixed and rectified the cause behind the short-dump in ECC.

Regards,

Amit

[Former Member]

Hi Amit,

Can you let us know the dump type your were getting?

Regards,

[Former Member]

Hi Guru,

When I am trying to replicate the SRM(3.0 SP11),ECS PO to R/3 (ECC 6.0), getting the same error in RZ20 "YSQ\Business to Business Procurement(250)\...\Purc: method BBP_ANALYZE_PO_APPLIC is not released".

Whereas I am not getting any dump in EBP or ECC also when executing the FM BBP_PD_PO_TRANSFER_EXEC and checking RZ20, getting following error

"YSQ\Business to Business Procurement(250)\...\Purc: method BBP_ANALYZE_PO_APPLIC is not released"

Please advice.

Regards,

Gopesh

[Former Member]

Did you resolve this? If you resolved your issues please indicate how.

I have an alert message indicating": Error in ABAP statement when processing an internal table. table."

This is happening when a limit item PO is transfered from SRM to the backend

When I click on the message I get the "BBP_ANALYZE_PO_APPLIC is not released" message

Thanks

Jamz

[Former Member]

Hi James,

I found some short dump in backend while replicating PO to ECC. I fixed and rectified the cause behind the short-dump in ECC.

Regards,

Amit