PI service users locked

PI service users comes default with the installation and exists along side the password within the client of Integration server and exchange profile.
They are utilized in the PI environment for dialog free communication between central components of Netweaver usage type PI and also between app servers and PI

Below are the roles assigned to them

Service User	Description	Assigned Role
PILSADMIN	User for the Change Management Server	SAP_XI_CMS_SERV_USER
PIREPUSER	User for the Enterprise Services Repository	SAP_XI_IR_SERV_USER_MAIN
PIDIRUSER	User for the Integration Directory	SAP_XI_ID_SERV_USER_MAIN
PILDUSER	User for the System Landscape Directory (SLD)	SAP_BC_AI_LANDSCAPE_DB_RFC
PIAPPLUSER	User for sender applications	SAP_XI_APPL_SERV_USER
PIRWBUSER	User for the Runtime Workbench	SAP_XI_RWB_SERV_USER_MAIN
PIAFUSER	User for the Advanced Adapter Engine	SAP_XI_AF_SERV_USER_MAIN
PIISUSER	User for the Integration Server	SAP_XI_IS_SERV_USER_MAIN
PIPPUSER	User for principal propagation	SAP_XI_APPL_SERV_USER

These users will be maintained in different connections and transactions. Inorder to change the passwords, we need to change them in all those connections and transactions.

There is a typical procedure to vary the passwords of those users provided by SAP.


We need to follow the procedure from below notes for changing the passwords supported your PI version.

999962 - PI 7.10 and higher: Change passwords of PI service users

2474153 - How to change passwords of PI service users in Java Only PI system

936093 - PI: Change to passwords of PI service users

721548 - XI 3.0: Changing the passwords of the XI service users

Client deletion procedure

Client is a business unit in SAP system. we can see three standard clients which usually comes with the installation of SAP system. 000,001 and 066

066 is early watch client and now a days it's of no use as solman is mandatory.
So in such cases, we may have to delete the clients 066 and 001.
Below is the procedure for deleting client.

Client deletion through scc5

First log within the client you'd wish to delete with username as SAP* and password as pass if you're logging into that client for the primary time.

Use transaction code SCC5 and select the check box which says Delete entry from T000 and click on start immediately... you will get the prompt if you can continue, click continue and wait till it deletes the client.

 Once the client is deleted, login to 000 Client and issue the transaction code SCC4 to see if the deleted
client is listed within the list or not... If it's unlisted then you've got successfully deleted a client.

Client deletion through R3trans

1)logon to system as SAP Admin

2)goto /user/sap/trans/bin dir

3)use standard editor to create a control file
 with ctl ext(eg. delcli.ctl) with following text
 clientremove
 client=xxx
 select*

4) run the commnd on command field
 r3trans -w delcli.log -u1delcli.ctl

Notes regarding client deletion

Note 70643 - CC-TOPIC: Client Deletion (SCC5)

Note 35952 - Client deleted, space still filled in database

Reprocessing and Deletion of IDOC

IDOCs are Intermediate Documents which are used for the communication between two SAP systems which can be having the encoded data which SAP system only can read.

IDOCs will be getting transferred between SAP systems and will sometime fails due to the lack of resources or due to queue stuck etc.

In such situations, we'd like to reprocess the idocs. Below are the steps which shows us to re-process/flag the IDOCs in SAP system.

How to reprocess an Idoc:

1. Go to transaction BD87

2. Enter Idoc number, and make sure the dates are correct

3. Click the Execute button or press F8

4. To reprocess, select the Idoc status within the "IDOC in inbound processing" tree.

5. Click the Process button

6. the subsequent screen will give the status of the IDOC and wheter it processed sucessfully

How to flag an Idoc to be deleted:

1. Go to transaction BD87

2. Enter Idoc number, and make sure the dates are correct

3. Click the Execute button or press F8

4. To delete, select the Idoc status within the tree and click on EDIT -> RESTRICT AND PROCESS

5. Click the Execute button

6. Un-check the Bkgd Processing checkbox.

7. Click the Execute button

8. Click the Delete Flag button.

Administration of IDoc Communication

IDoc communication is predicated on transactional Remote call (tRFC).

You can optimize the performance of ALE processing by using the subsequent settings and procedures.

