In this blogpost we will see the use cases of characteristics in SAP COPA. It is essential to understand the importance of characteristics because this is a first building block of Profitability Analysis.

If you are setting up profitability analysis, then as initial steps you have to sit down with client to point out required characteristics based on which profitability reports will be extracted.

Characteristics are also important from database point of view, as the number of characteristics impacts the size and complexity of data.

Before we get into more details, as disclaimer this blogpost is a piece of eBook – Controlling Profitability Analysis in SAP. If you want to learn end to end SAP COPA then you can checkout this book, which talks about everything from start to end in simple & plain English.

What are the characteristics?

Characteristics are nothing but those aspects on which we want to break down the profit logically such as a customer, region, product, sales person etc.

Several essential and obvious characteristics are pre-defined automatically for every operating concern; these are known as fixed characteristics.

In addition to fixed characteristics, up to 50 non-fixed characteristics can be added to an operating concern.

Characteristics can be categorised in four types:

• Fixed characteristics: Some characteristics are automatically pre-defined in every operating concern.
• Pre-defined characteristics: In addition to fixed characteristics, a number of other pre-defined characteristics are available in the field catalogue and can be added to operating concern.
• Copying characteristics from reference table: You can create characteristics by coping from table.
• Characteristics created from scratch: You can create characteristics, by defining own logic to derive values.

To derive values of these characteristics, it is necessary to create derivation rules or table lookup rules unless they are readily available in the sender application (For e.g. in SD data flow to CO-PA, fields on the billing document).

When a value flows from SD, MM, CO, and FI to CO-PA, it will create a line item in the CO-PA tables. The way you customize the master data will directly impact how the characteristics and value fields are populated in the line items. Below is one example of a CO-PA line item.

You can see that the characteristics were populated automatically by the system in above snapshot. You can change the behaviour of the assignments and also complete the missing ones. It’s very important to have all characteristics filled for each posting so that the CO-PA reports you run for any characteristic are complete.

Characteristics derivation makes it possible for the system to automatically derive unknown characteristics value (especially for user defined characteristics) if these are dependent on characteristics whose values are known.

Also read: Everything about derivation rule in SAP Controlling Profitability Analysis

Also

Maintain Characteristics

Access the activity using the following navigation options:

SAP Easy Access	Controlling -> Profitability Analysis -> Structures -> Define Operating Concern -> Maintain characteristics
Transaction code	KEA5

Click on display.

Following screen shows available and created CO-PA Characteristics in the system.

The characteristic region is not readily available, so we need to create it.

Click on

Then click on

(Note: We have two options while creating defining characteristics, one is to transfer it from existing SAP table or second is to create user defined characteristics, which will have it’s own SAP table to maintain values)

We are copying region characteristic from table KNA1

Here you can see the field region is added.

Now we will create a user define characteristics.

Note: A user defined characteristics should begin with WW.

Inputs:

Description:        District (we are creating district characteristic)

Data type:           Character

Length:                 18

Check table:       T25** (here system will create table which starts from T25 and the values of this characteristics stored there)

We have created this characteristic from scratch (without any reference), so we need to update it manually at the time of posting.

Click on

After activating characteristics you can see the status of characteristic and generated table.

Characteristic district is created.

Conclusion

In this blogpost we learned why characteristics are needed and how to maintain it.

As said at the start of the blog this blogpost is from this eBook, so if you want to know more about Controlling profitability analysis then you can checkout the book.

If you want to get notified with new blogpost, then do subscribe below

Get update of new blog posts

Name

Country Your country Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire, Saint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos Islands Colombia Comoros Cook Islands Costa Rica Croatia Cuba Curacao Cyprus Czech Republic Democratic Republic of the Congo Denmark Djibouti Dominica Dominican Republic East Timor Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Isle of Man Israel Italy Ivory Coast Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Republic of the Congo Reunion Romania Russia Rwanda Saint Barthelemy Saint Helena Saint Kitts and Nevis Saint Lucia Saint Martin Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and the South Sandwich Islands South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu U.S. Virgin Islands Uganda Ukraine United Arab Emirates United Kingdom United States United States Minor Outlying Islands Uruguay Uzbekistan Vanuatu Vatican Venezuela Vietnam Wallis and Futuna Western Sahara Yemen Zambia Zimbabwe

