Revaluate Activity Type at Actual Price

I just want to share if anyone may need. It is complete scenario from configuration to planning, actual posting and final revaluation. I used some of the comments/posts on the forum - That I see it valuable and clear

1. Master data & set up
1.1  KL01-Create activity type

• Set the ‘Price indicator’ to “1” (Plan price, automatically based on activity) in the ‘Allocation default values’ section in order that the plan prices are calculated automatically. -> This means that the cost center budget entered in transaction KP06 will be divided by the quantity entered in transaction KP26 when you run the plan price calculation in transaction KSPI.
• You need to set the ‘Act. Price indicator’ to “5” (Actual price, automatically based on activity) in the ‘Variance Values for Actual Allocation’ section in order that the actual prices are calculated automatically. This means that the actual costs posted a cost center will be divided by the actual quantity consumed in the cost center when you run the ‘Actual Price Calculation’ in transaction KSII.

GL Planning/Budgeting

Purpose

In this Document we will capture GL Planning/ Budgeting Process, Scenarios and requirement of an Organization.
This component is used to handle GL accounting transactions that you can Prepare Future forecast, Allocation in a Particular Department.
You can use the planning function in General Ledger accounting to enter and distribute plan data to create budgets, forecasts, and other reports.
You can quickly and easily enter large amounts of plan data. You have the following options for plan data entry:

1. You can enter amounts as plan totals that are (automatically or manually) distributed to the planning periods.
2. You can enter amounts as period amounts that are automatically totaled.
3. You can enter a combination of both totals and period amounts.

SAP Inventory Valuation through FIFO

The below article will explain one of the approaches through which Inventory can be valued on FIFO basis in SAP -

We have two approaches to present our Inventory on FIFO basis -
1. Batch Input Method - A batch capturing the Receipt Value and the Quantity for every GR is maintained in the system. At the time of Goods Issue, the system will fetch the value from the batches in the ascending order.
2. Balance Sheet Valuation Method - In this approach, the goods are valued at the Moving Average Price throughout the period and at the Period-end date, an adjustment entry is posted to bring the inventory at the FIFO method.

I will discuss the configuration steps of Balance Sheet Valuation Method here.
Before beginning with the configuration of this approach, let me explain with an example for what exactly this approach will do -

Module pool for CO Month End Process

This document is explaining the process of creating a module pool for the SAP CO Month End Process. The objective is to provide a simplified screen to the end user to complete the month end process. Normally this process will be done by an ABPER, but it can be done by a functional consultant with a little bit knowledge on coding which is very simple.

Note: The document is appears to be lengthy because of adding detailed screens for every step.

I have provided the detailed steps to complete the process. Before going into the details, end result of the screen to be developed is as follows:

Error FS 861 in External Tax System

The purpose of this blog is help to identify the root cause of error FS 861 in External Tax System (SABRIX, VERTEX and TAXWARE).

Error FS 861 can be a generic error resulted from RFC_CALCULATE_TAXES_DOC when external tax calculation is used. The cause can be wrong jurisdiction code, jurisdiction code structure, country not supported and so on.

The steps bellow should be followed to identify the root cause of error FS 861.

1. Check if company code is US,CA,PR:

According with SAP Note 1738657, SAP supports external tax systems only for the country codes US, CA and PR (Puerto Rico). This means the country of the company code must be one of these countries so that taxes are calculated using the external tax system and are also updated there.

Most unnoticed functionalities in SPRO

As a functional consultant, we might have seen SPRO screen day in and day out. But, many of us may have missed to notice, there are many additional functionalities available in SPRO. Usually, we just run to the node where we wish to do the changes, complete required changes and rush for testing.

Through this blog, I would like to bring to the notice of fellow community members about many unnoticed functionalities available in SPRO.

1. How to find the list of tables that are updated through particular SPRO node?

Place cursor on the node where changes are being done and go to below path in SPRO.

In next screen, double click on underlying view.

COPA Planning

Planning is a key tool available in Profitability Analysis (COPA), which is widely used to plan for annual forecast for Profitability Plans and track the actuals against the planned figures.  Planning in Profitability Analysis allows to plan Sales, revenue and profitability data in any selected profitability segments.  The planning data can be displayed in various ways, depending on business demands. It is not a standalone component. It can not only send data to other applications but it can also receive planning data from those applications. It is also not limited by any specific time frame. The planning can be done more than one fiscal year at one or on a rolling basis. The data can also be planned by posting periods or calendar weeks. It is also possible to create and store planning data in different plan versions.

The planning framework is the main working environment for sales and profit planning. It contains all possible settings for building the planning framework. The planning can be carried out from this framework screen. MS Excel can be used as a planning screen for planning data in the SAP system. The planning framework allows for planning with or without MS Excel. The various ways in which manual planning can be executed are as under

KP06 Excel Upload

Creation of Planning Layout

Go to t.code: KP65

Click on Create

Select the Version, Period and Fiscal year in the General Data Selection in the Menu Bar Edit --> Gen data selection --> Gen data selection

