Showing posts with label Sap Online Tutorials. Show all posts
Showing posts with label Sap Online Tutorials. Show all posts

Tuesday, 15 December 2015

SAP SD Online Training Tutorials

Free SAP SD (Sales and Distribution) Training Tutorials

SAP SD ( Sales and Distribution ) Training tutorials by the real time functional consultant and experts . The SAP SD module handles all the processes starting from an Order to delivery. The main operations of this SAP SD module handle Customer Sales Orders processing, pricing, Picking, packing, Shipping, billing and risk management etc.


Sales and Distribution (SD) is one of the core and most-used modules of SAP R/3 products beside Financial (FI), Controlling (CO), Material Management (MM), and Production Planning (PP) modules. The Sales & Distribution (SD) module consists of various components also called sub-modules. Which are follow as below,

(SD-BF) Basic Functions and Master Data in SD Processing. (Also subdivided in several components as: Pricing, Output…etc)
(SD-BF-PR) Pricing and Conditions
(SD-BF-EC) Extra Charge
(SD-BF-CM) Availability Check and Requirements in Sales and Distribution Credit and Risk Management
(SD-BF-AS) Material Sorting
(SD-BF-OC) Output Determination
(SD-SLS) Sales
(SD-SLS-OA) Scheduling Agreements for Component Supplierssap sd training tutorials
(SD-SLS-OA) Customer Service Processing
(SD-FT) Foreign Trade/Customs
(SD-BIL) Billing
(SD-BIL-IV) Payment Card Processing
(CAS) Sales Support: Computer-Aided Selling
(SD-EDI) Electronic Data Interchange/IDoc Interface
(LE-SHP) Shipping
(LE-TRA) Transportation
(SD-IS-REP) Reports and Analyses

SAP SD (Sales and Distribution) module and with the sub module are
  • Pre-sales activities, including Inquiry and Quotation creation.
  • Sales Order processing, including Sales Order (SO)
  • Shipping, including Outbound Delivery document creation.
  • Billing, including Billing document and invoice creation.

Sales and Distribution (SD) is a module highly integrated with other SAP Modules as FI, CO, MM, PP & more. This can make SAP SD complex module, so as part of this Introduction we will also try to detail a normal sales process and how the activities integrate and are covered by this module.

Pre-sales activities: It starts when a customer or a prospect requests information by any source about a product or service offered by the company. This request is processed through SAP and the first integration we have is by the creation of an Inquiry Document or a Quotation Document. At this point of the process we still haven’t effectively made a sale that’s why it is considered as a presale activity.

Sales Order processing: Our quotation document previously created is send to our customer so they can make effective their purchase procedure. At this point they may want to negotiate payment terms, price, dates or any adjustments to the original document created by us.

As soon as we receive a Purchase Order (PO) from our Customer we create a Sales Order (SO) which makes reference to the previously created Quotation Document. Now scenario  is adjusted based on the business requirements. In some cases depending on the business Sales Orders (SO) can be made without a previously created quotation document as also in other scenario this can be a requirement.

Inventory Sourcing: The product requirement from the Sales Order at the required date needs to be available by one of the following options:

To fulfill the products requirement from an SO at the required date, we can obtain them by one of these options:
  • Taking from Available stock at warehouse. At this point the SD module may trigger stock transfers between warehouses.
  • Triggering a production order to produce the products in-house.
  • Triggering a purchasing order to purchase the products from vendor.
Here is where the integration between Production Planning (PP) and Material Management (MM) starts.

Shipping: When the product we sold is available at the warehouse, the sales personnel can start shipping activities by creating an outbound delivery document (Delivery Order/DO). Now this Deliver Order (DO) can be created by referring to our original Sales Order (SO). This will trigger the preparation of the product by the personnel of the warehouse. If the Warehouse Management (WM) module is integrated, a Deliver Order (DO) can trigger a Transfer Order. When the products are ready to be sent, the warehouse personnel will post the Goods Issue (GI) transaction that refers to the DO. The GI transaction will reduce the inventory level of products and then the warehouse personnel sends the products to the customer by transportation mode that has been determined in Sales Order (SO) document.

