Short SAP SD Questions 1 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 XD02 XD03 XD04 XD05 XD06 XD07 XD99 XDN1 Create Customer (Centrally) Change Customer (Centrally) Display Customer (Centrally) Customer Changes (Centrally) Block customer (centrally) Mark customer for deletion (centr.) Change Customer Account Group Customer master mass maintenance 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. Centrally XD01/XD02/XD03 etc. 3. Sales urpose 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.

SD Questions on Corporate Structure In R/3 you can represent a companys 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 companys mail department or a plants 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.

Short SAP SD Questions 2 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. Theres 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. - Evilboy 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.

Short SAP SD Questions 3 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) VEDKmeans 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 BPOs (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 clients 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 BPOs 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 BPOs (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. SAP SD Tips by : Moyin 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. *-Sabir 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. *-- Vaibhav 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. *-- Ganeshan.D

Answers for SAP SD Certification Sample Questions

Question: Which statements concerning goods issue are true?

Answer: A Goods issue reduces requirements in materials planning B Goods issue posts value changes to the stock account in inventory accounting C Goods issue posts value changes to the stock account in asset accounting D Goods issue posts value changes to the tax account E Goods issue reduces warehouse stocks Question: Which of the following statements about billing are correct? Answer: A. Invoice dates for creating invoices at certain times are maintained in the calendar. B. You cannot carry out pricing again during billing. C. A transaction-specific requirement, such as deliveries must be combined in a collective invoice can be set to control billing. D. If there are several payers for one delivery, only one billing document is created for each player. Question: How is the schedule line determined? Answer: A. Item category and document type B. Item category group and strategy group on the material master record C. Item category and MRP type on the material master record D. MRP Type and shipping point Question: When processing a billing due list, you have the following options: Answer: A. The invoicing run can be started as a simulation run. B. For performance reasons, the invoicing run via billing due list processing can only be carried out in batch. C. The invoice run can be carried out for delivery-related and order-related billing documents simultaneously. D. Order-related billing documents and delivery-related billing documents must always be created separately. Question: How does the SAP system enable you to check the reason for documents not being combined in a billing document? Answer: A. Using the Spilt analysis function in the environment menu of the billing document. B. Control of the document flow. C. Control of the billing log. Question: How is the schedule line determined? Answer: A. Item category and document type.

B. Item category group and strategy group on the material master record. C. Item category and MRP type on the material master record. D. MRP Type and shipping point.

My SAP SD Certification Experience

Let me share my certification experience with you. Keep following things in mind when preparing for the exam: 1. Prepare as per the weightage per topics given in the syllabus. 2. Be very confident on sure shot questions from the topics like: All determination rules - plant, material, pricing procedure, picking location, route, shipping point, tax, item category, account determination etc. One question on effect of PGI. 35 to 40 % questions will come from control tables like sales doc types, item category , copy control , delivery doc. , del. Item cat. , billing docs , schedule lines etc . So try and mug up all the imp. Control fields .Your preparation level should be such that once you close your eye and think of TAN or OR you should be able to see all the fields in your mind . These above, are sure to shot and you cannot afford to do mistakes in this sections. 3. Go through the screens, transaction level screens like sales order, delivery, billing, delivery list, billing due list, even standard reports etc. and check what is possible and what is not possible at each docs. What is defined at header and what is at item Go through the menu path of each docs and check what all is possible and from where it is coming. For example packing proposal and account determination analysis is possible at sales order. 4. Go through all the masters like customer, cust- material, material, > condition records for price, output, etc. Check what is defined at what level, what all is possible etc. 5. Check entire IMG - SD related, it will help you to understand what is defined at what level etc. 6. In exam be very careful with the sap English, particularly with the words like can, only, always, except. Read question very carefully. Sap statements in the exam will be always confusing, so think logically and holistically before exam. 7. Dont take any chance in preparation but always sticks to core basics, they will not ask configuration, but they will ask you what is possible and what is not and where it is defined. 8. Last but not least have confidence, how much a guy who have studied for 5 weeks is suppose to know that standard will be asked . Prepare well you will definitely succeed.

Important Tips for Interview for SAP SD

Let me share some important tips for interview for SAP SD: 1. Please be through with the projects you have mentioned in your resume. 2. Remember all the versions you have worked upon. 3. If your projects are in Indian scenario be thorough with CIN/Excise VAT and pricing procedure. 4 For offshore client specially in Europe and NASA prepare yourself for Warehouse/Lean warehouse 5. Third party billing / Intercompany / Make to order are important topics. 6. Cost booking that is accounting enteries after PGI and Billing should be known to you. 7. Mug up all the determinations. 8. Remember your last ticket. 9. Have general awareness about ALE/EDI/IDOC, as this provides added advantage. (not very tough) 10. Please be through with your basics, the process, the pricing and the master data. 11. People who are thorough with route, transportation, shipping always have an added advantage. The MOST IMPORTANT THING: Do not try to fool your interviewer, say exactly and only what is asked do not show your excitement and do not speak too much if you know the topic too well, and say a straight NO if you have not worked on something, or dont know about something, pls pls pls dont not go for flukes otherwise you will end up in soup. What I understand is most of the companies especially in the US are looking for a candidates with 1) good communication skills (SAP is all about interacting with the client, users and team) 2) good business knowledge 3) are you able to convince the client That comes in next round when you are interviewed to be deputed for any US/Europe project, in this round take care of the following: 1. Speak slow, I mean normal, because usually Indians speak english too fast. 2. Listen to them carefully, if you are not able to understand their question request them to repeat it, rather than assuming it to be something else and giving a wrong reply. 3. Again I should repeat prepare yourself for warehouse, I mean even general knowledge will help. 4. Say a straight no when you dont know or have not worked on the topic. 5. Always be strong on SD MM FI integrations What the job responsibilites would be for the Support Consultant? If the Consultant is working in Offshore Support, How the business interaction would be there between the Consultant and Customer? How the Customer Queries were handled successfully sitting from his location. Job responsibility of a Support consultants is to handle routine tickets, which can be incident (routine problems), change tickets (need configuration change, therefore a change request), normally a support consultant can only advice a change but cant do it , because there is always a change advisory board on client end to evaluate and implement the adviced change. Business intercation between users and customer can be through mail box utilities, outlook, even telecons and some companies also allow chat. Usually the customer provides with the number of the document and client/company code and other necessary info.

