cancel
Showing results for 
Search instead for 
Did you mean: 

PDP - Error determining follow on Doc

Former Member
0 Kudos

Dear SRM Gurus,

while implementing PDP (SRM 4.0; Classic) we are getting an error for creating a PO. The PO is supposed to be a classic one, but the system gives the message "error in determining follow on doc in backend". I assume something is missing with the number ranges.

Any ideas?

We are using the same transaction type EC like the one for operational procurement. Or is it mandatory to use the ECDP code?

Could some of you give some insights?

Many thanks,

Claudia

Accepted Solutions (1)

Accepted Solutions (1)

yann_bouillut
Active Contributor
0 Kudos

Hi Claudia,

I have activated the PDP scenario and do not use the ECDP code

We use the same transaction type, number range as for operational procurement (ECS scenario).

Kind regards,

Yann

Former Member
0 Kudos

Hi Yann,

thanks for feedback!

The differences to your scenario is ECS and CS.

PDP is supposed to work in CS as well, but it seems something is missing.

Classic POs are working fine out of Sourcing Cockpit, only the PDP PO are resisting. Any idea?

Many thanks,

Claudia

yann_bouillut
Active Contributor
0 Kudos

Hi Claudia,

Could you please confirm the following points :

1- In case of PDP, your customizing does not create local PO instead of classic PO.

2- your SC is NOT incomplete and SRm system is not trying to create a PR in your backend .

Kind regards,

Yann

Former Member
0 Kudos

Hi Yann,

yes, settings are done in the way to create classic PO. Also the SC is complete. I am able successfully create a Classic PO with the same material, category etc. based on a SRM SC out of Sourcing Cockpit. Hm? Any idea?

Many thanks,

Claudia

Answers (1)

Answers (1)

Former Member
0 Kudos

Dear Claudia,

Did you solve this PDP issue.

We are facing the same problem. Your help will be highly appreciated.

Thanks and Regards,

Anil Rajpal.

Former Member
0 Kudos

Nope, not yet.

I am wondering, if the document type ECDP is mandatory? It should not, but in the SRM world you never know.

Does anybody in the group have any further insights into that?

Many thanks,

Claudia