Mass Creation of Vendor (Supplier) Master Records through LSMW

Easy 12 steps for mass creation of vendors(suppliers) using Legacy System Migration Workbench - SAP Standard Tools.

Step 1: Maintain Object attributes
Step 2: Maintain Source Structures
Step 3: Maintain Source Fields
Step 4: Maintain Structure Relations
Step 5: Maintain field mapping and conversion rules
Step 6: Maintain fixed values, translations, user-defined routines
Step 7: Specify files
Step 8: Assign files
Step 9: Read & Display imported data
Step 10: Convert and Display converted data
Step 11: Create batch input session
Step 12: Execute Batch Input Session

First, call Legacy System Migration Workbench by entering transaction code LSMW.

Distinguish FI Documents Doc Type for corresponding Controlling Documents

Probably we may have noticed that all FI documents for corresponding controlling document that are generated from the controlling application component is most of the times same i.e. AB or any other document type that we might have configured.

However there might be a Business Requirement that we should be able to distinguish the FI documents that are generated because of the corresponding controlling document from other FI documents generated out of non-controlling application component.

How to address this Business Requirement

• First: We can definitely look at the business transaction from FI Table – BKPF & BSEG and Text field in BSEG in order to check if the FI document is related to a Controlling Document however this may not be very handy as more analysis might be required.
• Second: We can create & designate a different document type for the FI postings that are generated because of corresponding controlling document posting and in that way only by referring the document type it is quite easier to identify instead of depending on text or business transactions.

Now the question comes where we configure the Document Type that is used for FI posting for a controlling document:

Simple Finance - The Convergence of the GL Account and the Cost Element

In this post we will look at the convergence of long standing pieces SAP ERP finance master data, the GL Account and the Cost Element. As anyone that has worked with SAP CO in the past knows the cost element is key to the controlling side of SAP. It in an object that allows you to identify the type of activities that can be done within controlling with that account. They are generally divided into Primary and Secondary cost elements.

• Primary cost elements have an associated GL account and are generally expense or revenue accounts.
• Secondary cost elements exist only in CO and are used for internal settlements, assessments, and allocations.

When creating a new revenue or expense account in the GL you have to create a corresponding cost element in CO and typically all you were doing was selecting a Cost Element Category.

With the Simple Finance Add-on 2.0 (now called On Prem 1503) the traditional cost element create, change and display transactions are gone. The functions have been combined in FS00 - Manage G/L Account Centrally. This greatly simplifies the act of creating a new account and eliminated the need to maintain separate masters.

Understanding the Standard Product Cost Estimate

Product costing is one of the key areas in Manufacturing and process industries. It is used for estimating and valuating the internal cost of a product.Product cost planning is used for estimating/predicting the cost incurred in producing a Finished Product . This estimate is also used for budgeting purpose . When the material is actually produced, the actual cost is incurred and the variance between planned cost and the actual cost is calculated. Based on the magnitude of variance, decision is taken to re-estimate the cost of the materials.

Standard Cost estimate is the basis of product cost planning . This is nothing but the estimation of cost of a particular product, being manufactured.

Before getting in to SAP terminologies, let’s relate it with a very simple practical scenario, so that it is more clear and understandable.
Suppose a company is manufacturing glass containers. The components used are

1. The Glass
2. The Cap

How discover batch jobs that are running for a specific program?

To discover which batch jobs are running for a specific program you have to first find out the program name then use the transaction SM37 to look for the jobs.
To do this follow the steps:

1. Go to transaction SE93 and fill the transaction code and click on Display. In this example we are using the transaction FBL3N;

.

Use of conditions in DMEE-tree

Quite recently I worked on implementation of budget payment orders (taxes, social payments etc.) for our Client. First of all, I compared the structures of ordinary and budget payment orders and found out that there is a dozen of extra fields in budget payment order that are not supported in an ordinary payment order. So the task boiled down to add these extra fields to the existing DMEE-tree (for ordinary payments), however output them only when certain conditions are met. I decided to implement this requirement using conditions in DMEE-tree. As it turned out, this functionality is quite simple, but when you try to use it for the first time it will take some time to understand the mechanics behind it.  Let’s take a closer look at this functionality.

Condition technique is a standard functionality in DMEE that enables you to control whether a node would be processed during the generation of payment orders or not. Basically, if the condition for a separate node is not fulfilled then the node will not be processed and hence not displayed in the file with payment orders. The conditions can be configured for any node type. If the condition should apply to several fields, you can apply it to a composite node or a segment that contain these fields.

Financial Enterprise Structure

Purpose

• Provide an overview of SAP Enterprise Structure and some of the specific finance related organizations 

SAP Enterprise Structure Overview

• Enterprise Structure is the system representation of your business structure
• SAP has a number of organizational unit elements that help you portray the Accounting, Logistics, Sales, and Human Resources structure of your company
• The structure of your company, business processes, and implementation scope will guide the SAP organizational units that will be required
• Example Org Units are: Company Code, Sales Organization, Purchasing Organization, Plant, Segment, Profit Center, Cost Center, etc

