2017-06-27 Page 1/11

1920686 - eSocial: FAQ

Version 34 Type SAP Note
Language English Master Language English
Priority Recommendations / Additional Info Category FAQ
Release Status Released for Customer Released On 27.04.2017
Component PY-BR (Brazil)

Please find the original document at https://launchpad.support.sap.com/#/notes/1920686

Symptom

This SAP Note publishes a list of frequently asked questions that relate to eSocial, published on Executive
Declaratory Act N. 5 on July 17th, 2013 (see also related SAP Note 1575963).

Although every effort has been made to provide a thorough set of FAQs in this SAP Note, this document is
not exhaustive. If additional FAQs arise, this SAP Note will be updated to reflect the most current and
accurate information.

If your question is not answered in this SAP Note, log a corresponding customer message in SAP Support
Portal.

Business Processes

1. Q. Where can I find documentation for eSocial?

2. Q. Are the S-1010 events required for S-1200 event?
3. Q. If I changed a wage type customizing I need to regenerate the S-1010 event?
4. Q. The period of eSocial table events is composed by month and year, but in the system the stored
period is composed by day, month and year. How does SAP deal with table entries?
5. Q. Does the S-1200 event make use of the wage type evaluation class 15?
6. Q. Why do I have to select the event type 2220 to run event S-2205 Alteração de dados cadastrais do
trabalhador?
7. Q. Why there are four event types to generate event S-2230 Afastamento temporário?
8. Q. How can I make the framework skip the status "Ready for verification" when generating an event?
9. Q. What information should be filled regarding the Software House fields on S-1000 event?

General

1. Q. What is the best way to install the eSocial solution?

2. Q. If I do not want to use SOA Manager, what should I do?
3. Q. Will the XML file be generated in the ERP-HR system?
4. Q. What are the prerequisites for SOA Manager?
5. Q. How do I know in which delivery phase a part of the eSocial events has been delivered?
6. Q. How can I run the S-3000 event?
7. Q. What are the advantages of installing the CLC packages?
8. Q. If I do not use SOA Manager, can I maintain the events using the eSocial Events Monitor?

Framework

1. Q. How can I implement my own event?

2. SAP SE or an SAP affiliate company. All rights reserved

© 2017
2017-06-27 Page 2/11
2. Q. Which component will do the digital signature?
3. Q. Why did not SAP create BAdIs for the events that are out-of-scope?
4. Q. Will customer developed events be supported by eSocial framework delivered in the SAP standard?
5. Q. How does the SAP delivered eSocial framework control which events were and which were not sent
to Government?
6. Q. If I do not use SOA Manager, do I have to implement my own data extractor class (business class)?
7. Q. How does the change/deletion/rectification of events work in the eSocial framework?
8. Q. Does the extractor class need to treat modifications and deletions of records to generate the
rectification events?
9. Q. How does the framework identify that an event was deleted?
10. Q. Will the log that is generated when I modify an infotype in PA30 transaction work for customer
infotypes?
11. Q. Is the log in PA30 that is used for eSocial the same log that is stored in the PCL4 cluster?
12. Q. If I do not have in my system the PA30 log that is created for eSocial, what I have to do to run the
rectifications and deletions of events?
13. Q. Do the table events have change log as the infotypes for eSocial?
14. Q. What is the consequence of executing multiple times the extractor logic for the same selection in
production mode?
15. Q. How can I find the source code that fills a field?
16. Q. If I create my own infotype, can I customize it to generate eSocial events when I maintain the
infotype?
17. Q. Can we have more than one event type generating the same eSocial event?
18. Q. SAP does not cover the data extraction for all events, and for these events, do we have to create
the data structures and tables?
19. Q. How can I delete events that I generated for testing from my database?
20. Q. What is the difference between the event type and the legal event type fields in T7BREFD_EVTYPE
and T7BREFD_EVTY_C tables?
21. Q. Why are there fields in the output display of the generators reports that do not belong to the eSocial
layout?

Relevant notes for eSocial solution

1. Digital Signature and transmission

Other Terms

eSocial; FAQ

Solution

Business Processes

1. Q. Where can I find documentation for eSocial?

