Ansicht
Dokumentation

Infotype enhancements ( RELNPA_PA_JP_45A_INFOTYP )

ABAP Short Reference   Addresses (Business Address Services)  
Diese Dokumentation steht unter dem Copyright der SAP AG.

Kurztext

Infotype enhancements

Beschreibung

Enhancements were performed for the following infoytpes:

• Infotype 0002 Personal Data

• Infotype 0006 Address

• Infotype 0148 Family information Japan

Additionally, the initial data entry screen of the Recruitment module, which also contains data of infotype 0006 and 00002, was enhanced.

Enhancements for Infotype 0002 Personal Data

The fields for the maintenance of the employees name were enlarged to 40 bytes for each writing style.

• The division of the name of birth and the KOSEKI name was emphasized by grouping them in frames for a better contextual understanding.

• A field showing the formatted name of the employee was added to the screen. It displays the name according to the setting the user chooses in the name format field.

• Additionally, an enhanced, system and code page dependent katakana check was implemented for the katakana name.

Enhancements for Infotype 0006 Address

• All address lines for kanji writing and katakana character

• address were enlarged to 40 bytes.

• To provide additional space for maintenance of the address in double byte katakana, a fourth katakana address line is provided from 4.5A. However, this line is hidden by default and can be displayed via corresponding setting in table T588M.

• Additionally, the documentation for all field was changed towards more consistency and better reflection of the Japanese requirements.

Enhancements for Infotype 0148 Family information Japan

Several changes were implemented in infotype 0148 Japan, as follows.

Infotype view

The following international fields present in infotype 0148 were moved to infotype 0021 Family and Related persons:

Type of family record, birth date, country of birth, nationality, gender key, state, birth place, name format indicator, child type and relationship indicator.

In order to make all necessary fields available for online maintenance, the two infotypes are joined through an infotype view. In the view, infotype 0021 is the primary infotype, and infotype 0148 is the secondary infotype. As a consequence, infotype 0148 cannot be maintained directly online anymore, and all access to its information must be done through infotype 0021.

In the same way for reporting purposes, international fields must be accessed from infotype 0021 as they will not be available in infotype 0148 in the future.

As infotype 0148 became the secondary infotype in the infotype view, all its basic characteristics are now inherited from infotype 0021.

The following changes arise due to this restriction:

• Subtype settings

Subtype 3 (Relatives) was changed to subtype 8 (Related persons) and subtype 4 (Guardian) was changed to subtype J1 (Guarantor).

• Time constraint settings

The time constraint for subtype 4 (Guardian) will be changed from 3 to 2.

• Several fields in infotype 0021 will trigger retroactive calculation.

Field enlargement

The following fields were enlarged to 40 bytes:

• the last and first name in kanji characters

• the last and first name in katakana characters

Field addition

The following fields were added:

• the last and first name in roman

• two new flags to describe the following statuses which influence tax dependency:

Death flag: to indicate if the family member in question is deceased.

Non-residence flag: to indicate if the family member in question went abroad.

Others

In 4.5A there is a new field in table T591A called OBJRQ (Object identification permitted for subtype). This field indicates for which subtypes it is possible to use field OBJPS (Object identification) to differentiate records.
For details please check the following release note:

Object identification permitted for subtype

Conversion requirements

The following conversions are necessary to effectively implement the enhancements described in this document:

1. Data currently in infotype 0148 must be transferred to infotype 0021.
2. Subtype reassignment must be performed accordingly.
3. Field VIEKN in infotype 0003 must be set to the view identifier, that is 22, in order to make the new infotype view accessible.
4. The new Deathand Non-residenceflags must be initialized from the values current stored in field Reason for change. At the same time, the field Reason for change must be cleared (initialized) after the new flags are set.

To carry out these changes, the following conversion program was created:

RPUFAMJ0 Conversion from infotype 0148 to 0021

Please refer to the report documentation for details.

Enhancements for the initial data entry screen (Recruitment)

Corresponding to the changes in infotype 0002 (Personal data) and 0006 (Addresses), the lines for the applicant's name and address were enlarged to 40 bytes. For the katakana writing of the applicant's name, the same katakana check as for infotype 2 was implemented.

ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
Diese Dokumentation steht unter dem Copyright der SAP AG.

Length: 7065 Date: 20240523 Time: 204307     sap01-206 ( 83 ms )