How to read Idoc acknowledgement in BPM

Hi ,
I am trying to get data from database and send Idoc to sap . Upon successful idoc processing i want to send success msg to file . To achive this functionality i am using BPM , but i am not able to understand how to read acknoiwlegement in XI ? Do I need to create another datatype for acknowledgement in XI ??
Please advice
Suvarna

Hi,
Configure the Acknowledgements as shown in the Link i had given earlier.
Next, in your BPM, with the SEND step activate APPLICATION Acknowledgements. Now, your BPM will wait for the acknowledgements before going to the next step and so on.
Also, if you do not want to wait for longer than a particular period of time, you can have a deadline monitoring branch and so on.
Regards,
Bhavesh

Similar Messages

How to Send Idoc Acknowledgements back to Http sender (Http to Idoc)

Hi
I have scenario: Http To Idoc
first requirment:
i need to map xml file come from HTTP Sender to Idoc (SAP system), and need to send Idoc acknowledgements/status back to Http sender.
second requirment:
while mapping COM Xml file come from Http to COMMAT04 idoc into SAP system i need to to check whether corresponding material already exist in R/3 or not, if material is not exist, process should be cancelled and alert should be raised. ( i mean to say before sending COMMAT04 idoc into SAP, corresponding material should be exist already, if not alert should be send to http sender)
please thrown some inputs, if sombody has already done with htis....
Thanks in Advance, and help would be appreciated..
Thanks and Regards
Rajesh Babu

Just providing the specifics that Suhail has intended.
How to handle IDOC Acknowledgements in XI.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
RFC Mapping Lookups:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439
Regards,
Ravi
Edited by: Ravi Kanth Talagana on Jul 7, 2008 3:32 PM

Idoc Acknowledgements and BPM.

All,
My current requirement is to post an Idoc from my BPM, and get back the Idoc Acknowledgement. On the basis of the status field in the ALEAUDIT Idoc I need to determine the further course in my BPM.
Option 1:
1. In the Send Step of my BPM , I can request for Application Acknowledgement. I have done this and am able to receive the Acknowledgement and see the same against the Acknowledgement Msg ID in MONI. I am able to see the ALEAUDIT idoc triggered for my Send Step back to my BPM .
The question in case we are to use this Option is , how do I access this AleAudit Idoc message in my BPM. As I want to have a switch, I need this to be populated in a container element of my BPM. Is this possible? Is this approach a correct one? Any Ideas?
Option 2
I can have a Send Step in my BPM to send the Idoc from XI to R3. this will be a normal Send Step with no Acknowledgements. I can also use a Receive Step in the BPM to receive the ALEAUDIT Idoc back to the BPM.
This I guess can be done with a Receive determination where R3 is the sender and the AleAudit Idoc is the receive etc.
Issues with this approach, I need to use a Correlation against the Send and Receive Step to send the Idoc and receive the AleAudit.
1. What is the Correaltion that can be used? Is there a standard correaltion. for such cases?I looked into the Idoc and the AleAudit but could' nt find a suitable Correlation Field.
Do both these solutuons make sense? has anyone got a better approach?
Any comments are appreciated.
Regards
Bhavesh
PS: Have gone through the How to guide on Idoc Ack's and the blogs on SDN as well. But if still someone feels that there is a blog that is relevant to this issue, please do let me know if I have missed anything.

