Doubt in SM59

Hi Experts,
While creating the RFC destination for IDOC Adapter we choose the connection type as " 3 " ( ABAP Connection )
But for the RFC adapter the connection type is " T " (TCP/IP) .
What is the reason behind this ?
And in the Sender RFC adapter we give a Program Id ( which is case-sensitive) and this is used in the Sender RFC communication channel.
what is the use of Program ID ?
what is the relation between the XI and SAP using this PROGRAM ID ?
Regards,
Jude

Hi,
>>While creating the RFC destination for IDOC Adapter we choose the connection type as " 3 " ( ABAP Connection )But for the RFC adapter the connection type is " T " (TCP/IP) .What is the reason behind this ?
IDoc used ALE layer for transport to PI/XI. But for RFC RFC Adapter is used which lies on JAVA engine of SAP XI/PI
>>And in the Sender RFC adapter we give a Program Id ( which is case-sensitive) and this is used in the Sender RFC communication channel. what is the use of Program ID ? what is the relation between the XI and SAP using this PROGRAM ID ?
PROGRAM ID binds a RFC DESTINATION with a RFC Sender Adapter. And hence it should be unique for each sender channel. Program id binds channel with RFC Destination
Regards
Suraj

Similar Messages

Doubt on server proxy and file to idoc scenario

Hi,
     I could able to solve most of my doubts from this forum, many regards to all who assisted me.Here are some simple doubts plz help me in solving them.
          1.In FILE to PROXY scenario is it necessary to create rfc destination on IS and receiver system? becoz in some blogs it is written to create RFC dest only in case of CLIENT PROXY,since we XI adapter to connect receiver syst in case of server proxy?
          2.In FILE to IDOC scen at receiver side is it necessary to formalities in SM59,WE21,WE20 or just configure in WE20 to maintain partner profile?
          3. In case of single SLD for DEV,CON,PROD while transferring from DEV TO CON using file system how do we move file in EXPORT DIRECTORY TO IMPORT DIRECTORY of cons system?
          4.for transporting IR objects we can use TRANSPORT LIST or CHANGE LIST which will be more preferable?
          Plz kindly answer to any of questions u know ?
          Points will be rewarded for valuable answers.
                                                                                Regards,
                                                                                Smitha.

> 1.In FILE to PROXY scenario is it necessary
> to create rfc destination on IS and receiver system?
> becoz in some blogs it is written to create RFC dest
> only in case of CLIENT PROXY,since we XI adapter to
> connect receiver syst in case of server proxy?
You need to maintain the setting on your R3 system to connect to XI for the Transaction SPROXY as shown in the blog "How to Activate ABAP Proxies".
Apart from that as you are doing a file to proxy via XI, XI would need to send data to the R3 system . For this, you can either key in the Details of the R3 system in the XI adapter directly or you can maintain a HTTP destination on your XI in SM59 and use this in the XI adaper.
> 2.In FILE to IDOC scen at receiver side is
> it necessary to formalities in SM59,WE21,WE20 or
> just configure in WE20 to maintain partner profile?
Just the partner porfile. SM 59 and We 21 are used for port and RFC destination and as it is XI that is posting the Idoc these steps are not needed on R3
> 3. In case of single SLD for DEV,CON,PROD
> while transferring from DEV TO CON using file system
> how do we move file in EXPORT DIRECTORY TO IMPORT
> DIRECTORY of cons system?
You have to go to the Folder Level / OS level of your XI server, copy the files from the Export DIrectory and move these manually to the import folder of the CONS server. This is for both IR and ID objects.
> 4.for transporting IR objects we can use
> TRANSPORT LIST or CHANGE LIST which will be more
> preferable?
If you perfrom File Transport, the imported objects will be available under the Import Change List and you need to activate this Import Change List.
Regards
Bhavesh

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

SM59 - Remote Logon taking very long time - RFC is receiver