Email address:

Leave this field empty if you're human:

If you enjoy the blogpost then you can stay connected with us on below platforms:

YouTube

LinkedIn FICO Page

LinkedIn ABAP Page

LinkedIn Logistics Page

Instagram

🙂

In this blogpost we will see basics of IM, Why IM is needed and what is use of IM? Major Config. and end user transactions in SAP Investment Management.

Flow of Blogpost:

• Introduction
• IM in SAP
• Configuration steps of IM

Basics – What is Investment Management in SAP?

Investment Management is a budgeting tool that helps organizations to budget, plan and structures investment goals. Investment programs are used on top of Project System. Now you might say, project system itself have budgeting functionality, then what is the need of Investment management?

Lets understand this with one example; Consider your organization have international presence. The head office is in Europe. And there are hundreds of different projects going on at different locations. All projects are undergoing for different purposes. Some projects are for setting up new offices, some for restructuring existing plants, building new stores etc.

So project level expenditure management and budgeting is the lowest level management in organization hierarchy. On top of projects business needs investment programs to categorize and allocate budget as per business priorities and decisions.

Investment programs can be created based on geographical areas and then further drilled down to different segments of business. For e.g. there will be separate Investment program for each country and then under that investment program budget can be allocated to different segments like IT, Sales & Marketing, Accounting, Manufacturing etc. or based on product mix, revenue mix.

It can also be done vice versa, Multiple investment programs as per business segments and then under each segment different geographies can be added.

Before it gets too confusing lets have look at sample Investment program:

Highest level node is the main node of Investment Program, it tells you about investment program. We can see in above image this Investment program is for Mexico. After first node you can assign multiple levels as per business requirement (99 level drilldown is supported)

Each node can have organization units assigned to it along with responsible person. Budget has to passed on from top to down. Which can be monitored and validated with allocation and approval approach.

Projects are assigned to the lowest level nodes. In above structure you can see under CAPEX there is lowest level node for New Stores. So all the projects in Mexico created for New stores can be assigned to this node. This node will have certain amount of approved budget that can be distributed to all assigned projects based on requirement or management decisions.

Lets understand the life cycle of Investment programs in bullet points:

• Decision of Investment (appropriation request)
• Creation of Investment Program
• Budgeting the Investment program nodes
• Creation of Project (Investment Measure)
• Transferring budget from IM to Project
• Booking actual expenses during project completion time
• Periodic settlement to AUC
• Upon Project completion final settlement to Final Asset
• Asset Depreciation will be booked as per legal and other valuation methods.

If you want to know more about it from business standpoint, how things happens in business from top to down? How budgets are approved, allocated and monitored, then you can give try to this eBook which is written by a project manager to understand things from high level management.

Hope you got the high-level overview of IM, In next chapter we will see end user activities in Investment Management followed by backend configuration chapter.

Investment Management in SAP (End user activities)

Earlier we saw the use of Investment program. Based on it you can guess the basic things, we will require to create Investment program. Below is the list of activities that users do in SAP:

• Create Investment program definition IM01
• Create top position of Investment program IM11
• Change/Create IM Program structure IM22
• Budget Program IM32
• Supplement budget IM30
• Budget return IM38
• Assign Investment program position to Project CJ20N
• Allocate budget to project IM52
• Return budget from project IM52 (with return radio button)

And that’s pretty much that you can do in Investment Management. Let’s check each activity in little deep:

Also Read: Functioning of CO-PA in make to order scenario

Create Investment program definition IM01

