Idoc to File Strucutre error..

Hi Experts,
The scenario is IDOC to File scenario in which i am mapping the DESADV05 idoc at the source side and at the target strucutre i have structure like below
MT_Receiver
Header
--Field1
--Field2
Purc Order
--Field1
--Field2
SubHeader
--Field1
--Field2
Details
--Field1
--Field2
--Field3
when i populate with mulitiple Purchase orders from the IDOC the output now coming is as below
MT_Reciver
Header
--Field1
--Field2
Purc Order
--Field1
--Field2
Purc Order
--Field1
--Field2
SubHeader
--Field1
--Field2
Details
--Field1
--Field2
--Field3
Details
--Field1
--Field2
--Field3
But i require the output as ..
MT_Reciver
Header
--Field1
--Field2
Purc Order
--Field1
--Field2
SubHeader
--Field1
--Field2
Details
--Field1
--Field2
--Field3
Purc Order
--Field1
--Field2
SubHeader
--Field1
--Field2
Details
--Field1
--Field2
--Field3
So what change is required for this, i have checked with maximum options.. didnt get the above structure in output.
regards,
Kishore

Hi Abhishek,
I have modified the structure as
MT_Receiver
Header
--Field1
--Field2
BODY_NODE
Purc_Order
--Field1
--Field2
SubHeader
--Field1
--Field2
Details
--Field1
--Field2
--Field3
and when i do testing for the multiple Purchase Orders the output that coming was..
MT_Receiver
Header
--Field1
--Field2
BODY_NODE
Purc_Order
--Field1
--Field2
Purc_Order
--Field1
--Field2
SubHeader
--Field1
--Field2
SubHeader
--Field1
--Field2
Details
--Field1
--Field2
--Field3
Details
--Field1
--Field2
--Field3
Details
--Field1
--Field2
--Field3
So do i need to change any context for this.. still facing this issue
regards
Kishore

Similar Messages

Idoc to file scenario error

Hell Experts,
I have done desgin and configuration from Idoc to File Scenario in XI Intergration server.
Source is R/3 and Target system is File. I have successfully configured each and every step. Send Idoc from R/3 to Intergration server and run sxi_cache. But I didn't get successful results, always the error message shows in SXMB_MONI as follows:
Ackn Status contains system error
During the application mapping com/sap/xi/tf/_CUST_MMAP_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeExcep
tion in Message-Mapping transformatio~
Exception of class CX_XMS_SYSERR_MAPPING
My system Patche level as follows:
SAP_BASIS     640        0012        SAPKB64012
SAP_ABA     640     0012                SAPKA64012
PI_BASIS     2004_1_640 0009        SAPKIPYI69
SAP_BW     350     0009                SAPKW35009
The above error is related to patches problems or any Mapping problems ?
Please help me.
Advanced Thanks.
Regards,
Chandra

Hi,
This may be a mapping issue, try this:
a)in interface mapping see if grids are formed at source and target after executing the test option,
b)also take the xml of the idoc from sxmb_moni , copy it and paste it at the source of the mapping ( use the src tab now) and execute the mapping, is your file structute formed?
i am not sure of the patch levels.
Regards,
Anirban.

Seeburger IDOC-to-File scenario: Error using Classifier module

Hello,
I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
localejbs/SeeClassifier        classifier
localejbs/CallBicXIRaBean      bic
CallSapAdapter                 0
classifier   attID             classifierAtt
classifier   destSourceMsg     MainDocument
classifier   showInAuditLog    true
bic          classifierAttID   classifierAtt
bic          destEncoding      UTF8
bic          destSourceMsg     MainDocument
bic          destTargetMsg     MainDocument
bic          mappingName       AUTO
bic          newLine           true
bic          srcEncoding       UTF8
After conversion in XI, the file fails to write to the folder because of this error:
Message processing failed. Cause: javax.resource.ResourceException: ---
Conversion of synchronous request from module chain ended with errors
---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
BICMapping Error: The mapping [not specified] you are trying to load cannot
be found in the right path! Maybe you forgot to compile or to activate the
mapping!
When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine. But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
I am only facing this problem for the IDOC-to-File scenario. Somehow the same configuration works for a File-to-IDOC scenario.
I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be. Has anyone encountered this problem before?
Any suggestions would be appreciated.
Thanks,
Arianne

