SAP SD INTERVIEW QUESTION ANSWER

SAP SD (Sales Distribution) is all about the process of order to delivery. Further, it is essential for executing all kinds of business procedures like shipping, selling, and billing of products. It is also used for –

• Sales orders
• Consignment
• Credit & Debit memo requests
• Backorder
• Inquiries and Quotes
• Sales return
• Contract & Scheduling agreements
• Rush orders & Cash sales

Yes! It is possible to assign the same company code.

We all know that shipping is an essential part of any manufacturing company to ensure efficient customer services and delivery of products. Shipping is required for outbound delivery, planning and monitoring, post goods issues, picking and packaging of goods, and shipping communication.

Talking about the modes of transport, there are few ways of defining them –

• Using T-code SPRO.
• Visit IMG> Logistics Execution > Transportation > Basic Transportation Function > Routes > Define Routes > Define modes of transport > Click on ‘Execute’

Firstly, about the periodic, it is a full amount mentioned in each bill and continues until the contract period. In contrast, the milestone is about the partial amount, which is mentioned until the full amount is billed.

Basically, the product groups are generally defined as a wide-ranging spectrum of products. In every division, it is possible to create a customer-specific agreement. Moreover, it is also possible to carry out statistical analyses and setting up separate marketing.

A credit control is necessary for assigning more than one company code to more than one credit control area. Credit Control Area is present as an organizational unit used for specifying and checking credit limits for customers.

In general, there are two types of techniques available in delivery Scheduling. These are mentioned as –

• Forward scheduling – In this system, you can calculate the earliest possible date dependent on the material available date.
• Backward Scdg – This is about calculating the requested delivery date.

Well, an Outline Agreement is defined as a long-term purchasing agreement done with the vendors. In this agreement, you will find general terms and conditions related to the material that is usually supplied by the vendors. Outline agreements have two types that are involved in the SAP SD course.

• Scheduling Agreement: It is known as an external agreement comprising the details of services, products, and delivery dates.
• Contract: The contracts usually exist between ordering parties and vendors over a specified period. You will find two types of contracts mentioned as value contracts and quantity contracts.

Product proposals are known as critical aspects whenever we discuss SAP SD. Such proposals are used in various companies needed for revamping the sales quotient by endorsing the products at the time of sales document processing. Moreover, these proposals can easily be mapped depending on the specific requirement of business partners so that they can easily match the market demands.

Firstly, the inquiry is the process that includes registration of the customer’s probable requirements. On the other hand, the proposal is a kind of legally abiding document, which is offered to customers following the terms and conditions for delivering the service as well as the product.

ACross-company Stock Transfer is the method of delivering the sales order via another company code. Moreover, it is also essential for providing the material from a plant having one company code to plant in another company code.

Consignment stock is generally the material that is available on the company premises but does not add in the stock. It is only added when it is either marked as sold or sent to the production department.

In SAP SD, pricing is mentioned as a process that generally includes the calculation of costs and prices for both external vendors and customers. Defining the pricing elements, these are the condition types present in an SAP system. The condition types are defined as a set of scenarios that are taken care of at the time when pricing is assigned to a service or product. Some such elements are surcharges, prices, taxes, and discounts.

Whenever any key transaction in sales is done, there is a required sales document that needs to be copied to another document. Here, the process of copy control is usually incorporated. Several routines show how data should be copied using a source document to target the document.

As the name suggests, it is about transferring the legacy data to all new configured and installed systems. Legacy data is known as data like material and customer that is maintained by organizations before they install the ERP system. There are lots of tools available that are needed to transfer the legacy data to Systems such as Legacy System Migration Workbench Programs and Batch Data Communication (BDC).

Here are some of the Transaction codes which are used for the same purpose.

– XD01: Used for creating customers.

– XD02: Required for changing a customer.

– XD03: Needed for displaying a customer.

– XD04: Essential for altering customer changes.

– XD05: Required for blocking a customer centrally.

– XD06: marking a customer for deletion.

– XD07: Changing a customer account group.

– XD99: Upholds customer maintenance.

– XDN1: Keeping the numbers ranging for a customer.

There is a sequence of steps included in determining the tax number as well as tax classification. These are –

• In case the payer has a VAT registration number, it is easy to copy the tax classification and tax number from the payer. Further, this tax number is copied depending on the ‘country of destination relevant for taxes.’
• If step 1 is not able to apply or ship-to party has a VAT registration number, it is possible to copy the tax number and classification from the ship-to party.
• Moreover, if step 2 also doesn’t work, then also tax number and tax classification can be copied from the sold-to party.

At the time of working on Inter-Company Sales, there is a transaction code MM01 required for creating materials relevant to the plant and sales organization. One can extend the material if someone is using a common server.

Here, we are mentioning the necessary elements required for a customer master record.

• Company code data
• General data
• Sales area data

As we know, the quotations are present as legal documents that are sent to the customers. There is information like the delivery of services and goods that are included in the quotation. For creating a quotation, one has to use the transaction code ‘VA21’.

Sales Document: This document is related to sales and is generally built in the SAP system for managing the complete sales process.

Sales Activity: The mentioned activities are classified as post- and pre-sales activities. They are used to improve the sales of any company.

Any inquiry coming from the customers’ side mostly comprise one or more items containing the number of products. This quantity is further divided into business lines that have different sales parameters. It has seen that the items are generally combined in a hierarchy, and therefore, it is possible to create a difference between batches.

Talking about the SAP credit memo, it is usually created based on a credit memo request. It can be generated at the time when you have to pay the customer. The return order is about receiving the returned goods coming from the customers. Hence, the sales department is responsible for creating return orders, and based on this return delivery document is created.

Purchase Organization is the key element used during the time of purchasing.

Sales Office: Sales office is a geographical group that is created for structuring a sales team within an organization. The sales office can be assigned to one or more Sales Area.

Sales Groups: There is a staff of Sales Office that is divided into Sales Groups and further to Sales Employees. So, Sales Groups is a kind of group of persons related to the sales department working for numerous purposes.

Sales Employees: Sales employees are those who have personnel master records required for managing data of Sales employees.

First coming to the shipping point, it is a point from where the team can ship the deliveries of products. Though, the subdivision of the shipping point is referred to as a loading point that means a manual entry in the header data of delivery according to customization.

A division is present as a product group for a vast range of services. In sales organizations, there are lots of divisions that incorporate customer-specific arrangements.

R/3 is present as a three-tiered architecture, which is used by the system. There are three tiers mentioned:

• Application server
• Database server
• Presentation server

ERP (Enterprise Resource Planning) is called a software package. It is designed especially for the integrated management of numerous business processes like order placement, invoicing, inquiry, and billing. Though, it is much needed in manufacturing industries to accomplish the core business areas like finance and production. Due to the popularity of the ERP package, its functionalities can also be extended to cover the overall business management.

It is available as a beneficial tool for creating reports in System. Furthermore, it is useful for creating reports without any help from programming. It is quite similar to ABAP Query.

SAP has recognized to offer different reports in every module. In case if the standard reports do not comply with the business requirement, then there is a need to develop your reports. Z reports, also known as ABAP custom reports, can create any program that needs to start with Z.

This indicates typically a formula required for a condition type to promote an alternative base value needed for the calculation of a value.

Invoice correction is a kind of sales document (RK). It is a documented process showing a new method of processing complaints and issuing both debit and credit memos. It also allows the users to correct the price and quantity for more than one faulty item present on an invoice. The request for each invoice is made about the invoice. There are two items in each invoice correction request. The first one is the quantity and value copied from the given invoices. The second one is the debit item that shows the correct quantity and value.

• Sales Organization: It is an organization unit involve in selling and distributing products, negotiating terms of sales, and accountable for truncations.
• Distribution channel: As the name implies, the mentioned channel acts as a medium for materials or services to reach customers. It contains internet sales, retail, direct sales, and wholesale. The distribution channel can be assigned to one or more sales organizations.
• Division: This is a wide-ranging spectrum of products.

