-
SAP Note
Header Data
Symptom
This SAP Note provides enhanced functions in SAP ERP, which
enable a more efficient preparation of electronic financial
statements. To prevent misunderstandings:An end-to-end solution for
electronic financial statements in SAP ERP is not planned. The
creation of the XBRL files and transfer to the financial authority
using ELSTER Rich Clients (ERiC) is not supported by SAP ERP.For
this, SAP BusinessObjects Disclosure Management is available (see
SAP Note 1463434). SAP plans to also provide relevant functions for
Releases 4.7 and (with a reduced scope of functions) 4.6C. However,
this is more difficult than in the higher releases:
l In Release 4.7, the functions for decompressing ZIP files
(class CL_ABAP_ZIP) are missing. The Basis colleagues have already
confirmed that they will provide these in the next Support Package
72 for Release 4.7 (see SAP Note 616958).This Basis Support Package
(end of corrections 19-Jun-12, delivery usually 4-6 weeks later) is
therefore a prerequisite for the electronic financial statement
note.
l In Release 4.6C, no fields of the type STRING (with variable
length) are allowed. Therefore, even a different table design is
required here.Follow-on effects (in the case of a release change)
also have to be considered here.In particular, problems occur for
item descriptions, which are very long in some taxonomies
(particularly the insurance taxonomy).
As a result, the delivery for these releases is delayed. We
currently expect a delivery in Q3/2012 for Release 4.7 and 4.6C;
however, due to the unpredictable factors that still exist, we
cannot specify a precise date.
The following functions are included in the delivery:
l Creation of financial statement versions according to the XBRL
taxonomies specified by the tax authorities.
Assignment of accounts or functional areas to the items of the
(XBRL) financial statement versions.This is done in the same way as
for the (normal) financial statement versions that are in your
system.
l Data export for electronic financial statement at item and
account level according to the XBRL taxonomy including XBRL
tagging.
l Display of the financial statement based on the new structures
in the ALV tree format.
Technical description of the scope of delivery
1. Transactions:
l FSE0_XBRL - Fin. Statement According to XBRL Taxonomy
l FSE1_XBRL - Create Fin. Statement Version from XBRL
Taxonomy
l FSE1_XBRL_COPY - Fin. Statement Vers. - Account Assignment
Transfer
l FSE2_XBRL - Change Fin. Statement Version (XBRL)
l FSE3_XBRL - Display Fin. Statement Version (XBRL)
l OB58_XBRL - Change Fin. Statement Versions from XBRL
Taxonomies
l FSE0_EXPORT_NODES - Data Export for Electronic F/S: Items
l FSE0_EXPORT_DETAILS - Data Export for Elect. F/S: Accounts
2. Authorization object:
l F_T011XBRL - Fin. Statement from XBRL Taxonomy: General
Maintenance Authorization
1666580 - Electronic financial statement: Account mapping in
ERP
Version 17 Validity: 19.10.2012 - active Language English
Released On 19.10.2012 08:58:29 Release Status Released for
Customer Component FI-GL-IS Information System Priority Correction
with high priority Category Legal change
-
3. Lock object:
l EFT011_XBRL - Fin. Statement Version from XBRL Taxonomy
Other Terms
Electronic financial statement, electronically submitted
financial statements (E-Bilanz), section 5b, German Income Tax Act
(EStG), electronic tax return (ELSTER), XBRL
Reason and Prerequisites
Solution
Import the Support Package or the transport request and
implement the correction instructions relevant for your
release.
Dependencies
Do not import the transport request if your system has a Support
Package level that is the same or higher than the following Support
Package levels.
Note that all new objects (except for the objects in the
function group FAGL_BSPL_SERVICES) in the correction instructions
are also included in the transport request that you have to import
as part of the manual pre-implementation steps. The correction
instructions simplify the tracking of the changes and the SAP Note
implementation status.All new ABAP/4 programs are also included in
the transport request.
------------------------------------------------------------------------
|Manual Post-Implement.|
------------------------------------------------------------------------
|VALID FOR | |Software Component SAP_APPLSAP Application | |
Release 500SAPKH50001 - SAPKH50026 | | Release 600SAPKH60001 -
SAPKH60021 | | Release 602Until SAPKH60211| | Release 603Until
SAPKH60309| | Release 604SAPKH60401 - SAPKH60410 | | Release
605Until SAPKH60507| | Release 606SAPKH60601 - SAPKH60602 |
------------------------------------------------------------------------
Manual post-implementation step "Transport of the objects into
the follow-on systems":
Include the object lists of the transport requests that you have
imported in the manual pre-implementation steps in the new
transport requests created in your system. This ensures that all
changes required for this SAP Note are included in transport
requests that you can transport to your entire system landscape
using your normal transport paths.This prevents problems that may
result from incorrect import jobs. If you proceed as described, you
do not have to import the transport requests attached to this SAP
Note into the other systems of your system landscape.The changes
are provided using the new transport requests created by you.
Include object lists. Transport request for object changes
(attachment FIN_eBilanz_source_code.zip)
l Call transaction SE09.
l In the menu, choose Request/Task >> Display Individually
(F5).
l Enter the transport request that you use to implement the
correction instructions using transaction SNOTE.
l Choose Copy (Enter).
Release Package name
500 SAPKH50027
600 SAPKH60022
602 SAPKH60212
603 SAPKH60310
604 SAPKH60411
605 SAPKH60508
606 SAPKH60603
-
l Position your cursor on the transport request ID.
l In the menu, choose Request/Task >> Object List >>
Include Objects...
l Select Object List from Request and enter the transport
request ID from the file FIN_eBilanz_source_code.zip.
l Choose Copy (Enter).
Transport request for Customizing settings and ALV layouts
(attachment FIN_eBilanz_customizing.zip)
l Call transaction SE09.
l If you want to create a new Customizing request:
In the menu, choose Request/Task >> Create (F6).
Select Customizing request and choose Copy (Enter).
Enter a short description (for example, FIN electronic financial
statement: Customizing) and choose Save.
l If you want to use an existing Customizing request:
In the menu, choose Request/Task >> Display Individually
(F5).
Enter the transport request that you want to use and choose Copy
(Enter).
l Position your cursor on the transport request ID.
l In the menu, choose Request/Task >> Object List >>
Include Objects...
l Select Object List from Request and enter the transport
request ID of the transport request from the file
FIN_eBilanz_customizing.zip.
l Choose Copy (Enter).
------------------------------------------------------------------------
|Manual Activity |
------------------------------------------------------------------------
|VALID FOR | |Software Component SAP_APPLSAP Application | |
Release 500SAPKH50001 - SAPKH50026 | | Release 600SAPKH60001 -
SAPKH60021 | | Release 602Until SAPKH60210| | Release 603Until
SAPKH60309| | Release 604SAPKH60401 - SAPKH60410 | | Release
605Until SAPKH60507| | Release 606SAPKH60601 - SAPKH60602 |
------------------------------------------------------------------------
l First, import the attached transport requests. Two transport
requests in two separate files are attached to this SAP Note.
FIN_eBilanz_source_code.zip
FIN_eBilanz_customizing.zip
Note the following:
The transport in FIN_eBilanz_source_code.zip contains only
German texts. The texts in all other languages are delivered with
the relevant Support Packages only.
When you import the transport requests, activate the following
options:
Leave the transport request in the queue for a later import.
Overwrite the originals.
Overwrite the objects in unconfirmed repairs.
l Manual tasks after implementing the above transport requests
and before implementing the correction instructions.
Perform these manual tasks in the sequence described here.
When you create or change ABAP Dictionary objects, the system
issues warning messages or information messages several times.You
can confirm these messages by choosing Continue (Enter).
Create a transportable workbench request.
Call transaction SE09. In the menu, choose Request/Task >>
Create. >> Select
-
Workbench request. >> Choose Copy (Enter). >> Enter
the Short Description. >> Choose Save (Enter). Transfer all
new and changed objects to this request.
Create the function group FAGL_BSPL_SERVICES.
Call transaction SE37. In the menu, choose Goto >>
Function Groups >> Create Group. >>
Function group = FAGL_BSPL_SERVICES
Short text = Financial Statements - Service Functions
>> Choose Save (Enter). >>
Package = FAGL_REPORTING >> Save (Enter)
Reassign the function module BSPL_DATA_GET (Enhancement Package
6 only).
Call transaction SE37.
Enter the function module BSPL_DATA_GET.
In the menu, choose "Function Module >> Other Functions
>> Reassign....
Old function group = BSPL
New function group = FAGL_BSPL_SERVICES
Choose "Reassign".
Adjust the structure RFPOSINF.
Call transaction SE11. Select Data type and enter RFPOSINF in
the relevant input field. >> Choose Change. >> Add the
following fields to the end of the structure:
Component Component Type
OWPOS FAGL_FSV_OWPOS
TYPE FAGL_FSV_NODETYPE
CALCSIGN_XBRL FAGL_FSV_XBRL_CALCSIGN
FISCALREQ_XBRL FAGL_FSV_XBRL_FISCALREQ
TEXT_XBRL FAGL_FSV_XBRL_LABEL_255
NAME_XBRL FAGL_FSV_XBRL_NAME_255
>> Save the object.
>> In the menu, choose Extras >> Enhancement
Category. >> Select Can be enhanced (character-type or
numeric). >> Choose Close (Enter). >> Choose Save.
>> Choose Activate (you can ignore warning messages regarding
the fields KEY and SUM).
Adjust the structure RFGBST.
Call transaction SE11 >> Select Data type in the relevant
input field RFGBST choose >> Change. Before the component KEY
add the component VERSN_XBRL with the component type
VERSN_011_XBRL: >> Select the component KEY. >> Choose
Insert Row (+). >> In the row added, enter the component
VERSN_XBRL and the component type VERSN_011_XBRL. >> Choose
Save.
Switch to the Entry help/check tab page. >> Select the
component VERSN_XBRL. >> Choose Foreign Keys. >>
Confirm the proposal for the value table T011_XBRL with Yes and
choose Enter.
>> In the menu, choose Extras >> Enhancement
Category. >> Select Can be enhanced (character-type or
numeric). >> Choose Close (Enter). >> Choose Save.
>> Choose Activate (you can ignore warning messages regarding
the field KEY).
l Implement the correction instructions.
Now implement the correction instructions valid for your release
using transaction SNOTE.
On the Confirm Changes screen, select all objects in the Copy
Changes column (also those with a yellow traffic light) and choose
Continue (Enter) to confirm the screen.
You can skip messages and warnings that occur during the object
transfer by choosing Continue (Enter) or Save (Enter). 'The
messages are, for example, Object can only be created in SAP
package or Original system set to "SAP" or Create Object Directory
Entry.
In the last dialog box 'Activate Object Changes' or 'Inactive
Objects for ...', choose 'No' or Cancel(F12).
l Manual tasks after implementing the correction
instructions:
Activate the function group 0FAGL_FSV_VIEW.
-
Call transaction SE80. Enter the function group 0FAGL_FSV_VIEW.
>> Choose Display (Enter). >> Position your cursor on
the object name 0FAGL_FSV_VIEW, right-click it and choose
Activate.>> >> In the subsequent dialog box Inactive
Objects for ..., choose Continue (Enter). In the "Error During
Activation" dialog box, choose Activate anyway.
Create the maintenance and transport objects. You can skip
messages and warnings by choosing Continue (Enter) or Save (Enter).
Important: The warning message "The original of the view package
FAGL_FSV_MAINTENANCE is in VBS" (SV 359) appears in the footer of
the screen and can be overlooked easily.Confirm this message with
Enter.
Transaction SE54 >> Table/View V_FAGL011FC_XBRL >>
Environment >> Maintenance Objects >> Generate
Transaction SE54 >> Table/View V_FAGL011PC_XBRL >>
Environment >> Maintenance Objects >> Generate
Transaction SE54 >> Table/View V_FAGL011VC_XBRL >>
Environment >> Maintenance Objects >> Generate
Transaction SE54 >> Table/View V_FAGL011ZC_XBRL >>
Environment >> Maintenance Objects >> Generate
Transaction SE54 >> Table/View V_T011_XBRL >>
Environment >> Maintenance Objects >> Generate
Set the compare flag.
Call transaction SE54. Enter the table/view V_T011_XBRL.
>> Select Generated Objects. >> Choose Create/Change.
>> For "Compare Flag", select Not Adjustable. >> Choose
Save (Ctrl+S).
Regenerate group-specific programs.
Call transaction SE54. Choose Edit Function Group and enter the
function group 0FAGL_FSV_VIEW. Select Re-generate
group-specificprograms and choose Change. In the Group-Specific
Subprograms dialog box, select all entries and choose Continue
(Enter).
Copy the graphical user interface.
Call transaction SE41. Choose Copy User Interface (Ctrl+F5).
From program = SAPL0F00 To program = SAPL0FAGL_FSV_VIEW >>
Choose Continue (Enter). >> Choose Activate. >> In the
subsequent dialog box Inactive Objects for ..., choose Continue
(Enter).
Create text symbols for the program SAPL0FAGL_FSV_VIEW.
Call transaction SE38. Enter the program SAPL0FAGL_FSV_VIEW.
>> Select Text elements. >> Choose Change. Enter the
following text symbols:
Symbol Text
018 Data was changed
019 Save changes first?
A01 Delete financial statement
A02 For this version
A03 financial statement items have already been created. Delete
everything?
A04 Financial statement items
A05 Foreign lang.texts
>> Choose Save. >> Choose Activate (Ctrl+F3).
>> In the subsequent dialog box Inactive Objects for ...,
choose Continue (Enter).
Correct the application log.
Call transaction SLG0. Choose Position. >> Enter the
object FIGL. >> Choose Enter. >> Select the row FIGL.
>> Double-click "Sub-objects". >> Choose New Entries.
>> Subobject = FSV_XBRL_CREATE >> Sub-object text =
Create Fin. Statement Version from XBRL Taxonomy >>
In the same way, position your cursor on the object FIGLGL and
delete the subobject FSV_XBRL_CREATE.
Choose Save (Ctrl+S). Confirm any warning messages and other
messages that are displayed with Enter.
Change the selection texts for the program
FAGL_FSV_UPLOAD_XBRL_TAXONOMY.
Call transaction SE38. Enter the program
FAGL_FSV_UPLOAD_XBRL_TAXONOMY. >> Select Text elements.
>> Choose Change. >> Switch to the Selection Texts tab
page. >> Change the following texts:
Name Text old Text new
P_STRLAN Texts in Language Original Language
-
P_STRNAM Name Financial Statement Version
P_STRSCR Structure Financial Statement Version
>> Choose Activate. >> In the subsequent dialog box
Inactive Objects for ..., choose Continue (Enter).
Checking the interfaces of function modules
The interfaces of the following function modules may no longer
exist after you implement the attached correction instructions.
Check this and enter the interfaces as required:
Call transaction SE37, enter the function module
FAGL_FSV_DELETE_XBRL, choose Change, choose the Import tab page and
add the following parameter:
Parameter Name Typing Associated Type Pass Value
BS_NAME TYPE VERSN_011_XBRL X
>> Choose "Save"(Ctrl+S).
Call transactionSE37 and enter the function module
FAGL_FSV_FILENAME_F4_EXIT_XBRL , choose Change, choose the Changing
tab page and add the following parameters: Confirm the warning
message regarding the typing 'LIKE' with Enter.
Parameter Name Typing Associated Type Pass Value
SHLP TYPE SHLP_DESCR X
CALLCONTROL LIKE DDSHF4CTRL X
Choose theTables tab page and add the following parameters:
Confirm the warning message regarding the typing 'LIKE' with
Enter.
Parameter Name Typing Associated Type
SHLP_TAB TYPE SHLP_DESCT
RECORD_TAB LIKE SEAHLPRES
>> Choose "Save(Ctrl+S)".
Activate the remaining objects.You can confirm the dialog box
Inactive Objects for ... with Continue (Enter) each time.
Call transaction SE11. >> Enter the type group FIBS.
>> Choose Activate (Ctrl+F3).
Call transaction SE80. >> Enter the function group
FAGL_FSV_XBRL. >> Choose Display (Enter). >>
Right-click the object name FAGL_FSV_XBRL. >> Choose
Activate.
Call transaction SE80. >> Enter the function group
FAGL_BSPL_SERVICES. >> Choose Display (Enter). >>
Right-click the object name FAGL_BSPL_SERVICES. >> Choose
Activate.
Call transaction SE80. >> Enter the function group FIBS.
>> Choose Display (Enter). >> Right-click the object
name FIBS. >> Choose Activate. In the dialog box for the main
program, select SAPLFIBS.
SE38 >> Program FAGL_FSV_UPLOAD_XBRL_TAXONOMY >>
Activate (Shift+F9)
SE38 >> Program FAGL_FSV_COPY_ASSIGNMENTS_XBRL >>
Activate (Shift+F9)
SE38 >> Program RFGSBSTR >> Activate (Shift+F9)
SE38 >> Program FAGL_BSPL_XBRL >> Activate
(Shift+F9)
SE38 >> Program FAGL_BSPL_XBRL_DETAILS >> Activate
(Shift+F9)
SE38 >> Program FAGL_BSPL_XBRL_NODES >> Activate
(Shift+F9)
SE37 >> Function module NODE_TAB_TRIM_LENGTHS >>
Activate (Ctrl+F3)
Adjust the selection texts for the program RFGSBSTR.
Call transaction SE38. Enter the program RFGSBSTR. >>
Select Text elements. >> Choose Change. >> Switch to
the Selection Texts tab page. >> Text for VERSXBRL =
Financial Statement Version from XBRL >> Choose Save
(Ctrl+S). >> Choose Activate (Ctrl+F3).
Make additions to the piece list for the transport object
V_T011_XBRL.
Call transaction SOBJ. Choose Maintain. >> Choose
Position. >> Enter the object V_T011_XBRL. >> Choose
Continue (Enter). >> Select the row V_T011_XBRL. >>
Choose Details (Ctrl+Shift+F2). >> Set the Current Setting
indicator. >> Choose Back (F3). >> Choose Piece list.
>> Choose New Entries. >> Add the following
entries:
FAGL_011CC_XBRL
-
FAGL_011FC_XBRL
FAGL_011NC_XBRL
FAGL_011PC_XBRL
FAGL_011QT_XBRL
FAGL_011VC_XBRL
FAGL_011ZC_XBRL >> Choose Save (Ctrl+S)
l In addition, note the manual post-implementation step
"Transport of the objects into the follow-on systems".
Validity
Correction Instructions
Causes - Side Effects
Support Packages & Patches
Software Component From Rel. To Rel. And Subsequent
SAP_APPL 500 500
600 600
602 602
603 603
604 604
605 605
606 606
Correction Instructions
Software Component Valid from Valid to Number
SAP_APPL 500 604 1459650
605 605 1459618
606 606 1448423
Notes / Patches corrected with this note
Note Reason From Version To Version Note Solution Version
Support Package The table does not contain any entries
The following SAP Notes correct this Note / Patch
Note Reason From Version To Version Note Solution Version
Support Package
1666580 0 0 1709059 1 1666580 0 0 1712817 1 1666580 0 0 1731513
0 1666580 0 0 1788558 1
Support Packages
Software Component Release Support Package
SAP_APPL 603 SAPKH60310
604 SAPKH60411
605 SAPKH60508
500 SAPKH50027
606 SAPKH60603
600 SAPKH60022
602 SAPKH60212
603 SAPKH60311
604 SAPKH60412
605 SAPKH60509
606 SAPKH60604
-
References
This document refers to:
SAP Notes
This document is referenced by:
SAP Notes (4)
Attachments
1690315 EFS: Information about the taxonomies 1732201 E-Bilanz:
Global Common Data(GCD) 1746294 Docu on e. financial statement:
data provisioning (4.6C-500) 1463434 Electronically submitted
financial statements in Germany
1463434 Electronically submitted financial statements in Germany
1690315 EFS: Information about the taxonomies 1732201 E-Bilanz:
Global Common Data(GCD) 1746294 Docu on e. financial statement:
data provisioning (4.6C-500)
File Name File Size (KB) Mime Type
FIN_eBilanz_customizing.zip 8 application/x-zip-compressed
E-Bilanz__Handbuch_1-04.pdf 1703 application/pdf
FIN_eBilanz_source_code.zip 362 application/x-zip-compressed
E-Bilanz__Handbook_1-02_en.pdf 872 application/pdf
