Need help in ALE

WHAT IS the transaction to create partner profile in sap ?

Hello Deb,
You can find every transaction realeted to ALE/EDI in work menu
Transaction : WEDI
check this transaction.you will find everythg here.
@award pts if useful.
Regards,
Nisha
null

Similar Messages

Need help in ALE configuaration !

Please send me an example of how to create an ALE configuaration with in one client !

HI,
What is ALE?
ALE stands for Application Link Enabling and is a remote connection technology allowing the decentralization of business processes by connecting decentralized systems together.
Using ALE, it is fairly easy to synchronize several SAP systems so that they contain the same data objects at anytime. These objects may be master data (customers, vendors, GL accounts, cost centers, ...) or transaction data (FI documents, purchase orders, ...). To enable the synchronization, ALE supports not only mass transfer of data between systems but also selective data transfers of objects changed since the last transfer.
How does it work?
Viewed from a high level perspective, the process is straight and simple: a sender system selects the data that needs to be distributed, packs it in a standard format and sends it to one or several receiving systems. When a receiving system gets the data, it unpacks the standard format and records the data.
In fact, 3 layers are involved in this process:
An application layer which selects and records data in R/3.
A distribution layer which filters and converts data.
A communication layer which ensures the actual communication of records generated in a standard format.
The senders and receivers are determined thanks to a so-called distribution model which defines the transfer rules (who sends what to who?). The definition of the distribution model must be known by all systems involved (either as sender or receiver) and must consequently exist on all those systems.
The Intermediate Document (IDoc)
The data transferred using ALE must have a SAP standard format to be understood from all partners in the communication. This format is the Intermediate Document (IDoc) which represents an intermediary structure between raw SAP data and EDI formats. This structure is not constant, it depends on the data to be transferred and SAP provides the structures for most SAP standard objects such as customers master data, sales orders, ...
An IDoc with a specific structure is said to have a specific type. The IDoc type is nothing more than a version of a specific IDoc structure designed to contain data for a specific object type. For example, the IDoc type DEBMAS05 is the fifth version of a structure that represents a customer master data. The management of versions for IDocs structures is necessary because the objects evolve with time and tend to become more and more complex with new data fields or tables being added regularly.
The conversion of raw data forth (for the sender system) and back (for the receiver system) to the IDoc format is also ensured by SAP standard function modules as long as you transfer standard objects. For non standard objects (enhancements), you must define your own IDoc structure and write your own conversion function modules.
RFC connections
The data communication between the SAP servers may be done by several ways. The 2 most common ways are the transactional RFC and the file. The RFC connection is used to make a direct connection between servers while the file interface speaks for itself, it uses a file containing the IDocs from the sender system as input in the receiver(s) system(s).
The selection of a communication method is made though the ports configuration as we will see in the next section. For the purpose of this article, we are going to choose the most efficient method: the transactional RFC method. To set it up, we first need to define the RFC destinations of the partner systems.
An RFC destination may be seen as a set of settings necessary to connect to a system using the RFC protocol. These settings include the address and type of the partner system along with connection information such as the user ID and password to use.
The RFC destinations of all partners systems must be defined on all systems to include in the distribution model. The transaction to use for this purpose is SM59.
Definition of the communication ports
The communication ports determine the type of data communication that must occur between systems. When the communication is to use the RFC protocol, transactional RFC ports must be created specifying the RFC destinations of the partner systems. Use transaction WE21 for this purpose.
Partners profiles
In SAP, all partners systems involved in a distribution model have a profile. There exist several profile types such as customers profiles, vendors profiles, ... but this distinction between profiles is generally not necessary and you will create in most cases your partners profiles using a generic Logical System type.
Before entering the settings of the logical systems partners, you have to create them in customizing. Also, each system in the distribution model must be assigned in its own system its own logical system that represents it. This assignment is done at client level and not at system level. This is not easy to explain nor to understand so let's take a simple example. Let's consider we have a simple distribution model made up of a sender system (S01) and a receiver system (R01). We need to transfer data from S01 / client 100 to R01 / client 200. In both the systems, we will define the logical systems S01_100 and R01_200. But in sender system S01, the logical system S01_100 will be assigned to the client 100 while in the receiver system R01, it will be R01_200 that will be assigned to client 200. With such a configuration you see it is even possible to transfer data between two clients from the same system.
A partner profile is used to determine a lot of important settings that will be involved in the data transfer. These settings vary depending on the role of the partner system (sender / receiver) and are defined per message type. A message type is more or less a version independent IDoc type. It is mainly a convenient way of defining settings and identifying IDocs using a criterium independent of the partner system.
For a sender partner system (inbound parameters are filled in), following important settings are set per message type in the partner profile:
A process code used to indicate which function module will be used to convert the IDoc data to SAP data.
The time of input of the IDoc: as soon as the IDoc is created in the system or on request (using program RBDAPP01).
The post processing agent who will have to treat the data input errors if need be. The post processing agent may be either a user or any other HR organizational unit.
For a receiver partner system (outbound parameters are filled in), following settings are specified in the partner profile:
The receiver port to which the data will be sent.
The sending method: one IDoc at a time or by packets.
The IDoc type that will be sent to that partner. For a given message type, the IDoc type sent may vary depending on the receiver system. Indeed you may have different versions of SAP in your system landscape.
Definition of the distribution model and data filtering
We have already seen that the distribution model is used to decide who sends what to who. But, as you guessed, there is a little bit more to be said about it and the way to manage it.
The distribution model is maintained in a central transaction (BD64) which lets you access the most useful environmental settings necessary to set up the model. Before creating the model, you must first decide on which system you are going to create it. Indeed the model must exist in all partners systems and two possibilities exist to achieve this.
Either you create the model on each system manually (with the same model technical name), which is feasible only with few systems and/or simple models. Either you create it in a specific system (usually the source system) and distribute it to the other systems thanks to the distribution command in the BD64 transaction menu.
If we want to copy the customers master data from the production system to the other systems in the maintenance line for example, we may create the distribution model on the production system and distribute it to all partners systems.
The actual creation of the model requests that you mention a technical name for the model (unique identifier in the systems landscape), a sender system, a receiver system and message types to exchange between those systems. You may afterwards add more sending and receiving systems in the model as well as more message types.
For each message type defined between a sender and a receiver, you may set filters on specific fields of the message type so that IDocs be generated only when these specific values are matched. For example, you may decide to send only customers of a specific account group. These filters are set by selecting the 'no filter set' text under message types in BD64.
There exists also another kind of filters which are segments filters. They do not filter IDocs creation based on values like we have just seen but filter unconditionally segments of created IDocs which must be excluded from the transfer (transaction BD56).
This article will help you understand the basics of ALE and IDocs via a simple do-it-yourself example. We will create a custom IDoc in one SAP system and then post some business data through it to another SAP system. Business data will be picked up from custom data dictionary tables.
ALE Application Link Enabling is a mechanism by which SAP systems communicate with each other and with non-SAP EDI subsystems. Thus it helps integration of distributed systems. It supports fail-safe delivery which implies that sender system does not have to worry about message not reaching the source due to unavoidable situations. ALE can be used for migration and maintenance of master data as well as for exchanging transactional data.
The messages that are exchanged are in the form of IDocs or Intermediate Documents. IDocs act like a container or envelope for the application data. An IDOC is created as a result of execution of an Outbound ALE. In an Inbound ALE an IDOC serves as an input to create application document. In the SAP system IDocs are stored in the database tables. They can be used for SAP to SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data. Complete documentation on IDOC is obtained by using transaction WE60.
Every IDoc has exactly one control record along with a number of data records and status records. Control record has the details of sender/receiver and other control information. Data records contain the actual business data to be exchanged while the status records are attached to IDoc throughout the process as the IDoc moves from one step to other.
Now, let us understand the ALE Configuration by means of an example scenario below:
The Scenario
Data from custom tables (created in customer namespace) is to be formatted into an IDoc and sent from one SAP R/3 system to another using ALE service. We need to have two instances of SAP R/3 systems or we can simulate this on two clients of the same SAP R/3 system.
Create three tables as shown below.
Creating Custom IDoc type and Message type
All the objects created should be present on both source as well as target system(s).
1. Create segments Transaction WE31
Create a segment ZRZSEG1
Add all fields of table ZCUSTOMERS to it
Save the segment
Release it using the menu path Edit -> Set Release
Similarly create two more segments given below
Seg. ZRZSEG2 to hold all fields of table ZSOHEADERS
Seg. ZRZSEG3 to hold all fields of table ZSOITEMS
2. Create Basic IDoc type Transaction WE30
Create a Basic type ZRZORDER
Add the created segments in the hierarchy shown
Maintain attributes for each of the segments
Save the object and go back
Release the object using the menu path Edit -> Set Release
3. Create/Assign Message type Transactions WE81/WE82
Go to WE81
Create a new Message type ZRZSO_MT
Save the object
Go to WE82 and create new entry
Assign the message type ZRZSO_MT to the basic type ZRZORDER
Also specify the Release Version
Save the object
Thus we have defined the IDoc structure which will hold the data to be transferred. In the [1] next part of the article we will understand the outbound settings, i.e. the settings to be done in the source system.
Outbound Settings
Define Logical Systems and Assign Client to Logical System Transaction SALE
Go to Define Logical System (See the figure)
Define a new logical system to identify the local system and save it
Now, go to Assign Client to Logical System (See the figure)
Add a new entry
Specify the client, previously created logical system and other attributes
Save the entry
Define a new logical system to identify the partner system and save it
Maintain RFC Destinations Transaction SM59
Create a new RFC destination for R/3 type connection
Specify the target host on Technical settings tab
Provide the Logon credentials on the Logon/Security tab
Save the settings
To verify the settings, Click on Test connection or Remote logon
Define Ports Transaction WE21
We need to define a tRFC port for the partner system
Click on Transactional RFC node
Create a new port
Provide a description
Specify the name of the target RFC destination
Save the object
Maintain Distribution Model Transaction BD64
Click on Change
Create a new model view
Provide a Short text and Technical name to the model view
Add message type
Specify sender and receiver systems
Also, specify the message type that we created previously
Save the Distribution model
Generate/Create Partner Profile Transactions BD82/WE20
To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles
Otherwise, you may use transaction WE20 to create a partner profile
On selection screen, specify the model view, target system and execute
The result log will be displayed on the next screen
To verify the partner profile go to WE20
Check the partner profile for the target system
Distribute Model View Transaction BD64
Select the Model View
Go to menu path Edit -> Model View -> Distribute
Result log will be displayed on the next screen
Outbound IDoc Generation Program
Create an executable program ZRZ_ORDER_IDOC in SE38. Below, I have described the program logic:
Fetch the data from the DDic tables ZCUSTOMERS, ZSOHEADERS and ZSOITEMS as per the selection criteria
Fill the control record structure of type EDIDC
Specify message type, Basic IDoc type, tRFC Port, Partner number and Partner type of the receiver
Fill the data records
Define structures like the IDoc segments
Fill the structures with fetched data
Pass the segment name and the above structure to the appropriate fields of EDIDD type structure
Append the EDIDD structure to the EDIDD type internal table
Now, call the function module MASTER_IDOC_DISTRIBUTE and pass the IDoc control record structure and data record table
Commit work if return code is zero
Function module returns a table of type EDIDC to provide the details about generated IDoc
Display appropriate log
You can [2] download sample code for the above program here.
Thus we have completed sender side configuration required for ALE. In the [3] next part we will see how to configure the receiving system to be able to receive and post the inbound IDoc.
Inbound IDoc Posting Function Module
In the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37. Below, I have described the logic for the same.
Add Include MBDCONWF. This include contains predefined ALE constants.
Loop at EDIDC table
Check if the message type is ZRZORDER. Otherwise raise WRONG_FUNCTION_CALLED exception
Loop at EDIDD table
Append data from the segments to appropriate internal tables
For example: append data from ZRZSEG1 segment to the internal table of type ZCUSTOMERS
Update the DDic tables from internal tables
Depending on the result of the update, fill the IDoc status record (type BDIDOCSTAT) and append it to the corresponding table.
Status 53 => Success
Status 51 => Error
You can [3] download the sample ABAP code for the above function module here.
Inbound Settings
Define Logical Systems Transaction SALE (Please refer to Outbound Settings discussed in [4] previous part)
Assign Client to Logical System Transaction SALE (Please refer to Outbound Settings discussed in [5] previous part)
Maintain RFC Destinations Transaction SM59 (Please refer to Outbound Settings discussed in [6] previous part)
Define Ports Transaction WE21 (Please refer to Outbound Settings discussed in [7] previous part)
Generate/Create Partner Profile Transactions BD82/WE20 (Please refer to Outbound Settings discussed in [8] previous part)
Assign Function Module to Logical message Transaction WE57
Create a new entry
Specify name of the Function Module as Z_IDOC_INPUT_ZRZSO_MT
Also, specify Type as F, Basic IDoc type as ZRZORDER, Message type as ZRZSO_MT and Direction as 2 (Inbound)
Save the entry
Define Input method for Inbound Function Module Transaction BD51
Create a new entry
Provide Function Module name as Z_IDOC_INPUT_ZRZSO_MT
Specify the Input method as 2
Save the entry
Create a Process Code Transaction WE42
Create a new Process Code ZPCRZ
Select Processing with ALE Service
Choose Processing type as Processing by function module
Save the entry
On the next screen, select your function module from the list
Save the changes
Now you will be taken to the next screen
Double-click on Logical message
In the Assignment to logical message, specify the message type ZRZSO_MT
Save the changes
Send and receive data
On the sender system, execute the IDoc Generation Program. Check the status of IDoc using transaction WE02.
Check the status of the IDoc in the receiver system using transaction WE02. You can also check the contents of DDic tables to make sure that the records have been created in the receiver system.
Thus to summarize we have learned how to:
*& Report ZRZ_ORDER_IDOC *
REPORT ZRZ_ORDER_IDOC .
PURPOSE OF REPORT *
Generats an Idoc for Customer Master, Sales Master
and Sales item table.
TABLES : ZCUSTOMERS, "Cutomer Header
 ZSOHEADERS, "Sales Header
 ZSOITEMS. "Sales Items
