RFC Port
Is it necessary to create RFC port when I am sending IDOCS to XI? If no then under what circumstances do we need to create a RFC port. Why do we need to create the distribution model through SALE transaction.
Hi Sonia,
If you are sending IDocs to XI ....
1. You need to maintain a Partner profile for XI in your R3 system using transaction we20.....
2. Now the message type of that IDoc will be listed in the Outbound table of the partner profile.
3.Now the port that entry of messsage type will be using --- should be configured in we21
4. The RFC destination that port will be using should be created using transaction sm59
You dont need to configure any ALE settings at the XI side....
**Reward points if helpful..
Regards,
Sushil.
Similar Messages
-
Why T-RFC Port canu2019t handle Partner Profile Segment Release Version.
Can TRFC Port handle the segment release of each of the segment if configured in Partner Profile.
As per sap, in Partner Profile, if we maintain the two field "Seg. Release in IDoc Type" and "Segment Application release" to a SAP Release lower than the current release version then all the segment populated by the IDoc adapter should be populated as per the lower release structure.
For test Purpose I have created two IDoc using File Port and TRFC port and for both of then I have maintained the Partner Profile Fields "Seg Release in IDoc Type" and "Segment Application Release" as 46C although the latest release is 701.
In the IDoc there is a custom segment ZE1PMX with two Version Release 46C & 701. 46C is having 7 Fields and 701 is having 9 fields.
Test using TRFC Port: Using TRFC port the IDoc that is getting generated are not having the segment structure of release 46C instead of that it is taking the segment structure of latest release 701 which is having 9 fields.
Test using File Port: Using File port the IDoc that is getting generated are having the segment structure of release 46C instead of latest release 701 which is having 7 fields which is desirable.
I have also done these testing in other SAP release like 700 and found that while saving the partner profile with a lower segment release number it throws an warning message as "Segment definitions missing for release 620/620" and IDocs are not getting generated with a error status Code 2 "Segment E1BPMEPOITEM1 is unknown in Release 620 /". But from release 701 sap allows us to save the Partner Profile without warning and also creates the IDoc without error but the segments takes the latest release structure instead of the release maintained in the Partner Profile.
If any one has already done some investigation on this issue please let me know why there is a difference in TRFC Port and File Port. Is there any other configuration that is missing for T-RFC Port.Hi Dennis
This forum is focused on [SAP NetWeaver Gateway|http://www.sdn.sap.com/irj/sdn/gateway], i.e. the (relatively) new OData/REST-orientated mechanism to expose ERP data and functions.
You're talking about the ('classic') Gateway i.e. the service that runs on port 33<SYSNR>. As a result, you are better off posting in the forum that covers that Gateway, i.e. [Application Server Infrastructure|SAP NetWeaver Application Server;
The names do make it confusing, for sure.
Good luck!
dj -
Error when testing INTEGRATION_DIRECTORY_HMI rfc port
hi friends,
I have created a RFC port of type HTTP INTEGRATION_DIRECTORY_HMI it was working fine tillyesterday..
All of a sudden 2day when i am executing the proxy i got error. when i check the rfc is not working.. and giving this error ..
ICM_HTTP_CONNECTION_FAILED
Please suggest me what can i do for that..
Regards
Vijayhi
In my case all the four rfcs
INTEGRATION_DIRECTORY_HMI
2. SAPISU_XID
3. LCRSAPRFC
4. SAPSLDAPI
are working fine..
and now sproxy is not working now ..
Repository Version UNKNOWN
when i check =>Check/maintain with report SPROX_CHECK_IFR_ADDRESS
i am geeting this error.
Regards
Vijay -
Port A000000016 is not an RFC port
Hi,
While configuring ALE/IDOC configuration I am getting below error while distributing Model View.
"Distribution of model view ERECRUIT
Target system QERCLNT300 RFC destination for synchronous communication (message type
SYNCH) Port A000000016 is not an RFC port, or RFC destination
is missing."
I have generated the partner profiles and that is showing port A000000022 is assigned with the rfc. but this Model View is picking A000000016 port again & again and throwing error. This all happened after we did the refresh from prod system.
Will appreciate early help.
Thanks,
KamalTarget system QERCLNT300 RFC destination for synchronous communication (message type
SYNCH) Port A000000016 is not an RFC port, or RFC destination
is missing."
I have generated the partner profiles and that is showing port A000000022 is assigned with the rfc.
but this Model View is picking A000000016 port again & again and throwing error. This all
happened after we did the refresh from prod system.
Go to WE20 and select the partner system to which you are communicating. now select the
message type. You will see the Port that particular Message type is using. *You can add
you A000000022 here for all the message types in the distribution model.* Even if one message
type id using A000000016 it will give the same error.
In addition also check if the port A000000022 has correct RFC Specified thru WE21.
Regards
Shital -
HI Experts,
I have trying to Created RFC Port for ECC to IDOC as TYPE: 3 i have given the all fields and Tested the Connection i got this error:
Connection Error
Error when opening an RFC connection
ERROR: partner 'eccdcs1s:sapgw01' not reached
LOCATION: SAP-Gateway on host gcecc6 / sapgw00
DETAIL: NiPConnect2
CALL: connect
COMPONENT: NI (network interface)
COUNTER: 246
ERROR NUMBER: 10060
ERROR TEXT: WSAETIMEDOUT: Connection timed out
MODULE: nixxi.cpp
LINE: 2764
RETURN CODE: -10
SUBRC: 0
RELEASE: 700
TIME: Fri Jun 25 19:16:36 2010
VERSION: 38
can u please help me out to resolve this problem.
Regards,
-Prabhakar.AHello,
I have given the IP address and tested it is given the following error.
Connection Error
Error when opening an RFC connection
ERROR: timeout during allocate
LOCATION: SAP-Gateway on host gcecc6 / sapgw00
DETAIL: no connect of TP sapdp01 from host eccdcs1s after 20 sec
COMPONENT: SAP-Gateway
COUNTER: 322
MODULE: gwr3cpic.c
LINE: 1872
RETURN CODE: 242
SUBRC: 0
RELEASE: 700
TIME: Fri Jun 25 19:56:47 2010
VERSION: 2
Regard's
-Prabhakar.A -
I created RFC destination and then when I try to create RFC port for the XIServer and I don't see the RFC destination when I click the input help. Is there some equivalent of actiavtion in R3. I went back again in RFC destination and I see the destination is very much there. The name of my RFC destination is ZXISERVER2. Does that make a difference.
Hi Sonia,
To log in to the R/3 or XI system there will different types of users like dialog users,system users.
Dialog users are the one who will log in to the system via log on pad.
System users will log in to the system directly. The system user and password should be provided in the RFC destinations so that it will directly log in to the system during runtime or execution of any interface.
>>i]When I say Remote Connection it shows up as user02 in the logon screen. Why is this happening?</i>
You might have given dialog user id because of this it is showing log on screen again. Ideally it should go through the as u click on the remote connection if u are using system user details.
Regards,
Prasanthi. -
Outbound IDOC( Error passing data to port)
Hi,
We have an interface running daily configured such that the idocs are converted to files and placed on a directory path.
All the idocs are processed successfully but for one hour the idocs failed and the error message says:
Status: Error passing data to port
Error at OPEN (Directory path) with operating system error msg.:No such file or directory.
The missed data from the error idocs have been sent via PFAL.
But again after this one hour the idocs were successfully posted for the same directory path.
Please let me know what the issue can be here or how can we avoid this.
Thanks.Hi
*Some times it may happen that IDOC doesnt reach to the port , in case if you are using Transactional RFC port so*
*you can use the report RSEOUT00 for sending the IDOC to port .*
*Hope it may help you .* -
How many types of ports are there which we use for data transfe in ale/idoc
friends let me know how many types of ports are there which we use for transfering
data in ale/idocs?Hello,
you can use file port,trnasactional RFC port.FI you are using IDOC-XML conversion combination,then you can XML port also.
Thanks -
Collection problem with RFC function module WSDL.
Hi.
I have developed an RFC function module in a SAP system version 4.7 (WAS 620). This FM has 2 table parameters. I have no problem when I see the WSDL in the SAP Web Service Browser.
Another team is trying to consume this RFC FM as a web service from a Java application but they say they can't see the table parameters as collections.
Here is the WSDL of the FM, the table parameters are T_MOVIM and T_ERROR:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="urn:sap-com:document:sap:rfc:functions">
<types>
<xsd:schema targetNamespace="urn:sap-com:document:sap:rfc:functions">
<xsd:element name="ZMMFUSAPTK_0001">
<xsd:complexType>
<xsd:all>
<xsd:element name="GENIDOC" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="T_ERROR">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0012" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="T_MOVIM">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0011" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element name="ZMMFUSAPTK_0001.Response">
<xsd:complexType>
<xsd:all>
<xsd:element name="CODRET">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="T_ERROR">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0012" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="T_MOVIM">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0011" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ZMMTASAPTK_0011">
<xsd:sequence>
<xsd:element name="REFERENCIA" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FECHACONT" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FECHADOC" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CODMOV" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NROPLAN" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NROCOMP" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CLASEMOV" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CENTRO" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ALMACEN" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MATERIAL" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LOTE" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CANTIDAD" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MOTIVOMOV" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CENTROREC" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ALMACENREC" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CENTROCTO" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ORDEN" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TIPOSTK" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NROPEDIDO" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CODCISTERNA" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ZMMTASAPTK_0012">
<xsd:sequence>
<xsd:element name="REFERENCIA" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CODERR" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MSJERR" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="ZMMFUSAPTK_0001Input">
<part name="parameters" element="s0:ZMMFUSAPTK_0001" />
</message>
<message name="ZMMFUSAPTK_0001Output">
<part name="parameters" element="s0:ZMMFUSAPTK_0001.Response" />
</message>
<portType name="ZMMFUSAPTK_0001PortType">
<operation name="ZMMFUSAPTK_0001">
<input message="s0:ZMMFUSAPTK_0001Input" />
<output message="s0:ZMMFUSAPTK_0001Output" />
</operation>
</portType>
<binding name="ZMMFUSAPTK_0001Binding" type="s0:ZMMFUSAPTK_0001PortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="ZMMFUSAPTK_0001">
<soap:operation soapAction="http://www.sap.com/ZMMFUSAPTK_0001" />
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
</operation>
</binding>
<service name="ZMMFUSAPTK_0001Service">
<documentation>SAP Service ZMMFUSAPTK_0001 via SOAP</documentation>
<port name="ZMMFUSAPTK_0001PortType" binding="s0:ZMMFUSAPTK_0001Binding">
<soap:address location="http://dbades00.bue.bemberg.com.ar:8002/sap/bc/soap/rfc" />
</port>
</service>
</definitions>
Should I change something in the definition of the parameters of the FM? or the problem is with the parsing process on the other system?
Thanks in advance.
Fabian.Welcome to SDN.
I am not sure about this particular issue, but i have used WSDL from WAS6.20 system in MS Office infopath to consume webservice where we have had table parameters without any issue.
may be try with office infopath to make sure that the problem is with the WSDL or with the java application.
Regards
Raja -
Setting up the HR-PDC interface to ext. system without direct RFC
Hello,
Setting up the HR-PDC interface to external system without direct RFC - Uploading time events
Following note number 647145, I tried to set up connection to external time collection system. As the external system isn't able to work with RFC, I setup a fileport using transaction WE21. When an outbound IDOC is created with transaction PT80, it will be stored at the outbound path. The IDOC then will be transfered to the external system with a unix script triggered by event.
For inbound IDOCS, the fileport cannot be used as I don't see any way to configure it as the time events that should come in via RFC port, will be uploaded and processed according the ALE distribution model. The BOR object "PTManagerExtPEvent" of type "BUS7014" with method "Insert" is used to insert the time events into the interface table CC1TEV from an HR-PDC certified subsystem. The message type is "HRCC1UPTEVEN".
As standard process won't work in our case, I'd need alternative solution. Actually the time events are send via ftp to the SAP directory that points to incoming IDOC path setup on WE21.
Maybe there should some way to setup RFC connection to own SAP system that points to the SAP directory where the inbound files are stored.
Maybe using the FM IDOC_INPUT_HRCC1UPTEVEN can be used to trigger the upload manually but first the files have to be uploaded from file similiar to report RSEINB00. Testing this report using the SAP directory and port where the inbound files are located I get error message that IDOC control record is missing, that seems to be understandable as this report is used to upload IDOCS from file but HR-PDC upload file HRCC1UPTEVEN01 has no specific IDOC segments in this moment as it was created according specific HR-PDC interface description. The IDOC in the standard process will be created with the BAPI.
As I'm new in HR and ALE, I'd be grateful for any help on this matter.
Best regards
AndreasHello Andreas,
thanks for Your contribution. Recently I've got the trial version and made some tests and found out that the bapi-handler works perfectly for managing HR-PDC interface.
Nevertheless actually there's no compilation for OS/400 and the AS/400 I'm working with has an old OS release without C compiler and furthermore RFC libraries of SAP cannot be installed on this release.
The Bapi-handler for testing runs on Windows
and I'd need an intermediate machine to manage the data between AS/400 and SAP. I'd prefer direct connection between timecollection subsystem and SAP for obvios reason.
Regards
Andreas -
Hi experts,
Q1. What are the configurations steps (Transaction codes) required at R/3 and XI while sending the IDOC to XI? Please provide the list of TCodes required at both sides. if any weblog is exists which provides detail explanation on IDOC scenarios plz provide the path.
Q2. While sending the IDOC we need to generate partner profile and port. How many types of port exist and wht each port represents?
Q3. In RFC Sender Adapter we need to create RFC port in R/3 and there we specify Connection type as T which TCP/IP why we use connection type T instead of 3 (which represents connection type as R/3). While communicating with SAP systems we need to specify the connection type as 3.
Q4. How many types of partner profiles exist and wht each type represents?
Q5. How to transport design, configuration objects and SLD objects from Development system to Quality system. Please provide me the steps to transport the objects?
Q6. Once the objects are transported a .tpz file is created wht is the purpose of the file and where it will generated? Suppose if Ive transported the namespace from Dev to Quality system then at quality side to which SWC this transported namespace is assigned. Do we need to create any SWC at quality system side?
Cheers
FaisalHi Abdul,
for the first one u need to create a logical system and assign that logical system and need to create a port and partner profile and distribute the system,, for that follow this blog
Steps
SAP XI
1) RFC Destination (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.
2) Create Port (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 (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
2.& 3 ) for the 2nd question the answer was in above u need to create the partner profile and port.
port can be created as HTTP Port and RFC port which are used to communicate with the R/3 server and depends on the requirement we need to choose the port..
4. partner profile creation depends on ur scenario, it is a custmized one it purely depends on the customer requirement, there is no specific partner profiles exists in R/3.
5. For transportation u may choose File level transport or CMS, if u trnasfer through File level it is very easy to maintain and reimport in the production server,, just while exporting from the development server a .TPZ file was created and import this .TPZ file in the production server this gives the entire objects of IR and ID, but when u deal with SLD instead of .tpz there u will be creating .zip file, so u neeed to reimport the file in the production server..
6. The .TPZ file will be created when u export the objects either in IR and ID..., so as i explained in the above point it will go top the export directory of development server and import in production server with IMPORT directory..
regards,
Kishore -
Problem in Port determination !
Is there any specific port already exists for the sender and the receiver While configuaring ALE ?
Where tje RFC call is only through TCP/IP connection or any other protocol is used like R3 ?hi
good
check this probably this would help you
Create background ALE user
An ALE background user ALE-BATCH needs to be created on EVERY client that needs to be ALE enabled. The ALE-BATCH user needs SAP ALL rights.
The Finesse standard for passwords for all ALE-BATCH users is init (without the quotes).
2.2. ALE Administrator position
The ALE administrator position needs to have been created, on each client, and the responsible persons linked to it. Please refer to the workflow procedures as to how to do this. These positions should then be documented on the respective Visio diagram for the particular client series currently being implemented.
Currently the Position is 50000085.
Please refer to the ALE Administrator Troubleshooting procedure should you suspect that something is functionally wrong once the ALE config is up and working.
2.3. Set up logical system
The distribution of systems makes it necessary to be able to identify every system individually within a network. The "logical system" is used to do this.
A logical system is an application system within which the applications are co-ordinated to work in one database. In the SAP sense of the word, a logical system corresponds to a client.
A logical system needs to be set up for each client that the system, on which you are working, needs to communicate to via ALE. In Eskoms case from 4xx to each of the group clients.
In the following steps, you must define every client as a logical system by first of all defining logical systems and then assigning the clients in question to the corresponding logical systems.
Note:
Assignments must be unique (that is, a client may only be assigned to one logical system.
Several clients must never be assigned to the same logical system.
The same applies to pre-production systems and production systems: the pre-productive system must be assigned to a different logical system than the productive system.
2.3.1. Maintain logical systems (Client independent)
1. In the IMG, choose Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Set up logical system -> Maintain logical systems
2. To create a logical system, choose Edit -> New Entries.
3. Enter a name for the logical system according to the ALE Naming Standards document
4. Enter a clear description for the logical system. If you want to change this short text for a logical system, please proceed as follows:
a) Select the appropriate line.
b) Choose Edit -> Change field entries.
5. Enter the new short text.
6. Choose Replace.
7. Save your entries.
8. Repeat steps 2-4 for the 6 different clients (4xx - 9xx).
2.3.2. Maintain Dummy Client Logical Systems (Client independent)
This is required for the internal charges-within purchasing and selling scenarios. Dummy clients should only be created for the corresponding group clients, not for reference clients or consolidation clients. Should be created on the Reference client system as well as the applicable group system. Refer to the ALE Dummy Client Configuration Guide for further information.
1. In the IMG, choose Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Set up logical system -> Maintain logical systems
2. To create a dummy logical system, choose Edit -> New Entries.
3. Enter a name for the dummy logical system according to the ALE Naming Standards document. For example DUMF01C700.
4. Enter a clear description for the dummy logical system. If you want to change this short text for a logical system, please proceed as follows:
a) Select the appropriate line.
b) Choose Edit -> Change field entries.
c) Enter the new short text.
d) Choose Replace.
5. Save your entries.
6. Repeat steps 2-4 for the other 3 group clients.
2.3.3. Allocate logical systems to the client
This step only needs to be performed for the clients that reside on the box where you have just created the logical systems. For those logical systems that refer to clients that exist on other systems, the logical system will be linked to the client on its respective system. Eg. ALEF01C400 will be linked to client 400 on system F01.
1. In the IMG, choose Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Set up logical system -> Allocate logical system to the client
2. Select the relevant client.
3. Choose: Goto -> Detail. You branch into the detail screen.
4. In the field Logical system, specify the name of the logical system to which you want to assign the selected client, as per the naming conventions.
5. Save your entries.
2.4. Maintain number range for ports
The ALE interface generates ports automatically. The EDI interface assigns numbers internally for these ports. Hence the ports can be identified explicitly.
The system can only generate the numbers if a number range is entered for the number range object EDIPORT in number range 01.
Check first whether a number range in the number range 01 exists for the number range object EDIPORT. Proceed as follows:
2.4.1. Procedure
1. In the IMG, choose Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Maintain number range for ports
2. Perform function. The screen for number range object maintenance appears. The object name EDIPORT has already been pre-set.
3. Choose Goto -> Number ranges -> Interval -> Display. An interval must be entered for number range number 01. If no interval is entered, proceed as follows:
4. Go Back and choose Interval -> Maintain.
5. Enter a number range for number range number 01
6. Choose Interval -> Check to check whether your entry is error-free.
7. Save your entry.
2.4.2. Notes on the transport
You transport number range objects as follows:
In the initial screen, choose "Interval - Transport".
Note that all intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.
Dependent tables are not transported or converted.
2.5. Maintain number range for IDocs
Numbers are assigned internally for sent and received Intermediate Documents. This way the Intermediate Documents can be identified explicitly.
The system can only generate the numbers if a number range is entered for the number range object EDIDOC in number range 01.
2.5.1. Procedure
Check first whether a number range exists in number range 01 for the number range object EDIDOC. Proceed as follows:
1. Perform function for EDIDOC. The screen for number range object maintenance appears. The object name EDIDOC has already been pre-set.
2. Choose Goto -> Number ranges -> Interval -> Display. An interval should be entered for number range number 01. If no interval is entered, proceed as follows:
3. Go Back and choose Interval -> Maintain.
4. Enter a number range for number range number 01.
5. Choose Interval -> Check to check whether your entry is error-free.
6. Save your entry.
2.5.2. Notes on the transport
You transport number range objects as follows:
In the initial screen, choose "Interval - Transport".
Note that all intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.
Dependent tables are not transported or converted.
2.6. Maintain number ranges for IDoc types and segment version
Settings which are defined in the EDI area are to be maintained here.
2.6.1. Number ranges for Intermediate Document types
If you made customer enhancements to Intermediate Document types and a new version of R/3 is imported, automatic merging of the new versions of the basic IDOC types (from SAP) and your customer enhancements is carried out.
For this merging, the EDI interface assigns numbers internally for Intermediate Document types, for unique identification.
The system can only generate the numbers if a number range is entered for the number range object EDIDOCTYP in number range 01.
2.6.2. Procedure
Check first whether a number range interval in the number range 01 exists for the number range object EDIDOCTYP. Proceed as follows:
1. In the IMG, choose Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Maintain number ranges for IDocs types and segment
2. Perform function.
3. The screen for number range object maintenance appears. The object name EDIDOCTYP has already been pre-set.
4. Choose Goto -> Number ranges -> Interval -> Display. An interval must be entered for the number range 01.
5. If no interval has been entered, proceed as follows:
6. Go back and choose Interval -> Maintain.
7. Enter a number range interval for the number range 01.
8. Choose Interval -> Check to check whether your entry is error-free.
9. Save your entry.
2.6.3. Notes on the transport
You transport number range objects as follows:
In the initial screen, choose "Interval - Transport".
Note that all intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.
Dependent tables are not transported or converted.
2.7. Maintain number range for change pointers
In this section, the number ranges are maintained for the change pointers.
The change pointers are needed to generate Intermediate Documents from the application documents. For these pointers, internal numbers are assigned for unique identification. The system can only generate the numbers if a number range is maintained in number range 01.
Example
Number range From number To number
01 0000100000 1000000000
Standard settings
SAP delivers the number range for change pointers.
2.7.1. Procedure
If you must create number range 01, proceed as follows:
1. In the IMG, choose Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Maintain number range for change pointers
2. Perform function. The screen for number range maintenance appears. With Interval -> Display, you can see whether a number range was already maintained.
3. If no number range is maintained, choose Interval -> Maintain.
4. In the "Maintain Intervals" screen, choose Edit -> Insert interval.
5. Enter the number of interval 01 and a number range. Finish the entry with Insert.
6. Choose Interval -> Check to check whether your entry is error-free.
7. Save your entry.
2.7.2. Notes on the transport
You transport number range objects as follows:
In the initial screen, choose "Interval - Transport".
Note that all intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.
Dependent tables are not transported or converted.
2.8. Set up ISO codes
Currencies, units of measurement and country codes are held as international standardised ISO codes so that all messages sent can be understood on any system. This means that the ISO codes have to assigned to the SAP-internal units as necessary.
Note that this procedure is usually performed by a functional team.
2.8.1. Procedure
Define the ISO codes for the units in use here.
Use the following IMG functions for this:
In the IMG, choose Cross-Application Components -> Distribution (ALE) -> Basic Configuration -> Set up ISO codes
OR
Currencies:
Global Settings -> Currencies -> Check currency codes
Units of measurement:
Global Settings -> Check units of measurement
Countries:
Global Settings -> Set countries -> Define countries
2.9. Make basic settings for Workflow
The workflow runtime environment has to be set up in each client. Workflow will be used for error handling in ALE. Technical errors are distinguished from application errors and each type of error (technical/functional) can be sent to a different person/role in the organisational structure.
The setting up of the workflow runtime environment will be covered in a procedure that explains how to set up workflow on SAP. When the actual document becomes available, it will be referenced from here.
2.10. Deleting change pointers copied from source client
When a client is created using a client copy, some open change pointers may be copied from the source client that are actually not needed in the target client. These unwanted change pointers can be deleted by running a program RBDCPCLR, or executing transaction BD22. This program will only delete unprocessed change pointers.
To clear all change pointers (including the unprocessed change pointers) run transaction ZCPC, or program ZCPCLEAR.
2.11. Archiving Idocs copied from source client
Because Idocs are client dependant, they get copied to the target client from the source client with a client copy. Whenever a client copy is done, these copied Idocs need to be archived and deleted to remove them from the newly created client.
Refer to the Idoc archiving strategy and procedure for the procedure to archive Idocs. When archiving and deleting Idocs in a newly copied client, all Idoc statuses must be enabled for archiving (to ensure that all Idocs are archived and deleted), refer to section 2.2 of the Idoc archiving strategy and procedure document (transaction WE47).
2.12. Activating change pointers
If you want to be able to distribute changes to master data, you must write change pointers at the same time as the change documents.
If you want change pointers to be written by the system, you must maintain a number range for them. This can be done in the section Number ranges -> Maintain number range for change pointer.
Once youve activated the change pointer for the particular message type then any changes made to this master data will have an IDoc automatically generated and forwarded according to the distribution model.
2.12.1. Procedure
In this section it is possible to activate the writing of change pointers. This activation must be done at two levels (general, per message type).
Execute function in IMG: Cross-Application components -> Distribution (ALE) -> Distribution Scenarios -> Master data distribution -> Activate Change pointer -> Activate change pointer (generally).
Check the box to activate.
2.13. Define RFC destination
In this section, you define the technical parameters for the RFC destinations.
This must be set up for all the logical destinations manually. RFC destinations are client independent.
The Remote Function Call is controlled via the parameters of the RFC destination.
The RFC destinations must be maintained in order to create an RFC port.
The name of the RFC destination should correspond to the name of the logical system in question. EG. ALEF01C410
2.13.1. Procedure
1. Execute SM59
2. Click on R/3 links and choose Edit -> Create;
3. The RFC destination name must be the same as the logical system name in order for the port to be automatically generated.
4. The type of RFC destination is 3.
5. Enter the required parameters dependent on the type.
For an R/3 link, that is, for example, the name of the RFC destination, the name of the partner machine, logon parameter ALE-BATCH with password init.
6. Select the Destination -> TRFC options function from the menu.
7. Enter the value 'X' into the 'Suppress backgr. job in case of comms. error' field.
8. Save and exit.
2.14. Define RFC destination for Dummy Clients
In this section, you define the technical parameters for the dummy client RFC destinations. This must be set up for each dummy logical system created previously. RFC destinations are client independent.
The Remote Function Call is controlled via the parameters of the RFC destination.
The RFC destinations must be maintained in order to create an RFC port.
The name of the RFC destination should correspond to the name of the dummy logical system in question.
2.14.1. Procedure
1. Execute SM59
2. Click on R/3 links and choose Edit -> Create;
The RFC destination name must be the same as the logical system name in order for the port to be automatically generated.
3. The type of RFC destination is 3.
4. Enter the required parameters dependent on the type.
5. For an R/3 link, that is, for example, the name of the RFC destination, the name of the partner machine, logon parameter ALE-BATCH with password init.
6. Select the Destination -> TRFC options function from the menu.
7. Enter the value 'X' into the 'Suppress backgr. job in case of comms. error' field.
8. Save and exit.
2.14.2. Notes on the transport
The maintenance of the RFC destination is not a part of the automatic transport and correction system. Therefore the setting has to be made manually on all systems.
thanks
mrutyun^ -
Schedule Receiver RFC communication channel to call R3 RFC-FM.
Hi,
I have requirement that I need to schedule/trigger from PI to RFC call R3 function module. Wonder if anyone here has done similar thing before? I tried to use ATP (Availability time planning) in RWB. But this seem does not success for me as there is no response and error message for this.
Below is my configuration detail:
Configured:
1. Receiver communication channel - RFC
2. Receiver agreement with the RFC message type assigned.
3. Scheduled receiver RFC communication channel via ATP daily
*(It is possible to make scheduling job in R/3 but we are not considering this way)
Please let me know if anyone has done this before or any other suggestion to do the scheduling from PI.
Thanks!
Regards,
SPHi SP,
As you mentioned, ATP would allow adapter to be open and in start state. Adapter's RFC, SOAP, JMS would need some other application to trigger the message processing because these are not like pooling adapter's File, JDBC and Mail. RFC adapter channel always listening to the RFC port and FM execution. Once FM from R/3 executed then the RFC adapter would trigger it's message processing.
For Sender RFC channel: In order to trigger the RFC adapter execution at particular time then you should write a simple ABAP code which would act a batch application and which does the triggering the FM and Sender RFC channel.
For Receiver Channel: For Receiver RFC channel it's bit trichy because here you have force Receiver RFC adapter to connect backend the execute or initialize the variables without having any XI message triggered from Sender PI channel.
I have 2 ideas:
1. A little difficult approach, similar to the ABAPbatch code, you need to write a java adapter module which can trigger RFC receiver channel to connect and do an initialisation at FM at regular interval.
2. Simple approch configure a File-> 2-> RFC receiver scenario, configure File sender adapter to pick a dummy file at regular interval and RFC receiver channel does the rest.
Please let me know still you have any doubts,
Thanks,
RK -
I am using Seebeyond as middleware and it sending Vehicle IDoc VEHCLE01 to SAP System.
Please help me
what should port type I need to use? Should it be file port or t-rfc port?
What should partner type need to use? Can it be LS type?
Is it ALE or EDI Scenario?
Thanks in advance.Hi,
Yes, the Port can be a File Port (IDocs will be saved in this folder) or t-rfc port. File port should be OK.
Partner Type can be LS.
Cheers,
Bhanu -
Create a RFC connection of type ABAP pointing to nowhere?
Hi guys
I would like to create a RFC destination of type ABAP pointing to nowhere. IDocs sent to a transactional RFC port using this RFC destination shall be listed as processed successful but they shall disappear and not be transported to the target system.
Does anybody have an idea?
Thanks and regards
MarkusThink this won't work because tRFC will wait for a commit from the receiving system. You won't get it and the messages will stuck in SM58...
Regards,
Kai
Maybe you are looking for
-
Vendor wise drill down in Trial Balance or Balance sheet report
Dear Experts, Is there any report for Trial Balance or P&L/ Balance Sheet report where vendor wise drill down of amounts is possible? Please suggest. Regards Komal
-
Revenue recognition at the time of Delivery - COPA
Dear Gurus, Our sales cycles are bit different than the standard sales process. In one of the sales cycle the business does the Billing first and delivery later and the revenue recognition should happen at the time of delivery not billing. How do I a
-
Display file count on time machine
How can I see how many file are still remainingfom being backuped? When you run time machine for the first time you could see how many files ar left, but once you use TM over and over... Where can find that information?
-
When I export to .h264 it says .mp4 and has been exported with .mp4 before, but now when export to .mp4 the file become an m4v file that I can not use. It works with some projects, and this particular project has worked before. Any idea what I´m doi
-
Will not install despite using cloud cleaner
I have uninstalled Adobe Elements 11and deregistered it from my old PC. On my new iMac I uninstalled it because Parallels Desktop automatically installed all my old programs on my mac when I installed Windows 7 on it. I am now trying to install Adobe