Export Sales Business Steps in SAP SD: Customer sends the purchase order with the requested products and the Sales Operations Team creates the sales order. Business Partner Determination – Based on the sold-to business partner, the default ship-to, bill-to and payer partners are proposed in the order.
First we export the users from the Target Client (DEV.300 in your case) with Tx SCC8. We then perform a Remote Client Copy from Production with TX SCC9 and after the client copy is complete we use Tx STMS to import the users back into the Target client, then we perform Tx SCC7 for the Post import Activities. Export SAP Users and Authorizations Logon to the target SAP system in the client you want to save and go to transaction SCC8. Select the SAPUSER or SAPUONL profile and the Target System, - Click the Schedule as Background Job button and then check Immediately. The data in customer master records enables to control how the transactions data is to be posted and processed for a customer. Master records are divided into the following areas. General data; Company code data; Sales area data; During sales transactions, the SAP system automatically determines the details of customer from the customer master.
Before reading about the client copy in SAP we should get to know a little about the concept of client first. A client is a self contained unit in technical, organizational and commercial terms having its own set of table key ranges and user master data. At the kernel level data from different clients is kept separately.
In the where clause the client number is used by the application executed by SQL statements. The access to particular clients is limited by where clause, so data from several different clients may be contained in a table.
The following are client specific data examples:
Application Data – Material master data and business transaction data is included here.
Customizing Data – Document types, assignments and organizational units are included here.
User Master Data – User groups, authorization and parameters are included here.
By using the SAP authorization concept and company codes, several companies or subsidiaries can be integrated in a single client in the SAP client concept.
How to do client copy in SAP?
There are 3 client copy methods delivered by SAP. They are as mentioned below:
1. If we want to perform client copies inside a given instance then we can do so by local client copy.
2. If we want to perform client copies between different SAP instances then we can do so by remote client copy.
3. Another way to perform client copies between different SAP instances is through client import and export.
We can copy different data types like the users data, application data, cross client customizing and client dependant customizing by using the local client copy method. It is important to know that we cannot use the local client copy in SAP to handle objects from ABAP dictionary like ABAP reports, table definitions and so on. We have to use other instances to transport these objects through transport requests.
The difference between the other two copy methods is that in remote client copy method Remote Function Call (RFC) can be used to immediately transfer data across the network. In the other copy method i.e. client import and export, the data can be exported in files in a second’s time to the transport directory.
Prerequisites of Client Copy
A low system activity timeframe should be performed for client copy. You should not have any activity on the source system to have a consistent client copy. So you should lock the dialog users by disconnecting them. You also have to suspend background jobs using BTCTRNS1 report. Later on you have to use BTCTRNS2 to release the jobs. The data dictionaries between the source and target systems should be the same for remote client copies.
Client Copy in SAP
Tcode sccl is used to perform local client copy while scc3 is used to check the client copy logs. For remote client copy sm59 should be used to access the source client after RFC has been declared. Client import and export is performed in two steps: the client import option is used to import data in the target client and the client export option is used to export files in source client by checking on with /usr/sap/trans/data | cofiles.
Scenario
Source System
• SAP ECC6.0 with Kernel Release 700
• Oracle Database 11g
• SUSE Linux
Target System
• SAP ECC6.0 with Kernel Release 700
• Oracle Database 11g
• SUSE Linux
• Point in Time Recovery Method
Pre-Steps
1. Check the database backup for source and target systems are completed successfully.
2. Check the sapdata directory size for source and target systems are sufficient.
3. Put the system messages via transaction code SM02 on the target system to warn users that the system refresh is happening.
4. Create a control file of the source system and sent to the target system. Please be aware that the creation of the control file is advisable to generate after the source system backup is completed. This is because we are using point in time recovery method. This is to avoid any other sapdata is added in between the control file is created.
5. On transaction code SE10. Tick all for Request Type and tick only Modifiable for Request Status. List down all the transport that has not been released. Forward the transport list to the appropriate team (Functional) for further analysis. (Hint) You can released the transport directly via transaction code SE03. All Modifiable transport will wipe out after the system refresh.
Sap Export Settings
6. If your refresh system is in CUA landscape (child CUA), please take the screenshot as per this link https://itsiti.com/find-cua-parent-sap-system
7. Take screenshot of SCC4: Client Overview (including the each client details). Compare with the source system and please be noted that on each client that are not existed, you will need to use SAP_ALL during the client copy process.
8. Screenshot of SCOT, STMS, SMLG, RZ12, RZ04, DB13, BD54, WE20, WE21, SM37 – capture all released jobs, STRUSTSSO2, SE06, RSA1, RSA7.
9. Export the User Master Export (UME) from client 000 and client production(s). Please refer to https://itsiti.com/sap-client-export-import-using-scc8
10. Export the all the printer configured to your local computer/laptop. Please refer to https://itsiti.com/export-import-printers-in-sap
11. Export the RFCDOC & V_TBDLS tables via transport of copies. Please refer to https://itsiti.com/export-import-table-rfcdoc-v_tbdls-via-transport-of-copies
System Refresh
1. Bring down the target system and delete the SAP data files on the target system. Now, copy the SAP data files from source to the target system.
Sap Export Sqvi
2. Edit the control file (adapt the control file to target SAP system). Create the control file and open the database.
3. Add Temp files to database (PSAPTEMP)
4. Import the table.
5. Disable R/3 RFC destinations
6. Cleanup SID –dependent tables
7. Create the OPS$ connect mechanism.
Post Steps
1. Install License Keys.
User Master Export In Sap Steps Using
2. Disable Background work processes
Sap Data Export
3. Check SAP/Oracle connectivity
Export Sap Data To Excel
4. Edit and adapt below configurations from the following transaction codes and reports
• SCC4 – Change Client Role
• SE06 – Set System Change settings
• STMS – Configure Transport System
• SCOT – Disable Smtp Client
• SM37 – Set All Batch Jobs To Scheduled Mode
• SICK – Check System Is Ok After Restart
• DB02 – Refresh Database Stats
• BD54 – Change Logical System Descriptions
• SPAD – Convert Printers
• RZ10 – Import Active Profiles
• RZ04 – Delete And Recreate Op Modes
• Update RFC Destinations
• Delete Old OSCOL Definitions
• SMLG – Delete And Recreate Login Groups
• SM61 – Update Batch Processing Servers
• RSTS0022 – Delete Old Temse Objects
• RSBTCDEL2 – Delete Old Batch Job Logs
• SE61 – SAP Sign On Message
• Delete And Recreate DB13 Jobs
• RZ12 – Delete And Recreate RFC Login Groups
• SCUA, SCUM, SCUG, SCUL – Central User Administration
• WE20, WE21 – Partner Profiles
• SM36 – Configure SAP standard jobs
• SWU3 – Automatic Workflow Customizing
• SECSTORE – Administration program for SECURE STORAGE
• SCC7 – Import / Post processing of users
• SM21 – Check system log
• ST22 – ABAP dump
5. Perform full backup and hand over to ABAP and FUNCTIONAL team to verify!