ASAP is all about streamlining the implementation process, and this can be done by offering methods, tools, templates, and accelerators. These are generally built on various SAP implementations. Further, this implementation is divided into 5 phases.

Phase 1 – Project Preparation

Phase 2 – Business Blueprint

Phase 3 – Realization

Phase 4 – Final Preparation

Phase 5 – Go-live and Support

In the field of SAP, the sales item category is considered to be very important. A company requires it to control the sales document flow while impacting the schedule line category. The item category put an effect n delivery and billing process.

There are specific steps required to be followed when there is a cleared down payment request is needed to be cancelled. Such steps are also required to avoid the doubled down payment items.

• T-code FBRA is used for clearing.
• If someone wants to cancel the clearing needs, it can be done via t-code FB08.
• One can cancel the down payment request by VF11.

When a company wants to offer a discount regardless of combination up till a certain period, this is known as Condition Supplement. The system, by default, provides discounts together with a base price.

• Discount: It is a general disc, which is usually applied in business transactions frequently. It is available for all the customers.
• Rebate:Rebate is an agreement present between Sales Org. It is a kind of special discount, which is given occasionally. Thee customers can avail of this discount on reaching the sales volume within a time.

Access Sequence is a type of search strategy that is used for finding the correct condition record using the condition table.

Sometimes, there is a lack of material to complete the sales order. In such circumstances, a delivery date is given when the goods available are available before the delivery date. Thus, it is possible to deliver the goods before the arrival of the first delivery date. This process is known as Backorder processing.

Bill of Material is a ubiquitous term used in Sales Distribution. It combines a group of materials with two products named header level item and item level item. You can say that it is a list of raw materials, parts, intermediate assemblies, sub-components, and quantities required at the time of manufacturing.

There are four types of partner functions available mentioned –

• Ship to Party – Where a person received the goods.
• Payer – In this, a person pays the payment.
• Sold to Party – An individual who places the order.
• Bill to Party – A person who gets the bills.

For your information, it is difficult to delete the sales orders once you saved them. One can either cancel the sale order or reject it.

Here, we are mentioning some of the influential factors that you should also know.

• AAG of the customer.
• A/c key.
• Chart of A/c.
• AAG of material.

There are lots of technical reasons that make you implement SAP in your company as well. SAP is highly configurable, provides safe data handling, minimize data redundancy, maximum data consistency, and others. Thus, you can get the profit of sales like tight integration-cross function and purchasing.

It can be done through an availability check.

The assignment ensures that the sales organization is capable of supplying the materials to customers via the distribution channel. The steps include in this are:

We are mentioning steps followed for customizing the Rebate processing.

• Firstly, activating the rebate in customer master data.
• Activating the selling material in MM data.
• It is required to activate sales org.
• Activate the billing doc.

Shipping Point is defined as an organizational element that is answerable for shipping the materials and deliver to the customers.

In simple terms, a transfer order is a process of picking the order. Generally, the material is picked from the storage, loading area, and picking area.

XDO1

3 Tabs. General Data, Company Code and Sales data.

General Data—– Control Data —- Tax Information

Master Data refers to the characteristics of an object whereas transaction data refers to all the transactions that are carried out using the object. Any data which does not change so frequently in master data like configuration settings like company data, personal area etc. Any data which keeps changing so often in transactional data, like employee data.

In this case, we are using third party process. This process uses a purchase order (Which is sent to you by vendor). Also, invoice verification is used further along the process to check that the invoices you send to your customer are the same material and quantity as that which the vendor sent to the customer (But obviously shipped directly to your customer).

One or more company code.

One or more.

One or More.

SAP have provided a lot of reports in each module. However, if the standard reports do not meet the business requirement, we can develop our own reports. ABAP custom reports are called z reports because any program developed have to start with Z.

FICO Consultant.

VKOA.

In Pricing Procedures 16 steps are needed to maintain. These are Step, Counter, Condition Type, Description, From, To, Manually, Mandatory, Statistically, Print, Sub
Total, Requirement, Alternative Condition Type, Alternative condition base value, Account Key, Accruals Key.

This column indicates a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value. For example, you may specify a formula that uses a subtotal of 4 from the subtotal field and then modifies it slightly by dividing it by 2 and using the resultant value as a base value for a condition type.

This column is used to specify that the system is to use the formula represented in this column as an alternative in finding the value of the condition type, rather than by using standard condition technique. This is may be used, for example, to calculate complex tax scenarios.

It is a sales document type(RK). This documented process a new way of processing complaints and issuing credit and debit memos. The document allows us to correct the quantity and the price for one or more faulty items on an invoice. Each invoice correction request is made in reference to a (mandatory) invoice. We cannot create one in reference to an order or quotation. Each invoice correction request contains two items for each item on the invoice. The first item is the value and quantity copied from the invoices; this appears as the credit item. The second item is the debit item, which represents the correct quantity and or value. Should you change this second debit item due to new pricing etc, the difference between the two would then be automatically passed on to billing as either a credit or debit memo.

Sales Document Header (VBAK), Sales Document Item (VBAP), Sales Document Schedule line (VBEP).

OBYC.

VKOA.

Sales Organization, Distribution Channel, Division, Document Pricing Procedure, Customer Pricing Procedure, Pricing Procedure, Pricing Procedure(Description), Condition Type, Condition Type(Description).

• Sales Organization: An organizational unit sells and distributes products, negotiates term of sales, and is responsible for these truncations.
• Distribution Channel: This channel through which materials or services reach customers.Typical distribution channels include Internet sale, wholesale, retail and direct sales. You can assign a distribution channel to one or more sales organisations.
• Division: Product groups can be defined for a wide-ranging spectrum of products.

One or More.

Yes, it’s possible.

ASAP streamlines the implementation by providing templates, methods, tools and accelerators that have been built on the success of thousands of previous SAP implementations.
This methodology divides the implementation process into 5 phases.

• Phase 1: Project Preparation.
• Phase 2: Business Blueprint.
• Phase 3: Realization.
• Phase 4: Final Preparation.
• Phase 5: Go-live and Support.

The sales item category is one of the most important fields in the SAP sales order. It controls the sales document flow and also impacts the schedule line category. The item category of the sales order affects the delivery and finally impacts the billing process as well.
Sales Document Type, Item Category Group, Item Category Usage, Higher-Level Item, Default Item Category.

Higher level item category depends upon the material type and item category of the other item. The higher level item category by looking at any linkage of items and then tracing back to the main item category.

Higher Level Item Category is the item category of the high-level item. It controls the item category of the item along sales document type, item category group, and usage.

Basically higher level item makes the functionally of how the item should behave along with material type.

In IMG screen Global Settings

yes

Instead of the of ‘MATERIAL’ field, user must use ‘MATERIAL_LONG’ fi

In case, a cleared down payment request is required to be cancelled then the user must perform the following steps in order to avoid doubled down payment items in the final billing document:

• The clearing should be set back via t-code FBRA
• The clearing needs to be cancelled via t-code FB08
• Finally, the down payment request can be cancelled by VF11.

User is required to maintain the default tax jurisdiction code in transaction OBCL

This must be at a state level, that is only first level which has to be maintained. For instance:

• Inside t-code OBCO the tax procedure encompasses jurisdiction code structure 2 2 0 0
• the default tax jurisdiction code should be XX00 (where XX is the code of first level)

The term ‘Period’ refers to an option visible on the initial screen for report RVKRED08 where a selection option for ‘Date of next credit check’ has been provided, in the documentation.

The default period is referred to as the starting to the end of the current month, this can also be adjusted in case the date falls outside this default period.

The option ‘Take release data into account’ permits the user to exclude all those documents which have been released manually. For Instance, incase this option is selected, all documents which were released manually will be excluded when the report is executed.

