Event raised upon successful outbound idoc INVOIC

Is there any event that I can use to trigger a workflow when an INVOIC02 idoc is created successfully?
This is an SD billing document created from VF01. output type RD00
I want to use workflow to take that idoc, transform it to another format, then send it off.
I'd like to trigger this follow on function from a successfull idoc event.
I've tried IDOC.processStateReached and IDOC.statusIDocProcessed. They don't seen to be raised when I create the idoc.
The events in IDOCINVOIC only relate to inbound idocs.
I can only find inbound or failure events. Not outbound success events.
Thanks

Hi-
I want to use workflow to take that idoc, transform it to another format, then send it off.
I'd like to trigger this follow on function from a successfull idoc event.
I am not sure, why to use workflow to transfer the idoc. Normally after creation of successfull idoc, ECC will send the idoc to other middleware like PI and they will convert and transform the idoc
ok, If you need to trigger the workflow for success idoc, then are you creating idoc immediately after creating billing document or using batch job process?. This you will be configuring in NACE
If it is batch job process, then you need to check prog- RSNAST00 (which will be scheduled periodically to create idoc) and check any way to enhance to add logic to trigger workflow for success idoc, else, you could create a copy of std and make change
Vinoth

Similar Messages

Editing an Outbound Idoc and resending

Hello all,
I have looked but can't find the answer to my questions.
I have an outbound idoc (invoice) - I have used BD87 to edit the idoc. the idoc is now in a status of 32.
How do I resend this idoc?
when I hit process I am taken to a screen showing me
Idoc |Old Status|New Staus|Status Text |Error Text
5917058 |32 | |Doc was edited |Changed data record was saved
How do I resend the edited idoc?
I know the answer is simple - I just don't see it.
Thanks
Edited by: Helen Wadino on Nov 11, 2008 3:57 PM

I believe you created a new idoc num with the BD87 after editing. The old idoc num is still there and probably failed. Did you try re-submitting the new stat 32 idoc in BD87?
Or, you may want change the status of the idoc:
PARAMETERS: docnum like edidc-docnum.
update edids set status = '30' where docnum eq docnum and status eq '03'.
Edited by: Tom M. on Nov 11, 2008 4:00 PM
Edited by: Tom M. on Nov 11, 2008 4:01 PM
Edited by: Tom M. on Nov 11, 2008 4:07 PM

Raise an event when an idoc invoice (INVOIC02) gets created in error

Hi All,
Im trying to generate an email message from an output invoice when processed incorrectly.
I created a subtype of IDOCINVOIC, updated the linkage table using swe2 but the events are not raised when I go to re-issue my invoice output.
I know its possible to raise these events in idoc invoice exit ZXEDFU02 but the status is not created at this stage.
Is it possible to raise an event when an idoc invoice gets created in error?
King Regards
Ann

@CoolDadTX -That's because I've written com servers in the past using VB.net, however they were not registered with the Running object table.
What I'm trying to do in this case is have an application that will be started by the user, and then they will start another application written in .Net to connect to that first application. The reason for this is that we have an application
written in an old version of smalltalk that doesn't seem to support getObject but can create an IUknown, and we already have base classes to attach to COM objects written in .Net. As this new application needs to be started first it can't be tightly
coupled to the legacy application, so we are trying to register the new application and then connect a Dotnet Client that is being started through a COM Interface from the legacy application. I know it's convoluted but we need to keep the legacy
application alive for a bit longer while we rewrite it as an add-in for the new application.
The article that you linked to has been very helpful on the server side, but do you have any ideas as to how I can connect the sink on the client side in C#?

Is it possible to generate outbound idocs for FI invoices? How?

Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

Dear Gabriel
Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP. However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
thanks
G. Lakshmipathi

Outbound EDI Invoice IDOC

