50
FIT SOLUTIONS E-LEDGER SOLUTION User Manual
FIT SOLUTIONS
E-LEDGER SOLUTION
User Manual
FIT Solutions® 2
DOCUMENT DETAIL
PUBLISH DATE 13.10.2014
CURRENT VERSION 2.0
REVISION HISTORY
Revision Date Revision Notes
22.10.2014
Resetting e-Ledger Processes for a Given Period title has been detailed
and such mistakes in the document has been fixed.
FIT Solutions® 3
TABLE OF CONTENTS
1 Processes In ERP Side .......................................................................................................................................................... 6
1.1 Create Job for e-Ledger Creation Program ...................................................................................................... 6
1.2 Reset e-Ledger Processes For A Given Period ............................................................................................... 8
1.3 Controlling Reports ................................................................................................................................................... 15
1.3.1 To Establish And Reporting Of Documents Which Has Incomplete “Source Document
Number” 15
1.3.2 To Establish of Documents Which Has Incomplete “Source Document Number” ......... 15
1.3.3 Reporting of Documents Which Source Document Number Has Not Been Entered .... 17
1.3.4 To Establish Of Accountant Documents And Items Which Are Not Occurred In The e-
Ledger 19
1.3.5 Reporting Of Numerical And Statistical Informations Related To e-Ledger ..................... 20
2 Processes In Portal Side .................................................................................................................................................... 22
2.1 Logon To e-Ledger Portal ....................................................................................................................................... 22
2.2 User Creation ................................................................................................................................................................ 22
2.3 Creation Of Company Data .................................................................................................................................... 24
2.4 Creation Of Branch Data ......................................................................................................................................... 24
2.5 Creation Of Account Data ....................................................................................................................................... 25
2.6 e-Ledger Process Start ............................................................................................................................................. 26
2.7 Following e-Ledger Process In Postal, Analyzing Report Screen ...................................................... 27
2.8 Upload/Download Transaction For Completed Ledgers And Certificate Files In Report
Screen 29
2.9 Displaying e-Ledger And Certificate Files ..................................................................................................... 30
2.10 Analysis Of Ledger And Certificate Files ........................................................................................................ 32
2.11 Description Of Ledger Statutes ........................................................................................................................... 33
2.12 Detailed Informations about Ledger Status .................................................................................................. 34
2.12.1 Status 14: An error occurred while reading company code data or tmp xml file ........... 34
2.12.2 Status 41: An error occurred during ledger signing process .................................................... 34
2.12.3 Status 61: An error occurred while signing certificate file ......................................................... 35
2.12.4 Status 81: An error occurred in Ledger File Schema Control.................................................... 35
2.12.5 Status 91: An error occurred in Certificate File Schema Control ............................................ 35
FIT Solutions® 4
2.12.6 Status 101: An error occurred during archiving process ............................................................ 36
3 Uploading of Created Berat Files To TRA Portal .................................................................................................. 36
3.1 Logon to Program ....................................................................................................................................................... 36
3.2 Package Uploading ..................................................................................................................................................... 40
3.3 Accessing To e-Ledger Berat ................................................................................................................................ 43
4 Troubleshooting .................................................................................................................................................................... 44
FIT Solutions® 5
Figures
Figure 1: Creation Job For e-Ledger Creation Program ................................................................................................ 6
Figure 2: Simple Job Selection .................................................................................................................................................... 7
Figure 3: Reset e-Ledger Processes for a Given Period ................................................................................................ 9
Figure 4: Reset e-Ledger Processes for a Given Period - Company Code ............................................................ 9
Figure 5: Reset e-Ledger Processes for a Given Period - Begin Data of Period .............................................. 10
Figure 6: Reset e-Ledger Processes for a Given Period - End Date of Period .................................................. 11
Figure 7: Reset e-Ledger Processes for a Given Period - e-Ledger Creation Process ................................. 12
Figure 8: Reset e-Ledger Processes for a Given Period - Document Journal Sending Log ....................... 13
Figure 9: Reset e-Ledger Processes for a Given Period - General Ledger Sending Log .............................. 14
Figure 10: To Set e-Ledger Source Document Analyze Program as Job ............................................................. 16
Figure 11: e-Ledger: Documents which source document entry has not been entered ............................ 18
Figure 12: e-Ledger: Documents which source document entry has not been entered ............................ 18
Figure 13: Accounting records which are not occurred in the e-Ledger ........................................................... 19
Figure 14: Accounting records which are not occurred in the e-Ledger ........................................................... 19
Figure 15: e-Ledger period analysis ..................................................................................................................................... 20
Figure 16: e-Ledger period analysis ..................................................................................................................................... 21
Figure 17: User Creation Screen Step 1 ............................................................................................................................... 23
Figure 18: User Creation Screen Step 2 ............................................................................................................................... 23
Figure 19: Creation Of Company Data ................................................................................................................................. 24
Figure 20: Creation Of Branch Data Step 1 ........................................................................................................................ 25
Figure 21: Creation Of Branch Data Step 2 ........................................................................................................................ 25
Figure 22: Creation Of Account Data .................................................................................................................................... 26
Figure 23: Process Start .............................................................................................................................................................. 26
Figure 24: Following e-Ledger Process In Postal, Analyzing Report Screen Step1 ...................................... 27
Figure 25: Following e-Ledger Process In Postal, Analyzing Report Screen Step2 ...................................... 28
Figure 26: Following e-Ledger Process In Postal, Analyzing Report Screen Step3 ...................................... 29
Figure 27: Displaying e-Ledger and Certificate Files Step1 ...................................................................................... 31
Figure 28: Displaying e-Ledger and Certificate Files Step2 ...................................................................................... 31
Figure 29: e-Ledger Program Login Page ........................................................................................................................... 37
Figure 30: Enter Type and Password of Token ............................................................................................................... 38
Figure 31: Selection of Certificate .......................................................................................................................................... 38
Figure 32: Signing Process for Login to System .............................................................................................................. 39
Figure 33: Main Screen of e-Ledger Program .................................................................................................................. 40
Figure 34: Package Uploading Page ...................................................................................................................................... 41
Figure 35: Package Uploading Page (Multiple Uploading) ........................................................................................ 42
Figure 36: Saved Package To System ................................................................................................................................... 42
Figure 37: Package List Page .................................................................................................................................................... 43
Figure 38: Access to e-Ledger Berat ..................................................................................................................................... 43
FIT Solutions® 6
1 PROCESSES IN ERP SIDE
1.1 Create Job for e-Ledger Creation Program
User must run /FITE/LDG_R01 transaction code. In the selection screen, company
code, start and end time of period is selected and clicked to run. The job occurs at the
end of this process.
Figure 1: Creation Job For e-Ledger Creation Program
After e-Ledger process is triggered, SM37 transaction is executed. Displayed screen
must be as shown below. In this screen, Job Name is “EDEFTER_*”must be specified. As
Username Source System User Id which is defined in company settings must be given.
Process trigger date must be entered into Job start condition segment.
FIT Solutions® 7
Figure 2: Simple Job Selection
When Execute button is pressed all processes that are executed in selected dates will
be listed on screen. If job info contains spool flag as shown in red circle below, it means that
job has got an error. This error must be analyzed and problem must be solved and process
must be triggered again. If there is no spool and status is “Completed” then it means that
ledger info is sent to Portal.
FIT Solutions® 8
1.2 Reset e-Ledger Processes For A Given Period
1.2.1 Overview of Initialization Program
If you need to initialize created e-ledger data or e-ledger sending logs, /FITE/LDG_R02
transaction code must be run. If everything is ok,you don’t need to run this transaction
code.
The program’s parameters are shown below.
FIT Solutions® 9
Figure 3: Reset e-Ledger Processes for a Given Period
1.2.1.1 Company Code
Figure 4: Reset e-Ledger Processes for a Given Period - Company Code
FIT Solutions® 10
Company code must be chose to initialize the selected period.
1.2.1.2 Begin Date of Period
Figure 5: Reset e-Ledger Processes for a Given Period - Begin Data of Period
The starting date of the period which is wanted to be initialized.
FIT Solutions® 11
1.2.1.3 End Date of Period
Figure 6: Reset e-Ledger Processes for a Given Period - End Date of Period
The ending date of the period which is wanted to be initialized.
FIT Solutions® 12
1.2.1.4 e-Ledger Creation Processes
Figure 7: Reset e-Ledger Processes for a Given Period - e-Ledger Creation Process
This option clears both journal and ledger creation process, the data on header an item
tables and data creation job. If the program is run with this option, than “Document Journal
Sending Log” and “General Ledger Sending Log” options must be selected and run also to
initialize the period.
FIT Solutions® 13
1.2.1.5 Document Journal Sending Log
Figure 8: Reset e-Ledger Processes for a Given Period - Document Journal Sending Log
This option is used to initialize journal ledger period. Journal ledger’s logs are deleted
(/FITE/LDG_T003) if program is ran with this option.
FIT Solutions® 14
1.2.1.6 General Ledger Sending Log
Figure 9: Reset e-Ledger Processes for a Given Period - General Ledger Sending Log
This option is used to initialize journal ledger period. General ledger’s logs are deleted
(/FITE/LDG_T003) if program is ran with this option.
Note: The period to be initialized must be selected with the same period which the ledger data
creation process is selected. The creation process date can be found on /FITE/LDG_T008 table.
If the whole period is wanted to be initialized, than program must be run with all options
selected separately.
FIT Solutions® 15
1.3 Controlling Reports
In line with the experience gained in projects, some additional controls in scope of e-
Ledger is important to make sure that whether e-Ledger has been created correct or not. In
line with these needs, /FITE/LEDGER_TOOLS package has been created. Programs and
their functions are described below.
1.3.1 To Establish And Reporting Of Documents Which Has Incomplete “Source Document
Number”
There is an alert mechanism that provides to be established the documents which
source document number has not been entered. In this way, there is no need to run the e-
Ledger creation program in live mode. This alert mechanism is important to create more
correctly e-Ledger.
This alert mechanism consists of two steps:
1.3.2 To Establish of Documents Which Has Incomplete “Source Document Number”
Before all else, the documents which has incomplete “Source Document Number” have
to be established. For that, the program (program name:
/FITE/RLDGT_SRC_DOC_ANALYSE_J) which has /FITE/LDGT_R01 process code is run.
FIT Solutions® 16
Figure 10: To Set e-Ledger Source Document Analyze Program as Job
A job is created automatically which is named as “SOURCE_DOC_<company code>_<the
date of the day>_<running time> after company code and period information are entered
and clicked to “Run” button. Analysis information as a result of running this job will be
written to /FITE/LDG_T035 table.
PREREQUISITE 1: e-Ledger ABAP Patch 2 have to be taken to system to run this program.
PREREQUISITE 2: NO_SOURCE_DOC field of ps_header or pt_item parameters must be set
as ‘X’ for documents which cannot be found in spite of required in
USEREXIT_GET_SOURCE_DOC_NUM user-exit which is used to find source document by e-
Ledger creating program to run this program.
For instance;
FORM userexit_get_source_doc_num_j TABLES pt_item TYPE zeldg_item_t
USING ps_docu_ type TYPE /fite/ldg_t002
pv_bukrs
pv_gjahr
CHANGING ps_heade r TYPE zeldg_header
pv_item_ lvl_ind.
IF ps_header-blart EQ 'XX'.
READ TABLE pt_item INDEX 1 TRANSPORTING sgtxt.
FIT Solutions® 17
IF sy-subrc EQ 0 AND pt_item-sgtxt(8) CO '01234 56789'.
ps_header-source_doc_num = pt_item-sgtxt+9.
IF NOT ps_header-source_doc_num IS INITIAL.
CONCATENATE pt_item-sgtxt+4(4) pt_item-sgtx t+2(2) pt_item-sgtxt(2)
INTO ps_header-bldat_long.
ps_header-document_type = ps_docu_type-sour ce_doc_type.
ELSE.
ps_header-no_source_doc = 'X'.
ENDIF.
ENDIF.
ENDIF.
ENDFORM. " USEREXIT_GET_SOURCE_DOC_NUM
As can be seen, if there is a required situation about source document number (it
means, in most interior if block) and this source document type field has not been entered,
no_source_doc field is set as ‘X’.
1.3.3 Reporting of Documents Which Source Document Number Has Not Been Entered
After running process of job is completed (after defining document which their source
document entry has not been entered), reporting of these documents can be done. For that,
report which has /FITE/LDGT_R02 (program name:
/FITE/RLDGT_SOURCE_DOC_ANALYSE) process code is run.
FIT Solutions® 18
Figure 11: e-Ledger: Documents which source document entry has not been entered
Company code and period values must be entered which analysis result will be seen in
selection screen. As desired, filtering based on SAP document type and e-Ledger document
type can be done. As following ALV will be seen after entering the parameter from the
selection screen and clicking the “run” button.
Figure 12: e-Ledger: Documents which source document entry has not been entered
FIT Solutions® 19
1.3.4 To Establish Of Accountant Documents And Items Which Are Not Occurred In The e-
Ledger
After running e-Ledger in Live, /FITE/LDGT_R03 (program name:
/FITE/RLDGT_MISSING_RECORDS) process code has been developed to be seen of
accountant documents which do not come into e-Ledger.
Figure 13: Accounting records which are not occurred in the e-Ledger
After entering company code, year and period values from the selection screen and
clicked to “run” button, as following ALV screen will be seen.
Figure 14: Accounting records which are not occurred in the e-Ledger
Note: In e-Ledger, items don’t occur which have a header value but not have an item value
and if their amount is 0 TL. These kinds of records can be seen with this report.
FIT Solutions® 20
1.3.5 Reporting Of Numerical And Statistical Informations Related To e-Ledger
After e-Ledger is run in Live for a period, a report which has /FITE/LDGT_R04 process
code (program name: /FITE/RLDG_PERIOD_ANALYSE) has been developed to be seen of
numerical information such as balance information at the end of the related period,
information in related period, whether the related period is consistent with the previous
period or not.
Figure 15: e-Ledger period analysis
Company code, year and month values must be entered from the selection screen of the
report. Additionally, selection criteria is also available to be seen of total debt and total
receivable values based on main account number or sub account number in related month.
As following screen will be shown after entered the parameter entry and clicked to “run”
button.
FIT Solutions® 21
Figure 16: e-Ledger period analysis
Note: “Main account number” or “Sub account number” parameters which are entered
from the selection screen will be affect the values of “Total debt according to filtering
criteria” and “Total receivable according to filtering criteria” fields which are at the bottom.
Other numerical values on the screen are the calculated values on the basis of all records of
the related month.
FIT Solutions® 22
2 PROCESSES IN PORTAL SIDE
2.1 Logon To e-Ledger Portal
First of all Portal Logon must be provided.
Portal Link, user id and password will be provided to you.
Example Link: http://nwserver:50000/eledger
2.2 User Creation
The path to be used for company creation is Settings->User Management->New User
FIT Solutions® 23
Figure 17: User Creation Screen Step 1
Figure 18: User Creation Screen Step 2
FIT Solutions® 24
2.3 Creation Of Company Data
Separate company data must be created for each company that will use eledger. Source
system User id and password must have SAP_ALL authorization in R3 side. The path to be
used for company creation is Settings->Company Management ->New Company
Figure 19: Creation Of Company Data
2.4 Creation Of Branch Data
If there are branches of the company, you have to define them on portal. Settings-
>Company Management ->Branch Management
FIT Solutions® 25
Figure 20: Creation Of Branch Data Step 1
Figure 21: Creation Of Branch Data Step 2
2.5 Creation Of Account Data
Separate Accountant data must be created for each company that will use e-Ledger.
The path to be followed in order to create accountant is; Settings->Accountant
Management-> New Accountant
FIT Solutions® 26
Figure 22: Creation Of Account Data
2.6 e-Ledger Process Start
The paths to be followed in order to start processes are:
For Document Journal: ELedger-> Eledger Process ->Journal Process ->Start
For General Ledger: ELedger-> Eledger Process ->General Ledger Process ->Start
Figure 23: Process Start
FIT Solutions® 27
After starting process “Journal Ledger process is started” message is displayed. If this is
not the message displayed, then it means that process is not started. For General Ledger the
message is like this “General Ledger Process is started.”
2.7 Following e-Ledger Process In Postal, Analyzing Report Screen
After completion of job in R3 side, we can follow up ledger processes in e-ledger report
segment in e-ledger portal side. If Ledger has status 100, it means that process is completed
without an error. If Ledger has status 1, 5, 10, 20, 30, 40, 50, 60, 80, 90, it means that ledger
is continuing into some processes. If Ledger has status 2, 6, 11, 12, 13, 14, 41, 51, 61, 81,
91, 101, it means that there is an error in ledger. Press (information) button and cursor
on status info error explanation can be displayed. Addition to that, you can see error
explanations at the last page of this document. In the below screen shut, document journal
example sent from R3 is displayed. Ledger is divided into 4 pieces; first piece is completed
without an error, second piece got a signature error (41), 3rd and 4th pieces still continue to
be processed.
Figure 24: Following e-Ledger Process In Postal, Analyzing Report Screen Step1
FIT Solutions® 28
Next to the piece with error, (restart process) button is displayed in order to restart
process. In this transaction, without connecting to R3 side, process is restarted for that
piece by using backup files.
Process steps can be monitored by pressing (information) button next to the related
piece.
Figure 25: Following e-Ledger Process In Postal, Analyzing Report Screen Step2
FIT Solutions® 29
Figure 26: Following e-Ledger Process In Postal, Analyzing Report Screen Step3
2.8 Upload/Download Transaction For Completed Ledgers And Certificate Files In
Report Screen
After ledgers are completed you can press (download Ledger, Download
Certificates) buttons in order to analyze the results. Or at the top of the list Multiple
Certificate Download button is used to select required ledgers’ certificates.
FIT Solutions® 30
After completion of all ledger processes, Certificate files must be downloaded from E-
Ledger Management Portal and uploaded to TRA portal manually. After TRA approval to
ledgers, certificate files must be reloaded to E-Ledger Management Portal.
In order to do this, either (Download Certificate) button must be pressed one by
one for each file or Multiple Certificate Download button at top of the list must be pressed.
After loading TRA approved certificate files successfully to E-Ledger Management Portal,
ledgers’ statuses become “105” and Certificate Download button is replaced by (Download
Approved Certificate) button. If approved certificates would like to be downloaded as a
whole, (Download Multiple Approved Certificate) button can be used.
2.9 Displaying e-Ledger And Certificate Files
The path to be followed for display screen is; e-Ledger->Ledger Analysis
For Ledger;
FIT Solutions® 31
Figure 27: Displaying e-Ledger and Certificate Files Step1
For Certificate File;
Figure 28: Displaying e-Ledger and Certificate Files Step2
FIT Solutions® 32
2.10 Analysis Of Ledger And Certificate Files
Document Journal Display:
General Ledger Diplay:
FIT Solutions® 33
Certificate File Display :
2.11 Description Of Ledger Statutes
<statu id="1" Ledger (txt) is successfully read
<statu id="2" Error occurred when reading Ledger (txt)
<statu id="5" General Ledger and Journal compatibility is verified
<statu id="6" General Ledger and Journal is not compatible
<statu id="10" Ledger converted to tmp xml successfully.
<statu id="14" An error occurred while reading company code data or tmp
xml file
<statu id="20" Control files are read successfully
<statu id="30" Ledger is prepared successfully
<statu id="40" Ledger is signed successfully
FIT Solutions® 34
<statu id="41" An error occurred during ledger signing process
<statu id="50" Certificate is created successfully
<statu id="51" An error occurred while creating certificate file
<statu id="60" Certificate is signed successfully
<statu id="61" An error occurred while signing certificate file
<statu id="80" Ledger Schema Control passed successfully
<statu id="81" An error occurred in Ledger Schema Control
<statu id="90" Certificate File Schema Control passed successfully
<statu id="91" An error occurred in Certificate File Schema Control
<statu id="100" Certificate and Ledger Files are archived successfully
<statu id="101" An error occurred during archiving process
<statu id="105" Approved Certificate File is uploaded to e-Ledger Portal successfully
2.12 Detailed Informations about Ledger Status
2.12.1 Status 14: An error occurred while reading company code data or tmp xml file
When the ledger status is 14, there is no available space error. Check the disk which is
the ledger was transformed. If there is enough space in disk, you should inform the
consultant for deep search of the fix.
2.12.2 Status 41: An error occurred during ledger signing process
1. If the system uses USB Token, it can be disconnected.
2. Maybe Apache Tomcat Server Service was stopped. (It can be for both HSM and USB
Token).
FIT Solutions® 35
If you faced error like this, firstly check the USB Token is connected, then restart or
start the Apache Tomcat Server Service. If error continues then inform the consultant.
2.12.3 Status 61: An error occurred while signing certificate file
In addition to Status 41, Timestamp informations can be added wrong. Or you filled
your TimeStamp quota. Please check quota and informations then contact with the
consultant.
2.12.4 Status 81: An error occurred in Ledger File Schema Control
There was an error in ledger data, which is not valid by GIB controls. You can see the
detail of the error in e-Ledger Cockpit, e-Ledger Report Page. There is a button which name
is Show Validation Error, if the detail is not clear for you please inform the related
consultant.
2.12.5 Status 91: An error occurred in Certificate File Schema Control
There was an error in certificate data, which is not valid by GIB controls. You can see
the detail of the error in e-Ledger Cockpit, e-Ledger Report Page. There is a button which
name is Show Validation Error, if the detail is not clear for you please inform the related
consultant.
FIT Solutions® 36
2.12.6 Status 101: An error occurred during archiving process
When the ledger status is 101, there is no available space error. Check the disk which is
the ledger was archived. If there is enough space in disk, you should inform the consultant
for deep search of the fix.
3 UPLOADING OF CREATED BERAT FILES TO TRA PORTAL
There is not any option connecting to TRA portal as English so the portal is in Turkish.
You can find the necessary part as below which has been translated to English.
3.1 Logon to TRA Web Page
The berat files(cover pages) will be uploaded to TRA through TRA’s web site. Firstly,
login to this web site must be done. Private corporation will be login to e-Ledger web site
with token certificate and real person will be login with token or qualified electronic
certificate.
After the user logon to system, the berat files will be uploaded to TRA. Controlled berat
files will be approved by TRA. The user can download the berat files which has been
approved by TRA.
You can login to e-Ledger program as using https://uyg.edefter.gov.tr/edefter/.
FIT Solutions® 37
Figure 29: e-Ledger Program Login Page
The process of obtaining the session code occurs as clicking to “Start” button. Type and
password of token are entered and is clicked to “Enter” button.
FIT Solutions® 38
Figure 30: Enter Type and Password of Token
And then, the certificate which will be used is selected and is clicked to “OK” button.
Figure 31: Selection of Certificate
FIT Solutions® 39
“Sign” button is clicked because of login to system.
Figure 32: Signing Process for Login to System
Program main screen will be displayed after login to the web page by using token or
secure electronic signature.
FIT Solutions® 40
Figure 33: Main Screen of e-Ledger Program
3.2 Package Uploading
Uploading process of created Berat files will be processed as selecting “Upload the
package” button from the main screen.
FIT Solutions® 41
Figure 34: Package Uploading Page
More than one package can be uploaded as selecting multiple if it is necessary.
FIT Solutions® 42
Figure 35: Package Uploading Page (Multiple Uploading)
The system gives a process number after package uploading process will be done
successfully.
Figure 36: Saved Package To System
Status of the packages can be controlled also from the “Package List” menu.
FIT Solutions® 43
Figure 37: Package List Page
3.3 Accessing To e-Ledger Berat
Berat files which is existed in uploaded package is checked to controls needed.
Controlled files are appoved by TRA(it means files are signed by TRA). These files should
be saved because of proving the validity of the current ledger.
Figure 38: Access to e-Ledger Berat
FIT Solutions® 44
When these processes are completed, approved Berat files must be uploaded to Portal
as defined the title of 2.8.
4 TROUBLESHOOTING
Error
message in
Portal with
status
You can see these messages from "e-Ledger Report" screen of
Portal
System Status Error message Solution
Portal 2Error occurred when
reading Ledger (txt)
Check whether disk is full or not. If it is
not then open OSS note.
Portal 6General Ledger and
Journal is not
compatible
Check the difference from e-Ledger
Report Page and fix it from ERP side.
Then delete the general ledger from e-
Ledger Portal and trigger again.
Portal 13Database connection
error while reading
Accountant
Trigger ledger again e-Ledger Report
Page. If error continues open OSS Note.
Portal 14An error occurred while
reading company code
data or tmp xml file
Trigger ledger again e-Ledger Report
Page. If error continues open OSS Note.
Portal 41An error occurred
during ledger sigining
process
Control the signer tool. Check token was
removed or HSM disconnected. Fix them,
restart the tomcat service and trigger
ledger from e-Ledger Report Page again.
Portal 51An error occurred while
creating certificate file
Open OSS Note.
Portal 61An error occurred while
signing certificate file
Control the signer tool. Check token was
removed or HSM disconnected. Also
check if sign server can reach
http://kamusm.gov.tr for getting
timestamp. Fix this errors, restart the
tomcat service and trigger ledger from e-
Ledger Report Page again.
FIT Solutions® 45
Portal 81An error occurred in
Ledger Schema Control
Check the error on e-Ledger Report Page.
If the error is something you can fix from
Portal or ERP fix it and trigger ledger
again. If not please open OSS Note.
Portal 91An error occurred in
Certificate File Schema
Control
Check the error on e-Ledger Report Page.
If the error is something you can fix from
Portal or ERP fix it and trigger ledger
again. If not please open OSS Note.
Portal 101An error occurred
during archiving
process
Check disk is not full. If it is ok then
create OSS note.
Error
message in
Portal
without
status
You can see these messages from "e-Ledger Process" screen
of Portal on a pop-up screen while triggering e-Ledger
creation process
System Error Description Solution
Portal Job creation
error!
e-ledger sending job
cannot be created in R3
side.
There occurred any technical problem
while creationg job in R3 side.Triger e-
ledger sending again.If the problem
continues please ask your basis team
why job creation fails.
Portal The
program of
creation
Ledger
Journal
could not be
started!
Document journal
sending program cannot
be executed.
There occurred any technical problem
while executing document journal data
sending program in ECC side. Trigger e-
ledger sending.If the problem continues
please inform ABAP team who developed
ABAP part of e-Ledger project.
Portal Maintain
the
/FITE/LDG_
T001 table.
/FITE/LDG_T001 table
wasn’t maintained
correctly.
/FITE/LDG_T001 stores some company
specific data for e-ledger processing.So
this table must be filled in a correct
way.Please inform ABAP team who
developed ABAP part of e-Ledger project.
Portal
FIT Solutions® 46
Portal The
program of
creation
General
Ledger
could not be
started!
General Ledger creation
program cannot be
executed.
There occurred any technical problem
while executing general ledger sending
program in R3 side. Triger e-ledger
creation again.If the problem continues
ABAP team who developed ABAP part of
e-Ledger project.
Portal Ledger
Journal
which
belongs to
these date
range has
not been
created yet.
You triggered a general
ledger sending but there
wasn’t a document
journal created with the
same period before.
If you want to send a general ledger data
for a period,you must send a document
journal with the same period before.At
first you trigger document journal
sending with the same period please.
Portal There is and
inconsistenc
y between &
table and
/FITE/LDG_
T005 table.
There is an
inconsistency between
document journal
number value in the SAP
standart table TRVOR/
FAGL_TRVOR and
/FITE/LDG_T005.
Please inform ABAP team who developed
ABAP part of e-Ledger project.
Portal More than
one & can
not be run
at the same
time!
Please, try
again later.
There is still a running
e-ledger sending
process for document
journal or general
ledger and you have
triggered one more
sending for a company
at the same time .
You cannot send more than one
document journal or general ledger for a
company at the same time .Please wait
for finishing the active job’s operation
and try again.
Portal e-Ledger
sending
processes
have been
completed
fort his
period!
e-Ledger sending
processes have been
completed successfully
for this month.
You shouldn't trigger e-ledger sending
process for a completed period.
Portal First date of
the period
must be &!
First date of the
triggering period should
be &!
You should trigger e-Ledger sending
processes with correct date
interval.Please trigger e-ledger sending
processes with first date &.
FIT Solutions® 47
Error
message in
ECC for e-
Ledger
Creation
Job
You can see these messages from e-Ledger Creation job's logs
via sm37 transaction code.
This job's name begins with 'EDEFTER_'.
System Error Description Solution
ECC <account>
numbered
account
must be in
<chart of
accounts>
account
plan which
has
<Financial
Statement
Version> !
An account in the
created e-ledger isn’t
defined under Financial
Statement Version that
used for e-ledger.
You must add the account into Financial
Statement Version that used for e-ledger.
ECC Maintain
the
/FITE/LDG_
T006 table!
/FITE/LDG_T006 table
must be maintained.
Please inform ABAP team who developed
ABAP part of e-Ledger project.
ECC Document
selection
must be
done in
consideratio
n of &.
Otherwise,
ledger
journal
remains
incompleted
.
you try to create a
document journal for an
error period.
There musn’t be any date gap between
document journal periods .Please trigger
document journal creation considering
this.
ECC Documents
must be
seletected
in
consideratio
n of &.
Otherwise,
You try to create a
document journal for an
error period.
There musn’t be any conflicts between
document journal periods .Please trigger
document journal creation considering
this.
FIT Solutions® 48
period
amounts are
mistake.
ECC &2
document
type in &1
company
code is not
in scope of
e-Ledger.
&2 accounting
document type is not in
the e-Ledger scope for
&1 company code!
All accounting document types which are
related to e-ledger , should be stored at
/FITE/LDG_T002 table.Please don't add a
new acconting document type to this
table , inform ABAP team who developed
ABAP part of e-Ledger project.
ECC An error
occured
when
created e-
Ledger is
written to
&2 table
Created e-Ledger &1
data, couldn't be written
to the table &2!
Please inform ABAP team who developed
ABAP part of e-Ledger project.
ECC Maintain
the
/FITE/LDG_
T001 table!
/FITE/LDG_T001 table
wasn’t maintained
correctly.
/FITE/LDG_T001 stores some company
specific data for e-ledger processing.So
this table must be filled in a correct
way.Please inform ABAP team who
developed ABAP part of e-Ledger project.
ECC At the same
time, more
than one
Ledger
Journal can
not be run!
Please try
again later.
There is still a running
e-ledger creation job
and you have triggered
one more creation for a
company at the same
time .
Please wait for finishing the active job’s
operation and try again.
ECC Ledger
creation
processes
has been
already
completed
for this
period.
e-Ledger creation
processes have been
completed for this
period already!
There is already created e-ledger data for
given perion.If you want to create e-
ledger data for the same period
again,please reset e-ledger creation
processes for this period via e-Ledger
period reset report(transaction code
/FITE/LDG_R02)
ECC There is
inconsistenc
y beetween
There is an
inconsistency between
document journal
Please inform ABAP team who developed
ABAP part of e-Ledger project.
FIT Solutions® 49
& table and
/FITE/LDG_
T005 tables!
number value in the SAP
standart table TRVOR/
FAGL_TRVOR and
/FITE/LDG_T005.
ECC Journal
Ledger item
and line
number
must be
passed to
their last
value(&1,&2
)!
Document journal
number and document
journal line number
values should be reset to
old values(&1,&2)!
Please inform ABAP team who developed
ABAP part of e-Ledger project.
ECC Job creation
error!
e-ledger creation job
cannot be created in R3
side.
There occurred any technical problem
while creationg job in R3 side.Triger e-
ledger creation again.If the problem
continues please ask your basis team
why job creation fails.
ECC Ledger
Journal
creation
program
could not be
started!
e-Ledger creation
program program
cannot be executed.
There occurred any technical problem
while executing e-Ledger data creation
program in ECC side. Run e-ledger
creation program again.If the problem
continues please inform ABAP team who
developed ABAP part of e-Ledger project.
Error
message in
ECC for e-
Ledger
Sending
Job
You can see these messages from e-Ledger Creation job's logs
via sm37 transaction code.
This job's name begins with 'YEVMIYE_' or 'KEBIR_' or
'JOURNAL' or 'GNRL'
System Error Description Solution
ECC Maintain
the
/FITE/LDG_
T001 table!
/FITE/LDG_T001 table
wasn’t maintained
correctly.
/FITE/LDG_T001 stores some company
specific data for e-ledger processing.So
this table must be filled in a correct
way.Please inform ABAP team who
developed ABAP part of e-Ledger project.
FIT Solutions® 50
ECC e-Ledger
has not
been
created fot
&1-&2!
No e-Ledger data
created for period &1-
&2
Please create e-Ledger data for given
period at first
ECC Accounting
record
could not
found for
&1-&2!
No e-Ledger data could
be found for period &1-
&2
e-Ledger creation program has been
completed for given period but there is
no accounting document entries for
given period.Please trigger a another
period that includes accounting
document entries
There might be got different error while sending created e-ledger data.Please inform
ABAP team who developed ABAP part of e-Ledger project
for the rest of errors
