REG: SFTP to SFTP scenario

Hi All,
         I have a SFTP to SFTP scenario where file is getting picked up from the source location and failing at the taget side.
       When tested with File to SFTP the same channel is able tp place file sucessfully.
       However when scenario becomes SFTP to SFTP the receiver SFTP channel fails to place the file.
          I am using see burger adapter to connect to sftp server.
Please help me on this.
Thanks,
Siva

Hi,
       I dont have certificate issuse with the target system because when i do a File to SFTP scenario with same channel the channel is owrking fine.
       But when i make it SFTP to SFTP scenario the receiver channel is failling.
     I have maintained all the certificates in the trusted keystore.
Thanks,
Siva

Similar Messages

SFTP to Mail Scenario

Hi
Am trying to Pass an PDF file using the sFTP to Mail scenario. i also have to keep the same file name of the source.
(ie Attachment should have the source file name). i have tried all the possible ways to do it but the files get stuck up at the Mail adapter with error
Exception caught by adapter framework: com.sap.aii.messaging.util.XMLScanException: java.lang.NullPointerException; nested exception caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 25, 50, 44(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 25, 50, 44(:main:, row:1, col:3)
I am not able to use the MM as there are some special charcter coming in the PDF document.
Currently am using the JAVA Mapping to pass the file name and the data.
Experts please help.

Hi,
Find below link will helpful for configuration, but as per my knowledge file name at attachment will take as message id. Check it with below link, i hope it will work
/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure

FTPS or SFTP for file scenario. Suggstions

Hi,
I have searched blog in sdn but do not get good blogs/links.
For File scenario which to use FTPS or SFTP.
How to do the configuration in XI and Visual admin.
Full points will be awarded.

Hi,
1) SFTP (Secure File Transfer Protocol)
"SSH File Transfer Protocol" or SFTP is a network protocol that provides file transfer and manipulation functionality over any reliable data stream. It is typically used with the SSH-2 protocol to provide secure file transfer. SFTP encrypts the session, preventing the casual detection of username, password or anything that is being transmitted. One key benefit to SFTP is its ability to handle multiple secure file transfers over a single encrypted pipe. By using a single encrypted pipe, there are fewer holes in the corporate firewall.
SFTP:
As per the latest SAP PI/XI support pack, it does not support SFTP via File Adapter.
So alternative approach to cater this requirement from XI is to make use of Unix Script at OS level to transfer the files from/to third-party systems.
Inbound Interface - i.e. third-party system ->XI->SAP:
File is transferred to a folder in SAP XI landscape from the third-party legacy system using UNIX Script with secured protocol. Once the file is ready in the XI landscape, File Adapter will poll this directory and file is picked up by NFS protocol.
Outbound Interface i.e. SAP->XI->third-party system:
XI is responsible for writing a file into a folder in the XI landscape. These files are transferred to the third-party system by executing UNIX scripts with secured protocol i.e. via sFTP.
Pre-Requisites:
Public key should be exchanged between external systems and the PI system.
UNIX shell script has to be developed and scheduled.
Advantages:
Highly Secured.
Ability to handle multiple secure file transfers over a single encrypted pipe .By using a single encrypted pipe, there are fewer holes in the corporate firewall.
Disadvantages:
Two-Step process i.e. XI>Temporary folder>External System and vice-versa
Files have to be temporarily stored in XI server.
Multiple failure points i.e. XI and Unix script execution
Maintenance of an external UNIX script.
Difficulty in monitoring the execution of the shell script as it cannot be monitored thru XI.
Need to generate keys and install it in the SFTP site as a pre-requisite i.e. SFTP clients must install keys on the server.
SFTP uses keys rather than certificates. This means that it can't take advantage of the "chains of trust" paradigm facilitated through Certificate Authorities.
Files from the XI server should be deleted/archived in a periodic manner to increase the disc space so that it will increase the performance.
Note: UNIX shell Script can be executed as a background job or' can be triggered from SAP XI through OS command at File adapter level.
Secure FTP (SSH) with the FTP Adapter
Secured File Transfer using SAP XI
Secure FTP in SAP XI
SFTP (FTP over SSH) in XI
/people/krishna.moorthyp/blog/2007/07/31/sftp-vs-ftps-in-sap-pi
encryption adapters or how to secure data
/people/krishna.moorthyp/blog/2007/07/31/sftp-vs-ftps-in-sap-pi
Regards,
Phani
Reward points if Helpful

SFTP to File Scenario using multiple files

