Idoc to idoc scenario with idoc tunneling

IN idoc to idoc scenario with idoc tunneling the XML_CONVERSION parameter to value 2 is set whish means An IDoc is converted to IDoc-XML if requested by the service
I want to know where we specify this and how we specify?

1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
ref these weblogs.
It is given under;
TCODE - SXMB_ADM
- Integration Engine configuration
- set the XML_CONVERSION parameter to value 2

Similar Messages

IDoc-to-File scenario with external Partner ... PCK necessary?

Hi all,
I have a question concerning to a IDoc-to-File Scenario with an external Partner. Here is a short Description of the Scenario:
The SAP ERP System creates an IDoc which should be send to the SAP Integration Server. The Integration Server respectively the IDoc-Adapter transform the IDoc in IDoc-XML. The Integration Server executes a Mapping and so on. In the final step the Integration Server should send the XML-File to a FTP Server in New York (external Partner) with the File/FTP-Adapter.
Have I to install the Partner Connectivity Kit at a Server in New York or is it working without the PCK? Which are my possibilities?
Thanks for your help
with kind regards
Christopher

Hello,
If the FTP server has connectivity to XI and if the
port is open XI can directly do the FTP using File
Adapter.
Thanks,
Himadri
Hi,
thanks for your quick answer.
What means "connectivity to XI"? Our SAP-Environment is in Germany and the FTP-Server is in New York. Is it enough to open the port in the firewall?
Thanks for your answer
Christopher Kühn

IDOC to FILE scenario With Screen shots

CAN YOU PLEASE SEND US THE DETAILS OF IDOC to FILE scenario With Screen shots and do the needful for me

Hi Surya,
I thought i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this helps.
Regards,
Abhy Thomas

IDOC to File scenario with multiple directories on same FTP.

The scenario is IDOC -- to FTP (Receiver file adapter). Based on the condition in the sender IDOC say if EIDKA01-BSART = Y than the directory path on FTP server is 'A' ELSE 'B'.
There is only one reciever service defined for the FTP server in the Integration Directory. Its not multiple receiver scenario.
How do we do this?
Thanks

Hi !
Just create an UDF in graphical mapping and put this code inside:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
//get Key of Directory
DynamicConfigurationKey keyD = DynamicConfigurationKey.create( URLFile, "Directory");
//Replace value of Directory
conf.put(keyD,dir);
where "dir" contains the destination path depending on the EIDKA01-BSART value. When this code executes, if the receiver file adapter has the adapter-specific attributes (directory) checked, then it will set the "directory" value to the one specified in the "dir" variable.
Regards,
Matias

Idoc to proxy scenario with an acknowledgment

Hi ;
I have to implement a IDoc to abapProxy scenario but an application acknowledgment must be return so IDOC status will be set.
How can i understand whether an application error exists while abapProxy is executing or not in status of IDOC?
Do I need to create and sent back new IDOC to the sender system in abapProxy code?
Thanks.

Hi,
See if you just want the ack for your IDOC coming from r/3 to XI, then you can use ALEAUD01 IDOC and you can configure it by running report IDX_NOALE in XI system..........
But if you want status change for appl error occuring in ABAP proxy system, then i think you will have to use a BPM for it.........you will have a recive step for getting your IDOC, then a transforamtion step for IDOC to proxy mapping, then a synch send step for sending proxy req and getting proxy response, then a transformaton step for mapping the proxy response to SYSTAT01 IDOC in r/3 for changing the IDOC status depending on success or error for your proxy response, then a send step to send this IDOC to r/3 system...............keep teh IDOC number in proxy req and proxy response so that you can use it in SYSTAT01 IDOC for sending it to r/3 and changing your IDOC status.
Regards,
Rajeev Gupta

Idoc to file scenario - collect idocs

Hi experts,
I need help regarding collecting the idocs as per the reciver id available in idoc.
After collecting these idocs at XI, the data of all idocs should be transferred in one text file.
How I can do this ?
Give me complete solution with example scenario ?
Please do not give any example in standards scenarios as given in SAP BASIS Patterns.
Regards,
Study SAP