Suppressing Background Processing
If tRFC errors occurs in the standard SAP system, , a background job is generated to re-establish the connection. In certain circumstances this might end in an outsized number of background jobs being started that completely block backgrounding .

Note:
Use program RSARFCEX to restart tRFC to cancel a background job if tRFC errors occur .

Select a connection to change in ALE Customizing (transaction SALE), 

Communication

Create RFC Connections (SM59)

Choose Destination ® tRFC Options and select the option Suppress Background Job at Comm. Error.

Setting Dispatch Status to OK
When an IDoc is passed to the communication layer, it's assigned a globally unique transaction identifier (TID). If the IDoc has been successfully dispatched, this information isn't automatically passed to the ALE communication layer. So that ALE processing sets the IDoc status to Dispatch OK, you ought to compare the TID numbers within the communication layer and therefore the ALE layer.

The SAP program RBDMOIND checks that the IDocs passed to the tRFC have already been sent to the receiving SAP system. If they need been sent, the IDoc status is modified to "12" - Dispatch OK

Note:
To set the IDoc dispatch status, run the program RBDOIND after the IDocs are passed to the communication layer.

Checking the tRFC Status

Use
Transactional RFC calls which transfer IDocs use the function module IDOC_INBOUND_ASYNCHRONOUS at reception (before release 4.0: INBOUND_IDOC_PROCESS).

If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.

Activities
To check the status of the tRFC calls, select Tools -> IDoc Interface/ALE -> Administration -> Monitoring -> Troubleshooting -> RFC Queue (SM58) and setout any additional selection criteria.

The program RSARFCEX restarts unsuccessful tRFC calls.

Note:
You cannot choose the choice is being executed in backgrounding .

PI configuration notes

SAP PI/PO is the Module which integrates all the SAP modules where it acts as a mediator or for interpretation between different SAP systems and also between SAP and Non SAP systems.

Generally PI/PO systems will not be refreshed and it is very complicated.

If we get in to a situation to refresh PI/PO system, below info will be helpful.

Here are couple of notes for PI post configuration

PI SLD Self Registration - SAP Note 1439558

7.10 SP5 Patch 8, 7.11 SP1 Patch 0, 7.30 SP0 Patch 0

PI Demo Client - SAP Note 1304208

7.11 SP0 Patch 0, 7.30 SP0 Patch 0

PI Full Qualified Host Name - SAP Note 1320707

7.11 SP1 Patch 0, 7.30 SP0 Patch 0

PI Adapter Engine in Java Proxy Runtime Mode - SAP Note 1346933

7.11 SP4 Patch 0, 7.30 SP0 Patch 0

PI Robustness Configuration - SAP Note 1400543

7.30 SP0 Patch 0

PI Single Sign-On Configuration - SAP Note 1473556

7.30 SP1 Patch 0

PI Self Test for SAP NetWeaver - SAP Note 1286149

PI Wizards Overview - SAP Note 1286428

Performing a PI system copy SAP Note 1299373

Configuration Wizard: SAP Note 1400543

Parameter description SAP Note 1375656

Correcting the CALL_FUNCTION_SECSTORE_ERROR short dump

This information is for troubleshooting the short dump CALL_FUNCTION_SECSTORE_ERROR.

The system cannot read the password of the required RFC connection from the secure storage, or the password doesn't exist within the secure storage.

Use transaction SECSTORE to see the status of the secure storage.

If this seems correct, select the application "RFC Destinations" and search for the destination /RFC/.

The destination entry should have a green indicator.
If it doesn't , the message text column displays information about the error.

You can use the question mark within the end column to get an in depth description of the error and notes fix it.

If the destination /RFC/ is not listed in the secure storage, the password is lost.

If this happens, you'll use transaction SM59 "Configuration of RFC Connections" to reenter that password.

Once we save the destination, the status of the password (PW-Status) should be set to "saved" and a corresponding entry should be available in transaction "secstore".

PI POST INSTALLATION STEPS

After a PI installation you have to configure your system. 
This is a mandatory post installation step called "Running the Configuration Wizard".
Before running the Wizard, it is recommended to update the following Java Software Components (SCs) to the highest available Support Package and Patch Level:
Life Cycle Management:

LM CONFIGURATION (LMCFG)
LM CONFIGURATION WIZARD (LMCTC)

Process Integration:
    MESSAGING SYSTEM SERVICE (MESSAGING)
    XI ADAPTER FRAMEWORK (SAPXIAF)
    XI TOOLS (SAPXITOOL)
    PI GUI (SAPXIGUI, only 7.11)
    PI GUILIB (SAPXIGUILIB, since 7.30)
    ESR (SAPXIESR)

The ABAP stack must have the same Support Package level as Java.
This Wizard Template is available since Release 7.10.

A prerequisite to run the Wizard is that the system was installed with the PI Installer (SAPInst). All PI services must be up and running.
For further information about the Configuration Wizard, see the following collective notes:

    SAP note 0923359 - Collective Note: Configuration Wizard (Release 7.0x)
    SAP note 1107808 - Collective Note: Configuration Wizard (Release 7.1x)
    SAP note 1362909 - Collective Note: Configuration Wizard (Release 7.3x)
    SAP note 1286428 - Configuration Wizard: PI Wizard Templates overview (Releases 7.1 and higher).

Solution
To run the CTC Wizard, start the SAP NetWeaver Administrator and navigate to "Configuration Management --> Scenarios --> Configuration Wizard". Depending on your release do the following:

Releases 7.10 / 7.11:
In the drop down list, please choose "Initial Configuration" or "All Configuration tasks -> NetWeaver initial setup".

Releases 7.30 / 7.31 and higher:
Click on link "Functional Unit Configuration UI". Select Functional Unit "SAP NetWeaver Process Integration (PI)". All required Functional Units are selected automatically. Press button "Enable automatically" to start the CTC Wizard.

Oracle shutdown types

During a normal shutdown, Oracle closes all sessions . closes the database, un-mounts the data files then shut down the instance in two steps, first issuing a "free" the SGA RAM heap and eventually , terminating the background processes.

Oracle has three shutdown modes:

Normal (default) - waits for in-flight work to finish . This could take houes.

Immediate - terminates all sessions and rollbacks all uncommitted transactions. 

Abort - it aborts all sessions, leaving current DMLs for rollback and de-allocates the SGA terminating all the background processes. Note that a shutdown abort isn't dangerous. The "abort"  means Oracle will terminate all active work, which is what most of the people want during a shutdown!

The "normal" and "immediate" modes can take an extended time in you've got in-flight transactions, and lots of Oracle DBA's ensure a swift clean shutdown this manner , aborting the sessions, re-starting to allow warmstart rollback of the aborted transactions, and a shutdown immediate to shut cleanly:

SQL> shutdown abort
SQL> startup
SQL> shutdown immediate

Normal Shutdown:
A normal shutdown of an Oracle database is really rarely used. This is because the normal shutdown waits for everybody to finish their work then logoff in an orderly fashion. When a normal shutdown occurs, the database is closed in a normal manner, and all changes made within the database are flushed to the database datafiles . This is known as a “clean shutdown.”

It will simply wait forever until we  kill those sessions manually. Because of this, we frequently recommend the shutdown immediate or shutdown abort commands, which we'll discuss within the next sections. Below is the syntax for the utilization of the normal shutdown command.

SQL> shutdown

When shutdown is executed , Oracle flushes all the changes in memory out to the database datafiles . This makes database startup quicker because the database is during a consistent state.

 A clean shutdown is one that's prepared to return copy at once . A dirty shutdown is one that lands on its back; it can't come up without first recovering itself.

Shutdown Immediate:
Perhaps the simplest way to initially shutdown the database is that the shutdown immediate command. This command will prevent any new logins, then rollback any uncommitted transactions, then bring down the database. In the process of bringing down the database, Oracle will flush all the changes in memory bent the database datafiles too, a bit like a daily shutdown does. This makes database startup quicker. Below is the syntax for shutting down a database with the shutdown immediate command:

SQL> shutdown immediate

usually shutdown immediate command will work mostly, but some times when it can hang and fail to shutdown the database. In these cases, the shutdown abort command is named for.