A. Documentation for eSocial is available in the system and in the SAP Help Portal. System
documentation (like transactions, field help, customizing, messages, features) is delivered via Support
Packages. SAP Help Portal documentation is available under http://help.sap.com/bscserp/ ->Application
Help English ->Americas ->Brazil ->Payroll Brazil (PY-BR) ->Final Activities ->eSocial.

You can find the most recent version of the SAP Help Portal documentation at
http://service.sap.com/hrbr ->Resources ->eSocial - SAP Help Portal Documentation (<Month, Year>).

2. Q. Are the S-1010 events required for S-1200 event?

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-06-27 Page 3/11

A. The S-1010 events are required to generate the S-1200 events, because the S-1200 event
implementation makes use of the S-1010 wage types attributes. The S-1300 event does not require the
event S-1010, as it does not report wage type, but it reports tax information.

3. Q. If I changed a wage type customizing I need to regenerate the S-1010 event?

A. Yes, in case you change an accumulation class of the wage type or you modify the customizing of the
V_T596J table for the wage type. It is not necessary to regenerate the event S-1010 in case you modify
the value of the evaluation class 15 of the wage type.

4. Q. The period of eSocial table events is composed by month and year, but in the system the stored period
is composed by day, month and year. How does SAP deal with table entries?

A. In the system tables, the validity of the entries is made with day, month and year. Because eSocial
requires this information on month granularity, the following rules were applied:

If a customizing entry starts and ends in the same month it is disregarded by the events.
If a customizing entry starts in the middle of the month, this entry is considered to start at the
beginning of the month to be reported to eSocial.
If a customizing entry ends in the middle of the month, this entry is considered to end at the last
day of the previous month to be reported to eSocial.

5. Q. Does the S-1200 event make use of the wage type evaluation class 15?

A. Yes, both events use the evaluation class 15 of the wage types to deal with the wage type signal. For
example, if you customize a wage type with value "DR" or "P", the eSocial events will keep the wage
type signal to report it.

6. Q. Why do I have to select the event type 2220 to run event S-2205 Alteração de dados cadastrais do
trabalhador?

A. The event type field in the selection screen of eSocial generator reports holds the internal information
to identify each way of running the events. In other words, the event type that you select in the selection
screen of the reports is not the event type defined by the eSocial layout (like S-2205). For each internal
event type, there is a legal event type that is defined in the T7BREFD_EVTYPE and T7BREFD_EVTY_C
tables (in Customizing, see Cálculo das folhas de pagamento ->Cálc.folha pagamento Brasil ->eSocial -
>Configurações básicas ->Definir tipos de eventos). When you run the generator report with the event
type 2220, you will run the eSocial event S-2205, because S-2205 is the eSocial event that is defined for
event type 2220.

7. Q. Why there are four event types to generate event S-2230 Afastamento temporário?

A. The S-2230 Afastamento temporário event has three different kinds of information: start of temporary
absence, return from temporary absence, and change to temporary absence reason. For this reason, there
are four ways of generating the event:

1) Event type 307 runs only the start of temporary absence.

2) Event type 309 runs only the return from temporary absence.

3) Event type 308 runs only the change to temporary absence reason.

4) Event type 306 runs all event types together: 307, 308 and 309.

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-06-27 Page 4/11
8. Q. How can I make the framework skip the status "Ready for verification" when generating an event?

A. You can customize the V_T7BREFD_EVTYPE or V_T7BREFD_EVTY_C views (in Customizing, see
Cálculo das folhas de pagamento -> Cálc.folha pagamento Brasil -> eSocial -> Configurações básicas -
> Definir tipos de eventos) to skip the "Ready for verification" status when generating new events by the
generator reports. Also, you can use the BAdI: eSocial - definição do status inicial dos eventos
(HRPAYBR_EFD_INITIAL_STATUS) to implement specific code to define different rules to skip the
"Ready for verification" status.

9. Q. What information should be filled regarding the Software House fields on S-1000 event?

A. The following information can be filled to generate the Software House fiels on S-1000 event:

1) CNPJ da Software House: 74.544.297/0001-92

2) Razão Social: SAP Brasil Ltda

3) Nome de Contato: Inayara de Souza