about the process which is facing problem, the consultant tracks the project by logging in to development server and search out for causes, the solution is then sent to user, maybe with snapshot if required. For those people who asks for for tickets: 1. Tickets are normally raised by end user and carry a priority. 2. Those who are asking SAP gurus to tell them about tickets, pls note that most of the problems except for the basic questions discussed in this group are the tickets themselves, tickets are nothing but the routine incidents the SAP consultants get, if you regularly read the mails in the group you will soon start recognizing tickets. And the most important thing Believe in yourself and God, as there is always somebody there to help you. Tips by : Nitin What is the team size? Duration of the project. Hardly the team of the sd will be 4 to 5 and entire team of the project will be around 20-24 (all modules like fi/co, sd, mm, pp, hr, qm, pm). If its big project, it will be around 40. Team size means the employees who you are working on sap r/3 implementation. For the project completion it will take around 8-10 months to get into golive. After that, post implementation for 3 months. After that supporting it depends as

SAP SD Interview Questions

Following are some SD Interview questions that might be asked. 1. What is the purpose of text determination, account determination, partner determination, output determination,storagelocation determination 2. What are the five imp fields to be maintained in account determination 3. How to create excise invoice and what is it 4. What is meant by transfer of data from legacy code to sap 5. What do you do really in pricing determination, and what are the main deifferences between one pricing procedure determination to the others, which data control these differences 6. What type of reports generally a support consultant maintain and report 7. What are interfaces used generally an indian organisation which is in retail business and and which is in banking business and oil business. 8. What is the purpose of shipping point determination not menu path 9. What and where types of copy controls we change 10. How to and where to maintain copy controls 11. What is purpose of maintaining common distribution channels and common divisions Q.No.11 Common Distribution Channel and Common Divison are maintained so that if any master data like customer or material maintained with respect to one distribution channel can be used in other DCh. It prevents the multiplication of master records. Eg: A customer is created for say sales area 1000/20/00 then the same customer can be used in sales area 1000/30/00 if we maintain 20 as common distribution channel. Hence no need for extending the customers...the same for

materials also. Rajendra Babu As of what I know answer to question 5 would be: 5. we determine how the prices are calculated, taking into account sales area(sales org, distribution channel, division), document type and customer(generally sold-to-party). The main differences between pricing procedures would be the differences as I mentioned above, from the point of view of field entries. Coming to the output and the procedure, I suppose the condition types used will be different and hence the following whole procedure. Uday 1. What is the purpose of text determination, account determination, partner determination, output determination, storage location determination Text determination: For transferring information from material or customer to order/delvery or invoice (and anything inbetween) Account determination: For transferring financial and costing information to proper financial docs Partner determination: For determing who is is legally resposible for A/r, who the goods are going to and whatever else you waana drive through this functionality. Output determination: What kinda output does a sales/delivery/billing document create and who gets it, where?. For example A partner might get an EDI notification for a sales order just confirmed, whereas a financial/leasing company gets the invoice! 2. What are the five imp fields to be maintained in account determination Go to IMG and find out 3. How to create excise invoice and what is it. Ive never worked in india so I dunno 4. What is meant by transfer of data from legacy code to sap Legacy Code ? It should be legacy data to SAP. What it means is you want to transfer all the customer and materials and all other information from Older (legacy system) to new SAP system. You can do it using many tools, most noticeably MDMs. Vivek Regarding q-3,

As per Indian tax system, Excise duty (16%) is payable by each manufacturing unit on the value of manufactured goods / on the value added. The manufacturing plant is supposed to submit an excise duty report on fortnightly / monthly basis. Various registers (RG1, RG23A, RG23C, PLA) are maintained for that purpose, which record all the transactions including movement of goods, cenvat credit available and cash balance available. In SAP, we use transaction j1id for configuration and j1iin, j2i7, j1i5, j2i5, j2i6, j1ip for creating, extracting and printing excise invoice. Jitesh 1. (a) Text Determination: Any Texts in Masterial Master/Material Determination/Order/Delivery , etc is meant to convey messages to the subsequent documents for compliance. e.g. Give Top Priority message mentioned in Order is meant for Production Dept. (b) Account Determination:is integration between Finance and SD. The A/P along with Account Keys need to be allocated accordingly with combination of Account Determination Group for Customer and Material if required. Partner Determination:To identify which type of Partner it is so that if required for same Customer different Partner Functions may be required e.g Only One Sold To Party per Customer. More than One Ship to Party/ Bill to Party/ Payer possible. Accordingly different Masters will have to be created. Useful for despatch of Material in casae of Ship to Party, sending Bill in case of Bill to Party and payment followup/Dunning in case of Payer. (d) Output Determination: What type of Output (Fax/Mail, etc) is required, where and in what Format(ABAP Customisation may be required in some cases especially Invoices). (e) Storage Location Determination: depends on Plant, Shipping Point and Storage Conditions (2) Account Determination: Sales View, Sales Organisation, Distribution Chanel, Chart of Accounts, Account Assignment Group for Customer and Material and Account Keys. (3) I will check and let you know within week. (4) Before installation of SAP, Data maintained by Company is called Legacy Data. At the time of instalation, it is required to transfer Data from Legacy to SAP like Masters (Material/Customer, etc). It can be done in various ways like BDC, LSMW, etc. (5) Pricing is determined by combination of Sales Organisation, Distribution Channel, Division, Customer Pricing Procedure and Document Pricing Procedure. (6) Depends on Customer requirements. (7) Its not clear. (8) So that Shipping Point is determined automatically once the settings for the same are done. (9) Copy Control: is basically meant so that Data is copied from preceding Document to subsequent one. What subsequent Document is required is to some extent determined by Customer Requirements as well as Document Types. e.g. In general case of Standard Order, it will be Copy Control (Order to Delivery) from OR to LF .

(10) Check for yourself in IMG (Sales Document types and Delivery Document Types) Shailesh What is the difference between the Avaialbility check 01 (Daily requirement) and 02 (Individual Requirement) in material master? 01 and 02 are the checking group. Availability check is carried out with the help of these checking group and checking rule. Checking group 01 and 02 are maintained on the material master. 01 - Individual requirement -For this system generates transfers the requirement for each order to the MRP .So that MM can either produce or procure. 02- Collective requirement.-In this all the requirements in aday or in a wek are processed at a time. System stores all req and passes on to the MRP in MRP run.In this system performance is high however you can not do the backorder processing whereas in other you can do. *-- Vishwajit

Interview Question and Answers on SAP SD

