7/30/2019 zhhgg

http://slidepdf.com/reader/full/zhhgg 1/7

Management of Automatically Executing BDC Sessions 

Applies to: SAP HR, ABAP 4.6C, 4.7 Enterprise, mySAP ERP.

Title

Managing automatically executing BDC sessions.

Target Audience SAP ASM analysts, ABAP application developers, SAP HR functional consultants.

Overview 

Executing an ASM project in SAP HR and facing the problem of master-data feeds (via BDC sessions) getting rejected when payroll

is running?

Repeatedly getting a larger number of tickets in the production support queue saying - 'BDC session XXXX did not execute last nightwhen the payroll for salaried population was running. The session is lying in error in SM35. Pls. resubmit the session to create health plan records for all employees'?

This paper addresses the above issues which a production support team faces and provides an automated solution and associated

 process to solve them.

Pain Points 

7/30/2019 zhhgg

http://slidepdf.com/reader/full/zhhgg 2/7

  Considerable amount of man-month effort blocked for solving these issues.

  Master data not updated on time and failure remains un-noticed.

Problems   Manual mechanism for timely identification of these failures in SM35.

  Manual mechanism to inform and repeated follow-up with the payroll operations team about the failure of each session.

  Manual mechanism to re-submit failed BDC session. Chance of technical and human error while operations team re-submitsthe session in SM35.

  Authorization issues. Who and how many operations team members should have the authorization for SM35.

Process Steps 

  A naming convention has to be formed for giving names to the BDC sessions. For example, all sessions which update Benefits

data will start with 'BE*'.

  Before going live on the technical solution following data is to be maintained in the SAP system. For each session-- An operations team member need to be identified for each session, example 'BE_HEALTH' or 'BE*'. He will be

responsible for this/these session(s).- Email Id. Of the operations team member to be maintained with the session name. He/She will get an automatically

generated e-mail reporting the failure.- Operations team member will specify in advance whether a particular session should be re-submitted at least once before sending the failure e-mail. This data needs to be maintained.

- An ABAP program will pick failed sessions from the SAP system tables and will either re-submit or send an auto-emailto the concerned operations team member.

Technical Solution 

7/30/2019 zhhgg

http://slidepdf.com/reader/full/zhhgg 3/7

7/30/2019 zhhgg

http://slidepdf.com/reader/full/zhhgg 4/7

7/30/2019 zhhgg

http://slidepdf.com/reader/full/zhhgg 5/7

Selection Screen 

Report Output- Error Mail 

7/30/2019 zhhgg

http://slidepdf.com/reader/full/zhhgg 6/7

Report Output- Re-Submit Session 

Table Design HR Constant table 

7/30/2019 zhhgg

http://slidepdf.com/reader/full/zhhgg 7/7

Summary 

The presented solution automates a cumbersome and a non-value adding process. It also eliminates the requirement of providing

SM35 authorizations to the end users and de-risks the chance of any technical and human error committed by end users in attempt of rerunning the failed sessions. It enables the Master Data updating to happen at first earliest available chance and hence strengthens all

subsequent processes.