How to migrate sa scripts smartforms

hi floks,
i have script with z_name . how to magrate this script to smartform .can u any body know's reply me . and do u knows standard smartforms names send me . if any body having documents send me my id [email protected]
thanks in advance ,
suresh

SAP cautions to limit the use of this Migration tool where it is unavoidable.. It is better to design a SMARTFORM from scratch than do the conversion.. PL go through this <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/9d/9599386185c064e10000009b38f8cf/frameset.htm">SAP Help</a>
~Suresh

Similar Messages

  • How to migrate the predefined smartform to the user defined

    hi
    how to migrate the predefined smartform to the user defined

    Hi,
    U have an option from smartform screen to take a copy of the existing smartform.
    In starting screen of smartforms, there is an icon for copy, try with that.
    Regards,
    Sathya Rajkumar.

  • How to Migrate SAP Scripts to Adobe form

    Hi,
    Can yo uplease tell me step by step how to convert/migrate SAP Script to Adobe forms.
    Thanks,
    Rajeev Gupta

    Hi
    Transforming SAP Scripts - > Smartform -> Adobe Forms is the right way.
    refer this thread...
    [Re: Convert SAP Scripts to Adobe PDF Forms|Re: Convert SAP Scripts to Adobe PDF Forms]
    Regards
    Raj
    Edited by: Rajasekhar Dinavahi on Dec 9, 2008 5:25 AM

  • How to migrate SAP Acript to Smartforms

    Hi All,
    We have requirement to migrate SAP Script to smart form, please suggest how to do this?
    Thanks
    Saurabh

    Hi Saurabh
    Just as some guys said you, u need to run trx SMARTFORMS and then Utilities->Migrate from sapscript or (if you've a release => 47): Utilities->Migration->Import Sapscript form
    But remember: only the sapscript will be imported to the samrtform, so only the layout. All code of program used to manage the sapscript will have to be imported manually.
    Max

  • How to get standard program ,script,smartforms all from sap

    hi friends
    how to get standard program ,script,smartforms all from sap.
    thanks&regards
    Babasish

    Hi,
    reports:
    goto se38
    all programs not starting with y or z will be sap std programs only
    same for se71 scripts
    samse for smartforms
    but the use of those will be known when you see the documentation
    for each programme
    for std programs there will be documentation available so that you can understand
    why they have developed that object
    thanks & regards,
    Venkatesh

  • How to find the standard smartform,sap scripts and theur driver programs

    Hi friends,
    can any one tell me how to find the standard smartforms and their driver programs and same for scripts also.
    bye
    sasi

    Hi sasidhar,
    1. Either standard or Y sapscript layouts,
       we can check their standard programs
       in this manner also.
    2. goto se71
       open the layout in DISPLAY mode.
    3.  FORM------> CHECK -
    > TEXTS
    4.  a small window will come.
        click ok (tick button)
    5. Again a new window will come
      which will list out all the DRIVER programs,
      which use this layout.
    regards,
    amit m.

  • How to migrate rtf Templates in XML Publisher ?

    Hi All,
    I want the script so that i can download and upload the RTF files directly from my development instance to my production instance.
    For this i have come across 3 links
    How to migrate rtf Templates in XML Publisher?
    http://download.oracle.com/docs/cd/B40089_10/current/acrobat/120xdoig.pdf
    unable to migrate physical files using XDO Loader utility
    and from here i am running this command from /home/aryan directory
    java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD -DB_USERNAME apps -DB_PASSWORD fnd -JDBC_CONNECTION sharp.apps.com:1522:tst1 -LOB_TYPE TEMPLATE -APPS_SHORT_NAME CUSTOM -LOB_CODE ZEMP -LANGUAGE en -TERRITORY US
    but it is giving me error "ksh: java: not found". could anyone can tell me how and from where i have to run the download and upload command
    Thanks
    Aryan

    Hi Hussein,
    I tried with applmgr also and still for java -version it is giving me error ksh Java not found
    and for which java it is giving me error no java found in different directories path.
    Thanks
    Aryan

  • I have migrated Scrippt as smartform but in pdf O/P chinese chars corrupted

    Hi Experts,
    we have migrated sap script as smartform and modified the driver program accordingly. In print preview  output is fine and no data corruption. we are converting this output as PDF and sending via email. For this we have used FM 'CONVERT_OTF'  and sending an email. In PDF chinese characters are getting corrupted where as other characters are fine. But in pdf chinese character did not corrupted.
    We are in ECC6.0 environment which is unicode enabled and code page is compatable to chinese language charelacters.
    Please help me on this to resolve .
    I am in ciritical situation.
    Thanks in Advance.
    Regards,
    J.P.

    Prakash,
    Clarify which is true here in ur post,
    In PDF chinese characters are getting corrupted where as other characters are fine. But in pdf chinese character did not corrupted.
    So that we can answer your query
    Rgds,
    Sripal

  • How to Migrate Row Level Security Configuration

    Hi Guys,
    Does anybody know how to migrate row level security configuration? I suppose PeopleSoft provided a data mover script, like securityexport.dms.
    Thank you in advance,
    Bob

    Here are two options to achieve what you want.
    A. You can do this by coding, that's if you are ready to. Are you? If yes then try the steps below:
    1. create a security codes table. Say for example
    001 - company a
    002 - company b
    2. create a security table that will list all users and which company they should have access to. You can also implement this by roles.
    3. alter all tables in the application schema to add a security code column. This will be a foreign key reference to table created in 1 above.
    4. update all data in the tables according to which company they belong to.
    5. write a procedure or package that does a validity check whenever a user requests for data. This procedure/package determines which company data the user has access/rights to.
    With this, you should be able to achieve what you want if you do not want to spend on VPD and FGAC. The problem comes where there are users who would have cross access to data from both companies. In this regard, then you have to modify your security table a little bit to handle this.
    B. This option i will admit is not so clean. You can also achieve this by two different views for every table in the application schema. And on each of these views, create a private synonym for every user. For illustration purposes:
    Table name = Employee.
    Create a view employee_a on employee
    create a view employee_b on employee
    Let's say you have users x and y. X has access to employees of company a and y has access to employees of company b. You can now create private synonyms for each of these users as follows:
    create synonym employee on employee_a in x schema.
    create synonym employee on employee_b on y schema.
    This i have not tried but believe should work.
    Hope one of these options serve your purpose.

  • How to migrate the Objects from 3.1c to BI7

    Hi,
    We are in Functional Upgradation.
    How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
    Please help me to doing this....
    regards,
    anil

    BW Upgrade tasks (BW 3.1C to BI 7.0)
    Prepare Phase:
    Task     How-To     Who
    Review BI 7.0 feature lists     Review BI 7.0 feature lists for possible inclusion in developments.     Basis/BW
    Obtain the BI 7.0 upgrade guide     Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
         Basis/BW
    Review all upgrade SAP notes     In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
         BI 7.0 Upgrade notes
         SAP Web Application Server 6.40 upgrade notes
         OS and DB specific upgrade notes
         SAP BW Add-on upgrade notes
    (e.g. SAP SEM, ST-PI, etc)
         Plug-In upgrade SAP notes
         Other notes identified in above notes and/or upgrade guides.
         Basis/BW
    Check DB and OS requirements for the target SAP BW release     Check DB version/patch level and OS version/patch level required for upgrade
         First check the most current information from the SAP BW homepage http://Service.sap.com/BW  -> <SAP BW release> -> Availability
         Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
         Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
         Basis
    Check SAP BW Add-on upgrade requirements     Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
         SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
         WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
         Basis
    Check SAP BW upgrade requirements          Minimum Support Package and kernel levels for upgrade
         SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
         Source system Plug-In requirements     Basis
    Check compatibility requirements with 3rd party software          3rd Party Reporting tools (example: Crystal)
         ETL Tools (example:  Ascential, DataStage, etc)
         Scheduling tools (example. Control-M, Maestro, etc)
         Monitoring tools (example: HP OpenView, Patrol, etc)
         Other OS or DB related tools     Basis
    Check new component requirements for BI 7.0          If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
    The IGS chart migration will also be required after the SAP BW web report conversion.
         If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
         If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0.  (ArcView 8.2?).
         If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
    Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides  -> SAP NetWeaver).
         Basis
    Test and distribute new SAP BW Frontend
              Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
         A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
         After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
         Basis
    Alpha Conversion:
    Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool)      Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
    Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
    Transaction RSMDCNVEXIT
    Check the system status:
         u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
         u201CNo Check yet/Inconsistent Internal Vales existu201D:
    The Alpha converter check has not been executed.
         u201CCharacteristics have Inconsistent Internal Valuesu201D:
    The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
         BW
    Upgrade SAP Note updates     Check for newer versions of your SAP notes for the Upgrade.
    Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
         Basis/BW
    Confirm SAP BW support package, kernel and DB/OS configuration     Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
         Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
         Basis
    Alignment of SAP BW objects within your SAP BW system landscape     Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
    SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
         This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
    Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
         Basis/BW
    Confirm all developments are deployed.     Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
         In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
    For SAP BW developments not already collected in the transport collector, a decision must be made:
    Deploy the developments or wait until the upgrade has completed to deploy.
    o     Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
    o     Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
         In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
         BW
    Implement BI 7.0 Business Explorer Frontend     Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
         Basis/BW
    Pre-upgrade Process:
    Download required BI 7.0 support package Stack for inclusion in the upgrade     Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
         There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
         It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
         BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
    For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
         You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
         Basis
    Apply latest Support Package tool patch     Apply latest SPAM patch before executing PREPARE     Basis
    Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency     Check Database consistency
         Transaction DB02:
    o     Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
    o     Check missing database objects (indices, tables, etc)
    o     Missing indices may identify erred data loads or process problems
    Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
    Note: check for running data loads before executing a repair!
    o     Check DDIC/DB consistency
         Verify database objects and consistency
    (e.g. SAPDBA check for offline data files)
         BW
    Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
         This reduces the numbers of database objects that need to be copied during the upgrade.
         Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
         BW
    Validate your SAP BW Objects for correctness prior to your upgrade     Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
    Note: this test should be repeatable so you can re-validate after the upgrade!
         Ensure that any inconsistencies are identified and corrected
         RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
         Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
         BW
    Ensure DB Statistics are up to date prior to the upgrade          Check DB statistics for all tables.
    Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
         Check DB statistics for missing Indexes for InfoCubes and Aggregates
    o     User transaction RSRV to check      BW
    Check SAP BW Support Package status     Check the status of all support packages (via transaction SPAM)
         Ensure the Support Package queue is empty
         Confirm all applied Support Packages     Basis
    Check all u2018Repairsu2019     Check for unreleased repair transports
         Release all unreleased transports
    In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
         Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
         BW
    Check InfoObject status          Check for revised (modified) InfoObjects that have not been activated.
    All InfoObjects should be active or saved (not activate):
    o     Check all inactive InfoObjects:
    Transaction RSD1 (Edit InfoObjects),
    click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
    Modified InfoObjects are denoted by yellow triangles!
    o     Determine if revision should be activated or removed.
         'Reorgu2019 or u2018Repairu2019 all InfoObjects
    This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
         Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
         BW
    All ODS data loads must be activated.          Activate all inactivated ODS Object requests.
    All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
    o     Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
         BW
    All Transfer and Update rules should be active          Check for inactive Update and Transfer Rules
    o     All update rules and transfer rules should be active or deleted.
    o     Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure.     BW
    All InfoCubes should be active          Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
    o     All InfoCubes should be activated or deleted.
    o     Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
         BW
    All Web Report objects should be consistent prior the upgrade.          Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
    o     For Original release SAP BW 3.x:
    A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
    Please see SAP note 484519 for details.
         BW
    Backup your system before starting PREPARE     Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
         Database admin
    Address any instructions/errors generated by PREPARE          Address any issues listed in log files Checks. Log generated by PREPARE.
    o     Repeat PREPARE until all checks are successful.     Basis
    Complete any Logistic V3 data extractions and suspend V3 collection processes          Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
    o     The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
         Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
         BW
    Complete any data mart data extractions and suspend any data mart extractors          Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    o     The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
         Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
         BW
    Check that your customer defined data class definitions conform to SAP standards          Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
    o     Check your data class definitions as detailed in SAP Notes 46272 and 500252.
    o     Incorrect data classes could create activation errors during the upgrade.
         BW
    Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
    For more information see SAP note 308533 (2.x) and 449891 (3.x).
         This reduces the numbers of database objects that need to be copied during the upgrade.
         Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
         Basis/BW
    Backups!     Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
    Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
         Database Admin
    Before Execution:
    All SAP BW administration tasks should have ceased          Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
    The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
         Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
    - timing depends on the type of upgrade selected
         Basis/Admin
    Remove unnecessary SAP BW temporary database objects     Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
    For more information see SAP note 308533 (2.x) and 449891 (3.x).
    - timing depends on the type of upgrade selected
         BW
    Check system parameters     Check OS, DB, and Instance profile parameters.
         Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
         Check for any DB specific parameters for BI 7.0
         Check for any new OS parameters     Basis
    Check Database archiving mode     Turn database archive log mode back on if it was disabled during the upgrade!
         Database Admin
    After Execution:
    Check the systemu2019s installation consistency     Execute Transaction SICK to check installation consistency
         BW
    Check the system logs     Perform a technical systems check.
         Example: Check system and all dispatcher logs (inc. ICM logs)
         Basis
    Apply latest executable binaries     Apply the latest 6.40 Basis Kernel for all executables
         Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
         Basis
    Review BI 7.0 Support Packages for follow-up actions.          Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
    o      Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
    o     Follow any required instructions identified in the SAP Notes
         Basis
    Apply latest patches          Apply the latest SPAM patch
         Apply any required support packages that were not bound into the upgrade.
         Basis
    Apply additional BI 7.0 Support Packages
    (if required)          SAP recommends that customer remain current on SAP Support Packages.
         Review SAP Notes for all SAP BW Support packages applied in previous task.
    o      Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
    o     Follow any required instructions identified in the SAP Notes
         Basis
    Resolve any modified SAP delivered Role issues      If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
         Review and implement SAP note 569128 as required     Basis
    Configuring Information Broadcasting EP/KMC Connections
         If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
         Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
         Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
         For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
         Basis
    Re-check SAP BW Object and consistency     Execute RSRV to check SAP BW Object consistency
         Repeat tests that we executed prior to the upgrade.
         Validate results      BW
    Check InfoCube views for consistency     Check consistency of InfoCube fact table views
         It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
         BW
    Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks          If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
         The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
         It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
    o     Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
         Check that all other Source Systems are active.
    o     Activate as required.     Basis/BW
    Check SAP BW Personalization is implemented     (SAP BW 2.X upgrades will have performed this in the previous task).
    Validate that personalization has been activated in your SAP BW system.
    Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
         Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
    Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
         To activate highlighted Personalization, click Execute.     BW
    For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
    Convert ODS secondary indexes to new standard     For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
    Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
         Re-create all indexes in the ODS Object definition screen in transaction RSA1.
         ODS indexes must conform to the new naming convention
         BW
    Converting IGS chart settings
         Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
         Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
    o      Test via transaction RSRT
         Execute the conversion process as directed the BI 7.0 upgrade guide.
         Note: This step is required for all BI 7.0 upgrades     Basis
    Backup your SAP BW system     Perform a full database backup (including the File system)
    Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
         Database Admin

  • Plm in migrating sapscript to smartform

    hi gurus,
    i can migrate the sapscript to smartforms through t.code smartforms -->define the smart form name -->utilites(menu) -->migration -->import sap script form, then save after that if u go for syntax check it shows the somany syntax errore saying that 'x' is not defined or something is not defined.
    do i have any other way to migrate sapscript to smartform to avoid these(above mentioned) sytax errors?
    waiting for reply,
    seshu.m.

    hi,
    pls refer to this sdn thread.
    https://forums.sdn.sap.com/click.jspa?searchID=286390&messageID=2667564

  • How to find SAP Scripts to Prepare functional Spec

    Hello SAP GURUS,
    Could any one help me out how i can find Sap Scripts,or SAP programs to create a functional spec for Billing, user want a writing at the bottom of billing,
    Could any one help me out
    Thanks
    Edie

    HI,
    Pls go to T-Code : NACE. Inside this choose the application as V3 and press the button Output Types in the application toolbar.
    If your client is using std output type then choose the type: RD00 and press on processing routines. Here in this screen, we can find out the script/smartform name along with the driver pgm name.
    The same procedure is applicable for customized output types.
    Hope this helps.
    Regards,
    JLN

  • How to debugg a script when the Required out put is like Fax  or email

    Hi this is Durga Prasad i have small doubt in scripts can any one clarify that one plz  normally we will do that one with activating debugger but when a special requirement is like fax or e mail    how we will do that one
    "how to debugg a script when the Required out put is like Fax  or email"
    Thanks in advance
    Durga Prasad.

    Hi
    DEBUG Smartform:
    1) One way to debug smartform is to debug the Function Module of that smartforms.
    If you want to debug particular smartform node that the solution would be,
    insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint.
    So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
    2) SFTRACE can be used for debugging SMARTFORMS.
    Read More here.
    http://help.sap.com/saphelp_erp2004/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
    script
    1). Use Tools - Word Processing - Layout Set (SE71). Enter name of layout set and then Utilities - Activate Debugger.
    It is of no consequence which layoutset you enter when selecting the SAPscript debugger. (Menu path: Tools-Wordprocessing - Forms, Utilities - Activate Debugger) The next layoutset called will invoke the debugger.
    2). Another way to set the SAPScript debugger is to run program RSTXDBUG.
    When you debug Print program it is same as you debug any other ABAP program. While when you debug SAPScript, you actually debug the code ( scripting) you have written SAPScript Form.
    As per ur question there is nothing new with script debugging,
    it is same as normal report debugging...
    SMARTFORMS DEBUGGING
    For smartforms debugging you can do this.
    1. Execute the smartform (execute button in SMARTFORMS transaction)
    2. Take the generated function module and display it in SE80.
    3.Find the smartforms Elements (text elements, windows, code lines, loops) in this and set Soft break points.
    Correct name is SMARTFORM_TRACE. You have lots of options for adequate analysis
    Tcode - SFTRACE
    Re: How to Debug a Smartform
    Debug of smartform and sapscript.
    Debugging SmartForms
    Debugging of a subroutine pool.
    SCRIPT
    There are 2 separate kinds of debugging available when you try to debug scripts.
    1. Debugging the print program : This is the normal debugging we do for our report programs.
    2. Debugging the script itself : You Can debug a SAP Script by activating debugger in two ways:
    a .In SE71->Menu->Utilities->Activate Debugger, then debugger will be get activated and when your print program is executing Script Debugger will be in active and you can proceed with your debugging.
    b. Goto se38-> RSTXDBUG ->Execute this same as going thru in se71-> Menu, now debugger will be activated.
    refer to the link below
    http://www.howforge.com/how-to-debugging-sapscript-form
    Look at the BLOG here, it is well explained
    /people/sudheer.junnuthula2/blog/2007/01/09/script-debugging
    Regards
    Anji

  • How to migrate sharepoint 2010 infopath form to sharepoint online.

    how to migrate SharePoint 2010 infopath form to SharePoint online.

    Hi Partha,
    You use powershell script to migrate infopath forms from SP 2010 to SP Online. But you need to be careful about external connections used in infopath forms(web service connections etc.) because they might required to be changed. So, for data connections,
    use of Data Connection Library is a preferable way or you can write a powershell script to update the data connections also.
    You can find the sample script from the below url:
    https://drive.google.com/file/d/0B_mYrpgMRd3IbHdpZkNBLVNhd1k/view?usp=sharing
    Best Regards,
    Brij K

  • How to migrate BPM 11g server to another BPM 11g server

    Hi All,
    There is no change on BPM version (BPMN Editor 11.1.1.3.0.6.84 )
    just simply a physical migrate, changed application server, DB and server domain/IP
    Now we met questions when migrate DB date, there are four schemas DEV_MDS、DEV_SOAINFRA、DEV_ORABAM、DEV_ORASDPM, cannot used including install config settings, could not be used any more, could not be started.
    Is there any guide of how to migrate just user data please?
    Thanks for any help!
    Regards,
    Katherine

    Migration of environment should really be done through backup tools that ensure a consistent point-in-time view of the data. We recently had a need to use import/export for an environment. I'll post those notes here hopefully save some time if you have to use this approach. But I'll emphasize again that a backup/restore model is the better way to go.
    What we did
    We took an environment that had a small set of BPM processes and exported the data from the three core schemas.
    •     PS2_MDS
    •     PS2_SOAINFRA
    •     PS2_ORASDPM
    We then loaded that data into another domain, started the server, and interacted with the composites that had originally been deployed in another domain.
    What we didn’t do
    •     Export complex composites. We didn’t have access to things like AIA applications
    •     Export large amounts of data
    •     Test a broad set of features. We did use Workspace to create roles, view dashboard, and interact with task lists.
    What we learned
    We believe this confirmed the basic assumption that data can be exported from one BPM/SOA environment, then loaded and run in another environment. However the issues around user privileges, starting queues, etc, highlight the need to test the process in a broader context.
    Tools Used
    Data Pump
    Data Pump is an import/export tool provided by Oracle. A summary of features can be found at:
    http://wiki.oracle.com/page/Data+Pump+Export+%28expdp%29+and+Data+Pump+Import%28impdp%29
    SQL*Plus
    Used to run scripts
    Setup
    Create Users
    The data pump export will include privilege information in the export. And the data pump import will create users in the target database (assuming sufficient privileges for the user running the import). However we found that some roles related to AQ were not granted during the import. To resolve that issue we created scripts to pre-create the schema users and grant required privileges in the target environment.
    TODO:
    1.     Review the required privileges to see if there are data pump options that would resolve this
    2.     Verify that there are no additional privileges needed by applications in the target integration environment.
    Create Output Directory
    Data Pump needs to have access to the file system from the database.
    Make sure that the output directory is writable by the DB process.
    From SQL*Plus:
    create directory dbexport as '/scratch/ dbexport';
    grant read,write on directory dbexport to system;
    Export Data For Selected Schemas
    The Data Pump tool supports providing a list of schemas to export as part of a single operation. In this test case we exported the following core BPM schemas to a single file. The commands are in the do_exp.sh script.
    •     PS2_MDS
    •     PS2_SOAINFRA
    •     PS2_ORASDPM
    TODO:
    1.     Verify space required for the target database to ensure that there is sufficient space to export the data.
    Import Data into Target Schemas
    Data Pump supports mapping schema names and table spaces as part of the import specification. In this case we used the same Oracle instance, so the schemas were mapped to new names. The PS2 prefix was mapped to XYZ.
    Note that the OID transform property is required to avoid conflicts with existing object Identifiers.
    impdp system/welcome1 DIRECTORY=dbexport DUMPFILE=bpm.dmp transform=oid:n \
    REMAP_TABLESPACE=PS2_MDS:XYZ_MDS \
    REMAP_TABLESPACE=PS2_SOAINFRA:XYZ_SOAINFRA \
    REMAP_TABLESPACE=PS2_IAS_ORASDPM:XYZ_IAS_ORASDPM \
    REMAP_SCHEMA=PS2_MDS:XYZ_MDS \
    REMAP_SCHEMA=PS2_SOAINFRA:XYZ_SOAINFRA \
    REMAP_SCHEMA=PS2_ORASDPM:XYZ_ORASDPM \
    TODO:
    1.     Check the log for errors. The only errors we saw were related to trying to build stats on empty indexes.
    2.     Identify any other schemas being used
    3.     Verify if any other transform operators are needed
    Post Import
    Start Queues
    SOA infrastructure makes use of queues in the DB server. While the queue structures were created, they were not started as part of the import. The start_queues.sql script starts the queues.
    TODO:
    1.     Verify if there are any other queues that need to be started/configured
    2.     Verify if there are any other Stream/Queuing configuration tasks needed
    Update Data Sources on WLS
    Assuming an existing installation of SOA, the datasources need to be updated to use the new schemas.
    Start Domain and Verify Logs
    It’s important to check the admin and managed server logs for errors related to composite instances and MDS operations.
    Verify Composite State
    Log into EM and ensure that the state of instances is consistent with the prior state.
    Verify Application Roles and Role Mappings
    Since the composites are loaded from MDS, there will be no deployment to create application roles. If the environment is using LDAP or DB, then the validation is to check the mappings through Workspace. If the old environment used a file store, then you’d have to crate the role mappings through Workspace.
    Verify Workspace Operations on Existing Instances
    Verify that task list operations and dashboards are functional.

Maybe you are looking for