Hi Friends,
We have ABAP connection (SM59) to R/3 system from PI system. The connection test is fine. But, when we click the Remote Logon from SM59, it is taking very long time. It is unable to login.
Due to this, messages are in scheduled state in the receiver CC monitoring. (SOAP to RFC - Async ). Receiver RFC CC also are green.
We checked with R/3 team, the remote user which is used in SM59 is not locked in R/3 system and password also not changed.
Friends, kindly clarify why it is taking very long time from PI in SM59 when the connection is fine.
Kind regards,
Jegathees P.

Hi Sabarish,
I checked in SM58. There are no entries. SM59 is for other interfaces (IDoc). In the Message Monitoring all messages showing 'To be Delivered' and 'Delivering' from yesterday onwards. In the CC monitoring, it shows 'Message Processing Started' from yesterday onwards. But not completed.
I checked in SM21 take log of type 'RD'. I doubt is this the correct log for this problem.
The specified operating system call was returned with an error. |
For communication calls (receive, send, etc) often the cause of errors
are network problems.
It could also be a configuration problem at operating system level.
(file cannot be opened, no space in the file system etc.).
Additional specifications for error number 146
Name for errno number ECONNREFUSED
Interprocess communication (e.g. TCP/IP) connection refused by partner.
|This usually means that the necessary receiver program is not running.
Kindly clarify.
Kind regards,
Jegathees P.

IDOC - doubts

Hi Experts,
I have few doubts regarding Idoc.
1. Max size of an Idoc
2. How many times a sigment can get repitated in Idoc (maximum)
3. What is use of Trust system in logical system SM59
4. in Distribution model, where filter objects/documents are stored.
Waitng for your valueble answers.
Regs
Rams

Hi,
Please find some answers below
1. Max size of an Idoc - 1000
2. How many times a sigment can get repitated in Idoc (maximum) - You can set the maximum number while creating the segments
3. What is use of Trust system in logical system SM59 - If you want to pass data to other SAP or non SAP system, an RFC connection is required to do so....Here in IDOC you require to create a partner profile (WE20).
4. in Distribution model, where filter objects/documents are stored.: Check BD64 transacction and you can find the filters there for the distribution model
Reward if usful
Regards
shiva

IDOCs creation - Transfer Orders(TOs) for Deliveries - Basic doubts, thanq

Hi Experts,
Am new to IDOCs. I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
My doubts:
1- I hv been asked to create IDOC, Wht does it mean?
2 - How the created IDOC will be get posted?
My requirement is:
Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product. The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D. Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc. Create a new TO confirm idoc per delivery idoc being processed. Create a line item on this idoc for every line on the delivery idoc. Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc. There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP). There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality. Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process. The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
Source = DELVRY03     Destination = WMTCID01
Record Name-Field Name-Record Name-Field Name-Description---Comments
E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look w/ idoc delivery line nbr
EVERY THING IS DATA TRIGGERED!!!
thanq
Edited by: Srinivas on Jun 27, 2008 4:41 PM

IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.

SMGW doesn't show "registered program" from SM59

Well i have a TCP/IP Destination in SM59 where a "registered program" is used to call this RFC-Destination!
This i have to give in IDoc-Receiver-Channel to get the incoming IDoc from external System (nonSAP) to be processed!
Because i made the same with another System i am not able to figure out what is wrong now. When i try to do a connection test i get error:
ERROR: program XXX not registered
Therefore i checked in SMGW, found the former registered program for the other system, but the new one is not visible. After this i recreated the destination, Test failed again, program is not appearing!
What might be the problem?!
br

well mikes blog focuses on getting an RFC connectivity for a Sender RFC adapter. Now for a RFC sender the connection type for the destination is of type TCP/IP.
But what i pointed out earlier is that in case u are using a IDoc adapter, then the RFC destination should be of type R3. I hope you got the point i am trying to make.
Well i got ur point. But since we have some other scenario which runs that way i doubt that i know need to add a Destination of type R3 since it is also a nonSAP System.
But what are ur steps of connecting an external nonSAP-System or even a program to a R3-System (here it is XI)?!
Can u explain in detail??!
br

Basic Doubts

