ALL SAP Netweaver

Procedure documentation Configuring Size of Data Packets and Frequency

2009-01-07T12:04:00.002+05:30

Use

To upload large sized flat files, the setting of the following parameters within the BW Customizing is important:

Size of data packets
Frequency

For data transfer into BW, the individual data records are sent in packets of variable size. Using the parameters for the size of data packets you can control how large a data packet typically is. If no entry is maintained, the data is transferred with the default setting of 10,000 Kbytes per data packet. Within BW Customizing you can increase this setting to 40,000 Kbytes or higher.

By specifying the frequency, you determine after how many data IDocs an Info IDoc is sent, or how many data IDocs are described by an Info IDoc. Choose a frequency of between 5 and 10, but not greater than 20.

Procedure

Open the customizing tree from the SAP Easy Access menu under the folder Tools

Business Engineer

Double-click on BW Customizing and select SAP Reference IMG.

Expand the tree BW Customizing Implementation Guide

Business Information Warehouse

Links to Other Systems

Maintain Control Parameters for the data transfer.

Change the parameters as required.

Expanding Table Spaces

2009-01-07T12:04:00.001+05:30

Use

SAP recommends that the following table spaces should be expanded:

PSAPSTABD
PSAPSTABI
PSAPFACTD
PSAPFACTI
PSAPDIMD
PSAPDIMI
PSAPCLUD
PSAPODSI
PSAPTEMP

The following table can be used as a guide. It illustrates the table space sizes that are used to upload 1,8 million records based on an Oracle database.

Table space sizes

Table space	Size (kb)	Free
PSAPSTABD	2.048.000	At least 1.6 GB free
PSAPSTABI	2.048.000	At least 1.6 GB free
PSAPFACTD	716.800
PSAPFACTI	965.904
PSAPDIMD	102.400
PSAPDIMI	117.744	At least 40 MB free
PSAPCLUD	51.200
PSAPODSI	2.702.824
PSAPTEMP	5.013.480	At least 5 GB free

Procedure

For detailed information, see SAP note number 184905.

Customizing BW for the Usage of the D&B Marketing Universe

2009-01-07T12:03:00.002+05:30

Procedure

In your BW system, select transaction rsmonitor_db.

From the Environment menu, choose D&B Registration.

Create a new scenario using the Create icon.

If you are using a SAP CRM system, choose the logical system name of your CRM system. If you use a 3^rd party CRM leave the logical system blank.

In the field CRM Scenarios choose D&B Integration of external Data.

Save your scenario.

Customizing for Business Partner Creation from BW in SAP CRM

2009-01-07T12:03:00.001+05:30

Procedure

In your CRM system, register the InfoObject DUNS Number 0DBDUNS_NUM as an identification object for the business partner.

Use transaction sm30 to maintain the table RSCRMEXTERN as follows:

Logical System: system name of the CRM system

InfoObject: 0DBDUNS_NUM

InfoObject: 0BPARTNER

ID Category: BUP001 (provided with the customizing of your CRM system)

Maximal allowed age of master data (in calendar days): for example 365 for 1 year

Bear in mind that the D&B scenario is a B2B scenario. Therefore only companies and organizations are considered as business partner. To check if the ID category BUP001 is valid for organizations proceed as follows:

In your CRM system, use transaction sm30 to display the table v_tab039A.

Mark the row with BUP001 and click on the Details icon.

The Identificationtype should be relevant for organizations only.

InfoPackages for Initial Upload

2009-01-07T12:02:00.001+05:30

Together with the first D&B data files you also receive some D&B files containing customer-independent information. These files need to be uploaded only once. To prepare the upload process you create the required InfoPackages.

The following table shows the files you get from D&B for the initial upload. For each file you create one InfoPackage. In the right column you see the InfoObjects to which the new InfoPackages belong.

D&B File	Technical name	InfoObject for which you create the InfoPackage
Legal Status Text File	0DBLGLSTAT_TEXT.CSV	0DBLGLSTAT
D&B Rating Net Worth - Text	0DBRATENW_TEXT_MU.CSV	0DBRATENW
D&B Rating Condition – Text	0DBRATECON_TEXT_MU.CSV	0DBRATECON
D&B Score - Text	0DBSCORE_TEXT_MU.CSV	0DBSCORE
D&B Sector Code - Text	0DBSECTCOD_TEXT_MU.CSV	0DBSECTCOD
Country Code Text File	0DBCTRYCOD_TEXT.CSV	0DBCTRYCOD
D&B Region Code - Text	0DBREGCOD_TEXT_MU.CSV	0DBREGCOD
D&B Area Code - Text	0DBAREACOD_TEXT_MU.CSV	0DBAREACOD
D&B District Code - Text	0DBDISTRCOD_TEXT_MU.CSV	0DBDISTRCOD
SIC Text File	0DB87SIC1_TEXT.CSV	0DB87SIC1
SIC Hierarchy File	0DB87SIC1_HIER.CSV	0DB87SIC1

All the InfoPackages have got the same pattern as described in following table. Create the InfoPackages with this information.

Tab	Field	Value
Select data
		No entries required
External data
	Load external data from	Application server
	File name	A combination of the path of the working directory on the application server and the file name For example D:\usr\sap\QB5\D19\work/0DBLGLSTAT_TEXT.CSV for InfoPackage 0DBLGLSTAT_TEXT Ask your system administrator which directories the files will be stored in (see also Storing D&B Data on an Application Server)
	Control file	No
	File type	CSV file
	Data separator	,
	Escape sign	"
External data parameters
	Thousand separator	,
	Character for decimal point	.
	Number of headers that should be ignored when loading	1
Processing
	Update data	PSA and then in the InfoObject
Update parameters
	Update mode	Full update

InfoPackages for Repeated Upload

2009-01-07T12:01:00.000+05:30

Each time D&B provides new data, the master data for the InfoObjects DUNS Number (0DBDUNS_NUM) and Customer number (0CUSTOMER) require updating. If you are using a SAP CRM system, the InfoObject Business Partner (0BPARTNER) also requires updating. The data has also to be loaded into the MarketingCube. For this purpose the following files are sent from D&B:

D&B Marketing Universe Matched Client File

(0DB_IMPORTFILE_MU.csv)

D-U-N-S Text File

(0DBDUNS_NUM_TEXT_MU.csv)

D&B Universe of Abstract Data

(0DBDUNS_NUM_ABSTRACT_MU.csv)

The first time you get data from D&B, D&B provides these files in addition to the files required for initial upload.

For the InfoObjects 0CUSTOMER, 0BPARTNER and 0DBDUNS_NUM new InfoPackages are required. The D&B Marketing Cube (InfoSource 0DB_MKT_1) needs one new InfoPackage as well.

For the InfoObject 0DBDUNS_NUM you create four InfoPackages for the different data sources:

One for the text description (data source 0DBDUNS_NUM_TEXT)

Three for the master data upload (for each data source 0DBDUNS_NUM_ATTR, 0DBDUNS_NUM2_ATTR, 0DBDUNS_NUM3_ATTR).

For each of the InfoObjects 0CUSTOMER and 0BPARTNER and for the D&B Marketing Cube (InfoSource 0DB_MKT_1) you create one new InfoPackage.

The parameters of the InfoPackages are described in the following tables. Create the InfoPackages with this information.

InfoPackages 0DBDUNS_NUM_TEXT, 0DBDUNS_NUM_ATTR and 0DBDUNS_NUM3_ATTR

Tab	Field	Value
Select data
		No entries required
External data
	Load external data from	Application server
	File name	A combination of the path of the working directory on the application server and the file name. For example D:\usr\sap\QB5\D19\work/0DBDUNS_NUM_ABSTRACT_MU.CSV for InfoPackage 0DBDUNS_NUM_ATTR D:\usr\sap\QB5\D19\work/0DBDUNS_NUM_CONT_MU.csv for InfoPackage 0DBDUNS_NUM3_ATTR D:\usr\sap\QB5\D19\work/0DBDUNS_NUM_TEXT_MU.csv for InfoPackage 0DBDUNS_NUM_TEXT Ask your system administrator which directories the files will be stored in (see also Storing D&B Data on an Application Server)
	Control file	No
	File type	CSV file
	Data separator	,
	Escape sign	"
External data parameters
	Thousand separator	,
	Character for decimal point	.
	Number of headers that should be ignored when loading	1
Processing
	Update data	Only PSA and then in the InfoObject
Update parameters
	Update mode	Full update

InfoPackage 0DBDUNS_NUM2_ATTR, 0CUSTOMER and 0BPARTNER

Tab	Field	Value
Select data
		No entries required
External data
	Load external data from	Application server
	File name	A combination of the path of the working directory on the application server and the file name. For example D:\usr\sap\QB5\D19\work/0DB_IMPORTFILE_MU.csv Ask your system administrator which directories the files will be stored in (see also Storing D&B Data on an Application Server)
	Control file	No
	File type	CSV file
	Data separator	,
	Escape sign	"
External data parameters
	Thousand separator	,
	Character for decimal point	.
	Number of headers that should be ignored when loading	1
Processing
	Update data	Only PSA Update Subsequently in Data Targets Ignore Double Data Records
Update parameters
	Update mode	Full update

InfoPackage for InfoSource 0DB_MKT_1

Tab	Field	Value
Select data
		No entries required
External data
	Load external data from	Application server
	File name	A combination of the path of the working directory on the application server and the file name. For example D:\usr\sap\QB5\D19\work/0DB_IMPORTFILE_MU.csv Ask your system administrator which directories the files will be stored in (see also Storing D&B Data on an Application Server)
	Control file	No
	File type	CSV file
	Data separator	,
	Escape sign	"
External data parameters
	Thousand separator	,
	Character for decimal point	.
	Number of headers that should be ignored when loading	1
Processing
	Update data	PSA and then in the InfoObject
Data targets
		Select data targets Under the column Updating the data target, mark the field that refers to the D&B Marketing Cube
Update parameters
	Update mode	Full update
	Error Handling	Valid records update, reporting possible (request green)
	Error Handling – Termination by no. errors	9999999999

Creating a Task in Solution Manager

2009-01-07T11:59:00.000+05:30

Purpose

The Service Data Control Center administers operations and processes as so-called tasks. You can create the following task types:

Create session Add-on(s)

Delete old session and log data

Export session data to file

Maintenance Package

Refresh service definitions

Refresh sessions

Request session data

Send session data

Service Preparation Check

See also:

Task-specific Settings

Create and Assign Landscape Component Attributes in Solution Manager

2009-01-07T11:56:00.001+05:30

Use

You create attributes for servers, databases, systems, system components and main instances, to be able to assign additional properties to them, e.g. hardware attribute information or the person responsible for a system.

Prerequisites

You are in the Solution Manager System Landscape transaction (SMSY).

Procedure

Define Landscape Component Attributes

...

1. Choose Utilities ® Attribute Definitions.

2. Switch to change mode.

3. Choose New Entries.

4. Assign an attribute key in the customer namespace, i.e. beginning with Y or Z.

5. Enter the required data.

6. Specify the landscape component for which the attribute is to apply.

7. up possible entries help for the landscape component attribute values.

8. Save your entries.

The system displays the newly-defined attributes of the landscape components, in the Other Attributes tab.
Assign values to the attributes of a landscape component

...

1. Choose a landscape component.

2. Choose a value for the attribute from the possible entries help for the Attribute Value column in the Other Attributes tab.

3. Save the changes.
Result

You can display the assignment of attributes to landscape components, graphically, in the overview tree, under Overviews.

Set-up Possible Entries Help for Landscape Component Attributes in Solution Manager

2009-01-07T11:55:00.000+05:30

Use

You can use existing possible entries help in your system for user-defined attributes. You can, for example, set-up a list of your system administrators as possible entries help for the attribute „Person Responsible“, which you have defined.

You can set-up possible entries help for an attribute by specifying an existing values table or search help when you define the attribute. You can also define all the possible entries yourself.

When a user calls the possible entries help, the system first checks whether a value table and/or search help was specified when the attribute was defined. If so, the possible entries are the entries in the value table or search help.

If no value table or search help was specified, the system fills the possible entries help with the values specified individually in the attribute definition. If no values were specified, there is no possible entries help.
Prerequisites

You are in the Solution Manager System Landscape transaction (SMSY).

You have defined at least one landscape component attribute.
Procedure

...

1. Choose Utilities ® Attribute Definitions.

2. Switch to change mode.

3. Choose an attribute.

