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

Similar Messages

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

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

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

SRM 7 - Centralised Contract Management SAP XI inbound/outbound interfaces

Hi there,
We are busy implementing SRM 7 and I would like to get "centralised contract management" working between SRM 7 and the ECC backend/s (via SAP PI).
Could you please let me know what the correct SAP PI CONTENT to load is? And what the correct service interfaces I need to use for this scenario as well as what "software component version" and "namespace" I can find them in?
Any guide on the details of this specific scenario?
Thanks for the help, much appreciated
Lynton

Note 1268821 - SRM 7.0 / ERP 6.04: Config. of Central Contract Management
Settings in PI
=================
For CCM scenario to work, PI set up is required for the following asynchronous enterprise services.
(Namespace; Software Component Version; Interface:)
http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0; PurchasingContractSRMReplicationRequest_Out
http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchasingContractSRMReplicationRequest_In
http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchasingContractSRMReplicationConfirmation_Out
http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0; PurchasingContractSRMReplicationConfirmation_In
http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchaseOrderERPContractReleaseNotification_Out
http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0; PurchaseOrderERPContractReleaseNotification_In
Settings in SAP Enterprise Portal
=================
Please refer to paragraph Settings in the Enterprise Portal in note 1263876.
Notes to be implemented
=================
Notes 1262480, 1252865, 1263470, 1260829

In PI 7.1, condition editor does not show the outbound interface structure

Hello,
I am using PI 7.1, I need to use condition whild determing receivers. So I opened the condition editor, then open the expression editor, select XPath instead of Context object. I would expect that the outbound interface structure appears in the box underneath the XPath, so that I can navigate the structure to choose the field I want to use. However nothing appears here. Do you knwo why is that? Or do I need to do anything to bring up the outbound interface structure in the expression editor?
Thanks
Jayson

Hi Jayson,
I had the same problem
the use of context objects and the value help for xpath is available for XI3.0 interfaces in PI 7.10 only. The functionality for "new" interfaces has been implemented in 7.11 only.
you have to use xpath w/o value help.
I have created a context object in one of our 7.10 test systems, and indeed I was unable to use it in a receiver determination unless the service interface pattern is "Stateles (XI 3.0 compatible)". If you were to change the service interface to that pattern, you have to change the operation name unless it is already identical to the interface name. So that may not be an option for you.
It was possible to use the context object in a receiver rule but then I could not activate the receiver determination because the software component version was supposedly unknown. I will check with my PI contacts - please let me know if the change to "XI 3.0" interface would be a possible workaround for you.
Try the steps which I am giving below, although it's a workaround and don't know the exact reason why it is failing.
1. Open your Outbound Message Interface (which you are using in your Receiver Determination) in IR, edit it and change the Interface pattern (which is there just below the category "Outbound") to "Stateless (XI30 - Compatible)" , save it activate it.
2. Follow the same step for your Inbound Message Interface. Change the Interface Pattern from "Sateless" to "Stateless (XI30 - Compatible)" .
3. Go to ID. Remove your Outbound and Inbound Message Interface from their respective Business Service/Comp and add it again.
4. Create your your receiver determination again using the Outbound and Inbound MI you have changed.
5. Open condition editor of your receiver determination.You should be able to see your Message Interface and can choose the XPath.
Thanks,
Raj
Edited by: raj reddy on Jan 21, 2009 5:41 PM

ABAP-HR OUTBOUND INTERFACE

HELLO EXPERTS,
Plz provide me with any sample code for outbound interfaces in abap-hr as i'm new to this concept.
Thanks,
Naveen Sharma

Dear Naveen,
would you mind checking this site? Perhaps you find some useful information.
<a href="http://erpgenie.com/abaptips/content/view/302/62/">ABAP Inbound/Outbound interfaces iDoc - User Exits</a>
Kind regards,
Zsolt

How to connect to third party using PI for outbound and inbound interfaces

