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

Similar Messages

Vendor Outbound IDoc and Unblock Indicator...

Hi All,
I am using an outbound IDoc to pass on the information of vendor master to a legacy system via PI. Basic type I am using for the same is CREMAS05.
Now, when I am unblocking a vendor via XK05 and when I am changing the data of vendor, I am not able to make a difference between these 2 scenarios.
If vendor data is changed, I need to send the legacy system an action flag as 'C'; if vendor is unblocked, I need to send the legacy system an action flag as 'U'.
So, could somebody please let me know how can I differentiate based on IDoc data if vendor is changed or is unblocked.
Any suggestions are really appreciated.
Thanks in advance.
Regards,
Richa

Thanks for answer.
but, Serialization process will have two message type each one for Vednor mater and Addres and seriallise the Idoc i.e. two Outbound Idoc will be created.
But I want ONLY I Idoc to be created which should have Vendor Master data and also address Data.
~Pramod

How could i get a list of outbound idocs and read them via RFC?

So I need to fullfill the following szenario:
.) my application has to retreive latest iDoc (outbound queue) from the SAP ERP
.) processing payload of iDoc
.) set the IDOC in SAP R3 to 'OK'
Are there any RFC functions for LIST all Outound IDOCs and one for setting the idoc state?
Thanking you very much in advance for helping me
best regards
Thomas Lustig

It sounds like you really might want to consider seeking legal advice for this matter.

Outbound idoc resend

Hi all . I have come up with a requriement. The scenario is as the following
    once we raise a sales order and save it ,an outbound IDOC gets triggered and send to the customer via EDI. after some time customer asks for one more copy and there is a need to change the values of some of the fields and resend to the customer. This can be done in two ways
1.Go to va02 make the requried changes and issue the output
2. change the idoc which is already processed and resend it
    our client wants to go for the second option.
Can anyone help me out
1.' Where we can change and resend an already processed outbound idoc '?
2.if we make any changes in an outbound idoc at idoc processing level will the changes reflect in the order?
3. Can we restrict the user to change certain fields only?
Any inputs given by you people will help me a lot.
Thanks in advance
Srini

Hi srini,
As i Understand the senario, Their might be some changes to the document required by the customer. This also needs to reflect in the changes in Order.
It will be complex way to update both the IDOC and order, if you are changing in the IDOC and resending it. It would be more wise to go ahead with the first option making changes in through VA02 and then sending it accross . And most of the companies do not hold the IDOCs for too long & hence it would be wise to make changes in VA02 and send the IDOC once more. This can be done by minor code change based on the edit checks business wants to perform.
Well if you still want to go ahead with the second option here are answer to the questions.
.' Where we can change and resend an already processed outbound idoc '?
First the IDOC status needs to be changed from program RC1_IDOC_SEt_status
then you need to reporces it throught program RSEout00
2.if we make any changes in an outbound idoc at idoc processing level will the changes reflect in the order?
The changes will not reflect in the order unless you have a code written in SAPLxved.
3. It is not possible to restirct the change to certian fields only.
Reward points if this helps
Thanks,
Kamal
Message was edited by:
        Kamalakar vp

Urgent --- How to resend an outbound IDoc which is in status 03

Hi Experts,
I've a rquirement to resend an outbound IDoc which is in status 03. I don't want to use BD87 or WE19 to reprocess.
Please provide me some FM or some technique by which I may use in a Z-program to accomplish the above requirement.
Even if IDoc no is changed....that won't cause any problem....i just need to resend the IDoc.
Thnx in advance
Rudresh
Mumbai

Test: Outbound Processing from IDoc
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated, to allow the test program to intervene. You can make sure that this is the case by setting the output mode to "Collect IDocs" in the partner profile for the IDoc interface. If you now generate an outbound IDoc for the partner (for example, via the application or the test tool), the IDoc is only generated in the R/3 System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report
RSEOUT00, which is also generally scheduled with the output mode "Collect IDocs" in live operation.
Activities
Start the test program from the initial node of the IDoc interface by selecting Test ® Outbound from IDoc.
You can decide whether the output mode is set to "Start subsystem" or "Do not start subsystem" in the partner profile. This defines whether the external (sub) system processes the IDocs further.

Steps for configuring Outbound Idoc OILSHI01

Hi experts,
    can anybody tell me the steps how to configure an Outbound IDOC.
    It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
    if not anything else will also do.
    Kindly give me steps in detailed. Since i have never done this. Including
    distribution modle (BD64). in which case it generates the Automatic Partner
    profiles.?
<REMOVED BY MODERATOR>
Regards,
Umesh
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