Hello Experts,
Please any one of them clarify my some of the Basic doubts
1.Reg ODS activation failure in Process chain,I know how to correct incase if ods activation failed.I want to know,What could be the reason for failure and in background whats happening(Techincally)
2.Reg Attribute change run failure in process chain,what could be the reason.(technically)
3.Whats is the purpose of trfc and what we have to check in SM58.
4.What is the diff between the IDOC(transfer method) and Idoc which is used to transfer the data in PSA transfer method..(For ex - If i am using the PSA transfer method,even there to transfer the datapackets,we are using Idoc)
5.Some of the time,I am getting the error like this"Non updated idoc in source system and error mesg from the source system/Business warehouse.
This mean,what could be the reason.(Frequently i am getting the above errors and If i used the repeat option,It has been corrected and loaded succesfully)
6.How many datasources can be assigned to one Infosource(Is any limit is there)
I request you to advise on the above doubts and I will assign the points.
Thanks in advance
Regards
Kumar

Hi,
1. During the month end procedures and week ends the number of records will be more rather than the week days, so the data packages defined will run for long time, so we will be getting Time out error, we have to manually activate the data packages.
2. if you r not using Attribute change run, then your Master data(text, attribute, hierarchy wont get activated when you run a process chain)
.so it is mandatory that once you fill the master data u have to activate those, for that we need Attribute change run.
3. tRFC calls which transfer IDocs use the function module IDOC_INBOUND_ASYNCHRONOUS at reception If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.
In the standard SAP system, if tRFC errors occur, a background job is generated to re-establish the connection. In certain circumstances this could result in a large number of background jobs being started that completely block background processing. To cancel a background job if tRFC errors occur use program RSARFCEX to restart tRFC.we go for SM59 transaction for this.
Choose Destination ® tRFC Options and select the option Suppress Background Job at Comm. Error.
4. PSA :
The data is sent directly from the source system to the BW and it is stored in the PSA (Persistent Staging Area), we can update automatically/manually to corresponding Info providers .The transfer type here is called the TRF (Transactional Remote Function).
IDOC :
The data is packed into IDocs by the source system and sent to the Business Information Warehouse. In BW the data is saved persistently and intransparently in the IDoc store. we have some prerequisite here to use this method ,Transfer transfer structure must not have more than 1000 Bytes in the character format.
6. One datasource can be assigned to one info source.

Https communication not connecting from sm59

Hi Team,
Scenario is , via sm59 we are connecting https URL to third-party using a proxy server within our network , and https port also opened in proxy server.
Is there any configurations required in sap for https communication with third party URL.
Error Logs:- While trying to connect https connection from proxy server to a third party URL , we are getting proxy 502 error.
My doubt is do we need to activate https service from ICM , Also is it required to open 443 port number on that particular box
Can anyone help on this. Really appreciate your inputs.
Please suggest.
Regards,
Pradeep G.

Hi Amit,
Please find the below ,
Status HTTP Response    502
Status Text    Proxy Error ( No data record is available. )
Duration Test Call    18895 ms
Technical Information (for support personnel)
Error Code 11004: Host not found
Background: This error indicates that the gateway could not find the IP address of the website you are trying to access, possibly due to lack of information in the DNS server.
Date: 2/07/2014 11:36:51 AM [GMT]
Server: adelisa001.originenergy.com.au
Source: DNS error
Thanks,
Pradeep G.

Basic doubts Regarding the RFC to File scenario.

Hi All,
I'm doing a RFC to File scenario, so before starting the development i went through many blogs and sites to know more the about scenario. I'm confused in the step where we have to create a RFC (type TCP/IP) in sm59.
I have the following doubts :
1)whether to create the RFC in sender (which will be ECC system) or XI.
i.e., RFC in sender (ECC) pointing to xi system in sm59 of Sender(ECC)
or
in XI pointing to sender (ECC) system.
2) the program id maintained in RFC.
the program id is any name or the FM which is being imported in XI system.
Thanks in Advance,
Kind Regards,
Lalitkumar.

