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

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

HTMLError in sxmb_moni, Idoc to ABAP Proxy Scenario

Hi Friends
I am trying to send data from R3 to SCMTM system(SAP System), via Idoc to ABAP Proxy Scenario ,I am getting the following under HTMLError in sxmb_moni
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Any ideas will be helpful.

Hi,
I faced similar problem. it was due to configuration problem in SXMB_ADM. corss check specific server confiration in SXMB_ADM.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Reyaz

IDOC and RFC/PROXY Scenarios

Is there a way to practice IDOC or RFC Scenarios if you only have access to the XI System? So you have XI abap and Java but no R/3 System...
Can someone tell me how I can practice IDOC and RFC scenarios please

It is possible to practive IDOC & RFC scenarios with XI's abap stack as sender & receiver of IDOCs and RFCs with the "XI" in the middle....
However, the problem might be the IDocs & RFCs might have to be created from scratch to test these out....
If you have some IDOcs that you can use in XI abap stack, have the program that generates this IDOc and when(if) XI abap stack receives this, the processing module to process this IDoc...
Similarly, the RFC FM has to be available on XI ABAP so that it can bhe invoked from the RFC interface..
Thanks.
Message was edited by:
Renjith Andrews

Issue in Iodc- abap proxy scenario

Hi all
I have a idoc to abap proxy scenario. The issue is ,
when we send the idoc to client A of target system, it works ifne.
But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
Is it because of any error in XI configuration or somethin else.

hi all
thanks for all your responses.
I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
I gave the conditions in Receiver Determination.
Same Server Proxy is used in both the target business sytems.
I have done all the Configuration Steps ,( Created two separate business systems also )
Also I have checked wiht all the system settings to be made in the target system B.
When i trigger the idoc to Client 100, it goes to XI and then reaches Client 100 of System B
without any problem. I get the desired result from proxy code.
When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
the Call Inbound PRoxy step. (from sxmb_moni)
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

IDoc to SOAP scenario is showing error

Dear Experts,
We were trying a scenario which is IDoc-XI 3.0->SOAP and where the WebService is situated outside our office network. Our network team have bypassed proxy for accessing that WebService URL and the same is accessible from our XI3.0 application server from browser. We have configured the scenario and when we have tested the scenario from RWB->Component M onitoring->Integration Engine->Test and this has worked fine. But when we have tested the scenario by triggering IDoc from the R/3 system, it is throwing the below mentioned error in both at the comm chanel and at the SXMB_MONI acknowledgement.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Service Error
points to be noted here:
1. Business Service has been configured correctly for triggering ALEAUD messages and ALEAUD messages are reaching R/3 successfully.
2. We have chosen option Keep Headers and Do not use SOAP header options.
3. We are passing some values to the SOAP Header from SOAP channel.
Please could somebody help us on the root cause of the error message.
We have run report IDX_NOALE for that particular IDoc so that it doesn't return any acknowledgement back to the R/3 system.
Thanks and regards,
Sugata
Edited by: Sugata Basu on Nov 19, 2011 12:40 PM

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Why is a sender communication channel not required for IDOC and PROXY ?

Hello,
In case of IDOCs, metadata will be available in PI for the IDOCs used both at inbound and outbound.
Why is a sender communication channel is not required in case of IDOC and PROXY outbound scenarios (i.e. IDOC to File or PROXY to file ..) when a receiver channel is required for scenarios like file to IDOC or file to PROXY.
Though this might be a regular question, I am not able to find a proper reason.
Please let me know the reason for the above request.
Thanks & Regards.

You will create RFC destination in ECC , it will have details about PI system details, when ever you send IDoc, ECC will use Port and RFC destination to connect PI Integratiion engine to deliver data to PI.
But when receiver side you will create RFC destination in PI with ECC details, but to call RFC destination and Port we need medium that was the reason we create IDoc communication channel.
Even the same case for Proxy also, but HTTP deastination establish the conection between ECC and PI, but receiver side you have to create XI channel with PI integratioin engine adress to post data.
Regards,
Raj

Idoc Vs Proxy

Hi Experts,
I have a scenario like i want to transfer the Idoc data from One sap system to another sap system through XI. So What is the best option to do this useing IDoc or Proxy?
Can you please breiefly explain me above Adavantage & Disadvanctage of these ways and Which one is best for me in this scenario.
Thanks in Advance,
Points rewared for each valuable answers.
Best Regards,
Vijay

