The generation of Social Insurance affiliation messages is performed using the Affiliation message through the RED system of the Social Insurance Administration (TGSS). (RPCAFIE1). Using this program, you can communicate registrations, de-registrations and changes in the details of workers directly in the Social Insurance affiliation data file.

In the payroll Implementation Guide, the activities related to setting of data exchange through the RED system must have been performed, under Evaluations for Social Insurance ® RED system:

Program RPCAFIE1 creates a file for sending information to Social Insurance with the object of maintaining company employee data in the affiliation data file. Using this program, you can communicate registrations, de-registrations and changes in the employee data. The notifications of changes of data supported by the program include all the actions at employee level: change of contribution group, change of contract and change of epigraph for industrial accident (IA) and industrial disease (ID). Meanwhile the possibility is included of modifying or eliminating previous movements.

You create the file in accordance with the specifications published by the Social Insurance Administration for the exchange of documents through the RED system (Electronic Document Readmission), which is based on Electronic Data Interchange technology (EDI).

You can display the data and store it in the data carrier with the help from the display program of sequential (TemSe) files (RPUTMSE0). Likewise, it is possible to choose the display of individual data medium exchange (DME) records. You can perform this display with both MS-Word and MS-Excel.

The affiliation message is structured in such a manner that it allows inclusion of only one EDI message from:

• Employee grouping by company and action

• Sending of documentation on successive entries, departures and modifications of different employee data

• Multi-category, multi-company, multi-contribution account code (CAC)

The segments constituting the AFI message are:

• EMP: Company identification

• RZS: Registered company name

• EXC: Exploitation and key (1)

• TRA: Employee

• AYN: Name and surnames

• DOM: Address (1)

• LDD: Address locality decoded (1)

• FAB: Entry and leaving dates
• DAM: Data associated with the movement

Note: (1) Not created by the program, since this is optional for TGSS.

The program creates the enrollment message from actions carried out in the system at employee level. Generally only those actions and reasons associated with one or several actions with their reasons according to the RED System through the table Adapt Actions and Reasons for Social Insurance (T5E30) are considered. Before being able to run the program successfully it is therefore essential to set the corresponding basic data as shown above.

One exception is the change of epigraph actions (MT), change of contract category (MC) and change of contribution group (MG). These actions are automatically reported, so it is not necessary to carry out any allocation of them in the table T5E30.

To report these changes at employee level, the program consults the infotype Personnel Actions (0000). For each segment of this infotype, it looks in the infotype Social Insurance (0061) to see if there has been any change (change of epigraph, change of contract category, change of contribution group) and if so, it automatically reports them in the FAB segment. Additionally, for each segment of infotype 0000, the program also looks in infotype 0061 for a change of contribution account code and, if there is one, reports it, generating two EMP segments with a general leaving action in the previous CAC and an entry action in the new CAC.

The data exchange file generated in the user work directory in the R/3 server takes as name:

MMM.RRRRRRRR.V01

being:

MMM, the logon client, and

RRRRRRRR, the name of the program being run

You can access the program through the system menu, under System ® Services ® Reporting.

Enter the name of the program RPCAFIE1 and then press the activation key.

In the selection screen of the program, enter the corresponding data in accordance with the information shown below and then run the program.

Action and Situation fields: the keys entered in these fields will tell the system the transaction and employee-level reason to be carried out.

If you do not enter the action or reason, all the transactions/reasons that have occurred in the period are selected for the selected persons.

The keys allowed by the program are:

The selection screen also offers the following groups of fields:

Identify Message Syntax: This identifies the category of the following message.

Release Message Syntax: Release of previous message.

Identif. process syntax: Identifies the version of the validation program, printout and process that the previous issuer has used in the exchange.

Version process syntax: Version of previous validation module.

Authorization key: Key provided by the TGSS when it receives administrative authorization to present the nominal employee list. One per company, employer group or authorized professional.

SILCON key. SILNET network: Key provided by Social Insurance Administration (TGSS). This identifies each physical person that interacts with the system.

New Silcon key: Since the SILCON key has a limited time duration, a new access key is requested, that is entered as new if the existing key has expired or you want to change it. (Future use).

Presentation date: The year, month and day of sending the message.

Presentation time: In hours and minutes.

External name AFI file: This records the MS-DOS plan file name with AFI suffix that has been prepared for the exchange.

Test indicator: This indicates the category of message sent:

• Blank: Normal

• S: Substitute
• P: Test

CENDAR reference: TGSS reference. For internal use by the TGSS.

Change Contract Keys: This field is related to the use of contract keys.

Personal Key AFI File: Operator’s personal key.

Printout indicator: This indicates whether the user wants a printed response to the request, or not.

With the object of notifying of a previous movement, you must ensure that personnel action and reason correspond to two actions according to the RED System. The first action is to delete the movement to be modified (ME) and the second, notification of entry, leaving or change in employee data.