Question:
Hi friends.
I have run into a problem while changing standard code for va22 transaction. To explain the problem I have listed the steps involved.
Go to va22.
Enter a quotation number(VBAP-VBELN) and press enter.
We go to a screen with all the item details for the quotation number.
Select an item number and go to the item details configuration to see the characteristics. Just click on the bottom right most button to go to this screen.
This screen will contain the various characteristics for the item.
I want to know the flow from the quotation to the characteristics.
The characteristics are stored in the table 'CAWNT'.
It would be great if someone could help me with this problem.
Thanks a lot
Pavan.
Answer:
1. switch on the SQL trace (incl. buffer trace if appropriate)
2. Start your transaction
3. switch of SQL trace.
4. View the trace list.
5. locate the SELECT statement.
6. Double-klick.
7. set a dynamic break-point.
8. restart the transaction
9. in debugger, have a look at the SELECT statement and which variables have been passed in the WHERE clause. If necessary, examine the ABAP call stack.
Answer:
Hi friends.
I have run into a problem while changing standard code for va22 transaction. To explain the problem I have listed the steps involved.
Did I read it correctly? Changing standard code? Isn't it a BIG NO NO?
Answer:
Hi friends.
I have run into a problem while changing standard code for va22 transaction. To explain the problem I have listed the steps involved.
Did I read it correctly? Changing standard code? Isn't it a BIG NO NO?
What i meant was actually adding to the logic or in other words using a user exit.
Thanks.
pavan kumar reddy
Answer:
Hi friends.
I have run into a problem while changing standard code for va22 transaction. To explain the problem I have listed the steps involved.
Did I read it correctly? Changing standard code? Isn't it a BIG NO NO?
Still better than creating n copies in the customer name space.
Answer:
I would add to guest's list 1 .. 9 another one; as a standard transaction may access a lot of tables you may have to reduce the list of candidates. The wood is there, but there's a lot of trees in the way. Or the other way round.
Anyway, either examine the table structures (in some cases you will know by common sense that the table must contain X and Y as keys and Z as the 'result'). Alternatively, start with a known example (your functional consultant should be able to provide one) and use SE16 plus a bit of trial and error to try and find recognisable data.
Oh, and finally a tip for those who think in the longer term (so anyone from Hampshire can ignore this section):
Some of the ones you find might not be the ones you need for this program, but who knows about the next one? If you're likely to be working in the same functional area, keep notes.
_________________
First he pinches my sig, Now he's cribbing my posts too!