Billing: This whole process will be managed before the delivery date specified in the Sales Order (SO) document. The finance department will generate a billing document and send an invoice form to the customer. The invoice will request the customer to pay the products we have sent at the price condition and terms of payment we have agreed in SO document.

SAP Sales and Distribution consists of all business processes required in selling, shipping the goods, and final billing of the item. This SAP SD module is closely integrated with other SAP Modules.

Thursday, 10 December 2015

Material Ledger Closing in SAP Quick review

Movements for a material that is valuated with the material ledger are always carried out using the valuation price. If the price control indicator in the material master record is S, movements for the material are carried out with the standard price. If the price control indicator in the material master record is V, movements for the material are carried out with the periodic unit price.

When postings such as invoice receipts occur, the prices can differ from the valuation price. These differences are collected and totaled by the material ledger and taken into account during material ledger closing.

The Before Material Ledger Closing: The differences between the valuation price that occur when postings are made are collected the following categories:

GR/IR (goods receipt/invoice receipt): Differences between actual values and the valuation price that may occur due to invoice receipts are collected here. Differences can occur between a goods receipt and an invoice receipt, because the invoice price is unknown at the time of goods receipt. The values from invoice receipts are posted to a GR/IR clearing account and the offsetting entry is made in the vendor account.

Value Variances: Differences between actual values and the valuation price that can occur due the to the following are collected as,

1. The Goods receipts for the production order
2. Transfer postings
3. Goods issues
4. The Initial entries of inventory data with a specified amount
5. Deliveries free of charge
6. Inward movements from consignment inventory to the company’s own stock
7. Purchase order-related goods receipts

Values from goods receipts are posted to a GR/IR clearing account; the offsetting entry takes place in the material inventory account. If the the order price differs from the valuation price in the goods receipt, the system posts an offsetting entry to the material stock account and the price difference account (transaction key PRD). Such differences are totaled in the material ledger and indicated as to be closed. With goods receipts that are not based on a purchase order item, price difference are posted directly to the price difference accounts.

Posting to a Prior Period: Variances are collected here when a posting is made to the previous period using a valuation price other than the one in the current period.

At Material Ledger Closing: At material ledger closing, the system takes the differences arising in the above categories into account, depending on the price control of the material. If you carry out material ledger closing for a single material (without saving), you can display which postings the material ledger would make and with what amounts if you were to save the material ledger closing at this time

Materials with S price control (standard price): The system calculates for each material, the balance on the GR/IR clearing account and posts this amount to a price difference account (transaction key PRY). Differences that were collected in the Value variances category were posted to various price difference accounts before material ledger closing. These postings are not changed.

Differences that were collected in the Posting to a prior period category were posted to the revaluation account before material ledger closing. These postings are not changed. The new periodic unit price is calculated for statistical information.

Materials with V price control (periodic unit price): The system calculates the balance on the GR/IR clearing account and posts this amount to the material stock account in proportion to the current inventory quantity. The portion of the balances with which the material inventory cannot be debited are posted to a price difference account (transaction key PRY). Differences that were collected in the Value variances category were posted to various price difference accounts before material ledger closing. These postings are offset in total against a separate price difference account at material ledger closing (transaction key PRY).

The system calculates the balance and posts this amount to the material stock account in proportion to the current inventory quantity. The portion of the balances with which the material inventory cannot be debited are posted to a price difference account (transaction key PRY)

Differences that were collected in the Posting to a prior period category were posted to the revaluation account before material ledger closing. The system calculates the balance on this account and posts this amount to the material stock account in proportion to the current inventory quantity.

The portion of the balances with which the material inventory cannot be debited are posted to a price difference account (transaction key PRY). The postings to the material stock account result in a new periodic unit price for the material, found by dividing the inventory value by the inventory quantity.

Monday, 7 December 2015

SAP HR Table list