Hi Umesh,
Sorry for the late reply. Let me clear your couple of misconceptions first.
Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
Now the further steps:
Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
2. Again, ask your functional consultant, as to which output type is configured for your business transaction. Select that output type and go to "Processing routines".
3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc.
Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
     a. trigger the idoc on saving the doucment. this triggers idoc as soon as you save the idoc.
     b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
     c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
Hope this was helpful.
<REMOVED BY MODERATOR>
Cheers,
Karan
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM

Trying to change Inbound IDOC to Outbound IDOC for testing....

Hi Friends,
I am trying to do the following
1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
HELP!! Rewards

Hi Friend,
        The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
Use
You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an empty IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
Activities
·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the file type. The default file is the inbound file entered there.
·        You generate the IDoc using .
The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
·        Click on the white fields to change data in the segments.
In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
·        The additional procedure depends on whether you want to test inbound or outbound processing.
Test: Outbound Processing from MC
Use
Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
Prerequisites
You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
·        Customer or vendor records
·        Material records
·        Info records
·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as messages from the respective application.
The appropriate file ports and partner profiles must exist in the IDoc Interface.
Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to 1 (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
Activities
Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to Collect IDocs in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode Collect IDocs in live operation.
Activities
You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
You can decide whether the output mode is set to Start subsystem or Do not start subsystem in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Use
This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to File.
Prerequisites
A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are credited to the relevant IDoc in the form of status records in the SAP System.
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
Test: Inbound Processing: Modified Outbound File
Use
This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to File.
Prerequisites
You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type File must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
Standard inbound processing is then triggered;
·        Reading the modified file
·        Generating the IDoc(s) in the SAP System
·        Processing in the application
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
The recipient in this case is the SAP System. The port is used for identification purposes:
·        SAP (for example RSMITH
Test: Inbound Processing: Original Inbound File
Use
This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
Prerequisites
You require a correct inbound file. In this case, correct means that the:
·        Sender and recipient in the control record are correct
·        Direction in the control record is set to 2 (inbound)
·        Client in the control record and data records are correct or empty
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
The file is deleted after being read successfully!
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
·        Inbound port
·        Name and directory of the file
These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
Thanks

Duplicate Outbound IDocs getting Triggered at the same time.

Hi Folks,
I have created custom outbound idoc and done all the configurations required like WE20, WE30, WE31, WE81, WE82, WE 41, WE57 etc.
Also I have written my code to populate segments and then call MASTER_IDOC_DISTRIBUTE in the custom function module which is assigned to the process code and also done the configurations like we57 etc. for the same.
Now when I trigger my output type from VL74 transaction, I noticed two entries in we02 resulting in two IDocs generated for 1 HU.
The difference in two IDocs is the first IDoc getting generated in error with status 29. While the second one as success with status 03.
The data records containing segments have same values for both the IDocs number.
Whether the configuration is a issue here or problem in code of custom fm?
Please help.

Hi Anil,
Appreciate your quick response.
In my custom FM I have populated an internal table it_master_idoc_data with two records of two segments, containing segment name in SEGNAM filed and segment data in SDATA field.
Please let me know whether the data in this internal table of structure EDIDD sufficient for passing to MASTER_IDOC_DISTRIBUTE FM? Or do I need to populate any other field of EDIDD.
Also I am exporting a structure master_idoc_control containing values in this 5 fields.
MESTYP = Z message type, Z IDOCTP, partner and details in RCVPOR, RCVPRN, RCVPRT fields.
I am not populating the internal table communication_idoc_control while calling FM MASTER_IDOC_DISTRIBUTE from my custom function module.
After executing MASTER_IDOC_DISTRIBUTE FM, when the control comes back to my custom FM there is one record in communication_idoc_control internal table with IDoc number in DOCNUM field with status 29(error). Now when we check in WE02 there are two IDocs generated after this transaction's execution.
The first one in error which FM MASTER_IDOC_DISTRIBUTE returns and second one in success with status 03.
Please help....
Thanks,
Pravesh

Validation on outbound idoc

Hello team
I have the below requirement now. please check and suggest me
1. i am sending outbound MATMAS05 idoc from SAP system. but i want to do few validations on the data of idoc (for example i will check the value of plant data with some other value of the table). if my checking is success then only i need to create outbound idoc and send it to downstream systems.
So now i want to know where i need to write the code which performs the validations against the data before creating/posting of idoc.
Please suggest me.
Regards
Raj

Vinod
Dont mine of asking little more clarification. you mean to say go MM01 and find out the package (ie MGA) and then goto SMOD and findout the exits right.
But when check in this way, i didnt find the enhancment MGV00001 you have provided.
please tell me the procedure to check in a detail way. i want to know how can we check for the related enhancments for any idoc type. please tell me to check for MATMAS05 as an example, i will use the same techinque for any idoc type.
Regards
Raj

Outbound Idocs in 03 status

How do these get processed to be sent to the external system...in this case XI. They are setup as "Transfer idoc Immediately" but I am not sure what to execute to get them to process....message type WP_PLU....Thank-You

Test: Outbound Processing from IDoc
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated, to allow the test program to intervene. You can make sure that this is the case by setting the output mode to "Collect IDocs" in the partner profile for the IDoc interface. If you now generate an outbound IDoc for the partner (for example, via the application or the test tool), the IDoc is only generated in the R/3 System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode "Collect IDocs" in live operation.
Activities
Start the test program from the initial node of the IDoc interface by selecting Test ® Outbound from IDoc.
You can decide whether the output mode is set to "Start subsystem" or "Do not start subsystem" in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Thanks,

Process Code in outbound IDOC

Hi,
We have created a process code for outbound IDOC and assigned an FM to it.In that FM, code is written to generate an IDOC(FM 'master_idoc_distribute').Please let us know how to trigger the outbound IDOC using the process code.Are there any FM or standard programs??
Regards
Prathima

Hi Prathima,
For outbond Idoc you have to define the output parameters for the corresponding Partner profile (transaction WE20). Look there that there is a tab called Messages control to specify and aplication, a message class and a process code. Is here where you have to add the process code.
The application/message is responsible of select the data adapted for the FM linked to the process code.
Reward points if helps.
Roger

Converting Inbound idoc to Outbound idoc

Hii,,
How to convert inbound idoc to outbound idoc.
I have IDOC -> SOAP -> IDOC Scenario.
In case of error at SOAP side , it return idoc with 51 status.
Now i need to convert the Inbound idocs to Outbound Idocs and send it back to the Sender system...
How to do accomplish this??
Regards,
Siya

Hii,
By using we19 and by exchanging sender & receiver we can convert outbound idoc to inbound idoc.
Just want to confirm is it proper way??
Regards,
Siya

SLSRPT Inbound or Outbound idoc ?

is SLSRPT inbound idoc or outbound idoc and what is the Process code used ?
Thanks
Praveen chindam.

Hi Praveen,
Welcome to sdn.
This function allows you to receive and process the following types of partner transmissions in CRM:
· Resale Report u2013 (ANSI X12; EDI 867, Message Type SLSRPT)
it is an inbound idoc.
see this link
http://repository.edifice.org/migs/slsrpt3/compare.htm
thanks
trinadh

How to trigger an Outbound IDOC with a default status 68

Hi,
How an Outbound IDOC can be created/triggered with a default status 68??
I have a requirement where the outbound IDOC should always get created with status 68. Once an Outbound IDOC is created, I should not be changing its status manually or using a program.
Basically we don't want any IDOCs created in other status and changing to 68 once an IDOC is created with a different status.
Currently i'm using fm 'IDOC_OUTPUT_DELVRY' to trigger an outbound idoc, and the idocs are triggered with different status 30, 2, 3 etc... By using a program i can change the status of the IDOC. But what we need is "Whenever an outbound idoc is triggered, it should always have status 68".
Please let me know the ways to achieve this functionality.
Thanks!

Hi,
We need to display all the IDOC data on a Smartform layout. But we dont need the IDOC to be used for our requirement. So we want to make sure that IDOC is triggered but will not stay in 02 or other status.
We have a process to monitor the failed idocs (02 status) and we do not want our idoc to have failed status. So we need the idocs to be tirggered directly with status 31 (thanks for letting me know that i cant use status 68 for outbound idocs).
Thanks!

Scheduling inbound and outbound idoc processing

Hi everybody.
I ´d ike to know which is the best way to schecule the outbound and inbound idoc process.
Nowadays we are using this:
INBOUND PROCESSING
- In WE20 the idocs are checked with "Trigger with a background program".
- The program RBDAPP01 is scheduled with a job to trigger the process of the inbound idocs.
OUTBOUND PROCESSING
- The program RBDMIDOC is scheduled to create the idocs than have been created with change pointers.
- The program RSEOUT00 is scheduled with a job to trigger the process of the outbound idocs.
Is there any better option to improve de perfomance????
Edited by: Christian Abad Chico on Nov 13, 2009 10:09 AM

Any answer

Editing an Outbound Idoc and resending

Similar Messages

Maybe you are looking for