cancel
Showing results for 
Search instead for 
Did you mean: 

ECP PO# is different in backend R3

Former Member
0 Kudos

Hi experts

We are having SRM5.5 and backend ECC5.0.

Scenario : Extended classic

1. SC approved

2.PO created in SRM (with local PO# range internal)

3.PO completed and ordered in Process PO

4. PO replcated to backend R3 with different number range(maintained same number range as SRM internal PO with external checked).

Can you throw some light on this.

Am I missing anything???

Thanks in advance

Jagadish

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Jagdish,

It looks the PO range you are trying to pass from SRM its not available in backend, you can try this:

1. Change Number range in SRM PO

2. Put the same Number range in R/3 for SRM doc type - create ONLY external number range.

Regards,

Shiv

Former Member
0 Kudos

Hi Jagdish,

U need to maintain same number ranges at both the ends.Only thing is that while maintaining the document type in r/3 (which is alrady defined in srm) should be maintain as extenal number range.

And maintain the document type in your org structure also as defined in SRM.

Reward points if solution is useful to you.

regards,.

Navneet.

Former Member
0 Kudos

Maintained Internal number range in SRM trans type and same as external in R3 Doc type.

Dont understand why Internal num range is picked in R3 for ECS PO.

We have not maintained any BADI.

Any thoughts on this...???

Regards

Jagadish

yann_bouillut
Active Contributor
0 Kudos

Hi Jagadish

Did you check that your current backend <u>number</u> is available .

Maybe there was a desynchronisation between SRM and MM number range.

Kind regards,

Yann

Former Member
0 Kudos

Yann

I did not get your point.

You mean the PO number which SRM has passed is not available in backend?

Please clarify.

I have maintained same number range in SRM and Backend.

I even tried removing Int number range for backend doc type to check if system looks for Ext num range if Internal is not assigned. In that case system throws error "Internal number assignment not defined..." when processing PO in SRM.

Regards

Jagadish

yann_bouillut
Active Contributor
0 Kudos

Hi,

Very simple :

Goto TA OMH6

Here you get 3 boxes and one of them is called "status"

Select "status" and it will display the last number taken by the system meaning that if SRm is trying to send a PO number below this status number, it won't be possible.... and maybe it will take the internal number range (i will be surprised but to be checked)

Kind regards,

Yann