1.What are the responsibilities of a functional consultant in an implementation project? a) Responsibilities in implemention project - Preparing the functional specification documents. - Review and approval of functional specifications. - Designing a road map and setting approval from client. - Changing existing configuration whenever needed. - Setting up configuration for new enhancements. - Handling basic issues of MM module. b)Responsibilities in support project - Handling customization, configuration, and enhancement related issues - Handling tickets on Day to Day basis - Monitoring S&D reports on daily basis required by clients - Preparing functional specification documents - Preparing end user training Documents 2.What are the responsibilities of a technical consultant in an implementation project? Preparation of techinical specifications, getting apporvals from functional consultant and PM,assitance to functioal consultant. 3.What are the main and sub modules in SAP?

MM,FICO,PP,ABAP 4.What is ERP and SAP?and why inplementing SAP in an organization? Explain the special features of SAP over other ERPs? SAP is an ERP package. SAP can be fit it any language. It is used to get exact data with a fraction of section which will be use fully for management to take correct decision in a short span of time. Using of sap means there is no need to maintain the middle management in the organization because the CEO of the company is able to direct the executives direcltly with the system. SAP is able to integrate all functional organizational units togethere and retrieve exact data needed by management. Therefore, investing on middle management will become less. and the user will be able to acess instance reports using the logistic informaion systems in SAP. 5.Explain the business flow of an implementation project? - Project prepration - Business blue prints - Fit gap analysis - Realization - Golive - Support 6.Explain breifly about your role in current/previous project? (If you have one) Team member 7.Explain your functional experience prior to SAP? For this yo will give explanation depends of your previous experience. 8.Can you explain the modern technologies in SAP? Do you use this in your current project? I think the ans is APO, BW, CRM, if its wrong pls guide me any body. 9.Explain the terms AS IS and FIT GAP ANALYSIS? Business blue print stage is called as is process. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There should be a gap. So by filling this gap, we make configuration with the help of these documents. This is called as fit gap analysis. In this stage, we should analysis the gap between as is and is as process 10.What are the responsibilities of CORE TEAM and FUNCTIONAL TEAM in an implementation? Core Team are the power users who are selected for the SAP implementation. The Functional Team gather the initial implementation requirement from these core team users who will be the bridge between the SAP Functional Team and their department users with the expert work knowledge.

Some SAP SD Interview Questions 1

1. What exactly is automatic posting can you explain? 1. Automatic posting could be, posting of accounting documents to FICO once invoice is created which can also be controlled manually. Automatiaclly detremine the freight while pricing in ship doc. and post to the relevant account to fico. usually automatic posting is posting of documents to FICO based on variuos account keys and account groups. 2. How many clients we will create in land scape (like in development server, quality server, production server ) if we are creating more than one in each server what is exact use of that client. 2. Client landscape : Basic layout : dev -testing- production also - Sandbox env. for trial and error - Development env. for actaully creating transports(CTS) - Global env. If you have global implementations at different client locations (eg; canada, US, UK) (for testing purposes with actual master dataas well) - Testing env.(for regression testing purposes before moving to prodcution, integration etc..) - Prod. env. the actual production system The clients could be variable and could be created to a specific env. usually a dev. where abap, functional would mess around. say : client 100-functinal consultants client 300- abapers client 400- other users(like super etc) 3. How we will configure export sales in sd (respect to plants assign and sales process)? 4. How we can do invoice split depending on item category in which scenario we will use? 4. You first need to go for copying controls either from sales to billing (invoice) or delivery to billing or billing to billing use transactions (vtaa,vtaf,vtla,vtfa,vtfl,vtff) all possibilities for copy controls. this basicly is flow of doc to doc. (may it be sales to billing, del to bil, or bil to bil etc..) -> this is where you see the Item category and you control whether split is possible or not with the indicatorB. eg: representing split in invoice based on item category. The field here data VBRK/VBRP (headre/item)whcih actually is used for splits or combining different deliveries. create a splitting rule using VOFM (you need access key to get here). Here you define comparisions for the fields at header table and item tables and the comparision fields say SPARTdivision. purchase order BSTKD Instance: 5 sales orders combined into 2 deliveries and the split at the invoice would be 5 individual billing with respect to fields PO and DIv. of each sales order would let you create 5 billings. You need to define the exact field in the comparisions both at header and item level that could lead to invoice split. the key here is the field that is different from header to item will cause split at the item level. 5. Can any one explain how we will configure milestone billing , periodic billing and which scenario we will use?

5. Menu path: IMG->sales &distr->Billing->billing plans->define billing plan types. You set the start date and end dates if applicable to the type of billing you are using. What time to be billed (end of month, start of month etc..) Milestone is a billing plan type where a customer is billed for the amount distributed between the dates until total value is reached eg: if the total billing amountis 1000 USD for a year. You will bill the customer in different amounts say 200, 500, 300 at different intervals as per customer agreement. On the other hand Periodic billling is billing the customer for the total amount(here 1000 USD) at regular intervals peridically until the customer agreement is reached. eg: 1000/12 for a 1 year agreement and say billed at the 1st day of every month. 6. What are some pricing routines and sd functional specs? 6. Form routines for prcing and variuos other functions can be maintained form routines are something todo with ABAP code. Go to (VOFM) where all requrements whcih are represented by form routines can be maintained. Requrements are available to be assigned where access sequenses are used (for determination procedures, here pricing). Once the tcode VOFM is accessed you will see requrements and go select pricing again you need access key to create your own or copy a routine. Say you want header price not to have effect the item pricing, you need to go to the program to change abap code to meet the requirement. this specific requirement you created will be assigned in the pricing proc. determination requirements field usaully with a number beyond 600. Note: make sure you activate your routine for its effect to take place.

Some SAP SD Interview Questions 2

Some of the interviewed questions and answers are as follows: What is the movement type you used in consignment process? ### 632, 633, 634, 631 Can team size be 40 in a project? Is there any generalized team size no. for any project? If we tell my team size is 40 in that what no. we can say sd people are? ## Team size cant be forty, Theres no genralized size of team. Never 40 sd consultants work together on same project. What is ALE? ## Application Linking and Enabling - Generally ABAPers work on it. What is meant by condition technique: can we say it is the combination of condition types, access sequence and condition tables? ## yes Where do we can find pricing procedure indicator in sd ? ## Pricing procedure is where we maintain all Conditions (like PR00, K004, mwst, kp00, etc) Where do we assign calender in the master records? ## In IMG screen Global Settings.