DATA : S_CTRL_REC LIKE EDIDC, "Idoc Control Record
 S_ZRZSEG1 LIKE ZRZSEG1, "CUSTOMER Header Data
 S_ZRZSEG2 LIKE ZRZSEG2, "SALES HEADER Data
 S_ZRZSEG3 LIKE ZRZSEG3. "SALES Detail Data
DATA : T_ZCUSTOMERS LIKE ZCUSTOMERS OCCURS 0 WITH HEADER LINE.
DATA : T_ZSOHEADERS LIKE ZSOHEADERS OCCURS 0 WITH HEADER LINE.
DATA : T_ZSOITEMS LIKE ZSOITEMS OCCURS 0 WITH HEADER LINE.
DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE."Data Records
DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
"Generated Communication IDOc
CONSTANTS :
C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG1',
C_ZRZSEG2 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG2',
C_ZRZSEG3 LIKE EDIDD-SEGNAM VALUE 'ZRZSEG3'.
CONSTANTS: C_IDOCTP LIKE EDIDC-IDOCTP VALUE 'ZRZORDER'.
Selection Screen
SELECT-OPTIONS : S_KUNNR FOR ZCUSTOMERS-KUNNR OBLIGATORY,
 S_VBELN FOR ZSOHEADERS-VBELN.