• There is no authorization check available for restricting the completion of a pro forma billing document.
• The ‘Complete’ field can be inactivated via modification
• In program MV60AF0C_CUA_SETZEN the internal table cua_exclude is required to be filled with ‘FERL’ in field FUNCTION.
• By performing this function, the field ‘Complete’ will be inactivated and pro forma billing documents cannot be cancelled.

Post output processing (e.g. for billing document), user can verify the output processing log in VF03 through the menu path Goto -> Header -> Output: by selecting the relevant output type and clicking on ‘Processing log’.

Yes. The tool will detect the mapping between SAP Tax Authorities (e.g. ‘FED’) and BSI Tax Authorities (e.g. ‘00000000’) and it automatically creates any missing mapping in the BSI Dataset which subsequently corresponds to the client of the system in which the user ran the tool. This is done when user selects to run the tool in productive mode for client-specific tables.

Yes, by maintaining the validity period in records & the value gets triggered as per the pricing date mentioned in the transaction (Order).

The price is get determine in sales based on

1. Sales are

2. Customer pricing procedure

3. Sales document

4. Pricing procedure

The pricing procedure is assigned to the combination of sales area and customer pricing procedure and document pricing procedure by using transaction code ovkk

Billing is a document which raised to the payer. It includes the amount he has to pay for the product/service he is receiving from the business.

Delivery is a document which contains the information related to the delivery of the product. Like delivery quantity, actual delivery date, packing,picking etc. Generally, delivery document can be created for the ship-to-party.

Requirement is a field which is used to validate a condition type i.e. if certain condition is met then only the corresponding condition type will be accesses else it will not.

For Ex: Plant is a pre-requisite to pick the Pricing while making a Sales Order, hence until or unless Plant name is inserted in SD pricing will not be picked as its a requirement.

SAP Sales and Distribution is one of key component of SAP ERP system and is used to manage shipping, billing, selling and transportation of products and services in an organization.

SAP Sales and Distribution module is part of SAP Logistics module that manages customer relationship starting from raising a quotation to sales order and billing of the product or service. This module is closely integrated with other modules like SAP Material Management and PP.

SAP SD organization structure majorly consists of two steps: Creation of Organization elements in SAP system and second is to link each element as per requirement. On the top of organization structure in SD module, sales organization is at highest level and is responsible for distribution of goods and services.

SAP recommends to keep number of sales organization in organizational structure to be minimum which helps in making reporting process easy and ideally it should have a single Sales organization.

• Distribution channel tells the medium by which products and services are distributed by an organization to its end users. Division in an organizational structure represents a product or service line in a single organization.
• A Sales area is known as entity which is required to process an order in a company. It is comprised of Sales organization, distribution channel and a division.
• In SAP SD organizational structure, each sales organization is assigned to a company code. Distribution channel and divisions are assigned to Sales organization and all comprise to make a sales area.

A Sales area is known as entity which is required to process an order in a company. It is comprised of Sales organization, distribution channel and a division.

No, shipping point is required to perform goods delivery.

No, invoice is not possible without delivery.

Consider an example of creating a sales order in SAP SD, it involves copying details of item from Material Management.

Availability check of the item and price details are also taken from MM but this can be controlled this data in SD module. To create inbound and outbound delivery of goods for a sales order, shipping details, loading point etc. also come from Material Master.

In case of standard sales order, you create an outbound goods delivery to the customer. Here movement 601 takes place. This movement is configured in MM and movement of goods hit some G/L account in FI.

Partner function allows you to identify which functions partner has to be perform in business process. Consider a simplest case, where all the customer functions are performed by partner customer. As these are mandate functions they has to be defined as obligatory functions in SD system.

• Domestic customers
• Export Customers
• One Time Customers

All Sales activities in SAP SD system can be divided into presales and post sales activities. Presales activities are classified as activities which occurs before product is sold to customer and post sales activities are those which occurs after product is sold.

• Pre Sales Activities − Inquiry, quotation
• Post Sales Activities − Support, Relationship management

Sales support is one of the key component in Sales and Distribution SD module. It is also called computer Aided Selling SD-CAS.

This module helps organizations to create new sales, tracking of existing sales, and performance and eventually help in improving marketing and sales in an organization.

SAP SD Sales support module provides an option of creating email list for the customer and directly sending mails for new leads.

Sales order processing describes a function related to whole sale part of an organizational business. Common functions under sales order processing −

• Availability of the articles purchased
• Checking for incomplete data
• Checking the status of the sales transaction
• Calculation of pricing and taxes
• Schedule the deliveries of goods
• Printing of documents or e-transfer of documents

Structure of a Sales Order −

An inquiry from a customer consists one or more items that contains the quantity of a material or service entered in the order.

The quantity in a Sales order is further divided into business lines and comprise of various subsets and delivering dates.

Items in Sales order are combined in a hierarchy and allows to differentiate between batches or to use combinations of materials.

All the valid conditions on the items are mentioned in item conditions. These conditions for an item can be derived via a full condition and can be valid for entire sales order.

You can divide an item to multiple billing plan deadlines and each tells the time when a fixed amount of the item is to be billed.

• VA02 − Edit a Sales Order
• VA03 − Display a Sales Order
• T-Code − VA01 Create a Sales Order

An Inquiry is not a legal document and is used to record the information about delivery or services from customers. The information that is captured using an inquiry is related to materials and quality of goods.

Menu Path − Logistics → Sales and Distribution → Sales → Inquiry → Create

T-Code − VA11

Quotation is a legal document to customer for delivery of goods and services. This is normally issued after an inquiry from customer or without an inquiry.

SAP R/3 Menu
Logistics → Sales and Distribution → Sales → Quotation → Create
T-Code − VA21

Sales Activity

Sales activities are categorized as Presales and post sales −

This include when you sell material rather you do your preparation for sales with the customer…

Sales Call, Phone Call, Sales Letter, and post sales like support and relationship, etc.

Sales documents

These documents are considered under sales, where you sell the materials to the customer and are created in SAP system to manage sales process.

Example − Sales orders, Quotations, etc.

• SPRO-IMG-Enterprise Structure-Assignment-SD-Assign Plant to Sales Organization/Dist.Channel
• T-Code − OVX6

No

Sales support is one of the key component in Sales and Distribution SD module. It is also called computer Aided Selling SD-CAS.

This module helps organizations to create new sales, tracking of existing sales, and performance and eventually help in improving marketing and sales in an organization.

SAP SD Sales support module provides an option of creating email list for the customer and directly sending mails for new leads.

Sales support stores all the data related to sales and distribution related to customers, products, materials, competitor products, etc.

There is a customer telephone inquiry in the system and then customer requests a quotation which can be created by referring to same inquiry. Next is the customer place an order on the basis of quotation and a sales order is created by copying the information from the quotation and if any modifications are required.

Merchandise is shipped and bill is sent to the customer. After the delivery of goods, customer raises a claim damaged articles, a delivery can be created free of charge with reference to the sales order.

There are different types of sales document that can be defined in SAP system −

• Credit Memo
• Debit Memo
• Standard Order
• Delivery Returns, etc.
• To define a Sales Document

Enter T-Code − VOV8 or SPRO → IMG → Sales and Distribution → Sales → Sales Document → Sales Document Header → Define Sales Document Type

In SAP Sales process, a standard item function is same as function of free or charge item or text item?

No

• General Data Control Elements
• Shipping data Control Elements
• Billing Data Control Elements

Inquiry −

• No Delivery of an item
• No Availability check
• Information purpose

Quotation −

• No Delivery
• No Movement

Order −

• Schedule line is suitable for delivery
• Movement type 601

Return −

• Schedule line is suitable for delivery

You can assign particular material master to particular Plant and it picks up from there.

It shows date of calculation of pricing procedure for that Particular document. So that in future you can see the date on which pricing calculated for that particular document.

Copy Control is defined as a process in which important transactions in a sales document are copied from one document to other. It consist of routines which determines the system how the data is to be copied from source document to target document.

A SAP system contains number of these routines and you can also create additional routines to meet the business requirements. To create a new routine you can use an existing sales document as a reference.

