SAP MDG · MDG FINANCE
How do I configure SOA Manager for MDG-F local replication without PI in a hub/client setup?
Configure the web service runtime, authorizations, required business functions, inbound transport customizing, SLD connectivity, and SOAMANAGER profiles/provider systems/logon data in both MDG Hub and MDG Client. Then build the local integration scenarios and activate the relevant replication models for your finance master data objects.
Configure the web service runtime, authorizations, required business functions, inbound transport customizing, SLD connectivity, and SOAMANAGER profiles/provider systems/logon data in both MDG Hub and MDG Client. Then build the local integration scenarios and activate the relevant replication models for your finance master data objects.
Configure MDG-F local replication in two layers: first the technical prerequisites in both systems, then the SOAMANAGER setup for profiles, provider systems, and logon data. The guide also requires transport customizing for inbound financial services, SLD validation with SLDCHECK, and activation of the point-to-point infrastructure before replication can run cleanly.
Process flow
- Configure the technical web service runtime per SAP Note 1043195.
- Assign SAP_BC_WEBSERVICE_ADMIN_TEC and authorizations for SU01, SUIM, and PFCG.
- Create a dedicated service user in SU01 and assign SAP_BC_WEBSERVICE_ADMIN_TEC.
- Activate FND_SOA_REUSE_1 and the required replication business function in SFW5.
- Maintain inbound transport requests via the IMG activity or SM34 / VC_TRN_REG_RQST.
- Enable point-to-point communication infrastructure.
- Validate SLD connectivity with SLDCHECK in both systems.
- Activate Error and Conflict Handler in the MDG Hub system. Create the MDG profile in SOAMANAGER on both systems. Retrieve the Business Application ID from SAP Client Settings -> Service Identifier. Create the Provider System and maintain WS
SFW5Business function activation
Activate FND_SOA_REUSE_1 and the replication-specific business function such as FIN_MDM_SOA_ORG or FIN_MDM_SOA_CU.
SM34VC_TRN_REG_RQST
Alternative maintenance of transport requests for inbound services when the IMG activity is unavailable.
SE09Transport request creation
Create the Customizing transport request before assigning it to inbound service groups.
SLD connection validation
Verify that the Hub and Client systems are connected to the System Landscape Directory.
Goto -> Services
Copy the HTTPS hostname and port used for the WSIL access URL.
SOAMANAGERTechnical Administration -> Profiles
Create the MDG point-to-point profile with User ID/Password and No IBC Determination.
Referenced tables
| Object | Purpose |
|---|---|
FINS_HIER_CONF | Maintain inbound hierarchy configuration so global hierarchy runtime tables can be populated during inbound processing. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What are the SOAMANAGER steps for MDG Financials point-to-point replication?
- How do I set up SOA Manager for MDG-F local replication in NetWeaver 7.53 or higher?
- What prerequisite settings are needed for MDG-F replication over enterprise services without PI?
Possible questions
- Which business functions must be active for MDG-F point-to-point replication?
- Which transport request customizing is needed for inbound financial services?
- How do I maintain the provider system and logical port settings in SOAMANAGER?
- Which SLD and ECH checks are required for MDG-F local replication?
- What is the correct co-deployment rule for local integration scenarios?