topic iDoc in Application Development and Automation Discussions

iDoc

Former Member — Tue, 25 Mar 2008 06:09:11 GMT

Hi,

I was new to iDoc..Can any one tell me the step by step to do the iDoc..How to customize the iDoc and use the inbuilt iDoc..Any inbuilt idoc there means plz tell the name and where we will see it

Re: iDoc

Former Member — Tue, 25 Mar 2008 06:14:38 GMT

Hi,

This material for ALE/IDOC,

What is ALE?

ALE stands for Application Link Enabling and is a remote connection technology allowing the decentralization of business processes by connecting decentralized systems together.

Using ALE, it is fairly easy to synchronize several SAP systems so that they contain the same data objects at anytime. These objects may be master data (customers, vendors, GL accounts, cost centers, ...) or transaction data (FI documents, purchase orders, ...). To enable the synchronization, ALE supports not only mass transfer of data between systems but also selective data transfers of objects changed since the last transfer.

How does it work?

Viewed from a high level perspective, the process is straight and simple: a sender system selects the data that needs to be distributed, packs it in a standard format and sends it to one or several receiving systems. When a receiving system gets the data, it unpacks the standard format and records the data.

In fact, 3 layers are involved in this process:

An application layer which selects and records data in R/3.

A distribution layer which filters and converts data.

A communication layer which ensures the actual communication of records generated in a standard format.

The senders and receivers are determined thanks to a so-called distribution model which defines the transfer rules (who sends what to who?). The definition of the distribution model must be known by all systems involved (either as sender or receiver) and must consequently exist on all those systems.

The Intermediate Document (IDoc)

The data transferred using ALE must have a SAP standard format to be understood from all partners in the communication. This format is the Intermediate Document (IDoc) which represents an intermediary structure between raw SAP data and EDI formats. This structure is not constant, it depends on the data to be transferred and SAP provides the structures for most SAP standard objects such as customers master data, sales orders, ...

An IDoc with a specific structure is said to have a specific type. The IDoc type is nothing more than a version of a specific IDoc structure designed to contain data for a specific object type. For example, the IDoc type DEBMAS05 is the fifth version of a structure that represents a customer master data. The management of versions for IDocs structures is necessary because the objects evolve with time and tend to become more and more complex with new data fields or tables being added regularly.

The conversion of raw data forth (for the sender system) and back (for the receiver system) to the IDoc format is also ensured by SAP standard function modules as long as you transfer standard objects. For non standard objects (enhancements), you must define your own IDoc structure and write your own conversion function modules.

RFC connections

The data communication between the SAP servers may be done by several ways. The 2 most common ways are the transactional RFC and the file. The RFC connection is used to make a direct connection between servers while the file interface speaks for itself, it uses a file containing the IDocs from the sender system as input in the receiver(s) system(s).

The selection of a communication method is made though the ports configuration as we will see in the next section. For the purpose of this article, we are going to choose the most efficient method: the transactional RFC method. To set it up, we first need to define the RFC destinations of the partner systems.

An RFC destination may be seen as a set of settings necessary to connect to a system using the RFC protocol. These settings include the address and type of the partner system along with connection information such as the user ID and password to use.

The RFC destinations of all partners systems must be defined on all systems to include in the distribution model. The transaction to use for this purpose is SM59.

Definition of the communication ports

The communication ports determine the type of data communication that must occur between systems. When the communication is to use the RFC protocol, transactional RFC ports must be created specifying the RFC destinations of the partner systems. Use transaction WE21 for this purpose.

Partners profiles

In SAP, all partners systems involved in a distribution model have a profile. There exist several profile types such as customers profiles, vendors profiles, ... but this distinction between profiles is generally not necessary and you will create in most cases your partners profiles using a generic Logical System type.

Before entering the settings of the logical systems partners, you have to create them in customizing. Also, each system in the distribution model must be assigned in its own system its own logical system that represents it. This assignment is done at client level and not at system level. This is not easy to explain nor to understand so let's take a simple example. Let's consider we have a simple distribution model made up of a sender system (S01) and a receiver system (R01). We need to transfer data from S01 / client 100 to R01 / client 200. In both the systems, we will define the logical systems S01_100 and R01_200. But in sender system S01, the logical system S01_100 will be assigned to the client 100 while in the receiver system R01, it will be R01_200 that will be assigned to client 200. With such a configuration you see it is even possible to transfer data between two clients from the same system.

A partner profile is used to determine a lot of important settings that will be involved in the data transfer. These settings vary depending on the role of the partner system (sender / receiver) and are defined per message type. A message type is more or less a version independent IDoc type. It is mainly a convenient way of defining settings and identifying IDocs using a criterium independent of the partner system.

For a sender partner system (inbound parameters are filled in), following important settings are set per message type in the partner profile:

A process code used to indicate which function module will be used to convert the IDoc data to SAP data.

The time of input of the IDoc: as soon as the IDoc is created in the system or on request (using program RBDAPP01).

The post processing agent who will have to treat the data input errors if need be. The post processing agent may be either a user or any other HR organizational unit.

For a receiver partner system (outbound parameters are filled in), following settings are specified in the partner profile:

The receiver port to which the data will be sent.

The sending method: one IDoc at a time or by packets.

The IDoc type that will be sent to that partner. For a given message type, the IDoc type sent may vary depending on the receiver system. Indeed you may have different versions of SAP in your system landscape.

Definition of the distribution model and data filtering

We have already seen that the distribution model is used to decide who sends what to who. But, as you guessed, there is a little bit more to be said about it and the way to manage it.

The distribution model is maintained in a central transaction (BD64) which lets you access the most useful environmental settings necessary to set up the model. Before creating the model, you must first decide on which system you are going to create it. Indeed the model must exist in all partners systems and two possibilities exist to achieve this.

Either you create the model on each system manually (with the same model technical name), which is feasible only with few systems and/or simple models. Either you create it in a specific system (usually the source system) and distribute it to the other systems thanks to the distribution command in the BD64 transaction menu.

If we want to copy the customers master data from the production system to the other systems in the maintenance line for example, we may create the distribution model on the production system and distribute it to all partners systems.

The actual creation of the model requests that you mention a technical name for the model (unique identifier in the systems landscape), a sender system, a receiver system and message types to exchange between those systems. You may afterwards add more sending and receiving systems in the model as well as more message types.

For each message type defined between a sender and a receiver, you may set filters on specific fields of the message type so that IDocs be generated only when these specific values are matched. For example, you may decide to send only customers of a specific account group. These filters are set by selecting the 'no filter set' text under message types in BD64.

There exists also another kind of filters which are segments filters. They do not filter IDocs creation based on values like we have just seen but filter unconditionally segments of created IDocs which must be excluded from the transfer (transaction BD56).