4. To use existing value tables and search help, you can either:

a. Enter a table name in the Value Table field,

b. Enter a field name from this table in the Values Field field.

or

...

a. Specify a search help in the Search Help Name field.

b. Specify the return parameter for this search help in the Search Help Field field.

If you only specify the search help name, the system shows the first parameter of the search help in the search help.

5. To define the possible entries help values for an attribute yourself:

a. Choose Possible Entries Help in the dialog structure.

b. Choose New Entries.

c. Enter the required data.

Note

The system also shows text which you enter in the Description column in the attribute possible entries help. This text is language-dependent.

6. Save your entries.

Copy Business Scenarios and Processes into Solutions

2009-01-07T11:50:00.003+05:30

You copy data from:

● a project

● the Business Process Repository (BPR)

Note

The Business Process Repository is a structured set of all preconfigured structure elements for business scenarios and processes, that you can reuse.

● an existing solution

into the Solution Directory.

Prerequisites

You have:

● created a solution.

● created a project to copy from a project in the Project Administration (transaction: SOLAR_PROJECT_ADMIN).

● created other solutions with business process scenarios, to copy business scenarios, business processes, and steps of another solution from the Solution Directory.

● assigned Solution Directory roles to users.

Procedure

...

1. Choose the transaction SOLUTION_MANAGER.

2. Choose the Solution Landscape tab, in the Operations Setup area.

3. Choose the Solution Landscape link.

4. Select your solution.

The solution header data contains:

○ the navigation role,

○ the structure level

○ thn change request status, if you are using Change Request Management

○ the Check Out status for checked out business processes or process steps in thesolution attributes of a maintenance project.

5. Select Business Scenarios, by double-click.

6. Choose the Structure tab.

Proceed as follows:

a. Specify whether you want to copy business processes from the Business Process Repository, from a Project, or another Solution Directory solution, in the possible entries help for the field Selection Help.

b. Proceed as follows, depending on your selection:

○ Business Process Repository (BPR)

...

i. Choose a business scenario in the possible entries help for the Scenario Name column.

ii. Confirm the following dialog box.

The system copies the business scenario and its business processes/process steps.

○ Project

...

i. Choose a business scenario in the possible entries help for the Scenario Name column.

ii. Choose Copy Options.

iii. Flag what you want to copy, and how you want to handle the documents, in the dialog box.

iv. Confirm.

The Logical Component Assignment dialog box may appear.

v. Check the assignment of the logical components to the systems.

vi. If it meets your requirements, confirm. Otherwise, assign the logical components first.

The system copies the business scenario and its business processes/steps.

○ Solution Directory solution

...

i. Choose a business scenario in the possible entries help for the Scenario Name column.

ii. Choose Copy Options.

iii. Flag what you want to copy, and how you want to handle the documents, in the dialog box.

iv. Confirm.

The Logical Component Assignment dialog box appears.

v. Check the assignment of the logical components to the systems.

vi. If it meets your requirements, confirm. Otherwise, assign the logical components first.

The system copies the business scenario and its business processes/steps.

b. Choose the business scenario status.

Note

To be able to monitor your business scenario and business processes in the Business Process Monitoring Sitzung, you must set the Status to Production.

c. Save your entries.

Note

The background information for Solution Directory Copy Scenarios tells you which other data is copied from the tabs.

Result

You have defined business scenarios. You can define other attributes for the business scenarios, in the other tabs.

Confirm Alerts and Create Service Desk Messages in Solution Manager

2009-01-07T11:49:00.000+05:30

Use

Confirm processed alerts or create Service Desk messages for specified alerts.
Prerequisite

You have resolved the alert in your satellite system.

You are in the check of the alerts which you want to confirm, in the Business Process MONITORING session.

You have asigned the role SAP_SOL_SERVTRANS_CREATE to the user, to create Service Desk messages.
Procedure
Confirm Alerts

...

· Individual alert

a. Set the Alert Handled flag in the Select column.

b. Choose Confirm.

c. Save.

· Selected by alert rating

§ ...

¡ all yellow alerts

i. Choose Confirm All Yellow.

ii. Save.

¡ all red alerts

§ ...

iii. Choose Confirm All Red.

iv. Save.

Note

§ You can sort the alerts by decreasing rating, by double-clicking on a field in the Rating column.

§ ...

Create Service Desk Message

...

1. Set the Alert flag in the Select column.

2. Choose the Create Notification pushbutton.

A dialog box appears.

3. Enter the required data, and the text of your Service Desk message.

4. Choose the Create Message pushbutton.

The system writes the Service Desk message number in the Support Message column.

Note

§ If the message is relevant for more than one alert, copy the message number into the relevant row of the alert.

§ To edit the message:

i. Double-click on the message number.

You go to the Service Desk screen.

ii. Choose Display/Change Trans.

iii. Enter a text.

iv. Save your data.

v. Go Back.

§ To refresh the status of the Service Desk message, choose Refresh Message Status.

5. Save.

Configure ECM Planning Columns In MSS

2009-01-07T11:47:00.000+05:30

I recently muck with a new piece of configuration involving MSS portal screen for ECM 5.0 which is pretty interesting. You could read more about it from SAP help document (HERE).
(Note: You need an OSS ID and LOGIN to access the document from SAP)

This walkthru is intended to show you at a high level what is involved. Let's start with the MSS portal screen of the ECM 5.0. As you can see (below) the MSS portal screen consist of several columns. These columns is a configuration item on the R/3 side.

You could add columns, remove columns, and/or even define your own custom columns. The define custom column piece will be mentioned here, however will not go into detail.

In SAP R/3 system, we will look at the IMG node

SPRO -> Integration With Other SAP Components -> Business Packages / Functional Packages -> Manager Self Service (mySAP ERP) -> Object and Data Provider

We will focus our configuration in this particular IMG area. We will not use all of the pieces in here.

Let's start with "Define Columns". In the "Define Columns" (table: V_TWPC_COL_ERP), you will be listing all the possible columns to-be used by the MSS screen. It is in this particular area where you will define any custom columns you wish to define as well and link them to custom function module that will lookup the information needed to pass back to the column.

As you can see from the image above, you have Column Name, Heading, Alignment, and FM for Columns Contents. In the "FM for Column Contents" is where you specify the custom function module for the custom columns. SAP delivers a lot of standard column for ECM 5.0, you should look through them first to see if it exist prior to creating your own.

In the "Define Column Group", you have two pieces to configure. The first one is "Define Column Groups" (table: V_TWPC_ARRAYTP) and the second one is "Assign Columns To A Column Group" (table: V_TWPC_ACOL_C or V_TWPC_ACOL). In the "Define Column Groups" you will define the name where you will group all of these columns in earlier step together. In our example, we will call it as ECMDEM.

In the second section, "Assign Columns To A Column Group" is where you link all of the columns you've identify to the column group you gave the name to earlier (ECMDEM).

As you can see from the image above, ECMDEM column group has 6 columns (in actual table there are more, but screenshot has been cropped for blog). The position column shown above determine the position of the column from left to right. The "Visible" column forced the column to be visible and can not be hide from the USER profile in MSS. The next column you don't see is called "DO NOT DISPLAY", this will totally hide the column. The last column you need to know is "Invisible". Which allow the USER Profile in MSS to hide the column at the user level.

The last piece of config on the R/3 side is "View Definition" (table V_TWPC_V). I am not sure where this is located on the IMG step, I've always go to the table directly. This table specify what column group to use on the MSS portal side. The view name is what is used on the portal iview configuration.

The "View" field will be used on the portal content adminstration side. This is what you tell your portal administrator to reference the iview from. See sample portal content administration screen below.

Now you've completed a simple walkthru on how to quickly modify columns for MSS ECM 5.0 screen. Chances are you might have access to do the R/3 configuration, however you would need to work with the portal team on modifying the portal iview to specify the proper view name.

A couple of things you need to know and remember. First is some of these fields are considered as dynamic driven fields. Such as Compa Ratio, New Base Salary, etc. In order for these fields to properly work, a setting need to occur. Second is there are limitation to how many columns you could display. While you have more shown on the R/3 table configuration, there is a max of how many could be show on the portal screen. The MSS User would need to de-select which of those they don't care to show and select those they care to show. Please refer to main SAP HELP document (link provided top of blog) for further information. Otherwise, you will be scratching your head for days trying to figure out why there are no data showing in these fields.

Lastly, from what I've gathered, ECM in later version after 5.0 have slight changes to how the portal screen look like. As the result, this method might not be correct for later version. Please refer to their documents for further details.

Enterprise Services Documentation Download

2009-01-07T11:46:00.000+05:30

On this page, you can find every document related to enterprise services. The documentation provided here explains everything from the transactions required to maintain enterprise services to the required information to consume enterprise services. In addition, the comprehensive documentation for each application type ranges from the business content and usage of enterprise services to detailed technical information.

The documents are grouped by the process components they belong to. That way, you should be able to find all semantically related documents in one place. All documents are in PDF format, so that you can save them and refer to them offline as often as you need.

Document Downloads

You can download the documentation packages from the links below:

ERP 2004 documentation (ZIP 4.6 MB)

ERP 2005 documentation (ZIP 10.6 MB)

SCM documentation (ZIP 4.4 MB)

SRM documentation (ZIP 2.4 MB)

CRM documentation (ZIP 2.2 MB)

Color of SAP GUI windows

2008-11-04T12:51:00.001+05:30

I’m posting a small hint which helps to recognize in which SAP system you are connected via SAP GUI. Sometimes when you are working with several sessions in different systems and you switching between windows very often it is problem to do not get confused.

To avoid such an mistakes you can change the color of SAP GUI windows for production client screen to red color for test systems to some different color and as well some other color for development systems. Procedure to do so is following:

Log in to some SAP system in which you want to change the color via SAP GUI -> select Customizing local layout (ALT+F12) -> Set color to system (select color) -> Save.

Setting BW Production Client

2008-11-04T12:50:00.000+05:30

To setup production client in a BW system in order to use BW func. (e.g. RSA1) take the following steps.

1. create new client via SCC4

2. copy client from 000

3. adapt Instance or Default profile parameter login/system_client so the the system opens with prod. client

4. Edit the cust. in table RSADMINA and change the value of field BWMANDT to your new client.

5. Test with running RSA1.

References: OSS Note 122679 and 116432

Check Business Processes In/Out in Solution Manager

2008-11-04T12:49:00.000+05:30

Purpose

As project team member, you want to:

● check business scenarios and/or processes which have already been used productively, out of the Solution Directory, to adjust or change them in a maintenance project.

● check business processes which have been changed or adjusted for production processing in a maintenance project (transaction SOLAR01), back into the Solution Directory.

As project leader or administrator, you want to:

● confirm business scenarios or processes to be checked out of the Solution Directory, and assign them to project team members for processing.

● confirm changed or adjusted business scenarios or processes from the maintenance project (transaction SOLAR01) which are to be checked in, for production processing.

Prerequisites

You have assigned a maintenance project with project team members, to your solution, and selected the check-out function in the solution settings.

Process Flow

Once the business scenarios or processes are checked out, they can no longer be changed in the Solution Directory.

...

1. Check-out of the Solution Directory into the maintenance project (transaction SOLAR01)

You are in the Solution Landscape Maintenance (Solution Directory):

a. as project team member:

i. Select the business scenario or process, in the Structure tab.

ii. Click on the button Request.

The system changes the status of the change request to Check-Out Requested.

You can reset the request with the pushbutton Cancel Request.

iii.

b. as project leader or administrator:

i. Choose Check Out to check the processes in the project out.

If you have assigned the roles for the project leader, the project team member selection appears.

ii. Assign project team members by selecting them.

iii. Confirm.

The system changes the status of the change request to Checked-Out.

The checked out business scenario or process appears in the maintenance project under the hierarchy node for your solution.

2. Check-in from the maintenance project (transaction SOLAR01) into the Solution Directory

a. as project team member:

You are in the Business Blueprint (transaction SOLAR01). The system displays the status Checked Out.

i. Select the business scenario or process, in the Structure tab.

ii. Click on the button Ready.

The system changes the status to Check-In Requested.

To be able to release the processes, you must set the status of all associated documents, such as documentation, test cases, etc. to Released.

b. as project leader or administrator:

You are in the Solution Directory for your solution. The system shows the change request status as Check-In Requested.

i. Choose Check-In.

ii. Save.

Result

You can trace changes to your business processes, in the change history.

Changing Logo In Netweaver Screen Shots free downloads