While creating investment measure you will have option to enter person responsible for the investment program. You have to enter fiscal year variant and currency. Based on fiscal year variant, year end budget transfer will take place.

Create top position of Investment program IM11

In IM11 you will have to create top positions of budget which can be restricted to organizational units like controlling area, company code, profit center etc. In our initial example we discussed how we can have same investment program created for different geographies. And it can be drilled down to multiple countries and company code. So we can assign each node of investment program to separate controlling area/company code (currency validation will be there).

Change/Create IM Program structure IM22

Here you can create whole structure of Investment program

You can double click on any node to assign it to any organizational unit.

Budget Program IM32

Once the structure is created, you can budget the program nodes as per requirement in IM32

In above screen budget can be entered on various nodes, following top-down or bottom-up approach.

Supplement budget IM30

Once the initial budget is updated through IM32 then afterwards you can supplement more budget through IM30 or can return the budget by IM38 transaction.

Assign Investment program position to Project CJ20N

Once the investment programs are created and budgeted, it needs to be assigned to projects in CJ20N

Allocate budget to project IM52

Now projects are assigned to investment programs, then we have to transfer budget to projects from Investment program positions. This is done through IM52 transaction.

We can notice that project is reflecting on level 4 under level 3 investment measure.

And you are done with budgeting in Investment management.

Further you will have to budget lower levels of project then you can use WBSE to capture cost.

Investment Management reporting transactions: S_ALR_87012824 and S_ALR_87012813

In next chapter we will see major configuration that are required in Investment Management in SAP.

Read eBook: SAP DME – A Simplified Guide

Configuration steps of Investment Management in SAP

Configure Program Type

First step in IM configuration is to configure Program type. You enter program types at the time of create of Investment program (in IM01)

So, let’s see what program type controls:

SPRO – Investment management – Investment Program – Master data – Define Program Types

You can notice that we entered budget profile and plan profile in program type. These needs to be created separately. It controls that how many years of future / past planning / budgeting you can do.

Status profile will allow the approval and rejection functionality in IM.

Represent. Form will decide how IM structure should be displayed. (In coding format or text format)

Object class help to categorize CO class for IM

Investment profile will control automatic creation of AUC while creating WBS/IO

Budget dist. Overall & Budg. Dist. Ann. Vals – these check box will affect the budget distribution.

On left hand side you have one tab for assignable operative object

Here you can select what are the object type to which Investment program can be assigned.

Define Person Responsible

Here you have to define responsible person that can be assigned in investment programs. Same will be used in various workflows.

SPRO – IM – Investment Programs – Master Data – Allowed Values for certain master data fields – Define responsible person

In this config node you can configure below values:

Enter numeric value in responsible person field and in Office user enter the SAP user ID.

Define Plan Profile

Plan profile will control how much years in future you want to plan your investment. (this is assigned in Program Type)

SPRO – IM – Planning in programs – Cost Planning – Maintain Plan profile

Which values should be allowed to plan – Total / Annual

Past, Future, Start enter the number of year system should allow to enter and change values. If you enter 2 in Past field. Then you will be able to change and enter past two years plan data.

Decimal Places, scaling factor can be decided in plan profile.

Planning currency – Co area currency / object currency

Define Budget Profile

It is similar like Plan Profile, only this time the budget will be controlled as per profile maintenance.

SPRO – IM – Investment program – Budgeting in program – Define budget profile for investment program

Define Number range for budgeting line items

SPRO – IM – Investment program – Budgeting in program – Define number range for budgeting line items

Define Investment profile

When you settle Investment Measure (WBS, Internal Order) it gets settled to AUC. In IM AUC is created automatically at the time of release of Investment Measures. During periodic settlement system collects all debit items from WBS / IO and settle it to AUC. You don’t have to enter settlement rule manually.

This is controlled in Investment profile:

If you tick manage AUC, system will automatically create AUC while releasing WBS / IO.

