topic Re: Resequence POSNR in Application Development and Automation Discussions

Resequence POSNR

Former Member — Tue, 25 Oct 2011 11:32:09 GMT

Im not sure that this is even an ABAP problem anymore but its unlikely not to have been an issue for others.

The user creates a requirement via CO01. The corresponding item and its BOM appear in RESB. Typically a BOM can have over 3000 components.

A change is made to the BOM and SAP rebuilds it. So far, so good. Here's the rub : The new BOM is created under the reservation number in RESB but the POSNR sequence starts where the copied BOM left off. So if the earlier BOM ended with POSNR = 3122, the replacement will start with 3123.

The issue is that POSNR is not big enough. Too many changes and the program dumps.

There are plenty of views for RESB and many FMs available to change RESB. BUT, becasue the reservation is created automaticlly, MB22 cant touch it and neither can any FMs.

I dont think ABAP is going to solve this anyway. Any suggestions?

Re: Resequence POSNR

eduardo_hinojosa — Tue, 25 Oct 2011 13:40:31 GMT

I'm not sure about your requirement. Does the dump happens when you try to do a re-explosion of the new BOM? If the answer is no, try to do it with tcode CO02 and in menu path go to fucntions / read PP master data and in BOM try the option new BOM and the date for explosion.

I hope this helps you

Regards

Eduardo

Re: Resequence POSNR

Jelena_Perfiljeva — Tue, 25 Oct 2011 17:08:26 GMT

Assuming that this is how it works due to SAP's design or configuration or business process, I do agree that ABAP is not a solution here. I'd suggest to ask in SD forum (might want to use a different subject) and, since there is a dump created, search for SAP notes and possibly send a message to SAP.

Hypothetically there are user exits in SD that could be used to avoid dumps and prompt to create a new order if the number of lines exceeds certain threshold, but this wouldn't really solve the issue.

Re: Resequence POSNR

Former Member — Tue, 29 Nov 2011 15:24:26 GMT

This is a problem in SAP. There are a number of SAP Notes that might apply. These are :

98893 : SAPSQL_ARRAY_DUPREC in table RESB

131904 : Problem when assigning many components to a network order.

This one has gone back to SAP.

I will post here when we get some feedback. Thanks for your comments.