1
Purpose of This Document
This document outlines the technical integration approach for the proposed P2P Payment Automation solution.
We request your technical team to validate the following:
- SAP connectivity and access requirements
- Network and security prerequisites
- Available integration methods (RFC/BAPI vs OData)
- Required authorizations and user access
Note: This is a technical validation document only. Full solution details will be shared after technical feasibility is confirmed.
2
Integration Overview
The solution will integrate with your SAP ERP system to automate the P2P payment validation workflow. Here's the high-level data flow:
Document Sources
Invoices, GRN, Weighment
→
Automation Platform
OCR + Validation Engine
→
SAP ERP
MIRO / MIR7 Posting
What We Will Do:
Read from SAP
- Purchase Order details (ME23N)
- Goods Receipt data (MIGO)
- Vendor master data
- Material master information
- Custom Z-table for FG Sales
Write to SAP
- Invoice verification posting (MIRO)
- Parked invoice documents (MIR7)
- Document attachments (GOS)
3
SAP Connectivity Approach
We can integrate with your SAP system using either of the following methods. Please confirm which is available/preferred:
RFC/BAPI Integration
- Direct connection via SAP RFC SDK
- Uses standard BAPIs for transactions
- Requires RFC user with specific authorizations
- Port: 33XX (where XX = instance number)
- Supports both read and write operations
OData Services
- REST-based API integration
- Requires SAP Gateway activation
- HTTPS-based communication
- May require custom OData service development
- Modern approach for cloud deployments
Required SAP Transactions/BAPIs
| Function |
BAPI/Transaction |
Purpose |
Access Type |
| Purchase Order |
BAPI_PO_GETDETAIL |
Read PO header and line items |
Read |
| Goods Receipt |
BAPI_GOODSMVT_GETDETAIL |
Read GRN/MIGO data |
Read |
| Invoice Verification |
BAPI_INCOMINGINVOICE_CREATE |
Create MIRO document |
Write |
| Invoice Parking |
BAPI_INCOMINGINVOICE_PARK |
Park invoice (MIR7) |
Write |
| Vendor Master |
BAPI_VENDOR_GETDETAIL |
Vendor information lookup |
Read |
| Material Master |
BAPI_MATERIAL_GET_DETAIL |
Material code validation |
Read |
| Custom Table |
RFC_READ_TABLE |
Read custom Z-table data |
Read |
| Document Services |
ARCHIV_* / GOS APIs |
Attach supporting documents |
Write |
4
Network & Security Requirements
Network Connectivity
- Secure connection to SAP server
- VPN or direct connectivity options
- Firewall rules for RFC/HTTPS ports
- SSL/TLS encryption for data in transit
SAP User Requirements
- RFC communication user (Type: System/Service)
- Specific authorization objects for BAPIs
- Company code level restrictions
- Audit logging enabled
Environment Access Needed
We will need access to the following environments during implementation:
- Development (NSY) - Initial integration development and testing
- Quality (NSQ) - UAT and validation testing
- Production (NSP) - Final deployment (post UAT approval)
5
Technical Validation Questions
Please review and provide answers to the following questions to help us finalize the integration approach:
⚠ SAP Connectivity
-
1
Which integration method is available/preferred?
RFC/BAPI, OData Services, or both?
Response:
-
2
Is SAP Gateway activated for OData services?
If yes, are there existing OData services for MM/FI modules?
Response:
-
3
Can we get RFC connectivity to Development environment?
Server details, instance number, and client for initial testing
Response:
⚠ Authorization & Access
-
4
Can a dedicated RFC user be created for integration?
System/Service user type with required BAPI authorizations
Response:
-
5
Are the listed BAPIs available in your SAP system?
Any custom alternatives or restrictions?
Response:
-
6
Is RFC_READ_TABLE allowed for custom Z-tables?
Or is there an alternative method to read custom tables?
Response:
⚠ Network & Security
-
7
What is the preferred connectivity method?
Site-to-site VPN, Point-to-site VPN, or direct connection?
Response:
-
8
Are there IP whitelisting requirements?
If yes, we will provide our static IPs for whitelisting
Response:
-
9
Is SNC (Secure Network Communications) required?
For encrypted RFC connections
Response:
⚠ Custom Development
-
10
What is the structure of your custom FG Sales Z-table?
Field names and data types for integration mapping
Response:
-
11
Are there any custom BAPIs/Function Modules we should use?
Instead of standard BAPIs for your specific processes
Response:
-
12
How are documents currently attached in SAP?
GOS, DMS, or custom attachment handling?
Response:
6
Pre-Implementation Checklist
Please confirm availability of the following before we proceed:
-
Development environment access (NSY) for integration testing
-
RFC/Service user credentials for development
-
Network connectivity path confirmed (VPN/Direct)
-
Required BAPIs are available and accessible
-
Custom Z-table structure documentation
-
Technical point of contact for integration queries
-
Sample test data (PO, GRN, Invoice) for development
✉
Next Steps
Once the above questions are addressed and prerequisites confirmed, we will:
- Schedule a technical deep-dive call with your SAP/IT team
- Set up connectivity to development environment
- Begin integration development and provide progress updates
Please share this document with your SAP Basis and Security team for review.