SAP Training Tutorials gives the to know ore on the SAP HR tables which frequently using SAP HR Module.The list of SAP Human Resources tables as below,


www.technosap.com
DD01L Domains
DD02L SAP tables
DD06L Pool/cluster structures
DD20L Matchcode Ids
DD03L Table Fields
DD03T DD: Texts for fields (language dependent)
DD04L Data elements
DD04T R/3 DD: Data element texts
DD05S Foreign key fields

DD24S Fields of a matchcode ID
T000 Clients
T001 Company Codes
T001E Company code-dependent address data
T001P Personnel Areas/Subareas
T012 House banks
T012K House bank accounts
T012T House bank account names
T504C Benefit Type (NA)
T500L Personnel Country Grouping
T500P Personnel Areas
T502T Marital Status Designators
T500T Personnel Country Groupings
T501 Employee Group
T501T Employee Group Names
T503 Employee Groups / Subgroups
T503K Employee subgroup
T503T Employee Subgroup Names
T504A Benefits – Default Values (NA)
T504B Benefit Option Texts (North America)
T504D Benefit Credit Group Amount
T504E Benefit Amount
T504F Benefit Costs
T508A Work Schedule Rules
T508T Texts for Employee Subgroup Groupings for Work Schedules
T510 Pay Scale Groups
T510A Pay Scale Types
T510F Assign Pay Scale > Time Unit, Currency
T510G Pay Scale Areas
T510H Payroll Constants with Regard to Time Unit
T510I Standard Working Hours
T512R Cumulation Wage Types in Forms
T512S Texts for Cumulation Wage Types in Forms
T510J Constant Valuations
T510L Levels
T510M Valuation of pay scale groups acc. to hiring date
T510N Pay Scales for Annual Salaries (NA)
T510S Time Wage Type Selection Rule
T510U Pay Scale Groups
T510Y Special Rules for Wage Type Generation
T511 Wage Types
T512T Wage Type Texts
T512W Wage Type Valuation
T512Z Permissibility of Wage Types per Infotype
T513 Jobs
T514S Table Name Texts
T514T Field Name Texts
T51D2 Wage Type Classes
T52C0 Payroll Schemas
T52C1 Payroll Schemas
T52C2 Texts for Personnel Calculation Schemas
T52C3 Texts for Personnel Calculation Schemas
T52C5 Personnel Calculation Rules

T52CC Schema Directory
T51D3 Reduction Rules
T51D4 Cumulation Rules
T527X Organizational Units
T528B Positions – Work Centers
T528C Wage Type Catalog
T528T Position Texts
T529A Personnel Event
T529F Fast Data Entry for Events
T529T Personnel Event Texts
T52BT Texts For HR Objects
T52CD Schema Directory
T52CE Directory of Personnel Calculation Rules
T52CT Text Elements
T52CX Cross References via Generated Schemas
T52D1 Valid Processing Classes
T52D2 Valid Values for Processing Classes
T52D3 Valid Evaluation Classes
T52D4 Permitted Values for Evaluation Classes
T52D5 Wage Type Groups
T52D6 Wage Type Group Texts
T52D7 Assign Wage Types to Wage Type Groups
T52D8 Valid Processing Classes – Texts
T52D9 Valid Values for Processing Classes – Texts
T530 Reasons for Events
T549M Monthly Assignment: Payroll Period
T549N Period Modifiers
T549O Text for date modifier
T549P Valid Time Units for Payroll Accounting
T549Q Payroll Periods
T549R Period Parameters
T549S Payroll date types
T530E Reasons for Changes
T530F Reasons for Changes
T530L Wage Types for Special Payments
T530T Event Reason Texts
T531 Deadline Types
T531S Deadline Type Texts
T533 Leave Types
T533T Leave Type Texts
T539A Default Wage Types for Basic Pay
T539J Base Wage Type Valuation

