ALE Configuration problem in FI

Hi all,
I need some help on a solution to set up for FI doc ALE distribution using standard tools.
The goal is to send Invoice Documents (FB60) from an R/3 to another external R/3 system via IDoc, using standard messages, functions, etc.
I am looking for some guidelines and technical explanation on how I should proceed.
I saw that message type FIDCMT should be used. Do I need to enhance User Exit EXIT_SAPLF050_007?
I found some explanations in OSS Note 114814 and on other forum threads but I am kind of confused on what I need to do exactly. Some setups in BD64 were described in other threads, is that relevant?
Thank you in advance for your answers.
Regards,
Sylvain

first of all u have to find out the user exit.and then if u need to add fields ,then u can write the code here. and then determine the outbound partner profle using tcode WE20. AND then u can u can assign those things in bd64 bussiness model.and if need filters u can set there.
Regards,
Jampani.

Similar Messages

ALE Configuration problem

Hi All,
I have to send idoc from R/3 to R/3.
For this i have created logical systems(D100 and R200) in both the clients(100 sender and 200 Receiver ). I am able to remote login from sender and receiver systems.
I have created the ports in both the systems with the sender and receiver logical system as the RFC destination for receiver and sender system. In sender RFC destination will be R200 and in receiver system RFC destination will be D100.
I have created partner profiles with the logical system names (D100 and R200) in both the clients.
In sender sytem, i have created outbound parameters and in receiving system i have created inbound parameters. I have used MATMAS as message type and MATMAS05 as basic type in sender outbound parameters.
I have created Model view distributer ( BD64) in both the clients.
I am able to remote login from both sender and receiver systems.
Now i am going to WE19 and selecting the basic type as MATMAS05 and executing. there i have to select the sender and reciver details. Here i am unable to get the receiver port details, and i am unable to send the idoc. Can anyone ple let me know whats missing here... if my process is completely incorrect, pls send the complete configuration that needs to be done on sender and receiver systems so that i can send the idoc.
Thank,
Raju

Hi Raj,
After going through your post, I came to know that you are trying to create an IDoc by using WE19 tcode. Usualy, WE19 is used for analysis of existed IDoc.
1.
Here, you have tried this to create an IDoc with message type MATMAS05. After excuting the first screen of we19, you wil be getting the empty structure of the IDoc. There you have to fil the Control Reccord and DataRecords. Till this point you were suceeded.
The issue came into picture while you are going to fill the Cotrol Record. It is not giving you the tRFC port name in F4 help. Here, in this case, you have to provide manually the tRFC name which you created. You manually fill the selected segments.
2.
The other issue is with the partner profile. Here you have created partner profiles(not generated from Distribution model) . After creating the partner profiles we usualy forget to test them.
To test the Partner Profiles execute the programme RSECHK07 and give the partner profile names which you created. It will clearly give the analysis.
By doing this, the post may be solved. HOpe you have understand and might be helpful.
Thanks
Ram.

Problem in ALE configuration

Hi ,
I am doing ALE configuration to transfer the Vendor information from 800 client to 700
client.
In client 800 while I am creating partner function I am getting
error...Could you please help me to resolve.
In "Generate Partner Profile" (in 800 client)
I have given ....
Model View : "VENDMODEL1"
Partner System : IDES_700
Next screen "log for partner profile generation is displayed"
Partner
No error is displayed here...
But in "port"
the following message is displayed....
System IDES_700   : Port could not be created
                    RFC destination IDES_700 not specified for system
ides_700
              Enter the RFC destination and restart the generation
After creating Model view with Sender and Receiver with Message type as CREMAS
what we have to do...
whether we have to distribute it ..
I am getting error log as ...
Targert system IDES_700 : RFC Destination for Synchronous
communication(message type SYNCH)
                  Partner Profile LS IDES_700 SYNCH does not exist
please help me in this regard
With Regards,
Sagar.