Ha, now that was interesting question. Brains were rusty, relooked into that lookup and these are the fields of the IDXRRCVPOR we use,
Used the RFC - RFC read table
XI's Idoc Number is in Field IDOCNUMBER
Original SAP IDoc Number is in Field SNDLAD.
Code excerpt attached below.
@ Henrique : Work's been crazy past few months. The blog is on my to do list, hopefully someday soon it should be out. My Apologies guys!
Channel rfcChannel = LookupService.getChannel(BusinessService, CommChannel);
//As the call is being made to RFC, RFCAccessor is obtained.
rfcAccessor = LookupService.getSystemAccessor(rfcChannel);
rfcXML =
 "<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns0:RFC_READ_TABLE xmlns:ns0=\"urn:sap-com:document:sap:rfc:functions\"><DELIMITER/><NO_DATA/><QUERY_TABLE>IDXRCVPOR</QUERY_TABLE><ROWCOUNT/><ROWSKIPS/><DATA><item><WA/></item></DATA><FIELDS><item><FIELDNAME>SNDLAD</FIELDNAME><OFFSET/><LENGTH/><TYPE/><FIELDTEXT/></item></FIELDS><OPTIONS><item><TEXT>IDOCNUMBER EQ '"
 + SourceDocNum
 + "'</TEXT></item></OPTIONS></ns0:RFC_READ_TABLE>";