Hi,
Plz do refer the following links:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm - collecting IDocs without BPM
/people/daniel.graversen/blog/2006/09/07/using-a-bpm-to-collect-messages-for-a-set-interval-of-time
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b
Also this link,
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Regards,
Vinod.
Edited by: Vinod Reddy on Jun 26, 2008 9:23 AM

Character Encoding for IDOC to JMS scenario with foreign characters

Dear Experts,
The scenario is desribed as follows:
Issue Description:
There is an IDOC which is created after extracting data from different countries (but only one country at a time). So, for instance first time the data is picked in Greek and Latin and corresponding IDOC is created and sent to PI, the next time plain English and sent to PI and next Chinese and so on. As of now every time this IDOC reaches PI ,it comes with UTF-8 character encoding as seen in the IDOC XML.
I am converting this IDOC XML into single string flat file (currently taking the default encoding UTF-8) and sending it to receiver JMS Queue (MQ Series). Now when this data is picked up from the end recepient from the corresponding queue in MQ Series, they see ? wherever there is a Greek/latin characters (may be because that should be having a different encoding like ISO-8859_7). This is causing issues at their end.
My Understanding
SAP system should trigger the IDOC with the right code page i.e if the IDOC is sent with Greek/Latin code page should be ISO-8859_7, if this same IDOC is sent with Chinese characters the corresponding code page else UTF-8 or default code page.
Once this is sent correctly from SAP, Java Mapping should have to use the correct code page when righting the bytes to outputstream and then we would also need to set the right code page as JMS Header before putting the message in the JMS queue so that receiver can interpret it.
Queries:
1. Is my approach for the scenario correct, if not please guide me to the right approach.
2. Does SAP support different code page being picked for the same IDOC based on different data set. If so how is it achieved.
3. What is the JMS Header property to set the right code page. I think there should be some JMS Header defined by MQ Series for Character Encoding which I should be setting correctly) I find that there is a property to set the CCSID in JMS Receiver Adapter but that only refers to Non-ASCII names and doesn't refer to the payload content.
I would appreciate if anybody can give me pointers on how to resolve this issue.
Thanks,
Pratik

Hi Pratik,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
This link might help.
regards
Anupam

B2B scenario with IDocs, sender system not in SLD

Hello all
When sending a purchase order IDoc (ORDERS05) out of SAP ECC 6.0 I get the following error in SM58:
No service for system SAPPEE, client 200 in Integr ation Directory
Message no. SR053
Until now I did not register the SAP ECC 6.0 system in the SLD. Is this absolutely mandatory?
The RFC-Destinations work like a charm, the user (type C) and authorizations (for now SAP_ALL) should be ok (same settings in XI and SAP ECC system).
In the integration directory I defined a partner "IDOC_SENDER" with the following identifiers:
Agency = http://sap.com/xi/XI
Scheme = XIParty
Name = IDOC_SENDER
Agency = PEE_200 (SID with client from customers system)
Scheme = ALE#LI#LF
Name = 0000601140 (this is the vendor id from customers point of view)
Agency = AEE_200 (SID with client from vendors system)
Scheme = ALE#KU
Name = 0000001011 (this is the customer id from vendors point of view)
Within this partner "IDOC_SENDER" I defined a business service "Order" and assigned ORDERS.ORDERS05 as allowed outbound-interfaces.
Within this business service "Order" I defined a sender communication channel "Order_send_IDOC" with adapter type IDoc.
Based on this I created a receiver determination, interface determination, etc.
I also configured things in IDX1, IDX2. The metadata (structure info of idoc type ORDERS05) was successfully loaded.
Did I miss something? What to do to eliminate this error:
No service for system SAPPEE, client 200 in Integr ation Directory
Message no. SR053
Any help would be greatly appreciated!
Thanks in advance
Renaud

