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

Similar Messages

IDOC Acknowledgement and Header Mapping

Dear all,
I've got the following scenario:
SAP 4.6C is sending many different IDOCs to XI 3.0 (SP14).
On XI side there are several integration processes, business systems and business services receiving the IDOCs.
I want to create IDOC acknowledgements and send them back to SAP system.
For one integration process I was able to successfully create and send back an acknowledgement by following the steps described in the very good blog:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Now I want that every integration process/business system/business service is sending back an acknowledgement with the same logical system name (meaning "this acknowledgement is coming from XI").
As it is not possible to enter the same logical system name for more than one process I created a receiver agreement with:
Sender Service = the integration process
Receiver Service = the SAP 4.6C business system
Receiver Interface = ALEAUD.ALEAUD01
Receiver Communication Channel = IDOC receiver channel called "Ack_IDOC_Receiver", existing in SAP 4.6C business system and pointing to this system
Additionally I created a header mapping in this receiver agreement where I set the Sender Service to the business system of the XI system.
Unfortunately the tests showed to me that obviously the header mapping (maybe even the whole receiver agreement) is being ignored completely as no Acknowledgement IDOC will be created. Instead I get the error message "Unable to convert sender service to an ALE logical system".
I also played around a bit with the options "Apply Control Record Values from Payload" and "Pass Sender value from Payload" but this didn't make any difference.
Why is the header mapping not replacing the sender service in the acknowledgement message?
Best regards,
Tobias

Tobias,
we have the same Problem.
we´re sending with Receiving Partner "12345" and the IDoc in the target System is filled with the standard SAP Value maybe the one configured in the SDL.
We have configured our IDOC_REceiver with a mark on "Apply Control Record Value from payload".
If you have a look at the SAP Helpfile you will find out that some header fields are not be changeable and get the value from sap.
like IDOC-Number, Receiving Partner and maybe the sender service ???
Regards,
Gordon

Difference between IDOC Bundling and IDOC Packaging

Hi,
Can anybody please explain the difference between IDOC bundling and IDOC packaging?
Thanks,
Loveena.

