SAP SD Questions and Answers

This document is brought to you by => http://www.filemaze.ws/users/sepstica/


http://www.filemaze.ws/users/sepstica/



SAP®SD

Questions and Answers

Kogent Learning Solutions, Inc.

JONES AND BARTLETT PUBLISHERS

Sudbury, Massachusetts BOSTON TORONTO LONDON SINGAPORE





World Headquarters

Jones and Bartlett Publishers 40 Tall Pine Drive Sudbury, MA 01776 978-443-5000 [email protected] www.jbpub.com

Jones and Bartlett Publishers Canada 6339 Ormindale Way Mississauga, Ontario L5V 1J2 Canada

Jones and Bartlett Publishers International Barb House, Barb Mews London W6 7PA United Kingdom

Jones and Bartlett’s books and products are available through most bookstores and online booksellers. To contact Jones and Bartlett Publishers directly, call 800-832-0034, fax 978-443-8000, or visit our website www.jbpub.com.

Substantial discounts on bulk quantities of Jones and Bartlett’s publications are available to corporations, professional associations, and other qualified organizations. For details and specific discount information, contact the special sales department at Jones and Bartlett via the above contact information or send an email to [email protected].

Copyright © 2010 by Jones and Bartlett Publishers, LLC

Reprint & Revision Copyright © 2010 by Jones and Bartlett Publishers, LLC. All rights reserved. Original Copyright © 2009 by Dreamtech Press.

All rights reserved. No part of the material protected by this copyright may be reproduced or utilized inany form, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without written permission from the copyright owner.

Production Credits

Publisher: David Pallai

Editorial Assistant: Molly Whitman

Production Assistant: Ashlee Hazeltine





Senior Marketing Manager: Andrea DeFronzo

Associate Marketing Manager: Lindsay Ruggiero

V.P., Manufacturing and Inventory Control: Therese Connell

Composition: diacriTech

Art Rendering: diacriTech

Cover and Title Page Design: Scott Moden

Cover Image: © Bocanm/Dreamstime.com

Printing and Binding: Malloy, Inc.

Cover Printing: Malloy, Inc.

Library of Congress Cataloging-in-Publication Data SAP SD questions and answers/Kogent Learning Solutions, Inc. p. cm. Includes index.

ISBN-13: 978-0-7637-8198-9 (pbk.)

ISBN-10: 0-7637-8198-3 (pbk.)

1. SAP ERP. 2. Integrated software. 3. Materials management. I. Kogent Learning Solutions, Inc. QA76.76.157S255 2010 005.5–dc22 2009023558 6048

Printed in the United States of America

13 12 11 10 09 10 9 8 7 6 5 4 3 2 1





TRADEMARK ACKNOWLEDGMENTThis publication contains references to the products of SAP AG. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius and other Business Objects products and services mentioned herein are trademarks or registered trademarks of Business Objects in the United States and/or other countries.

SAP AG is neither the author nor the publisher of this publication and is not responsible for its content, and SAP Group shall not be liable for errors or omissions with respect to the materials.





TABLE OF CONTENTS Introduction Chapter 1 Introduction to SD Module Chapter 2 Basic Structure—SD Module Chapter 3 Master Data Maintenance Chapter 4 Basic Functions Chapter 5 Sales Chapter 6 Shipping Chapter 7 Billing Chapter 8 Sales Return, Credit, and Debit Memo Chapter 9 Miscellaneous Glossary Question Index





INTRODUCTIONCongratulations on buying the SAP®SD Questions and Answers book! This book is designed to suit theneeds of students or professionals who intend to prepare for interviews on SAP Sales and Distribution (SAP SD). When preparing for interviews, you may struggle to find a book that gives you an overview of important topics and valuable concepts that you feel might be asked about in an interview. Such a frantic search consumes a lot of time and energy, as you must go through countless books on the SD module. To solve this problem, we developed this concise text.

This book covers all of the most useful content necessary to emerge successfully from an interview. It is compiled in an easy-to-understand and self-explanatory manner. This book provides readers with a quick understanding of the SD module and its key features. This book discusses the following topics:

The concept of Enterprise Resource Planning (ERP) and its advantages; various modules in the SAP system; the role of SAP R/3 and the SD module; and the International Demonstration and Education System (IDES)

Application areas, needs, functions, advantages, and architecture of the SAP R/3 system

Master data in the SD module; the concepts of the shipping point and loading point

The concepts of pricing and quotation in the SD module; generation of invoices; purpose of transaction codes in the mySAP ERP system

The basic structure and needs of the SD module; role of the SD module in the SAP system; specifying customer tables for the SD module

Maintenance of master data in SD and the concepts of partner, text, and output determination

Basic functions of the SD module; the concepts of user exit, rebate processing, subtotals, payment terms, and pricing mechanism

The tax determination process; the access sequence; the material listing and exclusion; and individual, collective, and summarized requirements

The concepts of requirement class, requirement type, availability check, schedule line category, itemcategory, item group, outline agreement, and copy control; and the need of contracts and its types

The concept of BADIs, quick viewer, System Query, InfoSets; the process of defining shipping and loading points, customer master data, prices, quotations

The concepts of contract grouping, risk category, value contract, assortment module, master contract, referencing requirement, scheduling agreement, and the service and maintenance process





The sales process in the SD module and the concepts of inter-company and one-time customers and backorder processing

The process to define hierarchy types, tax relevance of master records; the process of blocking a customer

The concept of order and target quantities, item proposal, sales orders, quotation, backward scheduling, consignment stock, consignment fill-up, consignment pick-up, and sales document lists

The concept of the third-party order process; the process of shipping in the SD module; and the concepts of consumption modes, picking, warehouse management, and special stock

The billing process in the SD module; a comparison of billing and invoice; pro-forma invoice billingdocument

The role of cancellation; inter-company invoice; and a comparison between two types of billing: milestone and periodic

The credit and debit processes and the concepts of the invoice correction request and dunning





CHAPTER 1INTRODUCTION TO SD MODULE

1. List the SYSTEM modules that are included in the financial application component.

The following SYSTEM modules are included in the financial application component:

FI—Financial Accounting

CO—Controlling

EC—Enterprise Controlling

IM—Investment Management

PS—Project System

2. List the SYSTEM modules that are included in the human resource application (Human Capital Management) component.

The following SYSTEM modules are included in the human resource application component:

PA—Personnel Administration

PT—Personnel Time Management

PY—Payroll

3. List the SYSTEM modules that are included in the logistic application component.

The following SYSTEM modules are included in the logistic application component:

SD—Sales and Distribution

MM—Materials Management

PP—Production Planning and Control

LE—Logistics Execution

QM—Quality Management

CS—Customer Service





4. List the components the SD module consists of.

The SD module consists of the following components:

Basic Functions and Master Data in SD Processing (SD-BF)

Pricing and Conditions (SD-BF-PR)

Extra Charge (SD-BF-EC)

Availability Check and Requirements in Sales and Distribution

Credit and Risk Management (SD-BF-CM)

Material Sorting (SD-BF-AS)

Output Determination (SD-BF-OC)

Sales (SD-SLS)

Scheduling Agreements for Component Suppliers (SD-SLS-OA)

Customer Service Processing (SD-SLS-OA)

Foreign Trade/Customs (SD-FT)

Billing (SD-BIL)

Payment Card Processing (SD-BIL-IV)

Sales Support: Computer-Aided Selling (CAS)

Electronic Data Interchange/IDoc Interface (SD-EDI)

Shipping (LE-SHP)

Transportation (LE-TRA)

Reports and Analyses (SD-IS-REP)

Business Package for Internal Sales Representative

5. What is the purpose of transaction code in SYSTEM?

The transaction code is the short path to reach a specific screen in SYSTEM. Instead of going through the routine menu, you can enter the Transaction Code and then press “Enter,” which would directly take you to the specific transaction. For example, you can access the VA22 transaction code to reach the Change Quotation screen. However, the VA01 transaction code is used to create Sales document in SYSTEM.





6. What is meant by match code in SYSTEM?

The comparison key that helps you to find the key of a specific database record, depending on the field value entered in the record, is known as match code. On the basis of the match code, the system then displays a list of records from which you can select the appropriate one.

7. Explain the three main areas of customer master data.

Customer master is a part of the SD module and forms the basis for customer-related transactions. It is divided into three areas:

General Data—It is used for the maintenance of general customer details such as name, address, phone/fax nos., and so on.

Sales Area Data—It is used for Sales-related data maintenance.

Company Code data—It is used for accounts-related data maintenance.

8. What is the purpose of Implementation Guide (IMG Menu) in the SYSTEM?

The Implementation Guide (IMG Menu) is used to collectively group the areas that must be configured and customized, and form a basic structure of an organization in the System to run.

9. How will you maintain a company code in SYSTEM?

To maintain a company code, navigate the following menu path:

Customizing Implementation Guide (IMG Menu) > Enterprise Structure > Definition > Financial Accounting > Edit, Copy, Delete, Check Company Code.

10. What do you mean by Enterprise Resource Planning (ERP)?

ERP is a way to integrate processes and data of an organization into a single system to provide easy access and workflow in an organization. It refers to the way in which large organizations efficiently plan to use resources to their fullest.

11. List the advantages of implementing an ERP system in an organization.

The advantages of implementing an ERP system in an organization are as follows:

Various processes and workflow of an organization are integrated in a single system.

Efficient utilization of resources in an organization.

Ability to easily share organizational data across different departments.





Improves efficiency and productivity levels.

Lower costs.

Better customer service.

12. Specify the role of the Sales and Distribution (SD) module in an ERP system.

The SD module is an application module for supply-chain and operational performance management, and provides support to customers. This module is integrated with the Material Management (MM) and Production Planning (PP) functional modules. It also allows organizations to input sales price of products for customers and check for open orders.

13. Explain all modules in the system.

The modules in the system are as follows:

Financial Accounting (FI)—Regulates books of record including general ledger, accounts payable and receivable.

Controlling (CO)—Deals with the cost and management accounting in an organization.

Asset Management (AM)—Manages and tracks the value of assets in an organization.

Project Systems (PS)—Manages large or small projects in an organization.

Human Resources (HR)—Manages data and activities of human resource or Human Capital Management in an organization.

Plant Maintenance (PM)—Manages and maintains plant equipment, such as machines, in an organization.

Materials Management (MM)—Maintains material-related data, such as material purchase and inventory.

Quality Management (QM)—Maintains quality systems in an organization.

Production Planning (PP)—Maintains comprehensive planning for production in an organization.

Sales and Distribution (SD)—Maintains sales- and distribution-related data in the system, such as customer master, pricing, distribution channel, product line, and various aspects of sales and distribution.

Cross-Application (CA)—Manages workflow, workplace, and various cross-applications in an





organization.

14. What are the application areas of the R/3 system?

Application areas of the R/3 system are also called functional areas or functional modules. The following are the application areas:

Sales and Distribution

Human Resource Management

Production Planning

Fixed Assets Management

Material Management

Production Planning

Financial Management

Industry Solution

Workflow

Plant Maintenance

Quality Management

Controlling

Project System

15. What are the advantages of the R/3 system?

The following are the advantages of the R/3 system:

Functionality—Provides software solutions that cover all the commercial process and transactions used in an organization.

User-friendliness—Provides a uniform graphical user interface for all application areas for all users.

Flexible structure— Provides flexible systems structure, as flexibility is an important aspect in every department.

Real-time integration—Provides all the information on the basis of real-time scenarios.

Enterprise-wide integration—Provides integration among all the modules in a system.





Three-tiered architecture—Provides enterprise-wide and three-tiered architecture that includes presentation, application, and database application. This architecture provides flexibility and the ability to make changes according to the organizational needs.

Concurrent engineering—Helps in building the real-time workflow application links that are essential and required.

Desktop integration—Provides the export utility to export the data to the desktop of a computer.

Individual solutions—Provides system-controlled customizing procedures to build solutions and to fulfill the individual requirements.

16. How does the R/3 system integrate all the application modules?

Integration of all application modules has been done by the R/3 basis system. This system helps in the integration of various modules in the following manner:

Guarantees the optimal integration by providing runtime environment.

Provides administration tools for the entire system.

Provides equilibrium architectural framework for enhanc- ing the system.

Provides portability of the complete system.

17. What are the functions of the R/3 system?

The R/3 system provides the following functions:

Integration—Provides a complete integration of the various data transfers, which, in turn, is helpful in making good quality reports.

Saving time with integration—Helps reduce the time needed to close the books of accounts.

Automation of consolidation procedure—Saves time and cost as there is no need to enter all the documents manually.

Customizing the software according to the needs—Provides the facility of creating new programs whenever the requirement arises.

Cost-effective audits—Provides the facility to the auditor for performing interactive analysis of special infor mation.

Easy to learn and use—Provides context-sensitive functions and extensive online documentation thatis easy to understand and learn.





Information System—Includes functions for creating reports. It provides information through exceptional and interactive reporting.

International accounting—Allows parallel-valuation approaches at all levels for external and internalaccounting purposes by using different currencies.

18. What is R/3 system landscape?

Landscape is an architecture of servers. The following are three different landscapes for SYSTEM:

Development—In a development server, a technical/function person creates the programs or configures the system as per the company’s requirement and sends it to the quality server.

Quality—In this server, team members test the development/configuration with various parameters. Then the final configuration is transported from development server to production server.

Production—Through this server, the software is finally handed over to the client for users.

19. What are the databases supported by the SYSTEM R/3 system?

The SYSTEM R/3 system provides support for the following databases:

ADABAS D

DB2/400

DB2/Common Server

DB2/MVS

Microsoft SQL Server

Oracle

Oracle Parallel Server

20. What is the role of an ABAPer in the SD module?

The ABAPer uses the data transfer tools, such as BDC/LSMW, to upload huge data, such as customer master data. ABAPer writes the Z-Development and programs as specified by the functional consultant as per the business requirements.

21. Who can be the business partner in SYSTEM?

A business partner in the system can be:

Customer





Vendor

Contact person

Employee recognized as sales personnel

Customized as per the specific requirement of business

22. Explain BADIs and its relevance.

In the R/3 system, system provides an enhancement technique called business add-ins (BADIs). BADIs are business transaction events helpful to bundle program, menu, and screen enhancements into a single business add-in.

23. How do you define BADIs?

The following menu path can be navigated to define BADIs:

SYSTEM Menu > Tools > ABAP Workbench > Utilities > Business Add-Ins > [SE18]—Definition.

24. What is the Quick Viewer?

The Quick Viewer is a very useful tool to create reports in system. It helps create reports without actually doing any programming. It is similar to an ABAP Query; however, it does not have all the capabilities that the ABAP query procedure has.

25. What are System Query and InfoSets? How can you create InfoSets?

The System Query is a tool used to create reports with little coding. It provides more flexibility than the quick viewer, as with the modification of code a wider functionality can be achieved. To create a query we need to create InfoSets to hold actual data. The following menu path can be navigated to create InfoSets:

SYSTEM Menu > Tools > ABAP Workbench > Utilities > SYSTEM Query > [SQ02] – InfoSets.

26. Which kinds of servers are used to define the functioning of a system?

There are three servers in the SYSTEM application modules:

Development server

Quality server

Production server





27. What is the role of ERP in a business environment?

Enterprise Resource Planning (ERP) is a software package that is designed for the integrated management of the various business processes, such as inquiry, order placement, invoicing, and billing.It initially was designed for manufacturing industries to manage the core business areas, such as production and finance. With the popularity of the ERP package, its functionalities also extended to cover the complete business management.

28. Define IDES.

IDES stands for International Demonstration and Education System, and is an application used to quickly learn and implement ERP.

29. What is R/3?

R/3 means the three-tiered architecture used by the system. The three tiers are as follows:

Database Server

Application Server

Presentation Server





CHAPTER 2BASIC STRUCTURE—SD MODULE

1. What is a division in the Sales and Distribution module?

A division refers to a product group that can be defined for a wide range of products or services. In sales organizations, there can be multiple divisions, which can also include customer-specific arrangements.

2. What do you mean by a sales office in the SD module?

The geographically located unit of a sales organization refers to a sales office in the SD module.

3. What do you mean by a shipping point and loading point in the SD module?

A shipping point refers to the point from which the deliveries of products are shipped. One or more plants can have the same shipping point. However, the subdivision of a shipping point refers to a loading point, which is manually entered in the header data of a delivery as per customization.

4. What do you mean by the terms sales office, sales groups, and sales employee in the SD module?

The geographical groups created for an organization to structure a sales team are known as sales offices. A sales office is then assigned to one or more sales areas. The staff of a sales office is divided into sales groups, and then sales employees are assigned to a sales group. A sales employee refers to theindividual with personnel master records that are used to manage data of that sales employee.

5. How can you maintain a sales office and sales group in the system?

Navigate the following IMG menu path in the SD module to define a sales office:

Customizing Implementation Guide (IMG Menu) > Enterprise Structure > Definition > Sales and Distribution > Maintain Sales Office.

Navigate the following menu path in the SD module to define a sales group:

Customizing Implementation Guide (IMG Menu) > Enterprise Structure > Definition > Sales and Distribution > Maintain Sales Group.

6. How can you define or create a shipping point?

To define or create a shipping point, navigate the following menu path:





Customizing Implementation Guide (IMG Menu) > Enterprise Structure > Definition > Logistics Execution > Define, Copy, Delete, Check Shipping Point.

7. What do you mean by business area and how can you assign a business area in the SD module?

A business area is a subdivision of a company code for accounting purposes. On the basis of the business area, you can draw financial reports. Navigate the following menu path to assign a business area:

IMG > Enterprise Structure > Assignment > Sales and Distribution > Business Area Account Assignment.

The determination rule for business area is as follows:

Plant and Item Division

Sales Area

Sales Organization or Distribution Channel or Item Division

8. What do the prefixes VA, VL, VT, and VF of a transaction code stand for?

The definitions for the prefixes VA, VL, VT, and VF of a transaction code are as follows:

VA—Sales Order

VL—Delivery

VT—Shipment

VF—Billing

9. What do the suffixes 01, 02, and 03 of a transaction code represent?

The suffixes 01, 02, and 03 of a transaction code represent the following:

01—Create

02—Change

03—Display

10. How can you configure the sales districts?

Navigate the following menu path to configure the Sales district:





Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Master Data > Business Partners > Customers > Sales > Define Sales Districts [OVR0].

11. How can you assign a shipping point to a plant?

You can assign a shipping point to a plant by navigating the following menu path:

Implementation Guide (IMG Menu) > Enterprise Structure > Assignment > Logistics Execution > Assign Shipping Point to Plant.

12. Suppose that a new info structure is created and the update rules are activated for it. How would you then transport it to a production client?

After the approval from the QA team, the info structure can be transported in the time when no documents are created or posted.

13. How is the company code created?

Perform the following steps to create the company code:

Customization Implementation Guide (IMG Menu) > Enterprise Structure > Definition > Financial Accounting > Define Company Code.

14. What is the relationship between sales organizations and company codes?

There is a many-to-one relationship between sales organizations and company codes.

15. Give the name of the central organizational element used in purchasing.

The central organizational element used in purchasing is called the Purchase Organization.

16. What is the relationship between sales organizations or distribution channels and plants?

There are many-to-many relationships between sales organizations and plants.

17. What is the relationship among sales organizations, plants, and company codes?

There are many-to-many and many-to-one relationships among sales organizations, plants, and company codes.

18. Mention the total number of the shipping points that can be assigned to a sales organization.

You do not assign shipping point to sales organization, but assign it to plants only.









CHAPTER 3MASTER DATA MAINTENANCE

1. List the transaction codes used to create a customer in the SD module.

VD01 is the transaction code used to create a customer in the SD module. To create customer centrally, the transaction code is XD01.

2. List the basic elements of a customer master record.

The following are the basic elements of a customer master record:

General Data

Company Code Data

Sales Area Data

3. Which menu path is navigated to access the account groups defined in finance?

Navigate the following menu path to access the account groups defined in finance:

Customizing Implementation Guide (IMG Menu) > Financial Accounting > Accounts Receivable and Accounts Payable > Customer Accounts > Master Records > Preparations for Creating Customer Master Records > Define Account Groups with Screen Layout (Customers) [OBD2].

4. State a few examples of common material types.

The examples of common material types are as follows:

DIEN—Service Item

HALB—Semi-Finished Good

FERT—Finished Good

HAWA—Trading Item

NLAG—Non-Inventoried

ROH—Raw Material

UNBW—Non-Valuated Item





5. List a few common material master views.

The following are a few relevant material master views:

Accounting 1, 2

Material Requirements Planning (MRP) 1, 2, 3

Purchasing

General Plant Data Storage 1, 2

Sales Org Data 1, 2

6. How can you create Customer-Material Info Records in the SD module?

Navigate the following menu path to create Customer- Material Info Records:

SYSTEM menu > Logistics > Sales and Distribution > Master Data > Agreements > Customer Material Information | [VD51] – Create.

7. Which transaction code and movement type helps in adding stock (from legacy stocks) for the newly created material type into a particular plant after creating a new material type in SYSTEM?

For such a situation, you can use transaction code MB1C and the movement type 561.

8. How can you define your own hierarchy types?

Perform the following steps to define your own hierarchy type:

Enter a one-character alphanumeric key and description.

Enter a default partner function that is valid for the hierarchy type.

Save the hierarchy type.

9. How will you create material in both company codes while working on inter company sales?

While working on inter company sales, the transaction code MM01 is used to create material related to the plant and sales organization. For the other company code, this material can be extended if the server being used is common.





10. Which factors do you need to verify if the tax field in the customer master and material master is not displayed?

We need to make sure that for all the countries in the transaction code OVK1, we have defined a tax category. At the same time, we also need to verify whether the tax classes are defined in OVK3 and OVK4.

11. List the sequence of steps performed by the underlying system to determine tax number and tax classification.

The underlying system uses the following sequence of steps to determine tax number and tax classification:

If the payer has a VAT registration number and is identical to the sold-to party, the tax number and tax classification are copied from the payer. The tax number is copied on the basis of the “country of destination relevant for taxes.”

If step 1 does not apply, and if the ship-to party has a VAT registration number and the sold-to party does not have the same, tax number and tax classification are copied from the ship-to party.

If step 2 does not apply, then tax number and tax classification are copied from the sold-to party.

12. How do you define tax relevancy of master records?

The following menu path is navigated to define tax relevancy of the master record:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Taxes > Define Tax Relevancy of Master Records > Material Taxes.

13. Imagine you are defining tax determination rule for a country which has regional tax code also. How will you define regional code?

The following menu path is navigated to defi ne regional tax codes:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Taxes > Define Regional Codes > Define County Code.

14. What are the transaction codes that are used to create and change the customer master?

The following are certain transaction codes used to create and manipulate the customer master:

XD01—Creates a customer

XD02—Changes a customer





XD03—Displays a customer

XD04—Changes customer changes centrally

XD05—Blocks a customer centrally

XD06—Marks a customer for deletion

XD07—Changes a customer account group

XD99—Maintains customer maintenance

XDN1—Maintains number ranges for a customer

15. Which transaction code is used to view messages in SYSTEM?

The transaction code SE91 is used to view all messages in SYSTEM.

16. What do you understand by transferring the legacy data to SYSTEM?

It means to transfer the legacy data to the newly installed and confi gured system. The data such as customer and material maintained by an organization before the installation of ERP system is known asthe legacy data. You can use various tools to transfer the legacy data to the system, such as Batch Data Communication (BDC) and Legacy System Migration Workbench (LSMW) programs.

17. Specify a way to block the transaction for a material flagged for deletion.

You can block the transaction for a material flagged for deletion by customizing the sales status fieldin the sales organization view of the material master.

18. List the master records from which a sales order receives the organizational data for a specific sales area.

The master records from which a sales order receives the master data are as follows:

Customer Master Record

Material Master Record

19. Suppose you have to automatically transfer the payment method from customermaster to sales order. How can you do that?

The payment method can be automatically transferred from the customer master to the sales order byusing the “userexit_move_field_to_vbkd” user exit in the MV45AFZZ report along with the following coding:





DATA: via LIKE knb1-zwels.IF vbkd-zlsch IS INITIAL.IF NOT vbak-kunnr IS INITIAL.SELECT SINGLE zwels INTO viaFROM knb1WHERE bukrs = vbak-bukrs_vfAND kunnr = vbak-kunnr.Vbkd-zlsch = via(1).ENDIF.ENDIF.

20. Which document do you use to enter shipping conditions and how are these conditions used in determining the shipping point?

The customer master record in the shipping screen and in the sales document type is used to specify shipping conditions. The shipping conditions are used to decide the shipping point by copying them into the sales document during order creation.

21. Suppose that you have blacklisted a customer and now want to block that customer. How can you do that?

A customer can be blocked by navigating the following menu path:

SYSTEM Menu > Logistics > Sales and Distribution > Master Data > Business Partner > Customer> Block [VD05].

22. Give the menu path to define the customer hierarchy types.

The menu path to define the customer hierarchy types is:

Implementation Guide (IMG Menu) > Sales and Distribution > Master Data > Business Partners > Customers > Customer Hierarchy > Define Hierarchy Types.

23. Give the menu path to set the partner determination for hierarchy categories.

The menu path to set the partner determination for hierarchy categories is:

Implementation Guide (IMG Menu) > Sales and Distribution > Master Data > Business Partners > Customers > Customer Hierarchy > Set Partner Determination for Hierarchy Categories.

24. List the items for which you can define the customer hierarchy.

The customer hierarchy can be defined for the following:

Customer Master

Sales Document Header





Sales Document Item

Delivery

Shipment

Billing Header

Billing Item

Sales Activities (CAS)

25. Give the menu path to assign a sales area to the customer hierarchy.

The menu path to assign a sales area to the customer hierarchy is:

Implementation Guide (IMG Menu) > Customer Hierarchy > Assign Sales Areas.

26. Give the menu path to assign the hierarchy type for pricing by sales documents to the customer hierarchy.

The menu path to assign the hierarchy type for pricing by sales documents to the customer hierarchyis:

Implementation Guide (IMG Menu) > Sales and Distribution > Master Data > Customers > Customer Hierarchy > Assign Hierarchy Type for Pricing by Sales Document Type.

27. Give the menu path to define the product hierarchies.

The menu path to define the product hierarchies is:

Implementation Guide (IMG Menu) > Logistics-General > Material Master > Settings for Key Fields > Data Relevant to Sales and Distribution > Define Product Hierarchies [OVSV].

28. Suppose that you create a new customer account group and the system increments it by an arbitrary value. What would you do?

The existing problem is called number range buffering. You need to perform the following step:

Transaction code > SNUM > Debitor > Change Mode and Change the Numbers.

29. What are the customer tables for SD module?

The following are the customer tables of the SYSTEM SD module:

KNA1—general data





KNB1—customer master

KNB4—customer payment history

KNB5—customer master

KNBK—bank data

KNKA—credit management

KNKK—credit control area data

KNVI—sales area data

KNVP—partner function key

KNVD—output type

KNVS—customer master ship data

KLPA—customer vendor link





CHAPTER 4BASIC FUNCTIONS

1. List the standard output types in the Sales and Distribution module.

The following are the standard output types in the SD module:

Sales Order Confirmation—BA00

Outbound Delivery Note—LD00

Billing Document—RD00

Inquiry—AF00

Quotation—AN00

Contract—KO00

2. What do you mean by user exit?

A user exit is implemented as a call to a function module. A customer’s developer can access data objects and program components with the help of user exit. User exits are used in case there are some specific needs that are not met by the standard system.

3. What is the need of user exit?

User exits are used in case there are some specific needs which are not met by the standard system. The purpose of user exit is to add a particular business-related functionality to standard SYSTEM.

4. What do you mean by rebate processing?

Rebate refers to a specific discount given to a specific customer for sales within a specific period of time. For example, a customer gets 2% discount on buying 500 pounds in a particular month, and another customer gets 5% discount on buying 2000 pounds in the same month.

5. Imagine you are facing a problem with Logistics Information System (LIS), as a result of which, after client copy, your test system does not update LIS info structures. When you save a delivery, sales order, or billing document, an error message “update was terminated” is displayed. How can you resolve such a problem?

In such a problem, you should generate the info structure and update group again for the client in





which your error message is displayed.

6. What do you mean by subtotals?

Subtotals are generally used in pricing procedures. Subtotals are not tied to condition types; however, you can control the value entered in the fields by assigning subtotals within the pricing procedure.

7. Imagine you have defined a condition type Z004 in accordance with the conditiontype K004. After creating the Z004 condition type, you try to create a condition record in transaction code VK31 in the section Discount/Surcharges > By Material. While creating a condition record in VK31, the error message “Table 304 is not defined for use with condition type ZEC1” is displayed. How you can resolve such an error?

Perform the following steps to create a new condition type maintainable through VK31:

Create pricing report through V/LA transaction code.

Include the required tables.

Extend the price area menu through SE43, where area menu = COND_AV.

8. How can you configure a distribution channel as a default in the transaction fieldthat requires distribution channel data?

Perform the following steps to set a distribution channel as default for the transaction field that requires distribution channel data:

Use the SU01 transaction code and enter the user ID.

Go to the parameters tab page and add VTW parameter.

Enter the default distribution channel in the parameter value.

9. Can you perform an availability check on a plant by excluding a storage location?

Yes, you can perform availability check in MM by excluding a storage location.

10. What is the purpose of a rebate agreement?

An agreement between a sales organization and a customer specifying a special discount provided toa customer for a specific product based on the sales volume for a specified duration is known as rebate agreement. You can navigate the following menu path to define a rebate agreement:





Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Billing > Rebate Processing > Rebate Agreements > Define Agreement Types.

11. List the transaction codes with respect to rebate agreement processing.

The following are the transaction codes in the context of rebate agreement processing:

VBO1—Create

VBO2—Change

VBO3—Display

12. What do you mean by payment terms?

The terms of payment that a company offers to a customer based on which a discount may be given for prompt payment or penalties that can be charged in case of late payment is known as “payment terms.”

13. What is the purpose of condition indexes and how can you activate them?

The purpose of condition index is to search all records for a specific condition type. For example, you can search all the condition records for the condition type PR00. You can activate the condition index in the customizing screen for the condition type PR00 by navigating the following menu path:

SPRO > Sales & Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types > Maintain Condition Types > Enter PR00.

14. What is the role of user exit?

The empty ABAP forms at particular points in the standard system, where the system allows customers to make enhancements to the way the code functions, are called user exits. These are helpful tools to meet the specific business requirements.

15. Which transaction code is used to view enhancements in the system?

The transaction code SMOD can be used to view all the enhancements in the system.

16. Which menu path should be followed to view all the enhancements in the system?

The following menu path can be navigated to view all the enhancements in the system:

SYSTEM Menu > Tools > ABAP Workbench > Utilities > Enhancements > Definition.





17. List user exits for partner determination.

The following are the user exits for partner determination:

EXIT_SYSTEMLV09A_001




18. How do you create user groups?

The following menu path can be navigated to create user groups:

SYSTEM Menu > Tools > ABAP Workbench > Utilities > SYSTEM Query > User Groups.

Alternatively, you can also use the transaction code SQ03 to create user groups.

19. Describe the relevance of condition technique in sales and distribution (SD).

The condition technique is the most important technique used for configuration in the sales and distribution module. It is used for different types of determinations in SD such as pricing, text determination, output determination, account determination, and material determination. It is called condition technique, because it provides a technique to select one from alternative choices, based on conditions, access sequence, and condition tables.

20. Which rounding rules are available in the course of maintaining condition types?

The following three rounding rules are available while maintaining condition types:

Commercial rounding—In case of commercial rounding, a value less than 5 is rounded down to nearest value, while the values greater than 5 are rounded up to the nearest value.

Always round up—In this case, regardless of whether it is greater than or less than 5, the value is always rounded up to the nearest value.

Always round down—In this case, regardless of whether it is greater than or less than 5, the value is always rounded down to the nearest value.

21. How do you begin with defining and assigning pricing procedures?

Navigate the following menu path to begin with defining and assigning pricing procedures:





Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and Assign Pricing Procedures > Maintain Pricing Procedures.

22. Imagine that you have allocated a discount condition type Z007. How will you create a condition record for this condition type?

Navigate the following menu path to create condition record for the condition type Z007:

SYSTEM Menu > Logistics > Sales and Distribution > Master Data > Conditions > Select Using Condition Type > Create.

23. List the sequence of steps used to customize pricing procedure.

Perform the following steps (in sequence) to customize pricing procedure:

Put the required fields into the field catalog.

Create the required condition tables.

Create the required access sequence.

Assign the condition tables to the access sequence.

Create the condition types.

Assign the access sequence to the condition types.

Create the determination procedure, if necessary, and assign the condition types to it.

Assign the determination procedure.

Lastly, create the condition records.

24. What is the relevance of pricing procedure and how is it configured in the SD module?

As the name suggests, pricing procedure is responsible for mapping the needs of business and underlying processes. It calculates the pricing, discounting, and taxes. The pricing procedure can be configured by navigating the following menu path:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and Assign Pricing Procedures > Maintain Pricing Procedures (Transaction Code V/08).





25. Which topics in SD have impact on pricing procedure?

The following topics in SD have impact on pricing procedure:

Credit management

Payment terms

Cost of sales

Rebate

26. How do you activate pricing for item category?

We can activate pricing for item category by navigating the following menu path:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Pricing by Item Category > Activate Pricing for Item Categories.

27. Which menu path do you follow to activate cost determination for item category?

The following menu path is navigated to activate cost determination for item category:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Pricing by Item Category > Activate Cost Determination for Item Categories.

28. What is the relevance of the condition exclusion group?

The condition exclusion group is a technique to ensure that the customer does not receive all types of discount; rather, the customer receives the best discount of all given discount condition types. A best condition type is chosen from this “Condition Exclusion Group” based on your configuration.

29. How do you maintain condition exclusion group?

The following menu path is navigated to maintain condition exclusion group:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Pricing > Condition Exclusion > Condition Exclusion for Groups of Conditions > Define Condition Exclusion Groups.

30. How do you assign condition types to the exclusion groups?

The following menu path is navigated to assign condition types to the exclusion groups:





Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Pricing > Condition Exclusion > Condition Exclusion for Groups of Conditions > Assign Condition Types to the Exclusion Groups.

31. What do you understand by condition supplement?

The condition supplement is a group of conditions that is applied every time that a condition is matched. Condition supplements will come for a condition if you have maintained pricing procedure under master data of the condition.

32. Explain the tax determination process in brief.

The tax determination is performed automatically by system. The tax determination is based on the structure of the organization, country, region, or city of the plant delivering the products and the country of the receiving customer. It works in coordination with the tax relevancy indicators on the customer master record and material master record. Condition technique is used for the tax determination procedure.

33. How do you define tax determination rules in SD?

The following menu path is navigated to define tax determination rules in SD:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Taxes > Define Tax Determination Rules.

34. How do you define dependencies of revenue account determination?

The following menu path is navigated to define dependencies of revenue account determination:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Account Assignment/Costing > Revenue Account Determination > Define Dependencies of Revenue Account Determination.

35. How do you maintain requirement and formulas?

The following menu path is navigated to maintain requirements and formulas:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > System Modifications >Routines > Define Copying Requirements.





36. Where and when are requirements and data transfer routines available to be assigned within the system?

The general rule of availability of requirements and data transfer routines are as follows:

Copying requirements are available to be assigned during transfer of data between documents and texts.

Data transfer routines are available during copying between documents and texts.

Requirements are available to be assigned to any access sequence, as well as before most functions.

Formulae are available to be assigned during pricing determination.

37. List the divisions of data transfer routines.

The data transfer routines are categorized as:

Orders

Deliveries

Billing documents

Sales activities

Shipping units

Texts

Text names

Shipments

38. How do you define and assign account keys in SD?

The following menu path is navigated to define and assign account keys:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Account Assignment/Costing > Revenue Account Determination > Define and Assign Account Keys.

39. How do you set price limits in SD?

Price limits can be set by navigating the following menu path:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types > Define Upper/Lower Limits for Conditions.





40. Imagine you are maintaining a pricing procedure. In which circumstances will you use the “From” and “To” columns?

The “From” and “To” columns are used in the following two circumstances:

To define the range for a subtotal

To define the basis for a calculation

41. List the transaction codes related to condition record selection by condition type.

The following are the transaction codes relating to condition record selection by condition type:

[VK11]—Creates a condition record

[VK12]—Changes a condition record

[VK13]—Displays a condition record

42. What is access sequence in material determination?

The access sequence is a sequence of steps that are used by the underlying system to obtain a condition record used for material determination. All of the condition records have specific values assigned to them, which determine the order in which the system will read the access sequence. The system starts reading the access sequence with the lowest number step assigned to it and tries to process everything assigned to that particular access sequence through the condition table and fields. The whole process is called “condition technique.”

43. How do you maintain access sequence in material determination?

Navigate the following menu path to define the access sequence:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Material Determination > Maintain Prerequisites for Material Determination > Maintain access sequences.

44. How do you define/maintain checking group?

Checking group is used for the purpose of availability check and transfer of requirement. Checking group is maintained in material master and on the basis of this, the requirement is passed to Material Requirement Planning (MRP). The checking group may be defined so as to pass on the requirement on per-transaction basis or may be a day’s collective requirement to MRP. Navigate the following menu path to define a checking group:





Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Availability Check and Transfer of Requirements > Availability Check > Availability Check with ATP Logic or Against Planning > Define Checking Groups.

45. How do you maintain condition type for material determination?

Navigate the following menu path to define a condition type:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Material Determination > Maintain Prerequisites for Material Determination > Define Condition Types.

46. How do you maintain condition tables for material determination?

Navigate the following menu path to maintain condition table:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Material Determination > Maintain Prerequisites for Material Determination > Display Condition Tables.

47. List the steps for a condition technique.

Perform the following steps to create a condition record:

Place the required fields into the field catalog.

Create condition table.

Create access sequence.

Assign condition table to the access sequence.

Create the condition types.

Assign the access sequence to the condition types.

If needed, create the determination procedure and assign the condition types to it.

Assign the determination procedure.

Create the condition records.

48. Explain material listing and exclusion.

When we deal with many customers, we need to keep track of what they purchase. The material listing and exclusion process is used to list those items that are purchased by a particular customer and





exclude the items that are not purchased by that particular customer. The material listing and exclusion process uses the condition technique to determine the items to be listed and excluded. It is applicable on the two ingredients, sold-to party and the payer.

Transaction code used for material listing and exclusion is VB01.

Condition types used for material listing and exclusion, respectively, are as follows:

A001 ListingB001 Exclusion

49. Define Material Requirements Planning (MRP) and Transfer of Requirements (TOR).

While creating the sales order, the items ordered in the sales order creates a schedule line consisting of the customer-requested delivery date and quantity to be delivered. This information is then transferred to the Material Requirement Planning (MRP) module. Based on the sales order created, the MRP transfers the requirement (TOR) to the Material Management and Production Planning module.

TOR ensures that the ordered materials ordered can be delivered for the requested delivery date. It works in coordination with the Material Management (MM) and Production Planning (PP) modules.

50. How do you configure transfer of requirements?

Navigate the following menu path to configure transfer of requirement:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Availability Check and Transfer of Requirements > Transfer of Requirements.

51. Differentiate individual and collective requirements.

You can have a transfer of requirement either with an individual requirement or with collective requirements.

In the individual transfer of requirements, a single transfer of demand occurs to the MRP for each schedule line. In case of individual transfer, the order quantity, the sales document number, the item number, and requirement class for each schedule line for which the demand has been created are shownby the requirement overview.

The collective requirements are a group of requirements created over a certain period of time such ason the daily basis, weekly, or monthly, and transferred to MRP. In this case, requirement overview doesnot show the single transactionwise descriptions of the requirements; rather, it shows details of the group of requirements. The collective requirement is benefi cial for the organizations that deal with a large volume of sales orders daily.





52. List the key transaction codes relating to integration between logistics in MM and SD.

The following are the key transactions related to integration between logistics in MM and SD:

MMBE—Stock Overview

MD04—Stock/Requirement List

MB53—Plant Stock Availability

CO09—Availability Overview

MB52—Warehouse Stock

MB5M—Expiration Date List

MB5B—Stock for Positioning Date

MB5T—Stock in Transit

MBBS—Valuated Special Stock

MBLB—Stock with Subcontractor

53. List a menu path to access stock requirements lists.

The shortest and simplest menu path to access the stock requirement list is as follows:

SYSTEM Menu > Logistics > Materials Management > Material Requirements Planning (MRP) > MRP Evaluations > Stock/Requirements List [MD04].

54. What are the data on which the transfer of requirement is dependent?

The transfer of requirement is dependent on following data:

Requirements type

Requirements class

Checking group

Schedule line category

55. What are the criteria you need to ensure for the availability check and transfer of requirement to be carried out?

The following are the important settings at material master level for transfer of requirement and





availability check:

Maintain Strategy Group at MRP1 page

Maintain MRP Group at MRP1 page

Maintain Planning Strategy

Maintain Item Category and MRP Type

Procurement or Production Time at MRP2 pages

Replenishment Lead-Time at General/Plant Data Page and MRP Page

Plant for Material in Material Master

In addition, you also need to maintain the following settings:

Schedule Line allowed at Item Category Level

Active Availability Check at Schedule Line and Requirement Class Level

In Transaction Code OVZ9 – Availability Check Controls Defined with Respect to Checking Rule and Checking Group

56. What are the requirement classes and requirement types?

For all the sales document types, the requirement class is the controlling factor for availability checkand transfer of requirements. It is used as the default source of data from which the underlying system inserts data into sales order. The system uses search strategy to find requirement type and, on the basis of the searched requirement type, a requirement class is assigned. In this way, a requirement class is determined. Following is the search strategy used to determine requirement type:

Through strategy group of MMR

Through MRP group of MMR

Through MRP type of MMR

Through material type of MMR

Through item category and MRP type (OVZ8)

Through item category only

Moreover, if the system still fails to determine the requirement type, then it is assumed that transaction is not relevant for availability check or transfer of requirement.





57. How do you define requirement class?

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Availability Check and Transfer of Requirements > Transfer of Requirements > Define Requirements Classes.

58. What is requirement type?

After creation of the requirement classes, we need to assign a requirement type to the requirement class. A requirement class can be assigned with more than one requirement type; however, a requirement type cannot be assigned to more than one requirement class. The requirement type can be changed during creation of sales order.

59. List the search strategy that the underlying system uses to determine the requirement types.

The following are the predefined search strategies that the underlying system uses to determine the requirement types:

The system uses strategy group in the material master to find a requirement type.

If the strategy group is not maintained, the system uses MRP group to determine a requirement type.

If the MRP group is not defined the underlying system uses material type to determine a requirement type.

If none of these is found, the system follows a special rule and tries to determine a requirement type with the help of item category and MRP type.

When the MPR type is not defined, the system uses only the item category to determine the requirement type.

60. Define the role of availability check in SD.

Availability check plays an important role in the business sales process. It is a process to determine whether the delivery quantity requested by a customer can be made available for shipping on the delivery date. The availability check is performed at the plant level.

61. Define the types of availability checks.

The following are the three types of availability checks:

The availability check on the basis of Availability to Prom- ise (ATP) quantities.

The availability check against product allocation.





The availability check based on the stand-alone Advanced Planner and Optimizer (APO).

62. What are the advantages of individual requirements over summarized requirement?

The following are the advantages of individual requirement over summarized requirement:

You can do back-order processing, as it is not possible in case of summarized requirement processing.

You can access the order line items and schedule line-in-stock requirement list.

63. What is the disadvantage of individual requirement over summarized requirement?

The disadvantage of individual requirement processing can be seen in system performance. Demand is placed immediately in the stock requirement list, which results in processing overhead and may affect the system performance.

64. How do you define/maintain procedure for each schedule-line category?

Navigate the following menu path to define a procedure for each schedule-line category:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Availability Check and Transfer of Requirements > Transfer of Requirements > Define Procedure For Each Schedule-Line Category.

65. Which types of stock are available to select from while carrying out the availability check?

The following types of stocks are available to select from while carrying out availability check:

Safety stock

Stock in transfer

Quality inspection stock

Restricted use stock

66. What is the relevance of the “Product allocation found changes to the confirmation” message?

The “Product allocation found changes to the confirmation” is displayed during an availability checkon a line item. It means that the quantity allowed to a customer for a particular stock has exceeded its





maximum limit.

67. What is the relevance of the “No feature combination exists …” message?

The “No feature combination exists …” message is related to the product allocation and availability check. This message indicates that no availability check will be carried out. This is because the underlying system has attempted to do an availability check according to product allocation, but errors are found in the setup of the process.

68. What is a change request? How is it done?

The change request is the request that is intended to adopt a new change in the system. After the submission of the change request, the system pops up the change request and shows it in the popup box. The request name is entered and the requested change is named accordingly. A new request number is generated automatically that consists of the client system name and system-generated requestnumber.

69. How is a request released?

To release a request, the transaction code associated with a request is entered in the system. The requests are stored under the modifiable or released heading. We need to select the modifiable option that contains the internal request number, which needs to be released first, followed by the external request number.

70. What is automatic posting in FI?

Automatic posting is the process of posting the accounts in the finance module. The automatic posting configuration does the posting automatically in accounts as determined by the system. This process works as per your configuration and as per your business requirements.

71. What is the item category and the item category group?

The item category is the key field included in the sales cycle. It affects the sales data and schedule-line category. Unlike the sales document type, which is entered manually in the sales order, the item category is automatically determined by the system by using the determination rule, whereas the item category group examines how a material is processed in the sales document. When processing a sales document, the system uses the item category group to examine the item category and suggests it in the respective document. Item category group is defined in the Sales Org View 2 of the Material Master Record.





72. What are outline agreements?

In a business process, the agreements are the type of relationship between the customers and the business. They are done on business entities such as material, price, and quantities. These contracts are represented in the system as outline agreements.

73. What is a quantity contract?

The quantity contract is a contract that is prepared after the issue of quotation but before an order. Quantity contracts are used to limit the quantity of products that a customer can buy. It is a type of arrangement that is followed when the demand for a material is greater than the available supply and the business needs to ensure the product supply evenly among the branches. The standard sales document type for quantity contracts in the system is KM or CQ.

74. What activities are exempted from the quantity contracts?

The quantity contract does not create a requirement for stock within the plant. Therefore, there is notany assurance on the stock of product availability in the contract. There is not any binding agreement from the organization to produce items or to purchase the items to satisfy the contract. There also are not any schedule lines or a validity date. In addition, the contract does not mention any specific delivery dates.

75. How is a quantity contract created?

The quantity contract is created by performing the following step:

SYSTEM Menu > Logistics > Sales and Distribution > Sales > Contract > Create.

Alternatively, the transaction code used for creating a contract is VA41.

76. How can a quantity contract be set up?

The quantity contract can be set up by performing the following step:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Document Types.

77. Which are the contracts that appear in the Implementa tion Guide (IMG) menu?

The IMG (Customizing Implementation Guide) contains the menus that are related to the following contracts:

Master contracts





Value contracts and contract data related to contract profiles and cancellation

78. Which table is used to list the partner functions in a delivery?

The VPBA table is used to view the partner functions in a delivery.

79. How is the pricing procedure determined? How can you define the right pricingprocedure in the sales order?

The pricing procedure is determined according to the various factors such as sales area, customer master, and sales documents type. For determining the right pricing procedures in the sales order, the transaction code OVKK is used. The rule for pricing procedure determination is as follows:

Sales Area

Customer Pricing Procedure

Document Pricing Procedure

80. How would you resolve the problem “MSWT is missing” even when it is presentin the RVAA01 procedure?

In such a case, you need to maintain the condition record for this condition type by using the transaction code VK11.Here you maintain the condition record with a validity period.

81. How is the item text copied from sales order to delivery?

The item text is copied from sales order by performing the following step:

IMG Menu > Sales and Distribution > Basic Function > Text Control.

82. Why is text determination used in SD?

The text determination is used to transfer information from the material or the customer document tothe order or to the invoice document.

83. Why is the partner determination done in SD?

The partner determination is used to determine the partners, such as “Sold to Party,” “Payer,” “Ship to Party,” “Bill to Party,” and Sales Employee, and so on, for the sales document. You maintain the partners in the system as per your business requirements and configure a partner determination procedure. This partner determination procedure determines the partners in a sales document. The whole process goes as follows:

Define the partner functions.





Assign the partner functions to the account group. Define the partner determination procedure.

Place the required partner functions in the procedure.

Assign the procedure to the account group.

84. Why is the output determination used in SD module?

The output determination is used to decide which output mode is used to send an output notification to a partner (customer). Some of the output forms are e-mail, electronic data exchange (EDI), and fax.

85. List the five important fields that need to be maintained during the account determination.

The following fields need to be maintained during the account determination:

Chart of Accounts

Sales Organization

Account Assignment Group for Customer

Account Assignment Group for Material

Account Keys

86. How is the pricing procedure determined?

The pricing procedure is determined through the combination of Sales Organization, the Distribution Channel, the Division, the Customer Pricing Procedure, and the Document Pricing Procedure. The transaction code used here is OVKK.

87. What do you mean by the copy control?

The copy control is meant to copy data from a preceding document to the succeeding document. Thesucceeding document is decided on the basis of the document type and the customer requirements.

88. Specify the purpose of maintaining the common distribution channels and the common divisions.

The common distribution channels and the common divisions are maintained to prevent the master record’s multiple maintenance. For example, if you have created a customer 550 for sales area 0105/30/01, then 550 can be used in the sales area 0108/40/01 if you maintain 30 as the common distribution channel.





89. Why is availability check required?

The availability check is used to determine that whether the requested order quantity would be delivered on the customer-requested delivery date or not. The availability check takes care about the time required to produce or obtain the material and picking or packing time, loading, and transit time for the material.

90. Which kind of requirements does the checking group 01 and 02 represent?

The checking group 01 represents the daily requirements, whereas 02 represents the individual requirements.

91. Suppose in case of output determination, you have generated a condition table with a condition record. In the condition table, the access sequence is assigned to the output type. However, when a billing document is created, the blank output screen appears. During determination analysis, “Note 524 Access not made (Initialized Field)” error occurs. How can this error be resolved?

To resolve this error, assign the output determination procedure to the document header and the output type.

92. Which user exit can be used to copy data into the planning table?

The user exit that you can use to copy data into the planning table is:

User exit MCP20001 along with ZXSOPU01

93. List the forms of number ranges in SD.

There are two forms of number ranges in SD and those forms are as follows:

Internal—In this form, the system automatically assigns a number range to a document.

External—In this form, the system allows a user to assign a number range to a document.

94. What is the purpose of using copy control?

The purpose of using copy control is to decide what document type, item category, and schedule-linecategories can be proposed to the proceeding document.

95. What is contract grouping?

The contract grouping can be defined as the process to link lower-level contracts to one master contract to maintain data consistency.





96. Is it required to create a condition record for the customer and material defining the scale while creating the customer rebate?

No, it is not required to create a condition record for every customer and material while creating the customer rebate. A rebate is customer- or material-specific in nature.

97. How can you create a pricing procedure that calculates the price for the industrial customers when they also purchase the domestic goods?

You can create a pricing procedure that can calculate the price for the industrial customers by performing the following steps:

Create a VOFM subroutine that is VOFM > Formulas > Condition value.

Now set this subroutine in your procedure as V/2 transaction code in the AltCTy field. You can describe your requirements in the ABAP coding.

98. How does the system show storage condition? How can the storage condition be defined?

System uses a two-character alphanumeric key storage condition to show the storage condition of a material. The storage condition is used in coordination with the plant and shipping point to decide the storage location. You can define the storage condition of a material by navigating the following menu path:

Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Picking > Determine Picking Locations > Define Storage Conditions.

99. Suppose that you have customized the customer’s credit limit in your company in such a way that when a customer exceed his/her credit limit, the system respondsto you. What is the name of this management in SYSTEM, and what data do you use for this management?

This management is known as the credit management. The data you use for the credit management isthe credit management master data. The finance module is used to assign credit limit to customers.

100. Give the menu path to assign credit limit to customers.

The menu path to assign credit limit to customers is:

SYSTEM Menu > Accounting > Financial Accounting > Customers > Credit Management > MasterData > Change [FD32].





101. In SYSTEM there is functionality, which is used to manage the customer credit limits. That functionality can be assigned with one or more company codes. By using the company code, the system decides that organizational unit when a saleoccurs. What is the name of that functionality?

The name of that functionality is credit control area.

102. Give the menu path to create a credit control area.

The menu path to create a credit control area is:

Implementation Guide (IMG Menu) > Enterprise Structure > Definition > Financial Accounting > Define Credit Control Area.

103. Define the risk category.

It is a grouping category, which is used to control the process to check the credit limit when the credit control takes place automatically. You use this category to segregate customers group on the basis of different credit rules. For example, you can put high-risk customers in one group and low-risk customers in another group.

104. Give the menu path to assign a company code to a credit control area.

The menu path to assign a company code to a credit control area is:

Implementation Guide (IMG Menu) > Enterprise Structure > Assignment > Financial Accounting > Assign Company Code to Credit Control Area [OB38].

105. Is it required to assign a sales area to a credit control area? If yes, then give themenu path to assign a sales area to a credit control area.

Yes, it is required to assign a sales area to a credit control area. You can navigate the following menupath to assign a sales area to a credit control area:

Implementation Guide (IMG Menu) > Enterprise Structure > Assignment > Sales and Distribution > Assign Sales Area to Credit Control Area [OVFL].

106. List the places where a credit check can occur.

The credit check can occur at the following three places:

The sales order

The delivery





The goods issue

107. List the credit management checks that the system uses to check the credit.

The various automatic credit management checks that the system uses are:

Simple Credit Check

Automatic Credit Check—Static or Dynamic

108. Suppose that you have to define the risk categories for various customers, thenwhich system module you use to define the risk categories. Which menu path can you use to define the risk categories?

The risk categories are defined in the financial accounting module of system using the following menu path:

Implementation Guide (IMG Menu) > Financial Accounting > Accounts Receivable and Accounts Payable > Credit Management > Credit Control Account > Define Risk Categories.

109. Once the risk categories are defined, you need to define the credit groups. Which system module do you use to define the credit groups? Give the menu path to define the credit groups.

The sales and distribution module of system is used to define the credit groups by navigating the following menu path:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Credit Management/Risk Management > Credit Management > Define Credit Groups.

110. Is it required to assign a credit group to the sales and delivery document types? If yes, then which menu path do you use to assign a credit group to the sales and delivery document types?

Yes, it is required to assign a credit group to the sales and delivery document types. The menu path that can be used for this purpose is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Credit Management/Risk Management > Credit Management > Assign Sales Documents and Delivery Documents > Credit Limits Check for Order Types > Credit Limit Check for Delivery Types.





111. The automatic credit management is controlled by the combination of two items. What are those items and what is this control called? How can you maintain this control?

The combinations of the items that control the automatic credit management are the risk category and document credit group. This setting is called as the Automatic Credit Control. You can maintain theAutomatic Credit Control by navigating the following menu path:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Credit Management/Risk Management > Credit Management > Define Automatic Credit Control.

112. What is a static credit limit check?

A static credit limit check is a credit check done by comparing the customer’s credit limit with the following items:

The total value of open sales orders.

The total value of open deliveries whose invoice is not yet created.

The total value of open billing documents that are not yet passed to the accounting department.

The total value of the billing documents that are passed to the accounting department but the billing amount is not yet paid by the customer (open items).

113. What is dynamic credit check?

A dynamic credit check is a credit check done comparing the credit limit assigned to the customer with the following items:

The total value of open sales orders that are not yet delivered.

The total value of open deliveries whose invoice is not yet created.

The total value of open-billing documents that are not yet passed to the accounting department.

The total value of the billing documents that are passed to the accounting department, but the billingamount is not yet paid by the customer (open items).

Plus-horizon period (those documents covered that have a shipping date within the horizon period).

114. Give the menu path to define the forms of payment guarantee.

The payment guarantee is used against the billing amount that a customer has to pay. It can be any form, such as a letter of credit or payment cards. You can define the forms of payment guarantee by navigating the following menu path:





Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Credit Management/Risk Management > Receivables Risk Management > Define Forms of Payment Guarantee.

115. Give the menu path to configure the payment guarantee procedure.

The menu path to configure the payment guarantee procedure is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Credit Management/Risk Management > Receivables Risk Management > Define and Assign Payment Guarantee Schemas > Define Payment Guarantee Schemas.

116. Give the menu path to define a customer determination schema.

The menu path to define a customer determination schema is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Credit Management/Risk Management > Receivables Risk Management > Define and Assign Payment Guarantee Schemas > Define Customer Determination Schema.

117. Give the menu path to define the document determination procedure.

The menu path to define the document determination procedure is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Credit Management/Risk Management > Receivables Risk Management > Define and Assign Payment Guarantee Schemas > Define Document Determination Schema.

118. Suppose you have to create a block to stop transferring the goods requirement from the sales document to the plant. Which block do you create for this purpose?

The requirements block is created for this purpose.

119. Give the menu path to define the status groups for the incompletion log.

The menu path to define the status groups is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Log of Incomplete Items > Define Status Groups.

120. List the items for which you can create incompletion logs.

The incompletion logs can be created for the following items:

Sales document header data





Sales document item data

Sales document schedule line data

Sales activity data

