RICEF Functional DesignIT0008 Changes Without an Action

ZHR_IT08_Changes

Version 1.2October 26, 2011

Contents

1 Overview and Scope............................................................................................................................... 51.1 Functional Description.............................................................................................................................51.2 Dependencies/Constraints.......................................................................................................................51.3 Assumptions............................................................................................................................................51.4 Transaction Volume................................................................................................................................51.5 Processing Type.......................................................................................................................................51.6 Authorizations.........................................................................................................................................51.7 From System............................................................................................................................................51.8 To System................................................................................................................................................5

2 Detailed Functional Requirements.......................................................................................................... 62.1 Functional Specification...........................................................................................................................62.2 Initial Selection Criteria Detail.................................................................................................................7

2.2.1 Required Selection Parameters:.....................................................................................................72.2.2 Optional Selection Parameter:........................................................................................................7

2.3 Report Output.........................................................................................................................................82.3.1 Report Output Fields......................................................................................................................82.3.2 Report Output Body Format...........................................................................................................82.3.3 Report Header Fields......................................................................................................................8

3 Technical Requirements.......................................................................................................................... 83.1 Usage Frequency (Query Execution Frequency).......................................................................................83.2 Transaction Volume Detail......................................................................................................................8

4 Testing Requirements............................................................................................................................. 94.1 Key Business Test Conditions...................................................................................................................94.2 Technical Test Conditions........................................................................................................................94.3 Risk and Controls Test Conditions............................................................................................................94.4 Testing Considerations/Dependencies.....................................................................................................9

1 Overview and Scope

1.1 Functional Description

The “Changes to IT008 Without an Action” Report (“the Report”) is designed to determine any/all instance(s) where a change to HR Master Record Infotype 0008 (Basic Pay) was entered via the Maintain HR Master Data transaction [PA30] without an appropriate Workflow. This report satisfies a key condition set by Internal Audit.

The Report logic will take into account selection parameters entered by User that consist of a date or date range (mandatory).

1.2 Dependencies/Constraints

NA

1.3 Assumptions

Applicable authorizations/role assignment present for Report User.Changes by WF-BATCH or ZCBATCH are ignored as assumed WF/automated programs.

1.4 Transaction Volume

Volume dependent upon date parameters entered by Report User.

1.5 Processing Type

This Report is available to run ad-hoc via transaction code ZHR_IT08_Changes.

1.6 Authorizations

OM/PA Audit role assignment Appropriate structural authorization

1.7 From System

SAP HCM Production

1.8 To System

SAP HCM Production

1.9

2 Detailed Functional Requirements

2.1 Functional Specification

1. Extract all changes to Basic Pay [0008] within date parameters specified by user at initial selection screen. Date criteria is based upon “Changed On” date [AEDTM] of infotype 0008.

The Report will, by default, exclude all entries where “Changed by” field [UNAME] is “WF-BATCH” , “ZCBATCH”.

2. Extract all roles that has access to PA30, using transaction code AGR_TCodes.

Table AGR_TCODES, “PA30” in Extended Name field [TCODE].

3. Use each UserID for each record with the changed on date from Step 1, and test each userID for authorization to the list of roles in Step 2. If the UsersIds has authorization to one or more roles valid on the changed on date on the record from PA0008 data, the record will be included on the subsequent steps.

If the UsersIds has authorization zero roles valid on the changed on date on the record from PA0008 data, the record will be removed on the subsequent steps.

4. The Report then tests each record remaining for valid workflow. We will exclude records that have a corresponding entry in the ZPROC_SCEN_STEP table. To qualify as a “corresponding entry”, the ZPROC_SCEN_STEP record must have

o Process [Process] = Default list (See list below)o Process Status [Process_status] = “Completed”o Object Key [Object_Key] = [PA0008 ].[PERNR]o Start Date [BEGDA] in the WF process form = [PA0008 ].[BEGDA]o End Date [Completion_Date] = Changed on Date from PA0008

Default List of Processes:1. Z_CIPAY (Change in Pay)2. Z_ILP (In Line Promotion)3. Z_SEV (Severance)4. Z_WSR (WSR)5. Z_Job_COR (Job Correction)

All records without corresponding workflow with the above criteria continues to subsequent steps.

5. The next step would be to evaluate each outputted records by using the program code RPUAUD00 (or a method which replicates it).

Use only the Pernr, Changed on and Changed by information from the report and enter them in the program RPUAUD00 (transaction code - S_AHR_61016380) as shown below:

A. Long Term Documents must be checked (Static)B. Personnel Number to be entered – one pernr at a time (variable)C. Infotype should be 0008 (Static)D. Changed On to be entered (variable)E. Changed by to be entered (variable)

