Error in outbound delievery

hi folks,
when i was doing an outbound delievery after the creation of sales order (va01), i am getting the following error,
NO SCHEDULE ITEMS DUE FOR DELIEVERY UPTO THE SELECTED DATA.
can anybody help me out please.
thanks in advance

Check the  delivery date for the schedule line. The delivery date can be the
Date requested by the customer, or
Earliest date proposed by the system after automatic availability checks and delivery scheduling
Modify the selection date and test.
SD forum is ideal for this question.

Similar Messages

  • Cancel or Reprocess BPM message with error on outbound state

    I have a BPM scenario, IDOC comes from R3 and triggers a BPM. The BPM has a fork step which sends the message across 4 branches. Each branch has its own steps. Now, the problem is the IDOC has come and has trigerred the BPM but has errored on outbound side. The first step in each branch is a mapping step and the BPM has failed at this due to Jco communication failure. This has been fixed now. Now I need to reprocess this message, but can not restart as it shows succes message in inbound side.
    I have to re process this message, but how?
    Regards,
    Jaishankar

    Jai,
    I dont know whether it is the correct appraoch.
    Have a look at the transaction SWWERRE_DEBUG
    Regards,
    Sudharshan N A

  • Message has Error Status Outbound Side

    Hi All,
    I have one question.... we procssed one file from ftp it should creates Idocs in R/3 side we developed this scenario using BPM....it processed successfully inbound side but in Outbound side it is showing Red Flag (Error Meaase : Message has Error Status Outbound Side) and its not creating IDOCs in R/3 Side but in Process engine all steps completed Sucessfully and created Idocs in XI....i tried so many ways...like in Queues and Refreshed Cache and checked RFC connection in Both ways and checked passwords in communication channels.... i could't find any this....if any body help me on this....it would be appritiated.
    This was i am testing on Test system i got this type of problem but in Development box it is working successfully we are using the same fuctionality and same code also i don't know why its happening.
    Thanks,
    Sudheer.

    Hi,
    Where are you find the Error and
    > Process engine all steps completed Sucessfully and created Idocs in XI....
      Can you explain in detail
    Regards
    Sangeetha

  • IDoc error :'Message has error at outbound side'.

    Hi Experts,
    am working on JMS-->IDoc, where TIBCO sends MBGMCR01 IDoc to ECC through XI .
    in SXMB_MONI : shows red flag in outbound:with the message as 'Message has error at outbound side'.
    please, suggest  to solve the issue.
    thank you,
    <b>MK</b>

    Hi
    Have a look this
    Message has error on outbound side in sxmb_moni
    BPM - Message has error on the outbound side
    Reprocess a message with error at outbound side

  • Message has error on outbound side in sxmb_moni

    Dear All,
    I have a query related to sxmb_moni messages.
    Scenario : FILE - XI - IDOC
    In sxmb_moni, message is successfully processed by XI but <b>it is showing error " message has error on outbound side".</b>
    My questions are:
    <b>1)Is it possible to restart the message . When I tried to restart the sucessful message with error on outbound side it showed me message " You cannot restart xml message".</b>
    2)I tried to analyze error for outbound side using SM58, it showed me message "No connection to database,session terminated" .
    Can anyone please advice what could be the reason for this .
    Thanks & Regards
    Prabhat

    Hi Prabhat,
    the message was send to the IDoc adapter. The error occures there.
    Control, if the send XML can be translated to IDocs (use a message mapping).
    Control, if the SM59 destination to R/3 is working.
    Conrol, if the communication channel is customized in the right way. Control, if the port is customized (transaction IDX1).
    Also the metadata for that IDoc should be in IDX2, that should happen automaticly, if not, assumedly the destination is not working.
    Regards,
    Udo

  • AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

    Hi Gurus,
    We are configuring the AES filing.
    we've done the EDI  configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
    Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
    All suggestions are welcome.........
    Thanks in Advance.

    Hi Shiva,
    Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
    Cheers
    Harsha

  • Error in outbound processing:ALE/IDOC

    Dear all,
    I am getting an error in outbound processing as follows(I have extended the BD12 IDOC for customer master).
    The issue is that there is no hierarchie of segments in IDOC transaction we05.(Thogh the hierarchie can be observed in WE30)
    EDI: Syntax error in IDoc (segment cannot be identified)
    Message no. E0078
    Diagnosis
    The segment Z1KNA1M_ADRC does not occur at the current level of the basic type DEBMAS06 (extension ).
    This error can have several reasons:
    u2022     The segment Z1KNA1M_ADRC is assigned to a group whose header segment does not occur.
    u2022     The segment Z1KNA1M_ADRC does not exist in the syntax description of the basic type DEBMAS06 (extension ).
    u2022     The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Procedure
    Please check the IDoc or the syntax description of the basic type DEBMAS06 (extension ).
    I will be thankful if anybody can help resolve the issue.
    thanks.
    Edited by: sanjivrd on Aug 4, 2009 2:17 PM

    hi,
    after adding those segments you need to release it.
    check it menu you can see the release option, you need to release it.
    then only it will work
    [Refer following link|EDI: Syntax error in IDoc (segment cannot be identified)]
    In the menu edit-> set release
    click on it and release
    Even check If the Hierrarchy of the segment is correct. This also will result in Syntax Errors.
    thanks & Regards,
    ShreeMohan

  • Error in Outbound Queue while Releasing order from CRM to ECC

    Hi,
    When I release my sales order from CRM to ECC, I got an error in Outbound Queue saying "Screen output without Connection to User".
    This is occuring in FM : BAPI_SALESDOCU_PROXY_UPLOAD
    Can you please tell me why this error is coming?
    Thanks,
    Sandeep

    Hello Sandeep,
    During the RFC call from CRM to ECC, this is a background processing, the screen call is not allowed.
    If a call screen is executed, there is the mentioned error.
    Please check in your ECC system, whether you have any user exits that have the coding 'call screen'.
    Best regards,
    Maggie

  • Procedure to Error Out Outbound IDocs

    Hello,
             I have a Requirement in which I am using ORDERS05 IDoc Type and extended it to ZORDER05 to populate Custom Fields and sending the Purchase Order Outbound IDoc to the Vendor from SAP System. Now, my requirement is that if any of the Custom Fields are not maintained in SAP and not populated in the IDoc, I need to Error Out the IDoc with Error Status 26. I am currently working on the SAP ECC 5.0. I have implemented similar Error Handling Mechanism earlier by using Enhancement Framework as I was working in ECC 6.0 environment where I've added the Code by Creating an Enhancement Implementation in the Function Module IDOC_CREATE_ON_DATABASE. But since ECC 5.0 does not have the Enhancement Framework feature,  please let me know how to achieve this.
    Thank You,
    Venkata Phani Prasad K

    Hi
    why don't you try using the standard method for validation of data?
    By implementing the customer-function EXIT_SAPLEINM_002 or BAdI MM_EDI_ORDERS_OUT  you can make checks of completeness of the idoc segments (in your case, additional custom data) and, if they were not complete, report an error message raising the exception DATA_NOT_RELEVANT_FOR_SENDING
    ie
    if <Idoc Custom Field> is initial.
    MESSAGE ID 'S1'
                   TYPE 'E'
                   NUMBER '333'
                   WITH Additional data are incomplete' 
                   RAISING data_not_relevant_for_sending.
    endif.
    Thus you have the evidence of the error in the processing log of the output message while the IDOC is not created.
    The solution works very well and is not invasive.
    Regards.
    Andrea

  • 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.

  • SPROXY error testing outbound proxy interface

    Hi,
    I am trying to test an outbound proxy interface using SPROXY but am getting the following error:
    Apart from the above messages there is no more help available. When I try testing the generated XSLT program using SXSLT_TEST it gives an error "No valid XSLT program supplied". I have checked and the auto generated XSLT program does exist.
    Any help appreciated.
    Thanks
    Che

    Hi Che Eky,
    Check out below helpful thread & doc:
    SERIALIZE_APPLICATION_DATA Conversion error ABAP => XML: Request Message
    Serialization issue in abap proxy
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a89312f8-0b01-0010-86b3-fdd7178e0534?QuickLink=index&…
    Regards,
    Krupa

  • Error in Outbound scenario : AE_DETAILS_GET_ERROR

    Hello Experts,
    Need your help urgently
    right now i am doing outbound scenario, in that R/3 -> XI -> Oracle.
    Here when i trigger 1 outbound IDOC then it is working fine... but when i try to send 100s of idocs at a time then half of them i getting through and half of them are going into error saying
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL"><b>AE_DETAILS_GET_ERROR</b></SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><b>Error while reading from the secure store: ERROR_U: No service user password found for Adapter Engine</b></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack><b>Error while reading access data (URL, user, password) for the Adapter Engine</b></SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    When i try to restart them into the SXMB_MONI at that time they are getting through.
    I am not able to trace that y it is happening like this....
    Some of them are going into the "System Error - Manual Restart Possible" and some of them are going in to the "System Error - Restart Not Possible".
    Can anybody please help me out in this problem? I am not able to understand that y it is happening.
    Regards,
    Hetal

    Hi Hetal,
    Check ur adapterframework service username,password in the exchange profile are given correctly.
    Also check in the Business system of the XI server, please verify the URL in the pipeline.It should be:
       http://<servername>:<HTTP Port>/sap/xi/engine?type=entry.
    Regards,
    Prasanthi.

  • IDoc error on outbound side

    Hi.
    I'm setting up a communication with (JMS adapter -> XI -> IDoc adapter).
    No w to the problem. When we send the message with the IDoc adapter we get the following error.
    Message has error status on outbd. side
    We can see this message when I put my cursor over the red flag in the outbound status column in SXMB_MONI.
    I do not think there's anything wrong with the adapter because we are using it to send an other IDoc and that IDoc gets processed correctly to the target system.
    What can cause the error on the that I get above?
    BR
    Kalle

    Hi,
          go to details of that transaction and check the error that caused idoc in outbound status failure...
    an error tab can be seen in the outbound binding pipeline entry of that transaction and check the error caiused that
    Rajesh

  • XI- CRM through IDOC adapter - error in outbound status of XI

    I have set of messages created today, each of which have 10,000 records as well as same no. of idocs as outbound in XI.
    only few messages have status 'messages processed' adn lot of messages are in staus 'Message Recorded (Commit follows)' and 'System Error (Restart Possible)'.
    So only the expected idocs are not coming in CRM. But i see the idocs XI. i clicked on IDOC in outbound column of SXMB_MONI.
    how can i restart the same message and get the idocs into CRM.
    THanks for your help in advance.
    Regards,
    Jilan Bhasha

    hi Agasthuri Doss,
    Do you mean to Restart the message?
    i tried restarting the message, then prompted with the below message.
    Do you want to retain the trace level for the
    selected messages (with errors) for the restart
    or increase it (maximum level)?
    i click on Retain, then the below error appears.
    'You cannot restart XML message
    E79C4320576611DBBAB10003BAD9E360 with this
    status/type'.
    Thanks & Regards,
    Jilan Bhasha

  • Inbound Function Module SM58 Error in Outbound R3- XI- file Scenario

    I am getting an SM58 error message of "Use IDOC Adapter for FM IDOC_INBOUND_ASYNCHRONOUS...." in my R3 system when trying to implement an Outbound R3->XI->file Scenario.  This implies that the system thinks I am doing inbound when I am really doing an outbound IDoc to XI. I followed the guides and seem to have everything set up properly.
    I also found a closed posting concerning the same error message, but there was no resolution.
    My idoc also appears fine (outbound, right ports). To test, I changed my XI rfcDestination to an EDI System rfcDestination and the ORDRSP outbound idoc goes to the edi system as expected.
    Any idea why my R3 system thinks I am using IDOC_INBOUND_ASYNCHRONOUS?
    Thanks in advance!

    Hi,
    I have couple questions before exactly answering your question
    What type of data you are trying to send like
    1. Master data (Customer master, Vendor master)
    2. Transactional data (Sales orders, Purchase orders)
    If you are trying to send transactional data then check the partner profile configuration for whom you are trying to create outbound IDocs. Select your partners outbound message type and go to Message Control details tab and check your Process code and corresponding functional module if the function module used is ment for creating outbound Idocs then there should be some other that is causing the problem otherwise I guess this is the problem so you can change the associated process code function module.
    Jagadish.