Hi,
Please ensure the RFC destination for both logical system (client 800 and 700) are created in SM59.
Also you can add manually message type SYNCH with IDoc type SYNCHRON in the partner profile (WE20) prior to generate partner profile for message type CREMAS via BD64.
Message type SYNCH is a dummy message type for determination of RFC destinations and IDoc type SYNCHRON is a dummy IDoc type for synchronous communication.
You can setup something like this.
Outbound parameter options:
Field          Value
Message type   SYNCH
Receiver port A000000015 (Transactional RFC)
PacketSize     100
Output mode    Transfer IDoc immed.
Basic type     SYNCHRON
Hope this will help.
Regards,
Ferry Lianto

ALE Configuration Again !!!

Hi All,
I am trying to do ale configuration for idoc to file scenario. I created two RFC connection one for XI system and one for R3 system. Then I created ports for both the RFC. After that I created two Logical system having same name as the two RFC above. But as per the instruction , i should assign client to above logical system. But problem is that the client number ie 030 is already defined to R3 system. My XI system have same client id, so when i am trying to assign client 030 to XI logical system, it is giving as client number is already present. I don;t understand the logic of assigning client to LS.
what should i do here?
Second thing: Can we create more than one logical name for the same system. I asked this because in the RFC list of R3 system, i already have RFC for R3 system , logical name is also present. So can i create another logical system for R3 system?
Ranjeet Singh.

An excerpt from SAP documentation on Logical System Names.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: <System-ID>CLNT<Client>. Refer to url
http://help.sap.com/saphelp_nw04/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
SCC4 should already have been set. So I assume that you are creating your logical systems in the IMG to then assign in WE20 (Partner Profiles). As the XI SystemID will be different to your R3 SystemID, CLNT should not be an issue.
If not then please clearly define the issue to include where you want to create the logical system and which way your IDOC will travel. We currently send IDOCs from CRM to XI and vica versa

ALE Configuration for Transactional Data (Purchase Order)

Dear Experts,
I want to configure ALE for Purchase Orders(Transactional Data).
For that:
I have done neccessary Condition Records at NACE with necessary Output Type Configuration. Configured Port and Partner Profile with Message Types: ORDERS and ORDECHG (as Outbound Parametrs) .Assigned those Message Types against defined Sender and the Receiver at Customer Distribution Model . Configured Port and Partner Profile at the Receiver System also.
Now I have 2 queries.
i) Is this much of ALE configuration is enough for Transactional Data for communication between 2 systems or I have to do something more?
ii) For Master Data we configure Change Pointer(we can see field assignments against Change Document Object at BD52 for Master Data Messaage Types) . Is it necessary to configure Change Pointer for Transactional Data or it will autometically handled by the system(field assignments cannot be seen against Change Document Objects at BD52 for Transactional Data Messaage Types)?
Regards
Arnab

Hi kumar,
what Alexander said is absolutely correct .
from your second question no master data distribution configuration is required for the transactional data distribution.
let us know once if you face any problems.
~linagnna

ALE Configuration SET UP

Hi,
I am creating a ALE Scenario with Material Master. I am doing this for the first time. Please tell me whether it is possible to trasfer data from a sandbox(UPG) system to a development system. If this is possible, what are the configuration steps i need to do in bothe the system to trasfer data from sandbox to Development system. thse two systems are physically independent systems.
Thanks
Jiten

Hi Jitendra,
Before you Configure go through this, If you need any clarification contact me.

ALE Scenario Development Guide
To develop a new custom ALE scenario, comprises 5 steps:
1. Design and develop the custom IDoc with its segments and a new message type
2. Configure the ALE environment with the new IDoc and message type (customer model, partner profiles and linking IDoc to message type)
3. Develop the outbound process which does the following:
 Populates the custom IDoc with control info and functional data
 Sends the IDoc to the ALE layer for distribution
 Updates status and handles errors
4. Configure the ALE inbound side (partner profiles with inbound process code)
5. Develop the inbound process which does the following:
 Reads the IDoc into a BDC table; selects other data that is required
 Runs transaction using call transaction or BDC session
 Updates status and handles errors