T539R Events for Standard Wage Maintenance
T539S Wage Types for Standard Wage Maintenance
T548 Date Types
T548S Date Conversion
T548T Date Types
T548Y Date Types
T549A Payroll Areas
T549B Company Features
T549C Decision Trees for Features (Customers)
T549D Feature Directory
T549L Date modifiers
T549T Payroll Areas
T549M Monthly Assignment: Payroll Period
T549N Period Modifiers
T549O Text for date modifier
T549P Valid Time Units for Payroll Accounting
T549Q Payroll Periods
T549R Period Parameters
T549S Payroll date types
T549T Payroll Areas
T554S Absence and Attendance Types
T554T Absence and Attendance Texts
T554V Defaults for Absence Types
T554Y Time Constraints in HR TIME
T555A Time Types
T555B Time Type Designations
T559A Working Weeks
T559B Name of Working Week
T572F Event Texts
T572G Allowed Values for Events
T572H Event Value Texts
T582A Infotypes
T582B Infotypes Which Are Created Automatically
T582S Infotype Texts
T582V Assignment of Infotypes to Views
T582W Assigns Infotype View to Primary Infotype
T582Z Control Table for PA Time Management
T584A Checking Procedures – Infotype Assignment
T588A Transaction Codes
T588B Infotype Menus
T588C Infotype Menus/Info Groups
T588D Infogroups for Events
T588J Screen Header Definition
T588M Infotype Screen Control
T588N Screen Modification for Account Assignment Block
T588O Screen Modification for Assignment Data
T588Q Screen types for fast entry
T588R Selection Reports for Fast Data Entry
T588S Screen Types for Fast Entry
T588T Menu and Infogroup Designations
T588V Business object type
T588W Event types for infotype operations
T588X Cust. composite definition of event types for IT operations
T588Z Dynamic Events
T591A Subtype Characteristics
T591B Time Constraints for Wage Types
T591S Subtype Texts
T596F HR Subroutines
T596G Cumulation wage types
T596H _Cumulation wage type texts
T596I Calculation rule for cumulation wage types
T596U Conversion Table
T599B Report Classes
T599C Report Classes
T599D Report Categories
T599F Report Classes – Select Options
T777A Building Addresses
T777T Infotypes
T777Z Infotype Time Constraints
T778T Infotypes
T778U Subtypes

Error Messages tables
T100 Messages
T100A Message IDs for T100
T100C Control of messages by the user
T100O Assignment of message to object
T100S Configurable system messages
T100T Table T100A text
T100V Assignment of messages to tables/views
T100W Assign Messages to Workflow
T100X Error Messages: Supplements

More Details: SAP Support Portal, SAP Solution Manager, SAP Training Tutorials, SAP Online Training Tutorials.

Friday, 4 December 2015

What is Purchase order in SAP? | SAP online training

This post provides general information about purchase order and how they are processed with Material Management (MM) Purchasing. The purchase order defines a formal request or instruction from purchasing organization to vendor or a plant to supply certain quantity of goods or services by certain point in time.

What is a purchase order?

The purchase order represents the formal and final approval of a purchasing transaction with the vendor. It identifies the below
  • The vendor
  • The material or service to be ordered
  • The quantity
  • The price
  • The delivery date and terms of delivery
  • The terms of payment
In addition, the purchase order determines whether the ordered material is placed in stock or consumed directly upon goods receipt. Purchase orders can be subject to a release procedure.

Structure of a purchase order

As in the case of other purchasing documents, the PO consist of:

1. Header, It containing information specific to the entire PO. For example, the terms of payment and the delivery terms are in the header.

2. Tems, It containing information specific to the material or service.
For example:
  • Material number or short description (“short text”)
  • Quantity
  • Price
For each item, you can enter additional information such as time-spot schedule lines and item-specific texts. The PO history menu enables you to monitor deliveries and invoices received with regard to the item.

Item category

The item category defines whether a purchase order item:
  • Requires a material number
  • Requires an account assignment
  • Will be placed in stock
  • Requires a goods receipt (GR) and/or an invoice receipt (IR)
The following are the item categories defined in the standard system:

Standard items categories in POs

Standard, It provides for normal goods and invoice receipt