Shutdown Abort:
The shutdown abort command is just about a guaranteed way to get your database to shutdown. It’s a “hard crash” of the database, and this will end in a extended time to start out the database copy .  you aren't really hurting the database using the shutdown abort command, and through your DBA years you'll find quite a couple of occasions to use the shutdown abort command.

A shutdown abort are often your first shutdown method of choice, since there could also be times once you must force the database down. below is the syntax for using the shutdown abort command:

SQL> shutdown  abort

CTS+ Confguration for Portal Transports

CTS+ Confguration for Portal Transports

Use:

Enhanced Change and Transport System (CTS+)  helps us to transport Java objects and SAP-related non-ABAP applications in the system landscape, alongside ABAP objects. we can also administer non-ABAP systems during a CTS transport domain in SAP NetWeaver Application Server ABAP.

Transportable Objects:

You can use CTS+ to move the subsequent additional objects:

•Java-based and J2EE-based objects:

 Software Component Archives (SCAs)
 Enterprise Application Archives (EARs)
 Software Deployment Archives (SDAs)

•SAP NetWeaver usage type SAP NetWeaver Portal (EP) objects:

 Enterprise Portal Archives (EPAs)
 Enterprise Portal Applications (PARs)
 Knowledge Management objects (KM Content and KM Configurations)

• SAP NetWeaver usage type PI (Process Integration) Non-ABAP objects:

 Integration Builder objects (TPZs)

Objects related to SLD content  (products, software components, technical systems, and business systems)

Configuration – Concept:

The following three components must be configured before you'll use the improved Change and Transport System.

• CTS Deploy Web service (SAP NetWeaver AS Java)

This is a Java Web service liable for communicating with the deployment tools in non-ABAP systems. The transport control program tp communicates with the 

CTS Deploy Web service when deploying the non-ABAP objects.

• CTS Deploy proxy (SAP NetWeaver AS ABAP)

A CTS Deploy proxy is required on the ABAP side to enable the transport control program tp on SAP NetWeaver AS ABAP to communicate with the CTS Deploy Web service on SAP NetWeaver AS Java.

• Transport Organizer Web UI (SAP NetWeaver AS ABAP)

This is an Web Dynpro ABAP application during which you create and edit transport requests for non-ABAP systems.

Configuring the CTS Deploy Web Service:

Use:The CTS Deploy Web service connects the ABAP transport tools to the deployment tools within the non-ABAP applications.

Prerequisites:

This deployment Web service has been a part of SAP NetWeaver 7.0 since Support Package Stack 12.

Information about using the CTS Deploy Web service in another SAP NetWeaver system is out there in SAP Note 1003674.

Checking the CTS Deploy Web Service:

1.  Open the CTS server in SAP NetWeaver Application Server Java,.
2. In your Web browser, enter the following URL:
3. Open Web Service Navigator.

The DeployProxy Web service is within the list of deployment Web services.

Note: Deploy the patch DI CHANGE MGMT SERVER 7.00 as per the SAP Note no: 1076189 if you couldn’t find the service

Configuring the HTTP Connection:

You should be in SAP NetWeaver Application Server ABAP in your CTS system.

1. Call transaction SM59.
2. Create a new HTTP connection called CTSDEPLOY.
3. Choose the Technical Settings tab page.

 a. Enter the name of the target host, the service number (500), and therefore the path prefix /DeployProxy/default?style=document. Confirm by choosing Enter.

 b. If you see any warnings about invalid query strings or missing documentation, ignore them by choosing Enter.

 c. Save your entries.

4. Choose the Logon and Security tab page.

 a. Select Basic Authentication as the logon procedure.

 b. Enter a J2EE user name and password.

 c. Save your entries.

5. to check the new HTTP connection, choose Connection Test.
6. Choose Continue to confirm.

If you've got created the new HTTP connection successfully, the status text within the test results is about to OK.

Setting a Timeout for the Deployment:

Use:Large objects can cause timeouts in deployments. set more time out duration  than the longest expected deployment time.

Procedure:
You should be in SAP NetWeaver Application Server ABAP in your CTS system.

1. Call transaction SM59.
2. select HTTP Connections to External Server ® CTSDEPLOY.
3. Select the Special Options tab page.

The ICM Default Timeout option is chosen because the default under Timeout.

