IDOC Issues

Hi,
We have one IDOC with some Enhanced fields in R/3.
When ever we trigger the idoc from R/3 the inbound paylod in MONI  is comming correctly but when we check the received file in the AL11 of XI Server means we are missing so many fields in that file
1) We are able to see the success in MONI
2) We took the Inbound Payload from MONI and tested in Message mapping. It's working fine
3) We tested in Interface mapping also
4)We checked in Receiver Channel also. this is also fine
What may be the real problem here.
Where and all i can check the possibilities to check this problem
Regards
Suman

Hi Suman,
ask your xi basis guys to create a folder for you for outputting the file.....give the complete folder path in recever file adapter and do not use AL11directory.......save and activate it.............now re-run your scenario...........now see your target file is getting generated or not......if not, then go to RWB - comm channel monitoring and remove your recever file adapter error...............and if your target file is generated, see its contents................
now your error should be resolved................
Regards,
Rajeev Gupta

Similar Messages

  • IDOC ISSUE full point assigned

    Hi all
    I m facing problem to upload data through idoc.the scenario is like we receive electric meter reading in flat file format. And to upload that data JAVA code is written which will create an IDOC FILE this authorization is only give to 2-3 person in organization and to basis guy also as user changed it’s password in SAP and in JAVA the java code is not going to create the IDOC file and data is not going to upload. after changing user password in sap system ,user not able to upload the data.
    ISU_MR_UPLOAD01 is the idoc file generated. So is there any authorization issue, password issue how to see and view IDOC IN SAP, can any one help me out into this.
    The error with java throws is as;
    1ST ERROR IN TRACE FILE
    ERROR file opened at 20061109 133610 India Standard, SAP-REL 640,0,59 RFC-VER 3  MT-SL
    T:2736 ======> User TR has no RFC authorization for function group SYST .
    T:2736 <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
    2ND ERROR ON COMMAND PROMT
    C:\j2sdk1.4.2_07>cd bin
    C:\j2sdk1.4.2_07\bin>java sandsupload
    Creating IDoc...Exception in thread "main" com.sap.mw.idoc.IDoc$Exception: (2) I
    DOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ISU_MR_UPLOAD01
    " is unavailable.
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:233)
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:187)
            at com.sap.mw.idoc.jco.JCoIDoc.createDocument(JCoIDoc.java:10521)
            at sandsupload.main(sandsupload.java:35)
    the part of java code
    try {
                //create a JCo client pool
                JCO.addClientPool( "MyPool",    //pool name
                                   3,           //maximum pool connections
                                   "333",       //SAP client
                                   " TR",    //user ID
                                   " XYZ",  //password
                                   "EN",        //language
                                   " 1.1.1.1   ", //app server host name
                                   "00" );   //system number
                //create an IDoc repository
                IDoc.Repository idocRep = JCoIDoc.createRepository("MyIDocRepository", "MyPool");
                //create a new and empty MATMAS02 document
                System.out.print("Creating IDoc...");
         Line where it shows error
                IDoc.Document doc = JCoIDoc.createDocument(idocRep, "ISU_MR_UPLOAD01");
                //get the root segment from the document
                //The root segment does not contain any fields or data. It is only
                //used as the standard parent segment and won't be transmitted when
                //the document is sent to an SAP system.
                IDoc.Segment segment = doc.getRootSegment();
                //create and add a new and empty child segment of type E1MARAM
                //and fill the segment data

    Seems like the error is because the user passed through the JCO call does not have the necessary authorizations...in SAP. Trace the authorizations for that user and grant what is needed... in particular the functions about the IDOC setup and structure used by the repository...
    Enjoy

  • IDOC ISSUE-10/10 POINTS ASSIGNED

    Hi all
    I m facing problem to upload data through idoc.the scenario is like we receive electric meter reading in flat file format. And to upload that data JAVA code is written which will create an IDOC FILE this authorization is only give to 2-3 person in organization and to basis guy also as user changed it’s password in SAP and in JAVA the java code is not going to create the IDOC file and data is not going to upload. after changing user password in sap system ,user not able to upload the data.
    ISU_MR_UPLOAD01 is the idoc file generated. So is there any authorization issue, password issue how to see and view IDOC IN SAP, can any one help me out into this.
    The error with java throws is as;
    1ST ERROR IN TRACE FILE
    ERROR file opened at 20061109 133610 India Standard, SAP-REL 640,0,59 RFC-VER 3  MT-SL
    T:2736 ======> User TR has no RFC authorization for function group SYST .
    T:2736 <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
    2ND ERROR ON COMMAND PROMT
    C:\j2sdk1.4.2_07>cd bin
    C:\j2sdk1.4.2_07\bin>java sandsupload
    Creating IDoc...Exception in thread "main" com.sap.mw.idoc.IDoc$Exception: (2) I
    DOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ISU_MR_UPLOAD01
    " is unavailable.
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:233)
            at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.<init>(JCoIDoc.java:187)
            at com.sap.mw.idoc.jco.JCoIDoc.createDocument(JCoIDoc.java:10521)
            at sandsupload.main(sandsupload.java:35)
    the part of java code
    try {
                //create a JCo client pool
                JCO.addClientPool( "MyPool",    //pool name
                                   3,           //maximum pool connections
                                   "333",       //SAP client
                                   " TR",    //user ID
                                   " XYZ",  //password
                                   "EN",        //language
                                   " 1.1.1.1   ", //app server host name
                                   "00" );   //system number
                //create an IDoc repository
                IDoc.Repository idocRep = JCoIDoc.createRepository("MyIDocRepository", "MyPool");
                //create a new and empty MATMAS02 document
                System.out.print("Creating IDoc...");
         Line where it shows error
                IDoc.Document doc = JCoIDoc.createDocument(idocRep, "ISU_MR_UPLOAD01");
                //get the root segment from the document
                //The root segment does not contain any fields or data. It is only
                //used as the standard parent segment and won't be transmitted when
                //the document is sent to an SAP system.
                IDoc.Segment segment = doc.getRootSegment();
                //create and add a new and empty child segment of type E1MARAM
                //and fill the segment data

    Hello,
    If the IDoc is creaetd in systen with error or with anty status,you can view it via we02 transaction.
    But if it's autorisation issue,i guess IDoc will not get created.
    Thanks.

  • Regarding Idoc issue

    Hi Folks,
    I have triggered the Idoc from R/3 to XI.
    For the statue 30: I can see the text as:
    Receiver exists , No filters , No conversion , No version change
    Please let me know the meaning of this.
    can we use any code page conversion parameter in ALE to convert the data.
    Issue is like:
    In the Idoc I am getting the data correctly. But when the Idoc sent to XI with the help of batch run it went with some invalid character set. (I have checked inbound message payload in XI)
    I have re-triggered the same Idoc manually using the logon language as chenese and now it went to XI with the correct Chinese character set.
    Please guide me why it is transferred to Xi with Invalid data for the first time ?
    Thanks,
    SPMD.

    Hi ,
    I will explain you oit clearly.We are sending idoc to XI.
    we have 2 cases here:
    1st case:
    Idoc triggered for the first time and in data segements we can see the data as:
    name : ³£ÖÝÊа²½°Ù»õÓÐÏÞ¹«Ë¾ --this is in data segment.
    In XI (Inbound payload) we see the same data:   (Inbounb payload )
    My doubt is when the same idoc triggered for the first time the data conversion is not done and when the same Idoc is triggered manually the data conversion happend and we se the correct data in chinese format.
    Appreciate your help.
    Thanks,
    SPMD

  • IDOCs issue in XI

    In our IDOC -> XI -> IDOC scenario, we are facing an issue when a large number (~4000) of IDOCs are sent to XI system at the same time.
    The source SAP system sends the IDOCs to the XI system using a system user. When a large volume of IDOCs are sent at the same time, this user takes up all the dialog processes in the XI system.
    The system eventually becomes slow and needs to be restarted.
    One message gets created per IDOC in XI. The mapping between source and target IDOCS is simple. There is no issue with small number of IDOCs.
    Request your suggetions/inputs in this case. Could we make the IDOC process to run in background in XI to avoid this situation?

    Have a look into this thread to know how to improve performance when large IDOCs are transferred:
    Processing of huge IDocs ...
    You can also opt for IDOC packaging : /people/michal.krawczyk2/blog/2007/12/02/xipi-sender-idoc-adapter-packaging
    Regards,
    Abhishek.

  • Purchase Order Idoc Issue - PORDCR103

    Hello Experts,
    I have one PO and 5 PO Items in my source. I sent Idoc(PORDCR103) to SAP from SAP BODS4 successfully and I was expecting to see 1 PO with 5 items But I saw 5 PO's were created with 5 items each instead of 1 PO with 5 items. Please find attached my Job screenshots.
    Any Idea on this.. Please can anybody share your experience.
    Thanks...Mohan

    This was because of different purchase group's in source data for all other 5 po items. I have resolved this issue by make same purchase group for all 5 po items.

  • Purchase order idoc issue

    Hi,
        I am facing a issue with an inbound purchase order change IDOC (message type: PORDCH).
    I am getting the following error: FM VENDOR_MASTER_DATA_SELECT_15 ; no partner functions found for vendor VENDOR_MASTER_DATA_SELECT_15 1.
    The vendors are configured such that they dont need a partner function. The suprising part is that the same message type idoc from the same vendor got succesfully posted a few days back and a few days after the issue was found, which means the error doesnt occur every time.
    Any input is highly appreciated.
    Thanks,
    Aparna.

    Hi Aparna,
    I want to make changes in an existing PO through an inbound idoc. I am using idoc type PORDCH01 and message type PORDCH, process code BAPI. But I am getting an error "Characteristic does not exist in operating concern".
    Can you please explain how u are using idoc type PORDCH01??
    Thanx in advance,
    Shaleen

  • Purchase Order Outbound Idoc issue. Message Type ORDER

    Hi Experts,
    I am having issue with outbound IDoc generated from Purchase Order.(Message Type ORDER and Basic Type ORDERS05)
    Issue is when i create PO idoc Segment  E1EDP01 and field ACTION populates as 001 this works fine.
    Now when made any changes to the purchase order.* PO trigers one more EDI - Idoc. but the ACTION field is stil as 002.*
    Could any tell me how to fix this.
    Cheers...Gopinath.

    Hi,
    Thank you.
    I have found the issue and fixed.
    Below three setting was missing same has been done in Partner Profile now ok.
    Message type u2013 ORDCHG, Processing Code u2013 ME11 and Change flag On.
    Cheers..Gopinath
    Edited by: Gopinath A.R on Oct 8, 2009 3:14 PM

  • Payext Idocs Issue

    Hi,
    I am generating payext idocs off the back of a payment run (F110). The issue that I have is where I am paying a supplier with multiple invoices, that the individual invoices are all included in the IDOC. When the bank statement is returned to us, for this type of example, the bank statement is delivering all of the invoice references in the Payment Notes section. I am being informed that this is due to my system sending out segments E1EDP02 009 / 010. I am also informed that I need to make changes in FBZP - "Payment methods in Company Code". So far my settings (under payment advice control) here are:-
    1. Note to payee lines on form - None
    2. Payment Advice output according to number of lines - always payment advice
    Also in the DME I am using program RFFOEDI1 and have amended the variant in the output control section to only generate 2 "number of " invoice details.
    Is anyone able to advise please.

    Hi,
    This thread has been created some time ago and recieved no response. Can you please close if you feel this issue/query has been resolved in the meantime. If it has not then please provide additional information in relation to your query. By providing updates to your thread it moves you thread to the first page of thread and increases visibility and possiblity for the multiptude of experts in SDN Forums to offer their support.
    Therefore please update with more information or close thread.
    Thank you for your assistance.
    Regards,
    Brendan.
    (ERP FI/CO SDN/WIKI Moderator)
    http://wiki.sdn.sap.com/wiki/display/ERPFI/ERP+Financials

  • Idoc issue - canbe fixed with enhancement?

    Hi idoc Gurus,
    I have issue related to idoc.
    We have extended the DEBMAS with one custom segment(Z1KNA13).
    Custom segment(Z1KNA13) has three fields. one of the field is to store customer's second address line(cust_address2).
    When someone changes the customer's second address line in Mainframe. It updates the same in SAP.
    And in WE05 under segment Z1KNA13
    Field                                         Value
    cust_address2                       B. P. road
    But if someone deletes the customer's second address line in Mainframe, it does not deletes the same in SAP.
    And in WE05 under segment Z1KNA13
    Field                                         Value
    Even field "Field" is empty.
    Could anyone help me to figure out, where the problem could be.
    Thank you so much in advance.

    Hi,
    Could you please clarify if my understanding is correct..
    You are receiving the IDoc from the Mainframe...When you change the Customer Master in Mainframe then the MAinframe sends an IDoc to SAP with the change vales....the issue when deleting the record might be from mainframe side wherein they do  trigger the IDoc exchange interface only for change and not for delete...if that is the case then you may have to extend your Idoc with another update indicator which states whether to change or delete the address record...
    and based on the update indicator you can update or delete the record in the IDoc processing in SAP end...
    Why I guess this is because you have sadi that the value in the IDoc field is empty..so if mainframe doesnot send the value in IDoc you will not get the value in SAP also...
    Hope you find this helpfull...
    Sitakant...

  • IDoc issue

    Hi,
    i'm trying to test a scenario from idoc  to idoc.Partner profile is defined properly.
    But when i post through runtime work bench i'm facing a issue.PFB error
    error category  - IDOC_ADAPTER
    error id - ATTRIBUTE_IDOC_METADATA
    When i try to load metadata(PI box) i'm unable to load the IDoc its showing as Segment versions could not be read.
    Kinldy suggest on the same.
    Regards,
    Anitha M

    Anitha,
    It seems some issues with the idoc itself. Check in SAP whether it is released properly and dont have any errors. You can also see some info on this error here:
    Error importing Idoc - Unable to read segments
    Regards,
    ---Satish

  • LOIPRO01 outbound idoc issue

    Hi All,
    When I release the production order, Idoc need to be send to external system.
       I have extended LOIPRO01 idoc(for Production Order)and called RCCLORD program using SUBMIT in user exit include ZXCO1U01 for creation of IDoc and it is successfully dispatching to External system.
    My issue is after releasing the production order(CO02) and sending the Idoc from R3 to external system port,I need to mark the radio button  'Sent to WM'.
    SO I need to write the code based on the Idoc status is 03. But I am not getting the idoc number or EDIDC table values in my include.
    Anybody faced similar kind of situation,is there any way of solving this, please let me know.
    Thanks in Advance....
    Ranjith.

    Hi Rajgopal,
    use the latest version idoc type(basic type)for example for orders we have orders01,orders02,orders03,orders04,orders05,it's better to use the latest version.
    else
    u have to extend the stanard idoc with those additonal fields and write the code in user exit to populate them.
    Regards,
    nagaraj

  • IDoc issue - update address data vendor

    We make use of iDocs to interface our vendor master data from an AS/400 system to SAP ERP.
    But we now have an issue with the address data updates of the vendor.
    If we check the vendor with XK03 - Environment - Field Changes:
    Date: 12/02/2010
    Field: City
    New: LOUISVILLE KY 40290-1076
    Old: CINCINNATI OH 45274-0124
    But in XK03 the field city still contains: CINCINNATI OH 45274-0124 (and not the new updated city)
    Table LFA1:
    LFA1-ORT01: LOUISVILLE KY 40290-1076
    LFA1-MCOD3: LOUISVILLE KY 40290-1076
    Table ADRC:
    ADRC-CITY1: CINCINNATI OH 45274-0124
    ADRC-MC_CITY1: CINCINNATI OH 45274-0124
    If we check WE05 ---> green flag, so no error while updating vendor master data (+ correct city is in E1LFA1M)
    This is not always an issue - so not all vendors have this issue.  If we reinterface the same vendor later, the address data is upated without any issue.
    How can this be solved?
    Kind regards,
    Lieselot...

    Check if there is some custom code concerned or not.
    If not, check sap notes, then ask sap support to help you solve the issue.
    Otherwise custom code may handle incorrectly something, but I can't tell you what!

  • IDOCs issue

    Hello,
       When we load data from R3, everything looks good. But when we load data from flat files, the IDOCS get stuck with status 64. We need to manually execute these IDOC's and after which load goes geen. But it happens all the times when we load flat file data and only in development box. Can you please guide me on how to fix this issue!
    Thanks.

    I got your question . Please find the suggestion as per my understanding .
    In case of R/3 background jobs are there which process the IDOCS which are there .
    But in case of flatfiles it was missing . So better ask the Basis team or the team which looks for the
    scheduling of the jobs .
    So may be you can ask the Basis team or ABAP team who can develop a BDC in a program which will be scheduling by jobs and can pull the data .
    Assign marks is the best way to appreciate help

  • Payext Idocs Issue - E1IDPU1

    Hi,
    I am an Idoc novice, but stumbling around trying to find my way.  I have configured my system (ECC6.0), to send payments to our group IHC, however I have an anomoly that I cannot figure out. 
    It seems to refer to reference details (BKREF) in the master data (but i may be following a red herring).  If I pay a vendor with this field populated I have an idoc that works and E1IDPU1 has a hierarchical structure, however, if I pay a customer, E1IDPU1 is not structured in the same way and the child segments follow immediately, so my idoc fails, with status 26
    Can anyone advise areas that I need to look at to troubleshoot, as I am at a loss where to look.
    Any help would be greatly appreciated.
    Thanks
    Jackie

    Hi Jackie,
    The issue decription, idoc status 26 and sub-segments not aligned, suggest that the IDoc failed due to syntax error. Standard code doesnt cause any syntax error in forming the segments of the idoc.
    Here syntax error with the Idoc means that the structure of the Idoc was not according to the standard. This happens wheenever there is a user exit implemented to append a segment or sub segment to the idoc structure.
    My suggestion would be to check for any user exit implementation and see if there is any incorrect coding that modifies the idoc structure. The exact segment which causes this syntax error would be mentioned in the status log of the idoc.
    Hope this helps!
    Best regards,
    Sidhartha

  • Idoc issue in AFS-Retail.

    one of our customers require the following criteria for VAT & Surcharge Calculation:
    AS PER SAP
    Customer's requirement
    TAXABLE AMOUNT
    1695.83
    TAXABLE AMOUNT
    1696.37
    VAT-5.50%
    93.79
    VAT-5.50%
    93.30
    S/C-10% ON VAT-5.5.%
    9.38
    S/C-10% ON VAT-5.5.%
    9.33
    BILL AMOUNT
    1799.00
    BILL AMOUNT
    1799.00
    Sales process:
    Sales done in third part software then via an XML file billing gets uploaded in SAP by 'Z' transaction.
    Which means Release to Accounting is not done after VF01.
    They do not do VF01 they directly post their billing in accounting by 'Z' Transaction.
    More Details
    AFS & Retail= 2 Servers
    Interface = Idoc
    Third Party software at retail stores.
    Issue: When we wrote a new sub-routine in pricing procedure, everything started working good but Idoc processing Failed. When we remove that routine Idoc works fine.
    Error thrown by SAP:
    We checked the SAP Note 506040 also but could not find any solution. Plz help..
    Regards,
    Abdul Wahab

    Idoc issue solved.
    .Thanks for your valuable inputs but the issue was due to the inconsistency in data.
    an implicit enhancement was there which was changing few values in some tables but not in all the related tables.
    so the above mentioned ERROR came.
    But now the data is consistent and no IDOC error is there but while release to accounting( from a Custom program ) still the same old values are sent to accounting.
    We are on ECC 6.0 so the note number is not valid for us..
    Regards
    Abdul Wahab

Maybe you are looking for

  • How to make my waveform in control and design simulation run continuously?

    Hi all, i m a begineer of Labview and have some question to ask. I am using the Labview to design and implement a controller for FOPTD system, but i found that the waveform in the "control and simulation loop" is not running continuously. I mean it k

  • Give us a way to get rid of the Home View screen after closing last document

    After closing the last open document, a new window pops up. Please let us disable this. It's bad in a production environment, gets in the way.

  • SAP PM stand-alone with Baan ERP ?

    Does anyone have experience with implementing SAP PM module with Baan ERP ? I don't think that this is a good idea at all, but I just wanted to check if someone already did it, and how much it did cost. Many thanks for your feedback. Best regards, He

  • Installing Application Server in RHAS 2.1

    Hi Guru's I want to do install Application Server on RHAS 2.1 to RHAS 2.1 what are the pre requisites are required can u tell me please. including patches.

  • No Sun application server installes

    I've installed java sun studio creator but because of i've to use a proxy to go in internet, installation program didn't install the application server. Someone knows flags or parameter that i've to use to indicate to the installation program the pro