Hi Yomesh,
Here is the payload.
<?xml version="1.0" encoding="UTF-8"?>
<LIST>
<S_ISA>
    <D_I01>00</D_I01>
    <D_I02/>
    <D_I03>00</D_I03>
    <D_I04/>
    <D_I05>ZZ</D_I05>
    <D_I06>CELORGS01</D_I06>
    <D_I05_2>ZZ</D_I05_2>
    <D_I07>AVX</D_I07>
    <D_I08>032008</D_I08>
    <D_I09>1718</D_I09>
    <D_I10>X</D_I10>
    <D_I11>00401</D_I11>
    <D_I12>000000008</D_I12>
    <D_I13>0</D_I13>
    <D_I14>T</D_I14>
    <D_I15>^</D_I15>
    <S_GS>
      <D_479>PO</D_479>
      <D_142>CLS01</D_142>
      <D_124>058895921</D_124>
      <D_373>20080320</D_373>
      <D_337>1718</D_337>
      <D_28>8</D_28>
      <D_455>X</D_455>
      <D_480>004010</D_480>
      <S_ST>
        <D_143>850</D_143>
        <D_329>800001</D_329>
        <S_BEG>
          <D_353>00</D_353>
          <D_92>SA</D_92>
          <D_324>4500005037</D_324>
          <D_373>20051110</D_373>
        </S_BEG>
        <S_CUR>
          <D_98>BY</D_98>
          <D_100>USD</D_100>
        </S_CUR>
        <S_FOB>
          <D_146>CC</D_146>
          <D_309>OR</D_309>
          <D_352>FREE CARRIER</D_352>
          <D_334>02</D_334>
          <D_335>FOB</D_335>
          <D_309_2>DE</D_309_2>
        </S_FOB>
        <S_ITD>
          <D_336>01</D_336>
          <D_333>3</D_333>
          <D_351>45</D_351>
        </S_ITD>
        <G_SN9>
          <S_N9>
            <D_128>L1</D_128>
            <D_369>GEN</D_369>
            <S_MSG>
              <D_933>TEST</D_933>
            </S_MSG>
            <S_MSG>
              <D_933>MESSAGE</D_933>
            </S_MSG>
          </S_N9>
        </G_SN9>
        <G_SN1>
          <S_N1>
            <D_98>BY</D_98>
            <D_66>92</D_66>
            <D_67>6310</D_67>
            <S_PER>
              <D_366>BD</D_366>
              <D_93>Graham Crawford</D_93>
            </S_PER>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>BT</D_98>
            <D_66>92</D_66>
            <D_67>6310</D_67>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>SE</D_98>
            <D_93>3M COMPANY</D_93>
            <D_66>92</D_66>
            <D_67>0000019591</D_67>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>ST</D_98>
            <D_93>SAMPLE</D_93>
            <D_66>92</D_66>
            <D_67>6310</D_67>
          </S_N1>
        </G_SN1>
        <G_SPO1>
          <S_PO1>
            <D_350>00010</D_350>
            <D_330>10.000</D_330>
            <D_355>EA</D_355>
            <D_212>10</D_212>
            <D_639>PE</D_639>
            <D_235>BP</D_235>
            <D_234>230-1812-01JDS</D_234>
            <D_235_2>EC</D_235_2>
            <D_234_2>A00000000000002</D_234_2>
            <G_SPID>
              <S_PID>
                <D_349>F</D_349>
                <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
              </S_PID>
            </G_SPID>
            <S_REF>
              <D_128>CO</D_128>
              <D_127>4500005037-00010</D_127>
            </S_REF>
            <G_SSCH>
              <S_SCH>
                <D_380>10.000</D_380>
                <D_355>EA</D_355>
                <D_374>002</D_374>
                <D_373>20051208</D_373>
              </S_SCH>
            </G_SSCH>
          </S_PO1>
        </G_SPO1>
        <G_SCTT>
          <S_CTT>
            <D_354>1</D_354>
          </S_CTT>
        </G_SCTT>
        <S_SE>
          <D_96/>
          <D_329>800001</D_329>
        </S_SE>
      </S_ST>
      <S_GE>
        <D_97>1</D_97>
        <D_28>8</D_28>
      </S_GE>
    </S_GS>
    <S_IEA>
      <D_I16>1</D_I16>
      <D_I12>000000008</D_I12>
    </S_IEA>
</S_ISA>
</LIST>
Thanks,
Arianne

Graphic Mapping:IDOC to File-Avoid Error in Adapter Engine

