SAP NW Newbie

Here are some important Oracle parameters and information in the context of use with SAP applications. BACKGROUND_DUMP_DEST Path for alert log and background trace files COMPATIBLE Defines the Oracle version whose features can be used to the greatest extent As a rule, it must not be reset to an earlier release (see Note SAP 598470). A value with three parts (such as 10.2.0) rather than five parts (such as 10.2.0.2.0) is recommended to avoid changing the parameter as part of a patch set installation. If an ORA-00201 error occurs when you try to convert the value with five parts 10.2.0.2.0 to 10.2.0, you can leave the value 10.2.0.2.0 (independent of the patch set used). CONTROL_FILES Path and name of the control files that are used CONTROL_FILE_RECORD_KEEP_TIME Defines how many days historic data is retained in the control files Historic data is required by RMAN, for example. May cause control files to increase in size (see Note 904490) CORE_DUMP_DEST Path ...

The configuration of SAP Fiori is a painstaking process. On the front end system (where the gateway is used) you have to perform several tasks to activate Odata capabilities. You can automate most of those tasks using transaction STC01. With SAP NetWeaver 7.4 SPS 10, SAP has added tasks to automate OData and HTTP (ICF) services . Following are the task available on STC01 to perform Fronend setup: SAP_FIORI_LAUNCHPAD_INIT_SETUP - To activate launchpad OData and HTTP services on an SAP Gateway system (frontend) SAP_SAP2GATEWAY_TRUSTED_CONFIG - To create a trusted connection from an SAP system to SAP Gateway. SAP_GATEWAY_ADD_SYSTEM -  To connect an SAP system (backend) to an SAP Gateway system (frontend). SAP_GATEWAY_ADD_SYSTEM_ALIAS - To create a system alias for an existing remote function call destination (to backend). SAP_GATEWAY_ACTIVATE_ODATA_SERV - To activate multiple OData services. OData services are required to initially set up the SAP Fiori Launchpad and the ...

HANA Studio is an important administrative and IDE tool to manage SAP HANA. Where to get the HANA Studio Software? You can download  HANA  studio from http://support.sap.com/swdc (requires S-user with download authorization) Select Support Packages & Patches and Browse Download Catalog Now traverse through the following links: SAP NetWeaver and complementary products SAP HANA SAP HANA PLATFORM EDITION SAP HANA PLATFORM EDIT. 1.0 Entry by Component HANA Studio SAP HANA STUDIO 2 Depending on your PC's operating system, choose one of the four links. Download one of the SAR files (the revision should either match or exceed the HANA Database Server revision). To extract the SAR file, you need SAPCAR executable. Extract HANA Studio SAR File Go to the folder where you downloaded  the HANA studio SAR file and SAPCAR.EXE, and run the following command SAPCAR.EXE -xvf IMC_STUDIO2_<Revision>_<Patch>_<Material...

Understanding SAP ERP Architecture can be a daunting task for a beginner. An easy way out is to begin from the beginning and see how the architecture evolved. We will start with what problem SAP started off to solve how they ended up with SAP S/4 HANA  in 11 (biggish) steps: Computers taking over jobs.   SAP could have been an IBM company  Welcome to the world of Real-time Systems  Client and Server Revolution  Functional Modules, Industry Solutions and Technology Layer   SAP R/3 up to 4.6c, EnjoySAP and what happened to "SAP R/3 4.6D"   SAP R/3 Enterprise Enterprise Extensions   Integrating the business, MySAP ERP 2003 and SAP NetWeaver   ESoA, MySAP ERP 2004 and NetWeaver 2004   NetWeaver suites up and ECC is a switchboard   The next big thing in the evolution Computerization of Business Processes With the advent of computing technology, companies looked for opportunities to automate various business tasks, ins...

This is a starter guide for Basis Administrators to understand the architecture and various nuances of SAP PI Administration. This guide will be updated time to time, so I recommend you to bookmark and keep revisiting this page as you see fit. Enterprises run different software solutions to support their business processes. Not all of them are built and supported by SAP. These solutions are integrated one-to-one using various middleware solutions or customized programs or scripts. When there is a change in one system or business process, multiple point-to-point interfaces are affected and are often expensive to change. Although these point-to-point interfaces are using different technologies, there are recurring themes. Although there are recurring themes, code is not reusable because they were implemented using different technologies. In 2003, SAP introduced NetWeaver, which helped them focus on providing a platform for integrating various aspects of business , in...

The area in which you enter an SAP transaction code is called Command-field or "OK Code". The shortcut to select this command field is CTRL+/ Here are some entry options for OK codes: /n - The /n option terminates the current transaction /n<TXNCODE> - The /n option terminates the current transaction and TXNCODE followed by /n calls transaction TXNCODE /nend - This option terminates all the sessions from the current PC and logs the user off. /nex - This option terminates all the sessions from the current PC and logs the user off immediately without issuing warnings /o - The option /o lists existing sessions and allows deletion or opening of a new session. /o<TXNCODE> - The option /o followed by a transaction code TXNCODE opens a new session and starts transaction TXNCODE in the new session. If the maximum number of sessions per user are breached, an error is displayed. /i - The option /i terminates the current session /i1 - The option /i1 terminate...

