Re send a succesfukl idoc.

Hi Experts,
I have send an IDOC and it shows success in we03. Status 03. I want to resend it. The same Idoc, with respect to it's IDOC No. Can it be done???..If positive, pls tell me the process. !!
Arnab

>
Arnab Mondal wrote:
> Rainer....U r wrong....It can be done using we19. We can put the idoc no and resend it. Thanks to all.
What is the Approach you used to Resend the same IDoc with out getting the new one using WE19. What Rainer said is correct.
See may be you can send the Data , Not the same IDoc, It creates a New IDoc. It is not possible to Resend the same IDoc using WE19.

Similar Messages

Error message mes when trying to send PO via IDOCS to another system?

Hi Abap expert,
I am getting wired message what I ma trying to send PO via IDocs to other SAP system.
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

Hi,
Go and check it in NACE tcode, whether , Condition type, output types are maintained or not? if not maintained, Maintain it for 6 -PO for EDI.
Hope this is the error you are getting.
Thanks
Manju

Do we need a sender channel for IDOC to file scenario.

Hi,
Do we need a sender channel in IDOC to FILE scenario.
Because IDOC is being sent by SAP R/3 System and when creating objects in ID using wizard, it doesn't ask for sender channel.
What is the reason for this?
Regards,
Younus

Younus,
to add more...
From WAS(Web Application Server) 6.20 and above BASIS is not the runtime for SAP.WAS is the runtime for SAP.
And it has got ABAP and JAVA engine in it.
It handles connections made over various protocols such as SMTP for mail, HTTP(S), and SOAP/XML.

The SAP Web AS 6.10 did not have a Java engine.
and IDOC and HTTP are present on the ABAP engine and the rest reside on JAVA engine.
and that is the reason why IDOC and HTTP doesnt require Sender Adapter and Sender Aggrement aswell.
Hope i cleared ur point...
Cheers,
Raghavesh
Message was edited by:
Raghavesh Reddy

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML

Hello Rescue Team,
I am facing the following error :\
16.06.2014 23:22:42.164
Error
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.166
Error
MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
and the payload transferred is as attached in the attachment below.
I have refered various blogs, however I am still not able to understand how to get the exact location of the error location..According to me, the value that is giving trouble is OTH in <BSARK> however I have checked the permitted values for BSARK on ECC and OTH is maintained.
Can you please help how I can resolve this error.
Thanks
Saurabh

Hi Guys,
This is solved..I corrected the date format of the ZZTIME segment from 1157 to 115700.
Thanks
Saurabh

Pls send material for idocs in ECC 6.0

Pls send material for idocs in ECC6.0

Hi sitaram s ,
IDoc
- IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Archiving Processed IDocs
IDoc archiving is a two-step process:
1. Archive the IDoc.
2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
Transaction SARA works in the following way:
On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
SAP Integration Using ALE(Application Linking and Enabling)
- IDOCS -
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
ALE Inbound Pre-Processing
http://www.erpgenie.com/sapedi/idoc_abap.htm
cheers!
gyanaraj
reward points if u find this helpful

ME23N Error when trying to send PO via IDOCS to another system?

Hello Experts,
I am getting wired message what I ma trying to send PO via IDocs to other SAP system (XI)
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

I just got the same problem. Everything worked fine when i was using message type ORDERS01, but when i changed it to ORDERS05 this problem started happening.
This might solve your problem. If you have it solved out can you tell us the solution you found??
regards,
Diogo

IORD for sending Order via Idocs

Hi SAP Experts,
Does anybody know how to use T-Code IORD for sending Idocs, every time I run this T-Code not a single Idoc gets created.
Also I would like to know what does 'Status Profile/User status to be set' mean on the selection-screen, I think its happening due to this only.
I've done lots of Idoc Integration using HR Idocs but this is a first Idoc Integration for me in PM module so not sure what should be the best way of sending Order via Idocs to 3rd Party system.
Any help would be appreciated.
Thanks,
Sunny Thakur

Hi Pete,
We are trying to send SAP PM Work Order for production equipment changes , I came to know that IORD generates Idocs for Order but somehow whenever we try to run this T-Code all the orders are getting rejected. Also I've noticed Idoc Type IORDER cannot be used for sending Delta changes , is it true? I can't find any entry for this message type in BD60 so makes me think SAP did not design this Idoc type for delta changes, even though I know we could customize it
Do you know what should be the best way of sending SAP PM Work Order to external system , should we create one custom Idoc type?
Let me know in case you could help me out.
Thanks,
Sunny Thakur

Can we send attachements with Idoc?

Hi ,
Can we send attachements with Idoc?

