Some PI questions regarding RFC and receiver determination

If we import the design objects in one customer system from another customer system , and in the original system there is an imported RFC ,
This RFC has been created in the new SAP customer system.
My question is do we have to import the RFC again , as it is already in the imported design objecs.
My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the BPM ,
Thanks

My question is do we have to import the RFC again , as it is already in the imported design objecs
Yes....the RFC/ IDOC should be imported from the system to/ from which you will send/ receive the data.
If the RFC was in system1 earlier and now in system2.....then you have to delete the RFC imported from system1 (if it is not used) and then import it from system2
My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the
BPM ,
Irrespective of sync/ async send step.....you should create Receiver Determination....which will have BPM as sender and the TO_SYSTEM as receiver.....not separately for response....just once
Regards,
Abhishek.

Similar Messages

Question regarding Dashboard and column prompt

My question regarding Dashboard and column prompt:
1) Dashboard prompt usually work with only for columns which are in subject area. In my report I've created some of the columns which are based on other columns. Like I've daysNumber column that is based on two other columns, as it calculates the difference of two dates. When I create dashboard prompt I can't find this column there. I need to make a prompt on this column.
2)For one of the column I've only two values 1 and 0. When I create prompt for this column, is it possible that in drop down list It shows 'Yes' for 1 and 'No' for 0 and still filter the request??

Hi Toony,...
I think there was another way of doing this...
In the dashboard prompt go to Show option > select SQL Results from dropdown.
There you need to write your Logical SQL like...
SELECT CASE WHEN 1=0 THEN PERIODS.YEAR ELSE difference of date functionality END FROM SubjectAreaName
Here.. Periods.Year is the column which is already exists in repository's presentation layer..
and difference of date functionality is the code or formula of column which you want to show in drop-down...
Also write the CASE WHEN 1=0 THEN PERIODS.YEAR ELSE difference of date functionality END code in fx of that prompt.
I think it helps you in doing this..
Just check and inform me if it works...
Thanks & Regards
Kishore Guggilla
Edited by: Kishore Guggilla on Oct 31, 2008 9:35 AM

Some simple questions regarding the Xcode.

I have some preliminary questions regarding the Xcode (objective C):
What is the difference between the programming files followed by .h and .m?
What does an asterisk * followed by a text mean (i.e. *window;)?
Is there any source that briefly explains the most common codes with examples (nsstring, nsarray, iboutlet, inaction.....etc)?
Any other tips will be highly appreciated.
Many thanks.

Xcode is the IDE.
Objective-C is the most common language used within Xcode.
UIWindow *window ..... the * means return the address of the instance variable 'window'.
An * is called a pointer to a variable.
Everything you need is explained here: https://developer.apple.com

Some basic questions on ESS and MSS

Hi Experts,
This is the first time I am going to deal with
ESS and MSS.
I have some basic questions about it and they are
listed below:
1. In an organization if they want to integrate
ESS and MSS, how do they go about? What I mean
is, will they install the packages in the R/3
system and then use the to portal features to
make iViews of ESS and MSS.
2. Or is there a seperate package for the portal
and the R/3 system
3.What is the best way to customize ESS and MSS
iViews? Is WebDynpro used to customize ESS and
MSS applications, if yes how?
4. Are these ESS and MSS packages different for
ECC and the older version of R/3 systems? If yes what are the major differences?
Please do let me know on these subjects and also
if anyone of you have any links or documents
associated with this scenario please do send me.
Thank you
Regards
Luke

Hi,
here is what I know..
1 & 2. Depending on the backend SAP version, the relevant ESS/MSS Business Packages have to be installed on the Portal. On the backend it will be via an Add-on.
3. The webDynpro versions of ESS/MSS are available from mySAP ERP2004/2005 (ECC5/6). The best way to customize the iViews would be through the NetWeaver DevStudio.
ent
4. Yes, the ESS/MSS packages are differ depending on the backend SAP version.
You can find all the different packages & their info right here on SDN. From the home page click on the Portal Content Portfolio on the right hand side of the page>Browse Content Portfolio>Self Service for ESS & Line Manager for MSS.
Regards,
Suresh Datti

