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.