Protect the Integrity of Your PD Data by Managing Time Constraints

  • by A.J. Whalen, SAP Marketing Director, Velocity Technology Solutions
  • January 15, 2005
You can control how your Personnel Development (PD) objects and structures react and relate to one another over time by properly using time constraints.
Key Concept

Personnel Development (PD) data in SAP consists of complex groupings of related objects and data structures. The relationships between PD objects carry specific meanings and are configured to exist only between allowed objects and for predetermined time frames. For example, while PD configuration controls the object types to which you can assign a cost center object, the same configuration also controls when and how often you can use those relationships. Data elements called time constraints control the “when” and “how often” aspects of PD relationships.

Imagine that your SAP security team has presented you with the following issue. Your Manager Self-Service (MSS) application security is driven by the A012/B012 “chief” relationship between a position and an organizational unit. A position in your organizational structure may be chief for one or many units, but, according to your company security policy, each unit should have only one chief.

It has come to the attention of the security team that in some situations in R/3, units have more than one chief at the same time, putting your MSS security at risk. Your task is to change your Per-sonnel Development (PD) configuration to allow only one chief per unit at any time. You also must audit your existing PD objects and relationships to identify and correct any instances of multiple concurrent chiefs per unit.

To resolve the issue of unwanted concurrent chief relationships, you must first address the configuration in PD that controls the allowed relationships between objects, particularly time constraints. PD relationships define the interaction between objects. Time constraints are configurable data elements that allow you to maintain the integrity of those relationships by controlling whether or not they can overlap or exist simultaneously for the same objects. Time constraints are configured to exist based on particular infotype or object relationship combinations. They are not attributes on the PD objects themselves.

A.J. Whalen

A.J. Whalen has successfully combined more than two decades of global business expertise with in-depth experience in the strategic development, management, and delivery of large-scale projects and education for SAP ERP HCM. Prior to his current role as SAP Marketing Director at Velocity Technology Solutions, he served as lead consultant for several global SAP implementations and engagements as well as an SAP Conference Producer for Wellesley Information Services. A.J. has been invited to speak at nine annual SAP educational events and holds an MBA degree from the Stern School of Business at New York University.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.