What is the importance of customer account groups? ## We maintain the customer account to maintain payment terms and incoterms. Lets say, if SP is only booking order but the goods should deliver in foreign country and for which SP is not going to bare the excise and other taxes then the SH party or payer will tke teh responsibity then the tax is calculated based on account groups. What are incoterms? Where do we fix them? Where do you find in regular process? ## Incoterms or international comm. terms and u find in CMR - Sales area Data - billing Tab. How can you make some of the fields as key field in generic tables? ## Some fields in all tables have a indicator on it.To see, then go to SE11, display VBAK, u will find MANDT on top, if you see after description 2 tick marks, those are key fields. Gernerally, these key fields are used in writing any Program or Interface. The key fields will extract data of non key fields . What is the standard group condition routine in condition type, what is its importance? ## Its better u read Group Conditions in PR00. How do you control entry possibility of condition values at order through condition type settings? ## You can maintain the maximum and minimum value for all conditions. What are the customizing settings in pricing procedure for tax condition type? ## Check out the standard pricing procedure RVAA01 - MWST. A bunch of data need to be imported. A huge no.of creations are required, how it is possible in SAP? ## thru LSMW, BAPI. What is the difference between PGI cancellation and returns order? ## PGI cancellation is done before the transportation of goods. But return order means its already transported reached customer during transit if materil is spoiled or broke or the goods r not delivered as per customer requested date.then customer send the goods baack to company. What is the integrated areas in SD AND FI, SD AND MM, SD AND PP in both implementation and support projects? ## SD & FI - Possible in Account Determination, for posting the conditions to revelant G/l account like all prices goes to one particular g/l account. Also in Credit Management, Taxes. SD & MM - Possible in Batches, Material Requirement Planning. SD & PP - Possible in Material Requirement planning.
.

SAP Sales and Distribution Frequently Asked Question

Master Data
Q: Some materials have been blocked for procurement and production. Even though deletion flag is set for a material/plant level, the order can be still entered ( with a warning message). Is there a way to block such transactions for a material flagged for deletion?

A: Sales Status field in the sales organization view of the material master may be used to block any transaction for the material. Q: We can define our own exchange rate types and use them instead of the defaulted types, M, B and G. How can we overwrite default types in SD? A: Exchange rate gets copied from the customer master record. Exchange rate types are to be maintained for the customer in the sales screen of the customer master record.

Shipping
Q: The PL00 condition is fine in delivery. But when we try to print to either the screen or printer, an error V1032 occurs. Why? A: In order to use the Packing list PL00 (packing slip in delivery) you must do Packing in the delivery note (edit>packing) Q: we have to enter a shipping point while creating a delivery. Is it possible to create delivery without shipping points? A: When you are releasing a sales order, choose Sales document -> Subsequent functions-> Create delivery, then the shipping point will be brought in from the sales order. In all other scenarios you have to key in the shipping point. The above described scenario will only work if all items on the sales order are to be shipped from the same shipping point.

Billing
Q: SAP allows a non-inventory item and an inventory item to be in the same document till delivery but splits at the time of creation of billing document. Can we combine a non-inventory item with an inventory item in one invoice? Can we treat it as a value item in sales order so that it is priced and then make it as a text item in delivery documents so that it appears in the same invoice and does not split? A1: Make the non-stock material deliverable, but not pickable. Both items will carry into the delivery, and therefore appear on the same invoice. A2: Change the copy rule for orders->invoices and deliveries->invoices to specify that invoice combination is permitted. However note that for system to create combined invoices, PO number, payment terms, sales organization, and distribution channel must be identical. Else undesirable combinations may be created by the system.

Pricing Conditions Q: It is impossible to price at the material level (matnr) , when a material has a pricing reference (mvke-pmatn) set
up against it in the master data. Pricing always look for the pref, even if a price is set up against the material and not

the pref. How can we price by material and pref? A: The field used to look up at the price is defined in Access sequence. You may find a step with PMATN as material number. If you insert a step with MATNR then the system will first look for the material, if not found (use the exclusion tick box) it will look for the pref.

Customizing
Q: We generated a new condition table. Assigned the condition to access sequence. Created a condition record. Access sequence is assigned to the output type. But when we create a billing document, output screen comes up blank for the output type. When we look up Determination Analysis, we get an error Note 524 Access not made (Initialized Field). What else is required to be done? A: Assign output determination procedure to the header of the document and the output type. Q: How can we set up to have the VAT# be accepted in the Ship-To Master File Data Control screen? A: IMG->Fin. Acct.->AR and AP ->Customer acct->Master Record -> Prepare to Create Customer-> Define Acct. Group. Q: We want to explode Bill of Material automatically at time of Order entry and explode an Equipment BOM in the sales order. What are the setting required? A: Use an item category that is configured for bills of material for having a sales BOM to explode automatically. Standard SAP item categories are : TAQ - Pricing and inventory control take place at the BOM header level TAP - Pricing and inventory control take place at the BOM item level These can be automatically derived using the item category groups ERLA and LUMF, respectively. Q: How can we make the Customer Group 1 (or 2, 3, 4, 5) a mandatory field? A: Logistic General-> Logistics Basic Data: Business Partners -> Customers -> Control -> Define account groups and field selection for customer Choose Customer Acct. GR. (double-click). -> Field Status: Sales data (double click) -> sales (double click) .Check the radio button against Customer Gr as REQ. ENTRY. Save the settings to make customer GR entry mandatory . Q: Is there an user exit to copy the data into planning table? A: Use user exit MCP20001 and include ZXSOPU01.

Others Q: We get a report screen: Goods issue: Problem Log during the delivery process when activating Post Goods
Issue button. We want to include our own error message to this list if the selected batch is not on a customer defined table. What is the best way? A: Try User exit - USEREXIT_SAVE_DOCUMENT_PREPARE

Link Between SAP SD, MM & FI

1. In SAP you will always get integration with other modules. SD will interact with FI, MM will interact with SD :1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped directly to your customer). 1b. Billing is an SD function. But SAP needs to know, when processing a customers payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination. 2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc. *-- Shahee The link between SD and MM :1. When you create sales order in SD, all the details of the items are copied from Material master of MM. 2. MRP and availibility check related data is also taken from MM although you control this data in SD also. 3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master. 4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material. There are many such links between SD and MM. Now the link between SD and FI :1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the background. eg. In case of standard sales order, you create an outbound goods delivery to the customer. Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account. 2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI 3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM

SD Integration points with other modules

SD module is highly integrated with the other modules in SAP.
Sales Order Integration Points Module

Availability Check Credit Check Costing Tax Determination Transfer of Requirements Delivery & Goods Issue Integration Points Availability Check Credit Check Reduces stock Reduces Inventory $ Requirement Eliminated

MM FI CO/ MM FI PP/ MM Module MM FI MM FI/ CO PP/ MM Module FI/ CO FI/ CO FI/ CO PS Module MM FI FI FI FI