PARAMETERS : C_MESTYP LIKE EDIDC-MESTYP DEFAULT 'ZRZSO_MT',
 "Message Type
 C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS',
 "Partner type of receiver
 C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'Y901',
 C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000226',
 C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'LSSENDS',
 C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'.
"Destination System
***START-OF-SELECTION
START-OF-SELECTION.
PERFORM GENERATE_DATA_RECORDS.
PERFORM GENERATE_CONTROL_RECORD.
PERFORM SEND_IDOC.
*& Form generate_data_records
FORM GENERATE_DATA_RECORDS .
PERFORM FETCH_ZCUSTOMERS.
PERFORM FETCH_ZSOHEADERS.
PERFORM FETCH_ZSOITEMS.
PERFORM ARRANGE_DATA_RECORDS.
ENDFORM. " generate_data_records
*& Form fetch_zcustomers
FORM FETCH_ZCUSTOMERS.
SELECT *
FROM ZCUSTOMERS
INTO TABLE T_ZCUSTOMERS
WHERE KUNNR IN S_KUNNR.
IF SY-SUBRC NE 0.
 MESSAGE E398(00) WITH 'No Customers Found'.
ENDIF.
ENDFORM. " fetch_zcustomers
*& Form fetch_zsoheaders
FORM FETCH_ZSOHEADERS.
SELECT *
FROM ZSOHEADERS
INTO TABLE T_ZSOHEADERS
WHERE VBELN IN S_VBELN
 AND KUNNR IN S_KUNNR.
