As already mentioned in the short summary above the scenario used for this collaboration brief deals with two key components: Microsoft Active Directory and SAP Central User Administration. Active Directory, being the integrated, distributed directory service included with Microsoft Windows Server 2003 and Microsoft Windows 2000 Server, provides a central user repository used to centrally maintain user data, thus avoiding the redundant, error-prone maintenance of user information in several systems. Most organizations already use Active Directory to organize and manage information about all kinds of their different resources like users, computers, applications and so on.
Read the rest of this entry »

• 0 Comments

There are several ways to import Microsoft Access tables into SAS. They are as follows:
1) Using SAS/ACCESS to ODBC:
1) SAS/CORE, SAS/BASE and SAS/ACCESS interface to ODBC licensed and installed at your site.
2) The Microsoft Access ODBC driver must be installed and configured on your PC.
3) Use the following code to read the Microsoft Access file into a SAS dataset. Libname sasuser ‘c:\foo’;
Read the rest of this entry »

• 0 Comments

In order to translate in the R/3 System, you will need to maintain the translation environment. You set up the translation environment in transactions SLWA and SLWB. Implementation Considerations Before you start maintaining the translation environment, you should: · provide or extend system resources - please see System Resource Setup [Page 10] · perform administrative measures and preparation - please see Administrative Measures [Page 11] The translation environment must be defined before the start of productive translation. Integration After you have completed the above preparation, you start maintaining the translation environment in transaction SLWA.
Read the rest of this entry »

• 0 Comments

This topic gives you a quick overview of the functionality in transaction SE63. However, for a detailed explanation of the various functions, please refer to the individual topics. Working With SE63 You translate short texts and long texts in the respective editors within transaction SE63. To call up this transaction, either: • Enter /NSE63 in the command field in the initial screen of the R/3 System • Choose Tools ? ABAP/4 Workbench ? Utilities ? Translation ? Short/Long texts on the initial screen of the R/3 System. You can translate texts either: • By using a worklist • By calling up the objects directly.
Read the rest of this entry »

• 0 Comments

Use Intensive test phases, with function and acceptance tests in all phases, are essential to the success of an R/3 project. This starts with the first implementation of an SAP System and continues through all modifications of the system to customer requirements by customizing, modification and customer developments. SAP provides the Test Workbench to support customers in this area. From the test planning stage onwards, the Test Organizer in the Test Workbench provides a tool to create a structure of the applications to be tested. Individual test cases can be created when planning is complete.
Read the rest of this entry »

• 0 Comments

RFC with External Systems In the SAP System, the ability to call remote functions is provided by the Remote Function Call (RFC) interface. This interface allows for remote calls between two SAP Systems (R/3 as of Release 2.1 and R/2 as of Release 5.0D), or between an SAP System and a non-SAP system. The present section describes how to write RFC partner programs that run in non-SAP Systems. If you are writing RFC programs in an SAP System, see RFC-Programming in ABAP [Ext.]. Client and Server Programs RFC programs for non-SAP Systems can function as either the caller or the called program in an RFC communication. There are two kinds of RFC programs: RFC client and RFC server programs: The RFC client is the instance that calls up the RFC to execute the function which is provided by an RFC server.
Read the rest of this entry »

• 0 Comments

The function library in R/3 provides a facility for generating and then downloading RFC programs to a workstation or PC. This facility is the RFC Interface Generator. With this tool, you can create RFC stub programs (that call SAP function modules) and example programs (that show how to call stub programs). The RFC Generator is only available for and in R/3 Systems and not for R/2 Systems. Generating RFC Stubs: RFC stub programs contain all the parameter-handling and communications necessary to call SAP function modules from a non-SAP System. Once a stub has been exported to your machine, you can compile it as a library file or DLL (dynamic-link library) routine. DLL routines can be called without having been linked together with your program at compile time. You can call DLL routines from any programming language whose compiler offers DLL options. (This includes, for example, most recent C and BASIC compilers.)
Read the rest of this entry »

• 0 Comments

The SAP System is equipped with a special lock mechanism that synchronizes access to data on the database. The purpose of the lock mechanism is to prevent two transactions from changing the same data on the database simultaneously. Implementation Considerations Locks are defined generically as “lock objects” in the Data Dictionary. A lock request is a specific instance of a lock object and locks a certain database object, such as a correction or a table entry. Lock entries are usually set and deleted automatically when user programs access a data object and release it again.
Read the rest of this entry »

• 0 Comments