Hi ,
I have a requirement for Outbound EDI invoice where I need to validate something at the control record level and if it fails i need to Error out the IDOC say status 51 or any status in RED with my custom status message.
I tried raising the exception in my user exit and it did'nt create the IDOC itself but i need the IDOC created with error status. Are there any other User exits in RSNAST00 or even in RSEOUT00 before i write it to the file.? Basic idea is not to send the IDOC to sub system and reprocess it after correction.
Any ideas on how to do this is really appreciated!!
Thanks,
Naveed.
Edited by: Alvaro Tejada Galindo on Mar 10, 2008 4:22 PM

Hi ..
Am using the process code SD09..
Veni, The user exits you mentioned, there is no error table to fill with..all i was able to do is raise an exception which is not creating the IDOC itself..
There is a FM 'IDOC_STATUS_WRITE_TO_DATABASE' that i want to try .it needs the IDOC number but i dont have the IDOC no in any of the user exits in FM IDOC_OUTPUT_INVOIC...i need some user exit beyond that FM..
Any ideas??

How to debug outbound Idoc function module for invoice

I have to debug the outbound IDOC function module and UserExit for invoice message type INVOIC, process code SD09, function module is IDOC_OUTPUT_INVOIC and user exit for the function module LVEDF001.
I tried putting the break point in function module IDOC_OUTPUT_INVOIC and recreate the IDOC using WE19 but it creates the idoc but does not stop at the break point. I have also tried generation of idoc through VF02. It again creates the idoc but does not stop at the function module.
Please let me know if I am missing any thing and not doing it right.
Appreciate your help.
Rohit

Hi Ali,
I faced the same problem. Thing is the break point is not getting triggered when i ran tha IDOC through WE19.
What i have done is i created a project for my exit in CMOD and kept some junk code in the exit and executed it through BD21. Then the Break point got triggered. See if it works.
Regards,
Uday S.

Outbound Idoc after created Invoice document

Hi All,
May i know how to create outbound idoc after invoice document created.
Because i just found out some solution for inbound idoc.
Regards,
Luke

You need to set up the Output type using the NACE tcode and this output type should be configured to trigger the IDOC. Check the below link.
http://www.erpgenie.com/sapedi/messagecontrol.htm
This output type can be linked with the IDOC type in WE20 tcode.
~Srini
Edited by: VaasPal on Dec 22, 2011 8:13 AM

How to generate an outbound IDOC for customer Invoice

Hi
I want to configure that if I create a invoice using TCODE FB70 it should automatically create a outbound IDOC ACC_BILLING( for customer).How I can achieve this. Can any one give me complete step by step help.
thanks in advance.
karunb

You should be able to use it using 'change pointers'.
For this you will first need to activate change pointer for this message type (check SALE > modelling..>Master data distribution). Next, you will need to setup your ALE config for this IDOC/message type.
In ALE, you will be able to either run a standard SAP report adhoc, or schedule it such that all changes recorded using change pointer (changes including new customerr records) are collected as IDOCs and sent.
This is a standard SAP scenario, you only need to do the config/setup to get there. You may wish to read more on change pointers to understand this.
cheers,

Outbound Idoc from FI Customer Invoice

Hello,
Does anyone know if it is possible to create an outbound Idoc originating from an FI Invoice for a customer? Specifically, we are trying to do this for an interest invoice. I would think that we might be able to create a correspondence type that would do this, however I am unable to find any documentation on this functionality.
Thanks,
Mark

Hello,
For the texts you can try a subsutition, specifically the exit program or use a BTE via the FIBF transaction.
Mark as helpful.
Regards
Waza

Create event Outbound Idoc

Hi Community,
I configured all to send by Nast an outbound idoc DELVRY03 message type DESADV.
Now I wish to know idoc number e its status in order to update custom table about process.
Is there some event (like Created) that I could catch after the idoc is created? Have you any suggestion to solve my trouble?
thanks in advance,
Frank

hi ,
Check in trx WE05 for idoc list.
there u can get idocno,status,...
Cheers
ALfred
Reward points for helpful answers.

NetConnection.connected is false upon receiving NetStatus event "NetConnection.Connect.Success"

