Request iDoc and status iDoc correlation

Hello,
I have a strange problem.
In my XI 3.0, I have an iDoc2iDoc interface which used to work fine, until I installed patch level 14.
Now, when the acknowledgement (ALEAUD) comes back into my R/3 system, the iDoc system does not recognize it as a response for a specific request iDoc I've sent, but as an ordinary inbound iDoc.
After a short investigation, I found out that the iDoc number is not correlated, it seems like a problem in the iDoc adapter in the XI, that does not translate the iDoc number of the target system back into the iDoc number of the original system.
Has anyone met with this kind of problem ? any solutions ?
Thank you,
Elad.

Hi Anand.
All of the partner profile and iDocs configuration are complete and correct.
I'll try to be a bit more specific:
Local R/3 sends iDoc MATMAS through XI 3.0 and receives ALEAUD iDoc as an applicational acknowledgement.
For the R/3 to be able to correlate between the inbound ALEAUD and the outbound MATMAS the iDoc system uses a field containing the iDoc number.
The problem is that ALEAUD has the number generated by the remote system and the MATMAS has the number of my local system, the XI is suposed to translate the remote iDoc number back to the local iDoc number.
I hope it's clearer now, and that someone can help.
Thank you,
Elad.

Similar Messages

Difference between Master Idoc and Communication Idoc.

Can anyone list out the difference between Master Idoc and Communication Idoc?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI
Layout of an IDoc control record
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records are used to record these errors and the date/time of their occurrence.
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system Records in a multiple-message IDoc

Idoc and status (68)

Hello all,
My customer gets sometimes inbound messages with status 51 that can't be processed automatically (with BD87 or other). For a few kinds of messages, my customer corrects the problem manually in the target business document => The relevant idoc won't have to be processed in the future.
We would like to change the status of this idoc in order to identify it as an idoc that :
- has never been processed => status <> 53
- are never should never be be processed => status <> 51
Status 68 seems to be defined for such a request.
Is it the case ?
How can I turn my Idoc status from 51 to 68 with a business transaction (without using RC1_IDOC_SET_STATUS). (I want an User action)
Thanks a lot
J.C.

Hi JC,
Yes, with status 68 the Idoc cannot be send to application again.
If you need the user change the status manually, maybe you could generate a new transaction for this pourpose associated to a abap program that performs first a selection of Idocs with status 51, and later performs an user action that simply call IDOC_STATUS_WRITE_TO_DATABASE function module to change them to 68 .
Regards,
Roger

Missing IDoc and recurring IDoc errors

Hi,
I would like to ask for a help or any ideas on below case.
We encountered almost everyday a number of generated IDoc errors and the number increases everyday. All of these IDocs has Status "51" (application document not posted) and description "EDI: IDoc 63120 does not exist, please check data".
This IDoc errors does not happen before. It only started when the IDoc 63120 was missing and we can't find it already. We don't know why this is missing and we really need to get rid of these recurring IDoc errors whcih increases almost everyday.
Your response will be helpful in solving my problem.
Thanks in advance!

Hi Juan Francisco Zurita Duque
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
Use
Sold-to party number sent in by the customer in delivery schedules.
Use
The system uses this number to automatically determine the ship-to party.
Every thing good for ORDRE05 IN ECC6.0
Check your config settign related to Message type and idoc type.....once again.....
RR

How to encode XML to Idoc and decode Idoc to XML in business connector?

Hi all,
first of all: thanks for all, who are reading and perhaps responding this question!
Here some facts and my question(s):
The facts:
- I have the business connector version 4.6!
- I'm not working with any SAP Netviewer!
- I have XML files on an FTP-server and Idoc-files on an FTP-server --> so no connection between SAP and business connector, meaning: the files are just on the ftp-server!
What am i doing and what is working properly:
- Business connector logs in into the FTP-server (with FTP-service: pub.client.ftp:login)
- gets the file (with FTP-service: pub.client.ftp:get) (the idoc-file, when i want to convert it into XML or the XML-file, when i want to convert it into idoc-format)
- puts the file into another place in the server (with service wm.PartnerMgr.gateway.transport.FTPTransport:OutboundProcess)
!!!So far only getting and putting of the file works!!!
What is missing between getting the file in one format - for example idoc-format - and putting the file into the server in the other format - for example XML-format is:
CONVERSION FROM XML INTO IDOC AND VICE VERSA
My question:
- which services i have to use between getting and putting the files?
Thanks to all,
Tamer

Hi,
I have the same problem. I do fix it?
Thanks
Wilson Xavier
Brazil

How to send single person-records with HRMD_A Idoc and change Idoc header?

