No inbound/outbound interfaces for Business Systems

Hi,
after upgrading from XI 3.0 to PI 7.1 there are no inbound and outbound interfaces in the Communication Component definition for our Business Systems any more.
We didn't change anything in SLD.
Does anybody know why these entries are lost in 7.1?
Regards
Thorsten

Hi Thorsten,
I faced the same problem while i was trying to select the interfaces while configuring the scenario in ID.
I could not found any interfaces after i selected my Business System for the sender.
Solution: Go to the SLD.
In the technical system Go to the
Technical System------> Installed Software (TAB) and add the Product name under this tab as it appears in the IR.
After this you need to go to the corresponding business system
Business System-----> Installed Software (TAB) check the installed products under this tab.
This has done the solution for me.
Hope this will help.
Thanks
Ajay

Similar Messages

Monitoring of inbound and outbound messages for business system ECC 6.0

Hi Guys,
I am working on ABAP proxy. I want to monitor the flow of Inbound and Outbound messages for my Business system (ECC 6.0).
XI server is on a different system.
I understand that SXMB_MONI is used for tracking XML messages. What kind of tracking can we do by this transaction in our Business system and the XI system?
And how do I know whether the outbound XML message sent is lying in the Sending Business system or in the XI system?
When I am testing my interface, there is a fault message generated. How do I know whether the fault message is being sent to XI?
Thanks,
James.

James,
Go to SXMB_MONI in your sending system.
Here you will find a message ID fro your Message.
Go to XI, --> SXMB_MONI -->Monitor For Processed XML messages --> Advanced Selection Crieteria and use the Message ID here to see if the Message has hit XI or not.
Likeiwse it can be traced in the target system as well.
The basic point, The messages will have same Message Id on your R3 and on XI.
Regards
Bhavesh

Including Inbound and Outbound Interfaces to Business System

Hello
Iam new to SAP XI, but have expierence in webMethods EAI Tool.
Iam developing a sample interface to pick and put a file in SAPXI itself and for this have created the Interface(data type,mesg typ , mesg inetface , mappin and interface) in Repository.
Now to pick and put file what setting should have to do in Directory.
I have added a Business Service, but it is not listing the Component which was created by me from SLD (only standard component versions which came along with SAPXI are listed). Because of this the interface (inbound and outboound) which was created in my component is not listed.
Can any one help me with this.
Also can you suggest an devleopment doc to refer.
Thanks
Vinod

Hi Vinod,
Check out this thread..
Inconsistence Adapter Framework
No entry for adapter engine in CPACache
Also check OSS Note : 764176 - Error in XI due to inconsistent SLD contents
This note provides a lot of information, but may not be enough. Carry out the following checks:
check that the CPACache works ok
check that sxi_cache works ok
check that sxi_cache->goto-->AE Cache shows an entry for the adapter engine
check the roles for the service users, especially xidiruser
Nilesh

Need information on how to create Idoc Inbound Interfaces for Business Sys

Hi,
I'm losing it.
Can anyone point me to some documentation or an example of how to create inbound interfaces for Business Systems in PI 7.1.
Here's the scenario
I'm working on a B2B integration process which sends inbound idocs to an ECC 6.0 system.
I've created the Business System communication component but under the Inbound Interfaces it is blank.
I want to have MBGMCR.MGBMCR03 as an inbound interface.
But I forget how to get it there.
For Business components you can just add the inbound interface.
I've already defined the Business System in the SLD pointed it to the correct Tech System, imported the idoc definitions in the Enterprise Service Builder and set up IDX1, IDX2 to ensure the metadata exists in PI.
But for Business systems the hep says that it's got to come from the SLD.
Outbound/Inbound Interfaces
For each business system, the interfaces that are installed on the business system are also entered in the SLD. These interfaces are displayed in this frame. You cannot add any other interfaces.
I know I've done this before, but I can't remember how.
Cheers,
John

Hi John ,
Please have a look at the following links which might be of help to you
PI 7.1 IDocs interfaces act as operations
http://www.sdn.sap.com/irj/scn/weblogs;?blog=/pub/wlg/7933
/people/peter.gutsche/blog/2008/10/27/what146s-new-in-sap-netweaver-pi-71
There is a section in the following link on IDOC , have a look at the links in that section
https://wiki.sdn.sap.com/wiki/display/XI/ImportantBlogsand+Notes
Best Regards