2008-11-04T12:45:00.004+05:30

JAVA Overview
WEB AS Positioning
J2SE To J2EE
SAP WEB AS JAVA Security
SAP Netweaver Developer Studio
WEB Infrastructure
Java Development Infrastructure
Persistence Components
JDBC Java Database Connectivity
SQLJ Embeeded SQL In Java
How To Change The JDK To J2EE
J2EE Administration Manual
JAVA Engine Administration Tools
JAVA Startup Control Frame Work
JAVA_Docs
J310 JAVA Web Dynpro
Master Guide MYSAP SR1
Master Guide SAP Netweaver
XI System Content Copy
XI In High Availability Environments
XI Tuning Guide
XI Sample Chapter
Creating I views Screen Shots
Changing Logo In Netweaver Screen Shots
Creating Pages Work Sets Roles Screen Shots

Changes not visible after Transport of BI 7.0 Web Template

2008-11-04T12:45:00.001+05:30

You transport a BI 7.0 Web Template but after the import the changes is not visible in the report.Do get around this problem, clear the ICM cache in your BI backend system via transaction SMICM.See the screenshot below:

Password Rules

2008-11-04T12:44:00.001+05:30

A lot of new features have been introduced with NetWeaver 2004s and its ABAP SAP Application Server 7.0. Finally password is case sensitive and may have from 8 to 40 characters in length. Huge bunch of new system profile parameter have been acquaint as well:

For details see following SAP notes:
862989 1023437 992855 968558 943505

Change/Adjust Business Scenarios and Processes in Solution Manager

2008-11-04T12:42:00.000+05:30

Purpose

You can change and adjust production business scenarios and processes, using the 4 eyes principle.

Prerequisites

You have:

● Defined solutions.

● Defined business scenarios and processes

● assigned Roles for the Solution Directory:

○ Project team member: SAP_SOLMAN_DIRECTORY_EDIT

○ Project leader or administrator: SAP_SOLMAN_DIRECTORY_ADMIN

● assigned roles for Project administration

Process Flow

...

1. The project team member responsible for modelling the business scenarios and processes wants to change one or more production business scenario or process. The processes must be checked out of the Solution Directory into a maintenance project for processing. Project leader or administrator:

a. assigns an existing maintenance project to the solution in the solution settings or defines and assigns a new maintenance project with Create and Assign New Project in the Project Administration (transaction SOLAR_PROJECT_ADMIN).

b. activates the history and check out/in functions in the solution settings.

c. assigns project team members to make changes in the maintenance project later.

2. The business scenarios or processes of the solution are selected for check-out into the maintenance project, by the project team member responsible.

3. The administrator or project leader releases check-out of the business processes into the maintenance project for specified project team members.

4. The project team members edit the business scenarios or processes assigned to them, in the maintenance project.

5. When the project team members have edited the business scenarios, they check the business scenarios or processes back into the processes.

6. The administrator or project leader confirms the procedure so that the changed business scenarios and processes are productive.

Change Request Management Roles in Solution Manager

2008-11-04T12:41:00.000+05:30

Before users can start working with Change Request Management, the system administrator (or equivalent user) has to create user roles that contain the relevant authorizations, and then assign these roles to the corresponding users. The roles have to be created (by using transaction SU01) for users in the following systems:

· SAP Solution Manager system (Change Request Management runs in this system)

· Satellite systems that are managed by Change Request Management

Roles in the SAP Solution Manager System

2008-11-04T12:40:00.002+05:30

The following roles are provided by SAP and have to be assigned to the corresponding users in the SAP Solution Manager system:

· SAP_CM_CHANGE_MANAGER

This role enables the user to approve and reject change requests.

· SAP_CM_DEVELOPER_COMP

This composite role enables the user to make corrections in the development and maintenance systems, and to release the necessary transport requests. It comprises the following single roles:

¡ SAP_SOCM_DEVELOPER

¡ SAP_CM_SMAN_DEVELOPER

· SAP_CM_TESTER_COMP

This composite role enables the user to test and validate corrections in the test system. It comprises the following single roles:

¡ SAP_SOCM_TESTER

¡ SAP_CM_SMAN_TESTER

· SAP_CM_OPERATOR_COMP

This composite role enables the user to import corrections into systems, and to perform operational tasks in task lists. It comprises the following single roles:

¡ SAP_SOCM_IT_OPERATOR

¡ SAP_CM_SMAN_OPERATOR

· SAP_CM_PRODUCTIONMANAGER_COMP

This composite role enables the user to approve and perform the import of corrections into the production system. In certain critical situations (such as during a payroll run), the production manager can decide not to import corrections into the production system; otherwise, the system could be rendered inconsistent. It comprises the following single roles:

¡ SAP_SOCM_PRODUCTION_MANAGER

¡ SAP_CM_SMAN_PRODUCTIONMANAGER

· SAP_CM_REQUESTER

This role enables the user to create change requests.

· SAP_CM_ADMINISTRATOR_COMP

This composite role enables the user to customize and check all Change Request Management functions in the Solution Manager system, as well as perform administrative and technical tasks for task lists and cProjects. It comprises the following single roles:

¡ SAP_SOCM_ADMINISTRATOR

¡ SAP_CM_SMAN_ADMINISTRATOR

¡ SAP_CPR_PROJECT_ADMINISTRATOR

¡ SAP_CPR_USER

Roles in the Satellite Systems in Solution Manager

2008-11-04T12:40:00.001+05:30

From a transport point of view, the remote architecture of Change Request Management consists of one central SAP Solution Manager system, which is where Change Request Management runs and where all transports are controlled, and satellite systems where transport requests are created, released, and imported. In all these satellite systems, the local users need to have special authorizations within the Change and Transport System (CTS) according to their particular tasks.

· Real Users

For users in the satellite systems that have the system role types Development, Test or even Production, assign the following roles:

¡ SAP_CHANGEMAN_DEVELOPER

Contains the authorization profile S_TMW_DEVELO. This profile contains CTS authorizations for developers: No authorization to create transport requests, and no authorization to release transport requests but to create and release tasks.

¡ SAP_CHANGEMAN_OPERATOR

Contains the authorization profile S_TMW_OPERA. This profile contains CTS authorizations for operators: All transport authorizations; no configuration authorizations

¡ SAP_CHANGEMAN_ADMIN

Contains the authorization profile S_TMW_ADMIN. This profile contains CTS authorizations for administrators: All authorizations in the CTS (including configuration)

Note that the roles SAP_CHANGEMAN_PROJECTASSISTANT and SAP_CHANGEMAN_PROJECTLEAD are obsolete; do not assign them to users.

For SAP systems based on SAP Web Application Server 6.10 and lower, the profiles listed above are available, but not the roles. Therefore, you have to explicitly assign the authorization profiles to the relevant users.

· Trusted System Users

For all client system actions in Change Request Management, users are required to log on by using trusted systems. For this purpose, you must also assign trusted system authorizations to the relevant users. In particular, you have to assign the authorization object S_RFCACL. For more information, see SAP Solution Manager: Configuration Guide ® Technical Requirements ® Automatic Generation of Trusted System RFC Destinations.

· Background User

This user is required for communication between the SAP Solution Manager system landscape (transaction SMSY) and all systems that have the role type source system. For more information, see Generate/Change RFC Connections. In these logical systems, a communication (background) user is generated for executing tasks in the background (user SOLTMW). This background user automatically has the following profiles from the CTS area:

¡ S_TMW_CREATE for creating and releasing transport requests in development systems as well as for setting the project status switch for creating transport requests

¡ S_TMW_IMPORT for importing transport requests into test systems (empty)

The most important task of the background user is to create and release transport requests and tasks remotely from Change Request Management. Requests that are created in this way are known to Change Request Management, which means that Change Request Management can control the distribution of these requests within the landscape.

Requests that are created, released, or imported locally cannot be identified by Change Request Management in conjunction with a change request and are therefore not part of the Change Request Management transport control and distribution process. For this reason, we recommend that no users (apart from administrators) have authorization to create transport requests or tasks in Change Request Management-controlled clients.

· Import Authorization Checks

Change Request Management uses the import functions of the Transport Management System (TMS). The TMS remote infrastructure is based on RFC connections that point solely to the 000 client of a target system. For this reason, you must make sure that Operators and Administrators have users both in the client into which changes are imported, and in the 000 client of these systems.

· Automatic Imports

In test systems, it is sometimes necessary that imports are performed automatically. If you want developers within the Change Request Management scenario to start imports into a test system automatically, you must add the profile S_TMW_IMPORT to the user TMSADM in client 000 of the test system. Since S_TMW_IMPORT is delivered empty, you have to assign it the authorizations S_CTS_IMPALL and S_CTS_IMPSGL, which are also contained in the authorization object S_CTS_ADMI.

It is now possible to start an import into this system from every satellite system within your domain by using the CPIC user TMSADM; therefore, do not use this method in production systems or in any other security-critical systems.

The system where you want to start the import automatically must share the same transport directory as its preceding system. If the transport directories were different, the user who starts the import would need “addtobuffer” authorizations for the buffer adjustment, which would present a security risk not only for the system concerned, but also for the whole landscape (including the production system).

Authorizations in Solution Manager

2008-11-04T12:39:00.000+05:30

The following figures show which authorizations are contained in the Change Request Management roles.

· Roles in SAP Solution Manager system

The following table shows which task list authorizations are assigned to the roles in SAP Solution Manager system:

	Developer	Tester	Prod. Manager	Operator	Administrator
Display	X	X	X	X	X
Create	X	---	---	---	X
Change	---	---	---	---	X
Delete	---	---	---	---	X
Run	X	X	X	X	X
Change status	X	X	X	X	X

· Roles in the satellite systems

The following table shows which transport request/task authorizations are assigned to the satellite system roles:

* See Roles in the Satellite Systems (Automatic Imports section)

Maintenance Optimizer Roles in Solution Manager

2008-11-04T12:38:00.002+05:30

Technical name: SAP_MAINT_OPT_ADMIN

Technical name: SAP_MAINT_OPT_DISP

Tasks

The individual roles allow users to either administer or display product maintenance procedures in the Maintenance Optimizer.

Activities in

This individual role allows users to create and change product maintenance procedures in the Maintenance Optimizer

Activities in

This individual role allows users to display product maintenance procedures in the Maintenance Optimizer

mySAP Supply Chain Management

2008-11-04T12:38:00.001+05:30

Certification Requirements Solution Consultant mySAP Supply Chain Management
- Order Fulfillment ( SD )2002
From:SAP DOC

Software components: SAP R/3 4.6C Certification duration: 3 hours Number of certification questions: 80 multiple choice questions Required certifications for participation in this certification test:
Please note that you are not allowed to use any reference materials during the certification test (no access to online documentation or to any SAP system).
The certification test Solution Consultant mySAP Supply Chain Management - Order Fulfillmen 2002 verifies the knowledge in the area of the mySAP Supply Chain Management solution for the consultant profile Order Fulfilment. This certificate proves that the candidate has a basic understanding within this consultant profile, and can implement this knowledge practically in projects.
The certification test consists of questions from the areas specified below:

Topic Areas

1. Special Business Transactions (+)

Availability Checking Consignments Backorder Processing

2. Integration (+)

Organizational Structures SD/FI interface SD/MM interface

3. Reporting (+)

Overview

4. Billing (++)

Credit/Debit Memos Billing Plans Billing due List Billing Document types Account Determination

5. Pricing (++)

Rebate Processing Condition Technique General Pricing Processing and Configuration Condition Records Pricing Procedure

6. Master Data (++)

Customer Master Material Master Customer Material Information Record Customer and Product Hierarchies

7. Shipping (++)

Basic Delivery Processing Picking, Packing and Goods Issue Scheduling Routes and Route Determination

8. Sales Processing (+++)

Basic Sales Document Processing and Configuration Contracts Copying Control Partner and Output Control Item Categories and Schedule Line categories

9. ASAP (+)

Accelerated SAP-Overview

10. Experiences from Implementations (Case Study or Project)* (+)

Setting Up Company Structures (organizational units in mySAP.com) Integration and Dependencies
* = In topic area 10, you will be tested on cross-topic implementation and integration issues. Implementation and integration knowledge that refers to a specific area (such as Picking, Packing and Goods Issue) will be tested in the relevant topic (such as Shipping).
Weighting Key in the Test:
+ = 1 - 10% ++ = 11 - 20% +++ = over 20%

CCMS and SAP Solution Manager