How to find Copy Controls in SAP system?

These controls are created and configured under IMG and can be found at below menu path −

• SPRO → IMG → Sales and Distribution → Sales → Maintain copy control for sales documents
• SPRO → IMG → Sales and Distribution → Shipping → Specify copy control for deliveries
• SPRO → IMG → Sales and Distribution → Billing → Billing Documents → Maintain copy control for billing

Pricing in Sales and Distribution is used to define the calculation of prices for external vendors or customers and cost. Condition is defined as set of conditions when a price is calculated.

Example −

Consider a case when a customer orders specific quantity of a product on a particular day. Various factors like customer, product, order quantity and date tells the final price to customer. This information is stored in the system as master data in the form of condition records.

There are various pricing elements like prices, surcharges, discounts, and taxes are defined in SAP system as condition types. To manage pricing information for a pricing element in a system, you have to create condition records.

A Condition table is defined as combination of keys to identify an individual condition record. A condition record is defined as how system stores the specific condition.

Example of Condition Record −

Entering the price of a product or to specify the discount for a privilege customer.

Example of Condition Table −

Condition records for a customer specific material prices are stored by a sales department. SAP system contains a conditional table 005 for this purpose. Key of table 005 includes below field −

• Customer
• Material
• Sales Organization
• Distribution Channel

First two fields − Customer and Material determines the relationship between customers and specific materials. Last two fields are used to identify organization data in SAP system.

Condition type is defined as specific features of daily pricing activities in SAP system. Using condition type you can also put different condition types for each pricing, discounts on goods, tax and surcharge that occurs in business transactions.

Condition type allows you to define the discount for special material. This can be specified in the system to calculate discount as an amount or it can calculate discount in terms of percentage.

In case you have to use both discount types, two separate condition types has to be defined in the system.

A standard SAP system includes variety of common discount types. You can also define customize discounts and surcharges as per business requirement.

While creating a condition records, you can use any of standard discount types. While doing automatic pricing, system checks for the discount that satisfies a certain condition and it checks for a valid condition records.

If a discount refers to a group like a material group or price groups, that group must be assigned to relevant customer or material master record before automatic pricing is done in the system.

Product Proposal helps an organization to increase the sales by recommended other products to the already added products or by replacing one already added. The products recommended can be cheaper, expensive or similar to the product that is requested by the customer.

Automatic Product Proposal is one of most powerful tool used in online marketing of products.

Product Proposals can be mapped to specific requirement of business partners to match their market requirement.

Sales area is a combination of sales organization and distribution channel and Division. Division is a logical grouping of products, hence you can’t extend material to other sales areas. But you can extend customer to other sales areas through common Distribution channel & division.

There are different types of Sales Order that can be placed −

• Cash Sales

This is defined an order type where customer place an order, pick up the order and pay for the goods. In this order type delivery of the order is executed immediately when the order has been entered. Cash invoice and billing can be printed immediately from the order.

No Receivables is entered for customer as invoice amount is paid cash and directly entered to a cash account.

• Rush Order

In this order type, delivery of good is picked by customer or you deliver the goods on the same day when the order is placed.

• Scheduling Agreement

A scheduling agreement is defined as an external agreement with the customer and having details of quantity of goods and delivery dates. This information is mentioned as schedule lines In a standard system, Schedule lines can be created with the scheduling agreement or you can also create these at later stage.

Free of charge delivery or subsequent delivery is made when customer is not satisfied with product or good or lesser quantity of good is delivered and company has to initiate a return as per customer request. In this delivery, customer is not charged for shipping of goods.

Steps to be followed in case of Return request −

• Credit Memo −

This is done when customer wants refund for the delivered goods. System creates credit memo sales document to customer with reference to sales order.

• Subsequent delivery −

This includes free of charge delivery of disputed goods to the customer. This is required when incorrect quantity of goods is delivered to customer.

Creating a return request in system − T-Code − VA01

Outline agreement is a long term purchasing agreement with vendor containing terms and conditions regarding the material that is supplied by vendor.

Outline agreement are valid up to certain period of time and cover a certain predefined quantity or value.

Outline agreement is of following two types.

• Contract
• Scheduling Agreement

Contract

Contract is a long term outline agreement between vendor and ordering party over predefined material or services over certain framework of time. There are two types of contract

Scheduling Agreement

A scheduling agreement is defined as an external agreement with the customer and having details of quantity of goods and delivery dates. This information is mentioned as schedule lines In a standard system, Schedule lines can be created with the scheduling agreement or you can also create these at later stage.

Quantity Contract − In this type of contract overall value is specified in terms of total quantity of material to be supplied by vendor.

Value Contract − In this type of contract overall value is specified in terms of total amount to be paid for that material to the vendor.

Contract can be created by following the below steps −

Path to create Contract −

• Logistics ⇒ Materials Management ⇒ Purchasing ⇒ Outline Agreement ⇒ Contract ⇒ Create
• T-code − ME31K

Path to create Scheduling Agreement −

• Logistics ⇒ Materials Management ⇒ Purchasing ⇒ Outline Agreement ⇒ Scheduling Agreement ⇒ Create ⇒ Vendor Known
• T-code − ME31L

Consignment stock management includes four key activities in the system −

• Creating a Consignment Fill-Up (Stock is fill up at warehouse)
• Creating Consignment Issue (Stock issued from warehouse)
• Creating a Consignment Pick-Up (Stock return to manufacturer)
• Displaying Consignment Returns (Stock return from customer)

Shipping is defined as an important activity in sales process. It comes under logistic chain and guarantees customer service and distribution of goods.

It is a component of Sales and Distribution module and is used to perform outbound delivery and other shipping activities like picking and packing of the goods.

In shipping process, below are the key sub processes −

• Delivery processing of the goods
• Picking of items
• Packing of the goods
• Post goods issue
• Shipping communication
• Planning & monitoring of shipping

To define Modes of Transport, navigate −

• SPRO → IMG → Logistics Execution → Transportation → Basic Transportation Function → Routes → Define Routes → Define modes of transport → Execute.

XDO1

3 Tabs. General Data, Company Code and Sales data.

General Data—– Control Data —- Tax Information

Master Data refers to the characteristics of an object whereas transaction data refers to all the transactions that are carried out using the object. Any data which does not change so frequently in master data like configuration settings like company data, personal area etc. Any data which keeps changing so often in transactional data, like employee data.

In this case, we are using third party process. This process uses a purchase order (Which is sent to you by vendor). Also, invoice verification is used further along the process to check that the invoices you send to your customer are the same material and quantity as that which the vendor sent to the customer (But obviously shipped directly to your customer).

One or more company code.

One or more.

One or More.

SAP have provided a lot of reports in each module. However, if the standard reports do not meet the business requirement, we can develop our own reports.ABAP custom reports are called z reports because any program developed have to start with Z.

FICO consultant.

VKOA.

Total, Requirement, Alternative Condition Type, Alternative condition base value, Account Key, Accruals Key.

when after we r creating the IDOC type it will show screen, there we can create the segments by right click. then one pop up window will display like which segment(Ex: SEG1) u need to add to the IDOC then add the one more segment(Ex:SEG2) to the IDOC . while add SEg2 to the IDOC , pop up will display like segment name which u can add and there is the options like under which segment u need to create the segment here u can select SEG1.

now SEG1 —-> parent segment

SEG2 —-> child to the SEG1

In Pricing Procedures 16 steps are needed to maintain. These are Step, Counter, Condition Type, Description, From, To, Manually, Mandatory, Statistically, Print, Sub

Total, Requirement, Alternative Condition Type, Alternative condition base value, Account Key, Accruals Key.

This column indicates a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value. For example, you may specify a formula that uses a subtotal of 4 from the subtotal field and then modifies it slightly by dividing it by 2 and using the resultant value as a base value for a condition type.