Partner data in sales documents, deliveries, and sales activities

Delivery header data

Delivery item data

121. Give the menu path to define incompletion procedures.

The menu path to define incompletion procedures is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Log of Incomplete Items > Define Incompleteness Procedures.

122. Is it possible to assign an incompletion procedure to an object? If yes, then givethe menu path to assign an incomplete procedure to an object.

Yes, it is possible to assign an incompletion procedure to an object. You can do that by navigating the following menu path:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Log of Incomplete Items > Assign Incompleteness Procedures > Assign Procedures to the Sales Document Types.

123. List the documents, activities, and records for which the system automatically determines partners.

The system automatically determines the partners for the following documents, activities, and records:

The sales documents

The delivery documents

The billing documents

Sales activities

124. Give the menu path to set up the partner determination.

The menu path to set up the partner determination is:





Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Partner Determination > Set Up Partner Determination.

125. Suppose you want the system to copy a text line from the customer master record to a sales document automatically. How can you make the system do that?

The system can be made to copy a text line from the customer master record to a sales document automatically by using the text determination procedure.

126. Give the menu path to configure the text determination procedure.

The menu path to configure the text determination is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Text Control > Define Text Types.

127. List the text objects for which the sales and distribution module is used in the text determination.

The text objects for which the sales and distribution module is used in the text determination are:

Customer

Central texts

Contact person

Sales and distribution

Info record

Customer/Material

Pricing conds

Agreements

Conditions

Sales document

Header

Item

Delivery

Header





Item

Billing doc.

Header

Item

Sales act.

General text

Shipment

Header

Financial doc.

General text

Legal control

General text

Agency business

Header

Item

Trading contract

Header

Item

128. What is an output?

An output is defined as a medium that links various business partners. An output medium can be one, such as e-mail, fax, Electronic Data Interchange (EDI), and printouts. Output media are usually created for invoices, delivery notes, and order confirmation.

129. Give the menu path to maintain the output determination for the sales documents.

The menu path to maintain the output determination for the sales documents is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Output Control >





Output Determination > Output Determination Using the Condition Technique > Maintain Output Determination for Sales Documents.

130. List the sales and distribution related output determination activities.

The output determination activities that are related to the sales and distribution are:

Sales Activities

Sales Documents

Outbound Deliveries

Inbound Deliveries

Handling Units

Groups

Shipments

Billing Documents

131. List the transaction codes to create, change, and display the output condition records.

The transaction codes to create, change, and display the output condition records are:

For sales order

[VV11]—Creates the output condition records

[VV12]—Changes the output condition records

[VV13]—Displays the output condition records

For delivery




For billing








132. Give the menu path to define forms.

The menu path to define forms is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Output Determination > Process Output and Forms > Define Forms.

133. Give the menu path to define the form texts.

The menu path to define the form texts is:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Output Determination > Process Output and Forms > Assign Form Texts > Assign Form Texts Per Sales Organization.

134. How is the transaction code CTO4 related with characteristics?

When the desired class of material is selected in the material master, the characteristics of that class needs to be chosen. The CTO4 transaction code is used to define these characteristics.

135. What is excise tax, and how is it related to the system?

The excise tax or excise duty is a type of tax that is charged on the goods that are produced for selling within a country. It is different from the customs duties, which are charged on imported goods. As per the system guidelines, the procedure of excise tax calculation is country-specific. Therefore, the ERP software, which is implemented in India, has a built-in Country India (CIN) version. You need to configure CIN for excise tax calculation.

136. What are the pricing procedures of CIN?

The Country India (CIN) version comes with the following four pricing procedures:

JINFAC (Sales from Manufacturing Plants)

JINEXP (Export Sales)

JINDEP (Sales from Depots)

JINSTK (Stock Transfers)

137. How are the data related to excise registrations maintained?

You need to perform the following step to maintain excise registration data:





System Customization Implementation Guide > Logistics > General > Tax on Goods Movement > India > Basic Settings > Maintain Excise Registrations.

138. How is the contract configuration setting opened?

You need to perform the following step to open the contract configuration setting:

Implementation Guide (IMG Menu) > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Document Types and select a contract document type from the sales document type.

139. What are the major settings in the contract configuration setting screen?

The following are major settings in the contract configuration screen:

Price Procedure Condition Header

Contract Profile

Billing Request

Group Reference Procedure

Contract Data Allowed

Follow-Up Activity Type

Update Lower Level Contract Fields

Check Partner Authorization Type

Subsequent Order Type

140. What is the service and maintenance process?

The service and maintenance process or service contract is a type of agreement between the supplier and receiver of the goods or service. This contract forms a basis on which the regular activities of the business, such as billing, cancellation, and other related items are done. A service contract contains validity dates, cancellation conditions, price agreements, and information.

141. Which is the standard sales document type for the service contract?

The WV is the standard sales document type for the service contract.





142. What are service items?

The service items are used by the service contract documents and can be one or all of the following:

Service task

Material used in the service

Time charged by the technician as per hourly rate

143. What is a standard service item category?

A standard service item category represents a service that is carried out and billed periodically. In standard system, the standard item category for a service is WVN.

144. What is the standard material type for service items?

There is a standard material type for service items. DIEN is the material type which is generally usedfor services in standard system.

145. What is the value contract?

The value contract is similar to the quantity contract, but the main difference is that the value contract is based on the total value of the quantity rather than its numbers. The value contract is createdand maintained in the same way as the other contracts. You need to perform the following step to configure a value contract:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Sales > Sales Documents > Contracts > Value Contracts > Maintain Value Contract Type and Contract Release Type.

146. What is an assortment module?

An assortment module is a tool for order entry. It displays a list of materials and services likely to be released from a value contract. It has a specific validity date. There is a condition for the inclusion of the items in the assortment module according to which only materials and services that belong in the same sales organization and for which the release order is being made will be displayed. You need to perform the following step to create an assortment module:

SYSTEM Customization Implementation Guide > Logistics > Sales and Distribution > Master Data > Products > Assortments > Assortment > Module.

After going through the preceding steps, the assortment module screen appears from which the assortment modules are created.





147. What is a master contract?

A master contract is a contract that groups contracts at a lower level. It contains the information that is relevant to the rest of the contracts. The main objective of the master contract is to ensure consistency at all levels. The documents included in the master contract are as follows:

Quantity contracts

Value contracts

Service contracts


Contract grouping is the process by which lower-level contracts are linked to a master contract. It is required that all the contracts are assigned to the same sales area. Only one master contract can remain in the contract hierarchy.

149. What is referencing requirement?

The referencing requirement is used to assign the contracts that are referenced by master contract. It is necessary for grouping contracts or linking quantity contract to master contract. You need to perform the following step to reference a requirement:

System Customizing Implementation Guide > Sales and Distribution Sales > Sales Documents > Master Contract > Define Referencing Requirements > Define Sales Document Type.

150. How would you define referencing?

The next stage after defining a referencing requirement is defining the reference. You need to perform the following step to define referencing:

System Customizing Implementation Guide > Sales and Distribution Sales > Sales Documents > Master Contract > Define Referencing Requirements > Define Referencing Procedures.

151. What is standard application logic?

If any field in the new reference procedure screen is changed in the master contract, then only those fields of the master contract will be copied by the system, which has the same value of master and lower level contracts. This is known as application logic.





152. What is workflow? Name the person who can assist you while configuring a workflow for a system.

It is a sequence of steps either processed manually or automatically by the system for implementing a task, such as updating a contract. It is handled by a workflow resource.

A workflow consultant is a person who looks after the problems associated with a workflow.

153. What are scheduling agreements?

The scheduling agreements are the type of agreements that are accomplished between the customer and the business organization. It includes the details related to the delivery of the products such as delivery date and quantities that are to be delivered. The delivery dates are then passed to the schedule line for further activities.

154. What is the planning delivery schedule?

The planning delivery schedule is a type of delivery schedule that is used to manage the planning requirement of a project. The planning delivery schedule is conducted for limiting the planning period of schedule lines in forthcoming delivery schedules.

155. What are the various sections of the planning delivery schedule?

The following are the three sections of the planning delivery schedule:

Maintain Delivery Schedule Splitting Rules—Determine features of the planning and delivery schedule.

Maintain Delivery Schedule Instructions—Define the splitting of the quantities which are in the schedule line.

Assign Delivery Schedule Splitting Rules—Assign the rules of splitting for planning delivery schedule.

156. What is a correction delivery?

A correction delivery is when a product is wrongly delivered to the customer and returned. The goodreceipt is not processed. As a result, the cumulative quantity in the scheduling argument is updated and the original delivery quantity is called off in the scheduling agreement.

157. How is the scheduling agreement created?

You need to perform the following step to create the scheduling agreement:





SAP Menu > Logistics > Sales and Distribution > Sales > Scheduling Agreement.

Alternatively, you can create the scheduling argument by using the VA31 transaction code.

158. What is a rebate agreement?

The rebate agreement is a type of agreement that is accomplished between the customer and the buyer for the discount paid to the customer. It depends on conditions such as buying certain amounts ofgoods over a particular time period. This agreement specifies the rebate amount agreed on for each product.

159. How are the rebate agreement types defined?

You need to perform the following step to define rebate argument types:

Customization Implementation Guide(IMG Menu) > Sales and Distribution > Billing > Rebate Processing > Rebate Agreements > Define Agreement Types [VBO1].

160. What are the rebate argument types as per standard system guidelines?

The rebate agreement types as per system agreement are as follows:

0001—Group Rebate

0002—Material Rebate

0003—Customer Rebate

0004—Hierarchy Rebate

0005—Independent of Sales Volume

00E1—Exp. Group Rebate

00E2—Exp. Material Rebate

00E3—Exp. Customer Rebate

00E4—Exp. Hierarchy Rebate

00E5—Exp. Revenue Independent

161. List the components of rebate processing in System.

Rebate processing in System is divided into the following three components:

Configuring rebates





Setting up rebates

Managing rebate agreements and payments

162. How can you define a change request? How can you release a saved change request?

A change request is defined as a request that is automatically generated by the SYSTEM when you do any new customizing or configuration task in the SYSTEM. Once you save the change request, the SYSTEM generates a request number, which you have to save for further processing. A change request can be released by using the SE10 transaction code.

163. Give the menu path to create the tax calculation procedure.

The tax calculation is country-dependent, because every country has its own tax procedures to calculate tax. The menu path to create the tax calculation procedure is:

System Customizing Implementation Guide > Financial Accounting > Financial Accounting Global Settings > Tax on Sales/Purchases > Calculation.





CHAPTER 5SALES

1. What do you understand by intercompany customers and one-time customers?

The Sales customers who deal within the same client between different company codes are known asintercompany customers. One-time customers refer to those customers for whom you do not want to create a separate record, so that such type of customer account group can be reused.

2. Explain the terms Minimum Order Quantity and Minimum Delivery Quantity.

The Minimum Order Quantity refers to the minimum quantity that a customer needs to order. The concept of Minimum Delivery Quantity refers to the minimum quantity that you need to deliver to a customer.

3. Imagine you want to trace the changes made in the sales order in context of the changes to the partner function in the sales order. How can you do the same?

To trace the changes, you should go to Environment in Sales Order and follow the following path to trace the changes made:

Environment > Change.

This will depict the partner functions in the changed documents.

4. What is the difference between confirmed quantity and the order quantity?

The quantity ordered by a customer is referred to as Order Quantity, and the quantity allocated by Availability to Promise (ATP) is known as Confirmed Quantity.

5. How can you assign movement type?

The movement type is assigned while defining the schedule line category.

6. What is the menu path to reject and cancel the sales order items?

Perform the following steps to reject and cancel the sales order items:

Use the VA02 transaction code; a sales initial screen appears.

Enter the sales order number; the sales order document appears.

Click the reject document button and then enter the reason for rejection.





These steps will reject the line items and the sales order.

7. How can you copy text from the sales order header to the billing document header?

To copy text from the sales order header to billing document header, use the VOTXN transaction code and then create an access sequence with the VBBK text object.

Note:

You must ensure that the requirement of access sequence is provided as the ‘1’-Refdoc. header.

8. Suppose, in a particular case, customer requirements for the sales order do not appear in the MD04 transaction. How can you resolve such a problem?

To resolve the problem of nonappearance of customer requirements for the sales order, you need to check whether the requirement class and schedule line category of your document are activated for requirement transfer.

9. What transaction code is used for printing addresses or details of all customers at a single point of time?

You can use S_ALR_87012179 and S_ALR_87012180 transaction codes for printing all customer details at one time.

10. What do you mean by backorder processing?

Backorder processing is functionality in the System where you change the commitments and override the blockage of stocks marked against sales documents/deliveries. For example, you receive an order from a very important customer for material “X” but the entire quantity of X is committed to another customer “Y” via earlier orders. This is where backorder processing works to change the commitment and shift stock due for Y to X.

11. What is the functionality of the update button in the VA01 transaction at item level of conditions?

The update button is to update the pricing of products, even though the System performs an automatic update for it. This button is mainly used when an organization makes changes in the pricing conditions, such as taxes and discounts. By clicking the update button and selecting an appropriate condition that appears after clicking, the effect of change in the pricing conditions is depicted in the existing sales order.





12. Describe the ways to include a new field in the VA01 sales order.

The following are the two ways to include a new field in the VA01:

Enter the transaction code SE93 on the Easy Access Menu screen. Enter VA01 in the transaction code text field in the screen. This will take you to a new screen. In this screen, you need to select the programs option. When you select programs, the module pool screen appears. Click the Find icon and enter the customer key to get the user exits in that particular program.

Enter the transaction code SPRO as transaction code on the Easy Access screen. A new screen appears; click the IMG tab then SD > System Modifications and finally User Exits. In the next screen, click the Help document. It displays all of the user exits with the program name. Add a new file there.

13. What is material determination?

When preparing the sales order, we need to determine the materials to be entered in the sales order. Material determination is a method in SD that helps determine the material to be used in the sales order.It uses condition techniques to determine the products to be selected. It is also helpful in determination of products when we need to replace an old product from the sales order as it has become obsolete and new products are available at that place. It automatically replaces the old product with the new one in this case. Material determination is also called product selection, and can be implemented as an automatic or manual process.

14. How do you maintain substitution reasons?

Navigate the following menu path to define substitution reasons:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Material Determination > Define Substitution Reasons.

15. How are the sales orders deleted?

The sales orders are deleted by using the particular transaction code associated with it, such as VA02. This is a required condition that is necessary to be followed while processing this transaction. This is so that no additional document is created against it. If a full SD cycle before the invoice creationhas been done, then you need to first cancel the invoice by using the transaction code VF11. Next, reverse the goods issue by using the transaction code VL09. Then go to delivery document in change mode (VL02n). Finally, replace the picking quantity with 0. After that, delete the delivery by going to the Delivery Document tab and selecting “Delete.”. To delete the sales order, you can go to VA02, then go to the Sales Document tab and then select “Delete.”





16. What are the order and target quantities?

The quantities that are available in the quantity contract are called target quantities. Similarly, the quantities that are ordered are called the order quantities.

17. How can a release order be created?

The release order is created by performing the following step:

SYSTEM Menu > Logistics > Sales and Distribution > Sales > Order > Create.

Alternatively, the transaction code used here is VA01.

18. Can you create more than one customer hierarchy for the same payer? If yes, then how?

Yes, it is possible to create more than one customer hierarchy for the same payer. We can do it by first creating the order and delivery and then performing the PGI for the first and second customer hierarchy.

19. A sales document is divided into three levels. List those three levels.

The three levels into which a sales document is divided are as follows:

Header Level (Table VBAK)—All of the master data, such as the customer material master, the sales area, and the organization data of a sales document is stored at header level in the VBAK table.

Item Level (Table VBAP)—All of the material item data, such as the order quantity and the material master data of a sales document, is stored at item level in the VBAP table.

Schedule Line (Table VBEP)—Information about the material delivery dates and the delivery quantity of a sales document is stated at the Schedule line in the VBEP table.

20. What is a sales order?

A sales order is given by a customer to an organization for product or services. A sales order is processed in the system to determine the basic organizational data and requirements for the entire sales process.

21. Write the statement to display your own error message when the selected batch is not available on a customer-defined table.

The statement to display your own error message when the selected batch is not available on a customer-defined table is:





User exit - USEREXIT_SAVE_DOCUMENT_PREPARE

22. Define an item proposal.

If a customer frequently orders the same combination of materials, or if you recommend a particular selection of products for an opening order, you can store the frequently used data as an item proposal inthe system. If you want, the item proposal may also include proposed order quantities. During the sales order creation, you can copy all or some of the materials and quantity data from the item proposal directly into your document (sales order, quotation, and so on). You can assign a particular item proposal to a specific customer master record. The system can then automatically propose the number of the assigned item proposal whenever you process sales orders for the relevant customers.

23. What is a quotation?

A quotation is a sales document that you create before a sales order and after an inquiry. A quotation is a legally binding document that informs the customer of proposed prices and terms and conditions.

24. When is the cash sale process used?

The cash sale process is used when a customer places an order, picks goods, and pays for the goods at the same time. When the cash sale process is used, the system proposes the current data as the goods delivery and billing date. After you save the sales order, the system creates a delivery and prints a cash sale receipt. The cash sale concept is generally used for sales to employees rather than to a one-time customer.

25. When is the rush order process used?

The rush order process is used when a customer places an order and picks the items immediately. Once you save the Sales order, the System creates a delivery; however, the invoice is generated later and sent to customer.

26. A pop-up screen appears with a message “for this customer there are open quotations”, when you create a sales order using VA01. How can you disable this pop-up?

The pop-up can be disabled by checking the order header configuration (V0V8) and field quotation messages.





27. Write down the steps to decide a fixed discount for all possible values. For example, for each $75, discount amount should be $5. It means for $150 the discount amount should be $10, for $225 the discount amount should be $15, and soon.

Perform the following steps to determine a fixed discount for all possible values:

New routine in VOFM > Formulas > Condition values. Now divide the quantity by 75 and multiplythe integer part of result by 5.

New condition > calculate type > G- formula.

Input condition in your pricing procedure and then input condition formula for alternative calculation (AltCTy) -new formula.

28. How can you assign a sales representative as a partner by using the MASS transaction?

You can assign a Sales representative as a partner by performing the following steps:

Select the KNA1 object by using the MASS transaction.

Now select the KNVP table.

29. How can you change a position in a sales order with bapi_Salesorder_change?

To change a position in a Sales order with bapi_Salesorder_change, you have to properly fill the update structure and need to take care of the following:

The order header should read order_header_inxupdateflag=‘U’.

The item must read order_item_inx=‘U’.

Every field in order_item_in should have an ‘X’ in the matching field of order_item_inx.

30. How can you update a system to generate an error message when a user tries to enter two sales orders with the same reference to the customer’s purchase order?

You can update a System to generate an error message when two Sales orders are entered with the same reference to the customer’s purchase order by doing the following:

Enter “A” in the check PO number field under general control in the VOV8 transaction.

Modify the message category of V4-115 to “E” from “W” in the OVAH transaction.





31. How can you issue items from a storage location that has negative stock?

Perform the following steps to configure the System so that you can issue items from the storage location having negative stock:

Start transaction OMJ1. Then select the check box to allow issuing negative stock for the respective plant and the valuation area.

Start transaction MMO2 > Plant data/stor.2 > Check negative stock in the plant.

32. Give the menu path to define shipping conditions using the sales document type.

The menu path to define shipping conditions by using the Sales document type is:

Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Basic Shipping Functions >Shipping Points and Goods Receiving Point Determination > Define Shipping Conditions by Sales Document Type.

33. What is the use of a loading group? How can you define the loading groups?

A loading group is used to decide the shipping point. A loading group is a mandatory field of the material master record because a delivery cannot be made without a loading group. You can navigate the following menu path to define the loading groups:

Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Basic Shipping Functions >Shipping Points and Goods Receiving Point Determination > Define Loading Groups.

34. Define backward scheduling.

Backward scheduling is defined as the process used to schedule the Sales process to meet a delivery date from the requested delivery date. The backward scheduling starts from the requested delivery date;for example, if the requested delivery date is the 15 th, then the scheduling process will start from the 15 th and move backward by considering the different time periods such as Transit Time, Loading Time, Pick and Pack Time, or Transportation Planning Time and Material Availability Time. If the Material Availability Date, as calculated through Backward Scheduling, falls after the Order Date then System confirms the Customer requested Delivery Date; otherwise, the System starts doing Forward Scheduling by considering all above time slots in forward order and proposes another confirmed Delivery Date by proposing a new Schedule Line in the Sales Order.

35. List the various business functions that are performed to meet the delivery date.

The business functions that are performed to meet the delivery date are as follows:

Scheduling the time required to procure the material.





Scheduling the time required to pick or pack the material or transportation planning time.

Scheduling the time required to load the material.

Scheduling the time required to shift the material to the customer’s site.

36. Suppose you have received a sales order on the 10 th and the requested delivery date for the material is the 17 th. When you check the stock, you find that the material is not available on the 10 th; rather, it is available on the 15 th. Now because the material is not available on the 10 th, you cannot deliver the material on the 17 th. On this condition, SYSTEM starts scheduling the process to find out the next earliest delivery date. What is this scheduling process called?

This scheduling process is known as forward scheduling.

37. List the factors that need to be considered when deciding the routes.

The following are the factors that need to be considered when deciding the routes:

Departure Zone

Shipping Conditions

Transportation Group

Transportation Zone

38. Give the menu path to define the order block reason.

The menu path to define the order blocks is:

Implementation Guide (IMG Menu) > Sales and Distribution > Sales > Sales Documents > Define and Assign Reason for Blocking.

39. How can you create a list of the incomplete Sales documents?

A list of the incomplete Sales document can be created by navigating the following menu path:

System Menu > Logistics > Sales > Information System > Orders > Incomplete Orders [V.02].

40. List the activities for which you can set up the partner determination.

The partner determination can be set up for the following activities:

Customer Master

Sales Document Header





Sale Document Item

Delivery

Shipment

Billing Header

Billing Item

Sales Activities (CAS)

41. How is the consignment stock created?

You need to perform the following step to create a consignment stock:

System Library > System R/3 Enterprise Application Components > Logistics > Sales and Distribution (SD) > Sales Special Business Process in Sales > Consignment Stock Processing.

42. What is the consignment stock?

The consignment stock consists of the items which are kept either at the customer or the business site for the consumption by the customer on the basis of a written agreement between them. The customer has the right to return the goods if not further sold or used. Till the time of sales or consumption of such stocks, it remains legally as company’s property. The customer pays the company only when the stocks are sold/ consumed, otherwise he returns the stocks to the company. This would occur in some special sales-related scenario, such as pushing of stocks to meet an increased sales requirement, or is used for exhibition purpose as well.

43. What are the consignment steps?

Consignment Fill Up: Providing stocks to Customer (No Invoice).

Consignment Issue: Billing of Consignment Stocks to Customer (Invoice is generated).

Consignment Pick-Up: Taking back of stocks from customer (No Invoice).

Consignment Returns: Taking back of stocks which were invoiced to customer through ConsignmentIssue Process (Invoice is generated).

44. How can you view the consignment stock allotted to the customer?

You need to perform the following step to view the consignment stock assigned to a customer:

Customization Implementation Guide(IMG Menu) > Logistics > Material Management > Physical Inventory > Environment > Stock Overview [MMBE].





45. What is a consignment issue?

The consignment issue is the allotment of products for the customers. Its Standard document type is KE and the Standard order type using which it is recorded is the same. The standard item category usedfor the consignment issue is KEN. C0 and C1 are the standard schedule lines used for consignment issue. To create a consignment issue order, the Document Type KE is selected.

46. What is consignment returns?

It is the sales process flow which includes the material or the product which are defective and either returned by the customer or sold by the consignee. These types of products are returned back to the consignment stock and stored as a faulty item. The sales document type for the consignment return is KR.

47. Why is the consignment not returned into plant stock?

When a consignment is issued to the customer, the business process is abstracted at the level of two parties; the customer and supplier. Therefore, customer maintains his own records related to the stock issue or return. If it is returned to the plant stock then it would be difficult for the customer to manipulate his transaction from the huge database of products at the plant level.

48. What is customer pick-up?

The customer pick-up is the last process of the consignment procedure. It includes picking of the faulty as well as the unused/unsold materials which are left by the customer. The specific return shipping point is determined for the products. There is no need of any invoice with consignment pick-up, because the ownership of goods is not changing. KAN is the standard item category for the consignment pick-up.

49. Name the standard overview for consignment.

SYSTEM contains a standard overview for the listing of all the consignments for all the materials issued to the customers in the plant. It is called Display Consignment and Returnable Packaging Stocksat Customer.

50. How would you access the Display Consignment and Returnable Packaging at Customer overview?

You need to perform the following step to access the consignment overview:

Customization Implementation Guide(IMG Menu) > Logistics > Inventory Management > Environment > Consignment at Customer [MB58].





51. What are sales document lists?

The sales document lists are similar to the lists that are usually prepared throughout the business process. They are many sales documents lists that are prepared during the selling process. For example,the sales order list is very common in the sales and distribution module.

52. What are the common sales document and work lists?

The common sales document and work lists are as follows:

List of Sales Orders

Outbound Delivery Monitor

List Billing Documents

Sales Documents Blocked for Billing

Sales Documents by Objects or User Status

Display Backorders

Incomplete Sales Orders

Incomplete Sales Documents

Outbound Delivery Monitor

Transportation Planning Lists

Blocked Billing Docs

53. What is the sales document status?

In the sales documents, there is status at header and item levels. It is used for knowing and controlling the stages in the sales documents.

54. What are the fields of the processing status?

The processing status indicates the stages of an item, whether it is processed or not. It includes the following fields:

Overall Status

Delivery Status

System Status





55. How can you configure a status profile?

You need to perform the following step to configure a status profile:

Customization Implementation Guide(IMG Menu) > Sales and Distribution > Sales > Sales Documents > Define And Assign Status Profile > Define Status Profile.

56. How can you configure a status profile to sales documents?

You need to perform the following step to configure a status profile:

Customization Implementation Guide(IMG Menu) > Sales and Distribution > Sales > Sales Documents > Define And Assign Status Profile > Assign Order Type/Status Profile.

57. How can you configure a status profile to item categories?

Perform the following step to configure a status profile:

Customization Implementation Guide(IMG Menu) > Sales and Distribution > Sales > Sales Documents > Define And Assign Status Profile > Allocate Status Profile to Item Categories.

58. List the tables that are used to display the status of sales documents.

The following are certain tables used to display the status of sales documents:

VBUK—Displays header status and administrative data.

VBUP—Displays item status.

VBAKUK—Displays sales document header and status data.

59. How will you define Incompleteness procedure?

You need to perform the following step:

Customization Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Log of Incomplete Items > Define Incompleteness Procedures.

Alternatively, you can also use the transaction code V.00.

60. What is general table display?

The General Table Display screen displays the populated fields of a table. The transaction code usedfor this purpose is SE16.





61. How is the sales document list configured?

You need to perform the following step to configure sales document lists:

Customization Implementation Guide(IMG Menu) > Sales and Distribution > Sales > Lists > DefineSelection Criteria.

62. What is document flow?

Right from the enquiry through quotation, ordering, shipping and final billing of the products, many documents are prepared. The chain of such type of documents created in a sales process is called a document flow.

63. What are the sales document types?

The sales documents may have several types, but the most commonly used are as follows:

Standard Order

Returns

64. What is sales order stock?

The sales order stock is a stock with a stock type E. It is the stock of items which is reserved as per the sales order issued.

65. What is backorder processing?

The backorder processing is the process of changing of the previous commitment of the delivery of goods from one customer to another due to strategic reasons.

66. What are the transaction codes used for backorder processing?

The transaction codes used for backorder processing are as follows:

OMIH

OPJL

OPJJ

V_RA

67. What is trading process?

Let’s consider three organizations: A (the service provider), B (the service receiver), and C (works as





a vendor which provides the services to service providers). In this situation, when A receives a purchaseorder from B it either manufactures it or purchases it. If the option of procurement is chosen, then after receiving the purchase order from B, A creates a sales order for it. Also, it creates a purchase order for C to arrange the goods. C prepares the product and sends to A which delivers it to B, who is the ultimate buyer. This process is called the trading process.

68. What is third-party order process?

Let’s consider three organizations: A (the service provider), B (the service receiver), and C (works asa vendor which provides the services to service providers). In this situation, when A receives a purchaseorder from B it either manufactures it or purchases it. If the option of procurement is chosen, then after receiving the purchase order from B, A creates a sales order for it. Instead of preparing the purchase order for C, as in the case of trading process, A authorizes C to deliver the product to B on behalf of A. This process is called third-party order processing.

69. What is invoice verification? Name the transaction code for it.

