Scribd Logo
Upload

Welcome to Scribd!

  • Client Copy in HANA

    Uploaded by

    Prasanta Kumar Nanda
    236 views13 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document

    Copyright:

    © All Rights Reserved
    Download as PDF or read online from Scribd
    Flag for inappropriate content
    236 views13 pages

    Client Copy in HANA

    Uploaded by

    Prasanta Kumar Nanda

    Copyright:

    © All Rights Reserved
    Download as PDF or read online from Scribd
    Flag for inappropriate content
    of 13
    Folk RSS feed Like ‘Aska Question Write a Blog Post i Technical Articles Roman Gorbenko February 12,2021 6 minute read Remote client copy and activity after copying. Step-by-step guide for S/AHANA and EWM 3.Likes 1,851 View 2Comments Prerequisites. For testing purposes and for a lot of other reasons you must periodically refresh SAP systems in QAS landscape with data from SAP systerns in PROD landscape. This is typically a business case almost in all companies. In this scenario we have ERP (SAP S/4HANA), SCM systems (standalone SAP EWM) and SAP ATTP integrated via CIF-interface. In the first part of this blog post, we consider a remote client copy process with tips and restrictions in the second part we consider activity after copying. Resolution. Step 1. RFC settings In SOURCE client. ‘Transaction — SM59 — RFC Destinations (Display/Maintain) ‘Create RFC connection from a Source system to a Target system Step 2. Preparation in a Target system In TARGET client. Strongly recommended copy client only for system without any users and background jobs activity (see Note #489690). ‘Transaction — SE38 — ABAP Editor Report - BTCTRNS1 (Move Jobs with Status “Rescheduled due to Upgrade”) ‘Transaction - SE37 - ABAP Function Modules FM - SCCR_LOCK_CLIENT (to lock the client) Step 3, Remote Copy In SOURCE client. ‘Transaction - SCC9 - Remote Client Copy Selected Profile- SAP_APPX * * Ifyou want only refresh data in QAS from PROD Source destination, - RFC destination from Step 1 o vi« aee Halon Client Copy - Copy a Client "gi Schedule as Background Job [[)start Inmedately figRFC System Comparison =5 Target Clent a, Selected Profile ‘SAP_APEX [| Description SAP_APPL w/o Authorization Profiles and Roles Source destnat. oT tert cony, fa System Name source Clent Test Run Set checkbox to “Immediately” Schedule Client Copy in Background Schedule Job Background Server (Optional) a Picneats No Printer Dialog Test Run Step 4, Display Log In SOURCE system (000 Client) After you start copying the procedure SOURCE client is locked for all users But you can check the copying process from another client (usually from client — 000) Transaction - SCC3 - Client Copy Log Ym We [betas [25File Loo System Nene: Client in Source syatem copy Type lnenote copy Frofile sae APEK seatue fuser Start on 25.01.2021 / 23:16 ftast Entry on 26.01.2021 / 03 Statistics for this Fun = No. of Tables 1a722 of 1478] ~ Deleted Lines 3342318 = Copied Lines 44512407 Tips. Tip #1 Ifyou have more than one system in integration you must start a copy of all systems together. Simple example. You copy only $/4HANA, MM-Consultants create a test inbound delivery in S/4HANA and we have possible errors in EWM (Material, Batch, BP... and so on — not exists) Tip #2 ‘There are many situations when it is necessary to exclude a particular table from copying. ‘Transaction - SE38 — ABAP Editor Report - RSCCEXPT Few possible examples: PP/DS tables (exist in liveCache and cannot be copied): /SAPAPO/ORDKEY /SAPAPO/ORDMAP /SAPAPO/STOCKANC Giant HR static table (all-Russian address database): HRPADRU_D_FIASHS. and so on RSS feed il Like BO [options | copy indwdualy | wan Process (MESES Packages | lent Cony: Excluded Tables Table Name User Date To Basis Release o [SAPABOTORDREY) 23.01.2021 999 . SAPRPO/ORDMAP 23.01.2021 999 x /SAPAPO/STOCKANC 23.01.2021 990 FOERIVEOO1 73.01.2021 FMDERIVED02 23.01.2021 FMDERIVEO03 23.01.2021, FMDERIVEDD4 22.01.2021 FMDERIVEDDS za12021 732 FDERIVEO0S 23.01.2021 FMDERIVE00S 23.01.2021 752 FMDERIVEO09 23.01.2021 FTR_FP_WHERECOND 26.01.2019 752 a HROADRU_D_FIASHS 97.02.2019 752 v Links: 70290 - CC-INFO: Exclude tables with RSCCEXPT https://launchpad.support.sap.com/#/notes/70290 Examples and restrictions from real life. Q: What is the estimated time for the client copy? S/4HANA (Db size: 140 GB) - 12h SAP EWM (0b size 44 GB) - 4h 30m Q: Are there any performance issues for the TARGET system when copying S/4HANA during business hours? ‘A: No, any performance issues detected but it is strongly recommended to copy the client only for the system without any users and background jobs activity (see Note #489690), Q: Are there any performance issues for the TARGET system when copying SAP EWM during business hours? A: Yes, performance issues detected, target system can’t work during system copy procedure. Q: Any restriction dependent on DB-size? A: Yes, you can't copy large clients via RFC. In this case very important the number of records in the tables, For tables with millions of records, copying cannot be performed at the optimal time. So you must use alternative ways at this case. For example Homogenous System Copy. See this blog-post — https://blogs.sap.com/2019/11/16/sandbox-system-via-homogenous-system-copy-sap-hana-specific-backup- restore-step-by-step-guide/ Links: 489690 - CC-INFO: Copying large production clients https://launchpad.support.sap.com/#/notes/489690 FL, Bose Like Transaction - BDLS - Logical system name conversion BDLS looks for all references to fields of data type “LOGSYS" and “EDI_PARNUM" and changes these values to the new logical system name (from the old one). In our example run BDLS in QAS Landscape for S/4HANA, EWM, and ATTP systems. For each system after client copy in BDLS: EWM PROD CLNTXXX = EWM QAS CLNTXXX S/4HANA PROD CLNTXXX = S/4HANA QAS CLNTXXX ATTP PROD CLNTXXX = ATTP QAS CLNTXXX It is only Warning (W). Press Enter to Continue. Converting logical system names (Old Logical System Name Cc) New Logical System Name =I © Conversion of Cient-Dependent and Cient-Independent Tables (e.g. Renaming Orginal System or Folowing Database Copy) © conversion of Clent-Dependent Tables (e.g. Following @ Gent Copy) D1 Test run 1 check Existence of New Names in Tables Number of Entries per Commit 100,000 Tables to be Converted to 2 ‘Options LCibetermine Relevant Tables Again Start Conversion of Tables with Special Handing Sometimes BDLS can't convert several tables. This issue is not new. For example - Table BUTOID and Note #1391535 "BDLS does not convert table BUTOID” Link — https://launchpad.support.sap.com/#/notes/1391535 This is an old Note and it is not relevant for a new system So lam writing a simple ABAP code for this situation: REPORT zupdate. UPDATE butOid SET institute = ‘XXX’ WHERE institute EQ ‘YY’ XXX — New Logical System Name i] Rssteea — 4 Like QIELINSP_DOC, QIE_IRULE_ARGS REPORT zupdate. UPDATE QIE_INSP_DOC SET INST_ID = ‘XXX’ WHERE INST_ID EQ ‘YYY’. UPDATE QIE_IRULE_ARGS SET INST_ID = ‘XXX’ WHERE INST_ID EQ ‘YYY’ Links: BDLS at SCN https://wiki.scn.sap.com/wiki/display/BI/BDLS+-+Logical+system+name+conversion Step 2. Re-generate Screen Containers Transaction - BUSP ~ Generate Screen Containers Often a side effect of client copy ~ dump in BP transaction, 1. Go to Transaction BUSP 2. Activate the radio button ‘All screens’ 3. Execute the report Links 1621119 - Dump DYNPRO_NOT_FOUND in SAPLBUSS in module PBO_START_SUBSCREEN when using transaction BP https://launchpad.support.sap.com/#/notes/1621119 Step 3. Adjust Number Range Buffer Transaction - SMS56 — Administration of the Number Range Buffer For each system after client copy: ‘SM56 — Goto — Number Range Buffer — Reset 9 | entries Enter ett ne Number k WiTerRange Buffer +) Rosot 5 = sorters | hack 8 By auc take—Severres tee Y estes status vaue Nar. No, of Entries 5.000 Gurrento. of Entnes 107 Wax. No, oF Indexes 15.000 Gurrent No. of Indexes 115 See 2.720.152 Bur Cals 201.121 Get Cals 182.108 Server Cals 5533 Database Cals 5.599 Conficts 0 Timeouts 0 and reset buffer area in SAP command line via /$SYNC SAP Step 4. Adjust Distribution model ‘Transaction - BD64 — Maintenance of Distribution Model Add BAP! and Message Type for QAS system instead PROD system Display Distribute ©} RD ED sScheck Models ClsystemView “PrterModelDisplay —}Creste Novel View )Aad [Add Message Type Detibutlon Model Deseristn/Tachnical Name Bustoss Objoct JALE SWC . No short text exits IERP<->EWM Ho short text exits posh te eae 7h sew SFpong abound © & utooundDsivensPEDeivenctange [oa for Cange to Cutbound Delvery ~ FF Receiver Determination: Fiter Active > GB Fiter Group os crang coves for deter evar rduccon > Duthoundoehensre-svetepica unit of deenes > § InbounaDever-DeheyChange __|aaotforCrange to Imacune Detery > & InboundD every. SaveRevix Duotaton oF sound deers > Manufacutnooider scageevaemats acer! stzang for EWM Fas ~ BE sare sa0 Pr. No shortest ents Step 5. Adjust RFC destination ‘Transaction - 8D97 — Assign RFC dest. to Logical Systems Remove assignments for PROD systems. Check assignment QAS systems with RFC address to QAS systems Step 6. Registering a Queue Name Transaction - SMQR - Registering a Queue Name Register queues in ERP/EWM. + cr + DLV + DLW* =o + MDP + WMMB* + WMQF* + wMT* + EWM* etc, RSS feed e SS registration ¢RFC Montor Scheduler Ineaemation ‘Updae (Every 2 Minar: None of AS Group (DEFAULT sabes OF Pacrtse Pispievey queue name ar Number of Rotive Conneezios Node > Scheduler Monitoring | Max, Runtire o Desration fox. foene mane | Attemots ea mee Pause 300 SchaculerMentorna 0 some eo |tiwe aed alae ® [8 @ soon] 300 ore a fo o acca | ace a) macow ae © coo | 200 safer x |o © acca | ca cree» a fo o acca | ace Step 7. Registering a Queue Name Transaction — SMQS - Registering a Destination Register Destinations to ERP/EWM QAS systems: RFC Monitor (QOUT Scheduler) GF BLL peosaton Regsterwtheutacaten Delegation TRECHootor GRFC Monto Jarl soeconn 2 e008 yo ee coh secular montana iis Step 8. Revise Integration Mode! ‘Transaction - SE38 - ABAP Editor Report - RIMODGEN - Variants dlsset Laaieal fenen BRON, foe nach Vasiant RSS feed Like Create Integration Model Oe me Model Name Logical system [ADO Application FiO BATCH Hateral Dependent Objects Materals Pints [MRP Aree Mat! MRP areas 2 NPL Planning Mat ATP Check exer.pant | FFF Classes I & Suoply Area (Pel) coitrects f schedagreements [i Pur.Info Record PPM PDS (ERP) eel] | lS I Storage Loc.stk #/8) q 3 <> Links: Integrate it! SAP EWM and SAP ERP integration via CIF. Step-by-step guide https: //blogs.sap.com/2020/08/17/integrate-it-sap-ewm-%D0%B8-sap-erp-integration-via-cif.-step-by-step- guide/ ‘Step 9. Email Transaction - SOST - ABAP Editor Often a side effect of client copy ~ password resetting in SOST Ghent Identity z Authentication (SMTP AUTH) es | | Password sressncianninsnssaranssascsenseaceisse PT [Eltogon data coped in plantext {IF __Logon Data || ‘Step 10. Adjust multiple SPRO settings In EWM: SPRO - SCM Extended Warehouse Management ~ Interfaces ~ ERP Integration - General Settings Adjust: + Define Own Bussiness System + Define Bussiness System + Assign RFC Destinations to Logical Systems Change View "Assign RFC Destinations for Logical Systems": Overview °% New entries (9 ES Eh BR Eh Assign REC Destinations for Logical Systems Receiver Function REC destination

    You might also like