Often Integration Consultants face challenge of maintaining high volume value tables sometime there is need to maintain mapping tables with huge volume for determining routing rules. This pose a challenge to developers as it becomes cluttered over the period due to ever growing new entries and becomes hard to incorporate and maintain any further addition of Values mappings.
In this tutorial we are going to explore use of SAP NetWeaver BRM for Routing Rules.
The Use Case:
The purpose of this use case it to use SAP BRM service within Receiver Determination step and provide additional inputs to Integration Flow to determine Receiver Party or Business Component at runtime.
Environment:
- SAP PO 7.50 SP14
- Compatible SAP NetWeaver Developer Studio (NWDS)
Step1: Scenario
In this use case we will explore how a Receiver Determination can be extended by using SAP BRM and a Decision Table that will be used to Lookup Receiver.
In this scenario we will Look up a BRM Decision Table based on Plant value as coming in Request payload to determine Receiver Party (Service) and Component.
In the interest of our readers and to keep this blog short we will assume an Integration Scenario exists which need to be extended using Extended Receiver Determination.
- Design Artefacts
- Create Datatype “PurchaseOrder_Request”
- Create Message type “PurchaseOrder_Request” and “PurchaseOrder_Response” based on above created Data Type
- Create Outbound Async Service Interface” PurchaseOrder_Out”
- Cretae Inboudn Aync Service Interface “PurchaseOrder_In”
- Create Message Mapping “PurchaseOrder”
- Create Operation Mapping “PurchaseOrder”
Extended Receiver Determination
- Create message mapping “ExtendedReceiver_PurchaseOrder” between Request MesasgeType and Receivers.
- Create one User Defined Function for SOAP Lookup to be called within our Message Mapping
- Add one Parameter “soapLookup” of Type SOAP
- Configuration Artefacts
- Create Integration Flow with Dynamic Recipient List using Extended Receiver Operation mapping created above.
- Deploy IFLOW.
Note: Once IFLOW is deployed an Integrated Configuration will be created and can be validated in Integration Builder as
Step2– End to End testing
For this use case we are using SOAP Sender and FILE Receiver communication channels.
Note: We can test this Integration using external tools such as Postman, SOAPUI etc…
- Message is delivered to respective Business Service and Component as defined in Decision Table.
