Your Ad Here
Showing newest posts with label Scenarios. Show older posts
Showing newest posts with label Scenarios. Show older posts
Monday, September 10, 2007
SD - Q and A
Org Structure
In R/3 you can represent a company’s structure by defining and assigning corporate
structure elements. What is the purpose of doing that?
Enterprise organization diagram. Chart showing the organizational structure of an enterprise, its
organization units and how they are related. A combined structure can be created from the point
of view of accounting, MM, SD. This structure forms a framework in which all business
transactions can be processed.
Which three organizational elements make up a sales area and briefly explain their
function?
Sales organization: An organizational unit that sells and distributes products, negotiates terms of
sale, and is responsible for these transactions.
Distribution channel: Channel through which salable materials or services reach customers.
Typical distribution channels include wholesale, retail and direct sales. You can assign a
distribution channel to one or more sales organizations.
Division: Product groups can be defined for a wide-ranging spectrum of products. For every
division you can make customer-specific agreements on, for example, partial deliveries, pricing
and terms of payment. Within a division you can carry out statistical analyses or set up separate
marketing.
Name the three internal organizational elements within a sales organization and briefly
explain their function.
Sales Office. Geographical aspects of the organization in business development and sales are
defined using the term sales office. A sales office can be considered as a subsidiary.
Sales offices are assigned to sales areas. If you enter a sales order for a sales office within a
certain sales area, the sales office must be assigned to that area.
Sales Group. The staff of a sales office may be subdivided into sales groups. For example, sales
groups can be defined for individual divisions.
Salespersons. Individual personnel master records are used to manage data about salespersons.
You can assign a sales person to a sales group in the personnel master record.
What does the term “business area” refer to and how can it be used?
Business Area. The system posts costs and revenue according to the business area. The business
area can be equivalent to the:
- sales area (if the accounts are to be posted according to sales)
- plant/division (if the accounts are to be posted according to products)
The business area is defined in Customizing for Sales.
o Business area. A unit in an enterprise, grouping product and market combinations as
homogeneously as possible for the purpose of developing unified business policy.
o Financial Accounting (FI). A business area is an organizational unit within financial
accounting which represents a separate area of operations or responsibilities within an
organization. Financial accounting transactions can be allocated to a specific business area.
Briefly explain the relationship between sales organizations and company codes.
Many to One.
What is the central organizational element in purchasing?
Purchasing Organization.
Explain the relationship between sales organizations and plants.
Many to Many.
Explain the relationship between sales organizations, plants and company codes.
Many to Many to One.
Can one business area be assigned to several company codes? Which (sub) module of SAP
could make business areas obsolete?
Yes in CO .
What is a credit control area? What relationship exists between credit control areas and
company codes?
Credit control area. Organizational unit in an organization that specifies and checks credit limits
for customers. A credit control area can include one or more company codes. It is not possible to
assign a company code to more than one credit control areas.
Which organizational element is central in shipping? Give a definition of it.
Shipping Point: Organizational unit at a fixed location that carries out shipping activities. A
shipping point could, for example, be a company’s mail department or a plant’s rail depot. Each
delivery is processed by only one shipping point.
Give a definition of plant (in SAP).
Organizational unit within Logistics, serving to subdivide an enterprise according to production,
procurement, maintenance, and materials planning aspects.
A plant is a place where either materials are produced or goods and services provided.
Classification: Business object
Structure: A plant can assume a variety of roles:
As a maintenance plant, it includes the maintenance objects that are spatially located within this
plant. The maintenance tasks that are to be performed are specified within a maintenance
planning plant.
As a retail or wholesale site, it makes merchandise available for distribution and sale.
As a rule, the plant is the organizational unit for material valuation.
The preferred shipping point for a plant is defined as the default shipping point, which depends
on the shipping condition and the loading condition.
For the placement of materials in storage (stock put-away), a storage location is assigned to a
plant. The storage location depends on the storage condition and the stock placement situation.
The business area that is responsible for a valuation area is determined as a function of the
division. As a rule, a valuation area corresponds to a plant.
Can you assign two different sales organization to the same company code?
Yes.
To what do you assign distribution channels and divisions?
Sales Organizations.
What are the highest organizational units in SD, MM.PP,FI,CO?
SD: Sales Organizations.
M: Plant
PP: Plant
FI: Company Code
CO: Controlling Area
Can you further subdivide a plant? If yes into what?
A plant can be subdivided into storage locations, allowing stocks of materials to be broken down
according to predefined criteria (e.g., location and materials planning aspects).
A plant can be subdivided into locations and operational areas. Subdivision into locations takes
geographical criteria into account, whereas subdivision into operational areas reflects
responsibilities for production.
Can a sales organization sell from a plant belonging to a different company code?
Yes.
How many shipping points can you assign to a plant?
Many.
How many shipping points can you assign to a sales organization?
None.
If you have a warehouse management system active, to what would you assign the
warehouse number?
Plant & Storage Location.
********************************************************
Pricing
What is the difference of VK11 and VK31 (condition records)?
My condition type is PR00 and Access sequence is PR02. And in this access sequence table
304 is available. Now when I was entering the PR00 in VK31 it shows error Table 304 is not
defining for the condition type PR02. But when I was entering the PR00 at VK11 it is
accepting it.
Difference between VK11 and VK31 - if you go through the menu path you will get the vk 31 as
condition record from the tamplets whereas vk11 as simple condition record. In VK11 you can
store condition record for more than one condition
type. This means you can have same condition record for different condition types.This feature is
given to enhance the system’s performane and not to create the duplcation of the work for each
condition type.
Again system is not allowing to store the record in the vk31 for the condition type pr00 and
access sequence pr02.This is because if you see this ac seq cointains two accessses 20 and 30
having the same table no.But you see there is the difference between the technical view of it for
transfering the data from document field and condition field,so you can not maintain the data at
VK31.
What is the difference between Header condition and Item condition? I know item
condition applies to each item in a sales document. Header condition can only be applied to
an entire document.
Difference between header and item condition - as YOU CORRECTLY SAID HEADER
CONDITION IS APPLICABLE FOR THE WHOLE DOCUMENT where as item is for
item.Ex-Say fright is dependent on the total weight of all the items in the documents then header
condition adds on weights of all items and calculates the record accordingly.
You have two different types of the header conditions.
a) In one you can duplicate the same value throughout the document for each item.Say discount
2% at header level which is also applicable to all the items
b)Second is the accumulation of the values of all the item at the header level,as earlier explained
for the weight/fright.
These differenes are controlled through the indicator of group condition in the cond.type
configuration.
And so obviously header condition can not have the condition record and hence access sequence.
Disallowing Condition Types - How I can accomplish the following:
Be able to DISALLOW Z0BP Condition type to be negative ( Invoice Block)
You can modify condition type from customising;
Sales and Distribution->Basic Functions->Pricing->Pricing Control->Define Condition Types-
>Maintain Condition Types
Change condition type ZOBP’s plus/minus indicator to “A” which means only positive is
allowed.
In pricing procedure there are column such as requirement, sub total altclty, altbv,
accurals. What are these and where we calculate all these values which we put.
1. Requirement: Denoted by nos and maintained in VOFM, this is a condition required for a
particular condition type to be executed. Eg. PR00: req 2 ie item relevant for pricing
VPRS/EKO1: req 4 ie cost
Rebate BAO1 Req 24/Req 25 etc
2. Subtotal: this represents where a which table a value is stored, which can be processed for
further calculation.
Eg. for PR00, if this value is to be used for credt check of a customer, we mark the subtotal as A.
3 Alternate Calculation type: this is also denoted by numbers and maintained in VOFM. Eg.
Suppose for 45 units , each unit is charged $100 per unit, the order value comes out to be $4500,
that is calculation is done as per unit price, if the client wants calculation type to be based on
volume or wieght, alternate calculation type can be configured.
4. Alternate base value: Denoted by no. and maintained in VOFM.
Eg, if the pricing scale is maintained and pricing for 45 units comes under the scale of $100 per
unit., the base value is 45 units, but if the client wants a standard base value in some casesto be
assumed inspite of maintaining the scale, an alternate base value is confihured, that is the base
value based on which the order value is to be calculated changes.
5. Accruals: Accruals are maintained for rebate agreements, it constitutes the total accumulated
value which customer has earned through rebate, one the rebate for certain amount is settled the
amount from the accruals get deducted.
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?
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
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)
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.
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.
1. 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.
2. 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
3. Do header condition type have an access sequence?
No
4. 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.
5. What are legacy systems?
The Existing system on which current system is working, from which the current system will be
migrated to SAP system
6. 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.
7. 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?
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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)
14. Can you create sales order for 40 items if the quotation is sent for 30 items?
Yes.
15. What is the importance of requirment field in access sequence?
System will not go to asscess condition type system will reply through formula.
16. What makes the immediate delivery in cash sales?
Order type immediate delivery switch on.
…………………………………………………………………………………………………………………………………………………………………
………………………………………………………………………………………………………………………………………………………..........
Your Ad Here
Friday, October 26, 2007
How To Add New Fields To Field Catalog
For adding field into Field catalog:
I shall give an example. But you should first identify the field for Profit Center (Design ID) and then do as
follows:
For example if you want to use field PSTYV (’Sales document item category’) that is included in structure
KOMP (’Pricing Communication Item’) as a key for a condition table.
When you create a condition table (Transaction V/03), however, the system does not propose the field in
the field catalog.
Prerequisites:
For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG
(’Allowed Fields for Condition Structures’).
To solve the problem, proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a
domain.As a short text, you can use, for example, ‘ZZ - sales document item category’ and as a field
label, you can use the field labels of PSTYV.Save, check and activate your entries.
2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make
the following entry:
Component Component type
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.
3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG
and KOMP because structure KOMPAZ is included in both structures.
4. Call up Transaction SPRO. Navigate to ‘Sales and Distribution -> Basic Functions -> Pricing -> Pricing
Control’ and execute ‘Define Condition Tables’. Choose ‘Conditions: Allowed fields’ and include
ZZPSTYV as a new entry.
5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
6. Supply the new field you defined by including the following source code line in
USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you
find it in Include RV60AFZZ.
Consider that you can also use this note as a help if you want to use other customer-specific fields as key
fields in a condition table.For header fields, use structure
KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of
USEREXIT_PRICING_PREPARE_TKOMP.
For more information, see Transaction SPRO via the path ‘Sales and Distribution -> System Modifications
-> Create New Fields (Using Condition
Technique) -> New Fields for Pricing’ and Note 21040.
For creating a condition Table:
1) There are almost all the regularly used Conditon Table predefined in the system from 001 to 500.
See what best you can use the Standard Tables to avoid further errors.
2) In case you should define the new condtion Table,
a) Goto TCode: V/03
b) Give a Table any number from 501-999
Press execute and reach to next screen.
c) Check up whether the field you are looking is already added in Field catalogue.
d) Double click on the fields you want to make a Table..one by one. Note that the sequence here is
important in higher hierarchical to lower..
Eample : Sales Org, DC, Division, Customer and then Material etc..,
e) After selecting, click on the Techincal View buttin (redone) and reach to next screen.
7) Check which key should be in header and which key should be footer. Use check and uncheck
functionalities there..
Once you are through with all the above steps ..click on generate button.
Check the Table is generated or not.
You can check it at V/04 or V/05 or in SE11.
…………………………………………………………………………………………………………………………………………………………………
……
ntercompany Sales Process
In this business process- Sales organization of company A receives sales order from customer
and ask Plant B assigned to company B to deliver it to customer for any reason. Both companies
belong to same client.
Prerequisite to Intercompany Sales process
Billing Type IV is maintained. It is available in SAP. - Assigned this billing type to Sales order
type in T-code VOV8 or IMG- SD- Billing-Intercompany billing-Define order types for
Intercompany billing
Material has to be created in both plants(Plant of ordering company and plant of delivering
company)- MM01
Plant of company code A to be assigned to Sales organization of company code B- T-code
-OVX6 or IMG- SD- Billing-Intercompany billing-Assign organizational units to plants
Define Internal customer number by sales organization- It means that in supplying sales
organization/company master data records ordering company has to be created as Internal
customer in T-code XD01.
Assign Internal customer no IMG- SD- Billing-Intercompany billing-define internal customer
no by sales organization to order company code/sales organization.
Pricing - in this case we have to have two pricing procedure - RVAA01 and ICAA01- Tcode-
VOK0
RVAA01- is assigned to order sales org/dist/div/doc.type and customer.It is normal pricing
procedure; as per business requirement of the order company for the customer.
ICAA01- Pricing procedure is assigned to supplying sales org/dist/div/doc type and order
company code customer. Conditions PI01 or PI02 are maintained in RVAA01. Since it is
intercompany business process PIO1 or PIO2 represent cost of the material and statistical only.
PIO1 and PIO2 represents IVO1 and IVO2(in ICAAO1) respectively. Condition record for PIO1
or PIO2 have to be created in VK11.
It is assumed that standard SD configuration is in place.
What do you mean by Transfer of Requirement ?
Explain transfer of requirement? How it works and how to configure?
It specifies the following points:
1. Whether an availability check and a transfer of requirements is carried out for a transaction
(for sales documents, fine tuning using the schedule line category is possible),
2. Whether the requirements are relevant for MRP,
3. The allocation indicator from the sales view which controls the settlement of customer
requirements with requirements,
4. Whether an item is to be settled to an auxiliary account assignment,
5. The settlement profile,
6. The results analysis key.
When a sales order is raised, then the system check for availability of goods. If the availability
of goods is not there, then the system creates a TOR for the supply of goods to PP. Then PP can
do procure or produce the goods. This can be configured by creating requirement class and
requirement type and in the corresponding schedule line category requirement had to be checked.
The MRP department is informed about the quantities and deadlines by which incoming orders
should be delivered. The system checks the availability of the goods based on the requested
delivery date of the customer and creates MRP records which contain all necessary information
for passing on to planning. It ensures that the goods are available in time for the delivery.
Materials planning transfers the reported requirements and creates orders or purchase
requisitions from them etc.
The following sections on the transfer of requirements describe how to control the transfer of
requirements.
The transfer of requirements is basically dependent upon the following factors:
- requirements type
- requirement class
- check group
- schedule line category
The transfer of requirements is controlled globally using the requirements class which is derived
from the requirements type for all sales document types.
For the sales document types, fine tuning is also possible at schedule line level. This fine tuning
is described in the section "Defining the procedure for each schedule line category".
Note that the requirements classes are also used in production so you should coordinate any
changes to the requirements classes with production. The requirements type and, eventually,
requirements class are determined in the strategy group so all changes made there should also be
coordinated with production.
For performing transfer of requirements, you have to carry out the following steps:
1. Each requirement type has to be allocated to one requirement class only.
2. The transfer of requirements must be switched on at requirements class level, the sales
documents at schedule line level.
3. You must define a check group. It is possible to have this check group proposed for the initial
creation of a material master record.
4. Note that a plant must exist for transfer of requirements to be carried out at document item
level.
Requirements transferred to planning are further processed in the module MM. You must,
therefore, coordinate the transfer of requirements with the module MM.
