Inbound IDoc SHPCON - Batch update issue

Hi all,
I would like to use SHPCON.DELVRY03 idoc in order to update Outbound delivery document.
Scope is :
- picking
- good issue
- update batches
- update serial numbers
- update volume and weights
We met issue on update batches a soon as one document item already has batch information before receiving IDoc.
2 cases :
- no batch spliting => High level item has already a linked batch (LIPS-POSNR = 000010 and LIPS-CHARG not empty.
Is there a way to update batch information if external warehouse confirms another batch number ?
- batch splitting => High level item has already 2 sublines POSNR = 900001 & 900002. Both has batch numbers.
If I want to confirm it, I can send E1EDL19 with BAS qualifier but sublines are added...
Must I delete existing sublines with E1EDL19 DEL ?
Thanks a lot for your help.
J.C.
and to post good issue.
All is OK except

Hi,
We are having same issue as of yours...
i.e Updation of batch via IDOC to the delivery if delivery contains batch ...its not happening and also idoc not throwing any error
Did you able to resolve this ?
Thanks
Rajesh

Similar Messages

  • Inbound IDoc used for updating Sales order status

    I have a requirements to set use standard IDoc to send out the Sales order to a non-SAP software as well as receiving Inbound IDoc to update the status of sales order in SAP. Could someone comment on my questions below:
    1. What are the difference between all the ORDERSxx Idoc types?
    2. What IDoc should be used for Inbound IDoc to update the sales order stataus in SAP?
    3. Can the same IDoc type be used for both Inbound and Outbound with only the difference in the segment of Direction?
    Thank you. Points will be awarded appropriately for helpful comments.

    Hi,
      1.Intially  standard IDOC types "ORDERS01"  is having limited
          segments. After few months the requirement got increased to
          add more fields to "ORDERS01".So,once you release the IDOC
          type you can not add any more fields .So SAP come up
          with "ORDERS02" with new fields.Like that all IDocs types have
          some more new seg ments.
    2.You  can use ORDER05
    3. Yes you can use same IDOC type

  • Inbound IDoc w/message ORDERS - issues with error processing

    We are using inbound IDoc ORDERS05 with message type ORDERS to create the sales orders in SAP. In WE20 we have the following settings:
    - partner type LS (= Sales Org VKORG)
    - process code ORDE
    - trigger by background program
    - post-processing agent of type US (user) with a user ID.
    We create IDocs through an ABAP program and use RBDAPP01 to post the IDocs. When there is an application error in the IDoc posting we expect the designated user to receive a workflow item in the SAP Inbox, but for some reason this is not happening.
    I did some research and went through all the possible settings for workflow, task, etc. and everything seems to be set up correctly. When debugging RBDAPP01 I have noticed that it calls FM APPLICATION_IDOC_POST_IMMEDIAT, which, in turn, calls IDOC_START_INBOUND. If IDOC_START_INBOUND returns SY-SUBRC = 1 then the workflow item is sent correctly to the designated user, exactly as we want. But for some reason it returns 0 (I changed it to 1 in the debugger).
    It seems that IDOC_START_INBOUND reads TEDE2 records (TEVE2-EVCODE = ORDE) and sy-subrc = 1 is only possible when EDIVR2 is 1,2,3 or 4. In our case TEDE2-EDIVR2 = 6. It seems that TEDE2 is maintained in the transaction WE42. However, I tried to change the settings there but it affects the IDoc processing in whole (IDoc gets some odd status and doesn't get processed as before). I've also tried to use process code ORDE_BY_WORKFLOW in WE20 with the same "success".
    What do we need to do to get a workflow item for the errors that happen in the application layer when IDoc is posted? Is it even possible with this message type?
    Any ideas would be appreciated.

    Hi,
    Can you please share how do you overcome the problem, so that it can be helpful for others.

  • Inbound idoc values when updated from user exit not saved

    I'm trying to process some user exits of an inbound idoc from WE19.
    The values get correctly populated to IDOC_DATA internal tables of IDOC_INPUT_ORDRSP function module in debug kode
    but when the new idoc is generated from WE19 , those segment values (populated by exit) are not shown/saved.
    The user exit is EXIT_SAPLEINM_007.
    Is it not possible to populate segment values of inbound idocs from using user exits. If yes , then during testing using WE19 , every time a new idoc is created it should display those values into the concerned segments. Please help.

    Hello,
    yes is possible it ...
    I think the problem is:
    or
    you have something wrong when to append the new line on internal table
    or
    the exit used is not correct: read the documentation on EXIT_SAPLEINM_0**

  • How to change field values AFTER Inbound IDOC Posted successfully

    Hi SAP Experts,
    In my project I receive the inbound IDOC PORDCR05 from PI and posted as an Purchase Order in ECC.
    I create the Z process code and Z function module (which is a copy version of IDOC_INPUT_PORDCR) and complete all the necessary configuration steps. It works perfectly.
    My problem is: I have to  collect some inbound idocs (that satisfied some criteria) and change the value of field EKPO-TXJCD and EKKN-KOSTL of the PO AFTER  it posted successfully (means the purchase order is created and save in database).
    How can I do this? I've try to put the logic code in Z function module, but it does not work, since at that time, the Inbound IDOC is not updated to the database yet.
    Aprreciate your advise.
    Regards,
    Elaine.

    Hi Elaine ,
    as per your cretiria pick the idocs and take created PO# from status 53 & use the BAPI (BAPI_PO_CHANGE) to change the neccessary values in the PO. We can't reprocess those idocs again.
    Reddy

  • Mails whenevr an inbound idoc fails

    Hi Experts,
    Is there any way I can trigger mails whenevr an inbound idoc fails to update in r3.With reference to workflow etc
    Regards,
    Arnab

    Hello Arnab
    On SAP release >= 6.20 you have the standard report RSEIDOCA available which can be scheduled in background.
    Unfortunately SAP did not provide an e-mail notification mechanism for this report but only workflow. For our company I created a ZRSEIDOCA report having this e-mail function. For more details please refer to
    ALE Error Message Handling
    e-mailing: How to sent out an email to the Managers OUTLOOK express account
    Regards
      Uwe

  • Triggering a mail when ever a perticular inbound IDOC fails

    Hi Experts,
          Is there any way I can trigger mails whenevr an inbound idoc fails to update in r3.With reference to workflow etc
    Regards,
    Arnab

    hi,
    i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
    if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
    ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
    Workflow functions as follows:
    A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
    If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
    If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
    For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
    1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
    2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
    3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
    If an error occurs, the system determines:
    1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
    2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
    3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
    regards,
    pankaj singh

  • ECC6 Super Session Chains - Standard Inbound IDoc/BAPI

    I am trying to setup supersession chains in ECC6 environment. Is there a BAPI/standard Inbound Idoc for creating/updating these?
    Also, is there an standard outbound IDoc if I want to syndicate these chains to other SAP Systems?
    Please note that I am not implementing APO,

  • Inbound idoc for updating delivery date of purchase order

    Hi All,
    Our vendor sends a delivery file consisting of delivery date and quantity(could be partial) for line items of a purchase order.
    I need to update the Purchase order line item with the delivery date and quantity sent from the Vendor. It should add a new confirmation line with custom confirmation category in the confirmation tab of the line item in the Purchase order.
    Each time we get a delivery file we need to add a new confirmation line in the confirmation tab of the purchase order line item.
    How can I get this working using inbound idoc processing? Which Idoc type should I use to solve my issue. Will ORDERSP work for my scenario?
    Thank you,
    Sonali.

    >
    sonali ashi wrote:
    > We have all EDI set up done for ORDERSP idoc in our system. Problem when I use this idoc type by default system is always adding confirmation catgeory 'AB' but we want our custom  category to be added instead of 'AB'.
    > Edited by: sonali ashi on Dec 23, 2010 9:47 PM
    Confirmation category used for order acknowledgement is define in configuation. You can change that from AB to your custom condition and EDI should pickup that.
    SPRO->Material Management->Purchasing->Confirmation->Define Internal Confirmation Category
    >
    sonali ashi wrote:
    > I have also noticed that 'AB' confirmation accepts only full quantity order acknowledgement through Idoc processing.
    > Manually I can add a "AB" confirmation for partial quantity but in the idoc processing it fails.
    > Edited by: sonali ashi on Dec 23, 2010 9:47 PM
    Check tolerance limit defined for confirmation category in 'Conformation Control' Node in SPRO at same level as above.
    Regards,
    Pawan.

  • Urgent help required : Batch processing error of an inbound idoc

    hi,
       i have a problem while posting an idoc to the GL(FB01).
    i'm using an Inbound idoc message type : ACC_GL_POSTING
    idoc type : ACC_GL_POSTING01.
    Process code : BAPI.
    In the transaction code OBA7 i have enabled a particular document type as BATCH INPUT ONLY.
    i have set the option " Trigger by background program" in the partner profile (we20).
    while testing the process i'm getting the error "Document type -- is only defined for batch input".
    how can i overcome this error? can idocs be used to post for transaction that are batch enabled . plz help me.
    with regards.
    T.Jeyagopi.

    Jeyagopi,
    There are different types of Data loading into SAP.
    BATCH INPUT / BDC / IDOC / BAPI etc. BATCH INPUT are standard programs that take the data and update SAP. I don't think that is same as batch processing of IDOC.
    You might want to remove the setting of batch input, retain the batch processing in WE20 and try it out.
    In my opinion it should work.
    Regards,
    Ravi
    Note : Please reward points for the posts that help you.

  • Post Goods Receipt for Inbound Delivery via IDoc SHPCON (DELVRY03)

    hi all,
    I'm using IDoc SHPCON (Delvry03) for posing goods receipt for inbound delivry.
    Can anyone give a sample IDoc or tell which segments must be filled.
    Thanks!
    Regards,
    Hui

    Hi Uwe,
    Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
    The binary answer would be no. You should use WMMBXY or MBGMCR instead.
    But if we are doing goods receipt against Inbound delivery then answer is YES with additionally E1EDL18-QUALF = 'PIC' populated. But please remember no partial receipt is possible against Inbound Delivery.
    We should populate E1EDL20-VBELN with our Inbound delivery number and line item info should go to E1EDL24.
    I have done a similar interface recently where we are doing receipt against Inbound delivery. But our case was a bit complex because we had to support against Inbound delivery. So we had to go for a custom solution on top of IDOC_INPUT_DELVRY.
    Hope this helps. Let me know if you have more questions.
    Regards,
    Rudra

  • Outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON

    Hi Friends
    I am trying to pack outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON.
    But IDOC has error Specification of destination HU missing.
    Could you please help us to resolve the issue to Pack the outbound delivery with the  IDOC.
    Thanks
    SR

    HI Ian Kehoe
    Sorry for delay in reply
    Thanks you very much
    I solved that problem .
    Could you please advice  test data for IDOC  DELVRY06 packing hierarchy (multi level packing) to pack SAP outbound delivery.
    Thanks
    Ravi

  • Inbound Idoc (From DWM to ERP) Batch No. change

    Hi all,
    Our client requrement is changing Batch no. from DWM to ERP inbound process throough IDOC when Inbound delivery is confirmed in DWM.
    I tried SMOD_V50B0001 but Batch no. is changed both DWM and ERP. It doesnt work.
    I just want to change only ERP Inbound delivery.
    Is thre any solution?
    This is DWM inbound delivery.
    Inbound delivery in ERP is also confirmed by IDOC.
    We wanna change only ERP batch no.
    Regards
    Kiichiro

    Hello Kiichiro,
    Please let us know what is the Idoc type and message type which you are using for the confirmation.
    For inbound idoc go to the function module which processes the idoc and find exit in it, then do your changes to update the batch no.
    Also please explain in detail about your requirement like, what is the structure of the idoc you are using and also batch no. is received from Idoc or to be calculated within the system.
    Regards,
    TP

  • WF-BATCH user locks up inbound IDoc processing

    Hi Experts!
    We have an issue with our inbound IDoc processing randomly being locked by the WF-BATCH user.  I have searched SAP Notes, and the only thing I could find was on Note 519420, it said to check the default settings for date format and decimal notation format in SU01.  All looked fine, except for the decimal notation which was 1.234,567.89, instead of 1,234,567.89.  If I changed this, would this fix the problem?  Any suggestions would be greatly appreciated.  Thank you in advance. 
    WC

    WF-BATCH - is an ID in SAP which processes batch workflow tasks.
    So if your IDOC posting triggers workflow task - it's going to be processed by WF-BATCH.

  • Updating transaction MD61 using information from inbound IDOC

    Is there any standard IDOC type for Planned Independent Requirement(having fields of table PBED and PBIM in its segment)?If such an IDOC type doesnt exist then i have to go for custom idoc type creation
    I have an inbound IDOC having 4 fields in its segment
    1.SAP Material number
    2.Plant
    3.Plant Quantity
    4.Requirement date
    Now i have to use this information in IDOC to update transaction MD61(create a planned order).
    constraints:
    in MD61 screen1
    SCREEN 1
    Material radio button is defaulted to on. This must also be set in the interface. Material number will be valued from the input file.
    Plant will be valued from the input file.
    Version number defaults to 00, so that value should also be used for the interface.
    Planning Horizon From and To dates will be the same date and valued from the input file.
    Planning Period should be set to D for Day
    SCREEN 2
    Material number should default from SCREEN 1 input. The interface should also do this.
    MRP Area will default from the Plant on SCREEN 1 input. The interface should also do this.
    Version will default from the 00 on SCREEN1. If needed on interface, also default to 00.
    Version Active checkbox will be checked by default.
    Base Unit of Measure will default from material master.
    Only a single date column will appear which should be the date input on SCREEN 1. Value this column with the quantity from the input file.
    Input fields are highlighted in screenshots below.
    After input is complete, use the SAVE icon to store the data.
    Kindly tell me the approach to prepare this interface?

    Done,used BAPI_REQUIREMENTS_CREATE TO DO SO

Maybe you are looking for