Basic SAP Tax Overview

Purpose

I would like to provide a document that outlines the basics of SAP tax configuration and provides a couple of examples of how tax code could be determined in SD and MM.

Overview

• SAP provides the majority of the tax configuration out of the box by country
• There are three SAP areas that work together to determine taxes FI,MM, and SD
• FI – Base configuration for tax procedures, rates and accounts
• SD – Configuration/master data to determine output tax code
• MM – Configuration/master data to determine input tax code
• Master data such as customer, vendor, and material, as well as transactional data like POs and Sales Orders are key to determining the correct tax
• Rates can be maintained in SAP or SAP can call an external system for them (this document with focus on rates maintained in SAP)

Debugging for Functional Consultants

Introduction to Debugging

SAP consists for various transactions codes and data. Data are stored in the tables and the transaction codes have ABAP programs at the back end. Literal meaning of debugging is ,to make something(a program in current discussion) bug-free. But that is just one aspect of debugging.

Through debugging, we can analyze a program, understand the flow logic and most importantly find out the root cause to any issue .Although Debugging is the obvious task of an ABAP consultant, the debugging knowledge would be of great help to functional consultants. It will save their time for analysis and issue resolution , reduce over-dependence of ABAP team , help in effort estimation.

Let's look at the different aspects of debugging. We will divide the discussion in to the below parts.

1. Programs in SAP ABAP
2. Initiating the Debugging
3. Breakpoints
4. General tips

Pre-requisites for FI-SD Integration

This series of documents for FI-SD integration is divided into 4 parts. This document is the first part of the series. Adding links for other parts before I start with the content.

Part-II : FI-SD Integration - I
Part-III : FI-SD Integration - II
Part-IV: FI-SD Integration III

FI-SD Configuration Pre-requisites

The pre-requisites for carrying out this configuration are as follows:

• Material Master
• Customer Master
• Pricing Procedures
• Condition Records
• G/L Accounts 

FI-SD Integration - I

This series of documents for FI-SD integration is divided into 4 parts. This document is the second part of the series. Adding links for other parts before I start with the content.

Even though the document title says FI-SD Integration - I, it is the second part because part I was the pre-requisites required for the integration.

Part-I : Pre-requisites for FI-SD Integration
Part-III : FI-SD Integration - II
Part-IV : FI-SD Integration III

Automatic Account Determination
The accounting entries with respect to the billing will generally result in

• Debit Customer account
• Debit Freight-out account
• Credit Revenue account
• Credit Excise Duty Payable account
• Credit Sales Tax Payable account 

FI-SD Integration III

This series of documents for FI-SD integration is divided into 4 parts. This document is the last part of the series. Adding links for other parts before I start with the content.

Even though the document title says FI-SD Integration - III, it is the fourth part because part I was the pre-requisites required for the integration.

Part-I : Pre-requisites for FI-SD Integration
Part-II : FI-SD Integration - I
Part-III : FI-SD Integration - II

Assign G/L Accounts

FI-SD Integration - II

This series of documents for FI-SD integration is divided into 4 parts. This document is the third part of the series. Adding links for other parts before I start with the content.

Even though the document title says FI-SD Integration - II, it is the third part because part I was the pre-requisites required for the integration.

Part-I : Pre-requisites for FI-SD Integration
Part-II : FI-SD Integration - I
Part-IV: FI-SD Integration III

Define And Assign Account Determination Procedures

KSII - PER Settlement Rule - Service Flow

When you work with PER settlement Rule on PM/CO Orders, and you post and settle activities with the same cost element, sometimes something called the Service Flow is triggered. Some time ago i spend time investigating about this stuff. A friend of mine tell me 'this is the system behavior', but don't explain me the reasons, i guess lot of people know about this but have never read the documentation.

OSS '156563 - Settlement after activity allocation/revaluation' explain this behavior of the system. I think this oss is a bit difficult to understand so in this document im going to post the step by step to recreate what i think is the most important.

Lets begin:
1. Create 2 cost centers
6000_PMSF01 Sender of the activity
6000_PMSF02 Settlement Cost Center of the PM Order

How to Estimate HANA Sizing for CO-PA Accelerator

Since the second half of 2014 a new dedicated SAP HANA Quick Sizer tool has been available which covers SAP Suite on HANA including the CO-PA Accelerator option.
Also see SAP Note 1793345 Sizing for SAP Suite on HANA.

===================================================================

THE INFORMATION BELOW IS NOW OUT OF DATE

===================================================================

The SAP Quick Sizer tool is available now for SAP HANA and even includes content for the CO-PA Accelerator.

The mechanics of using the QuickSizer for CO-PA Accelerator are very easy.
1) Start the QuickSizer
2) Input the Customer No.
3) Provide a Project Name
4) Select SAP In-Memory Computing
5) Select HANA Rapid Deployment Solutions
6) Locate the row element for CO-PA-ACC
7) Input the Number of CO-PA Users, the Source Data Footprint in GB, and the estimated Compression factor (7 is the default)
8) Click on the Calculate Results button