Invoice Verification is the process used when a Purchase is made. For every purchase made, an Invoice is received from Vendor/Supplier. In this process the data related to invoice is posted in the system, which also creates payment liability for the supplying vendor. MIRO is the transaction code that is used for invoice verification.

70. What is product group?

The product group is categorized as the group of the products which are allocated for specific customer order. The product group can be either multi-level or single-level. The single-level product group contains only the materials whereas the multi-level group can contain more than one product group.

71. Mention two ways to restrict a user from changing fields in VA02 transaction code.

The following are the two ways to restrict a user from changing fields in VA02 transaction code:

Create a transaction variant using SHD0 and then assign that variant to a sales document. During thevariant creation, check the non-changeability feature for the fields that cannot be changed by a user. After creating a variant, allow users to work with the variant rather than the original transaction.

Use the user exit FORM USEREXIT_FIELD_MODIFICATION through authorization objects.





72. How can you set the ZOBP condition type to allow only the positive values?

The ZOBP condition type can be set to allow only the positive values by navigating the following menu path:

Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types > Maintain Condition Types [V/06].

Now change the plus/minus indicator of the ZOBP condition type to A. Once you change the ZOBP condition type to A, it will allow only the positive values.

73. Mention the differences between the stock transfer among the plants that have the same company code and the plants that have different company codes.

The differences between the stock transfer among the plants that have the same company code and the plants that have different company codes are:

The stock transfer among the plants that have the same company code is called intracompany stock transfer, while the other is called intercompany stock transfer.

The stock among the plants that have the same company code is transferred without any pricing, while the stock transfer among the plants that have different company codes includes pricing and is similar to a purchase order.

74. Explain the relation between the MM, SD, and FICO modules.

In the software based on the concept of ERP, SYSTEM comprises of various modules, such as MM, SD, and FICO. All of the SYSTEM modules are integrated to each other to automate the business-management process. The SD module of SYSTEM receives data from MM, while the FICO receives data from SD; therefore, functionality of a module depends on other modules. MM module is responsible for Material purchase/stocking, etc.; SD is responsible for all Sales & Distribution related transactions and FICO keeps the records through G/L assignment and controlling analysis of all the transactions which take place in other two modules. The interdependency is always there, at least among these modules, in a commercial organization.

75. List the various types of special stocks.

The various types of special stocks are:

Consignment stock related to vendor

Consignment stock related to customer

Components provided to vendor





Project stock

Pipeline material

Orders on hand

76. Give the document flow from Enquiry to Invoicing in SD.

The menu path for invoicing in SD is:

SD Inquiry > Quotation > Sales Order > Delivery > Transfer Order > Post Good Issue > Billing > Invoicing.





CHAPTER 6 SHIPPING

1. How can you link the Automatic Packing Procedure with the Delivery Type or Item category?

The Automatic Packing Procedure is assigned in the OVHU2 transaction code; therefore, you need to assign the procedure to 0002 Outbound Delivery. This would help control packing in the delivery item category. However, to have better control, you can design the access sequence with the available fields.

2. What is the most important concern that needs to be taken care of when creatingdelivery notes in different languages?

When creating delivery notes, the language of the notes is decided by the destination country for which the delivery notes are created. Therefore, it is most important to ensure that the country is identified accordingly in the program and the correct form is used to create the delivery note.

3. Define consumption modes.

The consumption mode defines the direction of the consumption of customer requirements from the requirement date, with planned independent requirements. The requirement date is the date on which the sales order items were created.

4. How is the billing delayed to the next month in a delivery note?

You need to postpone the invoice date in the sales order relating to that delivery. If this is not done, then the GI date would be picked up by the invoice as the delivery date. Alternatively, the GI date may be put on hold until the date of the invoice.

5. What is the purpose of the shipping point determination?

The purpose of the shipping point determination is to determine dispatch-related data and conditions for a particular delivery to be supplied to a particular customer. The transaction code used is OVL2.

6. An error V1032 occurs when we try to print the PL00 (packing slip in delivery). How can this error be avoided?

This error can be avoided by specifying packing in the delivery note.





7. Write down the menu path for entering Shipping Point in Delivery from Sales Order.

The menu path to enter a shipping point in delivery when releasing a sales order is as follows:

Select Sales document > Subsequent functions > Create delivery; the shipping point is automatically entered in the “Create delivery” option when you select it from the sales orders.

8. What is the purpose of using the delivery process?

The delivery process is used to send the items from the plant to the customer through the shipping point. The delivery process is also used to receive items back from a customer.

9. Can you create a delivery document with a reference?

You can create a delivery document with reference to a sales document or with reference to an inbound return sales document.

10. Give the menu path to define delivery document types.

The menu path to define delivery document types is as follows:

Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Deliveries > Define Delivery Types (Transaction code is OVLK).

11. Which delivery document type can be created without reference to the sales order document?

The delivery document type LO can be created without reference to the sales order document.

12. Give the menu path to define the delivery item category.

The menu path to define the delivery item category is:

Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Deliveries > Define Item Categories for Deliveries (Transaction code is OVLP).

13. Give the menu path to configure the delivery item category determination.

The menu path to define the delivery item category determination is:

Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Deliveries > Define Item Category Determination in Deliveries.





14. List the transaction codes to execute the delivery due list.

The transaction codes that can be used to execute the delivery due list are as follows:

VL10A—Sales orders, fast display

VL10B—Purchase orders, fast display

VL10C—Sales orders, items

VL10D—Purchase orders, items

VL10E—Sales orders, schedule lines

VL10F—Purchase orders, items schedule line

VL10G—Sales and purchase orders, fast display

VL10H—Sales and purchase orders, items fast display

VL10I—Sales and purchase orders, item schedule line

15. How do you describe a shipping point?

The shipping point can be described as a location linked to a plant from where items are delivered to/received from a customer. A plant may have more than one shipping point assigned to it.

16. Give the menu path to determine the shipping point.

The menu path to determine the shipping point is:

Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Basic Shipping Functions >Shipping Points and Goods Receiving Point Determination > Assign Shipping Points.

17. How can you transfer the stock in an organization from one plant to another under one company code?

Stock Transfer Flow Chart:

ME21N (PO by Ordering Plant)

VL10B (Background Delivery)

VL02n (Picking, Sr. No., and PGI)

VF01 (Pro-Forma Invoice)





MIGO (by Receiving Plant)

18. Suppose that you do not have stock but you can successfully press PGI, which iswrong. How can you configure a system that cannot press PGI without stock?

To configure the system in such a way that PGI cannot be pressed without stock, you must ensure that negative inventory is not allowed in MM.

19. Suppose that you have to view the serial number assigned in a delivery document. Which report can be used to view the serial number assigned in a delivery document?

To view the serial number assigned in a delivery document, you can use function modules with SERIAL_*—for example, SERIAL_LS_PRINT.

20. In which document can you enter the serial number for material?

You can enter the serial number for material in the delivery document (Extras > Select Sr. Nos).

21. What is picking? How can you configure picking?

Picking is defined as the process to select goods from the storage location to create a delivery. You can configure the picking by adopting the following menu path:

Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Picking.

22. Why is warehouse management used? How are goods placed in the warehouse?

Warehouse management is used for picking when a storage location is assigned to a warehouse defined in SYSTEM. You can place goods in the warehouse by performing the following process:

Receive items in an interim storage area.

Create transfer order in WM, the transfer order informs the warehouse staff about the location in the warehouse where the items should be placed.

After placing the items on the specified place, confirm the transfer order; the transfer order informs the system that the items have been moved successfully into the warehouse.

23. Why are delivery blocks used and how can they be configured?

They are used to block the stock so that it cannot be assigned to a delivery document, which is already blocked. You can configure the delivery blocks by adopting the following menu path:





Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Deliveries > Define Reasons for Blocking in Shipping > Deliveries: Blocking Reasons/Criteria.

24. Why is packing by item category used and how can it be configured?

The packing by item category is used to specify that the goods packing should be carried out at the item level. The packing by item category can be configured by adopting the following menu path:

Implementation Guide (IMG Menu) > Logistics Execution > Shipping > Packing > Packing ControlBy Item Category.

25. What is special stock? Which transaction code is used to view the special stock?

The special stock is the stock, which is delivered along with the packaging material. The special stock is considered to be the company’s property even when it is placed at the customer’s location. You can view the special stock by using the MMBE transaction code.

26. Why is route determination required and how can it be defined?

The route determination is used to decide the transportation route to deliver the goods to the customer’s location. The route is automatically suggested by SYSTEM on the basis of the sales document items in the sales order. Routes can be defined by adopting the following menu path:

Implementation Guide (IMG Menu) > Sales and Distribution > Basic Functions > Routes > Define Routes > Define Modes of Transport.

27. Give the menu path to define the shipping blocks.

The menu path to define the shipping blocks is:

Implementation Guide (IMG Menu) > Logistics Execution > Deliveries > Define Reasons for Blocking in Shipping > Deliveries: Blocking Reasons/Criteria.

28. Why are the factory calendars used?

The factory calendars are used for various purposes. Some calendars are used:

To decide the working days at a specific location.

To decide the day to create delivery so that a customer can receive the delivery on a working day.

29. Give the menu path to define the customer calendars.

The menu path to define the customer calendars is:





Implementation Guide (IMG Menu) > Sales and Distribution > Business Partners > Shipping > Define Customer Calendars.





CHAPTER 7BILLING

1. Compare the milestone with periodic billing.

The concept of billing a customer on completion of a particular work milestone or activity is known as milestone billing. However, the concept of billing a customer on completion of a specified time period is known as periodic billing.

2. What happens if there is a negative posting in billing document?

Negative posting on the debit side reduces the credit side of an account. However, when a negative posting is made on the credit side, it reduces the debit side of an account.

3. Compare billing and invoice.

When the goods are supplied to a customer, then an invoice is also sent. In other words, an invoice isa billing document. Apart from an invoice, the other billing documents are a credit memo and a debit memo.

4. How can you print an invoice multiple times?

Perform the following steps to print an invoice multiple times:

Use transaction code VF02.

Click Go To > Header > Output.

Select the output type, usually RD00.

Click on the Communication method.

Enter the number of copies you want to print in the “Number of messages” field.

5. How can you view the due date of the invoice after making a delivery and invoice?

You can view the due date of an invoice in the AR module. If you go to fbl5n and search for the customer, the due date appears in the overview screen.

6. List a few commonly used sales documents that result in order-related billing.

A few commonly used sales documents that result in order-related billing are:





CR—Credit memos

DR—Debit memos

7. What is the role of a pro forma invoice billing document?

The pro forma invoice is used for information purposes and does not post any financial amount to general ledger. For example, the pro forma invoice is used to represent the actual value of the products; however, the invoice is sent to the customer through the mail. No accounting document is generated fora pro forma invoice.

The pro forma invoice feature is also used for intra company stock transfer orders.

8. What is the role of the cancellation invoice?

The cancellation invoice is generated by the system when an invoice is cancelled for any business-related decision. The cancellation invoice reverses the related transactional effects made by the invoice that has been cancelled.

9. What is the role of an inter company invoice?

The inter company invoice refers to an internal invoice that is not passed to an external partner or sold-to party; rather, it is passed between two company codes belonging to the same business.

10. What is the difference between inter company sales and intra company sales?

The inter-company sale represents a sales transaction in which more than one company codes belongto the same client. However, the intra company sale represents a transaction within one company code—for example, movement of stock between two plants within a company code.

11. What do you mean by invoice lists?

The lists of billing documents that are combined into one document for a specific customer are known as invoice lists. You can create an invoice list by adopting the following menu path:

Customizing Implementation Guide (IMG Menu) > Sales and Distribution > Billing > Billing Documents > Invoice Lists.

The following two types of the invoice lists are provided in the standard system:

LR—Used for invoices and debit memos

LG—Used for credit memos





12. What is the difference between milestone billing and periodic billing?

The final bill at a completion of specific milestone in accordance to the services provided or the items sold is known as milestone billing. However, the periodic billing is a bill for a predefined date proposal that bills a customer at periodic intervals. Billing for a project milestone is an example of milestone billing and the bill for rental of an object is an example of periodic billing.

13. How do you perform a price adjustment when you have inputted an incorrect price in a completed invoice receipt and invoice issue for STO? How is a subsequent credit and debit in SD created for a subsequent credit and debit in MM?

We need to cancel the invoices created in MM and SD and change the price quoted in the STO PO. The new SD and MM invoices are created again, and the values are considered to be new prices. The appropriate account stock is automatically updated with the difference in the material value once the invoice in MIRO is created.

14. An accounting document is created when you release an invoice to accounting. Imagine that you have canceled the invoice. Is it then necessary for the account module to delete the respective accounting document?

No, it is not necessary to delete an accounting document when the respective invoice is canceled. The cancellation invoice reverses the related effects generated by the invoice.

15. List the user exits for self-billing.

The following are the user exits for self-billing:

EXIT_SYSTEMLVED4_001






16. Which setting is used to activate the account setting at the header and item level?

The VKOA transaction code is used to activate the accounts assignment settings at the header and





item levels.

17. How can you send an invoice by e-mail?

You first need to define the output type and use the NACE transaction code. Then the correct transmission medium needs to be defined in the V3 application. If the dispatch is being sent as own transaction, then dispatch time is selected as 3. After the attachment of correct output type, the VF31 transaction code is used to send the message.

18. How can you fix the error message “Error in account determination”?

Let’s consider a situation in which you create the bill successfully but the invoice is not released to accounting. This is called an error in account determination. You first need to check the account determination log in the invoice for which you need to perform the following step:

Transaction code VF02 > Environment > Acc.determ.analysis > Revenue Accounts.

After that you can proceed to fix the problem, as you now know the exact reason for the error.

19. Why is the account determination used by the system?

The account determination is used to determine that which ledger should be used to contain account-related information, and posting should be made to the relevant account only.

20. How can we combine non-inventory and inventory items in one invoice?

To combine noninventory and inventory items in one invoice, change the noninventory items to deliverable but not pickable. Then change the copy rule for Orders > Invoices and Deliveries > Invoices to Permit Invoice Combination. However, to create combined invoices, the PO number, payment terms, sales organization, and distribution channel must be identical, otherwise an undesirable invoice combination may be created.

21. Describe two types of credit processes.

Two types of the credit process are as follows:

First—A customer returns a previously purchased item and requests a credit.

Second—A customer receives credit not for an item but instead against some additional offer or scheme.

22. When is the debit process used?

The debit process is used when a customer is charged for a specific reason such as late payment,





excess scheme paid, and so on. This is a charge to the customer based on a specific business-related requirement.

23. What is an invoice correction request?

This is the document that helps you to correct the quantity and price of items on an incorrect invoice and to generate credit and debit memos. The procedure is called an invoice correction request. For eachitem, two entries are created: a credit item and a debit item. You can only correct the debit item.

24. Give the menu path to define the billing blocks.

The menu path to define the billing blocks is:

Implementation Guide (IMG Menu) > Sales and Distribution > Billing > Billing Documents > Define Blocking Reason for Billing.

25. What are the FI entries that are posted at the time of PGI and billing?

The following are the entries posted at the time of PGI and billing:

Debit (Dr) Credit (Cr)

At PGI A/c COGS A/c Inventory

At Billing Revenue A/c Customer A/c Sales

Tax A/c (s)

26. Define dunning. What do you need to configure before dunning?

The dunning is defined as a process that is used to generate a bill or invoice when a customer does not pay an amount according to the payment terms offered. Before performing dunning, you must configure the following:

Define the dunning area.

Define the dunning keys.

Define the dunning block reasons.

Configure the dunning procedure.

Assign the dunning procedure to customer accounts.

Define the correspondence types.

Configure the dunning run.









CHAPTER 8SALES RETURN, CREDIT, AND DEBIT MEMO

1. What is Sales Return?

Sales Return is the process of returning the purchased goods by the customer because of various reasons, such as damaged during transportation, inferior quality, overstocking, less or no sales uptake, or winding up of business by the customer (e.g., in case of trader or dealer). In these situations, a customer returns the goods purchased. As per the business agreement between the organization and customer, a credit note is issued in the name of the customer to settle the accounts.

2. What do you exactly mean by Credit Note and Debit Note?

Credit Note—This is a kind of billing that you generally raise when you need to credit a customer because of a sales return or an extra incentive or bonus offered.

Debit Note—This is a kind of billing that you need to charge a customer for reasons such as delayed payment made by the customer or check dishonor penalties.

3. Explain the system processing of Sales Return.

The process of Sales Return is the opposite of the process of sales. Sales Return is basically a process in which a customer returns the goods sold to him by your company for any business-related reasons. A return order is created (standard return order type is RE); then return delivery is created by performing the “post goods return” activity; and, then, a credit note is issued for that particular customer, thereby crediting the customer account.

4. Is a shipping point assigned to a plant used during the process of Sales Return?

Yes, a shipping point is assigned to a plant works as a “goods receiving point” for return delivery creation.

5. Can a Sales Return be denied for a credit note to a customer?

Yes, it is quite possible. This happens when the sales organization is not convinced by the reasons provided by the customer for sales return. This may also be possible if a sales return is not part of an agreement between the sales organization and the customer.

6. Can an additional scheme be issued to a customer through a credit note?

Yes, an additional sales scheme can be issued to a customer by issuing a credit note to a customer.





This may be based on the predefined or later defined understanding for a sales promotion between a sales organization and a customer.

7. What is a Return invoice?

A Return invoice is a credit memo issued to a customer for a sales return.

8. What is the process of charging the customer in the case that a customer does notreturn the returnable packaging material?

A sales order is created, and then a debit note is issued in the name of the customer for not returning the returnable packaging material.

9. What is the effect of a sales return on the inventory of material?

When you generate a “post goods receipt” at the time of creation of a return delivery, the inventory of the material is updated in the system. But, as per customization, the sales return stocks could be kept in restricted stocks inventory. This configuration setting is basically done to avoid the further sales of such stocks because this stock might have been returned for specific reasons, such as damage during transit or some quality-related issues. To bring back this stock to unrestricted stock inventory as per business planning, the materials management module has to generate a transfer posting process by using the Movement Type 453.

10. How are the goods returned by the customer handled?

The goods returned from the customers are adjusted along the sales order RE. The sales orders for the goods returned are prepared with reference to the billing number.





CHAPTER 9MISCELLANEOUS

1. Explain all the transaction codes related to the sales and distribution module.

The following is the list of all the transaction codes related to the SD module:

Transaction Code Description

V QuickstartRKCOWUSL

V+01 Provides the functionality to create Sales Call

V+02 Provides the functionality to create Telephone Call

V+03 Provides the functionality to create Sales Letter

V+11 Provides the functionality to create Direct Mailing

V+21 Provides the functionality to create Sales Prospect

V+22 Provides the functionality to create Competitor

V+23 Provides the functionality to create Sales Partner

V-01 Provides the functionality to create Sales Order

V-02 Provides the functionality to create Quotation

V-03 Provides the functionality to create Ordering Party (sales)

V-04 Provides the functionality to create Invoice Recipient (sales)

V-05 Provides the functionality to create Payer (sales)

V-06 Provides the functionality to create Consignee (sales)

V-07 Provides the functionality to create One-Time Customer (sales)

V-08 Provides the functionality to create Payer (centrally)

V-09 Provides the functionality to create Ordering Party (centrally)

V-11 Provides the functionality to create Carrier

V-12 Provides the functionality to create Customer hierarchy nodes

V-31 Provides the functionality to create Freight 1

V-32 Provides the functionality to create Freight 1 with Reference

V-33 Provides the functionality to change Freight 1



V-36 Provides the functionality to create Freight 1 with Reference





V-37 Provides the functionality to change Freight 2

V-38 Provides the functionality to display Freight 2

V-40 Provides the functionality to display Taxes (export)

V-41 Provides the functionality to create Material Price

V-42 Provides the functionality to create Material Price with Reference

V-43 Provides the functionality to change Material Price

V-44 Provides the functionality to display Material Price

V-45 Provides the functionality to create Price List

V-46 Provides the functionality to create Price List with Reference

V-47 Provides the functionality to change Price List

V-48 Provides the functionality to display Price List

V-49 Provides the functionality to create Customer-Specific Price

V-50 Provides the functionality to create Customer-Specific Price with Reference

V-51 Provides the functionality to change Customer Price

V-52 Provides the functionality to display Customer Price

V-61 Provides the functionality to create Customer Discount or Surcharge

V-62 Provides the functionality to create Customer Discount or Surcharge with Reference

V-63 Provides the functionality to change Customer Discount or Surcharge

V-64 Provides the functionality to display Customer Discount or Surcharge

V-65 Provides the functionality to create Material Discount or Surcharge

V-66 Provides the functionality to create Material Discount or Surcharge with Reference

V-67 Provides the functionality to change Material Discount or Surcharge

V-68 Provides the functionality to display Material Discount or Surcharge

V-69 Provides the functionality to create Price Group Discount or Surcharge

V-70 Provides the functionality to create Price Group Discount or Surcharge with Reference

V-71 Provides the functionality to change Price Group Discount or Surcharge

V-72 Provides the functionality to display Price Group Discount or Surcharge

V-73 Provides the functionality to create Material Price Group Discount or Surcharge

V-74 Provides the functionality to create Material Price Group Discount or Surcharge with Reference

V-75 Provides the functionality to change Material Price Group Discount or Surcharge

V-76 Provides the functionality to display Material Price Group Discount or Surcharge





V-77 Provides the functionality to create Customer or Material Price Group Discount or Surcharge

V-78 Provides the functionality to create Customer or Material Price Group Discount or Surcharge with Reference

V-79 Provides the functionality to create Customer or Material Price Group Discount or Surcharge

V-80 Provides the functionality to display Customer or Material Price Group Discount or Surcharge

V-81 Provides the functionality to create Customer or Material Discount or Surcharge

V-82 Provides the functionality to create Customer or Material Discount or Surcharge with Reference

V-83 Provides the functionality to change Customer or Material Discount or Surcharge

V-84 Provides the functionality to display Customer or Material Discount or Surcharge

V-85 Provides the functionality to create Price Group or Material Price Group Discount or Surcharge

V-86 Provides the functionality to create Price Group or Material Price Group Discount or Surcharge with Reference

V-87 Provides the functionality to change Price Group or Material Price Group Discount or Surcharge

V-88 Provides the functionality to display Price Group or Material Price Group Discount or Surcharge

V-89 Provides the functionality to create Price Group or Material Discount or Surcharge

V-90 Provides the functionality to create Price Group or Material Dis- count or Surcharge with Reference

V-91 Provides the functionality to change Price Group or Material Discount or Surcharge

V-92 Provides the functionality to display Price Group or Material Discount or Surcharge

V-93 Provides the functionality to create Domestic Taxes

V-94 Provides the functionality to create Domestic Taxes with Reference

V-95 Provides the functionality to change Domestic Taxes

V-96 Provides the functionality to display Domestic Taxes

V-97 Provides the functionality to create Cross-Border Taxes

V-98 Provides the functionality to create Cross-Border Taxes with Reference

V-99 Provides the functionality to change Cross-Border Taxes

V.00 Provides the functionality to list Incomplete Documents

V.01 Provides the functionality of Sales Order Error Log

V.02 Provides the functionality to list Incomplete Sales Orders

V.03 Provides the functionality to list Incomplete Inquiries

V.04 Provides the functionality to list Incomplete Quotations





V.05 Provides the functionality to list Incomplete Scheduled Agreements

V.06 Provides the functionality to list Incomplete Contracts

V.07 Provides the functionality of Periodic Billing

V.14 Sales Orders Blocked for Delivery

V.15 Provides the functionality to display Backorders

V.20 Provides the functionality to display Collective Delivery Process

V.21 Log of Collective Run

V.22 Provides the functionality to display Collective Runs

V.23 Release Orders for Billing

V.24 Provides the functionality to display Work List for Invoice Lists

V.25 Release Customer Expected Price

V.26 Selection by Object Status

V/03 Provides the functionality to create Condition Table (SD Price)

V/04 Provides the functionality to change Condition Table (Sales Price)

V/05 Provides the functionality to display Condition Table (Sales Price)

V/06 Condition Categories: SD Pricing

V/07 Maintain Access (Sales Price)

V/08 Conditions: Procedure for AV

V/09 Condition Types: Account Determination

V/10 Account Determination: Access Sequence

V/11 Conditions: Account Determination Procedure

V/12 Account Determination: Provides the functionality to create Table

V/13 Account Determination: Provides the functionality to change Table

V/14 Account Determination: Provides the functionality to display Table

V/21 View V_TVSA_NAC

V/22 View V_TVTY_NAC

V/23 View V_TVST_KOM

V/24 View V_TVTK_NAC

V/25 View V_TVFK_NAC

V/26 View V_TVKK_NAC

V/27 Conditions for Output Determination

V/30 Output Types (Sales Document)

V/31 View V_TNAPN Application V3





V/32 Sales Doc Output Determination Procedure


V/34 Maintain Condition Type Application V2

V/35 Customizing for Output Determination

V/36 Delivery Output Determination Procedure

V/37 Assign Customer


V/39 View V_TNAPR Application V6


V/41 View V_TVST_NAC

V/42 Output Determination Procedure (Billing Doc)

V/43 View V_TVAK_NAC

V/44 Maintain Condition Type Application DB

V/45 View V_TNAPN Application K1

V/46 Output Determination Procedure Customer


V/48 Access Sequences (Sales Document)


V/50 Access Sequence (Delivery)


V/52 Access Sequences Application V3


V/54 Access Sequence (Billing Document)

V/55 View V_TVBUR_NA

V/56 Output – Condition Table - Create Orders

V/57 Output – Condition Table - Change Order

V/58 Output – Condition Table - Display Order

V/59 Output – Condition Table - Create Delivery

V/60 Output – Condition Table - Change Delivery

V/61 Output – Condition Table - Display Delivery

V/62 Output – Condition Table - Create Bill Doc

V/63 Output – Condition Table - Change Bill Doc





V/64 Output – Condition Table - Display Bill Doc

V/65 Output Condition Table or Create Sales Support

V/66 Output Condition Table or Change Sales Support

V/67 Output Condition Table or Display Sales Support

V/68 Maintain Access Sequence (Sales Activity)

V/69 View V_TVAP_NAC

V/70 Maintain Condition Type Application K1

V/71 View V_TVLK_NAC

V/72 Output Determination Procedure (CAS)

V/73 View V_TVLP_NAC

V/76 Maintain Product Hierarchy

V/77 Output – Condition Table- Create Transport

V/78 Output – Condition Table- Change Transport

V/79 Output – Condition Table- Display Transport

V/80 Access Sequence (Transport)


V/82 Maintain condition type Application V7


V/84 Output Determination Transport

V/85 View V_TVKO_NAC

V/86 Conditions: V_T681F for B V1






V/92 Conditions: V_T681F for B K1

V/93 Output – Condition Table- Create Packaging

V/94 Output – Condition Table- Change Packaging

V/95 Output – Condition Table- Display Packaging

V/96 Access Sequence (Packaging)

V/97 Output Type Packaging

V/99 Output Determination Procedure Packaging





V/C1 Strategy Types: Batch Determination SD

V/C2 Access: Maintain Batch Determination SD

V/C3 Batch Determination Procedure for SD

V/C4 Search Types: Optimize Access

V/C5 SD Table T683C Search Procedure Determination

V/C6 Conditions: V_T681F for HV

V/C7 Condition Table: Create (Batches, SD)

V/C8 Condition Table: Change (Batch, SD)

V/C9 Condition Table: Display (Batches, SD)

V/CA Automatic Batch Determination in Sales Order

V/CL Automatic Batch Determination in Delivery

V/G1 Output Condition Table or Create Group

V/G2 Output Condition Table Change Group

V/G3 Output Condition Table or Display Group

V/G4 Access Sequence (Groups)

V/G5 View V_TNAPR Application K1

V/G6 Maintain Condition Type Application V5

V/G7 View V_TNAPR Application V1

V/G8 Output Determination Procedure Groups

V/G9 View VN_TNAPR Application V2

V/I1 Activation of Condition Index

V/I2 Set Up Condition Indices

V/I3 Conditions: Pricing SD – Index

V/I4 Conditions: Pricing SD – Index

V/I5 Condition: Pricing SD – Index in Background

V/I6 Provides the functionality to display conditions using index

V/LA Provides the functionality to create Pricing Report

V/LB Provides the functionality to change Pricing Report

V/LC Provides the functionality to display Pricing Report

V/LD Execute Pricing Report

V/LE Generate Pricing Reports

V/N1 Maintain Accesses (Free Goods – Sales)





V/N2 Provides the functionality to create Free Goods Table

V/N3 Provides the functionality to display Free Goods Table (SD)

V/N4 Free Goods Types – Sales

V/N5 Free Goods: Procedure for SD

V/N6 Free Goods Procedure Determination SD

V/T1 Maintain Profile

V/T2 Network Types

V/T3 Deadlines: Assign Network Profile to Delivery Type

V/T4 Maintain Deadline Functions

V/T5 Maintain Deviation Reasons

V/T6 Maintain Assignment to Plant

V/T7 Assign Shipping Deadlines to Shipment

V/T8 Shipping Deadlines – Graphics Settings

V101 Initial Sales Menu

V12LDV_A Provides the functionality to create Pricing Report

V12LDV_B Provides the functionality to change Pricing Report

V12LDV_C Provides the functionality to display Pricing Report

V12LDV_D Execute Pricing Report

V12LEV_A Provides the functionality to create Pricing Report (Rebate)

V12LEV_B Provides the functionality to change Pricing Report (Rebate)

V12LEV_C Provides the functionality to display Transactions (Rebate)

V12LEV_D Execute Pricing Report (Rebate)

V23 Sales Documents Blocked for Billing

V633 Coupling: Conversion of Customer Key

VA00 Initial Sales Menu

VA01 Provides the functionality to create Sales Order

VA02 Provides the functionality to change Sales Order

VA03 Provides the functionality to display Sales Order

VA05 List of Sales Orders

VA07 Compare Sales Purchasing (Order)

VA08 Compare Sales - Purchasing (Organization Department)

VA11 Provides the functionality to create Inquiry





VA12 Provides the functionality to change Inquiry

VA13 Provides the functionality to display Inquiry

VA14L Sales Documents Blocked for Delivery

VA15 Inquiries List

VA21 Provides the functionality to create Quotation

VA22 Provides the functionality to change Quotation

VA23 Provides the functionality to display Quotation

VA25 Quotations List

VA25N List of Quotations

VA26 Collective Processing for Quotations

VA31 Provides the functionality to create Scheduling Agreement

VA32 Provides the functionality to change Scheduling Agreement

VA33 Provides the functionality to display Scheduling Agreement

VA35 List of Scheduling Agreements

VA41 Provides the functionality to create Contract

VA42 Provides the functionality to change Contract

VA42W Workflow for Master Contract

VA43 Provides the functionality to display Contract

VA44 Actual Overhead: Sales Order

VA45 List of Contracts

VA46 Collective Subsequent Processing of Contracts

VA51 Provides the functionality to create Item Proposal

VA52 Provides the functionality to change Item Proposal

VA53 Provides the functionality to display Item Proposal

VA55 List of Item Proposals

VA88 Actual Settlement: Sales Orders

VA94 Load Commodity Codes for Japan

VA95 Merge Commodity Code or Import Code No.

VACF Commit. carried forward: Sales orders

VAKC Items in Sales Order Configuration

VAKP Configuration: Maintain T180

VALU Valuation Analysis

VAL_RELN Release Note Approval





VAM4 Merge: Japan - Commodity Code

VAN1 Actual Revaluation: Sales Order

VAP1 Provides the functionality to create Contact Person

VAP2 Provides the functionality to change Contact Person

VAP3 Provides the functionality to display Contact Person

VARA Archiving

VARC SD: User Guide to Archiving

VARCH Provides the functionality to change Report Variant

VARD Provides the functionality to display Report Variant

VASK Deleting Groups

VAUN Reload

VB/1 Rebate Number Ranges

VB/2 Rebate Agreement Type Maintenance

VB/3 Condition Type Groups Overview

VB/4 Condition Types in ConditionType Groups

VB/5 Assignment Condition – Condition Type Group

VB/6 Rebate Group Maintenance

VB/7 Rebate Agreement Settlement

VB/8 List Rebate Agreements

VB/9 Maintain Sales Deal Types

VB/A Promotion Type Maintenance

VB/B Copying Control Maintenance

VB/C Maintain Copying Control

VB/D Rebate Agreement Settlement

VB01 Provides the functionality to create Material Listing or Exclusion

VB02 Provides the functionality to change Material Listing or Exclusion

VB03 Provides the functionality to display Material Listing or Exclusion

VB04 Reference Material Listing or Exclusion

VB11 Provides the functionality to create Material Substitution

VB12 Provides the functionality to change Material Substitution

VB13 Provides the functionality to display Material Substitution

VB14 Reference Material Substitution





VB21 Provides the functionality to create Sales Deal

VB22 Provides the functionality to change Sales Deal

VB23 Provides the functionality to display Sales Promotion

VB25 List of Sales Deals

VB31 Provides the functionality to create Promotion

VB32 Provides the functionality to change Promotion

VB33 Provides the functionality to display Promotion

VB35 Promotions List

VB41 Provides the functionality to create Cross-Selling

VB42 Provides the functionality to change Cross-Selling

VB43 Provides the functionality to display Cross-Selling

VB44 Copy Cross-Selling

VBBLOCK Documents Blocked for Billing

VBELN_SET_GENERATE Generate Sales Order Set

VBG1 Provides the functionality to create Material Grouping

VBG2 Provides the functionality to change Material Grouping

VBG3 Provides the functionality to display Material Grouping

VBK0 Bonus Buy Selection

VBK1 Provides the functionality to create Bonus Buy

VBK2 Provides the functionality to change Bonus Buy

VBK3 Provides the functionality to display Bonus Buy

VBK6 Delete Bonus Buy

VBKA Bonus Buy: Access Sequences

VBKB Bonus Buy: Provides the functionality to create Condition Table

VBKC Bonus Buy: Provides the functionality to display Condition Table

VBKD Bonus Buy: Condition Types

VBKE Bonus Buy: Calculation Schema

VBKF Bonus Buy: Schema Determination

VBKG Bonus Buy: Field Catalog

VBN1 Free goods - Create (SD)

VBN3 Free goods - Display (SD)

VBO1 Provides the functionality to create Rebate Agreement

VBO2 Provides the functionality to change Rebate Agreement





VBO3 Provides the functionality to display Rebate Agreement

VBOE Currency Conversion Rebate Agreements

VBOF Rebate: Update Billing Documents

VC/1 List of Customers

VC/2 Customer Master Data Sheet

VC/A Sales Activity Description 01

VC/B Sales Activity Description 02

VC/C Sales Activity Description 03

VC/D Sales Activity Description 04

VC/E Sales Activity Description 05

VC/F Sales Activity Description 06

VC/G Sales Activity Description 07

VC/H Sales Activity Description 08

VC/I Sales Activity Description 09

VC/J Sales Activity Description 10

VC00 Sales Support

VC01 Provides the functionality to create Sales Activity

VC010102 Only Follow-up Activities

VC010104 Internet Mailing

VC01N Edit Sales Activity

VC01N_M Edit Mailing

VC02 Provides the functionality to change Sales Activity

Vc03 Provides the functionality to display Sales Activity

VC05 Sales Support Monitor

VC06 Parallel Processing for Address List

VC10 Report Tree - Select Addresses

VC15 Cross matching

VCC1 Payment Cards: Worklist

VCH1 Provides the functionality to create Batch Search Strategy

VCH2 Provides the functionality to change Batch Search Strategy

VCH3 Provides the functionality to display Batch Search Strategy

VCHECKBONUS Customizing Checks for Rebate

VCHECKT683 Customizing Check Pricing Procedure





VCHECKT685A Customizing Check Condition Types

VCHECKTVCPF Customizing Check Copying Control

VCHECKVOFA Customizing Check Billing Types

VCHP SD Table TVLP Deliveries: Items

VCOMP Completed SD Documents

VCR1 Competitive Products

VCTP Maintain Allocation Structure

VCU3 Provides the functionality to display Incompletion Log

VCUAC Provides the functionality to display Anti-dumping – Quantity-Dependent

VCUAE Provides the functionality to display Anti-dumping – Weight-Dependent

VCUDC Provides the functionality to display 3rd Country – Quantity-dependent

VCUDE Provides the functionality to display 3rd Country – Weight-Dependent

VCUN Reload

VCUP1 Provides the functionality to display Preference – Quantity-Dependent

VCUP2 Provides the functionality to display Preference – Weight-Dependent

VCUPC Provides the functionality to display Pharmaceuticals Production – Quantity-Dependent

VCUPF Provides the functionality to display Pharmaceuticals Production – Weight-Dependent

VCUST Customer List

VCUZ1 Provides the functionality to display Ceiling – Quantity-Dependent

VCUZ2 Provides the functionality to display Ceiling – Weight-Dependent

VCUZC Provides the functionality to display Quota – Quantity-Dependent

VCUZE Provides the functionality to display Quota – Weight- Dependent

VCUZP Provides the functionality to display Ceilings – Percentage

VD01 Provides the functionality to create Customer (Sales)

VD02 Provides the functionality to change Customer (Sales)

VD03 Provides the functionality to display Customer (Sales)

VD04 Customer Changes (SD)

VD05 Block customer (sales)

VD06 Mark customer for deletion (sales)

VD07 Reference doc determination for referring customer

VD51 Maintain Customer-Material Info





VD52 Maintain Customer-Material Info

VD53 Provides the functionality to display Customer-Material Info

VD54 Provides the functionality to display Customer-Material Info

VD59 List Customer-Material Info

VDBLOCK Documents Blocked for Delivery

VDDI EMU currency conversion customer Master

VDF1 Provides the functionality to display Format Date Type/Period

VDH1 Customer Hierarchy Maintenance (SD)

VDH1N Provides the functionality to display/Maintain Customer Hierarchy

VDH2 Provides the functionality to display Customer Hierarchy

VE01 INTRASTAT: Selection Dispatch to EU

VE02 INTRASTAT: Create Form – Germany

VE03 INTRASTAT: Create File – Germany

VE04 EXTRASTAT: Data Selection for Export

VE05 EXTRASTAT: Create File – Germany

VE06 INTRASTAT: Paper Form – Belgian

VE07 Provides the functionality to create INTRASTAT Form for France

VE08 Provides the functionality to create INTRASTAT File for Italy

VE09 Provides the functionality to create INTRASTAT File for Belgium

VE10 Provides the functionality to create INTRASTAT File for Holland

VE11 Provides the functionality to create INTRASTAT File for Spain

VE12 Provides the functionality to create INTRASTAT Form for Holland

VE13 KOBRA data selection: export Germany

VE14 Provides the functionality to create KOBRA file for Germany

VE15 Provides the functionality to create disk - INTRA/EXTRA/KOBRA/VAR

VE16 Provides the functionality to create INTRASTAT form for Austria

VE17 Provides the functionality to create INTRASTAT form for Sweden

VE18 SED data selection for USA exporters

VE19 Provides the functionality to create SED form for USA

VE20 Provides the functionality to create AERP file for USA

VE21 VAR: Selection of billing documents Switzerland

VE22 Provides the functionality to create VAR form for Switzerland





VE23 V.A.R.: File - Switzerland

VE24 Commodity Code Number Information (old)

VE25 SED: Selection: USA Carriers

VE26 Number of CAP Products List

VE27 HMF: Selection - USA

VE28 Name of Market Organization

VE29 Assigned Documents for Each License

VE30 Existing licenses

VE31 Blocked SD Documents

VE32 INTRASTAT: Paper Form - Ireland

VE33 INTRASTAT: Paper Form - U.K.

VE34 INTRASTAT: Paper Form - Belgian

VE35 Number of Market Organization

VE36 Group for CAP Products

VE37 INTRASTAT: File - France

VE38 INTRASTAT: Selection Simulation - EU

VE39 EXTRASTAT: Selection Simulation

VE40 KOBRA: Selection Simulation

VE41 VAR: Selection of billing documents Switzerland

VE42 INTRASTAT: File - Denmark

VE43 SED: Selection Exp. USA Simulation

VE44 SED: Select Carrier USA Simulation

VE45 INTRASTAT: Paper Form - Greece

VE46 INTRASTAT: File - Finland

VE47 PRODCOM No.

VE48 Customs Quota Code

VE49 Code for Pharmaceutical Products

VE50 Legal Regulations

VE51 Legal Regulation/License Type

VE52 Country or Legal Regulations

VE53 Export Situation for a Country

VE54 Preference Determination: Collective

VE55 Preference Determination: Individual





VE56 Check Export Control for Consistency

VE57 Country Classification

VE58 Product Classification

VE59 Legal Regulations or Country Grouping

VE60 Expenditure Control Class According to Legal Regulations

VE61 Legal Regulations or Embargo Group

VE62 Material Group According to Legal Regulations

VE63 Customs Areas

VE64 Commodity Code or Customs Areas

VE65 Preference Regulations or Percentage Rates

VE66 Preference Procedure

VE67 Aggregate Vendor Declarations

VE68 Request Vendor Declarations

VE69 Incompletion Log

VE70 Place of Manufacture

VE71 Preference: Determine Customs Area

VE72 Export - Billing Documents

VE73 Goods Catalog: Create Document

VE74 Goods Catalog: Create Diskette

VE75 Preference Code

VE76 Anti-dumping Code

VE77 Preference: Tariff Alternation

VE78 Plant Parameters for Vendor Declaration

VE79 Quota Code Determination

VE80 Assign Chapter to Section

VE81 Check Report: General FT Data

VE82 Check Report: Export Control Data

VE83 Check Report: Preference Data

VE85 Provides the functionality to change Statistical Value - Import

VE86 Provides the functionality to display Statistical Value - Import

VE87 Provides the functionality to change Statistical Value - Subcontracting

VE88 Provides the functionality to change Statistical Value - Export





VE89 Provides the functionality to display Statistical Value - Export

VE90 Provides the functionality to change Preference Values

VE91 Provides the functionality to display Preference Values

VE92 Provides the functionality to create INTRASTAT tape Luxembourg

VE93 EDI-CUSTEC Austria

VE94 Load Commodity Code for EU Countries

VE95 Provides the functionality to create INTRASTAT papers: Portugal

VE96 EXTRASTAT Data Select: Initial. Screen

VE97 Provides the functionality to create EXTRASTAT tape: Netherlands

VE98 Sales Invoice Values per Period

VE99 Provides the functionality to create Document - Austria

VEA1 FT-Create Commodity Code Import

VEA2 FT: Create Commodity Code Export

VEA3 EXTRASTAT: File Version France



VEB1 Period-End Closings: Control

VEB5 Calculate Assemblies Individually

VEB6 Calculate Assemblies Collectively

VEB9 Customer Exits: Print Control

VECN Profitability and Sales Accounting

VECS Legal Control: Special Character Code

VECZ INTRASTAT: File - Czech Republic

VED1 Print Parameters for Export Docs

VED2 Form Data Control

VEFU Foreign Trade: Add INTRASTAT Data

VEG1 Handling Unit Group 1



VEG4 Handling Unit 4


VEGK FT: Combination Bus Transaction Type - Procedure

VEGR Material Group: Packaging Materials





VEHU INTRASTAT: File - Hungary

VEI0 Provides the functionality to create INTRASTAT CUSDEC EDI IE

VEI1 Provides the functionality to display IDoc Import

VEI3 Provides the functionality to Display Statistical Value - Subcontracting

VEI4 Merge: Remaining Commodity Codes

VEI5 Provides the functionality to create value limit subcontracting

VEI6 EDI: IDoc List - Import Basis

VEI7 Provides the functionality to create INTRASTAT CUSDEC EDI GB

VEI8 Provides the functionality to create INTRASTAT CUSDEC EDI AT

VEI9 Provides the functionality to create INTRASTAT CUSDEC EDI ES

VEIA Provides the functionality to create INTRASTAT CUSDEC EDI SE

VEIAI INTRASTAT Archiving

VEIB Provides the functionality to create INTRASTAT CUSDEC EDI PT

VEIC Provides the functionality to create INTRASTAT CUSDEC EDI FI

VEID Provides the functionality to create INTRASTAT CUSDEC EDI LU

VEIE SAPMSED8: Call EXPINV02

VEII SAPMSED8: Call IMPINV01

VEIV Foreign Trade: Add EXTRASTAT Data

VEIW Provides the functionality to create file INTRA or EXTRA or KOBRA

VEKU Foreign Trade: Provides the functionality to change KOBRA Documents

VEM4 Merge: EU - Commodity Code

VEPL Provides the functionality to create INTRASTAT CUSDEC EDI PL

VEPR Customs Log

VESK Provides the functionality to create INTRASTAT CUSDEC EDI SK

VEU4 Load Commodity Code - Other Countries

VF00 Access Billing

VF01 Provides the functionality to create Billing Document

VF02 Provides the functionality to change Billing Document

VF03 Provides the functionality to display Billing Document

VF04 Maintain Billing Due List

VF05 List Billing Documents

VF06 Batch Billing





VF07 Provides the functionality to display Billing Document from Archive

VF08 Billing for External Delivery

VF11 Cancel Billing Document

VF21 Provides the functionality to create Invoice List

VF22 Provides the functionality to change Invoice List

VF23 Provides the functionality to display Invoice List

VF24 Edit Work List for Invoice Lists

VF25 List of Invoice Lists

VF26 Cancellation Invoice List

VF27 Provides the functionality to display Invoice List From Archive

VF31 Output from Billing Documents

VF42 Update Sales Documents

VF44 Revenue Recognition: Worklist

VF45 Revenue Recognition: Revenue Report

VF46 Revenue Recognition: Cancellation

VF47 Revenue Recognition: Consistency Check

VFBZ Scale Basis for Pricing

VFLI Log Tax Exemption

VFP1 Set Billing Date

VFRB Retro-billing

VFS3 Adjusting Info Structure S060

VFSN Reorganization Info Structure S060

VFUN Reload

VFX2 Provides the functionality to display Blocked Billing Documents

VFX3 List Blocked Billing Documents

VG01 Provides the functionality to create Group

VG02 Provides the functionality to change Group

VG03 Provides the functionality to display Group

VGK1 Provides the functionality to create Group for Delivery

VGK2 Provides the functionality to change Group for Delivery

VGK3 Provides the functionality to display Group for Delivery

VGL1 Provides the functionality to create Group for Delivery





VGL2 Provides the functionality to change Group for Delivery

VGL3 Provides the functionality to display Group for Delivery

VF48 Revenue Recognition: Compare Report

VFAE Archive EXTRASTAT Documents

VFAI Archive INTRASTAT Documents

VFBS Next Screen Control

VFBV Reorganization of discount-rel. Data

VFBWG Bulkiness and Minimum Weights

VGM1 Provides the functionality to create Group for Freight List

VGM2 Provides the functionality to change Group for Freight List

VGM3 Provides the functionality to display Group for Freight List

VGW1 Provides the functionality to create Picking Wave

VGW2 Provides the functionality to change Picking Waves

VGW3 Provides the functionality to display Picking Waves

VHAR Maintain or Create Packaging Material Types

VHZU Allowed Packaging Material Types

VI00 Shipment Costs

VI01 Provides the functionality to create Shipment Costs

VI02 Provides the functionality to change Shipment Costs

VI03 Provides the functionality to display Shipment Costs

VI04 Provides the functionality to create Shipment Cost Worklist

VI05 Provides the functionality to change Shipment Cost Worklist

VI06 Collective Run In Background

VI08 Provides the functionality to display FT Data In Purchasing Document

VI09 Provides the functionality to change FT Data in Purchasing Document

VI10 Provides the functionality to display FT Data in Billing Document

VI11 List Shipment Costs: Calculation

VI12 List Shipment Costs: Settlement

VI14 Provides the functionality to change FT Data in Billing Document

VI15 Provides the functionality to display Logs (application log)

VI16 Logs for Worklist Shipment

VI17 Provides the functionality to display FT Data in Inbound Delivery

VI18 Provides the functionality to display Anti-dumping





VI19 Provides the functionality to display Third-Country Customs Duties

VI20 Provides the functionality to display Customs Quota

VI21 Provides the functionality to display Pharmaceutical Products

VI22 Provides the functionality to display Customs Exemption

VI23 Provides the functionality to display Preferential Customs Duties

VI24 Code Number Information - Import

VI25 Provides the functionality to display Gross Price - Customs

VI26 Provides the functionality to display Surcharge/Discount - Customs

VI27 Provides the functionality to display Freight - Customs

VI28 EDI: Customs ID Number - Vendor

VI29 Incompletion - Foreign Trade Data

VI30 Declaration to Authorities: Exclusion

VI31 Code Determination-Pharmaceutical Products

VI32 Code Determination - Anti-dumping

VI33 Customs Exemption

VI34 Preferential Customs Duty Rate

VI35 Third-Country Customs Duty Rate

VI36 CAS Number

VI37 Import Simulation Control

VI38 Determination of Verification Docs

VI39 Authority for Verification Docs

VI40 Preference Type

VI41 Verification Document Type

VI42 Document Type (Export/Import)

VI43 Definition of Section

VI44 Assign Chapter to Section

VI45 Export > Import Conversion

VI46 Conversion: Mode of Transport

VI47 Conversion of Business Transaction Type

VI48 Conversion of Customs Offices

VI49 Foreign Trade Data Control in Document

VI50 Conversion: Import or Export Procedure





VI51 Define Payment Guarantee Procedure

VI52 Define Form of Payment Guarantee

VI53 Provides the functionality to change FT Data in Inbound Delivery

VI54 Customs Approval Numbers

VI55 Approval Number per Plant

VI56 EDI: Customs ID Number - Customer

VI57 Legal Control - Order Header

VI58 Legal Control - Order Item

VI59 Legal Control - Delivery Header

VI60 Legal Control - Delivery Item

VI61 Conversion - Reference Country

VI62 Conversion - Reference Country

VI63 Assign Delivery Item Categories

VI64 Provides the functionality to display FT Data in Outbound Delivery

VI65 Maintain Market Organizations

VI66 Maintain No. of Market Organizations

VI67 Maintain CAP Products List Numbers

VI68 Control Commodity Code/Code Number

VI69 Maintain CAP Products Group

VI70 Default Values - Stock Transport Order

VI71 Provides the functionality to change Preference Values

VI72 Provides the functionality to display Insurance - Customs

VI73 Maintain Vendor Declaration

VI74 Provides the functionality to display Vendor Declaration

VI75 Vendor Declarations - Dunning Notice

VI76 Mode of Transport - Office of Exit

VI77 Provides the functionality to change FT Data in Outbound Delivery

VI78 Foreign Trade: Country Data

VI79 Provides the functionality to display FT Data in Goods Receipt

VI80 Provides the functionality to change FT Data in Goods Receipt

VI81 Check Report: CAP Products

VI82 Check General Customer Master Data





VI83 Check Customer Master/Legal Control

VI84 Document Payments: Check Customer Master

VI85 Incompleteness: Foreign Trade Vendor

VI86 Incompleteness: Cross-Plant

VI87 Foreign Trade: Header Data Proposal

VI88 Input Table for Preference Determination

VI89 Customs Law Description

VI90 Fill Foreign Components in BOMs

VI91 Provides the functionality to display Foreign Components in BOMs

VI92 Preference: Alternative Comm. Code

VI93 Foreign Trade: Import Control

VI94 Load Import Code Numbers - EU Countries

VI95 Default Value of Foreign Trade Header Data

VI96 Customer Exits: Default Values

VI97 Define Control Codes

VI98 Receipt-Basis for Intercompany Billing

VI99 Returns and Credit Memos

VIAR Archive Shipment Costs

VIB1 Send IDoc Output

VIB2 Call Print Program From VI10 or VI14

VIB3 Foreign Trade Output Status

VIB4 Print Transaction: Initial Processing

VIB5 Print Transaction: Repeat Processing

VIB6 Print Transaction: Error in Processing

VIB7 Send IDoc Output - Initial Processing

VIB8 Send IDoc Output - Repeat Processing

VIB9 Send IDoc Output - Error in Processing

VIBA Send IDoc Output-AES-Initial Processing

VIBB Send IDoc Output-AES-Repeat Processing

VIBC Send IDoc Output-AES-Error in Processing

VIBD Printing: Analysis Form Data Audit

VIBN Monitor Messages

VIC00 Consistency Check IMG Shipment Cost Calculation





VICC Convert Format Currency Field

VICI Call shipment info via CALL TRANS

VIE4 Incompleteness Periodic Declarations

VIFBW Reorganization Shipment Costs in BW

VII4 Merge: Rest - Import Code Number

VII5 Import Control in the Material Document

VIIM FT: Optional Cockpit: Purchase Order

VIJ1 Journal Import

VIJ2 Journal Export

VILG FT: Country Group Defi nition

VILI FT: Export Deliveries Journal

VIM4 Merge: EU - Import Code Number

VIM6 Customer Exits: Data Selection

VIMM Declaration Receipts or Dispatches Mineral Oil Production

VIMU Foreign Trade: Comparison of Codes

VINC List of Incomplete SD Documents

VINK Import Processing: Quota Number

VINP Import Processing: Ceiling Numbers

VIPL Provides the functionality to display Customs Duty for Ceiling

VIR1 Import Reorganization - Incompleteness

VIR2 Export Reorganization - Incompleteness

VIRL Reload Shipments

VIS3 Check program: Cross-Plant

VISW Service: Information: Keywords

VIU4 Load Import Code No.-Other Countries

VIUC FT Upload: Convert custom duty types

VIUL Foreign Trade: Data Upload

VIZB Import Processing Means of Transport

VIZN Import Processing Type of Goods ID Seal

VIZP Import Processing: Package Type

VK+C Condition Master Data Check

VK01 Conditions: Dialog Box for Condition Element





VK03 Provides the functionality to create Condition Table

VK04 Provides the functionality to change Condition Table

VK05 Provides the functionality to display Condition Table

VK11 Provides the functionality to create Condition

VK12 Provides the functionality to change Condition

VK13 Provides the functionality to display Condition

VK14 Provides the functionality to create Condition with Reference

VK15 Provides the functionality to create Condition

VK16 Provides the functionality to create Condition with Reference

VK17 Provides the functionality to change Condition

VK18 Provides the functionality to display Condition

VK19 Provides the functionality to change Condition Without Menu

VK20 Provides the functionality to display Condition Without Menu

VK30 Maintain Variant Conditions

VK31 Condition Maintenance: Create

VK32 Condition Maintenance: Change

VK33 Condition Maintenance: Display

VK34 Condition Maintenance: Create with Reference

VKA1 Archiving Conditions

VKA2 Deleting Conditions

VKA3 Reloading Conditions

VKA4 Archiving Agreements

VKA5 Deleting Agreements

VKA6 Reloading Agreements

VKAR Read Archive File

VKAW Generate Archive File

VKC1 Provides the functionality to create General Strategy

VKC2 Provides the functionality to change General Strategy

VKC3 Provides the functionality to display General Strategy

VKDV Number Range Maintenance: RV_SNKOM

VKM1 Blocked SD Documents

VKM2 Released SD Documents

VKM3 Sales Document





VKM5 Delivery

VKOA Account Determination

VKOE Assign GL Accounts

VKP0 Sales Price Calculation

VKP2 Provides the functionality to display POS Conditions

VKP3 Pricing Document for Material

VKP4 Pricing Document for Organizational Structure

VKP5 Provides the functionality to create Calculation

VKP6 Provides the functionality to change Pricing Document

VKP7 Provides the functionality to display Pricing Document

VKP8 Provides the functionality to display Price Calculation

VKP9 Currency Conversion in Price Calculation

VKPA Archiving

VKPB Sales price calculation in background run

VKPR Read Archive File

VKU1 Report: Revaluation at Retail for Retail Price Change

VKU10 Correction of Valuation at Retail

VKU11 Delete Count Document Items

VKU2 Total Revaluation at Retail

VKU3 Partial Revaluation at Retail

VKU4 Retail Revaluation Docs for Material

VKU5 Provides the functionality to display Retail Revaluation Document

VKU6 Revaluation at Retail: Selection of Retail Price changes

VKU7 Report: Total Revaluation for Retail Price Change

VKU8 Test Transaction BAPI Count List

VKU9 Retail Revaluation Correction: List Display

VKUN Reload

VKVF Conditions: Dialog Box for Condition Element

VKVG Maintain Condition Elements

VKVI General View Maintenance: Enter Values—Transaction VKVI

VKXX Provides the functionality to create Test for RKA

VKYY Provides the functionality to change Test for RKA





VKZZ Test for RKS-Surcharge Conditions

VL00 Shipping

VL01 Provides the functionality to create Delivery

VL01N Provides the functionality to create Outbound Delivery with Order Reference

VL01NO Provides the functionality to create Outbound Delivery w/o Order Reference

VL02 Provides the functionality to change Outbound Delivery

VL03 Provides the functionality to display Outbound Delivery

VL04 Process Delivery Due List

VL06 Delivery Monitor

VL06C List Outbound Deliveries for Confirmation

VL06D Outbound Deliveries for Distribution

VL06F General Delivery List - Outbound Delivery

VL06G List of Outbound Deliveries for Goods Issue

VL06I Inbound Delivery Monitor

VL06IC Confirmation of Putaway Inbound Delivery

VL06ID Inbound Deliveries for Distribution

VL06IF Selection Inbound Deliveries

