on 06-05-2007 12:57 AM
hai friends,
1)
can some body explore me on why we use in determination pricing the condition type
if u take standards we say sales areadoc ppcuc ppp roceduc.type
why we use condition type ..with out condiotion type it works...
2)how u work returns in systems...customer took goods and returned to u ..how u do the config in system...
3) WHAT CUSTOMISATION WE DO IN PRICING....if we say we copied rvaa01...in interview they are saying for copying u r paid for are what?kindly explore the scenario of how to customize pricing....
4)what is functional spec?
5)how many types pricing procedures u r company is having.....
6)you are saying u have not worked in CIN so how u configured u r pricing?have u configured with out TAX?
6)what is transaction variant?
kindly explore me these ......
****very urgent*******
sent mail ...
REWARD if its helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1. its not compolsory to have price there keep anything there.. conditiontype.. we kkep PR00 bcoz its famaous.. order starts with Pr00...
2. separte doc type.. Re and item cat. REN, Schedule line cayt. D0. and delievry doc. LR, and item cat. REn, and billing doc. F2... you can have same pricieng procedure... or u can create sepater priocing procedure..
3. we do lot of changes in pricing, like it all depends on cleint requiremnts and bisuness... No company will copy form RVAA01. they treat as standard.
4. function spec we give to ABApers for a change or new development..
5. it depends on client... you can say if its a indian company with 300 crs. 8 - 10 ....
6. Transcation variant is where we can surpress and make mandatory feilds in all the screens like in VA01 you want P.O mandatory.. goto SDHO and select the T.code make mandatory...
Reward if it helps
ramki
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Functional spec:--
The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made.
Transaction variant:--
Transaction variants:--
What you can do with a transaction variant
Insert default values into fields
Change the ready for input status for fields
Hide various screen elements, menu functions or entire screens
Adjust table control settings
Note: Transaction variants can only be used with dialog transactions.
How to create a transaction variant
Transaction variants are created with transaction: SHD0
In the field Transaction on SHD0 enter the transactioncode for the screen you want tpo modify (E.g.
VA03)
In the field Variant on SHD0 enter the name you want to give the transaction variant (E.g. ZVA03)
Press Create
Now the screen for the transaction is shown and you can enter default values in the fields of the
screen
Press Enter. Now a screen that enbles you to make further customizing (Hide, Output only, Invisible,
Mandatory) if the screen fields is shown.
After you have finished customizing the screen press Enter to go to the next screen or ave and exit
to save the Transaction variant. Finally you assigned to sales document type through VoV8.
To run the transaction varian, you must create a new Transaction code in SE93 that referes to the
Transaction variant. Choose Transaction with variant as Start object.
Reward points if u helpful
Cheers
Govind.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hai guys this is vijay and new to this forum. coming to the rajus question
1: what is pricing procedure determination
RVAA01 is the default pricing procedure given by sap ag
for every company on the material that is manufactured r sold there shud be a price determined which is based on many factors like discount, frieght, taxes, which r again dependent on other things like place, rules many at the end of which we wud be profitable. the reason why we shud determine our own pricing procedure for the company.
RVAA01 is the pricing procedure under which we have
condition type separately for pricing (pr00), discount ( k007), freight(kf00).....
under which we have
access sequence where we define the settings
under which we have
condition table burnt taking the field catalogs as we wanted like how the price shud change (price change district to district r only state to state depending on out business..)
field catalogs are for example if the price changes district to district then field catalogs wud be
sales org
distribution channel
division
counntry
region
district
thats 1% of how wat pricing procedure in the same way we have to do for discount , tax, all the rules we wish to in combine totally becomes pricing procedure of a company r pricing policy of a company
regarding other things u have asked for i havent r partially only understood the issues.sorry
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hai,
1. condition type:
in sap pricing is based on condition technique, so when system gets the pricing procedure from the sales area + cupp+dopp-- it looks in the pricing procedure
that some condition types have been maintained, condition types are notheing but
some aspects of pricing which we see in our daily life, ex: price,discount,surcharges,taxes,etc ,without which we cant do any thing ,we cant configure a price ,without a condition type.
2. in returns , pricing if u use a seperate pricing procedure,it does not contain any discounts,we are just taking back our goods, excise gets affected(NOT SURE,CHECK)
3.FUNCTIONAL SPECIFICATION:
it is what u give to a abaper , if u want to add certain fields,remove certain fields,
whatever coding u want to happen with the abaper,functional spec is being raised and forwarded to him,giving all specification.
4.types of pricing procedures used:
u can say suppose u have following distribution channelsin your company
1. exports 2. distributors 3.dealers 4. government bodies.
u can say that for each distribution channel we have one pricing procedure,
because the basic price,the discounts given differ.
it is better to have a fair knowledge aboout CIN.
rewards points if helpful.
regards
sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
8 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.