I can only reproduce this on Chrome with a non-debug version of Flash.
I can see that "NetConnection.connected" is still false after receiving NetStatus event "NetConnection.Connect.Success".
1. I wonder whether this issue only applies to certain versions.
2. Using a netConnection which is not connected to create a NetStream populates an "arugment error". I wonder what would be the safe thing to do here? Perhaps after receiving the NetConnection.Connect.Success, check "NetConnection.connected" before using it to create the NetStream?

Are you sure your FMS is up - NetConnection.Connect.Failed comes when client was not able to reach server kind - which would happen when FMS is down or your FMS is running on some other machine and your client is on some other machine as i see you are using localhost. If your FMS is one "A" machine and your client in on "B" machine please put "ip address" or "domain name" of "A" machine where FMS is in Netconnection URI i.e. "rtmp://ipaddressofA/live"
my fms is on and it is on the same computer as my flash document

OUTBOUND IDOC DEBUGGING

I have Output type defined for the application V3
i.e meant for Billing.and the output type is custom development with name ZD00 for invoice-Bill to.
This output type is defined for edi processing.
Now the problem is when invoice is created and this
outputtype is selected the quantity field in idoc and invoice differs.just get double in idoc.but if the same output is fired again data in idoc gets corrected.now i want to debug the idoc outbound processing.what i did i run the transaction we41 and find the process code and find the function module that is running in the background for collection of data of invoice and
filling the idoc.but but but the problem is i put break point in the function module to check the value at run time but this is not triggered . iam confused tell me how to debug the outbound idoc.
Help me out i will be waiting for the response.

Hi,
You can use the Update Debugging. If you know the prognam name/function module of your source code, upon saving your document, a new screen will pop up if the Update Debugging mode is on. From this, you can then hit F8 to stop on your break-point.
Let me know if you need further help.
Thanks,
Eric

About Orders05 outbound Idoc.

Hi,
I am using an outbound idoc of basic type Orders05 with an extension of the idoc header segment.This outbound idoc will get triggered once a PO is saved and sent through EDI.
I have to do an enhancement wherein I have to populate the mode of transport field(EXPVZ) and place of loading(LADEL) in the fields of the extended segment selecting them from EIKP depending upon the BELNR value in the header of the idoc(E1EDK01-BELNR).
I am unable to understand how do I populate the fields.
Could you please help me.
Thanks,
Sandeep.

HI,
see the below steps you will completely understand the processing outbound..
2.1 Outbound Interface
PROCESS DIAGRAM
Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
 Enter segment name and click on Create.
 The name of the segment type must start with Z1 , and have a maximum of eight characters.
 Enter description and enter the relevant field names and data elements.
 The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
 Save the segment and enter Person Responsible and Processing Person .
 Go to Edit and Set Release.
 Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
 Enter segment name (starting with Z), click on Basic Type and then Create.
 Create as new, enter Person Responsible and Processing Person and enter description.
 On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
 Complete relevant fields in the Maintain Attributes screen:
 From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
 The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
 The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
 Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
 When IDOC created return to initial screen. Go to Edit and Set Release.
 Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
 Display/Change and click on New Entries
 Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
 Display/Change and then click on New Entries.
 Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
 WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
 BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
 Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
 The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
 c_SEGMENT_type1.
 The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
 The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
 NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
 The ALE Layer handles the sending of the IDOC to the receiving system.
 Error Handling (see Step 7b).
 Commit work.
Project Specific
Step 7b Error Handling Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
 Declare a structure of type MCMAILOBJ for sending instructions.
 Enter values for the internal table based on structure MCMAILOBJ
 For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
 Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
 MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
 Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
 Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
 Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
 Enter your message type and execute.
 Status should be green, double click on one of the Idocs you have created to view its contents.
 If a problem has occurred click on Status which will give you a description of the error.
 Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
 Click on each individual segment and view the content to check that the correct data has been read.
 If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
rewards if useful
regards,
nazeer

Recommended Status Codes usage for Inbound & Outbound IDocs