Hi,
1. in standard you cannot
2. you could however send it in a text field
and then combine in adapter or java proxy
on the other hand abap proxies work with attachments
in standard - check out my blog:
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

T-code ME23N message when trying to send PO via IDOCS to another system?

Hello MM Experts,
I am not sure if my question is more for ABAP guys , but since it is MM related I decided to share it with MM experts as well.
I am getting wired message what I am trying to send PO via IDocs to other SAP system (XI)
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

Hi Boby ,
TRY going thru this link and check for the details given in it wether they are in place or not specially in the message controls, viz: application EF ,message type NEU and process code ME10
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
regards
kp

Sending a mail(IDOC REPROCESSING)

hi all,
I have a requirement that when an IDOC fails while being processed in xi then a mail should be sent to the sender of the idoc........i heared that there is a custom RFC function which does the same....can anyone help me out with this....
Thanks and Regards
keerthi

Hi keerthi !!
Check the following link
https://websmp203.sap-ag.de/~sapdownload/011000358700003237612005E/HowToCreateAdapterModules.pdf
/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken] - File to Mail
Check the following link
/people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
t is possible to configure the mail adpater to send attachemnts without any ABAP coding. Just check out these
blogs by michal that deal with the mail adapter,
/people/michal.krawczyk2/blog/2005/11/23/xi-html-e-mails-from-the-receiver-mail-adapter
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
You can also check these links on SAP help for configuring the mail adapter,
http://help.sap.com/saphelp_nw04/helpdata/en/ad/bf93409c663228e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/6b/4493404f673028e10000000a1550b0/content.htm
Pls reward if useful

Is there any way to send HR-specific IDoc to CRM?

Hi,
Does anyone know if there's a way to send SAPHR-specific IDoc, which does not exist in CRM, from HR to CRM?
If this IDoc was created in basis, there won't be any problem, since the IDoc type and message type would exist in both HR and CRM. But if the IDoc and message type are HR specific, which means they don't exist in CRM, is there a way to send the IDoc to CRM for processing?
Thanks,

Hi, Tiest
Thanks for your reply. Actually, I'm look for a solution to download HR employee balance to CRM. The IDoc type in HR is HRCC1DNBALAN01.
The problem is that, not like IDoc HRMD_ABA, which exist in basis, this IDoc type and related message type don't exist in CRM.
How can I use this IDoc type in CRM?
Thanks,
Wei

Send out failed IDOCS as XML files or as email from production client

Hello Gurus,
We run SAP R/3 in a Retail environment and use MS BizTalk as the interface tool to our POS system.
We have a requirement to be able to send out failed IDOCs to developers / interface team for verification. This is not a regular task, but needs to be done once in a while.
Please advice how this can be achieved in a production region, where the IDOCS can be converted into XML format or emailed out for verification. How are such situations handled at other sites?
All help provided will be useful and rewarded well.
Many Thanks,
Regards,
Nisch

Hi Nisch,
I hate to write custom program,as i did lot of R&D On this ,there is no sap standard transaction,you can monitor by using WE02 or WE05 ,see each you can able to see one idoc completely by using WE02 or WE05 ,you can not send the data .
Thanks
Seshu

Unable to send PO through IDOC

Hello!!
Good Evening.
I have a problem, while sending PO through idoc orders03, some idocs are going fine and some are stucking and i cross checked the succesful and failed idocs and came to know that, one segment is missing.
How this has happened.
Actually, E1EDKA1 is the segment.
How to track this issue and rectify the mistake.
Reply ASAP...!!

It is the case that from sender system, you are sending data in a segment(we31) which you have not maintained in the idoc type(we30) in the receiver system.there may be an extension which you have to add in the message type in the patner profile.
doing this will completely resolve the issue.
you may reprocess your i/b idoc from BD87 after maintainng the extension(we30)
let me know if you have any doubt

How to send outbound ASN IDoc with all the delivery info on legacy system??

Hi EDI-Gurus,
I have a small question.
We accept inbound sales orders into SAP and send outbound Order Acknowledgments out of SAP. We don't really maintain shipping and billing info on SAP. They are being maintained on legacy. But we have to send Outbound ASN, Invoice out of SAP for them.
Can you please let me know how exactly we can do that in detail.
thanks,
Matt

Can we do this way, correct me if i am wrong.
We'll send ASN when we issue Goods right??. If we get all the Goods issues details relevant to an order from legacy using LSMW using IDoc method, can we send it out of SAP.
I am just wondering if it is possible or not.
Or get the Shipping and Billing details from legacy (using which method i don't know), and using a custom function module can we send the outbound 856 and 810 out of SAP.
Can you throw some light on this?
Thanks,
Matt

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

Re send a succesfukl idoc.

Similar Messages

Maybe you are looking for