File to Idoc - File not picked up

Hi experts,
               In the file to idoc scenario when i post a file in the file server it is not picked up by the file adapter. But in the communication channel monotoring it reports <b>'Process finished sucessfully'</b>.
Help me out in this issue.
Regards
Santhosh Kumar V

HI Santhosh
if you are using NW latest version.check in Communication channel monitoring
otherwise in Adapter monitoring.
Check u r Sender Communication channel working or not... in RWB->Component monitoring->Communication channel monitoring..
in which color it is displaying u r Sender Communication channel?? If it is in RED color then u r sender cc is error one.
Check the following:
1. Name of the input file and the filename in communication channel should match.
2. The communcation channel is activated
3. The folder path is correct.
4. The Processing mode is "Delete"
5. XI server is up when u try the scenario
6. The adapter has status green in RWB Adapter Monitoring
7. Sender Agreement is properly configured
As explained above
See ,,
--Check the FTP server details
--Check the User.pwd and authorisations -- to read file,
--Check the File name sapecified in sender CC, and check the file i spicked by CC or not in RWB channelmonitorservlet
by http://host:port/mdt/channelmonitorservlet
--Also see the below links
/people/michal.krawczyk2/blog/2005/08/17/xi-operation-system-command--error-catching
OS Command on FTP
OS command line script - Need help
FTP - Run OS Command before file processing
/people/sravya.talanki2/blog/2005/08/23/sender-xi-ftp-adapter-with-regular-path-expression-150-abap - Sender XI FTP Adapter with Regular Path Expression – ABAP
Cheers..
Vasu
<i>** Reward Points if found useful **</i>

