ABAP, NetWeaver, ERP Tutorial

SAP Installation number is a 10-digit number supplied by SAP. You receive the installation number as part of the installation package. The number is printed on the "Request Fax License Key" form.

SAP has stated that they recommend one installation number per SAP product landscape. For example, in a typical R/3 landscape where you have a development, QA and production system. This would all be defined and registered under one installation number. If you then have developers who have registered developer keys (developer keys are defined for and map to a SAP installation number) then that developer key will work in all of the systems defined for that landscape. That means that a developer key available in the development system would then also work in the production system. The developer will only have to supply it once per SAP instance. This also applies to SAP access key(object key) which is used to modify SAP standard programs.

Below link explains SAP installation number, license key, developer key perfectly.

Installation SAP Numbers, SAP Keys, SAP License number

Below code snip can be used to copy one KM folder and its subfolders to another location.

Note:

1. The destination folder shouldn’t exist before the copy. Otherwise the copy method will raise an exception.

2. The source folder display name are copied too. It might need to be changed if necessary.

String source = ";/documents/source";;
String destination = ";/documents/destination";;
 
try {
	//1. Create a RID
	RID aRid = RID.getRID(source);
	logger.errorT(aRid.getPath());
	//2. Get Resource Factory
	IResourceFactory resourceFactory = ResourceFactory.getInstance();
	//3. Get user and resource context
	com.sapportals.portal.security.usermanagement.IUser user =
		WPUMFactory.getServiceUserFactory().getServiceUser(";cmadmin_service";);
	ResourceContext rContext = new ResourceContext(user);
	//4. Retrieve the collection for Resource using the resource context
	IResource aResource = resourceFactory.getResource(aRid, rContext);
	//5. Get Destination RID
	RID dRid = RID.getRID(destination);
	logger.errorT(dRid.getPath());
	IResource dResource = aResource.copy(dRid, new CopyParameter());
 
	dResource.setProperty(new Property(PropertyName.createDisplayname(), ";destination";));
 
	logger.errorT(";After Copy";);
} catch (ResourceException e) {
	logger.errorT(";ResourceException INSIDE copy(): "; + e.toString());
} catch (UserManagementException e) {
	logger.errorT(";UserManagementException INSIDE copy(): "; + e.toString());
}
 
wdControllerAPI.getComponent().getMessageManager().reportSuccess(";Files are copied successfully.";);

SAPconnect provides a standard interface for external communication, which supports sending using telecommunication services, such as FAX, text messages (pager/SMS), Internet mail and X.400, as well as sending to printers and between different SAP Systems.

Read more…

SAPEP – SAP NetWeaver Portal Fundamentals

EP120 – SAP NetWeaver Portal Development

EP130 – SAP Knowledge Management and Collaboration Development

EP200 – SAP NetWeaver Portal System Administration

EP300 – Configuration of Knowledge Management and Collaboration

EP600 – Configure of the Universal Worklist

There are many companies utilize the SAP portal as the central access of company-wise business applications. If company launches the SAP CRM, it also needs to be integrated into the portal landscape.

SAP deliveries predefined content bundled as business packages for completing business tasks. In essence, the business packages provide out-of-the-box portal applications that can be easily modified to suit a customer’s needs. SAP provides business packages for CRM from version 5.0 to 7.0.

In general, the business packages are downloaded and installable via SAP Solution Manager. In exceptional cases, the business packages can also be downloaded from the Service Marketplace, but it require approval before download.

Another way to integrate the CRM into portal environment is to create BSP iViews directly in the portal content. This is the easiest way to integrate the CRM into portal if you just want to have a simple integration, for example, allow certain groups have the capability to search CRM opportunities.

Below are the detailed procedures:

1. Configure SSO between portal and CRM server.

Generally there are two methods to configure SSO. One is user mapping, the other is using logon ticket.

2. Create the BSP iView.

Create the BSP iView with below attributes:

There are some other parameter patterns you can use to view other CRM objects:

http://<serverhost>:<port>/sap/crm_logon/default.htm?crm-object-type=BT126_APPT&crm-object-action=B&crm-object-value=<guid>

http://<serverhost>:<port>/sap/crm_logon/default.htm?crm-object-type=BP_ACCOUNT&crm-object-action=B&crm-object-keyname=PARTNER&crm-object-value=<partner_id>

http://<serverhost>:<port>/sap/crm_logon/default.htm?crm-object-type=BP_CONTACT&crm-object-action=B&crm-object-keyname=CONP_NUMBER&crm-object-value=<contact_id>

Other object types can be found in CRM view BSPDLCV_OBJ_TYPE.

3. Create portal pages, role and assign role to users or groups.

Below screenshot shows the result of CRM and portal integration.

In some portal scenarios, the portal users need the capability to register by themselves, for example, the portal is used as an external facing site to allow customers to find, download product information. In this post, I will give a step-by-step guide on how to configure it.

1. Start user management configuration

Read more…

Software units are installation units. Usage types of SAP NetWeaver are software units to be installed and configured. Software units or usage types can be run together with others in one system, they can run separately on different systems. The usage types Application Server ABAP(AS ABAP) and Application Server(AS Java) are also used as a foundation for other units. You can select one or more usage types during NetWeaver installation as below picture shows.

The delivered usage types are: AS ABAP, AS Java, BI Java, DI, EP Core, EP, MI, PI.

Read more…

What is Service Registry?

SAP Service Registry is a UDDI-compliant registry that supports the publication. classification, discovery and testing of enterprise services across the IT landscape. The SAP Service Registry along with Enterprise Services Repository are shipped with SAP NetWeaver Process Integration 7.1 and SAP NetWeaver Composite Environment 7.1.

In SAP NetWeaver Process Integration 7.1, you can use the ES Repository and Registry with SAP NetWeaver PI and take full advantage of the process integration capabilities of SAP NetWeaver.

SAP NetWeaver Composition Environment 7.1 offers full service provisioning capabilities, also for those who need to work with a lean development environment and do not focus on process integration. For those customers, the ES Repository and Registry offers capabilities for service provisioning and consumption.  Below diagram shows roles that Enterprise Service Repository and Services Registry play in SAP Enterprise Service Architecture.

Read more…

In my previous post, I have explained what the DataSource is and how SAP deal with it. In this post, I would like to share more information about the DataSource.

The default JDBC drivers are delivered in library component: com.sap.portal.jdbcdrivers. You can find a list of JDBC driver library for each DBMS – P9sybase.jar, P9db2.jar, P9oracle.jar, P9informix.jar, P9sqlsever.jar.

You can add your aliases in the DataSource definition. Aliases are alternative names that are used by the application components when they look up a DataSource object. Below figure shows the aliases used by SAP standard applications.

Read more…

As a system, the SAP J2EE Engine consists of three logical layers:

• SAP Java Enterprise Runtime – comprises low-level modules that provide functions such as class loading, cluster communication, persistent configuration data management, and so on. For more information, see SAP Java Enterprise Runtime.
•  Pluggable components – consists of interfaces, libraries and services components that provide various runtime functions and programming APIs. For more information, see Pluggable Components.
• Applications layer – refers to the applications that are deployed and run on the SAP J2EE Engine. For more information, see Applications.

Read more…