Hi all,
I'm using Graphic Mapping in my IDOC to File scenario in which each segment in source IDOC will generate a ROW in target File with the condition: DATBI >= currentdate (and some other conditions)
I have a UDF and use the mapping function CREATEIF for this purpose:
DATBI -> UDF -> CREATEIF -> ROW
Problem scenario: In the source IDOC if all the segments have DATBI < currentdate then there is no ROW created, and I get the error in Adapter Engine
Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure ...
How can I avoid this?
I've tried to put this condition using XPATH in Interface Determination and got the error.
There is a way to use function current-date() in XPATH condition?
Thanks for your help,
Elaine

Hi all,
How can I "suppress the row node if condition fails"? I'm new in PI, so please give more details.
My FCC as follows:
Record Structure: Record, Row
Row.addHeaderLine 0
Row.fieldSeparator ,
Record.fieldSeparator 'nl'
Row.endSeparator ; 'nl'
It works fine if the condition satisfied.
In Message Mapping, I've use Test to double check my mapping, and in the scenario that conditions fails, there is no Row in the target message.
Please advise.
Thanks,
Elaine

IDOC-BPM-FILE scenario ERRORS

Hi gurus,
I am trying to send IORDER01(pm order) from an R/3 system to a file, which works fine.
but when i try to use some business logic like if order type = 'PM01' then only i have to write to the file, using ccBPM, it fails...
this is my first BPM scenario and am having trouble....have read lot of blogs etc...can u please tell me where i am going wrong...
I have a data type DT_FILE for writing to the file.
I have interfaces:
si_oa_iorder(outbound asynchronous interface for file)
si_aa_iorder(abstract asynchronous interface for idoc)
si_aa_file( abstract asynchronous interface for file)
si_ia_file (inbound asynchronous interface for file)
I have message mapping MM_IORDER2FILE mapping IDoc to flat file structure
I have operation mapping OM_IORDER2FILE where I have mapped si_aa_iorder and si_aa_file
(( Is this right? are both abstract interfaces to be mapped? or do i need to create more mappings like si_oa_iorder to si_aa_iorder etc? please clarify...))
My IP is very simple with just a 'recv step' having container element of type si_aa_iorder and 'send step' having container element of type si_aa_file to start with..i haven't yet put the switch control etc...even such simple IP fails....
I have created Configuration objects like
Business System for file receiver
Business component for Idoc sender with adapter specific details set
Communication channels for Idoc and file adapters
No sender agreement as it is Idoc communication
Receiver agreement between the Integration Process(IP_IORDER2FILE) and the file server
2 Receiver determinations between BC_idoc_send to IP and other from IP to FileRecv system
2 interface determinations , one from si_oa_iorder of BC_idoc_send to IP and other from si_aa_file of IP to file recv system.
This is my setup and this fails....
My question is..is my message mapping and operation mappings correct? and can u see any obvious blunders i am doing?
please bear in mind that with same interfaces and sending and recv components, it runs fine without BPM....so please look at the BPM bit of mappings/config that i might have missed and please advice asap..
Thanks in advance and i am sure there would be lot of gurus for whome it is just a peanut...so please reply...
Regards
Jhansi

Hello,
I am trying to implement one pi scenario :
File -> file adapter -> ccBPM -> soap receiver adapter -> web service request -> web service response -> ccBPM -> output file adapter.
The web service that I call works file from wsnavigator. I have created all the design and configuration objects
needed for the scenario.
I place a file with following contents:
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
    <pns:GetSetNameWS xmlns:pns="urn:file2soap2fileWSVi">
     <pns:name1>ajeet</pns:name1>
      <pns:name2>phadnis</pns:name2>
    </pns:GetSetNameWS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When I look at the process monitor I get this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists. Problem while determining receivers using interface mapping: No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists. No operation with XML root tag http://schemas.xmlsoap.org/soap/envelope/.Envelope exists.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have no clue about this error. Can you help me with this ?
If yes I can send you more details, if you liked 
Hoping to get help from you,
Cheers,
Ajeet Phadnis

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

IDOC to File (BYpass)-- Error or Warning : " Message Branched. "

HI all,
Iam trying idoc to file scenario(bypass)
my idoc is triggered succesfully and it is reaching to the receiver system.
but the problem is in SXMB_MONI ,it is not showing my Receiver service details and showing with different symbol like " <b>>></b> " with message as " MESSAGE BRANCHED".
what might be the problem....???
Also Idoc reaching to the receiving system very lately.
Pls suggest me ASAP..
Thanks in Advance.
Regards,
Vijji