Consignment
  • Material number required- no account assignments
  • Kept in stock
  • GR necessary
  • IR not necessary
Subcontracting
  • GR allowed
  • IR necessary
Stock transfer
  • Material number required
  • GR necessary
  • No IR
Third-party
  • Account assignment required
  • GR and IR allowed
Standard
 
Items with the item category “Standard” are orders for goods that are to be procured externally. In this case, goods and invoice receipt are possible.

Consignment
 
Items with the item category “Consignment” are items relating to goods procured on a consignment basis. Account assignments cannot be made for material ordered on consignment. Consignment stocks are managed separately and are not valuated.

Subcontracting

Order items with the item category Subcontracting are used to order finished assemblies from a subcontractor, for example. Any components the subcontractor requires to assemble the final product are entered as “material to be provided.”

Stock transport order (inter-plant stock transfer order)


The stock transport order is a mechanism facilitating the transfer of stock from one plant to another (that is, a transfer involving transport over a longer distance). The stock transport order is one of the special order types in Purchasing.

Third-party order

Part of a triangular business deal. A third-party order is an order placed with a vendor instructing the latter to supply goods to or perform a service for a third party (for example,
one of your customers). The third-party order is specified in the item category field of a requisition or purchase order. The third-party order is one of the special order types in Purchasing.

Item category and account assignment

The item category requires an account assignment for materials that are consumed directly (that is, materials that are not taken into stock). In the case of stock material, an account assignment is possible, but not mandatory.

PO texts

You can enter text in a purchase order directly or change texts that are suggested by the system. There are two kinds of text:
  • Header text – applies to the entire document
  • Item text – applies to an individual item
You define which texts appear in which order on printouts in Customizing. You can enter several header or item texts, which you can identify by your own codes

More Details: Sap fico training, Sap training in Chennai, Sap training in Bangalore, Sap online training.

Wednesday, 2 December 2015

ASAP Methodology Implementation Steps

The SAP ASAP Methodology (Accelerated SAP) provides the roadmap for optimizing and continuous implementation of SAP systems in the real time business processes. 

The ASAP roadmap brings in to multiple number of tools, information and accelerators to assist team members with the implementation of SAP R/3. The various phases of ASAP Methodology which consist below

Project Preparation

This phase to discuss the requirements of the project initial aspects.
  • Identification of team members
  • Developing a high level plan
  • Estimation of cost of the project
  • Duration of the project
Business Blue print Phase
  • To understand the business goals of the company.
  • To determine the business requirements needed to support the business goals.
  • Formulating the TO BE processes after thorough review of questionnaires sent to the key users/core users.
Realization Phase
  • Mainly to implement all the business and process requirements based on the business blue print.
  • The system is customized step by step in two work packages: Baseline and Final configuration.
  • The mapping done on how the system should get configured and tested

Final Preparation Phase
  • Main purpose is to complete testing, end user training, system management and cut over ativities.
  • Critical open issues should be resolved here.
  • Upon successful completion of this phase the business transactions are ready to run in the SAP system.
Go live and Support Phase
  • Transition from a project oriented, pre- productive environment to a successful and live productive operation.
  • Post implementation support.
  • System monitoring and fine-tuning.

The ASAP Methodology will cover the entire project life cycle right from the initial preparation and evaluation via delivery and till the end of post project management. The other side ASAP is concerned with the process and value of the application life cycle.

Friday, 20 November 2015

SAP Vendor Evaluation System

What is SAP Vendor Evaluation System and how Integrated?

The vendor Evaluation component has been completely integrated into SAP MM Purchasing. The information such as delivery dates, prices, and quantities can be taken from purchase orders. The SAP Vendor Evaluation uses the various data from Quality Management, and this will be shows the result of incoming inspections or other way the quality audits of the system. It also accesses basic data in Materials
Management, which as goods receipt data from Inventory Management, and data from the Logistics Information System (LIS).

What is Vendor Evaluation?

The Vendor Evaluation in sap System which supports you in the optimization of your procurement processes in the case of both materials and services.

