Issue :

Error from dev_jrfc.trc file

================================================

LOCATION SAP-Gateway on host <hostname>

ERROR registration of tp <Jco destination name> from host

<hostname> not allowed

TIME Fri May 10 10:30:58 2013

RELEASE 720

COMPONENT SAP-Gateway

VERSION 2

RC 720

MODULE gwxxrd.c

LINE 3642

COUNTER 6303

Return code: RFC_FAILURE(1)

error group: 102

key: RFC_ERROR_COMMUNICATION

Solution :

As of 720 kernel, registration of external server program is controlled by profile parameters gw/acl_mode, gw_reg_info and gw/sec_info.

For security reasons, SAP has made it mandatory to use gw/reg_info and gw/sec_info to allow any external program to get registered on host.

So, entries of the host wanting to register program in gateway, has to be maintained in the file reg_info and sec_info.

Location of these files is maintained using gw/reg_info and gw/sec_info profile parameter.

If the files are created without any entries, then no external server is allowed to register external programs. If files are created then entries for the servers has to be maintained.

If the files are not created, then parameter gw/acl_mode can be used to control registration of external programs on the system.

gw/acl_mode = 0 will allow registration of external server program

gw/acl_mode = 1 will not allow registration of external server programs and you need to maintain reg_info and sec_info files.

More information about the same can be found in below SAP notes :

Note 1408081 - Basic settings for reg_info and sec_info

Note 1069911 - GW: Changes to the ACL list of the gateway (reginfo)

·  Introduction

·  Component of ASCS

·  Architecture of ABAP System

·  Separation of  ASCS from Central Instance

·  Installation of ASCS

----------------------------------------------

· Introduction

AS ABAP instance of an SAP system containing the enqueue server and the message server (ASCS = ABAP SAP Central Services).

Since SAP NetWeaver 7.0 the Message Server and the Enqueue Work Process  are separated from the Central Instance. These two are grouped within the ABAP SAP  Central Services (ASCS) as server.

------------------------------------------------

· Component of ASCS

Enqueue work process administers the lock table in the shared memory . The lock table contains the logical database locks of the ABAP runtime environment of the SAP system. Only one enqueue work process is needed for each system

Message Server (MS) handles communication between the distributed dispatchers within the AS ABAP, thereby enabling scalability of several parallel application servers. The message server is configured only one per SAP system

-------------------------------------------------

· Architecture of ABAP System

--------------------------------------------------------------------

· Separation of  ASCS from Central Instance

1. Split ASCS from CI

2. Uninstall ASCS from CI host after splitting

------------------------------------------------------

· Installation of ASCS

Now you can install the ASCS on new host.

Thanks.

Atul

Case 1: Problem with Cache Refresh

When we perform any changes to our design objects and configuration objects which were created in our IR and ID and if the changes were not reflected to that objects, at that time every one mind would point to perform the cache refresh. We have different options available to perform the cache refresh. 

1.      In IR from MenuàEnvironmentàClear SLD Data cache.

2.      In ID from Menu ClearàEnvironmentàSLD Data Cache. 

When we log in to ABAP stack and hit the transaction SXI_CACHE there you can observe the status will be in red color and the cache will not be up-to-date and unable to refresh cache. Even though if we perform the cache refresh the changes are not reflecting since the cache is not working properly.

From IR from menu using cache notifications we can see whether cache is refreshing or not. From that option also it shows the status as RED color and cache is not up-to-date and cache is not refreshing.

So how to resolve this issue and what might be the problem for displaying the status as red and cache is not up-to-date. 

To resolve this issue logon ABAP stack and check the RFC Destination of

Type H: INTEGRATION_DIRECTORY_HMI in this check whether the path prefix is maintained or not. 

If we observe the above screenshot we can identify that path prefix as not maintained anything. So maintain the path prefix as in the below screen shot and save it. 

After performing the above step go to SXI_CACHE and perform cache refresh. Now cache will perform the refresh and the status will be as below. 

Case 2: Problem with Cache Refresh

When Path Prefix is fine and you unable to perform the Cache Refresh