Hello,
I have scenarios where I have data coming in from third party EDI subsystem and sent to SAP. And also from SAP to EDI subsystem. We need to send the XMLs to the EDI subsystema nd also receive XMLs.
Can someone please suggest the ways I can connect to EDI subsytem for both Outbound and Inbound interfaces.
Thanks

Hi Prabhu,
EDI file is different from the normal flat or xml file. Hope you understand the difference.
Now if your EDI subsytem has the capability of converting the xml file to edi file viceversa then create and receive the xml file from the EDI subsystem. For the xml file you may use the file adapter as an option.
If it doesnot have the capability then seeburger adapter needs to be used. This is not an inbuilt adapter. So your company needs to purchase it.
Regards,
---Satish

Can I supress BPM for Asyn outbound and syn inbound proxy interface

Hi all,
Is there any other alternate to remove the BPM at asyn outbound and syn inbound proxy interface. Reason because I can create another outbound proxy interface at the receiver. But at receiver side we already invested huge code to develop the sync server proxy. So the intension is, with out disturbing the code Can I make the message flow with out BPM?
Because the reason of removing BPM is for a simple interface like this I don't want to use BPM. souce is JDBC and receiver is ECC 6.0. I know with out BPM it can not be achieved but in PI 7.1 EHP 1 by any chance can we do?
I mean during response mapping from server proxy shall we use look up function to achieve?

This bean I have to use at sender channel right?
Yes
I mean is it is limited to JMS adapter?
No
You can find more information in the Wiki which deals with FILE to RFC synchronous...using the above Module

BPM with 2 JDBC outbound interfaces and one inbound file interface

Hi,
I have a scenario where data is coming from different databases into XI and after processing the data it creates a file at the target side. Some calculations are to be done in the middleware and the result will be sent through a file.
My question is
1. BPM will be used in this scenario?
2. There will 2 outbound interfaces(one for each database access), 2 abstract interfaces and one inbound interface(file). Please correct me if I am wrong.
3. I have to multiply the value of field from one database to a particular value in another database and get the final result. For e.g exchange rate from one database is multiplied to Transaction currency in another database and get the group currency value in the output. Can anyone give the sequence of steps in the intergration process for this scenario as I am new to BPM.
Thanks,
Aparna