Select a timeout that's above the longest expected deployment. If unsure , select No Timeout to avoid the connection timing out during a deployment.

Configuring the Logical Port for the Web Service:

Use:Logical ports for Web services are Customizing objects.

Prerequisites:

To configure a logical port, you want to enable Customizing changes to be made in client 000. You can cancel these changes once you've got configured the CTS Deploy Web service.

Setting the System Change Option:

You should be in SAP Net Weaver Application Server ABAP in your CTS system.

1. Call transaction SE03.
2. select Administration  -> Set System Change Option and click on Execute.

 The System Change Option screen appears ->
3. Choose Client Setting.

 The Display “Clients” View: Overview screen is displayed.

4. Select the client 001(The client which you're getting to use for CTS+ Transport Requests).

5. Choose Change ® Display.

A panel with the messageCaution: The table is cross-client. appears.

6. Choose Continue to confirm.

7. Make the following changes:

 a. Choose Detail.

 The Display “Clients” View: Detail screen is displayed.

 b. Select Automatic Recording of Changes.

8. Save your entries.


Creating a Logical Port:

You should be in SAP Net Weaver Application Server ABAP in your CTS system.

1. Log on to client 000.

2. User must be aside from DDIC and SAP*.

3. Call transaction LPCONFIG.

 The Display/Create Logical Port screen is displayed.

4. choose the proxy class CO_TFLDEPLOY_PROXY_VI_DOCUMENT from the proxy list.

5. Enter CTSDEPLOY as the logical port.

6. Choose Create.

 The Edit Logical Port screen is displayed.

7. Enter an outline for the logical port and choose the Default Port checkbox.

8. Under General Settings, choose the decision Parameters tab page.

9. Select CTSDEPLOY as the HTTP destination.

10. Save your entries.

 A panel is displayed that prompts you to specify a customizing request.

11. Enter your changes in a change request.

12. Activate the CTS Deploy Web service logical port .


Activating the online Service for Transport Organizer Web UI:

Use:To sign up non-ABAP objects to a transport request, you want to activate the online service CTS_BROWSER.


Prerequisites:

• You have authorization for transaction SICF.

• Ensure to activate all ICF services required to run an ABAP Web Dynpro application.


Note: For more information, see SAP Note 517484.

Procedure:

1. Call transaction SICF. This transaction is a cross-client transaction.

2. Enter SERVICE within the Hierarchy Type field and CTS_BROWSER within the Service Name field.

3. Choose Execute

4. Select the online service (CTS_BROWSER) on the Maintain Services screen.

5. Activate the online service by opening the context menu (secondary mouse button) and selecting Activate Service.

A dialog box for activating IFC services is displayed.

6. Choose Yes (with tree icon).


If you would like to check the online service, open the context menu (secondary mouse button) and choose Test Service.


Starting Transport Organizer Web UI:

Use:You must start Transport Organizer Web UI before you'll begin editing and organizing your transport requests.

Prerequisites:

You have set the parameter NON_ABAP_WBO_CLIENT.


Procedure:

1. go online to the SAP system client with the user and password that you simply want to use to start out Transport Organizer.

2. To start Transport Management System (TMS), call transaction STMS.

3. to try to to this, choose Environment -> Transport Organizer Web UI.

 This starts Transport Organizer Web UI for the client to which you're logged on.

4. within the System panel , choose the system ID of the system that you would like to organize your transport request. This is usually the development system.

5. In other way, you'll use below URL to open Transport Organizer Web UI:

http://:/sap/bc/webdynpro/sap/cts_browser?SYSID=


Customizing for Application Types:

Use:The application type is only a display attribute and doesn't determine the deployment method. Application types are utilized in the CTS_BROWSER Web Dynpro to classify attached objects. You can also add your own application types manually within the table CTS_RQ_APPLID.


Procedure:

1. Call transaction SE16.

 The Data Browser: Initial Screen appears.

2. In the Table Name field, enter CTS_RQ_APPLID.

3. Choose Table Contents or Enter.

 The Data Browser: Table CTS_RQ_APPLID: Selection Screen appears.

4. Click on  Execute button leaving the application field empty.

 The Table CTS_RQ_APPLID screen appears.

5. Click on Create button if the application type doesn’t exist.

 The Insert Table CTS_RQ_APPLID screen appears.

6. Enter the name of the application within the Application field.

 When you choose the F4 help within the Application field, the application name you entered appears within the list box.

7. Enter an outline of your application type within the Description field.

8. Save your entries.


Defining and Configuring Non-ABAP Systems:

Use:When you create a transport landscape in Transport Management System (TMS), you define how you want objects to be transported between systems in the different phases (development, quality assurance, and production) of the software lifecycle.


Prerequisites:

You have configured the CTS Deploy web service.

Creating Non-ABAP Systems:

You are in your TMS domain controller.

1. Call transaction STMS.

2. Choose System Overview.

3. Select SAP System -> Create -> Non-ABAP System.

 The TMS: Configure Non-ABAP System panel is displayed.

4. Create the non-ABAP system with a system ID and an outline .

5. Select the CTS system because the communication system.

6. Make the following settings, depending on whether your system is a source system or a target system (or both):

 o Non-ABAP system as source system

 Under Source System Settings, select the Activate Transport Organizer flag and enter the client where you would like to use Transport Organizer.

 o Non-ABAP system as target system

 Select the Activate Deployment Service flag under Target System Settings, Select the preferred deployment methods filling out the remainder of the fields accordingly.

7. Provide system user and password for your preferred deployment methods.

8. Save your settings and ensure that you simply want to distribute the TMS configuration.

All parameters and their values will automatically be generated bu the system now by default. To display these parameters, select your system within the system overview and choose the Transport Tool tab page.


Configuring Transport Routes:

1. Goto STMS and choose Transport Routes in Overview menu

2. it'll open below window to configure Transport Routes. Change to Edit Mode as below

3. In Menu Option: Configuration -> Standard Configuration -> Select appropriate Configuration option consistent with your landscape requirements.

 Here we have selected Development and Production System.

4. Provide both Development System and Production system SIDs 

5. it'll create Transport Routes in between above two mentioned systems. Save the configuration.

6. In the popup screen click Yes to distribute and Activate the configuration.


Configuring the Destination Service:

Use:You must first use RFC to connect your SAP application system ( before you can attach objects to transport requests directly in the application;such as SAP NetWeaver PI or SAP NetWeaver Portal) to the CTS server. This enables your application to talk with the transport system.


Prerequisites:

• You have change authorization in Visual Administrator.

• you've got a user with the acceptable authorizations in SAP NetWeaver Application Server Java.


Procedure:

1. Open Visual Administrator in SAP Application Server Java.

2. Opt Cluster -> Server -> Services -> Destinations.

3. Create an RFC connection naming it as sap.com/com.sap.tc.di.CTSserver by choosing Create.

4. Under Connection Settings, provide the connection data of the CTS server.

5. Under Logon Data, select the present User (Logon Ticket) option as authentication for the connection to your CTS server. We recommend that you use Single Sign-On (SSO).

If you can't use SSO, select the Configured User option and enter your preferred language, a client, and an appropriate user and password.

Enter the client entered within the parameter NON_ABAP_WBO_CLIENT in TMS.

6. Under Repository Connection and Pool Settings, use the default settings.

7. Save your entries.

If you would like to check the connection, choose Save and Test.


Choosing a Transport Strategy:

Use:You can influence the behavior of the transport system once you create and release transport requests by configuring the strategy parameters. In this manner, we can provide optimum support for your chosen transport process (automatic or manual creation and release of requests).

You only require these parameters for applications that have a close coupling with the CTS system (such as SAP NetWeaver Portal systems and SAP NetWeaver PI systems).

Prerequisites:

You have configured the connection between your application and therefore the CTS server.

Procedure:

1. Call transaction STMS.

2. Choose Overview ® Systems.

3. Select a system.

4. The screen Display TMS Configuration: System appears.

5. Choose the Transport Tool tab page.

6. Switch to change mode.

7. Add the following parameters:


o WBO_GET_REQ_STRATEGY - smart

Once you export an object from an SAP NetWeaver portal system or an SAP NetWeaver PI system, transport request will be automatically created.

The following values are possible:

§ Smart

The system creates a transport request (if not already available) and flags it because the standard request.

§ Tagged

This is configured because the default value within the system. You must have created a transport request already in Transport Organizer Web UI and flagged it because the standard request.


o WBO_REL_REQ_STRATEGY - Manual

Transport request will be automatically released  in an SAP NetWeaver portal system or an SAP NetWeaver PI system.

The following values are possible:

§ Auto

Transport request will be released automatically from the system as soon as an object is added to the request in an SAP NetWeaver portal system or an SAP NetWeaver PI system.

§ Manual

This is configured because the default value within the system. You must release the transport request manually or set the worth of the parameter to Auto.


Create Transport Request using Transport Organizer Web UI

1. Use below URL to access Transport Organizer:

'Protocol'://'server':'Web AS Port'/sap/bc/webdynpro/sap/cts_browser?SYSID='SID of Development System as Configured in TMS'

E.g.: http://pwdf4156.wdf.sap.corp:8002/sap/bc/webdynpro/sap/cts_browser?SYSID=CAI

2. Transport Organizer will look like below. Click on Create Request to create new Request.

3. Mention Short Description and Owner of Request. Project field can be left blank.

4. Click on Attach Object to connect non ABAP Object to move Request.

5. In crop up window, select Client and Browse for the file and click on on OK

o Client: look for the file on your desktop and ensure by choosing OK.

o Server: Search the directory defined within the parameter NON_ABAP_WBO_INBOX for the acceptable source system. In the directory, select the file and confirm by choosing OK.

6. you'll check the attached Non-ABAP Object in Object List Tab as below:

7. Now click on Release to Release the Request to move Queue.

Document References:

1. https://websmp108.sap-ag.de/changecontrol

2.http://help.sap.com/saphelp_nw70/helpdata/EN/45/ec25370fdc3481e10000000a1553f6/frameset.htm

ASSERTION_FAILED dump and solution in SAP APO/BW

Below answer is for fixing ASSERTION_FAILED dump  in APO and BW systems.

Procedure:
Call transaction SE16 (Table Browser) and the 'RSTRANRULE' Table with the following choice parameters:

GROUPID   =  'space'
GROUPTYPE =  'space' or 'S'
REF_RULE  <> 'space'
If you see  inconsistent entries in the RSTRANRULE Table like:
TRANID        *
OBJVERS      *
RULEID         *
SEQNR          *
GROUPID      00
GROUPTYPE  space  or  GROUPTYPE    'S'
RULETYPE      space
REF RULE       *

Remove these entries from the table.

Activate the affected Changes.

Check if dump nevertheless occurs. 

Owners and authorizations for BR*Tools

The following setup is essentail to call the BR*Tools with out any error, especially while using transaction DB13 or DBACOCKPIT:

(1) ora and adm groups on DB server have a search path on /sapmnt//exe.

(All br* are contained in this directory.)

ora belongs to the dba group,

adm belongs to the sapsys group,


(2) adm group on the DB server has the rhosts entry: "+ adm".


(3) The ops$adm Oracle user has to be created within the DB and should have the sapdba role (not DBA!) (refer SNote 134592 for more information about the role).


(4) brarchive, brbackup, and brconnect belongs to ora and should have authorization 4775:

-rwsrwxr-x ora sapsys ...


Reason:

Both the operating system &#40;OS&#41; user ora and the OS user adm (for example, from SAP R/3, transactions DB13 or DBACOCKPIT) must be able to call these tools. These tools require access authorization to the database directories and files also on the log directories (saparch,

sapbackup, sapcheck, and sapreorg) of the BR*Tools. To ensure that they will be executed by both ora and by adm, they need to belong to the user ora, and therefore the s-bit must be set.

(5) brrestore, brrecover, brspace, and brtools belongs to adm and should have authorization 755:

-rwxr-xr-x adm sapsys ...

Reason:

These tools could also be used only by OS user ora, but not by adm. This ensures that the user adm doesn't have write authorization for the log directories and thus cannot create any logs. For this, no s-bit is about , and it's not necessary to define an owner aside from the standard owner adm.

If the tools were started using adm, they might terminate immediately after the beginning thanks to the missing log authorization. However, the user ora can start the programs despite this and also has the specified authorization for the log directories.