GO to SM21, search for the system logs. You could find multiple entries as below for user “SAP_PI_RFC”.

During processing of asynchronous messages a lock was triggered that prevents a message being processed more than once in parallel. Either the lock prevented this, or the lock was not cleared in an earlier call and so now prevents further processing. It should not be possible to execute a message more than once. Notify support of the problem. If the lock was not cleared, you can remove it manually SM12 – You can confirm with PI team). You should then be able to continue processing without problems.

Solution: Please make sure these are NOT recent entries. Delete these entries from SM12 after confirmation from functional/Technical team.

Case 3: Problem with Cache Refresh

There is a chance that system has too many suspended DB commands at DB02. There might be any SQL command blocking other inbound queue.

Solution: It just happens due to huge blocking. Kill the culprit process which is causing blockage.

Case 4: Problem with Cache Refresh

Once I have resolved the issue by restarting the Java stack system from SMICM T-code.

The goal of integrating independent IT  systems  with Web services was almost cut short by a  lack  of interoperable implementations, even  though  they were based on the same specifications.  This  paper outlines how this situation arose, what  has been done to date, and continuing efforts.

View Document

This tutorial shows: how to create a Web  Service  from a Portal Service and how to test a Web  Service with the Enterprise Portal Web  Services  Checker.

View Document

In this article I examine three different tools  for testing your SOAP web services. I explain  how to use them, highlight their pros and  cons, and provide some additional tips. The  three tools to examine are: XMLSpy, SAP  SOAP client, and the Web Service Navigator  (in Web AS).

View Document

This document answers frequently asked  questions about SAP and Web services.

View Document

This SAP Insider article gives an overview of  web services and web services standards and  explains where they fit in to your business  processes.

View Document

there are a lot of documents in smp and scn - but they are all not exactly cleare where to put the needed parameters.

for example: http://help.sap.com/saphelp_crm60/helpdata/en/a5/0822bcc7d844269557634f013c6b04/frameset.htm

here is a screenshot of my webas java config with working proxy-configuration, so you can easy find where to put the parameters in configtool:

Please make use of following feature to upload files (Data and Cofiles) to application server in case OS access is not present.

Step 1: Log-On to R3 of the system on to which you want to copy the files. And go to transaction SE37. The following screen should come up:

Step 2: Give Function Module Name - ARCHIVFILE_CLIENT_TO_SERVER and execute.

Step 3: Give source file name (compete path + Filename from loccal drive) in parameter PATH and Target filename (compete path + Filename), target path can be taken from AL11, Please note that soft links are not accepted. And execute.

Accept pop-ups asking for permission if any.

Done!!!

Proceed with adding the request to buffer as usual. In addition to uploading Data file and Cofiles it can be used to many other purposes as per your requirement.

Don't forget to press like button if you find this document useful

Activate Emergency User on SAP AS Java

Start Config Tool --> Path is as below

/usr/sap/SID/J*/j2ee/configtool/

Switch to configuration editor mode.

You will find below screen, choose cluster_config®system ®custom_global ®cfg ®services ®com.sap.security.core.ume.service ®Propertysheet properties.

After reaching to this place, click on Change Button --> It will give you warning,

--> Please make sure you have stopped your SAP Application.

Once you press “Yes” Button. You will find below screen where you can see that “ume.superadmin.Activated” field is deactivated means False.

Double click on “ume.superadmin.Activated” and replace Custom Value with “TRUE”

Also double click “ume.superadmin.password” and replace Custom Value with your desired password.

>> Start SAP Application.

>> Log on to NWA (with user name SAP* and password you created) and change the password for ADMINISTRATOR user.

--> Point to be Noted :

If you will try to log on with ADMINISTRATOR immediately after changing password, it will not allow until you deactivate the super admin parameter.

--> Stop SAP Application.

--> Revert back the changes as you have done before.

--> Start SAP Application and try login with ADMINISTRATOR user with your created password

T-Code RSPCM is not working

Problem:

This is a very Common problem from BW team that they are unable to run transaction Code RSPCM in BW system.

Reason:

This problem start when system start SAP_CCMS_MONI_BATCH_DB job to gather the information from Process Chain and request for CCMS Monitoring. The purpose of this job is to check and evaluate the all request and Process chain where the status has been changed since last run of the job.

Immediate Work Around:

Cancel the job SAP_CCMS_MONI_BATCH_DB.

Permanent solution:

1. The first and most important step to improve performance is to create an index on table EDIDC including the fields MANDT, CREDAT and MESTYP.
2. The ALE tables (EDIDC, EDI40 etc) should be reorganized in your BW and also in the connected source systems to improve the performance of the job.
3. Perform a request archiving to reorganize all the maintenance tables for the Infopackage & DTP requests such as RSMONMESS and RSBMONMESS. This can be done with the help of the archiving object BWREQARCH, documentation on this is available in the link below:

Recommended link:

http://wiki.sdn.sap.com/wiki/display/BI/A+Performance+Issue+With+Transaction+RSPCM

Assumptions

Target System and Source System have

OS : Windows

DB : Oracle

SAP : AS ABAP

Hardware Migration of SAP Server

Prerequisites

Install Java on C:\ Drive

Right Click My Computer --> Properties --> Advanced --> Environment Variables --> System Variables

2. Set SAPTRANSHOST

in c:\Windows\system32\drivers\etc\hosts

3. Install Oracle on the Same Drive as in the source system.

4. Patch Oracle.

5. Copy Extracted Export

6. Run SAP Installation master (SAP ERP -->Software life Cycle Options --> System Copy  -->Target System Installation).

7. Copy the Database Backup

8. Restore the BACKUP (EITHER Manually or from BRTools)

Login with SIDADM

BRtool Command from command prompt brrestore –b Filename –m full

9. Copy the backup file in /oracle/SID/Sapbackup.

Copy the source system control file,Orig Log & Mirror Log file.

NOTE: Control File is mirrored on several locations please copy the control file to all locations.

10. Start Database

Login with SIDADM --> cmd --> sqlplus --> / as sysdba --> startup

After successfull startup

11. Recover database

SQL>recover database;

For Recovery Offline Redo logs must be copied to oraarch folder

12. Copy New Kernel

Copy new kernel from Source System to Target System

13. Check Schema & OPS Users

SQL>alter database open;

SQL> Select username,account_status from dba_users;

14. Set OPS Users with Script

Run --> sqlplus /nolog @oradbusr.sql SCHEMAOWNER NT COMPUTER|DOMAIN SAP_SID

sqlplus /nolog @oradbusr.sql SAPPRD NT ASCEN1 SAP_PRD; 

Unlock ifuser is Locked

Run --> ALTER USER username ACCOUNT UNLOCK;

15. Set environment variables

Dbs_ora_schema = Schema Name

16. Start  Application Server

17. Add SAP License

18. Maintain Profile Parameters.

Copy Trans Folder for transport requests

Switch online redo log to offline redo log.

Alter system switch logfile;

Copy the Recent control File;

Recover databse;

Hello,

I work on SAP Product Support. There are several incidents opened by customers related to transport from different system releases. Basically they transport notes or objects, and after that, several inconsistencies start occurring (especially dumps of type SYNTAX_ERROR). My goal with this post is to show how dangerous such transports are, the incompatibilities might be unrecoverable.

SAP objects may NOT be transported between different releases. Even though it is technically possible, it is not supported by SAP. Data loss and severe inconsistencies may happen if you transport SAP objects between different releases, between systems with same release but different support package level, or between systems with different add-on versions etc. Below there are some example of inconsistencies, which mighr result in synatx errors:

1. A table in an old release could have less fields than in the newer release and, then, such a transport might delete data.
2. The code calls a function module and, in a different released, a new mandatory parameter has been added.

Usually there are three options to fix the inconsistencies:

1. Restore the system before you have done the transport.
2. Transport all object of the transport requst from a system with same support package level and notes.
3. Using the version management to replace the object that were modified by the transport request.

So be carefull when transaporting such requests, especially for basis control objects into the production system. Some objects are used by all applications (for instance Function modules DD_NTAB*). If such objects get inconsistenty, the whole system will most likely be inconsistent as well. In this cases, the only solution is a restoring from a backup.

Additional information can be found on the following notes:
SAP Note 556734 - FAQ Transport: Setup and further information
SAP Note 1090842 - Composite note: Transport across several releases

Best regards,

Maurício Grisa.

SAP NetWeaver Scheduler for Java, part of  the SAP NetWeaver Application Server, Java  EE 5 Edition, is a low-level scheduler that can  be used to schedule Java applications and is  part of the standard Java application server  installation.  With this new capability,  customers can develop applications that  automate business processes running on the  Java Server and schedule tasks to manage  activities in SAP NetWeaver components  running on the Java stack.

View Document

When SUM GUI comes up enter the Local host and Port:

Create Password for the Administrator Role.

Password for DDIC OS and DB is specified in the extraction phase.

Provide the profiles for the Central Instance.

Implement the missimg Notes which are important for the tool.

In the configuration phase enter all the required information for configuring the preocess.

Tool Configuration during Configuration phase.

Parameters for procedure.

Select the Support Packages level you want to include.

Include change request.

Modification adjustment. provide your SPDD and SPAU request.

Provide ABAP shadow Instance  and ABAP shadow DB user password.

SUM ask if  we want to use the profiles from <SAVE> subdirectory.

Lockec SAP objects have been found.If orders are not  release, you will not be able to adjust these objects.

Asks to lock the development environment.

Preperation of Downtime during Prepossesing.

Before Downtime SUM asks for Backup Request.

In Execution phase Backup Request  makes a full backup of your database.

Dring  Postprocessing  if no SPAU request is imported it will promt you a message with,

All SPAU activities can be performed without  the registration key for a period of 14 days.

In Summary phase Feedback form is provided in interrest to improving  its tool.

While installing an ADD-ON or performing a SP Update, one often comes across the situation when:-

1.       1. One of more prerequisites haven’t been met properly

2.       2. There is equivalence level mismatch between source and target SP levels

Due to either of the above situations, you may come across –

ERROR: OCS package does not match the current software component vector

Error Encountered during Phase: SUM PREP_EXTENSION/ADDON_QCALC, PREP_EXTENSION/EHP_INCLUSION

SOLUTION:

For Case 1: Ensure that all the prerequisites are met and then repeat the phase.

For Case 2:  In case of a equivalence level mismatch between source and target SP levels, kindly cross check

the valid equivalence levels are met.  For more details, kindly refer

http://scn.sap.com/docs/DOC-49207

However, despite ensuring that equivalence level are fine, the issue persists.

In such cases, one needs to include the ACP (Attribute Change Package) for the component

into the underlying system (or generated stack xml file).

Despite the ACP file being included in STACK XML file, this error might still popup.

The reason for this is: The concerned ACP File is deleted (status - ‘D’) from ‘EPS/in’ directory.

SOLUTION:

     a.       Download the ACP file (.SAR) from SAP SMP and manually add it to EPS/in

     b.       Go to SPAM/SAINT --> Utilities --> Reload Package Attribute

     c.       Continue with the process.

While applying support packages using SPAM/SAINT it hangs with the following error in SLOG:

Kindly move or rename the file <package>.SID from \\usr\sap\trans\tmp directory

and then repeat the phase in SPAM/SAINT. For more information, please refer the SAP note

12746:  WARN <file> is already in use (), I'm waiting 5 sec

What are transport Requests?

Transport Request is a  10 character alphanumeric code having the syntax <SID>KXXXXXX where the SID is the System ID in which the transport request was created.  Transport request contains a list of objects that can me moved between systems. Transport Requests is a way in which you can record changes and move them across systems.

Types of transport Requests:

Workbench Requests:

Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients.

Customizing requests:

Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).

Merging Transport Requests:

Consider there are two workbench requests as shown.

Select the transport request to which the other request is to be merged and press ctrl + F12.

In the below screen, mention the transport request which is to be merged.

Click the Green Tick or Press Enter,

Both the transport requests are merged to a single Transport Request,

If you have issues, Kindly raise a Message(Ticket) in BC-CTS Component.