In the receiver determination, do you have multiple receivers, i.e , is the same idoc being sent to multiple receivers ?
If yes, then the message branch is used to split the source message so that it can be send to differetn targets. You will find multiple entires below the Slit Message Entry one for each receiver.
Regards
Bhavesh

IDOC-XI-FILE Scenario: Error in ABAP Mapping

Dear All,
I am working on IDOC-XI-Flat FIle scenario in which I am using ABAP Mapping as per document "How To Convert an IDoc-XML
structure to a flat file and vice versa in XI 3.0".
I created one customized Idoc for this. The Idoc is reacing XI but its flat file is not getting created. Its giving me following error:
<SAP:Stack>Error in mapping program Z_ABAP_MAPPING_PACKING_LIST (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I have also gone thru threads posted for the same topic earlier but still I am not been to resolve this error.
Please help me out in resolving this error.
Regards,
N.Jain

HI,
   Log saying that, u have problem in the mapping program.
i.e Z_ABAP_MAPPING_PACKING_LIST
   the problem is due declaration of data.
   i hope that, you have some methods.
   those are declared under intialization section in mapping program.
please use start of selection before the method.
other wise, it will come under intilization section.
warm regards
mahesh.

IDoc to File Scenario Error ( IS - Retail )

Hi all ,
I was trying scenario IDoc (SAP ECC 6.0) (IS-Retail) to File scenario .
When i trigerred IDoc from ECC system , it's showing sent successfully to external system or program.
But the problem is it's not coming inside XI sxmb_moni .
I have checked the ALE Configuration and SLD configuration .
Everything is fine.
When i run the TCODE WE05 for IDocs List in XI , it's getting stucked there and the Error showing is
"IDoc: 0000000000000028 Status: IDoc with errors added
External segment name E2WBB01003 cannot be interpreted "
Even i tried with other IDoc WPDWGR it is showing the same error
"IDoc: 0000000000000029 Status: IDoc with errors added
External segment name E2WPW01 cannot be interpreted"

Hi Ashwin,
Please check :
1.The SAP system from which you want to import the IDocs contains function modules for calling metadata.
2.You can import IDocs from SAP Release 4.0 and higher.Support Packages Required for IDoc Imports:
Release    Minimum Support Package Requirement
40B                   SAPKH40B48
45B                   SAPKH45B26
46A                   SAPKB46A20
46B                   SAPKB46B12
46C                   SAPKB46C05
3.check for the authorizations required to import.
Also see SAP Notes 677732 (authorizations), 672745 (missing function modules), 212011 (access to IDoc metadata), and 718320.
check http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
*Pls: Reward points if helpful*
Regards,
Jyoti

IDOC TO FILE Segment Error

Hi,
I am doing IDOC->FILE. When I am posting to Idoc I am
gettng this error in R/3 - "Segment 'ZMESSAGE',
segmentnumber '000001' not correct in structure ZIDOC"
thx and regards,
Ansar.

Hi Ansar,
In your R/3 system from where IDoc is triggered check whether the idoc segment ZMESSAGE is released.
Pls do check whether the latest idoc metadata is existing in the IDX2. If not pls do delete it using IDX_RESET_METADATA report and try it.
Also do compare the structure you are using for the IDoc is similar to the one which is being used in the integration repository. If not pls do reimport it.
Cheers
JK

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 .

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

IDoc to File, SM58 shows error, ST22 short dump - Runtime error

Hi friends,
I am doing a simple IDoc to file scenario using the EVMSTA01 IDoc. My XI is running on client 100 and I am trying to send the IDoc from the client 200 on the same machine. I have completed the design and configuration steps required and also performed the required steps in Sender client (Sm59, we21 and BD54) and receiver client (Sm59, IDX1 and IDX2).
When I tried sending the IDoc from WE19, status meesage says that, the IDoc has been successfully sent to the receiver but SM58 shows error "IDOC_ERROR_WORKFLOW_START_R". When I looked in to ST22, there was a short dump with the below message -
Runtime Errors         MESSAGE_TYPE_X
Date and Time          18.10.2008 23:24:29
ShrtText
     The current application triggered a termination with a short dump.
What happened?
     The current application program detected a situation which really
     should not occur. Therefore, a termination with a short dump was
     triggered on purpose by the key word MESSAGE (type X).
Error analysis
     Short text of error message:
     Unable to read RFC destination WORKFLOW_LOCAL_200
     Technical information about the message:
     Message classe...... "SWF_RUN"
     Number.............. 617
     Variable 1.......... "WORKFLOW_LOCAL_200"
     Variable 2.......... "RFC_READ_DESTINATION_TYPE"
     Variable 3.......... "DESTINATION_NOT_EXIST"
     Variable 4.......... " "
     Variable 3.......... "DESTINATION_NOT_EXIST"
     Variable 4.......... " "
Trigger Location of Runtime Error
     Program                                 CL_SWF_RUN_WIM_LOCAL==========CP
     Include                                 CL_SWF_RUN_WIM_LOCAL==========CM07Z
     Row                                     10
Module type                             (METHOD)
Module Name                             IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
rce Code Extract
e SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2   DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4   TRY.
5       IF me->m_int_state-system_user IS INITIAL.
6         me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7       ENDIF.
8       re_user = me->m_int_state-system_user.
9     CATCH cx_swf_run_wim INTO l_excp.
>>       MESSAGE ID     l_excp->t100_msg-msgid
11               TYPE   'X'
12               NUMBER l_excp->t100_msg-msgno
13               WITH   l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14                      l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15   ENDTRY.
16
17 ENDMETHOD.                    "
Any help would be appreciated..!!
PS: Points would be assigned to all the helpful replys without fail

Hi,
See check for RFC destination and it is working as per your configuration or not , i mean , it is trying to locate remote server.. , so try to check in sm59, remote login and the respective result is going to your required client or not ??
Also see the further errors while doing Idoc related scenarios..
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not reaching XI. Not posted in the receiver SAP
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
Regards
Chilla

Error during variable substitution: idoc to file

Hi Friends,
I have a got a issue which is Idoc to file scenario.
Iam getting the following error.
Attempt to process file failed with com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: date_processing
Could you please tell me waht could be the reason for the same?
as per my analysis, I observed that the field date_processing has been declared

Hi Sandeep ,
If the variable date_processing refers to an element in XML schema, Please check if you have added the prefix payload: to the information under Reference.
The reference then comprises a pseudo path description in the form of a comma-separated list with the schema namea,na,nameb,nb,....
Where namea,nameb,... corresponds to the element name and na,nb,... corresponds to the occurrence of the element name at the respective level in the document.
The description begins at the root of the document and ends at the respective element.
Also please check
Re: Variable substitution
Regards,
Jyoti

IDoc to File scenario... Receiver Comm Channel Error...

Hi Guru,
On the scenario IDoc to file, I'm encountering the ff error on my receiver comm channel (File Adapter)...
ttempt to access the 1 requested objects on 1 failed.
Detailed information:
com.sap.aii.ib.core.roa.RoaObjectAccessException:
Attempt to read object Adapter Metadata File | http://sap.com/xi/XI/System,
type AdapterMetaData from application REPOSITORY on
system REPOSITORY failed. Object does not exist. Detailed
informatio n: SWCV ID: << removed >>
does not exist in Enterprise Service Repository and
System Landscape Directory (ROA_MOA_NOTCOMPLETED)
<< removed >>
Attempt to access the 1 requested objects on 1 failed.
Detailed information:
com.sap.aii.ib.core.roa.RoaObjectAccessException:
Attempt to read object Adapter Metadata File | http://sap.com/xi/XI/System,
type AdapterMetaData from application REPOSITORY on
system REPOSITORY failed. Object does not exist. Detailed
informatio n: SWCV ID: e5a519a0766111dca2e8e95d0a115642
does not exist in Enterprise Service Repository and
System Landscape Directory (ROA_MOA_NOTCOMPLETED)
Attempt to access the 1 requested objects on 1 failed.
Detailed information:
com.sap.aii.ib.core.roa.RoaObjectAccessException:
Attempt to read object Adapter Metadata File | http://sap.com/xi/XI/System,
type AdapterMetaData from application REPOSITORY on
system REPOSITORY failed. Object does not exist. Detailed
informatio n: SWCV ID: e5a519a0766111dca2e8e95d0a115642
does not exist in Enterprise Service Repository and
System Landscape Directory (ROA_MOA_NOTCOMPLETED)
Please advise what possible solution can we apply?
Thanks.
Edited by: Rob Burbank on Dec 17, 2010 10:43 AM
Edited by: Rob Burbank on Jan 3, 2011 12:03 PM

Hi,
You can check File adapter metadata under Basis SWCV -->namespace http://sap.com/xi/XI/System in IR.
-Rahul

Idoc to File Strucutre error..

Similar Messages

Maybe you are looking for