Hello group,
we have different companies in our SAP system (BUKRS). Now when an infotype is changed the changepointers are activated and using program RBDMIDOC we can send Idocs of type HRMD_A to f.i. files. In order to have these files distributed to different parties depending on BUKRS of the person we would like to have HRMD_A to deliver single records, an Idoc for each person and the Idoc header fields for variant and function should be filled so that the partner profile would distribute the Idoc to the partie.
Is this possible? And if yes how?
Regards, Léon Hoeneveld The Netherlands

Transaction PFAL lets me trigger the Idoc manually, but with a job for RBDMIDOC this is automatically.
I found fm RH_HRMD_BLOCK_SIZE in wich you can enhance the code to set the block size for an Idoc-type to 1.
But now I still have to change the Idoc header with an enhancement of user-exit.
HRALE00OUTBOUND_IDOC BADi does not have the functionallity.
Regards, Léon Hoeneveld

Difference between CREMDM04 Idoc and CREMAS04 Idoc

Hi all,
I am creating a vendor using an idoc CREMAS04.
But there are some fields which are not there in that IDOC (fields like Email address , POBOX number for other country) so i want to know that is there any other IDOC which contains all the fields for the vendor creation.
I have found the IDOC CREMDM04 which contains those fields but i want to know the difference between the CREMDM04 and CREMAS04.
I also want to know that will it make any difference is i use CREMDM04 instead of CREMAS04(like is it that all the fields of CREMAS04 is there in CREMDM04 or no).
If anybody knows ,then please let me know.
Thanks in advance.
Shruti.

to name a few:
CREMAS01 Vendor master data distribution ALE
CREMAS02 Vendor master data distribution ALE
CREMAS03 Vendor master data distribution
CREMAS04 Vendor master data distribution
CREMDM01 MDM: Mass Processing CREMAS (Vendor Master)
CREMDM02 MDM: Mass Processing CREMAS (Vendor Master + Addresses)
CREMDM03 MDM: Mass Processing CREMAS (Vendor Master + Addresses)
CREMDM04 MDM: Mass Processing CREMAS (Vendor Master + Addresses)

What is IDOC and ALE?

Hi anybody,
         Please tell me what is IDOC and ALE? What pupose using IDOC and ALE?
          Give me Example sample code of using IDOC and ALE.
Thanks
S.Muthu.

Dear,
Here is some facts which will be helpful to clear yr concepts for ALE/IDOCs.
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.
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.
*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.
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.
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
How to create idoc?
*WE30 - you can create a IDOC type
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
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
This report creates IDocs from the change pointers for the specified message type. It then sends them to the receiving system and flags the change pointers as processed in respect of the specified message type.
The receiving systems for the specified message type are determined from the customer distribution model.
Output:-The report outputs information about the number of master IDocs and communication IDocs created.
RSEOUT00 Process all selected IDocs (EDI) Report for generation of files for EDI outbound processing.The report processes the IDocs available in the system with the status 'to be processed'. The IDocs are selected according to the selection options and parameters specified.
It is important that you make sure that only test messages or productive messages are selected.
The IDocs are processed in various files for various output modes and for various ports. The names of the files are created according to the naming definition for the outbound file. This definition is determined in the port definition.
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.
Hope This will be helpful,
Best Regards ,
P Singh

How to trigger automatically an IDOC and RFC from SAP R/3 system?

Hi ,
lets say if we are implementing IDOC to FILE &RFC to FILE scenario ,how can we trigger on timely basis(schedules)
1)standard IDOCs and BAPIs?
2)customized Idocs and Customized Bapis?
3)Master Idocs and transactiona Idocs?I think we need to use change pointers for master Idocs and donno about Transactional Idocs.
please explain ,
thank you very much for your help.
regards,
Babu

sorryfor the late reply, I was busy with my work.thank you for your posts.
so all of you say just run the RSEOUT00 no matter what interface we use in XI like Master ,transactional Idocs,standard or customized BAPIs?
And I think we use RSNASTED if we have on recieving side right?
<b>then when we would use a report of format below to trigger an RFC,is this format for Asunc RFC ?</b>
REPORT Z_SEND_DATA_TO_XI.
parameters: dest like rfcdes-rfcdest default '(RFC Destination you defined in SM59)'.
<<your other variable declaration and ABAP Code here>>
call function 'ZXI_SEND_DATA'
in background task
destination dest
exporting
Name = John
City = Smith. (The values to pass to XI)
commit work.
<<Any Write statements or sy-subrc statements here>>
6) Save and Activate your ABAP program.
6) After all these steps, execute your ABAP Program to send the data to file via XI.

Idoc and EDI for FI

Hi all,
Can anyoune help me out with the topics.
Idoc and EDI and how this are related to FI.
I was looking for some scenario.
How to process inbound idoc and outbound idoc.
Thanks advance for help.
Regards,
sha

