1. Go to your GB Test site > Admin section.
2. Download the JSON file and name it. (Ex: TO-BE-PRODGB.JSON), then:
   1. Replace all realm name to your Production realm name. 
   2. Replace http://TESTREALMNAME-T.procurement.ariba.com with the complete URL for your site.
   3. Find and replace all occurrences of ‘testrealmname-T’ with your production realm name.
   4. Remove the ‘-T’ because this is the production realm JSON. 
      
      
3. Go to your GB production site (NOT Test) > Admin section.
4. Download the JSON file and name it. (Ex: OLDPRODGB.JSON), then:
   1. Search for the word PopularPage. About 3 to 4 lines above it, you will need to copy and make a note of the uniqueName.  (Ex: "Yxx5a1039f-ed3e-4579-b518-710fc218fdax1xxx")
5. In the file intended for Production:
   1. Search for the word  PopularPage again. In this part of the code, just 3 to 4 lines above, replace the uniqueName value with the one that you copied from the file downloaded in step 4. 
   2. Search for the word  NodeID. If no results, move to step 9. If you do see results, go to the “NodeID Test/Production Comparison” section below.
   3. Go to the Admin section >Upload to add your intended Production file.

Refer to the Guided Buying Admin Guide for the following:

• If you configured Policies in your GB Test site and need to copy them.
• To maintain parameters in GB Production site as that of Test site by copying the configuration.
• If you wanted to add translations for the titles and descriptions of your landing pages and tiles to support users in multiple languages.
• If you wanted to load Translations for your policies in GB Production site.
• If your organization has implemented the concepts and controls of ‘Community’ on GB Test site and want to implement the same on your GB Production site.

Additional Considerations

1. Image files:

1. Some images could take few minutes to show up. Limit your upload to 10 images at one time for best performance.
2. Manage Using UI > Upload images from the upload option on the right-hand side. See the tile’s image selection area.

2. Steps to load forms into your GB Production site:

1. Log in to your GB Test site.
2. Go to Home > Options > Admin.
3. In the Landing pages section > Download landing pages and save the JSON file to your computer.
4. Remove everything from the file except the JSON for the form tiles you want to migrate to production.
   Note: Do not include the JSON that maps the form tile to one of your landing pages. For example, your file should look something like this if you're migrating only one form to production:
   

   [{"uniqueName":"6948abd8-e779-4e30-b141-9083eed2fc79",

   "title":"Creative advertising", "description":"Request quotes from suppliers for creative advertising.\n", "commodityCode":"45", "currency":"USD", "language":"en", "type":"Form", "imageUrl":"assets/images/footer_SAP_Ariba_pos_blugld.png", "targetUrl":"resource/6948abd8-e779-4e30-b141-9083eed2fc79",

   "tenantId":"p2pTeCustProd-T"}]

5. Go to Admin > Forms > Forms to Production. Browse to locate your file.
6. Click Upload to import your file.

Results: The forms you migrated are added to the Manage Forms section of your production site.

Next Steps: Add the form tile to the landing page file in your production site. Link the form tile to a landing page in your production site to make it available to users.

3. Check and Change commodities of tiles

Check and change any commodity code that you need to, in the JSON file or directly make changes on the Mange Using UI option of GB Admin site.

4. NodeID Test/Production Comparison

If the Catalog Hierarchy Node ID in your file for Production is different from what you want to use in your Production GB site, then follow the steps below to find and replace the Node ID:

1. On the dashboard > click Manage > Core Administration.
2. Choose Catalog Manager Hierarchy Editor.
3. Click File > Export Hierarchy from the dropdown. You have the option to open or save the catalog hierarchy XML file.
4. Open the XML file in a text-editing program, such as Notepad++.
5. Find the ProductCategoryBranch or ProductCategoryLeaf that corresponds to the category you want to associate with a landing page tile.

Ex- You are configuring a landing page tile for toner for printers and copiers. You want all the available toner products to show up when users access this tile. After you download the catalog hierarchy file, you search the file for "toner" and find the following ProductCategoryLeaf:

<ProductCategoryLeaf nodeID="NI.146.1146072102234">

<Description xml:lang="en-US">Toner</Description>

<Description xml:lang="x-ariba-I18N">@ariba.catalog.hierarchy/Toner</ Description> <Description xml:lang="en-US">Toner</Description> <ProductCategoryConditions> <IsIn> <Field>ClassificationCode.unspsc</Field> <Literal>44103103</Literal> </IsIn> </ProductCategoryConditions> </ProductCategoryLeaf>

To show all the right products when users access the toner tile, you need to map the tile to node ID NI. 146.1146072102234. 6.

Make note of all the node IDs that you plan to use to configure your landing pages.

5. Maintain Commodity Subset for ad-hoc

1. Get hold of the ad-hoc commodity code ZIP file that you used in your GB Test site and know location of where it is saved on your computer.
2. Go to the Admin section of your GB Production site.
3. In the Adhoc classifiers for commodity codes section > Update commodity codes.
4. Click Upload file and choose the ZIP file you saved to your computer.
5. Click Upload or Upload all to import the list of commodity codes.

To get an access to the Guided Buying Administration Guide from Connect.ariba.com, please use this URL: https://help.sap.com/viewer/855d3e61ce304b1cb81987bdc5322911

Note: If you have an active Production realm and do not want users to access GB in Production yet then DO NOT activate GB in Production realm.

[There might be situations where users are assigned to the Re-direct group/parameter in P2P and will be accessing Production GB instead of Production P2P all the time.

So, until and unless the GB Test site has thoroughly been tested and signed-off for move to Production, DO NOT get GB Features activated in Production realm ]