Beruflich Dokumente
Kultur Dokumente
com/2016/08/01/a
ctivation-of-material-ledger-on-sap-s4-hana-
1511-finance/
ML
Activation of Material Ledger is mandatory on S/3 HANA due change in the data design for
Inventory valuation but activation of actual costing is not mandatory on SAP S/4 HANA.
Below mentioned screen shot prescribes traditional Inventory management Vs S/4 HANA
Inventory management based on Material ledger.
Material Valuation in SAP S/4 HANA allows Up to 3 currencies,
Actual Costing:
But SAP recommends if you activate the material ledger for a plant, you should also activate it
for all the other plants in the company code. This ensures that the accounts in Financial
Accounting and Materials Management are reconciled.
The planned prices are handled by the system with the following priority:
Actual Costing:
Inventory and material movements are generally valuated either at Standard price (S) which is
constant over a period of time or Moving average price (MAP) which gets adjusted (calculated)
automatically based on every Goods receipt or Invoice receipt. Both of these two methods have
their own pros and cons. Actual costing combines the advantages of standard price with
advantages of using MAP.
ML captures all price variances (like purchase price variances, production variances etc) and
allows (as optional period end activity) revaluation of ending inventories at period end and
releases it as standard price (generally) for next period. Actual costing is optional in S/4 HANA.
Actual consumption is updated in the quantity structure but not considered by price
determination.
You can use this setting if you simply want information about the complete actual quantity
structure. You can assign variances between the plan price of the cost center/activity type or
process, and the actual price calculated at period end to the particular cost object at period-end
closing using the function ‘Revaluation at Actual Prices’.
Actual consumption is updated in the quantity structure and taken into account for the
price determination.
If you choose this setting, the variances between the plan price and the actual price are adjusted
subsequently. The cost center or the process is then credited and the material associated with the
consumption is debited. In the context of multi-level price determination, these variances can be
rolled up through the production structure up to the finished product in the same way that
material price variances are rolled up.
If you choose this setting, you cannot use the function ‘Revaluation at Actual Prices’ at period
closing in Cost Object Controlling, as the variances from the cost centers/processes are debited
to the material direct. If you do use the function ‘Revaluation at Actual Prices’ at period closing,
the cost centers/processes are credited twice and the materials are debited twice.
We have to keep below mentioned points during Migration of Material Ledger Customizing:
Key Points:
The material ledger is required if you are using SAP S/4 HANA Materials Management –
Inventory Management (Simplified Logistics).
You need to migrate the material ledger even if you are already using SAP Simple
Finance (that is, you are migrating from SAP Simple Finance to SAP S/4 HANA
Inventory Management).
You need to migrate the material ledger even if you are already using the material ledger
in your source system.
TAX:
What is the difference between maintaining tax codes in TAXINJ and TAXINN
Both procedure TAXINJ and TAXINN has thin line difference where as TAXINN procedure is
condition based & TAXINJ is fomula based.If you drag down details of TAXINJ is fomula
based,where you can find Routine( selection with logic in line of condition type) are play vital
role in tax calculation.
If you selected TAXINN procedure , you can maintained tax rate with respective condition
types in FTXP during creation of tax code.But you should maintain condition record in FV11
t.code for condition types JMX1 & JMX2 are as 100%. Also you can maintain tax rate for
condition types Basic Excise Duty,Edu cess , H. Edu cess,VAT/CST in FV11 t.code in stead of
maintaining tax rate in FTXP.
1. TAXINJ is a tax calculation procedure for country version India and it supports
formula-based excise determination. You need to configure this tax calculation procedure
Excise Conditions
LST/CST/VAT Conditions
3. Define the Tax Procedure according to the settings in the figures below.
You can do this in the IMG ⇒ Financial Accounting ⇒ Financial Accounting Global Settings
⇒ Tax on Sales/Purchases ⇒ Basic Settings ⇒ Check Calculation Procedure ⇒ Define
Procedures. Tcode:OBBG
You can do this in the IMG ⇒ Financial Accounting ⇒ Financial Accounting Global Settings
⇒ Tax on Sales/Purchases ⇒ Basic Settings ⇒ Assign Country to Calculation
Procedure. Tcode:OBYZ
The standard system comes with two tax calculation procedures. TAXINN is only supports
condition-based excise determination, whereas TAXINJ supports condition-based excise
determination and formula-based excise determination.
Both tax procedures contain condition types that cover all of the excise duties and sales taxes
applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor
you purchase a material from, or which chapter ID the vendor stocks the material under, you
create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates
you have entered in the condition records.
Activities,
Customizing
Make the settings in Customizing for Logistics u2013 General, by choosing Taxes on Goods
Movements ⇒ India ⇒ Basic Settings ⇒ Excise Duties Using Condition Technique and u2026 ⇒
Account Determination.
These activities include one activity where you define a tax code for condition-based excise
determination.
Master Data
Create condition records for all excise duties that apply, and enter the tax code for condition-
based excise determination in each.
TAXINN Vs TAXINJ:
Definition: condition-based excise determination
This method requires you to create condition records for each combination of vendor or customer
and material (and possibly other conditions).When you create a purchasing document, the system
calls the tax procedure assigned to India. The tax procedure finds all of the condition records that
you have created for that combination of vendor and material.
When you create a sales document, the excise duties and sales taxes are determined by the
pricing procedure (not the tax procedure).
This method was used in the Country Version India Add-On and requires you to maintain
additional data in the Excise Rate Maintenance transaction, J1ID.
When you create a purchasing document, the system calls the tax procedure assigned to India.
Each of the excise duties in the tax procedure has its own condition types, and each condition
type is assigned to a formula. This formula instructs the system to calculate the excise duty using
the data that you have maintained in the Excise Rate Maintenance transaction.
When you create a sales document, the system determines the excise duties and sales taxes using
the pricing procedure (not the tax procedure).
Pricing Procedures:
The primary job of a pricing procedure is to define a group of condition types in a particular
sequence. The pricing procedure also determines:
If a sales department processes sales orders for a variety of foreign customers, the department
can group the customers by country or region. A pricing procedure can then be defined for each
group of customers. Each procedure can include condition types that determine, for example,
country-specific taxes. In sales order processing, you can specify pricing procedures for specific
customers and for sales document types. The system automatically determines which procedure
to use.
Choose Basic Functions Pricing Pricing control Define and assign pricing
procedures.
T Code: OVKK and assign respective sales area for different kind of pricing procedure.
Pricing procedure follows below assignment.
2. Create access sequence and maintain accesses assigned with condition table. ZAS -
>CUSXXXXX
Determination part.
Sales org + distribution channel + division + customer pricing procedure + document pricing
procedure ,SO+DC+DIV+CP+DP = ZPP
and we assign pricing procedure against above 5 parameters in the configuration.
based on condition maintenance we restrict the application where you gonna maintain the
condition record.
lets say you restricted it to product and successfully you maintained a condition record for
testing.
now I am using this product in a transaction document(example ZAG). you called the transaction
type(ZAG) and entered the customer ABC and entered some product XYZ with quantity. now
the minute you enter the product and hit on enter.
System searches for relevant pricing procedure to determine. by formulating all 5 parameters
from the sources based on org model it brings respective sales area data(SO+DC+DIV) and
based on ABC’s customer pricing procedure(you can find it in sales area data a/block under
billing area.
based on transaction type it will bring the value document pricing procedure ( ZAG’s transaction
category header data).
after forumalting all 5 parameters it determines corresponding pricing procedure from the
configuration.
again based on the maintained condition record it will apply the value on to the screen.
based on number of different condition types(diff calculation types) it will show different price
element in the output. and all these calculation will be done by IPC.