Below is a pictorial representation of the flow of a complete ALE scenario from the sending system to the receiving system.
Figure 1: ALE Scenario model
1.1. ALE Example
For the purposes of this example we will develop a small ALE scenario. This scenario is described below.
The receiver of an internal service must be able to reverse (cancel) the invoice receipt which will then cancel the applicable billing document automatically on the service providers system.
Figure 2: Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
 Working ALE environment - See ALE Basis Configuration Guide;
 ALE scenario design together with the business requirement;
 Development access; and
 ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
 Segment fields
 LIFNR Vendor account number
 XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
 Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
 Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
 Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
 Click on ZINVRV01 and then on the Create icon
 Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
 Enter a description for your segment type and create
 Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
 Save and generate, press back
 To release the segment choose Goto, Release from the menu
 Check the box on the line of your new segment
 Save, back and enter
 Your IDoc type structure should be displayed with your new segment
 Save and back
 To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
 Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
 Choose Create logical message type by double clicking on it
 Click on change icon to enter change mode
 Click on New entries to add a new type
 Enter the required message type, in our case it is ZINVRV and an appropriate description
 Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
 Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
 Click on change icon to enter change mode
 Click on New entries to create the link
 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
 Save and exit
 Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
 Click on change icon to enter change mode
 Click on New entries to create the link
 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
 Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
 Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
 Type in your message type ZINVRV and press enter
 Click on New entries
 Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
 Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
 Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
 Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
 Choose the receiving systems to which the sending system must forward message type ZINVRV to.
 For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
 Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
 Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
 Make the settings for the communication with the other decentral systems, you have not set them yet.
 Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
 Create the output partner profile.
 Distribute the customer model
 Specify the name of the customer model.
 You must specify the target system to which you want to distribute the customer model.
 You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
 Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
 The customer model must be maintained.
 RFC destinations must be maintained.
 The customer model must be distributed.
 To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
 populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
 populates the control record info with the message type and IDoc type; and
 calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
*--- Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
 C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
 C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
 Z1INVRV LIKE Z1INVRV,
 C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
 IDOC_CONTROL LIKE EDIDC,
 T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
 IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
*--- Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
*--- Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
*--- Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
*--- Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
*--- Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
 EXPORTING
 MASTER_IDOC_CONTROL = IDOC_CONTROL
 TABLES
 COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
 MASTER_IDOC_DATA = IDOC_DATA
 EXCEPTIONS
 ERROR_IN_IDOC_CONTROL = 1
 ERROR_WRITING_IDOC_STATUS = 2
 ERROR_IN_IDOC_DATA = 3
 SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
 OTHERS = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
 populates a BDC table with the IDoc info;
 calls the transaction via a BDC call; and
 updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
*--- Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
 LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
 CASE IDOC_DATA-SEGNAM.
 WHEN C_SEGNAM.
* Here we get the info from the idoc table
 IT_Z1INVRV = IDOC_DATA-SDATA.
 ENDCASE.
 PERFORM REV_INV.
 ENDLOOP.
 PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
*--- Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
*--- Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
*--- Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
*--- OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
*--- Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
*--- Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
*--- Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
 CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = 'ZINVRV'
 USER = C_ALE_USER
 KEEP = 'X'.
 CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = C_TCODE
 TABLES
 DYNPROTAB = BDC_TAB.
 CALL FUNCTION 'BDC_CLOSE_GROUP'
 EXCEPTIONS
 NOT_OPEN = 1
 QUEUE_ERROR = 2
 OTHERS = 3.
ELSE. "No problems
 C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
 SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
 Select from the sales document table to get user status number
 SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
 POSNR = VBRP-AUPOS.
 Select from the status table to change the user status to pending
 SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
 STAT LIKE C_USER_STATUS.
 IF JEST-STAT = C_US_PENDING. "User status is pending
 JEST-INACT = C_UNCHECKED. "Make pending the active status
 UPDATE JEST.
 C_EXISTS = 'Y'. "I.E. An entry is already in table
 ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
 JEST-INACT = C_CHECKED. "Make everything else inactive
 UPDATE JEST.
 ENDIF.
 ENDSELECT.
 IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
 JEST-OBJNR = VBAP-OBJNR.
 JEST-STAT = C_US_PENDING.
 JEST-INACT = C_UNCHECKED. "Make pending the active status
 INSERT JEST.
 ENDIF.
 ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
