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

Similar Messages

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

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

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

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

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

Inbound idoc posting directly even with 'Trigger by background' option

We have inbound idocs coming into ECC from Siebel via PI. The partner profile is setup for "Trigger by background program' .So that we can run the job RBDAPP01 to sweep these status 64 idocs. But we don't get a chance as the idocs are getting posted directly(its already in status 51 or 53) as if we used the 'Trigger Immediately' option. Where could the problem lie ? Is there a possibility of some RFC call from PI overriding the Partner Profile config ? Any advice or useful tip is welcome!
thanks,
S

Hi,
I guess you can still check in the control record for EDIDC-EXPRSS - Overriding in inbound processing, the documentation of the Data Element EDI_EXPRSS is as below
Short Text
Overriding in inbound processing
General
This field determines for ALE whether a time schedule is to be deactivated for inbound processing and replaced by immediate processing.
Regards,
Chen

Trigger an outbound idoc to sender system after inbound idoc has status 53

Hi all,
We have two different partners (say A and B)which send inbound idoc to ECC of same message type WMMBXY. This updates goods movement. The partner A collects the idocs(WE20 partner profile setting) and partner B trigger's immediately. Now our requirement is after successful processing of idocs (satus 53) we need to send another type of idocs to the sender regarding the updation/ changes occured in ECC.
Since partner A collects the idocs how can we check that it reaches 53 status and send the outbound idoc to A.
Kindly help me in solving this issue.
Thanks,
Aravind

Create a new process code WMMB to ZMMB & assign a FM ZL_IDOC_INPUT_WMMBXY
& call the standard FM L_IDOC_INPUT_WMMBXY , check the status or any error other wise create a new IDOC using
Master_IDOC_CREATE, hope the solution works for you

EOIO should be enabled for Inbound IDocs to SAP

Hi All,
My Interface requirement:
i want to send my IDoC's to SAP ECC from SAP PI using IDoc Adapter in EOIO manner. so i have followed the below link.
http://help.sap.com/saphelp_nwpi71/helpdata/EN/96/791c42375d5033e10000000a155106/frameset.htm
1)I have have enabled EOIO in sender File adapter.
2)i have checked the Queue Processing in IDoC adapter.
assumed that IDocs are processing in EOIO manner. for proving the same, i have stopped the RFCUSER which is in ECC to process the IDOCs to SAP.
but still messages are stuck in Trfc queue, so i am thinking that EOIO is not enabled as messages are not stuck in SMQ1.
how to achive EOIO for inbound IDoCS??
Thank You,
Madhav

Hi
It's fine that messages are not stuck in smq2 on PI side. You set in smq1 system, connection and assing connetion pool numer and meesage is transfered to Ecc using common connection. On target Ecc check tcode WEINBQUEUE.
Br
Maciej

How to trigger outbound IDOC when data changed in BP through Inbound IDOC.

Hi,
    In our system whenever we create a new Business Partner, these data is send across to SAP R/3 (as BDOC) and to Mainframe system (as outbound IDOC). Whenever we change any Business Partner record the data is send across to SAP R/3 (BDOC) and to Mainframe system (as outbound IDOC).
    This functionality is working fine.
    Currently we are getting a value for one standard field (Customer_Group3) of Business Partner as an inbound IDOC. The value of the inbound IDOC is reflecting in the field (Customer_Group3) in Business Partner Transaction. Once the inbound IDOC is received, the modified value is send across to SAP R/3 as BDOC. But the modified value is not send across to Mainframe system (outbound IDOC). The outbound IDOC is not getting triggered.
Kindly help

Is your mainframe system configured as Site in SMOEAC. If so are you using XIF Adapter.

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.

Help required in posting inbound idocs

Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George

Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George

Message variant is missing in INBOUND IDOC.

hi,
Any one can help on this issue?
The sender has confirmed that message variant was filled in outgoing file.
However, When we received this Inbound IDOC, the message variant is blank.
I still am confused by two questions:
1. The function module which insert record into table EDIDC and EDIDD, is same as the function module which post this IDOC to sap module(normally we maintained it in WE57)
2. We normally need to maintained in WE57, but also need create one processing code, what is relationship between WE57 and processing code(WE42)

Hi,
Message Type/Message Variant needs to be maintained in WE20 ( Partner Profiles). In case of inbound IDOC ( receiving the data other systems) Data processing/posting will happens via function module. the function module will attach to the process code.
Process Code : The IDoc interface uses the process code to find the business process which controls the conversion of the IDoc into the SAP document.
The Process code will assign to the function module in WE42, the same function module will assign to the Message type and Idoc type in WE57
In a short summary, The Function module required to post the Idoc/update the data in SAP. However the Function module should process specific to the Message type and Idoc type only. It means the settings is required to identrify the correct function module to process the Inbound Idocs.
Whenever there is a problem with ALE setting the message 64 will trigger, it means the IDOC is ready to transfer to the application ( process through FM ).
Thanks,
Kiran.

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.

EDI Inbound Idoc problem

Hi,
We are facing an issue with Inbound IDoc.
We have a PO inbound idoc which is in status '53' but the PO document did not get created.
Can you please help us if anyone faced similar issue.
Thanks,
Anil

Hello,
sounds strange.
1. check the status record of 53 Idocs you should find a message like: Standard oder nnnnnnnnnn has been saved.
2. If order number nnnnnnnnnnn does not exists check transaction SM13, ST22 for errors.
3. for testing change inbound options in WE20 to <trigger by background programm> and book the idoc in forground.

Inbound IDOC should trigger worklfow.

Similar Messages

Maybe you are looking for