REG: Error in IDoc adapter outbound processing

Hi All,
      I had a couple of doubts regarding these IDoc's.
1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
"IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
Can any one help me to Solve my Problem
2) How to find out whether the IDoc is of synchronous or Asynchronous mode
    and how to handle the synchronous type of IDoc's
Thanks in advance.
with Regards,
Kalyan Dannapaneni.

Hi Kalyan,
IDOCs are only Aynchronous (EO or EOIO).
If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
Best regards,
Silvia

Similar Messages

Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller: PIAFUSER
FM: IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server; and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

XI Business content for MDM - Syntax error in IDOC adapter

Hi mates,
I'm trying out the Master Data Harmonization scenario for Vendor data with R/3 as the client system. I'm using SAP delivered XI Business content for MDM. The mapping program is generating ADRMAS and CREMAS IDocs but the IDOC adapter reports that there is a syntax error in ADRMAS IDOC. Find below the details.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Generated ADRMAS IDOC is
 <?xml version="1.0" encoding="utf 8" ?>
<ADRMAS02>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1" />
<E1ADRMAS>
<OBJ_TYPE>LFA1</OBJ_TYPE>
<OBJ_ID>0000500140</OBJ_ID>
<CONTEXT>0001</CONTEXT>
<E1BPAD1VL SEGMENT="1">
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<NAME>Swift Transportation</NAME>
<COUNTRY>US</COUNTRY>
<COUNTRYISO>US</COUNTRYISO>
<LANGU>E</LANGU>
<LANGU_ISO>EN</LANGU_ISO>
<SORT1>SWIFT TRANSPORTATION</SORT1>
<TIME_ZONE>CST</TIME_ZONE>
<E1BPAD1VL1 SEGMENT="1">
<LANGU_CR>E</LANGU_CR>
<LANGUCRISO>EN</LANGUCRISO>
<ADDR_GROUP>BP</ADDR_GROUP>
</E1BPAD1VL1>
</E1BPAD1VL>
</E1ADRMAS>
</IDOC>
</ADRMAS02>
Strangely, the control record is blank. I looked at the XSLT program, it is coded that way. I do not understand the reason. Is the error pointing to the control record?
Look at the code sample from XSLT mapping program
<xsl:for-each select="IDOC/*/E1ADRMAS">
 <IDOC BEGIN="1">
 
 <EDI_DC40 SEGMENT="1"/>
 <xsl:apply-templates select="."/>
 </IDOC>
</xsl:for-each>
How can an IDOC w/o control record be posted?
Did anyone come across this error? Whats wrong/missing?
I appreciate ur inputs.
thx in adv
praveen

Moorthy,
I tried reloading the IDOC metadata from IDX2. Still I get the same error.
Regd, IDOC w/o control record, can u elaborate on "dynamic value while posting IDOCs". From where, XI message SOAP header with Business System replaced by corresponding logical system names?
Thanks
Praveen

Error using IDOC adapter

Hi All,
I'am trying to run the following scenario:
FILE --> XI --> IDOC (r/3).
Data is read and mapped towards an internal format. Then a mapping from the internal format to MATMAS_BAPI01 is done.
I disabled EDI_DC40 and did the needed mappings.
When I execute the scenario I get the following error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I expected that the XI system would automaticly fill in the needed info in EDI_DC40.
Does anyone has an idea what is going wrong?
Kind regards
Message was edited by: Geert Wouters

hi,
most probably your idoc message
has a wrong format
when you import your new idoc to integration repository
does it have EDI_DC40 at the beggining?
BTW
try without disabling the edi_dc40
you cna also have a look at my weblog:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
Regards,
michal
Message was edited by: Michal Krawczyk

MIRO - Idoc for outbound process ( LIV)

Friends,
SAP has to send the following data to Oracle Financials. XI is the interface. So I need to identify the idocs used in LIV ( Invoice Verification) module.
Can any one help me what idoc / bapi should i use for the below outbound process.
Vendor invoice and credit memo
Also, i heard transactional data cannot be triggered by programs RBDMIDOC and it will be send automatically.
How can I send the idoc automatically in the outbound ALE layer. Is theres any message type to set up or any program to be execute. In other words , how the change pointer is triggered for the transactional LIV data.
Regards
Raj

Raj,
It really depends on where you are sending yor IDOC or whom you want to be informed.. If you think it is just for records.. After reding your initial description.. if it is an ERS based invoice, you could use ERS, else
Create a new condition table and include all teh fields that you want.. make sure you do not mix the item fields with the header,
Include that table in a custom access sequence that you create and assign a new message type-- custom again..
That is the only way you'd actually be able to capture all teh fields and information you want.