Idocs can be triggered internally by standard coding logic. It can also be triggered by output.
For idocs in delivery processing:
http://help.sap.com/saphelp_erp60/helpdata/en/38/c1853488601e33e10000009b38f83b/frameset.htm
LE-SHp -> printing and communication -> Delivery interface. (here these idocs are generated by output).

Very simple and working IDoc to IDoc scenario

Hi!
I would like to implement for demo issues a working IDoc to IDoc scenario with SAP XI 7.0.
The IDocs sohuld be send from SAP ECC 6.0 system client 100 to SAP ECC 6.0 system client 200.
Questions:
- which material type should be used (e.g. MATMAS02,..)
- how should the message mapping (e.g. MATMAS02 to MATMAS02) look like
- what are the other settings in IB Repository and IB Configuration
- how should the test from WE19 look like?
Thank you very much!

Hi Holger,
No issues for that , U can use the MATMAS 02 or MATMAS 03.
Setting in R/3 system:
1) Create the RFC Destination(SM59).
2) Create the tRFC port(WE21)
3) Create the Partner profiles( WE20)
4) Create the Distribution Model(BD64)
Setting in XI:
1) Create the RFC Destination
2) Create the IDOC Port into IDOC Adapter(IDX1)
3) Load the Metadata into IDOC into IDOC Adapter(IDX2).
Same settings happened in Receiver IDOC also.
Directory : No need to create the Sender agreement & no need to create the Sender Communication Channel.
Repoistery: Import the Sender IDOC and Receiver IDOC from R/3 system.
In WE19 Testing tool we can test IDOC generated or not.
Regards,
Sateesh
D

Info idocs and request idocs

Hi,
I am working in SAP BI extraction presently.
In sap bi/bw systems, data is taken out from SAP R/3 system and sent into BI/BW via Idocs.
This process is called as extraction. I know that data transfer between the SAP R/3 and BI systems happen via idocs.
But here in sap bi we have two type of idocs,
1. Request idocs ( Message type is RSRQST)
2. Info Idocs (Message type is RSINFO)
Request idocs come from BI system to R/3 and from R/3 system data is sent to BI system via Info idocs.
Please can some one give clear explanation about these request and info idocs and how technically they are different
from normal idocs.
Regards,
Lakshminarasimhan.N

no reply to the question and hence closing the question from open status to answered status

IDOC number and status

Hi All,
i am using Function Module IDOC_INBOUND_ASYNCHRONOUS to post inventory records.
its posting the data sucsessfully but it does not return IDOC number and status.
i can see the status and number in WE02 but please tell me how can i get that in my program.
Thakns and regards
Pankaj

Hi friend,
       U can get the status and number of IDOC in WE05 and WE07.
       Once u get the number of IDOC got to table EDIDC(Control Rec table),
       EDID4(Data Rec table) and EDIDS(status Rec table) to get the information
       related to status and content of idoc.
       Directly, u can specify it in ur program as Tables:EDIDC,EDID4,EDIDS
       and get the info according to ur idoc number.
Thanks N Regards,
        Manian.

Idoc not moved to application and status not updated

Hi Guys,
<b>I am facing one issue in our system for message type DESADV (inbound). please read through </b>
When an IDoc is pushed in from the external EDI system & even though the inbound Partner Profile is set to immediate processing mode:
The IDoc stays in status 64 - 'IDoc ready to be transferred to application'. This assumes that the IDoc has not been processed yet
and still needs to be processed with program RBDAPP01 (or via the process button in BD87).
The issue can not be replicated in test mode i.e. using WE19 to copy and process an IDoc, as it has been found that when using WE19 and processing is set to be immediate, the inbound update is fully completed and the IDoc status is set to 53 - Application document posted.
The issue occurs when an IDoc is pushed into SAP from the external EDI system. "
Please help.

Ramandeep28 wrote:
But still I am not able to make any call.
To/within which country?
TIME ZONE - US EASTERN. LOCATION - PHILADELPHIA, PA, USA.
I recommend that you always run the latest Skype version: Windows & Mac
If my advice helped to fix your issue please mark it as a solution to help others.
Please note that I generally don't respond to unsolicited Private Messages. Thank you.

IDOC confirmation and status change ???

SAP friends,
I have a question about IDOCS. We are implementing. In AP after processing payments, our bank will send us a text file which will have idocs number. and status number ( accept and reject).
We have to update that status number for our idoc in the system and if the number that was rejected we have to send an email to everyone. How can we change the status of idoc using the file the bank sends us.
Thanks,
Kavita Reddy

Hi,
Please explain the process detaily. question is not clear.
IDOCs are the intermediate documents, which carry information from SAP to Legacy or vise versa.
IDOCs will be distingwished by message type. These will generate by Program. In program please check about the status.
Thanks
Kalyan

Request iDoc and status iDoc correlation

Similar Messages

Maybe you are looking for