Sap Sale Module: RE:[sap-log-sd] VA02 - Need Access to Sales Document Already Created

Posted by Typewriter
on Jul 12 at 9:29 AM

Hi Walt,

First, lets take a step back in order to understand "Number range & Sales orders #" -
(maybe some things here are obvious, but needed for clear explaining)

a) Every sales order needs an identification #. Therefore SAP has given a concept of "Number range" and assignment of this number range to Sales document type.

b) System can generate number for a sales order - This is internal number
User can choose a number for a sales order - This is called external number
For doing the configuration for this, one has to go to VOV8 and then in your Sales doc type fill in whether external or internal and then the number range (e.g. 01, 02 etc.)

c) If you have filled in both external and internal number ranges, system shall give ONE # per sales order.
So sales order can have 8186 or 5000003. NOT both numbers for the same sales order, not in standard functionality.
If user types in 5000003 in VA01, then after saving the sales order has this number. If user keeps number blank, when pressing save, number range shall appear at the bottom of the screen.

d) (your Question 3) The choice of external or internal depends upon business requirements and then appropriate configuration would have to be done in VOV8 and VN01.

Your Q2 - Check for your sales doc type in VOV8, field "No. range int. assigt." does this have a number range?

Your Q1 - Check in the sales order, for that line item, in Tab Conditions, click Analysis. Go to condition type MWST and see what is the message. Understand why there was no message. And please us know.

General suggestion - In test envt. create a new Sales doc type, copy of OR. Check the 2 fields with number ranges.

Create 5 sales orders with internal number range and 5 sales order with external number ranges and "observe" the numbers in VN01, in VA02; things shall become clearer.

Regards,
Typewriter

---------------Original Message---------------
From: Walt Woo
Sent: Monday, July 11, 2011 7:09 PM
Subject: VA02 - Need Access to Sales Document Already Created

Hi Typewriter,

Thank you for your solutions road map and your good own and recommended testing sequence in your SAP system indicated in your email below.

I am now able to answer your questions in the numbered sequence below in your email. I got a little tied up this morning at work.

A) In TC VA03 I checked for sales order 5000002. For the first TC VA03 that I used, I used as my inputs, sales order = 5000002, sold-to party = 100096, and PO = PO-112. Likewise, for the second TC VA03, I used as my inputs sales order = 8165, sold-to party = 100096, and PO = PO-112. Both VA03 views displayed the SAME sales order data, so I assume it's the same sales order, since both times VA03 displayed " document" field = 8165 . There was no field in the display that displayed the document data value 5000002 for VA03, ether via entering sales order (as an input field, along with sold-to party and PO #) = 5000002 or entering sales order (as an input field) = 8185.

On this occasion for the first time , I first got displays of tabbed data fields (for me to update as needed I assume), such as tabs for a) Sales tab, b) Billing tab, and c) Accounting tab, d) Conditions tab, and e) Assignment tab, to name several. I entered some data, and then saved the sales order 5000002. I first got the only error message "Legal Control: Issue Error Log - Item" for document # 8185" for my material (Nokia phones), then went into material master via TC MM02 for Nokia to supply the missing data needed for the Legal Control section, and then went back to VA02 to save it with no errors this time. The order = 5000002 is now is in open status, which I have not seen before in the earlier sales order 5000001 due to the previous and still existing errors I was receiving . Condition type PR00 appeared as well for 5000002 as I expected it to appear . This time I also did not get the error for the condition MWST that I received previously in 5000001. I checked in MM02 for Nokia that MWST output tax was still set for zero tax (i.e. no taxes). I did not change the pricing procedure for 8165 - it is same as for 8164 The plant TABA also appeared in VA02 for sales order 5000002 , it did not for 5000001 (I could not enter the plant in the header portion of both sales orders , but I entered the plant in the detailed material portion at the bottom of the screen for VA02 for sales order 5000002. Also the SP, BP, PY and SH parties were also all populated already for 5000002 .

It would seem that it would take some more practice to create partner determination procedure ZEGT customized customer groups (ZEG1, ZEG2, and different address for PY customer account group from the other customer account groups for the same customer, a sales representative customer account group, etc.) properly, as I would need for sales order = 5000001. The relationships between partners are more complex, and this is my main lesson learned.

Q1 - Why did I not get the MWST error message this time? You must have anticipated that this error would not re-appear in sales order 5000002 per your email below.

Then I created another sales order with VA01 with inputted fields sales order = 5000003, sold-to party = 100096, and PO = PO-113. I then via VA02 accessed the sales order with the inputs sales order = 5000003, sold-to party = 100096, and PO = PO-113, but as of this morning, the number 8166 did not appear via the TC VN01. The last sequence # shown via VN01 was still 8165. Therefore I could not use sales order = 8186 to access this newly created sales order 5000003 via VA02 or VA03. (I will check for it later tonight and the next couple of days and let you know.)

Q2. It also appears that I cannot create a new sales order with an internal sales order number (I attempted to without success), but I can access a sales document with an internal sales order number via VA02 and VA03, once the internal sales number is later generated and is made available by SAP. Does this description describe the situation correctly?

Q3 - Is it necessary to create a user exit for the number range for each and every SD implementation? Is the reason largely because the internal number and external numbers need to be synchronized (it seems like the problem is a timing issue when making the NEXT internal number available)? Which number should be used by (or preferred by) the end user, the external number or internal number, or should both be available to the end user?

Thank you.

Walt

__.____._