4) Telefone: 11 5503-2400

General

1. Q. What is the best way to install the eSocial solution?

A. SAP recommends the installation of the eSocial by applying the HR Support Packages or the CLC
packages. The HR Support Packages are released monthly and they contain objects from all HR
components and countries, including the international functionality. The CLC packages contain only the
country specific objects. The Brazilian CLC packages will basically include the content described in the
eSocial SAP Notes. In other words, installing the Brazilian CLC packages, you will have the eSocial
content with less risk and effort than installing the eSocial notes individually. It has less risk because it
will install in your system all the needed objects, and it has less effort because it is done without the
need of executing manual steps.

2. Q. If I do not want to use SOA Manager, what should I do?

A. You have to develop your own transmission class (which uses the interface
IF_HRPAYBR_EFDF_DATA_TRANS) that will contain the logic to send and receive messages (XML) to
Government authority. And, for each event type (V_T7BREFD_EVTYPE) you have to customize the
transmission class you created.

3. Q. Will the XML file be generated in the ERP-HR system?

A. Yes. With the standard solution the XML-file will be generated in the ERP-HR system, and the SOA
Manager is the default component to transmit the XML to the government.

4. Q. What are the prerequisites for SOA Manager?

A. The prerequisites for SOA Manager are the same required by the eSocial Solution. This information
can be checked in the announcement note 1575963 (LC Announcement: eSocial).

5. Q. How do I know in which delivery phase a part of the eSocial events has been delivered?

A. All delivery notes of the legal change eSocial are listed in the references of the announcement note
1575963 (LC Announcement: eSocial).
© 2017 SAP SE or an SAP affiliate company. All rights reserved
2017-06-27 Page 5/11

6. Q. How can I run the S-3000 event?

A. The S-3000 event is generated automatically by the eSocial framework. It is generated when an
employee master data was deleted and the old information was already sent to the government, then
the framework evaluates that there was an event for that master data and now there is not. This process
works because the extractor classes of the events always generate the events as a "picture" of the
database. For example, if you create an absence for the employee, the extractor class will generate an
event to eSocial. If you delete this absence, the data extractor class will not generate the absence event,
but the framework will automatically identify that you had generated it before and in the current
execution it was not generated. In this scenario, the event S-3000 will be triggered by the framework.

7. Q. What are the advantages of installing the CLC packages?

A. The CLC packages contain the SAP Notes delivered by a country solution in a determined period.
Therefore, the CLC packages for the Brazilian solution contain just the SAP Notes delivered which
belong to the application components PY-BR and PA-PA-BR (software component SAP_HRCBR).

When you install a CLC package, this action has the same effect of the manual installation of each SAP
Note individually, but with fewer risks. When you install the Brazilian CLC packages, you are not
installing enhancements and corrections of other components, like time management, personnel
administration or international payroll. The enhancements and corrections of these other components
occur twice a year, in the synchronization Support Packages.

Internally, the CLC installation has the same effect of a Support Package installation. In other words,
when you install a CLC you make the installation of future SAP Notes easier, because the notes will
have fewer prerequisites.

8. Q. If I do not use SOA Manager, can I maintain the events using the eSocial Events Monitor?

A. Yes. The eSocial Events Monitor is charge of controlling the events statuses. It allows the
implementation of interfaces in order to run the web services, it means that, with an extra
implementation, you can make the eSocial Events Monitor connect with any Web Service technology.

Framework

1. Q. How can I implement my own event (event that is not supported by SAP)?

A. Please read the cookbook document ("How To Create a new event for e-Social_v1.x.pdf") that is
attached to this SAP Note, which contains technical information on how you can implement your own
event.

2. Q. Which component will do the digital signature?

A. The digital signature will be done by the ERP (SAP_HR) component.

3. Q. Why did not SAP create BAdIs for the events that are out-of-scope?

A. All relevant events are implemented by an ABAP class that uses the interface
IF_HRPAYBR_EFDF_DATA_EXTRACTOR. For events that are out-of-scope you can implement your
own ABAP class that contains logic for the event, and this class must implement the OO interface
IF_HRPAYBR_EFDF_DATA_EXTRACTOR and assign it to the event type via table view

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-06-27 Page 6/11
V_T7BREFD_EVTYPE. The implementation of ABAP OO interfaces is similar to the implementation of
BAdIs, and it gives more flexibility than BAdIs would provide. For more details, see the answer of
question 1.