*--- Now we check the CALL TRANSACTION return code and set IDOC status
 CLEAR IDOC_STATUS.
 IF RETURN_CODE = 0.
 WORKFLOW_RESULT = '0'.
 IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
 IDOC_STATUS-STATUS = '53'.
 IDOC_STATUS-UNAME = SY-UNAME.
 IDOC_STATUS-REPID = SY-REPID.
 IDOC_STATUS-MSGTY = SY-MSGTY.
 IDOC_STATUS-MSGID = SY-MSGID.
 IDOC_STATUS-MSGNO = SY-MSGNO.
 IDOC_STATUS-MSGV1 = SY-MSGV1.
 IDOC_STATUS-MSGV2 = SY-MSGV2.
 IDOC_STATUS-MSGV3 = SY-MSGV3.
 IDOC_STATUS-MSGV4 = SY-MSGV4.
 RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
 RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
 APPEND RETURN_VARIABLES.
 ELSE.
 WORKFLOW_RESULT = '99999'.
 IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
 IDOC_STATUS-STATUS = '51'.
 IDOC_STATUS-UNAME = SY-UNAME.
 IDOC_STATUS-REPID = SY-REPID.
 IDOC_STATUS-MSGTY = SY-MSGTY.
 IDOC_STATUS-MSGID = SY-MSGID.
 IDOC_STATUS-MSGNO = SY-MSGNO.
 IDOC_STATUS-MSGV1 = SY-MSGV1.
 IDOC_STATUS-MSGV2 = SY-MSGV2.
 IDOC_STATUS-MSGV3 = SY-MSGV3.
 IDOC_STATUS-MSGV4 = SY-MSGV4.
 RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
 RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
 APPEND RETURN_VARIABLES.
 ENDIF.
 APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
 Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
 Select an entry (EG. IDOC_INPUT_ORDERS) and copy
 Type in module name Z_IDOC_INPUT_ZINVRV
 Type in basic IDoc type as ZINVRV01
 Type in message type as ZINVRV
 Type object type as IDOCINVOIC (Invoice document) - Used for workflow
 Direction should be set to 2 for inbound
 Enter and save
3.2.2. Define FM settings (BD51) Client independent
 Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
 Click on New entries
 Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
 Enter 0 for mass processing in the output column
 Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
 Log on to the appropriate receiving system client
 Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
 Choose Inbound with ALE service
 Choose Processing with function module
 Click on Processing with function module and choose create icon
 Click on New Entries
 Type in process code ZINR and give it a description and save
 Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
 Enter your process code ZINR
 Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
 Enter IDPKFIDCMT in object type
 Enter MASSINPUTFINISHED in End event
 Enter IDOCINVOIC in IDoc object type
 Enter INPUTERROROCCURREDFI in IDoc start event
 Enter INPUTFINISHEDFI in IDoc End event
 Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
 Add the message type ZINVRV with process code ZINR.
 Enter the output mode (background, immediately) for inbound processing and NO message code.
 Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.

Thanks.
Manju.
Reward Points.

ALE Configuration HCM - Program read table idoc_structure error

Hello SCN community,
I have small problem with ALE Configuration of HRMD_A message type. I created extension named 'ZRMD_A06'.
When I'm trying to run t-code: bd21 (report RBDMIDOC)
I'm getting following error message:
At the beginning I thought there is problem with segment structure of Z1P2006 of extension 'ZRMD_A06'
I compared segment Z1P2006 with structure 'P2006' in se11 - and it is the same.
Next I checked the bd21 transaction in debug mode.
I figured out that there is error in FM 'RH_MASTER_IDOC_DISTRIBUTE_HRMD' in include 'LRHALF10'.
Could you please help me?