2008-11-04T12:37:00.000+05:30

System and Business Process Monitoring in the SAP Solution Manager

The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.

You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system.

CCMS and system monitoring in the SAP Solution Manager

The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.

The graphical display in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.

The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwriting the values in the local CCMS.

CCMS and business process/interface monitoring

You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, „BPM“ of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.

The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:

● The system collects performance (dialog transactions), posting cancellations (V1 and V2) and „Other CCMS“ and interface data, in the local CCMS of the satellite systems.

● The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.

The SAP Solution Manager system copies the data from the local CCMS.

The graphical display in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.

The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.

BW upgrade to BI 7.0 - New Web Reporting

2008-11-04T12:36:00.000+05:30

You've probably heard about all the new functionality that comes BI 7.o , especially around web reporting. You can actually upgrade to BI 7.0 "as is" without having to do all the BI-JAVA stuff but then you won't be able to use the new web reporting functionalities that come with BI 7.0 like :

New BEx Web Application Designer (Unicode, Command Wizard, ...)

Exporting to PDF and Printing

Integrated Planning

Drag&Drop (Analysis Web Item)

Web Items (Container Layout, Menu Bar, Tab Pages, Button Group, ...)

Formatted Reporting with BEx Report Designer

Document Integration with storage in Knowledge Management

To use the new functionalities you need a BI-JAVA stack, in essence a Netweaver Portal with BI business packages installed on it. You can either utilize your existing Portal or install a dedicated Portal for BI Web reporting.

SAP has a comprehensive note regarding setting this, see Note 917950 - SAP NetWeaver 2004s: Setting Up BEx Web. Also check the handy attachments to the note .

One thing I can add to this : Please try and run this on a 64bit Portal as the BI reports use a lot of memory on the Portal's J2EE. The reason for this is that the query data is transferred to J2EE as a whole during runtime, and we how big BI queries can be! (Note 996600 - 32 Bit platforms not recommended for productive NW2004s apps, Note 1044330 - Java parameterization for BI systems)

BW Go live Optimization report

2008-11-04T12:33:00.002+05:30

SAP AG always recommend to performing the SAP Going-Live Checks for your production system. Depending on the phase of your project, these checks, offered by SAP, analyze the hardware sizing, check the configuration of the server and components, find performance bottlenecks, and verify the capacity of CPU and memory. The results of the checks are issued in a report (approximately 50 pages) provided by SAP.

EP Going-Live Check Analysis Session (GA) - The GA session checks whether the available hardware is sufficient for the planned workload. Recommendations for the component settings are made. EP Going-Live Check Optimization Session (GO) - The GO session simulates workload on the system and identifies performance bottlenecks and potential risks.
EP Going-Live Check Verification Session (GV) - The GV session checks the behavior of the production system after going live and provides appropriate recommendations.What does such a GO session report contains in case of BW system is depicted below. The purpose of the session is to analyze most important InfoCubes and Queries, and to assess any potential problems in system. SAP takes few InfoCubes and Queries and makes this session based on them. Report may have following structure:BI Overview checks

BI Administration and design
Data distribution

Analysis of InfoProviders

3. Analysis of aggregates

4. Recommendations for BI

5. BI Statistics

BI Reporting and planning

1. BI Runtime Statistics

2. Analysis of Query Definition

3. Analysis of OLAP Cache

4. Frontend Servers

BI warehouse management

1. Upload Statistics

2. Process Chains - Runtime Overview

3. Source System Settings

BI application checks

Optimization of InfoProvider

1. InfoCube 1

2. InfoCube N

Analysis of reporting and planning performance

1. Report 1

2. Report N

Upload checks for

Configuration for BI uploads

1. Important SAP Notes for data upload

Process chains

1. Chain: 1

2. Chain: N

For more information check out http://service.sap.com/safeguarding.

FAQ in SAP Business Information Warehouse

2008-11-04T12:32:00.000+05:30

1. What is table partition?
2. What are the options available in transfer rule and when ABAP code is recquired during the transfer rule what important variables you can use?
3. How would you optimize the dimensions?
4. What are the conversion routines for units and currencies in the update rule?
5. Can you make an infoobject as info provider and why?
6. What are the steps to unload non cumulative cubes?
7. Give step to step approach to archiving cubex.
8. What are the load process and post processing.
9. What are the data target administration task
10. What are the parallel process that could have locking problems
11. How would you convert a info package group into a process chain?
12. How do you transoform Open Hub Data?
13. What are the data loading tuning one can do?
14. What is ODS?
15. What is the use of BW Statistics?
16. What are the options when definging aggregates?
17. How will you debug errors with SAP GUI (like Active X error etc)
18. When you write user exit for variables what does I_Step do?
19. How do you replace a query result from a master query to a child query?
20. How do you define exception reporting in the background?
21. What kind of tools are available to monitor the overall Query Performance?
22. What can I do if the database proportion is high for all queries?
23. How to call a BW Query from an ABAP program?
24. What are the extractor types?
25. What are the steps to extract data from R/3?
26. What are the steps to configure third party (BAPI) tools?
27. What are the delta options available when you load from flat file?
28. What are the table filled when you select ABAP?
29. What are the steps to create classes in SAP-BW
30. How do you convert from LIS to LO extraction?
31. How do you keep your self-updated on major SAP Develppments, Give an analytical example.

BW

2008-11-04T12:31:00.000+05:30

Guys, just want to give you some idea about the examination:

It divides into 6 sections:

1. Data Modelling, (8 questions)

2. Warehouse Management,

3. Reporting,

4. Authorization, (4 questions)

5. Implementation Project, (6 questions)

6. Extraction

The weight of each section is different. The Data Modelling, Authorization, and Project Implementation are not that heavy. It would be better spending more time on the rest.

You need to understand at least the concepts for the following:

Hierarchy, line item, aggregation, display attribute, navigation attribute, Bex Map (TBW20 - Chapter 16), exception aggregation, direct update...

Good Luck.

FREE DOWNLOAD Business Task Management in Netweaver

2008-09-25T09:51:00.000+05:30

http://rapidshare.com/files/60028653/Business_Task_Management_in_SAP_NetWeaver.rar

Business Process Monitoring Session in Solution Manager

2008-09-25T09:46:00.002+05:30

Use

You want to:

· activate the Business Process SETUP session settings for a business process.

Prerequisites

You have set up business process monitoring in the Business Process SETUP Session.

Activities

...

1. Start the transaction SOLUTION_MANAGER.

2. Choose Solution Monitoring ® Business Process Monitoring, in the Operations area.

3. Choose the Business Process Monitoring link to the desired business process.

You go to Change Mode: Business Process Monitoring.

4. Perform the following checks in change mode:Basic Settings

Activation

Business Process

§ Step

The system generates the check with its process step subchecks when you have activated the monitoring for the business process. Check the activation log.

Session Change Modes Netweaver

2008-09-25T09:45:00.002+05:30

Definition

In the change mode:

· of the business process monitoring maintenance session, you specify the business processes and business process steps which you have created.

· of the business process monitoring Setup session, you specify the business processes and their alerts which you want to monitor.

· of the business process monitoring Monitoring session, you monitor the business processes and process the alert messages.

Structure

The screen is divided into three areas:

Left-hand column

Displays all the checks which you must perform to set-up the business process monitoring of your solution.

Business Process Maintenance session

· Business Processes - Overview

· Interface Overview

· Contact Data

Business Process SETUP session

· Solution Support Organization

· Business Processes

¡ BPMon:

...

§ Notifications

§ Steps (according to process steps set up)

Monitoring Types (according to the number of monitoring types selected)

Monitoring Transactions

Monitoring Activities

Notifications

§ Generate Monitoring Customizing

¡ Interface Monitoring

§ Analyses and Monitoring tools

§ Monitoring activities

§ Notifications

...

· Data Collector Frequencies

· Local RFC Destination for Data Collection

· Monitoring Check Lists

· Cover Page

Business Processes MONITORING session

· Basic Settings

· Activation

· Business process

Any subitems of checks only appear when you have performed and saved the check. The subitems are partially preconfigured if the system has the necessary information.

Top right screen area:

Explains the use, background and procedure of the check.

To hide the documentation, move the frame.

Bottom right screen area:

The tables to be maintained by the check.

You can call the online documentation in the logon language, for the checks, with HELP (see SAP note: 789703).

Business Framework Architecture-BFA Netweaver

2008-09-25T09:45:00.001+05:30

Business Framework Architecture (BFA) provides a structure for SAP system to connect to their partners and customers thru a specific standard.

The basic componenet of Business Framework are:

Business components (Processes)
Business objects (Entity/Data)
BAPI (Business Application Programming Interfaces)
BAPIs are interfaces for business objects. Together with the business objects, BAPIs define and document the business interface standard.
Application Link Enabling (ALE)
This involve distributing business objects across SAP/Non SAP system

Communication Services
These are the communication technologies, for example, Distributed Component Object Model (DCOM) and Remote Function Call (RFC), which the Business Framework uses to access BAPIs.

BRTOOLS Netweaver

2008-09-25T09:44:00.001+05:30

Following tools are availabe for managing oracle database:

BRBACKUP
BRARCHIVE
BRRESTORE
BBRECOVER

BRBACKUP and BRARCHIVE is a command line program. So, it can be easily schedule on your unix command line. The backup are based on the following programs:

cpio, dd in a UNIX enviroment
MKS-cpio, MKS-dd in Microsoft enviroment
External backup program that can be accessed using BACKINT interface program (Networker, TSM etc.)
Oracle Recovery Manager (RMAN) on both UNIX & Microsoft platform

All action are logged in the filesystem (sapbackup & saparch folder) and some related tables. Backup logs and profiles are always included in backups performed by BRBACKUP & BRARCHIVE.

BRBACKUP and BRARCHIVE allow extensive volume management. To use the functions provided, the volumes need to be initialized with BRBACKUP and BRARCHIVE to ensure that they include an SAP-specific label. Volumes that have not been released for use cannot be overwritten, if the retention period has not expired.

FYI, brtools is not only can be use in SAP. You can also this tools to manage any other oracle/DB that are not connected to SAP.

BRBACKUP Netweaver

2008-09-25T09:43:00.002+05:30

The BRBACKUP tool allows an online or offline backup of the control file, of data files in individual orall tablespaces and, if necessary, of the online redo log files, as shown in the graphic. BRBACKUP also saves the profiles and logs relevant for the backup.

In addition to the actual backup, BRBACKUP also:

changes the state of the database automatically, depending on the type of backup wanted (that is,online or offline)
Checks the status of files
Optimizes the data distribution on the backup media. The algorithm for distribution is specially adapted to the requirements of a database backup, that is, to backing up a small number of large files. The distribution of data depends on whether you carry out a serial or parallel backup
Performs software compression, if the option is selected
Saves to hardware compressing tape stations, taking previously determined compression rates into account

The BRCONNECT program makes sure that the database status required for the online or offline backup remains unchanged during the backup. The saving rates largely depend on the number of tape stations in use and the CPU load (particularly when software compression is used).

You can also back up any files or directories you want. However, the backup of a directory is restricted to the files it contains. This enables backups of all SAP objects that do not belong to the database (for example, programs, SAP start profiles, selected logs, and so on).

You can also perform database backups on several disks or remotely connected tape stations.
BRBACKUP also supports Oracle databases on raw devices and Oracle Real Application Cluster
(RAC) configurations.

BRARCHIVE Netweaver

2008-09-25T09:43:00.001+05:30

You can use the BRARCHIVE tool to archive the offline redo log files, that is, the online redo log files saved to the archiving directory by Oracle. For more information, see the graphic. BRARCHIVE also saves all the logs and profiles of the archiving process.

Reasons for archiving offline redo log files include the following:
In the event of a failure, a consistent database status can only be recovered, if all relevant redo log files are available.

The database system of a production SAP System has to be operated in the ARCHIVELOG mode to prevent overwriting of unsaved online redo log files. To protect the archive directory against overflowing, it has to be emptied regularly.

An online backup of data files is useless if the related redo log files are missing. Therefore, you must archive the offline redo log files generated during the online backup immediately after running BRBACKUP.

For security reasons, BRARCHIVE offers duplicate archiving of offline redo log files (redundant serial or parallel archiving is possible). On the basis of the logs, BRARCHIVE can make sure that redo log files are not deleted before they have been archived and that the same files are archived once or twice.

BRARCHIVE allows the database administrator to continually archive offline redo log files. This means that the archiving directory, where Oracle places the offline redo log files, can be kept free by continually archiving and then deleting saved redo log files.