4. Q. Will customer developed events be supported by eSocial framework delivered in the SAP standard?

A. Yes. If all necessary implementation steps have been done correctly then the customer-event will be
processed properly. For more details, see the answer of question 1.

5. Q. How does the SAP delivered eSocial framework control which events were and which were not sent to
Government?

A. The eSocial stores in the database the event data of every event that was sent to the Government,
then this database will be used by the framework to control what should and what should not be sent to
the Government.

6. Q. If I do not use SOA Manager, do I have to implement my own data extractor class (business class)?

A. No, in this case you can reuse the standard extract class (the one that uses the interface
IF_HRPAYBR_EFDF_DATA_EXTRACTOR) and implement your own transmission class.

7. Q. How does the change/deletion/rectification of events work in the eSocial framework?

A. The business classes of the events always generate all the events considering what you chose in the
selection screen of the generator report. The framework evaluates what you chose to generate the
change/deletion/rectification for each event.

For example, when you run the S-2230 (Temporary Absence) event, the business class will generate all
the events considering the employee and period you chose in the selection screen of the generator
report. The framework evaluates each event generated and compares them with the events that were
already sent for the same selection period and employee you chose in the selection screen. After that,
the framework generates the necessary deletion and rectification.

There are different rules for table events and employee events:

Table events: table events do not have rectification, they have insertion, change and deletion
instead. This means that if you want to change or delete a table event, you have to fill in some
fields that indicate the operation that you performing and send the event again.

For these events, there is no log mechanism to identify what was changed since the last time you
sent the event to the legal authorities. So, the business class always generates all events for the
selection period and the framework evaluates each event according to the following rules:

The event has not been sent yet: the event is sent as insertion.
The event has been sent and there is no difference in the data: the event is not sent.
The event has been sent and there are differences in the data: the event is sent as a change
event.
An event with a specific key has already been sent, but it has not been currently generated:
the event is sent as a deletion.

Employee events: for employee events it is possible to send rectifications and deletions. Because
these events generally depend on employee master data (infotype), there is a log mechanism to
identify which period should be generated again for the employee.

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-06-27 Page 7/11
The business classes work with the same concept of the Table events by generating all the events
in the selection period, and then the framework evaluates each event according to the following
rules:

The event has not been sent yet: the event is sent.
The event has been sent and there is no difference in the data: the event is not sent.
The event has been sent and there are differences in the data: the event is sent as a
rectification.
An event with a specific key has already been sent, but it has not been currently generated:
the event S-3000 (Deletion) is generated and sent instead.

Payroll events: for payroll events it is possible to send rectifications and deletions.

The business classes work with the same concept of the Employee events by generating all the
events in the selection period, and then the framework evaluates each event according to the
following rules:

The event has not been sent yet: the event is sent.
The event has been sent and there is no difference in the data: the event is not sent.
The event has been sent and there are differences in the data: the event is sent as a
rectification.
An event with a specific key has already been sent, but it has not been currently generated:
the event S-3000 (Deletion) is generated and sent instead.

8. Q. Does the extractor class need to treat modifications and deletions of records to generate the
rectification events?

A. No. The extractor class has to select the data from the database and fill the event's data considering
the selection criteria. It always generates all the events considering the selection and the framework
evaluates what was generated by the extractor class to:

Discard if the event was already sent;

Generate a rectification if the event was already sent but some data has changed;

Generate a deletion event if there was an event that was not generated now by the extractor class.

9. Q. How does the framework identify that an event was deleted?

A. The framework stores each event that was generated and manages its status. With this information,
the framework is able to identify what was and what was not sent to the Government yet. For example:
You create an entry in infotype 2001 (Absences) for an employee. You run the generator report
selecting the employee and period for the Temporary Absence event (S-2230). The extractor class will
read the infotype and generate the Temporary Absence event for the relevant period. After that, you
send this event to the Government. Now you delete the infotype 2001 you created before, and run the
generator report for the same employee and period, the extractor class of Temporary Absence will not
find any infotype for the selection period and will not generate any event. The framework will identify that
you have previously sent to the Government an event for the employee in the selection period, and now
the extractor class did not generate any event, then the event that was already sent to the Government
should be deleted. Then the framework generates a deletion event automatically.