For that you will have to enter asset class in Inv. Meas. Ast. Class field. If selected fix default class, then system will not allow you to change asset class manually at investment measure level.

You can enter different asset class for depreciation simulation.

Assign this investment profile to project profiles.

Conclusion

With this set of configuration you should be able to start using IM. Hope you got an overview of Investment Measures along with end user activities and backend configuration related to it.

Sign below to get weekly notification of new blogpost.

Get update of new blog posts

Name

Country Your country Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire, Saint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos Islands Colombia Comoros Cook Islands Costa Rica Croatia Cuba Curacao Cyprus Czech Republic Democratic Republic of the Congo Denmark Djibouti Dominica Dominican Republic East Timor Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Isle of Man Israel Italy Ivory Coast Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Republic of the Congo Reunion Romania Russia Rwanda Saint Barthelemy Saint Helena Saint Kitts and Nevis Saint Lucia Saint Martin Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and the South Sandwich Islands South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu U.S. Virgin Islands Uganda Ukraine United Arab Emirates United Kingdom United States United States Minor Outlying Islands Uruguay Uzbekistan Vanuatu Vatican Venezuela Vietnam Wallis and Futuna Western Sahara Yemen Zambia Zimbabwe

Email address:

Leave this field empty if you're human:

If you enjoy the blogpost then you can stay connected with us on below platforms:

YouTube

LinkedIn FICO Page

LinkedIn ABAP Page

LinkedIn Logistics Page

Instagram

Basics

In this blogpost we will see everything about cost object settlement. How each cost object are settled? What configuration is required to do settlement run? And how to trace these settlements on table level?

In order to understand settlement of cost objects, first we have to look into cost object itself. Controlling module is made of various cost objects. Cost objects are used to capture cost. So first we need to understand how many cost objects there are to capture any kind of cost.

• Cost Center CTR
• Sales order SDI
• Internal Order ORD
• Production order ORD
• Profitability segment PSG
• Network NTW
• Network activity NWA
• Work breakdown structure WBS

Every cost object has separate purpose. And it is used to capture different set of cost. For e.g. WBS/Network are used to capture project related cost. Whereas internal order and cost center usage is dependent on each and every organization.

But the bottom-line for this blogpost is that most of the cost objects are temporary cost carriers and has to be settled to final receiver.  And this makes settlement a major activity.

Examples: WBS is settled to asset, sales order settled to profitability segment, Internal order is settled to cost center. (It is not possible to settle cost center, because cost center is considered as final object. If you are booking cost in cost center, then it means there should not be any further transfer of cost)

Settlement Profile – What is the use of settlement profile?

Settlement profile is the template for any object to settle cost. Every cost object that needs to be settled should have settlement profile.

Settlement profile is configured in transaction OKO7. Here you can create settlement profile for sales order, production order, projects, internal order etc.

This is how settlement profile looks like. First you decide whether the cost object should be settled in full as mandatory or it can be optional.

In second part, where you maintain allocation structure, source structure, PA structure these all are used to restrict or filter the settlement cost. For e.g. in allocation structure you can maintain some cost elements in grouped manner and assign that allocation structure in settlement profile. Then whenever this settlement profile will be used it will only consider cost of those cost elements that are entered in allocation structure. It is also used for better reporting by grouping different cost elements separately.

In indicators part you have options to select % settlement or amount settlement (this impacts at the time of settlement rule creation)

In valid receivers, you have to make all potential receivers optional. For e.g. if this settlement rule is for WBS element then we know WBS is settled on asset, so asset settlement should be optional here.

Once settlement profile is created it should be assigned to source cost object.

• Project/WBS – Settlement profile is assigned to project profile
• Internal order – Settlement profile is assigned to internal order type
• Sales order – Settlement profile is assigned to requirement class
• Production order – Settlement profile is assigned to order type

So you create settlement profile in OKO7 irrespective of source object and then assign it to source type.

