Idoc  ERROR IN WE19

Hi SAP gurus,
          i had a problem in IDOC..i am using the message type <b>CREMAS.CREMAS03</b>
I designed the <b>IDOC-XI-JDBC </b>scenario. Using <b>BD14 </b>i posted some idocs to XI. in sender side r3, idocs is in green color, <b>i received the idoc in XI also</b>. its not there in sm58 of XI .. its is there in <b>we02.. its shows red color</b> i used we19 to do something.it was not happening.. But in <b>SXMB_MONI.. i am unable to see the idoc</b>..what was the error.. How to solve this
please send you ideas ASAP.
regards
kumar

hi Kumar,
WE 19 is used to send the test data ..however, in ur case it seems the ALE settings are not done on XI and R/3 side.Just check if u have done all the f following steps on both  ends.
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.
In SLD – System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
Ashwin M
Reward if helpful

Similar Messages

  • IDoc Error 51 - Make Entry in All Required Fields

    hi,
    I am using a scenario where an idoc is being posted into an R/3 system from a legacy application. For some reason I keep getting Idoc error 51 (Document not posted).
    Once I drill down further, the specific error states "Make entry in all required fields". Have checked to make sure all mandatory fields have been mapped and proper constant values have been specified.
    But cannot seem to get rid of the problem. Could anybody help out in determining how else to troubleshoot this and identify the possible cause?
    thx,
    Manpreet

    Manpreet,
    What IDoc Type you are trying to post ? One way is debugging the inbound function module using WE19. The second option is talking to a functional consultantor who worked, what fields are needed for that particular IDoc.
    I wouldn't care much about whether the IDoc is posted or not because, it is the ABAP ALE/EDI consultant's job to do that. The only way XI Developer is concerned is when it is not posting, ABAPer would tell what's missing.
    Hope this info helps.
    regards
    SKM

  • IDOC error using PREQCR102

    Dear All,
    I am looking for some help in the below issue.
    We have an inbound IDOC scenario, we are using PREQCR102 IDOC type to process incoming PRs.
    I still receive errors during the IDOC test in WE19.
    The error refers to "Enter Plant" and "Enter Quantity" although these fields have a value in the segments.
    I received hints that I incorrectly use segment E1BPMEREQITEM and should use E1BPMEREQITEMIMP. However when populating E1BPMEREQITEMIMP I got the same errors and in addition I receive an error(Maintain services or limits for Item 00020) related to item 20 which is not in my IDOC at all.
    I attached my IDOC contents hope this helps.
    Thanks in advance for any help.

    For the notes, the solution was to add requisition item number to some additional segments(like delivery address and some other) as technically this is required in SAP.

  • Idoc error (Account vendor no. is currently blocked by user user name )

    Hello ,
    I am sending a cremas idoc from external system (XI) to R3
    But the idoc doesnt get posted.
    It throws the following error 51
    Account <vendor no.> is currently blocked by user <user name(login id for R3)>
    I tried resending this idoc using tcode we19 and was successful in testing it
    However, when i try sending it through XI, it gives me the error
    Does any one know how this can be solved?
    Regards,
    Roshani

    Hi,
    Please make sure that no more screens are open while trying to send the idoc and try again after you get succes from WE19 , It should be posted.
    Also check the thread it says in sm12 if there is any lock entry delete it.
    Error :Account 1000 is currently blocked by user SAPUSER
    Thanks!
    Edited by: sudhir tiwari on Nov 21, 2008 1:07 PM

  • Resolve IDoc Errors

    Could anyone define the ways in which IDoc errors are resolved?
    Based on my understanding, any IDoc processing error (inbound or outbound) creates a pre-defined or custom workflow that eventually leads to the modification (if necessary) and re-processing of the IDoc.

    Hi Kevin,
       You can resolve the Errors in IDOC processing in different ways.
    In Outbound:
    Status     
    29           Error in ALE Service (Problem can be in the Partner profile settings)
    30           Idoc ready for dispatch (Execute the Report RSEOUT00 )
    26           Syntax error in IDOC (When IDOC Data records are created properly)
    We can use the Tcode BD87 to monitor the idocs and Reprocess the Failed idocs
    In Inbound Processing
    Status
    51         Application doc not posted (When IDOC contains data that cannot be updated in the receiving system. Such as integrity errors, Missing mandatory fields etc.
    Display the Application log to find the errors.
    We can use IDOC test tool WE19 and execute the inbound processing using the inbound Function module in Debugging mode.
    56   or 65  : Check the Partner profile settings.
    62 : Application doc has to be posted using the report RBDAPP01
    Hope this info  would help you.
    Regards,
    Varma

  • IDoc error In case of ERS procedure, please enter terms of payment

    Hi,
    I tried to use BAPI_PO_CREATE1 to post purchase order. However, I encountered this error.
    IDoc error In case of ERS procedure, please enter terms of payment
    I passed the payment term in IDOC PORDCH. Segment E1BPMEPOHEADER-PMTTRMS has value filled out. This value is passed into the BAPI correctly but for some reasons, it got cleared out in the BAPI. Any ideas or suggestions would be greatly appreciated.
    Thanks

    Check
    BAPI_PO_CREATE1 -  E 06 436 In case of account assignment

  • IDoc Errors in ECC

    Hi Experts,
    what kind of IDoc Errors can occur in ECC for the scenario :
    ECC sending <b>PO</b> to Ariba(E-commerce hub, using third party adapter) and in receiving back <b>Order confirmation</b> from it.
    Thank you,
    <b>MK</b>

    Hi,
    This depends on the design and landscape and also Disaster Recovery or High Availability Plan.
    some hints:
    1. Connection Problem: Because of timeout , unavailability of the Receiver system.
    2. Data Problem may cause you the error in IDoC posting [ probably functional/Business Team should look into this]
    3. User ID and Password Maintenance - it may hit sometimes
    4. If any pre-requisite process is required to process this IDoC, then problem in the pre-requisite process will lead the problem
    these all kind of problems you may face..
    Rgds , Moorthy

  • File to IDOC - Error Inbound -56

    Hi,
       I am doing file to Idoc. (CREMAS01).. My scenario in
    RWB is successful. But in R/3 it is shwoing IDOC
    error :"EDI: Partner profile inbound not available".
      I created Partner Profile in R/3(logical name of BS-
    sender file). Still is shwoing Error.
    Regards,
    Mukharji
    Message was edited by: Mukharji T

    Hi Mukharji,
    I hereunder give you the step by step procedure for File to IDOC scenario.  Cross check whether you have done all these:-
    SLD
    1) Create a Product/Software Component
    2) Technical System pointing to R/3 system
    3) Business System for the above technical system
    In the Repository
    1) Import the Software component created in the sld
    2) Create a namespace,
    3) import the idoc and then create sender data type/message type etc and mapping
    4) Mapping Rules is depends on the requirement
    In the Directory
    1) Create a Scenario /import the business system
    2) Create Receiver/Interface determination
    3) Create communication channels for sender and receiver
    4) Sender Agreeement and Receiver Agreement.
    Then the file adapter configuration is depend on the input file format.
    Also you need to have Logical destionation created in the XI , and the IDX1 entry
    In R/3 Port, Partner profiles etc should be created
    Have a look into this document~
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    While doing an File -> XI -> IDoc scenario, The Points to noted are:
    1. You don’t need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
    2. You import the IDOC and use the same in your mapping.
    3. In this configuration note that you will need a sender agreement for the file.
    4. In this configuration note that you will also need a receiver agreement for the IDOC.
    For any File -> XI -> IDoc scenario ref:
    /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
    Hope this helps you.
    Regards.
    Praveen

  • Incoming IDOC Error "No batch input data from the screen SAPMV45A 4001"

    Hello ,
    The Incoming IDOC with Message type 'ORDERS' is triggering the error message "No batch input data from the screen SAPMV45A 4001" with message no 00344 . There is an SAP note 785000 to handle this type of error message which has been already implemented. Still we are encountering few IDOC error's  at the time of sales order creation. The IDOC reaches status 51 throwing the error which is again reprocessed through BD87 .
    We are unable to replicate the similar scenerio in Development & Testing systems as it works fine.
    Can any one kindly advise how to eliminate the error "No batch input data from the screen SAPMV45A 4001" message at the time of Incoming IDOC processing.
    Thanks in advance.
    Best Regards
    Sateesh

    Dear Sateesh
    Check this link where the same topic was discussed
    [ VA01/VA02: batch-input error in IDoc processing|http://www.sapfans.com/forums/viewtopic.php?f=21&t=313032]
    thanks
    G. Lakshmipathi

  • IDOC error while receiving

    Hi Friends,
    In my scenario, I have to receive P.O. message from partner in to my R/3 system.
    I am using PI 7.1
    When partner is sending me message I am getting error , "Only asynchronous processing supported for IDoc adapter outbound processg" in SXMB_MONI
    I tried to find solution on sdn, and I got 2 related foroum,
    Idoc Error
    Re: No receiver could be determined. (File to Idoc)
    But from this also I am not sure hw can i solve this error.
    Please Suggest.
    Thanks & Regards,
    Brijesh Soni

    Hi
    For Error Only asynchronous processing supported for IDoc adapter outbound
    IDOC adapter support asynchronous only,
    Check Quality of Service in your sender adapter. Should be EO or EOIO, not BE.
    This thread had same problem and resolved :
    Re: No receiver could be determined. (File to Idoc)
    In Your case QOS is BE. Plz check in your CC if and BE is by default..
    If you use BE, HTTP expects a Response back and as IDOC does not support BE, you go the earlier error.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    Regards
    Abhishek
    Edited by: Abhishek Agrahari on Jan 21, 2009 3:14 PM

  • Thousands of IDOC Errors

    Hi there,
    I have recently configured workflow using SWU3 - Now suddenly there are about 10 000 new work items in everyones inbox - All related to IDOC errors.
    I have made sure that the workflow administrator is set to a specific user, and in WE46, the IDOC administrator is also set.
    Most of the wor-items are back-dated to about a year ago, way before the workflow was configured.
    Firstly, why are all these appearing now?
    Secondly, how can I get rid of them, or at least isolate them into only one persons inbox?
    This is on our test system, so there is no need to investigate any idoc errors...

    This is happening because you have made some program run in background while configuring SWU3 most probably the deadline program.
    You can get rid of them by checking the Workflow Log and then investigating from where agents are getting determined and accordingly changing the agents to a particular user Id.
    <b>Reward points if useful</b>

  • IDOC Error V1 042 - Sales document X is currently being processed by user X

    Hello Experts,
    I am using the IS-Retail solution of SAP and I am facing a IDOC Error which keeps the IDOC in Status 51. I traced the Error Message and it was V1 042. I am using an Inbound IDOC 'SHP_OBDLV_CREATE_STO01' to create the STOs (Deliveries) using the POs and there is a locking issue of the PO giving error message 'Sales document XXX is currently being processed by user XXX'.
    I have created a backgroung job using a program to post the STOs using IDOCs that picks up multiple files from Application Server and processes them one by one. Now when 2 or more files use the same PO then this error occus.
    I added a couple of minutes of wait time between the file processing but that did not help.
    Please let me know if you have faces same situation and what solution did you apply.
    Regards,
    PS

    Hopefully you have fixed this by now, but for anyone else who might be looking at this problem.  We had this problem and we had the 2 programs check to see if the other was already runing.  If so the program would submit itself for a number of minutes, different for both programs, and then exit.  We also, and just before this, checked to make sure that there were not 2 of the running programs running and if so to exit.  This was necessary because re-scheduling could put a program in conflict with itself.  I hope that this may help someone.  We used the join V_OP and searched for the program name, not the job name.
    Kevin

  • IDOC error in production server

    Hi everyone,
    I'm getting this error, when users trigger an Idoc:
    Error while writing IDoc to file
    Message no. EA084
    Diagnosis
    The IDoc was to be written to file
    cocca3301\interface\output_idocs\1120549.txt
    That was not possible because no authorization for writing to this file.
    Procedure
    Please inform your system administration.
    Anyone has seen this before? in development and quality servers didn't happen this...
    Thanks in advance. Helpful answers will be rewarded.

    Not at all, I was talking with basis administrators about this problem for a long time. I'm pretty sure that it's all about folder permission. I think it's a matter of system, not SAP. But they said that's not the problem... I'm not 100% confident with that answer.
    But, in order to keep idocs running, i found program RBDAGAIN, that reprocess the failed idocs. I put it into a job every 30 minutes. That solves my problem "temporary", until i solve the real problem.
    I advice you to talk with your system administrator and/or basis, and check the group permission for the folder you are trying to put your files. If it works, please let me know.

  • Missing IDoc and recurring IDoc errors

    Hi,
    I would like to ask for a help or any ideas on below case.
    We encountered almost everyday a number of generated IDoc errors and the number increases everyday. All of these IDocs has Status "51" (application document not posted) and  description "EDI: IDoc 63120 does not exist, please check data".
    This IDoc errors does not happen before. It only started when the IDoc 63120 was missing and we can't find it already. We don't know why this is missing and we really need to get rid of these recurring IDoc errors whcih increases almost everyday.
    Your response will be helpful in solving my problem.
    Thanks in advance!

    Hi Juan Francisco Zurita Duque 
    KNREF : Customer description of partner (plant, storage location)
    internal data type : CHAR
    Internal length : 000030 characters
    Position in segment : 040, Offset : 0906. external length : 000030
    Use
    Sold-to party number sent in by the customer in delivery schedules.
    Use
    The system uses this number to automatically determine the ship-to party.
    Every thing good for ORDRE05 IN ECC6.0
    Check your config settign related to Message type and idoc type.....once again.....
    RR

  • Idoc errors in supporting side

    Hi,
         can any one  xplain what idoc errors will occur while  doing in supporting side and xplain hw to rectify that errors?
    ram.

    Hi Ram,
    Mostly the one issue will be Idoc hanging - Goto BD87 and process it manually...
    Solution:
    To identify the Idoc ie hanging - Right click on the Particular Load event in the process chain, Select Display Messages --> Processing tab --> Process monitor. A new window containing the load status details will be opened. Select the DETAILS tab, and Navigate into
    Overall status--> Transfer (IDocs and TRFC). List of Idoc transfer between the Source and target system would be listed here.
    Place the cursor on each line, the details of the idoc transfer would be listed at the bottom of the screen. The detail of Idoc transfer shows that idoc number. Idoc Status 03 - represents that the Idoc has been successfully sent by a system and Idoc status 53 denotes that it has successfully received.
    In case of an issue, the Idoc number , the status in which its hanging and the system in which its hanging can be found.
    Regards,
    Kishore

Maybe you are looking for

  • Grow and shrink JLabel to the left?

    I'm interested in putting a JLabel on the right hand side of the screen and having it resize (grow and shrink) on an on-going basis to the left. Any pointers on this? Here's some code that places a label on the upper right of the screen and then resi

  • Having trouble installing iMovie HD on a new Mac with Mavericks

    I am having trouble installing iMovie HD on a new Mac with Mavericks. I know that iMovie HD works with Mavericks because we are using it on other Macs successfully.   However, those machines were upgraded starting with OS 10.6.   In other words, iMov

  • HT6147 Software Update 7.0.6

    Software update for iOS 7.0.6 keeps failing on my iphone 4.   Any known issues or problems?

  • Quadro fx3800 : what about my actual quadro fx3700 ?

    Hi all, actually my Dell Workstation Win 7 64bits (8go ram, 2x4core, raid0+ext eSata raid0, Master CS5) is equiped with quadro fx3700. Myt question is if I equip it with PNY quadro fx3800 do I let the actual fx3700 in place and add the fx3800 or do I

  • BP for "Non Portlet" pages

    What is the best practice for organizing pages (static or dynamic) that are not portlet pages? For instance, "Contact Us" type pages that we want to be 'in the portal' but not necessarily as a portlet? do they necessarily need a webflow? what is cont