9 Replies Latest reply on Feb 20, 2018 7:51 AM by JohnGoodwin

    Planning outline migration question

    3644742

      Hello,

       

      When we migrate dimensions via LCM from source to destination, only the dimension members are getting merged in the Planning application and the members are not removed (the one's which are extra) in destination application.

      Is there a way we can remove/delete these members in our migration process?

       

      Thanks.

        • 2. Re: Planning outline migration question
          adnan645

          delete whole dimension and then import it

          • 3. Re: Planning outline migration question
            3644742

            That will be lot of maintenance.

            Members will be in web forms and so we cannot delete all the members at once.

             

            Also, deleting each time clears the data as well.

            We are looking for a way to just update (includes adding/modifying existing/deleting) the dimension members from source to destination.

            • 4. Re: Planning outline migration question
              Kyle Goodfriend

              If you are using PBCS

              1. Navigate to Overview / Dimensions
              2. Select Import, then click Create
              3. Select the dimension and make sure you click the clear checkbox.

              Note:  My experience with this so far is that it works a little different than on-premise and doesn't clear the members that aren't in the load file, but clears them then reloads them.  This will fail if you have any members in forms, which you likely do.  What I have done, and this isn't a great option, is to have the automated load put all the members to be removed under a parent named something like delete entity members.  These can be removed manually, or even with a Groovy calculation by an admin, and that can be automated.

               

              That said, this could be updated from when I last used it, so it might is worth a try.

               

              If you are using on-premise, and you are trying to automate this, you will be using the outline load utility.  That has a parameter on the command line that will remove all members that don't exist in the import file.  It has been 3 years since I have done an on prem implementation, but I believe my memory is correct.

              • 5. Re: Planning outline migration question
                JohnGoodwin

                First of all it would help if you provide whether it is on-premise or Oracle cloud, also the version if it is on-premise, it stops having to assume.

                 

                Whether it is cloud or on-premise then LCM / migration uses the same method and format to load dimension, which behind the scenes is the OLU (Outline load utility)


                Prior to 11.1.2.3, LCM used a different method which replaced a dimension so source and target matched, from 11.1.2.3, LCM changed to the OLU method where the default operation is to merge, you can delete but that requires a change to the operation column in the source file. Unfortunately there are no options to change the overall behaviour at an LCM / Migration level.

                 

                Moving on to the import dimension option which once again uses the OLU, you can still use the same LCM files for the metadata as they are the same format.

                 

                If it is cloud you have the option to clear members, for on-premise it is a little different in the standard user interface as there is only option to delete all members.

                 

                The option to delete all members uses the /R option through the OLU - "Delete all members of the load dimension before performing the load"

                 

                This is not much use as it will try to delete all members before loading so you will be hit with errors straight away because the members will associated with things like forms.

                 

                If you are on 11.1.2.4 you have another parameter available in the OLU which is /IDU - "Delete unspecified members not explicitly specified in the load. Members not explicitly specified in the input source will be deleted from the Planning outline on load completion". This is the same as the clear members option in the cloud.

                 

                This parameter will only try to delete members which are not in the source file, so this is more inline with a replace method.

                 

                There will be still errors is members are associated with forms, if I remove two members from a source file which exist in the target and are associated with forms. then use the OLU with the /IDU parameter:

                 

                Deletion of unspecified load member "901" failed: Deletion of member "901" failed because the member is used in a form or data validations associated with a form.

                Deletion of unspecified load member "902" failed: Deletion of member "902" failed because the member is used in a form or data validations associated with a form.

                A total of 0 members were deleted in the Delete Unspecified Load Members operation.

                Planning Outline data store load process finished. 137 data records were read, 137 data records were processed, 137 were accepted for loading (verify actual load with Essbase log files), 0 were rejected.

                 

                The rest of the members will be loaded unlike when using the /R parameter which tries to delete them first.

                 

                The above errors also verify the cloud is using the same method.

                Anyway, If I remove any associations to the members and reload then this time the members are automatically deleted.

                 

                A total of 2 members were deleted in the Delete Unspecified Load Members operation.

                Planning Outline data store load process finished. 137 data records were read, 137 data records were processed, 137 were accepted for loading (verify actual load with Essbase log files), 0 were rejected.

                 

                If you are on 11.1.2.4 you also have the option of the simplified interface which has the same clear members option as the cloud.

                After checking the planning app log you can see it has run the OLU with the /IDU parameter:

                 

                Submitted command line: /-C /D:Entity /DL:comma /-F /DF:MM-DD-YYYY /A:Vision /K /T /IDU

                 

                So for 11.1.2.4 on-premise if you are looking to delete members automatically on target then take your metadata files from the source LCM exports or export them through the UI, then either use the simplified planning interface or use the OLU with the /IDU parameter against your target.

                 

                Cheers

                 

                John

                • 6. Re: Planning outline migration question
                  3644742

                  Hi John,

                   

                  We are on 11.1.2.3.500 version.

                  Yes, the LCM process is just merging the members in the migration process and not deleting the members.

                  Are you saying that we can still delete the members (in destination app) during the migration  -- but that requires a change to the operation column in the source file?

                   

                  Or, is there any other way?

                  Thank you.

                  • 7. Re: Planning outline migration question
                    JohnGoodwin

                    Yes you can delete members using the operation column in the source file, the available values are:

                    update  < this is the default if not populated.

                    delete level 0

                    delete idescendants

                    delete descendants

                    • 8. Re: Planning outline migration question
                      3644742

                      Thank you. I have never tried updating/deleting this above way.

                      Is there some place where I can find the format/steps on loading the members?

                       

                      Thanks.

                      • 9. Re: Planning outline migration question
                        JohnGoodwin

                        You can load the file through the UI (you can see from my previous screenshot - import metadata from a file) or the Outline load utility which is fully documented - Working with the Outline Load Utility

                        The properties are explained in the documentation, an example for account is Account Dimension Propertiesl