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

Similar Messages

How to do idoc to proxy scenario

Hi There,
As per requirement i am doing IDOC TO PROXY scenario. Can any one Pls help me how to do this configuration briefly.
with regards,
Naresh.K

Hi,
This is a Server Proxy Scenario.
To trigger the IDoc maintain necessary configuraions in R/3 and XI like.
1) RFC Destination (SM59) [XI & R/3]
2) Create Port (IDX1) [XI]
3) Load Meta Data for IDOC (IDX2) [XI]
3) Create Partner Profile (WE20) [R/3]
2) Create Port (We21) [R/3]
Also go thru this blog....<a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
There is no need to create sender IDoc communication channel and Sender Aggrement...
Go thru this blog for creating <a href="/people/siva.maranani/blog/2005/04/03/abap-server-proxies Server Proxies</a> by Siva Maranani
Regards
Santhosh
Remember to set the thread to solved when you have received a solution
[url=Use a Good Subject Line, One Question Per Posting - Award Points; Use a Good Subject Line, One Question Per Posting - Award Points[/url]

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

Mail to Proxy scenario with attachment. AF channel error.

Hi,
We are running SAP PI 7.1. I am experiencing the following problem in a Sender Mail adapter.(POP3).Mail to Proxy Scenario.
I have configured a sender mail adapter channel as POP3. This channel is configured to use the Mail Package and to Keep attachments. When I send a mail with an attachment to the mailbox that is being monitored by this channel, then the channel collects it from the mailbox.
In channel monitoring it indicates that the message was successfully delivered. However when I click on the message ID the view the audit Log it gives an error: u201CTransmitting the message to endpoint http://HOSTNAME:8101/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.u201D The message never arrives at the integration sever to be view in sxmb_moni.
Also when I sent a message without an attachment the message does go through. Or if I send a message with a text attachment the the message goes through, but not the attachment.
Any help would be most welcome.
Regards
Willie Hugo

Hi Willem,
I'm coming back to your original problem: "com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.u201D
Actually I had the same problem here and found a solution for it. In this case it was a file to Proxy scenario. The file send was large. After structure conversion the file size was more then 100 MB as indicated in the Audit Log of the message "2009-03-02 09:27:06 Information Send binary file "<File_Name>" from ftp server "<ftpuser>", size 106706248 bytes with QoS EO.
The ICM restricts all HTTP requests larger then 102 MB via the parameter icm/HTTP/max_request_size_KB which has a default value of 102400 (100 MB). Therefore it rejects the requests and your error is thrown.
There are two ways of avoiding this:
1) Increase the parameter:
Increasing the parameter implies a risk since large messages can overload the system (e.g. during the mapping). Therefore it is good to have these safety measurement in place.
2) Split the request:
Depending on the scenario it might be possible to split the request to restrict the max. number of records for a given file. This is the prefered option because it ensures better stability of the system and also better performance.
I think this situation applies to you as well - but I'm not sure since you did not specify the request size and the size of the attachement.
Best regards,
Mike

Mail to proxy scenario with condition

Hi Experts,
I am using mail to proxy scenario.
The mail box is having differnt files suppose:
BOOKING_REF_DELIVERYNO_WB.pdf
BOOKING_REF_SALESORDER_WB.PDF
BOOKING_REF_CUSDECNO_WB.PDF
DELIVERYNO_WB.pdf
SALESORDER_WB.PDF
CUSDECNO_WB.PDF
BOOKING_REF_WB.pdf
BOOKING_REF_DELIVERYNO_BOLCOPY.PDF
BOOKING_REF_SALESORDER_BOLCOPY.PDF
BOOKING_REF_CUSDECNO_BOLCOPY.PDF
BOOKING_REF_BOLCOPY.PDF
DELIEVERYNO_BOLCOPY.PDF
CUSDECNO_BOLCOPY.PDF
SALESORDER_BOLCOPY.PDF
BOOKING_REF_AWB.PDF*
DELIVERYNO_AWB.PDF
SALESORDER_AWB.PDF
CUSDECNO_AWB.PDF
Depending upon the file name in the mail box, the file needs to be attached via proxy with particular code:(x for case 1, y for case 2 , z for case 3)..for attachment abap code wrtiiten for proxy.
how to compare the file name from the mail?
DO i need to write a UDF..mapped with filename field of the sender XSD?How to do that?
Please suggest.
Thanks,
Sushama

You can use the other UDF
public String Get_Input_File_Name(Container container) throws StreamTransformationException
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);
return SourceFileName;
the previous one was for XI 3.0 , may be some differnt requiement I am not sure.
http://help.sap.com/saphelp_nw04/helpdata/en/43/03612cdecc6e76e10000000a422035/content.htm
regards
Ninad

Idoc to Proxy Scenario

