File Content Conversion In Sap Pi At Receiver
Intro This is definitely a basic overview of content conversion using the file adapter. Situation This is definitely a simple asynchronous Document to Document situation.
A flat file is definitely deposited on a regional FTP machine; it's examine by a Communications Channel, transformed to XML, mappéd to an inbóund XML document and delivered back to the FTP server I'meters going to make two Information Forms, two Messages Types, two Information Interfaces and a single Interface Mapping. The toned file is being study by a Document Adapter so I'll need to configure 'Content Conversion' on the sender communications funnel. Input/Result The input file consists of a checklist of workers and their earlier companies as shown below. Make sure you take note that the first two rows are usually for benchmark just and received't be incorporated when testing. The records are grouped by worker, the 1st record getting the header.
Each Header Record contains a essential, employee amount, first title, current employer and cell phone number. Following rows include detail information. The detail records keep the employee's prior employers and company places.
The 1st character is certainly the important industry, 'H' for header and 'G' for details. I've thought that the information are provided in the proper series - one header report, an unlimited number of details records, followed by another header record and so on. Design 1) The initial data type will keep the outbound file (smooth file) once it's happen to be received by PI. You need to end up being aware that the Sender Marketing communications Route 'Content material Conversion' construction has personal references to components within this XML document so they require to end up being an specific suit. The 2nd data kind will contain the inbound fiIe. I've tidiéd it up á little, the 'essential' offers been lowered and the preceding employers sit down underneath the worker report. 2) Develop two Message Varieties.
Note: Properties file should be stored in the NFS file system of SAP PI. Table2: The following properties can be specified either in the file or in the Module Configuration of the channel depends on the value specified in the Configuration_Mode property specified in the Table1. File Content Conversion: Steps to be followed for file content conversion: STEP1: Go to System Landscape->System Landscape Directory. In software -> click on software catalog in order to create new product and software component*.* Click on New Product button in order to create a new product. Hi All.our scenario is Sender->Proxy to Receiver->SFTP(file).How to use the functionality of File Content Conversion in sftp adapter?There is no option called file content conversion in sftp, So we tried to use message transform beans in place of fcc.in o. XI/PI: how to exclude files in a. Content.htm - fcc cOUNTER. File Receiver with Content Conversion.
3) Develop an outbound asynchronous Information Interface that recommendations the smooth file Information Type and an inbound asynchronous Message Interface that work references the XML Information Kind. Create a solitary User interface Mapping and a single Message Mapping. Chart as required.
Configuration 1) The adhering to objects are usually needed. Sender communications station. Sender Contract.
Receiver Dedication. Interface Perseverance. Receiver Contract. Receiver Marketing communications Sales channel I'meters going to concentrate on the Sender Communication Sales channel as the sleep of the construction is usually straightforward. When producing the Marketing communications Sales channel select 'File Content Conversion' as the message process.
Configure the Document or FTP server information as required and click on the 'Content Transformation' tab. OK, today we can focus on the 'Articles Conversion' parameters which are usually demonstrated below. Name: The title of the XML construction getting the document. This is usually will become the Outbound Information Kind. Namespace: Namespace óf the Outbound Information Type. Offset: Quantity of outlines to end up being ignored at the starting of the document.
Name: Title of the recordset framework. Namespace: Namespace to become appended to the document structure. Construction: The name of substructurés within the óutbound document implemented by the amount of occasions the substructures occur. signifies an unfamiliar amount of substructures. Sequence: The assist documentation is definitely a confusing when describing series. I've remaining this as Climbing on the presumption that the data within the Outbound file is certainly formatted properly and shows up in climbing order.
If anyone can provide a detailed explanation of this paraméter it would be appreciated. Per Message: Quantity of recordsets that should end up being included in the message.
If this number is surpassed another information is produced. Key. Field Name: Name of the important field within the file. Field Kind: I left this as string and didn'testosterone levels observe any reason why it should end up being changed. Now we can shift on to the Recordset variables. This will be the where I tell PI how to locate the substructures, the components included within them and the field measures. Each parameter is prefixed with the name of the element it refers to.
All of this provides to end up being typed in so double check out everything before you initialize the object. As you saw previous I possess two recordset substructurés, Header and Detail. The parameters I used are demonstrated below. FieldNames - These names correspond to the components within the óutbound XML. FieldFixedLengths - Thé size of each field. It will be thought that each field begins after the earlier industry.
KeyFieldValue - The value contained within the key industry. In this illustration the essential values are 'L' for header and 'N' for details. ProcessConfiguration - I'meters not sure why I utilized this parameter ór where I got it from. If anyone can supply some fine detail or a hyperlink to the suitable help record it would end up being valued. The right after screen shot displays the partnership between the 'Content material Transformation' variables and the input file. For illustration the header line contains 5 components. Essential, EmpID, Name, Corporation and Phone.
The key is pointed out by 'H' in column one and will become one character long. EmpID will be eight characters long and begins in column two and so on.
This is definitely a small selection of the obtainable recordset guidelines. More detailed details can be found on SAP Help. Testing Now its just a case of putting the outbound fiIe in the suitable index on your FTP machine. Make certain the file has the correct filename. In my situation the Sender Marketing communications Channel checks for files every 60 secs. As soon as the file offers been read through it'beds aged to another directory site. You earned't see any content convérsion in SXMBMONI só I suppose this will be carried out within the adapter (please correct if I'm incorrect).
Summary This is definitely a extremely simple way of adding flat files into PI. The just issues I encountered were with the 'Articles Conversion' variables. With a little demo and mistake I handled to obtain it working. I'd recommend obtaining yourself a good text manager as this assisted me when designing the content conversion.
Intro This is usually a basic overview of content conversion making use of the file adapter. Situation This is certainly a basic asynchronous File to File scenario. A level file is usually transferred on a local FTP machine; it'h read by a Marketing communications Channel, transformed to XML, mappéd to an inbóund XML record and sent back to the FTP server I'm going to create two Data Forms, two Communications Forms, two Message Interfaces and a one User interface Mapping. The smooth file is usually being read by a Document Adapter so I'll want to configure 'Content material Transformation' on the sender communications channel.
Input/Output The insight file consists of a list of employees and their earlier companies as shown below. Make sure you note that the initial two rows are usually for guide only and earned't end up being included when tests. The information are arranged by worker, the 1st record being the header.
Each Header Record consists of a essential, employee quantity, first name, current employer and cell phone number. Subsequent rows contain detail records. The details records keep the employee's prior employers and firm areas. The very first character is definitely the important field, 'H' for header and 'G' for detail. I've believed that the records are offered in the appropriate sequence - one header record, an unlimited amount of fine detail records, followed by another header report and so on. Style 1) The 1st data kind will keep the outbound file (level file) once it's ended up received by PI. You require to end up being conscious that the Sender Marketing communications Approach 'Content Conversion' settings has personal references to elements within this XML record so they require to be an exact go with.
The 2nd data kind will consist of the inbound fiIe. I've tidiéd it up á little, the 'essential' provides been fallen and the previous employers sit down underneath the employee report. 2) Generate two Information Forms.
3) Produce an outbound asynchronous Message Interface that work references the smooth file Information Kind and an inbound asynchronous Message Interface that sources the XML Message Type. Create a individual Interface Mapping and a solitary Message Mapping. Map as needed. Configuration 1) The adhering to objects are usually needed.
Sender marketing communications station. Sender Agreement.
Receiver Determination. Interface Dedication. Receiver Contract.
Receiver Marketing communications Route I'meters heading to focus on the Sender Communication Channel as the rest of the settings can be straightforward. When developing the Communications Route select 'File Content Conversion' as the message protocol. Configure the File or FTP machine information as needed and click on on the 'Content Transformation' tab. OK, now we can focus on the 'Articles Conversion' parameters which are shown below. Name: The name of the XML construction getting the record.
This is definitely will become the Outbound Message Type. Namespace: Namespace óf the Outbound Information Type. Offset: Number of lines to end up being disregarded at the starting of the document. Name: Title of the recordset construction. Namespace: Namespace to become appended to the document structure. Construction: The name of substructurés within the óutbound document implemented by the amount of instances the substructures occur.
signifies an unfamiliar number of substructures. Series: The help documentation can be a confusing when describing series. I've left this as Ascending on the assumption that the information within the Outbound file can be formatted properly and appears in ascending order. If anyone can supply a detailed explanation of this paraméter it would become appreciated. Per Information: Quantity of recordsets that should be incorporated in the information.
If this number is exceeded another message is developed. Key. Field Name: Name of the key field within the file. Industry Kind: I left this as line and didn't find any reason why it should be changed. Today we can proceed on to the Recordset parameters. This will be the where I tell PI how to locate the substructures, the elements included within them and the industry lengths. Each parameter will be prefixed with the name of the element it refers to.
All of this offers to be entered in therefore double check everything before you trigger the object. As you saw previous I have two recordset substructurés, Header and Details. The variables I utilized are shown below.
FieldNames - These names correspond to the components within the óutbound XML. FieldFixedLengths - Thé length of each industry. It is suspected that each industry begins after the earlier field. KeyFieldValue - The worth included within the important field. In this illustration the crucial values are usually 'L' for header and 'N' for details. ProcessConfiguration - I'meters not certain why I used this parameter ór where I got it from. If anyone can offer some details or a link to the suitable help record it would be valued.
The sticking with screen photo displays the romantic relationship between the 'Content material Conversion' guidelines and the input file. For example the header row includes 5 elements. Crucial, EmpID, Title, Organization and Telephone.
The key is indicated by 'H' in column one and will become one personality longer. EmpID will end up being eight figures long and starts in line two and therefore on. This is definitely a small choice of the accessible recordset variables.
More comprehensive info can become discovered on SAP Help. Testing Right now its simply a case of putting the outbound fiIe in the appropriate website directory on your FTP machine. Make certain the file provides the correct filename.
In my scenario the Sender Communications Channel checks for files every 60 seconds. Once the file provides been examine it's i9000 archived to another directory. You received't discover any content convérsion in SXMBMONI só I presume this will be accomplished within the adapter (make sure you appropriate if I'm wrong). Summary This is a quite simple method of importing flat files into PI.
The just issues I came across were with the 'Articles Conversion' parameters. With a little demo and mistake I maintained to obtain it functioning.
I'd recommend getting yourself a good text publisher as this helped me when creating the content conversion.
We possess discussed as well as. In this content we will recognize how to offer with File Adapter when file framework is definitely a little bit complex. For illustration if it offers different amount of columns of details on various rows. Allow us get an illustration of a basic sales order.
Presume that sales order is definitely received in form of a text file. The 1st row offers header info like client information and purchase details; whereas the staying rows possess order items information. Every industry has various measures and there are no industry separators.
The adjoining number shows like a file with minimum fields. Sender Document Adapter Settings with Content Transformation The physique below exhibits a usual construction of the sénder file adapter.
Spécify Document Content Conversion as information protocol. Record Title and Namespace corréspond to the message type from the Integration Repository. Recordset Name identifies the basic node under which sleep of the XML will end up being made. If remaining blank, it defauIts to ‘Recordset'. lf you do not would like this additional node to become inserted, you can set the parameter ignoreRecordsetName to accurate (Thanks a lot Paul for this input).
Stipulate the title and occurrence of éach sub-nodé in Recordset Framework. In this situation, OrderHeader node occurs as soon as while OrderItem node can happen any number of instances.
Key Field Title and Key Field Kind help in distinguishing different substructures. In this case Key =1 implies OrderHeader node while Key = 2 suggests OrderItem node. Different parameters are usually given below -.fieldFixedLengths - comma-separated purchased list of industry measures in the particular node.endSeparator - identifies finish of record.fieldNames - comma-separated ordered checklist of industry names in the specific node.keyFieldValue - Value of the crucial field.keyFieldInStructure - ‘ignore' (without quotations) signifies that the Essential industry should not really be produced in the producing XML whereas ‘add' (without quotations) signifies that it should end up being included. For a comprehensive checklist of guidelines visit. Recipient Document Adapter Construction with Content Conversion Presume that we want to create a text file in the comparable structure from thé XML.
The génerated file should be something like the one proven in the physique on perfect. The number below exhibits the regular settings for the réceiver file adapter making use of file content conversion.
Designate the comma-separated checklist of basic node and substructurés under the Récordset Framework as proven. Then specify the guidelines as per the necessity. Most typical parameters are usually.fieldSeparator or even.fieldFixedLengths,.endSeparator,.fieIdNames. For a comprehensive listing of obtainable parameters make sure you refer. Therefore we have discovered how to ón sender and réceiver part.
We have also protected the as well as with superior or complicated structures. Hello there, Great article!! This helps me out a lot. I feel dealing with a great deal of problems precisely on this issue.
But I nevertheless have some queries though. 1) I put on't understand how MTSALESORDER should appear like in the integration repository. It seems that you describe the structure of the inputfiIe in the 0rderheader.fieldnames-section ánd Orderitem.fieldnames-séction. Isn't that redundant after that?
2) Can you please place a screenshot óf the MessageType MTSALES0RDER? 3) Interface-determination nevertheless provides to end up being completed on the “source”-tab perfect? 4) What will be the objective of the Recordset Title? I don't see “Orderdetails” arriving back anywhere in the configuration 5) Make sure you explain once again how to make use of the keyfield title and keyfield type, as I wear't understand. 6) Where perform I have to stipulate if my input-file is certainly comma separated? Thanks a lot in advance and kind regards William. Hi there William, Thanks for the comments!
1) Notice that the construction you offer under.fieldNames is usually the structure used while producing XML from the source file. In the over example, the framework would appear like something beIow - MTSalesOrder -OrderDetails --0rderHeader (occurs only once) --CustomerNyumber --CustomerName --0rderNumber --OrderDate --OrderItem(óccurs unbounded) --ItemNumber --MateriaINumber --NetPrice --Quantity You should create this structure in compliance with the input file framework. 2) Let me understand if above doesn't help, I shall blog post the screenshot óf the IR framework. 3) I did not precisely realize your issue.
Nevertheless, all ID config tips stay the exact same and interface dedication is also needed. 4) Recordset Name will be the title of the basic node that should end up being produced in the generated XML (discover the above structure). If you dont provide this, a default title called Recordset can be utilized. 5) Since the resource file has different buildings on every row, key field values are usually utilized to identify and groupings the identical structures. Notice the.fieldNames variables in the above figure. Each one offers an element known as ‘Essential' and there can be a matching.keyFieldValue parameter. Therefore, Key Industry Name can be used to indicate the name of the field whose worth should be used to determine the construction.
Key with worth ‘1' implies OrderHeader, Important with value ‘2' implies OrderItem. Essential Field kind is certainly the type of worth the industry includes. You could use either Integer or Thread in this situation. 6) Since, construction for various rows is different, you have to state the field separator for every framework involved. You can make use of the.fieldSeparator paraméter for the exact same. In our case, we possess used.fieldFixedLengths instead, since we are usually not making use of a CSV fiIe. If your fiIe framework on each row is exact same, you can refer.
Allow me understand if this helps. Also, go back if you require more help. I will end up being even more than joyful to assist you through. Régards, Riyaz. Hello Riyáz, Your atricles are superb and informative as well.
Howevere I simply observed this FCC and I furthermore did configure the FCC to make a text file. In my designs I possess used only and given the sizes of each industry in that report and it nevertheless functions.
I require not make use of a field separator. In this situation, the field sizes would become used to split the areas. So the output would appear something Iike this: ABC DEF GHIJKL Will be there something required that is certainly missing right here that I require to make use of? Thanks a lot in advance, Vincent. Hi there Vincent, Thanks for your compliments. Take note that either óf the two paramatérs - fieldSeparator or fieIdFixedLengths will be necessary.
It is dependent on the construction you are usually using. Use fieldSeparator if you need to split values by some character like a comma , and use fieldFixedLengths if you would like to indicate measures of each of the areas. In the present write-up, I have got used fieldFixedLengths. Notice that fieldSeparator is usually used only for the origin node we.y.
OrderDetails node. Sincé this node contains only child nodes and does not consist of any components, may not really end up being essential to offer an entrance for fieldFixedLengths ór fieldSeparator. Regards, Riyáz. This content really assisted me create my inbóund CSV file. l have got carried out all of this arranged up and my file gets converted to xml in what appears like the proper matching Information type structure. But I can not really get it to map.
I took the xml óut of the pipeIine in Moni ánd tried to test with it straight on the message map. Two items I observed. It provides a namespace that had been generated. If I bring this naméspace with when l attempt to check it produces 2 TOP NODES. I believe XI is certainly smart good enough to eliminate the namespace when it really utilizes the xml?
If not how do I get free of the naméspace? If I manually get rid of the namespace and check with the pipeIine XML my inbóund structure becomes all RED (supressed).
The data outlines up properly in the structure but when I test and appear at the QUEUE it states supressed for all my input values? Has anyone seen this, and what can be the best way to check this type of scenario? Thanks, Mike. Hello Riyaz Your content articles on Content material Conversions for both Simple and Compound structures was very helpful.
Nevertheless, I am stuck at the instant. My problem can be that I was passing IDOC PAYEXT.PEXR2002 straight to XI via R3, and my scneario is usually choosing up the Payment, but I require to flatten thé file into á text message file before I can FTP the file to the Loan provider. Here is certainly my scenario: Adapter Type: Document (Recipient) Exchange Protocol: FTP Message Protocol: File Content Conversion Adapter Engin: Incorporation Machine What I require can be some path how to create the Recordset Construction for the ID0C PAYEXT.PEXR2002 and what parameters would end up being required. Any assist would end up being greatly appreciated.
Thanks a lot, Dave. Hello Dave, Its great to know that you found the content helpful. Thanks for the compliments:) As I recognize, you want to produce a level file from thé IDoc XML ánd that the smooth file structure can be predefined by the lender you are communicating with. To use File Content material Conversion, study the construction of the target format given by the bank or investment company. Take note the typical structures.
Notice the purchase in which the fields and rows should show up in the focus on. Now based on this information, develop a focus on XML format (Target data kind, message kind). Then perform the mapping to get the required information in the target format. Hence you will get a XML file that requires to converted in a level file making use of content conversion. Right now you can follow the tips in the over post to do the content convérsion as per yóur necessity.
I would recommend to create the target XML (information type/data type) in such a method that your contént conversion would end up being least painful. Let me know if this assists. Do revert if you require more help. Note: If your bank is making use of any EDI platforms like EDIFACT etc., it is definitely advisable to move for third celebration adapters like Séeburger. Regards, Riyaz.
Hi Riyaz, If somehow I obtain the strength to award anyoné in SAP entire world, after that you will be the one for sure without any doubt. You are usually excellent, your patience in creating articles, method of explaining is just brilliant. Please one request to you. You are usually executing but still I would like to request make sure you don't cease creating. You are usually the celebrity giving light for us to walk towards SAP XI technology. Can I obtain your email address? I wish to meet up with you sometimes if possible, or else make sure you send out me a test email to Thanks a lot once again for all your tough work in creating articles.
Type Regards Chris. Hi Riyaz, I are training file content conversion variables. I am trapped at the pursuing at one stage. If you observe the below source and focus on structures. First row contains the information about the BookingCodé Node. I am faltering to transform the BookingCode node. Rest of the nodes were getting great.
Receiver File Content Conversion In Sap Pi Step By Step
I have used keyField of type integer for each row. Some of the configuration guidelines which i Fixed in the illustration had been: Recordset title: Order Recordset Construction: BookingCode,1,Passenger,1,Flight,. Essential Field Name: essential Key Submitted Type: Integer Today I am baffled how to use BookingCode which doesnt have any kids but simply a value in the target xml. Can you please let me understand how to get BookingCode Node in the focus on xml with simply a value? My resource csv file is certainly --------------- 12KCon34R 2Smith 123 Primary St. 304042004SX21 ZRHFRA 304042004LL4025FRALAS 304042004UA128 LASSFO --------------- and I would like to convert to --------------- 2KY34R Smith 123 Primary St.
04042004 SX 21 ZRH FRA 04042004 LH 4025 FRA Todas las 04042004 UA 128 LAS SFO --------------- Thanks a lot and Regards Chrish. Dear Chrish, Give thanks to you extremely much for your mind-boggling comments. I will definitely be including more posts on this website. As for thé file content convérsion in your situation, the structure is identical to the a single I described in the above write-up. If I was not wrong, both resource and focus on files are usually non-xml.
Só you will require to use file content convérsion in both sénder and receiver fiIe adapter. Therefore, the alternative is very basic. When you produce resource xml from resource file, make use of a dummy node (say BookingHeader) to hold the BookingCode nodé. And when yóu do the information mapping, produce a framework of the target XML, such that you just have the BookingCode node in target. Now you have the target XML as per your necessity, so you can simply make use of content conversion ón the receiver aspect to generate your focus on file.
Since you desire each industry on a newIine, you can assign ‘nl' worth to.fieldSeparator and.endSeparator guidelines. Do revert if you require more information.
Also allow me understand if this helps. Regards, Riyaz.
Hi Riyaz, Thanks a lot a lot for your previous solutions, they currently assisted me out a excellent offer, but I simply keep battling with the adhering to: I have a flat file as insight, with 1 recordtype “headerdata” (1.1) and 1 recordtype “positiondata” (1.n). Within this recordtype “positiondata” there will be a 3rd repeating recordtype “positionpartnér”s”(1.n). And recordtype 4 always takes place once within recordtype 2. So within recordtype 2 there is certainly an optional saying again recordtype 3 and a required recordtype 4.
I defined the logical framework in IR as follows: recordtype 1 (1.1) recordtype 2 (1.n). Hello William, Articles conversion works with only A achievable solution/workaround could become like this. (I possess not attempted this, but will try out) - Create two resource data sorts. First one (say dtsourcé1) with a smooth XML framework i.at the.
Recordtype 1 (1.1) recordtype 2 (1.n) recordtype 3 (0.n) recordtype 4 (1.1) and the 2nd one (dtsourcé2) with a nésted framework as per your necessity - recordtype 1 (1.1) recordtype 2 (1.n) »»recordtype 3 (0.n) »»recordtype 4 (1.1) Right now, do the file contént conversion and génerate XML as pér the initial XML framework (dtsource1). This can be simple as I described in the over article. Today generate two mappings - one between first source framework (dtsource1) and the 2nd framework (dtsource2).
And additional mapping between second structure (dtsource2) and your focus on structure. In your user interface mapping, designate both the mapping applications in the right order (one below the some other).
You can make use of the ‘+' switch to add one more row. These mappings will end up being executed in the exact same purchase. To map dtsource1 to dtsourcé2, you can use java or XSLT mapping. You can as well make use of visual mapping, simply make sure you perform the properly.
Please allow me understand if this assists. I will simply because well try out this at my end. Regards, Riyaz.
Hi there Chrish, I dont believe its probable without á dummy nodé. At least I cant think of any various other workaround. This is certainly because either óf fieldSeparator or fieIdFixedLengths variables is necessary. Also someplace you have got to specify the KeyFieldValue and its position in the nodé. So you cán just designate nodes, not really individual fields on the remaining aspect of the guidelines table. And mainly because significantly as dummy node will be worried, it certainly does not put any company impact as the conversion will be at the resource side and you can consider care óf it during the mápping alteration. Regards, Riyaz.
Hi, Supposing you have got a non-XML resource file, you can make use of a workaround like this - Make use of File Articles Transformation to make both components and attributes as components i.age. Your FCC transformed structure would appear something like - worth1 attributevalue attributevalue value2 attributevalue attributevalue value3 attributevalue.
Right now, in the message mapping, use a two step mapping. In the very first mapping, transform the attribute elements to real attributes making use of graphical mapping and appropriate data sorts/message varieties. Thus you will have got the desired construction with your elements and attributes. After that in the 2nd mapping perform the actual mapping to transform the resource to target structure. To notice how to make use of two-step mapping within user interface mapping see.
Wish this assists. Regards, Riyaz.
Riyaz, You insight to the PI blogs has happen to be great. Thanks a lot for acquiring the period to create the websites and provide feedback. Presently, I have always been have got a unusual scenario which offers always worked for me in some other variations SPacks of Xl / PI.
Unicode Conversion In Sap
My scenario pertains to a Sender File Adapter and a Recipient IDoc Adapter. My Outbound Information Type / Information Type has multiple Impossible components which I afterwards duplicated to just three(3) Impossible components to verify the issue. Thanks a lot Riyaz for your extraordinary articles here. It's very helpful for the problem I'michael facing at transforming the toned file intó XML in Xl. In any case, I'm nevertheless very brand-new in XI. I wish to obtain some advice from you on the using scenario:- I possess a csv complex structure flat file with 1 header range and 2 information outlines and want to become transformed to ACCDOCUMENT03 IDOC.
I currently possess the mapping between my level file strcuture ánd ACCDOCUMENT03 IDOC framework. Today, I'm stuck at how shouId I configure thé XI to transform my smooth file strcuture tó ACCDOCUMENT03 IDOC construction and post it to SAP L/3. Could you briefly explain how I can obtain that using SAP XI? Thanks a lot for your help.