exporting

[Former Member]

if we are exporting from development system to quality sysem what type of fileas eill be created at the destination?

[aashish_sinha]

Hi,

Integration Repository objects are referred to as design objects and Integration Directory objects are referred to as configuration objects. Together, they are referred to as XI objects. The transport of XI objects consists of an export from the source repository or directory and an import to the target repository or directory, respectively. You can transport XI objects for the following reasons:

- To copy design objects from one Integration Repository to another Integration Repository. The software component version must be the same in the source and target repository in this case. In this way, you provide the design objects of the Integration Repository using export files. SAP Note 705541 gives a brief description of how customers can import this Process Integration Content to their Integration Repository.

- To copy configuration objects from one Integration Directory to another Integration Directory. In this way, you can copy a test configuration to a productive landscape.

Process in SLD:

1.We need to set different transport targets for the required business systems which are used in the scenario objects (ID) of developments. It is just assigning the business system of development to another business system of QA, which is just the replica of dev BS.

2.We need to export the SLD objects from the development to QA SLD. Detailed process can be referred from service market place or SAPHELP.

Process in IR:

1.We need to organise the IR objects in the name spaces properly and ensure that all objects of the name space are correctly available. Ex: Message types, Data types are present in the appropriate name spaces.

2.We need to ensure all the usage dependency objects for the required if any are also available.

3.We can transport the objects at the name space level or SWCV level initially depending on the complexity. We can do it by using the Tools->Export Design Objects Wizard in the development IR. We can see that the file that is getting generated using the wizard has the name File: XI3_0_SWCV Description_Version number.tpz when exported at the SWC level and File: XI3_0_SWCV Description-nsps_Version number.tpz when exported at namespace level. We need to ensure that all the reference objects also are exported together to avoid run time failures in QA box. For Ex: We have generic message types, data types, BPM’’s which are used by all namespaces in the corresponding SWCV. When we are importing the interface specific name spaces into QA IR it has imported successfully as we do not need activate the objects in QA IR. But when we tested it has given run time errors that required message type or data type cannot be found. We re-imported the generic name space objects and usage dependency objects into QA IR, tested the interface and it works fine after that.

4.We can transport each and every individual object of the IR like data type, message type,idoc type,rfc ..etc…by using the same wizard and the file name that is generated when exporting individual objects is File: XI3_0_SWCV Description -objs_VersionNumber.tpz

5.We have to make sure that if any custom RFC modules are developed for JCO calls that required connection parameters have to be changed to point to appropriate sand box. However this can be avoided by using gethostname and getclientname methods in JCO calls.

6.We also need to ensure that if any custom ABAP objects are developed in XI box those requests also have to be transported for avoiding run time failures in QA XI box.

Process in ID:

1.We can export configuration object either at the scenario or service or individual object level.

2.File Name conventions in the ID:

File: XI3_0_directory-selection_VersionNumber.tpz- Export of Individual Objects

File: XI3_0_ScenarioName_VersionNumber.tpz- Export of Scenario Objects

File: XI3_0_ServiceName_VersionNumber.tpz- Export of Service Objects

File: XI3_0_PartyName_VersionNumber.tpz- Export of Party Objects

3.However we can transport at the scenario level initially so that we can have a clear logical grouping of whether all the required individual objects like sender agreements, receiver determinations..etc are present for an interface to work.

4.Unlike IR when we import the scenarios in ID the configuration metadata will be lost and have to be manually entered in the QA ID. For Ex: Parameters like source directory, filename scheme, FTP server will vanish and have to be entered appropriately as required for QA sand box. After entering the metadata we need to activate all the scenario objects in the ID. After successful activation your interfaces are ready for testing.

Process in Runtime:

1.Check in the transaction SXMB_MONI of QA ABAP stack whether the interfaces are working as desired.

Refer this link for more detail. http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/content.htm

Hope this will help you.

Regards

Aashish Sinha

PS : reward points if helpful

[Former Member]

>

> if we are exporting from development system to quality sysem what type of fileas eill be created at the destination?

Here is the best blog to answer your question:-)

Overview of Transition from Dev to QA in XI : /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi

Thanks

Farooq

Edited by: FarooqFarooqui on Dec 17, 2007 5:31 PM