The 7.4x kernels allow you to trace the data that is being exchanged with SAP GUI for troubleshooting purposes. The tracing of SAP GUI data can be enabled via the dynamic  profile parameter rdisp/sapgui_data_trace . The following values are supported: 0: do not trace any SAP GUI data. 1: trace SAP GUI data in case of errors only. 2: trace received SAP GUI data in processes with trace level set to 2 or 3. 3: trace sent and received SAP GUI data in processes with trace level set to 2 or 3. Also trace the received data before SNC decryption and decompression in the work process.

In a JAVA-only PI system (AEX or PO), the exchange profile URL http://<server>:<port>/exchangeProfile will be a blank screen as it is obsolete. If you want to add/modify an exchange profile parameter, you have to do it from NWA using the following steps: Go to http://<server>:<port>/nwa/sys-config (http://<server>:<port>/nwa > Configuration > Infrastructure > Java System Properties) Choose Services tab Search for "XPI Service: AII Config Service" and select it In Properties tab, search for the property to be changed or added. If the property exists, select the property, click on Modify, perform the changes and click on Save. If the property does not exist, click on Add, inform the value and click on Save.

MDM Configuration Assistant is a standalone tool to help check typos, sub-optimal parameter values, duplicate parameters, missing mandatory parameters, relevance of the parameters within the sections, dependencies within the parameters, inconsistent and incorrect settings. MDM Configuration Assistant tool provides the following configuration options: Assistance with configuring MDM correctly so that you can connect your Master Data Server (MDS) to a DB server Assistance with validating and managing the configuration settings of the INI files (mds.ini, mdis.ini and mdss.ini) of your MDM server Prerequisites To run  Configuration Validation to Enable MDS Connection to DBMS option, MDM should be at MDM 7.1 SP03 or higher. Start MDM at least once so that the INI files are initialized. To run  Configuration Validation and Management of MDM Configuration Files option, MDM should be at MDM 7.1 SP06 or higher. JVM 6.1 or higher Downloading and Running the...

While SAP upgrade is in the preparation phases, SUM tool offers an option to reset the work done by SUM tool from the menu option: Update > Reset update This is the recommended method of resetting the upgrade. If the upgrade was not properly reset from a previous attempt. The subsequent run can fail at the step PREP_INIT/VALCHK_INI with error similar to the following: SAPup broke during phase VALCHK_INI in module PREP_INIT / Initialization Error Message: SAP_ABA is in an undefined state, that is not safe to be upgraded, reason Upgrade wasn't completed - Call the SAP Support This example shows SAP_ABA component, it could be any component(s) that may be in undefined state. If you encounter this problem, you have the following two choices: 1. Reset from command prompt by executing SAPup with reset prepare option cd <upgrade directory>/abap/bin ./SAPup reset prepare 2. Run the report  RSUPGRES as DDIC user from 000 client The repor...

When you generate a stack XML, the required software is automatically approved for download. However, when you want to download a single patch (to fix a bug for example), you would add the software to download basket, but it would be sitting there waiting for approval. You can manually approve the software using the function module /TMWFLOW/MO_UI_BASKET_AUTHORIZ Log in to Solution Manager system. Call transaction SE37 and execute the function module  /TMWFLOW/MO_UI_BASKET_AUTHORIZ Set I_OSS_RFC = SAP-OSS and execute Select the software file and click on Confirm download Now the software will be ready to download in the Download Basket. You can also use the report /TMWFLOW/RMOBASKETAPPROVAL to approve the software.

SAP recommends using SUM tool for updates or upgrades , and at the same time they support SPAM and SAINT tools for updating ABAP stack. Using SPAM/SAINT is faster (and at the same time time tested method we all are comfortable with). As long as SAP continues supporting SPAM/SAINT, Basis admins are more likely to use it. For J2EE stack, SAP has discontinued support of updating using using JSPM. Therefore patching J2EE can only be done using SUM. In case of Dual Stack, because JSPM is not supported, J2EE can only be updated using SUM. You would still prefer to update the ABAP part using SPAM/SAINT. But you cannot patch ABAP and then start up SUM with default options to patch J2EE. It will error out on the ABAP side of SUM. To patch J2EE on Dual Stack system, you can start SUM using the following option: STARTUP javaonly With this option, SUM will not patch ABAP stack and will only patch the J2EE patch. The advantage? One can patch ABAP using SPAM/SAINT and then patch J2E...

This post discusses various known issues and solutions to deal with the following error when running Software Upgrade Manager (SUM): Could not detect AS Java release. Return code condition success evaluated to false for process /usr/sap/<SID>/<INST>/j2ee/cluster/bootstrap/scripts/version.sh for action ACTION_VERSION. Using DEFAULT configuration fro web methods protection Edit DEFAULT.PLF file from /usr/sap/(SID)/SYS/profile and set configuration:  service/protectedwebmethods = DEFAULT Restart all the SAP instances (including sapstartsrv) and retry the failed step. Replace the scripts Download the latest SERVERCORE.SCA patch file from service market place. Extract sap.com~bootstrap.sda.sda from SERVERCORE.SCA/DEPLOYARCHIVES with an archiver. Extract the following files from sap.com~bootstrap.sda.sda/script launcher.bat launcher.csh launcher.sh version.bat version.csh version.sh version.jstart Go to /usr/sap/[SID]/[INSTANCE]/j2ee/j2ee...

