IDOC-XI-FILE Scenario

[Former Member]

Hi

I am working on idoc - xi - file scenario and wondering what seting I have to make in SAP R/3 to kick off Idoc automatically every after 5 minutes so that all the changes in material master can be sent to XI and then to the legacy system.

Please let me know the work around for the same.

Regards

Rinku

[Former Member · Accepted solution]

Hi Ashwin,

There is a SAP note : this note is for inbound interfaces.

Note 1011351 - DSD connector: Changed master data is replicated incorrectly

I hope you have used this program for Outbound interfaces and hope it didn't give any short dumps. Also I am assuming that the data will be sent to XI directly as RFC destination configuration will be done as a pre-requisite.

Regards

Rinku

[Former Member · Accepted solution]

hi Rinku,

You have got it right..Once u use RBDMIDOC report the data may not replicated properly...

However, for correct replication of Change Pointers enabled data ...u can use following Notes 844260,843743,843744.....

This assures correct data replication...

Regards,

Ashwin M

reward if helpful

[former_member529475]

Hi Malik

<u>Maintain the Sender R/3 System</u>

Create a RFC Destination to XI using the Tcode SM59

Create a TRFC Port and specify RFC Destination created above using the TCode WE21

Create the partner profile for Inbound and Outbound Parameters using WE20

<u>Maintain the Receiver XI System</u>

Create the RFC Destination for sender system using SM59

Create the port to get IDOC Metadata from Sender System using the Tcode IDX1. Here the Port name we are given and port name in the IDOC header will be identical.

Maintain the IDOC Metadata using the Tcode IDX2.

While creating the OUtbound partner profile in R/3 you will found the option like kick off the idoc automatically.

Cheers..

Vasu

<b><u>** Reward Points if found useful **</u></b>

[Former Member]

to add more....

<b>ALE settings.</b>

<u><b>SAP XI</b></u><b>1) RFC Destination (SM59)</b>

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

<b>h) Test the connection and remote logon.

2) Create Port (IDX1)</b>

a) Select create new button

b) Enter the port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP XI towards other system.

e) Save

<b>3) Load Meta Data for IDOC (IDX2)</b>

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

<u><b>SAP R/3</b></u>

<b>1) RFC Destination (SM59)</b>

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

<b>2) Create Port (We21)</b>

a) First Select Transactional RFC and then click create button

b) Enter the destination port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

<b>3) Create Partner Profile (WE20)</b>

a) Create New

b) Create the Partner no. name as same the logical system name of the destination system.

c) Select Partner type LS

d) Enter details for Type: US/USER, Agent, and Lang.

e) Click on the + button to select the message type.

f) Select Partner no. and LS which ever create above.

g) Select Message type

h) Select Process code related to the Message type.

I) save.

<u><b>In SLD – System Landscape Directory</b></u>

TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.

Ts for Third Party (Logical system):-

BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.

BS for Third Party (Logical system):-Enter the XI logical system name.

<b>In Transaction SALE</b>

Define and Assign the logical system name.

[Former Member]

Thanks Raghvesh for the steps. What needs to be done to kick off IDOC every after 5 mins or at any specific time. Do I need to make any changes in R/3 or at XI.

Regards

Rinku

[former_member529475]

Hi Rinku

schedule <b>"rseout00"</b>, every 5 mins

Cheers..

Vasu

[Former Member]

Hi Vasu,

Question1.

This solves my problem for 3-4 interfaces, but in one of the interface where Idoc needs to be kicked off whenever changes has been made in Good receipts......

Question 2

For Good receipt scenario I have 6 files and would be using ORDERS as standard SAP outbound. Each file has some identifier I mean some key field in the IDOC will be sent and then based on that file will be picked. I guess I would be using multiple mapping for the same. Do you have any idea abt the same. If you can provide me the steps for the same.

regards

Rinku

[Former Member]

Hi Rinku,

The solutions provided for the ALE settings will keep on distributing the whole bunch of records and <b>not the changes</b>.To trrack the changes and distribute them u shoud use the concept named <b>Change pointers</b>.

Change pointer enables to u distribute on the added/changed record....

Use the following transactions for enabling the change pointers for the particular msg type or globally

bd61--> For enabling CP globally

bd50--> For enabling CP for the msg type

bd52--> For enabling CP for the field type.

RBDMIDOC--Report For processing CP

This will solve ur problem

Regards,

AshwinM

[Former Member]

Hi Avinash,

Does it mean that I would be using two programs one for good receipt happening for the first time will use <b>rseout00</b> and another program <b>RBDMIDOC</b> for change pointers with all the changes. I hope this change pointer will catter all deletions also.

Please let me know if my understanding is correct?

regards

Rinku

[Former Member]

Hi Rinku,

U should do all the ALE settings first for distributing the existing data...

U should enable the Change Pointer for the msg type ie ORDERS in ur case....

and a program RBDMIDOC for processing those change pointers

This will pass on only the changes to XI and not the data and not the data distributed earlier...

By the way my name is Ashwin not Avinash:-)

Regards,

Ashwin M

Reward if useful

[Former Member]

Hi Ashwin,

Sorry for the incorrect name.

I understand tht changes will be sent by change pointer but at some time I would be sending data so it means i will be scheduling two different jobs....

Regards

Rinku

[Former Member]

hello Rinku,

U need not schedule two jobs for that .even if u make any updation ie addtion of new records that will be distributed to XI system one change pointers are enabled...

Regards,

Ashwin M

[Former Member]

Thanks Ashwin...

[Former Member]

Hi Ashwin,

There is a SAP note : this note is for inbound interfaces.

Note 1011351 - DSD connector: Changed master data is replicated incorrectly

I hope you have used this program for Outbound interfaces and hope it didn't give any short dumps. Also I am assuming that the data will be sent to XI directly as RFC destination configuration will be done as a pre-requisite.

Regards

Rinku

[former_member335553]

Hi

u can schedule the job very 5 minutes using SM36/SM37

For IDOC to File scenario

U can follow these steps....

https://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized

see the below links

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi