ALE/IDOC

[Former Member]

HI

can any one give me step by step how to create ale/idoc and how to handle errors and what are the function modules we use for all the message types.

max reward if they give me details. i don't want any links.

plz explain me

alka

[Former Member]

HI

can any one give me step by step how to create ale/idoc and how to handle errors and what are the function modules we use for all the message types.

max reward if they give me details. i don't want any links.

plz explain me

alka

[Former Member]

Hi,

Go thru thesee.......

ALE---IDOC Creation Steps

01 Error --> Idoc Added

30 Error --> Idoc ready for dispatch(ALE Service)

then goto SE38 --> Execute the Program RBDMIDOC

29 Error --> ALE Service Layer

then goto SE38 --> Execute the Program RSEOUT00

03 Error --> Data Passed to Port ok

then goto SE38 --> Execute the Program RBDMOIND

12 Error --> Dispatch ok

Inbound Status Codes

50 Error --> It will go for ALE Service Layer

56 Error --> Idoc with Errors added

51 Error --> Application Document not posted

65 Error --> Error in ALE Service Layer

for 51 or 56 Errors do the following steps

goto WE19 > give the IDOC Number and Execute>

Press on Inbound function Module

for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error

ALE IDOC

Sending System(Outbound ALE Process)

Tcode SALE ? for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 ? Create Model View

Tcode BD82 ? Generate partner Profiles & Create Ports

Tcode BD64 ? Distribute the Model view

Message Type MATMAS

Tcode BD10 ? Send Material Data

Tcode WE05 ? Idoc List for watching any Errors

Receiving System(Inbound ALE )

Tcode SALE ? for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 ? Check for Model view whether it has distributed or not

Tcode BD82 -- Generate partner Profiles & Create Ports

Tcode BD11 Getting Material Data

Tcode WE05 ? Idoc List for inbound status codes

ALE IDOC Steps

Sending System(Outbound ALE Process)

Tcode SALE ?3 for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 !V Create Model View

Tcode BD82 !V Generate partner Profiles & Create Ports

Tcode BD64 !V Distribute the Model view

This is Receiving system Settings

Receiving System(Inbound ALE )

Tcode SALE ?3 for

a) Define Logical System

b) Assign Client to Logical System

Tcode SM59-RFC Destination

Tcode BD64 !V Check for Model view whether it has distributed or not

Tcode BD82 -- Generate partner Profiles & Create Ports

Tcode BD11 Getting Material Data

Tcode WE05 !V Idoc List for inbound status codes

Message Type MATMAS

Tcode BD10 !V Send Material Data

Tcode WE05 !V Idoc List for watching any Errors

1)a Goto Tcode SALE

Click on Sending & Receiving Systems-->Select Logical Systems

Here Define Logical Systems---> Click on Execute Button

go for new entries

1) System Name : ERP000

Description : Sending System

2) System Name : ERP800

Description : Receiving System

press Enter & Save

it will ask Request

if you want new request create new Request orpress continue for transfering the objects

B) goto Tcode SALE

Select Assign Client to Logical Systems-->Execute

000--> Double click on this

Give the following Information

Client : ERP 000

City :

Logical System

Currency

Client role

Save this Data

Step 2) For RFC Creation

Goto Tcode SM59-->Select R/3 Connects

Click on Create Button

RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles

give the information for required fields

RFC Destination : ERP800

Connection type: 3

Description

Target Host : ERP000

System No:000

lan : EN

Client : 800

User : Login User Name

Password:

save this & Test it & RemortLogin

3)

Goto Tcode BD64 -- click on Change mode button

click on create moduleview

short text : xxxxxxxxxxxxxx

Technical Neme : MODEL_ALV

save this & Press ok

select your just created modelview Name :'MODEL_ALV'.

goto add message type

Model Name : MODEL_ALV

sender : ERP000

Receiver : ERP800

Message type :MATMAS

save & Press Enter

4) Goto Tcode BD82

Give Model View : MODEL_ALV

Partner system : ERP800

execute this by press F8 Button

it will gives you sending system port No :A000000015(Like)

5) Goto Tcode BD64

seelct the modelview

goto >edit>modelview-->distribute

press ok & Press enter

6)goto Tcode : BD10 for Material sending

Material : mat_001

Message Type : MATMAS

Logical System : ERP800

and Execute

