PAID REMOTE SAP BASIS SUPPROT


Website : www.sapbasis.in

SAP IDES SERVER Remote Full Access 24x7x365 just 500 /Month or $20 .
SAP IDES IS-OIL 6.0 / IS -RETAIL Remote Full Access 800 /Month or $30
SAP IDES SRM 7.0 + ECC 6.0 EHP6 Remote Full Acess 1300/ Month or $ 50
SAP IDES CRM 7.0 + ECC 6.0 EHP6 + ISU Remote Full Acess 1300/ Month or $50
SAP SCM +APO Server Full Access 1000 /Month
SAP BO4 Remote Access 1300 /Month $ 50

Please Contact : support@sapbasis.in /+919052825025

SAP OIL and GAS Certification Material @ $ 50 USD
SAP OIL & GAS CERTIFICATION TRAINING
Following Materials You Will Learn@HOME : ( All Below 9+ Courses -Latest and OLD VERSION COURSES )
=================================================
IOG100 - Primary & Secondary Distribution with SAP Oil & GasEHP6 ( v097 - Col97 ) - Latest
IOG150 - Oil & Gas Industry Supply ChainIOG320 - Oil & Gas Exchanges Business
IOG330 - Bulk Transportation and Shipment Costing
IOG340 - Trading & Scheduling with SAP for Oil & Gas - EHP6 ( v097 - Col97 )- Latest
IOG350 - Service Station Retailing
IOGW40 - Joint Venture Accounting (JVA)
IOGW50 - Offshore Logistics Management (IS-Oil)SAP OIL & GAS Overview - Presentation
+

GET BELOW - 4 Alternative Study Courses For FREE :



SCM500 - Processes in Procurement ( Col92 - 2009/Q2 )
SCM600 - Sales & Distribution Processes ( Col92 - 2009/Q2 )
SCM601 - Processes in Logistics Execution ( Col92 - 2009/Q2 )
SCM611 - Shipments ( Col92 - 2009/Q2 )

Monday, March 21, 2011

Configuring NFS on Solaris 10 for SAP Distributed System


Configuring NFS on Solaris 10 for SAP Distributed System


Step 1: enable NFS sever by running the following:

      svcadm -v enable -r network/nfs/server

Step 2: Run the following command to share via NFS

      share -F nfs -o rw /db2
      share –F nfs –o rw /sapmnt

Note: The above share command will not persist over reboots. To persist over reboots, add an entry to /etc/dfs/dfstab

      share -F nfs -o rw /db2
      share –F nfs –o rw /sapmnt

Step 3: Run the following command to mount from the client side:

                # mkdir  /db2
      # mkdir /sapmnt

      mount -F nfs server:/db2 /db2
      mount -F nfs server:/sapmnt /sapmnt

Note: The above mount command will not persist over reboots. To persist over reboots, add the following line in /etc/vfstab

        server:/db2   -   /db2   nfs   -   yes    rw,soft
        
        server:/sapmnt   -   /sapmnt   nfs   -   yes    rw,soft
         

Sunday, March 20, 2011

Creating Remote Client Copy SCC9

Creating Remote Client Copy SCC9

Step by Step Procedure to copy a Client to the Remote SAP Server.
  • Logon to destination SAP server
  • Use Transaction Code SCC4
  • Go to change mode
  • Create a new client, assign client number & description as per request
  • Logoff from current client.
  • Login to newly created client in destination SAP server using the following credentials :
i. Client Number : Newly created one
ii User Id : SAP*
iii Password : PASS
  • Use Transaction Code SM59 to create a RFC Connection for client copy if does not exist already.
  • RFC Connection should have Target Server as Destination and the test results should say “Connection test OK”
  • Use SCC9 Transaction code to go to client copy screen.

  • Give profile as per the request.
  • Select RFC destination created for the purpose for the source client to client copy
  • Use Transaction code SCC3 for monitoring the progress of client copy
___________________________________________________________________
Golden rules for CLIENT Copies

1. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data.
2. Application data (transactional and master) should not be copied without copying configuration data.
3. Client copy requires a valid client as the destination client. Make sure that the client exists in T000 table and you can logon to that client.
4. The transport system and the transport management system of 4.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance.
5. When you copy a client from one system to another, client-independent tables should only be copied if they are not yet modified in the target system.
6. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place.
7. Always check the database space before performing a client copy.
8. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system.
9. RSCLICHK program should be run in the target system remotely before doing a client export. This program will give information about the missing definitions from the data dictionary in the target. After executing this program and getting successful results you can ensure that the client copy will have no problems. In case some tables are different; you can use SE11 to compare and adjust the table structure in both the system before the client copy. A remote test client copy also can be executed to know the differences between source client and target client.
10. If you are not in release 2.2 then do not use R3trans to copy a client.

Email configuration in sap