You can save offline redo log files on local or remote tape or on local or remote disk. Backup on disk is used particularly in the standby database environment.

BI Workload Stats in Netweaver 7.0 Netweaver

2008-09-25T09:42:00.000+05:30

Recently installed or upgraded to BI 7.0? You will find that when using transaction ST03N to view BI Workload statistics (for OLAP,data load stats etc) that it's empty.
This is because ST03N does not read directly from the RSDDSTAT tables anymore.
Using the delivered technical content you need to load the data from RSDDSTAT into technical infoproviders which is then read by ST03N.

See SAP Note 964418 and 934848 for more information on this new feature.

Automatically Generated Information in BW Netweaver

2008-09-25T09:41:00.002+05:30

Definition

Automatically generated information in the SAP Business Information Warehouse (SAP BW) consists of technical information that is generated by the system as well as manually created documentation. Both are displayed together in the browser. This concerns information about BW objects, such as InfoSources, InfoCubes, or queries. Within this information, you can navigate to help or further documentation by using additional objects, such as necessary objects or those that have been used.

Prerequisites

You need access to an SAP BW system in order to be able to display automatically generated information. Otherwise, you can also export HTML pages: Metadata Exchange in XML Format by CWM.

Procedure

You can call up the automatically generated information from the following places:

Administrator Workbench (AWB)
Administration
Business Explorer Analyzer (BEx) / Query Designer

Different procedures are required at the individual places for displaying automatically generated information:

Administrator Workbench (AWB)

AWB ® Modeling

Select the respective object and choose F1.

AWB ® Modeling ® Object Maintenance ® MultiProvider

Select the respective MultiProvider.

Choose Documentation

AWB ® Modeling ® Object Maintenance ® InfoSet, InfoCube, or InfoObjects

Select the respective object.

Choose Documents .

Choose Display Documentation

AWB ® Modeling ® Object Maintenance ® ODS Object

Select the respective ODS object.

Choose Display.

Choose Documents

AWB ® Transport Connection

Select the respective object and choose F1.

AWB ® Documents

Select Metadata.

Select the Object Type you want.

Select the Object Name you want.

Double-click on Show Me the Documents from...

Choose Display Documentation

AWB ® Metadata Repository

Select the respective object type first, such as a query.

Double-click on the respective object.

The information is then displayed in the browser.

If you display automatically generated information for an InfoSource, you can use Communication Structure to see the InfoSource fields.

Administration

Administration ® Process Chains

Select the respective process chain by double-clicking on it.

Choose Documents .

Choose Display Documentation

Business Explorer or Query Designer

Go to the change mode for the query.

Choose Change Query (Global Definition).

Choose Query Properties.

Choose Documents.

Choose Display Documentation

Exchanging Metadata in XMI Format Netweaver

2008-09-25T09:41:00.001+05:30

Use

You can use the XMI format in the Administrator Workbench functional area Transport Connection to exchange metadata (BW objects) between different systems. A model derived along the lines of the CWM (Common Warehouse Metamodel) is used here.

You can find additional information about the CWM standard on the OMG (Object Management Group) homepage: www.omg.org.

You can find additional information about the Administrator Workbench function area Transport Connection under Transport Systems.

Integration

You can export or import the XML files (Download or Upload to/from PC) in the Administrator Workbench.

An HTTP service is also available under SAP/BW/XML/CWM. You can use this HTTP service to request this metadata in the way in which you are familiar from using the Web server. In order to request metadata for an object, use the following URL:

http://:Port/SAP/BW/XML/CWM?/CLASSID=&ID=&DETAIL=X&OBJECTVERSION=A

You need to replace the following terms:

Term	Information
:	Specify the name of the server and the port for the required BW system. http://LS0027.WDF.SAP-AG.DE:1080/ SAP/BW/XML/CWM?...
	Specify the name of the class for the required BW object. As an example for the class InfoCube: CLASSID=COM.SAP.BW.CWM.OLAP.INFOCUBE You get the BW model in XML format from the following URL: http://:Port/SAP/BW/XML/CWM? CLASSID=METAMODEL
	Specify the technical name for the required BW object. You get an Overview of All Objects from: http://:Port/SAP/BW/XML/CWM? CLASSID=LIST&ID=&DETAIL=&OBJECTVERSION=A You get an Overview of All Business Content Objects by using the parameter &OBJECTVERSION=D, namely http://:Port/SAP/BW/XML/CWM? CLASSID=LIST&ID=&DETAIL=&OBJECTVERSION=A You get an Overview of All Objects of a Specific Type by using the ID specification in the URL. For example, you specify the following for InfoCubes: http://:Port/SAP/BW/XML/CWM? CLASSID=LIST&ID=COM.SAP.BW.CWM.OLAP.INFOCUBE &DETAIL=&OBJECTVERSION=A

Functions

The exchange of metadata involves:

Importing from another system

Exporting into another system

Only objects for which there are BAPIs (Business Application Programming Interfaces) are supported with details. You can only import these objects after you have changed them. You are still not able to import non-BW objects.

You can export the current BW model according to the XMI (XML Metadata Interchange) standard. This is made possible with the SAP report RSO_REPOSITORY_EXCHANGE_XML.

You can find additional information about the XMI standard on the OMG homepage: www.omg.org.

The following graphic illustrates the functions EXPORT and IMPORT.

Searching for Metadata Netweaver

2008-09-25T09:40:00.000+05:30

Prerequisites

For you to be able to fully search in metadata, the search engine must be fully installed.

If the search engine has not been fully installed, the system generates an appropriate after entering a search term. You can either complete the installation of the search engine, or you can search for metadata using F4 help. However, this search process is limited to finding technical names, short and long texts for the objects.

Procedure

...

In the navigation area of the metadata repository, choose Search in Metadata Repository.

If you are using the search function in a BW system with release 2.0/2.1C for the first time, you have to create the search index first. To do so, choose Extras -> Metadata Search -> Create Search Index. The search index is created in the background.

Enter the term in the Search term entry field.

You can search by description (title) or by the object’s technical name. The system makes a full text search of all the objects in the search index.

If you want to restrict the search, you can choose one of the following object types:

InfoObjects

InfoCubes

ODS Object

Queries

Choose Start Search.

Result

You receive a list sorted according to object type /symbol, number, and technical name for activated objects and Business Content objects.

Defining Source System in BI 7.0 Netweaver

2008-09-25T09:39:00.002+05:30

BI 7.0 Source System Definition for Source System with Basis Release lower than 640 is quite different.

As of release 640, you can use upper and lower case characters for user passwords. This is only uppercase characters for previous releases. Remember that your passwords are automatically converted to uppercase in previous releases.

As BI System has Basis 700 in bottom, upper and lower case passwords are important.

So, for defining source system is almost same as ordinary BW source System definitions.

One more important thing is that you have to take into account the EDI Ports. This may cancel your system definition if the settings are not correct. This settings must be controlled on both BI and Source System.

Here are the steps to configure Source System with Basis Relase lower than 640 in BI 70:

1. Take a look at table EDIPORT of your BW system and note the next free number for the field "Port". This is the adjacent number of the highest entry like 'A0000000123' for example. In this case e.g. take '124'.

2. Choose transaction "snum" and object "ediport".

Select "number ranges" from the menu "Goto" and here the button "status".

Change the CURRENT NUMBER of the ranges to the next free number you noted from table EDIPORT.

If the number range of your BW system is correct please check the same in your OLTP system.

3. Call TCODE RSA1 on BI System in BI Client.

4. Select Source Systems on Left Menu

5. Left Click SAP System and Choose Create

6. Important think is, as source system has Basis Release Lower than 640, You have to give All Passwords (For BI ALEREMOTE User and for Source System ALEREMOTE User) in UPPERCASE.

My Favourite is giving RFCCPIC for ALEREMOTE Passwords.

7. It Must Be OK.

Setting BW Production Client Netweaver

2008-09-25T09:39:00.001+05:30

To setup production client in a BW system in order to use BW func. (e.g. RSA1) take the following steps.

1. create new client via SCC4

2. copy client from 000

3. adapt Instance or Default profile parameter login/system_client so the the system opens with prod. client

4. Edit the cust. in table RSADMINA and change the value of field BWMANDT to your new client.

5. Test with running RSA1.

References: OSS Note 122679 and 116432

BSP call : type of termination: RABAX_STATE

2008-09-25T09:37:00.001+05:30

If you are getting the following error when calling Web Interface Applications created by BPS_WB TCODE in SEM System;

500 SAP Internal Server Error
Error message: An exception that could not be caught occurred.
( type of termination: RABAX_STATE )

Then you've some configuration problem which is easy to solve.

When you checked the ST22 ABAP Dump logs you sould find the following Dump:

Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_BSP_HOST_NOT_QUALIFIED
Occurred on 09.12.2004 at 16:27:41

An exception that could not be caught occurred.

What happened?

The exception 'CX_BSP_HOST_NOT_QUALIFIED' was raised but was not caught at any stage in the call hierarchy.

Since exceptions represent error situations, and since the system could
not react adequately to this error, the current program, 'CL_BSP_RUNTIME================CP ', had to be terminated.

In this case you have to check your ICM Server setting icm/host_name_full. This parameter must show the fully qualified domain name of your machine.

like: .

You can change this parameter by adding it into Instance Profile of your SAP System (__) via RZ10 TCODE.

If your system is not connected via Domain or not within a domain, you must do the following TRICK.

1. Open your servers hosts file (UNIX: /etc/hosts, Windows:C:>WINNTsystem32driversetchosts).

2. Add the following line.

e.g.

10.0.0.1 saptest1

10.0.0.1 saptest1.domain

3. Change the icm/host_name_full profile value within Instance profile

4. Restart your SAP R/3 server (only R3 with stopsap__ r3)

5. Try your BSP Application.

6. It works ha?

The following Article published in SDN by Brian McKellar on Sep. 25, 2003 04:11 PM

In synchronized translation: “BSP Exception: The URL does not contain a full domain specification (ls0028 instead of ls0028.wdf.sap-ag.de).”

Lovingly, this is referred to as the “Fully Qualified Domain Name” problem. FQDN requires that the hostname must be specified with a complete domain name when addressing the server.

For example:

Usually only the host name in the URL is required for the browser to determine the IP address to use. In the above example, ls0028 can easily be resolved to the correct IP address without the requirement of a domain name. See:

In the first instance, the hostname part of the URL is only for the browser to find a route to the Web server. Once on the Web server, the rest of the path starting at / is used to resolve the specific page to view.

So why would BSP require an FQDN and other services would not?

Motivation for FQDN

The first interesting aspect to understand is that the host name in the URL is effectively a routing string, which tells the browser how to reach the target. A typical situation is that a host might have an intranet name (example ls0028.wdf.sap-ag.de) that is totally different from the Internet name (example bsp.sap.corp - name changed to protect the innocent:). The name entered in the URL is important for the SAP Web AS, as this tells us the route that was followed to the server.

This host name is always placed into the HTTP header (header field “Host:”). The information is available on the server as to what the browser thinks the correct name is.

There are three big reasons why the browser must access the Web AS with FQDN.

Use of HTTPS protocol. The SSL protocol requires that the server and browser names match the names in the certificates (if used).

When setting cookies for a specific domain, it’s important to know the domain the browser requires for the cookie, so that the cookie will always be returned to the server. A typical example is the SSO2 cookie used for Single Sign-On over multiple servers.

For Java Script calls to work over different frames (from different hosts in the same domain), each frame must relax its document domain. Typically the hostname is stripped, and the domain is set to the FQDN. For this to work, the browser must already know the FQDN for the document that it’s retrieving. This information cannot be set from the server and must be correct from the beginning of the request.

Especially for the domain relaxation aspect, the BSP runtime cannot know beforehand if this will be used for the application. If FQDN is not enforced, it just opens the potential for many other types of more difficult-to-diagnose problems.

ICM Configuration

Usually, FQDN and its use are a browser-related problem. The URL is entered at the browser and should be correct.

However, there are many cases where a URL is created at the server. One typical example is when a BSP application is tested in the SE80. A browser window is opened with the URL to test. In this case of course, the URL must also be a FQDN!

Usually the ICM picks up the correct domain for the server from a Domain Name Server (DNS). However, there are many cases where this does not work accurately. For them, ICM supports a profile parameter icm/host_name_full. We recommend you configure this parameter at all times. This is the hostname that will be used to build fully qualified URLs.