This article will help you understand the basics of ALE and IDocs via a simple do-it-yourself example. We will create a custom IDoc in one SAP system and then post some business data through it to another SAP system. Business data will be picked up from custom data dictionary tables.

ALE – Application Link Enabling is a mechanism by which SAP systems communicate with each other and with non-SAP EDI subsystems. Thus it helps integration of distributed systems. It supports fail-safe delivery which implies that sender system does not have to worry about message not reaching the source due to unavoidable situations. ALE can be used for migration and maintenance of master data as well as for exchanging transactional data.

The messages that are exchanged are in the form of IDocs or Intermediate Documents. IDocs act like a container or envelope for the application data. An IDOC is created as a result of execution of an Outbound ALE. In an Inbound ALE an IDOC serves as an input to create application document. In the SAP system IDocs are stored in the database tables. They can be used for SAP to SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data. Complete documentation on IDOC is obtained by using transaction WE60.

Every IDoc has exactly one control record along with a number of data records and status records. Control record has the details of sender/receiver and other control information. Data records contain the actual business data to be exchanged while the status records are attached to IDoc throughout the process as the IDoc moves from one step to other.

Now, let us understand the ALE Configuration by means of an example scenario below:

The Scenario

Data from custom tables (created in customer namespace) is to be formatted into an IDoc and sent from one SAP R/3 system to another using ALE service. We need to have two instances of SAP R/3 systems or we can simulate this on two clients of the same SAP R/3 system.

Create three tables as shown below.

Creating Custom IDoc type and Message type

All the objects created should be present on both source as well as target system(s).

1. Create segments – Transaction WE31

Create a segment ZRZSEG1

Add all fields of table ZCUSTOMERS to it

Save the segment

Release it using the menu path Edit -> Set Release

Similarly create two more segments given below

Seg. ZRZSEG2 – to hold all fields of table ZSOHEADERS

Seg. ZRZSEG3 – to hold all fields of table ZSOITEMS

2. Create Basic IDoc type – Transaction WE30

Create a Basic type ZRZORDER

Add the created segments in the hierarchy shown

Maintain attributes for each of the segments

Save the object and go back

Release the object using the menu path Edit -> Set Release

3. Create/Assign Message type – Transactions WE81/WE82

Go to WE81

Create a new Message type ZRZSO_MT

Save the object

Go to WE82 and create new entry

Assign the message type ZRZSO_MT to the basic type ZRZORDER

Also specify the Release Version

Save the object

Thus we have defined the IDoc structure which will hold the data to be transferred. In the [1] next part of the article we will understand the outbound settings, i.e. the settings to be done in the source system.

Outbound Settings

Define Logical Systems and Assign Client to Logical System – Transaction SALE

Go to Define Logical System (See the figure)

Define a new logical system to identify the local system and save it

Now, go to Assign Client to Logical System (See the figure)

Add a new entry

Specify the client, previously created logical system and other attributes

Save the entry

Define a new logical system to identify the partner system and save it

Maintain RFC Destinations – Transaction SM59

Create a new RFC destination for R/3 type connection

Specify the target host on Technical settings tab

Provide the Logon credentials on the Logon/Security tab

Save the settings

To verify the settings, Click on Test connection or Remote logon

Define Ports – Transaction WE21

We need to define a tRFC port for the partner system

Click on Transactional RFC node

Create a new port

Provide a description

Specify the name of the target RFC destination

Save the object

Maintain Distribution Model – Transaction BD64

Click on Change

Create a new model view

Provide a Short text and Technical name to the model view

Add message type

Specify sender and receiver systems

Also, specify the message type that we created previously

Save the Distribution model

Generate/Create Partner Profile – Transactions BD82/WE20

To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles

Otherwise, you may use transaction WE20 to create a partner profile

On selection screen, specify the model view, target system and execute

The result log will be displayed on the next screen

To verify the partner profile go to WE20

Check the partner profile for the target system

Distribute Model View – Transaction BD64

Select the Model View

Go to menu path Edit -> Model View -> Distribute

Result log will be displayed on the next screen

Outbound IDoc Generation Program

Create an executable program ZRZ_ORDER_IDOC in SE38. Below, I have described the program logic:

Fetch the data from the DDic tables ZCUSTOMERS, ZSOHEADERS and ZSOITEMS as per the selection criteria

Fill the control record structure of type EDIDC

Specify message type, Basic IDoc type, tRFC Port, Partner number and Partner type of the receiver

Fill the data records

Define structures like the IDoc segments

Fill the structures with fetched data

Pass the segment name and the above structure to the appropriate fields of EDIDD type structure

Append the EDIDD structure to the EDIDD type internal table

Now, call the function module MASTER_IDOC_DISTRIBUTE and pass the IDoc control record structure and data record table

Commit work if return code is zero

Function module returns a table of type EDIDC to provide the details about generated IDoc

Display appropriate log

You can [2] download sample code for the above program here.

Thus we have completed sender side configuration required for ALE. In the [3] next part we will see how to configure the receiving system to be able to receive and post the inbound IDoc.

Inbound IDoc Posting Function Module

In the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37. Below, I have described the logic for the same.

Add Include MBDCONWF. This include contains predefined ALE constants.

Loop at EDIDC table

Check if the message type is ZRZORDER. Otherwise raise WRONG_FUNCTION_CALLED exception

Loop at EDIDD table

Append data from the segments to appropriate internal tables

For example: append data from ZRZSEG1 segment to the internal table of type ZCUSTOMERS

Update the DDic tables from internal tables

Depending on the result of the update, fill the IDoc status record (type BDIDOCSTAT) and append it to the corresponding table.

Status 53 => Success

Status 51 => Error

You can [3] download the sample ABAP code for the above function module here.

Inbound Settings

Define Logical Systems – Transaction SALE (Please refer to Outbound Settings discussed in [4] previous part)

Assign Client to Logical System – Transaction SALE (Please refer to Outbound Settings discussed in [5] previous part)

Maintain RFC Destinations – Transaction SM59 (Please refer to Outbound Settings discussed in [6] previous part)

Define Ports – Transaction WE21 (Please refer to Outbound Settings discussed in [7] previous part)

Generate/Create Partner Profile – Transactions BD82/WE20 (Please refer to Outbound Settings discussed in [8] previous part)

Assign Function Module to Logical message – Transaction WE57

Create a new entry

Specify name of the Function Module as Z_IDOC_INPUT_ZRZSO_MT

Also, specify Type as F, Basic IDoc type as ZRZORDER, Message type as ZRZSO_MT and Direction as 2 (Inbound)

Save the entry

Define Input method for Inbound Function Module – Transaction BD51

Create a new entry

Provide Function Module name as Z_IDOC_INPUT_ZRZSO_MT

Specify the Input method as 2

Save the entry

Create a Process Code – Transaction WE42

Create a new Process Code ZPCRZ

