4 Replies Latest reply: Feb 29, 2012 2:34 PM by Tridip Chakraborthy RSS

How to transport configuration in E-sourcing

Naveena Shetty
Currently Being Moderated

Hello Experts,

 

I am new to E- sourcing,

 

Could you please help me in knowing, How can we transport the configuration of e-sourcing from Development to Production system.

 

Cheers

 

Naveena Shetty

  • Re: How to transport configuration in E-sourcing
    Vijay Vadgaonkar
    Currently Being Moderated

    Dear Naveena,

     

    I also new for this. If u got more details please do forward on spike_in_heart at yahoo dot com

     

    vijay

    • Re: How to transport configuration in E-sourcing
      Ankush Mittal
      Currently Being Moderated

      Hello Navenna,

       

      In E-Sourcing we have a option for transport QAS to PRD.

      but you need to do all basic configuration manualy. like upto uploading initial workbook and integration steps etc in PRD.

      After that there is a mechanisum for transporting buisness Object to production.

      you need to create object for import (in OML file), which you can import to Production

       

      Hope this helps

       

      Regards

      ~Ankush

    • Re: How to transport configuration in E-sourcing
      Tridip Chakraborthy
      Currently Being Moderated

      Hi Naveena and Vijay

      Please see the documentation below for an excerpt on how to do the transport migration SAP provides something called as SAP OMF Object Migration facility toolIf you have the license for ESO, you can actually go ahead and check for this

       

      This is how it works, lets take an example

       

      The SAP Object Migration Facility (OMF) is designed to enable the movement of objects from a test or staging environment to a production environment. The process for utilizing the Object Migration Facility requires definition and modification of objects in a test or staging (source) environment followed by creation of an Object Migration Archive (OMA) used to import the

      objects into the production (target) environment. The recommended usage of this facility is to complete object definition and implementation on the source system, followed by creation of an archive containing all datasets, which is then imported into the target system. Once this full import is completed, establishing the set of objects common to the source and target systems, partial exports may be created and used to update the target system with changes made to the source system

       

      Note, however, that the use of partial exports requires careful consideration of the

      interdependencies between objects. For example, suppose you have defined a new RFx template

      object in a source system that uses a Unit of Measure that was defined since the time of the full

      object migration from the source to the target system. Also suppose that you want to migrate the

      new template from the source to the target system. In this simple case, migration of the

      template without migration of the new Unit of Measure will fail, since the reference to the Unit of

      Measure will not be resolved during import of the template.

      The solution in this case is to create an export package of both RFx Templates and Units of

      Measure. When this package is imported, the Units of Measure will be imported prior to the RFx

      Templates, so that when the template is imported, the reference to the Unit of Measure will be

      resolved and the import will succeed.

       

       

      Implementation Note:

      One object relationship which is encoded in the system but not reflected in the reference guide is

      a relationship between the Extension Definition and Dynamic Class Metadata classes of objects. If

      either of these object classes is added to an export package, both object classes must be added.

      Export Data:

      You can export master data from SAPE-Sourcing in the form of OMA files, an XML format used

      for object migration. For details on object migration, see Exporting objects for migration.

      This section describes how to create and edit an export package.

      Field Help for Export Package Header page

      Display Name: Type a name for the export package.

      Description: Type a description of the export package.

       

      Creating an Export Package:

      You export master data from SAP® E-Sourcing in the form of OMA files, an XML format used for

      object migration. You can create an export package, described by one or more sets of

      instructions, for immediate or future export. For details on object migration, see Exporting

      objects for migration.

      You can also export the same package multiple times as needed. For example, you might create

      a package and manually export it weekly or monthly.

      Steps to Create an Export Package:

      - Click Setup in the toolbar at the top of the page.

      - In the Import and Export Tools section of System Administration, select Export Data from the

      drop-down list and click OK.

      - On the Export Package List page, click Create.

      - On the Header page, fill in the fields for basic export package information.

      - Under Instructions, click Add to build a set of instructions for an export package.

      - Follow the prompts in the wizard to finish adding the package. For more information on this

      wizard, see Export Data.

      - Optionally, repeat steps 5 and 6 to create additional sets of instructions if multiple types of

      data should be exported at the same time.

      - Under Exports, click Add to begin the export. If you have created multiple sets of

      instructions, the data indicated by each set will be exported.

      - In the New Export Package Header page, click the Save button in the toolbar. The export

      begins in the background. You cannot make changes to this Header page.

      - Click the Close icon or use the breadcrumbs to return to the Export Package Header page.

      - Click the Document button in the toolbar and select Refresh. The status of the export

      appears in the Exports table.

      Exporting an Existing Export Package:

      You export master data from SAP E-Sourcing in the form of OMA files, an XML format used for

      object migration. You can create an export package, described by one or more sets of

      instructions, for immediate or future export. For details on object migration, see Exporting

      objects for migration.

      You can export an existing package multiple times as needed. For example, you might create a

      package and manually export it weekly or monthly.

      To Export an Existing Export Package:- Click Setup in the toolbar at the top of the page.E-Sourcing Object Migration Tool

       

      - In the Import and Export Tools section of System Administration, select Export Data from the

      drop-down list and click OK.

      - On the Export Package List page, click the export package you want to run.

      - On the Header page, click the Edit button in the toolbar.

      - Under Instructions, optionally click a link to see the set of instructions for the export

      package.

      - Under Exports, optionally click the Edit icon to see details about the more recent export.

      - Under Exports, click Add to begin the export.

      - In the New Export Header page, click the Save button in the toolbar. The export begins in

      the background.

      - Click the Close icon or use the breadcrumbs to return to the Export Package Header page.

      - Click the Document button in the toolbar and select Refresh. The status of the export

      appears in the Exports table

       

      Edited by: Tridip Chakraborthy on Dec 2, 2009 9:54 AM

       

Actions