Thanks a lot Liang and madhusudana for your responses.
Since I can use JDBC lookup for this in my nornal scenario I think no need for BPM.
I have created the advanced UDF for JDBC lookup code. Below is the code.
String Query = " ";
Channel channel = null;
DataBaseAccessor accessor = null;
DataBaseResult resultSet = null;
MappingTrace importanttrace;
importanttrace = container.getTrace();
// Build the Query String
Query = "Select home_cur_code FROM gltrxcp WHERE company_code = '" + a[0] + "' ";
try{
//Determine a channel, as created in the Configuration
channel = LookupService.getChannel("BS_JDBC_send","cc_JDBClookup_rec");
//Get a system accessor for the channel. As the call is being made to an DB, an DatabaseAccessor is obtained.
accessor = LookupService.getDataBaseAccessor(channel);
//Execute Query and get the values in resultset
resultSet = accessor.execute(Query);
importanttrace.addWarning("resultset" + resultSet );
for(Iterator rows = resultSet.getRows();rows.hasNext();){
Map rowMap = (Map)rows.next();
result.addValue((String)rowMap.get("HOME_CUR_CODE"));
importanttrace.addWarning("result" + result );
catch(Exception ex){
result.addValue(ex.getMessage());
finally{
try{
if (accessor!=null) accessor.close();
catch(Exception e){
result.addValue(e.getMessage());
But I am not getting the desired result. I am getting result as 'Null'.
Can you please help in resolving this issue. I have also used trace for find out where it is passing Null and found that 'result' is coming null. Do i also need to parse it before passing it to 'result'?
Can anyone send sample code for JDBC lookup.

Regarding Inbound and outbound interfaces in ABAP HR

Hi,
Iam new to SAP. Can you send the document related to Inbound and Outbound Interfaces in detail.
i.e What these interfaces comes under and steps to develop these inerfaces.
Thanks&Regards,
B.Thulasi.

Hi,
Iam new to SAP. Can you send the document related to Inbound and Outbound Interfaces in detail.
i.e What these interfaces comes under and steps to develop these inerfaces.
Thanks&Regards,
B.Thulasi.

How to do an inbound and outbound interfacing using UTL_FILE ?

dear members,
How can we do interfacing from a legacy system to oracle and vice versa using the UTL_FILE package. I mean how to do an INBOUND and OUTBOUND interfacing using utl_file.
regards
sandeep

in/
file/
bad/
done/
out/
file/
bad/
done/
I would start by ftping / putting the file in in/file/ folder, once ftp has completed move it to complete/ folder and process the file. If errorrs are generated move the file over to bad folder. If completed successfully move over to done folder.
Having said that you would use UTL_FILE_DIR init parameter to set your directory.
ALTER SYSTEM SET UTL_FILE_DIR='directory1','directory2' scope=spfile;
Then you would use the regular utl_file packages to read / write to the files.
UTL_FILE.FOPEN and so on.

How to do inbound and outbound interfacing using UTL_FILE?

dear members,
How can we do interfacing from a legacy system to oracle and vice versa using the UTL_FILE package. I mean how to do an INBOUND and OUTBOUND interfacing using utl_file.
regards
sandeep

Hi Sandeep,
I do not know if I got your question correct.
Here is my understanding of it, pls correct me if I am wrong:
You want to read from and write to the OS from inside the DB? Right?
There are differnt waysa to do so, depanding on your Oracle version:
1. you can use the initialization parameter UTL_FILE_DIR to specify a directory on OS where you can read from and write to through the package UTL_FILE.
2. You can use a directory object in the DB to manage read write access to the OS. This is also usable with the package UTL_FILE as location where to read from and write to.
=> CREATE DIRECTORY my_dir AS '/home/oracle/my_directory';
GRANT read , write ON DIRECTORY my_dir TO scott;
SELECT * FROM dba_directories;
You need CREATE ANY DIRECTORY system privilege for this.
You can use directory objects also for external tables.
With these you can read from flat files in teh directory on OS with a select statement as if it were a table inside the DB.
Does this go into the direction you were thinking of?
Hope it helps for the first.
Regards,
Lutz

When To Use Inbound and Outbound Interfaces?

I use an Inbound message type when i am receiving some data and outbound message type when i push data out of the XI box??Is this correct..
And how to decide when to use a Inbound and Outbound Interface?

Hi Barik,
<b>I use an Inbound message type when i am receiving some data and outbound message type when i push data out of the XI box??Is this correct..</b>
WRONG!!!
outbound message->XI->Inbound message...
(sender system)->XI->(reciever system)
remeber: when u r sending some data to XI u send it using outbound interface.
and when u r sending some data from Xi to other system u use inbound interface...
Hope ur doubt is clear!!
regards
BILL
Use a Good Subject Line, One Question Per Posting - Award Points

Inbound interface found more than once for outbound interface

Hello everybody,
i have a simple problem.
I build a interface with XI3.0
File to idoc
for each file i need crate 2 idoc.
It's not a problem when Idoc type is different, but in my case i need crate 2 idoc of same type but with a different mapping.
so when i upload the file i have this error:
Inbound interface found more than once for outbound interface
how can i solve this problem? can i force this step?
i thought to create a different idoc type or create the 2 idoc in same mapping , but there is not my favourite solution because in case of error , both idoc will be not created.
any suggestion?
thanks in advance
alex

Hi,
Instead of exporting and changing the occurrence as suggested by Ravi,
use the same Idoc twice in mapping as well as Interface mapping.
Coming to ID part, do every thing as usual.
The only thing to note is instead of using normal Interface determination, use extended Interface Determination.
This will solve your problem. The error will not come again. I'm sure.
Try out and update the thread.
Regards,
Jeevan.

BPCA - Portal Changes and Inbound/Outbound Interfaces

Similar Messages

Maybe you are looking for