Billing Integration Points Debit A/R Credit Revenue Updates G/ L (Tax, discounts, surcharges, etc.) Milestone Billing Return Delivery & Credit Memo Integration Points Increases Inventory Updates G/ L Credit Memo Adjustment to A/R Reduces Revenue -

Tips by: Subha

SD Transaction Code Flow:

Inquiry / Document type IN Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP Quotation / QT Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP Purchase Order PO Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO. Sales Order OR Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP Delivery LF Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS Billing MN Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no. To create vendor tcode is xk01(create), xk02(change) , xk03(display)

Tables are lfa1. To create custmer tcode is xd01, xd02, xd03. Table is kna1.

Process Flow for 3rd Party Sales

Customize the third party sales in summary: 1. Create Vendor XK01 2. Create Material Material Type as Trading Goods. Item category group as BANS. 3. Assign Item Category TAS to Order type that you are going to use. 4. A sale order is created and when saved a PR is generated at the background 5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor. 6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO 7. Goods receipt MIGO 8. Goods issue 9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the config and, therefore, there is no delivery process attached in the whole process of Third party sales. 10. Billing *-- Seema Dhar

SD - 3rd party sales order Create Sales Order VA01 Order Type Sales org, distr chnl, div Enter Sold to PO # Material Quantity Enter Save SD - 3rd party sales order View the PR that is created with a third party sales order VA01 Order Number Goto Item Overview

Item ->Schedule Item SD - 3rd party sales order View the PR that is created ME52N Key in the PR number Save SD - 3rd party sales order Assign the PR to the vendor and create PO ME57 Key in the PR number Toggle the Assigned Purchase Requisition Execute Check the box next to the material Assign Automatically button Click on Assignments button Click on Process assignment The Process Assignment Create PO box , enter Drag the PR and drop in the shopping basket Save SD - 3rd party sales order Receive Goods MIGO_GR PO Number DN Number Batch tab , click on classification Serial Numbers tab Date of Production Flag Item OK Check, just in case Post Save SD - 3rd party sales order Create Invoice MIRO Invoice Date Look for the PO , state the vendor and the Material Check the box Clilck on Copy Purchase Order Number (bottom half of the screen) Amount State the baseline date Simulate & Post Invoice Number *Invoice blocked due to date variance SD - 3rd party sales order Create a delivery order VL01N In the order screen , go to the menu Sales Document , select Deliver Go to picking tab

State the qty and save SD - 3rd party sales order Create a billing document VF01 Ensure that the delivery document is correct in the Enter Go to edit -> Log Save

An Example Of Third Party Sales

Scenario: 2 companies are created in system - India & Singapore Customer places sales order for particular material on Singapore. Singapore is not able to produce the same. They pass on the order to India for processing. After processing India ships the material directly to the customer along with necessary documentation. Invoice copy is passed on to Singapore. Final Commercial Invoice will be raised by Singapore. How can the above scenario handled? By: Balaji You can do this using third party sales. The third party sales process is as under. 1) Singapore company creates an order for the singapore customer. 2) Because of the configuration settings of the sales document type, item category & schedule line category, as soon as the order is saved a PR (purchase requisition) is automatically generated. This is converted into PO (purchase order) and sent to the indan company. 3) Indian company supplies the material directly to the singapore customer. 4) Indian company sends the invoice to the singapore company. 5) Singapore company does the invoice verification in MM using tcode MIRO. 6) Singapore company raises the invoice to the singapore customer. In standard SAP, item category TAS is used for this. The schedule line category is CS. Here you can see a field order type with value NB. This triggers the automatic creation of the PR. Plus in the material master also you need to do certain settings. 1) If you are always following a third party process for a material then you have to create the material using item category group BANS. The procurement type should be marked as external procurement (F) in MRP 2 view of the material master record. 2) If you are not always allowing third party order processing then you can create a material master record with item

category group as NORM and the procurement type should be marked as (X) meaning both types of procurement (in house manufacturing and external procurement).
. Difference between Condition Type

Please explain the difference between Ek01 ( Actual Cost) and EK02 Calculated Cost. These are the condition type that will display the results of the unit costing for certain type of sales document. EK01 : If you use this condition type, the result of unit costing is issued to the first position on the conditions screen for the item. The value can be used as a basis for price determination. EK02: If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price. Please note the following points : 1) The condition type must have condition category Q (costing). 2) The condition type must agree with the condition type defined for unit costing in the pricing procedure. I have a customer who is being offered two discounts ie k007 and k005, now I want to exclude k007 for the next 2 orders or so? I have set the exclusion indicator for the condition type,but still the condition is being accepted when I create a sales order. Am I missing something, how do I do it? I think u need to change the validity of the condition record for the condition type K007 defining it not valid for that particular 2 months. And also the settings of the Requirements as it is correct that it overrules the exclusion.

Accumulate the amount of condition types in accounting document

To accumulate the amount of condition types in accounting document without affecting the pricing display in billing document. As an illustration :ZPXX 3500 ZDXX 1000ZWXX 500(all condition types are shown separately in pricing view) Journal: Dr Vendor 2000 Cr Sales 2000 (ZPXX - ZDXX - ZWXX) One way to do it is :-

Mark the condition types you want to group as statistical and remove the account assignment key. Create a subtotal in your pricing procedure that will add them together and put in the account assignment key for it. This way the individual components will still display on your pricing screen but FI will only get one posting. Creating New Pricing Procedure What is the transaction code for creating new pricing procedure and how to attach it to specific plant? You create PP in spro > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and Assign Pricing Procedures > Maintain Pricing Procedures You cant attach PP to specific plant. Pricing Procedure is determined thru trx OVKK. The defining parameters for pricing procedure determination are: 1. SalesOrg 2. Distribution Channel 3. Division 4. Document Procedure (defined in Sales doc\Billing doc maintenance) 5. Pricing procedure assigned to customer (defined in customer master) Hope this helps. Sabir Reg pricing procedure. 1. Use transaction code v/07 to create a access sequence and assign tables based on which you want to carry on pricing as accesses. 2. Use transaction code v/06 to define condition type. It can be for base price, discount, freight etc., (Do assign relevant access sequence) 3. Use transaction code v/08 to define pricing procedure. 4. Assign this to your relevant sales area+ dpp+cupp. While specifying requirement, we can give reqt no.22 which specifies that plant has to be set. This is generally done for output taxes since output taxes depend upon the delivering plant. But directly there is no assignment between plant and pricing procedure.

SD Questions About Pricing Condition