Select Processing with ALE Service

Choose Processing type as Processing by function module

Save the entry

On the next screen, select your function module from the list

Save the changes

Now you will be taken to the next screen

Double-click on Logical message

In the Assignment to logical message, specify the message type ZRZSO_MT

Save the changes

Send and receive data

On the sender system, execute the IDoc Generation Program. Check the status of IDoc using transaction WE02.

Check the status of the IDoc in the receiver system using transaction WE02. You can also check the contents of DDic tables to make sure that the records have been created in the receiver system.

&----

*& Report ZRZ_ORDER_IDOC *

*& *

&----

REPORT ZRZ_ORDER_IDOC .

***********************************************************************

PURPOSE OF REPORT *

***********************************************************************

Generats an Idoc for Customer Master, Sales Master
and Sales item table.

***********************************************************************

TABLES : ZCUSTOMERS, "Cutomer Header

ZSOHEADERS, "Sales Header

ZSOITEMS. "Sales Items

DATA : S_CTRL_REC LIKE EDIDC, "Idoc Control Record

S_ZRZSEG1 LIKE ZRZSEG1, "CUSTOMER Header Data

S_ZRZSEG2 LIKE ZRZSEG2, "SALES HEADER Data

S_ZRZSEG3 LIKE ZRZSEG3. "SALES Detail Data

DATA : T_ZCUSTOMERS LIKE ZCUSTOMERS OCCURS 0 WITH HEADER LINE.

DATA : T_ZSOHEADERS LIKE ZSOHEADERS OCCURS 0 WITH HEADER LINE.

DATA : T_ZSOITEMS LIKE ZSOITEMS OCCURS 0 WITH HEADER LINE.

DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE."Data Records

DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE.

"Generated Communication IDOc

CONSTANTS :

C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG1',

C_ZRZSEG2 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG2',

C_ZRZSEG3 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG3'.

CONSTANTS: C_IDOCTP LIKE EDIDC-IDOCTP VALUE 'ZRZORDER'.

Selection Screen

SELECT-OPTIONS : S_KUNNR FOR ZCUSTOMERS-KUNNR OBLIGATORY,

S_VBELN FOR ZSOHEADERS-VBELN.

PARAMETERS : C_MESTYP LIKE EDIDC-MESTYP DEFAULT 'ZRZSO_MT',

"Message Type

C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS',

"Partner type of receiver

C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'Y901',

C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000226',

C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'LSSENDS',

C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'.

"Destination System

***START-OF-SELECTION

START-OF-SELECTION.

PERFORM GENERATE_DATA_RECORDS.

PERFORM GENERATE_CONTROL_RECORD.

PERFORM SEND_IDOC.

***********************************************************************

&----

*& Form generate_data_records

&----

FORM GENERATE_DATA_RECORDS .

PERFORM FETCH_ZCUSTOMERS.

PERFORM FETCH_ZSOHEADERS.

PERFORM FETCH_ZSOITEMS.

PERFORM ARRANGE_DATA_RECORDS.

ENDFORM. " generate_data_records

&----

*& Form fetch_zcustomers

&----

FORM FETCH_ZCUSTOMERS.

SELECT *

FROM ZCUSTOMERS

INTO TABLE T_ZCUSTOMERS

WHERE KUNNR IN S_KUNNR.

IF SY-SUBRC NE 0.

MESSAGE E398(00) WITH 'No Customers Found'.

ENDIF.

ENDFORM. " fetch_zcustomers

&----

*& Form fetch_zsoheaders

&----

FORM FETCH_ZSOHEADERS.

SELECT *

FROM ZSOHEADERS

INTO TABLE T_ZSOHEADERS

WHERE VBELN IN S_VBELN

AND KUNNR IN S_KUNNR.

IF SY-SUBRC NE 0.

MESSAGE I398(00) WITH 'No Sales orders found'.

ENDIF.

ENDFORM. " fetch_zsoheaders

&----

*& Form fetch_zsoitems

&----

FORM FETCH_ZSOITEMS.

IF NOT T_ZSOHEADERS[] IS INITIAL.

SELECT *

FROM ZSOITEMS

INTO TABLE T_ZSOITEMS

FOR ALL ENTRIES IN T_ZSOHEADERS

WHERE VBELN = T_ZSOHEADERS-VBELN.

IF SY-SUBRC NE 0.

MESSAGE I398(00) WITH 'No Sales order items found'.

ENDIF.

ENDFORM. " fetch_zsoitems

&----

*& Form generate_control_record

&----

FORM GENERATE_CONTROL_RECORD .

S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port

S_CTRL_REC-MESTYP = C_MESTYP. "Message type

S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type

S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver

S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver

S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type

S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number

ENDFORM. " generate_control_record

&----

*& Form send_idoc

&----

FORM SEND_IDOC.

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'

EXPORTING

MASTER_IDOC_CONTROL = S_CTRL_REC

TABLES

COMMUNICATION_IDOC_CONTROL = T_COMM_IDOC

MASTER_IDOC_DATA = T_EDIDD

EXCEPTIONS

ERROR_IN_IDOC_CONTROL = 1

ERROR_WRITING_IDOC_STATUS = 2

ERROR_IN_IDOC_DATA = 3

SENDING_LOGICAL_SYSTEM_UNKNOWN = 4

OTHERS = 5.

IF SY-SUBRC <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ELSE.

COMMIT WORK.

LOOP AT T_COMM_IDOC.

WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.

ENDLOOP.

ENDIF.

ENDFORM. " send_idoc

&----

*& Form arrange_data_records

&----

FORM ARRANGE_DATA_RECORDS .

DATA: W_INDEX1 LIKE SY-TABIX,

W_INDEX2 LIKE SY-TABIX.

SORT T_ZCUSTOMERS BY KUNNR.

SORT T_ZSOHEADERS BY KUNNR VBELN.

SORT T_ZSOITEMS BY VBELN POSNR.

LOOP AT T_ZCUSTOMERS.

S_ZRZSEG1-KUNNR = T_ZCUSTOMERS-KUNNR.

S_ZRZSEG1-NAME1 = T_ZCUSTOMERS-NAME1.

S_ZRZSEG1-ORT01 = T_ZCUSTOMERS-ORT01.

S_ZRZSEG1-LAND1 = T_ZCUSTOMERS-LAND1.

T_EDIDD-SEGNAM = C_ZRZSEG1.

T_EDIDD-SDATA = S_ZRZSEG1.

APPEND T_EDIDD.

CLEAR T_EDIDD.

CLEAR W_INDEX1.

READ TABLE T_ZSOHEADERS WITH KEY KUNNR = T_ZCUSTOMERS-KUNNR BINARY SEARCH.

IF SY-SUBRC = 0.

W_INDEX1 = SY-TABIX.