Hi All,
I have a scenario wherein 2 separate CSV files ex a.csv and b.csv has to be picked up from the SFTP folder and the same has to be mapped and send to one single file ex c.csv.
Say a.csv contains fields Name,Address and b.csv contains Phone,Mobile and I need to map them as per FSD into c.csv which will then have Name,Address,Phone,Mobile
I am bit confused on how to do it.
Shall I use Additional File name option in SFTP sender channel configuration? In that case how will I use the FCC as we have 2 separate csv files and both the files are CSV files and needs to be converted to XML.
Any related threads will help.
Regards,
Shaibayan

Hi Inaki,
Thanks for your reply.
BPM is not an option in our case as we are told not to use BPM.
However as per the thread from Michael
"pick both files in one run (one as file, the other one as attachment - so one communication channel )
inside the mapping you can get the values from the attachment and do the mapping"
This part is fine and we can do the mapping by creating N:1 mapping but since our files are .csv files so a content conversion is required for both the a.csv and b.csv. How to go through with this.
The structure will be something like below in the message mapping after we add both the source structures in Signature Tab:
Message
     Message1
          MT_FILE_A
               RecordSet1
                    Name
                    Address
                    Field3
     Message2
          MT_FILE_B
               RecordSet2
                    Phone
                    Mobile
Can I use the below values for Content Conversion?
Document Name:MT_FILE_A,MT_FILE_B
Recordset Structure:RecordSet1,*,RecordSet2,* or we have to use MT_FILE_A.RecordSet1,*,MT_FILE_B.RecordSet2.*
And in the Name Value for Name do we need to use dot for each Document Name i.e.
MY_FILE_A.RecordSet1.fieldSeparator?
Regards,
Shaibayan

Reg:file to idoc scenario

In a file-xi-idoc scenario i created a business service for legacy
system and a business system for R/3 receiver system
i didn't assign logical system for the sender business service
and assigned a logical system for the reciver business system
so while maintaining partner profile in the R/3 system
i have to give partner no:
partner type:
here the problem is my sender business service i didn't assign any logical system,and it is not of LS type
so then what do i need to give in the above two fields?
answers required briefly

Hello,
you know this pdf:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
Could be helpful.
Regards
Patrick

Reg http to jdbc Scenario

Hi all,
I am trying to execute a synchronous Http to Jdbc Scenario using MS Access table as my back end.
In design part ,I have followed the steps like
1. Created a http req ,jdbc req, jdbc response ,and then http response in Data types and the in Message types.
2.Created Outbound MI with http req and http response as input and output messages respectively,then Inbound message interface with jdbc req and jdbc response as input and output messages respectively.
3.In Message mapping with Http req and jdbc req as request mappings and jdbc response and http response as Response mappings following the Action and access Steps.
Thats Fine with design part
IN Configuration Part, Since it is a Http Sender ,i didnt create any sender agreement and sender communicatin channel.
Then Configured Jdbc adapter properly and i am able to access my table with that.
While Executing ,I can find that my message is sent in Runtime workbench and can find that Jdbc adapter is Running by showing green flag.
I was trying to send an empid of a table as key and expecting to retrieve the complete row of the corresponding key.
But I could not find the response even though everything is fine with XI.
Where Could be the problem ,where can I see the response from jdbc adapter .
Please help me out in solving this .
Thanks and Regards,
Kalpana

Hi Kalpana,
Can you check this weblog
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
This should help you...
Check the Response Mapping,also you have one IM with Reqest and Response mapping...
Also if you have SP16 then you can have sender CC for HTTP also ...
Regards,
sridhar

Reg: JDBC to IDOC Scenario Message Mapping

hi Friends
i am designing a Scenario JDBC - IDOC for accounting document interface using ACC_DOCUMENT03 idoc.
i need the mapping program for that to map the JDBC fields with the IDOC fields, so can anyone help me the mandatory fields and the constant values for the IDOC which has to be mapped.Along with this can i know why the constants will be assigned to the fields like Begin =1 , MSGFN = 009 etc how these constants are defined.
Thanks&Regards
suman.

Hi,
for mapping constants in graphical msg mapping, select your target IDOC field..........then you have a constant in the below screen.........click it and then double-click on constant to change the value of the constant field.........then map this constant to your target IDOC field.
for knowing which are the mandatory fields, ask your functional guys to tell you the mandatory fields in data segment of your IDOC and regarding Control segment EDIDC, you have to map fields which have sender and reciever system details.
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Feb 2, 2009 7:55 AM