The Most Important Tips in Pricing For SAP SD Module to crack interviews... Whenever we define our pricing procedures, we remain least interested in creating our own Condition Types,Condition Tables & Access Sequences. What we do is, we just define our own pricing procedures by using the existing condition types (i.e: PR00, K004, K007, KA02, KF00 etc.) & then assign that Pricing Procedure with Sales Area, Document Pricing Procedure & Customer Pricing Procedure .

After that we put the values against each Condition Types, mentioned in our Pricing Procedure by using the T-Code VK11. But we also need to know about the Condition Tables, Condition Types & Access Sequence Creation. So for that purpose we have to use the following T-Codes respectively : V/05, V/06 & V/07. Now it will become easy to create the same. Also to inform that, using T-Codes is more smarter than following paths through IMG screen. Utsav Mukherjee - utsavmukherjee143@hotmail. 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 systems 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. SAP SD Tips by : Vishwajit 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 ZOBPs plus/minus indicator to A which means only positive is allowed. *-- Arvind Rana 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.

Header Condition and Group Condition

What are header conditions? Header conditions are those which appear in the header level of any sales order. these conditions are to be entered manually and get distributed automatically and the basis for distribution are taken from the NET VALUE of items mentioned at item level. When we go to the conditions section in a sales order, where the details of pricing is mentioned, here we add these conditions. Whenever any Header Condition is used, it overrides the PR00 condition type. Examples of header condition.

HA00 - % Based Header Condition. RB00 - Absolute or numeric value which applies to all items. HB00 - Numeric value or Absolute value. *-- Vivek Chokshi

What is the difference between group condition and header condition? Group Condition: You can use this is feature of a condition type to apply price or discount for a material based on common property. Header Condition: This is a manual condition which you apply to header (Condition screen) of a sales document. This amount is applicable to all items. Usage of this feature is to apply price / discount for a specific group of materials. 1. You maintained a discount based condition record fbased on material group ( = 01 for example). You maintained scales also. Qty 1 - 10 11 - 50 51 - 150 Discount Rs. 100.00 Rs. 105.00 Rs. 110.00 etc.

2. You are creating a sales order for a customer with five different items with different quantities as below ITEM 1 - 25 Nos ITEM 2 - 3 Nos ITEM 3 - 12 Nos ITEM 4 - 27 Nos ITEM 5 - 62 Nos All the material is having the material group = 01. 3. While calculating the discount, because of this group condition, system add the quantities of items which have material group = 01. In the above example total quantity is = 109. System apply a discount of Rs. 110.00 to each item irrespective of the individual quantities. 4. If you have not activated the group condition feature, system determines the discount value based on individual item quantity which is as below. Discount ITEM 1 - 25 Nos Rs. 105.00 ITEM 2 - 3 Nos Rs. 100.00 ITEM 3 - 12 Nos Rs. 105.00 ITEM 4 - 27 Nos Rs. 105.00 ITEM 5 - 62 Nos Rs. 115.00 5. Is it clear now. Just try a sales order and see the out come Procedure to Test: 1. Create 3 materials. Maintain Material Group of each item is same.

2. Activate the condition type as a group condition. 3. Create a condition record for this condition type with scales. 4. Process a sales order for a customer with these three material with different quantities. 5. Check the outcome. What are the 8 steps involved in condition technique? By: Rohit Joshi It starts with an understanding of the factors that influences the Price. Lets say it depends on Customer and Material. With this understanding now we will start with the Table where we will pass the above parameters. There is a table 5 which already has Customer and Material so we can now copy and rename it or use the same table in our Pricing Procedure. T Code VOK0 Step 1. Define/Choose your Table (with the requirement parameters that influence the price) Step 2. Define your Access Sequence and include the above Table in your Access Sequence Step 3. Define your Condition Type (There are four Price Types Basic Price, Discount, Freight and Tax) and include your Access Seq. Its always better to copy the Price Types provided by SAP. Step 4. Now comes your Pricing Procedure where you include include Condition Types and format. Step 5. Now comes Procedure Determination where you specify the Document Pricing Procedure and Customer Pricing Procedure along with Sales Organisation, Distribution Channel. Step 6. Maintain Condition Records for your Condition Types I guess you can make it 8 Steps by dividing some of the main steps. Few important things to note is following.. 1. XD01 - Create Customer - Always ensure that you pick the right Customer Pricing Procedure from here. 2. VA01 - Sales Order - Ensure that you have the right Document Pricing Procedure from here 3. While Creating Access Sequence, check your Fields and ensure that they appear with any warning (Highlighted in Red) 4. Do not forget to mention your Access Sequence while defining your Condition Type 5. Always remember that your Procedure Determination has only Basic Price as Condition Type 6. Do not forget to mention the Range (From To) while creating your Pricing Procedure. I made most of the mistakes that appear above. Hope it helps.

Determine Sales Price with Shipping Point

You are trying to use shipping point as a key field (with sales org. distribution channel and ship-to party together) to determine the sales price. You created a condition table with the above key fields, and maintained the relevant setting (access sequence, condition type and pricing procedure). There is an error message in the sales order pricing analysis (access not made in the shipping point field). In the access sequence, you found that the shipping point fields document structure is KOMK. Can you put to item level field in the condition table and access sequence? Structure KOMK refers to header of the sales order, but shipping point of course is on item level. Youll have to do some settings to reach your goal, it is possible.

Step 1 Append structure KOMP. Do this by changing through SE11 the table KOMPAZ. This is the include for structure KOMP. Add a component e.g. ZZVSTEL with component type VSTEL. Save, activate. If you want to make more points, assign search help H_TVST to the component. Ask a programmer if you dont understand this part. Step 2 Change user exit MV45AFZZ. Say there that field ZVSTEL should be filled with information from your shipping point. Do this under part FORM USEREXIT_PRICING_PREPARE_TKOMP. The coding should be like tkomp-zzvstel = vbap-vstel. Save, generate. Step 3 Make a new table as you did before, but first maintain your new field in Condition: allowed fields. When you create your new table you will see you have two shipping points. With the button technical view you can check which one ZZVSTEL or VSTEL. Step 4 Finish with the steps you did before. That was ok. Now, you will see in your sales order that the shipping point is filled with information.

Why Do We Assign Division to Sales Organisation

In SAP, why do we assign division to Sales organisation not to distribution channel? In SAP Business Process Sales Area= Sales Org.+Dist.Channel+Division. Its Triangular intraction Sales organization / \ / \ Dist.Channel<----------------->Division Sales Org controls Distribution Channel and Division Distribution Channel: The channel that is choosen the organization to make their product reach the end customer. (Network) Division: Ex: HLL--------> Detergents, Out of Home,Food Products,Health Care Sectors/Departments TATA Motars: Trucks/Bus,Cars,Heavy Vechiles Etc... Please note it is not: Sales organization