I think there are some mis-configurations:
defined a business service "Order" and assigned ORDERS.ORDERS05 as allowed outbound-interfaces.
You do not define a business service when IDOC/ RFC/ PROXY is sender/ receiver
It should be Business System and it has to be defined in SLD and then imported in ID. (search on SDN for How to create Business System )
defined a sender communication channel "Order_send_IDOC" with adapter type IDoc.
You do not create Sender channel when IDOC/ PROXY is sender.
I would suggest that you follow steps mentioned in this wiki: http://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
Regards,
Abhishek.

IDOC Serialization & Synchronous Scenarios with AAE

Hi Folks,
I have queries reg Advanced Adapter Engine (AAE):
1) Can we do the Synchronous scenarios through AAE.
2) How can i do the IDOC serialization. How AAE helps in that.
Am using PI 7.3 ...Can you please mention the possibilites for the above queries.
Thank you!!
Regards,
Sekhar

MDM Learn wrote:
Hi Folks,
>
> I have queries reg Advanced Adapter Engine (AAE):
>
> 1) Can we do the Synchronous scenarios through AAE.
Already supported as part of 7.1 / 7.11 so dont see any problem here
>
> 2) How can i do the IDOC serialization. How AAE helps in that.
>
> Am using PI 7.3 ...Can you please mention the possibilites for the above queries.
>
> Thank you!!
>
> Regards,
> Sekhar
the above should be very much supported if you are using the Java IDoc adapter. For serialization use qRFC in SAP partner profile

How can we do the Testing in Idoc to File Scenario( With out using We19)

Hi All,
As all we know we can generate the Idocs from SAP R/3 to XI using the change Pointers,this we will apply in Production time.
But as of now in the Test system we can'd do it daily.
So we have already created materials in the SAP R/3 system.
I want to send the Idoc to XI by selecting some n number of materials.means i want to generate the Idoc for materials.this is like i have to do repeatedly for testing purpose.
Is there any T-code
How can we do this
Regards

Hi Vamsi,
   For the Message Type ORDERS you can configure Output Type (txn NACE) for IDoc generations and then you can trigger the IDoc using transaction WE15.
Selection Parameter will be as follows
Output application: This will be from Output Type
Object key          : Order Number
Output type         : Output Type name, that you configured
Transmission medium : A
Check the checkbox "Send Again".
Thanks,
Punit

Doubt in idoc 2 file scenario

Hi,
I want to create idoc 2 file scenario with out any Transformation.
In that case how/what to create Data type for receiver.
I want to receive the same idoc in the receiver folder/Directory (like XML file) with out any transformation.
Thanks
Ruban

Hi,
For this scenario you need to create the Data type structures as similar to IDOC type and just have to transfer to file without FCC.
It will transfer the IDOC data as it is in XML format
refer
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
(Just avoid using FCC conversions on receiver file adapter in above scenarios)
Thanks
Swarup
Edited by: Swarup Sawant on Mar 24, 2008 6:15 PM

Real time idoc to file scenario - URGENT!

Hi all,
I have a real time idoc to file scenario with the idoc structure as below:
WP_PLU03
   IDOC
     Begin
     EDI_DC40
     E1WPA01
        E1WPA02
Now as can be seen, EDI_DC40 is the header record common for the eniter idoc. But the segment E1WPA01 will repeat for each item sent from R/3. E1WPA01 in turn has many segments within it whcih corresponds to that one item.
Now the problem i am facing is, I did the mapping for all required fields from E1WPA01 to my file structure and it works fine if i send one 1 instance of E1WPA01. But when i send multiple instance of E1WPA01 for each item, my result in teh file should be 1 line of record for each E1WPA01. But this doesnt happen. It takes allE1WPA01 as 1 and gives only one record in the file.
How can this be overcome? this is a very common requirments? did i miss anything in the configuration?
Thnaks,
Yash