Question regarding roaming and data usage

I am currently out of my main country of service, and as such I have a question regarding roaming and data usage.
I am told that the airplane mode is sufficient from keeping the phone off from roaming, but does this apply to any background data usage for applications and such?
If the phone is in airplane mode, are all use of the phone including wifi and application use through the wifi outside of all extra charges from roaming?

Ann154 wrote:
If you are getting charged to use the wifi, then it is possible. Otherwise no
Just to elaborate here, Ann154 is referring to access charges for wifi, which is nothing to do with Verizon, so if you are using it in a plane, hotel, an internet cafe etc that charges for Wifi rather than being free . Verizon does not charge you (or indeed know about!) wifi usage, or any other usage that is not on their cellular network (such as using a foreign SIM for example in global phones) So these charges, if any, will not show up on the verizon bill app. Having it in airplane mode prevents all cellular data traffic so you should be fine

Question regarding MM and FI integration

Hi Experts
I have a question regarding MM and FI integration
Is the transaction Key in OMJJ is same as OBYC transaction key?
If yes, then why canu2019t I see transaction Key BSX in Movement type 101?
Thanks

No, they are not the same. The movement type transaction (OMJJ) links the account key and account modifier to a specific movement types. Transaction code (OBYC) contains the account assignments for all material document postings, whether they are movement type dependent or not. Account key BSX is not movement type dependent. Instead, BSX is dependent on the valuation class of the material, so it won't show in OMJJ.
thanks,

**question regarding 3G and wif**.

I have a question regarding 3G and wifi. I have #G activated as well as wifi, when I go to retrieve mail for example I get a pop up asking me if I want to connect to a wifi network…should I have wifi and 3G activated at the same time, and why am I getting the pop up…
Thanks

You can have them on at the same time, but they will not be used at the same time for data. The order of preference for data is WiFi > 3G > EDGE > GPRS. You're getting the pop up, most likely, because you have Settings > Wi-Fi > Ask to Join Networks set to ON. You can set that to OFF, and the iPhone will still join known (i.e. previously used) WiFi networks automatically.

I have a Macbook Pro june 2011... I have 8GB ram but I only have 256mb VRAM... I've read some other questions about this and I realized... Why do I not have 560mb of VRAM since I have 8GB of RAM? Is there any way to get more VRAM to play games on steam?

I have a Macbook Pro june 2011... I have 8GB ram but I only have 256mb VRAM...
I've read some other questions about this and I realized... Why do I not have 560mb of VRAM since I have 8GB of RAM?
Is there any way to get more VRAM to play games on steam?
I've learned by reading other topics that I can't upgrade my graphics card on my Macbook Pro because it's soldered into the motherboard or somthing like that, but please tell me if there is any way to get more video ram by chaning some setting or upgrading something else. I'd also like to know why I only have 256MB of VRAM when I have 8GB of RAM, since I have 8GB of RAM I thought I was supposed to have 560mb of VRAM...
So the two questions are...
Is there any way to upgrade my VRAM, so that I can play games on steam?
Why do I only have 256MB VRAM when I have 8GB total RAM?
Other Info:
I have a quad core i7 Processor.
My graphcics card is the AMD Radeon HD 6490M.
I am also trying to play games on my BOOTCAMPed side of my mac, or my Windows 7 Professional side.
THANK YOU SO MUCH IF YOU CAN REPLY,
Dylan

The only two items that a user can change on a MBP are the RAM and HDD (Retinas not included). You have what the unit came with and the only way you will be able to change that is to purchase a MBP with superior graphics
If you are very much into gaming, the I suggest A PC. They are far superior for that type of application to a MBP.
Ciao.

Interface determination and Receiver Determination

Any one can give the clear idea about Interface determination and Receiver Determination????????

