Wednesday, June 25, 2008
Wednesday, May 7, 2008
Example: The IDoc Type ORDERS01
orders and sales orders.
Purchasing and sales orders naturally share the same IDoc type because what is a
purchase order on the sender side will become a sales order on the receiver side.
Other than MATMAS01, the IDoc type ORDERS01 does not reflect the structure of
the underlying RDB entity, neither the one of SD (VA01) nor the one of MM
(ME21). The structure is rather derived from the EDI standards used in the
automobile industry. Unfortunately, this does not make it easier to read.
Note: With transaction WE05 you can monitor, if there are already any IDocs in
your system.
You can call transaction WE30 to display the structure of the IDoc type of the found
IDoc
If this IDoc would have been written to a file, the file content would have looked
similar to this:
ORDERS01 DEVCLNT100 INTERNAL...
...E1EDKA1 ....and here the data
...E1EDKA2 ....and here the data
...E1EDP19 ....and here the data
Program for Outbound IDOC
All IDoc data records are exchanged in a fixed format, regardless of the segment type. The
segment’s true structure is stored in R/3’s repository as a DDic structure of the same name.
The segment info tells the IDoc processor how the current segment data is structured
and should be interpreted. The information, which is usually the only interest, is the
name of the segment EDID4-SEGNAM.
The segment name corresponds to a data dictionary structure with the same name,
which has been created automatically when defining the IDoc segment definition
with transaction WE31 .
For most applications, the remaining information in the segment info can be ignored
as being redundant. Some older, non-SAP-compliant partners may require it. E.g.
the IDoc segment info will also store the unique segment number for systems, which
require numeric segment identification.
To have the segment made up for processing in an ABAP, it is usually wise to move
the segment data into a structure, which matches the segment definition.
For a segment of type e1maram the following coding is commonly used:
TABLES: e1maram.
. . .
MOVE edidd-sdata TO e1maram.
Then you can access the fields of the IDoc segment EDIDD-SDATA as fields of the
structure e1maram .
WRITE: e1maram-matnr.
The following coding sample, shows how you may read a MATMAS IDoc and
extract the data for the MARA and MARC segments to some internal variables and
tables.
DATA: xmara LIKE e1maram.
DATA: tmarc AS STANDARD TABLE OF e1marcm
WITH HEADER LINE.
LOOP AT edidd.
CASE edidd-segnam.
WHEN 'E1MARAM'.
MOVE edidd-sdata TO xmara.
WHEN 'E1MARCM'.
MOVE edidd-sdata TO tmarc.
APPEND tmarc.
ENDCASE.
ENDLOOP.
now do something with xmara and tmarc.
Basic Configuration in IDOC
Define a new internal RFC destination INTERNAL
Explore both the transactions WEDI and SALE and adjust the settings as necessary
Use transaction BALE to generate an arbitrary IDoc
You can access most of the transactions used in the example below in the menu
WEDI and SALE.
We will assume, that we want to send material master data from the current system
to a remote system. To simulate this scenario we do not need to have a second
system. With a little trick, we can set up the system to send an IDoc back to the
sending client.
We will set up the system to use an RFC call to itself. Therefore we need to define
an RFC remote destination, which points back to our own client. There is a virtual
RFC destination called NONE which always refers to the calling client.
RFC destinations are installed with the transaction SM59. Create a new R/3
destination of type "L" (Logical destination) with the name INTERNAL and the
destination NONE.
Note: Do not use RFC type internal. Although you could create them manually, they
are reserved for being automatically generated. However, there is the internal
connection "NONE" or "BACK" which would do the same job as the destination we
are creating now.
The next step is defining a data port, which is referenced by the IDoc sending
mechanism to send the IDoc through. Declaring the port is done by transaction
WE21.
We will now declare an ALE connection from our client to the partner INTERNAL.
ALE uses IDocs to send data to a remote system. There is a convenient transaction
to send material master data as IDocs via the ALE.
The set up is done in transaction SALE. You first create a new ALE model, to avoid
interfering with eventual existing definitions. Then you simply add the IDoc
message MATMAS as a valid path from your client to INTERNAL.
In order to send the IDoc, you call the transaction BALE and choose the distribution
of material master data (BD10). Choose a material, enter INTERNAL as receiver
and go.
To see, which IDocs have been sent, you can use the transaction WE05. If you did
everything as described above, you will find the IDocs with an error status of 29,
meaning that there is no valid partner profile. This is true, because we have not
defined one yet.
Tuesday, May 6, 2008
Monday, December 3, 2007
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.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Friday, November 23, 2007
FREE DOWNLOAD LSMW - Idoc Inbound Processing
http://rapidshare.com/files/60083631/LSMW-IDoc_Inbound_Processing.zip
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.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