This column is used to specify that the system is to use the formula represented in this column as an alternative in finding the value of the condition type, rather than by using standard condition technique. This is may be used, for example, to calculate complex tax scenarios.

It is a sales document type(RK). This documented process a new way of processing complaints and issuing credit and debit memos. The document allows us to correct the quantity and the price for one or more faulty items on an invoice. Each invoice correction request is made in reference to a (mandatory) invoice. We cannot create one in reference to an order or quotation. Each invoice correction request contains two items for each item on the invoice. The first item is the value and quantity copied from the invoices; this appears as the credit item. The second item is the debit item, which represents the correct quantity and or value. Should you change this second debit item due to new pricing etc, the difference between the two would then be automatically passed on to billing as either a credit or debit memo.

Sales Document Header (VBAK), Sales Document Item (VBAP), Sales Document Schedule line (VBEP).

Yes, it’s possible.

ASAP streamlines the implementation by providing templates, methods, tools and accelerators that have been built on the success of thousands of previous SAP implementations.

This methodology divides the implementation process into 5 phases.

• Phase 1: Project Preparation.
• Phase 2: Business Blueprint.
• Phase 3: Realization.
• Phase 4: Final Preparation.
• Phase 5: Go-live and Support.

Instead of the of ‘MATERIAL’ field, user must use ‘MATERIAL_LONG’ field

In case, a cleared down payment request is required to be cancelled then the user must perform the following steps in order to avoid doubled down payment items in the final billing document:

• The clearing should be set back via t-code FBRA
• The clearing needs to be cancelled via t-code FB08
• Finally, the down payment request can be cancelled by VF11.

User is required to maintain the default tax jurisdiction code in transaction OBCL

This must be at a state level, that is only first level which has to be maintained. For instance:

• Inside t-code OBCO the tax procedure encompasses jurisdiction code structure 2 2 0 0
• the default tax jurisdiction code should be XX00 (where XX is the code of first level)

The term ‘Period’ refers to an option visible on the initial screen for report RVKRED08 where a selection option for ‘Date of next credit check’ has been provided, in the documentation.

The default period is referred to as the starting to the end of the current month, this can also be adjusted in case the date falls outside this default period.

The option ‘Take release data into account’ permits the user to exclude all those documents which have been released manually. For Instance, incase this option is selected, all documents which were released manually will be excluded when the report is executed.

Post output processing (e.g. for billing document), user can verify the output processing log in VF03 through the menu path Goto -> Header -> Output: by selecting the relevant output type and clicking on ‘Processing log’.

Yes. The tool will detect the mapping between SAP Tax Authorities (e.g. ‘FED’) and BSI Tax Authorities (e.g. ‘00000000’) and it automatically creates any missing mapping in the BSI Dataset which subsequently corresponds to the client of the system in which the user ran the tool. This is done when user selects to run the tool in productive mode for client-specific tables.

Yes, by maintaining the validity period in records & the value gets triggered as per the pricing date mentioned in the transaction (Order).

Billing is a document which raised to the payer. It includes the amount he has to pay for the product/service he is receiving from the business.

Delivery is a document which contains the information related to the delivery of the product. Like delivery quantity, actual delivery date, packing,picking etc. Generally, delivery document can be created for the ship-to-party.

SPRO stands for SAP Project Reference Object

SPRO is used to configure the SAP System as per client’s requirement. IMG (Implementation Management Guide) menu which you will find customization settings for all SAP modules, will be shown after executing SPRO transaction.

A customer orders some items from your company by creating a sales order

(Tcodes: VA01, VA02, VA03, Tables: VBAK, VBAP etc).

Your company decides to deliver the items ordered by the customer. This is recorded by creating a outbound delivery document (TCodes:VL01N, VL02N, VL03N, Tables: LIKP, LIPS etc).

Once the items are available for sending to the customer, you post goods issue which reduces your inventory and puts the delivery in transit. This will create a material document. You will post goods issue using VL02N but the material document created will be stored in tables MKPF, MSEG.

You will then create shipment document to actually ship the items. (Tcodes: VT01N, VT02N, VT03N, Tables: VTTK, VTTP etc).

You finally create a sales billing document. (TCodes: VF01, VF02, VF03, Tables: VBRK, VBRP etc). This will have a corresponding accounting document created that will be in BKPF, BSEG tables.

When customer pays to your invoice, it will directly hit your Account Receivables account in FI.

You will have to remember that these are not a required sequence. Some times, you may configure your system to create a SD invoice as soon as you create a sales order or you may not create a shipping document at all. This is the position where Functional Consultant would come into picture and study the company’s order to cash process and configure the SAP system to do so.

Menu path: IMG->sales & distribution->Billing->billing plans->define billing plan types.

You set the start date and end dates if applicable to the type of billing you are using. What time to be billed (end of month, start of month etc..)

Milestone is a billing plan type where a customer is billed for the amount distributed between the dates until total value is reached eg: if the total billing amount is 1000 USD for a year. You will bill the customer in different amounts say 200, 500, 300 at different intervals as per customer agreement.

On the other hand Periodic billing is billing the customer for the total amount(here 1000 USD) at regular intervals periodically until the customer agreement is reached. eg: 1000/12 for a 1 year agreement and say billed at the 1st day of every month

Explanation for Billing Plan for Milestone Billing

Milestone billing means distributing the total amount to be billed over multiple billing dates in the billing plan. As each milestone is successfully reached, the customer is billed either a percentage of the entire project cost or simply a pre-defined amount. During sales order processing, the system determines from the item category whether a billing plan is required and, if so, which type of plan ,The type of billing plan that is determined at this point is set up in Customizing and cannot be changed in the sales document. Billing plans for periodic billing and milestone billing plans for project-related milestone billing have different overview screens so that you can enter data relevant to your processing.

Posting Keys are defined at Client Level. Posting keys determine whether a line item is a debit or credit as well as the possible field status for the transaction. In this context, it is essential to understand the factors that determine the field status of a transaction. The field status within a FI document is controlled by Accout Type, field status of Posting Key and the field status of the G/L account.

Modifying the SAP delivered Posting keys are not recommended. if a posting key is to be modified the best possible action is to copy the posting key that needs to be modified and then modify the copy. we can define the posting keys using the transaction OB41.

It also determines the account type to which the debit or credit is to be made and whether it is Spl G/L transaction. If it is a Spl G/L transaction, then the field for Spl G/L indicator becomes required entry.

In SAP Materials Management, goods movement is distinguished using a three digit key which is called the “movement type”. The movement type is important because it controls the screen layout, adjustment of inventories, the GL account for financial purposes etc. Goods movement have been discussed elaborately here. The various types of material movement types in SAP materials management MM are given below:

Movement Type and Goods Movement

• 101 Goods receiving for ordering
• 104 Goods receiving blocking status for ordering
• 122 Return delivery to suppliers
• 201 Goods outflow (WA) to cost centers
• 221 Goods outflow to project
• 231 Goods outflow to customer order
• 241 Goods outflow to factory
• 251 Goods outflow to sales
• 261 Goods outflow to order
• 291 Goods outflow for all account allocations
• 321 Release from quality checking
• 551 Goods outflow for scrap
• 321 Release from quality checking
• 451 Returns from customers
• 453 Inventory to inventory transfers
• 501 Goods receiving without order
• 511 No cost delivery
• 521 Internal goods receiving without manufacturing order
• 561 Inventory taking

VPRS is the internal price condition which is copies from material master and can not be manual procss.It is mainly used to calculate revenue sv from particular material. EK01 is for actual costing EK02 is for calculates costing for costing purpose.

We Can’t stop PGI (Post Goods Issue ), if u want to reversal u can use VL09 and then cancelled delivery to use transaction VLO2N.

BPR means the existing business process how you re-engineered to get client requirements. (Line items clearing at the time of customer receipts which is not exists in the legacy)

shipping point will be determined based on the shipping conditions, loading group and delivery plant.

we assign movement type in schedule line category. As is is related to transfer.