References

ICM Configuration. Specifically icm/host_name_full.

For domain settings see OSS/CSN Note 434918.

Setting Up BEx Web in BI 7.0 Netweaver

2008-09-25T09:36:00.000+05:30

Did you recently upgrade to or install BI 7.0 and want to make use of the new functionalities of BI and Java?
Look at Note 917950 - SAP NetWeaver 2004s: Setting Up BEx Web.
It contains a few attachments which is very handy in setting this up.

FREE DOWNLOAD Beginners SAP XI

2008-09-12T16:35:00.001+05:30

http://rapidshare.com/files/60027978/Beginners_guide_for_SAP_XI_Part1.rar

http://rapidshare.com/files/60027989/Beginners_guide_for_SAP_XI_Part_2.rar

Background documentation Business Partner Integration Using Industry Standards Locate the document in its SAP Library structure

2008-09-12T16:34:00.002+05:30

With this variant, SAP NetWeaver uses industry-specific business packages to support the integration of both new and existing industry standards. The business packages contain the collaboration knowledge defined by the respective industry standards, and the technical adapters required for the transport, routing, and packaging of industry-specific messages.

The technical adapters provided are:

● The RNIF adapter for the RosettaNet industry standard for the high tech industry

● The CIDX adapter for the chemical industry

Both adapters run in the central or non-central Adapter Engine.

The Adapter Engine connects senders and receivers that do not speak the XI message protocol by handing over messages to the Integration Engine and the other way round.

In addition to the central Adapter Engine, non-central Adapter Engines can be installed on an SAP NetWeaver AS Java without Integration Engines. There may be any number of non-central Adapter Engines, each associated with exactly one Integration Server with which the Adapter Engine communicates using the XI protocol.

The following security aspects apply:

● Propagating user identities

User identity propagation should not be used for B2B communication, because external users cannot be distinguished from internal users.

See also: Service Users for Message Exchange

● User authorization

Access control lists (ACLs) can be defined in the Integration Directory for the RNIF and CIDX adapters.

See also: Service Users for Message Exchange

● Message-level security

Message-level security allows you to digitally sign or encrypt documents exchanged between systems or business partners. It improves communication-level security by adding security features that are particularly important for inter-enterprise communication. Message-level security is recommended and sometimes a prerequisite for inter-enterprise communication.

However, message-level security is not guaranteed across the entire communication path of a message, but only for the intended B2B connections, which means the following communication paths when the RNIF or CIDX adapter is involved:

RNIF and CIDX protocol

○ RNIF or CIDX sender to Adapter Engine

○ Adapter Engine to RNIF or CIDX receiver

The RNIF and CIDX adapters support both a direct and a single-level hierarchical trust model.

Background documentation Adding an ABAP System to ...

2008-09-12T16:34:00.001+05:30

When you add an SAP NetWeaver Application Server (AS) ABAP system to your system landscape, you must decide whether you want to do the following:

● Add the system to Central User Administration (CUA)

● Use Lightweight Directory Access Protocol (LDAP) synchronization

You can do both. The following figure shows a number of ABAP systems in a CUA where the CUA central system is synchronized with an LDAP directory.

This graphic is explained in the accompanying text

ABAP Systems in a CUA Landscape and Synchronized with an LDAP Directory

Central User Administration

With CUA, you maintain user master records centrally in one system. Changes to user information are then automatically distributed to the child systems. The CUA provides you with an overview of all user data in the entire ABAP system landscape.

For more information, see Structure linkCentral User Administration.

The use of CUA is not a requirement, but it is designed to make the management of multiple ABAP systems easier. If a new ABAP system is not a child system of CUA, then you must manage the new system independently.

For more information, see Structure linkUser Maintenance.
LDAP Synchronization

You can make use of or provide information to an LDAP directory in your system landscape. The direction of the synchronization depends on whether the LDAP directory or the ABAP system is the leading system for user data.

Note

The user password is not transferred from the AS ABAP to the LDAP directory when the user data is synchronized. You must maintain the user password, both in the ABAP (or CUA) system and in the directory service.

Using Single Sign-On (SSO) with an AS Java, you can avoid duplicate password maintenance altogether. Configure the user management engine (UME) of the AS Java to use the LDAP directory as its data source. All systems must be configured to accept logon tickets. Users can now log on using the UME, are authenticated with the directory service, receive a logon ticket, and can then access all systems with SSO.

For more information, see Adding an AS Java System to Your System Landscape.

Recommendation

If you want to integrate a large number of ABAP systems, we recommend that you use CUA and synchronize the CUA central system with the LDAP directory. This way it is not necessary to synchronize each ABAP system separately. You can then distribute the synchronized data from the central system to the child systems and use the central system to manage the system-specific ABAP authorization role assignments.

For more information about LDAP synchronization, see Structure linkSynchronization of SAP User Administration with an LDAP-Compatible Directory Service.

Inconsistency in SAP NetWeaver BI in Just 5 Steps

2008-09-12T16:33:00.001+05:30

Consider an organization with multiple source systems feeding master and transactional data to an enterprise data warehouse based on SAP NetWeaver BI. During these data update stages, all the data targets that the system retrieves for consolidation, cleansing, and enrichment need the most current data. This is particularly critical in a single-source data warehouse. When you consolidate or enrich information, you must confirm that all the dependent loads succeeded.

If your enterprise has a single master data chain, the transactional loads can still progress even though the master data chain has failed for some of the master data. This allows inconsistent data to infiltrate your system. To avoid this, you need to set up dependencies in the data load process chain.

However, SAP NetWeaver BI 7.0 and earlier releases lack the infrastructure capabilities to set up these dependencies. We developed a five-step process that allows you to set up and track dependencies for critical loads:

Step 1. Become familiar with using the ABAP program process type in transaction RSPC

Step 2. Create a custom table in transaction SE11 to map and store the dependencies

Step 3. Create a custom program to get the dependencies for the data load

Step 4. Create a variant for each dependency you need

Step 5. Run the process chain with the variant you created in step 4

When implemented, the process automatically synchronizes the data loads — using dependencies that you maintain in a custom table — and checks for successful completion of these dependencies in the process chain execution. If a dependent process does not complete successfully, the process blocks the next data load and raises an error.

Assigning Authorizations Netweaver

2008-09-12T16:32:00.001+05:30

Use

A single administrator (superuser) or a group of administrators assign authorizations, depending on the size and organization of your company. By assigning authorizations, the administrator determines (within the range of possibilities defined by the programmer) which functions a user may execute or which objects he or she may access.

Process Flow

As an administrator, you perform the following steps to assign authorizations:

· Maintaining authorizations for each authorization object

An authorization is the combination of permissible values in each authorization field of an authorization object.

· Generating Authorization Profiles

Authorizations are grouped in authorization profiles in such a way that the profiles describe work centers, for example, flight reservation clerk.

We recommend that your system administrator automatically sets up authorization profiles using the Profile Generator (see Role Maintenance). If necessary, the administrator can also set up an authorization profile manually by choosing Tools ®Administration, User maintenance ® Profiles (see Creating and Maintaining Authorizations and Profiles Manually).

· Assigning authorization profiles to a user master record

By assigning the roles, you assign the corresponding authorization profiles (work centers) to a user master record.

Result

When an authorization check takes place, the system compares the values entered by the administrator in the authorization profile with those required by the program for the user to execute a certain activity.

Authorization Netweaver

2008-09-12T16:31:00.000+05:30

Authority to execute a particular action in the SAP system. Each authorization references an authorization object. It defines one or more values for each authorization field contained in the authorization object. Authorizations are combined in profiles, which are entered in a user’s master record.

The user can work in the SAP System after a successful authorization check.

Editing Predefined Authorizations Netweaver

2008-09-12T16:30:00.000+05:30

Once you have a role, you can generate authorizations automatically. The values of these authorizations are predominantly supplied with SAP default values. However, you can add missing values, change default values and also add additional authorizations from SAP templates or profiles.

Generating Authorizations

...

1. In role maintenance (transaction PFCG), choose the Authorizations tab page.

In addition to creation and change information, there is also information about the authorization profile there: the profile name, profile text, and status.

The status display on the Authorizations tab page displays whether or not the corresponding authorization profile is current. The profile is not current if the display is red or yellow. In this case, the status text on the tab page shows the reason for this.

2. To change the predefined and open authorizations of the transactions assigned to the role, choose Change Authorization Data or Expert Mode for Profile Generation.

You can explicitly select the maintenance options for the authorization values in export mode. This option is automatically set correctly in normal mode.

3. Maintain the predefined and open authorization fields for the transactions.

4. To generate an authorization profile based on this data with the Profile Generator, choose Generate ( ).

The authorization profile generated in this way is added to the master records of the users of the role after the user master records are compared.

Changing authorizations

...

1. Choose Change Authorization Data.

2. You can maintain organizational levels by choosing Org. levels.

If the selected authorization data contains organizational levels, the dialog window appears.

Organization levels can be plants, company codes and business areas, for example. Specify a global value for this role for each organizational level; that is, for each field.

You can display and maintain existing organizational levels with the transaction SUPO.

3. Save your entries.

4. Check or change the default authorizations in the hierarchy view displayed. See SAP authorization concept and Authorization maintenance symbols and status texts.

Authorization Checks Netweaver

2008-09-12T16:29:00.000+05:30

To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.

The following actions are subject to authorization checks that are performed before the start of a program or table maintenance and which the SAP applications cannot avoid:

· Starting SAP transactions (authorization object S_TCODE)

· Starting reports (authorization object S_PROGRAM)

· Calling RFC function modules (authorization object S_RFC)

· Table maintenance with generic tools (S_TABU_DIS)

Checking at Program Level with AUTHORITY-CHECK

Applications use the ABAP statement AUTHORITY-CHECK, which is inserted in the source code of the program, to check whether users have the appropriate authorization and whether these authorizations are suitably defined; that is, whether the user administrator has assigned the values required for the fields by the programmer. In this way, you can also protect transactions that are called indirectly by other programs.

AUTHORITY-CHECK searches profiles specified in the user master record to see whether the user has authorization for the authorization object specified in the AUTHORITY-CHECK. If one of the authorizations found matches the required values, the check is successful.

Starting SAP Transactions

When a user starts a transaction, the system performs the following checks:

· The system checks in table TSTC whether the transaction code is valid and whether the system administrator has locked the transaction.

· The system then checks whether the user has authorization to start the transaction.

The SAP system performs the authorization checks every time a user starts a transaction from the menu or by entering a command. Indirectly called transactions are not included in this authorization check. For more complex transactions, which call other transactions, there are additional authorization checks.

¡ The authorization object S_TCODE (transaction start) contains the field TCD (transaction code). The user must have an authorization with a value for the selected transaction code.

¡ If an additional authorization is entered using transaction SE93 for the transaction to be started, the user also requires the suitable defined authorization object (TSTA, table TSTCA).

If you create a transaction in transaction SE93, you can assign an additional authorization to this transaction. This is useful, if you want to be able to protect a transaction with a separate authorization. If this is not the case, you should consider using other methods to protect the transaction (such as AUTHORITY-CHECK at program level).

· The system checks whether the transaction code is assigned an authorization object. If so, a check is made that the user has authorization for this authorization object.

The check is not performed in the following cases:

You have deactivated the check of the authorization objects for the transaction (with transaction SU24) using check indicators, that is, you have removed an authorization object entered using transaction SE93. You cannot deactivate the check for objects from the SAP NetWeaver and HR areas.

This can be useful, as a large number of authorization objects are often checked when transactions are executed, since the transaction calls other work areas in the background. In order for these checks to be executed successfully, the user in question must have the appropriate authorizations. This results in some users having more authorization than they strictly need. It also leads to an increased maintenance workload. You can therefore deactivate authorization checks of this type in a targeted manner using transaction SU24.

¡ You have globally deactivated authorization objects for all transactions with transaction SU24 or transaction SU25.

¡ So that the entries that you have made with transactions SU24 and SU25 become effective, you must set the profile parameter AUTH/NO_CHECK_IN_SOME_CASES to “Y” (using transaction RZ10).

All of the above checks must be successful so that the user can start the transaction. Otherwise, the transaction is not called and the system displays an appropriate message.

Starting Report Classes

You can perform additional authorization checks by assigning reports to authorization classes (using report RSCSAUTH). You can, for example, assign all PA* reports to an authorization class for PA (such as PAxxx). If a user wants to start a PA report, he or she requires the appropriate authorization to execute reports in this class.