Reg:Steps in IDOC Scenario

Hi,
    I am very new to IDOC concept so can anyone tell me what is the use and why do we want to create,
1)RFC Destination
2)Port
3)Logical sysytem name
4)Partner Profile ,in IDOC Scenario and also let me know the steps that I have to implement while doing that scenario.
Thanks in advance
B.Lavanya

Hi,
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Sending System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select create new button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in SAP R/3 towards other system
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Outbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
5)   Create Customer Distribution model in the transaction code BD64
1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3)   Save the Distribution model
    Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
4)   Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> Distribute to the destination client
    Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
             Step2:Repository
1)       From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
         From the list of Software Component Versions, Choose your own software component version .Click Import.
3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
         Your NameSpace is urn : DSZVFGD
4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
         After this specify the connection parameters to the R/3 system:
4.1)     System :SAPFOX
4.2)     Client :800
         Then Save it. The new namespace will be visible under software component version node in the left frame.
         Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3)     Application server:172.25.5.7
4.4)     System number:00
4.5)     User name: DEVELOPER
4.6)     Password: Password of Sap R/3 system.
         Then click continue .You will find IDOC node. Click on this node and select the   Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the    Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.
5).      Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6)        Create new data types.
6.1)      Right click on Data types and select New.
           Your Data Type is :DT_FILE
          In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
          Save the object.
6.2)      The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
          no need to create Data types. They are imported directly as Message types.
6.3)      To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
          Select the following.
6.3.1)    Category: XSD.
6.3.2)    Messages: From All Available Global Elements.
6.3.3)    File:
          Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7).      Create a new Message Type.
7.1)     In the left hand frame under Interface objects, right click on the Message types and select new.
7.2)     Give a suitable name to the Message type.(MT_ messagetype).
7.3)     For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
         Save it.
8).     Create a Message interface
8.1)    In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2).   The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
        Save it.
9) .    Create a graphical mapping between the target document and the sender .
9.1)    In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2)    As Source message select your own Idoc .You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- >     Namespace->Imported Objects.
9.3)    As Target Message you can choose your Message type .Choose Search for Integration Object.
9.4)    Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5)    Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
        Save It.
9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10).     Create an Interface Mapping.
10.1)   In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2)   Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose Search for Integration Object.
10.3)   Target interface:    Your Inbound Interface( The Target document interface).
        Then Select 'Read Interface' and Assign your 'Mapping Program' .
        Mapping Program: Your Message mapping.
        Then Save it.
11.)    Finally , in the left hand frame ,go to your change list and Activate it
           STEP 3: Directory
1)      From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
        Create a Scenario Object
2).     The First Step is to create a Scenario Object
        This will serve as container for all your configuration work. Create and save a scenario object
3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4)      In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) .    Create a Communication Channel.
6).     Expand your service and right click on Communication Channel. Name your Communication Channel
        Here we need to configure the adapter.
     Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
          For the Receiver, Specify the following Parameters
6.1       For the adapter type , use the F4 help and select FILE.
6.2       Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3       Specify the following parameters.
          Transport Protocol: File Transport Protocol.(FTP)
          Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
          Adapter Engine: Integration Server
          For the File system access Parameters, enter the following
          Source Directory:VILAS
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server: 172.25.7.116
          Port: 21(by default)
          Data Connection: Passive
          Connection security: None
          Connection Mode: Permanently
          Transfer Mode: Binary
6.5       For Processing Parameters, Specify the following
          File construction mode: Add Time Stamp
          File Type: Binary
6.6       For Content Conversion Parameters, Specify the Following
          RecordSet Structure:
          Adapter Status: Active
          The receiver file adapter is now configured. Save your Communication Channel.
           Create an Receiver Determination.
7).       From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1)      Select your sender service and interface.
          Sender:
          Party: blank
          Service: Sender service(Business system)
          Interface : Sender interface
7.2)      In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
            Create an Interface Determination.
7.3)       Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1)     In the Receiver Determination   you just created, have a look at the area Configuration Overview for Receiver Determination   at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2)     In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
           Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3)     You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
           After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5)     When you are done , Save the Interface determination object.
8.)         Create a Sender Agreement.
           In the left hand frame , right click on Sender Agreement ->New
8.1)       Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Outbound Interface
8.2)       In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.)         Create a Receiver Agreement.
           Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1)       Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2)       In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
           Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Inbound Interface
9.3)       In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
           Your Configuration is complete. Activate the objects.
PLZ REWARDS POINTS
VIKAS

Reg File to IDOC scenario with Acknowledgment