Need sample programs for inbound & outbound interfaces in abap hr?

hi friends
i need sample programs for inbound & outbound interface programs in hr abap . any one send me pls
thanks & regards
deepurd

&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Report ZPROG65_11 *
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
REPORT zprog65_11 .
TABLES : lfa1.
TYPES : BEGIN OF ven ,
lifnr LIKE rf02k-lifnr,
bukrs LIKE rf02k-bukrs ,
ekorg LIKE rf02k-ekorg,
ktokk LIKE rf02k-ktokk,
name1 LIKE lfa1-name1,
sortl LIKE lfa1-sortl,
land1 LIKE lfa1-land1,
spars LIKE lfa1-spras,
akont LIKE lfb1-akont,
fdgrv LIKE lfb1-fdgrv,
waers LIKE lfm1-waers,
anred LIKE lfa1-anred ,
END OF ven .
DATA : t_ven TYPE TABLE OF ven WITH HEADER LINE ,
t_bdc LIKE TABLE OF bdcdata WITH HEADER LINE .
DATA : v_file TYPE string ,
v_temp TYPE i ,
v_lifnr(10) TYPE n,
v_hdate LIKE sy-datum.
DATA : c_tcode LIKE sy-tcode .u201Dvalue u2018XK01u2032.
PARAMETERS : p_file(30) DEFAULT u2018c:\vendor1_11.txtu2019,
p_group LIKE apqi-groupid.
START-OF-SELECTION .
MOVE p_file TO v_file .
PERFORM file_upload TABLES t_ven USING v_file .
v_hdate = sy-datum - 1.
CALL FUNCTION u2018BDC_OPEN_GROUPu2019
EXPORTING
client = sy-mandt
DEST = FILLER8
group = p_group
holddate = v_hdate
keep = u2018Xu2019
user = sy-uname
IMPORTING
QID =
EXCEPTIONS
client_invalid = 1
destination_invalid = 2
group_invalid = 3
OTHERS = 11
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT t_ven .
clear lfa1.
v_temp = 0.
MOVE t_ven-lifnr TO v_lifnr.
SELECT SINGLE * FROM lfa1 INTO lfa1 WHERE lifnr =
v_lifnr.
IF sy-subrc = 0.
WRITE :/ u2018foundu2019.
v_temp = 1.
else.
write: / u2018not foundu2019.
ENDIF.
IF v_temp = 0.
c_tcode = u2018xk01u2032.
PERFORM fill_ddc_table .
ELSEIF v_temp = 1.
c_tcode = u2018xk02u2032.
PERFORM fill_bdc_table .
ENDIF.
CALL FUNCTION u2018BDC_INSERTu2019
EXPORTING
tcode = c_tcode
TABLES
dynprotab = t_bdc
EXCEPTIONS
internal_error = 1
OTHERS = 7.
REFRESH t_bdc .
ENDLOOP .
CALL FUNCTION u2018BDC_CLOSE_GROUPu2019
EXCEPTIONS
not_open = 1
queue_error = 2
OTHERS = 3.
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Form file_upload
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
u2013>P_T_VEN text
u2013>P_V_FILE text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
FORM file_upload TABLES p_tven STRUCTURE t_ven
USING p_vfile.
CALL FUNCTION u2018GUI_UPLOADu2019
EXPORTING
filename = p_vfile
filetype = u2018ASCu2019
has_field_separator = u2018Xu2019
IMPORTING
FILELENGTH =
HEADER =
TABLES
data_tab = p_tven
EXCEPTIONS
file_open_error = 1
file_read_error = 2
OTHERS = 17
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. u201D file_upload
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Form FILL_DDC_TABLE
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
u2013> p1 text
<u2013 p2 text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
FORM fill_ddc_table .
SCREN 100
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180100u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-LIFNRu2019.
t_bdc-fval = t_ven-lifnr .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-BUKRSu2019.
t_bdc-fval = t_ven-bukrs.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-EKORGu2019.
t_bdc-fval = t_ven-ekorg.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-KTOKKu2019.
t_bdc-fval = t_ven-ktokk.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
110
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180110u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-NAME1u2032.
t_bdc-fval = t_ven-name1 .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SORTLu2019.
t_bdc-fval = t_ven-sortl.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-LAND1u2032.
t_bdc-fval = t_ven-land1.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SPRASu2019.
t_bdc-fval = t_ven-spars.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
120
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180120u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
130
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180130u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018=ENTRu2019.
APPEND t_bdc. CLEAR t_bdc.
210
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180210u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFB1-AKONTu2019.
t_bdc-fval = t_ven-akont .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFB1-FDGRVu2019.
t_bdc-fval = t_ven-fdgrv.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
215
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180215u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
220
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180220u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
310
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180310u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFM1-WAERSu2019.
t_bdc-fval = t_ven-waers .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
320
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180320u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018=UPDAu2019.
APPEND t_bdc. CLEAR t_bdc.
ENDFORM. u201CFILL_DDC_TABLE
u201D FILL_DDC_TABLE
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Form FILL_BDC_TABLE
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
u2013> p1 text
<u2013 p2 text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
FORM fill_bdc_table .
SCREN 101
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180101u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-LIFNRu2019.
t_bdc-fval = t_ven-lifnr .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-BUKRSu2019.
t_bdc-fval = t_ven-bukrs.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-EKORGu2019.
t_bdc-fval = t_ven-ekorg.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
110
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180110u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018lfa1-anredu2019.
t_bdc-fval = t_ven-anred .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-NAME1u2032.
t_bdc-fval = t_ven-name1 .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SORTLu2019.
t_bdc-fval = t_ven-sortl.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-LAND1u2032.
t_bdc-fval = t_ven-land1.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SPRASu2019.
t_bdc-fval = t_ven-spars.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
300
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180300u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018=YESu2019.
APPEND t_bdc. CLEAR t_bdc.
ENDFORM. u201D FILL_BDC_TABLE
Best Regards