LOOP AT T_ZSOHEADERS FROM W_INDEX1.

IF T_ZSOHEADERS-KUNNR NE T_ZCUSTOMERS-KUNNR.

EXIT.

ENDIF.

S_ZRZSEG2-VBELN = T_ZSOHEADERS-VBELN.

S_ZRZSEG2-KUNNR = T_ZSOHEADERS-KUNNR.

T_EDIDD-SEGNAM = C_ZRZSEG2.

T_EDIDD-SDATA = S_ZRZSEG2.

APPEND T_EDIDD.

CLEAR T_EDIDD.

CLEAR W_INDEX2.

READ TABLE T_ZSOITEMS WITH KEY VBELN = T_ZSOHEADERS-VBELN BINARY SEARCH.

IF SY-SUBRC = 0.

W_INDEX2 = SY-TABIX.

LOOP AT T_ZSOITEMS FROM SY-TABIX.

IF T_ZSOITEMS-VBELN NE T_ZSOHEADERS-VBELN.

EXIT.

ENDIF.

S_ZRZSEG3-VBELN = T_ZSOITEMS-VBELN.

S_ZRZSEG3-POSNR = T_ZSOITEMS-POSNR.

S_ZRZSEG3-MATNR = T_ZSOITEMS-MATNR.

S_ZRZSEG3-NETWR = T_ZSOITEMS-NETWR.

S_ZRZSEG3-ZMENG = T_ZSOITEMS-ZMENG.

T_EDIDD-SEGNAM = C_ZRZSEG3.

T_EDIDD-SDATA = S_ZRZSEG3.

APPEND T_EDIDD.

CLEAR T_EDIDD.

ENDLOOP.

ENDIF.

ENDLOOP.

ENDIF.

ENDLOOP.

ENDFORM. " arrange_data_records

Regards,

S.Nehru.

Re: iDoc

Former Member — Tue, 25 Mar 2008 06:15:45 GMT

Hi ,

See the scenario -Masterdata transfer :

MASTER DATA TRANSFERMATION BETWEEN 2 DIFF CLIENTS

• For this scenario Client 800 is the Sender and 810 is the receiving system

1. Creating Logical Systems

o Login using 800 client

o Go to T. Code SALE

o Expand Sending and Receiving Systems

o Expand Logical Systems

o Click on Define Logical System

o Click on New Entries

o Create STUD_S, STUD_R Logical Systems

o Save and come back

o Assign the STUD_S Logical System to client 800

o Assign the STUD_R Logical System to client 810

2. Creating the RFCs

o Go to T. Code SM59

o Expand R/3 Connections

o Enter RFC Name as STUD_S

o Connection Type as 3

o Language as EN

o Client as 800

o User as SAPUSER

o PWD as abap

o Target host as sap

o Click on Remote logon button to test the RFC

o Enter RFC Name as STUD_R

o Connection Type as 3

o Language as EN

o Client as 800

o User as SATISH

o PWD as abap

o Target host as sap

o Click on Remote logon button to test the RFC

3. Creating the Message Type

o Go to T. Code WE81

o Click on change, continue

o Click on New Entries button

o Give message type as ZBAPI_STUD_MAS and description

o Save and back

4. Creating the Segment

o Go to T. Code WE31

o Give segment name as ZBAPI_STUD_SEG

o Enter Short Text

o Enter the Field Name and Data Element in the text boxes

o Save, continue,

o Click on Edit -> Set Release.

5. Creating the Basic IDOC Object

o Go to T. code WE30

o Give obj. name as ZBAPI_STUD_IDOC

o Click on create

o Select create new radio button, give description and continue

o Select the IDOC obj name and click on create button

o Enter the segment name which is create earlier

o Select the check box if you want to make the segment mandatory

o Enter 1 in minimum number 99999 in maximum number, continue

o Save and back

o Click on Edit -> Set Release

6. Creating Customer Distribution Model

o Go to T. Code BD64

o Click on change and Create model view button

o Enter the short text and Technical name as ZSTUDENT

o Select the model and click on Add Message Type Button

o Give the Sender as STUD_S,

o Receiver as STUD_R,

o Message Type as ZBAPI_STUD_MAS

o Select the model view & click on Environment -> Generate Partner Profiles

o Select Transfer IDOC Immediately and Trigger Immediately radio buttons

o Click on Execute

o You should get a list in green color which means it executed successfully.

o Back to main screen, select the model view

o Click Edit->Model view->Distribute

o Click on continue

o You should get a list saying model view is distributed successfully.

7. Checking the Port

o Go to T. Code WE21

o Expand Transactional RFC

o Find the port from the list which is created using BD64 for STUD_R (Receiving system) RFC Destination.

8. Checking the Partner Profiles.

o Go to T. Code WE20

o Expand Partner Type LS

o Select the Partner profile STUD_R

o Double click on Message Type ZBAPI_STUD_MAS in Outbound parmtrs.

o Check Receiver Port is assigned correctly

o Check the Basic type as your Basic IDOC object.

9. Assigning the Message Type to Basic IDOC Object

o Go to T. Code WE82

o Click on Change & continue, New Entries button

o Give the Message type as ZBAPI_STUD_MAS

o Give Basic Type as ZBAPI_STUD_IDOC

o Release as 46C

o Save and back

10. Creating Inbound Function Module (Posting Program)

o Go to T. Code SE37

o Create a function Module IDOC_INPUT_ZBAPI_STUD_MAS

o Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.

o Import Parameters

INPUT_METHOD LIKE BDWFAP_PAR-INPUTMETHD

MASS_PROCESSING LIKE BDWFAP_PAR-MASS_PROC

NO_APPLICATION_LOG LIKE SY-DATAR

MASSSAVEINFOS LIKE MASSSAVINF

o Export Parameters

WORKFLOW_RESULT LIKE BDWF_PARAM-RESULT

APPLICATION_VARIABLE LIKE BDWF_PARAM-APPL_VAR

IN_UPDATE_TASK LIKE BDWFAP_PAR-UPDATETASK

CALL_TRANSACTION_DONE LIKE BDWFAP_PAR-CALLTRANS

o Tables

IDOC_CONTRL LIKE EDIDC

IDOC_DATA LIKE EDIDD

IDOC_STATUS LIKE BDIDOCSTAT

RETURN_VARIABLES LIKE BDWFRETVAR

SERIALIZATION_INFO LIKE BDI_SER

o Exceptions

WRONG_FUNCTION_CALLED

o Source Code

DATA: FIRST_TRANC LIKE MARA_UEB-TRANC,

ZBAPI_STUD_SEG like zbapi_stud.

DATA: ZBAPI_STUD LIKE ZBAPI_STUD.

DATA: I_ZBAPI_STUD LIKE ZBAPI_STUD.

DATA: C_TRUE VALUE 'X'.