VL06IG Inbound Deliveries for Goods Receipt

VL06IP Inbound Deliveries for Putaway

VL06L Outbound Deliveries to be Loaded

VL06O Outbound Delivery Monitor

VL06P List of Outbound Deliveries for Picking

VL06T List Outbound Deliveries (Transport Planning)

VL06U List of Unchecked Outbound Deliveries

VL08 Confirmation of Picking Request

VL09 Cancel Goods Issue for Delivery Note

VL10 Edit User-specific Delivery List

VL10A Sales Orders Due for Delivery

VL10B Purchase Orders Due for Delivery

VL10BATCH VL10 Background Planning

VL10BATCH_A Background Planning VL10 (0 Tbstrps)

VL10BATCH_B Background Planning VL10 (3 Tbstrps)

VL10C Order Items Due for Delivery





VL10CU Delivery Scenarios

VL10CUA User Roles (List Profiles)

VL10CUC Provides the functionality to create Profile - Delivery

VL10CUE Exclude Function Code Profile

VL10CUF F Code VL10 Profile

VL10CUV Delivery Scenarios

VL10CU_ALL User Roles (List Profiles)

VL10D Purchase Order Items Due for Delivery

VL10E Order Schedule Lines Due for Delivery

VL10F Purchase Order Schedule Lines Due for Delivery

VL10G Documents Due for Delivery

VL10H Items Due for Delivery

VL10I Schedule Lines Due for Delivery

VL10U Cross-System Deliveries

VL12 Delivery Creation in Background

VL21 Post Goods Issue in Background

VL22 Provides the functionality to display Delivery Change Documents

VL23 Goods Issue (Background Processing)

VL30 Shipping

VL31 Provides the functionality to create Inbound Delivery

VL31W Provides the functionality to create Inbound Delivery Notification (WEB)

VL32 Provides the functionality to change Inbound Delivery

VL32W Provides the functionality to change Inbound Delivery Notification (WEB)

VL33 Provides the functionality to display Inbound Delivery

VL34 Worklist Inbound Deliveries

VL35 Provides the functionality to create Wave Picks: Delivery/Time

VL35_S Provides the functionality to create Wave Picks: Shipment

VL35_ST Provides the functionality to create Wave Picks: Shipment/Time

VL36 Provides the functionality to change Picking Waves

VL37 Wave Pick Monitor

VL38 Groups Created: Wave Picks

VL39 Billing Documents for Wave Picks





VL41 Provides the functionality to create Rough GR

VL42 Provides the functionality to change Rough GR

VL43 Provides the functionality to display Rough GR

VL51 Provides the functionality to create Route Schedule: Initial Screen

VL52 Provides the functionality to change Route Schedule: Initial Screen

VL53 Provides the functionality to display Route Schedule: Initial Screen

VL70 Output From Picking Lists

VL71 Output from Outbound Deliveries

VL72 Output from Groups of Deliveries

VL73 Selection Program for Issuing Output

VL74 Output from Handling Units

VL75 Shipping Notification Output

VL76 Output from Rough Goods Receipt

VLAL Archive Deliveries

VLBT Plan Delivery Creation as a Job

VLE1 Picking with Picking Waves

VLLA RWE: Picking/Goods Issue Analysis

VLLC RWE: Archive Data

VLLD Rough Workload Forecast: Delete Log

VLLE RWE: Goods Receipt/Putaway Analysis

VLLF Picking Waves: Archive Data

VLLG RWE: Analyze Complete Overview

VLLP Rough Workload Forecast: Display Log

VLLQ RWE: Returns to Vendor Analysis

VLLR RWE: Customer/Store Return Analysis

VLLS Standard Analyses Setting App 42

VLLV W&S: Control RWE/Picking Waves

VLMOVE HU Goods Movements

VLPOD POD - Change Outbound Delivery

VLPODA POD - Display Outbound Delivery

VLPODF Worklist: POD Subsequent Processing

VLPODL Worklist: POD Deliveries

VLPODQ Automatic Proof of Delivery Confirmation





VLPODW1 Proof of Delivery (Communicator)

VLPODW2 Proof of Delivery via WEB

VLPP Packing Request for Item Categories

VLRL Reload Delivery

VLSP Subsequent Outbound- Delivery Split

VLSPS Outbound Delivery Split via HU Scan

VLUNIV Provides the functionality to change Delivery (General)

VM01 Provides the functionality to create Hazardous Material

VM02 Provides the functionality to change Hazardous Material

VM03 Provides the functionality to display Hazardous Material

VM04 Filling Hazardous Substance Table MGEF

VMG1 Provides the functionality to create Material Group 1





VN01 Number Assignment for SD Documents

VN03 Number Assignment for Document Conditions

VN04 Number Assignment for Master Conditions

VN05 Number Assignment for Address List

VN06 Provides the functionality to create Number Interval-Sales Activities

VN07 Maintain Number Range for Shipments

VN08 Number Range for Shipment Costs

VN10 Number Range Maintenance: SD_SCALE

VNE1 Output: Create Condition Table-Shipment Notification

VNE2 Output-Condition Table-Change Shipment Notification

VNE4 Access Sequences (Shipment Notification)

VNE5 View V_TNAPN Appl. E1

VNE6 Output Determination Procedure-Shipment Notification

VNE7 View V_TVLK_NLA (Shipment Notification)

VNE8 View V_TVLK_NGW (Rough GI)

VNE9 Conditions: V_T681F for B E1





VNEA Output: Create Condition Table - Rough GR

VNEB Output-Condition Table-Change Shipment Notification

VNEC Output Types (Rough Goods Receipt)

VNED Access Sequences (Rough GR)

VNEE View V_TNAPN Appl. M1

VNEF Output Determination Procedure - Rough GR

VNEG Conditions: V_T681F for B M1

VNEH View V_TNAPR Appl. E1

VNEI View V_TNAPR Appl. M1

VNKP Number Range Maintenance: RV_VEKP

VNOP C SD-VN Maintain TVAK

VNPU Partner Conversion

VN_TP02 Salutation

VN_TP04 Marital Property Regime

VN_TP05 Employee Group

VN_TP06 Rating

VN_TP07 Credit Rating Institute

VN_TP10 Loan to Manager

VN_TP11 Employment Status

VN_TP12 German Banking Act Credit Info

VN_TP13 Target Group

VN_TP18 Undesirable Customer

VOA0 Order Information Configuration

VOA01 User Exit Lists Sales

VOA1 Inquiry Information Configuration

VOA2 Quotation Information Configuration

VOA3 Configuration of Scheduled Agreement Info

VOA4 Contract Information Configuration

VOA5 Product Proposal Info. Configuration

VOB3 Comparison: Billing Documents and Statistics

VOBO Configuration for Backorder Processing

VOC0 Contract List Configuration





VOC1 Customizing for List of Addresses

VOD5 Configuration Customer Independent Requisition Info

VOE1 Maintain EDPST

VOE2 SD EDI Customer/Vendor

VOE3 SD EDI Partner Functions

VOE4 SD EDI Conversion

VOEX Incompleteness: Billing Document

VOF0 Configuration of Billing Information

VOF01 User Exit Lists Sales

VOF1 Configuration: Collective Billing

VOF2 Configuration Invoice List Info

VOF3 Edit Work List for Invoice Lists

VOFA Billing Doc: Document Type

VOFM Configuration for Requisition Formulae

VOFN Call Up Transaction VOFM

VOIM Incompleteness: Purchase Order

VOK0 Conditions: Pricing in Customizing

VOK1 Account Determination: Customizing

VOK2 Output Determination

VOK3 Message Determination: Purchasing

VOK4 Output Determination: Inventory Management

VOK8 Condition Exclusion Assign Procedure V

VOKF Configuration Release of CustPrice

VOKR Configuration of Credit Release

VOL0 Delivery Information Configuration

VOL01 User Exit Lists Sales

VOL1 Configuration: Collective Delivery Procedure

VOL6 Configure Information On

VOL7 Settings for Packing

VOLI Incompleteness: Delivery

VONC Output Form for Each Group

VOP2 Configuration: Partner

VOPAN Customizing Partners





VOR1 Joint Master Data: Distribution Channel

VOR2 Joint Master Data: Division

VORA Archiving Control for Sales Document

VORB Group Reference Sales Document Types

VORI Archiving Control Shipment Costs

VORK Archiving Control for Sales Activity

VORL Archiving Control for Delivery

VORN Central Archiving Control

VORP Repairs Procedure: Short Texts Transaction

VORR Archiving Control for Billing Documents

VORS Group Reference Procedures

VORT Archiving Control for Shipments

VORV Repair Procedure

VOTX Configuration: Texts

VOV6 Maintain Schedule Line Categories

VOV7 Maintain Item Categories

VOV8 Document Type Maintenance

VOVA Default Values for Material

VOVB Screen Sequence Group Maintenance

VOVC Item Field Selection Group Maintenance

VOVD Header Field Selection Group

VOVF Variant Matching Procedure

VOVG Define Characteristic Overview

VOVL Cancellation Rules

VOVM Cancellation Procedures

VOVN Assignment Rules/Cancellation Procedure

VOVP Rule Table for Date Determination

VOVQ Cancellation Reasons

VOVR Default Values for Contract

VOVS Define Status in Overview Screen

VOW1 User Assignment GRUKO_WF

VOWE Incompleteness: Goods Receipt

VP01 Maintain Print Parameters





VP01SHP Print Parameter Maintenance Shipping

VP01TRA Print Parameter Maintenance Transport

VP01_PAG Maintain Print Parameters

VP01_SD Maintain Print Parameters SD

VP01_TC Print Parameter Maintenance Trading Center

VP94 Load Import Code No. for Japan

VPAR Archiving Preference Logs

VPBD Requirement for Packing in Delivery

VPE1 Provides the functionality to create Sales Representative

VPE2 Provides the functionality to change Sales Representative

VPE3 Provides the functionality to display Sales Representative

VPM4 Merge: Japan - Import Code Number

VPN1 Number Range for Contact Person

VPNR View of the Active PNR in 1A

VPRE PRICAT Manual Creation

VPRICAT Maintain and Create Price Catalog

VPW1 Portal Workset Administration

VPWL Portal Target Administration

VRLI FT: Reorganization T609S Delivery

VRRE Returns Delivery for RMA Order

VRWE FT: Reorganization T609S Goods Receipt

VS00 SD Main Menu for Customer

VS01 Provides the functionality to create Scale

VS02 Provides the functionality to change Scale

VS03 Provides the functionality to display Scale

VS04 Provides the functionality to create Scale with Reference

VS05 List Scales

VS06 List Scales for Shipment Costs

VSAN Number Range Maintenance: RV_SAMMG

VSB1 Self-Billing Proc. Inbound Monitor

VSCAN Configuration of Virus Scan Servers

VSCANTEST Test for Virus Scan Interface





VSTK Picking Confirmation

VT00 Transportation

VT01N Provides the functionality to create Shipment

VT03N Provides the functionality to display Shipment

VT04 Transportation Worklist

VT05 Worklist Shipping: Logs

VT06 Select Shipments: Materials Planning

VT07 Collective Run In Background

VT09 Number Ranges for Log VT04

VT10 Select Shipments: Start

VT11 Select Shipments: Materials Planning

VT12 Select Shipments: Transport Processing

VT13 F4-Help Shipment Number

VT14 Select Shipments: Utilization

VT15 Select Shipments: Free Capacity

VT16 Select Shipments: Check In

VT17 Extended Help (F4) Shipment Number

VT18 Start F4 Help Shipping

VT19 Shipment Tendering Status Monitor

VT20 Overall Shipment Process Monitor

VT22 Provides the functionality to display Change-Document Shipment

VT30 Initial Internet Transport for Shipment

VT31 Shipment Tendering

VT31C Customizing Screen for Shipment Tendering

VT32 Shipment Status List

VT33 Shipment Planning for Carriers

VT34 Event Reports for Carriers via HTML

VT34M Event Reports for Carriers via WML

VT60 Transfer Location Master Data to TPS

VT61 Extending Transport Planning deliveries

VT62 Send Deliveries to Forwarding Agent

VT63 Freight Planning Status from Deliveries

VT68 Deallocate Delivery from TPS





VT69 Plan Deliveries from Freight Planning

VT70 Output for Shipments

VTAA Order to Order Copying Control

VTAF Billing Document to Order Copying Control

VTAR Archive Shipments

VTBT Report for Definition of Batch Run

VTBW Reorganization: Shipment Data in BW

VTCM List of Continuous Moves

VTDOCU Tech. Documentation Transportation

VTFA Order to Bill Copying Control

VTFAKT Bill Deliveries

VTFF Bill to Bill Copying Control

VTFL Delivery to Bill Copying Control

VTLA Order to Delivery Copying Control

VTR1 XSI: Master Data: Service Codes

VTR2 XSI: Master Data: Routing Info

VTRC XSI Cockpit

VTRC_VVTR0011

Delivery Tracking - Collective Request

VTRK Tracking

VTRL Reload Shipments

VTRS XSI: Carrier: Master Data

VTRT XSI: Carrier

VTWABU Post Goods Issue

VUA2 Maintain Document Type Incompletion Procedure

VUA3 Provides the functionality to display Doc. Type Incompletion Procedure

VUA4 Assignment Delivery Type Incompletion Procedure

VUA5 Provides the functionality to display Assignment Delivery Type to Incompletion Procedure

VUC2 Maintain Incompletion Log

VUE2 Maintain Schedule Line Incompletion Procedure

VUE3 Provides the functionality to display Schedule Line Incompletion Procedure

VUP2 Maintain Item Incompletion Procedure





VUP3 Provides the functionality to display Item Incompletion Procedure

VUP4 Assignment Delivery Items to Incompletion Procedure

VUP5 Provides the functionality to display Assignment Delivery Items Incompletion Procedure

VUPA Provides the functionality to display Partner Incompletion Procedure

VV11 Provides the functionality to create Output: Sales

VV12 Provides the functionality to change output: Sales

VV13 Provides the functionality to display Output: Sales

VV21 Provides the functionality to create Output: Shipping

VV22 Provides the functionality to change Output: Shipping

VV23 Provides the functionality to display Output: Shipping

VV31 Provides the functionality to create Output : Billing

VV32 Provides the functionality to change Output: Billing

VV33 Provides the functionality to display Output: Billing

VV51 Provides the functionality to create Output for Sales Activity

VV52 Provides the functionality to change Output: Sales Activity

VV53 Provides the functionality to display Output: Sales Activity

VV61 Provides the functionality to create Output: Handling Units

VV62 Provides the functionality to change Output: Handling Unit

VV63 Provides the functionality to display Output: Handling Unit

VV71 Provides the functionality to create Output: Transportation

VV72 Provides the functionality to change Output: Transportation

VV73 Provides the functionality to display Output: Transportation

VVCB Maintain Activity Authorization

VVG1 Provides the functionality to create Output: Group

VVG2 Provides the functionality to change Output: Groups

VVG3 Provides the functionality to display Output: Group

VW01 SD Scenario “Incoming Orders”

VW02 SD Scenario “Freedom to Shop”

VW10 SD Scenario “Order Status”

VX00 Export Control

VX01 Provides the functionality to create License (Old)

VX02 Provides the functionality to change License (Old)

VX03 Provides the functionality to display License (Old)





VX05 Customers for License

VX06 Export Control Classes for License

VX07 Simulation: License Check

VX08 Simulation: Boycott List Check

VX09 Simulation: Embargo Check

VX0C Foreign Trade: Customizing Menu

VX10 Countries of Destination for License

VX11 Provides the functionality to create Financial Document

VX12 Provides the functionality to change Financial Document

VX13 Provides the functionality to display Financial Document

VX16 BAFA Diskette: Selection

VX17 Provides the functionality to create BAFA Diskette

VX22 Provides the functionality to change License Data (Old)

VX23 Provides the functionality to display License Data (Old)

VX30 Legal Control: Export Control Class

VX49 Document Payment Guarantee: Document Types

VX50 Document Payment Guarantee: Financial Document Types

VX51 Document Payment Guarantee: Bank Function

VX52 Document Payment Guarantee: Field Ctrl ID

VX53 Document Payment Guarantee: Financial Document Type ID

VX54 Document Payment Guarantee: Field Control-Bank Function

VX55 Document Payment Guarantee: Export/Import Documents

VX56 Document Payment Guarantee: Bank IDs

VX57 Document Payment Guarantee: Export Documents Default

VX58 Document Payment Guarantee: Export Documents Assignment

VX70 Sanctioned Party List: Legal Regulation

VX71 Sanctioned Party List: Departure

VX72 Sanctioned Party List: Scope of Check

VX73 Sanctioned Party List: Aliases

VX74 Sanctioned Party List: ExclusiveTexts

VX75 Sanctioned Party List: List Types

VX76 Sanctioned Party List: References





VX77 Sanctioned Party List: Delimiter

VX78 Sanctioned Party List: Normalization

VX79 Sanctioned Party List: Phon. Check

VX80 CAP: CAP Products List Number

VX81 CAP: CAP Products Group

VX83 CAP: Components Leading Good

VX84 CAP: CAP Material Components

VX85 CAP: CAP Bill of Material

VX86 Maintain Market Organizations

VX87 Maintain Number of Market Organizations

VX94 Declarations to Authorities: Check

VX98 Provides the functionality to display FT Data in Purchase Documents-INTERNET

VX99 FT/Customs: General overview

VXA1 Documents Assigned to Financial Documents

VXA2 Existing Financial Documents

VXA3 Financial Documents: Blocked Documents

VXA4 Financial Documents: Simulation

VXA5 Documentary Payments: Print Monitoring

VXA7 Documentary Payments: Simulation

VXBC SLS: List of Blocked Customers

VXCZ INTRASTAT: Form - Czech Republic

VXDA SLS: Audit Trail - Customer Master

VXDG Export Control

VXDP Declarations to the Authorities

VXDV List of Expiring SLS Records

VXGK Export Control

VXHU INTRASTAT: Form - Czech Republic

VXIE Maintain Foreign Trade Data

VXJ0 Foreign Trade: MITI Decl. - Japan

VXJ1 MITI Declarations

VXJ2 Declaration of Import Billing Docs Japan

VXJ3 Foreign Trade: Import Declaration Japan





VXKA SLS: Audit Trail: Vendor Master

VXKD Declarations to the Authorities

VXKP Configuration: Maintain Tables T180

VXL1 Legal Control: SLS - Scenario 1





VXL6 Legal Control: SLS: Sim.: Customer

VXL7 Legal Control: SLS: Search Terms

VXL8 Legal Control: SLS: Change History

VXL9 Legal Control: SLS: Sim.: Vendor

VXLA Legal Control: SLS - Audit Trail

VXLB Legal Control: SLS: Sim.: Address

VXLC SLS: Vendor Check - Scenario 3

VXLD Legal Control: SLS - List Display

VXLE SLS: Scenario 5 - Vendor Master

VXLP Legal Control: SLS: Keyword: Address

VXLU Legal Control: SLS - Data Service

VXLX Legal Control: SLS: Sim. Customer

VXLY Legal Control: SLS: Sim. Delivery

VXLZ Sanctioned Party List Screen

VXME Declarations to the Authorities

VXMO Common Agricultural Policy

VXPL INTRASTAT: Form - Poland

VXPR Export Control

VXS1 Legal Control: SLS: Create Entry

VXS2 Ges. Kontrolle: SLS: Change Entry

VXS3 Legal Control: SLS: Display Entry

VXSE Declarations to the Authorities

VXSIM Simulate Import

VXSK INTRASTAT: Form - Slovakia

VXSL Foreign Trade: Area Menu SLS





VXSW Mass Change Material Commodity Code

V_BPID003_E Identification Number Categories

V_BPUM_CTL BP: Activate Parallel Maintenance

V_FMAC Table Maintenance for FMAC

V_FMITPOC1 View Maintenance V_FMITPOC1




V_FMPY Table Maintenance for FMPY

V_I7 Condit: Pricing SD - Index in Background

V_I8 Conditions: Pricing SD - Index

V_MACO Completion of Sales Documents

V_NL Edit Net Price List

V_R1 List of Backorders

V_R2 Provides the functionality to display List of Backorders

V_RA Backorder Processing: Selection List

V_SA Collective Processing Analysis (Delivery)

V_TBC001 Business Partner: Grouping to Account Group

V_TBPID Characteristics of ID Numbers

V_TP019 Values Table Group Category Fields

V_TP23 Maintain Different Type Criterion

V_TP23S Control Different Type Criterion

V_TP24 Partner Grouping Characteristics

V_TPR1 BP: Assignment Categories

V_TPR2 BP: Assignment Category-Application

V_TPR4 BP: Assign Modules to Time Periods

V_TPR5 BP: Role Categories - Application

V_TPR6 BP: Role Categories - Application

V_TPR9 BPR: Role for Grouping/Address Type

V_TPZ18 Category of Additional Data Fields

V_UC_7 Incomplete SD Documents

V_V1 Updating Unconfirmed Sales Documents

V_V2 Updating Sales Documents by Material





2. Differentiate between the SD account key and FI account key.

The SD module defines account key in pricing and the FI module defines it for posting taxes.

3. What are the constituents of the organizational data in the System?

A organizational data in the System comprises the following:

Sales Organization—A unit that sells and distributes products

Distribution Channel—Channel through which the products or services reaches to customers

Division—Product groups defined for various products

4. Why is an outbound delivery, not Provides, the functionality to created by using the VL10D transaction code, even though STO Provides is the functionality to created? When you check STO, the delivery creation date is blank. What can be thecause this problem?

You can check a customer’s credit limit before processing the Sales order. Navigate the following menu path to trigger the standard credit check during the start of the Sales order creation:

Sales Order > Environment > Partners > Provides is the functionality to display Credit Account.

5. Imagine that you are implementing R/3 in an auction services company. You have two alternatives to treat the services: First is to treat business units as distribution channels and service types as division; second is to use a dummy distribution channel and treat business units as divisions. However, there are problems associated with each alternative. The problem with the first alternative is increasing Sales area number and that master data has to be extended across the Sales areas. The problem with the second alternative is to have different pricing forthe same order type. What is the appropriate solution in such a situation?

The solution to such a situation depends upon how the customer or client expects the reporting to be done. For example, if customer or client expects performance to be looked upon by services, then you should define them as divisions. Depending upon the reporting of a day and expected reporting out of SYSTEM, you can determine whether to treat a service type as a business unit or not.





6. Imagine you want to save a display variant under the SDO1 transaction code by using the Settings > Provides functionality to display Variants menu path. However, you are not able to save display variant as the save option is disabled. What would you do in such a situation?

If such a problem occurs, you might not have applied Standard Note. Once you apply the Standard, the save option is enabled and then you can simply save the display variant.

7. How can you change the sales document type of a sales order once you have saved it?

The following are two alternatives to change a Sales document type of a Sales order after saving it:

Configuring document type in the VOV8 transaction code

Using the Transaction Flow section

8. What are the different ways of getting sales output with respect to the sales organization of customers?

You can use either of the following ways to generate Sales output on the basis of Sales organization:

Use MTCE transaction code for 001 infostructure, if Sales Information System (SIS) is turned on.

Provides functionality to create ABAP query with Logical Database (LDB) VAV.

Provides functionality to create ABAP report by using transaction code VBRK > Billing Header Table and VBRP > Billing Item Table.

9. Explain the origin of SYSTEM R/3.

The first version enterprise was R/1, which came into existence in the year 1970. The SYSTEM R/1 version is used for performing financial accounting. In 1980, with the invention of mainframe-based application, SYSTEM R/2 came into existence. SYSTEM R/2 was helpful to multinational European companies that required business application which has soft-real-time capability. These companies also required software having multi language and multi currency capability. In 1999, SYSTEM R/3 came upwith the invention of distributed client-server model. It was a client version of software. It was officially launched on July 6, 1999.





10. Imagine that you are using the Provides functionality to create a quotation for aparticular enquiry and try to change the configuration in the quotation. Will you beable to change it? If yes, then explain how you can change the configuration in the quotation.

Although there is a configuration option between inquiry and quotation, we cannot change the configuration once it is fin-ished. To get the new configuration in quotation, we need to provide the functionality to create a new quote or order.

11. Which concepts of the SD module are crucial while implementing pricing requirement and formulas?

The following concepts of SD are crucial while implementing pricing requirement and formulas:

Requirements

Copying requirements

Data transfer routines

Formulas

12. Define the Determination Procedure.

The determination procedure is related to the Sales order preparation. During the Sales order creation, the determination procedure is accessed to validate the records in the condition table. The determination procedure accesses the condition table, calls the condition types according to the access sequence, and checks to see if a valid condition record exists.

13. Is it possible to change the Pricing Procedure once the document is prepared?

No, it is not possible to change the pricing procedure once the main document is prepared at the material level.

14. A free item that was scheduled to be delivered with the BOM item was not actually delivered, but indicated in the delivery status as delivered. Also, the initial number of free item is 0. How can it be resolved?

The free item was needed as a separate order.





15. Suppose you have two condition types for cost in which one is VPRS and another is customized. The values of both condition types are correctly determined in the sales order. Now suppose that you have to provide the functionality to create the delivery and the billing document, but when you provide the functionality to create them the condition type VPRS is found incorrect with the value “0”. What is the reason behind this?

The VPRS is known as the valuation condition. It is also considered as the cost of the items sold. When the VPRS comes from the material master record, it is known as a standard valuation price; but when the cost of the items sold varies, it means VPRS has come from the information record. If the VPRS has come from the information record, then there can be a price variation for the items. Therefore, you should check for the standard value in your material master record or should have a relevant info record.

Another reason can be that the customized condition is undoing the VPRS.

16. Give the menu path to include the condition type Z928 in the pricing procedure ZCS928.

The menu path to include the condition type Z928 in the pricing procedure ZCS928 is:

SPRO > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and AssignPricing and Procedures.

Now select “Maintain pricing procedures” followed by the selection of the ZCS928 procedure. Afterthat, select “Control Data” and include the Z928 condition type to ZCS928 procedure.

17. The discount given previously for each characteristic may vary from customer to customer. Is there any way to find out how to configure this?

You can find out the way to configure this by customizing the documentation for “$SET_PRICING_FACTOR,” in LO-VC.

18. Suppose you are working in area menu maintenance, SE43, where you provide the functionality to create a copy of COND_AV (standard for maintaining condition records in SD) as ZCOND_AV. You have also changed its description, butin the area menu the changed description does not appear. How can you change thedescription of the area menu maintenance?

The description of the area menu maintenance can be changed by creating a new menu area while working in SE43.





19. Imagine that you have two company codes and a new info structure SOO4 that you have to fill with the data of the first company code. However, at the same time the data from the second company code is also available. How can you stop updating the new info structure with the data of the second company code?

To stop updating the new info structure with the data of the second company code doesn’t include the Sales organization assigned to the second company code in the updating info structure.

20. What kind of records are updated by the system when you post goods issued in a delivery?

When the goods are transferred to the customer, the goods issue is posted in a delivery. Once the goods issue is posted, the System updates various records, such as reducing the stock in hand and increasing the amount of goods sold that is Debit COGS & Credit Inventory account.

21. Why is the automatic credit management done?

It is the type of Credit Management where the following is considered while applying the Credit Management over a transaction. This includes the following documents when doing the credit check for a transaction:

Open Order

Open Delivery

Open Billing

Open Items

Considers Horizon Period (only those documents which have shipping date inside this period are considered)

The configuration is done by using the Transaction Code – OVA8

22. Which block is used to prevent the system from creating deliveries by using the delivery-due list function?

The block used to prevent the System from creating deliveries by using the delivery-due list functionis called the delivery-due list book.

23. Which block stops the System from creating the picking list?

The block used to stop the System from creating the picking list is called the picking block.





24. List the most frequently used transaction codes in SD.

The most frequently used transaction codes in SD are as follows:

VS00—Accesses Master data

VC00—Accesses Sales Support

VA00—Accesses Sales

VL00—Accesses Shipping

VT00—Accesses Transportation

VF00—Accesses Billing

VOV8—Defines the Sales document type (header)

OVAZ—Assigns a Sales area to sales document types

OVAU—Configures Order reasons

VOV4—Assigns Item categories

VOV6—Configures Schedule line categories

OVAL—Assigns blocks to sales document types

OVLK—Defines delivery types

V/06—Configures Pricing

V/08—Maintains Pricing procedures

OVKP—Determines the Pricing Procedures

V/07—Accesses sequence

VD01—Create Customer Master

VD02—Change a Customer

VD03—Display a Customer

VD04—Change Customer account

VD06—Sets the flag for a Customer deletion

XD01—Create a Customer

XD02—Modifies a Customer





XD03—Display a Customer

MM00—Create other material

VB11—Create a conditional record to determine the material creation

CO09—Provides an overview of the material availability

