Problem in Outbound IDOC

hi experts,
I having an issue with the OUTBOUND IDOC.
i am getting error status code as 37 - Error IDOC added incorrectly.
what does it mean and how to rectify it.
message type : debmas04
extension msg type: exdebmas.
looking forward for your replies

Hi,
Double click on the status 37, in next screen click on information button, it will give you some more details of the error segments.
then we can discuss on those errors.
Reddy

Similar Messages

  • Is Reatil Problem in Outbound Idoc

    When I process POS outbound idoc wpdtax01 it will give error msg “Error in ALE service” and it have status 29, who can I resolved that problem
    can any method for reprocess POS outbound idoc
    thanks
    Amit Shivhare

    Hi Amit,
    You can reprocess POS Outbound Idoc using program RWDREPROCESS2
    Bye,
    Muralidhara

  • ECC 6.0 upgrade problem with outbound idocs

    We are currently in the process of upgrading from 4.6C to ECC 6 and have found that our outbound idocs that use to process immediately are now pending in status 30. Message type DEBMDM is one of the several outbound messages that has the issue. Any ideas of what may have changed between 4.6C and ECC 6 that may have caused this to occur?

    Hi Boss,
    This problem is with Upgrading only . so, i can give two solutions for this .
    1. create Background job with RSEOUT00 Executable program
       and give the time like 2 min or 5 min (your choice)
    2. check your code like includes  in that code  call the two Function modules that is DB_COMMIT
                                         DEQUEUE_ALL
    Try with this,,,,,,,,,,,,,
    Best Regards,
    Narasimha Rao.

  • Problem with outbound idoc

    Hi guys,
    How will I know the program that processes the outbound idoc given the mess type, basic type and extension?
    Thanks!

    Go to WE57 for assignment of FM to Basic idoc type, extension & message type.
    If it is change pointers, then check BD50 & Bd61 & run RBDMIDOC, in this there an fm  
        CALL FUNCTION tbdme-idocfbname
               EXPORTING
                    message_type       = mestyp
                    creation_date_high = date
                    creation_time_high = time
               EXCEPTIONS
                    error_code_1.
    Check the value in  "tbdme-idocfbname".
    Regards
    Kannaiah

  • Problem in  Outbound IDOC from SAP R/3

    Hi,
    I am working on to send an IDOC from SAP R/3 to XI.
    I configured all necessary things as follows:
    1. Created for XI in sender system -- RFC dest, PORT and a partner profile with an outbound parameters and reciever port as XI port.
    2. created for sender system in XI -- RFC dest, PORT(as SAP<SID>) in IDX1 and assigned an idoc type(coming from sender system) to the port.
    Now I am trying to push the IDOC from sender system using Test IDOC transaction and gets success message as data is passed to port.
    My problem is I am not able to see any message in SM58 of XI server.
    Could anyone help me out?
    Thanks In Advance.
    Yaseen.

    Yasseen,
    you hardly see the idocs in Xi in sm58. Try sxmb_moni.
    If you see anything there try sm58 on the sending R/3. There you see if you have connection problems (eg authorization in XI or missing receiver determinitions).
    Hope it hellps,
    helge

  • Problem in Outbound Idoc Scenario with change pointers

    Hi All,
    I have a requirement where i have to create an outbound scenario, whenever i create or change in transaction PAL1 (Create Sales Representative), an idoc should be triggered.
    i have created
    - ZBasic idoc type
    - ZSegments
    And have assigned the ZBasic Idoc type to ZMessage type
    Even I have maintained the fields to be triggered during change pointer in transaction BD52
    Now my problem is, whenever i change a field in transaction PAL1 or create a new one, change pointer is not getting triggered via RBDMIDOC program.
    Do we need to add an additional code to populate the Zsegments?
    If so... can you send me the logic or Sample Code which fits my scenario?
    Thanks.

    Satish,
    you cna check this badi HRALE00OUTBOUND_IDOC
    Thanks
    Bala Duvvuri

  • Error handling problem with outbound idoc status 02 and  XML HTTP Port

    I set up an ALE scenario to send master data out of SAP via an XML HTTP port.  All goes well until the idoc receives error 02. 
    It looks like idocs in this error status with the use of an XML HTTP port can not be reprocessed via the standard SAP techniques.  Program RBDAGAIN takes them out of the list for reprocessing (even though the connection is back up and running).
    Is there any solution to still use the standard ALE error handling ?

    Hi Karin,
    Looks like based on note 701597, you can only reprocess these idocs manually via a workitem.  I qouted the relevant text below:
    3. Error handling with status '02':
    An HTTP IDoc in status '02' should not automatically be sent once again.
    Up to now, the RBDAGAIN report was used to resend incorrect IDocs.
    However, this report was adjusted and now deletes all IDocs in status 02
    to be routed to a HTTP port from the list of selected IDocs. IDocs to a
    HTTP port in status '02' should only be sent manually via a work item.
    Regards:
    Rex

  • How to Reprocess Outbound Idocs in Status 02 (Errors)

    Hi,
        I have an urgent problem. How do I re-process an Outbound IDoc in Status '02' (Error Passing Data to Port)
        I have tried reprocessing this IDoc through BD87 using both the options Edit>Process and Edit>Restrict and Process, but it doesn't work
         Please help as we are migrating cutover data from SAP to another system
    Regards,
    Aditya

    Worth to have a look at this thread
    Error handling problem with outbound idoc status 02 and  XML HTTP Port
    Regards
    Vivek
    Reward points for all the useful answers

  • Duplicate Outbound IDocs getting Triggered at the same time.

    Hi Folks,
    I have created custom outbound idoc and done all the configurations required like WE20, WE30, WE31, WE81, WE82, WE 41, WE57 etc.
    Also I have written my code to populate segments and then call MASTER_IDOC_DISTRIBUTE in the custom function module which is assigned to the process code and also done the configurations like we57 etc. for the same.
    Now when I trigger my output type from VL74 transaction, I noticed two entries in we02 resulting in two IDocs generated for 1 HU.
    The difference in two IDocs is the first IDoc getting generated in error with status 29. While the second one as success with status 03.
    The data records containing segments have same values for both the IDocs number.
    Whether the configuration is a issue here or problem in code of custom fm?
    Please help.

    Hi Anil,
    Appreciate your quick response.
    In my custom FM I have populated an internal table it_master_idoc_data with two records of two segments, containing segment name in SEGNAM filed and segment data in SDATA field. 
    Please let me know whether the data in this internal table of structure EDIDD sufficient for passing to MASTER_IDOC_DISTRIBUTE FM? Or do I need to populate any other field of EDIDD.
    Also I am exporting a structure master_idoc_control containing values in this 5 fields.
    MESTYP = Z message type, Z IDOCTP, partner and details in  RCVPOR, RCVPRN, RCVPRT fields.
    I am not populating the internal table communication_idoc_control while calling FM MASTER_IDOC_DISTRIBUTE from my custom function module.
    After executing MASTER_IDOC_DISTRIBUTE FM, when the control comes back to my custom FM there is one record in communication_idoc_control  internal table with IDoc number in DOCNUM field with status 29(error). Now when we check in WE02 there are two IDocs generated after this transaction's execution.
    The first one in error which FM MASTER_IDOC_DISTRIBUTE returns and second one in success with status 03.
    Please help....
    Thanks,
    Pravesh

  • Problems with sender IDoc scenario

    hi experts..,
    when i create message Interface for a Outbound Idoc my scenario is not working.
    if i use idoc directly instead of message interface its working properly
    And in Interface Determination if i gv interface mapping we are gting errors and without mentioning interface mapping in Configuration its is working fine
    can any one explain me what is the reason for my two questions
    thx in advance
    john wesly

    Hi,
    I will explain one example by taking one IDOC
    we have ORDERS05 Idoc and we are using the same Idoc for two scenarios
    Scenario1 -
    IDOC---File( FTP Server)
    Scenario2----IDOC-JDBC
    Now let us assume that we have configured two scenarios.
    If we trigger the IDOC Orders05 from SAP R/3 means
    1) The Idoc will be triggered and it will reach to XI.
    Now your doubt is which Receiver will be take place and to be executed.
    This time the problem my come or may not come, let it be like that.
    If your requirement is like the above mentioned thing means
    1) We can develop a single scenario like
                     IDOC-------File( FTP Server)
    JDBC
    Here what we have to do is when the idoc comes to xi we have route the Idoc to the particular receiver based on some condition in Receiver Determination
    And one more thing is in mapping also if we have two mappings then we can use Interface determination based on condition which interface mapping to be execute.
    I hope this clears yor doubt
    Regards
    Seshagiri

  • Custom error in outbound idoc FIDCC1

    Hi all,
    I am generating outbounds idocs for FI documents and i need to put some of them in error. I need the FI Document created and the idoc in error so that i can reprocess it later. To do that i am using the User Exit EXIT_SAPLF050_007
    Enhancement - F050S004 FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
    ""Lokale Schnittstelle:
    *" IMPORTING
    *" VALUE(MESSAGE_TYPE) LIKE EDMSG-MSGTYP
    *" TABLES
    *" IDOC_DATA STRUCTURE EDIDD
    *" CHANGING
    *" VALUE(IDOC_CONTROL) LIKE EDIDC STRUCTURE EDIDC
    *" VALUE(DISTRIBUTION) LIKE BOOLE STRUCTURE BOOLE
    *" OPTIONAL
    IDOC_CONTROL-status = '26'.
    The problem is that in the UserExit i set the Idoc Status to some value diferent than 3 (Data passed to port OK) but finally the idoc is created with the status 3.
    Does anybody know how to change the idoc status in the creation from 3 to for example 26 or 27? ( an error idoc status ).
    thanks!!

    Hi,
    In the partner profile, set the option as Collect IDOC's option.
    Create a background job in which the first step of that should be your custom program and the second step is RSEOUT00 program.
    In your custom program, validate the idoc if you feel your idoc is correct then leave it like that and if you feel there is some problem in the idoc then flag that error idoc for deletion that means that error idoc will not be sent to your partner.
    For flagging an outbound idoc to deletion is nothing setting the idoc status to 31. This you can do with the program RC1_IDOC_SET_STATUS.
    Thanks,
    Mahesh.

  • Outbound IDoc Error: Status Code 37  'Sender Port' is invalid

    Hi
    I have an Error when the Outbound IDoc is triggered.
    It shows that 'Sender Port in Control Record is invalid'.
    Status Code: 37.
    I know that there are some issues with the Sender Port Definition.
    Please help me out to solve this problem using some checkpoints at each and every step.
    Reward Points Assured.
    Regards,
    Baburaj

    Hi Baburaj Manickam
    Good
    Follow this simple procedure
    1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
    -  Create File Port (WE21) for outbound file.
    -  Maintain Distribution Model (BD64) for sender ->receiver system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s). 
    _  Then you can FTP the file(s) to receiver system.
    2) Upload the flat file as an IDOC on the inbound sytem
    which is Client2(RECIEVER).
    -  Create File Port (WE21) for inbound file.
    -  Maintain Distribution Model (BD64) for receiver -> sender system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RSEINB00 to upload IDoc MATMAS file(s). 
    INBOUND IDOC PROCESSING:
    Firstly attach your idoc to a process code.
    In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
    Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
    1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
    2. Set Function Modules as Inbound: - Transaction BD51
    3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
    4. Create process codes : Transaction WE42, and link the z-function module.
    5. Create partner profile: transaction WE20 and attach the message type and process code.
    6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
    Try the Trasaction WE19 for testing your inbound and outbound IDOCs
    Good Luck and Reward me for the same
    Thanks
    Ashok.N

  • OUTBOUND IDOC DEBUGGING

    I have Output type  defined for the application V3
    i.e meant for Billing.and the output type is custom development with name ZD00 for invoice-Bill to.
    This output type is defined for edi processing.
    Now the problem is when invoice is created and this
    outputtype is selected the quantity field in idoc and invoice differs.just get double in idoc.but if the same output is fired again data in idoc gets corrected.now i want to debug the idoc outbound processing.what i did i run the transaction we41 and find the process code  and find the function module that is running in the background for collection of data of invoice and
    filling the idoc.but but but the problem is i put break point in the function module to check the value at run time but this is not triggered . iam confused tell me how to debug the outbound idoc.
    Help me out i will be waiting for the response.

    Hi,
    You can use the Update Debugging. If you know the prognam name/function module of your source code, upon saving your document, a new screen will pop up if the Update Debugging mode is on. From this, you can then hit F8 to stop on your break-point.
    Let me know if you need further help.
    Thanks,
    Eric

  • XI generates own IDOC numbers in outbound IDOC

    Hello, The scenario we have is R/3 --> XI --> 3'rd party (via IDOC rcvr adapter) AND then SYSTAT back from the 3'rd party to R/3 via XI.
    Example: R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number).
    Accordingly, the 3'rd party responds back with a status IDOC, SYSTAT, containing IDOC 200 in the E1STATS ==>DOCNUM field.
    This is now a problem since if XI submits the SYSTAT as received from the 3'rd party, it has 200 in the DOCNUM field and this fails in R/3 since there is no original IDOC with number 200.
    This can be solved if XI is able to pass the original number 100 through to the 3'rd party system (since then when the 3'rd party responds it will send a SYSTAT with IDOCNUM as 100 back, which will setup correctly in R/3).
    I have gone through the other pertinent posts and none of them have this specific problem / offer a solution. I'm hoping I have missed something as this seems to be a pretty basic requirement.
    Thank you for the time.
    Some additional details...
    - 3'rd party is non SAP.
    - In the IDOC rcvr adapter we have flags 'Apply Control Record Values from Payload', 'Take Sender from Payload' and 'Take Receiver from Payload' fields checked.
    - We have not checked any flags in the Rcvr Agreement.
    - We are not using BPM and do not have a way to correlate the inbound 200 with the original 100 that went out.

    Bhishma,
    Just clarrification for you...when you said..
    "R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number)."
    Here Idoc number 100 is outbound idoc from R/2 where as Idoc number 200 is inbound idoc...n they are totally different idocs..not same
    I think there is work around...while mapping data from XI --> 3rd party assign / store outbound idoc in one of the unused field of inbound idoc...and while mapping back use this field to map it back...I think this will work.
    Let us know the result.
    Nilesh

  • Generate outbound idoc for Customer Master

    Hi Developers,
    I have requirement to generate outbound IDOC for Customer Master Data. I need to send customer master data through an Outbound IDOC. Can we generate an outbound DEBMAS06 idoc? Can someone help me finding a solution to this problem?
    Thanks in advance for helping.
    Regards,
    Gajendra

    Hi,
    If you have done all the required settings (logical system, partner profiles, distribution model), then either transaction BD10 / BD14 will help you generate the IDOC.
    If you want to send the idocs automatically, then you will to configure some program.
    Unlike transaction data, Master data IDOCS are not triggered immediately, you will have to do the required configuration in SPRO.
    Transaction SPRO
    SAP Customizing Implementation Guide -->
    SAP Web application Server --> Application Link Enabling --> Modeling and Implementing Business Processes -->
    Master Data distribution --> Replication of Modified Data --> Creating IDOCS from Change Pointers
    Take a look at this thread.
    Re: automatic Idoc outbound
    Regards,
    Ravi
    Note : Please mark the helpful answers
    Message was edited by: Ravikumar Allampallam

Maybe you are looking for