Hierarchy
⤷ PY-US-PS (Application Component) Öffentlicher Dienst
⤷ P10P1 (Package) HR Public Sector USA
IMG Activity
ID | OHPSUSCERT21 | Define Renewal Codes and Assign Messages to Renewal Codes |
Transaction Code | S_ELN_90000011 | (empty) |
Created on | 20040312 | |
Customizing Attributes | OHPSUSCERT21 | Define Renewal Codes and Assign Messages to Renewal Codes |
Customizing Activity | OHPSUSCERT21 | Define Renewal Codes and Assign Messages to Renewal Codes |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHPSUSCERT21 |
Use
In this step, you perform two distinct actions:
- By making entries in the RenewCode column, you define the renewal codes that are used (in certain jurisdictions) to provide complete instructions for the renewal options that employees can pursue to remain certified or licensed
- By making entries in the Message Number column, you assign the message numbers whose contents you maintained in the previous IMG step to the renewal codes that you define in this IMG step.
Requirements
You have defined a single message class to be used for certification and licensing renewal codes, and thereby activated the use of renewal codes in the Certification and Licensing infotype (0795).
You have maintained the contents of all relevant message numbers in the previous IMG step.
Standard settings
No default renewal codes have been defined in the standard system.
The definition of renewal codes in this step - and the assignment of message numbers to those codes - is, however, optional. If your workplace does not intend to use renewal codes or to assign messages to them, then omit this step entirely.
Activities
- Execute this IMG step.
- On the subsequent screen, in the RenewCode column, enter the one- to four-character identifier that corresponds to each renewal code to be created.
- For each renewal code created, enter the three-digit message number in the adjacent column that you wish to assign to that code.
- Save your entries, then exit this step.
Example
Suppose you defined message class ZRENEWCODE as the customer message class whose messages will be used to describe the renewal codes in your system. Also, suppose you wish to create three renewal codes for use in the Certification and Licensing infotype (0795), namely:
- This is the holder's initial emergency permit. - which you assigned to message number 000 in the previous step,
- There are no additional requirements for the renewal of this credential. - which you assigned to message number 001 in the previous step, and
- This certificate need not be renewed. - which you assigned to message number 002 in the previous step.
To create the three renewal codes that will appear in the Certification and Licensing infotype (0795), you would execute this step and make the following entries:
- RenewCode - Message Number
P181 - 000
R15 - 001
S31B - 002
Upon completing this configuration, renewal code P181 would appear on the Certification and Licensing infotype (0795) to indicate the first message, while renewal codes R15 and S31B would appear to indicate the second and third messages, respectively.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
OHPSUSCERT21 | US | USA |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHPSUSCERT21 | 0 | I511000001 | Öffentlicher Dienst |
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 |
T5UPBSTC21 | S - Table (with text table) | SM30 | PSUS 10 | Mapping Renewal Codes to Messages |
History
Last changed by/on | SAP | 20050218 |
SAP Release Created in | 600 |