VL01—Create an outbound delivery with ref sales order

VL04—Enables collective processing of delivery

VA 11—Create Inquiry

VA12—Change Inquiry

VA13—Display Inquiry

VA01—Create Order

VA02—Change Sales order

VA03—Display Order

VA05—Lists all the Sales orders

VA32—Change the Scheduling agreement

VA42—Change Contract

VA21—Create Quotation

VA22—Change Quotation

VA23—Display Quotation

VF02—Change the Billing document

VF11—Cancels the Billing document

VF04—Maintains the billing-due list

FBL5N—Display customer invoices by line

FBL1N—Display vendor invoices by line

VL02N—Change the delivery document

VL04—Selects Sales orders/Purchase orders work list





VKM5—Display a list of all deliveries

VL06G—Display a list of outbound deliveries for goods issue

VL06P—Display a list of outbound deliveries for picking

VL09—Cancels goods issued

VT02N—Change Shipment

VT70—Display output for shipment

XD01—Create a customer centrally

XD02—Change a customer centrally

XD03—Display a customer centrally

XD04—Change a customer centrally

XD05—Blocks a customer

XD06—Tags a customer for deletion centrally

XD07—Change a customer account group

XD99—Enables mass maintenance of customer master

XDN1—Maintains customer number ranges


You need to perform the following steps to configure sales document lists:

Customization Implementation Guide (IMG Menu) > Sales and Distribution > Sales > Lists > Define Selection Criteria

26. What are the sales object types?

The most common sales object types are as follows:

VBK—Sales Order Header

VBP—Sales Order Item

VBEP—Sales Order Schedule Lines






The sales documents lists are similar to the lists that are usually prepared throughout the business process. There are many sales document lists that are prepared during the selling process.

28. When and how is blocking of sales process used? What are the transaction codes used for this purpose?

In some circumstances, there is temporary suspension of business with a particular customer. In suchcases, the new order as well as the existing order can be stopped. The common transaction codes used for the purpose are:

VD05—Block Customer

OVAS—Block Reason

OVAL—Blocking Reason with sales order type

OVZ7—Delivery Blocking

OVV3—Billing Blocking

29. What is the transaction code that can be used to delete a sales order?

The VA02 transaction code is used to delete a sales order; however, before deleting a sales order youmust ensure the following:

Cancel the Invoice. You can use the VF11 transaction code to cancel an invoice.

Reverse the goods issue. The goods issue is reversed using the VL09 transaction code.

Mark the picking quantity as zero in the delivery document and then delete the delivery order. You can delete a delivery document using the VL02N transaction code.

30. What is the transaction code to delete an invoice?

An invoice cannot be deleted; it can only be canceled by issuing the VF11 transaction code. However, before canceling an invoice you must either cancel or delete all the invoice-related accounting documents.

31. List the ERP packages available in the market.

The other ERP packages available in the market are:

BAAN





JD Edwards

Oracle Financials

Siebel

PeopleSoft

32. Define the term consignment stock.

The material available in the company premises but is not added in the stock is called the consignment stock. The consignment stock is added to the company stock when it is either sent to the production department or marked as the material to be sold.

33. Differentiate between the contract agreement and the scheduling agreement.

Both contract and SA are outline agreement and independent entities. However you can create a contract with reference to a scheduling agreement.

34. What do you mean by availability check?

The availability check is an integral part of the sales order processing that helps in determining whether the requested deliverable quantity would be available for shipping on the customer’s requesteddelivery date. This process of availability check is performed at plant level in an organization and results in the material availability date. This date is the due date on which the material would be available. The picking and packing and transportation scheduling time are added to the material availability date that is determined by the mySAP ERP system. After adding packaging and transportation time, the planned goods issue date is determined in which further the shipping time is added, resulting in the final delivery date of the material to the customer.

Navigate the following menu path to evaluate the stock in hand:

System Menu > Logistics > Sales and Distribution > Sales Environment > Availability Overview

35. Explain the following terminologies used in the availability check process in the SD module: Backorder Processing, Rescheduling, Availability to Promise, and Replenishment Lead Time.

The following are the definitions of the terminologies used in the availability check process in the SD module:

Backorder Processing—It is the processing of a sales order that has either not been confirmed fully or not confirmed at a specific date.





Rescheduling—It is a proposal of reassigning a sales order to another sales order due to higher priority. For example, the sales order assigned for the ABC customer can be reassigned to the XYZ customer as the sales order of the XYZ customer is at higher priority.

Availability to Promise (ATP)—It is a basis for availability check in which the mySYSTEM ERP system automatically evaluates the available quantity to promise or commit to a sales document.

Replenishment Lead Time—It is the time required to produce or procure the required stock. It includes the time consumed, either by a company to produce a material or to externally procure the material from the third party.

36. Explain the basic elements to be configured during the availability check process.

The elements of the availability check process are as follows:

Requirement Class—It is a controlling factor for the availability check and transfer of requirements for all sales document types. The entries at the requirement class level are used as default values by the system and the data is transferred into the sales order. Generally, instead of creating the new requirement class for business processing, the most appropriate existing requirement class is copied andrenamed. Navigate the following menu path to define the requirement class:

SYSTEM Customizing Implementation Guide > Sales and Distribution > Basic Functions > Availability Check and Transfer of Requirements > Transfer of Requirements > Define Requirements Classes.

Requirement Types—These are defined in relation with the requirement class and its features. You assign a requirement class to a requirement type in the transfer of requirements. You can allocate a requirement type to a single requirement class; however, a requirement class can be allocated to multiple requirement types. A requirement type is displayed in the sales order, and is based on item category as well as MRP type of a material. Navigate the foll owing menu path to define the requirement type:

SAP Customizing Implementation Guide > Sales and Distribution > Basic Functions > Availability Check and Transfer of Requirements > Transfer of Requirements > Define Requirements Types.

Checking Group—It provides a basis for defining the type of requirement to be passed; for example, whether you record daily requirements or weekly summed up requirements in the stock requirement list. Moreover, you can also record individual requirements for each sales order and line item in the stock requirement list. There are pros and cons of both individual and summarized requirements. The backorder processing is p ossible for the individual requirement processing instead of the summarized requirement. However, since individual requirement is based on each sales order and line items, it may





lead to more impact on the system performance compared to the summarized requirement processing. The SAP standard uses 01 to represent daily requirements and 02 for individual requirements.

Checking Rule—It controls the scope of availability check for each transaction in the SD processing. The control of the availability check is defined on the basis of the checking group on the material master record and the checking rule representing the transaction.

Schedule-Line Category—The availability check may be fine-tuned at the schedule-line level, and the schedule lines that are not relevant for availability check may be switched off at schedule-line level by ensuring the availability check indicator is not flagged.

37. What do you mean by cross-company stock transfer?

Instead of delivering the sales order from another company code, the material can also be delivered from a plant of one company code to the plant in another company code. This process can be accomplished by a cross-company stock transfer order.

38. List the conditions needed to perform transfer of requirements.

The following conditions must be met to perform transfer of requirements:

A plant must be assigned to the sales document line item level.

The schedule-line category must be active for transfer of requirements.

The transfer of requirements must be active at the requirements-class level.

A checking group must be defined and allocated to the material master record in the Sales: General/Plant view in the availability-check field.

39. Specify the menu path to display stock requirement list.

Navigate the following menu path to display the stock requirement list:

SYSTEM Menu > Logistics > Materials Management > Material Requirements Planning (MRP) > MRP > Evaluations > Stock/Requirement List.

40. Explain the functions controlled by the help of a blocking indicator.

The blocking indicator is used to control the following functions:

Blocking of the sales document for delivery

Blocking of the confirmation from availability check; thus, instead of confirmation of the stock in the schedule-line level, the stock will be available for other sales documents.





Blocking of sales document for automatic creation by the delivery-due list

Blocking of picking

Blocking of goods issue

41. List the tables used in the SD module.

The following tables are used in the SD module:

VBBE—Sales requirement

VBLB—Sales order release

VBAP—Sales doc item

VBAK—Sales doc header

VBEB—Sales doc schedule line header

VBEH—Sales doc schedule line history

LIKP—Delivery header

LISP—Delivery item

VBRK—Billing header

VBRP—Billing item

42. Explain the five views of the customer-credit master record.

The five views of the customer-credit master record are as follows:

Overview—Provides an overview of the credit settings in relation to the customer, such as credit limit, credit exposure, percentage of credit limit used, payment data, and risk category.

Address view—Provides the address details of a customer as they appear on the customer master record.

Central data view—Provides the total credit limit the customer may receive across all credit control areas, as well as the maximum limit he may receive in one credit control area.

Status view—Provides the customers actual individual details according to the particular credit control area being searched. This view constitutes credit limit, credit exposure, risk category, and blocks.

Payment history view—Helps display the payments made by the customer for a particular credit





control area with which a company code is assigned.

43. What is a credit-control area, and how is it related to company codes?

An organizational unit is an organization that checks credit limits for customers. Although a credit-control area can include one or more company codes, you cannot assign a company code to more than one credit-control area.

44. Specify the highest level of organizational units in the SD, MM, PP, FI, and CO modules.

The highest level of organizational units in these modules are as follows:

SD—Sales Organization

MM—Plant

PP—Plant

FI—Company Code

CO—Controlling Area

45. Explain the views of the material master record.

The views of the material master records are as follows:

Accounting—Provides valuation and costing information. For example, standard, past and future price of a material, and its current valuation.

Materials planning and control—Provides material requirements planning (MRP) and consumption-based planning information; for example, safety stock level, planned delivery time, and reorder level for a material.

Purchasing—Provides information related to the purchasing for a material; for example, purchasing group responsible, over- and underdelivery tolerances, and the order unit for a material.

Engineering—Provides information related to engineering and design data on a material; for example, CAD drawings, basic dimensions, and design specifications.

Storage—Provides data related to the storage or warehousing of a material; for example, unit of issue, storage conditions, and packaging dimensions of a material.

Forecasting—Provides information in context of prediction of material requirements; for example, how the material is procured, forecasting period, and past consumption or usage of a material.





Sales and distribution—Provides data related to sales orders and pricing; for example, sales price, minimum order quantity, and the name of the sales department responsible for a specified material.

46. What is the difference between an inquiry and quotation?

The inquiry is the process to register the customer’s probable requirements. The quotation is a legally abiding document given to a customer conforming to the terms and conditions to deliver the product or service to the customer.

47. Explain the five types of messages in the mySAP ERP system.

Figure 1.1 shows the five types of messages in the mySAP ERP system:

Figure 1.1: Displaying Types of Messages in the mySYSTEM ERP System

48. Explain the possible units of measurement that can be used for a material.

You can store, transport, and sell a material in various units of measure. In the mySAP ERP system, you can define various units of measure that are maintained in the sales and distribution screens. However, you only need to maintain the fields of the units of measure if they deviate from the base unitof measure. If no other fields with units of measure are maintained, the system automatically takes the base unit of measure as a basis for its calculations. You can enter the following units of measurement inthe sales and distribution screens:

Base unit of measure—Stocks of a material are managed in the base unit of measure. All quantity movements in other units of measure are converted automatically by the system into the base unit of measure.

Alternative unit of measure—If a product is managed in the base unit of measure “Piece” but is sold in the sales unit “Box”, you must define the conversion factor.

Sales unit—The unit of measure in which materials are sold is referred to as a sales unit (for example, “Piece” or “Bottle”). The value you define in the material master record is proposed during





business transactions relevant for sales, such as the sales order. You can replace them with other alternative units of measure in the sales order.

Delivery Unit—It refers to the unit in which materials can be delivered. Only exact multiples of the delivery unit can be delivered.

Quantity Specifications—The following two different quantity specifications are used:

Minimum order quantity—Refers to the minimum quantity that the customer must order. A warning message appears if the minimum order quantity is not reached during order entry. The order can be entered in spite of the warning message.

Minimum delivery quantity—Refers to the minimum quantity that you must deliver to the customer. The minimum delivery quantity is automatically checked during delivery processing. A warning message appears during delivery processing if you enter a delivery quantity lower than the minimum delivery quantity. The delivery can be created in spite of this warning message.

49. Why are different item and schedule-line categories used?

Item categories are defined to provide additional control functions for the sales documents, and therefore meet the demands resulting from the different business transactions.

The items in a sales document are divided into one or more schedule lines. These schedule lines differ from each other with respect to date and quantity. For some schedule lines, material requirement planning is not carried out; whereas for other schedule lines, it is carried out. Also goods receipt, not goods issue, is posted for a schedule line defined in a returns document.

50. List the archiving objects for the following objects in the SD module: Sales documents, Billing Documents, Sales activities, Rebate agreements and relevant conditions, Conditions, and Customer master data.

The archiving objects are as follows:

Sales documents—SD_VBAK

Billing Documents—SD_VBRK

Sales activities—SD_VBKA

Rebate agreements and relevant conditions—SD_AGREEM

Conditions—SD_COND

Customer master data—FI_ACCRECV





51. List the tables from where the system archives data when you use the SD_VBAK archiving object.

When you use the SD_VBAK archiving object, the system archives data from the following tables:

AUSP—Characteristic Values

CMFK—Storage Structure for the Error Log Header

CMFP—Storage Structure for Errors Collected

FMSU FI-FM—Totals Records

FPLA —Billing Plan

FPLT —Billing Plan: Dates

INOB—Link between Internal Number and Object

JCDO—Change Documents for Status Object (Table JSTO)

JCDS—Change Documents for System/User Statuses (Table JEST)

JEST—Object Status

JSTO—Status Object Information

KANZ —Assignment of Sales Order Items - Costing Objects

KEKO—Product Costing - Header

KEPH—Product Costing: Cost Components for Cost of Goods Mfd

KNKO—Assignment of a Cost. Est. Number to Config. Object

KOCLU—Cluster for conditions in Purchasing and Sales

KSSK—Allocation Table: Object to Class

NAST—Message Status

SADR—Address Management: Company Data

VBAK—Sales Document: Header Data

VBAP—Sales Document: Item Data

VBEH—Schedule Line History

VBEP —Sales Document: Schedule Line Data





VBEX—SD Document: Export Control: Data at Item Level

VBFCL—Sales Document Flow Cluster

VBLB—Sales Document: Release Order Data

VBSN—Change Status Relating to Scheduling Agreements

VBUK—Sales Document: Header Status and Administrative Data

VBUP—Sales Document: Item Status

VBUV—Sales Document: Incompletion Log

VEDA—Contract Data

52. List the functions and their report programs available for the SD_VBAK object.

The following are the functions and their report programs available for the SD_VBAK object:

Archiving S3VBAKWR

Deleting S3VBAKDL

Analyzing S3VBAKAU

Checking S3VBAKPT

Reloading data S3VBAKRL

53. List the tables from where the system archives data when you use the SD_VBRK archiving object.

When you use the SD_VBRK archiving object, the system archives data from the following tables:

EIKP—Foreign Trade: Export/Import Header Data

EIPO—Foreign Trade: Export/Import: Item Data

FPLA—Billing Plan

FPLT—Billing Plan: Dates

FPLTC—Payment Cards: Transaction Data - SD

KOCLU—Cluster for Conditions in Purchasing and Sales







VBFCL—Sales Document Flow Cluster

VBPA—Sales Document: Partners

VBRK—Billing Document: Header Data

VBRL—SD Document: Invoice List

VBRP—Billing: Item Data


54. List the functions and their report programs available for the SD_VBRK object.

The following are the functions and their report programs available for the SD_VBRK object:

Archiving S3VBRKWR

Deleting S3VBRKDL

Reading S3VBRKAU

Analyzing S3VBRKPT

Reloading data S3VBRKRL

55. List the tables from which the system archives data when you use the SD_VBKA archiving object.

When you use the SD_VBKA archiving object, the system archives data from the following tables:



VBFA—Sales Document Flow

VBKA—Sales Activities

VBPA—Sales Document: Partners


VBUV—Sales Document: Incompletion Log





56. List the functions and their report programs available for the SD_VBKA object.

The following are the functions and their report programs available for the SD_VBKA object:

Archiving—SDVBKAWR

Deleting—SDVBKADL

Reloading data—SDVBKARL

57. List the tables from which the system archives data when you use the SD_AGREEM archiving object.

When you use the SD_VBKA archiving object, the system archives data from the following tables:

EBOX—Index of Settlement Documents for Subsequent Settlement.

EKBO—Index of Documents for Price Determination/ Updating Subsequent. Settlement.

KONA—Rebate Agreements.

KONH—Conditions (header).

KONAIND—Index: Groups of Conditions/Header Record Conditions.

SDKONDARCH—SD Archiving of Conditions: Object Structure for Condition Tables.

WAKHIND—Promotion Header Data IS-R: Index Table for Conditions.

58. List the functions and their report programs available for the SD_AGREEM object.

The following are the functions and their report programs available for the SD_AGREEM object:

Archiving—RV130005

Deleting—RV130006

Reloading data—RV130007

59. List the tables from which the system archives data when you use the SD_COND archiving object.

When you use the SD_COND archiving object, the system archives data from the following tables:

KONH—Conditions (Header).

SDKONDARCH—SD Archiving of Conditions: Object Structure for Condition Tables.





60. List the functions and their report programs available for the SD_COND object.

The following are the functions and their report programs available for the SD_COND object:

Archiving—RV130001

Deleting—RV130002

Reloading data—RV130003





GLOSSARYAccess Sequence An access sequence is a sequence of steps, used by the underlying system to obtain a condition record used for material determination.

Assortment Module An assortment module is a tool for order entry. It displays a list of materials and services likely to be released from a value contract. It has a specific validity date. There is a condition for the inclusion of the items in the assortment module. This is according to the materials and services that belong in the same sales organization, and the release orders being created.

Automatic Posting Automatic posting is the process of posting the accounts in finance. This configuration does the posting automatically in accounts as determined by the system. This process works as per your configuration for your business requirements.

Availability to Promise Availability to Promise is a basis for availability check in which the mySAP ERP system automatically evaluates the available quantity to promise or commit to a sales document.

Backorder Processing Backorder processing refers to the processing of a sales order that has not been confirmed at a certain delivery date after the availability check has been completed.

Backward Scheduling Backward scheduling is defined as the process used to schedule the sales process to meet a delivery date from the requested delivery date.

BADIs In the R/3 system, SYSTEM provides an enhancement technique called business add-ins (BADIs).

Business Area A business area is a subdivision of a company code for accounting purposes. You can draw financial reports based on the business area.

Change Request A change request is defined as a request that is automatically generated by SYSTEM when you do any new customizing or configuration tasks in SYSTEM. This request then adopts the new change in the system.

Checking Group Checking Group provides a basis for defining the type of requirement to be passed inthe stock requirement list.

Checking Rule This controls the scope of the availability check for each transaction in the SD processing. The control of the availability check is defined on the basis of the checking group, on the material master record, and the checking rule representing the transaction.

Collective Requirements Collective requirements are a group of requirements created over a certain period of time such as on the daily, weekly, or monthly basis and transferred to MRP.

Condition Exclusion Group The condition exclusion group is a technique to ensure that the customer





does not receive all different types of discounts; rather, the customer receives the best discount out of all given discount condition types.

Condition Supplement A condition supplement is a group of conditions that are applied every time a condition is matched. Condition supplements will come with a condition if you have maintained pricing procedure under master data of the condition.

Confirmed Quantity The quantity allocated by Availability to Promise (ATP) is known as confirmed quantity.

Consignment Issue A consignment issue is the allotment of products for the customers. The standard document type is KE and the standard order type recorded is the same. The standard item category usedfor the consignment issue is KEN C0 and C1 are the standard schedule lines used for consignment issue. To create a consignment issue order, the KE type sales document are selected.

Consignment Stock A consignment stock consists of the items that are kept at the customer’s business site on behalf of a written agreement between them. The customer has the right to return the goods. Only after the items are consumed is the customer entitled to have a fresh stock.

Consumption Modes The consumption mode defines the direction of the consumption of the customerrequirements on the time axis from the requirement date, with planned independent requirement shouldoccur.

Contract Grouping A contract grouping is the process by which lower-level contracts are linked to a master contract. It is required that all the contracts are assigned to the same sales area. Only one master contract can remain in the contract hierarchy.

Copy Control The copy control is meant to copy data from a preceding document to the succeeding document. The succeeding document is decided on the basis of the document type and the customer requirements.

Correction Delivery The correction delivery is done when a product is wrongly delivered to the customer and returned, and the good receipt is not processed. As a result, the cumulative quantity in thescheduling argument is updated and the original delivery quantity is called off in the scheduling agreement.

Credit Note A credit note is a kind of billing that is generally raised when credit to a customer is needed as a result of a sales return, because of some extra incentive, or bonus offered.

Cross-Company Stock Transfer Instead of delivering the sales order from another company code, the material can also be delivered from a plant of one company code to the plant in another company code. This is called a cross-company stock transfer.

Customer Pickup Customer pickup is the last process of the consignment procedure. It includes the





picking of faulty, as well as unused/unsold materials. The specific return shipping point is determined for all products. There is no need of any invoice for the consignment pickup because the ownership of goods has not changed. KAN is the standard item category for the consignment pickup.

Debit Note A debit note is a kind of billing that you need to charge a customer for reasons such as delayed payment or check dishonor penalties.

Determination Procedure The determination procedure is related to the sales order preparation. During the sales order creation, the determination procedure is accessed to validate the records in the condition table. The determination procedure accesses the condition table and calls the condition types according to the access sequence. It then checks to see if a valid condition record exists.

Document Flow From the enquiry through quotation, ordering, shipping, and finally, billing of the products, many documents are prepared. The chain of such type of documents created in a sales processis called a document flow.

Dunning Dunning is defined as a process that is used to generate a bill or invoice when a customer does not pay the amount according to the payment terms offered by a company.

Enterprise Resource Planning Enterprise Resource Planning (ERP) is a way to integrate processes and data of an organization into a single system to provide easy access and workflow in an organization.

Excise Tax The excise tax or excise duty is a type of tax that is charged on the goods produced for selling within a country. It is different from the customs duties, which are charged on imported goods.

General Table Display The General Table Display screen displays the populated fields of a table. The transaction code used for this purpose is SE16.

IDES IDES stands for International Demonstration and Education System and is an application used toquickly learn and implement ERP.

Individual Transfer Requirements In the individual transfer requirements, a single transfer of demand occurs to the MRP for each schedule line.

Inter-Company Sale An inter-company sale represents a sales transaction in which more than one company code belongs to the same client.

Inter-Company Customers Sales customers who deal with the same client between different companycodes are known as intercompany customers.

Intra-Company Sale The intra-company sale represents a transaction within one company code—for example, movement of stock between two plants within a company code.

Invoice Correction Request This is the document that helps you to correct the quantity and price of





items on an invoice and to generate credit and debit memos. The procedure is called the invoice correction request.

Invoice Lists Invoice lists are billing documents that are combined into one document for a specific customer.

Invoice Verification In case of third-party order processing, the party that delivers goods to the customer on behalf of original manufacturer/supplier also sends delivery confirmation and the invoice to the supplier. The supplier verifies the invoice. The process is known as invoice verification.

Item Category The item category is the key field included in the sales cycle. It affects the sales data and schedule line category.

Item Category Group When processing a sales document, the system uses the item category group to determine the item category and proposes it in the respective document. Item category group is defined in the sales org view 2 of material master record.

Item Proposal If a customer orders the same combination of materials frequently, or if you recommenda particular selection of products for an opening order, you can store the frequently used data as an itemproposal in the system. During a sales order creation, you can copy all or some of the materials and quantity data from the item proposal directly into your document (sales order, quotation, and so on). You can assign a particular item proposal to a specific customer master record. The system can then automatically propose the number of the assigned item proposal whenever you process sales orders for the relevant customers.

Loading Point The subdivision of a shipping point refers to a loading point that is manually entered in the header data of a delivery as per customization.

Master Contract A master contract is a contract that groups contracts at a lower level than master contracts. It contains information that is relevant to the rest of the contracts. The main objective of the master contract is to ensure consistency at all levels.

Match Code The match code is a comparison key that allows you to locate the key of a particular database record depending on the field value entered in the record.

Material Determination While preparing the sales order, we need to determine the materials to be entered in the sales order. This is accomplished through a method in SD that helps determine the material to be used in the sales order. It uses condition techniques to determine the products to be selected. It is also helpful in determination of products when we need to replace an old product from the sales order as it has become obsolete and new products are available at that place. Material determination is also product selection that can be implemented as an automatic or manual process.

Material Listing and Exclusion The material listing and exclusion process is used to list those items





that are purchased by a particular customer and exclude items that are not purchased by that particular customer. The material listing and exclusion process uses the condition technique to determine the items to be listed and excluded. It is applicable on two ingredients: sold-to party and the payer.

Material Requirement Planning When creating the sales order, the items ordered in the sales order creates a schedule line consisting of the customer-requested delivery date and the quantity to be delivered. This information is then transferred to the Material Requirement Planning (MRP) module.

Milestone Billing The final bill at a completion of specific milestone in accordance to the services provided or the items sold.

Minimum Delivery Quantity Determines the minimum quantity that you need to deliver to a customer.

Minimum Order Quantity Determines the minimum quantity that a customer should order.

One-Time Customers These are customers for whom you do not want to create a separate record so that such type of customer account group can be reused.

Order Quantity The quantity ordered by a customer.

Outline Agreements In a business process, the agreements are the type of relationship between the customers and the business. They are done on the business entities such as material, price, and quantities. These contracts are represented in the system as outline agreements.

Output An output can be defined as a medium that links various business partners. Output media can be e-mail, fax, electronic data interchange (EDI), and printouts. Output media is generally created in the form invoices, delivery notes, and order confirmation.

Output Determination Output Determination helps to decide which output mode is to use to send an output notification to a partner.

Payment Terms The terms of payment that a company offers to a customer based upon which a discount may be given for prompt payment, or penalties can be charged in case of late payment.

Periodic Billing Periodic billing is a bill for a predefined date proposal that bills a customer at periodicintervals.

Picking Picking is defined as the process to select goods from the storage location to create a delivery.

Planning Delivery Schedule A type of delivery schedule that is used to manage the planning requirement of a project. The planning delivery schedule is conducted for limiting the planning period of schedule lines in forthcoming delivery schedules.

Pro Forma Invoice A pro forma invoice is used for information purposes and does not post any





financial amount to the general ledger.

Product Group The product group is categorized as the group of the products that are allocated for specific customer order. The product group can be either multi-level or single-level. The single-level product group contains only the materials, whereas the multi-level group can contain more than one product group.

Purchase Organization The central organizational element used in purchasing.

Quantity Contract A contract that is prepared after the issue of quotation, but before an order. Quantity contracts are used to limit the quantity of products that a customer can buy.

Quick Viewer The quick viewer is a very useful tool to create reports in SYSTEM. It helps to create reports without actually doing any programming.

Quotation Quotation can be defined as a sales document that you create before a sales order and after an inquiry. A quotation is a legally binding document that informs customers of the proposed prices andthe terms of sales to a customer.

Rebate A rebate refers to a specific discount given to a specific customer for sales within a specific period of time.

Rebate Agreement A type of agreement made between the customer and the buyer for the discount that is being paid to the customer. This agreement depends on conditions such as buying certain amountof the goods over a certain time period. This agreement specifies the rebate amount agreed on for each product.

Referencing Requirement The referencing requirement is used to assign the contracts that are referenced by master contract. The referencing requirement is necessary for grouping contracts or linking quantity contracts to master contracts.

Replenishment Lead-Time This is the time required to produce the required stock. It includes the timeconsumed either by a company to produce a material or to procure the material from a third party.

Requirement Class For all the sales document types, requirement class is the controlling factor for availability check and transfer of requirements. It is used as the default source of data from the underlying system inserts data into the sales order.

Requirement Type After creation of the requirement classes, we need to assign a requirement type to requirement class. A requirement class can be assigned with more than one requirement type, whereas arequirement type cannot be assigned to more than one requirement class. The requirement type can be changed during creation of the sales order.

Rescheduling Rescheduling is a proposal of reassigning a sales order to another sales order as a result





of a higher priority.

Return Invoice A return invoice is a credit memo issued to a customer for the sales return.

Risk Category Risk category is a grouping category, which is used to control the process to check the credit limit when the credit control takes place automatically.

Sales Document Lists Sales document lists are similar to lists that usually are prepared throughout the business process.

Sales Document Status In sales documents, the status at the header and item levels is used for controlling the stages in the sales documents.

Sales Employee Refers to the individual with personnel master records that are used to manage data.

Sales Group The staff of a sales office is divided into sales groups; then, sales employees are assigned to a sales group.

Sales Office The geographically located unit of a sales organization is refered to a sales office in the SD module.

Sales Order A sales order is defined as an order given by a customer to an organization for product or services. A sales order then is processed in the system to ascertain the basic organizational data and requirements for the entire sales process.