For internal order settlement profile will be assigned to order type. And under that order type all internal orders will have settlement same settlement profile. (however it can changed at all cost object level)

Settlement rule – How to create settlement rule?

Once the settlement profile is created and assigned, you have to create settlement rule for all cost objects. In all cost object somewhere in menu there is option to create settlement rule.

In sales order line-item level, you have account assignment tab where you can create settlement rule

In WBSE there is button at bottom for settlement rule

In internal order at menu there is option for settlement rule

This is how settlement rule will look like. You have to maintain receiver category and receiver. Remember that you can only maintain those receiver which you allowed in settlement profile.

Then mention % settlement, you can have multiple receiver and distribute settlement to all receiver.

There is also option to maintain amount, like how much amount you want to settle to this receiver. But this option will only be available if you tick it in settlement profile.

Also Read: Everything about FEBKO & FEBEP tables in SAP (Electronic & Manual Bank reconciliation)

Settlement run – What are the ways to run settlement?

There is dedicated transaction code for each cost object to run settlement.

• Sales order settlement – VA88
• Project/WBS settlement – CJ88
• Internal order settlement – KO88
• Production order settlement – C088/KO88

This is how selection screen looks like in almost all of the above transactions.

Enter sender object on top then settlement period and select processing type and execute.

It will settle the cost from sender to receiver as mentioned in settlement rule.

Upto this point everything is very clear and straight forward, but real challenge comes in when we have to track these settlements. In next heading that is what we will be looking into..

Read eBook: Controlling – Profitability analysis (CO-PA): Comprehensive coverage of the SAP CO-PA module

A

How to track cost object settlements

Working as SAP FICO consultant, many times you will have this question, when this cost object is settled? Whether this object settled before or not? What is receiver cost object?

We will check what are the important tables that can help to track down above information.  Each settlement run creates one document. That document header details is stored in AUAK table.

AUAK Document Header for Settlement

Every cost object in SAP has unique object number, that is used in 90% of tables. In AUAK you will not be able to search any document based on cost center number or WBSE number, you have enter relevant object number of that cost object.

Now where you can find the object number?

Object number is stored in master data table of every cost object. Cost center object number is available in CSKS table, WBSE object number is available in PRPS table. Sales order object number is available in VBAK table.

You can also use some naming convention for object number. Like Cost center object number is always starts with KS*, WBSE Object number starts with PR*, Sales order object number starts with VB*

So our analysis will start from getting object number respective cost object master data table.

Lets take e.g. you have one WBS element for which you want to check settlement details.

Then first you will go to WBS element master data table PRPS, get OBJNR number for that WBSE.

Then enter that OBJNR number in AUAK table.

You can also select settlement period and settlement year to narrow down selection criteria.

Then execute to see settlement details.

Here you can see between that time period how many times the cost object was settled. you will also get the settlement dates and document number.

But from this table you will not get who was the receiver of this settlement.

AUAA Settlement Document: Receiver Seg

In this table, you can enter the settlement document number (taken from AUAK) to see who the sender and receiver of the settlement was.

You can notice in our example settlement was done between WBSE and Asset.

What if you want to check settlement rule of any cost object?

We have other tables for that COBRA & COBRB. COBRA stores header details of settlement rule and COBRB stores item details of settlement rule.

In both table you can search using object number of cost object.

This is how COBRB will show settlement receiver details.

Important tables for settlement related transactions:

• AUAK Document Header for Settlement
• AUAA Settlement Document: Receiver Seg
• AUAB Settlement Document: Distribution
• COBRA Settlement Rule for Order Settlement
• AUAV Document Segment: Transactions
• AUAI Settlement Rules per Depreciation

With this would like to end this post here. Hope you enjoyed reading it. You can subscribe below to receive update of such new blogs.

Get update of new blog posts

Name