Hi,
It all depends upon the business Scenerio..
Proxies can be used when data is huge and it is quite fast in action and you can trigger when ever you want...
Assume if the data has to be updated immediately to the receiver system in that case IDOC is fine...once the Idoc is created we can trigger it by settings or thru by back ground job and by Tcode we02 we can find the status of the IDOC
Regards
Agasthuri Doss

ALE Configurations for JDBC to PROXY scenario

Can some body tell me what are the ALE configurations that needs to be done in both the systems and also in XI system.

Hi there
No need for ALE confihuration unless you are using IDocs in your scenario.
You need to configure the integration engine in the Proxy system using SXMB_ADM and create an RFC for the Integration server.
on the JDBC side you'll need the database bridge configured in the communication chanell...
what is your scenario specific...which system types and versions?
Nimrod

Idoc to Proxy code..

Hi,
Currently, one of my client is using Idoc's to load data (from sender file) into R/3 but becuase of Idoc's we are facing some performance issues.
My question is that
1. is it possible to convert the Idoc processing logic into a code, which can be used inside server proxy.
2. How much performance is going t improve using such a methodology.'
Thanks....

Hi,
What should be the basis to decide when to use proxies, RFC adapter and idoc adapter.
We have to first check for our scenario do we have the standard IDOC or not.If we have the IDOC then we have to go with the IDOC.
If client need some validation and need to add some fields. that can be done by extending the IDOC and we can copy the standard IDOC and we can modify the code in the funtion module.
Next we have to go with RFC when we require the responce back from the target system. we have to check is there any standard BAPI or not.If u dont find then u can do customize RFC according to client requirement.
We have to go with Proxy if we dont find the Standard IDOC.
and if we have to RFC to be called at a time.
Suppoce if ur doing a scenario were u have to create a production order in this case we can go with RFC but after creating we have to commit the BAPI that cant be done in one process. we have to go with BPM and again performance issue.
In this type of cases we go with proxy scenario.if cleint require any data validation we ca do it.
If we want to reporcess the error date we ca do it. we ca send an intimation mail from proxy to user. this all can be done in proxy scenario.
Thanks and regards,
Phani

Idoc-xi-file scenario. how to display file in html format

I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
In idoc-xi-file scenario....... how to display file in html format ??
Thanks in advance
Kumar

Hi Vijayakumar,
Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
Regards
Kumar

In idoc to file scenario, if XI system is down where do idocs pile up?

In idoc to file scenario, if XI system is down where do idocs pile up (get stuck)
what tcode can I use to reprocess it?

Sender System ,Check BD87 .. you will see alll the IDOCs in Yellow state ..
You can reprocess all the IDOCs in go from there .. if only they are in yellow state ...
regards
PS

FIle Content Conversion Problem in IDOC-XI-File Scenario

Dear All,
I am doing IDOC-XI-FILE scenario.
I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like %store_code%_%current_date%_sitemaster.xml , I have completed the dynamic generation successfully .
Now there is slight change in the requirement ,we have to suppress the current_date node of the xml content . i have tried to suppress the current_date using these DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut , But I am unable to suppress it Can some body provide me the details on this .
The output xml version generated by Reciever file adapter is as below :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
</ns0:MT_SITE_MASTER>
Plz provide me the code I have to write in the file content conversion .
Thanks in advance
Regards
Prabhat

If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier. Then use the Suppress Logic for the Current Date.
So it will look like this-
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
<CURR_DATE>
<CURRENT_DATE>20051105</CURRENT_DATE>
</CURR_DATE>
</ns0:MT_SITE_MASTER>
So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
CURR_DATE.fieldFixedLengths - 0
CURR_DATE.fixedLengthTooShortHanling - Cut
And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
Hope this solves ur problem.
Regards,
Moorthy

Error/Doubts in Idoc-XI-File scenario

Dear All,
I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
Can anybody guide if I have followed the correct steps & where I am doing the error.
Warm Regards,
N.Jain

Hi ,
Plese refer the following blogs ,
IDoc to File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
You have to do all this settings mentioned in the docuemnt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks ,
Suvarna
Award pts if it helps .

Idoc to Proxy Scenario

Similar Messages

Maybe you are looking for