EOIO (File 2 IDOC scenarion) in 4.6c system

Hello Experts,
My client wants to process Exactly once in order message processing in SAP 4.6c system (inbound side)(File 2 idoc ).
I have read from some of the forum threads saying that, to implement this solution using PI, SAP system version WAS should be minimum 6.40.
Can you provide me your inputs for implementing EOIO message processing (File to IDOC ) scenario in 4.6c with / without using PI
Thanks
Sai

Question1:
you want to preserve the message order exactly, choose the Switch Procedure and enter the required number of queues with the new prefix.
The Switch Procedure is time-consuming and performance-intensive and is therefore only to be used in a running productive system.
       4.      Select Continue and schedule the SXMS_EOIO_REORG report to reorganize the queue by entering the required values.
The Switch Procedure status changes from inactive () to started (). The reorganization job analyzes the old queues according to messages available and creates corresponding stop entries in the new queues. The status also changes from started () to active ().
If the Switch Procedure is active, all new inbound messages are redirected to the new queue set. The reorganization job periodically checks the old queues for messages and deletes the corresponding stop entries in the new queues, as long as no more messages are found in the old queue set all stop entries are deleted from the new queue set.
If you manually delete the stop entries, the queues involved will be stopped with an error message.
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/9555d5e85613eae10000000a155369/content.htm
Question 2:
PI will not bother about what happend in ECC system.It will pass the messages to ECC queue and ECC will Handle EOIO.