Country Your country Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire, Saint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos Islands Colombia Comoros Cook Islands Costa Rica Croatia Cuba Curacao Cyprus Czech Republic Democratic Republic of the Congo Denmark Djibouti Dominica Dominican Republic East Timor Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Isle of Man Israel Italy Ivory Coast Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Republic of the Congo Reunion Romania Russia Rwanda Saint Barthelemy Saint Helena Saint Kitts and Nevis Saint Lucia Saint Martin Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and the South Sandwich Islands South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu U.S. Virgin Islands Uganda Ukraine United Arab Emirates United Kingdom United States United States Minor Outlying Islands Uruguay Uzbekistan Vanuatu Vatican Venezuela Vietnam Wallis and Futuna Western Sahara Yemen Zambia Zimbabwe

Email address:

Leave this field empty if you're human:

you can stay connected with us on below platforms:

YouTube

LinkedIn FICO Page

LinkedIn ABAP Page

LinkedIn Logistics Page

Instagram

Basics

These two tables comprises 70% of bank reconciliation. FEBKO & FEBEP are very close to those who are working in Bank Management area. Even though it is very important tables still many don’t know much about these tables. So in this blogpost we will be covering, what is the use of FEBKO & FEBEP table? What are the major key fields in FEBKO & FEBEP tables?  How to get most out of these tables?

What is FEBKO & FEBEP table?

First lets understand the basic process of bank reconciliation in SAP. (Few can skip three paragraphs below if you already know about reconciliation process)

So there are two books of accounts involved in this process, one is of internal organization ledger maintained by organization and other is bank ledger maintained by bank. Two different parties trying to maintain same set of information in two different places. Whenever such situation happens, reconciliation jumps in. (this is something to be solved by blockchain technology).

User makes payment in SAP and book journal entry in Bank GL account (this is assumption). Same payment details send to bank (nowadays mostly electronically) via DME in SAP. Banks make the payment and book entry in their own ledger (this is actual). But sometime bank fail to make payment and don’t make any entry in their ledger, sometime bank make additional entries into their accounts for interest & charges (all are actual entries impacting your bank balance). But your SAP system don’t know about these transactions yet and so does the mismatch comes. And the reconciliation is required to match these two sets of books of accounts.

In SAP there are two ways (technically) to reconcile the balances. One is manually entering statement entries into system and reconciling through FF67. And other way is just uploading electronic bank statement in system through FF.5

If you want to learn entire process and configuration of manual & electronic bank reconciliation then you can read this ebook.

Now come back to our heading, what is FEBKO & FEBEP?

Before exploring these tables one should know that, Bank management is submodule of SAP FI, just like AA, AP, AR & GL. Hence just like in asset accounting, there are separate set of tables for asset accounting data and separate tables for storing accounting postings in GL area, in bank management also FEBKO & FEBEP tables are part of bank management and it does not store any accounting related data.

When you will run bank reconciliation transaction whether it is FF67 or FF.5, it will create some entries in FEBKO & FEBEP tables. Later on end user/ supervisor will check the bank statement data and post it to accounting (FEBAN process). At this stage accounting document tables BKPF & BSEG will be updated. Along with FEBKO & FEBEP with accounting document number.

FEBKO – Electronic Bank Statement Header Records

FEBEP – Electronic Bank Statement Line Items

As the description suggest FEBKO stores header records, it means for each bank reconciliation run in combination with house bank and account id FEBKO will have one line record generated.

FEBEP will have all the line items that are there in bank statements.

Fields of FEBKO table

FEBKO stores header records of bank statements in almost 109 fields. Obliviously we will not look into each and every, but we will see those which are important to know.

Whenever you will post bank statement via FF67 / FF.5 it will create one row in FEBKO table and multiple rows in FEBEP table depending on statement line records.

Now let’s see what information is available in FEBKO table:

Application field – It helps to filter records based on its application. You can see 0001 is for bank reconciliation. Similarly 0004 is used for account balance records (bank send these records as part of intra day statement). Lockbox & check deposit transactions can also be seen based on usage.