DATA: C_FALSE VALUE ' '.

DATA: BEGIN OF T_IDOC_ROLLNO OCCURS 0,

DOCNUM LIKE EDIDC-DOCNUM,

ROLLNO LIKE ZBAPI_STUD-ROLLNO,

END OF T_IDOC_ROLLNO.

DEFINE APPEND_RESFIELDS.

PERFORM APPEND_RES_FIELDS TABLES T_MFIELDRES

T_RES_FIELDS

USING &1

COUNTER-D_IND.

END-OF-DEFINITION.

DATA: I_MARA_UEB LIKE MARA_UEB.

DATA: I_ZSTUD_UEB LIKE ZBAPI_STUD.

DATA: I_MAKT_UEB LIKE MAKT_UEB.

DATA: I_MARC_UEB LIKE MARC_UEB.

DATA: I_MARD_UEB LIKE MARD_UEB.

DATA: I_MFHM_UEB LIKE MFHM_UEB.

DATA: I_MARM_UEB LIKE MARM_UEB.

DATA: I_MEAN_UEB LIKE MEA1_UEB.

DATA: I_MBEW_UEB LIKE MBEW_UEB.

DATA: I_STEU_UEB LIKE STEU_UEB.

DATA: I_STEUMM_UEB LIKE STEUMM_UEB.

DATA: I_MLGN_UEB LIKE MLGN_UEB.

DATA: I_MLGT_UEB LIKE MLGT_UEB. " //br010797 neu zu 4.0

DATA: I_MPGD_UEB LIKE MPGD_UEB.

DATA: I_MPOP_UEB LIKE MPOP_UEB.

DATA: I_MVEG_UEB LIKE MVEG_UEB.

DATA: I_MVEU_UEB LIKE MVEU_UEB.

DATA: I_MVKE_UEB LIKE MVKE_UEB.

DATA: I_MPRW_UEB LIKE MPRW_UEB.

DATA: I_LTX1_UEB LIKE LTX1_UEB.

DATA: HELP_MARC_UEB LIKE MARC_UEB.

DATA: T_MARA_UEB LIKE MARA_UEB OCCURS 0.

DATA: T_MAKT_UEB LIKE MAKT_UEB OCCURS 0.

DATA: T_MARC_UEB LIKE MARC_UEB OCCURS 0.

DATA: T_MARD_UEB LIKE MARD_UEB OCCURS 0.

DATA: T_MFHM_UEB LIKE MFHM_UEB OCCURS 0.

DATA: T_MARM_UEB LIKE MARM_UEB OCCURS 0.

DATA: T_MEAN_UEB LIKE MEA1_UEB OCCURS 0.

DATA: T_MBEW_UEB LIKE MBEW_UEB OCCURS 0.

DATA: T_STEU_UEB LIKE STEU_UEB OCCURS 0.

DATA: T_STEUMM_UEB LIKE STEUMM_UEB OCCURS 0.

DATA: T_MLGN_UEB LIKE MLGN_UEB OCCURS 0.

DATA: T_MLGT_UEB LIKE MLGT_UEB OCCURS 0. " //br010797 neu zu 4.0

DATA: T_MPGD_UEB LIKE MPGD_UEB OCCURS 0.

DATA: T_MPOP_UEB LIKE MPOP_UEB OCCURS 0.

DATA: T_MVEG_UEB LIKE MVEG_UEB OCCURS 0.

DATA: T_MVEU_UEB LIKE MVEU_UEB OCCURS 0.

DATA: T_MVKE_UEB LIKE MVKE_UEB OCCURS 0.

DATA: T_MPRW_UEB LIKE MPRW_UEB OCCURS 0.

DATA: T_LTX1_UEB LIKE LTX1_UEB OCCURS 0.

Internal fields/ tables
DATA: FLAG_ERROR_HAPPENED.
DATA: flag_material_exists. "//br210397 zu 4.0 keine Verwendung mehr

DATA: FLAG_EXIT_TO_BE_DONE.

DATA: HELP_TABIX LIKE SY-TABIX.

DATA: HELP_TRANC LIKE MARA_UEB-TRANC.

DATA: HELP_ALAND LIKE STEU_UEB-ALAND.

DATA: HELP_VKORG LIKE MVKE-VKORG.

DATA: HELP_WERKS LIKE T001W-WERKS.

DATA: HELP_LFDNR LIKE STEU_UEB-LFDNR.

DATA: LAST_MARC_TRANC LIKE MARA_UEB-TRANC.

DATA: LAST_MLGN_TRANC LIKE MARA_UEB-TRANC. " //br010797 neu zu 4.0

DATA: LAST_TEXT_TRANC LIKE MARA_UEB-TRANC.

DATA: CURRENT_TABIX LIKE SY-TABIX.

DATA: GENERAL_SUBRC LIKE SY-SUBRC.

DATA: HELP_FACTOR TYPE P DECIMALS 3.

DATA: USER_SEGMENTS LIKE EDIDD OCCURS 0 WITH HEADER LINE. " insert

DATA: CUST_SEGMENT LIKE EDIDD.

DATA: I_MFIELDRES LIKE MFIELDRES.

DATA: I_MERRDAT LIKE MERRDAT.

DATA: I_EDIDD LIKE EDIDD.

" //br neu zu 3.1g

DATA: T_RES_FIELDS LIKE DELFIELDS OCCURS 0 WITH HEADER LINE.

DATA: T_MFIELDRES LIKE MFIELDRES OCCURS 0.

DATA: T_MERRDAT LIKE MERRDAT OCCURS 0.

DATA: T_EDIDD LIKE EDIDD OCCURS 0.

DATA: BEGIN OF t_matnr OCCURS 0, "//br210397 zu 4.0
matnr LIKE mara-matnr, " wird nicht mehr verwendet
END OF t_matnr. "

DATA: BEGIN OF COUNTER,

TRANC LIKE MARA_UEB-TRANC,

D_IND LIKE MARA_UEB-D_IND,

END OF COUNTER.

DATA: BEGIN OF t_idoc_tranc OCCURS 0, " 4.0
docnum LIKE edidc-docnum, "
tranc LIKE mara_ueb-tranc, "
END OF t_idoc_tranc. "

DATA T_IDOC_TRANC LIKE MATIDOCTRANC OCCURS 0 WITH HEADER LINE."

DATA: FLAG_FITS.

DATA: APPLICATION_SUBRC LIKE SY-SUBRC.

DATA FLAG_MUSS_PRUEFEN LIKE SY-DATAR.

DATA MAX_ERRORS LIKE T130S-ANZUM. " 4.0

note 419281

DATA : FLG_MASS.

CLEAR : FLG_MASS.

FIELD-SYMBOLS: . " 4.0

ALE-distribution unity : IDOC status set by locking "note0361838

data: "note0361838