We do not deliver any predefined report classes. You must decide yourself which reports you want to protect in this way. You can also enter the authorization classes for reports with the maintenance functions for report trees. This method provides a hierarchical approach for assigning authorizations for reports. You can, for example, assign an authorization class to a report node, meaning that all reports at this node automatically belong to this class. This means that you have a more transparent overview of the authorization classes to which the various reports are transported.

You must consider the following:

· After you have assigned reports to authorization classes or have changed assignments, you may have to adjust objects in your authorization concept (such as roles (activity groups), profiles, or user master records).

· There are certain system reports that you cannot assign to any authorization class. These include:

· RSRZLLG0

· STARTMEN (as of SAP R/3 4.0)

· Reports that are called using SUBMIT in a customer exit at logon (such as SUSR0001, ZXUSRU01).

· Authorization assignments for reports are overwritten during an upgrade. After an upgrade, you must therefore restore your customer-specific report authorizations.

Calling RFC Function Modules

When RFC function modules are called by an RFC client program or another system, an authorization check is performed for the authorization object S_RFC in the called system. This check uses the name of the function group to which the function module belongs. You can deactivate this check with parameter auth/rfc_authority_check.

Checking Assignment of Authorization Groups to Tables

You can also assign authorization groups to tables to avoid users accessing tables using general access tools (such as transaction SE16). A user requires not only authorization to execute the tool, but must also have authorization to be permitted to access tables with the relevant group assignments. For this case, we deliver tables with predefined assignments to authorization groups. The assignments are defined in table TDDAT; the checked authorization object is S_TABU_DIS.

You can assign a table to authorization group Z000. (Use transaction SM30 for table TDDAT) A user that wants to access this table must have authorization object S_TABU_DIS in his or her profile with the value Z000 in the field DICBERCLS (authorization group for ABAP Dictionary objects).

See also:

· SAP Notes 7642, 20534, 23342, 33154, and 67766

· Documentation for RSCSAUTH

Authorization Checks in Your Own Developments

2008-09-12T16:27:00.002+05:30

Each time a transaction is started, the system automatically checks for authorization object S_TCODE. This check is also executed for any transactions that you created yourself.

If you use the Profile Generator to generate your authorization profiles automatically, the authorizations for the authorization object S_TCODE are contained in the profiles.

You can also add your own authorization checks to protect critical points in your ABAP programs.

If you call a transaction indirectly, that is from another transaction, the authorization check is not automatically performed. You must use transaction SE97 to set the check indicator check for the entry for the pair of calling and called transaction to ensure that the called transactions are also subject to an authorization check (see SAP Note 358122).

Adding Authorization Checks to Programs

In order to maintain authorization objects and fields, you need access to the authorization object Authorizations (S_USER_AUT).

To add authorization checks to programs, you need to do the following:

...

1. Create an Authorization Field
2. Create an Authorization Object
3. Programming Authorization Checks

Use the ABAP AUTHORITY-CHECK statement. Specify alphabetic values in uppercase letters: ABC. Test values from user master records are converted to uppercase before being passed to AUTHORITY-CHECK.

See the ABAP programming documentation for more information (check authorization).

Programming Authorization Checks

2008-09-12T16:26:00.000+05:30

programmer wants to make an authorization check before bookings for business customers can be changed.

To do this, the programmer should create authorization fields (ACTVT and CUSTTYPE) and assign for each field defined the value to be checked (02, B). Authorization fields are created under Tools ® ABAP Workbench ® Development ® Other tools ® Authorization objects ® Fields (transaction SU20).

Programmers should also create an authorization object (here S_TRVL_BKS) and assign the authorization object to an object class.

Authorization fields are created under Tools ® ABAP Workbench ® Development ® Other tools ® Authorization objects ® Objects (transaction SU21). Authorization objects can also be created in the Object Navigator (transaction SE80).

You program the authorization check using the ABAP statement AUTHORITY-CHECK.

AUTHORITY-CHECK OBJECT 'S_TRVL_BKS'
ID 'ACTVT' FIELD '02'
ID 'CUSTTYPE' FIELD 'B'.
IF SY-SUBRC <> 0.
MESSAGE E...
ENDIF.

The AUTHORITY-CHECK checks whether a user has the appropriate authorization to execute a particular activity.

When this happens, the system checks the authorization profiles in the user’s master record for the appropriate authorization object (S_TRVL_BKS). If the authorization is found and it contains the correct values, the check is successful.

The system administrator has defined the following authorizations for the authorization object S_TRVL_BKS:

· S_TRVL_CUS1 with the following values:

* for customer type ( CUSTTYPE field) and

03 for activity (field: ACTVT).

Users with this authorization can display all customer bookings (activity 03 = display).

· S_TRVL_CUS2 with the following values:

B for customer type ( CUSTTYPE) and

02 for activity (ACTVT).

Users with this authorization can change all business customers (activity 02 = change).

When assigning profiles, the system administrator gave different authorizations to different users.

User Miller has been assigned a profile containing both of these authorizations (S_TRVL_CUS1 and S_TRVL_CUS2). Miller can therefore change bookings for business customers.

User Meyers on the other hand, is only authorized to display the records (S_TRVL_CUS1) and therefore cannot change bookings.

Free Download APO Weeks pdf

2008-09-12T16:25:00.001+05:30

http://www.savefile.com/files/1203657

APO - Locking Planning Area Netweaver

2008-09-12T16:24:00.004+05:30

Question: Hello all,
I have a strange requirement from the project team:

We have a planning area which we do not want the users using during a certain point in time during the day. We do not want the users to be locked. We do not want the users to log out.

Is there a way to lock a planning area without user's logging out?

Planning area (APO_PAREA) is protected by the following authorization objects:

C_APO_FUN
C_APO_SEL2
C_APO_SEL3
C_APO_IOBJ
C_APO_CPY

System specifications:

SAP SCM 4.0
Kernel: 620

Thanks,
Sam

Answer:
SAP Security is not time dependent based on the hour. You can add and remove access based on the from-to date on the user master record but you cannot control it on an hourly basis without a lot of custom programming.

Sounds like you need to rethink your process.

APO - second role causes authorization problems

2008-09-12T16:24:00.003+05:30

Question: Hello all,

the following effect occurs on my APO system:
User A has assigned a role to do customer plannings, everything works. After that the user gets an additional role for PPDS or SCPT. Now, the customer planning doesn't work anymore?
More authorizations - less rights?
This effect is indenpendent of user A, I tried it with several ones. Always the same.

What can I do?

The users need access to both transactions!

Thanks for your help!

Answer:
may be user comparision issue.
if u get a solution for this problem please post it here.
thanks

Answer:
Hello,

it's not a problem of user comparison.

Answer:
Have you run a trace ?
_________________
Best Regards
Bazza

Answer:
Sometimes SAP performs an auth check to determine screens dynpros or the path which the runtime environment should be generated from.

In some special cases of the above, adding authorizations will give you a more restricted path followed (or it would appear to be so) as a result.

Try logging on with less auths (or none what-so-ever) and see what you get.

Contrary to popular belief, more auths (or SAP_ALL) does not contain more (or all) authorizations for the system.

Tarr

Answer:
No APO experience so look at this as a generalization thta may have some applicability.

If you had a role with an authorization with P_PERNR with value of I and another role with an authorization with the value of E and then assigned the roles together something the user could have done earlier will quit working. This is because these authorizations are mutually exclusive and the system is smart enough to recognize this. You may need to study the values of authorizations in your roles (and the help text) to see if APO delivers an object like P_PERNR.

ps if it does please share.

APO - tcode /SAPAPO/MC62 - Maintain Characteristic Values

2008-09-12T16:24:00.001+05:30

Question: Hi

Has anyone been able to restrict this transaction to planning area? The authorisation object with planning area is referenced, however the planning area field is not checked.

Has anyone else experienced this and if so have you found a solution to restricting to planning area or master planning object structure?

Thanks

Answer:
Hi

Has anyone been able to restrict this transaction to planning area? The authorisation object with planning area is referenced, however the planning area field is not checked.

Has anyone else experienced this and if so have you found a solution to restricting to planning area or master planning object structure?

Thanks

Yu can ask an ABAPer to check coding and see if these authorizations objects are checked.

Snowy
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified

Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759

Answer:
Hi,

I have the same problem.
It seems like the field APO_FUNC is checked, but not APO_PAREA.
Anyone that found a solution for this?

APO Alert Monitor Netweaver

2008-09-12T16:23:00.002+05:30

Question: Within our APO system, they want to split access to data in different countries. In the Alert Monitor, /SAPAPO/AMON1 you can see data for different product and locations. Also the Alert Monitor can be called from other transactions in APO.

The only authority check that I'm aware of for the Alert Monitor is C_APO_AMON and this doesn't permit me to split data.

Is there any way to ensure this kind of split? Or does the system do this automatically?

Thanks

Answer:
duplicate posting locked.

please never double-click inside a browser (such as Netscape or Internet explorer)

Snowy
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified

APO Alert Monitor Netweaver

2008-09-12T16:23:00.001+05:30

APO authorization problem Netweaver

2008-09-12T16:22:00.002+05:30

Question: Hello,

Anyone familiar with APO authorizations? I am trying to limit to display only in the product master with tcode /SAPAPO/MAT1. According to the person testing he has create, change, delete access but I only have an 03 and 08 as the activity value. Go figure

The other thing is in the planning book screen, certain buttons are missing when using tcode /SAPAPO/SDP94. I can not see the "selection window" nor the "display dependant objects" buttons. I traced a user that has it and added the access but still do not see the buttons.

Any help on either of the two issues above will be most appreciated.

Thanks in advance.

Answer:
For your /SAPAPO/SDP94 issue, you need to maintain C_APO_FUN to have C_SELCTION, C_SELE and C_SELORG on field APO_FUNC and the name of the planning area on APO_PAREA.

For the /SAPAPO/MAT1 issue, ensure you have only 03 on C_APO_PROD.

Good Luck.

Answer:
Thanks for the help. However in the /SAPAPO/MAT1 issue, I definately do have only 03 in the C_APO_PROD auth. Still he says he's able to do more.

Is this a situation were you may enter the screen and it looks like it's in "change" mode but when you actually try to do something it tells you that you are not authorized.

Also, is there an authorization book on APO. That would help.

Answer:
Hi am having a imilar issue. if i don't attach C_SELCTION to C_APO_FUN , the user is not able to see the selection window Icon or do any selection. But if i attach the C_SELCTION to C_APO_FUN, user is able to make changes fields like "confirm requirements " .

Can anyone help me to district it to Display only !

Answer:
Check out OSS Note:

Authorizations in APO demand planning - Note 400434

APO Security netweaver

2008-09-12T16:22:00.001+05:30

Question: Hi,

does anybody has an overview of which authorization objects are checked against which APO transaction? The standard SU24 for APO is maintained really poor.

Thanks a lot for all help!

Answer:
As with most Add-ons or industry solutions the SU24 AND the authorization checks themselves are lacking and not robust. You will find that many of the tcodes are controlled ONLY by S_TCODE and nothing more. To hasten your answer use ST01 and mark atuhorization trace and use the analysis report to configure SU24.

APO Security issue Netweaver

2008-09-12T16:21:00.001+05:30

Question: Hi Guys,

I am trying to implement APO security. (APO v. 3.1)

In R/3 the method we used to design roles was:
1. Listed down the organizational entities we would want to control
eg: company code, Business Area, profit centers, purchase org., plants etc
2. Build up roles restricting the values for these entities
3. Assign these roles to the users.

But in APO, we have only one organizational entity - Plan Version and we want to control many other values too. If we are to restrict the transaction access by location, planning book, resource etc for eg. a tcode say /sapapo/sdp94. The authorization objects that are validated against do not have a default status of check/maintain in SU24. I would have to manually change the status to check/maintain - Also then i would have to give default values for the fields of those objects. This would mean i am deviating from SAP standard way of doing things...

My question is : If i want to restrict access in demand planning module by say resource, planning book and location - Is the above said way the right way to carry on?

How is Security usually done in APO?

Regards,
VS

Answer:
There is no standard in Su24. It is a configuration table and is up to the customer to make it work the way they need it, NOT rely on SAP as they have access granted to object no end user should have. In the Add-on modules like APO the SU24 entries are abisimal at best and require your intervention.
note that moving the entry from 'C' to 'CM' means nothing as far as control goes. It is the move from 'N' to 'CM' that cause SAP to start failing the check if the user is not authorized.

