on 01-02-2014 6:49 AM
Dear experts,
I have a requirement of report , where customer want report of condition type.
Description-
select condition type. for ex- zpr0
which pricing procedure are using this condition
which sales organizations are using this pricing procedure.
Based on condition type parameters.
1) if manual condition- which sales org using this condition & in which documents.
2) if access sequence- which condition tables used .
result a list condition table,& no. of usages per sales org.ie. in pricing ,master data.& no. of usage in sales docs.
for this requirement as per my understanding i need to create a qwery withan Abaper .
and i need to join konp & konv .
Nut can you give me any further suggestion to accomplish this report.
ie. more table/structure.
Thanks in advance
Hi Jitesh
For this you need to create report through ABAP or you can give it a try in Query as well using SQ02,SQ01 but for this you have to be very good and smart using additional fields in query reporting.
Apart from KONP and KONV you have to use some IMG tables as well. For example T683S will be used to check which condition type is being used in which pricing procedure. T683V will be used to get which pricing procedure is being used in which sales organization.
If there are some if conditions then I would suggest you to go for ABAP report because it will be easy to control these if and but conditions.
Let me know in case of further clarification.
Thank$
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
These are at least 4 different reports... The condition assignment to the pricing procedure - that's a configuration. Conditions being used by Sales Org - what does this mean exactly? If a pricing procedure is assigned to an order type and that order type is possible for the Sales Org, does that count?
Condition tables - it's possible to tell which ones exist but nearly impossible to tell if they're actually used. It's not stored anywhere which access sequence the price came from.
Conditions used in actual documents - the tables have already been mentioned, but those are cluster tables and can't be used in JOIN, so a simple query (SQ01) is probably out of question. Writing a custom report seems like an overkill though (unless there is some other use for it). Just guessing, but I'd assume the customer is not realy expecting to make a major investment since this seems like an exploratory item.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with you that this looks like different reports and in SQ01 query tool its near to impossible.
Since you are techno functional consultant and you know ABAP and SD very well so I think you should have logic how to make relation from condition type to access sequence, pricing procedure, sales organizations and document types. In my opinion we can get this whole information and links in one report using some IMG tables and transactional data tables. Where we define and assign conditions, pricing procedures and their assignment to sales area and determination table etc.
For getting information of condition record which system has used in some document again we can go with reverse links. From condition type we can go to access sequence > tables and then find one by one valid condition record on report selection date and where system finds valid record ignore others. It is possible if we have a smart ABAPER and I had one in my previous role and I have actually done this.
Need your expert views on this.
Thank$
MoazzaM, certainly we can reverse-engineer the whole pricing analysis but, as I said, not sure this would be the wise use of resources. I might be wrong, but based on the OP this looks like some research a company would do when attempting to revamp their pricing. We have done it in the past, but never developed custom reports for this. At most, we did record count in SE16 for the condition types in KONV. People in charge of pricing knew very well what access sequences they use, so this was just a matter of having a call with the right person (which you will need for such project anyway).
If the OP's customer has the whole team of idle ABAPers then by all means - have at it. But I somehow doubt it's the case.
Hi
You are right that this is possible but this will be misuse of resources. I have also done this and created somehow similar functionality by going reverse in pricing analysis.
I have seen two types of companies. Let me tell you this with my personal experience.
May be it'll look weird to you but there are some companies which have best SAP teams with in-house ABAPER or ABAPERs. They create every report or application in SAP and their end users are not that trained and they are just data entry operators. They can just execute reports and they need ready made things.
Other companies have different approach. They don't have big in-house SAP teams and they hire only one technical and one or two functional guys. Their end users are well trained and they can make query reports or get dumps from DB tables from SAP team and make reports in excel and analyze it.
For former these kind of requirements are normal thing and they would ask ABAPER to take his time and develop this kind of report. For latter they would not pay high cost to some ABAPER or third party company for these kind of reports and they will use SE16N technique.
Now it depends what kind of client OP has and how he can handle it. Hope you understand what I wanted to explain. Thank you for sharing your views.
Thank$
Hello Jitesh,
Your requirement will not be available in a SQ00 Query. You will have to develop a huge ABAP report for this.
Also check with your ABAPer whether all required information will be available in a single report or not.
Thanks,
Jignesh Mehta
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.