HI Gabriel
Interface Determination
An InterfaceDetermination specifies which interface is to be used for the inbound process of a message.
Interface Determination is to specify which inbound interface of a receiver a message is to be forwarded to. We also specify which interface mapping from the Integration Repository is to be used for processing the message. Here it will know which kind of mapping you are using etc.
 ReceiverDeterminatioin.
A ReceiverDetermintaion defines on or more receivers for a sender and an outbound interface.
Receiver Determination is to specify which receivers a message is to be sent to.
Cheers...
Vasu
** REward Points if found useful **

Question regarding homehub and Open reach router -...

Hi all,
I had infinity installed earlier this month and am happy with it so far. I do have a few questions regarding the service and hardware though.
I run both my BT openreach router and BT Home hub from the same power socket. The problem is, if I turn the plug on so both the Homehub and Openreach Router start up at the same time, the home hub will never get an Internet connection from the router. To solve this I have to turn the BT home hub on first and leave it for a minute, then start the router up and it all works fine. I'm just curious if this is the norm or do I have some faulty hardware?
Secondly, I appreciate the estimated speed BT quote isn't always accurate, I was quoted 49mbits down but received 38mbits down - Which I was happy with. Recently though it has dropped to 30. I am worried this might continue to drop over time. and as of present I am 20mbits down on the estimate . For the record 30mbits is actually fine and probably more than I would ever need. If I could boost it some how though I would be interested to hear from you.
Thanks, .

Just a clarification: the two boxes are the HomeHub (router, black) and the modem (white). The HomeHub has its own power switch, the modem doesn't.
There is something wrong if the HomeHub needs to be turned on before the modem. As others have said, in general best to leave the modem on all the time. You should be able to connect them up in any order, or together. (For example, I recently tripped the mains cutout, and when I restored power the modem and HomeHub went on together and everything was ok).
Check if the router can connect/disconnect from the broadband using the web interface. Leaving the modem and HomeHub on all the time, go to http://192.168.1.254/ on a browser on a connected computer, and see whether the Connect/Disconnect button works.

File to RFC scenario - receiver determination problems

Hi ,
Im trying to work out a flat file to RFC scenario, and am facing problems in configuring the receiver determination .
While creating my receiver determination, in the configured receivers, when i click on the F4 help to select service, i do not see the business system that i configured in SLD .
This system i have configured as an WAS ABAP system and provided all relevant data. I can also import objects from this system into IR, so i dont think i have set it up wrongly. I have also created RFC destination .
Is there some setting that has to be made that im missing ? Could somebody point out why im not able to see this system in the list of business services available at receiver configuration time ?
Thanks,
Joe
I also cleared the SLD cache by the way.. that didnt work either .
Message was edited by:
Joe Stein

Thanks a lot for you replies guys , but problems still not solved ;
1. I looked at the blog given and ive done everything pretty much as given . My problem lies in not finding the business system itself in the list of services for the configured receiver. How to implement this has not been shown in the blog.
2. I tried refreshing the cache and checking again, but it still doesnt show me the necessary step.
SOS !
I checked in the inbound system , and found that an RFC wasnt created for the XI system . I created that but i still cant see this system as a business system when i try to create the receiver determination . Do i need to recreate the technical system in the landscape to incorporate this change ?
Any pointers at all ??
Message was edited by:
Joe Stein

Interface and Receiver determination steps

Dear Experts,
I have list of queries which I am facing issue in ID. I am working on SOAP<->SAP-PI<->PROXY scenario.
1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.
My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the node Communication Component without party). I created this Business System ABAP from the entries of SLD.
2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.
3. In the Receiver Determination, I can see in the "Configuration Overview" tab
that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB
but it shows SI_SOAP_OB.
4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"
and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.
5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.
I need urgent suggestions from experts , kindly help.
Regards
Alice Rebecca