IF SY-SUBRC NE 0.
 MESSAGE I398(00) WITH 'No Sales orders found'.
ENDIF.
ENDFORM. " fetch_zsoheaders
*& Form fetch_zsoitems
FORM FETCH_ZSOITEMS.
IF NOT T_ZSOHEADERS[] IS INITIAL.
 SELECT *
 FROM ZSOITEMS
 INTO TABLE T_ZSOITEMS
 FOR ALL ENTRIES IN T_ZSOHEADERS
 WHERE VBELN = T_ZSOHEADERS-VBELN.
 IF SY-SUBRC NE 0.
 MESSAGE I398(00) WITH 'No Sales order items found'.
 ENDIF.
ENDIF.
ENDFORM. " fetch_zsoitems
*& Form generate_control_record
FORM GENERATE_CONTROL_RECORD .
S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
S_CTRL_REC-MESTYP = C_MESTYP. "Message type
S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
ENDFORM. " generate_control_record
*& Form send_idoc
FORM SEND_IDOC.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
 EXPORTING
 MASTER_IDOC_CONTROL = S_CTRL_REC
 TABLES
 COMMUNICATION_IDOC_CONTROL = T_COMM_IDOC
 MASTER_IDOC_DATA = T_EDIDD
 EXCEPTIONS
 ERROR_IN_IDOC_CONTROL = 1
 ERROR_WRITING_IDOC_STATUS = 2
 ERROR_IN_IDOC_DATA = 3
 SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
 OTHERS = 5.
IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
 COMMIT WORK.
 LOOP AT T_COMM_IDOC.
 WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
 ENDLOOP.
ENDIF.
ENDFORM. " send_idoc
*& Form arrange_data_records
FORM ARRANGE_DATA_RECORDS .
DATA: W_INDEX1 LIKE SY-TABIX,
 W_INDEX2 LIKE SY-TABIX.
