Segement derivation issue in HR Postings
Hi,
we are derving segement using the BADI fagl_derive_segment its working properly for all FI postings
We are facing issue with HR Postings to FI that time its not taking from BADI its taking from somewhere we unable to identifing
please any body help on this
regards
i want to hold at document level in FI
for Eg: to day am going to post the document through HR to FI but the employer will make the pmt in the next month for the particular employee for time being we need to hold the document in FI... if u know the procedure plz let me know
Similar Messages
-
Cost Centre Derivation Issue at the time of PGI
Dear Experts,
At the time of Posting Post Goods Issue, SD Consultant is facing error that GL Account 6* requires assignment to a CO Object.
According to my understanding, system should derive Cost Centre at the time of P.G.I through following logic :
I have assigned Profit Centre : 999999 to the Cost Centre : ABCD and the said profit centre is being used at the time of Sales Order Posting. While doing PGI, system should derive cost centre data from Profit Centre Data which is used in Sales Order but currently system is not behaving like this.
Another way is to assign respective cost centres against COGS Gls through T-Code : OKB9 which is not right I think. Because how can we map Cost Centre Data with Profit Centre Data in order to get Profit Centre Wise Profitability Reports?
Please guide me any solution.
Regards,
SapnaHi Sapna,
For most cases, your COGS account should not be a cost element.
Secondly, if you want to make it a cost element, you will have to maintain OKB9 for it, either on the basis of profit center or plant.
System cannot pick cost center based on the cost center master data because there may be many cose centers assigned under the same profit center. There is no one-to-one mapping of cost center to profit center.
I would suggest you do not make COGS as cost element unless the sale order is an MTO sales order or business insists on it.
If business insists on it, then add the cost element to OKB9.
BR
Abhi -
I am running a view and I have been getting the following error:
ORA-01652: UNABLE TO EXTEND TEMP SEGMENT BY 1065 IN TABLESPACE SYSTEM.
Does anyone know any good methods of doing some analysis as to see what is going on. Any good SQL that someone can pass along??? any good links to one, or documentation. I am in a bind for time here, otherwise I would read the manuals....but you all know how it is when your under pressure.Hello Raman Gill ,
First of all, you should NEVER use tablespace SYSTEM as a temporary storage.
Check if you have a temporary tablespace:
SQL> SELECT TABLESPACE_NAME
2 FROM DBA_TABLESPACES
3 WHERE CONTENTS='TEMPORARY';
TABLESPACE_NAME
MY_TEMP
If you don't have any, create one asap.
If you have one, change your user's temporary tablespace to this one:
SQL> ALTER USER nom TEMPORARY TABLESPACE MY_TEMP;
User altered.
Next, check the temporary tablespace physical properties:
SQL> l
1 SELECT TABLESPACE_NAME, INITIAL_EXTENT, NEXT_EXTENT, MIN_EXTENTS, MAX_EXTENTS,
2 STATUS, EXTENT_MANAGEMENT, ALLOCATION_TYPE, SEGMENT_SPACE_MANAGEMENT
3 FROM DBA_TABLESPACES
4* WHERE TABLESPACE_NAME='TMPGNX1'
SQL> /
TABLESPACE_NAME INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS STATUS EXTENT_MAN ALLOCATIO SEGMEN
MY_TEMP 1048576 1048576 1 ONLINE LOCAL UNIFORM MANUAL
Check the values (tell us yours). If your RDBMS version is greater then or equal to 8, you should get "EXTENT_MANAGEMENT=LOCAL".
Check this.
Regards,
Yoann. -
E-Rec@ Job Postings are not reaching to Job Search !!!
Dear All,
We are facing an issue in Job Postings:
1.Published Job Posting (from 01.09.2011 to 27.09.2011) is not reaching to Job seasrch (under E-rec self services role >Employement Oppourtunites>Job Search.
2. If we EXTEND the period of Job posting (from 27.09.2011 to 31.10.2011) shld show under internal job search (under E-rec self services -->Job search). But here extended Job posting also not reaching to the Job search.
Can any one share the valuable opinion on this issue.
Thanks,
Asha....Hello Asha,
Please have a look at wiki page:
http://wiki.sdn.sap.com/wiki/display/ERPHCM/SES%28SearchEngine+Service%29
There you will find documents about several search problem topics discussed which may help you get the solution. Usually it is always good to check Report RCF_CHECK_SEARCH_SETTINGS and Report COM_SE_SEARCH_IIF_TEST and additionally the other links matching your issue.
Regards
Nicole -
PA Transfer Structure Issue while posting an accrual
Hi
I have an issue with accrual postings.
I am trying to post an accrual (reversing journal) but an error is coming up with PA Transfer structure has not mainted in COPA, but i have maintained inKEI1 and OKB9 also.
I really do not know as i have done this somany times previously.
Any help will be apprecaited highly.
cheers
krisHi Ashok
Thanks for your prompt reply.
I have checked and it is perfectly alright and i have just come to know that one of my team has transported a request wrongly that has messed up the system.
Anyway thanks for your time.
cheers
kris -
GM Derivation strategies (GMDERIVE) using statistical WBS elements
Hi experts!
I have a question related to GM derivation rules.
We need to derive Sponsor program throuhg WBS elements.
These objects are statistical in our system.
I note that SAP R/3 Derivation strategies need actual postings to derive Sponsor Program.
Is it true? What can i do to derive sponsor program from statistical CO objects? Maybe enhancement, function module?
Thanks in advance and best regardsHi
I did not explain properly. Postings are using cost centres and WBS elements, both in every posting. This means WBS postings are statistical.
As WBS elements correspond to sponsored programs I want to derive sponsored program from WBS. I tested in SAP and Sponsored program is derived from cost centre (actual) and not from WBS (statistical posting).
This means creating dozens of cost centres. Is there any way to derive Sponsored Program using GMderive from WBS elements?? I would like one direct way, assignment or derivation rule. Is it possible. I am afraid that only enhacements or function modules can be used. Has anybody used them for this?
Looking forward to hearing from you soon. -
Auto creation of Stor Location and Batch during stock upload via MI09
Hi Experts!
Please guide me to configure automatic creation of storage location and batch during stock count through mi09. Eg : I got material A in storage location 1000 and got batch 123 for this material. Then when i want to do the stock count, if i enter the storage location 2000 and batch 122 for this material, then system will auto create this storage location and batch in the master data.
I tried to configure it in OMJJ for storage location but it is not working. Please anyone guide me step by step how to configure it. Storage location and Batch.
Thanks.
Crystal.hi
check this
Create Storage Location Automatically
In this step, you specify whether the automatic creation of storage location data is allowed for goods issues and transfer postings.
This is advisable if you work with negative stocks and a material's first movement may be an outward movement.
Note that the reversal movement for a goods issue, for example, movement type 202 or 262, is not considered as an issue but as a receipt. If you only use the automatic creation of storage location data for reversals of goods issues, you do not have to allow negative stocks.
You have to allow automatic creation per plant first of all. You then have to explicitly allow the creation of storage location data for each movement type.
The storage location data is only created if the quantity is posted to 'standard' storage location stock. It is not created for receipts into a special stock (for example, into sales order stock).
Default settings
The standard system is set in such a way that the storage location data is created automatically for all types of receipts (goods receipt with/ without reference, stock transfers, intial entry of stock balances, reversal of goods issues, etc.).
Activities
1. Enter for each plant whether the automatic creation of storage location data is generally allowed.
2. Specify the movement types for which storage location data is created automatically. -
CRM 2015 Online, E-mail router performs so slow
Hi,
We are testing staging CRM 2015 Online. Email router for 2015 is installed in an online Windows 2012 server. We set Polling Period(seconds) 60 in Email Router Configuration Manager. However, when I send an e-mail, it takes
more than 20 minutes for the e-mail to arrive in my Gmail Inbox. Checking System Jobs and views regarding sent e-mail, all indicates that the e-mail was sent instantly. What shall I do to improve the Email Router performance? Thanks.Why are you using the email router if your Exchange Server is also Online? Dynamics CRM Online has Server Sync built in so it will directly communicate to Exchange Online. Much better solution than rolling up an email Router.
Also, if you don't have access to the Exchange server, I' doubt there's much you can do, since you don't have all the tools you need to troubleshoot the issue.
The postings on this site are solely my own and do not represent or constitute Hitachi Solutions' positions, views, strategies or opinions. -
Survey BSP application for never answered surveys
Hello Experts,<br />
I need to launch the BSP application CRM_SVY_SERVER for an order whose survey hasn't been answered yet.<br />
<br />
<b>Let me explain it better:</b><br />
The customer survey is properly setup, I'm able to answer it in CRMD_ORDER and see the results in CRM_SURVEY_SUITE.<br />
Now I need to enable answering for an order from the BSP application mentioned. But to create an answer in this application, relating to an order, I need to provide the valueguid of the answer (table CRM_SVY_DB_SVS, field VALUEGUID).<br />
<br />
<b>The main problem is:</b> The valueguid of the answer doesn't exist yet, as the survey wasn't answered yet. If I pass the order header guid (CRMD_ORDERADM_H-GUID) to the application, it says: "Survey not found".<br />
<br />
Is there a way to pass the order header guid (CRMD_ORDERADM_H-GUID) to the BSP application, so it creates the answer valueguid automatically? How this BSP application deals with surveys never answered?<br />
I think i'll have to code a little bit, to instantiate a survey and get a valueguid, before calling the BSP application. If you have any ohter idea, please let me know.<br/>
<br />
Sorry for the long text, its just a lot of details.<br />
<br />
Regards,<br />
Rafael Schaffer<br />
<br />Hi Rafael,
I'm not sure what's the error. I'll give sample code that's already working in my CRM system. It may give you some ideas.
REPORT ZTEST3.
INCLUDE:CRM_OBJECT_KINDS_CON,
CRM_OBJECT_NAMES_CON.
DATA: s_orderadm_h TYPE crmt_orderadm_h_com,
t_orderadm_h TYPE crmt_orderadm_h_comt,
s_input_fields TYPE crmt_input_field,
t_input_fields TYPE crmt_input_field_tab,
s_field_names TYPE crmt_input_field_names,
t_field_names TYPE crmt_input_field_names_tab,
s_activity_h TYPE CRMT_ACTIVITY_H_COM,
t_activity_h TYPE CRMT_ACTIVITY_H_COMT,
s_objects_to_save TYPE crmt_object_guid,
t_objects_to_save TYPE crmt_object_guid_tab,
s_saved_objects TYPE crmt_return_objects_struc,
t_saved_objects TYPE crmt_return_objects.
***** SURVEY**********
DATA: lead_guid TYPE guid_32,
activity_guid TYPE guid_32,
lead_id TYPE crmt_object_id,
activity_id TYPE crmt_object_id,
valueguid TYPE crm_svy_db_sv_guid,
valueversion TYPE crm_svy_db_sv_vers.
DATA: survey_value_guid TYPE guid_32,
it_values TYPE CRM_SVY_API_STRING_T.
DATA: et_survey_param TYPE CRM_SVY_API_PARAMETER_T,
it_survey_param TYPE CRM_SVY_API_PARAMETER_T,
wa_survey_param TYPE CRM_SVY_API_PARAMETER,
cs_evaluation_infos TYPE CRM_SVY_RE_TAR_OBJ.
DATA: o_survey_runtime TYPE REF TO cl_crm_svy_runtime,
o_surveyvalues TYPE REF TO cl_crm_svy_values,
t_application_params TYPE crm_svy_api_parameter_t,
t_all_values TYPE survy_t_all_values.
DATA: value TYPE string.
****** END SURVEY *****
DATA: guid_h TYPE CRMT_OBJECT_GUID,
guid_i TYPE CRMT_OBJECT_GUID,
process_type TYPE CRMT_PROCESS_TYPE,
item_type TYPE CRMT_ITEM_TYPE,
object_type TYPE CRMT_SUBOBJECT_CATEGORY,
process_mode TYPE CRMT_MODE,
it_survey_ui TYPE CRMT_SURVEY_UI_TAB.
* Fill required structures
CLEAR: s_orderadm_h, t_orderadm_h.
s_orderadm_h-object_id = 'BUS2000126'."'BUS2000108'.
s_orderadm_h-process_type = 'ZCRC'.
s_orderadm_h-description = 'Description nih'.
APPEND s_orderadm_h TO t_orderadm_h.
****** ADD FIRST PROPERTY TO INPUT FIELDS -> ACTIVITY_H
CLEAR: s_input_fields, t_input_fields .
s_input_fields-ref_kind = gc_object_kind-orderadm_h."'A'.
s_input_fields-objectname = gc_object_name-activity_h."'ACTIVITY_H'."'LEAD_H'.
CLEAR: s_field_names, t_field_names.
* in order to get location and external reference no values, their fieldnames must be added to these
s_field_names-fieldname = 'ACT_LOCATION'. APPEND s_field_names TO t_field_names.
s_field_names-fieldname = 'CATEGORY'. APPEND s_field_names TO t_field_names.
s_field_names-fieldname = 'EXTERN_ACT_ID'. APPEND s_field_names TO t_field_names.
s_input_fields-field_names = t_field_names.
APPEND s_input_fields TO t_input_fields.
****** END FIRST PROPERTY TO INPUT FIELDS -> ACTIVITY_H
****** ADD SECOND PROPERTY TO INPUT FIELDS -> ORDERADM_H
CLEAR: s_input_fields.
CLEAR: s_field_names, t_field_names.
s_input_fields-ref_kind = gc_object_kind-orderadm_h ."'A'.
s_input_fields-objectname = gc_object_name-orderadm_h."'ORDERADM_H'.
*Subtable FIELD_NAMES
s_field_names-fieldname = 'DESCRIPTION'. APPEND s_field_names TO t_field_names.
*/Subtable FIELD_NAMES
s_input_fields-field_names = t_field_names.
APPEND s_input_fields TO t_input_fields.
****** END ADD SECOND PROPERTY TO INPUT FIELDS -> ORDERADM_H
CLEAR: s_activity_h, t_activity_h.
s_activity_h-ACT_LOCATION = 'Location nih'.
s_activity_h-EXTERN_ACT_ID = 'Extern ref no nih'.
s_activity_h-category = 'ZC1'.
APPEND s_activity_h TO t_activity_h.
* Create activity
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
EXPORTING
* it_lead_h = t_lead_h
it_activity_h = t_activity_h
* it_partner = t_partner_h
* iv_collect_exceptions = ''
CHANGING
ct_orderadm_h = t_orderadm_h
ct_input_fields = t_input_fields
EXCEPTIONS
error_occurred = 1
document_locked = 2
no_change_allowed = 3
no_authority = 4
OTHERS = 5.
IF sy-subrc <> 0.
* MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
* WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
* Get GUID of created LEAD for later saving
READ TABLE t_orderadm_h INTO s_orderadm_h INDEX 1.
CLEAR: s_objects_to_save.", t_objects_to_save.
*s_objects_to_save = lead_guid = s_orderadm_h-guid.
s_objects_to_save = activity_guid = s_orderadm_h-guid.
APPEND s_objects_to_save TO t_objects_to_save.
*** continue to next post
because of SDN forum limitation (2500 line of code from [this link|Formatting issues in SDN postings (character limit and code tags);) , please see my next post to continue my code -
New GL documentaion in ECC 6.0
I appreciate if someone can post some notes or documentation on New GL in 6.0.
Thank you
Kumar KHello
Take a print out or copy desktop and go through the below documentation:
General Ledger Accounting (FI-GL) (New)
Purpose
The central task of G/L accounting is to provide a comprehensive picture of external accounting and accounts. Recording all business transactions (primary postings as well as settlements from internal accounting) in a software system that is fully integrated with all the other operational areas of a company ensures that the accounting data is always complete and accurate.
Beyond fulfilling the legal requirements, General Ledger Accounting also fulfills other requirements for modern accounting:
Parallel Accounting
General Ledger Accounting allows you to perform parallel accounting by managing several parallel ledgers for different accounting principles.
Integration of Legal and Management Reporting
In General Ledger Accounting, you can perform internal management reporting in parallel with legal reporting. For this purpose, the Profit Center Accounting functions are integrated with General Ledger Accounting. Furthermore, you can generate financial statements for any dimension (such as profit center).
Segment Reporting
General Ledger Accounting supports the segment reports required by the accounting principles IFRS (International Financial Reporting Standards) and US GAAP (Generally Accepted Accounting Principles). For this purpose, General Ledger Accounting contains the Segment dimension.
Cost of Sales Accounting
You can perform cost of sales accounting in General Ledger Accounting. For this purpose, General Ledger Accounting contains the Functional Area dimension.
Integration
General Ledger Accounting is integrated with all application components of the SAP System that generate posting data of relevance to General Ledger Accounting:
Asset Accounting (FI-AA)
FI Accounts Receivable and Accounts Payable
Controlling (CO)
Materials Management (MM)
Human Capital Management (HCM)
Treasury and Risk Management (TRM)
Travel Management (FI-TV)
Public Sector Management - Funds Management Government (PSM-FM)
When you activate the business function set Public Sector (EA-PS) and the global functions Funds Management (PSM-FM), you obtain a separate set of tables containing the Public Sector account assignments, such as fund and grant.
Features
General Ledger Accounting comprises the following functions for entering and evaluating posting data:
Choice between group level or company level
Automatic and simultaneous posting of all subledger items in the appropriate general ledger accounts (reconciliation accounts)
Simultaneous updating of the parallel general ledgers and of the cost accounting areas
Real-time evaluation of and reporting on current posting data, in the form of account displays, financial statements with different balance sheet versions, and additional analyses.
In this way, General Ledger Accounting automatically serves as a complete record of all business transactions. It is the central and up-to-date component for reporting. Individual transactions can be checked at any time in real time by displaying the original documents, line items, and monthly debits and credits at various levels such as:
Account information
Journals
Totals/transaction figures
Balance sheet/profit and loss evaluations
Configuring New General Ledger Accounting
Purpose
Before you can start working with the functions of New General Ledger Accounting, you have to activate them and make the general settings for Accounting. Furthermore, you have to configure the ledgers you use in General Ledger Accounting. On the basis of this data, you set up the integration with Controlling (CO) and, where applicable, your parallel accounting.
Process Flow
1. ...
1. 1. Activate New General Ledger Accounting. For information on this, see Activating General Ledger Accounting.
2. 2. Make the general settings for the fiscal year, the posting periods, and the currencies.
You find the settings for the fiscal year and posting periods in Customizing for Financial Accounting (New) under Financial Accounting Global Settings (New) ® Ledgers ® Fiscal Year and Posting Periods.
3. 3. Configure your ledgers.
4. 4. Define the integration with Controlling.
5. 5. Where applicable, set up parallel accounting.
Activating General Ledger Accounting
Use
To make the settings and use the functions in General Ledger Accounting, you have to activate it. To do this, in Customizing choose Financial Accounting ® Financial Accounting Global Settings ® Activate New General Ledger Accounting.
Features
Activating General Ledger Accounting has the following effects:
● The Customizing settings for General Ledger Accounting appear in the SAP Reference IMG. You access the settings under Financial Accounting (New) ® Financial Accounting Global Settings (New) and General Ledger Accounting (New).
● The General Ledger Accounting functions appear in the SAP Easy Access menu under Accounting ® Financial Accounting ® General Ledger.
● The tables for new General Ledger Accounting are activated and updated.
In the standard system, the tables from classic General Ledger Accounting (GLT0) are updated as well as the tables in new General Ledger Accounting during the activation. This enables you to perform a ledger comparison during the implementation of new General Ledger Accounting to ensure that your new General Ledger Accounting has the correct settings and is working correctly. To compare ledgers, in Customizing choose Financial Accounting Global Settings (New) ® Tools ® Compare Ledgers.
We recommend that you deactivate the update of tables for classic General Ledger Accounting once you have established that new General Ledger Accounting is working correctly. To do this, in Customizing choose Financial Accounting Global Settings (New) ® Tools ® Deactivate Update of Classic General Ledger.
In some of the General Ledger Accounting functions, you can use the Ledger Group field, such as for posting.
● The following functions are available:
Document Splitting
Real-Time Integration of Controlling with Financial Accounting
Functions for Profit Center Accounting (such as statistical key figures and transfer prices)
Fiscal Year
Definition
Usually a period of twelve months for which a company regularly creates financial statements and checks inventories.
The fiscal year may correspond exactly to the calendar year, but this is not obligatory.
Under certain circumstances a fiscal year may be less than twelve months (shortened fiscal year).
Structure
A fiscal year is divided into posting periods. Each posting period is defined by a start and a finish date. Before you can post documents, you must define posting periods, which in turn define the fiscal year.
In addition to the posting periods, you can also define special periods for year-end closing.
In General Ledger Accounting, a fiscal year can have a maximum of twelve posting periods and four special periods. You can define up to 366 posting periods in the Special Purpose Ledger.
Use
In order to assign business transactions to different time periods, you must define a fiscal year with posting periods. Defining the fiscal year is obligatory.
You define your fiscal year as fiscal year variants which you then assign to your company code. One fiscal year variant can be used by several company codes.
You have the following options for defining fiscal year variants:
Fiscal year same as calendar year
Fiscal year differs from calendar year (non-calendar fiscal year). The posting periods can also be different to the calendar months.
You define your fiscal year variants in Customizing for Financial Accounting as follows: Financial Accounting Global Settings  Fiscal Year  Maintain Fiscal Year Variant (Maintain Shortened Fiscal Year)
Integration
When you enter a posting, the system automatically determines the posting period. For more information, see Determining Posting Periods During Posting
In the general ledger, the system saves the transaction figures for all accounts for each posting period and each special period separately according to debits and credits. In the Special Purpose Ledger component (FI-SL), you can save the transaction figures as a balance.
Currencies
Definition
Legal means of payment in a country.
Use
For each monetary amount that you enter in the SAP System, you must specify a currency. You enter currencies as the ISO standards, for example, USD for US dollar.
You define currencies in Customizing. To do this, choose General Settings  Currencies  Check Currency Codes.
In Financial Accounting, you have to specify for each of your company codes, in which currency ledgers should be managed. This currency is the national currency of the company code, that is, the local currency (or company code currency). From a company code view, all other currencies are then foreign currencies.
You can manage ledgers in two parallel currencies in addition to the local currency, for example, group currency or hard currency. For more information, see Parallel Currencies.
In order for the system to translate amounts into various currencies, you must define exchange rates. For each currency pair, you can define different exchange rates and then differentiate between them by using exchange rate types.
Integration
In Financial Accounting, currencies and currency translation are relevant in the following circumstances:
General Ledger Accounts Receivable and Accounts Payable
Account master data Defining account currencies
Defining reconciliation accounts
Posting Posting documents in foreign currency
Clearing Clearing open items in foreign currency
Foreign currency valuation Foreign currency valuation
Parallel Currencies in Financial Accounting
Use
In Financial Accounting, you can define up to two parallel currencies in addition to the local currency. Your ledgers are thereby managed in these parallel currencies in addition to the local currency.
You can use various different currency types as parallel currencies. You define the currency for a currency type when you define the organizational units.
Group Currency
You define the group currency when you define your client.
Company Currency
You define the company currency when you define the company that is assigned to your company code.
Hard Currency
You define the hard currency when you define the country that your company code is assigned to.
Index-Based Currency
You define the index currency when you define the country that your company code is assigned to.
You can use a maximum of two parallel currencies (second and third local currencies).
If you have defined the group currency as the second local currency, this has no additional effects. In all other cases, in the application component Special Purpose Ledger you have to define an additional ledger in which transaction figures are managed.
Features
If you manage your ledgers in parallel currencies, this has the following effects:
During posting, the amounts are also saved in the parallel currencies. The amounts are translated automatically, but you can also enter them manually.
G/L account transaction figures are also updated in the parallel currencies.
Exchange rate differences also arise in the parallel currencies.
You can also carry out a foreign currency valuation in the parallel currencies.
Activities
To define parallel currencies, proceed as follows in Customizing for Financial Accounting: Financial Accounting Global Settings ® Company Code ® Parallel Currencies.
Local Currency Changeover (FI-GL) (New)
Use
In New General Ledger Accounting, you can change your local currencies to the euro. For more information, see the general documentation for Local Currency Changeover.
Prerequisites
You find these reports in Customizing for Cross-Application Components once you have activated New General Ledger Accounting.
Features
Translating local currency amounts can lead to rounding differences, which can mean that the converted currency amounts for each document do not produce a balance of zero. This is corrected automatically with the insertion of a correction document item with an account assignment relevant to general ledger accounting. These processes are run automatically for all phases of the local currency changeover.
If you migrate data from classic General Ledger Accounting into New General Ledger Accounting, note that you do not perform the euro changeover in the year of the migration. Clear all migrated open items in the migration year and perform the local currency changeover in the year following the migration. Consequently, in the year in which you then perform the local currency changeover, you no longer have any open items prior to the migration event.
Activities
You find the programs for the local currency changeover in the Implementation Guide for Cross-Application Components under European Monetary Union: Euro ®Local Currency Changeover.
See the important notes in the general documentation and in the documentation of the IMG activities.
Configuring Ledgers
Purpose
Before you can start working with the functions of new General Ledger Accounting, you have to configure the ledgers. When you have planned the data structure for General Ledger Accounting, you can reflect it in Customizing in your SAP system.
You configure ledgers. The term ledger describes a technical view of a database table and it is used in this documentation as a synonym for a general ledger.
Prerequisites
You have activated New General Ledger Accounting .
You have made the general settings for the fiscal year, the posting periods, and the currencies.
Process Flow
To configure the ledgers for General Ledger Accounting, proceed as follows:
2. ...
6. 1. Define the standard fields that you require. You make the settings in Customizing for Financial Accounting (New) under Financial Accounting Global Settings (New) ® Ledgers ® Fields ® Standard Fields.
7. 2. You can also define your own fields. For more information, see Customer Field.
8. 3. Create your ledgers and ledger groups and configure them. See Ledger and Ledger Group.
9. 4. Assign the desired scenarios to your ledgers. Read the information under Scenario in General Ledger Accounting.
Result
You have configured ledgers in General Ledger Accounting and can now create your master data (such as chart of accounts, G/L accounts, segment, and profit center).
Totals Tables
Definition
A totals table is a database table in which totals records are stored.
A totals table is used in General Ledger Accounting as the basis for your parallel ledgers. It offers a number of dimensions. SAP delivers the totals table FAGLFLEXT for General Ledger Accounting in the standard system.
Use
Standard Totals Table
When you activate new General Ledger Accounting, the totals records in General Ledger Accounting are updated in the standard totals table FAGLFLEXT. This totals table is deployed in functions such as planning and reporting.
SAP recommends working with the standard totals table delivered. In this way, you ensure that you can use the functions based on the standard totals table.
Own Totals Table
If the standard totals table delivered does not fulfill your requirements, you can define your own totals table. To do this, in Customizing for Financial Accounting (New), choose Financial Accounting Global Settings (New) ® Ledgers ® Fields ® Customer Fields® Include Fields in Totals Table. Choose Extras ® Create Table Group.
When a totals table is created, the system simultaneously generates the corresponding line items table. For more information on creating table groups, see the SAP Library under Financials ® Financial Accounting ® Special Purpose Ledger ® Configuration ® Database Tables ® Database Definition and Installation.
You can include your own dimensions in the totals table. For more information, see Customer Fields.
Ledger
Definition
A ledger is a section of a database table. A ledger only contains those dimensions of the totals table that the ledger is based on and that are required for reporting.
Use
In General Ledger Accounting, you can use several ledgers in parallel. This allows you to produce financial statements according to different accounting principles, for example. You create a ledger for each of the general ledgers you need.
A ledger uses several dimensions from the totals table it is based on. Each dimension of the totals table represents a subset of the coding block. You can also include customer fields in your ledgers. To do this, you have to add the customer field to the coding block and then include this field in the totals table that the ledger is based on. For more information, see Customer Fields.
You define your ledgers in Customizing for Financial Accounting (New) under Financial Accounting Global Settings (New) ® Ledgers ® Ledgers. When you create a ledger, the system automatically creates a ledger group with the same name.
Structure
You must designate one ledger as the leading ledger.
Parallel ledgers:
Leading ledger
The leading ledger is based on the same accounting principle as that of the consolidated financial statements.
If you use the account approach for parallel accounting, you post all data to the leading ledger.
This leading ledger is integrated with all subsidiary ledgers and is updated in all company codes. This means that it is automatically assigned to all company codes.
In each company code, the leading ledger receives exactly the same settings that apply to that company code: the currencies, the fiscal year variant, and the variant of the posting periods. You can define a second and third parallel currency for your leading ledger for each company code. In Customizing for Financial Accounting (New), choose Financial Accounting Global Settings (New) ® Ledgers ® Ledgers ® Define Currencies of Leading Ledger.
Non-leading ledger
The non-leading ledgers are parallel ledgers to the leading ledger. They can be based on a local accounting principle, for example. You have to activate a non-leading ledger for the individual company codes.
Posting procedures with subledger or G/L accounts managed on an open item basis always affect all ledgers. This means that you cannot perform ledger-specific postings to subledger or G/L accounts managed on an open item basis. If you manage G/L accounts on an open item basis to monitor accounting aspects such as reserve allocations and reversals, you need to take additional measures in your internal controls system.
Non-leading ledgers can have different fiscal year variants and different posting period variants per company code to the leading ledger of this company code. The second and third currency of the non-leading ledger must be a currency that is managed as second or third currency in the respective company code. However, you do not have to have a second and third currency in the parallel ledgers; these are optional. Alternative currencies are not possible.
For more information about parallel currencies, see Managing Parallel Currencies in Parallel Ledgers.
Rollup ledgers:
In addition to your parallel ledgers, you can also define a rollup ledger for special reporting purposes. In a rollup ledger, you can combine summarized data from other ledgers in General Ledger Accounting. This enables you to compile cumulated reports on different ledgers.
Day ledgers:
You use a day ledger to create a day ledger if you want to create reports for average balances (reports for displaying average daily balances). You can activate the day ledger for drilldown reporting.
You may not define day ledgers as the leading ledger or as the representative ledger in a ledger group.
Example
You create your consolidated financial statements in accordance with the IAS accounting principles. Your individual company codes apply the local accounting principles US GAAP or German HGB to produce their financial statements. You therefore create three ledgers:
Ledger LL (leading ledger) that is managed according to the group accounting principle
Ledger L1 (non-leading ledger) that you activate for all company codes that apply US GAAP
Ledger L2 (non-leading ledger) that you activate for all company codes that apply HGB
Making Settings for Ledgers
Use
In General Ledger Accounting, you can use several parallel general ledgers. You do this to produce financial statements according to different accounting principles, for example. You create a ledger for each of the general ledgers you need. You must check the settings of your leading ledger even if you do not use parallel ledgers.
Procedure
You make the settings listed below in Customizing for Financial Accounting (new) under Financial Accounting Global Settings (New) ® Ledgers ® Ledgers.
3. ...
10. 1. Define Ledgers for General Ledger Accounting
Define your ledgers and designate one ledger as leading ledger (see also Ledgers).
When you create a ledger, the system automatically creates a ledger group with the same name.
11. 2. Define Currencies of Leading Ledger
If necessary, define a second and third parallel currency for your leading ledger for each company code.
For more information, see Managing Parallel Currencies in Parallel Ledgers.
The following settings are optional:
12. 3. Define and Activate Non-Leading Ledgers
If you use parallel ledgers, define your non-leading ledgers. If necessary, create alternative additional currencies or an alternative fiscal year variant.
13. 4. Assign Scenarios and Customer Fields to Ledgers
Here you can assign the following to your ledgers:
 Scenarios
 Customer Fields
 Versions
In versions, you define general settings for the ledger that are fiscal year-dependent. You specify whether actual data is recorded, whether manual planning is allowed, and whether planning integration with Controlling is activated.
14. 5. Activate Cost of Sales Accounting
Activate cost of sales accounting for your company codes if required. If you do this, the functional area is derived and updated for postings in these company codes. For information about the prerequisites for cost of sales accounting, see the documentation for this IMG activity.
15. 6. Define Ledger Group
You can combine any number of ledgers in a ledger group. In this way, you simplify the tasks in the individual functions of General Ledger Accounting.
For more information, see Ledger Groups.
Result
You have made all of the settings required for your ledgers.
For parallel accounting, you can now assign an accounting principle to your ledgers.
Ledger Groups
Definition
A ledger group is a combination of ledgers for the purpose of applying the functions and processes of General Ledger Accounting to the group as a whole.
Use
You can combine any number of ledgers in a ledger group. In this way, you simplify the tasks in the individual functions and processes of General Ledger Accounting. For example, you can make a posting simultaneously in several ledgers.
In some General Ledger Accounting functions, you can only specify a ledger group and not individual ledgers. This has the following consequences for the creation of your ledger groups:
Each ledger is also created automatically as a ledger group of the same name. You can use these automatically created ledger groups to process an individual ledger.
You only have to create those ledger groups that you want to process together in a function using processing for several ledgers.
If you do not enter a ledger group, processing is performed automatically for all ledgers. You therefore do not need to create a ledger group for all ledgers.
You define your ledger groups in Customizing for Financial Accounting (new) under Financial Accounting Global Settings (New) ® Ledgers ® Ledgers ® Define Ledger Group.
Structure
Representative Ledger of a Ledger Group
When you define each ledger group, you have to designate one of the assigned ledgers as the representative ledger for that ledger group. The system uses the representative ledger to determine the posting period during posting and to check whether the posting period is open. The posting is then made to the assigned ledgers of the ledger group using the appropriate fiscal year variant for each individual ledger.
When the posting periods of the representative ledger are open, the postings are made to all other assigned ledgers, even if their posting periods are closed.
The following rules apply for the specification of the representative ledger of a ledger group:
If the ledger group has a leading ledger, the leading ledger must be designated as the representative ledger.
If the ledger group does not have a leading ledger, you must designate one of the assigned ledgers as the representative ledger. During posting, the system uses the fiscal year variant of the company code to check whether the selection is correct:
 If all ledgers in the ledger group have a different fiscal year variant to that of the company code, you can designate any ledger as the representative ledger.
 If one of the ledgers in the ledger group has the same fiscal year variant as that of the company code, you must designate that ledger as the representative ledger.
You may be unable to use the same ledger group for all company codes. In that case, you have to create separate ledger groups and, in each one, designate a different ledger as the representative ledger.
Day Ledger
Definition
A day ledger is a totals table with a fiscal year variant of 366 periods and containing all original postings for the general ledger.
Use
You create a day ledger if you want to create reports for average balances (reports for displaying average daily balances). You can activate the day ledger for drilldown reporting. For more information, refer to SAP Note 599692.
You may not define day ledgers as the leading ledger or as the representative ledger in a ledger group.
Example
When defining a cycle for a ledger, you can specify a ledger group.
You can define this ledger group so that it contains the source ledger and the day ledger.
Note, however, that an allocation is posted as period-end closing on the last day of the period.
Let us assume that you have made the following postings:
Date Amount in EUR
January 5 100
January 8 200
January 17 300
February 5 400
This results in the following balances in the ledgers:
Leading Ledger (16 Periods)
Period/Amount Day Ledger
Period/Amount
1 / 600 5 / 100
2 / 400 8 / 200
17 / 300
36 / 400
If you perform the allocation for January (postings up until January 31), you distribute EUR 600 to other units:
Leading Ledger (16 Periods)
Period/Amount Day Ledger
Period/Amount
1 / 0 5 / 100
2 / 400 8 / 200
17 / 300
31 / -600
36 / 400
For more information on allocation in New General Ledger Accounting, see Allocation.
Customer Field
Definition
A customer field is a database table field that is created and defined by the customer.
Use
You can include your own fields (such as the field Region) in the data structure of General Ledger Accounting. To do so, you have to make various Customizing settings. For more information, see Defining Customer Fields.
During posting, you can fill your customer fields in the following ways:
Automatic Derivation
You can have the system derive your customer fields automatically for all postings that are relevant for General Ledger Accounting.
Manual Posting
In the G/L account posting functions delivered in General Ledger Accounting, you find your customer fields as account assignment objects. For these fields to be available in the G/L account posting (Enjoy) as well, you need to assign your customer fields to the entry variant that you use during posting. For this, choose in Customizing General Ledger Accounting (New) ® Business Transactions ® G/L Account Posting - Enjoy ® Include Customer Fields in Enjoy Transactions.
In other application components (such as Logistics and Controlling), however, you cannot make postings directly to your customer fields.
Defining Customer Fields
To include a customer field in the data structure of General Ledger Accounting, you have to make various settings in Customizing for Financial Accounting (New):
4. ...
16. 1. Include the field in the coding block.
For this, choose in Customizing Financial Accounting Basic Settings (New) ® Ledgers ® Fields ® Customer Fields ® Edit Coding Block.
17. 2. Include the field in the totals table that your ledgers are based on.
For this, choose in Customizing Financial Accounting Basic Settings (New) ® Ledgers ® Fields ® Customer Fields ® Include Fields in Totals Table.
18. 3. Assign the field to the desired ledgers.
For this, choose in Customizing Financial Accounting Basic Settings (New) ® Ledgers ® Ledger ® Assign Scenarios and Customer Fields to Ledgers.
Scenario in General Ledger Accounting
Definition
The scenario combines Customizing settings from different business views. Each business view specifies which posting data is transferred from different application components in General Ledger Accounting, such as cost center update or profit center update.
Use
You assign the desired scenarios to your ledgers. For each ledger, you define which fields are filled with posting data from other application components.
To assign a scenario to a ledger, in Customizing for Financial Accounting (New), choose Financial Accounting Global Settings (New) ® Ledgers ® Ledgers ® Assign Scenarios and Customer Fields to Ledgers (see also Making Settings for Ledgers).
SAP delivers a number of scenarios in the standard system. You cannot define your own scenarios.
To display the fields for a scenario, in Customizing for Financial Accounting (New), choose Financial Accounting Global Settings (New) ® Ledgers ® Fields ® Display Scenarios for General Ledger Accounting.
Structure
For each scenario, the system transfers the posting data relevant for General Ledger Accounting from the actual and plan documents.
Overview of the Scenarios Delivered by SAP
Scenario Fields Filled Technical Field Name
Cost center update Cost center
Sender cost center RCNTR
SCNTR
Preparation for consolidation Trading partner
Transaction type RASSC
RMVCT
Business area Business area
Trading partner business area RBUSA
SBUSA
Profit center update Profit center
Partner profit center PPRCTR
PRCTR
Segmentation Profit center
Segment
Partner segment PRCTR
PSEGMENT
SEGMENT
Cost of sales accounting Functional area
Partner functional area RFAREA
SFAREA
You have to set up cost of sales accounting. The Functional Area field is not filled automatically by the assignment of the scenario to your ledger. For more information, see Activating Cost of Sales Accounting.
Integration
If you use document splitting, define the fields of a scenario that you have assigned to the ledger as document splitting characteristics.
For more information, see Making Settings for Document Splitting.
Cost of Sales Accounting
Use
The profit and loss statement of an organization can be created according to two different procedures:
Period accounting
Cost of sales accounting
Cost of sales accounting compares the sales revenue for an accounting period with the manufacturing costs of the activity. The expenses are allocated to the commercial functional areas (manufacturing, sales and distribution, administration, and so on). Expenses and revenues that cannot be assigned to the functional areas are reported in further profit and loss items, sorted according to expense and revenue type.
With this type of grouping, cost of sales accounting identifies where costs originate in a company. It therefore portrays the commercial purpose of the expense.
Prerequisites
You have made the required settings in Customizing. For more information, see Activating Cost of Sales Accounting.
Real-Time Integration of Controlling with Financial Accounting
Use
During allocations in Controlling, most of the postings created do not affect Financial Accounting. These postings do not update any G/L account transaction figures; they are postings within Controlling. If, however, an allocation in Controlling leads to a change in the functional area or any other characteristic (such as Profit Center or Segment) that is relevant for evaluations in Financial Accounting, a shift occurs between the affected items in the profit and loss statement. For this reason, this information has to be transferred to Financial Accounting. This reconciliation between Controlling and Financial Accounting takes place by means of real-time integration.
As a result of real-time integration, all Controlling documents that are relevant for General Ledger Accounting are transferred from Controlling to General Ledger Accounting in real time. This means that Financial Accounting is always reconciled with Controlling.
A document is created in Financial Accounting for each posting in Controlling. This means that the detailed information contained in the CO documents is always available in reports in New General Ledger Accounting. This information can be sorted by the following, for example:
● Functional area
● Cost center
● Internal order
Integration
Real-time integration replaces the reconciliation postings from the reconciliation ledger. Consequently, you do not need a reconciliation ledger.
If, however, you do not set the Reconciliation Ledger Active indicator in Customizing for the controlling area, you cannot use the reports belonging to report groups 5A* (5AA1-5AW1). You set this indicator in Customizing for Controlling under General Controlling ® Organization ® Maintain Controlling Area. The reconciliation ledger serves as the data source for reports belonging to the report groups 5A*. You find these reports in the SAP Easy Access menu under Accounting ® Controlling ® Cost Element Accounting ® Information System ® Reports for Cost and Revenue Element Accounting.
Replacement reports are available as follows:
● You find the reports in the SAP Easy Access menu under Accounting ® Controlling ® Cost Element Accounting ® Information System ® Reports for Cost and Revenue Element Accounting (New).
● You can create additional reports in report group 5A21. You can assign the report group to any drilldown report of New General Ledger Accounting using the report-report interface.
● From the report Financial Statements Actual/Actual Comparison, you can call up the report Cost Elements: Breakdown by Company Code. You find the report Financial Statement: Actual/Actual Comparison in the SAP Easy Access menu under Accounting ® Financial Accounting ® General Ledger ® Information System ® General Ledger Reports (New) ® Balance Sheet/Profit and Loss Statement/Cash Flow ® General ® Actual/Actual Comparisons.
You can define account determination for each controlling area. You do this in Customizing for Financial Accounting (New) under Financial Accounting Global Settings (New) ® Ledgers ® Real-Time Integration of Controlling with Financial Accounting ® Account Determination for Real-Time Integration. In this way, you use the same account determination as for the reconciliation ledger (transaction OK17). You can then use the reconciliation ledger reports to compare FI balances with CO balances.
Prerequisites
If you use real-time integration in at least one company code, you need to have activated company code validation for the related controlling area. You do this in Customizing for Controlling under General Controlling ® Organization ® Maintain Controlling Area ® Activate Components/Control Indicators. Otherwise, the reconciliation between Financial Accounting and Controlling at company code level is not possible.
In Customizing for Financial Accounting (New), you have processed the IMG activities under Financial Accounting Global Settings (New) ® Ledgers ® Real-Time Integration of Controlling with Financial Accounting.
Activate real-time integration for all company codes between which you want to make CO-internal allocations.
In the IMG activity Define Variants for Real-Time Integration, do not select all CO line items for transfer. If the same line items are to be transferred as through the reconciliation posting from the reconciliation ledger, select the following line items:
● Cross-Company Code
● Cross-Business Area
● Cross-Functional Area
● Cross-Fund (if you use Public Sector Management)
● Cross-Grant (if you use Public Sector Management)
Features
Value flows within Controlling that are relevant for General Ledger Accounting such as assessments, distributions, confirmations, and CO-internal settlements are transferred immediately. The FI documents are posted with the business transaction COFI. They contain the number of the CO document. This means that you can call up the CO document from the FI document, and vice versa.
Activities
If a document could not be transferred because the posting period was blocked in Financial Accounting or no account was found, for example, the document is included in a postprocessing worklist. You need to check this worklist regularly and process any documents in it. From the SAP Easy Access menu, choose Accounting ® Financial Accounting ® General Ledger ® Corrections ®Post CO Documents to FI.
Example
An internal order for business area 0001 is settled to a cost center of business area 0002. The document from this allocation is transferred in real time to Financial Accounting.
Parallel Accounting
Purpose
You can portray parallel accounting in your SAP System. This enables you to perform valuations and closing preparations for a company code according to the accounting principles of the group as well as other accounting principles, such as local accounting principles.
To simplify matters, this documentation assumes two parallel accounting principles.
Implementation Considerations
You can use the following approaches to portray parallel accounting in your SAP System.
Portrayal Using Additional Accounts
Portrayal Using Parallel Ledgers
You can also continue to use the option for portraying parallel accounting using an additional company code. However, this approach is not supported by all application components. For more information, see Portrayal Using Additional Company Code.
The solution scenarios described require that you have customized the application components that you use consistently.
For information about the settings for parallel accounting for the individual components, see the links in the list under Integration.
Integration
Parallel accounting is supported by the following application components:
Financial Accounting (FI)
Asset Accounting (FI-AA)
Corporate Finance Management (CFM)
Controlling (CO)
Inventory Accounting (MM and ML)
For information about the general settings for parallel accounting, see Defining and Assigning Accounting Principles.
Example
Parallel accounting is necessary for a German subsidiary of an American group. The German subsidiary has to create financial statements according to the accounting principles of the group (such as US GAAP) as well as according to German commercial law (HGB).
Portraying Parallel Accounting
Use
You can use the following approaches to portray parallel accounting in your SAP System:
Portrayal Using Additional Accounts
Portrayal Using Parallel Ledgers
You can also continue to use the option for portraying parallel accounting using an additional company code. However, this approach is not supported by all application components. For more information, see Portrayal Using Additional Company Code.
Portrayal Using Additional Accounts
Use
You can portray parallel accounting in your SAP System by creating additional accounts. This means that you have different account areas:
One joint account area for postings that are the same for both accounting principles
One area with specific accounts for each accounting principle. Each business transaction that, dependent on the accounting principle, leads to a different posting, is posted to the corresponding specific account area.
When you perform closing according to a specific accounting principle, the common accounts and the specific accounts for this accounting principle are evaluated.
Account Areas for Portraying Parallel Accounting Using Additional Accounts
All methods of parallel valuation in the SAP System (such as value adjustments or results analysis) support parallel accounting using additional accounts.
The additional accounts approach is particularly useful if the number of valuation differences in your accounting principles is limited and a larger number of general ledger accounts is acceptable.
Prerequisites
If you introduce this approach, note the following:
Systematic Assignment of Account Numbers
Before you create the general ledger accounts for the specific account areas, you should set up a concept for number assignment.
Retained Earnings Account and Balance Carryforward
You can manage a separate retained earnings account for each accounting principle. This means that, at a fiscal year change, you can carry forward the balances of the profit and loss accounts from the specific account areas to the retained earnings account specified. You only have to carry forward the balances once.
When you create the general ledger accounts for the specific account areas, make sure that you assign a separate P&L statement account type for each account area. Then assign a separate retained earnings account to each P&L statement account type.
For more information, see Balance Carryforward.
Features
Financial Statement Versions
You can create a separate financial statement version for each accounting principle. This means that when you create financial statements, you can select a separate structure for each accounting principle.
Complete Postings versus Difference Postings
You can perform parallel postings in the specific account areas either as complete postings in both areas or as difference postings:
 In Asset Accounting (FI-AA), both difference postings and complete postings are supported.
 All other application components (FI, CO, CFM) support only complete postings.
 The Material Ledger supports only difference postings.
Reporting
For reporting, you can use the following tools in this approach:
 Drilldown Reporting
 Report Painter/Report Writer
 To create financial statements, you can use the report Financial Statements (RFBILA00)
Activities
Create accounts that can be posted to in the company code. From the SAP Easy Access screen, choose Accounting ® Financial Accounting ® General Ledger ® Master Data ® General Ledger Accounts ® Individual Processing ®
Centrally
In Chart of Accounts
In Company Code
Portrayal Using Parallel Ledgers
Use
In General Ledger Accounting, you can perform parallel accounting by running several parallel ledgers (general ledgers) for different accounting principles. During posting, you can post data to all ledgers, to a specified selection of ledgers, or to a single ledger:
The data required according to the accounting principle for the consolidated financial statements is managed in the leading ledger of the general ledger (see also Ledgers). This leading ledger is integrated with all subsidiary ledgers and is updated in all company codes. This means that it is automatically assigned to all company codes.
For each additional (parallel) accounting principle, create an additional (non-leading) ledger in General Ledger Accounting.
SAP recommends that you implement this parallel ledger approach if the number of general ledger accounts would be unmanageable for the scenario using additional accounts.
Advantages:
1. You manage a separate ledger for each accounting principle.
2. You can use standard reporting for the leading ledger and all other parallel ledgers.
3. With this solution scenario, you can portray different fiscal year variants.
4. The number of general ledger accounts is manageable.
Disadvantage:
1. The use of parallel ledgers increases the volume of data.
Integration
You can post to the parallel ledgers from various different SAP application components:
Financial Accounting (FI)
Asset Accounting (FI-AA)
Treasury and Risk Management (TRM)
Controlling (CO)
Materials Management (MM)
Prerequisites
To portray parallel accounting using parallel ledgers, you have to make various settings in Customizing.
For information about the general settings, see Defining and Assigning Accounting Principles.
For information about the settings in the components, see the documentation for parallel accounting in the listed application components.
Features
You can use the following functions for your parallel ledgers:
Complete ledger
Parallel ledgers are always managed as complete ledgers. This means that all postings where there are no valuation differences are posted to the leading and the non-leading ledgers in each company code.
Ledger group
You can combine any number of ledgers in a ledger group. In this way, you simplify the tasks in the individual functions and processes of General Ledger Accounting. This means that you can enter a posting for several ledgers simultaneously (see also Ledger Group).
Ledger selection
2. Postings where no ledger or ledger group is specified are always updated in all ledgers.
3. In the case of manual valuation postings, you can enter the ledger group. This posting is then only updated in the ledgers contained in this ledger group.
4. Documents created by automatic valuations, such as the foreign currency valuation and currency translation, contain the account assignment Accounting Principle. You can assign this account assignment to a ledger group and thereby control in which ledgers this posting is to be updated.
SAP recommends that you define a separate document type for the manual postings that are only to be updated in specific ledgers.
Reporting
For reporting, you can use the following tools in this approach:
5. Drilldown Reporting
6. Report Painter/Report Writer
7. To create financial statements, you can use the report Financial Statements(RFBILA00) for all ledgers.
Activities
The system performs all postings automatically according to the Customizing setting made.
Manual Postings:
You can post manual postings that are only relevant for one individual ledger using the following function in General Ledger Accounting:
From the SAP Easy Access screen, choose Accounting ® Financial Accounting ® General Ledger ® Posting ® Enter General Posting for Ledger Group.
Portrayal Using Additional Company Code
Use
You can portray parallel accounting in your SAP System by defining an additional company code. Difference postings are created for additional accounting and posted to the additional company code. Reporting covers the actual company code and the additional company code.
Integration
The additional company code approach is only supported by the application component Financial Accounting (FI). It is no longer possible to post to an additional company code from any other application component.
If you are an upgrade customer from an R/3 Enterprise release, you can continue to use this obsolete approach in Asset Accounting (FI-AA). However, you cannot make new settings in Customizing or reconfigure the approach.
SAP recommends that you only use this approach if it is already implemented and you have no additional requirements.
Features
You can post to an additional company code with the following valuation reports:
Value Adjustment
Reclassification and Sorting of Receivables and Payables
Foreign Currency Valuation
In addition to the automatic postings created by the valuation reports, you can perform manual postings to the additional company code.
For more information about the settings for these reports, see Parallel Accounting in Financial Accounting.
Reporting
For reporting, you can use the following tools in this approach:
Drilldown Reporting
Report Painter/Report Writer
To create financial statements, you can use the report Financial Statements (RFBILA00)
Parallel Accounting in the Application Components
Use
If you want to create financial statements according to parallel accounting principles, this means that the system has to perform different postings for each accounting principle for some business transactions. In the individual SAP application components, various functions and valuation reports are affected by the use of parallel accounting.
Integration
The following SAP application components support parallel accounting in their valuation reports and functions:
Financial Accounting (FI)
Asset Accounting (FI-AA)
Treasury and Risk Management (TRM)
Controlling (CO)
Materials Management (MM) and Material Ledger:
 Material Price Change (MM-IV-MP)
 Balance Sheet Valuation (MM-IM-VP)
 Actual Costing/Material Ledger (CO-PC-ACT)
Parallel Accounting in Financial Accounting
Use
In Financial Accounting, the following functions or valuation reports are affected by parallel accounting:
Reclassification and Sorting of Receivables and Payables
Value Adjustments
Foreign Currency Valuation
Currency Translation
Accruals
Provisions
Prerequisites
Prerequisites for Reclassification and Sorting of Receivables and Payables
You can use the reclassification/sorting report to reclassify and sort your receivables and payables according to sort methods that you define, such as for due date periods.
If you want to sort and reclassify the receivables and payables for different accounting principles, you have made the following settings:
5. ...
19. 1. You have defined the valuation areas.
To do this, in the Implementation Guide for Financial Accounting (New), choose General Ledger Accounting (New) ® Periodic Processing ® Valuate ® Define Valuation Areas.
20. 2. You have defined the account determination for each valuation area.
To do this, in the Implementation Guide for Financial Accounting (New), choose General Ledger Accounting (New) ® Periodic Processing ® Valuate ® Reclassify ® Transfer and Sort Receivables and Payables ®
 Define Adjustment Accounts for Receivables/Payables by Remaining Term
 Define Adjustment Accounts for Changed Reconciliation Accounts
 Define Adjustment Accounts for Investments
Double-click a transaction to select it. The Enter Chart of Accounts dialog box appears. Choose with the quick info text Change Valuation Area.
21. 3. You have defined a sort method for each valuation area.
To do this, in the Implementation Guide for Financial Accounting (New), choose General Ledger Accounting (New) ® Periodic Processing ® Valuate ® Reclassify ® Transfer and Sort Receivables and Payables.
22. 4. To enable the execution of the postings resulting from the sorting and reclassification for your parallel accounting principle, you have made the following settings depending on the approach you have selected:
1. a. Portrayal Using Additional Accounts:
You assign an accounting principle to the valuation areas. You have already assigned accounts to the valuation areas under point 2. You create separate accounts for each type of accounting.
To do this, in the Implementation Guide for Financial Accounting (New) choose General Ledger Accounting (New) ® Periodic Processing ® Valuate ® Assign Valuation Areas and Accounting Principles.
2. b. Portrayal Using Parallel Ledgers:
You have defined the additional accounting principles and assigned them to the parallel ledgers (or ledger group) (see Defining and Assigning Accounting Principles). You then assign these accounting principles to the valuation areas as described under 4.a).
Run the sorting/reclassification valuation report separately for each accounting principle (see also Reclassification and Sorting of Receivables and Payables).
Prerequisites for Value Adjustments
If you want to perform value adjustments for doubtful receivables, you have the following options:
You can post the value adjustments manually.
You can post the value adjustments automatically using the flat-rate individual value adjustment. To do this, you have to define rules in Customizing. In these rules, you define when the system should adjust which receivables, and when the corresponding provisions are to be posted.
For more information, see Value Adjustments.
If you want to perform the value adjustment for different accounting principles, you have made the following settings:
You have defined the account determination for each valuation area (as in point 1 above).
To enable the execution of the postings resulting from the value adjustment, you have made the following settings depending on the approach you have selected:
 Portrayal via additional accounts:
You have made the settings as described in 4.a).
 Portrayal via parallel ledgers:
You have made the settings as described in 4.b).
Prerequisites for Foreign Currency Valuation
You use the foreign currency valuation to valuate open items posted in a foreign currency and balances of G/L accounts and balance sheet accounts managed in foreign currency. The report creates the postings that result from the valuation automatically. You have defined the account determinat -
Hi,
I am doing Movt Type 301 Plant to Plant Stock transfer for unrestricted stock in one plant to another
The materials has QM activated with 08 inspection Type Active. Control of IL is such that only one IL gets created for plant/sloc/batch
After doing the first posting, I have done UD for the IL and posted stock to unrestricted. Then I tried to do multiple postngs to same sloc/batch
For the subsequent postings, for some materials the stock gets posted to quality and for some it gets posted to unrestricted. What should be the normal behaviour
What can be the reasonHi,
Though I'm not sure I understood it correctly or not but seems you have issues with transfer postings (301 mvmnt with all QM active) and some of them goes to QI stock whereas others go to UR.
If that's the case, I believe you should check your inspection set up and look for 'Post to insp stock' under inspection type 08.
ntn -
GL Posting in incorrect account
Dear SAP gurus,
I am facing an issue in which postings to be done for a Material account is being charged to a Service Account.
Where can I check the incorrect assignment or setting in the PO or FI document?
Any help is very welcome
RogerHi Roger,
Please go to transaction OBYC.
There you will have all MM/FI Integaration customizing.
You double click on the appropriate type and you'll see the G/L account assignment if it's correct or not
Then you can change
Thanks -
SAP Payroll Integration with PCA
Hi Gurus,
Please assist on the integration logic for posting revenue postings from payroll.
As part of the payroll posting revenue due to interest earned from staff loans must be posted to a revenue account in FI
The revenue element is defined with cost element category 11-Revenues and thus the system requires a an CO account assignment in the form of a profit center. We are not using profitability analysis
The payroll posting is not successfully posted to FI because there is no account assignment to a CO objects (Message KI235).
The employee in question is assigned to a cost center via the position. And I was expecting that the profit center would be derived from this cost center. Unfortunately this is not the case.
Please assist me by explaining how the profit center can be entered/derived for the revenue postings resulting from payroll. In Hr there appears to be no possibility of assigning a personnel master a profit center.
Regards,
P.KHi Sridevi,
Check the link below.
http://www.oracle.com/media/peoplesoft/en/pdf/whitepapers/e_hcm_wp_choosingbest_sap_exsum_05_05.pdf
Reward points if it helps.
Regards
Karan -
Dear all,
Can anyone give me the detailed explaination of MM-FI configuration or any links where we get the information about this please
Thanks & Regards
Somashekar AnandHi,
SAP Materials Managements
Relationship to Finance
Finance in Logistics
Finance in Logistics - A look from Materials Management
The purpose of this document is to explore the relationship materials management has with accounting in SAP. We will take three swipes at this relationship. First, at an overview level, we will consider a materials management workflow scenario. Next, we will dig deeper as we create documents to support that scenario, and consider the account postings made. Finally, we will consider configuration, and show how SAP automatically posted to various accounts.
A Materials Management Workflow Scenario
Lets consider the following map :
Starting from the top box, we see that a purchase requisition is created. This can be entered manually (as in the case if a secretary wants to order office supplies), or automatically via MRP (through Materials Requirements Planning, where material requirements are generated based on satisfying customer orders, production lines, and other needs). A purchase requisition would contain information about :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
A P.Req. may have to go through a release procedure in order to be converted into a purchase order. At this point, suffice it to say that SAP has ensured that employees do not get to acquire materials just because they have nice smiles.
Next, it is up to purchasing to determine a vendor for this requisition. In SAP, the purchasing department has several options : source lists, purchasing info records (material-vendor records), quota arrangements, and vendor master records. A vendor may also be selected based on price quotations attained by the purchasing department.
A purchase order may now be created. Note : in the standard configuration, a purchase requisition is not required in order to create a purchase order. The same information entered in the purchase requisition is entered in a purchase order (note items 1 through 6), plus a purchase order would have a specified vendor.
Purchase order follow-up depends on the purchasing organization. In some organizations, confirmation of a received PO is required. The confirmation could then be a signal to the receiving dock to expect goods on a certain date. Follow-up might include further negotiation, such as price, quantity, or delivery date changes.
A goods receipt for the purchase order is now entered. In the standard configuration, a goods receipt does not require a PO, or any other type of order. With valuated materials, a goods receipt will now cause an account entry. This account entry will typically be against a stock (or production/sales order) account and a clearing account. More about this later. Note that to the side, goods issues and transfer postings are shown. These are also functions of a warehouse, and both can cause account postings. It is important to understand which goods movements will affect accounting and how.
Often an invoice will be received with the goods shipment, but it can be received independently. Invoice verification is the process of determining whether an invoice matches what was received. In SAP, invoices can be entered either from materials management or from the accounts payable side. Most of us would hold that it is up to A/P to enter the invoice, but who better to verify the invoice against the goods shipment and quality than MM? This issue is up to the company and project team installing SAP. The account entries made upon invoice receipt will typically be against the clearing account posted when the goods received and the vendors account (indicating that the vendor should be paid). The invoice may be blocked for payment for various reasons (e.g.invoiced too early, wrong quantity), but even blocked invoices can cause account postings in SAP.
The invoice can now be paid. Invoice payment is done by A/P, outside of MM. This is done by means of payment programs where A/P clerks have the ability to select which vendors to pay, the means of payment, and whether or not to block payment (based on subsequent QI, or poor relations with the vendor). The account postings for payment are typically against the vendors account (signifying that payment is being received) and against cash (or a bank account).
The Documents
The purpose of this section is to show account postings which relate to documents created from materials management. This will include the creation of the following documents :
1. Purchase requisition
2. Purchase order
3. Goods receipt
4. Vendor invoice
Note that RFQs and quotations will not be considered. This is because neither of these documents has an account assignment category. Their only relevance to accounting is that they specify a material (and thus a material type), and the quotation specifies a vendor and a price. With no account assignment category, however, there is no specification as to who will pay for the ultimate purchase.
The purchase requisition
The purchase requisition is created through transaction ME51 (Log > MM > Purch > Req. > Create). As mentioned, the following are determined in a purchase requisition :
1. What is being requisitioned? material / service
2. How much? quantity
3. When is it needed? delivery date
4. Where will it be delivered? plant, storage location
5. How will it be used? item category
6. How will it be paid for? account assignment category - this may also state how the material/service will be used, as the account assignment may be a sales or production order(for example).
This is shown on the following screen :
As mentioned, neither the vendor, nor the material price is specified in the requisition. A vendor can be specified in a requisition which has been "allocated", but thats a separate story.
The purchase requisition has no direct account postings. When a purchase order is created with reference to the requisition, the account assignment (category) and the material items are carried over. As of 2.2, the account assignment can be changed when the requisition is converted to a PO, but not the account assignment category. (You can change the account assignment from one cost center to another, but not from a cost center to a sales order -- different account assignment categories).
The purchase order
A purchase order can be created for a known vendor with the transaction code ME21 (accessed by Log>MM>Purchasing>Purchase Order>Create>Vendor known). An un-allocated (no vendor previously selected) purchase requisition might then be referenced. Alternatively, a purchase order can be created with reference to an allocated requisition using transaction code ME58 (Log>MM>Purchasing>Purchase Order>Create>via requisition).
As mentioned, the purchase order has the same entries as a requisition, plus item prices and a specified vendor. A sample purchase order is shown :
The purchase order has no direct account postings. However, account postings from goods receipts and invoices made against POs are very much affected by accounts designated in the POs. As of 2.2, a purchase orders account assignment can be changed as long as no goods have been received against the PO, and no invoice has been posted against it. (Thus, if no GR or invoice has been posted against a PO, the account assignment can be changed from one cost center to another, but not from a cost center to a sales order -- just like with requisitions).
The goods receipt (for a purchase order)
A goods receipt for a purchase order is created using transaction code MB01 (Log> MM>Inventory Management>Goods movement>Goods receipt>For purchase order). A movement type can then be selected via the menu bar, or using the list of possible entries. In SAP, every goods movement has a "movement type". The three headings of goods movements in SAP are good receipts, goods issues and transfer postings. Most goods movements will cause account postings. More will be said about that later.
With every goods movement (or transfer posting) in SAP, a material document is created. For every goods movement which affects a G/L account, an accounting document will be created (separate, but tied, to the material document). Material documents are not deleted, but they can be canceled or reversed. Thus, if a good receipt was posted with the wrong storage location and the wrong quantity, the receipt could be canceled. The cancellation will create a new material document (and probably an accounting document which will contain reverse debit/credit entries to what were entered in the first accounting document). Note, that if a goods receipt is entered for twenty-five pieces of a material, and only twenty pieces were actually received, a reversal could be entered. This reversal would be for five pieces. It would also have a material document, and the associated accounting document would have reverse debit/credit postings for the value of the five easy pieces.
The following is a goods receipt for the purchase order created in the last picture :
The movement type is one of the most important entries in materials management. It controls how account postings are made (as we will see), and it is very easy to overlook, as it is only a three-digit identifier. After several materials movements, one becomes familiar with common movement types (e.g. 101 - goods receipt of a PO, 201 - goods issue for a sales order, 561 - initial stock entry, and so on). The movement type will control the account postings with the aid of other parameters (such as the material type and the account assignment category).
The accounting view of the above transaction is shown in the following view :
Using the movement type (101), SAPs automatic account assignment was able to determine that a debit should be made to the cost centers account (which was specified on the purchase order), and the GR/IR clearing account should be credited. With automatic account assignment, the proper accounts with their respective "posting keys" were specified. Posting keys determine whether debits or credits are made against given accounts. More will be said about posting keys later.
The invoice (for a purchase order)
Invoices on the materials management side of SAP are entered via transaction code MRHR (Log>MM>Invoice verification>Document entry>Enter invoice). One could also enter credit memos in materials management (via a similar path to that just shown), as well as subsequent debits/credits against previous entries. As mentioned, these are usually entries made by accounts payable (A/P) clerks, but SAP allows its customers the option of entering this information in MM.
In SAP, invoices are not posted unless total debits and credits balance. New in 2.2, preliminary posted invoices can be made for invoices. In such a case, the proper PO to register the invoice against is unknown, therefore an A/P clerk can enter the invoice information, and "park" the document. Note that in "parked" invoices, no account postings are made.
Invoices can be blocked for payment because tolerances are exceeded. For example, the invoice date is much before the expected receiving date stated on a PO, thus date tolerance has been violated (it wouldnt be the first time a date was violated). Similarly, an invoice can be entered for a quantity greater than that which was received. Here the quantity tolerance has been violated. In SAP, even though an invoice is blocked for payment, account postings are made.
With goods movements, a material document is always created, and an associated accounting document is created when G/L accounts are affected. With invoices, one accounting document is created. An itemized listing of an invoice entered with reference to the PO created for this document is shown :
The accounts referenced in the above picture are not posted to until the invoice document has been saved. The "accounting view" of the above saved document is shown :
The accounting view of the invoice reflects what the item view showed, but note that the account entries could not be made unless the invoice balanced.
Also shown in the picture are tax codes. Tax codes can be created with a simple valuated entry (which would be manually maintained by A/P, purchasing, and system administrators). Tax codes can also be maintained via an external interface. In the US, tax codes are defined by :
1. the jurisdictional laws of the place to which the goods are shipped,
2. the material type of the goods being shipped, and
3. the taxability of the entity (customer) receiving the goods.
There are more than 50,000 different tax jurisdiction areas in the US (as they are defined by state, county, city, zip codes, etc.). External tax systems (such as AVP or Vertex) maintain the taxation rates for these jurisdictional areas. In 2.2, modifications have been created to interface external tax systems. In 3.0, this interface will be standard.
The account entries described in this section are shown in the following "T" account entries.
With the goods receipt, the debit to the cost center account (which could be the cost centers stock account) represents an increase in on-hand stock, while the credit to the GR/IR clearing account represents an outstanding invoice approval process.
With the invoice receipt, the invoice is verified that, in fact, the goods were received, and were of acceptable quality. This invoice entry creates a debit to the GR/IR clearing account (to balance the account), and a credit to the vendor account. A credit to vendor account signifies that in order to make the account balance, the vendor must be paid (debit the vendor account). Note that if the received goods were of sub-standard quality, payment could be blocked at this point by either not entering the invoice, or (more likely), the invoice would be entered, but blocked for payment. (Invoice verification is considered the third link of "three-way matching" -- the matching of the PO, GR and invoice. The invoice verifies the purchase order price and specifications, and that the goods in the PO were received and of appropriate quality)
The payment of the invoice is the final link in the workflow chain. The vendor is paid (account debited), and cash is decreased (credited). In SAP, maintenance of vendor payment is outside of materials management, but with an integrated system, it is coordinated.
Automatic Account Assignments in Materials Management
Consideration of automatic account assignments in MM will be approached in two steps, according to the accounting documents created in the last section. First, we will pursue the account postings made by goods movements, then we will consider account postings made by invoice entries.
Account postings through goods movements
Lets start from the basics. As mentioned, with each goods movement there can be an associated account posting. Where are these account postings maintained? A good place to first look is table 156s. This is accessed by table maintenance (SM31), entering "T156S", and hitting either the "Maintain" or "Display" button. The following table is then presented :
This table shows configuration information based on all the movement types (hundreds) in SAP. For our discussion on account postings, we do not need to concern ourselves now about the entries in the column and to the right of "SLoc".
From the fields shown, a quantity string and value string are determined. Note, that it is the combination of all the appropriate fields which makes this determination. The quantity string determines which quantity fields are updated (through a sequence of instructions), and the value string determines which account posting keys will be signaled (also through a sequence of instructions). Therefore, in order to determine which quantity string and value string are to be referenced for each goods movement, the significant fields of table 156S are now defined from left to right, the following fields have the following meaning :
Movement type - the three digit code associated with a goods movement. It must be specified with every goods movement.
Value update indicator - every material type is designated as to whether or not the material value is updated during goods movements. Thus, the value update indicator signifies if the account posting can affect the material account.
Quantity update indicator - every material type is also designated as to whether or not material quantities are to be updated during goods movements. Note that the the material types quantity update indicator and value update indicator must match a line entry in order to use the associated quantity and value strings.
Special stock indicator - this field indicates who owns the material and who gets the material. For example, the indicator might be blank (" "), where the stock is taken by the user in their plant. The indicator might be "K" (for consignment), where the vendor owns the material, but the stock is taken into the users plant.
Movement indicator - This specifies the type of order the goods movement might be against. For example, the movement could be with reference to a purchase order, a delivery note, or with no reference.
Receipt indicator - This field is currently not used. In the future, it is expected that specification will be possible to determine if this movement was for a stock transport order or an outside purchase order
Consumption posting indicator - this field is used in the case of goods receipts for purchase orders, and is defined from the account assignment category in the PO. Thus, in our previous example, the account assignment of "K" (for cost center) in the purchase order ensured that the receipt debited the cost centers account, and not the stock account.
So with the right combination of these seven (actually six) entries, we determine quantity and value strings. The quantity string is handled very similarly to the value string. Quantity strings are maintained in table 156M (accessed via SM31 and display/maintain "T156M"). In the last picture, the quantity string for the top entry is ME02. In table 156M, the quantity string indicates if orders are to be updated and other relevant quantity information. This table will not be analyzed here.
Value strings are handled in table 156W (accessed via SM31 with display/maintain "T156W"). The value string for the top entry in the last picture was WE06. Table 156W is shown :
The value string WE06 has two entries. These entries have different transaction/event keys (also called account keys). The transaction/event (t/e) keys specify the type of account to be posted to. These transaction/event keys are found in table 030. Thus, WE06 specifies that t/e key KBS will be referenced first, followed by key WRX. Lets look at table 030 (accessed through SM31, display/maintain "T030", and select group RMK; OR via the menu path Tools > Cust. > Config > Acc. > Fin. Acc. > Book. > Bus. trans. > Gen. Ledger > MM > Auto posting).
Paging down through this table we see that KBS signifies an account specified in a purchase order, and WRX signifies a GR/IR clearing account. If we double-click on (or choose) KBS, we are brought to the following screen :
So how do we know which posting key to take? Is this a debit or a credit? We look to table 156 (a.k.a. "T156) in SM31.
For movement type 101, we see that the first entry is "S" under D/C. This signifies that the first entry is to be a debit, thus the first t/e key (KBS in this case) is a debit. Therefore, we look to posting key 81.
Note the line "posting keys are independent of chart of accounts" in the screen for key KBS. Lets look at where posting keys are configured in transaction OB41 (in table TBSL through SM31, or via the menu path Tools > Cust > Config > Acc > Fin Acctg > Book > Bus trans > G/L > Control > Posting keys).
Posting key 81 shows a debit to a G/L account. Lets look into this...(double-click or choose posting key 81)
We see that this key causes a debit to the specified G/L account. Thus, an account was specified in the PO (since 101 was a GR for a PO), and by finding the value string in table 156S, then the appropriate transaction/event keys in table 156W, and then by digging into the t/e keys in table 030, we were able to determine the appropriate account postings. So that told us about the debit made, but what about WRX? Lets also look inside t/e key WRX in table 030 (we first must specify the chart of accounts, in this case CAUS) :
Here we see different postings, a valuation grouping code, an account modifier and a valuation class. Since the account modifier is not shown in this screen, well cross that bridge when we get to it. For now, lets look into the valuation grouping code. This is found in table 001K through SM31 (also available in transaction OMWD; Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct. det. > Val. area grouping).
.From this screen, we see that the valuation grouping code is used to group different valuation areas and/or different company codes together within a chart of accounts so that they have similar postings. So we understand the valuation grouping code, now how about that valuation class? Thats attained from the accounting view of the material master (for that specific valuation area).
For this material, the valuation class of 3000 is chosen. When this field is drilled into, we see that for this raw material, the system knew that only certain valuation classes were allowed. How did the system know which valuation classes were allowed for this material? It knew because when this material was created, a material type was chosen. Now on to material type configuration. This can be accessed via transaction code OMS2 (T>C>C>L>MM>Master data > material > control data > material type > click on change or display), select "ROH" (for raw materials), then click on the "account assignment" button. This shows the possible valuation classes assigned to the material types.
So for this raw material, the valuation class chosen was 3000. Therefore, back in table 030, for the t/e key WRX, using the valuation grouping code found in table 001K and the valuation class for the material (found in the material master), we can determine the GR/IR clearing account entry.
While were in the material type screen, lets look at one other thing -- quantity/value updating. From the last picture, click on the button labeled "quantity/value". The following screen appears :
Note that to restrict quantity or value updating of this material type, the button "in no valuation area" under the headings of quantity or value updating would be selected. Thus, FOR EACH MATERIAL TYPE, THIS IS WHERE WE DETERMINE IF THERE IS QUANTITY OR VALUE UPDATING.
Back to our example from II.3 (a goods receipt for a purchase order)
So guess what! With what weve covered in this section were ready to track down how our goods receipt posting in the last section happened as it did! Lets consider what we know about the goods movement :
1. It is a goods receipt for a PO -- movement type 101.
2. The PO had an account assignment category of "K", for a cost center and therefore is an item set for consumption.
3. The material used was a raw material with a valuation class of 3000.
4. For raw materials, there is both quantity and value updating.
5. It is "standard stock" item (no special stock type)
So lets look to table 156S ==>
We are looking for the entry which is the third from the top. It meets all the criteria. Therefore, we are looking to value string WE06 for answers WE06 is found in table 156W.
As we said about this screen, WE06 has only two t/e keys. We determined the account posting for KBS in the following way :
1. We found KBS in table 030
2. Under KBS, we saw that two posting keys were there, one for a debit, one for a credit
3. In table 156, we found that the first entry is a debit, thus we select posting key 81
4. Next we looked to table TBSL (in transaction code OB41), and chose posting key 81
5. There we saw that posting key 81 causes a debit to a prespecified G/L account (the cost center account specified on the purchase order)
We also determined the account posting for WRX in the following way :
1. We found WRX in table 030
2. Under WRX, we saw that we saw that we needed to specify a valuation grouping code and a valuation class in order to determine the proper GR/IR clearing account.
3. In table 001K, we saw that for our valuation area (US01) and our company code (US01), we have the valuation grouping code US01.
4. From the accounting view of our material master, we saw that our material has a valuation class of 3000 for the plant we are operating in (US01).
Therefore, in table 030, with a valuation grouping code of US01 and a valuation class of 3000, we have the GR/IR clearing account as account number 191100. This is shown in the accounting document created for the goods receipt.
A small change to the purchase order...
We said that a purchase order creates no direct account postings. However, they very much affect account postings for subsequent documents! In the purchase order of section II.2, what if we had chosen the account assignment category as being standard? Lets look again at table 156S.
In this case, we choose the top entry -- goods receipt for a PO, where there is no consumption specified. We are thus given the value string WE01. Lets look to table 156W.
Here we have 12 different posting keys! Note that there should always be more than one posting key for a goods movement because there should always be at least one debit and at least one credit. We saw that for movement type 101 (in table 156), the first entry is a debit. Thus, lets look to table 030 to see what a debit under posting key BSX does.
Again we see the valuation grouping code US01 and valuation class 3000, we have account 300000. This is exactly what we find with this goods receipt ==>
Offsetting entries for inventory postings (Key GBB)
One last point about automatic account assignments from materials movements.
One of the t/e keys definable for a value string is GBB. This is a key often associated with goods issues, but can be used whenever offsets are required for inventory. This key is maintained in table 156X, which is shown :
As we determined the quantity and value strings from table 156S, here we not only can find the value string, but also the account modifier. If we look in table 030, we see the t/e key GBB. When we choose that key, we find the following view :
Where in the t/e key screens of BSX and WRX we only had to know the valuation grouping code and the valuation class, here we also need the account modifier. This screen shows that a goods movement which has a valuation grouping code of US01, a valuation class of 7900 (commonly used for semi-finished goods), and an account modifier of AUF would have debit and credit postings made to account 895000.
An Easier Way...
To review, we recommend a way of determining account postings from goods movement documents :
1. Check table T156S for the appropriate movement type
2. Find the appropriate movement type and value string in table T156S based on :
a. if the material type is quantity and/or value updated
b. if the item has a special stock type
c. what type of movement is occurring
d. what type of account assignment the item might have (consumption, sales order,
e. stock account, etc.)
3. Based on the value string, check table T156W for the sequence of t/e keys accessed
4. Check table T156 to determine if the sequence from T156W begins with a debit or a credit
5. Check table 030 to see the possible postings for each of the t/e keys
a. for the t/e keys which have simple entries of posting keys (as with KBS), look to table TBSL to see what account this posting key affects
b. for the t/e keys which have a valuation grouping code, account modifier, and a valuation class specification, find the account by the following :
look to table 001K to find the valuation grouping code based on the appropriate valuation area and company code
look to table T156X if an account modifier must be checked
look to the accounting view in the material master to find the appropriate valuation class
To check the account postings, use transaction code OMWB (accessed via the path Tools > Cust > Config > Log > MM > Val/Acc.assign > Config > Acct determ > Auto posting > Simulate). Hit cancel (in 2.2) to get to the next screen, then hit the "Simulation" button choose a plant, material and a movement type, and hit the "Account assignment" button.
This is one way to check the configuration without creating all of the documents.
Postings from invoices
Account postings made by invoices are much easier to understand, but harder to examine, than goods movement account postings. With invoices and credit memos, there is an associated document type (note the initial screen of an invoice)
However, we can look at the posting keys for invoices we can expect to be affected. These are maintained with transaction code (accessed via the path : Tools > Cust > Config > Acctg > Fin Acctg > Book > Bus trans > Base params > Control > Posting keys). We are brought to the following screen :
We see that posting key 31 is an invoice in which we credit a vendor. Lets choose this key (or double-click on it).
We see that this is a credit to a vendor account. We also see that posting key 31 has a reverse posting key of 22. The previous screen showed that this is a reverse invoice receipt (different from a credit memo). A note about vendors -- in purchasing, vendors can be created with regard to purchasing, or centrally. If a vendor is created with regard to purchasing only, the vendor will not have accounting information maintained. Thus, the vendor would not bill in the SAP system. This is not to say that the vendor will not bill (we should be so lucky), just that it is not done in the SAP system. This might be for SAP users who are using an external system for accounting (or A/P only).
When a vendor is created, it is designated with an account group. The main functions of a vendor account group are :
1. to designate if the vendor is a one-time vendor
2. to specify the number range the vendor might be assigned to (to assign a vendor name)
3. to maintain screen control for vendor maintenance
Vendor account groups are maintained in transaction OBD3 (Tools > Cust > Config > Acctg > FI Acctg > Book > Master Recs > A/P > Control > Acct groups). If we choose LIFA (general vendors), we see the following :
The screen shows that the number range for LIFA is "XX" (transaction XKN1 shows this to signify external number assignment). The screen also shows that this is not a one-time vendor. If we double click on "Company code data", and double-click on "account management" in the next screen, we see how accounting fields for this vendor are maintained in the vendor master record.
If an invoice is created with reference to a purchase order, the account postings are already specified, as checking is done as to whether the goods have been received. Note that in creating an invoice, it is not necessary that an A/P clerk reference a PO (although it is advisable if known). If a PO is not reference, the A/P clerk must manually maintain account entries. These account entries have associated posting keys. For example, a freight charge might have a posting key of 50. This account can be seen in table 030. Likewise, unplanned delivery costs can be charged against the group receiving the goods.
During invoice entry, alternative account entries can be entered, either as debits or credits. Thus, account determination is made as the invoice is entered.
Postings from purchasing documents
One last note...
You may find that some account postings happen when referencing purchasing documents, and there is no reference to these postings in table T156S. For example, freight charges. They can be specified in a PO, but how does a goods receipt know to take the POs freight charge over to the account posting?
First, lets remember where freight postings are made in a purchase order. In the pricing condition record (note a special condition type) :
So the condition record of the screen shown has a condition type of FRA1, a percentage freight charge. Purchasing condition types are tied to account postings through PURCHASING configuration. Thus if we look into transaction M/08, yes with a "/" (Tools > Cust. > Config > Log > MM > Purch. > Functs. > Conds. > Pricing > Pricing Proc. > Pricing Proc.), we see the following screen :
If we now double-click on RM0000 (the first pricing procedure), page down to find FRA1, hit the "change view" button, we find the following screen :
Here we see that condition type FRA1 is tied to account key FR1. If we now look in table T030, double-click on "RMK" (MM postings), and double-click on FR1, we see that (in CAUS, for example), these freight postings are made to account number 192100.
Regards,
Archit -
Account Determination and Movement type
Hello Experts,
From SD course, we know that account determination is Account Key + Account assignment groups for customer and material respectively + Sorg + COA.
So, what does it mean by this definition of Movement type:
"The movement type is a three-digit key used to differentiate between goods movements in the R/3 System. Examples of these goods movements are goods receipts, goods issues or transfer postings It plays a central role in Automatic Account determination"
regards
PascalFrom SD course, we know that account determination is Account Key + Account assignment groups for customer and material respectively + Sorg + COA.
This is related to revenue account determination. Normally carried out by SD personal using t.code VKOA.
The movement type is a three-digit key used to differentiate between goods movements in the R/3 System. Examples of these goods movements are goods receipts, goods issues or transfer postings It plays a central role in Automatic Account determination
This is related to inventory account update (quantity/value]. For example, when a goods issue is made, the value and quantity in the stock account needs to be reduced. The G/L account assignment is configured by MM personnel using t.code OBYC.
Regards,
Maybe you are looking for
-
Problem with database access in EJB deployment to SJSAS on remote deploy
Hi, I have deployed an Enterprise application containing an EJB3.0 module to a remote sun application server (Edition 9.0_01 (build b02-p01)) using a mysql ver 5 DB with connector mysql-connector-java-5.0.0-beta-bin. It is being used by a swing appli
-
Photodownloader in Photoshop CS5 freezes when choosing a directory
This just recently happened in the last week. When I insert my CF card in my card reader and Adobe Bridge CS5 and photo downloader opens up, it hangs when I try to change the location where to download the files to. So in photodownloader, I select th
-
I watched several template tutorials and they seem to stop short on how to manage a website so that Contribute users can edit the website easily and web developers adding menu items without the need to update every page. So as I understand one create
-
No Exporting System for system ECP-100 in project ZECC_QGM
Hi we are using QGM Functionality in Solution Manager7.1 with SP08 for ECC Implementation project. last week we migrated your Solution manager system to a different Hardware, where there is a change in IP address, Host name and SID was changed. an
-
HI, I want to batch create multiple pdfs from tiff originals in multiple folders. I used to use Adobe capture but no longer available. What replaced it or can I do the same thing in Acrobat X pro?