1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.
My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the node Communication Component without party). I created this Business System ABAP from the entries of SLD.
ANS -
For SOAP, anything like Legacy_filer can be created & used.
For PROXY, use the business system of R/3 system maintained in SLD.
2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.
ANS-
Sender CC
Sender Agreement
Rec Determination
Int Determination
Rec CC
Rec Agreement.
Create the steps in COnfiguration Scenario directly.
3. In the Receiver Determination, I can see in the "Configuration Overview" tab
that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB
but it shows SI_SOAP_OB.
4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"
and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.
ANS
its cache error. Go for full cache refresh in IB>AdministrationData cahce--cache refresh.
5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.
ANS
Nope. create the structure in ESR & generate proxy for the same in ECC system. that's it. No need of WSDL here.
-santosh.

INTERFACE DETERMINATION AND RECEIVER DETERMINATION DOUBTS???

Hi Team
I am having doubts regarding the Interafce Determination and the receiver determination. In pur landscape in our objects, some times i am seeing a Condition is being defined in the Interafce Determination and sometimes am seeing a Condition is being defined in the receiver determination . could you please let me know the differences between the above two.
thanx in advance.

Hi Nabhinav,
Condtions in receiver determination - These conditions are evaluated and executed to determine the receivers for this incoming message.
Condtions in Interface determination - These conditions are evaluated and ececuted to determine the Interface mapping to be called in order to map the source message to the target message.
Please take a loot at these links for more details:
http://help.sap.com/saphelp_srm50/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a8e3a8e5430e10000000a42189b/content.htm
Also, search the SDN before posting you query.
Regards, Gaurav.

Flat Idoc and receiver determination

Hi Folks,
I have a scenario in which the Idoc is sent to XI in a flat format (Flat Idoc) using tunneling mechanism. The receiver determination configured is conditional based (Verifies the values in the specified fields of the Idoc).
Now my question is as we know flat Idoc doesn't contain any fields like XML in the input payload, how the receiver can be identified?
Reminder: (Receiver determination is conditional based and verifies some field values in the Idoc structure)
Thanks,
SPMD

Hi Shabbirmdpasha,
You can use file adapter channel to get idoc flatfile and convert to xml idoc in the module of the file adapter (available in PI 7.1). You only need to make a relation with the type of idoc with the name of the file: for example, DESADV_xxxxxx.txt for all files with DESADV flatfile idoc's.
With this method, you know the interface of the outbound interface, and in the receiver determination you can check in the header of the idoc (dc40) to determine the target system.
PD: Sorry for me english...
Edited by: Oscar Navas on Dec 1, 2010 4:11 PM

Regarding rfc and idoc sender

hi
   can any one provide me with some scenarios having
idoc and rfc as senders.

Hi
To Configure the RFC to FILE scenario ,Proceed as Follows
a.       Create an RFC Destination to XI in transaction code (SM59)
b.       Create new destination of type T (TCP/IP)
c.       Make sure you select Registered Server Program option before writing your program ID
d.       Write you program ID (remember it's case-sensitive)
e.       In the gateway host and gateway service write the values of your Application system - business system (not the XI server)
             Step2:Repository
1)       From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
         From the list of Software Component Versions, Choose your own software component version .Click Import.
3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
         The namespace is ur:rfctofile
4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
         After this specify the connection parameters to the R/3 system:
4.1)     System IS :sapfox
4.2)     Client IS :800
         Then Save it. The new namespace will be visible under software component version node in the left frame.
         Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3)     Application server:172.25.5.7
4.4)     System number: 00
4.5)     User name:developer
4.6)     Password: Password of Sap R/3 system.
         Then click continue .You will find IDOC and RFC node. Click on this node and select the   Idoc or Rfc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the   Rfc and Idoc will be available into XI as Message types. So no need to create any Rfc or Idoc Structure. We need to create a structure for file only.
5).      Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6)        Create new data types.
6.1)      Right click on Data types and select New.
           Your Data Type is. dt_file
          In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
          Save the object.
6.2)      The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
          no need to create Data types. They are imported directly as Message types.
6.3)      To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
          Select the following.