SORT T_ZCUSTOMERS BY KUNNR.
SORT T_ZSOHEADERS BY KUNNR VBELN.
SORT T_ZSOITEMS BY VBELN POSNR.
LOOP AT T_ZCUSTOMERS.
 S_ZRZSEG1-KUNNR = T_ZCUSTOMERS-KUNNR.
 S_ZRZSEG1-NAME1 = T_ZCUSTOMERS-NAME1.
 S_ZRZSEG1-ORT01 = T_ZCUSTOMERS-ORT01.
 S_ZRZSEG1-LAND1 = T_ZCUSTOMERS-LAND1.
 T_EDIDD-SEGNAM = C_ZRZSEG1.
 T_EDIDD-SDATA = S_ZRZSEG1.
 APPEND T_EDIDD.
 CLEAR T_EDIDD.
 CLEAR W_INDEX1.
 READ TABLE T_ZSOHEADERS WITH KEY KUNNR = T_ZCUSTOMERS-KUNNR BINARY SEARCH.
 IF SY-SUBRC = 0.
 W_INDEX1 = SY-TABIX.
 LOOP AT T_ZSOHEADERS FROM W_INDEX1.
 IF T_ZSOHEADERS-KUNNR NE T_ZCUSTOMERS-KUNNR.
 EXIT.
 ENDIF.
 S_ZRZSEG2-VBELN = T_ZSOHEADERS-VBELN.
 S_ZRZSEG2-KUNNR = T_ZSOHEADERS-KUNNR.
 T_EDIDD-SEGNAM = C_ZRZSEG2.
 T_EDIDD-SDATA = S_ZRZSEG2.
 APPEND T_EDIDD.
 CLEAR T_EDIDD.
 CLEAR W_INDEX2.
 READ TABLE T_ZSOITEMS WITH KEY VBELN = T_ZSOHEADERS-VBELN BINARY SEARCH.
 IF SY-SUBRC = 0.
 W_INDEX2 = SY-TABIX.
 LOOP AT T_ZSOITEMS FROM SY-TABIX.
 IF T_ZSOITEMS-VBELN NE T_ZSOHEADERS-VBELN.
 EXIT.
 ENDIF.
 S_ZRZSEG3-VBELN = T_ZSOITEMS-VBELN.
 S_ZRZSEG3-POSNR = T_ZSOITEMS-POSNR.
 S_ZRZSEG3-MATNR = T_ZSOITEMS-MATNR.
 S_ZRZSEG3-NETWR = T_ZSOITEMS-NETWR.
 S_ZRZSEG3-ZMENG = T_ZSOITEMS-ZMENG.
 T_EDIDD-SEGNAM = C_ZRZSEG3.
 T_EDIDD-SDATA = S_ZRZSEG3.
 APPEND T_EDIDD.
 CLEAR T_EDIDD.
 ENDLOOP.
 ENDIF.
 ENDLOOP.
 ENDIF.
ENDLOOP.
ENDFORM. " arrange_data_records

Need help with ALE

We are trying to go live with our XI / ICH implementation and are getting the following error
Unable to convert sender service to an ALE logical system
Can someone point me to where I can fix this?
Thanks
Mike

Hi Michael,
there are two things you need to check
1. compare with SLD (for technical system name) in SLD
2. you can also put another business system in sender system
field of your receiver agreement
both approaches described in:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Hi need help in ALE service !

If i want to create the Ale service for only one client which will act as both server and receiver then what r the steps ?

The code works for me.
Put a e.printStackTrace(); inside the catch block to see what exceptions are thrown (if the code isn't working then ignoring exceptions is the worst thing you could do when trying to find out what's wrong):    } catch (IOException e) {
        e.printStackTrace();
    }- Marcus

Need help for ALE Remote lock while dropping indexes in process chain

Hi Gurus,
Object requested is currently locked by ALE Remote is the message i got while dropping indexes from the process chain and is red
Entire chain is now status R. I tried by repeat still the dropping indexes step fail in the process chain.
Could u please advise me.
Thanks,
Srikar

Hi,
Even check any lock is happened for the cube in SM12. If it not rectified with all possible solutions please paste error log in batch monitor tab.
Regard's
Suman

Need help in ALE IDOC !

I have a requirement .where I have to create an IDOC when the credit memo is generated.
I have developed one IDOC out bound code I want to associate it with the credit memo generation.
Is there any USer exit ?
I am using tcode VF01 for credit memo creation !

hi,
find the function module for outbound Idoc.
it has prefix, IDOC_OUTPUT_<message type>.
by searching, find the function exit.
there you can write the code.
Regards,

Plz help me ALE/IDOC Scinario documentation

hi and all,
plz help me ale/idoc scinarios documentation plz send to me.
thanking u one and all.

Hi
ALE:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Outbound:
Step 1. Application document is created when transaction is saved.
 2. Message control is invoked.
 3. Messages are processed by system.
 4. Messages are Edited (if desired).
 5. Output (ALE / EDI) is checked
 6. Validate against Message control record from Partner Profile
 7. Application Document is saved.
 8. Entry NAST table is created for every selected output program
 along with Medium & Timing.
 9. Check for Process Immediately .
 If (yes)
 Determine Processing Program from TNAPR Table.
 ELSE
 Execute RSNASTED Program.
 10. Read Partner Profile to determine Process Code.
 11. Process Code points to the Function Module & Invoked.
 12. IDoc is generated.
 13. Check for ALE Request.
 if (Yes)
 Perform Filters, Conversions, Version Changes etc.
 Else.
 IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
 2. Subsystem calls Functional Module EDI_DATA_INCOMING from
startRFC program.
 3. Data in Control Record is validate against the Partner Profile.
 4. IDoc is generated in Database and syntax check is carried out.
 5. IDoc file is deleted once file read.
 6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
 7. Check for Process Immediately.
 If NO
 Execute RBDAPP01 Program
 Else
 Read Process Code from Partner Profile
 Process Code Points to Function Module
 Application Document Posted.