Procurement of Materials

The system helps you select sources of supply and facilitates the continual monitoring of existing supply relationships. It provides you with accurate information on prices, and terms of payment and delivery. By evaluating vendors, you can improve your enterprise’s competitiveness. You can quickly determine
and resolve any procurement problems that may arise on the basis of detailed information and in collaboration with the relevant vendors

Procurement of Services

You can check the reliability of the vendors from which you procure services on a plant by plant basis. You can determine whether the vendors perform the services within the specified timeframes and appraise the quality of the work carried out.

Scores and Criteria

The SAP Standard System offers you a scoring range from 1 to 100 points, which is used to measure the performance of your vendors on the basis of five main criteria. You can determine and compare the performance of your vendors by reference to their overall scores. The main criteria available in the standard system are:

1), Price
2), Quality
3),Delivery
4), General service/support

These four main criteria serve as a basis for the evaluation of vendors from whom you procure materials.

1), External service

This main criterion serves as a basis for the evaluation of vendors you employ as external service providers.

You can also define other or further main criteria, as required. You can assign different weights to the individual criteria. The vendor’s overall score is computed taking into account the weighted scores awarded for each of the main criteria. The Vendor Evaluation System ensures that evaluation of vendors
is objective, since all vendors are assessed according to uniform criteria and the scores are computed automatically.

In this way, subjective impressions and judgments can be largely avoided. To create a detailed evaluation, each main criterion can be divided into several subcriteria. The standard system provides you with certain subcriteria which suffice as a basis for evaluation, but you can also define your own additional subcriteria.

The scores for the subcriteria are calculated in three different ways.

Automatic, The scores are calculated by the system on the basis of existing data.

Semi-automatic, You enter individual scores for important materials, or for the quality and timeliness of a service performed, yourself. The system then calculates the higherlevel score from these.

Manual,You enter a blanket score for a subcriterion per vendor and you can decide yourself which of these methods you want to use.

Analyses

The results of sap vendor evaluation are displayed in the form of analyses. For example, you can generate ranking lists of the best vendors according to overall score or ranking lists for
specific materials. Changes to evaluations are recorded in logs, and you have the option of printing out evaluation sheets.

More Details: Sap fico, Sap fico training, Sap training in Chennai, Sap training in Bangalore.

Thursday, 19 November 2015

SAP Tutorials

What is Master Conditions in SAP?

Master conditions in SAP are conditions that determine the effective price in the purchase order. They serve as a central repository of pricing for purchase orders. They are automatically included in the price calculation in the purchase order if the PO references a contract or an info record, or if it meets certain criteria defined in the extended conditions.

There are three types of master conditions in SAP,

Conditions in contracts – Conditions in a contract apply to all release orders issued against the contract.

Conditions in info records – Conditions in the info record apply to orders that specify the material and vendor contained in the info record.

Extended conditions – These are a flexible way of setting vendor pricing. Extended conditions are master conditions that are included in the price calculation in a purchase order only if the PO meets certain criteria. One way to use extended conditions would be to define a 10% discount on all orders placed with a specific vendor that are created by a certain purchasing organization. In this case, the vendor number and purchasing organization are the two criteria a PO must meet before the price in the PO can be calculated.

Extended conditions are more flexible than master conditions in info records or contracts because you can define which criteria they must meet before they are applied to a purchase order.
     
The documentation on outline agreements and purchasing info records shows how the conditions specified in outline agreements and purchasing info records, respectively,
influence the calculation of the effective price in the purchase order.

The next post will learn how to specify conditions that apply to the pricing of all orders for any material with a vendor, not only for a specific material or material group as is the case with outline agreements and info records.


What is Condition Technique in SAP?

To discuss the Condition technique in sap, The condition technique is used to define pricing across applications. For example, it is used in the SAP SD (Sales & Distribution) module as well as in the SAP MM module. The goal of the condition technique is to calculate the effective price in a purchase order. Master conditions are simply conditions defined with the condition technique. While this section is not essential to your understanding of master conditions in purchase orders, it does provide useful background information on the mechanism for determining pricing in Purchasing.