Similar Messages

  • Multi mapping.. is it possible File to Idoc & FIle .. its urgent?????

    Hi All,
    File to Idoc & File.
    I need to pick the file and i need to do multi mapping, so that from the file we can generate
    one idoc which has to go to SAP and
    one acknowledgment's file and sent back to partner.
    Based on the below blog, looks like we can't use Idoc adapter when the target message is Idoc using Multi mapping.
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    Can anyone suggest me how i can achieve this scenario without using BPM.??
    Regards
    Seema.

    Hi,
    The Multi mapping is possible without BPM but not for IDOC as its not part of Java Stack. IDOC adapter is on ABAP stack.
    As Raj have suggested,
    You could create two different Mappings one for file to IDOC and another for file to file as an acknowledgment.
    In Receiver determination you need to use multiple receivers as IDOC --R/3 receiver and the File receiver system.
    It will create the IDOC as well as push the acknowledgment to file also.
    But incase if you get any problem with sending the IDOC then also you will get successful acknowledgment via file. So directly there will not be any relation between these IDOC and File receivers as an delivery recipt of IDOC.
    Here either you have to use the IDOC acknowledgment feature or BPM or Alert notification to get the exact notification about the IDOC posting to receiver system.
    Please refer below links
    1. IDOC acknowledgment
    This Feature is Available under SP 18 and we are on SP16
    http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
    Check this document on handling IDOC acknowledgements. This might give you some pointers.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    This Feature is Available under SP 18 and we are on SP16
    http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
    Check this document on handling IDOC acknowledgements. This might give you some pointers.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    How to Handle Acknowledgments for IDoc (NW7.0)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    IDOC acknowledgements
    2. BPM
    File to IDOC with BPM
    File to idoc with BPM
    Problem in BPM implementation
    Use Aleaud in BPM
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    3. Alert Notification
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config
    Thanks
    Swarup

  • File to IDOC scenario not working

    I have configured a file to idoc scenario and kept the XMl file in a shared location on XI server.
    I have also created and checked the communication channels correctly.
    Once Everything is done my xml file does not get picked up at all. Also the SXMB_MONI does not show any messages for my service.
    How do I find out what is the error ??

    Hi Kapil,
    Just check the File path that was in shared location once and the file name is properly mentioned or not..
    And also one thing after activating all IR and ID just goto SXI_CACHE and press <b>F6</b> to update cache refresh
    And also in RWB --> Message Monitoring --> Adapter monitoring --> check the status of the sender
    Regards,
    Sridhar

  • File Adapter as Sender not picking the files

    We configured the File Adapter as Sender, Transport Protocol =NSF and message protocol as FCC.
    In OS we have folder to read the file, but SAP XI unable to read the file.
    To trouble shoot this issue we copied that file into another location and reverted back to the same location then XI File adaptor is able to read the file.
    Now we have compared the Attributes of the path
    the only difference in file attributes
    Coded character set ID . . . . . . . . :   819      
    CCSID 819 (decimal)
    0333 (hex)
    Name ISO 8859-1 ASCII
    Description ISO 8859-1: Latin Alphabet Number 1Latin-1 countries and regions
    Notes Related CCSID with euro is 923           
    able to read the file attributes:
    Coded character set ID . . . . . . . . :   1252                    
    CCSID 1252 (decimal)
    04E4 (hex)
    Name MS-WIN LATIN-1
    SC Co-existence/Migration
    FMS Subset
    Registration Date 
    Description MS Windows, Latin-1
    Notes CCSID for this code page with euro is 5348
    We have tried to chage the File type as Text and File Encoding with ISO-8859-1even then its not picking the files.
    Please suggest me where i am doing wrong here
    Thanks,
    Venkat.

    Hi,
    Check the file path & file name , Check  the processing mode parameter which you have set?
    Check the folder properties & provide all the permission ...
    Finally check the communication channel status in RWB, If the problem persist try to stop & start the communication channel again..
    Hope it helps...
    Regards,
    Kumar.

  • File to IDOC Scenario Not able get Metadata (IDX2)

    Hi,
    I am doing File to IDOC scenario. I have done all configurations in IR and in ID. But it is throwing error like ATTRIBUTE_IDOC_METADATA-Basic type ZOIDOC does not exist.
    Where as my custom idoc is a not exit in metadata (IDX2). Also I am trying to reload same manually but I am not able to reload it. I have all required configuration in SAP R/3 side like partner profile.
    I would appreciate yours inputs.

    Hi Sunil,
    You are saying that you are unable to load the Metadata even manually.
    There could be a problem with the RFC destination defined within the IDX1 port. So first test the RFC destination using SM59.
    Also ensure that you have used the right naming conventions for the PORTS and RFC destinations as below:
    <SID>CL<ClientNo> e.g  DXXCL055 where DXX is the SID and 055 is the Client No.
    Rgds
    RC

  • IDOC-FILE - If IDOC is not triggered, need to genarate file with constants

    Hi Friends,
    I have a scenario like this.
    IDOC to FILE scenario.
    1. IDOC will get triggerd everyday and flat file will be genatated at specified location.
    2. If IDOC is not genarated for the day, need to genarate falt file with some constants.
    Can anyone help me on this.
    Thanks in advance.

    Hi Vivek,
       I assume that Idocs are being triggred from a different system say SAP r/3 system to XI server. Since you do not have any messages to verify whether idoc has been triggred for the day or not, you have to keep a log in the SAP r/3 system in form of a table. This table (say Z_IDOC_TIME) will contain one entry having date and time when last idoc has been sent to PI system. Now one ABAP code is required which will continuously read the contents of last entry in the ZIDOC_TIME and compare with current server time. If the difference between the time is found to be more or equal to 24 hours then emails can be triggred to a fixed set of recipients. The set of recipients may be made dynamic by storing them in a table say ZEMAILID. So the ABAP program will take contents from both Z_IDOC_TIME and ZEMAILID. The flat file with constants can be attached with the emails.
    In case you do not want emails to be sent then you would require batch jobs which will run in background. This batch job will check at a particular time if iodcs were sent for the day or not. If they not been sent then it will call ABAP code to trigger iodcs with a different data set than what is expected by PI in normal conditions (may be you can populate the idoc with the constants you would like in the file). When such an idoc is received in PI then you can easily generate an flat file with required constants.
    regards
    Anupam

  • IDOC-File : Service interface is not picking.

    I am doing IDOC to File scenario, in Integration Engine level it was picking the different "service interface"
    Ex: It was picking MAT_Sender_SI instead DBM_Sender_ SI.
    What could be the reason?
    Thanks in advance.

    Hi Kasi,
    I have a doubt in case of IDoc sender u need not create SI for outbound you can use the Idoc name directly.
    Hope i haven't understood it wrong.
    Hope this helps to configure:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539?overridelayout=true
    thanks and regards,
    Praveen T

  • Mid-process Receive (onEvent) is not picking up published event

    We have a composite (CompositeA), which has 2 BPEL processes (bpelprocess1 and bpelprocess2). bpelprocess1 is synchronous and bpelprocess2 is a one-way. bpelprocess1 receives a message from the client - then sends the message using a one-way Invoke action to bpelprocess2 - bpelprocess2 transforms the message and assigns some values - then sends the message to Event1 through an Invoke action - bpelprocess1 has a Receive activity waiting for an event from Event1 - then it will send the message back to the client as the Reply. Everything works up to the point where the bpelprocess1 Receive(onEvent) activity is waiting for an event, it sits in this "Pending" state until the SyncMaxWaitTime value has expired and then we get a timeout error (see below).
    "Waiting for response has timed out. The conversation id is null. Please check the process instance for detail."
    So our question is, why does the Receive(onEvent) in bpelprocess1 never pick up the published event? We've run some additional tests to ensure the event is being published, and that has been confirmed.
    Is it possible to receive an event that was published during the current instance of the process (i.e., since bpelprocess1 invoked bpelprocess2 which invoked the Event1 publish, can bpelprocess1 perform a mid-process Receive of the event that was just published?
    Please let us know if this makes sense or if you have any additional questions.
    On a side note, if we create an independent mediator component in the same composite and have it subscribe to Event1 as well, then just write the message out to a file. It would not pick up the message from the EDN in the scenario described above, if we set the property nonBlockingInvoke=true or bpel.config.transaction=requiresNew on the bpelprocess2 partnerlink from bpelprocess1, the Mediator would get the message from the EDN, but bpelprocess1 still timed out waiting for the event. If we setup another BPEL process (bpelprocess3) in the same composite (though not linked to bpelprocess1 and bpelprocess2) and it has a mid-process receive onEvent listening for Event1, it does not pick up the published event either, so seems to be an issue with the mid-process receive onEvent in the synchronous BPEL process.
    Any help is appreciated.

    Thanks for the reply, but there is no issue with the one-way from bpel1 to bpel2, we do not expect nor want a response from bpel2, it should just publish the event and complete. The bpel1 should continue it's flow (which it does) and the next action is a Receive action listening for an event (that was published by bpel2), but the Receive never finds the event.
    Here's a less complex use case:
    1. bpelprocess1 is a synchronous process which publishes to Event1 (this completes successful and returns a success message to the client)
    2. bpelprocess2 is an asynchronous process which has a mid-process Receive action that is listening for Event1
    3. bpelprocess3 is a process which is initiated by Event 1
    If we execute bpelprocess2 it will set at the mid-process Receive action in a PENDING state, waiting for Event1 to occur.
    If we then execute bpelprocess1 the Event1 is published and we receive a "SUCCESS" response back.
    At this point bpelprocess3 is initiated (b/c it's initial Receive is triggered by Event1)
    We would also expect the mid-process Receive in bpelprocess2, which is in a PENDING state to trigger, but it never does.
    Hopefully this use case makes more sense.

  • IDocs not created in file to IDoc scenario

    Hi all
    I am trying this file to IDoc scenario.
    File picked up successfully and sent to R/3 Backend…But Idoc is not posted…the status records
    In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
    I created/tested all basics like RFC dest, port etc.
    File service that I am using is a business service …hence I am specifying a Logical system name in
    <b>Adapter specific Identifiers</b> of the file service.
    I disabled EDI_DC40 control tag record as IDoc adapter
    takes care of it.
    So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
    But SXMB monitor gave an error regarding this control record tag…I guess as we have disabled it so there won’t be any values
    for control record in payload (correct me if I am wrong).
    So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
    But in the backend I am getting this error regarding partner profile.
    I also tried to use an existing profile (<b>LS</b> type) by modifying it’s inbound parameters to accept <b>CREMAS</b> Idoc.
    But the error is as persistent as me
    Pls help
    Sudhir

    Hi
    Sender --> LEGACY, maintained in SLD (Logical system).
    Receiver--> ENI maintained in SLD with logical sys name M700.
    Partner Profile LEGACY maintained in R3.
    <b>Following is the IDocOutbound in SXMB monitor in XI</b>.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>100</SAP:MANDT>
      <SAP:DOCREL>640</SAP:DOCREL>
      <SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>CREMAS</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
      <SAP:SNDPRN>LEGACY</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPENI</SAP:RCVPOR>
      <SAP:RCVPRN>M700</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS />
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>0000-00-00</SAP:CREDAT>
      <SAP:CRETIM>00:00:00</SAP:CRETIM>
      <SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
      </SAP:IDocOutbound>
    <b>Control record of IDoc in R3</b>
    Tab: Typeinfo
         Basic type-->CREMAS03
         Message Type-->CREMAS
    Tab: Partner
         Recipient
          Port  -->SAPENI
          Partner Number--> M700
          Partner Type-->LS
         Sender
          Port  -->SAPAXI
          Partner Number--> LEGACY
          Partner Type-->LS
    Pls help
    Regards
    Sudhir

  • ** File to IDoc scenario - IDoc not created in target system

    Hi friends,
    We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
    We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
    1) SM59 - Connections are OK both application and XI system
    2) IDX1 - In XI System, we have assigned SAP<R/3> port.
    3) IDX2 - IDoc is imported.
    4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
    5) In application system. - Partner Profile maintained correctly.
    6) SM58 - There is no error.
    So, what could be the reason ?
    Kindly reply, friends,
    Thanking you.
    Kind Regards,
    Jeg P.

    Hi,
    Check all the steps ..
    File to IDOC
    Do these configurations in R/3 and in XI...
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    Thanks,
    Satya

  • No messsage in SXMB_MONI, although file has been picked up in file to idoc

    Hi,
    i m working on a file to idoc scenario using MATMAS.MATMAS02, once i got the scenario executed with error status 51 ,
    "Messages have been issued: number 0000000000198012"
    the datas to be posted were MATNR ,MAKTX,MBRSH , etc , in this MATNR is self generating and I by mistake issued a no to it for testing purpose and the above error came.
    again when i tried to test the scenario without assigning any no to MATNR , I find no messsage in SXMB_MONI for this particular execution although file has been picked up from the source directory and it is also not found in the receiver R/3 system using we05 .
    Pl help how to rectify the error and find out where the error has again  occured and why .
    ans will be rewrded
    rgds
    mojib

    hi
    go to SXMB_ADM-->manage queues. here desregister, register and active ALL the queues again.
    see in SM58 if you have any error.
    also in SXMB_ADM go to integration engine configuration and check you have this variabbles
    RUNTIME--LOGGING--
    0   
    RUNTIME--LOGGING_SYNC--
    0   
    RUNTIME--TRACE_LEVEL--
    3
    Rgds
    Rodrigo

  • File Adapter is not picking few files

    Hi All,
    I am facing some issue in file adapter. Below are the possible file format that we need to pick.
    File format sample 1:
    865|FieldOrder|AK|620005168|1|Reject|Line Qty can not be Canceled,xyz,abc|The line has been shipped,fgh,hjk
    File format sample 2:
    865|FieldOrder|AK|570000259|10|Accept|
    - All the fields are separated by '|' & last filed is terminated by 'eol'.
    - The last two fields (C7 & C8) also have sub fields separted by ',' as shown in sample 1.
    - Fields C7 & C8 are optional. (Sample 2 is shown above)
    - File contains only one record.
    We are using below mentioned XSD which is working fine in case of sample 1 as shown above. When we have a file of format like sample 2 then file adapter is failing to pick the file. I also tried minoccur='0' attribute which also not worked. Please help me out to find the exact XSD which will pick both type of formats (sample 1& sample2).
    <?xml version="1.0" encoding="UTF-8" ?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
    targetNamespace="http://us.fujitsu.com/865_EDIFile"
    xmlns:tns="http://us.fujitsu.com/865_EDIFile"
    elementFormDefault="qualified" attributeFormDefault="unqualified"
    nxsd:encoding="ASCII" nxsd:stream="chars" nxsd:version="NXSD">
    <xsd:element name="Root-Element">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="Root" minOccurs="1" maxOccurs="unbounded">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="C1" type="xsd:string" nxsd:style="terminated"
    nxsd:terminatedBy="|" nxsd:quotedBy='"'></xsd:element>
    <xsd:element name="C2" type="xsd:string" nxsd:style="terminated"
    nxsd:terminatedBy="|" nxsd:quotedBy='"'></xsd:element>
    <xsd:element name="C3" type="xsd:string" nxsd:style="terminated"
    nxsd:terminatedBy="|" nxsd:quotedBy='"'></xsd:element>
    <xsd:element name="C4" type="xsd:string" nxsd:style="terminated"
    nxsd:terminatedBy="|" nxsd:quotedBy='"'></xsd:element>
    <xsd:element name="C5" type="xsd:string" nxsd:style="terminated"
    nxsd:terminatedBy="|" nxsd:quotedBy='"'></xsd:element>
    <xsd:element name="C6" type="xsd:string" nxsd:style="terminated"
    nxsd:terminatedBy="|" nxsd:quotedBy='"'></xsd:element>
    <xsd:element name="C7">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="C7_child" type="xsd:string"
    nxsd:style="array" nxsd:cellSeparatedBy=","
    nxsd:arrayTerminatedBy="|"
    maxOccurs="unbounded"></xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="C8">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="C8_child" type="xsd:string"
    nxsd:style="array" nxsd:cellSeparatedBy=","
    nxsd:arrayTerminatedBy="${eol}"
    maxOccurs="unbounded"></xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    <!--NXSDWIZ:C:\Documents and Settings\rastogvi\Desktop\cap.txt:-->
    <!--USE-HEADER:false:-->

    Hi,
    >>2) Even for those few picked files, why are we seeing less no. of Idocs
    than the file contents.
    Check the mapping by using the payload from SXMB_MONI. I think the mapping is not correct.
    >>3) Why is the adapter always picking files immediately even if a poll
    interval is set.
    Once the objects are activated in ID the channel picks the file immediately and then it waits for the polling interval and repeats the process.
    Regards,
    Jai Shankar

  • Mapping not sufficiently defined FILE TO IDOC(HRMD_A.HRMD_A06) scenerio

    Hello friends,
                         In message mapping part from File to IDOC. I am doing mapping of infotype 14 message type with the corresponding idoc. But when I activate it I am getting the following error:
    Activation of the change list canceled Check result for Message Mapping MM_INF14_LS | urn:tcs:test:  Mapping not sufficiently defined
    As far as I know I have properly mapped the fields which I am picking from the file. But I am not very sure what to do woth few fields in the IDOC which appear to be red in message mapping
                               Kindly give me the solution.
    Regards,
    Lokesh

    Thanx guys...I tried changing the description of other mappings whch were already activated. And thn I tried activating I got the same error:
    Activation of the change list canceled Check result for Message Mapping MM_02IT | urn:tcs:payroll:  Starting compilation  Source code has syntax error:  java.lang.NoClassDefFoundError: com/sun/tools/javac/Main Exception in thread "main"
    what possibly can go wrong? Is there any way to activate it.
    Looking forward for ur reply.
    Regards,
    Lokesh

  • Soap Adapter not Picking up files from sender

    Hello All,
    I have configured a SOAP Adapter and started it. When i place a file in the appropriate directory, it is not getting picked up. Are there any reasons this could happen ?
    I would really appreaciate it if someone can help me with this !!!
    Below is the log:
    17:26:27 (3812): Enabling service ToWS
    17:26:27 (3812): Enabling service FromWS
    17:26:27 (3823): SOAP adapter initialized
    17:26:27 (3830): Starting the server at 8660:/XIservices/MXS/xmb
    17:26:27 (3830): Starting the server at 4444:/XIservices/MXS/ws
    17:26:27 (3807): SOAP adapter started
    Below is part of the config file:
    The port and path where the adapter waits for web service messages from clients.
    XMBWS.WSPort=4444
    XMBWS.WSPath=/XIservices/MXS/ws
    XMB.SenderBusinessSystem=WLX_100
    #XMB.ReceiverBusinessSystem=MD1_400
    XMB.User=XIAPPLUSER
    XMB.Password=********
    XMB.Client =100
    XMB.Language=EN
    XMB.SenderInterfaceNamespace=http://xi.sap.com/wlx
    XMB.ReceiverInterfaceNamespace=urn:sap-com:document:sap:idoc:messages
    XMB.SenderInterfaceName=ProcesseFT
    XMB.ReceiverInterfaceName=Z_SERVICE_ENTRY.ZSERVICEENTRY01
    XMB.TraceLevel=0
    XMB.LoggingLevel=0
    XMB.QualityOfService=EO
    XMB.ContentType=text/xml

    Hi,
    If you are using a Stand-alone J2SE Adapter Engine, you can create a SOAP adapter to pick a SOAP message from a file system and send it to the Integration Server. This is available with the XI3.0.
    The configuration will look like this.
    Bubble adapter java class
    classname=com.sap.aii.messaging.adapter.ModuleBubble
    This adapter instantiates a bubble bag for supporting
    a soap file upload and sender. A bubble bag is a collection of Bubble
    instances that form some processing chain of message objects.
    Below parameter Bubble.Helper specifies the helper class that implements
    the ModuleBubbleHelper interface. This class is used to instantiate
    a bubble bag for this adapter.
    Sets the bubble module helper that can instantiate your bubble bag
    Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperSOAPFileSenderImpl
    #$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
    Below this line are the parameters specific to the ModuleBubbleHelperSOAPFileSenderImpl
    #$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
    This module loads files from the local file system, consruct SOAP messages
    (or SOAP with Attachments messages), and send them to the specified Web Service target URL.
    Upon successful completion, response messages are stored in the file system.
    Files stored can represent a plain payload, a SOAP envelope, or a SOAP with Attachments.
    Plain payload files and SOAP envelope files may be packaged in MIME using some MIME headers.
    SOAP with Attachments files must be packaged in MIME.
    Specifies the type of the file. The available values are:
    plain for plain; soap for soap envelope; swa for soap with attachments
    SFSender.ContentMode=soap
    Specifies the packaging
    true for MIME packaged file; false for bare content
    SFSender.MIMEPackaged=true
    log everything (4-digit binary, where the bits indicate which
    information is logged: req message, req context, resp request, resp context)
    SFSender.Log=1111
    The target URL to which messages are sent.
    SFSender.TargetURL=http://p28848:4040/mysoaphandler
    The upload directory on the local file system
    This directory has six sub directories with names 0, 1, 2, 3, 4, 5, and 6. (they will be created)
    The meaning of each sub directories are:
    0 = inbox where you place messages to be sent
    1 = trash box
    2 = work box
    3 = successfully completed (original) messages go in
    4 = response messages come in (if any)
    5 = undelivered (original) messages go in
    6 = error messages come in (if any)
    In these directories, the file names are used as key and there can be only one file with
    the same name except in the trash box. So, when you place in the inbox a file with
    the name identical to one of the files stored in another directory, it will not processed.
    SFSender.Directory=/tmp/sfsender
    The polling interval in milliseconds (default is 5000)
    #SFSender.PollingInterval=5000
    The retry delay after each failure in milliseconds (default is 5000)
    #SFSender.RetryDelay=5000
    The maximal retry count upon failures (default is 3)
    After the maximal retry count is reached, the message is moved as undelivered.
    #SFSender.RetryCount=3
    The number of dispatchers to send requests (default is 3)
    SFSender.DispatcherCount=1
    END
    Hope this helps.
    @Ravi: You may call me at +91 9844167672.
    Warm regards,
    Venki.

  • File Port Not Picking Up File

    Hello All,
    I'm trying to get a file sent from an external system to SAP. I created a file port. The inbound tab of the port has the full path of where the file will be after it's sent from the external system. The external system is a PC server and is sending the file to the folder no problem. However, the SAP file port is not picking up the file. This is an IDOC file I'm trying to send to SAP. In the file port I click "test connection" and I get a positive result showing "access is possible".
    I went into WE16 to manually bring the file in. I use the full path as in the file port plus the file name. I also enter the port name and try to execute. An error comes back saying "error opening file".
    In WE16 I use...
    <pc server>\directory\filename
    Any help as to why I can't get the file through the port or manually in WE16 would be greatly appreciated.
    Thank you.

    hi,
    have you seen below threads :
    Steps to create port in WE21?
    Steps for creating file port for inbound process!
    thanks,
    Edited by: bhavanisankar.solasu on Dec 21, 2011 6:02 AM

Maybe you are looking for