IDOC
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Reward points for useful Answers
Regards
Anji

Need help to master ABAP

I need help to master ABAP.
Please email me....if u can help me : [email protected]
I am looking for help with IDOC, ALE, RFC and BAPI.
Please send me mail. We can talk more.

Jeff, please ask specific questions here. The answer will come. Try to not ask for material to be sent directly to you. This is not in the community spirit as it will only benefit you. Also you might want to try the search functionality on this site. There is plenty of info out there.
Regards,
RIch HEilman

Need help correcting message error number

Hello, i need help correcting message number for running archiving test runs.
05.08.2011 08:31:42 Message number 999999 reached. Log is full BL 252 E
05.08.2011 08:31:42 Job cancelled after system exception ERROR_MESSAGE 00 564 A
Any help wopuld be appreciated.
Regards.

Summary
Symptom
One or several database tables of the application log contain too many entries.
The following database tables belong to the application log:
- BALHDR (all releases)
- BALHDRP(< 4.6C)
- BALM (< 4.6C)
- BALMP (< 4.6C)
- BALC (< 4.6C)
- BALDAT (>= 4.6C)
- BAL_INDX (all releases)
Other terms
RSSLG200,
RSSLGK90,
SLG2,
application log,
log
delete,
performance
Reason and Prerequisites
The application log is a tool to collect, save and display logs.
Many different applications collect messages in the application log which contain information or messages for the end user. The application automatically log serves as a temporary storage for messages. The logs are written on the database but they are not automatically deleted.
There is no general procedure for switching the application log on or off. Some applications provide this option or they offer the option of reducing the number of entries created. (See Notes 91519, 183960, 141244).
The expiration date of application logs
A log usually has an expiration date, which is set by the application, that calls the 'Application log' tool. If the application log does not set an expiration date, the 'Application log' tool sets the expiration date as 12/31/2098 or 12/31/9999,depending on the release, which allows the logs to stay in the system for as long as possible. The end user cannot set the expiration date. The expiration date does not mean that logs which have reached that date will automatically be deleted. It is used to control the deletion of logs when you call the Deletion report. The DEL_BEFORE flag in the BALHDR table determines whether or not the log can be deleted even before the expiration date is reached.
DEL_BEFORE= SPACE means that the log can be deleted before the expiration date is reached. (Default value)
DEL_BEFORE='X' means that the log can only be deleted after the expiration date.
Solution
Deleting the logs of the application log.
Releases >= 4.6A:
=====================================================================
In Releases >= 4.6A, use Transaction SLG2.
On the selection screen you can restrict the amount of logs to be deleted:
The 'Object' and 'Subobject' fields specify the application area in which the logs were written (see F4 Help).
The 'External Identification' field specifies the number which was provided for this log by the application.
o If you also want to delete logs which have not reached the expiration date you must set the option "Also logs which can be deleted before the expiration date".
Select 'Help with application' in Transaction SLG2 for further explanation of the procedure for deleting.
SLG2 is a report transaction. The corresponding report is SBAL_DELETE. At regular intervals, this can be scheduled as a background job.
Releases < 4.6A:
=====================================================================
For Releases < 4.6A, note the following instructions:
In general, the deletion of application logs can be carried out in two steps:
1. Report RSSLG200: Deletion of all logs which expired:
Use report RSSLG200 to delete all logs whose expiration date is reached or exceeded. (This report is not yet available in the standard in Release 3.0F. In this case, the report can be installed in advance; see corrections attached to this note).
As of Release 3.1H, Report RSSLG210 is also available. This report allows the definition of a job that runs regularly and deletes such logs.
2. Report RSSLGK90: Deleting all logs for which a deletion is allowed before expiration:
Sometimes, step 1 does not delete enough logs. The reason for this might be that the expiration date of the logs is too far in the future or that no expiration date has been defined at all (in this case, depending
on the release, the assumed expiration date is 12/31/2098 or 12/31/9999)
Use report RSSLGK90 for these logs.
When you execute this report, you can restrict the logs to be deleted in a selection screen:
The fields 'Object' and 'Subobject' specify the application area which wrote the logs (see F4 help).
The field 'External number' indicates the number which was assigned by the application for this log.
Field 'Log class' indicates the importance of the log.
NOTE: By default, this field contains the value '4', this means only logs with additional information. If you want to delete all logs, enter the value '1' in this field. All logs with log class '1' or higher will then be deleted.
The fields 'To date' and 'Until time' refer to the creation date of a log.
If you enter 12/31/1998 and 23:59:59, you get all logs created in and before 1998
NOTES:
Client-dependency:
Note that the application log tables are client-dependent. Therefore, you must delete data in each client.
Which applications create entires in the application log:
To determine which applications create the logs, look in Table BALHDR to see which objects the logs were created for ( Transaction SE16, Table BALHDR, Field OBJECT). You can find the text description for the object in Table BALOBJT. The application is usually derived from the name and text of the object. The log is displayed in Transaction SL61. The display is restricted to certain objects, among other things.
Database error:
If very many data exists on the DB, Report RSSLGK90 might cause problems. In this case, implement Note 138715.
In very rare cases a dump is created even after Note 138715 was implemented:
 ABAP/4 runtime error DBIF_RSQL_SQL_ERROR
 SQL error 1555 occurred accessing table "BALHDR "
 Database error text...: "ORA-01555: snapshot too old
