Idoc outbound door setting

I have to transport a new interface that is running in Dev and QA to PROD.
Basis guys do this in CMS, but I have to tell them what do they have to import.
With the interfases, I dont get any problem, but the idoc that the interface is using, isnt in Prod. and someone tell me that I have to configure the outbound door (maybe I have to do this in tc bd64 in R3, but I got no idea in this).
Anyone knows what am I talking about?

Do you mean Outbound Partner Profile?
Also without the idoc being available in production in your R3,the Idoc cannot be sent to XI and the idoc metadata cannot be imported in IDX2 in XI.
Both R3 and XI transports should be done parallely, but until R3 transports are not done, the Idoc cannot be sent to Xi and vice versa.
Regards
Bhavesh

Similar Messages

IDoc outbound errors - mail send step in WF to send info-mail to enduser

Hello specialists
I searched quite a lot in the forums now. I found lot of info but nothing regarding my issue.
I need to send an info-mail to the end user creating purchase orders. But only if the idoc (outbound ORDERS) could not be sent (failing for some reason, i.e. if rfc connection fails). This is what I've done to achieve this:
- in WE40 I linked my WF to process code EDIO
- the WF-BATCH user has an email address assigned to it (in SU01)
- the mail sending step in my WF is configured like this:
recipient type = G (organizational object)
Expression = &_WORKITEM.CREATEDBYUSER.ID& (this contains the enduser id)
subject = Test for &WORKITEM.CREATEDBYUSER.ID&
When testing the mail can not be delivered (error SO23).
When setting recipient type to U (E-Mail address) and giving a valid e-mail address, then it works fine (SCOT, etc. is configured and mailing to external systems works). But setting the e-mail address hard coded style in the mail send step is not an option here!
It seems that the send mail step (SELFITEM.SENDTASKDESCRIPTION) always requires a valid e-mail address. Is it not able to handle SAP user id's ?
Thanks in advance for some guideance on this one.
Renaud
Edited by: Renaud Desarzens on Feb 11, 2010 3:00 PM

Hello and thanks for your help.
I was able to solve it like this:
- don't use mail send step
- instead, add new activity with a new task (SELFITEM.SENDTASKDESCRIPTION)
- in the bindings (workflow -> step) set:
B --> &TYPEID&
&_WORKITEM.CREATEDBYUSER.ID& --> &ADDRESSSTRINGS&
Seems that the mail send step doesn't allow TYPEID to be "B" because each time I tried to tweak the generated bindings that way it messed up the recipient type and expression I set before.
Regards
Renaud

Convert IDoc outbound to IDoc Abstarct

Hello Friends,
Can any please tell me how to convert IDoc outbound to IDoc Abstarct type so that it can be used in BPM.
Thanks
Sam

Hi Woj,
Below is the xml message displayed.It says No Interface found .But I have all the objects at the right place.
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MATMAS.MATMAS04*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action INIT into MAST</Trace>
</Trace>
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MATMAS.MATMAS04*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface MIAbA_MATMAS_Req*</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
Also I have mapped IDoc_original_outbound to IDoc_asy_Abs _ED in my message mapping 1:1.I have selected original IDoc (not ED) in the receiver determination.
I don't think we need to explicitly maintain IDoc outbound asy in the MI..? should I..?
Kindly suggest me if you find any solution for this happening.
Please send me if you have any scenario of similar type else please mention the steps to be carried out for this scenario so that I can cross check with your steps.
Thanks alot for your valuable time.
Regards
Sam
Message was edited by: Sam
Guest

Outbound character sets

