Query For Master Agreement Extension Fields

[Former Member]

Hi Exeperts,

I'm trying to write query on Master Agreements Extension Definition for  migration

. Please any suggestion on this

[former_member227405]

Hi Rao,

Write an query  under Query definition with the Syntex:

SELECT 

<%RESULTS%>

FROM

<%SCHEMA%>.FCI_CONTRACT T1

LEFT OUTER JOIN

<%EXT_TABLE(contracts.Contract)%> EXT1 ON

T1.OBJECTID = EXT2.PARENT_OBJECT_ID

Now what ever You want to get as a result fro Extension ,Look the Extension Schema and select the proper value and add to the result field.

Regards

Peeyush

[Former Member]

Hi Peeyush,

Thanks for giving replay,but my query is regarding Extensions only(Like extension definition query).My query is when I move Extensions from development to quality I want to transfer single objects(Project Extensions,Maser Agreement Extensions) . Any suggestions on this.

Regards,

Eswar

[former_member227405]

when You move query to Quality nothing will change in query level but While transporting you shoud choose Single object and choose the perticualr Tpy"Query definition".

Regards

Peeyush

[Former Member]

Hi Peeyush,

I need Master Agreement Extension Definitions query only

[former_member190023]

Hi Eswar,

You can do that by creating a custom OML query (based on FCI-ExtensionDefinitions-OML) and restricting it to only MA.

Warning! - query is using an 'UNION' statement. Make sure you restrict both queries otherwise this will cause great damage to your system, to such an extent it might require a DB restore.

You can confirm that all underlying objects are transported correctly by comparing the object count from the custom OML query with the results from the standard one.

Bogdan

[Former Member]

Thaks Bogdan Toma,

I'm working on this development,If any query I will let you know.

[Former Member]

Pakkurti,

To expand on what Bogdan said, this is potentially a very dangerous operation. It has caused us to have to restore our dev environment.

From my experience, if you use OMA file transfers, it's VERY important to make sure you only make Extension Definition AND Value List Type changes in only one environment and transport them from there in a one-way direction.

You may be thinking, "this is bad practice-- we always go Dev -> QA -> Prod." But it can actually occur easily between a sandbox and dev. Seems like common sense at the time, make your experimental changes in sandbox so you don't trash up your dev system, then export them over to dev-- BUT if someone else makes changes in dev in the interim, this problem can occur.

The way SAP recommends is workbooks but it also has problems of it's own since it's entirely manual and easy to enter invalid values accidentally. Also version control of the workbooks is very important.

Hope this helps.

Mike