ATTRIBUTE _ WRONG _ INTF error in idoc adapter

hai
iam creating file to idoc scenario in that
iam copying the CREMAS in to XSD file
and chenge the occurence of name1
filed.
and this xsd file iam using at reciving side interface
my reciver adapter is idoc adapter
sender adapter is file adapter
when i configure this
iam getting this error
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>CRMAS_IF</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface CRMAS_IF</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
so pls any body can help me
what is this error

hai
THANKS FOR UR HELP
NOW IAM GETTING THIS KID OF ERROR
WHAT IS THIS IAM NOT UNDER SANDING
During the application mapping com/sap/xi/tf/_cr_mp_03_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformation
iam trying to vreate multi ple segments at reciver side for one field .at that time iam getting this error
i changed the occurs of that filed to unbouned .
is it need to change the idoc structure at r3 system also ?
can any body help me pls
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_cr_mp_03_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/sap/xi/tf/_cr_mp_03_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Idoc status error 66 - IDoc must be processed later; 000006 , IDoc no. 0000

Hi,
The following error appears when a particular Idoc is trying to get posted
Status 66 - IDoc is waiting for predecessor IDoc (serialization)
Message - "IDoc must be processed later; 000006 , IDoc no. 000002 required."
What is this error all about? How do I find out which is the predecessor Idoc which has to be posted first. I can not find any other idoc numbers mentioned here.
Thanks in advance

Rhea,
What you have mentioned is clear for me too. But the question is how do I trace the predecessor idoc? 0002 or 0006 are not Idoc numbers. They are Idoc types.
Any way in which I can trace out the predecessor idoc?
Regards

Idoc failure(outbound process)

I had worked with the transactional data (INVOICE) and message control technique which has triggered with an idoc but it fails to deliver to the reciever system. so, can trigger the idoc for sending the invoice next to this one with out solving the previous issue.
Thanks,
Mammula Raju.

Firstly, I didn't understand your question completely. If I understand what it is, then you're having an issue sending IDOC outbound and the receiver receiving it?
If this is true, you might want to look at the port setting. Check the folder which is configured to the port and if your EDI/ALE subsystem is looking at the same folder to pick up the data.
Additionally, what is the error you're receiving? Is the error being sent back by the subsystem that receiver is not getting it? If that is true then there is something wrong in your sub system layer. If this is in test, then note that you might receive this error because you do not want to send the data to your trading partner.
However if this is in production, you have looked in the areas I've mentioned above and still have an issue, then please elaborate a bit more on the error.

Error in Idoc adapter

Hi I am trying todo the from file to Idoc. I am getting the payload exactly but i am getting the error pls check the below code
Thanks
Gowri
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi All!
I've encountered the same error as stated above,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The RFC Destination is SAPA5A.
We're now on Acceptance box.
But, as of this moment, A5A was down (due to maintenance activity).
Is this the reason for this error?
Because A5A was down, there is no automatic refresh of metadata in Acceptance box ?
Kindly advise.
Thank you!
Fred

IDoc Adapter throws error

We are trying to send data to SAPR/3 47 IDES using IDoc Adapter.
the data is sent to XI from SQL database thro JDBC adapter and then to R/3 thro IDoc adapter.
All this is in Asynchronous mode and at no point we chose synchronous (IDoc adapter does not suppost Asynchronous process right).
But we are getting the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>B7685EB2-42F1-554B-80CC-6ADFC86C7975</SAP:MessageId>
<SAP:RefToMessageId>35A42550-81F9-11D9-AFC7-00C09F450580</SAP:RefToMessageId>
<SAP:TimeSent>2005-02-18T22:05:33Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>S70_812</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS04</SAP:Interface>
</SAP:Sender>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processing</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
We are not sure where from this synchronous is being picked?
Please advise.
Thanks,
Bhaskar and Anil

In the Processing Parameters section of the JDBC adapter, make sure you have Exactly Once (Asynchronous) selected.

IDoc Adapter - ATTRIBUTE_BE_NOT_SUPP Async processing

Hello,
I'm trying to establish IDoc communication. Here is the scenario that I need:
<XML Data> --- <SOAP> --> PI Server ( Map XML to IDoc XML) --- <IDoc> --> SAP Retail System
I have the following components set up:
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
2. Sender Agreement
3. Map from InXML to OutIDoc. OutIDoc - Message Interface - Inbound Asynchronous
4. Receiver Determination
5. Interface Determination
6. Receiver Agreement
7. Receiver IDoc Communication Channel
8. Business Service for all this
No Integration Scenario.
If I replace item 7 to the FTP for example, everything works just perfect - I send XML it gets Mapped to IDoc and in my FTP I have the IDoc file.
Now, I've asked SAP support specialist to establish communication from PI Server to Retail using IDoc. He send me parameters, which I used for IDoc Communication Channel:
RFC Destination: NX7CLNT800
Port: A000000022
SAP Release: 3 - this is I put myself
But when I run the whole system again, I'm getting the error:
IDOC_ADAPTER ATTRIBUTE_BE_NOT_SUPP - "Only asynchronous processing supported for IDoc adapter outbound processg"
This is very confusing because both my message interfaces are Asynchronous.
Can anyone tell me what I'm doing wrong and why I'm getting this error.
Thanks.

8. Business Service for all this
Should it not be Business System for IDOC.....for SOAP it will be Business Service
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
Check what is the QoS that is specified in the SOAP Channel.....if it is Best Effort then it will be a cause of the error......change it to Exactly Once (EO).
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 4, 2009 10:29 AM

Inbound & outbound process

Hi All,
I am new to ALE. I want to know what is the actual process behid inboud and outbound services in ALE.

Hi,
1.Here out bound means sender.Inbound mens --receiver.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Regards,
Shiva.

File Adapter BPEL Process getting switched off

The file adapter BPEL process reads a csv file which has a series of records in itfrom /xfer/chroot/data/aramex/accountUpdate/files. In between reading the files, the BPEL process gets switched off. The below snippet is the error we found in the domain.log. Anybody can you please suggest what to do?
<2010-11-25 16:22:28,025> <WARN> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound>
java.io.FileNotFoundException: /xfer/chroot/data/aramex/accountUpdate/files/VFQ-251120101_1000.csv (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at oracle.tip.adapter.file.FileUtil.copyFile(FileUtil.java:947)
at oracle.tip.adapter.file.inbound.ProcessWork.defaultArchive(ProcessWork.java:2341)
at oracle.tip.adapter.file.inbound.ProcessWork.doneProcessing(ProcessWork.java:614)
at oracle.tip.adapter.file.inbound.ProcessWork.processMessages(ProcessWork.java:445)
at oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:227)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
at java.lang.Thread.run(Thread.java:619)
<2010-11-25 16:22:28,025> <INFO> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound> Processer thread calling onFatalError with exception /xfer/chroot/data/aramex/accountUpdate/files/VFQ-251120101_1000.csv (No such file or directory)
<2010-11-25 16:22:28,025> <FATAL> <PreActivation.collaxa.cube.activation> <AdapterFramework::Inbound> [Read_ptt::Read(root)]Resource Adapter requested Process shutdown!
<2010-11-25 16:22:28,025> <INFO> <PreActivation.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - performing endpointDeactivation for portType=Read_ptt, operation=Read
<2010-11-25 16:22:28,025> <INFO> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound> Endpoint De-activation called in adapter for endpoint : /xfer/chroot/data/aramex/accountUpdate/files/
<2010-11-25 16:22:28,095> <WARN> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound> ProcessWork::Delete failed, the operation will be retried for max of [2] times
<2010-11-25 16:22:28,095> <WARN> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound>
ORABPEL-11042
File deletion failed.
File : /xfer/chroot/data/aramex/accountUpdate/files/VFQ-251120101_1000.csv as it does not exist. could not be deleted.
Delete the file and restart server. Contact oracle support if error is not fixable.
at oracle.tip.adapter.file.FileUtil.deleteFile(FileUtil.java:279)
at oracle.tip.adapter.file.FileUtil.deleteFile(FileUtil.java:177)
at oracle.tip.adapter.file.FileAgent.deleteFile(FileAgent.java:223)
at oracle.tip.adapter.file.inbound.FileSource.deleteFile(FileSource.java:245)
at oracle.tip.adapter.file.inbound.ProcessWork.doneProcessing(ProcessWork.java:655)
at oracle.tip.adapter.file.inbound.ProcessWork.processMessages(ProcessWork.java:445)
at oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:227)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
at java.lang.Thread.run(Thread.java:619)
<2010-11-25 16:22:28,315> <ERROR> <PreActivation.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Process state off.
The process class "BulkAccountUpdateFileConsumer" (revision "1.0" ) has not been turned on. No operations on the process or any instances belonging to the process may be performed if the process is off.
Please consult your administrator if this process has been turned off inadvertently.