Hi,
IDoc Bundling is the changing the occurance of IDoc.
In a scenario If there is a necessitity for changing the Occurance of some segment of the IDOC u have to perform this steps
1.Import the IDoc to XI.
2.Export the IDoc(i.e XSD format) and save it to the local machine.
3.Make changes to the IDoc structure by modifying the XSD file in the local machine.
4.Save it as an XSD file Itself.
5.Import the XSD file in the IR under the External Defination.
6.Use this XSD in your Message Interface/Mapping which is same as IDoc structure but with some changes that u have made.
Go Thru this Blog <a href="/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change Bundling - Trick without BPM</a> BY Michal Krawczyk where the Occurance of the IDoc is changed to 1...Unbounded from 1...999999999 by using the XSD.
IDoc Packing is collecting of IDoc
<a href="/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm of Multiple type IDOCs in BPM</a> BY Pooja
Regards
Santhosh
Remember to set the thread to solved when you have received a solution
[url=Use a Good Subject Line, One Question Per Posting - Award Points; Use a Good Subject Line, One Question Per Posting - Award Points[/url]

File to Idoc Scenario and Idoc to File Scenario's

Hi Friends ,
This is Shalini Shah,
Please give me the details of how many busines sytems required in File to Idoc Scenario and Idoc to File sceanrio's.
In business system , what is the name of Integration server(this name is related to XI ot Third Party)
Please give me the full details of these two scenarios from Scratch.
Thanks in Advance.
Regards,
Shalini Shah.

Hi
These r few links which gives u complete scenarios...
for idoc to file:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
for file to idoc:
part1
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
part2
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
part 3
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
This link is also good:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Troubleshooting File-to-IDOC Scenario in XI.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
kindly rewards points if helpful.

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

Diffrence between IDOC successor and idoc copy.

Hello experts,
I have a released IDOC that I can not change. I have now two options, create a copy of
the IDOC or create a successor of it. can you tell me what is the diffrence between the two?
Thanks in advance,
Udi Dekel.

Hi Udi
If you are talking about IDOC data ,you can create the Copy of the Idoc or you can run the IDOC creator
FM or transaction to generate a new Idoc .
An then you can process them using the standard programs or as per the settings.
It would be good if you explain your problem in detail.
Regards
Neha
Edited by: Neha Shukla on Nov 30, 2008 3:32 PM

Idoc Acknowledgement in File

Hi All,
I came through some threads in SDN regarding Idoc acknowledgement and followed handling Idoc acknowledgement document. I am able to get back acknowledgement(ALEAUD) in Xi.
I configured a scenario to receive this acknowledgement in File.
But i am not able get the acknowledgement in the File.
In SXMB_MONI ,in the pipeleine step Technical Routing of Response i am getting Acknowledgement Message Stopped.
How to rectify the above error..I need to get the acknowledgement back in File..?
Is it possible to do without BPM..?
Hoping for good solution..
Thank You
Regards
Prakash

Hi,
If you are lokinf for IDOC acknowledgements means check these
setting up Audit Response.
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
ALEAUD need at least following fields to be filled:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
If you are using XI 3.0 SP12 then there is some bug See : 828277
Just have a look into this blog-/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Or else if you are looking to receive the File Acknowledgements means have a look at this
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Regards
Seshagiri

Difference between message type and idoc type

Hi
difference between message type and idoc type
Regards
Rama

Hi,
Message Type:
A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
Diff. b/w IDOC type and IDOC
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
Example:
MATMAS is the message type and MATMAS05 is IDoc type for Material Master.
Thanks,
Shankar

Idoc type and message type

how to find the idoc type and msg type for particular delivery no.
[[i can see the idoc no in vl33n which i have to display in itab.]]

Message type. A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterizes the data sent across systems and relates to the structure of the data called an IDOC type (see below). For example, MATMAS is a message type for Material Master, and INVOIC is a message type for an Invoice (Billing Document). ALE supports over 200 message types in R/3 and about 200 application areas.

IDOC type and IDOC. An Intermediate Document (IDOC) type represents the structure of the data associated with a message type (DEBMAS02 for message type DEBMAS Customer Master, and WMMBID02 for message type WMMBXY Goods Movements), while an IDOC is an object containing the data of a particular message type. IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. For example, an IDOC of type SHPMNT01, message type SHPMNT, will contain data only of one Shipment Document. Generally, the architecture of an IDOC is independent of the message type by virtue of ALEs ability to redefine it for any message type.
Use transaction BD64 or the following menu path to maintain the model: From the IMG (Implementation Guide), Cross-Application Components -> Distribution (ALE) (*) -> Distribution Customer Model -> Maintain Distribution Customer Model Directly -> Maintain Distribution Customer Model Directly.
Hope this helps you....
Regards,
Pavan

Automatic Payment Process through IDOC and Receive Message Acknowledgement and BANST file format

Hi Experts,
We are implementing payment process to our client through Idoc.
Normally the process will go like below. Once Payment Initiated --> IDoc will generate --> This Idoc process through PI system and send to Bank.--> Once payment data received bank --> it will generate acknowledgement receipt and Bansta file and send it PI system --> This PI system system again send it --> SAP system. Here I want to know the required configuration from PI system to SAP system while receiving acknowledgement and Bansta file. And let me know if u guys have steps...
Thanks,
Raviram

Hi,
>is possible using the fileadapter to read this file and with pass it throug PI to IDOC receiver adapter without any mapping?
yes
>In that case what should the Message Type we are using in the file-sender adapter look like?
If you have no mapping it doesnt matter, the message type will not be validated during runtime. You can take the IDoc type imported from the SAP system
Regards,
Udo

What is the difference beween idoc package and idoc collection

Hi friends,
    i am unable to understand difference betwen Idoc package and Idoc cillection.
    Please give me clear clarification.
Thanks and regards
Bhanu

Hi Bhanu,
Apart from the replies above, in case you're looking for an answer from ECC perspective, here are some inputs: (ECC is considered as sender here)
1. IDoc Collection:
   This will collect the IDocs and will not immediately send it to the target system after they are created. Program RSEOUT00 can be later scheduled for these collected IDocs to deliver them to the target. You can treat this as a park and process approach which proves useful in several business scenarios.
This standard link gives more insight:
SAP Library - IDoc Interface/ALE
2. IDoc Packaging:
    This defines the number of IDocs to be packed and sent in 1 RFC call (tRFC). If you set is as 20, then 20 IDocs will be sent in 1 tRFC request. This doesn't connote whether the IDocs will be triggered immediately or later, this just talks about the bundling of IDocs per RFC call.
Hope this helps.
Regards,
Abhishek

Difference btw idoc ale and edi

Hi all,
I'm a beginner in abap, can anyone send me the concepts of ALE, IDOC and EDI and the difference btw all the three.
Also do send some materials for the same.

Hi,
ALE (Application Linking and Enabling)
Ale Technology is SAPs technology to support distributed yet integrated processes across several SAP systems.
Distributed Process:
A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
Need for Distributed Process:
Business in Different Geographical Locations.
Non availability of dedicated network.
Cultural and language differences in Geographical locations.
Running of Mission-critical Applications (Like Maintenance downtime etc.).
Separate up gradation of Modules.
Distributed SAP SYSTEM CHALLENGES
A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
Receiving systems that can handle their own problems and not tie up the sending system.
Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
A sound technology and methodology that can be used in all distribution scenarios.
SAP Distributed environment:
ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
Benefits of ALE:
Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch ALE Service).
IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
Basic integrity check: A basic integrity check is performed on the control record.
Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function modules output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).
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)
RFC:
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
[http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm]
check out the following link it might help you
[http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf]
EDI:
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
[http://www.erpgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
EDI FLOW :
Here is some thing which helps you and here the purchase order is taken as example too..
Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
What parts of the business cycle can be supported by EDI?
Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
How does EDI get started?
EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
What is the flow of EDI?
The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
check this.
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
[ALE / IDOC / RFC / EDI]
[SAP ABAP and EDI/ALE/IDOC]
[Re: IDOC/BAPI/ALE/EDI]
Regards,
Dhruv Shah

Logical system for IDoc acknowledgment?

Hi,
HTTP --> XI --> IDOC (with acknowledgment) is my scenario
whether the inbound and outbound parameters should be configured in the same logical system or in a different one (in transaction we20)
Thanks,
RPN

For IDOC acknowledgement ,go thru this and do the settings :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
This will help u :
Configuration Tips for a Business Service/Integration Process to send back ALE audit IDOC

Suppress Idoc acknowledgement in SAP PI 7.3

Hi Experts,
I need to suppress ALEAUD Idoc acknowledgements in PI. My scenaros is Idoc (ORDRSP) to file pass through.
Aleady entries are maintained for ORDRSP idoc in IDXNOALE table.
in SE16, IDXNOALE--> Selected ORDRSP entry--> change mode --> I have deleted values for NEG and TYPE, when i trigger Idoc from ECC, first time i am not getting acknowledgements but once i trigger automatically NEG value is updating as "X", from next time i am getting acknowledgements.
I have executed IDX_NOALE report in SE38, If i select ORDRSP message type and click on DoNotRequestAcknowledgments, its asking do you want to overwrite for all? if i select yes, all entries are deleted.
Help me to suppress these ALEAUD acknowledgements in SAP PI 7.3.
Attached is the enries i have updated.
Thanks & Regards,
Mohan.

Hi Harish,
I have checked this thread, As i mentioned earlier
I have executed IDX_NOALE report in SE38, If i select ORDRSP message type and click on DoNotRequestAcknowledgments, its asking do you want to overwrite for all? if i select yes, all entries are deleted.
To suppress idoc acknowledgements, do we need to add entries in IDXNOALE table or do we need to delete existing entreis by using report IDX_NOALE?
If i change NEG and TYPE values as empty, first time its working however next time automatically NEG value is updating as "X" due to that i am getting acknowlegement agan in the second time.
I am confused.
Thanks & Regards,
Mohan.

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 Acknowledgements and Idoc Packaging

Similar Messages

Maybe you are looking for