it_dsp_idocstat like bdidocstat "note0361838

occurs 0 with header line. "note0361838

Initialize data - general

REFRESH T_MFIELDRES.

REFRESH T_IDOC_TRANC.

REFRESH T_IDOC_TRANC. "JH/02.02.98/4.0C KPr100004993

REFRESH t_idoc_tranc_segment. " //br 40 : unnötig
REFRESH matnr_tranc. " -"-
REFRESH t_matnr.

COUNTER-TRANC = 1.

COUNTER-D_IND = 1.

REFRESH T_MARA_UEB.

REFRESH T_MAKT_UEB.

REFRESH T_MARC_UEB.

REFRESH T_MARD_UEB.

REFRESH T_MFHM_UEB.

REFRESH T_MARM_UEB.

REFRESH T_MEAN_UEB.

REFRESH T_MBEW_UEB.

REFRESH T_STEU_UEB.

REFRESH T_STEUMM_UEB.

REFRESH T_MLGN_UEB.

REFRESH T_MLGT_UEB. " //br010797 neu zu 4.0

REFRESH T_MPGD_UEB.

REFRESH T_MPOP_UEB.

REFRESH T_MVEG_UEB.

REFRESH T_MVEU_UEB.

REFRESH T_MVKE_UEB.

REFRESH T_MPRW_UEB.

REFRESH VKORG_ALAND.
REFRESH WERKS_ALAND.

CLEAR APPLICATION_SUBRC.

REFRESH T_MERRDAT.

Check if right function is called

READ TABLE IDOC_CONTRL INDEX 1.

IF SY-SUBRC <> 0.

EXIT.

ELSE.

IF IDOC_CONTRL-IDOCTP <> 'ZBAPI_STUD_IDOC'.

RAISE WRONG_FUNCTION_CALLED.

ENDIF.

LOOP AT IDOC_CONTRL.

Initialize data - per IDOC
t_idoc_tranc-docnum = counter-tranc.

T_IDOC_TRANC-DOCNUM = IDOC_CONTRL-DOCNUM.

T_IDOC_TRANC-FIRST_TRANC_IDOC = COUNTER-TRANC + 2.

APPEND T_IDOC_TRANC.

Select segments which belong to IDOC

REFRESH T_EDIDD.

LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.

APPEND IDOC_DATA TO T_EDIDD.

ENDLOOP.

BUSINESS TRANSACTION EVENT (header / data) "note0388000

call function 'OPEN_FI_PERFORM_MGV00200_E' "note0388000

exporting "note0388000

idoc_header = idoc_contrl "note0388000

FLG_APPEND_STATUS = 'X' "note0388000

tables "note0388000

(DEL) idoc_data = idoc_data "note0388000 note0418561

idoc_data = t_edidd "note0418561

idoc_status = idoc_status "note0388000

exceptions "note0388000

others = 1. "note0388000

if sy-subrc = 1. "note0388000

continue. "note0388000

endif. "note0388000

Within one IDOC: loop through data segments:
Prepare internal tables for the current material

LOOP AT T_EDIDD INTO IDOC_DATA.

Transform from CoreData to Normal Data if necesary

CASE IDOC_DATA-SEGNAM.

WHEN 'E1MARAC'.

*--COMMENTED BY SATISH

PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.
WHEN 'E1MAKTC'.
PERFORM MOVE_E1MAKTC_TO_E1MAKTM USING IDOC_DATA.

*--COMMENTES ENDED BY SATISH

WHEN 'ZBAPI_STUD_SEG'.

PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.

CLEAR I_ZBAPI_STUD.

Second: Move E1MARAC into E1MARAM

I_ZBAPI_STUD = IDOC_DATA-SDATA.

Third: Move E1MARAM back into IDOC-line

IDOC_DATA-SDATA = I_ZBAPI_STUD.

IDOC_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.

ENDCASE.

CURRENT_TABIX = SY-TABIX.

COUNTER-D_IND = COUNTER-D_IND + 1.

COUNTER-TRANC = COUNTER-TRANC + 2.

CASE IDOC_DATA-SEGNAM.

WHEN 'ZBAPI_STUD_SEG'.

Initialize data - per material

COUNTER-D_IND = 1.

FIRST_TRANC = COUNTER-TRANC.

interpret segment

ZBAPI_STUD_SEG = IDOC_DATA-SDATA.

MOVE-CORRESPONDING ZBAPI_STUD TO I_ZSTUD_UEB.

T_IDOC_ROLLNO-DOCNUM = IDOC_CONTRL-DOCNUM.

T_IDOC_ROLLNO-ROLLNO = I_ZSTUD_UEB-ROLLNO.

APPEND T_IDOC_ROLLNO.

ENDCASE.

if not ZBAPI_STUD_SEG is initial.

ZBAPI_STUD-MANDT = ZBAPI_STUD_SEG-MANDT.
ZBAPI_STUD-ROLLNO = ZBAPI_STUD_SEG-ROLLNO.
ZBAPI_STUD-FNAME = ZBAPI_STUD_SEG-FNAME.
ZBAPI_STUD-LNAME = ZBAPI_STUD_SEG-LNAME.

INSERT ZBAPI_STUD FROM ZBAPI_STUD_SEG.

COMMIT WORK.

ENDIF.

*-- ALE ditribution unity : update IDOC status "note03618

LOOP AT it_dsp_idocstat. "note036

LOOP AT IDOC_STATUS WHERE DOCNUM = it_dsp_idocstat. "note036

DELETE idoc_status INDEX sy-tabix. "note036

ENDLOOP. "note036

APPEND it_dsp_idocstat TO idoc_status. "note036

ENDLOOP. "note036

*--GENERATING THE IDOC STATUS

PERFORM HANDLE_ERROR_EXT " //br40

TABLES "

IDOC_CONTRL "

IDOC_STATUS "

RETURN_VARIABLES "

T_MERRDAT "

T_IDOC_TRANC "

T_IDOC_ROLLNO "JH/4.0C/KPr100004993

USING "

GENERAL_SUBRC "

NO_APPLICATION_LOG "

MASSSAVEINFOS "wk/40c

CHANGING "

WORKFLOW_RESULT. "

PERFORM HANDLE_ERROR

TABLES

IDOC_CONTRL

IDOC_STATUS

RETURN_VARIABLES

T_MERRDAT

T_IDOC_ROLLNO "JH/4.0C/KPr100004993

USING

APPLICATION_SUBRC

CHANGING

WORKFLOW_RESULT.

SORT T_IDOC_ROLLNO BY ROLLNO. "note 315124

React on general error

DATA: I_MERRDAT LIKE MERRDAT.

IF GENERAL_SUBRC <> 0.

I_MERRDAT-MSGTY = 'E'.

I_MERRDAT-MSGID = SY-MSGID.

