Number range "PO" does not exists *****Classic

[Former Member]

Hi Friends,

We are in SRM 5.5 and classic mode is on and we require backend PO to be created. We have replicated all data from backend and trying to create a PO (ECDP Direct Material) and when we click the create button in 'Process Pur Order' it does not allow to create a PO and gives error "No range PO does not exist". The same error is thrown while we convert an accepted Bid into a PO from Bidding engine. We have made the following settings.

• Classic mode is on.

• internal No Range "PO" created in SRM under shopping cart and follow on document.

• Defined trnsc type ECDP and assigned this no range PO to it. It is Active.

• Defined External no range "PO" in ECC B/E client with matching range. (Marked external)

• Defined Doc Type ECDP in ECC and assigned this no range to it.

• In SRM under "Define Number Ranges per Backend System for Follow-on Documents" Maintained Log Sys as ECC Backend client and "PO" in PO number range.

• Also all relavent attributes are maintained including BSA.

Is there any sttings which are missing how can we locate the problem. Any help in this would be highly appreciated.

Also post this are there any special tips for PO Creation and transfer from Bidding Engine in Classic Mode? where can I find the links?

Answers will be surely rewarded. Thanks

Hussain

[Former Member · Accepted solution]

you said

" internal No Range "PO" created in SRM under shopping cart and follow on document"

have you created internal no range for local purchase orders for SRM server

under

SRM IMG->SRM->cross applns->srm server no ranges->Define Number Range for Local Purchase Orders

this internal no range shld be assigned to the trans type ECDP

and furhter mapped as external to ECC reqd PO doc type

BR

Dinesh

[Former Member]

Any Replies to this querry?

[Former Member]

Hi,

As u are using classic scenario to create PO in R/3 with ECDP Doc type ,there is no need to maintain the below step in EBP.Remove the below step and try it again.

Defined trnsc type ECDP and assigned this no range PO to it. It is Active.

Remaining steps what u have done are correct.

V.Nanaji.

[Former Member]

Hi all,

Thanks for your interest in this issue.

We finally resolved that ECDP cannot be used to create a backend PO even in classic.

The Direct material scenario in SRM assumes that the follow on PO will always be a local PO and NOT a Backend PO, whereas in case of Indirect material (ECPO) the PO can be a Backend PO.

Hence when we tried to create ECDP it will try to create a local PO and search for a local number range. Which is similar to extended classic.

We achieved a different turnaround to create a Backend PO even in case of direct material with a seperate enhancement.

Regards

Hussain

[Former Member]

Hi,

could you share your experiance with your seperate enhancement with SDN?

Cheers,

Claudia

[Former Member]

Hi Hussain,

Could you share what type of enhancement you have done to solve this problem, because I am also facing similer type of problem. I want to create create PO in R/3 for direct materials also.

Thanx in advance

Moon

[Former Member]

Hi Guys,

appologies to reply late. Actually the resolution is taken from the SDN itself with little changes.

What we resolved is to fool the system by passing an ACC with a dummy cost centre.

use ECC BADI u2018BBP_BADI_EXTREQ_OUTu2019 to assign a standard ACC but with a dummy cost centre.

the SRM process for direct material is hardcoded hence this converts the direct procurement into indirect. The SRM SHC will contain the cost assignment tab.

Now when you process this document and generate a PO the document type should be ECPO and then it will pick up the number range defined under "Shopping Cart and follow-on documents".

**For a Direct Material system is hardcoded to look for a local number range irrespective of your scenario.

Now while creating a PO from SRM use BADI BBP_CREATE_BE_PO_NEW to check if the dummy cost centre exists then remove the CC and the ACC before creating the backend PO. The ECC PO will be that of direct material type.

Thanks

Hussain

[Former Member]

I mean the backend purchasing group responsible is ticked and extended scenario is NOT ticked.

Is this tick "backend purchasing group responsible" has anything to do with the Classic mode? Can it be used as ticked in classic mode?

Kindly help

Hussain

[Former Member]

Yes,

This setting is Maintained correctly.

Hussain

[Former Member]

Hi Dinesh,

As per my understanding in Classic mode we do not require Local PO and in this scenario you have to maintain the PO number range under the no range for SC and follow on document only.

If we define the number range under Local PO it creates local PO which gets transfered to ECC as display only, that means the system behaves as Extended Classic even when Exended Classic is NOT ticked. (*Strange*). We have tried this scenario it doesnt help our cause.

Let me know if you have some other view or solution upon this.

Thanks

Hussain

[Former Member]

while setting 'classic' mode (or switching off ECS)

have you also flagged "Backend purch grps responcible"

BR

Dinesh