7)goto Tcode : BD11 for Material Receiving

Material : mat_001

Message Type : MATMAS

and Execute --> 1 request idoc created for message type Matmas

press enter

Here Master Idoc set for Messge type MATMAS-->press Enter

1 Communication Idoc generated for Message Type

Regards,

Omkar.

[paruchuri_nagesh]

hi

CATSDB CUSTOM IDOC TRANSFERMATION BETWEEN 2 DIFFERENT APPLICATION SERVERS

For this scenario Client 800 of application server SAPADM is the Sender and client 800 of application server SAP-REMOTE is the Receiver

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 CATSSENDER, ECC Logical Systems

o Save and come back

o Assign the CATSSENDER Logical System to client 800 of Application Server SAPADMAssign the ECC Logical System to client 800 of Application Server SAP-REMOTE

2. Creating the RFCs

o Go to T. Code SM59

o Expand R/3 Connections

o Enter RFC Name as CATSSENDER

o Connection Type as 3

o Language as EN

o Client as 800

o User as SAPUSER

o Password as YESV13

o Target host as SAPADM

o Click on Remote logon button to test the RFC

o Enter RFC Name as ECC

o Connection Type as 3

o Language as EN

o Client as 800

o User as SAPUSER

o Password as YESV123

o Target host as SAPADM

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 ZCATSTIME and description

o Save and back

4. Creating the Segment

o Go to T. Code WE31

o Give segment name as ZSEGMENTTIME

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 ZTIMEIDOC

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 backo 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 CATSSENDER

o Select the model and click on Add Message Type Button

o Give the Sender as CATSSENDER,

o Receiver as ECC,