The Basic elements of the condition technique,The condition technique consists of four main elements:
  • Condition types
  • Condition tables
  • Access sequences
  • Calculation schema (pricing procedure)
These concepts are important for understanding how the system determines pricing in master conditions.

Condition type is a representation of a pricing element. Condition types exist for discounts, surcharges, and freight costs, for example. You use condition types to enter pricing in purchasing documents. You learned how to specify condition types when entering pricing in quotations and purchase orders, for example.

Condition table defines the combination of fields (the key) that identifies an individual condition record. The system stores the condition data you enter in the form of a condition record. For example, when you enter a vendor’s pricing in a purchasing info record with reference to a material master record, the key of the condition table includes the vendor number and the material number.

The actual pricing information – such as the gross price and any discounts – is stored in a condition record under this key.

Access sequence is a search strategy that the system uses to find condition records for a particular condition type. The access sequence determines the sequence in which the system searches condition records for a valid price.

Price calculation schema (pricing procedure), The calculation schema (also known as a pricing procedure, but the same mechanism can also be used to calculate tax amounts, periodend rebates, or costs, for example) is a group of condition types, defined in a particular sequence. It enables the system to determine that a particular set of condition types, in a specified sequence, apply in given circumstances. For example, the  calculation schema  determines Which condition
types apply to the gross price. The calculation schema also determines that the condition types for discounts are calculated in the effective price automatically.

With SAP MM Customizing, you can define price calculation schemas for specific vendors and/or purchasing organizations. The system searches for pricing data in condition records. The criteria it uses in the search depend on the keys in the condition table. The sequence of the search depends on the access sequence specified for the condition type. Which condition types are used in the search are defined in the calculation schema.

For example, suppose that you have just created an info record that specifies a 10% discount from the gross price. This

condition is then stored in a condition record under the vendor and material number. When the material is ordered from the vendor in a PO, the system searches for the discount using the access sequence. The calculation schema ensures that the 10% discount is deducted from the gross price instead of the net price during the price calculation process.
     
The different ways of maintaining master conditions, you can maintain conditions in the following ways:

Prices, As this method you can list or maintain the conditions that determine the net price in a single info record or contract. You can enter the going market price for a material.

Discounts and surcharges, As this method, you can enter discounts or surcharges that apply to all info records or contracts meeting your pricing criteria.

Other condition types, If your company has defined its own condition types, access sequences, and condition tables, you can define master conditions that use these pricing elements.

Price changes, You can change pricing by a fixed amount globally.

Tuesday, 17 November 2015

sap online training


Master conditions in SAP are conditions that determine the effective price in the purchase order. They serve as a central repository of pricing for purchase orders. They are automatically included in the price calculation in the purchase order if the PO references a contract or an info record, or if it meets certain criteria defined in the extended conditions.
There are three types of master conditions in SAP:
Conditions in contracts – Conditions in a contract apply to all release orders issued against the contract.
Conditions in info records – Conditions in the info record apply to orders that specify the material and vendor contained in the info record.
Extended conditions – These are a flexible way of setting vendor pricing. Extended conditions are master conditions that are included in the price calculation in a purchase order only if the PO meets certain criteria. One way to use extended conditions would be to define a 10% discount on all orders placed with a specific vendor that are created by a certain purchasing organization. In this case, the vendor number and purchasing organization are the two criteria a PO must meet before the price in the PO can be calculated.
Extended conditions are more flexible than master conditions in info records or contracts because you can define which criteria they must meet before they are applied to a purchase order. The documentation on outline agreements and purchasing info records shows how the conditions specified in outline agreements and purchasing info records, respectively, influence the calculation of the effective price in the purchase order.
The next post will learn how to specify conditions that apply to the pricing of all orders for any material with a vendor, not only for a specific material or material group as is the case
with outline agreements and info records.
More details
sap online training | Sap Online Tutorials | sap training courses | sap training in Chennai | sap training in Bangalore
,