| | Dist.Channel | | Division Division is an Oragaizational Unit. The Division in the Material Master is not an Organizational Unit that can be used to maintain related fields. It is a field which is used to uniquely assign a material to a Division.

Cross Selling : How To Configure

(1) Cross Selling: How to configure and the menu path details. (2) While creating individual order I face one error Plant not assigned to Controlling Area: How to configure controlling area and menu path. (3) Menu of path of subsequent Delivery Free of Charge. By : Ahmednsp Cross selling is a concept by which the business can improve the sales. By using this concept the business can offer combination material for ordered material. Ex: If the customer placed for the order for computer then computer stand can be suggested as a combination material. It can be mapped by using cross selling concept that uses condition technique. When the user raises the sales order and specifies ordered material then system automatically pup-up a box in which system displays suggested material Configuration settings: 1) Define determination procedure for cross selling: Path: - IMG - SD - Basic function - Cross selling - Define determination procedure for cross selling a) Create condition table: Here we define condition table ex: - material b) Maintain access sequence: Here we define access sequence ex: C001 and assign condition table ex:011 that we define in previous step. c) Define condition type: Here we define condition type C001 and assign it to access sequence C001 that we define in previous step. d) Maintain procedure: Go to new entries and define cross selling profile Ex: CS0001 and assign our condition type C001 that we define

in the previous step. 2) Maintain customer/document procedures for cross selling: a) Define customer procedure for cross selling: Here we define customer cross selling profile Ex: B -- cross selling b) Define documents procedure for cross selling: Here we define document cross selling procedure ex: B- cross selling c) Assign document procedure for cross selling to sales document: Choose sales document type OR and assign document cross selling procedure ex: B 3) Define and assign cross selling profile: a) Define cross selling profile: Go to new entries, specify cross selling profile key with description - Specify cross selling pricing procedure (CS0001) - Assign the pricing procedure (RVA001) - Specify cross selling dialog box indicator W If it is A dialog box appears only in request. It is blank dialog box appears in request and after date is released Check cross selling ATP indicator: If you check it , system carry out ATP check for cross selling product. b) Assign cross selling profile: - Go to new entries, specify sales area - Specify customer cross selling procedure B - Specify document cross selling procedure B - Assign cross selling profileCS0001 Maintain condition record for cross selling (VB41): Path: - Logistics - SD - Master data - Products - Cross selling - VB41 Specify condition type C001 Specify the order material, select condition line item Click on alternative material icon and maintain alternative material with cross selling delivery conditions options Blank Out bond delivery takes place regardless of main item A -- Out bond delivery only if main item has been partially delivered Go to VD02, sales area section of sales tab Assign customer procedure for product proposal - B Save it and exit

Go to VA01; raise the sales order with order material check the effect. 4) Path to created controlling area: Img-->Ent Str-->Defintio-->Controlling-->Maintain Controlling Area , here you can create controlling area

Customizing Customer Hierarchy in SD

How to configure and maintain the SD Customer Hierarchy? All the customizing is in SD/Master Data/Bussiness Partner/Customers/Customers hierarchy 1) Define hierarchy type: just put and ID and a name to the new hierarchy. 2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this informacition, in the order, you obtain the bussiness partner for each partner function. 3) Assign acount groups: you indicate which accounts groups are allowed for being part or your hierarchy. 4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas). 5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses hierarchy in pricing determination. It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount. Customer hierarchy setup, firstly decide the hierarchy type to be used. The standard is type A. You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you dont need that right? Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy. You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level. You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area. All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all

customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.

Backward and Forward Scheduling

Backward scheduling is the calculation of deadline dates: the arrival time at the customer site is calculated as the earliest possible goods receipt time at the customers unloading point on the requested delivery date. All four of the delivery and transportation scheduling lead times are subtracted from the customers requested delivery date to determine if this date can be met. The transit time, loading time, and pick/pack time are subtracted from the customers requested delivery date to calculate the required material availability date. The system calculates backward scheduling as follows: Requested delivery date minus transit time = Goods issue date Goods issue date minus loading time = Loading date Loading date minus transportation lead time = Transportation scheduling date Loading date minus pick/pack time = Material availability date By default, the system will calculate delivery dates the closest day, taking into consideration the working days of the shipping point and a rounding profile. In this case the system assumes a 24 hour work day and lead times can be entered in days up to 2 decimal points. This is referred to as daily scheduling. Precise scheduling calculated down to the day, hour and minute is supported. This allows the scheduling of a delivery within a single day. It is activated by maintaining the working hours for a particular shipping point. Backward scheduling is always carried out first. If the material availability date or transportation scheduling date is calculated to be in the past, the system must then use forward scheduling. Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities. The loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date.

SD material Determination based on availability check

For SD material Determination you can create a Substitution reason and on the Strategy field, the following info. is available: Product selection in the background is performed on the basis of the availability check. We want to have the material determination only in case on material shortage. We expect the Substitution reason to give us this functionallity. It does not hovever take the availabilty into account before substitution. We thought the worse case is to create a ABAP which is linked to the requirement field in the Procedure (OV13). Has anyone had the same requirement? Is this a bug or just incorrectly documented?

I also encountered this abnormally recently using material determination. In order to combat the problem, the first product substitution should be for the original material. Ive illustrated this below: Original Product: ABC Substitutes: DEF, XYZ In order to perform product substitution ONLY in the case of ATP failure for product ABC, structure the Material Determination record as follows: Material Entered: ABC Substitutes: ABC DEF XYZ There seems to be a devaition at availability check and or on a conceptual note still. Availability check can be configured both at requiremnt class and at the schedule line categories level. Whilst the availabilty check at the requirement class level via global and mandatory configuration the schedule line catgry availability check deals with the order. It is mandatory that the reqmnt class is flagged off for avlblty check and the schdelu line cat need not be. The following are the mandatory for Availability check to happen 1. Must be swithced on at the requirment class level and at the schedule line level. 2. Reqmnt type must exist by which a requiremnt class can be found 3. There must exist a plant and is defined 4.Checking group must be defined in Material Master records(it controls whthr the system is to create individual or collective reqmnt) A combination of checking gropup and checking rule will determine the scope of availbaility check. Basic Process of how Packing Works Lets say you want to pack a material shirt_jai in test_pack. Using MM01, create material type=packaging test_pack [SPRO] IMG-Logistics Execution-Shipping-PackingDefine Packaging Material Types Lets say JPAC. The settings that I chose: Plant determ. - Plant is entered manually in handling unit Pack. matl. cat. - Packaging materials Generate Dlv. Items - blank Number assignment - Number range interval HU_VEKP

