cancel
Showing results for 
Search instead for 
Did you mean: 

Partner numbers 'gaps' (leaps)

BGarcia
Active Contributor
0 Kudos

Hello everyone,

We're creating business partners in CRM. For that, we've configured 'grouping' field to be available at partner creation view at webUI, so users may be able to select the desired partner number range (internal).

After they select the desired numbering 'grouping', and press <enter> key, a number is automatically assigned to current business partner, that was not yet saved at database. Then, if they press 'cancel' button , and repeat the process all over again, a new number (one more that previous one) is assigned to new business partner in memory.

By doing that many times a day, it will cause several gaps (number leaps) in partner numeration. In previous versions, with BP t-code, we could de-activate number buffering at t-code SNRO to maintan number consistency, but in these new environemnt that is no more a solution.

Did anyone dealed with this situation? If so, did you get a solution/workaround for that?

Thanks in advance.

Kind regards,

Garcia

Accepted Solutions (1)

Accepted Solutions (1)

prasenjit_sharma
Active Contributor
0 Kudos

I vaguely remember an option to disable the 'Early no Assignment' check-box in SPRO. You may try that.

Regards

Prasenjit

BGarcia
Active Contributor
0 Kudos

Hi Prasenjit,

Thanks for your reply, but unfortunately I can only see that option for transactions

Kind regards,

Garcia

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Stephan and Garcia,

We are using CRM 7.0 and Iam seeing the same issue (EARLY Number assignment for CONTACTS before SAVING ) in DEV and QA.

Whereas in PRD client its perfect(system is assigning Number upon saving of the contact)

Any suggestion on this please.

Regards

BABU.

BGarcia
Active Contributor
0 Kudos

Thread closed without solution.

After contacting SAP Support, I was told that application is working as design, and nothing can be done.

So, my solution will be returning to old BP transaction code, or do some developing to 'workaround' the issue.

I feel so disappointed with this

stephenjohannes
Active Contributor
0 Kudos

Just to add my comments, SAP is correct in this situation.

Number ranges are not designed to provide "continous numbering", instead they are designed to prevent duplication of numbers. If you restart your CRM system, you automatically cause the number range buffer to be "refreshed" and introduce a so called gap.

Most applications work in this fashion, the problem in your case is that the business partner assigns the number early due to how the application is structured. The real question is why do you have business requirement that requires perfect numbering? Is there a concern about running out of numbers or are you putting some type of intelligence into the numbers which is not recommmended.

Did you provide SAP with your business scenario, or just that the system should number perfectly?

Take care,

Stephen

BGarcia
Active Contributor
0 Kudos

Hi there!

I accept your opinion, but I don't feel that it is right to leave away the 'continuous numbering' issue.

Note 504875, explains how to de-activate the number buffering so that is possible to have a continuous numbering, and this is not working in the new WebUI version. But it works on BP transaction, that we used in last years.

I cannot consider it such a law or legal business requirement, but the account management was organized in this way over the past years. And now that we're upgrading to the 7.0 version and we're supposed to leave the BP transaction behind, well... we just didn't expected to find a problem here. And also didn't expected that this was considered normal...

We can create documents without gaps in CRM webUI, in CRM GUI or in R3 GUI, by manipulating number range buffer.

We can also create partners without gaps on CRM GUI or R3 GUI, but not in WebUI.

I just don't feel that it's correct this way...

Thanks for your reply Stephen,

Kind regards,

Garcia

stephenjohannes
Active Contributor
0 Kudos

Garcia,

The reason why I really asked about the business case, is that normally if you want changes made to SAP software there needs to be more than a technical reason in the application to change the process.

Personally since I never heard of a business case for your requirement, I thought it would be interesting to find out why and then suggest you put it out on idea place(I would even vote for it). However it's hard to justify a change when the reason is that's how it always worked. Part of the understanding when you do an upgrade is that the system may change in how things function and things that were there before, may no longer be available.

My best example of this is that the favorites functionality available in the PCUI was removed when SAP introduced the CRM Webclient UI. After some lobbying/complaints SAP re-introduced this functionality back into SAP CRM 7.0EHP1. Now there was no logical reason not to have favorites in the webclient UI especially in CRM 7.0, but it was removed. I think your situation is similar, and in order to get it changed, you need to show/build support to why this feature would be critical to a broad group of CRM customers.

So I understand where you are coming from in this situation, and if you need any more ideas on how to perhaps ask SAP to put this option in 7.0 EHP2 :).

Take care,

Stephen

BGarcia
Active Contributor
0 Kudos

Hi Stephen,

I've follow your suggestion and submit this issue at SAP idea place

So, I invite everyone who agree and desire a 'early number assingment' switch off, for business partners, to vote at:

https://ideas.sap.com/ideas/1081

Thanks and kind regards from a sunny day at Lisbon,

Garcia

stephenjohannes
Active Contributor
0 Kudos

Garcia,

You have my vote.

Take care,

Stephen