10. Q. Will the log that is generated when I modify an infotype in PA30 transaction work for customer
infotypes?

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-06-27 Page 8/11
A. Yes. The log that is generated by the PA30 transaction is customized in the table
T7BREFD_ITEVTRIG, which can be customized with customers specific infotypes.

11. Q. Is the log in PA30 that is used for eSocial the same log that is stored in the PCL4 cluster?

A. No. The log used by the eSocial is a specific log delivered by the eSocial and it is stored in the table
T7BREFD_EVTOGEN. This table is maintained by a delivered BAdI implementation of infotype
functionality. This table stores: the personal number, the event type that needs to be generated, the
begin and end date.

12. Q. If I do not have in my system the PA30 log that is created for eSocial, what I have to do to run the
rectifications and deletions of events?

A. The log that is used by the eSocial functionality is used to accelerate the execution of the generators
report. It means that, if you run the generators report selecting all the employees and a very large
period, the eSocial framework will be able to generate the rectifications and deletions of the events
normally.

13. Q. Do the table events have change log as the infotypes for eSocial?

A. No. As the tables events depend pretty much of customizing tables, a log mechanism is not possible
because of the system landscape. For these events, we recommend that you run the generator report
with some frequency, selecting the whole period.

14. Q. What is the consequence of executing multiple times the extractor logic for the same selection in
production mode?

A. In the first execution the framework will save in the database the event with status "Ready for
verification". Up to the second execution the behavior of the framework is different according to the
event status that was generated in the first execution:

Status: Ready for verification, Ready for send, Waiting correction and Manually cancelled

The framework compares the content of the event generated now and the one that is already stored
in the database. In case the content is different the event data is updated in the database.

Status: Accepted

The framework changes the status of the first event to Obsolete and set the current event as a
rectification.

Status: Waiting correction, Obsolete

The framework ignores the event current generated.

15. Q. How can I find the source code that fills a field?

A. Each eSocial event type has a process called data extraction, which reads data from the database
and saves it on eSocial tables (for more information about the eSocial framework, see question 1). The
data extraction process is executed by an extraction class that is customized in the
V_T7BREFD_EVTYPE view, and it holds the entire logic to fill all the fields required by the event. Each
field of the layout corresponds to a field in an eSocial table.

To find out a source code of a field, follow the steps below:

© 2017 1.
SAP SE or an SAP affiliate company. All rights reserved
2017-06-27 Page 9/11
1. Get the name of the processing class of the event by entering the V_T7BREFD_EVTY_C view in
transaction SM30. If you do not find the processing class in that view, enter the
V_T7BREFD_EVTYPE view.
2. Open the processing class you found in transaction SE24.
3. Find the data structure of the event by entering method
IF_HRPAYBR_EFDF_DATA_EXTRACTOR~CREATE_STRUCTURE and looking for a code like "
CREATE DATA rr_data TYPE hrpadbr_efde_s_employer_info." - in this code, the data structure is
"HRPADBR_EFDE_S_EMPLOYER_INFO".
4. Open the data structure that in you found in step 3 by entering transaction SE11. Find out which
table and field is the one for which you want to find out the source code. The data structure of the
event contains all fields needed by the layout:
The data structure has fields that are structures of eSocial tables.
Each field of the layout corresponds to a field in an eSocial table.
The data structure can also contain deep structures.
6. Search for the field and table that you have identified by returning to the processing class in SE24
transaction. There you can find the source code that fills the field.

Note that the XML technical fields are filled by the framework.

16. Q. If I create my own infotype, can I customize it to generate eSocial events when I maintain the
infotype?

A. Yes. In the V_T7BREFD_ITEVTR you are able to customize which infotype fields are relevant to
trigger an eSocial event. In this table, you can enter the infotype number, subtype, field and which
eSocial events have to be executed in case of any kind of maintenance.

17. Q. Can we have more than one event type generating the same eSocial event?

A. Yes. In the eSocial framework there is a field to store which eSocial event code the event type
(eSocial legal code in V_T7BREFD_EVTYPE table view) corresponds to. It means that you can have
more than one implementation of the same eSocial event linked to the same eSocial legal code. For
example, you can use the SAP implementation of the event S-1200 (event type equals to 1200) to
generate S-1200 events related to regular employees, and you can create your own implementation of
event S-1200 (e.g. event type 9200) to generate S-1200 event related to employees category not
covered by SAP standard solution.

18. Q. SAP does not cover the data extraction for all events, and for these events, do we have to create the
data structures and tables?

A. No. SAP delivers the data structures and application tables for all eSocial events, even the ones
which data extraction is not covered in the standard. You can find the list of tables and structures for
each event in Customizing: Cálculo das folhas de pagamento ->Cálc.folha pagamento Brasil ->eSocial -
>Configurações básicas-> Implementar eventos não cobertos pelo sistema padrão.

19. Q. How can I delete events that I generated for testing from my database?

A. The change manager developed for eSocial is in charge of this task, so you do not need to delete test
events manually. In case you generated some events in your test environment, and after that, you have
deleted the data that is the source for the events (for example, employee infotypes or customizing
settings), you just have to run the eSocial generator reports again with a wide selection in order to make
the corrections in the eSocial database. Additionally you can run the report eSocial: Exclusão de
eventos/lotes (RPU_PAYBR_EFD_EVT_DELETION) to delete the test events.

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-06-27 Page 10/11
20. Q. What is the difference between the event type and the legal event type fields in T7BREFD_EVTYPE
and T7BREFD_EVTY_C tables?

A. The legal event type (LEGAL_EVENT_TYPE) identifies the event type code defined by the eSocial
layout, like S-1000, S-2200. The event type (EVENT_TYPE) field identifies an extractor class for
generating the events, in other words, it identifies different ways of generating events for eSocial. For
example, event types 1030 and 1031 generate legal event type S-1030, but with different data sources.

21. Q. Why are there fields in the output display of the generators reports that do not belong to the eSocial
layout?

A. The output display of the generators reports displays all the fields that are in the tables, used by the
event implementation (see question 1 to understand how the event is stored in the database). Generally,
the data of the events are stored in many tables in the database. As many events have similar
information (such S-2100 and S-2200), some of the tables are reused in more than one event.

For example: in case the event type 1 has the fields 'A', 'B' and 'C'; and the event type 2 has the fields
'B', 'C' and 'D', it is possible to create just one table in the database that is shared by both events with
the fields 'A', 'B', 'C', and 'D'. Then, in the output display of both event types, all the fields of the table are
displayed even though the field 'D' is not relevant for event type 1, and field 'A' is not relevant for event
type 2.

The eSocial's XML will consider only the relevant fields for the event. In the example above, the
generation of the event type 1 will not take into consideration the field 'D' of the table.

Relevant notes for eSocial solution*

1. Digital Signature and transmission

2427966 - Fixes in CommonCryptoLib 8.5.10

(*) This list is not to be considered as complete. Further SAP Notes might be added in future.

Software Components

Software Component Release

SAP_HRCBR 600 - 600

SAP_HRCBR 604 - 604

SAP_HRCBR 608 - 608

Other Components

Component Description

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-06-27 Page 11/11
PA-PA-BR Brazil

This document refers to

SAP Note/KBA Title

2427966 Fixes in CommonCryptoLib 8.5.10

1916329 eSocial: Release Phase I

1575963 LC Announcement: eSocial

This document is referenced by

SAP Note/KBA Title

1575963 LC Announcement: eSocial

2033144 eSocial: External Cockpit - Phase 2014/12

1916329 eSocial: Release Phase I

Attachments

File
File Name Mime Type
Size

How To Create a new event for e-Social_v1.8.pdf 853 application/pdf

eSocial-Delivery_Report-June_2015-ver2015Aug13-CUSTOMER.xlsx 154 application/vnd.openxmlformats-officedocument

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2017 SAP SE or an SAP affiliate company. All rights reserved