IDOC procedure

Former Member — Wed, 09 Apr 2008 05:03:40 GMT

Hi Experts

I want to transfer the material master from 391 client to 392 client.

How to establish the IDOC, can anyone explain me the step by step procedure.

Regards

Rajaram

Re: IDOC procedure

P507709 — Wed, 09 Apr 2008 05:13:50 GMT

Hi,

In order t0 process u r IDOc u have to do following

1) create RFc dest sm59

2)create logical system

3)assign u r clnt to logical system

4) create ports we20

5) create partner profile we21.

6)assign message type

7)assign u r business procedure for u r clnt

these u have to do for both clnts. For furthur if u want inf i will give brief

Regards

Durrgaprasad

Re: IDOC procedure

Former Member — Wed, 09 Apr 2008 05:18:59 GMT

HI,

Use This Steps

II. Master Data Transactions:

In SAPLID Server :

1. In the SALE transaction,

- Application Link Enabling (ALE) --> Sending and Receiving Systems --> Logical Sysems --> Define Logical Systems

- Click on 'New Entries'

- Enter 'Logical System' & 'Name'.

SAPLID Logical System for the server SAPLID

SAPLER Logical System for the server SAPLER

- Save it.

- Application Link Enabling (ALE) --> Sending and Receiving Systems --> Logical Sysems --> Assign Client to Logical System.

- Client : 800 Sending system

City : Hyderabad

Logical System : SAPLID

Std Currency : INR

client role : Demo

- Application Link Enabling (ALE) --> Sending and Receiving Systems --> Systems in Network --> Define Target Systems

for RFC calls.

- Select 'R/3 Connections' and click on 'Create' icon.

- RFC Destination : SAPLER

Connection type : 3

Descripiton : RFC for Destination Server SAPLER

Target host : SAPLER

System Number : 00

- Logon/Security

Language : EN

Client : 800

User : USER6

Password : RGSHYD

- Click on 'Test Connection'.

- Click on 'Remorte Logon'.

2. WE 81 Message type config (DEBMAS - Customer Master)

3. WE 30 Idoc type (DEBMAS06 - Customer Master data distribution)

4. WE 82 - Adding Message type to Idoc type.

DEBMAS ---> DEBMAS06

5. WE20 Partner Profile

Partner No : SAPLER

Par.Type : LS

Type : US

Agent : USER6

OUtbound Parameters :

Message type : DEBMAS

Receiver Port : Zbkpfport

Transfer Idoc Immediately

Basic type : DEBMAS06

6. BD64 MOdel View

- Select 'model view' and click on Create Model View.

- Technical Name : CUSTMODEL

- Place the cursor on 'CUSTMODEL' and click on 'Add message type'.

- Model View : CUSTMODEL

- Sender : SAPLID

- Receiver : SAPLER

- Message type : DEBMAS

- Save it

- Environment --> Generate Partner Profile

- Edit --> Modelview --> Distribute

7. XD01 Create Customer Master

- Create Customer Number : 0000000001

8. BD12 Sending Customer Data

- Customer : 0000000001

- OUtput type : DEBMAS

- Logical System : SAPLER

- Execute it

9. WE02 Idoc List

- Direction : 1

- Logical Message : DEBMAS

- Execute it

In SAPLER Server:

1. In the SALE transaction,

- Application Link Enabling (ALE) --> Sending and Receiving Systems --> Logical Sysems --> Define Logical Systems

- Click on 'New Entries'

- Enter 'Logical System' & 'Name'.

SAPLER Logical System for the server SAPLER

SAPLID Logical System for the server SAPLID

- Save it.

- Application Link Enabling (ALE) --> Sending and Receiving Systems --> Logical Sysems --> Assign Client to Logical System.

- Client : 800 Sending system

City : DELHI

Logical System : SAPLER

Std Currency : DEM

client role : Demo

- Application Link Enabling (ALE) --> Sending and Receiving Systems --> Systems in Network --> Define Target Systems

for RFC calls.

- Select 'R/3 Connections' and click on 'Create' icon.

- RFC Destination : SAPLID

Connection type : 3

Descripiton : RFC for Destination Server SAPLID

Target host : SAPLID

System Number : 00

- Logon/Security

Language : EN

Client : 800

User : USER6

Password : RGSHYD

- Click on 'Test Connection'.

- Click on 'Remorte Logon'.

2. WE42 Inbound Process Code

- DEBM : Process Code for DEBMAS

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

- Change Mode

- Click on New Entries

- Process code : ZDEBM

- Description : Process code for DEBMAS

- Choose "Processing by function module"

- Save it

- Function Module : IDOC_INPUT_DEBITOR

- Maximum number of repeat : 0

- IDOC Packet :

- Object type : IDPKDEBMAS

- End event : MASSINPUTFINISHED

- IDoc :

- Object type : IDOCDEBMAS

- Start event : INPUTERROROCCURRED

- End event : INPUTFINISHED

- Application object :

- Object type : kna1

- Save it

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

- CRE1 : Process Code for CREMAS

- MATM : Proces COde for Material

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

3. BD51 Characteristics of Inbound FUnction Module

- Function Module : IDOC_INPUT_DEBITOR

- Input : 1 (Individual Input)

- Save it

4. WE57 Assignment of Function Module to Log.Message and IDOC Type

- FM name : IDOC_INPUT_DEBITOR

- Type : F

- Basic Type : DEBMAS06

- Message tyep : DEBMAS

- Direction : 2

5. WE20 Partner Profile

- Partner No : SAPLID

- Partner : Type - LS

- Type : US

- Agent : User6

- Inbound Parameters

- Message type : DEBMAS

- Process Code : DEBM

- * Trigger Immediately

- Save it.

6. BD13 Get Customers

- Customer : 0000000001

- Message type : DEBMAS

7. WE02 Display Idoc

- Direction : 2

- Logical Message : DEBMAS

- Execute it

Regards,

Brown.

Re: IDOC procedure

Former Member — Wed, 09 Apr 2008 05:43:03 GMT

Hi prasad

Can you explain me briefly, my senior is telling that the clients which am going to configure already having logical system.

ie 391 and 392 having already logical system, so how to do this, i want to communicate these two clients.

pls explain me clearly.

topic Re: IDOC procedure in Application Development and Automation Discussions

IDOC procedure

Re: IDOC procedure

Re: IDOC procedure

Re: IDOC procedure