| ||
全球商業軟體解決方案領導供應商SAP與Sybase，雙方的領導高層首度共同宣布合併後的發展策略與產品研發方向，將藉由端對端行動平台，推動無線企業誕生。 SAP於2010年5月12日宣布計劃收購Sybase，這項結合了兩家信譽卓著的產業領導廠商大膽的併購案，改變了企業行動通訊的遊戲規則。 此後的幾個月內，雙方擬訂了產品發展與創新計畫，以期達到企業員工和企業營運上的轉型。合併後的公司在企業應用程式、業務分析、行動基礎設施領域中均居市場領先地位。 SAP十分看重Sybase既有商業模式的優勢，確認Sybase將以獨立的單位進行運作，而客戶對Sybase產品所投入的投資將繼續維持現狀並獲得支援。 【2010/09/29 經濟日報】 |
2010年9月29日 星期三
SAP推動無線企業 改變行動通訊遊戲規則 | 即時新聞 | 財經產業 | 聯合新聞網
SAP推動無線企業 改變行動通訊遊戲規則 | 即時新聞 | 財經產業 | 聯合新聞網: "
2010年9月14日 星期二
2010年9月6日 星期一
What is the client specific data?
Client specific data refer to the data that can be accesses
only when we log in to that Client
Client specific data :
a) Business data--Master data of business partners,
products, pricing etc
b) transaction data: Sales orders, delivery, billing
docuents etc
c) Customization data: All the IMG activities that are
saved with Custoizing request number form the client
specific data
SAP Enterprise Structure
SAP Enterprise Structure
SAP enterprise structure is organizational structure that represents an enterprise in SAP R/3 system. It consists of some organizational units which, for legal reasons or for other specific business-related reasons or purposes, are grouped together. Organizational units include legal company entities, sales offices, profit centers, etc. Organizational units handle specific business functions.
Organizational units may be assigned to a single module (such as a sales organization assigned to Sales and Distribution (SD) module, or to several modules (such as a plant assigned to Materials Management (MM) and Production Planning (PP) module).
SAP R/3 system can represent a complex enterprise structure. Its flexibility can integrate the structure of an enterprise by linking its organizational unit. Enterprise structure design is a fundamental process in a SAP implementation project. The design is mainly determined by the business scenarios performed in an enterprise. Once the design is determined, it will affect many things such as how to perform a transaction and generate reports on SAP system. Although it’s possible, it requires great effort to change the enterprise structure. So , we must ensure that the enterprise structure designed in the SAP implementation project can accommodate all business scenarios and enterprise’s requirements for current and future situation.
From MM and FICO view, the typical enterprise structure can be seen as following image.
From MM perspective there another important organizational unit: Purchasing Organization.
SAP enterprise structure is organizational structure that represents an enterprise in SAP R/3 system. It consists of some organizational units which, for legal reasons or for other specific business-related reasons or purposes, are grouped together. Organizational units include legal company entities, sales offices, profit centers, etc. Organizational units handle specific business functions.
Organizational units may be assigned to a single module (such as a sales organization assigned to Sales and Distribution (SD) module, or to several modules (such as a plant assigned to Materials Management (MM) and Production Planning (PP) module).
SAP R/3 system can represent a complex enterprise structure. Its flexibility can integrate the structure of an enterprise by linking its organizational unit. Enterprise structure design is a fundamental process in a SAP implementation project. The design is mainly determined by the business scenarios performed in an enterprise. Once the design is determined, it will affect many things such as how to perform a transaction and generate reports on SAP system. Although it’s possible, it requires great effort to change the enterprise structure. So , we must ensure that the enterprise structure designed in the SAP implementation project can accommodate all business scenarios and enterprise’s requirements for current and future situation.
From MM and FICO view, the typical enterprise structure can be seen as following image.
- A Client is the highest-level element of all organizational units in SAP R/3 system. The client can be an enterprise group with several subsidiaries. An SAP client has its own master data (Data which is used long-term in the R/3 System for several business processes such as customers, materials, and vendors master data). In SAP, a client is represented by a unique 3-digit number.
- A Company Code is a unit included in the balance sheet of a legally-independent enterprise. Balance sheets and Profit and Loss statements, required by law, are created at company code level. The Company Code is the smallest organizational unit for which we can have an independent accounting department within external accounting, for example, a company within a corporate group (client). In SAP, a company code is represented by a unique 4-digit alpha-numeric for a specific client. It is the central organizational element of Financial Accounting. At least there is one company code in a client. We can set up several company codes in one client in order to manage various separate legal entities simultaneously, each with their own balanced set of financial books. Besides company code, in FICO module there is also another important organizational unit which is Controlling Area. The Controlling Area is the business unit where Cost Accounting is carried out. Usually there is a 1:1 relationship between the controlling area and the company code. For the purpose of company-wide cost accounting, one controlling area can handle cost accounting for several company codes in one enterprise.
- A plant is the place of production or simply a collection of several locations of material stocks in close physical proximity. A plant is represented by a unique 4-digit alpha-numeric for a specific client. Plant is used in Material Management (MM), Production Planning (PP), and Plant Maintenance (PM) module. A plant is assigned to one company code.
- A Storage Location is a storage area comprising warehouses in close proximity. A Storage Location is represented by a unique 4-digit alpha-numeric for a specific plant. Material stocks can be differentiated within one plant according to storage location (inventory management). Storage locations are always created for a plant.
From MM perspective there another important organizational unit: Purchasing Organization.
It’s an organization unit that has responsibility to company’s purchasing requirements. It negotiates purchasing conditions (price, discount, and other things) with vendors. A Purchasing Organization is represented by a client-unique 4-digit alpha-numeric.
A company can have one or more purchasing organizations.
If a company centralizes its purchasing activities, it only needs one purchasing organization. It means that it only has one purchasing condition for a material with a vendor at a certain time.
If a company decentralizes its purchasing activities, it will need more than one purchasing organizations. It means that it can have more than one purchasing conditions for a material with a vendor at a certain time. For example, after negotiating with a vendor, a head quarter purchasing organization buys a material with 100 USD price. That company has a branch at other state/region that is assigned to other purchasing organization. The branch can purchase the same material to the same vendor, for some reasons, with different price e.g. 105 USD.
Facts about Purchasing Organization
A purchasing organization must be assigned to one or more plants.
A purchasing organization can be assigned to one company code.
A purchasing organization can also exist without being assigned to a company code. Since each plant must be assigned to a company code, the company code can be determined via the plant.
One plant can have one or more Purchasing Organizations.
Each purchasing organization has its own info records and conditions for pricing.
Each purchasing organization has its own vendor master data.
Each purchasing organization evaluates its own vendors using MM Vendor Evaluation.
Possible organizational forms of Purchasing Organization in a SAP client:
A company can have one or more purchasing organizations.
If a company centralizes its purchasing activities, it only needs one purchasing organization. It means that it only has one purchasing condition for a material with a vendor at a certain time.
If a company decentralizes its purchasing activities, it will need more than one purchasing organizations. It means that it can have more than one purchasing conditions for a material with a vendor at a certain time. For example, after negotiating with a vendor, a head quarter purchasing organization buys a material with 100 USD price. That company has a branch at other state/region that is assigned to other purchasing organization. The branch can purchase the same material to the same vendor, for some reasons, with different price e.g. 105 USD.
Facts about Purchasing Organization
A purchasing organization must be assigned to one or more plants.
A purchasing organization can be assigned to one company code.
A purchasing organization can also exist without being assigned to a company code. Since each plant must be assigned to a company code, the company code can be determined via the plant.
One plant can have one or more Purchasing Organizations.
Each purchasing organization has its own info records and conditions for pricing.
Each purchasing organization has its own vendor master data.
Each purchasing organization evaluates its own vendors using MM Vendor Evaluation.
Possible organizational forms of Purchasing Organization in a SAP client:
- Corporate-group-wide purchasing
A purchasing organization is responsible for the purchasing activities of different company codes.
In this case, we do not assign a company code to the purchasing organization. We assign plants from different company codes to the purchasing organization. - Company-specific purchasing:
A purchasing organization is responsible for the purchasing activities of just one company code.
In this case, we assign a company code to the purchasing organization. The purchasing organization may procure only for this company code. we assign only plants of the company code concerned to the purchasing organization. - Plant-specific purchasing:
A purchasing organization is responsible for the purchasing activities of one plant.
In this case, we assign the plant and the company code of the plant to the purchasing organization. The purchasing organization may procure for this plant only.
2010年9月5日 星期日
台泥資訊股份有限公司-SAP Client情形
台泥資訊股份有限公司
...
相關環境
‧ 目前SAP使用ECC5.0與ECC6.0之版本。
‧ 後端資料庫採用SQL Server 2003。
‧ Client數一直增加，目前有5個Client，預計到年底會增加為7個。
...2010年9月4日 星期六
分散架構也能達到集中的優勢 | CIO | iThome online
分散架構也能達到集中的優勢 | CIO | iThome online: "
當企業走向全球化時，都面臨IT架構是否要走向集中或分散架構的問題，台達電子資訊處處長朱漢安說：「只要做對，分散的IT架構同樣能達到集中的效果」。
如 果你身在20年前，相信你一定不會聽過「Chindia」。「Chindia」一字是由中國（China）與印度（India）兩個國家所組成。近年來， 隨著國際化分工的情勢，各國企業為了追求更低廉的勞工成本，許多企業不斷前往大陸或印度設廠，這也讓中國與印度分別成為傲視全球硬體與軟體製造的重鎮。
全球化的發展同樣也影響到臺灣的企業生態，企業為了確保競爭優勢，追求更為低廉的勞力成本，中國大陸成為臺灣企業走向全球化布局的第一步，而這一步也成為企業全球布局的基石。
這樣的狀況同樣也影響到世界第一大電源供應器製造大廠台達電子，台達電子於1992年便開始至中國大陸投資，這也開啟了台達電子全球運籌的序幕， 至今日台達電子的版圖不但涵蓋亞洲、美洲與歐洲，全世界光是製造工廠就有33個據點，物流中心也多達94個。而這些據點的文化、法令更是不同，為了有效管 理，台達電子資訊處處長朱漢安說：「企業組織分布全球，各地的文化與運作也是相異其趣，為了讓總部資訊能即時傳達，IT必須要達到集中化的優點，也更要符 合當地的文化。」
ERP走向分散但又具集中的效益
企業營運走向全球化，許多企業都面臨到IT架構是否要集中在臺灣總部，或是分散世界各地，而當時有很多的企業都選擇了集中式的IT架構，也就是將 系統集中於臺灣，再讓世界各據點透過網路連回臺灣。不過，台達電子卻走向分散式的IT架構，而這個開始則是源於1998年SAP ERP系統的導入。
過去台達電子使用MRP（Materials Requirements Planning，料品需求計畫）來管理生產、物料與財務的工作，不過，到了1998年，面臨Y2K千禧蟲危機，再加上當時台達電子主要的客戶如IBM、 HP、Compaq或網通大廠都是使用SAP ERP系統，台達電子面臨核心系統的轉換，而台達電子最後選擇了SAP ERP系統，「Y2K迫使我們必須更換系統，透過SAP ERP系統能夠讓台達電子與客戶講同一種語言，不但順暢了商業流程，這也奠基台達電子與國際接軌的第一步。」朱漢安說。
台達電子於1998年便開始著手導入SAP ERP系統，花了1年1個月的時間，臺灣總部的ERP系統正式布署完畢，而臺灣ERP系統的建立，並不代表ERP系統完成建置，臺灣據點的完成只是建立出 一套符合台達電子需求的ERP系統，而接下來的重點，便是如何讓台達電子在全世界各地的據點，同樣能採用這套系統。也因此，除了臺灣總部外，台達電子最後 選擇泰國與中國大陸成為ERP系統的設置據點，而這也確定了ERP走向分散的一條路。不過，當初選擇分散式的IT架構，朱漢安認為主要是文化與備援兩個問 題。
首先是文化的問題，全世界各地的風俗民情不同，比方來說，臺灣正在放過年年假，在歐洲卻必須要上班，如果系統集中在臺灣，要利用過年做年度歲修 時，在歐洲的分公司便會面臨問題。朱漢安表示，要做到因地制宜是一件很難的工作，系統的分散正是解決問題的一個方法。「系統是給人使用的，當然要符合當地 的需求。」朱漢安說。
為了達到資料的統一，在泰國與中國大陸都是使用臺灣的SAP ERP系統，只是在功能上，為了符合當地的需求，部分模組並未提供，也為了當地的需求，額外設計符合當地需求的功能。
而分散的架構，最令人擔心的地方便是資料無法即時傳輸，不過，這樣的狀況並未發生在台達電子身上，朱漢安表示，最後的資料每個月都會彙整至臺灣， 此外，如果某些資料傳遞較為急迫，如臺灣研發完某個產品，要傳送至大陸工廠生產，系統便會每天自動傳遞彼此需要的資料。「這樣的架構，不但能符合當地的文 化，同樣達到集中化的效益。」朱漢安說。
另一個問題便是備援，台達電子於1999年完成臺灣總部ERP系統的導入，而當時由於「兩國論」的提出，造成臺海局勢動盪。朱漢安表示，曾經評估 如果將系統集中在臺灣，但如果兩岸不小心開啟戰端，再加上臺灣屬於地震頻仍的地方，系統的安全便是一個問題。「雞蛋放在同一個籃子便會有風險。」朱漢安 說。
也因此，在緊急的狀況下，台達電子每天會將資料備份至泰國，如果在平日，大約一個星期至一個月系統便會備份一次，以確保系統的安全。
IT集中將提高人力成本
「如果在幾年前，整體環境的考量，我還是會建議走向分散式的IT架構，但至今日我覺得集中式的架構則是企業考慮的首選。」朱漢安說。
今日的政治環境較過往更為緩和，再加上網路頻寬及品質更大幅提升，也奠定了集中式架構的優勢。
此外，伺服器虛擬化技術越來越成熟，除了可以整合資源，更重要的是，透過虛擬化可以讓一臺伺服器區分出不同的區域，比方來說，可以讓一臺伺服器的 資源透過虛擬化讓不同的區域，因不同的文化，設置不同的虛擬機器來應付因地制宜的問題，也透過資源的集中，讓資源發揮出最佳的效益。
不過，現階段台達電子並無計畫走向集中式架構，主要的原因在時間與人力上。朱漢安表示，台達電子ERP運作的模式已有一段時日，系統如果沒有太大問題，並不會輕易更動。此外，如果IT集中在臺灣，IT人力支出的花費將會提升許多。
目前台達電子全球的IT人員約有240人，臺灣總部的IT人員占39人，若IT架構集中在臺灣，臺灣總部人力勢必也要跟著提升，IT的人力成本相 對的也會跟著增加。朱漢安表示，以台達電子為例，過去曾有過一名臺灣IT人員的薪資，可以在大陸雇用4～5名同樣素質的人員，如果IT集中人力成本將會提 升。
「世界是平的」，IT人力也走向委外
《世界是平的》一書告訴我們資訊科技將造成全球化的浪潮，個人與企業面對的競爭對手將越來越多，即使遠在中國或印度的勞工，總有一天會取代其他國家的地位，企業要有足夠的競爭力，才可以存活。而這樣的現象已經蔓延至IT人力上。
為了達到集中的好處又可以兼顧降低人力成本的要求，台達電子便於2年前開始走向IT人力委外，朱漢安表示，IT需求的人力變化很大，如果當年進行 較多的專案，IT人力也會跟著增加，而委外正可解決這樣的問題。「電子產業生命周期短，不可能建置每套系統都要花上一年，委外正可以解決效率與品質的問 題。」朱漢安說。
台達電子現階段所負責的軟體專案幾乎都會委外，不過，並不是將整個專案都委外出去，朱漢安表示，一個軟體工程有很多的段落，比方系統需求、分析、 編碼與測試等，並不是全部的東西都需要委外，只需要委外勞力密集的工作便可，比方來說，系統的分析與設計還是集中在臺灣，但編碼與測試的工作就交給印度的 委外公司負責。
也因此，朱漢安便是希望能將IT架構的資源集中在臺灣，並運用全球的資源讓IT以最少的成本發揮出最大的功效，「並非每一樣東西都必須要在臺灣執行，透過委外不但可以降低人力成本，卻同樣達到集中化的目的。」朱漢安說。文⊙林文彬
CIO小檔案：朱漢安
台達電子資訊處處長
學經歷：1983年進入美商瑞智公司，1985年加入資訊工業策進會擔任組長一職，並於1988年獲得臺灣大學資訊工程研究所碩士，而後於1992年在中央大學資訊管理系擔任兼任講師，並至國產汽車擔任行政處處長一職，於1999年進入台達電子，擔任資訊處處長至今。
公司檔案－台達電子
主要業務：交換式電源供應器
員工人數：臺灣約4,200人、全球約6萬人
資訊部門人數：臺灣39人、全球約240人
當企業走向全球化時，都面臨IT架構是否要走向集中或分散架構的問題，台達電子資訊處處長朱漢安說：「只要做對，分散的IT架構同樣能達到集中的效果」。
如 果你身在20年前，相信你一定不會聽過「Chindia」。「Chindia」一字是由中國（China）與印度（India）兩個國家所組成。近年來， 隨著國際化分工的情勢，各國企業為了追求更低廉的勞工成本，許多企業不斷前往大陸或印度設廠，這也讓中國與印度分別成為傲視全球硬體與軟體製造的重鎮。
全球化的發展同樣也影響到臺灣的企業生態，企業為了確保競爭優勢，追求更為低廉的勞力成本，中國大陸成為臺灣企業走向全球化布局的第一步，而這一步也成為企業全球布局的基石。
這樣的狀況同樣也影響到世界第一大電源供應器製造大廠台達電子，台達電子於1992年便開始至中國大陸投資，這也開啟了台達電子全球運籌的序幕， 至今日台達電子的版圖不但涵蓋亞洲、美洲與歐洲，全世界光是製造工廠就有33個據點，物流中心也多達94個。而這些據點的文化、法令更是不同，為了有效管 理，台達電子資訊處處長朱漢安說：「企業組織分布全球，各地的文化與運作也是相異其趣，為了讓總部資訊能即時傳達，IT必須要達到集中化的優點，也更要符 合當地的文化。」
ERP走向分散但又具集中的效益
企業營運走向全球化，許多企業都面臨到IT架構是否要集中在臺灣總部，或是分散世界各地，而當時有很多的企業都選擇了集中式的IT架構，也就是將 系統集中於臺灣，再讓世界各據點透過網路連回臺灣。不過，台達電子卻走向分散式的IT架構，而這個開始則是源於1998年SAP ERP系統的導入。
過去台達電子使用MRP（Materials Requirements Planning，料品需求計畫）來管理生產、物料與財務的工作，不過，到了1998年，面臨Y2K千禧蟲危機，再加上當時台達電子主要的客戶如IBM、 HP、Compaq或網通大廠都是使用SAP ERP系統，台達電子面臨核心系統的轉換，而台達電子最後選擇了SAP ERP系統，「Y2K迫使我們必須更換系統，透過SAP ERP系統能夠讓台達電子與客戶講同一種語言，不但順暢了商業流程，這也奠基台達電子與國際接軌的第一步。」朱漢安說。
台達電子於1998年便開始著手導入SAP ERP系統，花了1年1個月的時間，臺灣總部的ERP系統正式布署完畢，而臺灣ERP系統的建立，並不代表ERP系統完成建置，臺灣據點的完成只是建立出 一套符合台達電子需求的ERP系統，而接下來的重點，便是如何讓台達電子在全世界各地的據點，同樣能採用這套系統。也因此，除了臺灣總部外，台達電子最後 選擇泰國與中國大陸成為ERP系統的設置據點，而這也確定了ERP走向分散的一條路。不過，當初選擇分散式的IT架構，朱漢安認為主要是文化與備援兩個問 題。
首先是文化的問題，全世界各地的風俗民情不同，比方來說，臺灣正在放過年年假，在歐洲卻必須要上班，如果系統集中在臺灣，要利用過年做年度歲修 時，在歐洲的分公司便會面臨問題。朱漢安表示，要做到因地制宜是一件很難的工作，系統的分散正是解決問題的一個方法。「系統是給人使用的，當然要符合當地 的需求。」朱漢安說。
為了達到資料的統一，在泰國與中國大陸都是使用臺灣的SAP ERP系統，只是在功能上，為了符合當地的需求，部分模組並未提供，也為了當地的需求，額外設計符合當地需求的功能。
而分散的架構，最令人擔心的地方便是資料無法即時傳輸，不過，這樣的狀況並未發生在台達電子身上，朱漢安表示，最後的資料每個月都會彙整至臺灣， 此外，如果某些資料傳遞較為急迫，如臺灣研發完某個產品，要傳送至大陸工廠生產，系統便會每天自動傳遞彼此需要的資料。「這樣的架構，不但能符合當地的文 化，同樣達到集中化的效益。」朱漢安說。
另一個問題便是備援，台達電子於1999年完成臺灣總部ERP系統的導入，而當時由於「兩國論」的提出，造成臺海局勢動盪。朱漢安表示，曾經評估 如果將系統集中在臺灣，但如果兩岸不小心開啟戰端，再加上臺灣屬於地震頻仍的地方，系統的安全便是一個問題。「雞蛋放在同一個籃子便會有風險。」朱漢安 說。
也因此，在緊急的狀況下，台達電子每天會將資料備份至泰國，如果在平日，大約一個星期至一個月系統便會備份一次，以確保系統的安全。
IT集中將提高人力成本
「如果在幾年前，整體環境的考量，我還是會建議走向分散式的IT架構，但至今日我覺得集中式的架構則是企業考慮的首選。」朱漢安說。
今日的政治環境較過往更為緩和，再加上網路頻寬及品質更大幅提升，也奠定了集中式架構的優勢。
此外，伺服器虛擬化技術越來越成熟，除了可以整合資源，更重要的是，透過虛擬化可以讓一臺伺服器區分出不同的區域，比方來說，可以讓一臺伺服器的 資源透過虛擬化讓不同的區域，因不同的文化，設置不同的虛擬機器來應付因地制宜的問題，也透過資源的集中，讓資源發揮出最佳的效益。
不過，現階段台達電子並無計畫走向集中式架構，主要的原因在時間與人力上。朱漢安表示，台達電子ERP運作的模式已有一段時日，系統如果沒有太大問題，並不會輕易更動。此外，如果IT集中在臺灣，IT人力支出的花費將會提升許多。
目前台達電子全球的IT人員約有240人，臺灣總部的IT人員占39人，若IT架構集中在臺灣，臺灣總部人力勢必也要跟著提升，IT的人力成本相 對的也會跟著增加。朱漢安表示，以台達電子為例，過去曾有過一名臺灣IT人員的薪資，可以在大陸雇用4～5名同樣素質的人員，如果IT集中人力成本將會提 升。
「世界是平的」，IT人力也走向委外
《世界是平的》一書告訴我們資訊科技將造成全球化的浪潮，個人與企業面對的競爭對手將越來越多，即使遠在中國或印度的勞工，總有一天會取代其他國家的地位，企業要有足夠的競爭力，才可以存活。而這樣的現象已經蔓延至IT人力上。
為了達到集中的好處又可以兼顧降低人力成本的要求，台達電子便於2年前開始走向IT人力委外，朱漢安表示，IT需求的人力變化很大，如果當年進行 較多的專案，IT人力也會跟著增加，而委外正可解決這樣的問題。「電子產業生命周期短，不可能建置每套系統都要花上一年，委外正可以解決效率與品質的問 題。」朱漢安說。
台達電子現階段所負責的軟體專案幾乎都會委外，不過，並不是將整個專案都委外出去，朱漢安表示，一個軟體工程有很多的段落，比方系統需求、分析、 編碼與測試等，並不是全部的東西都需要委外，只需要委外勞力密集的工作便可，比方來說，系統的分析與設計還是集中在臺灣，但編碼與測試的工作就交給印度的 委外公司負責。
也因此，朱漢安便是希望能將IT架構的資源集中在臺灣，並運用全球的資源讓IT以最少的成本發揮出最大的功效，「並非每一樣東西都必須要在臺灣執行，透過委外不但可以降低人力成本，卻同樣達到集中化的目的。」朱漢安說。文⊙林文彬
CIO小檔案：朱漢安
台達電子資訊處處長
學經歷：1983年進入美商瑞智公司，1985年加入資訊工業策進會擔任組長一職，並於1988年獲得臺灣大學資訊工程研究所碩士，而後於1992年在中央大學資訊管理系擔任兼任講師，並至國產汽車擔任行政處處長一職，於1999年進入台達電子，擔任資訊處處長至今。
公司檔案－台達電子
主要業務：交換式電源供應器
員工人數：臺灣約4,200人、全球約6萬人
資訊部門人數：臺灣39人、全球約240人
2010年8月23日 星期一
What is SAP Client?
What is SAP Client?: "What is SAP Client?
A client is organizational and legal entity in the SAP system. All the business management data is protected here because other clients can not access them. The main objective of the client is to keep the data isolated. The data in a client can be only visible within that client; it can not be displayed or changed from another client. In a physical SAP system there can be multiple clients. Each of these clients can have different objective or each client represents a unique work environment. In a development environment one client can be used as sandbox client (developers learn how to configuration using SAP environment), one can be used as prototype client (users do the customizing according to the company’s requirements and testing) and another one can be used as the master development and configuration client (where the final configuration is done). A client has its own set of tables and user data. To know whether a table is client dependant or independent you can search for a field MANDT. The client dependant tables always include the client field ‘MANDT’ as a part of the primary key. There can be multiple clients in each of the system of SAP system landscape as we have already seen in chapter 5. It is better to understand the customizing process in the CTS pipeline before designing a good client strategy for the SAP systems. Customizing is a method in the SAP R/3 system that helps the user to configure the functionality from SAP, according to the customer requirements. When the SAP objects are just used by only one client, we define them as client dependant data. There are some objects as ABAP/4 programs, which are used by all the clients in a SAP system. Those objects are called client independent data. The functional changes resulting from customizing can be client specific (client dependant) or general (client independent). You must know the fact that client independent customizing can create problems if the authorizations and the client strategy are not defined properly. For example if you have three clients in a development environment then the role of each client should be defined properly. One of these three clients should be used for client independent customizing and in other clients, users will not have the authority to do any client independent configuration.
About SAP Clients
With a standard installation, SAP delivers 000, 001 and 066 clients. Client 000 is considered to be a SAP reference client and it should not be changed or deleted at anytime from the system. After a SAP system is installed, you can create other clients from 000 by using the client copy procedure. For some important configuration you have to logon to client 000. For example, if you want to configure your CTS system then this client must be used. Client 000 also plays a very important role in upgrade process. Every time you do upgrade client dependant changes will be automatically upgraded in this client and later on the changes can be copied to other clients.
The customer uses client 001 as a SAP sample client. After a new installation both 000 and 001 clients are identical, but after an upgrade 000 will have additional customizing data. Lot of customer sites does not use 001 client at all. Client 066 is there for SAP Early Watch service. This client enables SAP to remotely access the customer system. SAP provides this service to the customer to improve the system performance. After Early Watch group goes through the checking methodology, a system performance summery and recommendations to improve performance report are provided to the customer. SAP recommends to go for an Early Watch session before your project goes live and another one sometime after the go live date. Client 066 should not be changed or deleted from the system. In case this client was deleted from the system, then you have to follow the instructions in OSS note 7312 to download the client data from sapserv3 and import this data to create 066 client.
Creating a client and setting up the client attributes
To create a client you have to maintain T000 table. From 3.0 onward, transaction SCC4can be used to maintain T000 table. Also you can chose Administration-> Client admin -> Client Maintenance from the initial screen to do the same. In client table T000, SAP system displays all the clients available, their names, currency used and when the client was changed last as shown in Figure 9.1. If the system is in display mode then you must change it to the change mode by selecting the display/change icon to create a new client. When you click display/change button, a warning is displayed as “Warning: the table is client-independent”. The “New entries” icon should be clicked to create a new client as shown in Figure 9.2.
Figure 9.1 shows Client overview in SCC4 transaction
In the new client creation screen to define a new client you must fill all the required entries. The client number and the name are entered first. Then in the second line the location of the SAP system is defined.
Logical system is defined next. SAP uses logical system concept in ALE (Application Link Enabling), workflow and EDI areas. The logical system must be unique through out the company and any other ALE system group can not use it. You must be careful changing the logical system entry. SAP treats a logical system as a client. You can use transaction BD54 to create a logical system and then enter that entry in the logical system box while creating a client.
Next entry “standard currency” can be defined according to the country. For example USD can be used as a standard currency for USA. To enter a category of a client you must know the objective of that client beforehand. For example if this client will be used as a customizing client then customizing entry should be used from the options. In the next category “Changes and transports for client-dependent objects”, there are four options. If you want to use this client as a sandbox client; and you do not want to record or create a change request every time a change happens to the client then “Changes W/O automatic recording” is the right option. If all the changes to the client should be recorded in a change request then “Automatic recording of changes” is the right option. You must choose this option for your master configuration client. If “No changes allowed” is chosen, then no changes will be allowed to this client. You must chose his option for clients in the production environment to protect your system. “No transport” option is used when you do not want any user to create a transport from this client.
Figure 9.2 shows the client create screen
The “Client-independent object changes” category determines if the client independent data maintenance is allowed in this new client. You get following four options in this category:
* Changes to Repository and client-ind. customizing allowed
* No changes to client-independent customizing objects
* No changes to Repository objects
* No changes to Repository and client-independent custom. obj.
To choose the right option from “Client-independent object changes” category, you must know the definition of Clint independent customizing objects and repository objects. The examples of SAP repository objects are data dictionary objects, module pools and screens. Client independent objects apply to all the clients. The factory calendar is an example of client independent object of customizing. For sandbox client, where user learns how to do the customizing, you must not allow the client independent customizing.
Changes to Repository and client-ind. customizing allowed: Both client independent customizing objects and SAP repository objects can be maintained. Usually this option is selected in a master-customizing client.
No changes to client-independent customizing objects: No change is allowed for client independent customizing objects but changes to repository objects are allowed. This option can be used for a sand box client.
No changes to Repository objects: If you select this option, then no changes are allowed to the Repository objects but the client independent customizing is allowed. When you want to protect the repository objects in a client, this is the right option to use.
No changes to Repository and client-independent custom. Obj: This option does not allow any changes to client independent customizing objects and repository objects. You should use this option for a consolidation and production client where the security of client independent objects and repository objects are necessary.
In the restriction category of the ‘Change View “Clients”: Details’ screen, there are four options. You are allowed to maintain only the following three options as shown in Figure 9.2:
* Protection against overwrite by copying: If you chose this option, a client copy can not overwrite the new client. You should chose this option for a master-customizing client or for an important client as production.
* Start of CATT processes allowed: This option determines whether you want to allow the CATT (Computer Aided Test Tool) process in the client or not. Computer Aided Test Tool (CATT) is tool provided by SAP to test different functionality of the SAP system. To run the CATT tool you can execute transaction SCAT. CATT process changes the database extensively and requires lot of system resources. So we recommend not to chose this option if you are in the production environment.
* Protection against SAP upgrade: If you chose this option, then this client will be not updated in time of upgrade. You should use this option for a client that is used for backup purposes or client 066 (Early Watch client) that is used by SAP for customer’s SAP system performance. If you chose this option for any client, the upgrade will not provide any data to this client and it can not be used as a regular customizing client. You need S_CTS_ALL authorization to maintain this option.
System-level control in transaction SE06
You can use the system change option to control the system level access to different types of users in a SAP project. To use system change option screen you can chose SE06 and then system change option or use SE03 and then go to “for setting the system” category and chose “set system change options”. The option you chose here directly affects ABAP/4 workbench, Workbench Organizer and the transport system.
You need all access to Workbench Organizer to change the system change options as shown in Figure 9.3.
There are some TP commands that can be used to control the system level access. ·
System change option in se06 figure9.3
The following are the four system change options:
* Objects cannot be changed: If you select this option then no changes of any kind are allowed for any objects in the SAP system. The SAP customers use this option in the consolidation and production environment. Using this option you can control the developers and the customizing people directly changing any development objects and customizing objects in the consolidation and production environment. So the users use the transport method to move the objects from development system to other systems instead of directly creating or maintaining them in the target systems. The tp command “tp lock_eu ” can be used in the operating system level to set the system to “cannot be changed” and the command “tp unlock_eu” puts the system back to where it was when the lock command was executed.
* Only original objects (w. Workbench Organizer): If you go for this option then only original objects those are created in this system can be changed. If the original object exists in some other system and you have a copy of that object in this system then you can not change that object. In special cases you can use this option for the QA or test system. All the changes are recorded in Workbench Organizer.
* All customer objects (w. Workbench Organizer): This option allows you to edit or repair an object though it is not the original object of the current system. Any changes to customer objects are allowed. The changes are controlled and recorded by the Workbench Organizer. This option does not allow changing the objects came from SAP originally. You can use this option in a training system.
* All objects (w. Workbench Organizer): With this option you can change or repair any objects in the system. Now the system is totally open for any changes to all the objects. With this option also every change is recorded and controlled by the Workbench Organizer. This option is generally selected in a development or sandbox environment.
From 4.0 version the se06 change option looks as following:
Pre-Configured Client from SAP
The pre-configured client from SAP has pre-configured customizing objects for a simple organizational structure. The pre-configured settings of the client help a customer to configure a system quickly. SAP recommends the customers to install the pre-configured client in their system if they want to go for a rapid implementation using ASAP (Accelerated SAP) methodology. In the ASAP chapter we are going to give you an extensive definition about this methodology. Now instead of starting from client 001 copy, you can start from a pre-configured client that will provide more configured features.
SAP provides the transports and help documentation to create a pre-configured client. The pre-configured client for FI/CO, SD, AM, MM, HR and PP modules is already available from SAP. According to SAP, customers that have used the pre-configured client saved 4 to 6 weeks of project implementation time. The way pre-configured client is designed; some of the small companies can run the pre-configured client for production after the out of the box installation.
Following procedure is used to create a pre-configured client:
· A client is created in T000 table
· Copying client 000 to the new client
· Copying the data files and cofiles from SAP to your system
· Adding those change requests to the buffer and then importing them to the target client
· We recommend to check your number ranges after the import
· Creating a user and assigning SAP_ALL and SAP_NEW profiles
· Run the SCAT transaction for CATT tool to test the pre-configured client. This tool is a great tool for those users, who want to learn about SAP functionality and, what a pre-configured client can do for them?
·The pre-configured client comes with non-matric units of mass, area, length and volume and a sample factory calendar is pre-configured with the ten US government holidays.
Client COPY Procedures
After the SAP system is installed, the client copy is a common thing to do for creating new clients. A client copy can be done from one system to another or within one system. A client copy can affect the database and current users in the system; so you need to be aware of the following important information before scheduling a client copy.
For the stability of the system, always schedule the client copy in the nighttime when the users are not working in the system.
To avoid data inconsistency you should not keep on working in the source or target clients when the client copy is going on.
For the best performance, always schedule the client copy in the background. Try to examine the maximum online runtime parameter “max_wp_run_time” in the instance profile. You might need to increase this for a large table copy.
You should have proper authorizations to run the client copy. As a basis system administrator you should have SAP_ALL profile to complete a client copy successfully. If you do not want a generic id to run the client copy; we recommend using SAP*. The internal user SAP* has all the authorizations needed by the client copy.
Always check the database resources before executing a client copy. You can do that by running a “test run” client copy. The test run will provide all the information about the necessary database table spaces that you need in the target client.
The main memory plays a significant role in the client copy. Make sure that you have enough memory to finish the client copy without any problem. When you are planning the hardware requirement for the SAP installation, it is always better to install memory recommended by SAP. Version 3.X and 4.X require more memory for memory management and client copy.
When you trying to copy a large productive client, it better to copy the cluster tables first.
You should look for all the OSS notes that apply to the client copy in a particular version of SAP. For example according to OSS note number 34547, SAP_USR client copy parameter that suppose to copy only user data in the background also copies customizing data in the background for release 3.0B.
If the client copy is locked by another client copy run, then check the log before deleting the lock entry in SM12 to remove the lock.
In 2.2 release of SAP R3trans is used for client copy, client export and client import. You should not do the same in 3.0 or 4.0 release of SAP. You can use R3trans to remove a client in 3.0 and 4.0 also and we will see the procedure in the “deleting a client” part of this chapter. R3trans can be used also for some other important jobs as described in chapter 10.
It is very important to know that the number ranges have to be reset in the target client if you are just copying the customizing data. Though the client copy utility has been improved a lot still we get problems with number ranges. We recommend checking the OSS notes about number ranges before dealing with them.
When you perform a client copy, it is very important to know the three levels of data in SAP system and how they affect the client copy. The client dependent application data is created from the master and transaction data of the system during the application system operation. The client dependant customizing data is created during the development process of a SAP project and this data depend upon the client dependent application data. The client independent customizing data applies to the entire client. The client copy procedure copies the client dependent application data and client dependent customizing data unless you specify to copy the client independent customizing. To maintain the consistency you should follow some SAP rules. When you are copying the customizing data, you should copy the application data (master and transaction data). If you just want to copy the customizing data then remember that all the application tables are reset in the process and this reset process can guarantee the consistency of the client
Creating custom PROFILES to copy Clients
Client copy profiles are used to copy specific data from one client to another. SAP provides some custom profiles to perform a client copy. The following are the example of profiles provided by SAP.
SAP_ALL: All data of a client
SAP_APPL: Customizing, master and transaction data
SAP_CUST: Customizing data
SAP_UAPP: Customizing, master&transact.data, user masters
SAP_UCUS: Customizing data, user masters
SAP_USR: Authorizations and user masters
The objective of above client copy profiles is defined clearly. What profile you are going to use; depends on what you want to copy from one client to another. For example you want to copy the entire data of a client then you want to choose SAP_ALL as your copy profile. you can select a profile name from the profile input field possible entries and then chose Profile -> Display profile from the menu. You can create a custom profile according to your requirement. To create a custom profile you need to chose the path Profile-> Create profile from client copy or client export screen.
Profile: Here you define the profile name. The name should be according to the SAP standard; so it should start with either Z or Y.
Last changed by and last changed on: These fields show the information about the person who last changed the profile and the time it was changed.
In the data selection category we have the following three selections:
User masters: If you chose this option then the user master records will be copied from the source client to the target client.
Customizing data: If you want to copy all customizing data then chose this option.
Appl. Data. Initialization. Cust. Data: This option copies master, transaction and customizing data from the source client to the target client.
Important tips: It is very important for you to understand the data selection procedure before the client copy. In SAP environment it is not possible to copy selected parts of the application and customizing alone. If you want to copy application data, we recommend doing it in batch input. With batch input consistency is ensured.
In the copy mode category the following options are displayed:
Initialize Recreate: This option is grayed out and already selected. This option allows the system to delete all the tables (not selected in the client copy process) in the target client and initialize them. You can use the path Extras -> No initialization to have an option for not choosing this option. We recommend not doing that; it might create instability in the target client.
Copy variants: If you want to include variants in the client copy then chose this option.
In “transport between 2 systems” category there is one option:
Client Independent data: If you chose this option then the client independent data will be copied from one client to another. We recommend executing the client copy remote compare program “RSCLICMP”, before choosing this option to do a client copy. This program provides all the information regarding the differences between the source and target systems client independent tables.
The other options are:
* Default source client: You define the default source client for the client copy in the profile. You can change the client after choosing this profile before starting the client copy.
* Default source client user master record: You can enter the client number from where the user master records will be copied to the target client. You can also change this like default source client.
Comment: You should provide a meaningful description for the profile here.
Client COPY within a system
SCC0 or RSCLICOP (SCCL as of 3.1 release)
In 3.0 SAP uses RSCLICOP program in transaction SCC0 to copy the customizing environment from one client to another. This will copy client–dependent tables, match codes, number ranges and resolve the logical dependencies between tables and programs. RSCLIC01 or RSCLIC02 were used to copy clients in 2.0 release. These programs use to create command files and the basis administrator was running R3trans utility to transport the data files. Those programs are not supported in 3.0 anymore. For the mass data transfer and large number of table copy, we recommend you to run the RSCLICOP program in the background.
Tips: Trace information about each client copy run is stored in table CCCFLOW. Use program RSCCPROT to display information about the client copy. You can run RDDANATB program in the background to get the information about the size of all the tables in all the clients. If you start the RSCLICOP in restart mode then try to check the checkentries in table CCCFLOW.
The copy procedure using SCCL
If you are planning to copy the source client to a new client then you must create a new client in SCC4 or table T000 before starting the client copy.
Logon to the target client and chose transaction SCCL or use the path Tools ->Administration->Choose Administration ->Client admin->Client copy ->Local copy and you will see a initial client copy screen as shown in Figure 9.6.
The current client is your target client so it is already selected for you in the first line. In the second line select the appropriate profile you want to use for the client copy. You choose the source client in the third line. In fourth line you can define the client from which you want to copy the user master records. The “Source Client User Master” does not have to be same as source client. Then if you want to run the local client copy to get the information about the storage requirements or a complete table statistics then select the “test run” flag. We recommend you to run the client copy using the “test run” mode first. In test run phase, database updates are not performed.
You should schedule the client copy in the background after all the parameters are selected as shown in figure Figure 9.6. You can run a client copy online if you are just copying the user master records; because when you copy only user master records very limited data is copied form a client and it does not take that long to copy those data.
Figure 9.6 local copy transaction sccl
If the client copy fails for some reason then you can restart the client copy in the restart mode after the fixing the problems. In this case the client copy will start exactly from the same point where it failed. A pre-analysis phase requires sometime determining the restart point. SAP recommends to set the restart flag in the “Execute in background” screen when you plan to copy a large client.
Tips: We recommend to reset the buffers by entering “/SYNC” in the OK code on all the application servers after executing the RSCLACOP or SCC0 for the client copy. RSCLICOP compares the contents of each table in the source client with that in the target client.
Client COPY from one system to another
Client copy from one system to another:
SCC1, SCC2, SCC7, SCC8, RSCLIEXP, RSCLIIMP
The client export/import and remote client copy procedures are commonly used to copy a client from one system to another. The client can be exported from the system using transaction SCC8 and then importing the client using SCC7 or using the transaction SCC2 for both export and import process, the second procedure is to do a remote client copy from one system to another. If you are copying a production size client we recommend performing the client copy using the first procedure.
The following are the steps in the whole procedure:
* First the data from the client in the source system is exported from the database to a transport file on hard disk. Before you transport a client from the source client database, you need to know exactly what you want to transport and you use SAP delivered profiles accordingly.
* Then the SAP delivered TP command is used for the import to the target system client database.
* The post processing procedure is run in the target client to successfully complete the client import.
You have to be very careful when copying the client independent data, because client-dependent customizing objects are dependent on entries in client-independent tables. SAP recommends that you should not copy the client independent tables if they are not yet modified in the target system. If the customizing is being done in a system regularly then you have to be very careful taking the client independent customizing to that system; otherwise you might overwrite the whole client independent customizing settings and the system will become inconsistent. We recommend to consult the customizing team of a project before copying the client independent customizing tables.
Transporting a Client
Procedure: To transport clients from one system to another, go to System Administration then choose Tools -> Administration -> Client admin->Client transport -> Client export or transaction SCC8. In the client transport screen you can select a copy profile that matches your requirements and the target system in your CTS pipeline as shown in figure 9.7. Then you can execute the client export in the background or online. Before the client export starts, a popup screen shows all the information about the command files that will be created after the client export is done. After the process starts. You can watch the export process in client copy log using transaction SCC3.
Figure 9.7 showing transaction SCC8
After the client export procedure is completed, if you chose the client independent data then three transports are created in /usr/sap/trans/cofiles or there will be two transports:
KO for the client-independent data ( if selected). For example if the client export is done from development client 100 then the file will look like DEVKO0001.
KT for the client-specific data. For example DEVKT0001
KX for the SAPscript objects as Texts and forms. For example DEVKX0001
The data export is performed automatically. The output of the export includes the name of the COMMFILE that has to be imported. The following data files will be created in/usr/sap/trans/data directory using the same example given above:
For client dependent data: /usr/sap/trans/data/RT00001.DEV
/usr/sap/trans/data/DX00001.DEV
For client independent customizing data: /usr/sap/trans/data/RO00001.DEV
For SAPscript data of a client: /usr/sap/trans/data/SX00011.DEV
Tips: Make sure that all the cofiles and the datafiles exist in the data and cofile directories before starting the import phase.
Then add all the command files to the buffer by using the TP command in /usr/sap/trans/bin directory as following:
tp addtobuffer
Using the above example cofile: tp addtobuffer devkt00001 qas (if qas is our target system)
tp addtobuffer devko00001 qas
tp addtobuffer devkx00001 qas
Then logon as adm to the target system and then use then import the transports as following:
tp import devkt00001 qas client100 u148 – For the client dependent data
tp import devko00001 qas client100 u148 – For client independent data
(In the above example QAS is the target system and 100 is the target client)
After you import a client from another system, you must perform post-processing, activities in order to adapt the runtime environment to the current state of the data. To execute post-processing, choose Tools -> Administration- >Client admin ->Client transport->client import or transaction SCC7. Transaction SCC7 will take you to the client import post-processing screen . In that screen the transport from the last tp import is proposed. Please check the transport number and if every thing is according to the order then press enter and that will take care of the post processing activities. You can also use SCC2 to execute the same process as in transaction SCC7. During this process, the SAPscript texts are imported and application reports are generated. If there are inconsistencies, you need to repeat the import after checking the log.
If you get any problem importing the SAPscript objects then use the RSTXR3TR program in the target client to import those. In this screen you can enter the transport request for the SAPscript object. According to the above example devkx00001. In the second line you need to enter the path for the SAPscript data file as following:
/usr/sap/trans/data/
/usr/sap/trans/SX00001.DEV (using the above example)
You can choose the import option from the “mode” option. Then you can continue to execute the program and it will successfully complete the import of SAPscript objects to the target client.
Up to release 3.0, RSCLIEXP program can be used to create the command files. The tp command is used to do the import as we have seen before and the RSCLIIMP program is executed for the post-processing activities and the consistency of data.
Using the transport procedure in 4.0
In 4.0 after the client is exported from the source system using transaction SCC8 as we have seen in the client export section, the following transport files are created.
KO: For the client-independent data (if the copy profile selected includes client independent data:
KR: For the client-specific data.
KX: For the Texts and forms.
When all the above transports get released from the source system, the data is exported to the data files of /usr/sap/trans/data directory automatically. The cofiles are also created in the /usr/sap/trans/cofiles directory.
Then the command files need to be added to the buffer for the import using the format from the cofiles as following:
* Logon to the target system as adm
* cd /usr/sap/trans/bin - Change to the transport directory
* tp addtobuffer - Adds to the buffer
If you are transporting to a new client then the new client should be created in the target system. Then you can start the import into the target system as shown in the following UNIX example:
tp import client from /usr/sap/trans/bin directory
After the “tp import” process completes successfully, start transaction SCC2 and then execute the import into the target client. This process imports all the SAPscript objects and generates all the programs. After the client is imported successfully, you should perform the post-processing activities by using the following path:
Tools ->Administration->Client admin->Client transport->Post-process import.
After the post processing is done, we recommend doing table compare between the source client and the target client to check all the client dependent and independent tables for consistency.
Remote CLIENT Copy
SCC9 transaction
Overview of a remote client copy:
Remote client copy is done using the RFC connection between two systems. You might get errors if you do not have all the proper authorization you need including user administration authorization.
Tips: A remote copy requires as much memory as needed by the largest table in the system.
Upto 4.0, remote copy can not handle large volume of data. Remote client copy reads the entire table from the source system and then copies that to the target system using RFC connection. For big tables as BSEG, it takes more time then the RFC wait time; so it might not copy the big table at all. For the same RFC wait time constraint, large quantity of texts can not be copied and remote client copy might terminate without any error. You are not going to see this problem in 4.0 release, because the tables are copied in blocks by RFC. You should check the memory parameters for memory and MAX_wprun_time for run time before starting the remote client copy. Try to add the big tables to the exception list by executing RSCCEXPT report. In 4.0 an inconsistency check is performed automatically during the remote client copy; if any inconsistency is there then the system returns an error.
We recommend avoiding big client copies using remote client copy procedure until release 4.0. In the beginning of a development project upto 3.1I release you can use remote client copy for the smaller clients; when the client gets real big it is better to run client export/ import procedure instead.
Remote client copy procedure:
Before you perform a client copy, the RFC destination for the source system needs to be defined using transaction SM59. In transaction SM59 screen chose “R/3 connections” under “RFC destinations”. Now you click on the create button to create a RFC connection as shown in Figure 9.9.
Figure 9.9 picture of creating a RFC destination
After the RFC connection for the source system is created, you are ready to perform a remote client copy.
You can chose SCC9 or the menu path Tools ->Administration->Client admin->Client copy ->Remote copy.
First line shows the target client, which is the current client as shown in Figure 9.10. Now you select a copy profile according your requirements. We have already seen how to create a profile and what is their objective. In the fourth line enter the source client (from where you are copying). If click the enter button the fifth line “Source Client User Master” will be filled with the same number as source client. You can change it if you want to. Enter the source system name or RFC destination name that you created in SM59. You can execute the remote client copy in the test mode by selecting the test run flag. After you are done with all the selection you can click on the “Execute in backgrd.” button to start the remote client copy procedure as a background job.
Figure 9.10 to show the remote client copy screen
Deleting a CLIENT
You need to perform two steps to delete a client. First you need to delete the complete client from database and then delete it from client maintenance table T000.
To delete a client from a SAP system:
First log on to the client to be deleted with the proper authorization to delete a client.
Then choose path Tools ->Administration->Client admin->Special functions->Delete client or transaction SCC5 and you are going to see a delete client screen as shown in figure 9.11. In this screen you are going to find two entries; test run and also delete from T000.
If you want to run a client delete process to find out information about all the tables that will be deleted then test run is the right option to use. If you do not want to copy another client to this client and get rid of this client forever then “delete from T000” is the right option to use. You can delete the client in SCC5 by executing it online or in the background. You can choose either one of these options and in the verification popup screen you can check all the parameters for client deletion. After the client deletion process starts you can use SCC3 log entries to check the client deletion process.
Figure 9.11 to show the client delete screen of SCC5
In all the SAP releases so far you can use R3trans to delete a client. We have seen significant timesaving in this way of deleting a client. If you use the R3trans command in the operating system level to delete a client then the first step is to create the command file in /usr/sap/trans/bin (it does not have to be /use/sap/trans/bin as long as you provide the right path in the OS level) with the following contents:
Clientremove
Client = 100
Select *
For the above example the command file name = del100 and the client we want to delete = 100 are used
Then in /usr/sap/trans/bin directory run the following command to delete the client:
R3trans –w -u 1
For our example here you run: R3trans -w del100.log –u 1 del100
You can VI to the del100.log to anytime to the progress in the deletion process.
Tips: For the database performance, we recommend to do database reorganization after you delete a production size client from the system.
To check the contents of the log:
Choose Tools ->Administration ->Choose Administration ->Client admin->Copy logs then Select a client by double clicking on it and select a copy process by double-clicking on it. The transaction for the log selection is SCC3 transaction. You also can run the program RSCCPROT to get the same result.
You can select one of the client copy entry from “Client copy log analysis ” second screen, following three buttons are provided as shown in figure 9.13.
Log
Monitor
Refresh
System log
Resource Analysis
Figure 9.13 for the client copy log screen
If you select a “Log” button from the “Client copy log analysis” third screen, then not only you get the general information about the client copy but also the following information for each of the table copied in the process.
Table name
Delivery class
Development class
Number of entries in the source client
Number of inserts necessary in the current client
Number of updates
Number of deletes
Additional space required by the copied table in bytes
The following is an example of what you will see in a log display screen.
Table Dev.cl Class nbr-all -ins -upd -del bytes sec
ANKA AA C 35 0 35 COPY 13 1
ANKP AA C 0 0 0 COPY 0 0
ANKT AA C 43 0 43 COPY 8 1
ANKV AA C 0 0 0 COPY 0 0
T009Y AA C 2 0 2 COPY 0 0
T082A AA C 16 0 16 COPY 0 0
T082H AA C 27 0 27 COPY 1 0
The above example shows the class “C”. The class represents the delivery class. Through the delivery class you can know the kind of data the table has or what environment the table belongs to. For example, all the tables shown in the above display belongs to the customizing environment or they have customizing data. The following are the examples of the delivery classes and their definitions.
Delivery Class Description
A Application table includes the master and transaction data
C Customizing table
L Table for storing temporary data
G Customizing table. It is protected against SAP Update
E Control table
S System table. They are only maintained by SAP
W System table. Contents transportable via separate TR objects
The table information, all the additional storage required in Kbytes, the run time for the client copy and the end of processing time are also shown as following example in the client copy log analysis.
* Selected tables: 5,672
* Copied tables: 5,671
* Tables deleted: 0
* Storage required (Kbytes): 260,444
* Program ran successfully
* Runtime (seconds): 10,123
* End of processing: 13:37:24
You can click on the “Monitor “ button and watch the progress of the client copy real time.
The “Refresh” button always refreshes the screen to show you the up to date information.
The “System log” button takes you to the system log screen to show you all the system messages.
The next button “Resource analysis” is a very important utility to show you all the data base resources you need to run the client copy in the table space level. In the resource analysis utility you can get realistic picture of deletes and inserts calculation for the database. Memory requirements can also be found out by this utility.
Tips: You should always check SM21 (the system log) for all the client copy problems.
Ten 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.
Simple method for copying VARIANTS
The VARI, VARID and VARIT tables contain all the variants in the SAP system. Those variants can be copied in the client copy time using an appropriate client copy profile. If you just want to copy the variants then R3trans can be used to copy those very quickly.
To copy the variants from one client to another in a system using R3trans, follow the following procedure:
First create a control file with the following contains:
clientcopy
source client =
target client = < target client number>
select * from VARI
select * from VARIT
select * from VARID
The second step is to logon as adm and use the controls file with R3trans as shown in the client export and import section of this chapter. This procedure will copy all the variants from the source client to the target client as defined in the control file.
To copy all the variants between clients between two different systems:
First create a control file for R3trans with the following contents to create a data file:
export
client =
file = ‘’
select * from VARI
select * from VARIT
select * from VARID
The second step is to logon as adm in the source system and use R3trans as shown before to execute the control file. The process will create a data file as defined in the control file. The third step is to define a import control file for R3trans with the following contents:
Import
client =
file = ‘’
After the control file is created, logon as admin the target system and execute R3trans command with the control file to import all the variants to the target system.
Important client management tips
We recommend deleting the large cluster tables first from a client using R3trans client remove command before going for the deletion of entire client. To increase the client copy performance it is also better to copy the cluster tables first using the R3trans command. Then use the RSCCEXPT report to exclude all the cluster tables before doing the client copy. To get a list of cluster tables use transaction SE85, then chose other objects -> select pooled/cluster tables. The following control files are for both the above examples:
To copy the cluster tables:
clientcopy
source client = xxx
target client = YYY
select * from BSEG
select * from ……..
To delete the cluster table before deleting the whole client:
client remove
client = XXX
select * from BSEG
(XXX and YYY represent the client numbers)
Refer to chapter 10 to understand how to execute a R3trans command.
In each database, the rollback segments needs to be extended so that the largest table in the system can be copied without any problem. In release it only applies to client transports or copies and deleting the tables. In release 4.0 it only applies to transports.
SAP does not support a non-numeric client.
If you get a message “The client copy is locked by another run” and you want to kill the current process to start a new client copy then call transaction SM12 and check the entry RSCLICOP and then delete it. Make sure to check if any clientcopy job is running in the background before deleting the lock. If a job is still running, you should wait till it finishes because you can not start another client copy run.
After the client export is done, the command file might not be created for the SAPscript objects in /usr/sap/trans/cofiles directory, you only find the data file in /usr/sap/trans/data directory. Sometimes the SAPscript objects can be locked properly and the transport request does not get released. To release the SAPscript change request, logon to the source client and execute SE01. Then enter the transport number and try to release it from there. If there is a lock problem then solve it and then release the request.
Transporting from 4.0 to 3.0:
You have to be very careful while doing the transport of a logical database in 4.0. In release 4.0 the buffer of the logical database is changed. Always run RSLDB400 after the import of a logical database. Before transporting the repository objects from release 4.0 to 3.1 you need to know that the names of the repository objects in release 4.0 are extended. Always check the current version of R3trans; you might need for your system to transport objects from 4.0 to 3.1 releases. If your system has SAP release other than 3.1I; you can not transport SAPscript objects from 4.0 to 3.0. The internal buffer is also changed in release 4.0, so GUI screens can not be transported from 4.0 to 3.0.
See Also:
Default Clients in SAP
Creating a client and setting up the client attributes
Local Client Copy - SCCL
SAP Tips & Tricks
Trackbacks
1.
Default Clients in SAP January 6, 2009 9:31 pm
2.
Creating a client and setting up the client attributes January 6, 2009 9:33 pm
3.
SAP R/3 dispatcher and work processes January 17, 2009 8:02 am
- 已使用 Google 工具列寄出"
A client is organizational and legal entity in the SAP system. All the business management data is protected here because other clients can not access them. The main objective of the client is to keep the data isolated. The data in a client can be only visible within that client; it can not be displayed or changed from another client. In a physical SAP system there can be multiple clients. Each of these clients can have different objective or each client represents a unique work environment. In a development environment one client can be used as sandbox client (developers learn how to configuration using SAP environment), one can be used as prototype client (users do the customizing according to the company’s requirements and testing) and another one can be used as the master development and configuration client (where the final configuration is done). A client has its own set of tables and user data. To know whether a table is client dependant or independent you can search for a field MANDT. The client dependant tables always include the client field ‘MANDT’ as a part of the primary key. There can be multiple clients in each of the system of SAP system landscape as we have already seen in chapter 5. It is better to understand the customizing process in the CTS pipeline before designing a good client strategy for the SAP systems. Customizing is a method in the SAP R/3 system that helps the user to configure the functionality from SAP, according to the customer requirements. When the SAP objects are just used by only one client, we define them as client dependant data. There are some objects as ABAP/4 programs, which are used by all the clients in a SAP system. Those objects are called client independent data. The functional changes resulting from customizing can be client specific (client dependant) or general (client independent). You must know the fact that client independent customizing can create problems if the authorizations and the client strategy are not defined properly. For example if you have three clients in a development environment then the role of each client should be defined properly. One of these three clients should be used for client independent customizing and in other clients, users will not have the authority to do any client independent configuration.
About SAP Clients
With a standard installation, SAP delivers 000, 001 and 066 clients. Client 000 is considered to be a SAP reference client and it should not be changed or deleted at anytime from the system. After a SAP system is installed, you can create other clients from 000 by using the client copy procedure. For some important configuration you have to logon to client 000. For example, if you want to configure your CTS system then this client must be used. Client 000 also plays a very important role in upgrade process. Every time you do upgrade client dependant changes will be automatically upgraded in this client and later on the changes can be copied to other clients.
The customer uses client 001 as a SAP sample client. After a new installation both 000 and 001 clients are identical, but after an upgrade 000 will have additional customizing data. Lot of customer sites does not use 001 client at all. Client 066 is there for SAP Early Watch service. This client enables SAP to remotely access the customer system. SAP provides this service to the customer to improve the system performance. After Early Watch group goes through the checking methodology, a system performance summery and recommendations to improve performance report are provided to the customer. SAP recommends to go for an Early Watch session before your project goes live and another one sometime after the go live date. Client 066 should not be changed or deleted from the system. In case this client was deleted from the system, then you have to follow the instructions in OSS note 7312 to download the client data from sapserv3 and import this data to create 066 client.
Creating a client and setting up the client attributes
To create a client you have to maintain T000 table. From 3.0 onward, transaction SCC4can be used to maintain T000 table. Also you can chose Administration-> Client admin -> Client Maintenance from the initial screen to do the same. In client table T000, SAP system displays all the clients available, their names, currency used and when the client was changed last as shown in Figure 9.1. If the system is in display mode then you must change it to the change mode by selecting the display/change icon to create a new client. When you click display/change button, a warning is displayed as “Warning: the table is client-independent”. The “New entries” icon should be clicked to create a new client as shown in Figure 9.2.
Figure 9.1 shows Client overview in SCC4 transaction
In the new client creation screen to define a new client you must fill all the required entries. The client number and the name are entered first. Then in the second line the location of the SAP system is defined.
Logical system is defined next. SAP uses logical system concept in ALE (Application Link Enabling), workflow and EDI areas. The logical system must be unique through out the company and any other ALE system group can not use it. You must be careful changing the logical system entry. SAP treats a logical system as a client. You can use transaction BD54 to create a logical system and then enter that entry in the logical system box while creating a client.
Next entry “standard currency” can be defined according to the country. For example USD can be used as a standard currency for USA. To enter a category of a client you must know the objective of that client beforehand. For example if this client will be used as a customizing client then customizing entry should be used from the options. In the next category “Changes and transports for client-dependent objects”, there are four options. If you want to use this client as a sandbox client; and you do not want to record or create a change request every time a change happens to the client then “Changes W/O automatic recording” is the right option. If all the changes to the client should be recorded in a change request then “Automatic recording of changes” is the right option. You must choose this option for your master configuration client. If “No changes allowed” is chosen, then no changes will be allowed to this client. You must chose his option for clients in the production environment to protect your system. “No transport” option is used when you do not want any user to create a transport from this client.
Figure 9.2 shows the client create screen
The “Client-independent object changes” category determines if the client independent data maintenance is allowed in this new client. You get following four options in this category:
* Changes to Repository and client-ind. customizing allowed
* No changes to client-independent customizing objects
* No changes to Repository objects
* No changes to Repository and client-independent custom. obj.
To choose the right option from “Client-independent object changes” category, you must know the definition of Clint independent customizing objects and repository objects. The examples of SAP repository objects are data dictionary objects, module pools and screens. Client independent objects apply to all the clients. The factory calendar is an example of client independent object of customizing. For sandbox client, where user learns how to do the customizing, you must not allow the client independent customizing.
Changes to Repository and client-ind. customizing allowed: Both client independent customizing objects and SAP repository objects can be maintained. Usually this option is selected in a master-customizing client.
No changes to client-independent customizing objects: No change is allowed for client independent customizing objects but changes to repository objects are allowed. This option can be used for a sand box client.
No changes to Repository objects: If you select this option, then no changes are allowed to the Repository objects but the client independent customizing is allowed. When you want to protect the repository objects in a client, this is the right option to use.
No changes to Repository and client-independent custom. Obj: This option does not allow any changes to client independent customizing objects and repository objects. You should use this option for a consolidation and production client where the security of client independent objects and repository objects are necessary.
In the restriction category of the ‘Change View “Clients”: Details’ screen, there are four options. You are allowed to maintain only the following three options as shown in Figure 9.2:
* Protection against overwrite by copying: If you chose this option, a client copy can not overwrite the new client. You should chose this option for a master-customizing client or for an important client as production.
* Start of CATT processes allowed: This option determines whether you want to allow the CATT (Computer Aided Test Tool) process in the client or not. Computer Aided Test Tool (CATT) is tool provided by SAP to test different functionality of the SAP system. To run the CATT tool you can execute transaction SCAT. CATT process changes the database extensively and requires lot of system resources. So we recommend not to chose this option if you are in the production environment.
* Protection against SAP upgrade: If you chose this option, then this client will be not updated in time of upgrade. You should use this option for a client that is used for backup purposes or client 066 (Early Watch client) that is used by SAP for customer’s SAP system performance. If you chose this option for any client, the upgrade will not provide any data to this client and it can not be used as a regular customizing client. You need S_CTS_ALL authorization to maintain this option.
System-level control in transaction SE06
You can use the system change option to control the system level access to different types of users in a SAP project. To use system change option screen you can chose SE06 and then system change option or use SE03 and then go to “for setting the system” category and chose “set system change options”. The option you chose here directly affects ABAP/4 workbench, Workbench Organizer and the transport system.
You need all access to Workbench Organizer to change the system change options as shown in Figure 9.3.
There are some TP commands that can be used to control the system level access. ·
System change option in se06 figure9.3
The following are the four system change options:
* Objects cannot be changed: If you select this option then no changes of any kind are allowed for any objects in the SAP system. The SAP customers use this option in the consolidation and production environment. Using this option you can control the developers and the customizing people directly changing any development objects and customizing objects in the consolidation and production environment. So the users use the transport method to move the objects from development system to other systems instead of directly creating or maintaining them in the target systems. The tp command “tp lock_eu ” can be used in the operating system level to set the system to “cannot be changed” and the command “tp unlock_eu” puts the system back to where it was when the lock command was executed.
* Only original objects (w. Workbench Organizer): If you go for this option then only original objects those are created in this system can be changed. If the original object exists in some other system and you have a copy of that object in this system then you can not change that object. In special cases you can use this option for the QA or test system. All the changes are recorded in Workbench Organizer.
* All customer objects (w. Workbench Organizer): This option allows you to edit or repair an object though it is not the original object of the current system. Any changes to customer objects are allowed. The changes are controlled and recorded by the Workbench Organizer. This option does not allow changing the objects came from SAP originally. You can use this option in a training system.
* All objects (w. Workbench Organizer): With this option you can change or repair any objects in the system. Now the system is totally open for any changes to all the objects. With this option also every change is recorded and controlled by the Workbench Organizer. This option is generally selected in a development or sandbox environment.
From 4.0 version the se06 change option looks as following:
Pre-Configured Client from SAP
The pre-configured client from SAP has pre-configured customizing objects for a simple organizational structure. The pre-configured settings of the client help a customer to configure a system quickly. SAP recommends the customers to install the pre-configured client in their system if they want to go for a rapid implementation using ASAP (Accelerated SAP) methodology. In the ASAP chapter we are going to give you an extensive definition about this methodology. Now instead of starting from client 001 copy, you can start from a pre-configured client that will provide more configured features.
SAP provides the transports and help documentation to create a pre-configured client. The pre-configured client for FI/CO, SD, AM, MM, HR and PP modules is already available from SAP. According to SAP, customers that have used the pre-configured client saved 4 to 6 weeks of project implementation time. The way pre-configured client is designed; some of the small companies can run the pre-configured client for production after the out of the box installation.
Following procedure is used to create a pre-configured client:
· A client is created in T000 table
· Copying client 000 to the new client
· Copying the data files and cofiles from SAP to your system
· Adding those change requests to the buffer and then importing them to the target client
· We recommend to check your number ranges after the import
· Creating a user and assigning SAP_ALL and SAP_NEW profiles
· Run the SCAT transaction for CATT tool to test the pre-configured client. This tool is a great tool for those users, who want to learn about SAP functionality and, what a pre-configured client can do for them?
·The pre-configured client comes with non-matric units of mass, area, length and volume and a sample factory calendar is pre-configured with the ten US government holidays.
Client COPY Procedures
After the SAP system is installed, the client copy is a common thing to do for creating new clients. A client copy can be done from one system to another or within one system. A client copy can affect the database and current users in the system; so you need to be aware of the following important information before scheduling a client copy.
For the stability of the system, always schedule the client copy in the nighttime when the users are not working in the system.
To avoid data inconsistency you should not keep on working in the source or target clients when the client copy is going on.
For the best performance, always schedule the client copy in the background. Try to examine the maximum online runtime parameter “max_wp_run_time” in the instance profile. You might need to increase this for a large table copy.
You should have proper authorizations to run the client copy. As a basis system administrator you should have SAP_ALL profile to complete a client copy successfully. If you do not want a generic id to run the client copy; we recommend using SAP*. The internal user SAP* has all the authorizations needed by the client copy.
Always check the database resources before executing a client copy. You can do that by running a “test run” client copy. The test run will provide all the information about the necessary database table spaces that you need in the target client.
The main memory plays a significant role in the client copy. Make sure that you have enough memory to finish the client copy without any problem. When you are planning the hardware requirement for the SAP installation, it is always better to install memory recommended by SAP. Version 3.X and 4.X require more memory for memory management and client copy.
When you trying to copy a large productive client, it better to copy the cluster tables first.
You should look for all the OSS notes that apply to the client copy in a particular version of SAP. For example according to OSS note number 34547, SAP_USR client copy parameter that suppose to copy only user data in the background also copies customizing data in the background for release 3.0B.
If the client copy is locked by another client copy run, then check the log before deleting the lock entry in SM12 to remove the lock.
In 2.2 release of SAP R3trans is used for client copy, client export and client import. You should not do the same in 3.0 or 4.0 release of SAP. You can use R3trans to remove a client in 3.0 and 4.0 also and we will see the procedure in the “deleting a client” part of this chapter. R3trans can be used also for some other important jobs as described in chapter 10.
It is very important to know that the number ranges have to be reset in the target client if you are just copying the customizing data. Though the client copy utility has been improved a lot still we get problems with number ranges. We recommend checking the OSS notes about number ranges before dealing with them.
When you perform a client copy, it is very important to know the three levels of data in SAP system and how they affect the client copy. The client dependent application data is created from the master and transaction data of the system during the application system operation. The client dependant customizing data is created during the development process of a SAP project and this data depend upon the client dependent application data. The client independent customizing data applies to the entire client. The client copy procedure copies the client dependent application data and client dependent customizing data unless you specify to copy the client independent customizing. To maintain the consistency you should follow some SAP rules. When you are copying the customizing data, you should copy the application data (master and transaction data). If you just want to copy the customizing data then remember that all the application tables are reset in the process and this reset process can guarantee the consistency of the client
Creating custom PROFILES to copy Clients
Client copy profiles are used to copy specific data from one client to another. SAP provides some custom profiles to perform a client copy. The following are the example of profiles provided by SAP.
SAP_ALL: All data of a client
SAP_APPL: Customizing, master and transaction data
SAP_CUST: Customizing data
SAP_UAPP: Customizing, master&transact.data, user masters
SAP_UCUS: Customizing data, user masters
SAP_USR: Authorizations and user masters
The objective of above client copy profiles is defined clearly. What profile you are going to use; depends on what you want to copy from one client to another. For example you want to copy the entire data of a client then you want to choose SAP_ALL as your copy profile. you can select a profile name from the profile input field possible entries and then chose Profile -> Display profile from the menu. You can create a custom profile according to your requirement. To create a custom profile you need to chose the path Profile-> Create profile from client copy or client export screen.
Profile: Here you define the profile name. The name should be according to the SAP standard; so it should start with either Z or Y.
Last changed by and last changed on: These fields show the information about the person who last changed the profile and the time it was changed.
In the data selection category we have the following three selections:
User masters: If you chose this option then the user master records will be copied from the source client to the target client.
Customizing data: If you want to copy all customizing data then chose this option.
Appl. Data. Initialization. Cust. Data: This option copies master, transaction and customizing data from the source client to the target client.
Important tips: It is very important for you to understand the data selection procedure before the client copy. In SAP environment it is not possible to copy selected parts of the application and customizing alone. If you want to copy application data, we recommend doing it in batch input. With batch input consistency is ensured.
In the copy mode category the following options are displayed:
Initialize Recreate: This option is grayed out and already selected. This option allows the system to delete all the tables (not selected in the client copy process) in the target client and initialize them. You can use the path Extras -> No initialization to have an option for not choosing this option. We recommend not doing that; it might create instability in the target client.
Copy variants: If you want to include variants in the client copy then chose this option.
In “transport between 2 systems” category there is one option:
Client Independent data: If you chose this option then the client independent data will be copied from one client to another. We recommend executing the client copy remote compare program “RSCLICMP”, before choosing this option to do a client copy. This program provides all the information regarding the differences between the source and target systems client independent tables.
The other options are:
* Default source client: You define the default source client for the client copy in the profile. You can change the client after choosing this profile before starting the client copy.
* Default source client user master record: You can enter the client number from where the user master records will be copied to the target client. You can also change this like default source client.
Comment: You should provide a meaningful description for the profile here.
Client COPY within a system
SCC0 or RSCLICOP (SCCL as of 3.1 release)
In 3.0 SAP uses RSCLICOP program in transaction SCC0 to copy the customizing environment from one client to another. This will copy client–dependent tables, match codes, number ranges and resolve the logical dependencies between tables and programs. RSCLIC01 or RSCLIC02 were used to copy clients in 2.0 release. These programs use to create command files and the basis administrator was running R3trans utility to transport the data files. Those programs are not supported in 3.0 anymore. For the mass data transfer and large number of table copy, we recommend you to run the RSCLICOP program in the background.
Tips: Trace information about each client copy run is stored in table CCCFLOW. Use program RSCCPROT to display information about the client copy. You can run RDDANATB program in the background to get the information about the size of all the tables in all the clients. If you start the RSCLICOP in restart mode then try to check the checkentries in table CCCFLOW.
The copy procedure using SCCL
If you are planning to copy the source client to a new client then you must create a new client in SCC4 or table T000 before starting the client copy.
Logon to the target client and chose transaction SCCL or use the path Tools ->Administration->Choose Administration ->Client admin->Client copy ->Local copy and you will see a initial client copy screen as shown in Figure 9.6.
The current client is your target client so it is already selected for you in the first line. In the second line select the appropriate profile you want to use for the client copy. You choose the source client in the third line. In fourth line you can define the client from which you want to copy the user master records. The “Source Client User Master” does not have to be same as source client. Then if you want to run the local client copy to get the information about the storage requirements or a complete table statistics then select the “test run” flag. We recommend you to run the client copy using the “test run” mode first. In test run phase, database updates are not performed.
You should schedule the client copy in the background after all the parameters are selected as shown in figure Figure 9.6. You can run a client copy online if you are just copying the user master records; because when you copy only user master records very limited data is copied form a client and it does not take that long to copy those data.
Figure 9.6 local copy transaction sccl
If the client copy fails for some reason then you can restart the client copy in the restart mode after the fixing the problems. In this case the client copy will start exactly from the same point where it failed. A pre-analysis phase requires sometime determining the restart point. SAP recommends to set the restart flag in the “Execute in background” screen when you plan to copy a large client.
Tips: We recommend to reset the buffers by entering “/SYNC” in the OK code on all the application servers after executing the RSCLACOP or SCC0 for the client copy. RSCLICOP compares the contents of each table in the source client with that in the target client.
Client COPY from one system to another
Client copy from one system to another:
SCC1, SCC2, SCC7, SCC8, RSCLIEXP, RSCLIIMP
The client export/import and remote client copy procedures are commonly used to copy a client from one system to another. The client can be exported from the system using transaction SCC8 and then importing the client using SCC7 or using the transaction SCC2 for both export and import process, the second procedure is to do a remote client copy from one system to another. If you are copying a production size client we recommend performing the client copy using the first procedure.
The following are the steps in the whole procedure:
* First the data from the client in the source system is exported from the database to a transport file on hard disk. Before you transport a client from the source client database, you need to know exactly what you want to transport and you use SAP delivered profiles accordingly.
* Then the SAP delivered TP command is used for the import to the target system client database.
* The post processing procedure is run in the target client to successfully complete the client import.
You have to be very careful when copying the client independent data, because client-dependent customizing objects are dependent on entries in client-independent tables. SAP recommends that you should not copy the client independent tables if they are not yet modified in the target system. If the customizing is being done in a system regularly then you have to be very careful taking the client independent customizing to that system; otherwise you might overwrite the whole client independent customizing settings and the system will become inconsistent. We recommend to consult the customizing team of a project before copying the client independent customizing tables.
Transporting a Client
Procedure: To transport clients from one system to another, go to System Administration then choose Tools -> Administration -> Client admin->Client transport -> Client export or transaction SCC8. In the client transport screen you can select a copy profile that matches your requirements and the target system in your CTS pipeline as shown in figure 9.7. Then you can execute the client export in the background or online. Before the client export starts, a popup screen shows all the information about the command files that will be created after the client export is done. After the process starts. You can watch the export process in client copy log using transaction SCC3.
Figure 9.7 showing transaction SCC8
After the client export procedure is completed, if you chose the client independent data then three transports are created in /usr/sap/trans/cofiles or there will be two transports:
KO for the client-independent data ( if selected). For example if the client export is done from development client 100 then the file will look like DEVKO0001.
KT for the client-specific data. For example DEVKT0001
KX for the SAPscript objects as Texts and forms. For example DEVKX0001
The data export is performed automatically. The output of the export includes the name of the COMMFILE that has to be imported. The following data files will be created in/usr/sap/trans/data directory using the same example given above:
For client dependent data: /usr/sap/trans/data/RT00001.DEV
/usr/sap/trans/data/DX00001.DEV
For client independent customizing data: /usr/sap/trans/data/RO00001.DEV
For SAPscript data of a client: /usr/sap/trans/data/SX00011.DEV
Tips: Make sure that all the cofiles and the datafiles exist in the data and cofile directories before starting the import phase.
Then add all the command files to the buffer by using the TP command in /usr/sap/trans/bin directory as following:
tp addtobuffer
Using the above example cofile: tp addtobuffer devkt00001 qas (if qas is our target system)
tp addtobuffer devko00001 qas
tp addtobuffer devkx00001 qas
Then logon as adm to the target system and then use then import the transports as following:
tp import devkt00001 qas client100 u148 – For the client dependent data
tp import devko00001 qas client100 u148 – For client independent data
(In the above example QAS is the target system and 100 is the target client)
After you import a client from another system, you must perform post-processing, activities in order to adapt the runtime environment to the current state of the data. To execute post-processing, choose Tools -> Administration- >Client admin ->Client transport->client import or transaction SCC7. Transaction SCC7 will take you to the client import post-processing screen . In that screen the transport from the last tp import is proposed. Please check the transport number and if every thing is according to the order then press enter and that will take care of the post processing activities. You can also use SCC2 to execute the same process as in transaction SCC7. During this process, the SAPscript texts are imported and application reports are generated. If there are inconsistencies, you need to repeat the import after checking the log.
If you get any problem importing the SAPscript objects then use the RSTXR3TR program in the target client to import those. In this screen you can enter the transport request for the SAPscript object. According to the above example devkx00001. In the second line you need to enter the path for the SAPscript data file as following:
/usr/sap/trans/data/
/usr/sap/trans/SX00001.DEV (using the above example)
You can choose the import option from the “mode” option. Then you can continue to execute the program and it will successfully complete the import of SAPscript objects to the target client.
Up to release 3.0, RSCLIEXP program can be used to create the command files. The tp command is used to do the import as we have seen before and the RSCLIIMP program is executed for the post-processing activities and the consistency of data.
Using the transport procedure in 4.0
In 4.0 after the client is exported from the source system using transaction SCC8 as we have seen in the client export section, the following transport files are created.
KO: For the client-independent data (if the copy profile selected includes client independent data:
KR: For the client-specific data.
KX: For the Texts and forms.
When all the above transports get released from the source system, the data is exported to the data files of /usr/sap/trans/data directory automatically. The cofiles are also created in the /usr/sap/trans/cofiles directory.
Then the command files need to be added to the buffer for the import using the format from the cofiles as following:
* Logon to the target system as adm
* cd /usr/sap/trans/bin - Change to the transport directory
* tp addtobuffer - Adds to the buffer
If you are transporting to a new client then the new client should be created in the target system. Then you can start the import into the target system as shown in the following UNIX example:
tp import client from /usr/sap/trans/bin directory
After the “tp import” process completes successfully, start transaction SCC2 and then execute the import into the target client. This process imports all the SAPscript objects and generates all the programs. After the client is imported successfully, you should perform the post-processing activities by using the following path:
Tools ->Administration->Client admin->Client transport->Post-process import.
After the post processing is done, we recommend doing table compare between the source client and the target client to check all the client dependent and independent tables for consistency.
Remote CLIENT Copy
SCC9 transaction
Overview of a remote client copy:
Remote client copy is done using the RFC connection between two systems. You might get errors if you do not have all the proper authorization you need including user administration authorization.
Tips: A remote copy requires as much memory as needed by the largest table in the system.
Upto 4.0, remote copy can not handle large volume of data. Remote client copy reads the entire table from the source system and then copies that to the target system using RFC connection. For big tables as BSEG, it takes more time then the RFC wait time; so it might not copy the big table at all. For the same RFC wait time constraint, large quantity of texts can not be copied and remote client copy might terminate without any error. You are not going to see this problem in 4.0 release, because the tables are copied in blocks by RFC. You should check the memory parameters for memory and MAX_wprun_time for run time before starting the remote client copy. Try to add the big tables to the exception list by executing RSCCEXPT report. In 4.0 an inconsistency check is performed automatically during the remote client copy; if any inconsistency is there then the system returns an error.
We recommend avoiding big client copies using remote client copy procedure until release 4.0. In the beginning of a development project upto 3.1I release you can use remote client copy for the smaller clients; when the client gets real big it is better to run client export/ import procedure instead.
Remote client copy procedure:
Before you perform a client copy, the RFC destination for the source system needs to be defined using transaction SM59. In transaction SM59 screen chose “R/3 connections” under “RFC destinations”. Now you click on the create button to create a RFC connection as shown in Figure 9.9.
Figure 9.9 picture of creating a RFC destination
After the RFC connection for the source system is created, you are ready to perform a remote client copy.
You can chose SCC9 or the menu path Tools ->Administration->Client admin->Client copy ->Remote copy.
First line shows the target client, which is the current client as shown in Figure 9.10. Now you select a copy profile according your requirements. We have already seen how to create a profile and what is their objective. In the fourth line enter the source client (from where you are copying). If click the enter button the fifth line “Source Client User Master” will be filled with the same number as source client. You can change it if you want to. Enter the source system name or RFC destination name that you created in SM59. You can execute the remote client copy in the test mode by selecting the test run flag. After you are done with all the selection you can click on the “Execute in backgrd.” button to start the remote client copy procedure as a background job.
Figure 9.10 to show the remote client copy screen
Deleting a CLIENT
You need to perform two steps to delete a client. First you need to delete the complete client from database and then delete it from client maintenance table T000.
To delete a client from a SAP system:
First log on to the client to be deleted with the proper authorization to delete a client.
Then choose path Tools ->Administration->Client admin->Special functions->Delete client or transaction SCC5 and you are going to see a delete client screen as shown in figure 9.11. In this screen you are going to find two entries; test run and also delete from T000.
If you want to run a client delete process to find out information about all the tables that will be deleted then test run is the right option to use. If you do not want to copy another client to this client and get rid of this client forever then “delete from T000” is the right option to use. You can delete the client in SCC5 by executing it online or in the background. You can choose either one of these options and in the verification popup screen you can check all the parameters for client deletion. After the client deletion process starts you can use SCC3 log entries to check the client deletion process.
Figure 9.11 to show the client delete screen of SCC5
In all the SAP releases so far you can use R3trans to delete a client. We have seen significant timesaving in this way of deleting a client. If you use the R3trans command in the operating system level to delete a client then the first step is to create the command file in /usr/sap/trans/bin (it does not have to be /use/sap/trans/bin as long as you provide the right path in the OS level) with the following contents:
Clientremove
Client = 100
Select *
For the above example the command file name = del100 and the client we want to delete = 100 are used
Then in /usr/sap/trans/bin directory run the following command to delete the client:
R3trans –w -u 1
For our example here you run: R3trans -w del100.log –u 1 del100
You can VI to the del100.log to anytime to the progress in the deletion process.
Tips: For the database performance, we recommend to do database reorganization after you delete a production size client from the system.
To check the contents of the log:
Choose Tools ->Administration ->Choose Administration ->Client admin->Copy logs then Select a client by double clicking on it and select a copy process by double-clicking on it. The transaction for the log selection is SCC3 transaction. You also can run the program RSCCPROT to get the same result.
You can select one of the client copy entry from “Client copy log analysis ” second screen, following three buttons are provided as shown in figure 9.13.
Log
Monitor
Refresh
System log
Resource Analysis
Figure 9.13 for the client copy log screen
If you select a “Log” button from the “Client copy log analysis” third screen, then not only you get the general information about the client copy but also the following information for each of the table copied in the process.
Table name
Delivery class
Development class
Number of entries in the source client
Number of inserts necessary in the current client
Number of updates
Number of deletes
Additional space required by the copied table in bytes
The following is an example of what you will see in a log display screen.
Table Dev.cl Class nbr-all -ins -upd -del bytes sec
ANKA AA C 35 0 35 COPY 13 1
ANKP AA C 0 0 0 COPY 0 0
ANKT AA C 43 0 43 COPY 8 1
ANKV AA C 0 0 0 COPY 0 0
T009Y AA C 2 0 2 COPY 0 0
T082A AA C 16 0 16 COPY 0 0
T082H AA C 27 0 27 COPY 1 0
The above example shows the class “C”. The class represents the delivery class. Through the delivery class you can know the kind of data the table has or what environment the table belongs to. For example, all the tables shown in the above display belongs to the customizing environment or they have customizing data. The following are the examples of the delivery classes and their definitions.
Delivery Class Description
A Application table includes the master and transaction data
C Customizing table
L Table for storing temporary data
G Customizing table. It is protected against SAP Update
E Control table
S System table. They are only maintained by SAP
W System table. Contents transportable via separate TR objects
The table information, all the additional storage required in Kbytes, the run time for the client copy and the end of processing time are also shown as following example in the client copy log analysis.
* Selected tables: 5,672
* Copied tables: 5,671
* Tables deleted: 0
* Storage required (Kbytes): 260,444
* Program ran successfully
* Runtime (seconds): 10,123
* End of processing: 13:37:24
You can click on the “Monitor “ button and watch the progress of the client copy real time.
The “Refresh” button always refreshes the screen to show you the up to date information.
The “System log” button takes you to the system log screen to show you all the system messages.
The next button “Resource analysis” is a very important utility to show you all the data base resources you need to run the client copy in the table space level. In the resource analysis utility you can get realistic picture of deletes and inserts calculation for the database. Memory requirements can also be found out by this utility.
Tips: You should always check SM21 (the system log) for all the client copy problems.
Ten 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.
Simple method for copying VARIANTS
The VARI, VARID and VARIT tables contain all the variants in the SAP system. Those variants can be copied in the client copy time using an appropriate client copy profile. If you just want to copy the variants then R3trans can be used to copy those very quickly.
To copy the variants from one client to another in a system using R3trans, follow the following procedure:
First create a control file with the following contains:
clientcopy
source client =
target client = < target client number>
select * from VARI
select * from VARIT
select * from VARID
The second step is to logon as adm and use the controls file with R3trans as shown in the client export and import section of this chapter. This procedure will copy all the variants from the source client to the target client as defined in the control file.
To copy all the variants between clients between two different systems:
First create a control file for R3trans with the following contents to create a data file:
export
client =
file = ‘’
select * from VARI
select * from VARIT
select * from VARID
The second step is to logon as adm in the source system and use R3trans as shown before to execute the control file. The process will create a data file as defined in the control file. The third step is to define a import control file for R3trans with the following contents:
Import
client =
file = ‘’
After the control file is created, logon as admin the target system and execute R3trans command with the control file to import all the variants to the target system.
Important client management tips
We recommend deleting the large cluster tables first from a client using R3trans client remove command before going for the deletion of entire client. To increase the client copy performance it is also better to copy the cluster tables first using the R3trans command. Then use the RSCCEXPT report to exclude all the cluster tables before doing the client copy. To get a list of cluster tables use transaction SE85, then chose other objects -> select pooled/cluster tables. The following control files are for both the above examples:
To copy the cluster tables:
clientcopy
source client = xxx
target client = YYY
select * from BSEG
select * from ……..
To delete the cluster table before deleting the whole client:
client remove
client = XXX
select * from BSEG
(XXX and YYY represent the client numbers)
Refer to chapter 10 to understand how to execute a R3trans command.
In each database, the rollback segments needs to be extended so that the largest table in the system can be copied without any problem. In release it only applies to client transports or copies and deleting the tables. In release 4.0 it only applies to transports.
SAP does not support a non-numeric client.
If you get a message “The client copy is locked by another run” and you want to kill the current process to start a new client copy then call transaction SM12 and check the entry RSCLICOP and then delete it. Make sure to check if any clientcopy job is running in the background before deleting the lock. If a job is still running, you should wait till it finishes because you can not start another client copy run.
After the client export is done, the command file might not be created for the SAPscript objects in /usr/sap/trans/cofiles directory, you only find the data file in /usr/sap/trans/data directory. Sometimes the SAPscript objects can be locked properly and the transport request does not get released. To release the SAPscript change request, logon to the source client and execute SE01. Then enter the transport number and try to release it from there. If there is a lock problem then solve it and then release the request.
Transporting from 4.0 to 3.0:
You have to be very careful while doing the transport of a logical database in 4.0. In release 4.0 the buffer of the logical database is changed. Always run RSLDB400 after the import of a logical database. Before transporting the repository objects from release 4.0 to 3.1 you need to know that the names of the repository objects in release 4.0 are extended. Always check the current version of R3trans; you might need for your system to transport objects from 4.0 to 3.1 releases. If your system has SAP release other than 3.1I; you can not transport SAPscript objects from 4.0 to 3.0. The internal buffer is also changed in release 4.0, so GUI screens can not be transported from 4.0 to 3.0.
See Also:
Default Clients in SAP
Creating a client and setting up the client attributes
Local Client Copy - SCCL
SAP Tips & Tricks
Trackbacks
1.
Default Clients in SAP January 6, 2009 9:31 pm
2.
Creating a client and setting up the client attributes January 6, 2009 9:33 pm
3.
SAP R/3 dispatcher and work processes January 17, 2009 8:02 am
- 已使用 Google 工具列寄出"
訂閱：
文章 (Atom)