Similar Messages

  • IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

    Hello SDN Gurus,
    The scenario I am working on is IDOC(PAYEXT & EUPEXR) --> XI (ABAP Mapping) --> Flat File (IDOC Structure).
    The IDOCS produced in Appl system may be in the following order
    PAYEXT
    PAYEXT
    EUPEXR
    PAYEXT
    PAYEXT
    PAYEXT
    EUPEXR
    I need them to be processed in the same order into flat file.
    The scenario is working good except for the serialization. So I did the following
    Created two entries in IDXQUEUE one for each message type with the same Queue name in XI system.
    Created a new rule for the queue and an associated function module. Used this rule in partner profile for both the message types.  I used the following link to create the above two steps.
    /people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
    The SAP system in based on WAS 6.4.
    I can see the queue name & EOIO in the inbound message header.
    I am getting a mapping error in ABAP program. If I inactivate the queue(in Appl system SAP ECC), I don't get any error.
    Does anybody had this problem earlier? Please advice.
    Thanks
    Srini Vaidyam

    I found an OSS note to resolve my issue. The note number is 1057573.
    Whenever the queue is activated, the sender system will not send the <TABNAM> field value in EDI_DC40 structure. This note addresses this problem.
    I found out this by comparing the results from SXI_MAPPING_TEST individually for the message that failed after queue is activated and the message that was successful if the queue is inactivated.
    Only thing I noticed now is even if you selected the radio button "Trasfer Immediately" in Partner profile of Appl. system, the messages are not sent. They are getting collected. So we need to manually push them out using WE14.
    This forum Rocks.
    Thanks. 
    Srini Vaidyam

  • Idoc not appearing in Xi system

    Hi experts,
    I have developed a idoc to file scnario but the idoc trgerred in the ECC system i snot comming to XI. I have done all the setting IDX1 and IDX2 and partner profile settings in ECC. the idoc status is 03 in ECC which says the idoc is sent to port successfully, but it is not appearing in SXMB_MONI in XI.  It used to work earlier. Is there any batch job or peogram does this transfer. what do i check?/
    thanks
    sankar

    Hi,
    Add the Logical System of SAP R/3 in Integration Directory as shown in the Blog and check Now
    The specified item was not found.
    And also check these Disscussions
    No service for system in Integration Directory
    No Service for System XYZ,Client 300 in Integartion Directory
    Regards
    Seshagiri
    Edited by: N V Seshagiri on Aug 7, 2008 8:16 AM

  • File-idoc     Unable to convert the sender service  to an ALE logical syste

    Hi experts
    iam working on file-idoc scenario ,iam getting the below error in sxmb_moni and RWB
    "Unable to convert the sender service  to an ALE logical system"
    i checked the partnetr profile, RFC(sm59) and IDX1 t codes.
    the connection is ok. but still i could figureout the problem.
    please suggest me
    Thanks
    vasavi

    Hi,
    Have u checked the logical system is added in the Sender Business service in the Integration Directory?
    Open the Buiness Service/System --> EDIT-ADAPTER SPECIFIC IDENTIFIERS
    then specify the logical system name.
    Go throgh the following link
    Troubleshooting  File-to-IDOC Scenario in XI.
    Regards
    Sridhar Goli

  • ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

    Hi,
    I got this error in FIle-IDOC scenario.
    ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
    There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
    I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
    Is there any other suggestions?

    Hi aarthi,
    I suggest u chk all d settings dat u hav done..
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    Step 6)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 7)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    Xi
    IDx5(Idoc check)
    SU53(authorization check)
    reward points if helpful...
    MenoN

  • File -- IDOC scenario using XI 3.0

    Hi
       I tried out a simple flat file to IDOC scenario using XI as the middleware and tried to post documents of type CREMAS03 on the backend R/3 system.
    Now, I see that there is an IDOC number generated in the XI layer by the IDOC adapter. This IDOC number is seen under <SAP:DOCNUM>XXXXXXXXXX</SAP:DOCNUM>in the
    Response-->IDOCOUTBOUND section of the pipeline in SXMB_MONI
    According to SAP documentation :
    <b>To enable you to select IDocs in the target system later on, the system transfers the message GUID and the IDoc number in the ARCKEY field of the IDoc control record.</b>
    Now, I do find the XI msgid given as arckey in the control record of the Inbound in the target R/3 backend system. But I cannot find the XI IDOC number being cross referenced in the control record of the IDOC in the R/3 backend.
    1.Is there a way to cross reference the IDOC number in XI with the IDOC number in the R/3 backend ( we have two different IDOC numbers, right ) i.e a IDOC number to IDOC number cross referencing in this File-->IDOC inbound into the R/3 system scenario involving XI
    2. In the XI box, do we get as a part of async.reponse from the R3 system, the IDOC number that is created within the R3 system ? This would serve directly as a cross reference. Or do we have to indirectly query EDIDC table in the R/3 backend with the arckey value = msgid in XI - to retrieve the IDOC number created in the R3 backend ?
    Thank you in advance for your time.

    Hi,
    Pls look into following link about Acknowledgement.
    http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
    Pls note that , you can't get/receive the Acknowledgement for Sender File Adapter. Because File System acts as an Async system. But you can get the Idoc response and you can write it into another file. For this you need to use BPM.
    Hope this helps..
    Regards,
    Moorthy

  • Conversion of XML Idoc to File Idoc

    Hi,
    My query is:
    I have an XI (PI 7.0) in between an SAP system and a file system. An idoc comes into XI. It needs to be conerted to a file idoc, ie, each segment needs to be separated by a new line. How can I achieve this?
    1. Do I have to create a java/ ABAP class?
    2. Is an adapter available which does this for me?

    Hi Tamoghno,
    1. No
    2. Yes, use the File/FTP and IDoc Adapters.
    Do a search on SDN on "How To ..." for IDoc and File scenario and you will find a plethora of them. You can also start at the WIKI page for SAP XI.
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
    Also try this:
    https://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
    Hopes this helps!
    Regards,
    John Ta

  • EOIO for IDOCs to XI

    Hi,
    My scenario is IDOC ---> xi ---> File.
    Need to implement EOIO(serialization) for IDOCs coming from ECC.
    Checked "Queue Processing" and assigned rule "FIRST_16_OF_MESTYP".
    When I send the IDOC using WE19, I get message "IDocs are stored in the queue".
    But, IDOCs are not coming to XI. Please help.
    Versions: ECC 6.0 & PI 7.0 SPS 13.
    Also, do I need to maintain an entry in IDXQUEUE table?

    Hi
    use similar thread
    How to implement IDOC Serialization(EOIO) using IDOC Adapter
    Re: Posting idocs in sequence in SAP from file (without BPM)

  • File- idoc, port in control segment not being populated

    Hi guys,
    I have a file->idoc scenario. Everything works fine, but the receiver port in control segment of idocs has no value. I'm surprised, because this is provided in the Idoc adapter so I thought it is taken from this parameter.
    Any ideas, what could be wrong?
    Thank you,
    Olian

    You pls set the indicator - Apply Control Record Values from Payload
    If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.
    If you do not set the indicator, all combinations of communication parties and services are handled as services without party.
    If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values
    http://help.sap.com/saphelp_nw70/helpdata/EN/96/791c42375d5033e10000000a155106/frameset.htm

  • FILE-IDOC, no message no IDOC

    Hi experts..
    iam working in FILE-IDOC scenario.  when the scenario is excuted , the file is picking and archiving in the given directory. but when i check in  SXMB_MONI the message is not cretaed and finally the the IDOC is
    not created in destination system.
    i cheked in RWB --adapter monitaring --the adapetr in sucess status.
    please tell me what could be the reason?
    Regards
    vasavir.

    Hii
    Place a file in the specified source location.
    once the scenario is configured correctly then the adapter picks the file based on the time specified in the pollinterval and process the file.and based on IDX1 IDX2 settings the file is posted to SAP R3.and in R3 check the idoc in WE05 or WE02.
    there you can find the status of the idoc.
    these links will help u for checking ur scenario and error handling :
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    Error handling in File ---IDOC Scenario
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
    Regards

  • File-IDOC Scenario

    Hi,
    My scenrio is File -IDOC.
    I had done Design & Configuration part.
    I am getting following error
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
    Kindly help me;.

    Hello Srikant,
       Refer the following weblog in section 5 Troubleshooting  File-to-IDOC Scenario in XI.
    You have to define logical system name for sender system.Do the steps which are specified in weblog you can able to overcome this error.
    Cheers
    Veera

  • File-IDOC

    Hi All,
    I am trying a file-IDOC scenario. When I execute the scenario, I get an erro msg in SXMB_MONI. The error msg I get is "Receiver service cannot be converted into an ALE logical system".
    Any inputs on this would be of great help.
    Thanks & Regards,
    Jai Shankar.

    Hi Jai,
    Please check the following:
    1. Give an ALE name for the sender system (file adapter) also.
    - Go to Integration Directory - > double click on your business system (for file system) -> services -> Adapter-Specific Identifiers..... Here if there is no logical system, Please do give the ALE Logical System name that is maintained in the SLD. if you are giving the Logical system name, do save and then activate the changes made.
    2. When you create a business service, goto the menu option Service->Adapter-specific Identifiers and mention the ALE configuration information details.
    3. At first we should check if our Logical System Name is correctly maintained in the SLD:
    - go to the SLD - Technical system -> Client number -> Logical System Name and make sure your business system name is there .
    4. Then we have import the LS name to the XI Directory:
    - go to your Business System -> Service -> Adapter Specific Identifiers.
    - import the business system name from the SLD using the "Compare with SLD" button
    - Activate the changes and you can check your if your configuration works.
    5. If none of the above is the cause... then probably you'll need to refresh the cache and still if it doesnt work you need to implement OSS note: 791181 (which deals with an error caused by a header mapping)
    Also Check the following blog.
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    I hope it helps......
    Regards,
    Abhy
    Message was edited by: Abhy Thomas

  • Exceptions in file-idoc scenario

    Hi Folks,
    I am developing a file-idoc scenario. What are the different exceptions I would be needed to handle apart from the following two identified?
    1. Mapping issue
    2. Problem in posting the idoc (SAP system may be down and others)
    Thank you

    Hi Raja,
    The errors an happen at following steps:
    1. Error while picking the file:File adapter error
    2. Error in mapping: error due to incorrect data, incorrect format, corrupt file etc.
    3. While posting Idoc: due to Incorrect userId password, due to structure not matching, destination system being down.
    Hope this helps.
    Regards
    Vijaya

  • ALE Settings For File-IDOC  Scenario

    Hi All,
    While Doing IDOC-File Scenario we have to do the Following Settings
    In XI
    1) Create RFC Destination towards R/3
    2) Create Port
    3) Load Meta data
    In R/3
    1) Create RFC Destination towards XI
    2) Create Port
    3) Create PF
    Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
    Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
    Clarify me these Confusions
    Regards
    Bopanna

    HI,
    for IDOC TO FILE
    We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
    There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
    i.e for FILE-IDOC
    1) No need to Distribute the modal view
    2) For partner profile Specify the INBOUND PARAMETERS
    FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
    We need to do the following settings in XI
    1)   Create an RFC Destination to the Receiving System in transaction code (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.Both should be succesful
    2) Create Port Using Transaction Code  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 XI towards R/3
    e)   Save
    3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
    a)  Create new
    b)  IDOC Message Type
    c)  Enter port created in IDX1
                        SETTINGS IN SAP R/3
         We need to do the following settings in R/3
         Logon to Sap R/3 System
    1)   Create an RFC Destination to XI in transaction code  (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.Both must be succesful
    2)   Create communication Port for Idoc processing Using Transaction(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)
    d)   Enter the RFC Destination created in SAP R/3 towards other system.
    e)   Save
    3)   Create Partner Profile with Inbound Parameters (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
         Then Save
    e)   Select Partner no. and LS which were create above
    f)   Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
    g)   Select Message type
    h)   Double click on Message Type and Then Enter the details  for Message Type and Process Code.
    I)   save
    4)   In Transaction SALE, Create Logical System
    a).  Go to Basic Settings-> First Define logical systems
         and then assign logical systems
    b)   Double click on Define the logical systems
    c)   Give data for your Logicaal System and Name
    d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e)   Assign the logical system name to the client
    ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
    PLZ REFER THE LINK BELOW.
    PLZ REWARDS THE POINTS
    VIKAS JAIN
                                                                                    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
    Edited by: vikas jain on Jan 22, 2008 11:49 AM

  • Peculiar behaviour in picking file from FTP in File-IDoc scenario

    Dear XI Expert,
    I have successfully completed configuration of FTP --> XI --> IDoc scenario. I have noticed a peculiar behaviour in picking the file from FTP. I placed a file on FTP and activated File Adapter with poll interval '60' secs and processing mode as 'Archive'. For the first time it has picked the file with expected behaviour and IDoc got posted to SAP successfully. But when I placed file for the second time and when refreshed the FTP directory, immediately file got archived without waiting for 60 secs. But in sxi_monitor I could not see any activity of processing this scenario. Surprise is that, file got archived in target directory. This goes on and on... without registering any activity of processing the message in Message monitoring.
    In adapter monitoring it shows the message as described below:
    <i>History:
    2006-05-09 22:57:25 : Processing started
    2006-05-09 22:57:25 : Error: Processing interrupted due to error: FTPEx: No such file
    2006-05-09 22:57:24 : Processing started
    2006-05-09 22:57:24 : Error: Processing interrupted due to error: FTPEx: No such file</i>
    For your information my SAP XI system is on SP16.
    Please find below the parameters of sender adapter:
    <i>Quality of service: Exactly once
    Poll interval: 60 secs
    Processing mode: Archive
    Connect Mode: Per File Transfer
    Transfer Mode: Binary</i>
    Can anybody help me out in resolving such a problem in this scenario?

    Hi Jayakrishnan,
    Thanks for your reply.
    Once again the same problem is noticed. i.e., for the first time when file adapter is activated the file got picked, activities were logged in monitoring and IDoc got posted to destination system. For the second time when file is placed, before 60 secs got completed the file is picked and archived in the target directory. No activities in monitoring are logged.
    I have tried it checking the message at adapter level, but it is showing 'No results' (even in the case of successful pick of the file for the first time, not even it is showing other file adapters).
    I was not able to understand where the problem could lie?
    Regards,
    Suraj Kumar

Maybe you are looking for