IMG-Logistics Execution-Shipping-PackingDefine material group for packaging material Lets say JGRP IMG-Logistics Execution-Shipping-PackingDefine allowed packaging materials JGRP - JPAC MM02: Check settings for the materials First, test_pack Sales:General/Plant -> Matl. Grp. Pack. Matls: JGRP (Note) Sales:General/Plant -> Packaging Mat. Type: JPAC (Note) Basic Data 1 -> Material: JMAT Then, shirt_jai Sales:General/Plant -> Matl. Grp. Pack. Matls: JGRP Sales:General/Plant -> Packaging Mat. Type: Basic Data 1 -> Material: JMAT VL01N Outbound Delivery -> Packing Enter the materials at top and at bottom (Select shirt_jai and Edit - Pack) This is how the basic process of packing works. The Packing Process with an Example Example: You created a order for a material(R-1160 - hard disks) for a qty - 120 pieces. You need to create a delivery and A)pack 40 pieces each of the material are grouped together into larger cardboard boxes (PK-100 - shipping/packing material) and B)these 3 cardboard boxes are put into pallet (PK-095). Solution: A)Packing 40 pieces each of material (40 x 3 = 120 pieces) 1)Goto [VL02N] to change the delivery, you already created. Or you can do the following steps while you are creating a delivery also. 2)Go to pack icon. 3)In the upper section, enter the packing material (PK-100) 4)In the lower section, change the partial quantity to 40 of material R-1160. 5)Select both the lines of upper section and lower section and click the green ok. It generates a shipping unit/handling unit number. 6)Now, select both lines of upper & lower section & click the button per part. qty (New HU per part qty of

material) Check: click General Overview icon to see whether it packed 40 pieces of material in 3 cartons. B)Packing all 3 cartons in one big carton(PK-095) 1) from above screen, click pack HUs (pack shipping unit) 2)enter the packaging material (PK-095) in the upper section and select this line. 3)select 3 lines of PK-100 in lower section since you want to pack them in PK-095. 4)selecting both lines, click pack icon. 5)Now all the 3 cartons(PK-100 with 40 pieces each of material) are packed in one big carton (PK-095). Check: General overview icon. Then save the delivery. Implement the Product Allocation Functionality We are required to implement product allocation functionality in SAP R/3 (Enterprise Version). We tried to do the elaborate steps as per the implementation guide but are not successful. Can you kindly help by giving the simple steps for implementation. Please see if the following helps: Configuration Overview; Allocation Specific Usage 1.Allocation Procedure (OV1Z) The product allocation procedure is the parent of the entire allocation process. All materials that are to be included in the allocation scheme are required to have an allocation procedure assigned to it in the material master. In addition, as of release 4.0, it is in the procedure that the method of allocation is defined. The user has the opportunity to set an indicator to identify their choice of two different methods (discrete and cumulative allocation) to evaluate the quantities to be considered for product allocation. 2.Allocation Object (OV2Z) The allocation object is the root level of the allocation process where actual data is entered and planned in LIS. The object allows the user to further break down a procedure into smaller parts for future validation of components comprising a specific material 3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of an allocation procedure to an LIS information structure. Secondly, a character is assigned to the information structure to permit collective planning. Finally, the user can assign a step level to the procedure and information structure to sequence the order in which allocation quantities are checked. This functionality allows the user the opportunity to check product allocation against several product allocation scenarios, before the required quantity is confirmed 4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only valid if the allocation method flag has been set (OV1Z). If you have de-selected the method field, this functionality is not available. The consumption window indicates the number of past and future periods to be used in the allocation check. 5.Control Product Allocation (OV4Z) In order for the allocation process to function properly, allocation control records are created primarily to map allocation procedure steps to their corresponding objects so that the allocation data records can be located for validation. Secondly, validity periods must be established to indicate when the allocation control records are active. Finally, the user has the option of establishing a conversion factor per allocation control record to accommodate BOM listings of constrained materials

6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standard order processing functionality, the requirements class must have a flag indicating that allocation is relevant. 7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in the standard order processing functionality, the schedule line must have a flag indicating that allocation is relevant 8.Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the user must initially determine the level at which the allocation is to take place and the aggregation factor of the allocation quantities. In this step, the levels for the collective allocation search procedure are also identified. 9.Generate Masking Character (OV7Z) Upon completion of the level determination for the planning hierarchy, the collective allocation masking character must be generated to allow aggregation indicators to be established. This transaction simply reads the hierarchy established in the planning table and then generates a collective mask character for each level of the hierarchy 10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy was established. In order to complete the hierarchical set up, the collective allocation (mask character) hierarchy must now be maintained with the appropriate aggregation factors 11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocation process are the materials. Each material that is to be considered in allocation scenario must be mapped to an allocation procedure. In order entry, then, when a material is entered with a valid allocation procedure in the material master, the allocation data is verified prior to confirming the line item ordered 12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS information structures that can be used in the product allocation process. This report simply reads through the data dictionary and selects all the active information structures that contain the field product allocation object (KONOB) as the first field. This data can then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step to an information structure (previous step).

Pricing date based on delivery date

Used transaction VOV8. This configuration is by order type. There is a field called proposal for pricing date. There you can select pricing date as requested delivery date. A - Proposed pricing date based on the requested dlv.date (Header) This control is set at the document level as oppose to the condition type level (PR00). That means your other condition types such as surcharges and discounts are also determined using the requested delivery date. If your requirement is for PR00 to alone to be priced at delivery date then this will not work.

How pricing date is determine in the sales order and billing document? Where is the setting?
The pricing date is proposed based on the setting you make in the Sales document configuration. ( T code : VOV8) You have a field Prop.f.pricing date in the Requested delivery date / pricing date / purchase order date segment. Then you can choose the follwoing options: Blank - Indicates the current date as the pricing date A - Indicates the date based on the requested delivery date B - Indicates the date based on the order validity start from date And the pricing in the billing document is copied from thte sales order / Delivery document.. It again depends on the setting u have in the copy control from order - billng or delivery - billing. In the copy control, in the item settings you have two fields relavant for this. One is pricing source and the other is pricing type. The pricing sources are generally the order. But if you want you can change it to other values mentioned in the drop down, but this values have no effect if the pricing type is B. Any other value other than B in the pricing type will take the reference document price mentioned in the pricing source field. but for the pricing type B. The new price is determined in the billing order.