Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Account Key in the pricing procedure is generally used for the Freight and Rebates related conditions which
will have the transaction event key and will store the Current Purchasing documents value.
Accruals Key will store the accumulated values of the respective conditions. The buyer can see the amount
spent on the freights over a period of time.
Accruals mean accumulating, with the addition of the account key, the system can post amounts to certain
types of accruals accounts. For example, rebate accruals which are calculated from pricing conditions can be
posted to the corresponding account for rebate accruals.
2. How to define a condition type as header condition type?
Condition Type : Condition type is defined as specific features of daily pricing activities in a SAP system. Using
the condition type, you can also put different condition types for each pricing, discounts on goods, tax and
surcharge that occurs in business transactions.
Transaction : M/06
Select your condition type and click on the details icon
In that screen, go to the block CHANGES WHICH CAN BE MADE
In that block, there are two fields
1.Header condit.
2. item condition
If you selected item condition check box, then that condition type will appear in the item condition tab details.
If you selected header condition check box, then that condition type will appear in the header condition tab
details.
If you selected bth item condition & header condition check boxs, then that condition type will appear in the both
item and header condition tab details.
3. How system pickup pricing procedure in Purchase order.
Path : IMG>MM>Purchasing>Conditions>Define schema determination>Determine Calculation Schema for
Standard Purchase Orders>
Schema grp Pur rog and Sch group vendor are blank and this has assigned to any pricing procedure. The pricing
procedure will pick to purchasing document via..
After creating the pricing proceedure, you are going to create the vendor schema group , which will be assigned to
the pur org with the pricing procedure and you are going to assign this schema group to the vendor in the vendor
master.
4. What is Account Assignment Category?
A Key Indicating whether on item is not be assigned to auxiliary account ( such as Cost Center, Sales Order,
Project). The Account Assingment Category determines which assignment details are required for item or several.
The account assignment category determines:
The nature of the account assignment (cost center, sales order and so on)
Which accounts are to be charged when the incoming invoice or goods receipt is posted
Which account assignment data you must provide
Implementation Considerations
Consumption-based planning procedures are simple materials planning procedures which you can use to achieve
set targets with relatively little effort. Therefore, these planning procedures are used in areas without in-house
production and/or in production plants for planning both B- and C-parts and operating supplies .
The prerequisites for implementing consumption-based planning are:
If you use forecast requirements, the consumption pattern should be fairly constant or linear with few
irregularities.
Your Inventory Management must function well and should always be up-to-date.
Integration
Consumption-based planning is integrated in the Materials Management component. You can access the
consumption-based planning functions from the SAP Easy Access >Logistics>Materials Management >Materials
Planning>MRP
Features
MRP Procedures:
In consumption-based planning, the following MRP procedures are available:
Reorder point procedure
Forecast-based planning
Time-phased materials planning
Lot-sizing procedures:
The standard lot-sizing procedures are available in the SAP system. However, you can quite easily integrate your
own formulas without much effort.
1. Project preparation - This phase provides initial planning and preparation for the project. Each project has its own
unique objectives, scope, and priorities. The deliverables described in this phase assist in completing the initiation
and planning steps in an efficient and effective manner – like setup of agile project governance, project plan and
project schedule are prepared at this stage.
2. Lean blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to
run SAP to support their business. It focuses on the rapid setup of solution validation environment for validation
workshops with business users to confirm scope and determine delta requirements that will be realized in the
next phase to enhance the baseline build of the system.
3. Realization - The purpose of this phase is to implement all the business process delta requirements defined during
the Lean blueprint phase. The team configures, develops, tests and documents the solution in series of time-
boxed iterations – the most valuable functionality first. Before the solution is released to next phase it is fully end-
to-end integration tested and accepted by end users.
4. Final preparation - The purpose of this phase is to complete the cutover activities (including technical and load
testing, end user training, system management and cutover rehearsal activities) to finalize your readiness to go
live. The Final Preparation phase also serves to resolve all remaining critical issues. On successful completion of
this phase, you are ready to run your business in your live SAP System.
5. Go-live support - The purpose of this phase is to move from a project-oriented, pre-production environment to
live production operation and provide sustained support to business users to aid their transition into the new
environment.
6. Operate - The purpose of this phase is to fine-tune the application lifecycle standards, processes and procedures
established during the project and align them with operation needs. The central operation platform is SAP
Solution Manager, which leverages the documented solution for system operations.
Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays
vital role in Business Blueprint [AS IS Process] stage.
A through Gap Analysis will identify the gaps between how the business operates and its needs against what the
package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned,
Accounting entries get generated at the time of GR/IR, and invoice verification.
On doing the Invoice verification, the following entry gets generated and the liability is booked.
At the time of invoice verification if there are differences between GR value and IR and if stock is not available the
difference amount would go to price differences A/c.
At the time of Goods Receipt the following entry gets generated (Ex. with notional figures).
For a P.O of Rs. 100(Basic 70 + Freight 10 ) (when freight is borne by the company)
3) PURCHASE – CONSUMABLES
5) IMPORT PURCHASES
In case of Import Purchases, the process remains the same but for the additional charges, which are included
inthe cost of inventory.
6) PURCHASE RETURNS
Now, while doing 202 in MB1A, you can enter the correct stock (10 in your case) and stock value (value in the
field Ext. GA amount in LC : 1000 in your case) against the corresponding valuation type.
Test the scenario and revert back in case of any issues.
29. Importance of changeability Indicator?
I'm a newbie is SAP MM and currently doing support for Logistics team. I would like to ask few questions
regarding changeability in release indicator that we used in release strategy in PO. Currently I having a doubt with
my existing release strategy for PO.
Existing configuration used changeability 2 - "Changeable, no new determination strategy" in the release indicator
R (Released), which means after all approvers approved the PO any changes are allowed in the PO including
values and quantity and system will not retrigger the release strategy.
This will allow buyers to change values and quantity again after the PO approved without approvers knew it and
send it to vendor which is for me is wrong process and how SAP tackle this issue.
Thus I would like to know actually what is the use of changeability 2 in the PO release indicator.
30. Movement Controls and usage?
Movement Types
In Inventory Management, movement types play a central role as the instrument for controlling goods receipt,
goods issue, and posting change activities. For every goods movement, you therefore have to specify a three-
character key to identify the movement type that controls the movement. In the SAP ECC standard system, for
example, the key 101 describes the movement type "goods receipt" either
for a purchase order or a work order.
The system uses movement indicators to differentiate between goods receipts postings for purchase orders and
those for work orders. Movement indicator B stands for a goods movement for a purchase order, whereas
movement indicator F stands for a goods movement for a work order. The system determines the movement
indicator for the movement type on the basis of the transaction code of the transaction used for the posting
activity.
The movement type not only specifies the direction of the goods movement, it also decides on the update of the
stock and consumption accounts and the screen layout of the transactions for the movement posting. Basic
settings for batch management and shelf-life expiration data management are also made at movement type level.
Warehouse Management also has movement types which, similar to their counterparts in Inventory
Management, control the process flow in the warehouse. In particular, Warehouse Management movement types
influence the interim storage area to be used (the organizational bridge between Inventory Management and
Warehouse Management). You link the movement types from Inventory Management to the Warehouse
Management movement types in Customizing to ensure a technical connection between WM and IM. For
example, if a goods receipt for a purchase order or work order is posted using Inventory Management movement
type 101 to a storage location with Warehouse Management, the system determines the corresponding
Warehouse Management movement type and, depending on the settings for the WM movement type, generates
stock in a “goods receipt” interim storage area.
31. From where FI integration will start?
Integration FI with MM
Integration of SAP FI with MM is done at OBYC.
Let me elaborate... In MM you purchase goods and to which you pay, the purchasing process has the following
steps:
Step1: First you send a Purchase Order to the Vendor.
Here there won't be any accounting entry as this is simply like telling the Vendor what goods you want, its
quantity and the date of delivery etc.,
Step 2: You will receive the Goods to the Purchase Order.
When you receive Goods you CAN NOT make the following entry
Inventory A/c Dr
To Vendor A/c
because, some of the goods you have received may be damaged or may not be upto the mark or for any other
reason goods may reject, so before posting it to Vendor A/c we keep it in separate place till we verify the goods.
And the actual entry will be:
Inventory A/c Dr (Transaction Key BSX @ OBYC)
To GR/IR A/c (Transaction Key WRX @ OBYC)
Here the goods received is Debited to inventory and Credited to a temporary A/c i.e., GR/IR a/c
Step 3: You will post an Invoice to the Goods received.
Here you will post the invoice after you are satisfied with the goods received, the entry will be
GR/IR A/c Dr
To Vendor A/c
Now the goods are moved from GR/IR A/c and Vendor is Credited. Now you got the final entry of Goods to Vendor
Account i.e.
Inventory A/c Dr
To Vendor A/c
i.e., Inventory A/c was Debited and Vendor A/c was Credit and GR/IR A/c is Dr and also Credited hence its balance
became 'Zero', and it has to be Zero always.
Step 4: And make Payment to Vendor.
Vendor A/c Dr
To Bank Clearing A/c
Step 5: At the time of Bank Statement upload:
Bank Clearing A/c Dr
To Bank Main A/c