CA Component Short Description - Jessemerin.com · CA Component Short Description SAP AG Document...

™

CA Component ShortDescription

HE

LP

.CA

CO

MP

CA

Re lease 4 .6B

CA Component Short Description SAP AG

2 December 1999

Copyright

© Copyright 2000 SAP AG. All rights reserved.

No part of this brochure may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed withoutprior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks ofMicrosoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM

are registered trademarks ofInformix Software Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World WideWeb Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute ofTechnology, 545 Technology Square, Cambridge, MA 02139.

JAVA® is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto,CA 94303 USA.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.comBusiness Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAPBusiness Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, ManagementCockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in severalother countries all over the world. All other products mentioned are trademarks or registeredtrademarks of their respective companies.

SAP AG CA Component Short Description

December 1999 3

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Tip


4 December 1999

Contents

CA Component Short Description.....................................................................5Document Management ................................................................................................................ 6Document Processing................................................................................................................... 7Find Document............................................................................................................................... 8Classification ................................................................................................................................. 9Characteristics............................................................................................................................. 10Classes ......................................................................................................................................... 11Classification ............................................................................................................................... 12Object Selection........................................................................................................................... 13CAD Integration ........................................................................................................................... 14Objects Supported....................................................................................................................... 15CAD Function Libraries............................................................................................................... 16CA - Message Control ................................................................................................................. 17Business Framework Architecture ............................................................................................ 20ALE Integration Technology....................................................................................................... 21

Modeling ................................................................................................................................... 23Replication................................................................................................................................ 24Communication......................................................................................................................... 25Tools ......................................................................................................................................... 26

BAPI Interface Technology......................................................................................................... 27Web Basis..................................................................................................................................... 28Computer Aided Test Tool.......................................................................................................... 29CATT Tool..................................................................................................................................... 30Test Plan Administration ............................................................................................................ 31


CA Component Short Description

December 1999 5

CA Component Short Description


Document Management

6 December 1999

Document ManagementDefinitionThe R/3 document management system (DMS) comprises a range of functions for managingdocuments that may the stored both in your R/3 System and outside.

The DMS allows you to make documents available on a company-wide basis and to link them toSAP objects from various other application areas, such as material masters, change masters,and production resources and tools. You can automate the entire life cycle of a document, fromdocument creation through document storage.

Selection criteriaYou require this component if you want to set up a document management system in yourcompany.


Document Processing

December 1999 7

Document ProcessingDefinitionTo manage the documents in the document management system (DMS), you maintain documentinfo records.

A document info record is identified by the fields of the document key (document number,document type, document part, document version). A document info record contains master datawhich is required to manage documents and to integrate them in the flow of businesstransactions in a company. Some of the data has a control function, and some is purelydescriptive. There is also administrative data, which is maintained by the system.

The DMS supports the following interfaces to internal systems:

• links to other SAP objects (for example, material master)

• classification

• engineering change management with integrated workflow

• SAP Workflow

• bills of material

You can also use the interfaces to the following external system to process document inforecords:

• any workstation application

• CAD systems via SAP-CAD interface

• ArchiveLink via SAP ArchiveLink

Selection criteriaYou require this component if you want to manage documents in the R/3 System. If you are usinginternal or external interfaces to process documents, you must also install the relevantcomponents (for example, classification). There are no specific SAP components that you haveto install if you want to use interfaces to workstation applications. Before you can use aninterface, you must make certain settings in the customizing functions for documentmanagement.


Find Document

8 December 1999

Find DocumentDefinitionThis is an efficient tool for finding documents, which allows you to search from different views.

You can limit the hit list by entering the document data that you know. You have the followingoptions:

• Find via main parameters

• Find using classes (for classified documents)

• Enter selection parameters

• Find via status

• Find via linked objects

• Find via text elements

Selection criteriaYou should install this component if you use the DMS to manage documents. The functionality ofthis component allows you to find existing documents very quickly.


