Problem in Port determination !

Question

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 ?

Answer 1

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 Eskom’s 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 it’s 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 you’ve 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^