I_MERRDAT-MSGNO = SY-MSGNO.

I_MERRDAT-MSGV1 = SY-MSGV1.

I_MERRDAT-MSGV2 = SY-MSGV2.

I_MERRDAT-MSGV3 = SY-MSGV3.

I_MERRDAT-MSGV4 = SY-MSGV4.

APPEND I_MERRDAT TO T_MERRDAT.

ENDIF.

LOOP AT T_MERRDAT INTO I_MERRDAT

WHERE MSGTY = 'S' "success

OR MSGTY = 'D' "dummy

OR MSGTY = 'I' "Information " //br011097 zu 3.1I

OR MSGTY = 'H' "dummy " 4.0

OR MSGTY = 'W'. "warning

DELETE T_MERRDAT.

ENDLOOP.

ENDFUNCTION.

*&----

*& Form handle_error_ext

*&----

FORM HANDLE_ERROR_EXT

TABLES

IDOC_CONTRL STRUCTURE EDIDC

IDOC_STATUS STRUCTURE BDIDOCSTAT

RETURN_VARIABLES STRUCTURE BDWFRETVAR

T_MERRDAT STRUCTURE MERRDAT

IDOC_TRANC STRUCTURE MATIDOCTRANC

JH/02.02.98/4.0C KPr100004993 (Anfang)

T_IDOC_ROLLNO STRUCTURE T_IDOC_ROLLNO

JH/02.02.98/4.0C KPr100004993 (Ende)

USING

GENERAL_SUBRC LIKE SY-SUBRC

NO_APPLICATION_LOG LIKE SY-DATAR

MASSSAVEINFOS LIKE MASSSAVINF

CHANGING

WORKFLOW_RESULT LIKE BDWF_PARAM-RESULT.

DATA FLAG_ERROR_HAPPENED.

DATA I_MERRDAT LIKE MERRDAT.

DATA IDOC_INDEX_2_SUBRC LIKE SY-SUBRC.

DATA AL_HANDLES TYPE BAL_T_LOGH. "//br99

SORT T_IDOC_ROLLNO BY ROLLNO. "note 315124

React on general error

IF GENERAL_SUBRC <> 0.

REFRESH T_MERRDAT.

i_merrdat-tranc = 0. " //br261197

READ TABLE IDOC_TRANC INDEX 1. " zu 40b

I_MERRDAT-TRANC = IDOC_TRANC-FIRST_TRANC_IDOC. "

I_MERRDAT-MSGTY = 'E'.

I_MERRDAT-MSGID = SY-MSGID.

I_MERRDAT-MSGNO = SY-MSGNO.

I_MERRDAT-MSGV1 = SY-MSGV1. I_MERRDAT-MSGV2 = SY-MSGV2.

I_MERRDAT-MSGV3 = SY-MSGV3. I_MERRDAT-MSGV4 = SY-MSGV4.

APPEND I_MERRDAT TO T_MERRDAT.

ENDIF.

DATA: C_TRUE,

C_FALSE VALUE 'X'.

If error happened ==> Rollback whole work....

LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY NA 'SDHWI'.

EXIT.

ENDLOOP.

IF SY-SUBRC = 0.

FLAG_ERROR_HAPPENED = C_TRUE.

ROLLBACK WORK.

ELSE.

FLAG_ERROR_HAPPENED = C_FALSE.

ENDIF.

----------------------------------------------------------------------
Set IDOC status
two cases:
single IDOC-processing: ==> error can be written in IDOC status
package processing ==> anononymous "package error" for all IDOCs
----------------------------------------------------------------------

READ TABLE IDOC_CONTRL INDEX 2.

IDOC_INDEX_2_SUBRC = SY-SUBRC.

IF SY-SUBRC = 0.

IF 1 = 2. "//br40

MESSAGE E051(B1). "

ENDIF. "

CLEAR I_MERRDAT.

I_MERRDAT-MSGID = 'B1'.

I_MERRDAT-MSGTY = 'E'.

I_MERRDAT-MSGNO = '051'.

ENDIF.

IF IDOC_INDEX_2_SUBRC NE 0 OR FLAG_ERROR_HAPPENED = C_FALSE.

Nur in diesen Fällen wird Application Log geschrieben
Delete all Successes and Dummy records from t_merrdat
DELETE t_merrdat WHERE msgty = 'S' "success " testweise
OR msgty = 'D'. "dummy "

LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY = 'D'. "

I_MERRDAT-MSGTY = 'S'. "

MODIFY T_MERRDAT FROM I_MERRDAT. "

ENDLOOP. "

ENDIF.

WORKFLOW_RESULT = 0.

LOOP AT IDOC_CONTRL.

Set IDOC status

CLEAR IDOC_STATUS.

IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.

IF FLAG_ERROR_HAPPENED = C_FALSE.

Application log

PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC

T_MERRDAT

IDOC_STATUS

USING IDOC_CONTRL

FLAG_ERROR_HAPPENED

NO_APPLICATION_LOG

MASSSAVEINFOS

AL_HANDLES.

idoc_status-status = '53'. "OK!
APPEND idoc_status.
JH/02.02.98/4.0C KPr100004993 (Anfang)
Fill Return variables

CLEAR RETURN_VARIABLES.

RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.

RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.

APPEND RETURN_VARIABLES.

Verknüpfungseintrag anlegen

READ TABLE T_IDOC_ROLLNO WITH KEY ROLLNO = IDOC_CONTRL-DOCNUM

BINARY SEARCH.

IF SY-SUBRC = 0.

RETURN_VARIABLES-DOC_NUMBER = T_IDOC_ROLLNO-ROLLNO.

RETURN_VARIABLES-WF_PARAM = 'Appl_Objects'.

APPEND RETURN_VARIABLES.

ENDIF.

JH/02.02.98/4.0C KPr100004993 (Ende)

ELSE.

IF IDOC_INDEX_2_SUBRC NE 0.

Application Log

PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC

T_MERRDAT

IDOC_STATUS

USING IDOC_CONTRL

FLAG_ERROR_HAPPENED

NO_APPLICATION_LOG

MASSSAVEINFOS

AL_HANDLES.

ELSE.

IDOC_STATUS-MSGID = I_MERRDAT-MSGID.

IDOC_STATUS-MSGTY = I_MERRDAT-MSGTY.

IDOC_STATUS-MSGNO = I_MERRDAT-MSGNO.

IDOC_STATUS-MSGV1 = I_MERRDAT-MSGV1.

IDOC_STATUS-MSGV2 = I_MERRDAT-MSGV2.

IDOC_STATUS-MSGV3 = I_MERRDAT-MSGV3.

IDOC_STATUS-MSGV4 = I_MERRDAT-MSGV4.

IDOC_STATUS-STATUS = '51'. "ERROR!

APPEND IDOC_STATUS.