o Message Type as ZCATSTIME

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 continueo

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 ECC (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 ECC

o Double click on Message Type ZCATSTIME in Outbound parmtrs.

o Check Receiver Port is assigned correctlyo

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 ZCATSTIME

o Give Basic Type as ZTIMEIDOC

o Release as 4.6C

o Save and back10. Creating Inbound Function Module (Posting Program)

o Go to T. Code SE37

o Create a function Module ZCATSDB_TIMESHEET_SURESH

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

o Import Parameters

P_WORKDATE LIKE CATSDB-WORKDATE

P_COUNTER LIKE CATSDB-COUNTER

P_LSTAR LIKE CATSDB-LSTAR

o Export Parameters

o Tables

S_PERNR LIKE ZCATSPERNR

[PERNR is select option parameters in ZCUSTOMIDOC report program so that it should be passed to function module ZCATSDB_TIMESHEET_SURESH in tables section. And also in tables section we used ZCATSPERNR, which is a global structure, which contains four fields as

Ø SIGN

Ø OPTION

Ø LOW

Ø HIGH]

o Exceptions

o Source Code

FUNCTION zcatsdb_timesheet_suresh.

*"----

-

---

""Local interface:

*" IMPORTING

*" VALUE(P_WORKDATE) LIKE CATSDB-WORKDATE

*" VALUE(P_COUNTER) LIKE CATSDB-COUNTER

*" VALUE(P_LSTAR) LIKE CATSDB-LSTAR

*" TABLES

*" S_PERNR STRUCTURE ZCATSPERNR

*"----

-

---

TABLES: catsdb, edidc, edidd. " using structures of catsdb, edidc, edidd

CONSTANTS: c_doctyp TYPE edidc-idoctp VALUE 'ZTIMEIDOC', " idoc type

c_segnam TYPE edidd-segnam VALUE 'ZSEGMENTTIME', "segment type

c_mestyp TYPE edidc-mestyp VALUE 'ZCATSTIME'. " message type

*001 comment begin

• creating internal tables with out header lines for catsdb, edidc, edidd and also

- work areas

*001 comment end

DATA: it_edidc TYPE edidc OCCURS 0, " control internal table with out header line

it_edidd TYPE edidd OCCURS 0, " data internal table with out header line

wa_catsdb TYPE it_catsdb1, " work area for it_catsdb internal table

wa_edidc TYPE edidc, " work area for it_edidc internal table

wa_edidd TYPE edidd, " work area for it_edidd internal table

wa_zsegmenttime TYPE zsegmenttime, " work area for zsegment internal table

v_occmax TYPE idocsyn-occmax,

v_nbseg TYPE i.

CLEAR wa_catsdb. " clears work area of catsdb

CLEAR wa_edidc. " clears edidc work area

*002 comment begin

• Save the message type and the basic IDoc type in the control segment.

*002 comment end

MOVE c_mestyp TO wa_edidc-mestyp. " assigning custom message type to edidc workarea

MOVE c_doctyp TO wa_edidc-idoctp. " assigning custom idoc type to edidc workarea

*003 comment begin

• Retrieve the maximum number of segments in the basic IDoc type.

*003 comment end

SELECT MIN( occmax ) FROM idocsyn INTO v_occmax WHERE idoctyp EQ c_doctyp AND segtyp EQ c_segnam.

*004 comment begin

• Save the whole CATSDB table content in the IT_ZCATSDB internal table.

*004 comment end

SELECT pernr workdate lstar counter FROM catsdb INTO CORRESPONDING FIELDS OF TABLE it_catsdb WHERE pernr IN s_pernr AND workdate EQ p_workdate.

*005 comment begin

• Create a data segment for each line of IT_ZCATSDB.

*005 comment end

IF sy-subrc EQ 0.

LOOP AT it_catsdb INTO wa_catsdb WHERE pernr IN s_pernr.

MOVE-CORRESPONDING wa_catsdb TO wa_zsegmenttime.

CLEAR wa_edidd.

MOVE c_segnam TO wa_edidd-segnam.

MOVE wa_zsegmenttime TO wa_edidd-sdata.

APPEND wa_edidd TO it_edidd.

CLEAR wa_catsdb.

CLEAR wa_zsegmenttime.

ENDLOOP.

ELSE.

MESSAGE 'NO DATA FOUND FOR GIVEN SELECTION' TYPE 'I'.

ENDIF.

*006 comment begin

• Count the number of data segments.

*006 comment end

DESCRIBE TABLE it_edidd LINES v_nbseg.

*007 comment begin

• If the number of data segments exceeds the maximum allowed number,then display an error message.

*007 comment end

IF v_nbseg GT v_occmax.

MESSAGE 'IDOC ERROR Message' TYPE 'E000'.

ENDIF.

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' " for creating an catsdb idoc

EXPORTING

master_idoc_control = wa_edidc

• OBJ_TYPE = ''

• CHNUM = ''

TABLES

communication_idoc_control = it_edidc

master_idoc_data = it_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.

• ENDIF.

ENDFUNCTION.

Save, check and activate

111. 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 ZCATSDB_TIMESHEET_SURESH Type as "F"

o Basic Type as ZTIMEIDOC

o Message Type as ZCATSTIME

o Direction as 2

o Save and back

Now Login in 800 client of Application Server SAP-REMOTE

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 ZCATSDB_TIMESHEET_SURESH

o Give Input t. as 0 (zero)

o Save and back13. Creating Process Code

o Go to T. Code WE42

o Click on Change, New Entries Button

o Give Process Code name as ZCATSDB, 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 ZCATSTIME

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 Enter the short text and Technical name as CATSECC

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

o Select Transfer IDOC Immediately and Trigger Immediately radio buttonso Click on Execute 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 CATSSENDER

o Double click on Message Type ZCATSTIME in Inbound parmtrs.

o Give the Process Code as ZCATSDB

o Click on Trigger Immediately Radio button

o Save & Back

Save & Back

16. Creating the Selection Program (Outbound Program)

- Login in client 800.

- Go to T. Code SE38

- Create a Report Program as ZCUSTOMIDOC with the following code

REPORT ZCUSTOMIDOC

NO STANDARD PAGE HEADING.

TABLES:catsdb. " using structure of cats db table

*000 comment begin

• this selection screen contains one select option and one parameter

*000 comment end

SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.

SELECT-OPTIONS pernr FOR catsdb-pernr.

PARAMETER: workdate LIKE catsdb-workdate,

LSTAR like catsdb-LSTAR,

COUNTER like catsdb-counter.

SELECTION-SCREEN: END OF BLOCK b1 .

DATA: wa_val TYPE i.

wa_val = pernr-high - pernr-low.

*001 comment begin

• calling custom function module

*001 comment end

CALL FUNCTION 'ZCATSDB_TIMESHEET_SURESH'

EXPORTING

p_workdate = workdate " passing workdate parameter

p_LSTAR = LSTAR

p_counter = counter

TABLES

s_pernr = pernr. " passing pernr select option

IF sy-subrc EQ 0.

MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' pernr-low ' AND ' pernr-high .

• MESSAGE i000(zaluri) WITH 'IDOCS CREATED FOR EMPLOYEES BETWEEN' PERNR-LOW 'TO' PERNR-HIGH.

• gives information message if idocs are created for given employees

ELSE.

MESSAGE e000(zaluri) WITH 'NO IDOCS CREATED FOR EMPLOYEES' pernr-low 'TO' pernr-high. " gives error message

" if idoc is not created

17. Transferring the CATSDB records from sender Application Server SAPADM to receiver Application Server SAP-REMOTE

- Execute Report Program ZCUSTOMIDOC

- Give the Range of PERSONNEL NO'S, Date, Activity Type, Counter to Transfer

- Give Message Type as ZCATSTIME

- Give Receiver Logical system as ECC

- 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

18. SENDING IDOCS FROM APPLICATION SERVER SAPADM

TO APPLICATION SERVER SAP-REMOTE USING WEDI

- Go to T. Code WEDI & execute or T. Code WE19

- Give idoc number it is generated recently

- Continue & double click on segment to view data in segment

- Click on EDIDC to give port, partner no, message type, partner

type of receiver. [For sender no need to give any port no leave it as

blank]

- Click on Standard Outbound Processing button and click continue

- You will get a message as idocs successfully transferred

Now Login in Receiver 800 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 CATSDB & press F7

- See the contents of the table

- The table is updated with the catsdb records transferred from 800 client with our selection program.

Reward for useful inputs

Regards

Nagesh.Paruchuri

[Former Member]

Hi Alka,

This document is created by me.

In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients.

For our purpose we have two clients namely Client 100 and Client 200.

System name is satyam03

1. SETUP LOGICAL SYSTEM: To do this follow the following steps

Tools -> Business Engg ->Customizing.

Click Enterprise IMG button.

Cross Applications -> Distribution (ALE) -> Basic Configuration.

Set up ‘Logical System -> Maintain Logical System.

Click New Entries Button (E.g. WalMart100 receivin system)

(Walmart200 sending system)

Enter two logical system names and their description.

Save

Comeback to IMG setting screen.

2. Now you have to allocate the created logical systems to respective clients.

WalMart100 assign to client 100

WalMart200 assign to client 200

To do this, do the following.

Click Allocate logical system to the client.

Ignore the message that comes up on the screen.

Select client 100

Click details button on the toolbar icon or press F2.

In the logical system box, enter WalMart100.

Click on the save Icon

Click the back button.

Now select client 200.

Click details icon or press f2.

In logical Systems box, enter WalMart200.

Save

Back.

Come back to the IMG settings screen.

Now define the RFC Destination. Do the following.

Click Cross Application -> Distribution (ALE).

Click on communication.

Execute RFC Destination.

Click R/3 connections. (Expand it).

Put cursor on R/3 connection.

Click the create button.

Enter WalMart100 in RFC destination box.

Connection type 3

Give a description for the RFC destination.

Language E.

User: User11 (This is the logon for dist.)

Client : 100

Password: Enter the client logon password.

Save.

In target machine box enter cysap03 (This is the system

name)

Save.

Click on test connection and remote logon to verify.

Click on Back button.

Position your cursor on R/3 connection.

Click on create to do the above process for WalMart200

logical system for client 200.

Click on the back button.

Click on the distribution customer model.

Execute Maintain customer distribution model directly for

creating the customer model.

Put your cursor in Maintain customer distribution model directly box.

Click Choose.

Specify the source logical system (WalMart200) and give a

customer model name. (ModelMar10)

Click on create icon.

Select the target logical system (WalMart100) from the list.

Click on create message type.

In the resulting screen, in log message type enter MATMAS.

Click on transfer.

Save.

Back to IMG setting screen.

Click distribute customer model.

Select generate partner profiles and click choose.

In customer model box enter the model name that you

created (Modelmar10)

Click execute button.

You should get a screen mentioning successful creation of

customer model in green color.

Click back button

Select distribute customer model and click choose.

In the resulting screen enter customer model (Modelmar10)

Receiving logical system (WalMart200)

Click execute.

You get messages :

copy with RFC destination WalMart100

model data sent successfully.

Click back.

Now execute R/3 and login to client 100

Execute transaction SPRO.

Click Cross applications -> Distribution ALE

Communications -> generate partner profiles.

Enter the customer Model (Modelmar10)

Execute

Base unit of measure as PC

In the description area language (E) and material description.

Click Save.

Come back to the first screen of the session

Logistics -> Central Functions -> distribution

Master Data -> Material -> Send.

Enter the material name. (Mat1000)

Message type (Matmas)

Logical System (WalMart100- target logical system)

Click Execute.

Switch to Client 100 session to verify.

Logistics -> Material Management -> Material Master.

Material -> Display -> Display Current.

Give the name of the material (Mat1000)

Click select views button.

You should get select views screen for the given

material.

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

in ale you are new so tray it first.if ur not understand plz send a mail [email protected]/[email protected]

if it is help full for u give max reward. in ale and idoc u need to know lot of things.that things i can update u.for u start from here.

[Former Member]

Hi alka,

this is 2nd way.

Exercise 1: Start-Up

Set-up a partner profile to send purchase orders to vendor IDOC-LI-nn. The message control settings are EF / NEU / LF, the logical message is ORDLGT with process code ME21-BC621-nn.

This set-up was already done!

Create a purchase order via transaction ME21, and check with one of the monitor programs that the IDoc exists (note the IDoc‘s number).

Set-up a partner profile to receive customer orders from customer IDOC-KU-nn. The logical message is ORDLGT with process code VA01-BC621-nn.

This set-up was already done!

With the test tool, transaction WE19, flip-around the IDoc created in step 2. The IDoc will serve as the customer order. Because you have changed „sites“, you have to change the control record, so it will match with your set-up in step 3.

Due to those exercises set-up, the inbound processing will fail, and the IDoc reaches status „51“: Document type NB unknown.

Exercise 2: Extend Inbound (Cross Reference)

You plan to overcome the error from exercise 1 by implementing a cross-reference from purchasing document type NB to sales document type TA. Hence you implement a customer-exit for the inbound processing in project management.

Create a project

Select SAP enhancements; search with development class IDOCTRAINING

Implement the exit in enhancement components

Activate your project

Test your exit by reprocessing the inbound IDoc from exercise 1 with the test tool, transaction WE19.

The IDoc now reaches status „53“: Sales document posted.

Exercise 3: Extend Outbound (Fill Field)

The IDoc type ORDLGT01 has the field NAME (ekko-ernam in purchasing) in segment E1HEAD, anyway the field is not populated by outbound processing. Hence you implement a customer-exit for the outbound processing in project management.

Create a project (With exercise 2 the project already exists!)

Select SAP enhancements; search with development class IDOCTRAINING (With exercise 2 the enhancement is already selected!)

Implement the exit in enhancement components

Activate your project

Test your exit by creating a new purchase order via transaction ME21, and check with one of the monitor programs that the IDoc exists, and the field NAME is populated.

Exercise 4: Extend IDoc Type

You are asked to transmit „Terms of Delivery“ with your orders documents. Neither IDoc type ORDLGT01 nor one of its segments has fields for „Terms of Delivery“.

Extend the IDoc type ORDLGT01 with a 3-digit field for the code and a 28-digit field for the description of „Terms of Delivery“ (dataelements INCO1 and INCO2).

Create a customer segment Z1INCOnn

Create an extension ZEXTENnn by extending IDoc type ORDLGT01

Assign logical message ORDLGT to basis type ORDLGT01 and extension ZEXTENnn.

The processing of that extension will be implemented in the following exercises number 5 and 6.

Exercise 5: Extend Outbound (Fill Customer Segment)

You are asked to send „Terms of Delivery“ with your orders documents. The IDoc type ORDLGT01 was already extended in exercise 4. Now you have to implement the outbound processing.

Create a project (With exercise 2 the project already exists!)

Select SAP enhancements; search with development class IDOCTRAINING (With exercise 2 the enhancement is already selected!)

Implement the exit in enhancement components

Activate your project

Because of the IDoc type is maintained in the outbound partner profile, you have to adjust the partner profile for vendor IDOC-LI-nn.

Test your exit by creating a new purchase order via transaction ME21, and check with one of the monitor programs that the IDoc exists, and the segment Z1INCOnn was populated (note the IDoc‘s number).

Exercise 6: Extend Inbound (Process Customer Segment)

You are asked to receive „Terms of Delivery“ with your orders documents. The IDoc type ORDLGT01 was already extended in exercise 4. Now you have to implement the inbound processing.

Create a project (With exercise 2 the project already exists!)

Select SAP enhancements; search with development class IDOCTRAINING (With exercise 2 the enhancement is already selected!)

Implement the exit in enhancement components

Activate your project

Test your exit by reprocessing the inbound IDoc from exercise 5 with the test tool, transaction WE19.

With exercise 2 the IDoc reached status „53“: Sales document posted. With the changes of this exercise also the „Terms of Delivery“ in the sales document are updated.

[Former Member]

Hi alka,

ALE & Idoc’s T-Code

T-Code Descriptions Of T-Code

SALE Display IMG

Administration

WE02, WE05 DISPLAY IDOC’S

WE20 PARTNER PROFILE

WE21 PORTS IN IDOC PROCESSING

SM59 CREATE RFC Destinations

WE46 WORKFLOW CUSTOMIZING

Fiend Idoc’s

WE06 ACTIVE IDOC MONITORING

WE07 IDOC STATISTICS

WE09 IDOC SEARCH FOR BUSINESS CONTENTS

(DATABASE)

WE10 IDOC SEARCH FOR BUSINESS CONTENTS

(ARCHIVE)

Display Status

SM58 DISPLAY TRANSACTIONAL RFC

WE08 DISPLAY VIEW “FILE STATUS”

WECP DISPLAY VIEW “RECEIVED IDOC FROM R/2”

Test

WE19 TEST TOOL FOR IDOC PROCESSING

WE15 SELECTION PROGRAM ISSUING OUTPUT

WE14 PROCESS ALL SELECTED IDOC (EDI)

WE18 GENERATE TEST STATUS FILE FOR

OUTBOUND IDOC

WE17 PROCESS STATUS FILE (TRIGGER STATUS

PROCESSING)

WE12 INBOUND PROCG OF MODIFIED OUTBOND FILE

WE16 INBOUND PROCG OF ORIG.INBOUND FILE

Documentation

WE60 DOCUMENTAION

WE64 PROCESS CODE IN IDOC OUTBOUND AND

IDOC INBOUND

Development

WE31 DEVELOPMENT SEGMENT

WE30 DEVELOP IDOC TYPES

WE81 DEVELOP MESSAGE TYPE

WE82 OUTPUT TYPE AND ASSIGNMENT TO IDOC

TYPE

WE41 OUTBOUND PROCESS CODE

BD59 MAINTAIN OBJECT TYPE FOR MESSAGE TYPE

BD64 MAINTAIN DISTRIBUTION CUSTOMER MODEL

VIEW

BD71 DISTRIBUTION CUSTOMER MODEL VIEW

BD69 ASSIGNMENT OF MESSAGE TYPE TO IDOC

TYPE

Inbound Processing Settings

BD51 DEFINE FUNCTION MODULE (INBOUND

PROCESS)

WE57 LINK MESSAGE TYPE TO FUNCTION MODULE

WE42 INBOUND PROCESS CODE

Control Status

WE47 DISPLAY & CHANGE VIEW “STATUS

MAINTENANCE”

WELI DISPLAY & CHANGE VIEW “TRAFFIC LIGHT

ALLOCATION FOR STATUS GROUP”

WE43 DISPLAY & CHANGE VIEW OF STATUS

RECORD

Partner Profile

WE24 PROPOSAL FOR OUTBOUND PARTNER

PROFILE

WE27 PROPOSAL FOR INBOUND PARTNER PROFILE

WE44 DISPLAY/CHANGE VIEW PARTNER TYPES

WE55 DISPLAY/CHANGE VIEW “IDOC: FUNCTION

MODULE FOR FILE NAME”

WE34 CHANGE/DISPLAY VIEW “TABLE OF STYLE Ids

WITH THE OBJECT TO BE LOADED”

WE32 DEVELOPMENT IDOC VIEW

Please give max reward thanks

[Former Member]

Hi alka,

There is lot of function modules depends upon your scenario some times u have to create FM. If you create idoc manually u need to create each and every thing.1st u need to study some document then only u can understand what I am saying. i will send some document(ALE Project) today night ok.

give max reward.