Hi Lalitkumar,
1)whether to create the RFC in sender (which will be ECC system) or XI.
i.e., RFC in sender (ECC) pointing to xi system in sm59 of Sender(ECC)
or
in XI pointing to sender (ECC) system.
It should be in sender ECC.
2) the program id maintained in RFC.
the program id is any name or the FM which is being imported in XI system.
It can be any name but should be same in RFC destination and RFC adapter.
As stefen mentioned use ABAP proxy inspite of RFC as its better performance wise.
Regds,
Pinangshuk.

Doubt in fbl1n transaction

hi i have a doubt....
in fbl1n transaction, there are open items and cleared items.
in it the cleared items for certain document types such as invoice etc is not present in the open item table (bsik)
however the cleared items for document types such as general voucher its present in the open items table (bsik)
is this possible as all cleared item entries shld b present in the open item table with an indicator set for cleared or not...
plz exlain!

Hi
There are 2 tables(open and Closed Items) in FI for Account Payables and Account Receivables and GL accounts
1.Account payables: BSIK is Open Items and BSAK is Closed items
2.Account Receivables; BSID and BSAD for OPEN and closed items
3/GL accounts : BSIS and BSAS for Open and Closed Items
<b>Reward points for useful Answers</b>
Regards
Anji

Doubt in creation of a new object

Hi All,
I have one doubt in creation of a new object.If a new object is to be created and it is not a subtype
of any existing object, then what should we enter in the Program field for creating the object?
I hope I am clear with my question.
Thanks in Advance,
Saket.

Hi Saket,
Following will be required for created a custom business object.
1. Object Type - ZTEST (Internal Techincal Key)
2. Object Name - ZTESTNAME (Technical Key Name)
3. Name - TEST (Name of BO, it is used while selecting the object type)
4. Description - (Short Description of BO)
5. Program - ZTESTPROGRAM (ABAP program in which the methods of the object type are implemented)
6. Application - A or B.. etc (Area to which your BO is related)
Please remember that you can learn these basic things by giving F1 help on those fields and in HELP.SAP.COM.
Regards,
Gautham Paspala

Doubt in sender mail adapter

Hi Everyone,
Can we read and validate the attachment of the mail.If so how to do it.
Thanks in advance,
Sakthi

Hi Sakthi,
Please refere the below links:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ad/bf93409c663228e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0d/52b240ac052817e10000000a1550b0/frameset.htm
Let me know if you have any doubts regarding this.
Thanks,
sekhar.

SAP_PROXY_ESR: Problem with the 'Connection Test' on transaction SM59

Hi,
I have a problem when eject the 'Connection Test' command on Transaction SM59.
I made the RFC Destination SAP_PROXY_ESR with:
Technical Settings
Conection Type: G
Target Host: my_host
Path Prefix: /rep
Service No: 1080
Logon Security
Basic Authentication: X
SSL: Inactive
SSL Client Certificate: DFAULT SSL CLIENT (Standard)
User: ers_user
Password: ers_password
Especial Option
No Time Out: X
HTTP Version: HTTP 1.0
Compression: Inactive
Compressed Response: YES
Accept Cookies: NO
I completed the transaction SPROXSET with:
IFR_ADDRESS             ESR_USER     http://my_host:1080/rep
IFR_PASSWORD     ESR_USER     esr_password
IFR_USER             ESR_USER     ESR_USER
In the transaction SM59 (RFC Destination SAP_PROXY_ESR) I'm making the 'Connection Test' but this command give the Message: ICM_HTTP_CONNECTION_FAILED.
In the program SPROX_CHECK_IFR_ADDRESS
Message: 'Cannot determine repository version'
Log_1- No vendor specified
Log_2- No vendor specified
I don't know the reason of this messaje.
I tried change the Service No. with others Ports but, the error is the same everytime.
Can anyone help me please?
NOTE: In my landscape, i dont have the Stack JAVA installed.
Thanks and Regards

But the Enterprise Services Repository is Java.
the /rep points to the folder of the Repository.
the ESR is part of SAP PI or CE.

RFC Connection error in SM59 for SAP J2EE

