1 SAP Note 1825984 - Implementation instructions
1.1 Type-A and Type-B common actions
1. Create a customer message to SAP (http://service.sap.com/message) using component XX-CSC-GR and
requesting the transport files for note 1825984. Don’t forget to mention in the message your C-CEE add-on
version & SP level. Minimum required C-CEE version is 110_600 at SP level 0012.
2. Import the transport request that you‘ll receive from SAP in your system(s).
This transport contains the needed corrections and enhancements only for the standard Hellenization objects
(i.e. programs, tables, etc. belonging to the C-CEE add-on and have names starting with J_1G* and J_2G*).
Note that the above steps 1. and 2. are not necessary if your C-CEE add-on is at an SP level greater than the SP in
which note 1825984 is delivered (see “Correction delivered in Support Package” section of the note).
3. Copy the required corrections from the standard J printing programs to your Z/Y copies using suitable ABAP
editing tools (transaction SE38 or SE80).
In order to track down the changes that you have to copy, you can search in the standard printing programs
J_2GLPPSD, J_2GLPPDL, J_2GLPPMM, and J_2GPFI, for string “n1825984” (without the quotes).
4. Use transaction J2GLPP4 to assign a valid Document Code to every Print Task Code that will send data to GSIS.
Note that the assigned Document Code determines also if the values that will be sent to GSIS will be prosthetic,
subtractive, or zero.
5. Optional: If it is applicable for your business to send the Customer Receipt Card Number (Αριθμόσ Κάρτασ
Αποδείξεων Πελάτη) you should first maintain it in a suitable text field of the Customer's master data in
transactions FD02 or XD02. The field to be used must be a field of table KNA1 (Customer Master Data) or table
ADDR1_DATA (Address data), and must also be declared in Hellenization’s customizing transaction J2GFMD
(Figure 1).
Figure 1
1.2 Type-A only
Additionally for Type-A devices you have to add an additional line in all relevant SAPScript Forms.
You can maintain the forms after common action 3.
Note that the elements described below can also be found in the standard forms J_2GLP_DAMM, J_2GLP_DASD,
J_2GLP_DATIM, J_2GLP_TIM, J_2G_FI, J_2G_FI_MULT, and used for copying/pasting things from there.
In transaction SE71 and for every form in use, make the following changes to the form in its original language.
1. Create a paragraph format named VS using the smallest possible size of a proportional font of your choice. By
using a small size we want to avoid having the “e.txt” data string spreading in more than one line.
Do not maintain any other attributes of the paragraph format except the ones shown in the above screenshots.
2. Create a new window named EDAT.
3. Create the following text-element ESTR in window EDAT.
For SD, MM forms:
For FI forms:
Note that depending on the Type-A driver in use, you may need to change the contents of the EDAT windows in
order to better satisfy your driver’s requirements.
For example if a Type-A driver does not require start – end markings, and also expects to find a string with
positions for all 22 fields of the e.txt file (see the table in paragraph 1.3), then the EDAT window for
SD, MM forms, should be as shown below:
4. Create a page window in each page for window EDAT in a way that it is positioned at the bottom of each page
(of course you‘ll have to use different margins than the ones shown below, according to the geometry of your
form).
Following figure shows the corresponding page layout where window EDAT is positioned at the bottom.
5. Save and activate the form.
In case the form is defined in more than one language, don’t forget to make the same changes also in the other
languages.
1.3 Testing the new functionality
For testing the new functionality, you‘ll have to test all your print cases (invoices, credit memos, cancellations, etc).
According to POL 1221 for each printed document the following information is going to be sent to GSIS:
Field EN
Field EL
Max length Filled by
Issuer TIN
ΑΦΜ Εκδότη
12
TaxSpooler or Type-A Driver
Recipient TIN
ΑΦΜ Παραλήπτη
12
SAP
S/N SSFDRS
S/N ΕΑΦΔΣΣ
12
TaxSpooler or Type-A Driver
Customer Receipt Nr
Αρ. Κάρτασ Αποδείξεων Πελάτη
19
SAP
Date & Time
Ημερομηνία και Ώρα
12
TaxSpooler or Type-A Driver
S/N Daily Markings
Α/Α Ημερήςιων Σημάνςεων
5
TaxSpooler or Type-A Driver
S/N Overall Markings
Α/Α Προοδευτικών Σημάνςεων
5
TaxSpooler or Type-A Driver
Number Z
Αριθμόσ Ζ
4
TaxSpooler or Type-A Driver
Type of Voucher
Είδοσ Παραςτατικοφ
4
SAP
Validation Number
Σειρά Θεώρηςησ
10
SAP
Voucher Number
Αριθμόσ Παραςτατικοφ
10
SAP
Net Value A
Καθαρό Ποςό Α
18:2
SAP
Net Value B
Καθαρό Ποςό Β
18:2
SAP
Net Value C
Καθαρό Ποςό Γ
18:2
SAP
Net Value D
Καθαρό Ποςό Δ
18:2
SAP
Net Value E
Καθαρό Ποςό Ε
18:2
SAP
VAT A
ΦΠΑ Α
18:2
SAP
VAT B
ΦΠΑ Β
18:2
SAP
VAT C
ΦΠΑ Γ
18:2
SAP
VAT D
ΦΠΑ Δ
18:2
SAP
Total Sum of Voucher
Σφνολο Παραςτατικοφ
18:2
SAP
Currency Code
Κωδικόσ νομίςματοσ
1
SAP
Note also the following:
 The fields of the e.txt file are of variable length and are divided by the character «;» (semicolon delimited).
 In the numerical fields that contain sums (Net Value A …Total Sum of Voucher) the sums are with 2 decimal
points and the decimal point is represented by a full stop «.» . No symbols that separate triplets of numbers
(hundreds, thousands etc) are used.
 A zero sum is represented as 0.00.
 Negative sums are represented as in the following example: ;-100.00;-10.00;0.00;0.00; .
 The date and time have the following formatting: YYYYMMDDHHmm where YYYY is the year MM the month, DD
the day, HH the hour, mm the minutes.
 The currency code for Euro is 0.


The Ζ number is the one that will include the voucher, namely the Z number of the previous day increased by 1.
The type of document (voucher) is assigned a value according to transaction J2GLPP4.
1.3.1 Type-B
Before upgrading TaxSpooler you should be able to find the 16 fields sent by SAP in lines 1 – 16 of the “a.txt” file.
Check that their values are correct in accordance with the printed document.
After upgrading TaxSpooler you should be able to find all 22 fields in the “e.txt” file. Check that all fields have the
correct values.
Both files are located locally on the PC where TaxSpooler runs.
1.3.2 Type-A
Before (or after) upgrading your Type-A driver you should be able to see the string with the 16 fields sent by SAP at
the end of the last page of your printout. Check that it contains the correct values.
After upgrading your Type-A driver you should be able to find all 22 fields in the corresponding “e.txt” file. Check
that all fields have the correct values.
Note that some Type-A drivers may have the capability of removing the string after they read it, so after upgrading
the driver you may not be able to see the string at the last page…
Good luck!