When e-mails are transferred using SMTP, the SAP Web Application Server communicates directly with a mail server. No gateway or connector is necessary.
You can use any SMTP-compatible product as a mail server.
The SAP system always transfers the outbound mails to a single mail server. You can set its host address and port number.
The SAP system can receive inbound mails from any number of mail servers. You can reach each client using separate, configurable port numbers. You can address the SAP system or its client most effectively by using an individual subdomain for each client (for example, "crm-prod.company.com"). The assignment of these subdomains to host name and port numbers of the SAP system is defined by the routing rules on the mail servers.
As of Release 6.20, you can also send and receive fax and SMS or paging messages using SMTP. These are packed in e-mails for this purpose. When sending, the mail server refers to the domain of the recipients' addresses, and directs the e-mails either to a internal company fax/SMS server (for example "SMS=+491759628717@sms-server.company.com") or to an external provider (for example, "FAX=+16105954900@fax-provider.com"). When receiving, the fax or SMS server or the provider sends e-mails to addresses with the domain of the SAP system (for example "FAX=+496227751624@crm-prod.company.com").
Configuration
1.     Profile parameter
To be able to use the SMTP functions, you must adjust the profile of the SAP Web Application Server. We recommend that you activate SMTP on all application servers of an SAP system. If this is not the case, the SAPconnect send job may only be scheduled for servers on which SMTP is active. The scheduling is then done by the standard job definition (transaction SM36) rather than by the SAPconnect administration (transaction SCOT, for a description, see 4.c).











2.    












3.    



4.    
For SMTP, you must set the profile parameters listed below. The placeholder <*> stands for a number with which the parameters that can occur several times are numbered sequentially, starting with 0.
a) icm/server_port_<*> = PROT=SMTP,PORT=<port>
This opens a TCP/IP port for receiving mails by the SMTP Plug-In. <port> specifies the number of the port that you should use.  This must not be occupied by any other program on this host (for example, Sendmail usually uses port 25). If no mails (including status notifications) are to be received in this SAP system, <port> can be set to 0.
You can use the TIMEOUT option to define a maximum wait time for a response from the mail server (in seconds).
b) is/SMTP/virt_host_<*> = <host>:<port>,<port>,...;
This defines a "virtual mail host" for receiving mails. If all incoming mails (including status notifications) are to be received and processed in a single client of this SAP system, this parameter is not required (an entry is/SMTP/virt_host_0 = *:* is then assumed by default). If you want several clients to be able to receive, you must create a virtual mail host for every client. <host> specifies the name of the host to which incoming mails are addressed. The "*" value can also be specified here if the mail distribution is to occur independently of the addressed host. Important: If the mail is to be distributed according to host names, you must assign different IP addresses to these host names. <port> specifies the number of a port to which incoming mails are addressed. Several ports may be specified for each host, and several hosts (with several ports if necessary) may be specified for each virtual mail host. Important: The parameter line must always be completed with a semicolon (even if only one host is involved).
The assignment of virtual mail hosts to clients is carried out in the SAP system (see 3).
              Example:
With two clients capable of receiving mail, the profile parameters could read as follows (as of Release 6.20):
   icm/server_port_0 = PROT=HTTP,PORT=1080
  icm/server_port_1 = PROT=HTTPS,PORT=1443
  icm/server_port_2 = PROT=SMTP,PORT=25000,TIMEOUT=180
  icm/server_port_3 = PROT=SMTP,PORT=25001,TIMEOUT=180
  is/SMTP/virt_host_0 = *:25000;
   is/SMTP/virt_host_1 = *:25001;
2. User administration (transaction SU01)
a) System user
In each client of an SAP system in which incoming mails (or status notifications for sent mails) are to be received, a system user must be created to process the incoming messages. To do this, use transaction SU01 to create a user of the type "system", and assign the "S_A.SCON" profile to this user.
Important: Contrary to the documentation for user types, users of type "system" are also subject to password expiry, which can prevent the receipt of mails. To avoid this, use user type "service" until a correction of the incorrect behavior of type "system" is available.
b) User addresses
Each individual user who wants to receive e-mails in an SAP system needs an Internet mail address. This is also used as a sender address for sending e-mails. In transaction SU01, enter the Internet mail address of a user in the field "E-Mail" under "Address". As a domain, use the domain of the SAP system client if possible (see "General information" above and 4.a), for example "firstname.lastname@crm-prod.company.com".
3. Client assignment (transaction SICF)
For each client of an SAP system in which incoming mails (or status notifications for sent mails) are to be received, and processed if necessary, you must create an SMTP server in which the assignment to a virtual mail host as well as the logon data is defined. In transaction SICF, an SMTP server (envelope icon) should already be available in every SAP system. This is delivered by SAP. Use this for the first client that you want to be able to receive mails, and create a new SMTP server for every other client. You must make the following settings on the SMTP servers:
a) Host data
For "Profile Parameter Number", enter the sequence number of a parameter is/SMTP/virt_host_<*> from the profile. If you have only one client and did not create such a parameter in the profile, enter 0.
b) Service data
Enter the client into which the mails received using this virtual mail host are to be directed, as well as the logon data (user, password, language) of the service user that was created for inbound mails (see 2.a).
c) Handler list
Enter CL_SMTP_EXT_SAPCONNECT in the first position.
              As of Release 6. 20, you must activate the SMTP server after you create or change it (Service/Virt.Host --> Activate, or right-click).