BPCA - Portal Changes and Inbound/Outbound Interfaces

Hello Solman 7.1 Experts,
Currently involved in a BPCA implementation and have a question regarding that. In an SAP landscape Can BPCA be used to detect changes made in Portal and Inbound/Outbound Interfaces.
Most of the SAP documentation that I have come across so far speak to the functionality but hasnt covered scope. I would really appreciate your input.
Thanks,
-Anshul

Hi Thorsten,
I faced the same problem while i was trying to select the interfaces while configuring the scenario in ID.
I could not found any interfaces after i selected my Business System for the sender.
Solution: Go to the SLD.
In the technical system Go to the
Technical System------> Installed Software (TAB) and add the Product name under this tab as it appears in the IR.
After this you need to go to the corresponding business system
Business System-----> Installed Software (TAB) check the installed products under this tab.
This has done the solution for me.
Hope this will help.
Thanks
Ajay

Creation of one outbound interface for two diferent senders

helo.
i just want to conform ont thing that .
my scenario is two diferent files from 2 diferent business systems are sending to one Rfc.
so i was created only one outbound interface for both senders and one message type bcos the file structure is same for both senders.
so is there any thing wrong in creating only one datatype,message type,message interface for both senders.
waiting for your response.
cheers.
seeta ram.

Hi Ram,
That is perfectly correct when you have two senders and one receiver Scenario and Business Service is different. Then you can use the same Interface.
Just keep in mind that the key for XI to recognise the Right interface is combination of these 3 parameters:
Sender Service, Sender Interface and Namespace. These cannot be duplicated.
When the Message type is same in the sender input data then you can create just one Message Type and One Data type and RFC is anyhow the imported RFC which you need not have to worry.
In Configuration Scenario you need to configure separately the RD, ID, CC and Agreements for the Interfaces.
Hope this answers your query. Let us know if you need anymore clarification
Thanks
Srini

Table to find the interfaces for a system

Hi,
I need to find the number of inbound and outbound interfaces for a particular system.
Is there any specific table to find the total number of entries?
WE20 is a transaction to find it out manually. But I guess there is some table where we can find it in a easier way.
Kindly reply...
Thanks!.

Hi
You need to find the Message type and IDoc types
use table EDBAS for IDOC types and
EDMSG for finding message types
EDPP1 for all partner profiles
EDP12 and EDP13 for inbound and outbound views
Reward points if useful
Regards
Anji
Message was edited by:
Anji Reddy Vangala

Transport target for business system not found in System Landscape Director