Classification

December 1999 9

ClassificationDefinitionThe function of a classification system is to describe all kinds of objects (for example, materials,batches, work centers) by means of their characteristics, allowing you to group similar objectstogether in classes according to criteria you define. This allocation of objects to classes is whatwe mean by classification.

You can then use classes and the characteristics defined in them to help you to find objects. Thisensures that you can find objects with similar or identical characteristics as quickly as possible.

Finding objectsClassification

Value assignment

Functions Classification System

Class maintenance

Class TRUCK

Object ACMETRUCK

Attributes

- Length- Area of use- Price- Volume- Head height- Thread length- Age- and so on

Char. maintenance

Characteristics

- Weight

- Color- Height- Width- Manufacturer- Registration

LengthManufacturerRegistrationFreight volumePowerArea of use

- 11 Meters- ACME- 05/05/1993- 54 sqm- 200kW- international

AllocationObject ACMETRUCKClass Truck

- 11 Meters- ACME- 03.01.1994- 54 m- 200 kW_

3

LengthManufacturerRegistrationFreight vol.PowerTruck No.

Finding an initialclass for thesearch

Findingobjects in theclass

- Length- Manufacturer- Registration- Freight volume- Power- Truck No.


Characteristics

10 December 1999

CharacteristicsDefinition

Characteristics play an important part in the classification of objects. You can use a characteristicto describe any property of an object, such as the length of a bolt, the color of a casing, or theshelf life of a food product.

Characteristics are used in many different application areas to describe many different propertiesof objects. This means that functions for creating and maintaining characteristics need to supporta wide range of options, such as:

• Different characteristic formats, with checks on user entries (for example, numeric,alphanumeric)

• Units of measure

• Value sets

• Language-dependent text processing


Classes

December 1999 11

ClassesDefinitionThe objects that you want to organize in the classification system must be allocated to classes.Before you can do this, you first have to set up the classes. Classes contain characteristics todescribe object features.


Classification

12 December 1999

ClassificationDefinitionClassification means allocating objects to classes and assigning values to the objects.

Once you have created the classes for your classification system, you can allocate objects tothem. The objects are described by means of the characteristics contained in the class.

When you have classified your objects, you can use the classification system to help you findobjects with the features you require.


Object Selection

December 1999 13

Object SelectionDefinitionOnce you have classified objects in classes, you can search for them in the system.

To find a particular object in the classification system, the system must perform two steps:

• find the class in which the object was classified

• find the required object in the class

The system uses the characteristics as search criteria by assigning values to them andcomparing the values to those of the objects classified in the class.


CAD Integration

14 December 1999

CAD IntegrationDefinitionThe CAD interface links the SAP System to external technical applications (for example, CAD,PDM, GIS).

This enables your designers to access data in the production system (for example, informationon existing materials and assemblies) and use this information in their work. Since data can betransferred between the external system and the SAP System in both directions, inconsistency ofthe data in the two systems is avoided.

Selection criteriaYou require this component if you want to link the SAP System to an external technicalapplication.


Objects Supported

December 1999 15

Objects SupportedDefinitionThe SAP Function Library is a set of subroutines written in the C programming language. Eachsubroutine performs a particular function in the communication process with the SAP interfaceprogram. The SAP Function Library must be integrated in the technical application to allow thevarious functions to be accessed from there.

You can use functions of the SAP dialog interface for the following application areas:

• General functions

• Material master record functions

• Classification functions

• Document management functions

• Bill of material functions

• Plant maintenance functions

• Engineering change management functions

• Office functions

• User-defined functions


CAD Function Libraries

16 December 1999

CAD Function LibrariesDefinitionYou can use the CAD interface for the following functions to transfer data online between anexternal technical system and your SAP System:

• General functions

• Material master record functions

• Document management functions

• Bill of material functions

• Plant maintenance functions

• Engineering change management functions

• Mail and Workflow functions


