Inbound IDoc must trigger a workflow if shipment already exists

Hi friends, my requirement is that:
I will be getting shipment details via an Inbound IDoc into my SAP system. (IDOC_INPUT_SHPMNT) If the shipment number already exists in the system a workflow error must occur. Also the delivery number in the shipment should be validated for the shipment, if not a workflow notice should generate.
Could someone please help me in doing this.
All helpful answers will be appreciated.
Thank You

This report might help you
RSEIDOCM
Otherwise maybe in ALE customising you could create an event in a user program and use FM SAP_WAPI_START_WORKFLOW to launch your workflow.
You will have the IDOC message types coming in and the process codes which are executed so you should be able to monitor the process and take whatever action you need during the process..
(Customising -- use transaction SALE) 
cheers
jimbo

Similar Messages

  • Inbound IDOC should trigger worklfow.

    Dear Experts,
    My requirement is, when ever an Inbound IDoc is created, one workflow with that IDOC data sholud trigger.
    Problem is how to get IDoc data into workflow.
    Thanks in advance.
    Regards,
    Bala

    Whenevr you are triggering the workfLow via idoc you can pass the value to the workflow container.
    Nabheet

  • Inbound IDOC should trigger  a WF

    Hello WF Gurus,
    I have a unique requirement here. I am getting Order changes data from legacy system in an Inbound idoc.
    This Should trigger a mail to the approver with the order change data .
    If the approver approves these changes, this should flow back to the lefgacy system in the form of an outboutbound idoc which will carry order no. and the approval status.
    I am concerned about the 1st part here as using the BO - BUS 2012/2032 will not help as even though this is for Order change, the idea is to use the idoc to shoot the mail on idoc receipt and not on order change.
    The secon option is to use the BO - IDOC. However this may trigger a WF mail for every inbound idoc which is obtained.
    Please guide as to what should the BO that should be used here . And what should be my approch for this interface.
    Regards
    Dukhi Atma

    Hi viji,
    Thanks for your reply.
    I have not yet used any BO . I hope to use BO - IDOC.
    basially, i am asking if using BO-IDOC makes sense uin this scenario or do we have
    some other BO ?
    Will the idoc data be accessible at the start condition level ?
    Means can i check a field of the idoc or idoc segment and trigger or not trigger  my WF ?
    e.g lets say sales org.
    Can i set as start condtion like
    IF  idoc-data-sales org = "IN01'
        Trigger WF.
    ENDIF.
    Please let me know, if this makes sense .
    Regards
    Dukhi Atma

  • Workflow to be triggered if Inbound Idoc is successful

    Hi,
    Kindly help me out with the following senario:
    After the vendors are created in MDM, they are distributed to an R/3 (ECC 5.0) system via XI. XI uses  the message type CREMAS to distribute the vendors. When the inbound Idoc is successsful, a workflow should be triggered to the concerned user about the vendors created in the R/3 system.
    How can we find out which event gets triggered when the Idocs were successful such that we can trigger a custom/standard workflow??
    Thanks in advance
    Regards
    Kishan

    This report might help you
    RSEIDOCM
    Otherwise maybe in ALE customising you could create an event in a user program and use FM SAP_WAPI_START_WORKFLOW to launch your workflow.
    You will have the IDOC message types coming in and the process codes which are executed so you should be able to monitor the process and take whatever action you need during the process..
    (Customising -- use transaction SALE) 
    cheers
    jimbo

  • Inbound idoc ( shipment) - Status change

    Hi Experts,
    I will be getting an inbound idoc containing tracking number of the shipment from an external agent.
    I have to update this tracking number in the shipment and change the status of 'shipment Start' and 'Shipment End' to be completed.
    1. Is this status change feasible ?
    2. If so can you please guide me both to update tracking number & status .
    Thanks
    Seema

    Hi Martin,
    Thanks for the response.
    Can you tell me which basic type will suit for this among SHPMNT01 to 05. I need to get the tracking number from any of the segments.
    thanks
    Seema

  • Inbound Idoc customer number conversion

    I am new to EDI and have a question to ask you both about inbound IDOC's. We have customers sending remittance advices through EDI. The customer numbers in them are their own customer numbers. In SAP, we maintain different customer numbers. Where do the mapping of the customer numbers take place -- In the EDI subsytem itself or in SAP? If in SAP, can you let me know the procedure to do this.
    Any help will be appreciated and points awarded.
    Thanks,
    Nile.

    Hey Fren,
    1. Data Mapping
    Within the framework of SAP EDI, the conversion of a business document in IDoc format to an EDI standard format (and vice versa) is the most important task performed by a subsystem. This process is resource intensive and, hence, is better done at the subsystem level than within SAP. The following conversions and translations are carried out by the subsystem.
    Creating a control record for each inbound IDoc.
    An inbound IDoc must have a control record. The EDI subsystem builds the control record using the information stored in its local repository or from the SAP repository.
    Removing the control record during the outbound process.
    The control record in the IDoc file is used by the subsystem for housekeeping functions, such as locating the trading partner profile. The data on the control record is not needed for translating the content of the EDI documents.
    Translating data from IDoc format to EDI format.
    For an outbound transaction, the EDI subsystem converts data in the IDoc format to a suitable EDI format.
    Translating data from EDI format to IDoc format.
    For an inbound transaction, the EDI subsystem converts data in the standard EDI format to IDoc format.
    Bundling and unbundling IDocs.
    If several IDocs are passed to the EDI subsystem in one file, the subsystem separates them into individual documents. Similarly, on the inbound process the subsystem can bundle multiple IDocs into a single file to improve performance.
    2 Maintaining the Partner Profile
    A partner is defined as the business partner with whom you conduct business and exchange EDI documents. These partners are not necessarily the same as the partners in the partner profile of SAP. However, the concept is quite similar. In SAP, the partner profile maintains parameters specific to the IDoc process, and in the subsystem the partner profile maintains parameters specific to the EDI process. Some typical attributes in a partner profile are
    · A unique partner number
    · The partner type (Customer, Vendor)
    · The standard used (EDIFACT, ANSI X12, and so on)
    · The version of the EDI standard
    · The EDI message exchanged (850, 860, ORDERS, ORDCHG)
    · A functional acknowledgment flag
    3 Triggering the Inbound Process
    After receiving an inbound EDI transmission and creating an IDoc file, the subsystem is often responsible for triggering the inbound process. SAP provides a program named startrfc to start any RFC−enabled function module from the operating system level. For the EDI process, the subsystem uses the startrfc program to
    trigger the function module EDI_DATA_INCOMING. Chapter 6, "Configuring Basic EDI Components," provides the complete details and parameters of the startrfc progam.
    4 Reporting Process Status to SAP
    In an outbound process, after an IDoc has been transferred from SAP to the subsystem, SAP loses control over the process. However, SAP maintains visibility into the process by requiring the subsystem to report on the status of the process. SAP provides a file interface for the subsystem to send a status report at every milestone.
    I hope you got some idea from this process.....
    <REMOVED BY MODERATOR>
    Warm Regards,
    Abhi...
    Edited by: Alvaro Tejada Galindo on Apr 25, 2008 4:36 PM

  • How to start WF on inbound IDOC?

    Hi,
    the spec is to on every inbound IDOC to trigger an WF.
    If the IDOC has an error it works fine, but if its ok i don't konw how to catch it.
    Thanks in advance to all

    Hi,
    Try this way:
    1. For inbound IDoc processing, the event triggered is PROCESSSTATEREACHED from BOR IDOC.
    2. Create your workflow to act upon this event. You can refer to standard task TS30200090.
    3. Don't forget to create the event type linkage SWETYPV between the event and your workflow.
    Regards,
    Lim...
    Edited by: Ruslim Chang on Mar 5, 2009 2:11 AM

  • Inbound IDoc to generate Billing Document - t.code VF01

    Hi,
    which is the inbound idoc to trigger Billing Document.
    pls suggest
    thanks in advance...
    Regards,
    Balaji

    Hi,
    >IDOC name- INVOIC.INVOIC02
    INVOIC02 can only be used as outbound from VF01 not as inbound (at least in standard)
    unless you know a process code that can be used for inbound?
    in general sales invoice can only be created via interface with the use of ERS (selfbilling) scenario
    but I'm not sure if this is what you need
    Regards,
    Michal Krawczyk

  • Trigger workflow with inbound IDOC.

    Hi all,
    i have to trigger my workflow with incoming idoc which coming from other server. this IDOC content is  financial document. can any one tell me what is the procedure to make it happen.
    Regards,
    Sri harsha.M

    Hi Harsha,
    You have to call this Event FM in your ABAP program
    for example
    REPORT Z_TIBOR_EVENT_SAP_SW .
    INCLUDE <CNTN01>. " include container macros
    DATA: OBJKEY LIKE SWEINSTCOU-OBJKEY,
    EVENTID LIKE SWEDUMEVID-EVTID.
    DATA: EVENT_CONTAINER LIKE SWCONT OCCURS 0 WITH HEADER LINE.
    PARAMETERS:
    OBJTYPE LIKE SWETYPECOU-OBJTYPE DEFAULT 'BUS1001006',
    MATERIAL LIKE MARA-MATNR,
    EVENT LIKE SWETYPECOU-EVENT DEFAULT 'CREATED',
    END_DATE LIKE SYST-DATUM DEFAULT SPACE.
    OBJKEY = MATERIAL.
    CALL FUNCTION 'SWE_EVENT_CREATE'
    EXPORTING
    OBJTYPE = OBJTYPE
    OBJKEY = OBJKEY
    EVENT = EVENT
    CREATOR = ' '
    TAKE_WORKITEM_REQUESTER = ' '
    START_WITH_DELAY = ' '
    START_RECFB_SYNCHRON = ' '
    NO_COMMIT_FOR_QUEUE = ' '
    DEBUG_FLAG = ' '
    NO_LOGGING = ' '
    IDENT =
    IMPORTING
    EVENT_ID =
    TABLES
    EVENT_CONTAINER =
    EXCEPTIONS
    OBJTYPE_NOT_FOUND = 1
    OTHERS = 2
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    else.
    commit work.
    ENDIF.
    Thanks and Regards
    Prabhakar Dharmala

  • Park inbound EDI Invoices on iDoc failure from a workflow?

    Hello all,
    We have seen note 501524 that talks about parking inbound invoices by default.
    Our situation is this. We are expanding our use of EDI for inbound invoices. As such we would like to automate the validations steps as much as possible. To date with our limited use we have set up a workflow to notify on idoc failures and then a few agents have access to BD87 to make the idoc right and reprocess. We don't want to continue this process.
    Our preference would be to continue to allow the iDoc to fail, the workflow fires but at this point we communicate the failure to the appropriate person and park the invoice.
    Does this sound like a reasonable approach?
    Can we even park a red lighted iDoc?
    Once parked can the invoice be dealt with without using BD87?
    Has anyone ever tried this?
    Thanks,
    Doug

    Hi Ralph,
       In my opinion, you must have a PO Number for Invoice if you want to use standard functionality. You will probably need to create IDOC using an ABAP program which reads this file and search for PO based on the information available to you. I also notice that you are missing material number as well, how do you match the item number in the PO ?
       I don't see a way aroung without writing an ABAP program to handle this logic, but you can still use IDOC ( which comes with the standard processing logic and that is a big advantage ) so that you need to write only the PO matching logic.
      or if you are not inclined to write a separate program for uploading file into SAP and formatting IDOC, you can write your own process code (FM)for INVOICE01. Inside this process code (FM), you can put your PO matching logic and then call standard FM (process code). This is what I usually do.
    Cheers,
    Sanjeev
    Cheers,
    Sanjeev

  • Custom inbound Idoc error handling/ Workflow

    Dear Experts,
            I have a requirement where in I created a custom inbound idoc, but now i need to handle the errors in the workflow and notify the users thru workflow on an error.
    Can some one please provide me a step by step guide on how to create a organizational unit, position and assign users to the position... and any other steps that need to be configured to notify the user on the error.
    I'm pretty new to all these organizational uints and workflow related stuff. Any step by step would really be helpful.
    Thanks for your time.
    -Amit.
    Moderator message: sorry, these forums cannot replace proper training, if there is step by step guides out there, then please use the search functions.
    Edited by: Thomas Zloch on Oct 31, 2010 11:50 AM

    Vittal,
    1. If your requirement is for a SAP Standard Basic Message type and a Z extension: Then you simply have to find out the 'Standard Task' associated with basic type. You shouldn't worry about extensions. The standard task will be triggered at input error.
    2. If your requirement is for a Z basic type i.e. you have created a customer IDOC for a custom processing: There are many dependencies on how you can achieve this. Firstly, you need to know how you're are processing this Z_IDOC. Are you using a standard FM or custom workflow or custom FM? There should be some triggering event within the processing of this Z_IDOC which will raise a certain flag when the error you want to capture happens (or when there is a generic error). You can configure this event in binding objects to trigger a workflow task. If you take a look at any standard tasks, you'll get an idea how the triggering event happens.
    Once the workflow task (you can use custom task or use a standard task i.e. by triggering a standard event within the IDOC processing program) is triggered, you can either send it to SAP inbox, e-mail, trigger another processing etc. This is altogether another story.
    So bottomline: For custom IDOC processing, you need to trigger an event when error happens. This can be a custom event or a standard event. This event should be linked to a task (custom/standard - check in SWETYPV). Bind all of these in PFTC. Once the task is triggered, you can do whatever you want to do with it.

  • Creation of IS OIL TD Shipment using Inbound IDOC Processing?

    HI Expert,
    We are on IS OIL 4.72E version . As part of once of our requirement we need to process inbound shipment IDOC from SCM system and create the TD Shipment document in R/3 ..
    Delivery is already created in R/3 ; In SCM assginement of vehicle is done and IDOC is transferred to R/3.
    I want to know how to process this inbound shipment IDOC ; for creating only TD shipment not the delivery as it is already exist.. what is the process code and function module to be given in partner profile....
    Kindly explain me step by step if possible....
    Regards,
    Adityakumar Waghmode

    Hi,
    Function module field is used to define the path functionality of file generated.
    EDI_PATH_CREATE_CLIENT_DOCNUM is the recommned fucntion by SAP .
    Function is used to prevent unprocessed files being overwritten.Tihs function generates file directory path dynamically.
    Hope this helps.
    Thanks.
    Mark points if helpful.

  • Create shipment from inbound IDOC SHPMNT05 ?

    Hello All,
    I would like to create an individual shipment when i receive from a partner an inbound IDOC.
    I'm using Message type SHPMNT, Basic Type SHPMNT05, Process Code: SHPM and testing in WE19 via FM IDOC_INPUT_SHPMNT.
    How can I start the creation of the shipment with this inbound IDOC ?
    Is it possible ? or is it necessary  to develop in user-exit the code to create shipment with function module (which one ? BAPI_CREATE_SHIPMENT ?)? 
    Thanks a lot,
    My

    Hello Reddy
    thanks for your answer.
    is there particular customizing to be done ?
    i exactly use function BORES_IDOC_INPUT_SHPMNT
    The inbound idoc is generated but i have the following status message 51 "Application document not posted"
    What does it mean ? a problem of data in the inbound IDOC to create the shipment ?
    Thanks a lot
    MY

  • Inbound idoc processing by workflow

    Hello,
    How can I find if an inbound IDoc has been processed via workflow ?
    following are details -
    1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
    2)manual re process in test system using WE19 has all four status records by login user ID.
    3)BD67 values for this process code was checked for the start events.
    4)I checked standard task 30200090 following oss note 325361
    5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020 
    I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
    thank you very much in advance,
    Bhakti

    Hello,
    How can I find if an inbound IDoc has been processed via workflow ?
    following are details -
    1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
    2)manual re process in test system using WE19 has all four status records by login user ID.
    3)BD67 values for this process code was checked for the start events.
    4)I checked standard task 30200090 following oss note 325361
    5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020 
    I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
    thank you very much in advance,
    Bhakti

  • How to trigger change documents based on inbound-idoc?

    Hi experts,
    Currently I'm working in on a project where I have to create an interface based on IDOCS. This is an interface for two SAP-HR systems.
    If there are made changes in the dialog (gui) by a user, there will be created a change document, which can be displayed by report RPUAUD00. For the inbound-interface based on idocs it's important that there will also be created a change document in the system based on this idoc. We have tested this, but no change document is created.
    Can anybody help me to solve this problem: "How to create a change document based on the inbound-idoc?"
    Thanks in advance.
    With kind regards,
    Roy

    Thanks for responding. First, I like the idea of defining an event, but I'm still stuck with how to trigger it. I looked at dynamically registering events, and maybe doing something where a click on the graph control registers an event for key presses on the vi. I'd still have to figure out out to terminate the key press event. Unfortunately, (actually it's a feature I like..) there are a number of different ways to complete typing in a scale change. I routinely use ctr-enter (habit from working on a laptop), though enter works fine, and clicking somewhere else is probably the most common method. I am not that familar with User Defined Events, so I may be overlooking something obvious here.
    The graphs are a Bode Plot, with a seperate graph for RPM vs Phase Lag, and RPM vs Magnitude. I want them to always be plotted on the same x-axis. The plot is generated when the user doubleclicks on a dataset. After that, it's just the user looking at it. They can change the axis without any new data being generated.
    Thanks,
    Chris

Maybe you are looking for