Hi
Our outbound external messages go out via a GW704 GWIA. The GWIA thenpasses them onto our email security gateway.
The issue that I'm having is that I've enabled a 'disclaimer' on our email security gateway that is stamped on all outbound messages. The HTML version of the disclaimer that works perfectly but the Plain Text version is causing me grief.
When I include French characters such as and in the disclaimer it doesn't get appended to the outbound messages.
I spoke to the security gateway support team and they tell me that it won't work if our outbound character set is set to US-ASCII. It needs to be UTF8 (or similar) for these characters to work properly.
I checked the character set that the GWIA is sending out with and it is indeed US-ASCII.
Is there a way I can set the GWIA to use the UTF8 (or similar) character set so that I can include these dodgy foreign characters in our disclaimer? I've looked through the config file and settings and
nothing is jumping out at me.
If there is a way and I set it am I likely to run into any other issues with messages that were previously going out ok?
Thanks

On 6/17/2011 10:06 AM, MPlumb wrote:
>
> Hi
>
> Our outbound external messages go out via a GW704 GWIA. The GWIA
> thenpasses them onto our email security gateway.
>
> The issue that I'm having is that I've enabled a 'disclaimer' on our
> email security gateway that is stamped on all outbound messages. The
> HTML version of the disclaimer that works perfectly but the Plain Text
> version is causing me grief.
>
> When I include French characters such as and in the disclaimer it
> doesn't get appended to the outbound messages.
>
> I spoke to the security gateway support team and they tell me that it
> won't work if our outbound character set is set to US-ASCII. It needs to
> be UTF8 (or similar) for these characters to work properly.
>
> I checked the character set that the GWIA is sending out with and it is
> indeed US-ASCII.
>
> Is there a way I can set the GWIA to use the UTF8 (or similar)
> character set so that I can include these dodgy foreign characters in
> our disclaimer? I've looked through the config file and settings and
> nothing is jumping out at me.
>
> If there is a way and I set it am I likely to run into any other issues
> with messages that were previously going out ok?
>
> Thanks
>
>
Outgoing mail encoding is controlled at the Client. The gwia setting is
just a fallback
However they are IMO
a) lying - US-ASCII is a 100% subset of UTF-8. Hence any US-ASCII only
encoder will ALWAYS be accepted as UTF-8 . The reverse is NOT true -
UTF-8 will get corrupted going through a US-ASCII gate. But that's not
what they said.
b) Pretty much NOT an excuse, because email security gateways (unless
they are ineffective), have to be able to parse MIME in character sets
of, oh at least 15 varieties. So they are making a tacit admission their
product is substandard, and unable to protect against malware. By
definition if you can parse text for malware and content (and to do so
you must be able to read/write that character set), you should not have
this problem.
So either your description is incomplete, or you need to seriously
consider leaving this provider ASAP.
Disclaimer : I work for and have written email security software for
GWAVA, which would be a competitor.

RFC For IDoc outbound processing

I am creating an RFC for BDC for call transaction we19
input as : idoc number
and output:-.. iDoc Outbound processing done
so:-
I go to we19> give iDoc Number (say, some number for ALEREQ01), and execute> click on Outbound processing-->click enter -->enter
in this way, I can process any iDoc from SAP system to outbound.
I want to create RFC for the same.
Problem:-
when i am executing that RFC, and when I check the iDoc status in we05, that iDoc shows status as Idoc ready to dispatch( its in yellow color).. Its not showing green color and not saying that IDoc passed OK
when I try manually ,I see the status green..OK..successfully
Any idea why I am getting this problem??
Is there any problem in my BDC recording?..but when I run that recording for Process, i dont see any problem,it executes successfully.. but when I copy the Code from BDC and make a RFC using that code, its giving problem as mentioned.

Hi Ankit,
Theorotically it should work.... but I'll suggest not to use BDC here. What you can do is,
1. You have Idoc number..Right?
2. Read control record from EDIDC and data record from EDID4.
3. Then call Master_idoc_distribute.
4. This will again distribute the same IDoc with same control and data record as a new one. It will be same as WE19 , but without WE19.
Please check and confirm.
Regards,
Audy.

IDOC Outbound processing using SAP BC