4. SAPconnect administration (transaction SCOT)
You have to make the SAPconnect settings separately in each client from which e-mails are to be sent or in which e-mails are to be received.
a) Default domain
The domain of this SAP system client is defined here, for example, crm-prod.company.com. It is used for the following purposes:
o  The SMTP Plug-In logs on to the mail server with the domain as ID.
o  The message ID of outgoing mails is created with this domain.
o  If an SAP user who has not entered an Internet mail address in their user master record sends an e-mail, a sender address is generated from the SAP user name and this domain, for example SMITHJ@crm-prod.company.com.
b) Nodes
There are different types of node in SAPconnect:
o  SMTP nodes (for the SMTP function of the SAP application server)
o  HTTP nodes (for paging or SMS providers using Web services, as of 6.20)
o  RFC nodes (for old RFC-compatible e-mail/fax/paging gateways)
                       There is always a single SMTP node in each client. It is created automatically by the system and cannot be deleted. It is configured as follows (double-click on the node name):
o  Select "Node in use".
o  Under "Mail Host" and "Mail Port", specify the mail server to which outbound mails are to be transferred.
o  Select "Set" for "Internet".
o  Specify address areas of recipient addresses that are to be reached using these nodes (usually "*" if all e-mails are to be sent using SMTP).
o  For "Output Formats for SAP Documents", the following is recommended:
   SAPscript / Smart Forms      PDF
   ABAP List                    HTM
   Business Object / Link        HTM
   RAW Text                      TXT
                       If fax messages are also to be sent using SMTP:
o  Select "Set" for "Fax".
o  Specify address areas of recipient addresses that are to be reached using these nodes (usually "*" if all faxes are to be sent using SMTP).
o  For "Output Formats for SAP Documents", the following is recommended:
   SAPscript / Smart Forms      PDF
   ABAP List                    PDF
   Business Object / Link        TXT
   RAW Text                      TXT
o  For "Conversion into Internet Address", enter the domain of the fax server or fax provider. The local part of the Internet address is generated automatically by the system. The address then has the form "FAX=+recipientnumber@domain".
                       If paging or SMS messages are also to be sent using SMTP:
o  Select "Set" for "Pager(SMS)".
o  Specify address areas of recipient addresses that are to be reached using these nodes (usually "*" if all paging or SMS messages are to be sent using SMTP).
o  For "Conversion into Internet Address", enter the domain of the paging or SMS server or paging or SMS provider. The local part of the Internet address is generated automatically by the system. The address then has the form "SMS=+recipientnumber@domain".
                       Important: To be able to use paging or SMS in the SAP system, names must be defined for the messaging services to be used (e.g. "SMS"). You can do this using transaction SA14.
c) Send job
E-mails that are sent from an SAP application are merely put into a queue. A periodically running background process, the SAPconnect send job, takes the e-mails from the queue and sends them by Internet. This job can be scheduled from SAPconnect administration as follows:
o  Choose "View" --> "Jobs". Check whether a job is already scheduled (displayed as a calendar icon).
o  Choose "Job" --> "Create", and specify a job name.
o  Place the cursor on the "SAP&CONNECTALL" variant, and choose "Schedule Job".
o  Choose "Schedule periodically".
o  Specify a time interval (for example, 10 minutes), and choose "Create".
d) Receiving
With the settings made so far, SAP users can already receive e-mails in their inbox in the Business Workplace (transaction SBWP) at the address entered in the user master record.
If, on receipt of e-mails to a specific address or with specific contents (for example XML documents), you want a program that processes these e-mails to start automatically, you can configure this under "Settings" --> "Inbound Processing".
If, on receipt of e-mails to a specific address or from a specific sender, you want these to be directed automatically to another recipient or a distribution list, you can configure this under "Settings" --> "Inbound Distribution".
5. Settings on the mail server (SAP-external configuration)
To be able to receive mails in the SAP system, you need to set your mail server so that certain mail addresses are forwarded to one or several SAP systems or clients. For this purpose, you need to define routing rules that assign a mail host and/or port to address areas (generic address parts, usually the domain), for example:
      *@crm-prod.company.com  -->  SAPWASHost:25000
      *@crm-test.company.com  -->  SAPWASHost:25001
For more information about the exact setting procedure, see the mail server documentation. Note 546147 describes where the documentation can be found for the Microsoft Exchange 2000 Server, and what to do if your mail server does not allow routing to ports other than port 25.


Regards,


Alihamed.sa