Maybe you are looking for

  • My sent text messages are received, but are from my email address rather than my phone number since updating to iOS 7.

    Fellow iPhone users have complained that my text messages are not longer associated with my phone number. Instead, they see my texts messages as from my email address. The problem started after I updated to iOS 7. How can I resolve this? I would rath

  • Error Starting WebLogic Portal 4.0

    I have installed WebLogic Portal 4.0 using wlportal400_with_sp1_win.exe downloaded from http://www.bea.com, but when I tried to run it from Start menu, I got the following error: Starting WebLogic Server .... The WebLogic Server did not start up prop

  • Ideapad U110 - External DVD Player not working with Windows 7

    I did a windows 7 upgrade on my U110 and now the external DVD drive will not function. The computer recognizes that a DVD driver is plugged in (in an explorer folder) but Windows 7 doesn't register the DVD when I plug it in and the computer cannot re

  • USB Keyboard Not Working At Login Screen

    After waking my brand new Mac Pro (OS X 10.7.4) from sleep, my usb keyboard sometimes becomes unresponsive. So, at the login, I am unable to type my password in order to restore my session. Is there a reason for usb devices to not work after waking t

  • Issue in integrating Essbase cubes with OBIEE

    Hi I am trying to use Essbase cubes as datasource in OBIEE for generating reports,but the issue is in generating , No columns in fact table of cube in BMM layer. Outline of cube is Revel(cube) (Hierachies) Time Time <5> (Label Only) Item <54> (Label