ENDIF.

Fill Return variables

CLEAR RETURN_VARIABLES.

RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.

return_variables-wf_param = c_wf_par_processed_idocs.

RETURN_VARIABLES-WF_PARAM = 'Error_IDOCs'.

APPEND RETURN_VARIABLES.

WORKFLOW_RESULT = 99999.

ENDIF.

APPEND idoc_status.

ENDLOOP.

IF NO_APPLICATION_LOG IS INITIAL.

CALL FUNCTION 'BAL_DB_SAVE' "//br99

EXPORTING

I_IN_UPDATE_TASK = ' '

I_SAVE_ALL = ' '

I_T_LOG_HANDLE = AL_HANDLES.

EXCEPTIONS
LOG_NOT_FOUND = 1
SAVE_NOT_ALLOWED = 2
NUMBERING_ERROR = 3
OTHERS = 4.

CALL FUNCTION 'BAL_GLB_MEMORY_REFRESH' "//br99

EXPORTING

I_AUTHORIZATION =

I_REFRESH_ALL = ' '

I_T_LOGS_TO_BE_REFRESHED = AL_HANDLES.

EXCEPTIONS
NOT_AUTHORIZED = 1
OTHERS = 2

ENDIF.

ENDFORM. " handle_error

Save, check and activate

11. Assigning the Inbound Function Module to Basic Type & Message Type

o Go to T. Code WE57

o Click on change, continue, continue and New Entries Button

o Enter the Module as IDOC_INPUT_ZBAPI_STUD_MAS

o Type as “F”

o Basic Type as ZBAPI_STUD_IDOC

o Message Type as ZBAPI_STUD_MAS.

o Direction as 2

o Save and back

Now Login in 810 client

12. Assigning the Inbound Function Module in ALE Table

o Go to T. Code BD51

o Click on continue, New Entries button

o Give the Inbound Function Module IDOC_INPUT_ZBAPI_STUD_MAS

o Give Input t. as 0 (zero)

o Save and back

13. Creating Process Code

o Go to T. Code WE42

o Click on Change, New Entries Button

o Give Process Code name as ZSTUD, give Description & Save

o Select Processing with ALE Services Radio button

o Select Processing by Function Module Radio button

o Click the ALE Table (arrow Icon) in Identification

o Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS

o Give maximum number of repeats 0

o Save and back, back

o Select the process code from the list & click on Logical Messages Icon

o Give the Message Type as ZBAPI_STUD_MAS

o Save & Back, Save & Back, Save & Back

14. Changing the Customer Distribution model in Receiving system

o Go to T. Code BD64

o Click on change and Create model view button

o Select the model view & click on Environment -> Generate Partner Profiles

o Select Transfer IDOC Immediately and Trigger Immediately radio buttons

o Click on Execute

o You should get a list in green color which means it executed successfully.

15. Assigning the Process Code to Message Type in Receiving System

o Go to T. Code WE20

o Expand Partner Type LS

o Select the Partner Profile STUD_S

o Double click on Message Type ZBAPI_STUD_MAS in Inbound parmtrs.

o Give the Process Code as ZSTUD

o Click on Trigger Immediately Radio button

o Save & Back

16. Creating the Selection Program (Outbound Program)

• Login in client 800.

• Go to T. Code SE38

• Create a Report Program as ZSTUD_SEND with the following code

REPORT ZSTUD_SEND

NO STANDARD PAGE HEADING.

TABLES: ZBAPI_STUD.

DATA: IT_STUD LIKE ZBAPI_STUD OCCURS 0 WITH HEADER LINE.

SELECTION-SCREEN:BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-H01.

SELECT-OPTIONS: S_ROLLNO FOR ZBAPI_STUD-ROLLNO.

SELECTION-SCREEN SKIP.

SELECTION-SCREEN:BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-H02.

PARAMETERS: P_MESTYP LIKE EDIDC-MESTYP,

P_RCVPRN LIKE TBDLST-LOGSYS.

SELECTION-SCREEN:END OF BLOCK B2.

SELECTION-SCREEN:END OF BLOCK B1.

START-OF-SELECTION.

PERFORM CREATE_STUDENT.

PERFORM CREATE_IDOC.

*&----

*& Form CREATE_STUDENT

*&----

sending student

*----

FORM CREATE_STUDENT.

SELECT * FROM ZBAPI_STUD

INTO TABLE IT_STUD

WHERE ROLLNO IN S_ROLLNO.

ENDFORM. " CREATE_STUDENT

*&----

*& Form CREATE_IDOC

*&----

IDOC Creation

*----

FORM CREATE_IDOC.

DATA : IMAS_DATA LIKE EDIDD OCCURS 10 WITH HEADER LINE,

IMAS_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE,

ICOM_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE.

IMAS_CON-RCVPRT = 'LS'.

IMAS_CON-RCVPRN = P_RCVPRN.

IMAS_CON-IDOCTP = 'ZBAPI_STUD_IDOC'.

IMAS_CON-MESTYP = P_MESTYP.

IMAS_CON-DIRECT = 1.

APPEND IMAS_CON.

LOOP AT IT_STUD.

IMAS_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.

IMAS_DATA-SDATA = IT_STUD.

APPEND IMAS_DATA.

ENDLOOP.

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'

EXPORTING

MASTER_IDOC_CONTROL = IMAS_CON

OBJ_TYPE = ''
CHNUM = ''

TABLES

COMMUNICATION_IDOC_CONTROL = ICOM_CON

MASTER_IDOC_DATA = IMAS_DATA

EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5

IF SY-SUBRC <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

COMMIT WORK.

LOOP AT ICOM_CON.

WRITE 😕 'IDOC: ', ICOM_CON-DOCNUM, 'CREATED SUCCESSFULLY'.

ENDLOOP.

ENDFORM. " CREATE_IDOC

17. Transferring the student records from 800 to 810 client

• Execute Report Program ZSTUD_SEND

• Give the Range of Roll Nos to Transfer

• Give Message Type as ZBAPI_STUD_MAS

• Give Receiver Logical system as STUD_R

• Execute

• You should get the IDOC Number

• Take the IDOC Number and go to T. Code WE05 & Execute

• In Outbox you can see the IDOC Status

• Select the status record in left side window

• Double click on the Status record in right side window

• You can see the Control Record, Data Record and Status Records for that IDOC

• If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully.

Now Login in 810 client

• Go to T. Code WE05 & Execute

• You can see the status record in left side window

• If the status no is 53 and color is green, it means the IDOC is Posted to Application successfully.

• You can see the Log Information by double clicking on the status record in right side window.

• Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC

• Now go to T. Code SE16

• Give the table name ZBAPI_STUD & press F7

• See the contents of the table

• The table is updated with the students records transferred from 800 client with our selection program.

Reward if useful

Regards

Jagadeesh.G