Sales Order Stock The sales order stock is a stock with a stock type E. It is the stock of items that is reserved as per the sales order issued.

Sales Return Sales return is the process of returning the purchased goods by the customer because of various reasons, such as damaged during transportation, inferior quality, overstocking, less or no sales uptake, or winding up of business by the customer (e.g., in case of trader or dealer).

Schedule-Line Category The availability check may be fine-tuned at the schedule-line level. The schedule lines that are not relevant for availability check may be switched off at schedule-line level by ensuring that the availability-check indicator is not flagged.

Scheduling Agreement Scheduling agreements are the type of agreements that are made between the customer and the business. They include the details related to the delivery of the product such as delivery date and quantities. The delivery dates are then passed to the schedule line for further activities.

Service and Maintenance Process The service and maintenance process or service contract is a type of agreement between the supplier and receiver of the goods or service. This contract forms a basis by which the regular activities of the business, such as billing, cancellation, and other related items, are accomplished. A service contract contains validity dates, cancellation conditions, price agreements, and





additional information.

Shipping Point A shipping point refers to the point from which deliveries of products are shipped. Oneor more plants can have the same shipping point.

Special Stock The special stock is the stock that is delivered along with the packaging material. The special stock is considered as the company’s property even when it is placed at the customer’s location.

Standard Application Logic If any field in the new reference procedure screen is changed in the master contract, then only those fields of the master contract will be copied by the system that has the same value of master- and lower-level contracts. This is known as application logic.

Standard Service Item Category The standard service item category represents a service that is carried out and billed periodically. In standard system, the standard item category for a service is WVN.

Subtotals Subtotals are generally used in pricing procedures. Subtotals are not tied to condition types; however, you can control the value entered in the fields by assigning subtotals within the pricing procedure.

System Query System query is a tool used to create reports with little coding.

Target Quantities The quantities mentioned as available in the quantity contract are called target quantities.

Tax Determination Process Tax determination is performed automatically by SYSTEM. Tax determination is based on the structure of the organization, country, region, or city of the plant delivering the products and the country of the receiving customer.

Transaction Code Transaction code is the short path to reach to a specific screen in SYSTEM. Instead of going through the routine menu, you can enter the transaction code and then press the Enter key, which would directly take you to the specific transaction.

Transfer of Requirements Transfer of requirements ensures that the materials ordered are ready for the requested delivery date. It works in coordination with the Material Management (MM) and Production Planning (PP) modules.

User Exit An user exit is implemented as a call to a function module. The user exit allows a customer’sdeveloper to access program components and data objects in the R/3 system.

Value Contract The value contract is similar to the quantity contract, but the main difference is that thevalue contract is based on the total value of the quantity rather than its numbers. The value contract is created and maintained in the same way as the other contracts.

Workflow Workflow is a sequence of steps either processed manually or automatically by the system for implementing a task, such as updating a contract. It is handled by a workflow resource.









QUESTION INDEX

Chapter 1: Introduction to SD Module

1. List the SYSTEM modules that are included in the financial application component.

2. List the SYSTEM modules that are included in the human resource application (Human Capital Management) component.

3. List the SYSTEM modules that are included in the logistic application component.

4. List the components the SD module consists of.

5. What is the purpose of transaction code in SYSTEM?

6. What is meant by match code in SYSTEM?

7. Explain the three main areas of customer master data.

8. What is the purpose of Implementation Guide (IMG Menu) in the SYSTEM?

9. How will you maintain a company code in SYSTEM?

10. What do you mean by Enterprise Resource Planning (ERP)?

11. List the advantages of implementing an ERP system in an organization.

12. Specify the role of the Sales and Distribution (SD) module in an ERP system.

13. Explain all modules in SYSTEM.

14. What are the application areas of the R/3 system?

15. What are the advantages of the R/3 system?

16. How does the R/3 system integrate all the application modules?

17. What are the functions of the R/3 system?

18. What is R/3 system landscape?

19. What are the databases supported by the SYSTEM R/3 system?

20. What is the role of an ABAPer in the SD module?

21. Who can be the business partner in SYSTEM?

22. Explain BADIs and its relevance.

23. How do you define BADIs?





24. What is the Quick Viewer?

25. What are System Query and InfoSets? How can you create InfoSets?

26. Which kinds of servers are used to define the functioning of a system?

27. What is the role of ERP in a business environment?

28. Define IDES.

29. What is R/3?

Chapter 2: Basic Structure—SD Module

1. What is a division in the Sales and Distribution module?

2. What do you mean by a sales office in the SD module?

3. What do you mean by a shipping point and loading point in the SD module?

4. What do you mean by the terms sales office, sales groups, and sales employee in the SD module?

5. How can you maintain a sales office and sales group in the system?

6. How can you define or create a shipping point?

7. What do you mean by business area and how can you assign a business area in the SD module?

8. What does the prefixes VA, VL, VT, and VF of a transaction code stand for?

9. What do the suffixes 01, 02, and 03 of a transaction code represent?

10. How can you configure the sales districts?

11. How can you assign a shipping point to a plant?

12. Suppose that a new info structure is created and the update rules are activated for it. How would you then transport it to a production client?

13. How is the company code created?

14. What is the relationship between sales organizations and company codes?

15. Give the name of the central organizational element used in purchasing.

16. What is the relationship between sales organizations or distribution channels and plants?

17. What is the relationship among sales organizations, plants, and company codes?

18. Mention the total number of the shipping points that can be assigned to a sales organization.





Chapter 3: Master Data Maintenance

1. List the transaction codes used to create a customer in the SD module.

2. List the basic elements of a customer master record.

3. Which menu path is navigated to access the account groups defined in finance?

4. State a few examples of common material types.

5. List a few common material master views.

6. How can you create Customer-Material Info Records in the SD module?

7. Which transaction code and movement type helps in adding stock (from legacy stocks) for the newlycreated material type into a particular plant after creating a new material type in SYSTEM?

8. How can you define your own hierarchy types?

9. How will you create material in both company codes while working on inter company sales?

10. Which factors do you need to verify if the tax field in the customer master and material master is not displayed?

11. List the sequence of steps performed by the underlying system to determine tax number and tax classification.

12. How do you define tax relevancy of master records?

13. Imagine you are defining tax determination rule for a country which has regional tax code also. How will you define regional code?

14. What are the transaction codes that are used to create and change the customer master?

15. Which transaction code is used to view messages in SYSTEM?

16. What do you understand by transferring the legacy data to SYSTEM?

17. Specify a way to block the transaction for a material flagged for deletion.

18. List the master records from which a sales order receives the organizational data for a specific sales area.

19. Suppose you have to automatically transfer the payment method from customer master to sales order. How can you do that?

20. Which document do you use to enter shipping conditions and how are these conditions used in determining the shipping point?





21. Suppose that you have blacklisted a customer and now want to block that customer. How can you do that?

22. Give the menu path to define the customer hierarchy types.

23. Give the menu path to set the partner determination for hierarchy categories.

24. List the items for which you can define the customer hierarchy.

25. Give the menu path to assign a sales area to the customer hierarchy.

26. Give the menu path to assign the hierarchy type for pricing by sales documents to the customer hierarchy.

27. Give the menu path to define the product hierarchies.

28. Suppose that you create a new customer account group and the system increments it by an arbitrary value. What would you do?

29. What are the customer tables for SD module?

Chapter 4: Basic Functions

1. List the standard output types in the Sales and Distribution module.

2. What do you mean by user exit?

3. What is the need of user exit?

4. What do you mean by rebate processing?

5. Imagine you are facing a problem with Logistics Information System (LIS), as a result of which, after client copy, your test system does not update LIS info structures. When you save a delivery, sales order, or billing document, an error message “update was terminated” is displayed. How can you resolve such a problem?

6. What do you mean by subtotals?

7. Imagine you have defined a condition type Z004 in accordance with the condition type K004. After creating the Z004 condition type, you try to create a condition record in transaction code VK31 in the section Discount/Surcharges > By Material. While creating a condition record in VK31, the error message “Table 304 is not defined for use with condition type ZEC1” is displayed. How you can resolve such an error?

8. How can you configure a distribution channel as a default in the transaction field that requires distribution channel data?





9. Can you perform an availability check on a plant by excluding a storage location?

10. What is the purpose of a rebate agreement?

11. List the transaction codes with respect to rebate agreement processing.

12. What do you mean by payment terms?

13. What is the purpose of condition indexes and how can you activate them?

14. What is the role of user exit?

15. Which transaction code is used to view enhancements in the system?

16. Which menu path should be followed to view all the enhancements in the system?

17. List user exits for partner determination.

18. How do you create user groups?

19. Describe the relevance of condition technique in sales and distribution (SD).

20. Which rounding rules are available in the course of maintaining condition types?

21. How do you begin with defining and assigning pricing procedures?

22. Imagine that you have allocated a discount condition type Z007. How will you create a condition record for this condition type?

23. List the sequence of steps used to customize pricing procedure.

24. What is the relevance of pricing procedure and how is it configured in the SD module?

25. Which topics in SD have impact on pricing procedure?

26. How do you activate pricing for item category?

27. Which menu path do you follow to activate cost determination for item category?

28. What is the relevance of the condition exclusion group?

29. How do you maintain condition exclusion group?

30. How do you assign condition types to the exclusion groups?

31. What do you understand by condition supplement?

32. Explain the tax determination process in brief.

33. How do you define tax determination rules in SD?

34. How do you define dependencies of revenue account determination?





35. How do you maintain requirement and formulas?

36. Where and when are requirements and data transfer routines available to be assigned within the system?

37. List the divisions of data transfer routines.

38. How do you define and assign account keys in SD?

39. How do you set price limits in SD?

40. Imagine you are maintaining a pricing procedure. In which circumstances will you use the “From” and “To” columns?

41. List the transaction codes related to condition record selection by condition type.

42. What is access sequence in material determination?

43. How do you maintain access sequence in material determination?

44. How do you define/maintain checking group?

45. How do you maintain condition type for material determination?

46. How do you maintain condition tables for material determination?

47. List the steps for a condition technique.

48. Explain material listing and exclusion.

49. Define Material Requirements Planning (MRP) and Transfer of Requirements (TOR).

50. How do you configure transfer of requirements?

51. Differentiate individual and collective requirements.

52. List the key transaction codes relating to integration between logistics in MM and SD.

53. List a menu path to access stock requirements lists.

54. What are the data on which the transfer of requirement is dependent?

55. What are the criteria you need to ensure for the availability check and transfer of requirement to be carried out?

56. What are the requirement classes and requirement types?

57. How do you define requirement class?

58. What is requirement type?





59. List the search strategy that the underlying system uses to determine the requirement types.

60. Define the role of availability check in SD.

61. Define the types of availability checks.

62. What are the advantages of individual requirements over summarized requirement?

63. What is the disadvantage of individual requirement over summarized requirement?

64. How do you define/maintain procedure for each schedule-line category?

65. Which types of stock are available to select from while carrying out the availability check?

66. What is the relevance of the “Product allocation found changes to the confirmation” message?

67. What is the relevance of the “No feature combination exists …” message?

68. What is a change request? How is it done?

69. How is a request released?

70. What is automatic posting in FI?

71. What are item category and item category group?

72. What are outline agreements?

73. What is a quantity contract?

74. What activities are exempted from the quantity contracts?

75. How is a quantity contract created?

76. How can a quantity contract be set up?

77. Which are the contracts that appear in the Implementation Guide (IMG) menu?

78. Which table is used to list the partner functions in a delivery?

79. How is the pricing procedure determined? How can you define the right pricing procedure in the sales order?

80. How would you resolve the problem “MSWT is missing,” even when it is present in the RVAA01 procedure?

81. How is the item text copied from sales order to delivery?

82. Why is text determination used in SD?

83. Why is the partner determination done in SD?





84. Why is the output determination used in SD module?

85. List the five important fields that need to be maintained during the account determination.

86. How is the pricing procedure determined?

87. What do you mean by the copy control?

88. Specify the purpose of maintaining the common distribution channels and the common divisions.

89. Why is availability check required?

90. Which kind of requirements does the checking group and 02 represent?

91. Suppose in case of output determination, you have generated a condition table with a condition record. In the condition table, the access sequence is assigned to the output type. However, when a billing document is created, the blank output screen appears. During determination analysis, “Note 524 Access not made (Initialized Field)” error occurs. How can this error be resolved?

92. Which user exit can be used to copy data into the planning table?

93. List the forms of number ranges in SD.

94. What is the purpose of using copy control?


96. Is it required to create a condition record for the customer and material defining the scale while creating the customer rebate?

97. How can you create a pricing procedure that calculates the price for the industrial customers when they also purchase the domestic goods?

98. How does the system show storage condition? How can the storage condition be defined?

99. Suppose that you have customized the customer’s credit limit in your company in such a way that when a customer exceed his/her credit limit, the system responds to you. What is the name of this management in SYSTEM, and what data do you use for this management?

100. Give the menu path to assign credit limit to customers.

101. In SYSTEM there is functionality, which is used to manage the customer credit limits. That functionality can be assigned with one or more company codes. By using the company code, the systemdecides that organizational unit when a sale occurs. What is the name of that functionality?

102. Give the menu path to create a credit control area.

103. Define the risk category.





104. Give the menu path to assign a company code to a credit control area.

105. Is it required to assign a sales area to a credit control area? If yes, then give the menu path to assign a sales area to a credit control area.

106. List the places where a credit check can occur.

107. List the credit management checks that the system uses to check the credit.

108. Suppose that you have to define the risk categories for various customers, then which system module you use to define the risk categories. Which menu path can you use to define the risk categories?

109. Once the risk categories are defined, you need to define the credit groups. Which system module do you use to define the credit groups? Give the menu path to define the credit groups.

110. Is it required to assign a credit group to the sales and delivery document types? If yes, then which menu path do you use to assign a credit group to the sales and delivery document types?

111. The automatic credit management is controlled by the combination of two items. What are those items, and what is this control called? How can you maintain this control?

112. What is a static credit limit check?

113. What is a dynamic credit check?

114. Give the menu path to define the forms of payment guarantee.

115. Give the menu path to configure the payment guarantee procedure.

116. Give the menu path to define a customer determination schema.

117. Give the menu path to define the document determination procedure.

118. Suppose you have to create a block to stop transferring the goods requirement from the sales document to the plant. Which block do you create for this purpose?

119. Give the menu path to define the status groups for the incompletion log.

120. List the items for which you can create incompletion logs.

121. Give the menu path to define incompletion procedures.

122. Is it possible to assign an incompletion procedure to an object? If yes, then give the menu path to assign an incomplete procedure to an object.

123. List the documents, activities, and records for which the system automatically determines partners.

124. Give the menu path to set up the partner determination.





125. Suppose you want the system to copy a text line from the customer master record to a sales document automatically. How can you make system to do that?

126. Give the menu path to configure the text determination procedure.

127. List the text objects for which the Sales and Distribution module is used in the text determination.

128. What is an output?

129. Give the menu path to maintain the output determination for the sales documents.

130. List the sales and distribution related output determination activities.

131. List the transaction codes to create, change, and display the output condition records.

132. Give the menu path to define forms.

133. Give the menu path to define the form texts.

134. How is the transaction code CTO4 related with characteristics?

135. What is excise tax, and how is it related to the system?

136. What are the pricing procedures of CIN?

137. How are the data related to excise registrations maintained?

138. How is the contract configuration setting opened?

139. What are the major settings in the contract configuration setting screen?

140. What is the service and maintenance process?

141. Which is the standard sales document type for the service contract?

142. What are service items?

143. What is standard service item category?

144. What is the standard material type for service items?

145. What is the value contract?

146. What is an assortment module?

147. What is a master contract?


149. What is the referencing requirement?

150. How would you define referencing?





151. What is standard application logic?

152. What is workflow? Name the person who can assist you while configuring a workflow for a system.

153. What are scheduling agreements?

154. What is the planning delivery schedule?

155. What are the various sections of the planning delivery schedule?

156. What is correction delivery?

157. How is the scheduling agreement created?

158. What is a rebate agreement?

159. How are the rebate agreement types defined?

160. What are the rebate argument types as per standard system guidelines?

161. List the components of rebate processing in system.

162. How can you define a change request? How can you release a saved change request?

163. Give the menu path to create the tax calculation procedure.

Chapter 5: Sales

1. What do you understand by intercompany customers and one-time customers?

2. Explain the terms Minimum Order Quantity and Minimum Delivery Quantity.

3. Imagine you want to trace the changes made in the sales order in context of the changes to the partner function in the sales order. How can you do the same?

4. What is the difference between confirmed quantity and the order quantity?

5. How can you assign movement type?

6. What is the menu path to reject and cancel the sales order items?

7. How can you copy text from the sales order header to the billing document header?

8. Suppose, in a particular case, customer requirements for the sales order do not appear in the MD04 transaction. How can you resolve such a problem?

9. What transaction code is used for printing addresses or details of all customers at a single point of time?





10. What do you mean by backorder processing?

11. What is the functionality of the update button in the VA01 transaction at item level of conditions?

12. Describe the ways to include a new field in the VA01 sales order.

13. What is material determination?

14. How do you maintain substitution reasons?

15. How are the sales orders deleted?

16. What are the order and target quantities?

17. How can a release order be created?

18. Can you create more than one customer hierarchy for the same payer? If yes, then how?

19. A sales document is divided into three levels. List those three levels.

20. What is a sales order?

21. Write the statement to display your own error message when the selected batch is not available on acustomer-defined table.

22. Define an item proposal.

23. What is a quotation?

24. When is the cash sale process used?

25. When is the rush order process used?

26. A pop-up screen appears with a message “for this customer there are open quotations”, when you create a sales order using VA01. How can you disable this pop-up?

27. Write down the steps to decide a fixed discount for all possible values. For example, for each $75, discount amount should be $5. It means for $150 the discount amount should be $10, for $225 the discount amount should be $15, and so on.

28. How can you assign a sales representative as a partner by using the MASS transaction?

29. How can you change a position in a sales order with bapi_Salesorder_change?

30. How can you update a system to generate an error message when a user tries to enter two sales orders with the same reference to the customer’s purchase order?

31. How can you issue items from a storage location that has negative stock?

32. Give the menu path to define shipping conditions using the sales document type.





33. What is the use of a loading group? How can you define the loading groups?

34. Define backward scheduling.

35. List the various business functions that are performed to meet the delivery date.

36. Suppose you have received a sales order on the 10th and the requested delivery date for the materialis the 17th. When you check the stock, you find that the material is not available on the 10th; rather, it is available on the 15th. Now because the material is not available on the 10th, you cannot deliver the material on the 17th. On this condition, SYSTEM starts scheduling the process to find out the next earliest delivery date. What is this scheduling process called?

37. List the factors that need to be considered when deciding the routes.

38. Give the menu path to define the order block reason.

39. How can you create a list of the incomplete Sales documents?

40. List the activities for which you can set up the partner determination.

41. How is the consignment stock created?

42. What is the consignment stock?

43. What are the consignment steps?

44. How can you view the consignment stock allotted to the customer?

45. What is a consignment issue?

46. What is consignment returns?

47. Why is the consignment not returned into plant stock?

48. What is customer pick-up?

49. Name the standard overview for consignment.

50. How would you access the Display Consignment and Returnable Packaging at Customer overview?


52. What are the common sales document and work lists?

53. What is the sales document status?

54. What are the fields of the processing status?

55. How can you configure a status profile?

56. How can you configure a status profile to sales documents?





57. How can you configure a status profile to item categories?

58. List the tables that are used to display the status of sales documents.

59. How will you define incompleteness procedure?

60. What is general table display?


62. What is document flow?

63. What are the sales document types?

64. What is sales order stock?

65. What is backorder processing?

66. What are the transaction codes used for backorder processing?

67. What is trading process?

68. What is third-party order process?

69. What is invoice verification? Name the transaction code for it.

70. What is product group?

71. Mention two ways to restrict a user from changing fields in VA02 transaction code.

72. How can you set the ZOBP condition type to allow only the positive values?

73. Mention the differences between the stock transfer among the plants that have the same company code and the plants that have different company codes.

74. Explain the relation between the MM, SD, and FICO modules.

75. List the various types of special stocks.

76. Give the document flow from Enquiry to Invoicing in SD.

Chapter 6: Shipping

1. How can you link the Automatic Packing Procedure with the Delivery Type or Item category?

2. What is the most important concern that needs to be taken care of when creating delivery notes in different languages?

3. Define consumption modes.

4. How is the billing delayed to the next month in a delivery note?





5. What is the purpose of the shipping point determination?

6. An error V1032 occurs when we try to print the PL00 (packing slip in delivery). How can this error be avoided?

7. Write down the menu path for entering Shipping Point in Delivery from Sales Order.

8. What is the purpose of using the delivery process?

9. Can you create a delivery document with a reference?

10. Give the menu path to define delivery document types.

11. Which delivery document type can be created without reference to the sales order document?

12. Give the menu path to define the delivery item category.

13. Give the menu path to configure delivery item category determination.

14. List the transaction codes to execute the delivery due list.

15. How do you describe a shipping point?

16. Give the menu path to determine the shipping point.

17. How can you transfer the stock in an organization from one plant to another under one company code?

18. Suppose that you do not have stock but you can successfully press PGI, which is wrong. How can you configure a system that cannot press PGI without stock?

19. Suppose that you have to view the serial number assigned in a delivery document. Which report canbe used to view the serial number assigned in a delivery document?

20. In which document can you enter the serial number for material?

21. What is picking? How can you configure picking?

22. Why is warehouse management used? How are goods placed in the warehouse?

23. Why are delivery blocks used and how can they be configured?

24. Why is packing by item category used and how can it be configured?

25. What is special stock? Which transaction code is used to view the special stock?

26. Why is route determination required and how can it be defined?

27. Give the menu path to define the shipping blocks.

28. Why are the factory calendars used?





29. Give the menu path to define the customer calendars.

Chapter 7: Billing

1. Compare the milestone with periodic billing.

2. What happens if there is a negative posting in billing document?

3. Compare billing and invoice.

4. How can you print an invoice multiple times?

5. How can you view the due date of the invoice after making a delivery and invoice?

6. List a few commonly used sales documents that result in order-related billing.

7. What is the role of pro forma invoice billing document?

8. What is the role of the cancellation invoice?

9. What is the role of an inter company invoice?

10. What is the difference between inter company sales and intra company sales?

11. What do you mean by invoice lists?

12. What is the difference between milestone billing and periodic billing?

13. How do you perform a price adjustment when you have inputed an incorrect price in a completed invoice receipt and invoice issue for STO? How is a subsequent credit and debit in SD created for a subsequent credit and debit in MM?

14. An accounting document is created when you release an invoice to accounting. Imagine that you have canceled the invoice. Is it then necessary for the account module to delete the respective accounting document?

15. List the user exits for self-billing.

16. Which setting is used to activate the account setting at the header and item level?

17. How can you send an invoice by e-mail?

18. How can you fix the error message “Error in account determination”?

19. Why is the account determination used by the system?

20. How can we combine the noninventory and inventory items in one invoice?

21. Describe two types of credit processes.





22. When is the debit process used?

23. What is an invoice correction request?

24. Give the menu path to define the billing blocks.

25. What are the FI entries that are posted at the time of PGI and billing?

26. Define dunning. What do you need to configure before dunning?

Chapter 8: Sales Return, Credit, and Debit Memo

1. What is Sales Return?

2. What do you exactly mean by Credit Note and Debit Note?

3. Explain the system processing of Sales Return.

4. Is a shipping point assigned to a plant used during the process of sales return?

5. Can a sales return be denied for a credit note to a customer?

6. Can an additional scheme be issued to a customer through a credit note?

7. What is Return invoice?

8. What is the process of charging the customer in the case that a customer does not return the returnable packaging material?

9. What is the effect of a sales return on the inventory of material?

10. How are the goods returned by the customer handled?

Chapter 9: Miscellaneous

1. Explain all the transaction codes related to the sales and distribution module.

2. Differentiate between the SD account key and FI account key.

3. What are the constituents of the organizational data in the System?

4. Why is an outbound delivery, not Provides, the functionality to created by using the VL10D transaction code, even though STO is Provides the functionality to created? When you check STO, the delivery creation date is blank. What can be the cause of this problem?

5. Imagine that you are implementing R/3 in an auction services company. You have two alternatives totreat the services: First is to treat business units as distribution channels and service types as division; second is to use a dummy distribution channel and treat business units as divisions. However, there are problems associated with each alternative. The problem with the first alternative is increasing Sales





area number and that master data has to be extended across the Sales areas. The problem with the second alternative is to have different pricing for the same order type. What is the appropriate solution in such a situation?

6. Imagine you want to save a display variant under the SDO1 transaction code by using the Settings > Provides functionality to display Variants menu path. However, you are not able to save display variant as the save option is disabled. What would you do in such a situation?

7. How can you change the sales document type of a sales order once you have saved it?

8. What are the different ways of getting sales output with respect to the sales organization of customers?

9. Explain the origin of SYSTEM R/3.

10. Imagine that you are using the Provides functionality to create a quotation for a particular enquiry and try to change the configuration in the quotation. Will you be able to change it? If yes, then explain how you can change the configuration in the quotation.

11. Which concepts of the SD module are crucial while implementing pricing requirement and formulas?

12. Define the Determination Procedure.

13. Is it possible to change the pricing procedure once the document is prepared?

14. A free item that was scheduled to be delivered with the BOM item was not actually delivered, but indicated in the delivery status as delivered. Also, the initial number of free item is 0. How can it be resolved?

15. Suppose you have two condition types for cost in which one is VPRS and another is customized. The values of both condition types are correctly determined in the sales order. Now suppose that you have to provide the functionality to create the delivery and the billing document, but when you provide the functionality to create them the condition type VPRS is found incorrect with the value “0”. What is the reason behind this?

16. Give the menu path to include the condition type Z928 in the pricing procedure ZCS928.

17. The discount given previously for each characteristic may vary from customer to customer. Is there any way to find out how to configure this?

18. Suppose you are working in area menu maintenance, SE43, where you provide the functionality to create a copy of COND_AV (standard for maintaining condition records in SD) as ZCOND_AV. You have also changed its description, but in the area menu the changed description does not appear. How can you change the description of the area menu maintenance?





19. Imagine that you have two company codes and a new info structure SOO4 that you have to fill withthe data of the first company code. However, at the same time the data from the second company code is also available. How can you stop updating the new info structure with the data of the second company code?

20. What kind of records are updated by the system when you post goods issued in a delivery?

21. Why is the automatic credit management used?

22. Which block is used to prevent the system from creating deliveries by using the delivery-due list function?

23. Which block stops the system from creating the picking list?

24. List the most frequently used transaction codes in SD.


26. What are the sales object types?


28. When and how is blocking of sales process used? What are the transaction codes used for this purpose?

29. What is the transaction code that can be used to delete a sales order?

30. What is the transaction code to delete an invoice?

31. List the ERP packages available in the market.

32. Define the term consignment stock.

33. Differentiate between the contract agreement and the scheduling agreement.

34. What do you mean by availability check?

35. Explain the following terminologies used in the availability check process in the SD module: Backorder Processing, Rescheduling, Availability to Promise, and Replenishment Lead Time.

36. Explain the basic elements to be configured during the availability check process.

37. What do you mean by cross-company stock transfer?

38. List the conditions needed to perform transfer of requirements.

39. Specify the menu path to display stock requirement list.

40. Explain the functions controlled by the help of a blocking indicator.





41. List the tables used in the SD module.

42. Explain the five views of the customer-credit master record.

43. What is a credit-control area, and how is it related to company codes?

44. Specify the highest level of organizational units in the SD, MM, PP, FI, and CO modules.

45. Explain the views of the material master record.

46. What is the difference between an inquiry and quotation?

47. Explain the five types of messages in the mySAP ERP system.

48. Explain the possible units of measurement that can be used for a material.

49. Why are different item and schedule-line categories used?

50. List the archiving objects for the following objects in the SD module: Sales documents, Billing documents, Sales activities, Rebate agreements and relevant conditions, Conditions, and Customer master data.

51. List the tables from where the system archives data when you use the SD_VBAK archiving object.

52. List the functions and their report programs available for the SD_VBAK object.

53. List the tables from where the system archives data when you use the SD_VBRK archiving object.

54. List the functions and their report programs available for the SD_VBRK object.

55. List the tables from which the system archives data when you use the SD_VBKA archiving object.

56. List the functions and their report programs available for the SD_VBKA object.

57. List the tables from which the system archives data when you use the SD_AGREEM archiving object.

58. List the functions and their report programs available for the SD_AGREEM object.

59. List the tables from which the system archives data when you use the SD_COND archiving object.

60. List the functions and their report programs available for the SD_COND object.