Blue print means collecting the business requirements and mapping these with in sap R/3 if propose is not met then some other solution how to map in SAP R/3 i.e AS IS – TO BE study so the out put will be under standing the requirements and providing the solution in sap with flow charts and get the acceptance from the business team before configure the system i.e realization stage

The further subdivision of a plant are the storage locations, which allows stocks of materials to be broken down according to predefined criteria such as the location and materials planning aspects. It can also be subdivided into locations and operational areas. They are further subdivided into locations takes geographical criteria into account, operational areas reflects responsibilities for production is also a subdivision.

The highest organizational units in SD, MM, PP, FI/CO are:

• SD: Sales Organization.
• MM: Plant.
• PP: Plant.
• FI: Company Code
• CO: Controlling Area.

It is possible for a sales organization sell from a plant belonging to a different company code

The Distribution Channels and Divisions are assigned to Sales Organization. A plant can be assigned with many shipping points, coming to sales organization there will be shipping points that are assigned to that. When a ware house management system is active it would be assigned with a Plant and Storage Location in a ware house number.

Yes, it is possible to assign two different sales organizations to the same company code

Organizational unit at a fixed location that carries out shipping activities is called Shipping Point. A shipping point could, for instance it can be a company’s mail department or a plant’s rail depot. Each delivery is processed by only one shipping point.

When immediate delivery in cash sales is made the Order type delivery switch on immediately.

Yes, it is possible to create sales order for 40 items if the quotation is sent for 30 items.

It has to be set an item category as “automatic PO” so that PO and PR will automatically generate after saving the order.

Product groups can be defined for a wide-ranging spectrum of products. For every division you can make customer-specific agreements on, for example, partial deliveries, pricing and terms of payment. Within a division you can carry out statistical analyses or set up separate marketing is known as Division.

In access sequence, the system will not go to access condition type system will reply through formula.

More than one credit control areas is not possible to assign to a company code, since a credit control area can include one or more company codes. Credit control area is an organizational unit in an organization that specifies and checks credit limits for customers.

The steps that are included for the sales person as a partner function in the partner determination, that a partner function sales representative or person responsible for these two we can add through partner function in partner procedure

The Central Organizational element in purchasing is Purchasing Organization and the relationship between sales organizations and plants is Many to Many, to Company codes its Many to One and for Plants and Company codes its Many to Many to One.

CO is the sub module of SAP that could make business area obsolete and it is possible that one business area can be assigned to several company codes. Z transaction is a copied standard transaction code or objects that rename it by Z which is basically standard name which will stat from Z as user defined.

The costs and revenue according to the business area posted by the system is called as Business Area. It is used in Sales Area if the accounts are to be posted according to sales and Plant Division if the accounts are to be posted according to products. The business area is defined in Customizing for Sales. A unit in an enterprise, grouping product and market combinations as homogeneously as possible for the purpose of developing unified business policy. Business Area according to Financial Accounting (FI) defines that the business area is an organizational unit within financial accounting which represents a separate area of operations or responsibilities within an organization. Financial accounting transactions can be allocated to a specific business area.

Basic grouping of all individual deliveries for Billing is called Delivery Group. It should have the same Ship to Party, Shipping Point, etc.

The Geographical aspects of the organization in business development and sales are defined using the term sales office. A sales office can be considered as a subsidiary. Sales offices are assigned to sales areas. If a sales order is entered for a sales office within a certain sales area, the sales office must be assigned to that area. The staff of a sales office may be subdivided into sales groups. For example, sales groups can be defined for individual divisions. Individual personnel master records are used to manage data about salespersons. A sales person can be assigned to a sales group in the personnel master record.

Cumulative Condition Record is a field that Condition Update during configuration for a condition type that has anything to do with the cumulative condition records.

The Enterprise organization chart shows the organizational structure of an enterprise, its organization units and how they are related. A combined structure can be created from the point of view of accounting, MM, SD. This structure forms a framework in which all business transactions can be processed.

The views in a material master are Basic data, Additional basic data, Accounting views, MRP views, Purchasing views, Storage views, forecasting views, sales views and in IS Retail there is also a Listing view and POS view.

Sales organization is an organizational unit that sells, distributes products, negotiates terms of sales and is responsible for all the transactions involved with a sale.

Migrating from the existing system on which currently working to the SAP system is called the legacy system. Cutover strategy that depends upon how the organizations design their data load strategies. Normally, it decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then it make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies. Cutover planning is highly site specific. There’s no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.

The transaction code for creating a material in SAP is MM41. MM01 is the transaction code to extend a material.

The base unit is a measure which is used as a basis for all the transactions, all movements of quantities will be converted to that base unit of measure which is specific to an article

When a value is not entered for a manual and mandatory condition type the pricing procedure will reject the conditions in the sales order. There would be no header condition type to have an access sequence.

The examples of Global Settings are Currencies, Countries etc and this data is application independent

A general customer that is created for those customers for which it do not want to create separate records is called a one time customer. This customer can be reused.

According to customer master record a Payer is the individual or company who will settle the invoices for products or services sold.

Normally account groups are defined by the finance team and some of the tables in SAP SD for customer master are KNVV, RF02D, KNA1 etc.

The procedure to know the customer is one-time or regular since one can maintain Account Group for One-time customers

Yes, it is possible to have specific customer material information entered in SAP since VD51 is the transaction or inside VA02 also you can add customer material information records.

The transaction codes for creating a customer in SAP SD are VD01, VA01 and XD01

This customer represents the sales customers within the same client but between different company codes.

When the exclusive field of all access sequences is ticked, it will try to get available data from the first. Only in case, data is not available, will it move on to the next one.

According to SAP SD, a sales office is a geographically located unit of a sales organization.

Partner determination is used to find out who is responsible for A/R process and where the products are going.

• Master data
• Basic functions
• Sales(foreign sales and sales support)
• Shipping and transportation
• Billing
• Sales support
• Information systems are the important components of SAP’s SD module

The topmost organizational unit in SD module is called the sales organization. All the transactions relating to selling and distribution of products or services are represented by the sales organization unit. One sales organization can be associated with more than one distribution channel. It is represented by a 4 character code in SAP and is assigned to more than one plant. These plants are in turn assigned to company code. So obviously n number of sales area can be brought under a single company code.

After a product or service is sold, it takes various channels before it reaches the intented audience (customers). A distribution channel depicts such channels(eg. Retail, wholesale, direct sale etc).In sap it is identified by a 2 char code. It is assigned to more than one sales areas.

A distribution chain is the possible combination of sales organization and distribution channels.

Sales order is a contract between Sales organization and a customer, for supply of specified goods and/services over a specified time frame and in agreed quantity or unit. A sales order contains,

• Organizational Data
• Header data
• Item data
• Schedule line data

• SO-Rush order
• G2-Credit
• RE-Return order
• KN-FoC(Free of charge) subsequent delivery order.
• RK-invoice correction request.

There can be business scenario where we allow our stock to be stored at the customer’s site. Or even if the stock or material is stored in our place, a particular amount is reserved for the customer. He may sell or redistribute this stock allocated for him at his wish. We bill him only the amount he has consumed. This business process is called ‘consignment stock process.

The special stock(consignment) in our system both customer wise and material wise. The standard sales order document type used is KB and delivery type is LF.

The message is not configurable; at least in releases <= 4.6. But you can change the ‘W’ to an ‘E’ with a modification.

Plant to plant is handled using MB1B. If stock transfer orders with deliveries are configured, use ME27.

You must make sure you do not allow negative inventory in MM.

You can change this by checking order header configuration (VOV8), and field quotation message

Follow these steps:

1. New routine in VOFM->Formulas-> Condition value. There you divide quantity by 100, and multiply the integer part of result by 3.
2. New condition-calculate type-G-formula.
3. Input condition in your pricing procedure and input AltCTy (Condition formula for alternative calculation type) – new formula.

