Hi!

I assume you are reffering to IFS Cloud? Then you should have a look at this section of the tech docs:

http://techdocs/22r2/020_lifecycle/
http://techdocs/22r2/020_lifecycle/060_applying_service_updates/

Best regards
Roman

Thanks Roman, Yes, I am looking at these documents.

Hi @anushakh ,

Please note that with the 22R2  release, there are slight changes in the release update and the service-update processes. Make sure that you are referring to the correct documentation according to the current version of the build place.
 

Furthermore, if you are currently on 22R1/or a previous release, and planning the upgrade to 22R2, please refer to the technical documentation for 22R2. New features are added to the 22R2 Release Update studio and there are some deviations from the previous release-upgrade process.

Hi Shrirantha, The link I am using is 

https://docs.ifs.com/techdocs/21r2/047_lifecycle/090_release_update_studio/050_baseline_env/

https://community.ifs.com/ifs-cloud-faqs-311/what-is-the-process-of-obtaining-a-new-release-in-ifs-cloud-13748

PLEASE correct if I am at the wrong place.

What I got from these links is:

• In the Release update studio, request for release update to get baseline upgraded to latest version (for me, I selected 22.2.4)
• Then Customization upliftment to create topic branch created to get the upgrades in customer solution
• What order delivery does, is confusing-I found it is “to request to create delivery upgrades-from baseline to target branch”

I am stuck at 1 thing

22.2.4 is there in release studio but not in build places, so baseline is visible as 22.2.4 in rel update studio but at lower version in build places.

Hi @anushakh ,

If you could please share the build-place name or the build-place ID, I can take a look into the situation and provide you a detailed update.

If you are upgrading to 22R2 release, please refer to the below technical documentation,
https://docs.ifs.com/techdocs/22r2/020_lifecycle/090_release_update_studio/

Hi 

we also need help in moving our custom operational report to build place.

please let me know steps for 22R2.

Hi Shirantha

sorry for responding on this thread after long as we were trying several things on build place & release update studio. Below is the build place

Below is the release update studio.

We could upgrade the baseline & customer solution in release update studio but not on build place. Also, what’s the significance of both & how are they different. We read many documents but still the question remains.

Hi @anushakh,
 

In the build-place, the customer-solution developers will interact with the master branch of the customer-solution repository. The deliveries and sanity build will be performed on the master branch

During the release-update process, the customer-solution developers will interact with the Release-Update Studio. Same as the build-place, a new branch; release-update will be created in the customer-solution repository. The developers will interact with this branch to complete the release-update process.

At the end of the release-update process is the 'Complete' step. To complete the release-update you need to complete few prerequisites.
refer to the below technical documents

• https://docs.ifs.com/techdocs/22r2/020_lifecycle/090_release_update_studio/110_complete_release_update/#behavior_of_the_release_update_studio_navigator

• https://docs.ifs.com/techdocs/22r2/020_lifecycle/090_release_update_studio/110_complete_release_update/#trigger_complete_release_update_from_the_release_update_studio

During the stage, an automated process will update the build-place and customer-baseline, solution repositories. Once the process is completed, the end-users will not have access to Release-Update studio and the build-place will be upgraded to the new release. The version tag next to the repositories on the build-place will display to new release version number

Best Regards,
Shirantha Herath
https://www.linkedin.com/in/shiranthaherath/

Hi ,

Before completion step,  Delivery Creation failed with below reason even though sanity build is SUCCESS

Framework:    ------------------------------------------------------------------
Framework:                    ------   ERROR!!!   ------                      
Framework:    The following database objects are longer than the allowed length (30 chars).
Framework:    Included are also objects detected as added or modified before this refresh.
Framework:    This can cause the Dictionary cache refresh to fail.
Framework:    Correct the following and refresh dictionary again.
Framework:    ------------------------------------------------------------------
Framework:    METHOD - BASE_DATE_API.ENUMERATE_OUTGOING_CUST_BASE_DB
Framework:    METHOD - CONFIG_PRICE_RETURN_TYPE_API.ENUMERATE_DEFAULT_RETURN_TYPE_DB
Framework:    METHOD - PER_OH_ADJUSTMENT_OH_TYPE_API.ENUMERATE_BASED_ON_POSTING_GRP_DB
Framework:    PACKAGE - ASSEMBLY_TREE_VIEW_STRUCTURE_UTIL_API
Framework:    PACKAGE - BM_SIX_BOX_MODEL_EXPORT_UTIL_API
Framework:    PACKAGE - CLIENT_META_DATA_BUILDER_UTIL_API
Framework:    PACKAGE - CORR_CREDIT_INV_COMMON_UTIL_API
Framework:    PACKAGE - DAT_TEMP_INPUT_CONTAINER_UTIL_API
Framework:    PACKAGE - DAT_TEMP_OUTPUT_CONTAINER_UTIL_API
Framework:    PACKAGE - DCAT_STAGING_INITIALIZE_UTIL_API
Framework:    PACKAGE - DEFENSE_REPORT_OUTBOUND_UTIL_API
Framework:    PACKAGE - DELIVERY_INTERFACE_CUST_ORD_API
Framework:    PACKAGE - DIM_PLANNING_STRUCT_ITEM_TM_API
Framework:    PACKAGE - MOBILE_USER_PROFILE_UTILITIES_API
Framework:    PACKAGE - MX_CORE_ADMON_COMM_LOG_FACADE_API
Framework:    PACKAGE - MX_PART_REQUIREMENT_SERVICE_API
Framework:    PACKAGE - PART_REQUIREMENT_MESSAGE_HANDLER_API
Framework:    PACKAGE - RAISE_FAULT_MESSAGE_HANDLER_API
Framework:    PACKAGE - SCHED_TASK_EXIST_W_P_MESSAGE_HANDLER_API
Framework:    PACKAGE - SCHED_TASK_NEW_W_P_MESSAGE_HANDLER_API
 

