Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PY-XX (Application Component) Payroll: General Parts⤷
PCAC (Package) Customizing HR Payroll
IMG Activity
| ID | OHAXFO008 | Change Addresses Infotype (0006) |
| Transaction Code | S_AHR_61010549 | IMG Activity: OHAXFO008 |
| Created on | 19981221 | |
| Customizing Attributes | OHAXFO008 | Change Addresses Infotype (0006) |
| Customizing Activity | OHAXFO008 | Change Addresses Infotype (0006) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAXFO008 |
In this step, for each report class, you can change the sequence in which the subtypes of the Adresses infotype (0006) is read when fomatting addresses.
You only need to carry out this step, if you do not wish to use the Permanent Address subtype (1), which has been set up in the standard, as the basis for your address formatting.
The feature ADDRS determines the subtype and sequence of subtypes for address formatting. There is a standard entry for this feature with the decision criterion "Report class". This entry specifies that the address is printed on the basis of the subtype Permanent residence (1).
If you specify a sequence of subtypes, in each case the subtype that is in the highest position, and that has relevant employee data, is used for address formatting.
Note that in addition to the decision operation "Report class", you can also configure decisions using all other decision operations belonging to the feature structure. For example, you can use the field VARKY to control address formatting for individual forms.
Example
You want address formatting to be carried out for the remuneration statement using the subtype Postal address (5). To achieve this you must make the following entries:
D RCLAS
**** &ADDRS=1,
CEDT &ADDRS=5/1,
If there are no data records in this subtype for the employee, the system uses the Permanent Address subtype (1).
Activities
In the feature ADDRS, change the sequence in which the Addresses subtype (0006) is to be read during address formatting.
Further notes
When changing the feauture, you should include the Permanent Address subtype (1) as the last entry at least. In this way you avoid printing a form without an address, if there are no data records available for subtypes with a high priority.
If you want to specify address formatting for a particular form, you must configure a decision using field VARKY. You store the name of the form in this field. For each entry that you make in this field, you must specify the report class and the form name.
Example:
In your enterprise, you use two different forms for the remuneration statement (ZF01 and ZF02). For form ZF01, you want to use the Postal Address subtype (5) instead of the Permanent Address subtype (1). In this case, you must enter the following:
D RCLAS
**** &ADDRS=1,
CEDT D VARKY(4)
CEDT ZF01 &ADDRS=5/1,
CEDT **** &ADDRS=1,
The entry VARKY instructs the system to differentiate between forms.
In the second to last entry, you specify that the Postal Address subtype (5) should be used for the form ZF01. If there is no data record for an employee in this subtype, the Permanent Address subtype (1) is used.
In the last entry, you specify that for all further forms in report class CEDT the Permanent Address subtype (1) should be used.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | E | Invalid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHAXFO008 | AR | Argentina |
| OHAXFO008 | AT | Austria |
| OHAXFO008 | AU | Australia |
| OHAXFO008 | BE | Belgium |
| OHAXFO008 | BR | Brazil |
| OHAXFO008 | CA | Canada |
| OHAXFO008 | CH | Switzerland |
| OHAXFO008 | CN | China |
| OHAXFO008 | DE | Germany |
| OHAXFO008 | DK | Denmark |
| OHAXFO008 | ES | Spain |
| OHAXFO008 | FI | Finland |
| OHAXFO008 | FR | France |
| OHAXFO008 | GB | United Kingdom |
| OHAXFO008 | HK | Hong Kong |
| OHAXFO008 | ID | Indonesia |
| OHAXFO008 | IE | Ireland |
| OHAXFO008 | IN | India |
| OHAXFO008 | IT | Italy |
| OHAXFO008 | JP | Japan |
| OHAXFO008 | KR | South Korea |
| OHAXFO008 | MX | Mexico |
| OHAXFO008 | MY | Malaysia |
| OHAXFO008 | NL | Netherlands |
| OHAXFO008 | NO | Norway |
| OHAXFO008 | NZ | New Zealand |
| OHAXFO008 | PH | Philippines |
| OHAXFO008 | PT | Portugal |
| OHAXFO008 | SE | Sweden |
| OHAXFO008 | SG | Singapore |
| OHAXFO008 | TH | Thailand |
| OHAXFO008 | TW | Taiwan |
| OHAXFO008 | US | USA |
| OHAXFO008 | VE | Venezuela |
| OHAXFO008 | ZA | South Africa |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAXFO008 | 0 | HLA0100669 | Forms |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| PMKC | L - Logical transport object | PE00 | ADDRS 10 |
History
| Last changed by/on | SAP | 19990413 |
| SAP Release Created in |
