Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Capturing Batch Input Log without keeping BDC session

Former Member
0 Likes
605

Hi all -

Would like to capture the Batch Input log and keep it persistent in some manner (for example using an application log) without keeping the corresponding BDC session. The reason for this is that any manual corrections to data interfaces through BDC sessions MUST be logged indefinitely for audit purposes. The actual BDC sessions are HUGE and therefore precludes saving the entire BDC session. My thoughts are user-exit'ing in BDC session either as a Batch Input Log is being created or when a Session is being deleted (NOTE: running ECC 6.0 which has new enhancement concept permitting extremely flexible user-exit'ing so exit points are NOT an issue and repair/core mode not required). Anyone see any flaws with this approach or can recommend perhaps a simpler or standard approach so that Batch Input Logs are retained indefinitely whereas the Session is deleted?

Many thanks,

Pat

3 REPLIES 3
Read only

Former Member
0 Likes
489

HI,

the log will remain if you delete the session. so do not think that if you delete the session the log wil also deleted. just have a try in test system. even the spool request will be genereted, you can pick the data from the SPOOL number also

Regards

Sudheer

Read only

Former Member
0 Likes
489

Thanks Sudheer. The issue is that ultimately the batch input log will be deleted via the program RSBDCRE0 (if not manually). The requirement is to archive the batch input log in some (if not all) cases. Especially the case where a user has manually modified data in the BDC session (as this is recorded on the log and therefore is crucial for audit purposes). My (naive) approach to this would be to write the contents of the batch input log to an application log for persistence. Exclusive of this approach, I am asking if someone can identify a delivered approach or perhaps a simpler solution.

Thanks,

Pat

Read only

Former Member
0 Likes
489

Hi Pat,

Why dont you try archiving?

For archiving, archive object BDCLOGPROD can be used. if archived, then you can read the archived logs using program RSBDC_ARCHREAD (also accessible from SARA->Read).

See some notes if it is helpful:

147354, 18319, 24438, 18307

Also have a look at the Data Management Guide available at service.sap.com/data-archiving.

Hope this helps,

Naveen