6.3.1)    Category: XSD.
6.3.2)    Messages: From All Available Global Elements.
6.3.3)    File:
          Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7).      Create a new Message Type.
7.1)     In the left hand frame under Interface objects, right click on the Message types and select new.
7.2)     Give a suitable name to the Message type.(MT_ messagetype).
7.3)     For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
         Save it.
8).     Create a Message interface
8.1)    In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2).   The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
        Save it.
9) .    Create a graphical mapping between the target document and the sender .
9.1)    In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2)    As Source message select your own Message type.You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- >     Namespace->Imported Objects.
9.3)    As Target Message you can choose your Rfc .Choose Search for Integration Object.
9.4)    Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5)    Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
        Save It.
9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10).     Create an Interface Mapping.
10.1)   In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2)   Source interface : Your Outbound Interface (The Source document(Rfc) interface).You can Choose Search for Integration Object.
10.3)   Target interface:    Your Inbound Interface( The Target document interface).
        Then Select 'Read Interface' and Assign your 'Mapping Program' .
        Mapping Program: Your Message mapping.
        Then Save it.
11.)    Finally , in the left hand frame ,go to your change list and Activate it
           STEP 3: Directory
1)      From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
        Create a Scenario Object
2).     The First Step is to create a Scenario Object
        This will serve as container for all your configuration work. Create and save a scenario object
3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4)      In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) .    Create a Communication Channel.
6).     Expand your service and right click on Communication Channel. Name your Communication Channel
        Here we need to configure the adapter.
    Since the Sender is 'RFC', Specify the following Parameters
         For the adapter type , use the F4 help and select RFC.
         Specify Sender since the adapter will be sending messages to XI
         Specify the following parameters.
         Transport Protocol: RFC
         Message Protocol:   RFC(RFC XML )
         Adapter Engine: Integration Server
         Adapter status: Active
         RFC Server Parameter:
         Application Server(Gateway):172.25.5.7
         Application Server Service(Gateway Service): sapgw00
         Program Id: Id of Registered server program ( it is case sensititve)
         And the adapter is configured. Save it
          Since the Receiver is File , Specify the following Parameters
6.1       For the adapter type , use the F4 help and select FILE.
6.2       Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3       Specify the following parameters.
          Transport Protocol: File Transport Protocol.(FTP)
          Message Protocol: File Content Conversion(since the xml files produce by XI need to be converted to text files)
          Adapter Engine: Integration Server
          For the File system access Parameters, enter the following
          Source Directory:Test
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server:172.25.5.240
          Port: 21(by default)
          Data Connection: Passive
          Connection security: None
          Connection Mode: Permanently
          Transfer Mode: Binary
6.5       For Processing Parameters, Specify the following
          File construction mode: Add Time Stamp
          File Type: Binary
6.6       For Content Conversion Parameters, Specify the Following
          RecordSet Structure:
          Adapter Status: Active
          The receiver file adapter is now configured. Save your Communication Channel.
           Create an Receiver Determination.
7).       From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1)      Select your sender service and interface.
          Sender:
          Party: blank
          Service: Sender service(Business system)
          Interface : Sender interface
7.2)      In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
            Create an Interface Determination.
7.3)       Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1)     In the Receiver Determination   you just created, have a look at the area Configuration Overview for Receiver Determination   at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2)     In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
           Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3)     You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
           After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5)     When you are done , Save the Interface determination object.
8.)         Create a Sender Agreement.
           In the left hand frame , right click on Sender Agreement ->New
8.1)       Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Outbound Interface
8.2)       In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.)         Create a Receiver Agreement.
           Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1)       Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2)       In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
           Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Inbound Interface
9.3)       In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
           Your Configuration is complete. Activate the objects.
To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Sending System in transaction code (SM59)
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.Both should be succesful
2) Create Port Using Transaction Code IDX1
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 R/3 towards other system
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
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.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
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)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Outbound Parameters (WE20)
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
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
5)   Create Customer Distribution model in the transaction code BD64
1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3)   Save the Distribution model
    Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