CA - Message Control

December 1999 17

CA - Message ControlPurposeThe output or follow up processing of partner-dependent messages is automated via MessageControl. The application then calls the Message Control via the specified interfaces.

You can use these interfaces to describe various data combinations along with the requiredprocessing. If one of these data combinations appears during processing, the appropriateprocessing is started (synchronously or asynchronously). You can define processing with severaldifferent methods, for example as a workflow, print output or as an IDoc dispatch for EDI.

Implementation considerationsSD and MM applications always use Message Control for message output. You carry outCustomizing of the Message Control in the application’s Customizing. The Message Control isalso sometimes described here as “output control“.

IntegrationMessage Control is a "service program" for other applications. It is initiated via ABAP functionmodules. An application that uses Message Control must

• call the Message Control.

• transfer files which should be compared with the combinations defined in Customizing.

• provide a processed program, that is called from the Message Control, if the transferred datacorresponds with the combinations defined in Customizing

FeaturesThe condition technique in the R/3 System is used to formulate the data combinations required. Ifthe current application data corresponds to the conditions defined in Customizing, messagedetermination was successful and created a message default. If the application supports it, theproposal can be changed (processed).

As a result the message is processed immediately or at a defined time. The processing status ofthe message is stored in a status record. If the application supports it, a processing log is writtenas well.

Message Control scenarios:

• The credit limit has been exceeded in a sales order, whereupon the blockindicator is assigned. The Message Control should respond to the blockindicator by printing out this customer’s account history.

• A document is released and receives a corresponding status in its datarecord. The Message Control should thereupon issue a release message.

There are also applications which can “switch off” message determination anddirectly generate the message default.



18 December 1999

Message Control and connection to the R/3 application

receives statusIs processed

starts

.. Print

. . .

Fax Telex Mail EDI CPIC Workflow event

Messageprocessing

Processing program

calls transfers data

proposes

assignschecksprocesses

writes

Communication structures

Condition tables

Message determination

Message status

Message proposal

R/3 application Application object

Condition components

See also:Message Control Structure [Ext.]

The section describes the Message Control in Detail.

Message Control Customizing [Ext.]

You determine the rules in Customizing by which the system accesses the individual conditionrecords.



December 1999 19

Define messages as condition records in the application [Ext.]

You define concrete messages as condition records in the application.

Message Control connection to the application [Ext.]

The section is aimed at developers who want to install Message Control in an application.

ConstraintsThe Message Control only supports specific transmission media. For more information, see

Transmission media [Ext.]


Business Framework Architecture

20 December 1999

Business Framework ArchitecturePurposeThe Business Framework is the new strategic architecture of the R/3 System. It is based onbusiness components - configured software modules and it provides organizations with aversatile business infrastructure.

With the Business Framework Architecture (BFA), SAP defines the technical and conceptionalframework in which independent business components can be integrated and communicate witheach other. Business software can respond quickly to new requirements and can be changedand enhanced without disrupting business processes.

The Business Framework enables:

• Systems to be installed more quickly and easily and business processes to be optimized.

• Business components to be implemented in stages. Business components areconfigurable software modules that can be integrated using standard interfaces(Business Application Programming Interfaces, BAPIs), thus providing versatility andflexibility.

• Quick updating and dynamic reconfiguration of business processes, independently ofconventional release cycles.

• Easy integration of Internet and Intranet components in business processes.

• R/3 System software to be easily connected to software of other manufacturers and tocustomers’ own developments.

• The latest technology to be implemented without disrupting with business processes.

FeaturesThe fundamental components of the Business Framework Architecture are standardized,business programming interfaces - Business Application Programming Interfaces (BAPIs).BAPI interface technology enables simple access to R/3 business functions. BAPIs provide thebasis for integrating software components, regardless of whether they have been developed bySAP and SAP customers and partners or by external software manufacturers.