When you first launch SUM tool, it requests you to set an admin password for the tool itself. If for some reason you forgot the password (feeding incorrect password will throw the error: " The password you have entered for role Administrator is wrong "), here is how you can change it Stop the SUM tool Go to the folder <SUM Directory>/SUM/sdt/data Rename or move the files .sdt_storage and .sdt_keystore Start the SUM tool again and it will prompt you to set the new passwords Changing passwords will not reset the upgrade phases, you can continue from the point where SUM stopped.

As soon as you enter the credentials on ESR/Integration Repository/Integration Directory/Integration Builder, if you see the  error " com.sap.aii.ib.core.ejbutil.rb_all.SERVER_MS_NOT_AVAILABLE ", it means that the message server could not connect to  the P4 port of the PI system Call the following URL and check if P4 port is listed: http://<msg_server_host>:<msg_server_port>/msgserver/text/logon Try msg_server_port as the port 81NN, when NN is the instance number of ASCS or SCS or Central Instance (where ABAP message server and enqueue servers are running) Depending on which message server lists the P4 port, maintain the message_server_port (81NN) in the following exchange profile parameters com.sap.aii.connect.directory.mshttpport com.sap.aii.connect.repository.mshttpport If the error includes java.net.MalformedURLException, then the above profile parmaters are not maintained at all and must be maintained along with com.sap.aii.connect.rep...

Before you begin the refresh activity, note down the current value of trkorr in the table E070L. This table has only one row and the field TRKORR contains the current transport number. After refresh, the transport request numbering will be changed creating a conflict with the already exported transports that are present in the file system. This is because the production system would have fewer released transport requests compared to QA. To avoid this conflict, you can note down the current request sequence held in E070L table and update it after the refresh. If you did not note the current request number, you may be able to find that out from the /usr/sap/trans/log/ALOG* file.

When you want to archive CO tables (COEP, COEJ, COSP, COSS, COST), there are several possible archive objects: CO_ALLO_ST CO_CCTR_PL CO_COSTCTR CO_ITEM CO_KSTRG CO_ORDER CO_PROCESS COPA2_* PM_ORDER PP_ORDER PR_ORDER PS_PROJECT RE_RNTL_AG SD_VBAK In order to choose the best archive object suitable to archive the data in your system, SAP has delivered the following programs: RARCCOA1 : Creates data extract for analysis of CO tables for archiving objects: CO_ITEM, CO_PROCESS, CO_KSTRG, RE_RNTL_AG, CO_COSTCTR, PS_PROJECT, CO_ORDER, PP_ORDER, PM_ORDER, PR_ORDER, SD_VBAK, COPA2_* RARCCOA2 : Evaluates the data extract from the report RARCCOA1 RARCCOAA : For analysis of CO tables for archiving object CO_ALLO_ST. RARCCOAP : For analysis of CO tables for archiving object CO_CCTR_PL. RARCCOA1 and RARCCOA2 Program RARCCOA1 counts the entries of required CO tables, assigns them explicitly to an archiving object and creates a data extract with the required information. ...

SAP R/2 was the first highly stable solution released by SAP. "R" stood for real-time data processing and "2" stood for the two layers: presentation + integrated application & database. This was in late 70's, when companies were running their business applications on mainframes, and R/2 was apt with the existing technology. SAP R/2 marked the first generation of SAP's business solution. Then came SAP R/3 in the 90's, capitalizing on client-server architecture. "3" signified the three layer architecture (database, application and presentation). The separation of application layer from database layer reduced the load off database and helped improve the overall performance of the solution. This was immensely popular (second) generation of SAP's business solutions. One can attribute the success to Y2K and SAP R/3 fitting the business needs of most organizations looking to dodge Y2K paranoia. SAP was riding the wave of Y2K-led-success ...

Let us say, you have installed a Web Dispatcher in the DMZ and it is used so that the business partners can send SOAP messages over the internet to you. From a security perspective, you may want the business partners to access the SOAP URLs alone; they should even be calling admin related URLs. To achieve this, you can use a permission table (ptab) in the Web Dispatcher. Create a file (say ptabfile) which allows SOAP URL pattern /XISOAPAdapter/MessagingServlet*, so that a call to the SOAP URL (http://<host>:<port>/XISOAPAdapter/MessagingServlet?channel=<party>:<sendersystem>:<CC_sender>) is permitted. The contents of the file would then be: P    /XISOAPAdapter/MessagingServlet* D   * Add the following parameter to the web dispatcher profile file: wdisp/permission_table = <absolute_path_to_ptabfile> Restart web dispatcher for the change to get activated. When a call to the web dispatcher is made containing the pattern...