Folks,
We have new installed new PI 7.1 system and importing interfaces from the OLD XI 3.0 system in to new PID 7.1 system.
We are getting following error when we try to import an interfaces in to new PID system:
Import failed because of business system transfer object
Communication component XID_FileSystem: Obligatory
transport target for business system XID_FileSystem not found in
System Landscape Directory
We are yet to install PIQ system.
All the interfaces in the old XID system have transport target of XIQ system. I removed the transport taget for the interface, but transport target is still showing in the Business system under transport target head.
How can we overcome this issue as we will not have PIQ system atleast for two weeks.
Thanks in advance,
Regards
Chandu

Hi,
You need to maintain Transport Groups and target for business systems while SLD transports between your XI system and PI 7.1
Illustrated with DEv & PRD here.
Procedure:
1) Call Integration Builder screen on DEV Server with http://hostname:J2ee Port/rep
2) Call SLD (System Landscape Directory) Component from the Integration builder
Save all the Following .zip files on the Local Desktop
3) Select the Software Component & say Export that you want to Export from DEV
Server to Production server and which is going to use in the IR of XI
4) Also Select the Product of the above SWC and say Export
5) Select the Technical Systems (TS of XI & TS of the SAP R/3) and say Export
6) Select the Business System(s) & say Export; those are associated with above Exported
Technical systems.
In Production Server
1) Logon to the SLD of the Production Server.
2) Create a Technical System and Business system which points to the Production SAP R/3
3) Go to Administration TAB in the main page of SLD
4) Select the Import option to Import the SWC , PRD, TS,& BS which we Exported Earlier in DEV Server
5) Click on Browse and select the .zip files that is to Import into Production Server,
Which were stored on the local desktop at the time of DEV Server Export
And say Import Selected File Option
By this we exported and imported the SLD Objects
Now we have to create transport groups and transport targets in the Production server of SLD
Creation of Transport Groups
Edit GroupsGroup1) Select the Business systems
2) Click on New Group and give the name of the group as DEV_group & select the
Corresponding Development serveru2019s integration Server
3) Similar way create another group for Production serveru2019s business system as
PRD_group and select the Production serveru2019s integration Server
Creation of transport targets
This is to Define which business systems in two different groups correspond to each other
1) Select each Business system in the SLD and select transport TAB---click on
Add/Change Target and select its corresponding target business system.
For Example:
If you select the business system of Production XI server means
In the target you have to select group as DEVGROUP and the business system of Development XI server.
Like this do the same for other business systems also
Ex:
BS_PRD_Integration Server----
BS_DEV_Inetration Server
How to create Transport Groups & transport Targets
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
Regards
Seshagiri

Oracle EBS Inbound/Outbound Interface build using Oracle SOA 11g

Hi SOA Guru's,
I am very much new to SOA 11g, could you guy's help me in understanding "How I can build any Oracle EBS Inbound/Outbound interface using Oracle SOA 11g"
It will be great if anybody explain me with any example script/screen shot/document.
Thanks in advance.
Regards
Pankaj

I don't have any experience with ebs, but i assume it works like this.
In the composite editor you will find a list adapters at the right..over here you will also find the oracle applications (ebs) adapter.
This will be the component for you which will communicate with the ebs packages.
you need to drag this adapter on the swim lane, and after that you should create the composite application like the way it's described in the tutorials Oracle supplies, put a mediator component in the middle and expose this interface (drag the line to the left swim line)
Hope it's a bit clear like this ?
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/fod_intro2.htm
this should make a few things clear too

Obligatory transport target for business system SAPR3D not found in System

HI All ,
We have installed New PI 7.1 system and stared migrating the interfaces from XI 3.0 to PI 7.1 . in Devlopement system .
IR object have been successfully deployed but while delopying ID objects got the following error . Obligatory transport target for business system SAPR3D not found in System Landscape Directory.
When I checked with business system transport target was not defined ., Please suggest how to go ahead further .
Thanks ,
Prakash

Hi Ravi,
Please go through below disucssion it is on the same line of your question.
Transport target for business system not found in System Landscape Director

More than one outbound interface for the webservice scenario

Hi Experts,
Is it possible to have more than one outbound interface for the Webservice synchronous scenario? I have tried it , but I couldn't implement it.
I would like to have your suggestions.
Regards
Sara

Hey,
Creation of a wsdl file
/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
N:1 seemz he was refering to multimapping scenario.
Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*

DEV- QAS : Obligatory transport target for business system not found