The stable messaging technology of Application Link Enabling (ALE) and SAP BusinessWorkflow enable software integration and the distribution of business information within theBusiness Framework. SAP business objects are the central units for the interoperability and arefundamental to ALE technology.

Using independent components (Internet Application Components) Web Basis makes R/3business functions available across the Internet and enables business processes to beintegrated.


ALE Integration Technology

December 1999 21

ALE Integration TechnologyPurposeThe integration technology Application Link Enabling (ALE) is an important middleware tool inSAP's Business Framework Architecture [Ext.] (BFA). BFA is a component-based architectureenabling software components from SAP and from other software vendors to communicate andbe integrated with each other.

ALE can integrate business processes between R/3 Systems and non-R/3 systems as well asbetween R/3 Systems.

Data is exchanged between applications and remains consistent in all applications.

Company-wide applications such as accounting, human resource management andsales planning may be carried out in the company’s headquarters, whereasproduction and materials management may be carried out in decentralized plants.

Application systems are loosely coupled in an ALE integrated system. Data is exchangedasynchronously, whereby the data arrives in the receiver system, even if the receiver systemcannot be connected to at the time the data is sent. ALE uses synchronous communication forreading data only.

ALE provides administration, development and testing tools.

To use the ALE tools choose Tools → ALE.

ALE business processes are part of the standard R/3 delivery. They are documented in theLibrary of ALE Business Processes [Ext.].

For more information about the required system settings see the R/3 Implementation Guide.

Tools → AcceleratedSAP → Customizing → Project Management

SAP Reference IMG

Basis → Application Link Enabling (ALE).

For information on programming see the ALE Programming Guide [Ext.].

Implementation ConsiderationsDecentralized business applications ensuring data consistency are used because:

• The increasing globalization of markets has led to the physical division of organizationalunits.

• Business processes are not restricted to one organization only and more and morecustomers and vendors are becoming involved.

• R/3 System performance can be improved by distributing the business applications.

FeaturesALE supports the configuration and operation of distributed applications. ALE controls Messaging[Ext.] across loosely coupled R/3 Systems, ensuring that data is always consistent.


ALE Integration Technology

22 December 1999

Applications are integrated using a local database rather than a central one. There is no dataretention. ALE guarantees the distribution and synchronization of master data, Customizing dataand transaction data through asynchronous communication.

Synchronous communication is used in ALE to read data only.

ALE has many benefits:

• Application data can be distributed between different releases of R/3 Systems

• Data can continue to be exchanged after a release upgrade without requiring specialmaintenance

• Customers can add their own enhancements

• Communication interfaces enable connections to non-SAP systems.

• R/3 and R/2 Systems can communicate with each other.

ALE has functions for monitoring messages flows and handling communication problems.


Modeling

December 1999 23

ModelingThe settings made in the distribution model determine which applications communicate with eachother across the distributed systems. The distribution system contains all the system-widemessages flows in the organization.

Filters set for the individual message flows specify exactly which data is transferred to whichreceivers and the distribution model controls the data distribution.

The distribution model consists of individual model views and associated message flows can bedefined in each one. Each model view is maintained in one central system and distributed fromhere to the other systems.


Replication

24 December 1999

ReplicationPurposeThe distribution of application functions is based on asynchronous messaging using ALEoutbound and inbound processing.

PrerequisitesMessaging is based on IDocs. IDocs are created and dispatched for distributing messages typesand methods.

Process flowAn application creates a master IDoc containing the required data. The IDoc is passed to theALE layer where it is dispatched.

The IDoc is imported into the target system and triggers inbound processing. The data isprocessed and posted in the application according to specified settings either automatically orwith some manual intervention.

Both inbound and outbound IDocs can be processed either individually or in packets (massprocessing). In mass processing several IDocs are processing in one packet.

R/3 System 2Workflow ‘inbound'

Application functions

Filter/convertdata

Applicationdata

Comm.-IDoc