Hi,
Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
I assume we use 51 for Posting Program (not 56) and
26 for a Z-Selection Program (Not 37 or any other Code).
Please let me know what is recommended and which status codes most of the people use while Custom Development.
Thanks and Regards,
Venkat.

Hi,
Outbound IDOC Status Codes
The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
Outbound IDOCs
Code Error Event Severity SAP Meaning
02 Yes Error Error passing data to port
03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
04 Yes Error Control information of EDI subsystem
05 Yes Error Translation
06 No Harmless Translation
07 Yes Error Syntax check
08 No Harmless Syntax check
09 Yes Error Interchange handling
10 No Harmless Interchange handling
11 Yes Error Dispatch
12, 13, 14 No Harmless OK
15 Yes Warning Interchange acknowledgement negative
16 No Harmless Functional acknowledgement
17 Yes Warning Functional acknowledgement negative
18 No Harmless Triggering EDI subsystem
20 Yes Error Triggering EDI subsystem
22 No Harmless Dispatch OK, acknowledgement still due
23 Yes Error Retransmission
24 No Harmless Control information of EDI subsystem
25 Yes Warning Processing despite syntax error
26 Yes Error Syntax check
27 Yes Error ALE error
29 Yes Error Error in ALE services
30 No Harmless Ready for dispatch (ALE)
31 No Harmless IDOC is marked for deletion
33 No Harmless Original of an IDOC which was edited
34 Yes Error Error in control record of IDOC
36 Yes Error Timeout error; electronic signature not performed
37 Yes Error IDOC added incorrectly
38 No Harmless IDOC archived
39 No Harmless Receive confirmed
40 Yes Error Application document not created in target system
41 No Harmless Application document created in target document
Inbound IDOC Status Codes
The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
Inbound IDOCs
Code Error Event Severity SAP Meaning
51, 52 Yes Error Posting error
53 No Harmless Posting successful
54 Yes Error Error during formal application check
55 No Harmless Formal application check
56 Yes Error IDOC with error added
60 Yes Error Syntax error
61 Yes Warning Processing despite syntax error
62 No Harmless IDOC passed to application
63 Yes Error Error passing IDOC to application
64 No Harmless IDOC ready to be passed to application
65 Yes Error ALE error
68 No Harmless IDOC is marked for deletion
70 No Harmless Original of an IDOC which was edited
73 No Harmless IDOC archived
Regards,
Raj.

Multiple changes per HMRD outbound IDoc

We are currently implementing HR (SAP ECC 6.0) and having a problem with HRMD outbound IDocs.
Currently the system is creating a change pointer each time an Employee record is changed - we then run RBDMIDOC for the message type and it creates one IDoc for all changed employees using message type HRMD_A07.
However, we'd like to have one IDoc per employee change - so if 10 employees are changed we get 10 IDocs. Is this possible? (The reason is that the recipient system will send an ALEAUD message for each IDoc and we want to be able to identify the specific employee that failed in the event of any errors).
I think the problem is caused by the message type HRMD_A07 having a maximum of 9999999999 E1PLOGI segments. We don't want to create a bespoke message type so any suggestions would be appreciated.
Thanks and regards,
JB

I don't think there is standard program to handle the scenario. But my suggestion is to create Z Report.
Inside the Z report the call the Standard function module
CHANGE_POINTERS_READ which will return the change pointers, from the list of change pointer get the objects for which IDOC needs to be generated.
With this data call the standard report RHALEINI, in a loop for each employee.
The report will generate an IDOC for each call. U can check whether the IDOC is generated or not, by importing values from the memory ID COMM_HRMD_A into table COMM_CONTROL. if IDOC is generated successfully, call the functon module CHANGE_POINTERS_STATUS_WRITE to update the status of the change pointers.
This logic will Useful. Kindly award points, if satisfies ur requiement
With regards
K.Varadharajan

Event raised upon successful outbound idoc INVOIC

Similar Messages

Maybe you are looking for