Hello Experts,
I am trying to develop a simple IDOC outbound processing scenario using SAP BC. In this an IDOC from SAP ECC server will be sent to an external webserver via SAP BC, for this i have done all the setup i.e Establishing connection between SAP BC & SAP ECC, ALE settings, creating a new Routing rule, but when i try to run this scenario, i am getting the following error 'IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE' , is there any way to import the IDOC metadata, just like how we do in SAP XI using IDX2. Please Help...
Thanks & Regards,
Amit Naik

Hi Michal,
Following is the error which i am getting :-
2009-03-12 21:56:59 IST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.
     at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)
     at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)
     at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)
     at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
     at com.sap.conn.idoc.jco.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:88)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:141)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2621)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2298)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2130)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2012)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1903)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:258)
     at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:320)
     at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:219)
     at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
     at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
Thanks & Regards,
Amit

AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

26 Error during syntax check of IDoc (outbound)

Hi Experts
I am using TPSDLS - Idoc(outbound).
When we view in WE02 : for few of the deliveries it is working fine , but for some it is giving the following error
26 Error during syntax check of IDoc (outbound)
Please any one help me out for the same
Thanks & Regards
Shaveta

Please check the segments for the idocs in error status in WE02. The segments in the idoc should be in the same sequence as defined while creating idoc in WE30.
For eg. taking the case of invoic02 idoc.
Segment E1EDP01 cannot come prior to segment E1EDK01.
As in WE30 it is defined to come after E1EDK01\
Please reward the points if this information is useful.

PO outbound message control - Condition record / PO IDOC outbound user exit

Guys,
I have a system with PO outbound message control sending PO idocs to a unique plant that is set up as a customer in the partner profile. I am using a custom message type and RSEOUT00 to send my idocs with custom message type to this plant. This interface works fine. Now my requirement has changed. I need to send PO's to varying plants (depending on the plant in PO item- all items on my POs belong to same plant).
I noticed that i cannot create condition tables with PO type and Plant combination. (SAP Note 457497 .Q-34).
So I have decided to populate all my PO idocs with a generic receiving partner number '9999' and planning to change this somewhere in a user exit. I found an user exit which looks helpful.
EXIT_SAPLEINM_001 . FM
MM06E001 - Enhancement.
But somehow this exit is not triggered in during PO creation ME21N or change Me22N/Me22.
Is this because I am using a custom message type instead of standard message type ? (I still use the process codes Me10/Me11). Would this matter ? When should this user exit trigger (during creation of idocs in status 30 or when i run RSEOUT00 to sweep these idocs in status 30 to status 03) ? Any tips will be useful.
THanks.
Edited by: Shareen Hegde on Jul 21, 2008 10:13 PM