Sending bank will have account number and currency combination.

Statement ID is internally assigned unique statement number to each bank statement.

Next important field is short key, it is unique key assigned to each record of FEBKO irrespective of application. This field is used across tables and programs to identify unique statement record.

Let’s check one record:

In FEBKO –

In above screenshot you can see application number is 0001 so it is bank reconciliation entry. In sending bank field there is bank account number and currency (but we also have dedicated fields for account number and currency). In statement ID internal statement number is assigned. Short key is the unique number against this record, which you can use in any other tables/programs to find out this statement record.

Short key field is also a link between FEBKO & FEBEP table.

There is one program RFEBKA96 to delete bank statements from Bank management module (delete data from FEBKO, FEBEP.. etc)

If you execute this program in SE38:

You can see it is asking for two values one is application, 0001 for bank recon statements, 0004 for account balance statements

And other field is ID, it is nothing but short key.

So let me execute this program with above statement (application 0001 & ID 205978)

And here we go, got exact statement with statement id. now lets delete it from here.

It will show you how many tables data is deleted with this activity.

And you can notice all are bank related table, so this statement is disappeared from bank managent system but if this statement has posted any accounting document it will be still there. That will need manual reversal.

So mostly this is used when no accounting document is posted and you want to upload new statement.

Now coming back to FEBKO table fields

You can notice above there are several fields to filter out the statement records.

G/L – Of main bank account

Bank account – Bank account number

Statement no. – Bank statement number

House bank, Statement import date

Read eBook: SAP DME – A Simplified Guide

There is one more field that one should pay attention to and i.e. statement status (ASTAT)

This field will contain below values and by looking at it, you will be able to understand what is the posting status of this bank statement.

0 – Being entered
1 – Being post edited
2 – Entered =20
3 – Post edited=20
4 – Being posted
5 – Delete ID reset
7 – Posting incomplete
8 – Posting complete
9 – Deletion ID set

Whenever status will be 8 it means bank statement is fully posted without any error, Similarly 0 means statement is uploaded by selecting – ‘Do not post’ option. 7 – posting incomplete will tell that some of line items are not posted to accounting yet.

Next to statement status there are two fields A1 (Area 1) & A2 (Area 2). While defining posting rules you have option to define two accounting entries in two areas. It is used for clearing customer/vendor open line item along with incoming/outgoing bank GL line item. These fields will represent that two accounting entries, if marked with X means both entries are posted without any error.

(the above scenario is explained in more detail in this ebook)

Read Blog: Everything about derivation rule in SAP COPA

Field – statement number & statement date

These fields are populated from bank statement.

Statement number represents unique statement received for that specific bank account number. System also do not allow duplicate statement number for same bank account number.

Statement date is also taken from bank statement. It also represent the date on which transactions took place.

As we discussed FEBKO is header level table, so it also display the total debit & credit posting of statement and along with opening and closing balance.

These are all important field of FEBKO table, it helps a lot if you know what is the use of these fields & from where it is updated.

Next in FEBEP table we will see information about accounting documents, posting rules, interpretation algorithm

Fields of FEBEP table

This we will see in 2nd part of this blogpost.

Hope you enjoyed reading the post. You can subscribe to our newsletter to get update of new blogpost.

Get update of new blog posts

Name

Country Your country Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire, Saint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos Islands Colombia Comoros Cook Islands Costa Rica Croatia Cuba Curacao Cyprus Czech Republic Democratic Republic of the Congo Denmark Djibouti Dominica Dominican Republic East Timor Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Isle of Man Israel Italy Ivory Coast Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Republic of the Congo Reunion Romania Russia Rwanda Saint Barthelemy Saint Helena Saint Kitts and Nevis Saint Lucia Saint Martin Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and the South Sandwich Islands South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu U.S. Virgin Islands Uganda Ukraine United Arab Emirates United Kingdom United States United States Minor Outlying Islands Uruguay Uzbekistan Vanuatu Vatican Venezuela Vietnam Wallis and Futuna Western Sahara Yemen Zambia Zimbabwe