Hello,
Thank you all for your help.
I'm writing this post to provide solution for others like me.
To solve this problem you need to apply this sap note:
HR-CA-ALE: Segment Z1Pnnnn prevents distribution
for me:
As of Release 4.6: In the customer enhancement RHALE001, fill the function exit EXIT_SAPLRHA0_004 with the line
F_idoc_control-cimtyp = 'ZRMD_AXX'.
steps:
1. Go to SE37
2. Enter EXIT_SAPLRHA0_004
3. Double click on INCLUDE ZXHALU08 . (in my case)
4. Add to the code this line: F_idoc_control-cimtyp = 'ZRMD_A06'. (ZRMD_A06 - because I called so my custom extension)
5. and have a nice day because you solved this problem!

Homogeneous System Copy - Remaining ALE Configuration

We made a system copy of an R/3 HR productive system to a new server for testing purpose. The system copy was made with a backup / restore procedure. Now, the new server in online and is working fine. The problem starts when we want to make the accounting payroll. This process needs financial data from R/3 Finance system via ALE to make the accounting. So we decided to connect this new test system with our R/3 Finance QAS system, via ALE, to make possible the extraction of the data needed.
When running the accounting payroll process, we get the following error: "RFC Destination is not maintained for object BUS6004 and method check" and the accounting is canceled. We noticed that the system is trying to use a RFC which its destination is R/3 HR Productive system. Obviously, we deleted the RFC connection pointing to the real productive system to prevent any damages. Also, we checked the ALE configuration and everything is OK (Transactions: BD97, WE20, WE21). But, when we checked the consistency of the ALE configuration, in transaction BDM5, we noticed that there is another ALE configuration defined, which is pointing to the R/3 HR Productive system. It seems that the system copy brings all the definitions of the ALE configurations that were defined in the original R/3 HR productive system. However, this new system is using these settings for connecting via ALE. There is a way to delete or disable these old settings defined in this new system? When making a system copy, there is a way to avoid copying the ALE configurations defined in the source system?