I found a OSS note -Note 457497 (Q&A # 34), which talks about the same . This was my assumption too. I was just confused because I saw plant(WERKS) in the field catalag of the access sequence.
I don't know what header field I can use to map the plant (I agree its a good idea to do this). But I have decided to do it another way. I will change the receiving partner on the control record depending on the plant in an user exit
- EXIT_SAPLEINM_001.
Thanks for your answer , Mahesh.

Issue in IDOC : Outbound

Hi All,
I am trying to send an outbound IDOC, the data is filled successfully and IDOC is generated...But the status is set to 30: and not 53(successfully)....
I checked the log: Below is the IDOC log:
Receiver exists , No filters , No conversion , No version change
Message no. B1006
IDoc successfully processed in ALE outbox
The IDoc has passed through the ALE layer successfully and can be sent. It can either be sent online or as a batch job, depending on the settings in the partner profile.
If there are no further status records then the IDoc waits for the next dispatch report run.
Success/failure of transmission is documented in subsequent status records.
ALE layer actions
The 'Receiver exists' parameter specifies whether the recipient of the IDoc has already been entered by the calling application or by the ALE layer. In the latter case the settings of the distribution model are used for the receiver determination.
The 'No filters' parameter specifies whether the processing in the ALE layer has led to segments of the IDoc created by the application being left out. The settings in the segment filter and in the distribution model for this recipient are decisive here.
The 'No conversion' parameter specifies whether field values have been converted in the ALE layer. This is the case if the IDoc contains organizational units to be converted or if the ALE conversion tool has been activated for this recipient.
The 'No version change' parameter specifies whether the IDoc has been converted into an earlier version of the IDoc type. This happens if the IDoc type in the outbound partner profile for this recipient differs from the IDoc type which was created.
Regards
Shiva

Hi ,
You trigger transmission of the IDoc using report RSEOUT00. To start the report manually, choose Tools  Business Communication  IDoc Basis  Test  Outbound Processing from IDoc (/nWE14), or schedule a regular job in background processing for this report.
Check the outbound processing mode for the IDoc in the partner profile.
Outbound processing mode 2: The system sends the IDoc immediately
Outbound processing mode 4: The system collects IDocs that have been created and sends them in packets of a predefined size.
IDocs are not intended to be sent directly.
Status 30 in the IDoc can normally only occur if outbound mode is set to 4.
Please let me know if u have any Queries.
Rgds
Sree M
Edited by: sree m on Mar 12, 2008 9:01 AM

Problem in IDOC outbound

Hi All,
I am trying to send an outbound IDOC, the data is filled successfully and IDOC is generated...But the status is set to 30: and not 53(successfully)....
I checked the log: Below is the IDOC log:
Receiver exists , No filters , No conversion , No version change
Message no. B1006
IDoc successfully processed in ALE outbox
The IDoc has passed through the ALE layer successfully and can be sent. It can either be sent online or as a batch job, depending on the settings in the partner profile.
If there are no further status records then the IDoc waits for the next dispatch report run.
Success/failure of transmission is documented in subsequent status records.
ALE layer actions
The 'Receiver exists' parameter specifies whether the recipient of the IDoc has already been entered by the calling application or by the ALE layer. In the latter case the settings of the distribution model are used for the receiver determination.
The 'No filters' parameter specifies whether the processing in the ALE layer has led to segments of the IDoc created by the application being left out. The settings in the segment filter and in the distribution model for this recipient are decisive here.
The 'No conversion' parameter specifies whether field values have been converted in the ALE layer. This is the case if the IDoc contains organizational units to be converted or if the ALE conversion tool has been activated for this recipient.
The 'No version change' parameter specifies whether the IDoc has been converted into an earlier version of the IDoc type. This happens if the IDoc type in the outbound partner profile for this recipient differs from the IDoc type which was created.
Regards
Shiva

Hi Naveen,
I had selected "Transfer Idoc Immediately"
And I had also tried this multiple times just to be sure and theres no mistake in this.
Hi Kanagaraja,
There are no messages in SM58.
Usually if there are failures, I can see them in SM58. But since I cannot see any failures, I assume its fine.
The status of the idoc remains 30 though!
Not sure why
Point to note is that new messages using the same port and RFc are going through. These are the older messages which were stuck because of an RFC error and now they are not going through.
Regards
Prasad

Where is the IDOC Sender field set?

I have been asked to help solve an IDOC problem wherein a system is sending IDOCS with different values for the control record sender field. I am a BASIS person, so I know quite a bit about the IDOC transmission process but not much about the creation of them.
The IDOCS cover the basic buy/sell scenarios:
purchasing: ORDERS, ORDRSP, DESADV, INVOIC
sales: ditto, but in the opposite direction.\
The complaint is that for a given business partner, different IDOC types have different sender IDs. So the partners get DESADVs from sender BLERK and INVOICs from sender GURGLE. The actual sender values used are not related to the client's Logical System name (for example, one of them is '0101' which indicates that a customizing person might have put junk data into a field they did not understand.)
I am trying to figure out how the sender is being set. AFAIK there are no user exits and no IDOC rules in place.
IDOCs are sent from the ABAP system through a Business Connector, so I am interpreting the "Process Integration" topic of this forum in the broader sense, but I could not find a more appropriate forum.
There are various options for me to overwrite the sender - for example I can stomp it in the business connector, but I would rather fix the problem at the source and educate the monkeys that cause the problem in the process.
I have not been able to find anything in the partner profiles and output condition records for this.
Please tell me where the SENDER value can be set for any of the outbound logistics IDOCS.
Thanks,
Russ.

Hi Russell,
as you mentioned IDOC are getting triggered from ABAP.. that means,,
is your IDOC is Inbound IDOC or Outbound IDOC..?
if it is your Inbound IDOC then check for following details.
this is the problem of Partner profile.
check from which system you are getting this IDOC triggered.. if it is PI then check for related interface in PI and in interface you will be able to get this information that from where you are getting this Sender value how you are getting..and you can then change it accordingly in PI if PI is sending you that IDOC..
this is not necessary that IDOC will triggered from PI only as ABAP program can also triggered and create IDOC.. so in that case check which program or function module is generating that IDOC .. then in that you will get information before generating what values are getting passed to these control record.. so you can change it there...also..
if the IDOC is Outbound IDOC:
then in this your ABAP program is generating that IDOC and check for program or function from where this IDOC is getting generated and change the logic to fill control records ..
Thanks,
Bhupesh

ALE / IDOC Outbound Error Handling

Hi Experts,
I got an error in Outbound Process.
An IDOC gets the status 36 - Timed out.
Can anyone tell me how can i resolve this Error?.
Thanks in advance,
Sudhakar

Hi ,
Best option is to keep a sql trace on the outbound idoc which will tell you at which perform or functional module ,the performance is taking time to fetch .
all check with basis in terms of timed out ,they would have set a paramater for time out in terms of mins or hrs.

EDI IDOC OUTBOUND send Purchase Orders from sap to vendors

Hi Experts,
I am new to EDI IDOCS, but i got object on this. So my requirement is purchase orders are send to vendors from sap (OUTBOUND) through EDI-850 format. and also i have to add some more fields to standard idoc type ORDERS05, one more condition is if vendor type is not EDI, then the POs should send through fax, email, how can we solve this condition.
So plaese send some sample code on this object.
Thanks in advance,
S Reddy

Hi ,
You can send the purchase order to the vendors using different outytpes configurations in NACE transaction .
If you define a particular output type where you need to give medium 6 and define partner functions within this you can also set condition which partner needs to recieve EDI output and which one FAX or email all this will be done by Functional expert.
For adding extra segments to your basic type ORDERS05 you need to extend the idoc you can do it via WE30 and WE31 .Link you message type to basic type and extension . Please follow below tcodes for further help . Create all the requested steps in the tcodes mentioned below.
we20:patner profile
we21:port
we30:idoc creation
we30:segment creation
we81:message type
we82:link message with idoc type.
we02:to status of idocs.
Now you need to write code for filling those extra segments you have added to you extension type. For that you need to check where your new segment is placed in Idoc structure . There will be a exit avaliable to attach your code to fill those segments .
Please go through previous SDN links to see more info.
One the settings are done in the NACE , issue output from PO transction and once your output is processed check your Idoc in WE02 to see if the segments are coming with the desired data.
Regards
Vikas

File to Idoc - Outbound Error

Hi,
I am doing File to IDOC scenario. I got error
in "Message has error status at outbound status" .. When
I opend that messeage then i got this ...
<SAP:IDOCTYP>ZIDOCIN</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ZMTIDOCIN</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPX11</SAP:SNDPOR>
<SAP:SNDPRN>Logi_01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPA11</SAP:RCVPOR>
<SAP:RCVPRN>A11CLNT200</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
Can any one tell me what to do to solve this.
thx,
Ansar.

Hi,
There is somethig worng with your Partner Function while defining the the Partner Profile, please check it. The Partner function is optionla and see if you need it
Go thru the link,
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Thanks,
Prakash
Thanks,
Prakash

Idoc outbound door setting

Similar Messages

Maybe you are looking for