R/3 System 1 Workflow-‘outbound'IDOC

Comm.IDoc

Receiverdetermination

Filter/convert data

Generate IDocApplicationApplicationApplication Master-IDoc

ApplicationApplication ALEALE CommunicationCommunication

CarrierCarrier


Communication

December 1999 25

CommunicationA number of settings must be made for systems to communicate with each other:

• Define RFC destinations

The remote function call is defined in the parameters of the RFC destination.

• Assign RFC destinations to be used for synchronous method calls

RFC destinations must be assigned to call BAPIs synchronously and dialog methods inother logical systems.

• Generate partner profiles

The partner profiles are defined for all outbound and inbound messages based oninformation in the distribution model.

• Check partner profiles and settings in the distribution model

The consistency of the partner profiles and settings in the distribution model must bechecked.

• Set up communication control

The data transfer to the receiving system and the processing status here are checked.


Tools

26 December 1999

ToolsPurposeApplication Link Enabling provides tools to set up and monitor ALE functions:

• ALE audit to monitor the processing status of IDocs

• ALE performance to optimize ALE processing

• Serialization of messages


BAPI Interface Technology

December 1999 27

BAPI Interface TechnologyPurpose

SAP business objects and their methods, Business Application ProgrammingInterfaces (BAPIs), are the central component of Business Framework and thefundamental prerequisite enabling independent business components to interact with eachother. BAPIs are standardized, business programming interfaces that enable easy accessto business functions in the R/3 System.

BAPIs provide stable, standardized interfaces for the integration of non-SAP software andapplications in the Business Framework. These interfaces are defined by SAP in cooperationwith customers, partners and prominent standards organizations.


Web Basis

28 December 1999

Web BasisPurposeWith Web Basis Internet enables the processing of business functions and processes within theBusiness Framework. Using Web Basis business functions and processes can be accessed andintegrated into other business processes over the Internet using Web browser interfaces

FeaturesInternet Application Components (IACs), delivered in the standard R/3 System are part ofWeb Basis. IACs enables business processes to be processed both within an organization andbeyond the boundaries of the organization. IACs are grouped into the following implementationareas:

•••• Intranet, for business processes internal to the organization

•••• Consumer-to-Business, for business processes between one organizations and its endcustomers

•••• Business-to-Business, for business processes between organizations, for example, betweenone company and its suppliers

Web Basis is based on the technology of the Internet Transaction Server (ITS). The ITS is theinterface controlling the communication and data exchange between the R/3 System and aHyperText Transport Protocol (HTTP) server.

Using ITS functions customers and partners can develop application components toprovide R/3 functions over the Internet. A further component of the ITS is the SAP@WebStudio - a tool used to create and modify Internet Application Components and enablingIAC development objects to be managed in the R/3 Workbench Organizer.


Computer Aided Test Tool

December 1999 29

Computer Aided Test ToolDefinitionCATT allows you to collect and automate repeatable commercial procedures in test procedures.You can create modules for individual transactions and test procedures for a completecommercial procedure in the SAP System.

CATT procedures are used e.g. for the following purposes:

• test transactions

• test system messages

• calculate values and update database

• setup customizing tables

• test reactions to customizing setting changes


CATT Tool

30 December 1999

CATT ToolDefinitionThis tool allows you to collect and automate repeatable commercial procedures in testprocedures. The use of CATT reduces the number of manual tests and makes you testsystematically by defining inputs and planning test results.


Test Plan Administration

December 1999 31

Test Plan AdministrationDefinitionThe test plan management tool supports the set-up, performance and analysis of tests. It isbased on the SAP Hypertext concept. A hierarchy of test cases is constructed across allapplications. The test cases are the bottom level in the hierarchy.

Date post:	17-Mar-2020
Category:	Documents
Upload:	others
View:	19 times
Download:	0 times

CA Component Short Description - Jessemerin.com · CA Component Short Description SAP AG Document...

Documents