cancel
Showing results for 
Search instead for 
Did you mean: 

config for Number Ranges ? :-(

diegohs
Active Participant
0 Kudos

Hi guys,

Question for SRM gurus 😃

I have the extended scenario working fine. Now I need to switch to the classic scenario.

I have problems with number ranges, the system is burning 2 numbers per every Shopping Cart.

I realized that the number range configuration isn't clear at all for me.

Could you share which are the steps / example values for this configuration ?

Thank you !

Regards from Mexico 😃

Diego

Accepted Solutions (1)

Accepted Solutions (1)

yann_bouillut
Active Contributor
0 Kudos

Hi Diego,

What the problem with "burning 2 numbers per SC" ?

You should have enough numbers in your number range ?

The system is buffering more than one number even if less SC are created.

Kind regards,

Yann

Message was edited by: Yann Bouillut

yann_bouillut
Active Contributor
0 Kudos

Hi Diego,

You can change the buffering in transaction SNRO.

For example you can define that no buffering should happens.

Kind regards,

Yann

diegohs
Active Participant
0 Kudos

Hi Yann, whats up...

Well.. EBP creates the Shopping Cart 8000000021, and R3 receive the document 8000000022. =(

So, the new SC in EBP is: 8000000023 and it goes to R3 with number: 8000000024.

Obviously, I have something wrong in my configuration.

Could you give me a brief explanation about number ranges configuration ? (example values).

Or, do you have a document about these steps ?

Mille fois merci

Regards,

Diego

yann_bouillut
Active Contributor
0 Kudos

Hi Diego,

SC number has nothing to do with PR or PO number range.

It is not because your SC has number 8000000021 that your PR or PO should have the same number...

What is important is that the SRM number range for PR and PO should be the same in R/3.

SRM is picking the number in SRM and put it into the PR or PO bapi.

Thus it is a push method from SRM to R/3.

SRM is not reading dynamically R/3 number range !

Kind regards,

Yann

Message was edited by: Yann Bouillut

diegohs
Active Participant
0 Kudos

Hi Yann,

Thats exactly my problem. I dont understand well all this things.

My need is I need the classic scenario: Create a SC in SRM and then create a PR in R3 and continue the entire process in R3.

What should I do ? I have searched info (explanations) about this, but with no success =(

I understand this is a boring thing =( but Im really confused =( So, I would appreciate any help !!!

Diego

yann_bouillut
Active Contributor
0 Kudos

Hi Diego,

You have to define Number Ranges for Shopping Carts and Follow-on Documents :

for example :

01 1000000000 to 1999999999

PO 7000000000 to 7999999999

PR 8000000000 to 8999999999

PR and PO number range defined here (internal) should be the same in R/3 (external)

kind regards,

Yann

diegohs
Active Participant
0 Kudos

Hi Yann, so:

1. SC range number is not related with PO or PR range numbers 😃

2. I define these number ranges:}

01 1000000000 to 1999999999

PO 7000000000 to 7999999999

PR 8000000000 to 8999999999

3. What about Transaction Types ? Im confused about BUS2121 (classic scenario) and BUSS2201 (2201 for extended scenario). What should I put here in order to match my new Number Ranges ?

4. After point 3, I think I just need to update my number ranges in R3 as external and that's all.. right ?

Regards !

Diego

yann_bouillut
Active Contributor
0 Kudos

Hi Diego,

3- Transaction type is your document type : for example "EC".

It is the R/3 document type attached to your PR or PO number range.

This transaction type "EC" should be linked with your internal PO number range "PO".

4- yes

Hope this helps,

Kind regards,

Yann

diegohs
Active Participant
0 Kudos

Ey Yann..

I made the activities you suggested, but:

1. My Shopping Cart is created and authorized without any problem (with range number: 1000....)

2. Nothing happens after that... the SC status says "Authorized" but I dont have any other following document. SC says authorized and I dont have any error (administrator's monitor).

So, I dont have any error and its not working =(

How can I "debug" the SC transfer to R3 ?

Thank you !

Regards,

Diego

yann_bouillut
Active Contributor
0 Kudos

Hi Diego,

It is so easy when you are in front of the IMG and so tricky sometimes when you try to help remotely )

first go to BBP_PD to see if any PO number was assigned to your SC.

If yes, is is from the good number range ?

Please make sure that :

- document type is also the one you have in atribute BSA (prefixed by the backend logical system)

- R/3 and SRM PR and PO numbee range are the same AND that you start with a number that was not already used in your previous ECS PO !

- PR and PO number range in R/3 should be copied from "NB" :

Example : copy NB to EC type (copy all entries)

At this step, you have to set the external number of your PR (or PO) number range you use in R/3

Resume :

"EC" type should be the same as your transaction type in EBP and BSA attribute value.

Path : Materials Management -> Purchasing -> Purchase Order -> Define Number Ranges

-> ZZ 700000000 to 79999999 and flagged as external

Path : Materials Management -> Purchasing -> Purchase Order -> Define Document Types

-> copy of NB to EC types for example

and ZZ entered in "nb mg ext" field

Kind regards,

Yann

Message was edited by: Yann Bouillut

Message was edited by: Yann Bouillut

Message was edited by: Yann Bouillut

diegohs
Active Participant
0 Kudos

Hi Yann,

I followed your instructions ,in BBP_PD I have the following information:

Transfer:

LogSys EntryDate EntryTime DocType CoreKey

R3QCLNT200 26.04.2006 09:54:37 RQ 2000000000

I dont know why the DocType = RQ =( It should be PR, not RQ. I checked all my config but I cant find whats going on.

Do you have any idea about this ?

Thank you !!!

Diego

yann_bouillut
Active Contributor
0 Kudos

Hi Diego,

1- check that RQ is not present in the SRM org structure, transaction type or in front of any SRM number range as RQ is the SAP default one for Purchase Requisition.

You certainly have this number range's number in your SRM customizing.

Kind regards,

Yann

diegohs
Active Participant
0 Kudos

Hi Yann,

Finally it worked 😃

Thanks so much for your help 😃 *(to all of you)

Regards,

Diego

Answers (0)