inputStream = new ByteArrayInputStream(rfcXML.getBytes());
XmlPayload inPayload = LookupService.getXmlPayload(inputStream);
Payload outPayload = rfcAccessor.call(inPayload);
responseStream = outPayload.getContent();
DocumentBuilderFactory factory =DocumentBuilderFactory.newInstance();
/* Create DOM structure from input XML */
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(responseStream);
NodeList list = document.getElementsByTagName("WA");
for (int k = 0; k < list.getLength(); k++) {
 Node node = list.item(k);
 if (node != null) {
 node = node.getFirstChild();
 if (node != null) {
 if (!node.getNodeValue().equals("")) {
 OutputDocNum = node.getNodeValue();
Regards
Bhavesh

Handling idoc acknowledgements inside BPM

Hi,
I have a scenario like this
File - >XI BPM -> SAP (idoc)
after posting idoc into sap ALEAUD idoc will be triggered for sending acknowledgements back to XI
ALEAUD SAP->XI BPM -> email
             I have activated application acknowledgement in the send step of BPM and also cofigured ALEAUD idoc in the SAP, it is working fine I could able to see the acknowlegement back from SAP system in SXMB_MONI. But my requirement is to read the acknowledgement messsage back in XI and if there are any errors during idoc posting I should send that error message as an email . I tried configuring reciever determination as follows
Sender SAP
sender interface ALEAUD
reciever XIBPM
reciever interface ALEAUD
           But this also didn't work, I am not seeing any message transferred between SAP and XI for ALEAUD idoc . I referred SAP how to do docs for handling idoc acknowlegement and also looked into some forum discussion but nothing helped. Is there anyway to read the acknowledgement messsage in the BPM?
            If anyone had come across such kind of scenario please help me.
Thanks,
Jayanth

Hi Gasio,
     I checked SM58 nothing got stuck in that queue. Moreover I am explaining part of my BPM steps actually this is not the exact steps involved in BPM, lots of validation and data extractions are done prior to idoc send step.
     I am getting positive acknowledgement from SAP . I am seeing the idoc message in the acknowledgement payload. My question is how to read the content of acknowledgement message in BPM.
    I have created correlation between idoc and acknowledgement idoc in the BPM as shown below
Recieve file
Transform to idoc
Send step ( idoc )
Recieve (ALEAUD idoc)
But the process is waiting in the recieve step.
Thanks
Jayanth

How to get Idoc acknowledgment in File to Idoc scenario

Hi All,
Please give suggestions about the below mentioned scenario:
Scenario: FileXI- ECC - Data from File is converted to various IDocs and posted in SAP. (No BPM used)
Problem: Exception Handling > > We want a message back from SAP system telling us that out of 100 IDocs that were sent, n were posted successfully and rest failed along with the error description. How can this be achieved?
Regards,
XIer

Pls go thruough these links also
Please see the below links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
unable to import from SLD
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
IDOC Acknowledgements
R/3 IDOC ->XI-> ORACLE Error Handling
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
Regards
Abhishek Agrahari

How to save IDOC number in BPM to use in ALEAUD

Hi Experts,
I am doing IDOC - BPM - sync SOAP scenario, i am using async to sync bridge in BPM, how can i get original IDOC number so that i can use it in webservice response message to ALEAUD mapping??

hi
you have to use Configurable Parameters in the ccBPM. in runtimeyou assign the IDOCNUM field value to the parameter and then use it in the response mapping (WSDL-ALEAUD). you have to define the parameter in the Message Mapping under the Signature Tab.
Also you have to bind the parameter in the Operation Mapping. to do this,define a new parameter in the Operation mapping and then bind it with the parameter defined in the message mapping.
see this blog to know how:
SAP PI 7.1 Mapping Enhancements Series: Parameterized Message Mappings
rgds
RP
Edited by: Rodrigo Alejandro Pertierra on Nov 3, 2011 3:49 PM

How to read IDOC in flafile structure into SAP to create PO

HI,
We have a requirement like, we will be provided with IDOC PO flatfile structures(Exactly same as IDOC,but in Dlafile format) .
We have to read those flafiles and create POs in our SAP system.
how can we do that?what are the necessary configuration required?
please explian the different steps involved.
thank you in advance.
...Sri

Hi,
Thank you for your reply.
is there any other methods of processing the Flatfile IDOC into SAP.
like through using file port with configuration done in Partner Profile , standard FM and report ?
would this be different if we have customised IDOC?
thank you,
regards,
.....Sri

How to Read Idoc - Segment fields values and status messages

Hi,
I am having one requirement as i want to read the segments along with the field values and also i want to read all the status messages.
first i read the idoc data from EDIDS and segments data from EDID4 and the staus messges from T100. but still i am not getting all the status messages.
is there any other table which contains the information of IDOC segments and field values and also the status messages.
Regards,
Kumar

You need to use
V_MSGNO = EDIDS-STAMNO.
CALL FUNCTION 'MESSAGE_PREPARE'
EXPORTING
    MSG_ID   = EDIDS-STAMID
    MSG_NO   = V_MSGNO
    MSG_VAR1 = EDIDS-STAPA1
    MSG_VAR2 = EDIDS-STAPA2
    MSG_VAR3 = EDIDS-STAPA3
    MSG_VAR4 = EDIDS-STAPA4
IMPORTING
    MSG_TEXT = V_TEXT.
WRITE: / V_TEXT.
a®

IDOC Number in BPM (Bhavesh & Michal Help)

Hi ,
I tried the using the concepts from the blog (/people/mitesh.parekh/blog/2008/12/01/receiving-aleaud-as-acknowledgment-in-ccbpm)where i have the Message ID which entered into BPM
but not the message Id which triggered the IDoc send . I think i m missing some small detail where i need to capture the send step MSG Id
i'm aware that its not possible to get the Msg id in BPM . How is that ABAP Mapping in the above blog captures the message id ?
TRY.
l_msgid_ref = param->get(
IF_MAPPING_PARAM=>MESSAGE_ID ).
catch CX_SY_REF_IS_INITIAL into oref.
endtry.
Alternatively one more thread has some info
if someone can let me know where you can get this SourceDocNum would be great in this RFC Look up . in the thread Re: Idoc Acknowledgements and BPM.
"<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns0:RFC_READ_TABLE xmlns:ns0=\"urn:sap-com:document:sap:rfc:functions\"><DELIMITER/><NO_DATA/><QUERY_TABLE>IDXRCVPOR</QUERY_TABLE><ROWCOUNT/><ROWSKIPS/><DATA><item><WA/></item></DATA><FIELDS><item><FIELDNAME>SNDLAD</FIELDNAME><OFFSET/><LENGTH/><TYPE/><FIELDTEXT/></item></FIELDS><OPTIONS><item><TEXT>IDOCNUMBER EQ '"
+ SourceDocNum
+ "'</TEXT></item></OPTIONS></ns0:RFC_READ_TABLE>";
Since i do not have the Message ID it just creates the below payload from my mapping
This is the request being sent out using the ABAP Mapping as the Messgae ID is null .
<?xml version="1.0" ?>
- <ns0:ZALEAUDIT4XI xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<S_DOCNUM>0000000000000000</S_DOCNUM>
<S_MESTYP />
<S_SNDSYS />
<S_UPDDAT>00000000</S_UPDDAT>
</ns0:ZALEAUDIT4XI>
Looking forward for Help .

hi
you have to use Configurable Parameters in the ccBPM. in runtimeyou assign the IDOCNUM field value to the parameter and then use it in the response mapping (WSDL-ALEAUD). you have to define the parameter in the Message Mapping under the Signature Tab.
Also you have to bind the parameter in the Operation Mapping. to do this,define a new parameter in the Operation mapping and then bind it with the parameter defined in the message mapping.
see this blog to know how:
SAP PI 7.1 Mapping Enhancements Series: Parameterized Message Mappings
rgds
RP
Edited by: Rodrigo Alejandro Pertierra on Nov 3, 2011 3:49 PM

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

How to Read an IDOC

Hi Experts,
Can any one explain me about IDOC, and how to read it once it is created.
Regards
Venu

Hi,
IDOCS:
IDocs are SAPs file format to exchange data with a foreign system.
IDocs are an ASCII file format to exchange data between computers; the format is chosen arbitrarily .
IDocs are similar to segmented files; they are not a description language like ANSI X.12, EDIFACT or XML.
The IDoc contents are processed by function modules, which can be assigned in customizing.
IDocs are structured ASCII files (or a virtual equivalent). They are the file format used by SAP R/3 to exchange data with foreign systems.
IDocs are simple ASCII data streams. When they are stored to a disk file, the IDocs
are simple flat files with lines of text, where the lines are structured into data fields.
The typical structured file has records, each record starting with a leading string that identifies the record type. Their specification is stored in the data dictionary.
IDocs is the acronym for Interchange Document. This indicates a set of (electronic)
information which builds a logical entity. An IDoc is e.g. all the data of a single
customer in your customer master data file, or the IDoc is all the data of a single
invoice.
IDoc data is usually exchanged between systems and partners that are completely
independent. Therefore, the data should be transmitted in a format that can easily be
corrected by the computer operators. It is therefore mandatory to post the data in a
human readable form.
Nowadays, this means that data is coded in ASCII format, including numbers which
are sent as a string of figures 0 to 9. Such data can easily be read with any text editor on any computer, be it a PC, Macintosh, UNIX System, S/390 or any internet
browser.
The information which is exchanged by IDocs is called a message and the IDoc is
the physical representation of such a message. The name messages for the
information sent via IDocs is used in the same ways as other EDI standards. .
Everybody who has ever dealt with interface programming, will find IDocs very
much like the hierarchical data files used in traditional data exchange.
International standards like the ODETTE or VDA formats are designed in the same
way as IDocs are.
Other EDI standards like XML, ANSI X.12 or EDIFACT/UN are based on a data
description language. They differ principally from the IDocs concept, because they
use a programming language syntax (e.g. like Postscript or HTML) to embed the DATA.
The IDoc process is a straight forward communication scenario. A communication is
requested, then data is retrieved, wrapped and sent to the destination in a predefined format and envelope.
An R/3 application creates data and updates the database appropriately. An
application can be a transaction, a stand-alone ABAP Report or any tool that can
update a database within R/3.
If the application thinks that data needs to be distributed to a foreign system, it
triggers the IDoc mechanism, usually by leaving a descriptive message record in the
message table NAST.
The application then either directly calls the IDoc engine or a collector job
eventually picks up all due IDoc messages and determines what to do with them.
If the engine believes that data is ready to be sent to a partner system, then it
determines the function module which can collect and wrap the required IDoc data
into an IDoc.
In IDoc customising, you specify the name of the function module to use. This can
either be one which is predefined by R/3 standard or a user-written one.
When the IDoc is created it is stored in an R/3 table and from there it is sent to the foreign system.
If the foreign system requires a special conversion, e.g. to XML, EDIFACT or X.12
then this job needs to be done by an external converter, like the Seeburger ELKE
system. These converters are not part of R/3.
If you have to decide on a converter solution, we strongly recommend using a plain
PC based solution. Conversion usually requires a lot of fine tuning which stands
and falls with the quality of the provided tools.
DIFFERENCE B/W IDOC AND BDC:
IDOC's are intermediary documents into which the data will be transferred and then this idoc's gets transferred to sap or non-sap system.
ALE is used to create link between 2 systems. So without the linking the data cannot be uploaded or downloaded.
BAPI, LSMW and BDC are used to transfer data b/w systems.
BDC is used to transfer data b/w only sap systems.
LSMW is used to transfer data b/w sap and non-sap systems.
ale Idoc: Idoc is a part of ALE. it is applicable only if the external system and the sending system have the same format. ALE uses Internationally Standardized formats. Also it is facilitating Asynchronous data communication and safest data communication. If you got errors also you can correct it and send it again.
lsmw: It the legacy data transfer. which is used for bulk data transfers. It uses BAPI, IDoc, BDc internally....
bapi: SAP Provided way of data transfer. if the BAPi suits for our business bettere to go for bapi. it too uses internationally standardized data format Business Objects concept.
idocs
1.We will see the status of the IDOC in We02 or We05.
2.In that There are three records.
a.Data record
b.status record.
c.Control record.
3.If u click on data record you can see the data ,which is transfering it.
Details about IDOC:
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.
http://sap-img.com/abap/reads-an-existing-idoc-and-dispays-the-contents-in-a-spreadsheet-format.htm
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
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
IDOC Creation....
http://www.erpgenie.com/sap/sapedi/idoc_abap.htm
You can view the definition of any IDoc data structure directly with transaction WE30.
u cn use function module 'FIELD_POSITION_IN_SEGMENT_GET' to extract data from idocs.
You can view the idoc through we02 or we05. In that there are three types
status records gives the status of that idoc in differenttimes
data records gives the data in that idoc
control records gives the date, time and creater of that idoc.
I think its helps you.
Thanks and Regards,
D.Revathi.

Idoc Acknowledgements and Idoc Packaging

All,
I am implementing a requirement wherein we need to post 2 different types of Idoc's from our BPM. The Business requirements is such that until the Idoc 1 is not processed by the R3 system, the Idoc 2 should not be posted from XI as there is dependency in the data.
This can be addressed using Application Acknowledgements. The solution to this is to use the send step in my BPM with application acknowlegement. Until the application acknowledgement is not received for the first send step , the next send step will not be processed and so things will / should work fine.
The problem comes in the fact that the Idoc's being sent out of XI use Idoc Packaging, ie., the First Send Step uses Idoc Packaging to post multiple Idoc's to the target system. A question that arises due to Idoc packaging and Idoc ack's are,
How will the Idoc Ack's be sent back to XI?
I have read through the online help and it states that every ALE AUDIT Idoc can contain the status of maximum 500 Idoc's. Now, in my case , when using my Idoc packaging, if the number of Idoc's are greater than 500, how will the Application Acknowledgement for the Idoc's work? Will I still get a single acknowlegement in my BPM or will I get multiple acknowledgements? Will Send Step with Application acknowledgement still hold good?
Any ideas, thoughts / experiences on using idoc ack's with idoc packaging?
Regards
Bhavesh

If I undestatood correcty you have 2 send step, the first send a message containing multiple IDoc (IDoc Packaging). In this first send step you set the application Acknowledgements.
I think that this is not managed from the BPM, bacause the acknowledgements will come someone positive and someone negative, and so when the first send step will be completed ?
I think that the solution must to be changed a little bit, or removing the IDoc Packaging, or removing the wait of Acknowledgements.
Also take in mind that if you use a BPM with many possible correlation (Acknowledgements) you will have bed performances.
Regards,
Sandro

IDOC Acknowledgment

Hello All,
My scenario is SAP(IDOC) -
>XI-->SAP(RFC synchronous)--> Webservice(synchronous) using BPM and Scenario running successfully.
But my new approach is Source SAP(IDOC) expects the acknowledgement , If BPM process is success till step and after expects acknowledgement if it success.
Normally we used RFC/CWLD/ to send back the response about IDOC to source SAP system if the whole BPM process is success. But at the moment we don't want call the RFC/CWLD instead RFC we need to send the IDOC acknowledgment
So what is approach i need to follow from here? I am looking forward from you.
Thank you very much.
Kindest Regards,
Sateesh

Hi Bhavesh/ Indranil
Thanks for your great response.
@Bhavesh: I have little doubts related to your answer
                      1) SYSTAT IDOC is need to be import from sender SAP side?
                      2) is their any more configurations are required between XI and Sender SAP?
                      3) instead of using SYSTAT IDOC can I use ALEAUDIT01?
@Indranil:
          My Scenario is SAP(IDOC sending)->XI->RFC Call syn(SAP)-->Webservice(SOAP Sync)
Idoc is receviing to XI from Sender SAP system and it send to target SAP system using RFC call and getting RFC response back from target SAP and the response RFC is map Webservice call and get the response from Webservice call by status, If the status is 'success' then I am sending the IDOC number status back to sender SAP
system using RFC/CWLD call.
But using insted of RFC/CWLD call I need to use the IDOC acknowledment to send back to sender SAP system.
Please guide me how i will follow here. Thank you.
Kindest Regards,
Sateesh

Idoc acknowledgement message to web service

I am trying to set up the scenario SOAP sender>XI>IDoc Receiver.
I have exposed the outbound, synchronous message interface as a web service, and I'm planning to use sync-async bridge in BPM.
My problem is: I need a response message from SAP. Can I use an iDoc acknowledgement message for this purpose? If this is the case, how do I set up SAP to send this acknowledgement message to XI, and do I have to configure an iDoc sender channel for this purpose?
Any comment is appreciated!
Thanks,
Håvard

One option - not a ABAP expert but this is what I understood with my discussions with my ABAP team when we were coveringt he same issue -
In the Idoc Inbound Processing Code - write a ABAP Exit that after processing the Idoc will trigger the RBDSTATE report to trigger the AleAudit back to XI and XI will send it back to R3.
It is surely possible, as the Aleaudits are triggered by RBDSTATE report instead, you can manually makde the Idoc procesing code to trigger this report immdeitaly and so on.
An Abap , Ale_Idoc specialist will have the answer to this in seconds - on how to do this - but am not one
Regards
Bhavesh

Succesful IDOC acknowledgements from ECC

Dear MDM gurus,
What is the best way to handle acknowledgements from ECC (INTO MDM) for inbound IDOCS from MDM (MDM->XI->ECC).
We want it such that when an IDOC gets posted into ECC succesfully,it should send an acknowledgement signal back to MDM saying that IDOC was received properly.
Thanks.

HI Mugdha,
I have a concern on the Acknowledgement (ALEAUD) Idoc. I have implemented this scenario wherein DEBMAS IDoc is posted from MDM -PI - ECC and ECC sends back the acknowldgement using ALEAUD Idoc.
However, in PI (SXMB_MONI) there is no separate message entry created for this acknowledgment. The ALEAUD acknowldgement message details is attached to the original DEBMAS message which was triggered from MDM - PI - ECC. Due to this, PI interface created is not able to read the acknowledgement message and process it to post/dump the target file onto the MDM Port.
I tried triggering and ALEAUD Idoc manually using PI - RWB which generated a separate message for ALEAUD Idoc in sxmb_moni and then my target file was created in MDM (But this is just a manual way of testing the PI interface).
Can you advice on how this concern can be dealt with?
Thanks in advance,
Elizabeth.

How to read Idoc acknowledgement in BPM

Similar Messages

Maybe you are looking for