You have some options here ie after system copy
- Before starting the background process (ie #rdisp/wp_no_btc)
- Start SAP system, execute sm59 and append to all the <destination/target> with <destinaion/target>_no connect for each RFC. This way the connections won't happen
- Save
- Stop SAP
- remove # frm rdisp/wp_no_btc
- Restart SAP
whenever you want to try a connection then will remove the _NOCONNECT and it connect
or
you have a table RFCDES, which can be disabled (i haven't tried this).
Cheers

Issue with ALE configuration for creating the idoc for Purchase orders

Hello,
I am trying to send the purchase order through message type configuration using ALE.
I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
I have done ALE distribution using BD64.
Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
In NAST table, the entry is there but on executing RSNAST00 nothing happens.
Please provide me the pointers to solve the given problem.
Regards,
Mayank

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

Good afternoon.I have a computer with W Vista 8, Windows office home and business 2013. I recently tried to install Photoshop Elements by CD with serial number but on the desktop appears the following message: error 1 (configuration problem) try to uninst

What's error 1 in adobe photoshop elements configuration? I have a computer with W Vista 8, Windows office home and business 2013. I recently tried to install Photoshop Elements by CD with serial number but on the desktop appears the following message: error 1 (configuration problem) try to uninstall and reinstall. I have done this but the message continues to appear

You haven't mentioned which version of PSE. If it is PSE 13, that requires a minimum of windows 7.

Itunes starts but fails to open due to audio configuration problem

Hi
I have been running itunes 7.1 quite successfully until today. Running on windows xp/toshiba laptop.
Problem occurs when i select itunes on desktop, itunes appears on task bar below, after a number of seconds the following error message appears "itunes cannot run because it has detected a problem with your audio configuration", once I click ok on this message itunes terminates.
No changes have been made to my audio configuration (to the best of my knowledge), i can run Windows Media Player and that works fine, so too real player.
I reinstalled itunes, but this did not resolve the problem. I also ran itunes from another logon on my laptop and that presented the same error. I checked all my audio settings in the control panel and also ran the diagnostics on each device and all appears to be fine.
Has anybody faced the same issue, and could anybody advise on any diagnistic tool that could assist in pinpointing the configuration problem?.
Thanks
Toshiba Satellite Windows XP Pro

Hi
Got it resolved, thanks for the prompt responses all!.
Resolved by removal current version of Quicktime thru the control panel (add/remove programs), and then reinstalled from the website.
Phew!
Toshiba Satellite Windows XP Pro

Single Transaction code for ALE Configuration

Hi All,
I want to Know is there any Single Transaction code for the ALE Configuration instead of going through SALE, WEDI t-code or with defining logical systems assigning them to clients, creating RFC and Distribution Model, generate partner function and..so on.
Please let me know if there is any t-code through which i can do the ALE configuration in a single T-code.
Thanking you in advance,
Bhanu

hi ars
i got a task saying that message type is DESADV01 ,but u told that DESADV01
is basic type,can i know the difference.
regards
sagar

ALE Configurations?

Hi All,
Currently i'm working on the following requirements. we are using TIBCO system as a middleware tool and it will ceate an IDOC which needs to be directed to R/3 system. As we have already imported the IDOC to the TIBCO system and then it will fetch the data from non-SAP system and creates the IDOC and sends it to R/3 system? I've done the following ALE configurations but got the error message as 56..."Partner profile is not define".
I've done the following ALE configurations at R/3 side.
1. Created a logical system and RFC destination for TIBCO.
2. created a TRFC port.
3. Create a Partner profile and linked the TRFC port.
4. posted an IDOC from WE19.
but when i checked the status of IDOC in WE02 its displaying an warning message with status code 56 "Partner profile is not define". and i think no need to do any ALE Configuration at sender side since the sender system is TIBCO.
pls correct me if i'm wrong. as one of my colleage suugested me to create FIle port instead of TRFC port?
regards
Faisal

HI
SAP R/3
R/3 to 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 (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.
XI to 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 (IDX1) ( Create port to get IDOC Meta data from sender system)
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) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Refer the below links for further assistance
4.create partner profile using idx2
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)
cheers

ALE Configurations in File to IDOC Scenario

Hi All,
We are doing File to IDOC Scenario.
ALE Configurations done:
R/3 Side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to XI.
2. Created port in R/3(using automatically generated port name) and assigned the RFC dest created above.
3. Created partner profile and assigned the ports to the message types.
4. Created Logical system
XI side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to r/3.
2. Created port using IDX1 transaction with port name starting with SAP<SID> and assigned the RFC dest created above. (SID of XI)
3. Unable to load metadata in XI.
Now we are unable to test the scenario as it provides an error message in MONI as "Error: Transaction IDX1: Port SAP<SID>, client , RFC destination contain errors".
Also Let me know whether the steps mentioned above are correct for the scenario.
Regards,
Nithiyanandam

Hello,
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 XI 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 #####+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.
With Regards,
Vidya.
*******Reward with Points if found useful

Integration Directory(Configuration) Problem

Hi All,
I am facing one Probelm. I am working one the client through Citrix. I am not able to open Integration Directory(Configuration Problem) . In onsite it's working fine. Reming all other applications(Integartion Repository and SLD and Runtime work bench) are working fine.
if I open Integration Directory i am getting this messge.
<jnlp spec="1.0+" codebase="http://filp55.group.upm-kymmene.com:50100/dir">
 <information>
 <title>Integration Builder</title>
 <vendor>SAP AG</vendor>
 <homepage href="http://www.sap.com" />
 <description type="one-line">Directory</description>
 <description type="short">Directory</description>
 <description type="tooltip">Directory</description>
 <icon hight="64" href="start/graphics/sap6464.gif" type="splash" width="64" />
 <icon hight="32" href="start/graphics/SAP3232.gif" width="32" />
 </information>
 <security>
 <all-permissions />
 </security>
 <resources>
 <j2se version="1.4+" initial-heap-size="32m" max-heap-size="1024m" />
 <jar href="directory/aii_ibdir_client.jar" />
 <jar href="directory/aii_ibdir_core.jar" />
 <jar href="directory/aii_ibdir_sbeans.jar" />
 <jar href="directory/aii_ibdir_rb.jar" />
 <jar href="directory/aii_ib_client.jar" />
 <jar href="directory/aii_ib_core.jar" />
 <jar href="directory/aii_ib_sbeans.jar" />
 <jar href="directory/aii_ib_rb.jar" />
 <jar href="directory/aii_util_icons.jar" />
 <jar href="directory/aii_util_swing.jar" />
 <jar href="directory/aii_util_xml.jar" />
 <jar href="directory/aii_util_xsd.jar" />
 <jar href="directory/aii_utilxi_misc.jar" />
 <jar href="directory/aii_util_rb.jar" />
 <jar href="directory/clientaii_ib_sbeans.jar" />
 <jar href="directory/clientaii_ibdir_sbeans.jar" />
 <jar href="directory/frog.jar" />
 <jar href="directory/focus14.jar" />
 <jar href="directory/sapxmltoolkit.jar" />
 <jar href="directory/jta.jar" />
 <jar href="directory/ejb20.jar" />
 <jar href="directory/exception.jar" />
 <jar href="directory/logging.jar" />
 <jar href="directory/guidgenerator.jar" />
 <jar href="directory/jperflib.jar" />
 <jar href="directory/sapni.jar" />
 <jar href="directory/sapj2eeclient.jar" />
 <property name="sap.theme" value="Streamline" />
 <property name="jnlp.log.initialConfiguration" value="FILE, SIMPLE" />
 <property name="jnlp.com.sap.aii.ib.client.properties" value="com.sap.aii.ib.client., com.sap.aii.ib.core., com.sap.aii.util.xml., com.sap.aii.connect., com.sap.aii.repository.mapping.additionaltypes, com.sap.aii.docu., com.sap.aii.ibrep.core., com.sap.aii.ibdir.core.*" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.sysnr" value="01" /><property name="jnlp.com.sap.aii.connect.landscape.contextroot" value="sld" /><property name="jnlp.com.sap.aii.connect.cr.name" value="filp40.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.ib.client.content.languages" value="EN,DE" /><property name="jnlp.com.sap.aii.connect.repository.contextroot" value="rep" /><property name="jnlp.com.sap.aii.ib.client.login.languages" value="EN,DE" /><property name="jnlp.com.sap.aii.connect.directory.rmiport" value="50104" /><property name="jnlp.com.sap.aii.connect.cr.contextroot" value="sld" /><property name="jnlp.com.sap.aii.connect.rwb.r3.client" value="790" /><property name="jnlp.com.sap.aii.connect.directory.contextroot" value="dir" /><property name="jnlp.com.sap.aii.connect.rwb.contextroot" value="rwb" /><property name="jnlp.com.sap.aii.connect.landscape.httpsport" value="@com.sap.aii.server.httpsport.lcr@" /><property name="jnlp.com.sap.aii.connect.repository.rmiport" value="50104" /><property name="jnlp.com.sap.aii.connect.repository.httpport" value="50100" /><property name="jnlp.com.sap.aii.connect.directory.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.cr.httpsport" value="@com.sap.aii.server.httpsport.cr@" /><property name="jnlp.com.sap.aii.connect.repository.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.integrationserver.contextroot" value="run" /><property name="jnlp.com.sap.aii.connect.integrationserver.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.rwb.httpsport" value="@com.sap.aii.connect.rwb.httpsport@" /><property name="jnlp.com.sap.aii.connect.landscape.httpport" value="50000" /><property name="jnlp.com.sap.aii.docu.languages" value="null" /><property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.initialheapsize" value="32m" /><property name="jnlp.com.sap.aii.util.xml.parserFactory" value="com.sap.engine.lib.jaxp.SAXParserFactoryImpl" /><property name="jnlp.com.sap.aii.connect.directory.httpport" value="50100" /><property name="jnlp.com.sap.aii.connect.directory.httpsport" value="@com.sap.aii.server.httpsport.directory@" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.httpport" value="8001" /><property name="jnlp.com.sap.aii.connect.rwb.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.client" value="790" /><property name="jnlp.com.sap.aii.connect.cr.httpport" value="50000" /><property name="jnlp.com.sap.aii.connect.landscape.name" value="filp40.group.upm-kymmene.com" /><property name="jnlp.SAPMYNAME" value="filp55_GTX_01" /><property name="jnlp.com.sap.aii.connect.rwb.httpport" value="50100" /><property name="jnlp.com.sap.aii.docu.url" value="null" /><property name="jnlp.com.sap.aii.ib.client.applicationname.directory" value="sap.com/com.sap.xi.directory/" /><property name="jnlp.com.sap.aii.util.xml.transformerFactory" value="com.sap.engine.lib.jaxp.TransformerFactoryImpl" /><property name="jnlp.com.sap.aii.ib.client.applicationname.repository" value="sap.com/com.sap.xi.repository/" /><property name="jnlp.com.sap.aii.ib.client.login.InitialContextFactory" value="com.sap.engine.services.jndi.InitialContextFactoryImpl" /><property name="jnlp.com.sap.aii.connect.integrationserver.httpport" value="50100" /><property name="jnlp.client" value="true" /><property name="jnlp.com.sap.aii.connect.repository.httpsport" value="@com.sap.aii.server.httpsport.repository@" /><property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.maxheapsize" value="1024m" /><property name="jnlp.com.sap.aii.connect.integrationserver.httpsport" value="@com.sap.aii.connect.integrationserver.httpsport@" /><property name="jnlp.com.sap.aii.connect.integrationbuilder.startpage.url" value="rep/start/index.jsp" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.httpsport" value="@com.sap.aii.connect.integrationserver.r3.httpsport@" /><property name="jnlp.com.sap.aii.connect.rwb.r3.sysnr" value="01" /><property name="jnlp.com.sap.aii.util.xml.schemaValidator" value="com.sap.engine.lib.schema.validator.SchemaValidator" /><property name="jnlp.rc.release" value="7_00" /><property name="jnlp.rc.applname" value="DIRECTORY" /><property name="jnlp.rc.supportpackage" value="09" /><property name="jnlp.rc.synctime" value="${sync.time}" /></resources>
 <application-desc main-class="com.sap.aii.ibdir.gui.appl.ApplicationImpl">
 <argument>webstart</argument>
 </application-desc>
</jnlp>
Please help me on this..........
Thanks in Advacne.
Regards,
Chandra

Hello,
1)
May be the problem is a network connectivity issue. Do one thing copy the "cahce" folder from some other client PC(which has successfully opened IR and ID) to your client PC. The folder resides in "C:Documents and Settings<yourUserProfile>Application DataSunJavaDeploymentjavaws".
Copy "cache" folder to your client PC under the above path.
/people/shabarish.vijayakumar/blog/2006/02/13/unable-to-open-iresrid-xipipi-71-updated-for-pi-71-support
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1688 [original link is broken] [original link is broken] [original link is broken]
2) Go to http://filp55.group.upm-kymmene.com:50100/rep/
Click on Administration -> Java Web Start -> Java Web Start Administration ->
Try
1. Re-initialization (then try logging)
2. Re-initialization and force-signing (then try logging)
3. Delete lock (then try logging)
Do this for IR and ID tabs.
3) Check can be a firewall issue.
4) Check wether sufficient roles have been assigned -> Tcode -> SU01 -> roles tab. These roles need to be assigned to your username
SAP_BC_AI_LANDSCAPE_DB_RFC
SAP_SLD_CONFIGURATOR
SAP_SLD_DEVELOPER
SAP_XI_BPE_CONFIGURATOR_ABAP
SAP_XI_BPE_MONITOR_ABAP
SAP_XI_DEVELOPER
SAP_XI_DEVELOPER_ABAP
SAP_XI_DEVELOPER_J2EE
SAP_XI_MONITOR
SAP_XI_MONITOR_ABAP
SAP_XI_MONITOR_J2EE
*******************Reward,if found useful
Edited by: BVS on May 7, 2008 3:01 PM

ALE Configuration problem in FI

Similar Messages

Maybe you are looking for