Answer:
Thanks John, Your opinion is appreciated - It is good for me to start with. I was under the impression that changes done in SU24 meant deviation from the standard way of doing things..

Any idea what needs to be done during an upgrade - Would changes be overwritten by SAP Standard then.

VS.

Answer:
SU25 is your upgrade transaction for SU24, but before the upgrade use su25 to create a transport of SU24 and export it. then if you use SU25 incorrectly then you can recover by imporitng the file back into the system

Analysis of hanging situations

2008-09-12T16:20:00.000+05:30

A hanging situation can be caused by problems in the database, in the operating system or in the R/3 System. Afterwards an analysis is almost impossible. Therefore it only makes sense to open a OSS message on this, if all information described below was gathered during the hanging situation.

A hanging situation exists if many R/3 work processes run "endlessly". If only one individual work process is affected, this is not an hanging situation but a report that is running very long. The examination of such a report is described in Note 155413.

Symptoms of hanging situations:
- Archiver stuck
- Update process is deactivated (SM13/SM50)

Information to be gathered for analysis:
1. Process Overview
- SM50/SM66/dpmon
If you can get in to SAP transaction, then you need to execute dpmon on unix level (sidadm)

Example
- dpmon pf=d:\usr\sap\PRD\sys\profile\PRD_DVEBMGS00_sapserver
- Enter m (for menu)
- Enter l

2. Check on CPU/Memory/Disk utilization
- ST06 -> "Detail analysis menu" -> "Top CPU Process"
- topas-AIX
- top-hp
- nmon
- Caplan monitoring

3. DB Process Overview
- ST04 -> "Detail analysis menu" -> "Exclusive lockwaits"
- Check oracle trace file /oracle/SID/saptrace/background/alertSID.log

4. SAP Developer Trace/SQL Error Log
Before restarting the SAP system, backup all Developer Traces.

Reference:
Note 155402 - Analysis of hanging situations

Service Implementation in Java

2008-09-12T16:19:00.002+05:30

You can generate both client and server proxies in Java for Web Services. Client proxies are for consuming services and server proxies are for provisioning services. In this narrated recording, we will provision a server proxy to provide the business logic entirely in Java on the SAP NetWeaver Composition Environment for the ManageVender service interface (WSDL) that was modeled previously in this blog series. We will add the business logic for two web service operations CreateVendor and SearchVendor.

In the process of provisioning the service, we will use a number of features of Java EE 5, such as EJB 3.0 Session Beans, Java Persistence API (JPA), and the Java Persistence Query Language (JPQL). We will then test our service with the WS Navigator and verify the results in the database with the Open SQL Data Browser.

SEE VOICE RECORDED DEMO

Service Testing and Registry PP

2008-09-12T16:18:00.000+05:30

In this section we'll show you how you can test our server proxy from within the ABAP workbench as well as testing with the Web Services Navigator. We’ll cover some new 7.10 features of Web Service Navigator tool that my colleague, Vladimir Dinev, had shared with me. We’ll then move on to the Services Registry to show you how to add your own classification to the existing ManageVender service.

TESTING: SEE VOICE RECORDED DEMO

SERVICES REGISTRY: SEE VOICE RECORDED DEMO

Consuming Services with ABAP PP

2008-09-12T16:17:00.000+05:30

Continuing in the second week of the In-Depth Look at Enterprise SOA blog series, we will focus today on the ABAP capabilities to discover and create an application from ESR and Registry.

This video starts off with the process to create a Service Consumer object (former called a client proxy) in NetWeaver 7.1. We will then perform the same process in NetWeaver 7.0 so that you can study the differences and improvements that have been made. The main area of differences is in the new tool - SOAMANAGER - you use in NetWeaver 7.1 to create the Logical Port. We will also discuss some of the new capabilities of ABAP 7.1 to work with Asynchronous services and Reliable Messaging. The video will close out with some sample applications that use this Service Consumer object to call the service from within different types of ABAP programs. Special focus will be paid to using Web Dynpro ABAP and its Service Call Wizard.

Consuming Services with ABAP

Adjust Roles and Profiles in solution manager

2008-09-12T16:16:00.000+05:30

Before you assign SAP standard roles and profiles to users, copy and specify them.

SAP delivers roles and profiles with default values. If they are missing, you must set the values in the authorization objects yourself. Proceed as follows:

...

1. Load the roles/profiles from client 000 into your target client. You can:

○ Transport client 000 into your target client (roles and profiles)

○ Upload und Download (for roles in transaction PFCG)

○ RFC connection in transaction PFCG (for roles; menu path: MENU ® READ FROM OTHER SYSTEM WITH RFC). In this case, you must have set-up the RFC connection (transaction SM59).

2. Copy the roles/profiles into your namespace.

a. Choose Role Maintenance (transaction PFCG).

b. Enter a role name and choose Copy Role.

c. Enter the name of the new role in the To Role field.

d. Choose Copy All.

e. Save.

3. Complete missing values in the authorization objects.

a. Choose the Authorizations tab.

b. Choose ChangeAuthorization Data.

c. Enter your own values for the authorization objects, or double-click on the yellow traffic light.

The authorization objects appear with a green traffic light.

When you double-click on the yellow traffic light, the value “*” appears. This grants full authorization for this field of the authorization object.

e. Save.

f. Generate the authorization profile.

4. Assign the role to users.

a. Choose the Users tab.

b. Enter the user names.

c. Choose User Adjustment.

d. Save.

You can also assign the roles to the users, in the user maintenance (transaction SU01).

I have a problem with sending RFC from R/3 to XI

2008-09-01T20:47:00.001+05:30

This weblog is a response to a few question about the basic configuration of the RFC sender adapter
that were posted on the XI forum (and also on my e-mail) :)

So here we go, basically we have to configure 2 things:

a) RFC destination

b) RFC channel in the XI directory

RFC destination:

1. To create the RFC go to TCODE: SM59

2. Create new destination of type T (TCP/IP)

3. Make sure you select Registered Server Program option before writing your program ID

4. Write you program ID (remember it's case-sensitive)

5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)

7. No configuration in the J2EE administrator nessecary

Now we can proceed to RFC channel configuration:

1. Enter your Application Server

2. Your Application Server Service

3. Enter your Program ID from the RFC destination

And we're done:)
Now you can test the RFC destination in SM59 to see if it works.

How do I use 'Apply Control Record Values from Payload' parameter with the IDOC adapter?

2008-09-01T20:45:00.002+05:30

See notes:
a) 728792 - how the fields in the control record get set.
b) 792333 for an overview of how to convert partners in the IDoc adapter.

Also check:

Fields of the IDoc Control Record

The following table provides information about how the fields of the control record are filled by the receiver IDoc adapter.

Field Name	Value
TABNAM	Constant EDI_DC40, if version = 3 Constant EDI_DC, if version = 2
SNDPOR	Constant SAP+SYSID of the Integration Server
MANDT	Integration Server client
DOCNUM	Consecutive number from the IDoc number range EDIDOC/01. For reasons of uniqueness, it cannot be taken from the payload.
DOCREL	Integration Server release This is not the release from the communication channel or the receiver system release.
RCVPOR	Determined from port in the receiver IDoc adapter.
ARCKEY	Message GUID for revision
SERIAL	Determined from the control record of the IDOC XML payload.
MESTYP	From the XI interface
IDOCTYP	From the XI interface
CIMTYP	From the XI interface

Partner conversion takes place in the Integration Directory.

Logical systems for SAP systems can also be specified in the System Landscape Directory. B2B partners can be converted by using XI parties.

XI: IDOC Adapter - EDI_DC40 - demystified

2008-09-01T20:45:00.001+05:30

When you start working with IDOCs scenarios the first thing you'll probably notice
is the IDOC receiver channel configuration and maybe the lack of sender IDOC adapter:-)

There's one little checkbox you can set or not: "Apply control record values".
When you check standard documentation you may be little confused
but I hope to clear all things out with this weblog.

Scenario 1

We don't set the checkbox.

Since we do not want to fill the control record ourself we can Disable the EDI_DC40 segment.

Now the control record will be filled with those parameters:

TABNAM, SNDPOR, MANDT, DOCNUM, DOCREL, RCVPOR, ARCKEY, SERIAL, MESTYP, IDOCTYP, CIMTYP
SNDPRN, SNDPRT, SNDPFC, RCVPRN, RCVPRT, RCVPRT, STATUS, DIRECT OUTMOD, CREDAT, CRETIM

and they will have values like described on help.sap.com
(so basically nothing difficult over here).

Scenario 2

We set the checkbox.

If you read the documentation you may see this:

"If you have not set the Apply Control Record Values from Payload indicator
in the receiver IDoc adapter, the fields are filled as follows...."

but this is only half of the truth:) Because if you mark the checkbox you're also not able to fill those fields.

If you want to check how this works take a look the little example below.

As you can see I'm sending my IDOC to the IDOC adapter and I'm setting values
like SNDPRT, RCVPRN and also some other like MESTYP.

But the IDOC adapter changes them and uses the standard values as when you don't set that checkbox.

That means that the only values you're allowed to change are those:

MESCOD, MESCFT, TEST, EXPRSS, STD, STDVRS, STDMES, SNDSAD, SNDLAD, RCVSAD, RCVLAD, REFINT, REFGRP

as you can see from the example the IDOC Message Code (MESCOD) is created correctly (just like it was set in my mapping).

This is a very easy scenario but I hope it may be useful for IDOC adapter begginers.

I can't see my adapters in the adater monitoring after the import of a new SP

2008-09-01T20:44:00.003+05:30

a) try reimporting "SAP Basis software component"

b) take a look at the XI installation guide on how to do it: "Importing the XI Content for Software Component Version SAP Basis 6.40"

Where can I find J2SE plain Adapter

2008-09-01T20:44:00.001+05:30

https://websmp106.sap-ag.de/swdc

Then this path:

- Support Packages and Patches
- - SAP NetWeaver
- - - SAP NETWEAVER
- - - - SAP NETWEAVER 04
- - - - Entry by Component
- - - - - XI Adapter Engine J2SE
- - - - - - XI CONNECTIVITY SE 3.0
- - - - - - - OS independent

How can I access filename from File/FTP Sender Adapter

2008-09-01T20:43:00.000+05:30

Finally (from SP14) we can receive a file do something with it inside XI
and send it back with the same name. No need for writing adapter modules,
no need for variable substitution - SAP gave us a new, easy solution to this issue.
From XI 3.0 SP14 we can use Adapter Specific Message Properties.
Now not only can we use the filename of the received file but we can also change it
inside our mapping (using graphical mapping for example).

Let's see how the scenario works:

Step 1

Inside your file/FTP adapter we can now set "Adapter Specific Message Properties"
which tell the adapter to include those properties inside the SOAP message sent to XI
from the adapter. Because we want to see the whole example we can start by setting all of them.

Step 2

The file/FTP receiver adapter must also know that he has to use those new properties
so we also have to set them on the receiver's side.

Step 3

Because we also want to get the filename inside our mapping we have to create a user defined function
which will return the filename and map it to one of our XML tags.

The code shown above just takes the filename so we can map it, if you'd like to change it
have a look at the code provided by SAP: Accessing Adapter-Specific Properties

When we run our file to file scenario we can now see that there's a new section called DynamicConfiguration....

...which is being populated with some values.

When we take a look at our outbound message we can see that one of our tags has the filename value.

Later on we can check our FTP folder to find out that the created file has exacly the same name
as the file from the sender adapter.

Easy wasn't it? This example just shows that SAP listens to us (developers)
to make our lives a little bit easier :)

Where can I find FAQ on adapters?

2008-09-01T20:42:00.002+05:30

Take a look at this note:
821268 - XI 3.0 Adapter Framework: Overview of available FAQ notes
inside you'll find all available FAQ SAP notes.

How can I access adapter monitor?

2008-09-01T20:42:00.001+05:30

Try this link:
http://xiserver:j2eeport/mdt/amtServlet

Field Name	Value
SNDPRN	From XI sender service, configuration in Integration Directory, System Landscape Directory
SNDPRT	Constant LS
SNDPFC	Initial
RCVPRN	From XI receiver service, configuration in Integration Directory, System Landscape Directory
RCVPRT	Constant LS
RCVPRT	Initial
STATUS	Constant 03
DIRECT	Constant 1
OUTMOD	Constant 2
CREDAT	Date created
CRETIM	Time created