Data transfer via Rfcs

[Former Member]

Whenever the material master is created in ECC RFCs are triggered and the data is transferred to GTS via RFCs

(no idocs are triggered)

Is there any way out to stop this transfer

how can can we know the mapping of what fields of ECC are mapped to which fields of the other system

please advice

[Former Member]

Hi,

Have you created the logical systems and then distributed the message type between those system.

you need to create the partner profile and then execute the RBDMIDOC program by giving the message type as input, prior to that you need to activate the change pointers for your message type.

Otherwise you can execute the program RBDSEMAT program by giving the logical system and material number, you wanted to transfer as input and execute.

Thanks,

Mahesh.

[Former Member]

How is change pointers related to ?

when the data is being transferred via Rfcs(TRFCs)?

[Former Member]

If change pointers were to be activated then

Idocs should be created but i see no idocs created when the data is transferred

[Former Member]

Hi Kittu,

You might have missed out on any of the steps which you need to do, that's the reason why idoc's are not generated at the moment.

Thanks,

Mahesh.

[Former Member]

Hi,

let us say outbound is SAPLID server

and inbound is SAPLER server.

we need to following setting in order to generate idocs. You can see the generated IDOC in WE02 TCode.

Status code should be 03.

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 case if your IDOC is generated with errors (status would be red signal) get back me with status code.

Regards

Srikanth

[Former Member]

I am not concerned with idocs now

as the data seems to be replicated with Trfcs i want a wayout to find the Function moduled used by those Trfcs

[Former Member]

Hi,

Function modules are linked to process code. you can see the respective FM by simply double clicking process code in WE 20 tcode.

bye