After entering all the information mentioned above the program should then evaluate the result for following information:

a. If there is no Infotype logging data retrieved with the Changed On Date, PERNR and userID (Changed by) include the record on the ALV report.

b. If the Annual Salary value(s) in the Old Field(s) are all equal to New Field(s) for Annual Salary then the record should be excluded from the report.

If logging records are split for an employee, such as one old record and two new records, or two old records and one new record, then each value of annual salary must be the same dollar value in all records. If they are all the same value remove the record from the report, else show the record on the report.

Without Split

Record is displayed because 40,000.00 Does Not Equal 35,000.00

With Split

On 08/22/2011 – 12/31/9999 the Annual Salary was (Old Field) $34,999.90On 08/22/2011 – 10/01/2011 the Annual Salary was (New Field) $ 34,999.90On 10/02/2011 – 12/31/9999 the Annual Salary is (New Field) $ 22,000.00 – This is not equal to the one original or the other new record, display record on report.

2.2 Initial Selection Criteria Detail

2.2.1 Required Selection Parameters:

Date or Date Range Date or Date Range

Date criteria shall be based upon the ‘Changed on’ date [AEDTM] of infotype 0008. Company Code Org Key

2.3 Report Output

For records remaining after filtering logic has been applied, the following fields will display:

2.3.1 Report Output Fields

Infotype Table Field Display NameTechnical

Field Name

Data Type Conditions (refer to section 2.1) and Relationships

IT0008 PA0008 Personnel Number PERNR NUMC Record does not meet any condition detailed in section 2.1.

IT0001 PA0001 Employee Name ENAME CHAR IT0008 PERNR = IT0001 PERNR

IT0001 PA0001 Organizational Key VDSK1 CHAR IT0008 PERNR = IT0001 PERNR

T527O Org Key Description TEXT2 CHAR PA0001: VDSK1 = T527O: ORGKY

IT0001 PA0001 Cost Center KOSTL CHAR

IT0008 PA0008 Start Date BEGDA DATS Record does not meet any condition detailed in section 2.1.

IT0008 PA0008 End Date ENDDA DATS

IT0008 PA0008 Changed on Date AEDTM DATS Record does not meet any condition detailed in section 2.1.

IT0008 PA0008 Changed by UNAME CHAR Record does not meet any condition detailed in section 2.1.

IT0001 PA0001 Changed by Name ENAME CHAR

Determine where

[IT0008 : Field UNAME] = [IT0105 : Type = 0001 : Field USRID]

Then, IT0105 PERNR = IT0001 PERNR

Display [IT0001 - ENAME]

2.3.2 Report Output Body Format

Personnel Number

Employee Name

Organizational Key Org Key Description Cost Center Start Date End Date Changed on

Changed by

Changed by Name

12345678 Doe, John E CPHQ000000000 Cable Headquarters 987654321 9/5/2010 12/31/9999

11/1/2010 BAUTRY200

Autry, Brad

12345678 Doe, John E CPHQ000000000 Cable Headquarters 987654321 9/19/2010 12/31/9999

10/31/2010

BAUTRY200

Autry, Brad

12345678 Doe, John E CPHQ000000000 Cable Headquarters 987654321 9/19/2010 12/31/9999

10/31/2010

BAUTRY200

Autry, Brad

2.3.3 Report Header Fields

Report Title (Comcast HR - Basic Pay Changes Audit) Date or Date Range entered in selection Criteria Count of rows in output

3 Technical Requirements

3.1 Usage Frequency (Query Execution Frequency)

This report will be run on an ad-hoc basis. The expected frequency for report run is monthly.

3.2 Transaction Volume Detail

The Report output volume may remain (relatively) small, process runtime may be significant as larger timeframes are examined and, hence, volume of records analysed increases.

4 Testing Requirements4.1 Key Business Test Conditions

ID Condition Expected results Cycle Ref.

1 Perform a change in pay workflow. Confirm change do not display on report. 2 Perform a PA40 change in pay. Confirm the report shows the change. 3 Perform a PA30 changing Reason Code (or any other non dollar

amount field). Save.Confirm that record is not captured, step 5 check for Infotype logging should flag amounts old and new were the same and remove record.

4.2 Technical Test Conditions

Document all technical scenarios associated with this development. Examples would include testing an error-free run, testing the exception processes, and testing the error handling.

ID Condition Expected results Cycle Ref.

4.3 Risk and Controls Test Conditions

Document all control scenarios associated with this development. Examples would include rounding of dollars and cents, audit trail processing, and reconciliation Reporting.

ID Condition Expected results Cycle Ref.

4.4 Testing Considerations/Dependencies

N/A.