Idoc distribution with status of error records.

Hi Gurus,
my business requirement is i want to creat the Outbound Interface to distribute the data from sapserver to ESB server using the one userdefined function module, in this custom function module i written the logic to validate the input data if validation is file those error records are updated to one return table parameter and using the FM Master_Idoc_distribute for  create and distribute the sucessfull records. till its working fine (with status 30-ready to dispach, 01- idoc creatd is in we05 and i have done  the all configaration of message type creation, idoc type creation, port, partnerfrofil) ,
but my requirement is , for example if in 10 records even one record is also error records then no need to distribute the idoc data to sending system,  just i want to send the idoc number with status error with error message.
plese suggest me the appropriate procedure.
Thanks & Regards,
Sai Ram.

Hi,
in ur code ur filling the idoc data rcord, control record ryt ..before u append data to idoc data , u r also validating and u might be doing in loop for appening the idoc data.
if there is any error in idoc then it won't distribute the data, it will be in error status only..u can only see the data in WE02. Then u can also change the data in WE02 and redistirbute it via BD87.
if u have any conerns let me know
Regards,
Nagaraj

Similar Messages

  • Error in idoc with status 20 "Error triggering EDI Subsystem"

    Dear All,
    I have query related to IDOC Status 20.
    I am tirggering IDOC with standard t-code from IS-Retail system. I have created two ports a) TRFC port and b)File port .
    <b>We are having sending and receiveing application on two different OS i.e one XI on Windows and IS Retail on AIX(Unix). I am not able to send idoc to another system. I am getting these IDOC status in WE05 (STATUS 01 , 30 , 03 , 20 )</b>
    Keeping the above fatcs in mind could you please tell me how to remove the <b>error with status 20 "Error triggering EDI Subsystem".</b>

    Hi prabhat,
    You should have checked the automatic triggering possible at the file port level and the partner profile setting could be 'start subsytem'.
    Go to WE21 and do the access test for the file port.
    Once you done and find no issues then go to SM59 and test the connection for the RFC destination assigned to the ports.Possibly it has to do with the RFC destination.
    Other reasons could be yours is a test client and got refreshed recently.so the production client settings might be causing this error.Check with your basis to get it working.
    other reason could be the logical system assigned to the client should be having production client's name.
    Check these.
    I am sure you should be able to solve this issue.
    Thank you.
    regards,
    karun.M

  • 5 IDOC with status 29 Error in ALE service

    hi there,
    im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
    IDOC Status Outbox:
    IDOC failure between 13/07/2008 to 14/07/2009
    1 IDOC with status 02 Error passing data to port
    5 IDOC with status 29 Error in ALE service
    IDOC Status InBox:
    88 IDOC with status 51 Application document not posted
    regards
    raju

    Hi,
    Check this thread.
    DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
    Regards.

  • Email on Idoc Failure with Status 56 64 68 69 70

    We have standard inbound idoc processing for Basic Type : DELVRY01 and Message Type : DESADV using the function module IDOC_INPUT_DESADV1.
    We currently have a requirement to send an email, when any of these type of Idocs fail with status 56, 64, 68, 69 and 70.
    Where would be best place to provide this solution to send an email to a particular user when the Idoc fails with the above status?

    Hello Saleem,
    One approach would be to consider workflow based on object type IDOCAPPL.  The start condition for the workflow could be the triggering of the event errorProcessCompleted.  You could filter further by status and your message type (DESADV ) to only start the workflow for the errors that you mentioned.  The workflow could then send an email. 
    You will need to verify the details for your own scenario.
    Good luck,
    Greg Kern

  • IDoc received with status 8

    Hi Experts,
    Please find the below Error now i am getting.
    No data available
    Diagnosis
    The data request was a full update.
    In this case, the corresponding table in the source system does not
    contain any data.
    System Response
    Info IDoc received with status 8.
    Procedure
    Check the data basis in the source system.
    Please provide me solutions ASAP, this issue.
    Thanks & Regards,
    Bharathi.

    Hi Ananda,
    I have followed ur post, but same problem i am facing.
    The Error below following:
    No data available
    Diagnosis
    The data request was a full update.
    In this case, the corresponding table in the source system does not
    contain any data.
    System Response
    Info IDoc received with status 8.
    Procedure
    Check the data basis in the source system.
    Please give me any other solutions, how to resolved this issue.
    Thanks in Advance.
    Regards,
    Bharathi.

  • Info IDoc received with status 8 infopackage hanging in yellow status

    Hi All,
    when I extract the Text data without data selection it is fetching the 14 record into BW and changing the status to green,
    however when I go with data selection it has No record for this selection in RSA3 as well in BW .
    when I do this data selection in infopackage in BW it is bringing ' 0 ' records and hanging in to yellow status in RSMO for more than two days. it is not turning it to red/green
    it shows in Monitor with message " Info IDOC received with status"  in yellow status.
    I have found the OSS 713427, it is already had this correction .
    when I check in SM37 job is completed immediately.
    there is no short dump
    Many Thanks
    Ramm

    Hi Robort,
    thanks for reply
    there is no data for this data selection and there is no IDOC processed in BD87 or we02.
    I  checked out the note and its only for IDOC stuckup .
    may I have any other suggestion.
    many thanks
    Ram

  • IDoc created with status 03 checked via we02, but couldnt find in XI

    Hi all:
        Could you please do me a  favor?  implement a idoc to idoc issue. it has been created successfully .
    as It is found that the idoc created with status of 03 -
    data dispatched to  port ok (rather than 12 dispatch ok). however, I couldn't find  it via SXMB_MONI on XI,  there must be something wrong . coudl you please give me a hint ?
        Thank you very much!!!

    hi,
    you need to check transaction SM58 (remove the user from it) and F8
    it might be the reason that you didn't create a port in IDX1 on XI/PI
    but you will see that in SM58
    Regards,
    Michal Krawczyk

  • Info IDoc received with status 8 in BI but Data available in source system

    Hello Experts,
    I am loading Budget Period (attributes) into PSA in BI.
    Budget Period data Loading Issue : No data available while loading. But source system ie ECC has data in that data source
    Data source: 0PU_BDGTID_ATTR
    This is full load.
    I checked that whether I am making any mistake during data selection. I could not find any issue. Message while loading data into PSA (Yellow Traffic light)
    No data available
    Diagnosis
    The data request was a full update.
    In this case, the corresponding table in the source system does not
    contain any data.
    System Response
    Info IDoc received with status 8.
    Procedure
    Check the data basis in the source system.
    Already looked this thread and googled also.
    Re: IDoc received with status 8.
    Check points:
    sm58 - NO issue
    BD87 in ECC (RSINFO Idoc status: 03) -sucessful
    BD87 in BI (RSINFO Idoc status : 53)
    ST22 - NO issue
    sm37 - Job is successful (I could see Idoc no in ECC source system in Job log)
    I am not sure if I am missing any thing.
    Thanks
    Rana

    Hi all,
    I've got exactly the same issue with several extractors. I'm inialising the Master Data in a all new system, in the Quality the loads succeeded but in Prod it failed.
    For instance with the basic DataSource "0FUNCT_LOC_TEXT", I've made the following test:
    RS3 (R/3) - > 0 data
    ST22 -> no short dump
    WE05 (Idoc) - > everything is ok
    I reactivated the Datasource in R/3 (RSA5) and then deleted it and replicated it in BW but the same issue occured.
    Any ideas?
    Thanks
    jak

  • Loading Error from CRM datasource  - Info Idoc recieved with status 8

    Hello All,
    NEED YOUR HELP
    We have a CRM datasource 0CRM_SALES_ACT_1 which works well from source in RSA3. The dataload is a full and fetches 19,000 records from CRM
    However when we load it from an infopackage from BW it gives us the following  "No data in source sysetm" Info Idoc with status 8. We have tried the following to eleminate some doubts
    1) Checked the connection in SM59 using aleremote .Connection and authorization successful. Also loaded data in the BW system  for other datasources from same CRM system it works well, so no authorization/ connections issues.
    2) In the source system CRM  tried transaction RSA3--> extract data get 19000 records
    3) In the source system CRM Triied transaction RSA3--> Import Request from BW --> successful.
    4) Checked the TRFC queue in SM58 the TRFC queue is empty
    5) When we check the logs in CRM for ALEREMOTE we get the following message
    synchronous transmission of info IDoc 2 in task 0001 (0 parallel tas
    DATASOURCE = 0CRM_SALES_ACT_1
             Current Values for Selected Profile Parameters
    abap/heap_area_nondia......... 0
    abap/heap_area_total.......... 9437184000
    abap/heaplimit................ 40000000
    zcsa/installed_languages...... ED
    zcsa/system_language.......... E
    ztta/max_memreq_MB............ 256
    ztta/roll_area................ 3000000
    ztta/roll_extension........... 2000000000
    Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 0 records
    Result of customer enhancement: 0 records
    IDOC: Info IDoc 2, IDoc No. 266228, Duration 00:00:00
    IDoc: Start = 2008.10.22 14:18:38, End = 2008.10.22 14:18:38
    Synchronized transmission of info IDoc 3 (0 parallel tasks)
    IDOC: Info IDoc 3, IDoc No. 266229, Duration 00:00:00
    IDoc: Start = 2008.10.22 14:18:39, End = 2008.10.22 14:18:39
    Job finished
    *What is the issue ? Data is present and confirmed available in source system , yet we get 0 records in BW system ? WE NEED YOUR HELP *

    Hi
    May be you need to provide full authorizations to the user 'ALEREMOTE'.Ask your basis team to check the authorizations.
    Regards,
    Chandu.

  • Urgent:Idoc stuck with status 03 in TRFC

    My Idoc is in status 03, but it is not reached to destination.
    I guess It is stuck in Rfc layer or in some QUEUE.
    There was quality system refresh last week here with Production system.
    Pelase suggest what seetings need to be changed and where.
    in SM58 it give the following error
    'RFC address XXXXXXX doesn't exist'
    (where XXXXXXX i m not mentioning here for Client security reasons)
    is there any program to clear these layers?
    Thanks a ton in advance and the answer will be adequately awarded.

    hi,
    whnevr ur idoc is in status 03 just run the transaction BD75.
    the status will be converted to 12 and datawill be passed.
    reward points if hlpful.

  • Idoc failed with status 51 for Warning/Information messages

    Hi All,
    We are trying to create some Sales Orders with the help of Idocs. We are facing some problem as mentioned below.
    1.There are some warning messages/information messages written in standard Sales Order User Exit USEREXIT_SAVE_DOCUMENT_PREPARE
    2.As soon as the Idoc processing reaches any of these messages, it considers them as ERROR message and Idoc fails with the status as 51 which is not expected.
    3.Also, I see that the Sales Order is saved with the data that has been passed in the Idoc.
    Is this the standard behavior ?? (Or) Is there any EDI related configuration setting which can be used to suppress these kind of messages in Idoc Processing ??
    Any help on this would be highly appreciated.
    Thanks,
    Babu Kilari

    if your IDOC has status 51 then it is not posted, hence your sales order cannot be created from this IDOC. of course this error behaviour can be originated by the user exit.
    please read OSS note Note 747631 - Some tips when testing idoc_input_orders

  • IDOC stops with status 30

    We have migrated from SAP 4.7 to ECC6 , the Xi is on version 2.0 .
    After migration  some of our IDOC created from ABAP Proxy are not getting processed automatically. It stops with status 30 and we need to reporcess this . After reporocess the messages are getting processed
    Can anyone help in finding out how to find this error
    Edited by: Sanjeev Koganti on Aug 7, 2008 9:27 AM
    Edited by: Sanjeev Koganti on Aug 7, 2008 9:39 AM
    Edited by: Sanjeev Koganti on Aug 7, 2008 9:43 AM

    Hi,
    The status 30 of IDOC, status text u201EIDOC is ready for dispatching (ALE service)". Internally, the constant ALE_READY_FOR_DISPATCHING represents this status.
    Processing Selected Intermediate Documents  -->
    Use program RSEOUT00 to start processing all selected intermediate documents.
    You need to check your ALE settings for that error. test the proxy mannualy using payload.
    Then you will come to know wheather your proxy works fine or not.
    Go to SPROXY --> Select Your SERVICE INTERFACE --> clikc on TEST button or Press F8 --> provide your payload and check the result.
    Regards,
    Gunti

  • CUA - IDOCS - DISTRIBUTION UNCONFIRMED STATUS

    Hi,
    I have seen the strange issue in CUA IDOCs with respective of a child system...
    That is, If i do the user maintenance with respective of the child system  in the central system and save it.
    1) then the system is generating the IDOC's for central and the respective child systems.
    2) The changes are getting reflected to the respective child system.
    But when i check SCUL in CUA, still it is showing as DISTRIBUTION UNCONFIRMED STATUS
    I have verified the below things
    A) OUTBOUND and INBOUND jobs in central and Child are working fine.
    B) IDOCS are getting posted in child system with status 53
    C) RFC connection is fine
    D) Partner profiles are fine
    E) SCUA - showing green
    NOTE:
    The issue is happening only for one system -client and all other systems and clients were working fine without any issue
    Kindly let me know your opinion
    Sv

    >
    > NOTE:
    >
    > The issue is happening only for one system -client and all other systems and clients were working fine without any issue
    Hi,
    Please follow the [SAP Note 169538 - CUA: Too many unconfirmed users in the log|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=169538].
    Is the RFC from that Child system to Central system is working properly?
    Basically this kind of Unconfirmed status happens when the IDoc processing get stuck due to too many IDoc generation. You can schedule a job in that child system for the report RDBPROCESS to process the unprocessed IDocs in a certain interval of times.
    You may also want to check the changes happened in SCUL by [SAP Note 632486 - Improvements to transaction SCUL|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=632486].
    Regards,
    Dipanjan

  • Report ending in warning with status 127 error

    Hi,
    We ran a concurrent report with Print options set for a custom report.
    The report is ending in warning with the below error:
    ------------- 1) PRINT   -------------
    Printing output file.
    Request ID : 356879180      
    Number of copies : 1      
    Printer : ABSC_5WCC_HP9
    /bin/sh: jforasnd: not found.
    APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. Program exited with status 127
    Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. Program exited with status 127.
    Action: Review your concurrent request log file for more detailed information.
    Please suggest how to overcome this error.
    Regards
    Siva G

    Please see your other thread -- Re: Concurrent report ending in warning with status 127 (post upgrade to R12.1.

  • How to CANCEL/RESEND messages in Adapter with status system error in bulk?

    Hello all,
    I d like to know how can I CANCEL or RESEND messages with status error SYSTEM ERROR in adapter framework.
    Messages failed because of receiver system un-availability. Now, we have more than 50.000 messages stuck, waiting for being resent or cancelled.
    But from the Message Monitoring Tool at Runtime Workbench Monitoring, I can only process up to 200 messages each time.
    So, its practically imposible to do it manually.
    My question is how can I deal with that amount of messages? Is there a way to process them in bulk and get them cancelled in only one step/action?
    Many Thanks in advance.

    Hello, I hope you are doing fine!!
    The most common way to cancel these messages is through the Runtime Workbench as you have mentioned youu2019ve tried.
    Just one note: Once you are on the Message Monitoring screen -> Filter (where you can select the dates, message status, etcu2026), there is a Dropdown box menu at center of the screen called u201Cmaximum Numberu201D where I believe you said you can only see 200 messages.
    You may try to select u201C10.000u201D there and then cancel these messages from there.
    However, if you prefer doing this in one go, you can do this by changing the status of the messages from u201Cerroru201D to status u201Cdeliveredu201D by executing following SQL statement at the database level:
    UPDATE <DB Schema>.XI_AF_MSG SET STATUS='DLVD' WHERE MSG_ID='<MSG ID>
    AND DIRECTION='<INBOUND   OUTBOUND>'
    Cheers,
    Jorge Eidelwein

Maybe you are looking for