4)   Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> Distribute to the destination client
    Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
             Step2:Repository
1)       From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
         From the list of Software Component Versions, Choose your own software component version .Click Import.
3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
         Your NameSpace is urn:idoctofile
4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
         After this specify the connection parameters to the R/3 system:
4.1)     System :sapfox
4.2)     Client :800
         Then Save it. The new namespace will be visible under software component version node in the left frame.
         Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3)     Application server:172.25.5.7
4.4)     System number:00
4.5)     User name: developer
4.6)     Password: Password of Sap R/3 system.
         Then click continue .You will find IDOC node. Click on this node and select the   Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the    Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.
5).      Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6)        Create new data types.
6.1)      Right click on Data types and select New.
           Your Data Type is :dt_file
          In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
          Save the object.
6.2)      The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
          no need to create Data types. They are imported directly as Message types.
6.3)      To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
          Select the following.
6.3.1)    Category: XSD.
6.3.2)    Messages: From All Available Global Elements.
6.3.3)    File:
          Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7).      Create a new Message Type.
7.1)     In the left hand frame under Interface objects, right click on the Message types and select new.
7.2)     Give a suitable name to the Message type.(MT_ messagetype).
7.3)     For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
         Save it.
8).     Create a Message interface
8.1)    In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2).   The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
        Save it.
9) .    Create a graphical mapping between the target document and the sender .
9.1)    In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2)    As Source message select your own Idoc .You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- >     Namespace->Imported Objects.
9.3)    As Target Message you can choose your Message type .Choose Search for Integration Object.
9.4)    Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5)    Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
        Save It.
9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10).     Create an Interface Mapping.
10.1)   In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2)   Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose Search for Integration Object.
10.3)   Target interface:    Your Inbound Interface( The Target document interface).
        Then Select 'Read Interface' and Assign your 'Mapping Program' .
        Mapping Program: Your Message mapping.
        Then Save it.
11.)    Finally , in the left hand frame ,go to your change list and Activate it
           STEP 3: Directory
1)      From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
        Create a Scenario Object
2).     The First Step is to create a Scenario Object
        This will serve as container for all your configuration work. Create and save a scenario object
3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4)      In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) .    Create a Communication Channel.
6).     Expand your service and right click on Communication Channel. Name your Communication Channel
        Here we need to configure the adapter.
     Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
          For the Receiver, Specify the following Parameters
6.1       For the adapter type , use the F4 help and select FILE.
6.2       Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3       Specify the following parameters.
          Transport Protocol: File Transport Protocol.(FTP)
          Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
          Adapter Engine: Integration Server
          For the File system access Parameters, enter the following
          Source Directory:Test
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server: 172.25.5.240
          Port: 21(by default)
          Data Connection: Passive
          Connection security: None
          Connection Mode: Permanently
          Transfer Mode: Binary
6.5       For Processing Parameters, Specify the following
          File construction mode: Add Time Stamp
          File Type: Binary
6.6       For Content Conversion Parameters, Specify the Following
          RecordSet Structure:
          Adapter Status: Active
          The receiver file adapter is now configured. Save your Communication Channel.
           Create an Receiver Determination.
7).       From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1)      Select your sender service and interface.
          Sender:
          Party: blank
          Service: Sender service(Business system)
          Interface : Sender interface
7.2)      In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
            Create an Interface Determination.
7.3)       Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1)     In the Receiver Determination   you just created, have a look at the area Configuration Overview for Receiver Determination   at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2)     In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
           Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3)     You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
           After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5)     When you are done , Save the Interface determination object.
8.)         Create a Sender Agreement.
           In the left hand frame , right click on Sender Agreement ->New
8.1)       Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Outbound Interface
8.2)       In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.)         Create a Receiver Agreement.
           Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1)       Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2)       In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
           Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Inbound Interface
9.3)       In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
           Your Configuration is complete. Activate the objects.
plz rewards points
vikas

Some PI questions regarding RFC and receiver determination

Similar Messages

Maybe you are looking for