Purpose
This report is used for conversions from the old savings scheme out ofInfotype External Payments (0011) to Infotype SavingsSchemes (0854), subtype Employee Savings Scheme (0002).
The contents of the following fields from Infotype External Payments (0011) is converted to the adjacently-named fields from InfotypeSavings Schemes (0854). The technical names are also givenbetween parentheses:
Payee Code for Bank Transfer(EMFSL) ,,-->,,Payee Code for Bank Transfer(EMFSS)
Recipient Description (EMFTX),,,,--> ,,Recipient Description (EMFTS)
Postal Code (BKPLZ) ,,,,,,-->,,Postal Code (BKPLS)
City (BKORT) ,,,,,,,,-->,,City (BKORS)
Bank's Country Code BANKS,,,,-->,,Bank's Country Code (BASKS)
Bank-key (BANKL),,,,,,,,-->,,Bank-key (BASKL)
Bank Account Number (BANKN),,,,-->,,Bank Account Number (BASKN)
Payment Method (ZLSCH),,,,,,-->,,Payment Method (ZLSCS)
Description of Transfers (ZWECK),,-->,,Description of Transfers (ZWECK)

Selection

• The conversion starts as of the conversion date on the selection screen.
This date may not be before 01-01-2006.

• Both current and future records will be converted.


• It is possible to execute the report in background mode.


• Conversion only takes place if there is no infotype Savings Schemes

(0854) for the employee in the time period of the record to becreated. Otherwise an error message will appear.

• The old infotype External Payments (0011) will always be
delimited if data conversion is possible. For employees for whom this isnot possible, the old infotype External Payments(0011) can bedelimited if the user clicks on the relevant check box. In this case awarning will appear. Future records of infotype External Payments(0011) will be removed after the same fashion.

Output
The conversion of data is done using a Batch Input Map.
The report creates a log of which action has taken place (delimited,deleted, skipped and why) per record of Infotype External Payments(0011). Which new records will be created in Infotype SavingsSchemes (0854)is also displayed simultaneously.
There are two selection fields for the selection of wage types:
,,a. The first field contains wage types for saving from table wage.Thesavings amount of this wage type ,,will be converted to fieldSavings Amount (P0854 - BETRS). The first savings period(ZFPER) will ,,be converted to field First Savings Period(P0854-ZFPER) and the interval Amount for determining multiple datesof payment (ZANZL) will be converted to Amount for determiningmultiple ,,dates of payment (P0854-ZANZL)
,,b.The second field contains wage types for saving out of specialpayments.The savings amount of this wage type will be converted to thefield Savings Amount SP(P0854-BETRS). The First SavingsPeriod ,,(ZFPER) will be converted to field First Savings PeriodSP (P0854-ESPBB)and the interval Amount for determining multipledates of payment (ZANZL) will be converted to Interval BetweenSavings Periods for Special Payment(P0854-INTBB)
It is possible that different records of one employee from infotypeExternal Payments (0011) are both/all valid at one particulardate. It is possible that these records can be converted without anyproblems. An example of this situation is the saving of a monthlysavings amount of EUR 25,- from the normal wages and saving EUR 313,- inMay at the expense of the special payment.
If it is not possible to convert these records, an error message willappear on the screen. Examples of these situations are:
a. Different savings accounts for different savings schemes.
b. Different start dates or intervals for savings schemes with similarpayment methods.
c. The First payment date (P0011-ZDATE) and/or Time unit fordetermining next payment (P0011-ZEINZ) have been filled. There are nosimilar fields in infotype Savings Schemes (0854).
d.The Payee Code for Bank Transfer (value P0011 - EMFSL) isunknown in infotype in infotype Savings Schemes (0854). This isdue to a missing customizing in table Wage types to be distributed(T512C).

Activities
1. Fill the fields on the selection screen.
2. Execute the report.
3. The report will generate Batch Input Sessions.
The first session contains the transactions for infotype SavingsSchemes (0854). The second contains those for delimiting/deletinginfotype External Payments (0011). The sessions can be identifiedwith the name that we have given in the relevant field on the selectionscreen.
Check the output of the log. If all conversions have taken place in apleasing manner, you can process this in the system by running the BISvia transaction SM35. In the individual overview "Data conversion ofinfotype External Payments (0011) infotype Savings Schemes (0854)" thefollowing data illustrating the old and the new situation aredisplayed.
Old situation
- Blue: position in old situation, the employee's data are here as wellas the wage types to be converted.
- Pink: processing method. This is the way in which the old records areprocessed. Processing method A Delimits the record, V Deletes the recordand if it is empty, neither delimiting nor deletion occurs.
- Orange: contains the first payment date and the following paymentdate. There are no similar fields in infotype Savings Schemes(0854) and this is why they are not converted. The last user is alsodisplayed.
New situation
-Green: shows the position of the new situation: the validity intervalof the converted records, the savings amounts, the first payment period,the status of the BIS data (job icon for a created BIS or red cross forerror), counter of the number of records that are included in the BIS.
-Pink: displays the payee key as well as various details about the bankinstitution.
Statistics are displayed in the log. If you click on the button to thefar left in the individual overview (show application log), atstatistics, you can find information about summary data: total of sele
cted persons, total selected, processed, and rejected records. The totalnumber of converted and delimited records is stated in relation to theBIS.