Professional Documents
Culture Documents
5 - Part 2 - AP457 Technical Design Interface Architecture
5 - Part 2 - AP457 Technical Design Interface Architecture
Interface Logging
Architecture
Tyson Crosby
tyson.crosby@accenture.com
Canada Delivery Centre
1
SAP Development Community of Experts
Overview
Business Benefits
Architecture Explained
Architecture Flow
Demo of Architecture
Questions
2
SAP Development Community of Experts
Opening Questions
3
SAP Development Community of Experts
Business Benefits
4
SAP Development Community of Experts
Architecture Explained
Four Custom Tables
RICEF Id Check Table
Contains RICEF Ids, Sub Ids, and Descriptions
Contains Direction and Logical File Path for Log File Generation
5
SAP Development Community of Experts
Architecture Explained
Four Custom Tables
Interface Direction / Source
Contains Interface Direction, Source, and Processing Order
These Details are used by the Display Interface Logs Program
When Determining How to Sort the Messages.
6
SAP Development Community of Experts
Architecture Explained
Four Custom RFCs:
Get Interface Transaction Id
Generates Next Available Number using SAP Custom Number Ranges (T-Code OYSN)
Two Number Ranges Have Been Developed. One for Inbound and One for Outbound.
7
SAP Development Community of Experts
Architecture Explained
Two Custom Programs
Maintain Table Entries
Single Transaction Code Created to Maintain the Table Entries in the RICEF Id, Email, and
Direction / Source tables.
View Logs
Single Transaction Code Created to Allow End Users to View the Interface Logs.
Code is Setup to Purge Logs that are Over 90 Days Old.
This Program also Contains the Logic for Generating the Generic Emails and the
Generation of the Log Files. These options are Hidden from the End User So They Can Not
Manually Trigger Them.
Common Includes
A Common Top Include Has Been Created to Ease the Migration of the Code from Project to
Project.
A Common Subroutine Include Has Been Created to Help Drive Consistency in Creation of
Interface Logs
8
SAP Development Community of Experts
Architecture Flow
Inbound / Outbound Interface:
9
SAP Development Community of Experts
Architecture Flow
Inbound / Outbound Interface:
10
SAP Development Community of Experts
Architecture Flow
Inbound / Outbound Interface:
11
SAP Development Community of Experts
Architecture Flow
Inbound / Outbound Interface:
Error Handling:
If an Error Occurs In the Initiating System (Step 2 or 3), it is Responsible for Triggering
the Email and or Log File Creation (if required).
If an Error Occurs In the Middleware Tool (Step 4 or 5), it is Responsible for Triggering
the Email and or Log File Creation (if required).
12
SAP Development Community of Experts
Demo of Architecture
13
SAP Development Community of Experts
Questions
14