File to ABAP Proxy(ProductActivityNotification_In)

Question

Hi All
I have to develop one scenario for Flat File to ABAP Proxy (ProductActivityNotification_In).
I am going to use Receiver File Adapter(to receive file in PI) and Reiver XI adapter(to send file to SNC proxy ProductActivityNotification_In)
I am new to XI please let me know how to approach to this solution.
What could be the design steps I need to consider?
Do I Need to use content conversion?
Can I use graphical mapping?
Thanks for your inputs.
Regards
Amol.

Answer 1

Hey,
You need to import the SNC standard content in XI.
This will provide you with the Proxy interface.
Then you need to do certain settings on the SNC server.
R3 side
SLDCHECK
  Use this transaction to access the SLD of XI.
SLDAPICUST
  Create an entry for respective XI server
  requires hostname, port username and ip.
  Can have multiple enteries for different servers.
  But you can check only one entry.
  based on the entry that is checked, respective SLD API will be triggered from
  SLDCHECK.
SM59 (T type connections).
  To connect to the SLD you need 2 types of TCP/IP connections.
  1)LCRSAPRFC:-
      In this you require the gateway host(ip address) and gatewayservice(sapgw[system no.])
      YOu also need to give Program ID.
      Entry of corresponding Program ID must be maintained in SMGW.
      IN SMGW Click GoTo->logged on Clients.
      If entry is not there for corresponding XI.
      Create a communication channel in XI, pointing to R3 and give a Program ID
      in the channel. Once the channel is activated, corresponding Program ID wil
      appear in SMGW.
  2)SAPSLDAPI:-
     In this case follow the same porcedure as for LCRSAPRFC.
   As far as the Program ID is concerned te procedure mentioned above is for
   Customized RFC's
   The RFC destinations mentioned here are both standard RFC's
   Hence for these two RFC's no need to Create Program ID's. you just need to
   change the System ID of the Program ID.
   Both these RFC's are maintained in the J2ee server of XI.
SPROXY.
   In this transcation you can check the Proxies.
   If the proxies are not activated (i.e. if the message interfaces are not active)
   then you need to maintain one G type RFC destination pointing the resepctive XI server.
   In the G tpye RFC destination give the Ip adress of the XI server in the target
   host and set the path prefix as /rep.
   Goto SPROXY->Goto->connection test-> click on the table SPROXSET.
   In this table maintain enteries for ADDRESS_ONLY_FROM_SPROXSET and IFR_HTTP_DEST
   The values corresponding to these enteries will be the G tpye RFC destination.
In order to connect R3 to the Integaration server you need to maintain H type
The default RFC is XI_INTEGRATIONSERVER. In you need to give the Target host entry as the
Ip address and Path Prefic as.../sap/XI/engine/?type=entry (this you can get from SXMB_ADM of XI)
You can also create the H type RFc of your own.
goto SXMB_ADM(r3) and open Integration engine configuration.
Goto edit->change global configuration and give the RFC dest name like this:-
Corresponding Integration server:- dest://{h-type rfc destination}
If you do not want to create RFC destination you can directly give
the Integration server address(that you can obtain from SXMB_ADM of XI) in the
Corresponding Integration server field.
This is to activate the communication between SNC and PI.
now you need to create the file structure in XI.
the next step is to do the mapping between the file structure and the appropriate interface
As yours is a flat file you need to do a file content conversion
In Integration directory you need to configure two channels one for File and the other one for Proxy.
regards,
  Milan