Hi Matias,
I have two instances (may be much more than 2) of the same segment in the idoc (E1WPA01) and each instance should create a new root in the target message structure as in the link below
Link: [http://img299.imageshack.us/my.php?image=image3ct6.png]
I have mapped the segment E1WPA01 with the root like this:
Link: [http://img176.imageshack.us/my.php?image=image2of6.png]
Hence it creates 1 root for each segment. But for complex mappings such as:
Link: [http://img337.imageshack.us/my.php?image=image1yu1.png]
the 2 input parameter to the UDF - KONDART and KONDWERT - the queue can be seen. the problem which i m facing here is in this queue, values from both the instnace of the segment E1WPA01 is taken together where each instance should be processed seperately. The first 4 values in the top queue(till VKP0) belongs to the filed KONDART of the 1st isntance of the segment and the 1st 4 values of the below queue (till 17) belongs to the field KONDWERT. Similarly the remaining belogns to the other segment. My logic in UDF is built taking only one instance at a time. Is there anyway i can distinguish between the two instance within my UDF?
I hope u understand my problem here.
Thanks,
Yash

Replacing IDoc - IDoc with IDoc - Proxy

Hi every one,
I have an IDoc - IDoc integration scenario between 4.5B and ECC 6.0 systems. The Idoc in the receiver system is not directly posted but an User - Exit is called and every thing is working fine.
I thought of experimenting replacing the scenario with Idoc - Proxy, and the source being 4.5B and target ECC. The User-Exit stuff as told above will taken care while implementing proxy.
Approach:
I create an inbound interface object in IR and use the Idoc as the message type and generate a server proxy using SPROXY in the ABAP stack of XI.
Please correct me. Also notify me if there are any potentials problems.
Regards,
-Naveen.

Hi,
SPROXY on the ECC system should be used to generate the ABAP proxy, not the XI system. Therefore, configurations will be required on the ECC system to point to the XI system in order to retrieve the interfaces to generate the ABAP proxy.
Also, it might be easier to create a simpler message type to use in the interface. IDOC has a quite complex structure and probably contains a lot of elements which will not be used by your proxy. The proxy interface should be as simple as possible to simplify your program development.
Regards,
Bill

IDOC to FILE Scenario-Error in defining Adapter specific Identfier

Hi All,
I am configuring IDOC to FILE scenario where IDOC will be send from ECC to PI System.I did following configuration
I created RFC,PORT,LS and Partner Profile on R/3 System. I had maintained SLD and IR. In ID I created Configuration scenario and business system.When I click on menu->Adapter specific Identfier where I want to specify IDOC Adapter and RFC Adapter. But it is not allowing to edit it is not editable. As we provide LOGICAL SYSTEM,sender system ID and client number of the sender system.

Hi Kavi,
I assume you correctly filled the Logical System of your Business System in the SLD...
Then in Integration Direction, use menu "SLD clear cache".
Always in Integration Direction, open your Business System, go to menu "adapter specific identifier", and... close to button "close", you should have another button like something ''check'' or "compare to SLD' or ''retreive SDL data'' (I have not an openned PI to check the right term). Use this button to get value stored in SLD to this local definition.
Mickael

Problem IDOC to File scenario: No service for system SAPIDC, clnt in ID

in IDOC to File scenario, when IDOCis triggered from R/3 to XI, it gives error in SM58 transaction
"No service for system SAPIDC, client 800 in Integration Directory"

In a scenario, i have a BPM which has a transformation step which contains a mutimapping ...means 2 messages mapped to 1 messgaes, here in the mapping i m using an UDF and written code to extract the file name from dynamic configuration.....
the problem is ...the same BPM contains another transformation step which contains a message mapping (which is not multi mapping), and here the code (UDF) works to fetch the file name...
the code is all correct....and it looks like
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String sourceFileName = conf.get(key);
if (sourceFileName == null ){
sourceFileName = "ErrorFile.xml";}
return sourceFileName;

Idoc to idoc scenario with idoc tunneling

Similar Messages

Maybe you are looking for