If you cannot correct the error by means of database utilities, Note 368700 provides a way to bypass this error.
Report RSSLG200 can also run into problems. In this case, use the correction for Report RSSLG200 attached to this Note.
Expiration date in Report RSSLGK90:
There are logs on the database which may only be deleted explicitly after the expiration date (flag DEL_BEFORE = 'X' in table BALHDR). These logs are not deleted in advance by report RSSLGK90. Since, however, this flag is used very rarely, you can ignore this data.
Restriction of the quantity of log data by the application:
To avoid large quantities of logs from different applications, also refer to the following notes:
- 91519
- 183960
- 141244
Archiving logs:
As of Release 6.20, it has been possible to archive logs.
The logs are archived via archiving object BC_SBAL.
The archiving programs are started via Transaction SARA (archive administration).
Via Support Packages, the archiving of application logs has been made available for Releases 4.6C (SAPKB46C27), 4.6D (SAPKB46D17), and 6.10 (SAPKB61011) as well.
Header Data
Release Status: Released for Customer
Released on: 04.08.2005 13:55:45
Master Language: German
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-SRV-BAL Basis Application Log
Affected Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_APPL 30 30F 31I
SAP_APPL 40 40A 40B
SAP_APPL 45 45A 45B
SAP_BASIS 46 46A 46D X
SAP_BASIS 60 610 640 X
Corrections Instructions
Correction
Instruction Valid
from Valid
to Software
Component Last
Modifcation
158903 30F 30F SAP_APPL 16.05.2000 07:13:08
162069 31H 45B SAP_APPL 16.05.2000 07:16:07
Related Notes
1009281 - LAW: Runtime error CONNE_IMPORT_WRONG_COMP_TYPE
856006 - Mass processing saves unnecessary logs
737696 - Add. info on upgrade to SAP R/3 Enterprise 4.70 Ext. 2 SR1
706478 - Preventing Basis tables from increasing considerably
637683 - Add info about upgrade to SAP R/3 Enterprise Core 4.70 Ext 2
587896 - Add. info on upgrade to SAP R/3 Enterprise Core 4.70 SR1
540019 - Report RJBTPRLO does not work correctly
400687 - Delete application log: DBIF_RSQL_INVALID_CURSOR
390062 - Additional information about upgrading to 4.6C SR2
370601 - Composite SAP note: APO 3.0 and 3.1 performance
365602 - M/AM: Sales agent determination log - perf.
327285 - Additions to upgrade to 4.6C SR1
183960 - ALE: Deactivating application logs for data transfers
141244 - Deactivating the application log during data transfer
138715 - RSSLGK90: Too many lock entries in the database
118314 - Installing the interface to a separate EH&S
91519 - Deleting logs of the application log
Print Selected Notes (PDF)
Attributes
Attribute Value
Transaction codes BALC
Transaction codes BALM
Transaction codes CLEAR
Transaction codes HIER
Transaction codes SARA
Transaction codes

Need help to develop Pythagoras theorem-

Hi i need help to develop proofs 2,3,4
of pythagoras theorems in java as demonstrations
These are applets can anyone help me with it or give me an idea of how to go about developing it -
the site is the following
http://www.uni-koeln.de/ew-fak/Mathe/Projekte/VisuPro/pythagoras/pythagoras.html
then double click on the screen to make it start

Pardon my ASCII art, but I've always liked the following, simple, geometric proof:
     a                   b
---------------------------------------+
|       |                                |
a|   I   |              II                |
|       |                                |
---------------------------------------+
|       |                                |
|       |                                |
|       |                                |
|       |                                |
|       |                                |
b| IV   |              III               |
|       |                                |
|       |                                |
|       |                                |
|       |                                |
|       |                                |
|       |                                |
---------------------------------------+It almost goes without saying that I+II+III+IV == (a+b)^2, and II == IV == a*b,
I == a*a and III == b*b, showing that (a+b)^2 == a^2+a*b+a*b+b^2.
I hope the following sketch makes sense, stand back, ASCII art alert again:     a                   b
---------------------------------------+
|               .             VI         |
|     .                 .                |a
| V                               .      |
|                                        +
|                                        |
|   .                                    |
b|                                     . |
|                                        |
|                  IX                    |
| .                                      |
|                                    .   |b
|                                        |
+                                        |
|      .                                 |
a|               .                  . VII |
| VIII                   .              |
---------------------------------------+
                 a                    bThe total area equals (a+b)^2 again and equals the sum of the smaller areas:
(a+b)^2 == V+VI+VII+VIII+IX. Let area IX be c^2 for whatever c may be.
V+VII == VI+VIII == a*b, so a^2+b^2+2*ab= c^2+2*a*b; IOW a^2+b^2 == c^2
Given this fundamental result, the others can easily be derived from this one,
or did I answer a question you didn't ask?
kind regards,
Jos

I need help to find and open a job app that I exported, was able to fill out and sign and saved and now can't open it? What did I do wrong?

I need help to find and open a job app that I exported, was able to fill out and sign and saved and now can't open it? What did I do wrong?

What file format did you export it to?

Need help to open audios attached in a PDF file

Hello
I just need help. I have ordered a reviewer online that has audios and texts in a pdf file. I was told to download the latest adobe reader on my computer. I have done the same thing on my ipad mini. I am not so technical with regards to these things. Therefore I need help. I can access the audios on my computer but not on my ipad.
I want to listen to audios with scripts or texts on them so i can listen to them when i am on the go. I was also informed that these files should work in any device. How come the audios doesnt work on my ipad.
Please help me on what to do.
Thanks

Audio and video are not currently support on Adobe Reader. :-<
You need to buy a PDF reader that supports them. My suggestion is PDF Expert from Readdle ($US 9.99)

Need help to open and look for file by name

Hi,
Im needing help to open a folder and look for a file (.txt) on this directory by his name ... The user ll type the partial name of file , and i need look for this file on the folder , and delete it ....
How can i look for the file by his name ?
Thx =)

Hi ,
Sry ,, let me explain again ... I ll set the name of the files in the follow order ... Name_Serial_date_chanel.sxc ..
The user ll type the serial that he wants delete ...
I already figured out what i need guys .. thx for the help ^^
I used List Directory on advanced IO , to list all .. the Name is the same for all ... then i used Name_ concateneted with Serial(typed)* .. this command serial* ll list all serials equal the typed , in my case , ll exist only one , cuz its a count this serial .Then i pass the path to the delete , and its done !
Thx ^^

I need help, my ipod touch is not recognized by windows as a harddisk

i need help, my ipod touch is not recognized by windows like a memory card or a harddisk.
i would like to transfer the files from pc to my ipod touch without useing itunes.
as i see theres some people here that theires ipod touch are recongnzed as a digitl camra, mine is reconzied as nothing, some help plz.
Message was edited by: B0Om

B0Om wrote:
ok but i still dont understed, only my itnes recongnize my ipod, when i go to " my cumputer, it dosent show up there, not even as a digital camra
Your Touch is working correctly. Currently, without unsupported third party hacks, the Touch has NO disc mode. It will only show up in iTunes.
how do i put programes and games in my ipod touch
Right now, you don't. The SDK is scheduled to be released in Feburary. Then developers will be able to write programs that will be loadable.

Weird error message need help..

SO.. i havent updated my itunes in a while because i keep getting this weird message.. it comes up when im almost done installing the newest/newer versions of itunes. it says
"the feature you are trying to use is on a network resource that is unavailable" "click ok to try again or enter an alternate path to a folder containing the installation package 'iTunes.msi' in the box below"
now when ever i choose a file from the browse box it replies with this message "the file 'xxx' is not a valid installation package for the product iTunes. try to find the installation package iTunes.msi in a folder from which you can install iTunes."
no idea need help thanks
~~~lake
Message was edited by: DarkxFlamexCaster
Message was edited by: DarkxFlamexCaster

+it comes up when im almost done installing the newest/newer versions of itunes. it says+ +"the feature you are trying to use is on a network resource that is unavailable" "click ok to try again or enter an alternate path to a folder containing the installation package 'iTunes.msi' in the box below"+
With that one, let's try the following procedure.
First, head into your Add/Remove programs and uninstall your QuickTime. If it goes, good. If it doesn't, we'll just attend to it when we attend to iTunes.
Next, download and install the Windows Installer CleanUp utility:
Description of the Windows Installer CleanUp Utility
Now launch Windows Installer CleanUp ("Start > All Programs > Windows Install Clean Up"), find any iTunes and/or QuickTime entries in the list of programs in CleanUp, select those entries, and click “remove”.
Next, we'll manually remove any leftover iTunes or QuickTime program files:
(1) Open Local Disk (C:) in Computer or whichever disk programs are installed on.
(2) Open the Program Files folder.
(3) Right-click the iTunes folder and select Delete and choose Yes when asked to confirm the deletion.
(4) Right-click the QuickTime folder and select Delete and choose Yes when asked to confirm the deletion. (Note: This folder may have already been deleted if QuickTime was successfully removed using Add/Remove Programs earlier.)
(5) Delete the QuickTime and QuicktimeVR files located in the C:\Windows\system32\ folder. Click Continue if Windows needs confirmation or permission to continue. (Note: These files may have already been deleted if QuickTime was successfully removed using Add/Remove Programs earlier.)
(6) Right-click on the Recycle Bin and on the shortcut menu, click Empty Recycle Bin.
(7) Restart your computer.
Now try another iTunes install. Does it go through properly now?

Need help in ALE

Similar Messages

Maybe you are looking for