| SPO America's »Legacy Link«
Generally the R/3 interface team
faces the following problems:
- Satisfying the business rules and
data integrity checks incorporated in the new system.
- Maintaining a consistent approach
in terms of operation, error and exception handling, duplicate processing etc.
- Uniform approach in designing
interface between the new and other application running across different operating
systems.
- In the case of inbound transfer,
the problem of identifying the right sequence of screens, programs and input field
requirements for each transaction.
- And in outbound transfer, knowing
the complete logical and physical database model and relationships between corresponding
entities
In order to
create a solution to the above mentioned problems, SPO America has developed a tool called
the Legacy Link. This allows the designer to identify the right sequence of programs,
screens and fields. While this tool facilitates a development with uniform data transfer
control mechanisms between R/3 and other applications, it also generates BDC programs.
You only need to choose

Legacy Link offers three
different levels of solutions.
- Cut Over Support
- Interface support with user
supplied link programs
- Interface support with cooperation
partner software
Program generation,
a piece of cake.

To generate an interface, the
system has to know, which SAP pro gram and screen will be used. The user has to enter this
data in the definition step or he runs the transaction via Legacy Link screen caption
function with typical data. Legacy Link will then automatically supply the information.
To get the documentation and worksheets for the mapping process, the system provides a
legacy data dictionary. This information can be used to attach SAP fields to legacy
fields. Legacy Link allows to insert additional work fields for processing in user exits
to generate infor- mation, which is not available during extraction time.
Legacy Link minimizes the effort
The system produces a stand
alone BDC program set:

A specific scenario controller
- parameter driven
- list reporting
- A scenario program
- A user exit program
For use with the gate
controller as permanent interface
- A validation program
- A user validation program
For test purposes
A template program for test data.
A fully automated
interface solution

The system expects the data at the
gate controller. From here, an identification process takes care of validity and
processing options.
Batch files have
there specific naming convention, to allow multiple processing in all steps. Batch
arrivals for immediate processing are automatically handled by a dispatcher. Remote or
local function calls are independent from batch processes.
If you want to learn more about , please
go to the About SPO page and fill out the form. We will
provide you with additional information ASAP.
Home |
About | SAP
Jobs | SAP Consulting
| SPO Tools | LegacyLink |
JobMan | StressTest
Back to Top
|