Email address:

Leave this field empty if you're human:

 you can stay connected with us on below platforms:

YouTube

LinkedIn FICO Page

LinkedIn ABAP Page

LinkedIn Logistics Page

Instagram

Introduction

We know that substitution and validation rules are used to validate and substitute data from master data & transactional data in SAP Finance Module. It is widely used in across sub-modules as it gives more flexibility to functional consultant further to end users via set maintenance.

I am presuming that you already know about substitution & validation rules, if not you can learn through these slides to understand basics of validation & substitution rules.

Steps in validation & substitution rule:

Validation–

1. Prerequisite
2. Check
3. Message

Substitution –

1. Prerequisite
2. Substitute

We can easily understand the function of both rules with below diagram:

We have option to put user exit in check step of validation and substitute step of substitution

So prerequisite remains open for use in both cases, so once the prerequisite rules are being match then only user exit will trigger to make changes (substitution) or to decide whether error msg should be displayed or not (validation)

Validation & Substitution rule transaction codes

You can remember transaction codes in below sequence

GGB0 – Validation rule creation

GGB1 – Substitution rule creation

GGB4 – Assignment of Validation & Substitution rules

These three transactions you all need for validation & substitution rules.

How to check user exit in validation/substitution

Let’s go to GGB0

This is one validation rule, where in check step, user exit ZEVAL is used.

By clicking on check, you can go inside check condition:

Select the user exit and click on ABAP Routine (as mentioned above)

And you will be redirected to the section code for this user exit.

Also Read: Everything about OB52 authorization group

Here you can setup breakpoint, to debug the errors or to find out how user exit is working.

But this should be somewhere assigned, for system to know which program to check for user exit. And that we will see now.

How to create user exit for substitution and validation in SAP FICO?

In GGB0/GGB1 transactions, we have predefined list of user exit to select from. But that should be created somewhere, right?

Go to transaction GCX2

In this transaction code GCX2, you have to assign GBLR (Validation) & GBLS (substitution) Application area to z programs in which ABAPer will be writing code for all user exits.

To create z program, you can copy standard program RGGBR000 

ABAP team will write user exit name in subroutine ‘GET_EXIT_TITLES’,

Under user exit code will be written as per the specification / requirements.

So in our example we used user exit ZEVAL. This name will be written in program assigned above in (GCX2). In this program there will be blocks of code for multiple user exits. In our case system will only run the program block of code written for ZEVAL user exit.

This is how user exit is link to program and it is used in substitution and validation rules.

This brings us to an end. Hope you enjoy and learn something. We publish such blogs once in every week, if you want to get notified of new blogposts, then you can register to below newsletter:

Get update of new blog posts

Name

Country Your country Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire, Saint Eustatius and Saba Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos Islands Colombia Comoros Cook Islands Costa Rica Croatia Cuba Curacao Cyprus Czech Republic Democratic Republic of the Congo Denmark Djibouti Dominica Dominican Republic East Timor Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Isle of Man Israel Italy Ivory Coast Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Korea Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Republic of the Congo Reunion Romania Russia Rwanda Saint Barthelemy Saint Helena Saint Kitts and Nevis Saint Lucia Saint Martin Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and the South Sandwich Islands South Korea South Sudan Spain Sri Lanka Sudan Suriname Svalbard and Jan Mayen Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu U.S. Virgin Islands Uganda Ukraine United Arab Emirates United Kingdom United States United States Minor Outlying Islands Uruguay Uzbekistan Vanuatu Vatican Venezuela Vietnam Wallis and Futuna Western Sahara Yemen Zambia Zimbabwe

Email address:

Leave this field empty if you're human:

You can also stay connected with us on below platforms:

YouTube

LinkedIn FICO Page

LinkedIn ABAP Page

LinkedIn Logistics Page

Instagram