questions about IDoc to file scenario

[Former Member]

I 'm confused, and have a few questions:

1, we need to define a product for it at least , assign it to either of the systems?

2, we don't have to configure an IDoc communication channel, do we?

3, does the receiver system (file/ftp) need a logical system? and define it by t-code BD54, in XI or R/3?

4, at least define techinical system and business system for R/3?

Can you explain the sld configuration to me ?

thanks a lot.

[Former Member]

I have workd out.

Thanks for your help.

[former_member556603]

Hi,

,1) we need to define a product for it at least , assign it to either of the systems?

Ans: Yes we need to define a product.

2, we don't have to configure an IDoc communication channel, do we?

Ans: Sender agreement and Sender IDOC communication channel is not required as IDOC adapter

resides on ABAP stack.

3, does the receiver system (file/ftp) need a logical system? and define it by t-code BD54, in XI or R/3?

Ans: For third party system from ID create the business system and use that Business system for File or

FTP system.

Business System.

1.Goto Business Landscape->New Business System->Name the business system.

2. Choose the technical system that needs to be attached->WebAS ABAP->Technical System Name.

Business System have an entry in the SLD and Buiness Service do not.

Business Systems are used when you are sending data to and from an R3 system and can be of ABAP, JAVA and Third Party Types.

Business System is a logical representation of a Technical System.

Business Service is a abstract representation of a System. For instance, www.google.com have a several system working together and IPs of this machines change eventually. When we use a Business Services like google we reference a computer that we don't know the phisical implementation.

4, at least define techinical system and business system for R/3?

Technical System

In SLD, click on technical landscape->New Technical System->WebAS ABAP.

Ans: Yes : Technical system is a phisical machine, it have a IP. Can be a BBDD, ERP, J2EE ......... a Business System is a logical term that we use into the Business Scenarios and represent these Technical System that we had created.

Can you explain the sld configuration to me ?

SLD is the place where u can define systems that are existing in ur landscape. using these systems u can transfer data from one system to another using PI.

TBIT40:

https://websmp109.sap-ag.de/~form/ehandler?_APP=00200682500000001337&_EVENT=DISPLAY&COURSE=TBIT40

/people/sugree.phatanapherom/blog/2005/08/14/configuring-sld-in-sneak-preview-sap-netweaver-04-sneak - SLD preview

SLD - http://help.sap.com/saphelp_nw04/helpdata/en/6e/fba1c735e0b44496072595092d924c/frameset.htm

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30f8bd90-0201-0010-dd9a-c8a7f52c...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d64...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/652b1f46-0a01-0010-25ae-e7cb07b5...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c00e7efc-0f27-2a10-d9a2-c46fc386...

Check this out

http://help.sap.com/saphelp_nw04/helpdata/en/56/361041ebf0f06fe10000000a1550b0/content.htm

Log into SLD and click the Help Link

You will get the detailed documentation for SLD for your version

Thanks,

Satya Kumar

Reward if it is useful

Edited by: SATYA KUMAR AKKARABOYANA on Apr 24, 2008 12:30 PM

[Former Member]

Create Data Types

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

Create your Sender Data type -- DT_SRM

Create your Receiver Data Type -- DT_File

Create Message Types

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

MT_SRM(DT_SRM)

MT_File(DT_File)

Create the Message Interface

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

MI_SRM(MT_SRM) Outbound & Asynchronous

MI_File(MT_File) Inbound & Asynchronous

Create the Message Mapping

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

MM_SRM2File ---(MT_SRM to MT_File)

-

---

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

Log on to SRM System

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

Transaction /nSPROXY

Create your Proxy

-

---

XI Directory

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

Create Sender Agreement

Create Receiver Agreement (FILE Receiver)

Create Interface Determination

Create Receiver Determination (Refer your Receiver Agreement and Interface Determination)

Sender side no need to create comm channel..bcoz idoc is on ABAP stack..

Atleast we have to create one product..

Bussiness system is the logical name for the tech system..

first we have to create the tech sys.. and then we have give one logical name to the tech sys..that logical name we have given is the business sys...

Thanks

[Former Member]

HI,

I 'm confused, and have a few questions:

1, we need to define a product for it at least , assign it to either of the systems?

Yes.

2, we don't have to configure an IDoc communication channel, do we?

Sender agreement and Sender IDOC comm channel is not required as IDOC adapter resides on ABAP stack hence it is not required.

3, does the receiver system (file/ftp) need a logical system? and define it by t-code BD54, in XI or R/3?

For third party system from ID create the business system and use that Business system for File or FTP system.

For R3 which involved IDOC,RFC and PRoxy scenario u need to define the business system in SLD and import it into ID and use that.

4, at least define techinical system and business system for R/3?

Yes

Can you explain the sld configuration to me ?

Refer the below IDOC configuration link:

ALE configuration for pushing idocs from SAP to XI

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

IDOC testing using WE19

/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi

SLD configuration link:

Please follow the below process for configuration:

File To IDOC - Part1 (SLD and Design):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&

File To IDOC - Part2 (Configuration):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&

File To IDOC - Part3 (Steps required in XI and R3):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&

Pre-requisites for Inbound IDoc to R/3 from PI:

Configuration required at Xi side:

Go to IDX1: configure the port.

Go to IDX2: load the DOC metadata.

Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,

Configiration required at R3 side:

Maintain Logical System for PI (SALE transaction):

Maintain Partner Profile for XI system(WE20):

Pre-requisites for Outbound IDoc from R/3 to PI:

Configurations required in R/3:

Maintain Logical System (SALE)

Define RFC Destination (SM59) which points to PI system

Maintain Port (WE21)

Maintain partner profile. (WE20):

Maintain Distribution Model (BD64):

Troubleshooting File-to-IDOC Scenario in XI.

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

chirag

[Former Member]

I'm trying to work out this scenario.

Now I created business service for R3 and ftp.

My questions are,

1, Do I need to run bd64, and distribute the model view in R/3?

2, In R3, Create a logical system name, this LS is not the logical system name for any client?

3, How to use WE19?, there I need to input partner profile and port for both Reciever and Sender system.

R3 is the sender system, right?

in R3, How can I get the sender system's partner No.?

4, In ID, specify the adapter identifiers. the logical system is partner profile no or LS name of the sender R3 client?

5, If I created third party TS for R/3, then do I have to setup the Integration role for R/3, t-code sxmb_adm.

Thanks if you can help out.