The VPRS is a valuation condition, normally the cost of goods sold. If it comes from the material master record, it is a standard valuation price. However, if it comes from the information record, it is the very cost of goods sold. You may have a difference from the price you valued your material at and the real cost of purchase. Check if you have a standard value in your master record or if you have a relevant info record. Another possibility is your customized condition is undoing the VPRS.

Take a look at function modules with SERIAL_*. For example, SERIAL_LS_PRINT.

Follow pathway:

SPRO ->Sales and Distribution ->Basic Functions ->Pricing ->Pricing Control -> Define and Assign Pricing Procedures

From here select “Maintain pricing procedures.” Next, select procedure ZCS928, then “Control Data.” Add Z928 to your procedure.

Yes. Using the MASS transaction, select object KNA1. Then select table name KNVP.

Serial numbers are entered on the delivery document and not a sale order, as this allows for multiple serial numbers to be entered for a single line. For example, you may have 10 serial numbers for a quantity of 10.

You can find out how to configure this by taking a look at the documentation for $SET_PRICING _FACTOR,” in LO-VC.

This can be solved through SE43 itself. Create a new menu area then the name of that area menu is automatically assigned to the main node.

You can create a VOFM subroutine (transaction code VOFM-Formulas ->Condition value) and set this subroutine in your procedure as transaction code V/2 in field AltCTy (Condition formula for alternative calculation type). In the ABAP coding you can describe all of your requirements.

Use the user exit “userexit_move_field_to_vbkd” in report MV45AFZZ with this coding:

DATA: via LIKE knb1-zwels.
IF vbkd-zlsch IS INITIAL.
IF NOT vbak-kunnr IS INITIAL.
SELECT SINGLE zwels INTO via
FROM knb1
WHERE bukrs = vbak-bukrs_vf
AND kunnr = vbak-kunnr.
vbkd-zlsch = via(1).
ENDIF.
ENDIF.

Check whether the transmission medium has been maintained for the processing routines for your output type. Make sure that this transmission medium is placed in the partner functions evenly.
Follow this path:

SPRO -> SD-> Basic Functions-> output control–>output determination->determination using condition technique->maintain O.deter.for sales documents-> Maintain output types. Use transaction code V30.

You must fill the update structures properly. The order header needs to read “order_header _ inxupdateflag = ‘U’,”. The item must read “order_item_inx = ‘U’.” Each field touched in “order_item_ in” needs to have an ‘X’ in the corresponding field of “order_item_inx.”

You can control the updating of infostructure at both header level and tem level using IMG. If you do not want the second company code data to be updated in the info structure, do not include the sales organizations assigned to the second company code in the updating of info structure. For your information, the codes are OVRO and OVRP

In VOFA check the SD Document category. It should be set to U and the transaction group should be set to 8. Likely these were changed to real invoices. The transaction group tells pro forma invoices not to be posted to accounts. If you have a posting block, wait until someone releases it to accounting in change mode.

In the transaction VOV8 (sales document type definition) under general control put an “A” in the check PO number field. In the transaction OVAH (change system messages) change the message category of V4 -115 to “E” from “W”.

Follow these steps:

1. OMJ1-Allow negative stocks-at plant level and at storage location level.
2. MM02-Plant data/stor.2-check negative stock in plant.

You can view these in transaction code SE91.

This information is located in table VBPA.

The pricing procedure applies to the whole document(header and items). You cannot change it at material (item) level.

Use transaction code VKOA

Create an order and delivery, and then perform a PGI for first customer hierarchy. Do the same for the second customer hierarchy.

The pricing procedure is determined according to: sales area, customer pricing procedure field in the customer master (sold-to), document pricing procedure field in the sales document type. You may need to identify the criteria to determine the right pricing procedure when you enter a sales order. The transaction code to define pricing procedure determination is OVKK. Normally taxes are included in the actual pricing procedure, as part of the determination of the actual price (including taxes) the customer will pay. Taxes need to be calculated based on the given prices in the pricing procedure.

Use transaction code VK11 and enter condition type MWST. Next, enter the details in that document.

A sales usage means that production will not see it, and a production usage means that sales will not see it. The components each may or may not be saleable, but as a sales BOM is intended to explode onto a sales order, a non-saleable item on a sales BOM would generally not be recommended.

The usage is precisely what it sounds like; which function will use the particular BOM.

Use text control function, SD-> basic function-> text control.

You can postpone the invoice date in the sales order that belongs to that particular delivery under the billing tab. Otherwise by default, the invoice will pick up the GI date of the delivery. If it is acceptable to put the GI on hold until the day of invoicing you could also suggest this as a procedure.

You must create the GL account for the company code, exactly like you create a customer master for a CC, or a material in a plant.

You will have to take a look at copy control (from Sales document to Billing document), on item level. Most likely the routine will show 001. If you change that routine to 003, then you should get an invoice per sales order.

Use transaction code NACE. Define the output type here. In application V3, define the correct transmission medium. If you want to send it at your convenience select the dispatch time as 3 (Send with applications own transaction). Attach the output type to the correct output determination procedure defined for the document type. Use T Code VF31 to send the message. You will need basis while configuring the email addresses because SCOT and SOST will be used by it.

You cannot manipulate and make changes afterwards expecting the system to honor your requirements. You must add the child items as a separate order.

The first thing you should do is check the account determination log in the invoice.

Follow these steps: transaction code VF02-> Environment-> Acc.determ.analysis-> Revenue Accounts.

The problem is with the number range buffering. Go to transaction code SNUM, and then object type “debitor.” Click on the pencil (change mode) and change the number in buffer.

Material master leads to classification, and then you select the desired class. Based on class you can choose the characteristics. These characteristics are defined in CT04.

Follow pathway : SAP Library-> SAP R/3 Enterprise Application Components-> Logistics-> Sales and Distribution (SD) -> Sales-> Special Business Processes in Sales-> Consignment Stock Processing.

Excise tax is the duty charged on manufacture of goods listed in the chapter and section head of Central Excise Tariff Act. Process should amount to manufacture and separate identifiable finished goods should emerge having marketability and specified in Tariff Act.

As far as SAP is concerned you, find CIN version integrated with standard SAP. There are two places where you need to configure CIN. The first is Financial Accounting-> Tax on Sale and Purchase and the other is Logistic General-> Tax on Goods Movement.

After rigorous testing in the QA environment and approval of the user community you should transport the info structure and related items into a production environment during “down time,” possibly when no billing documents are being created and posted.

There are two ways to approach this. You can go to transaction code SE93 and give the Transaction as VA01. It will lead to a screen where you can click on a program that will take you to mod.pool. In this program click Find Icon and key in customer there. It will show you the user exits in that particular program. Another way is using SPRO.

Follow path : IMG->SD->System Modifications->User Exits. There you can click on the help document and it will show all the user exits with program name. Select the suitable one.

First cancel your invoices (SD and MM). Change the price in the STO PO. Then create new invoices SD and MM. The new values will be picked up if properly configured. The difference in the material value will be automatically posted to the appropriate stock account when you create the invoice in MIRO.

The document may already exist. Once fixed you cannot “unfix” the configuration by changing the customizing. You must create a new quote/order. Use setting “A.”

The destination country will decide which language the output should be printed. Make sure that you are identifying that in the program attached to the output and accordingly open the desired form.

You can copy text from Delivery Note to invoice. Go to the IMG (SD>Basic Functions>Text Control) and click on the help icons next to text types. Define access sequences for determining texts and define and assign text determination procedures. You need to check the delivery text field in the relevant billing document type. If you do not check this field you will not be able to copy the delivery texts to the billing document.

Use transaction code MM01 to create material with organizational data pertaining to the plants and sales organizations.

Make sure you have a tax category defined for your countries in OVK1. Then check if the tax classes are defined in OVK3 and OVK4.

New shipping points are defined in enterprise structure.