Hi Experts!
In a File to IDOC scenario , how to get the acknowledgment back to PI after posting the IDOC to SAP system and send the acknowledgment to the sender system.
What setting needs to be done in Sap and PI? Is it better if we have a BPM or is it good to have another interface to pass the acknowledgment IDOC back to the file sender.
Regards,
Srini

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

Reg:idoc to file scenario

q) In idoc to file scenario i used business service for sender R/3 system and maintained adapter-specific identifiers for it,can i use the business system or business service for receiver system and as it is a cross company environment?

Hi Srikanth,
you can use business system which is created for R3 system.There is no need to use the business service for R3.
can i use the business system or business service for receiver system and as it is a cross company environment?
As it is a cross company envirionment, might be you dont have created BS for u r receiver system in SLD. So it is better to use business service for receiver.
Hope it will gives the idea...
Cheers
Veera

Reg:Import Purchase Order Scenario

Hi All,
In the Import Purchase Order Scenario SVB load will come, which will display in MIRO after the PO creation
i have an requirement that in the MIGO transaction i just want to make the SVB load to 0,because if the SVB load comes it just adds to the inventory(i.e material cost which is wrong), could you please say how can i prevent the SVB load addition to the inventory or how can i make the SVB load to 0.

HI There,
Define a seperate condition type for SVB in M/06 make the condition category as delivery cost. Mantain this seperate condition type for SVB load value in PO, in pricing procedure for the SVB condition type mantain an account key. Then in OBYC for this account key mantain the GL account in which you want to record the debit SVB amount.
Now when you will do GR the SVB value will not get loaded in material.
Regards,
Sujoy

Reg:soap-xi-rfc scenario

In soap-xi-rfc scenario if the RFC function modules processed in R/3 system with some errors then , how to handle the errors , do we need to create the error structure in xi by using the fault message type or there is any other way to handle the application errors?
pls help with suitable answers
regards
chandrakanth.k

Hi,
The best way to go with ur senario is make it as SOAP XI Proxy.....in proxy u can catch the errors using the fault mesage typw and if u want to validate the data that can be done......if u want to send the error report that can be done in proxy....were u can collect all the errors and send they to the enduser or display them in Application server...
Think this option if possible....
check somelinks on fault mesage.
ExchangeFalultData & ExchangeLogData
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
Asynchronus RFC exception handling
XI Alerts are not getting triggered from proxy servers
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-
a258cf083bca
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Fault Message
Regards,
Phani
Edited by: phani kumar on Mar 12, 2008 1:05 PM

Reg RFC to JDBC scenario

Hi Techies,
This is inregard of RFC to JDBC Scenario.
Iam having an old RFC to JDBC scenarion which is working fine.
I want to call other BAPI programme using the same RFC connection.
I have changed BAPI and ABAP Programmes.
But Still in my integration builder, Still the RFC is calling the old stucture.
How flush the buffer and call the new structure using the same RFC.
Regards,
Kiran

But Still in my integration builder, Still the RFC is calling the old stucture.
what about the RFC structure that is imported in IR/ ESR....was it re-imported?

Reg Soap to Soap scenario

Hi...
I am doing soap to soap scenario. Can you please provide the details for doing the soap to soap scenario. I want to provide the input as soap request. Xi would take the soap request and process the request and provide the repsonse.
Pleasehelp out in doing the above scenario.

HI,
Invoke Webservices using SAPXI
sender Soap Adapter.
1) Create DT,MT,MI( Syncr,Outbound)
2)Configure ID
3Create Webservice (ID->Tools->Define Webservice , Save it as .wsdl)
Give that wsdl to the sender system
REceivere Soap Adapter
1) Need WSDl file from receiver system
2)mport Wsdl file from External definitions in IR
3) Create Message Interface ( Synch,Inbound)
4) Configure ID
ID :
Sender , Receiver adapter : Soap Adapter
Regards,
Jayasimha JAngam

Reg: IDOC to File Scenario Acknowledgments

Hi All,
I have created a Asynchronous IDOC to FILE Scenario. It is working perfectly fine, files are getting generated as expected and FTPed.
But I am receiveing Acknowledgments back to ECC system from PI. I dont want any acknowledgments back to ECC.
Please advice.
Thanks & Regards,
Navneeth K.

HI Navneeth,
Generally, you would not get any acknowledgement. Can u please explain abt the scenario? Have u done this woth BPM?
Thanks,

REG: SFTP to SFTP scenario

Similar Messages

Maybe you are looking for