Hi @ramank ,

While analyzing the customer-solution repository I noticed that the solutionset.yaml and the translationusage.json files have not been updated during the "Apply Release Update to Customer Solution Repository and Customization Uplifting Process". If you navigate to the above-mentioned files you will notice that they are still on the previous version. This information is available in the technical documentation as well.

https://docs.ifs.com/techdocs/22r2/020_lifecycle/090_release_update_studio/050_impact_analysis_and_cust_upliftment/020_apply_to_sol_and_cust_upliftment/#process (refer to step #5)

To rectify this, please follow the below steps

• I assume that you have the repository clones on your local machine. open the Git Bash tool from the directory to which you cloned the repo and run the belowcommand
  
  git branch -b topic/<enter your branch name> origin/release-update
  
  this will create a new topic branch based on the release-update branch in your remote (solution repository hosted on Azure DevOps)

• Download the translation.usage.json file from the customer-baseline repository release-update branch and copy it to the relevant folder path in the local topic branch.

• Push the topic branch with the above changes to the remote.
  git add .
  git commit -m "meaningful commit message"
  git push origin <topic branch name>
   
• Create a pull request from the newly created topic branch(step #2) to the release-update branch and merge the changes.

• Trigger a sanity build

• Once the sanity build is completed, use the new sanity tag to create a delivery package

Best Regards,
Shirantha Herath
https://www.linkedin.com/in/shiranthaherath/

I raised case in IFS Support also,

they mentioned below even no customization done from our end. 

Hi @Raman Kulshrestha,

We noticed in the pipeline that the delivery has failed due to the database deployment errors.

TASK Kenv-delivery-ru : Mark build as failed for db deployment errors] *********

During further investigation on Build Delivery logs the following error could be noted in _ERROR_install.log

!!!Error deploying file mfgexe/security_manufexecution.ins at 17-FEB-23 05:25:03
!!!Error occurred while executing Plsql Block
BEGIN
IF Database_SYS.Component_Active('MFGEXE') THEN
Fnd_Projection_Grant_API.Grant_All('ShopFloorConnector', 'MANUF_EXECUTION');
END IF;
END;
ORA-20111: FndProjection.FND_RECORD_NOT_EXIST: The Fnd Projection does not exist.
ORA-06512: at "IFSAPP.ERROR_SYS", line 140
ORA-06512: at "IFSAPP.ERROR_SYS", line 364

Could you kindly correct the database code errors from your end and re-order the delivery? Please feel free to contact us if you still receive delivery errors after correcting database code.
The errors you have mentioned in the case were raised during the refreshing of the dictionary cache and that does not lead to delivery failure.
 

Hi @ramank ,

The delivery creation has failed due to the incorrect solutionset.yaml file in the release update branch. Please refer to my previous comment on this thread and follow the action plan to rectify this issue.
 

Best Regards,
Shirantha Herath
https://www.linkedin.com/in/shiranthaherath/

Hi Shirantha,

Completed the steps mentioned above , now delivery is completed successfully but i have one question since we have copied translationjson.xml and solutionet.yaml from 22.2.5 baseline, still my version of customer solution RU and instnace based on delivery is showing 22.2.4

Hi @ramank ,

The minor version change difference between the baseline and solution repositories denotes that the users have performed a service update on the RU studio. 

RU studio job - ale-pz2amad-1676603161
 

The service update process is only partially automated. Only the baseline repository will be updated with the automation platform. Updating the solution repo with the service update is the solution-developers' responsibility. Please refer to the technical documentations do the needful.

technical documentation - https://docs.ifs.com/techdocs/22r2/020_lifecycle/090_release_update_studio/090_applying_service_updates/


Best Regards,
Shirantha Herath
https://www.linkedin.com/in/shiranthaherath/

Hi,

I have created the delivery based on customer solution RU and that created the instance with 22.2.4 , once process completes, we will merge this to customer solution master to update version in build place and we will propagate same to production as well.

I want to know since we have copied solutionset.yaml and translationusage.json from baseline as suggested which is of 22.2.5 , there will be no impact , right?

see the attachment

Hi Shrirantha,

Description:
1.Perform Release Update from Release Update Studio.
2.Completed the merge into Master into build place
3.in Master branch of customer solution and customer baseline folders of different modules are not visible.
they where present before release update.