Hi,
I am working on a Idoc (ECC) to proxy (SRM) scenario , I am triggering the Idoc message from RWB, when I am trying so, message is getting pushed and it shows a success message in PI Moni. But it failes in the SRM system and the error message is as follows, Please provide me with some inputs. Also the Idoc message is not directly getting posted from ECC system.
Note: Logical system already exists in PI, ECC and also in SRM systems, Let me know should I check anything else.
Error Message:
==================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""><SAP:Category>XIProxy</SAP:Category><SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code><SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1><SAP:P2>CL_BBPX_TRADING_PARTNER_SUS_IN</SAP:P2><SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Error during proxy processing
An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause
Application Error
</SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
Trace message is:
============================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">Work Process ID: 782464</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="1" type="T">system-ID = SND</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2011-05-28T04:49:46Z CET </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = F506D1E488E811E0AF6B0000089A81FE</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface </Trace>
<Trace level="1" type="T">select interface namespace </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000001 </Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In </Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement </Trace>
<Trace level="1" type="T">--no interface action for sender or receiver found </Trace>
<Trace level="1" type="T">Hence set action to DEL </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
</Trace>
<Trace level="1" type="T">Work Process ID: 786562</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SND</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2011-05-28T04:55:09Z CET </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="Inbound Framework"></Trace>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0"><asx:values><CX_ERROR href="#o93"/></asx:values><asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary"><cls:CX_SY_NO_HANDLER id="o93"><CX_ROOT><TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID><PREVIOUS href="#o92"/><KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID><INTERNAL_SOURCE_POS><PROGID>339</PROGID><CONTID>1580</CONTID></INTERNAL_SOURCE_POS></CX_ROOT><CX_NO_CHECK/><CX_SY_NO_HANDLER><CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME></CX_SY_NO_HANDLER></cls:CX_SY_NO_HANDLER><cls:CX_BBPX1_STD_MESSAGE_FAULT id="o92"><CX_ROOT><TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID><PREVIOUS/><KERNEL_ERRID/><INTERNAL_SOURCE_POS><PROGID>339</PROGID><CONTID>1754</CONTID></INTERNAL_SOURCE_POS></CX_ROOT><CX_DYNAMIC_CHECK/><CX_AI_APPLICATION_FAULT/><CX_BBPX1_STD_MESSAGE_FAULT><AUTOMATIC_RETRY/><CONTROLLER/><NO_RETRY/><STANDARD><CONTROLLER/><FAULT_TEXT>Error in an XI interface:
Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data
Program: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT><FAULT_URL/><FAULT_DETAIL/></STANDARD></CX_BBPX1_STD_MESSAGE_FAULT></cls:CX_BBPX1_STD_MESSAGE_FAULT></asx:heap></asx:abap></Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
</Trace>
<Trace level="1" type="System_Error">Error exception return from pipeline processing! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
</SAP:Trace>
Regards,
Nithiyanandam
Edited by: Nithiyanandam A.U. on May 28, 2011 8:08 AM

Hi,
      In service marketplace, try searching for notes related to SRM PI scenarios or the particular scenario you are imlementing. For exmaple, if you are implementing the scanerio for Invoice processing, try searching with this.
When we implemented the standard scenarios for SRM, found that they were quite a few notes for the individual scenarios that had to be implemented for the scenarios to run successfully. Most of these were on the ECC or SRM side.
Also, by the looks of your error message, seems the sender system (not PI) is not defined in SUS.
Might be that the logical system for ECC is not set up in SUS. Also check your SPRO settings in 'Define Backend Systems'.
Have a look at the following links which had a similar error :
Vendor replication from SRM 7.0 EBP to SUS via PI 7.0
Vendor Replication in SUS scenario
Regards

XML file to Proxy Scenario with BPM - ID Steps

Hi Guys,
Any one can help me to find about the scenario XML file to ABAP Proxy with BPM, ID steps please. Any link or logical routing, receiver determination and interface determination idea. Please correct me,
I have created Business Service as sender to send one xml file to BPM, BPM is sending a message to SNC system. I have created 2 receiver determinations, but I am confusing in interface determination, where to declare OM?
Please can any one respond bit quicker.
Thanks in advance
Regards
San

ES Repository
                     *Service Interfaces*
Create one outbound service interface for XML file.
Create one Inbound synchronous Interface for SNC system.
Create one Abstract Asynchronous interface ,same message type as you used for outbound service interface .This is for Integration process receive step.
Create one Abstract async interface for receiving the response from SNC system in Integration process.
Create one Abstract synchronous interface to be used in the Integration process for Send sync step.
Create on inbound asyn service interface for sending the response from integration process (received from SNC system) to the Receiver System.
              Operation Mapping.
Create an Operation Mapping using Abstract sync interface and inbound syn interfaces.
              Integration Process
start--->receive Step---->send Synchronous step----->send step.
Create two container elements
first with abstrat async interface for the XML request.
second for abstract asyn interface with the XML response structure (asyn receiver system structure)
In the send sync step select your abstract syn interface from the F4 help.and select the corresponding request and response message from the container element you defined earlier.
Integration Directory.
Create one sender File adapter Communication channel for XML file reading.
Create two receiver communication channel for sync system(receiver XI adapte for ABAP PROXY) and other for asyn receiver system .
Create 3 receiver determination
1.from sender to Integration process.
2.from Integration process to SNC system.
3. from Integration process to Asyn Receiver System.
Create 3 Interface determination.
Specify Operation mapping while you are creating interface determination from Integration Process to Syn BS.
Create one sender agreement
Create two Receiver agreement.
Regards
Kubra Fatima.

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

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 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

Proxy to Proxy Scenario with sender and receiver on same instance

Hi,
I have a scenario to integrate Erecruit to HR system usng standard content. Both the Erecruiting and HR are on same instance so my sender and receiver is the same system. Standard ABAP proxies are provided.
Now I need some help in how to configure the channels and the agreements as both the sender and receiver are on same instance. Do i need to use parties?
do i have to create a sender communication channel?
Please let me know the stps required in configuration for this scenario.
Thanks in advance.

Hey
It does not matter if your sender and receiver are same system or different systems,the configuration steps will be the same.
In your case you would need
1 Receiver determination
1 interface determination
1 receiver agreement
1 receiver communication channel(of type XI adapter,this will connect to HR system).
No party or sender communication channel or sender agreement are required.
You need to have configured 1 business system for HR system in SLD though.
Thanx
Aamir
Edited by: Aamir Suhail on Jul 23, 2008 7:36 PM

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

Idoc to proxy scenario with an acknowledgment

Similar Messages

Maybe you are looking for