cancel
Showing results for 
Search instead for 
Did you mean: 

Interface split based on the output from stored procedure

Former Member
0 Kudos

Hi Experts,

We need to develop 2 JDBC to IDOC interfaces. Based on the result of stored procedure, we have to decide to which interface, data needs to go.

We will get PacketID, PacketType when we execute the stored procedure.

If PacketType=1 need to go for interface 1

If PacketType=2 need to go for interface 2

DB team is not willing create separate SP's for both the interfaces and also they don't want to add PacketType as input parameter to SP.

At PO end, I know we can segregate this at Iflow level(interface split). But we want create seperate IFlow's.

I think we only left with adapter module. Please someone help me to create adapter module.

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

manoj_khavatkopp
Active Contributor
0 Kudos

Hi Tanu,

At PO end, I know we can segregate this at Iflow level(interface split). But we want create seperate IFlow's.

Yes you can use the PacketType as condition in interface determination and route it accordingly but why do you want to handle it via 2 different interface ? Even custom module cant help you here as the stored procedure is executed on DB end and before module execution.

Br,

Manoj

Former Member
0 Kudos

Hi Manoj,

Thanks for quick response. Business wants to see these as separate interfaces.

I am just wondering, can't we pass output from sp to module.

Thanks,

Tanu

manoj_khavatkopp
Active Contributor

Hi Tanu,

I really don't praise this solution but here is what you can do with 3 Iflows:

First Iflow: JDBC--->RD(Condition on PackType)--->SOAP1(Pointing to Second Iflow) and SOAP2(Pointing to third Iflow)

Second Iflow :SOAP1 (say PackType1)---->Actual Reciever

Thirs Iflow :SOAP2 (say PackType2)---->Actual Reciever

Br,

Manoj

Answers (1)

Answers (1)

former_member190293
Active Contributor
0 Kudos

Hi Tanu!

Frankly speaking, I don't understand and hardly can accept arguments like "... team doesn't want to ...".

Ok, let's develop the heavy-weighted and hard to maintan integration process instead?

Your primary task and duty in this situation is to explain to the business that required changes have to be made at source DB side.

Regards, Evgeniy.