Follow these steps: logistics execution -> define shipping points and assign the shipping point to plant in assign in enterprise structure under logistics execution. Next, click: shipping -> shipping point and good receipt determination. Configure for automatic determination of shipping point based on shipping condition, loading group, and plant. Maintain relevant shipping condition in customer master. Maintain relevant loading group in material master (normally the standard). For the combination that you derive from the sales order, you should have a configuration entry for automatic determination in sales order.

In FS01/02/03 you will see that there is a tax category field where you enter the used tax code for this account. Normally tax conditions have specific account keys. Through transaction code VKOA or OV35 you assign which account (using key fields from sales) will be used for the account doc. Check V08 price procedure for the used account key as well.

No, but you will have a credit note in your customer account.

Generate the infostructure and update group again in the client in which you are facing the problem.

If you go into the change mode of the sales order click on environment, and then change. This menu will show you that partner functions like SH / BP / PY in the document are changed. It also shows old and new values.

The delivery creation date is blank because the STO is blocked by release strategy.

The ideal way is to check the credit limit of the customer much before the processing the sales order. Follow the path mentioned within the sales order. Also check: Sales Order-> Environment-> Partners-> Display Credit Account.

Use transaction code VF02. Once inside the document, click on Go to-> Header ->Output. Select the output type (normally RD00). Click on Communication method and in the field “Number of messages”, enter the number of copies you want to print.

The confirmed quantity is the allocated quantity by the availability check (ATP).

Subtotals are not tied to condition types per say.You control what goes into the field by assigning subtotals within you pricing procedure. If you assign a particular line in your pricing procedure to be subtotal 5, its value will be moved to KOMP-KZWI5.

Make the modification to include a check within the copying requirements of the division in the source document instead of the user authorization.

Use transaction code MB1C and movement type 561.

VK31 works with pricing reports. If you want to have a new condition type to be maintainable via VK31 or VK32., you need to do the following: Create pricing report via transaction code V/LA and include the tables you need. Extend the price area menu via SE43. Area menu = COND_AV.

You assign movement type against the schedule line category.

You should be able to see the due date in the AR Module. If you go into fbl5n and search for the customer, you can see the due date in the overview screen.

Click the reject document button and then enter a reason for rejection. This will reject the line items and the sales order. You can enter a reason for rejection on the line item sales a tab.

There is an unapplied SAP Note that will correct the error. Once the correct note is applied the save option will not be grayed-out.

One way is through the configuration of document type in transaction code VOV8 (O Another way is in the “Transaction Flow” section. You can also perform “Alt sales doc type 1” and “Alt sales doc type 2.”

You can use the user master data to achieve this. Use transaction code SU01 and input the user ID. Go to the parameters tab page and add parameter VTW. Input your default distribution channel in the parameter value. The only drawback with this method is you will have to individually do this for all your users.

The procedure is assigned in transaction OVHU2. You will have to assign the procedure to 0002 Outbound Delivery. Here you cannot specify the delivery type or item category. To some extent, you can control this with the packing indicator in the delivery item category, however, you can have better control by designing the access sequence with the available fields.

You can make a storage location not available to the availability check in MM.

Use transaction VOTXN, and then create an access sequence with text object VBBK. Also make sure that the requirement of access sequence is given as ‘1’-Ref doc. Header.

Regarding fix date and quantity check box check transaction OVZJ for your sales area. With the second problem regarding MD04, you must check two things; requirements class and scheduling category. Check your document to see whether they are activated for requirement transfer.

For this requirement check TC: S_ALR_87012179 & S_ALR_87012180

If you have SIS update turned on, you can use transaction code MTCE against infostructure 001 to display sales by sales ganization and so forth. Apart from SIS, you may create simple ABAP query with LDB VAV. If you want to create an ABAP report only, then use transaction code VBRK ->billing header table and VBRP -billing item table.

i.Dynamic Menu
ii.Command Field

The material type determines a material’s procurement type. It also controls

• screen sequence
• field
• selection
• number assignment type in material master maintenance
• inventory management type
• account determination

Yes. Print out, Mail, EDI, Fax.

Order Confirmation, Delivery Note , Invoice.

Yes.

Account Group, Item Category.

i. Stocks
ii. Safety stock, stock in transfer, stock in quality inspection, blocked stock.
iii. Inward and outward movements
iv. purchase orders, purchase requisitions, planned orders, production orders, reservations, dependent reservations, dependent requirements, sales requirements, delivery requirements.

The partner type is an indicator which informs you of the type of partner, for example, partner type customer “KU”.

i. The document number
ii. The partner functions allowed at header level
iii. The partner functions allowed at item level
iv. The billing type that can be used to cancel the billing document
v. The transfer status of the billing document:
vi. Transferred to financial accounting
vii. blocked from transfer
viii. not transferred
ix. The procedure for account assignment in Financial Accounting
x. The allowed output for a business transaction and the procedure for output.

No.

Relevance for Picking, Determination of Picking Location, Minimum Delivery Quantity.

Sales Document Type, Item Category, Schedule Line Category, Partner Functions, Sales Activities.

Yes.

Sales document type + Higher level Item category + Item category group + Item Usage.

Relevance for delivery, Availability check, Transfer of Requirements, Goods Movement, Purchasing and Incompletion log.

Pricing, Relevance for delivery, Relevance for billing, Incompletion log, Partner, Tax.

Pricing, Taxes , Delivery.

For business transactions.

Returns can only be created referencing sales order.

Text, Partner, Pricing, Taxes, Output, Delivery.

Account Group, Transactions.

Number assignment, Screen Layout.

Yes.

Internal & External.

i. The Reference Model integrated into the R/3 System.
ii. The various ways into Business Navigator (the views) help you call just the models and list displays you need in the R/3 Reference Model.
iii. You can access other R/3 System components directly from the models.
iv. for example: data models, transactions, documentation.

i. The R/3 Procedure Model is both the methodological framework for the implementation and upgrade processes and a powerful tool that supports you at every stage of the implementation process.
ii. The R/3 Procedure Model provides
iii. all the fundamental understanding you need at the cross-application level for implementing R/3 application components successfully,
iv. a hierarchically-structured plan of the activities,
v. a correct sequence of the activities
vi. the link to the system setting activities

i. The R/3 Procedure Model is both the methodological framework for the implementation and upgrade processes and a powerful tool that supports you at every stage of the implementation process.
ii. The R/3 Procedure Model provides.
iii. all the fundamental understanding you need at the cross-application level for implementing R/3 application components successfully.
iv. a hierarchically-structured plan of the activities.
v. a correct sequence of the activities.
vi. the link to the system setting activities.

Yes.

No.

Yes.

Tool for configuring the SAP System to meet customer requirements. Also referred to as the ‘Implementation Guide’.

Yes.

Periodic billing, Milestone billing.

i. Alphanumeric character string for grouping materials by combining various characteristics. The product hierarchy is used for evaluation and pricing purposes.
ii. In Product Cost Controlling (CO-PC) : Structure consisting of the plant, product group, product, and order. Used for the interactive analysis of the product costs for each level of the hierarchy.

A rebate is a special discount which is paid retroactively to a customer. This discount is based on the customer’s sales volume over a specified time period.

Credit check, Tax calculation, Cost estimate.

i. sales area (if the accounts are to be posted according to sales).
ii. plant/division (if the accounts are to be posted according to products).

Yes.

Yes . If the data from the related reference documents differs in the header fields of the billing document. The system will automatically split the invoice.

Yes.

Yes. If the header data and header partners for specified delivery or sales order are identical and if requirements for splitting do not apply.

Billing Schedule.

Only sales order.

Based on sales order or delivery.

Yes.

No. You can cancel it and create cancellation document.

Yes.

In Pricing Procedure.

Yes.

Yes. Field specific.

Customer, Sales Document Type and Sales Area.

Validity Period to be specified in condition record.

Condition which can be used to determine a scale value based on more than one item in a document. The system groups the items using either the condition key for the appropriate condition record or a separately defined condition key.

Yes. Maximum Value, Maximum Orders, Maximum Quantity.