on 08-20-2009 12:53 PM
I configured a scenario in id.
In ID, i can see the following when i open the interface determintation that i created.
Sender Details:
Communication Component:Sys_Sample_One_D
Interface: UserMasterQuery_Outb
Namespace: urn:sample.com:I_Legacy_JDBC_Application
Receiver Details:
Communication Component:Sys_Sample_Two_D
Interface:EmployeeEmailProcessing_Inb
Namespace:urn:sample.com:I_Legacy_FileApplication
Interface Mapping: UserMasterResultset_to_EmployeeEmail
But when i execute the scenario, and when i see in the the Interface determination pipeline step in moni, it is showing:
<SAP:Main..
<SAP:Sender>
<SAP:Service>Sys_Sample_One_D</SAP:Service>
<SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
</SAP:Sender>
<SAP:Receiver>
<SAP:Party agency="" scheme=""/>
<SAP:Service>Sys_Sample_Two_D</SAP:Service>
<SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
<SAP:Mapping notRequired="Y"/>
</SAP:Receiver>
<SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
...
...
In the <SAP:Receiver> section, the <SAP:Service>Sys_Sample_Two_D</SAP:Service> is as per my configuratioin,
but <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface> is not the interface that i configured as the receiver interface, infact this is the sender interface.
the correct receiver interface to be pickedup is EmployeeEmailProcessing_Inb
and finally it is showing the error in moni, in the Technical Routing pipeline step
<SAP:AdditionalText>No standard agreement found for , Sys_Sample_One_D, , Sys_Sample_Two_D,
urn:sample.com:I_Legacy_JDBC_Application, UserMasterQuery_Outb</SAP:AdditionalText>
the error i can see later, but i would like the right interface to be determined by PI,
i refreshed various caches etc, recreated the config objects in ID, but it is not picking up the right receiver interface.
any inputs appreciated, to find out what went wrong.
thanks,
Madhu.
after a lot of R&D, the cause we found something as below:
In the jdbc sender communication channel, i forgot to mention the non-mandatory "Document namespace" field.
after entering the right "Document name" and "Document Namespace" in the JDBC sender communication channel, it selected right receiver interface.
I am not sure, why it is mandatory to mention the namespace in the CC, and even if missed, the moni couldnot mention that as the cause.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Madhu,
-->If you maintain the correct interfaces and Business systems while creating the interface determination it will not show any wrong interface.
-->Since in the IR level while performing the INTERFACE MAPPING we need to select the outbound interface and the inbound interface.
-->So based on that also it will depend.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Have you checked:
1. Environment --> Cache Notifications under Integration Directory?
2. SXI_CACHE?
3. Are you using BPM?
4. Is interface mapping correct?
Hope this helps,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
Check the Receiver Determination , you may be having more than one . Check whether you have given any condition or the correct condition . else it will pickup the first one or will be processed by all.
Regards,
Jude
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.