This patch is not for 10.1.3.1.
I have provided a response to on the following post
BPEL Process Going into Dead State Automatically.
cheers
James

Connecting of an external system by IDOC adapter

Hello everybody,
we want to connect an external (storage) system to XI by IDOC-Adapter.
In a scenario without XI the R/3 backend triggers the external system by RFC-Call (TCPIP-conncetion) and an program on the external system is called. This program executes an RFC-call on the R/3 to get the IDOC-informations.
IN the new scenario (with XI) the R/3 Backend sends the IDOC information to XI. The XI routes this to external system. An TCPIP-Connection is needed which calls the program from the external system.
But how should this work? The program can not (or should not) call the R/3 Backend directly but the XI.
What has to be done now? Has the program of the external system changed so that it can understand IDOC-structure directly?
Or do I have to implement a business process scenario to guarantee that the external system reads the IDOC data in XI (similar to "old" scenario?
Thanks a lot!

HI everybody,
thank you very much for your help. Now it es possible to send an IDOC from R/3 Backend and IDOC-Adapter via XI to an external system using the IDOC-Adapter.
But now the external system wants to send IDOCs back. So the communication is realised by using the IDOC-Adapter again. In this case we do not get the messages in XI. The conncection is ok (we see this in the Gateway), but the system gets an error in IDOC adapter (sys-log):
Transaktions-Abbruch IDOC_ADAPTER 151 ( LFS 910 )LFS = external system (AS400).
In the RFC-Trace we find following information:
 **** Tra
Transaktions-Abbruch IDOC_ADAPTER 151 ( LFS 910 )ce file opened at 20060223 111414 W. Europe Stand, SAP-REL 640,0,109 RFC
======> Der Funktionsbaustein "EDI_FILL_SYIDOC01_FOR_RFC" ist nicht vorhanden
ABAP Programm: SAPLIDX1 (Transaction: )
Called function module: EDI_FILL_SYIDOC01_FOR_RFC
User: RFC_USER (Client: 910)
Destination: C01 (handle: 3, , {C322581B-EB47-43E7-87D7-4607C2873828})
SERVER> RFC Server Session (handle: 1, 95896538, {43FD899F-8993-0202-E100-00000A
SERVER> Caller host: LHMAS40A.INTRANET.SYS
SERVER> Caller transaction code: (Caller Program: SAPCPIC)
SERVER> Called function module: ARFC_DEST_SHIP
Can anybody help us?
Thanks a lot!
Florian

ALE - Idoc not getting processed automatically, instead going fine in Debug

Hello All,
I have a problem with Inbound idoc processing.
IDoc settings were made 'immediate processing' in WE20, and the process code is set correctly and the attached of Z-Fun. module to process the idocs to process code.
The error in inbound side is as 'Function module not allowed: APPL_IDOC_INPUTI' 51 status. Am sure i have to do some thing with ALE settings.
Can some body help me with correction step or sequence of steps for this ALE process.
Thanks & Regards, Jilan

Hi Jilan,
Plz follow the steps:
ALE Configuration:
     WE30 - IDOC type creation
     WE31 - Create segment
     WE81 - Message type creation
     WE82 - Link IDOC type to Message type
     SE37   - Create Inbound Function Module
     BD51 - Maintain entry for Function Module
     WE57 - Maintain
     BD57 - Link Function Module, IDOC type and Message type
     WE42 Create Inbound Process Code
     BD67 - Link Process code to Function Module
     WE20 - Create Partner Profile
     BD64 - Display Distribution Model
     WE02 - IDoc List, Display all Inbound/Outbound IDocs
     WE14 - Outbound Processing of IDocs
     BD20 - Inbound Processing of IDocs
1st Step:   Create a Segment ( WE31)
         Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it. But, to actually use this Segment, you have to Release the Segment, otherwise u cant use the Segment, by menu, EDIT--> Set Release.
         Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
2nd Step:   Create IDOC Type ( WE30 )
        After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
       Basic IDoc Type: Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
       Extension IDOC Type: When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
3rd Step:   Create Message Type (WE81)
     Message Type is like the Postman for sending the Letter.
4th Step:   Attach Message Type to the IDOC Type (WE82)
5th Step:   Create a Function Module (SE37)
       Write the Processing logic in a Function Module.
6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
8th Step:   Create a Custom Process Code (WE42)
9th Step:   Attach the Function Module to the Process Code (BD67)
10th Step: Execute Inbound IDOC s (WE19)
Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
reward is useful,
regards,
Tanmay

REG: Error in IDoc adapter outbound processing

Similar Messages

Maybe you are looking for