Hi All,
i am getting the following error description while testing the connection for
SAP J2EE ...
Connection Test SAPJ2EE
Connection Type TCP/IP Connection
Logon              Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: program sapfallback not registered
Error Details     LOCATION: SAP-Gateway on host filip / sapgw00
Error Details     DETAIL: TP sapfallback not registered
Error Details     COMPONENT: SAP-Gateway
Error Details     COUNTER: 1483
Error Details     MODULE: gwr3cpic.c
Error Details     LINE: 1694
Error Details     RETURN CODE: 679
Error Details     SUBRC: 0
Error Details     RELEASE: 700
Error Details     TIME: Tue Mar 31 02:44:35 2009
Error Details     VERSION: 2
Help me resolve this
Regards,
Mahesh.

Hi,
Please follow this steps:
Creating RFC Destinations in the ABAP and Java Environment
You need to create the following RFC destinations in transaction SM59 (ABAP) and the Visual Administrator (Java):
u2022 AI_RUNTIME_JCOSERVER
u2022 AI_DIRECTORY_JCOSERVER
u2022 LCRSAPRFC
u2022 SAPSLDAPI
Depending on your client settings, it may be necessary to be logged on your SAP Exchange Infrastructure host as SAP system user with the authorization to maintain customizing tables and to release transport orders. Note, that user "SAP*" or "DDIC" does not have these authorizations.
Maintaining the RFC Connections (Transaction SM59)
1. Log on to your SAP Exchange Infrastructure central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
RFC destination: AI_RUNTIME_JCOSERVER
Connection type: T
Description: <your description>
5. Choose ENTER
6. Choose the tab Technical settings and do the following:
a. Select Registered Server Program
b. In the Program ID field, enter: AI_RUNTIME_<SID> where <SID> is the SAP system ID of your Integration Server host. Use uppercase letters only.
c. Enter Gateway host and Gateway service of your Integration Server host. To find out the required parameters:
a. On the Integration Server host, call transaction SMGW
b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and gateway service)
7. Choose tab Special Options and select the flag Unicode in the box Character Width in Target System.
8. Save your settings.
9. Repeat the steps 3 u2013 8 for the remaining destinations:
Destination
Values
AI_DIRECTORY_JCOSERVER
Program ID: AI_DIRECTORY_<SID>, where <SID> is the SAP system ID of your SAP XI host
LCRSAPRFC
Program ID: LCRSAPRFC_<SID>, where <SID> is the SAP system ID of your SAP XI host.
SAPSLDAPI
Program ID: SAPSLDAPI_<SID>, where <SID> is the SAP system ID of your SAP XI host.
10. Leave the transaction SM59 open for later tests.
J2EE Configuration for the Destinations (Visual Administrator)
1. On your SAP Exchange Infrastructure central instance host, start the J2EE Engine administration tool.
2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
3. In the section RFC destination, enter exactly the same program ID and gateway options for AI_RUNTIME_JCOSERVER that you used in the step Maintaining the RFC connection above. Additionally, set the number of processes to 10.
4. In the section Repository, do the following:
a. Enter the parameter for the SAP XI host: Application Server, System Number, Client and Language.
b. For User and Password maintain the login parameters for the user SAPJSF.
c. Select the flag Unicode.
6. Choose Set.
7. Repeat the steps 3 u2013 6 for the remaining destinations:
Destination
Values
AI_DIRECTORY_JCOSERVER
u2022 Corresponding values from SM59
u2022 Number of processes: 10
LCRSAPRFC
u2022 Corresponding values from SM59
u2022 Number of processes: 3
SAPSLDAPI
u2022 Corresponding values from SM59
u2022 Number of processes: 3
Testing the RFC Destination
After you have maintained all RFC destinations in both the ABAP and Java environment, you can check all the connections above as follows:
1. Call transaction SM59 again.
2. Open your RFC destination.
3. Choose Test Connection. No error should be displayed.
This will solve your problem.
Thanks
Laxmi Bhushan

Doubt in SM59

Similar Messages

Maybe you are looking for