Rebate Agreement
1. Which agreement type I should consider, is this custmer rebate(0003), material rebate(0002) or Rebate on the basis of sales volume(0005), because here client is not offering rebate on Sales volume in rupees or dollar. He is only concerned with totat sales in kiloleter(Quantity). As per rebate agreement concern rebate is offered in percentage. Please guide me for my scenario.
If your distributors are fewer (far less than 900 materials) then you should go for only customer rebate.
2. Guide me for conditions types and scale basis for maintaining condition records.
When creating customer rebates (T:VB01) select customer rebate, there you will see a header tab: Conditions , click it add how many customers you want. For each customer you can create scale based conditions (under the heading tab :Scales).
3. Is it necesary to maintain condition record for every material and every customer defining the scale? Because in this scennario client is going for incentives scheme for each material and each customer (distrbutor).
No need to create condition record for every material if you create customer rebate.
Customer Master
How to create the customer master?
The following are the T-codes for central creation of customer master.
XD01 Create Customer (Centrally)
XD02 Change Customer (Centrally)
XD03 Display Customer (Centrally)
XD04 Customer Changes (Centrally)
XD05 Block customer (centrally)
XD06 Mark customer for deletion (centr.)
XD07 Change Customer Account Group
XD99 Customer master mass maintenance
XDN1 Maintain Number Ranges (Customer)
You need to identify various parameters within each Account group based on which the reco account is identified within the customer master.
Customer master is basically divided into 3 tabs.
- General - General master details, Juristiction codes, Region, Transportation zone, export data, etc.
- Company data - payment terms, account management, reco account, insurance etc.
- Sales data - Sales product attributes, sales office, sales group, customer pricing procedure, Cust. Statistical grp,
- Shipping data
- Billing data
- Partner functions.
You can create a customer based on 3 views:
1. For Account purpose
FD01/FD02/FD03 etc
2. Sales purpose
XD01/XD02/XD03 etc.
3. Centrally
VD01/VD02/VD03 etc.
What is the Function of item category and item category group?
Item Category determines the processing of any Item/material that we enter in a sales order and in this way it also effects the procesing of any sales doc in which it is used.
Item Category Group is one of the component which along with the Sales Doc Type, The Item Usage and Higher Level Item Category decide about the Item Category in a sales doc.
1. What is change request and task? What was your task no.? I need an example or a task no. that is being used in your project to clear few things in my mind?
2. What is your client Number in the project? Like how we have 800 for IDES?
3. Few client requirements for customer master, material master, Organization and Transactions.
4. How to restrict users for not changing some fields in T-code va02?
5. How can we delete the Sales Orders?
How can an invoices be cancelled or deleted?
1. Which agreement type I should consider, is this custmer rebate(0003), material rebate(0002) or Rebate on the basis of sales volume(0005), because here client is not offering rebate on Sales volume in rupees or dollar. He is only concerned with totat sales in kiloleter(Quantity). As per rebate agreement concern rebate is offered in percentage. Please guide me for my scenario.
If your distributors are fewer (far less than 900 materials) then you should go for only customer rebate.
2. Guide me for conditions types and scale basis for maintaining condition records.
When creating customer rebates (T:VB01) select customer rebate, there you will see a header tab: Conditions , click it add how many customers you want. For each customer you can create scale based conditions (under the heading tab :Scales).
3. Is it necesary to maintain condition record for every material and every customer defining the scale? Because in this scennario client is going for incentives scheme for each material and each customer (distrbutor).
No need to create condition record for every material if you create customer rebate.
Customer Master
How to create the customer master?
The following are the T-codes for central creation of customer master.
XD01 Create Customer (Centrally)
XD02 Change Customer (Centrally)
XD03 Display Customer (Centrally)
XD04 Customer Changes (Centrally)
XD05 Block customer (centrally)
XD06 Mark customer for deletion (centr.)
XD07 Change Customer Account Group
XD99 Customer master mass maintenance
XDN1 Maintain Number Ranges (Customer)
You need to identify various parameters within each Account group based on which the reco account is identified within the customer master.
Customer master is basically divided into 3 tabs.
- General - General master details, Juristiction codes, Region, Transportation zone, export data, etc.
- Company data - payment terms, account management, reco account, insurance etc.
- Sales data - Sales product attributes, sales office, sales group, customer pricing procedure, Cust. Statistical grp,
- Shipping data
- Billing data
- Partner functions.
You can create a customer based on 3 views:
1. For Account purpose
FD01/FD02/FD03 etc
2. Sales purpose
XD01/XD02/XD03 etc.
3. Centrally
VD01/VD02/VD03 etc.
What is the Function of item category and item category group?
Item Category determines the processing of any Item/material that we enter in a sales order and in this way it also effects the procesing of any sales doc in which it is used.
Item Category Group is one of the component which along with the Sales Doc Type, The Item Usage and Higher Level Item Category decide about the Item Category in a sales doc.
1. What is change request and task? What was your task no.? I need an example or a task no. that is being used in your project to clear few things in my mind?
The Change Request is that request when you do some thing
new in customizing or configuration in the system. The system will
automatically pop with the change request pop box , when you can give request
name as defined by the system or can give your own request name with heading of
what changes you have made while customization. The system will generate a
request number and you save it. (e.g.:- VEDK-2785467) VEDK- means the Clients
System name then followed by the system generated request number.
Now when you want to release the request you have to use the
T-code SE10 where you can see the requests under the heading modifiable or
released. Go to the modifiable option. Each request will have again an internal
request number. First you have to release the internal request and then release
the external request number. This will in turn released by the basis guys thru
the T-code SM64 in a group when all the requests are pooled from different
users.
The task which you have mentioned in your question is
nothing but the what task you have performed while customizing the client
system and the heading name which have given it for that task and generated a
request for that task.
2. What is your client Number in the project? Like how we have 800 for IDES?
Generally like IDES client, when you are in the project, the
client is also given a number called client number. So while implementing a
project The entire implementation is done under phases and in different Client
no Servers.
e.g.:-take a company called ABC which is implementing
SAP.
So the Client is given a number in the following manner by the SAP Implementers at the site
So the Client is given a number in the following manner by the SAP Implementers at the site
291- Sand Box server (Initial Testing scenarios
Server)
292- Development Sever (With client data of minimum 15 days transactions)
294- Testing Server (the scenarios developed in development server is tested here)
295- Golden Master Server (Quality cum Testing Server) - checked finally before transferring to production server
296- Production Server (where the clients live data is stored and daily business transactions are done)
292- Development Sever (With client data of minimum 15 days transactions)
294- Testing Server (the scenarios developed in development server is tested here)
295- Golden Master Server (Quality cum Testing Server) - checked finally before transferring to production server
296- Production Server (where the clients live data is stored and daily business transactions are done)
3. Few client requirements for customer master, material master, Organization and Transactions.
The client requirements may be in the form of customized
reports and queries which are supposed to be suited according to their business
process. Generally the requirements would be coming from the BPO's (Business
Process Owners) who will deputed for each module e.g.:- SD, PP QM FI) by the
client as they would be expert in their areas and module who under the business
processes as they clients Project Team members. They are whole and sole
responsible to get the implementation done and meet the requirements raised by
them and the other users from the client’s side.
Generally before starting the implementation the entire
organization structure and the organizational elements are freezed and a
skeleton structure is prepared and then along with BPO's requirements the
system is 1st configured and then the customization is started to suit the
Clients specified requirements.
Now as far as the transactions are concerned not all the
users are allowed to run all the transactions. Here the user roles are defined
as per the BPO's (i.e., the user is given authorization only to run certain
transactions depending on the levels and stages in his area of specialization
like in SD module the entry level user is only allowed to enter the data like
creation of Sales orders or delivery and billing and the next level is give the
authorization for changes to be made for that same data that is entered by the
entry level users. The next higher level -Supervisor is given a few more
transaction authorization which will be above these mentioned users)
Here the reports are segregated like Higher Management
Reports, Middle Management Reports where by again authorization is given those
heads(Head of the Depts. or the Plants heads or GM etc.,) to run certain
transactions which allow to view reports that are needed daily by the
management.
4. How to restrict users for not changing some fields in T-code va02?
There are two ways to do this:
- Make a transaction variant thru SHD0 and assign it to your sales doc. While creating the variant you can place non-changeability ticks on specific fields. Next allow those users only to work with your transaction variant but not with the original transaction.
- You could make use of user-exit FORM USEREXIT_FIELD_MODIFICATION in include MV45AFZZ (via authorization objects, which you can assign in role customizing).
The latter is more flexible but it is not feasible if you want to place restrictions to a large amount of fields.
- Make a transaction variant thru SHD0 and assign it to your sales doc. While creating the variant you can place non-changeability ticks on specific fields. Next allow those users only to work with your transaction variant but not with the original transaction.
- You could make use of user-exit FORM USEREXIT_FIELD_MODIFICATION in include MV45AFZZ (via authorization objects, which you can assign in role customizing).
The latter is more flexible but it is not feasible if you want to place restrictions to a large amount of fields.
5. How can we delete the Sales Orders?
How can an invoices be cancelled or deleted?
You can very well delete sales order using transaction VA02,
but with a constraint that no subsequent document is created against it.
Invoice can be cancelled using T cose VF11 and then you can
reverse the Goods Issue using VL09 and making the picking quantity zero in the
deivery document and delete the delivery order using VL02n . You can then
delete the sales order then.
You cannot delete an Invoice. You can only cancel it with
(VF11) if the relevant accounting document is not been generated. Ask your FI
guy to reverse the accounting doc. Only after the accounting doc is reversed
and/or deleted, you can cancel your invoice. You also need to check if any TAX
documents are generated with your Invoice. You need to reverse/delete those
documents also.
|
6. How can we know
whether the customer is one-time or regular?
One can maintain Account Group for One-time
customers. By which we can identify one-time customers.
7. What happens when you do not enter a value for a manual and mandatory condition type?
The pricing procedure will reject the
conditions in the sales order
8. Do header condition type have an access sequence?
No
9. Org structure:
Relation between Company - Sales org One-to-Many Sales Org - Plants & company vs. Plants
Company - sales org - credit control area
What are sales area and its components?
Sales area consists of Sales Organisation,
Distribution Channel and Division.
10. What are legacy systems?
The Existing system on which current system is
working, from which the current system will be migrated to SAP system
11. What is cut over strategy?
Cutover strategy depends upon how the
organizations design their data load strategies. Normally, you decide the
sequence of Data loads for Configuration settings, Master data,
Transaction data which follows whom and then you make a copy of the system as
a Production system a day before and after checking the successful data
loads, you go-live 100% or partial again depending upon organizational
setup and policies.
Cutover planning is highly site specific.
There's no thumb rule. The stock data as on the date of going live should be
correctly entered. But stock being a highly dynamic quantity, the strategy
for loading should be crystal clear. Then you have to load all the back dated
transaction on the stock. Some stock comes into your plant/storage location
as return and some stock is actually delivered to your customer through sales
orders of various kinds.
12. What are Cumulative Condition Records?
There is a field:- "condition
update" during configuration for a condition type (at v/06)... has it
anything to do with cumulative condn. Records?
13. IF you have 3 different access sequences for one condition record then in a pricing procedure in what hierarchy will you maintain the three accesses?
In Condition Records (T Code VK11), you would
be putting values to corresponding Condition Types. Now one Condition Type
can be assigned to one access sequence. In Access Sequence, you can assign
whichever tables and fields are required.
So in my opinion, you cannot have one condition record for 3 access sequences. 14. What happens in the access sequence when you put all the ticks in the exclusive field?
When you put tick in exclusive field of all
access sequences, in my opinion, it will try to get available data from the
first. Only in case, data is not available, will it move on to the next one.
15. What is meant by delivery group?
Delivery Group is basically grouping all
individual deliveries for Billing. It should have the same Ship to Party,
Shipping Point, etc.
16. What triggers the automatic creation of PR or PO in case of third party sales?
In item category we can set "automatic PO" so
that PO and PR will automatically generate after saving the order.
You never change the item category
configuration to "automatic PO". It is the schedule line
category type which triggers the automatic PR creation.
17. What are the steps that are required to include sales person as a partner function in the partner determination?
Partner function sales represenative or person responsible
these two we can add through partner funtion in partner procedure.
18. What is z transaction?
We copied standard TC or object and rename it by Z
its basically stnd name which will start from Z (User defined)
19. Can you create sales order for 40 items if the quotation is sent for 30 items?
Yes.
20. What is the importance of requirment field in access sequence?
System will not go to asscess condition type system will
reply through formula.
21. What makes the immediate delivery in cash sales?
Order type immediate delivery switch on.
|