Hi guys!
I have read all the other threads about this subject, but since I still have no success, I´m feeling obligated to ask you for a help (deadline approaching fast!)
I´m trying to transport a Communication Channel, from DEV environment to QAS. I'm having the 'usual' error:
Import failed because of business system transfer of object Communication Channel * | SIGA | SOAP_SYNC_SENDER: Obligatory transport target for business system SIGA not found in System Landscape Directory
Here were my steps:
Keep in mind that in DEV, everything was up and running: Software Component, Product, Technical System and Business System for this name "SIGA".
1 - In DEV, I created a new Technical System, named "SIGA_QAS", pointing to my QAS server. (Keeping in mind I already had a "SIGA" pointing to my DEV server.)
2 - Still in DEV, I did create two groups: GROUP_DEV and GROUP_QAS, one points to INTEGRATION_SERVER_DX1 (DEV) and the other INTEGRATION_SERVER_QX1 (QAS).
3 - Still in DEV, I created the Business System called "SIGA_QAS" also, pointing to my QAS server.
4 - Still in DEV, I went inside both Business Systems and put: "SIGA_QAS" as TARGET BS of "SIGA" (which automatically puts "SIGA" as SOURCE BS of "SIGA_QAS")
If I look at my QAS SLD, I can see all of these objects already there, since my BASIS team did activate the 'sync' between these two environments. So, I dont need to create anything 'new' in my QAS SLD, all the objects are there, same as DEV SLD.
If I try to EXPORT/IMPORT a simple Communication Channel (using file system or even CTS - I tried both) I get the error mentioned above.
But this is 'wierd' for me, since the error says: "business system SIGA not found in System Landscape Directory", but it is there, in both SLDs.
Am I missing something here?
Thanks!
Ricardo Sancio Lóra
Brazil

Hi,
If you not tried this then try it. Delete the Business System SIGA from Integration Directory in your QAS system and then again import the business system from SLD. Acitvate the changes and then import the CC from Dev to QAS.
Regards,
Sarvesh

Role for business system defined in SXMS_CONF_ITEMS'

hi
in RWB integration engine status is red in detail it is showing.
'No role for business system defined in SXMS_CONF_ITEMS'.
how can i fix this.
regards,
krushi

HI
Runtime Workbench - Integration Engine
Are the Roles in SXMS_CONF_ITEMS and the SLD Consistent?
//***The role of a business system is defined centrally in the SLD. However, you can overwrite this setting locally in the table SXMS_CONF_ITEMS.
This test checks whether the role descriptions are consistent. If not, the locally defined role is used at runtime.
extract taken from this thread
http://help.sap.com/saphelp_nw04s/helpdata/en/a5/1b5342d8a7be30e10000000a155106/frameset.htm
Message was edited by:
Anusha Ramsiva

No role for business system defined in SXMS_CONF_ITEMS

Hi Experts.
I have the following problem. We were set up the XI in our company and now we are trying to configure and run it propertly. We had some problems so far and now there is the next one: I configured the simple scenario FILE-XI-FILE but it doesn't work :(. Every step from the scenario was completed successfully (after some problems) but when I have started runtime Workbench (RWB) in order to monitor the functionality of XI and I choosed Component Monitoring | Components | Integration Server | Integration Engine GPI I see that I have an error in Self-Test Status | Are roles in SXML_CONF_ITEMS and SLD consistent? In detail it's No role for business system defined in SXMS_CONF_ITEMS. My business and technical systems look to be well configured but now I'm hopeless because I can't find nothing more specific about SXMS_CONF_ITEMS table. I tried some notes and threads from the forum but nothing helped me after all. So please help if someone has an experience with something similar. Any help will be appreciated. Thanks
Ondrej

Hi,
The role of a business system is defined centrally in the SLD. However, you can overwrite this setting locally in the table SXMS_CONF_ITEMS.
This test checks whether the role descriptions are consistent. If not, the locally defined role is used at runtime.
Check in transaction SXMB_ADM -> integration engine configuration a parameter (Corresponding Integ. Server) if all parameters are correct n not lost.
refer : http://help.sap.com/saphelp_nw04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/content.htm
Runtime Workbench - Integration Engine
http://help.sap.com/saphelp_nw04s/helpdata/en/70/58b43be7492354e10000000a114084/frameset.htm
Regards
Aashish Sinha
PS : reward points if helpful

No inbound/outbound interfaces for Business Systems

Similar Messages

Maybe you are looking for