Note 1667160 - Consulting Note on BPC10 NW Granular Transport

7/15/2019 Note 1667160 - Consulting Note on BPC10 NW Granular Transport

http://slidepdf.com/reader/full/note-1667160-consulting-note-on-bpc10-nw-granular-transport 1/4

02.07.2013 of 4

SAP Note 1667160 - Consulting Note on BPC10 NW GranularTransport

Note Language: English Version: 11 Validity: Valid Since 15.04.2013

Summary

Symptom

You encounter problems when transporting Planning and Consolidation

contents using granular transport in Planning and Consolidation 10.0.

Other terms

Transport, Granular transport, Troubleshooting

Reason and Prerequisites

This note summarizes the solutions and best practices to overcome common

known issues during Planning and Consolidation 10.0 transports and will be

continuously updated.

Solution

First check if the corresponding notes have been applied to the system orthe fix has already been included in the deployed support package when you

encounter some of the transport problems listed below:

Notes included in Planning and Consolidation 10.0 NW SP02:

Note 1583684 - Fix the problem that if a dimension is deleted and then

re-created in the source system, the dimension import would fail in

creation mode on the target system

Note 1584175 - Fix the problem that the data checker will not be executed

if the BUI folder import fails

Note 1585591 - Fix the problem that when transport deletion of model and

dimension, if the deletion of dimension fails, the deletion of the relevant

model would also be rolled back


Note 1597557 - Eliminate duplicated warning message when releasing

transport request

Note 1598011 - Fix the problem that the import of environment would be

executed twice if in UJT_TRANS_DEL there is content to be deleted

Note 1598046 - Fix the problem that the journal parameters would be reset

in the target system if they do not exist in the target system

Note 1599006 - Add a check for the dimension structure before importing the

dimension member

Note 1599009 - Add a check for the work status when importing flag for

controls

Note 1605847 - Add a check for the dimension list in a model when importing

work status lock dimension setting


Note 1612085 - Fix the problem that a Drill-through parameter is lost

during the transport

Note 1616057 - Fix the problem that the BPF template name is not unique

after the transport

Note 1616446 - Add a check for the dimension list in a model when

transporting a journal template

Note 1616647 - Fix the problem that the dimension name in the target system

is capitalized after the transport

Note 1625496 - Fix the problem that a duplicate environment content wouldbe exported when running transaction UJBPCTR

Note 1626549 - Fix the problem that transporting deletion of a non-existed



02.07.2013 of 4


dimension in the target system would cause a dump error


Note 1643143 - Process the dimension during the transport if it is detected

that the structure of the dimension hierarchy is changed

Note 1643623 - Fix the problem that importing a dimension fails because of

a reference dimension check

Note 1645050 - Fix the problem that the state of a dimension is not set to

'to be processed' when a dimension attribute is added during the transport

Note 1648048 - Remove the unexpected 'Loop warning' message when

transporting Planning and Consolidation content without any dimensions

Note 1648376 - Set the state of dimensions to "processed" after the

transport if no further processing is needed when it contains a reference

dimension

Note 1656600 - Fix the problem that the parameter for the comment length is

not transported


Note 1662950 - Fix the problem of importing a member with attribute largerthan 255 bytes

Note 1665647 - Fix the problem that a user cannot export files with the

same name under the DM data file folder

Note 1666295 - Fix the problem that importing master data with hierarchy

level greater than 20 fails

Note 1671541 - Fix the problem that the member formula of a new dimension

transported to the target system is not expanded automatically

Note 1680704 - Fix the problem that when master data import fails, the

rollback process dumps

Note 1682385 - Fix the problem that when 2 dimensions have member formulas

referring to each other, the transport fails

Notes related to ensuring technical name consistency of BW objects:

Note 1689814 - Support to keep the technical names of info-cubes to be

consistent between source system and target system after transport

Note 1823400 - Support to keep the technical names of dimension attributes

to be consistent between source system and target system after transport

Besides the notes listed above, refer to the following guidance to fix

those common transport problems:

1. When you encounter authorization issues during the import of an

environment, such as, you have no authority to create BUI related

persistent resources, the ADMIN team is not created in the target system,or the tasks in the security profile are missing, do the following checks

first:

(1) Make sure you strictly follow the Planning and Consolidation

installation guide to configure the transport RFC destination and check

transaction RSTPRFC that the right user has been assigned to handle the

post-processing of the import.

(2) If the BW system level is below or equal to BW730 SP02, make sure BW

note 1537619 has been applied.

2. When you encounter errors such as "payload does not exist", "failed to

export document view" during the export, read BUI Note 1657427 and fix the

BUI resource in your environment first before exporting the content.

3 When you encounter export errors such as "cannot find document/directory"



02.07.2013 of 4


or "data not found in table [table name]", check if the content still

exists in your system. It is possible that the Planning and Consolidation

content is deleted by an end-user after you collect them to transport

objects and before you release the transport. If it has been deleted,

re-collect the transport objects to a new request and release it again.

4. When you enocunter export errors while exporting data files under the

Data Manager data file folder and get an error message such as "Cannot find

generated document content in DB Table", make sure the Data Manager data

files are uploaded by using the standard Data Manager Upload interface in

UJFS or by using the upload data feature in the EPM Add-in. If not, remove

the files and upload them in the correct way.

5. When you encounter the problem that the web report cannot be moved

across web folders during the transport, apply BUI Note 1586448.

6. When you encounter an error in the transport log saying: "Errors

occurred during post-handling RS_AFTER_IMPORT¡The errors affected the

following components: BW-WHM-MTD" and meanwhile there is relevant runtimeerror:"MESSAGE_TYPE_X" found in transaction ST22, which is raised from ABAP

Program:"CL_RSDMD_UPDATE_MASTER_DATA", check the number range of the

problematic info-objects of the BPC dimension and all its attributes which

may cause such transport failure.

To do this, open the detailed log of runtime error:"MESSAGE_TYPE_X" in

transaction ST22, search for string

"ME->IF_UJT_ENTITY~DS_ENTITY-ENTITY_ID". Double click on the search result

and find the dimension name under the search string. Then go to transaction

RSA1 and fetch the technical name of the info-object of this dimension and

the technical names of all the info-objects corresponding to the attributes

of this dimension. Run transaction RSRV, open folder "master data",

double-click on "Compare Number Range and Maximum SID", and enter the

info-object technical names you have collected in previous step. Then click

on "Execute" to perform the check. If any warning or error is found by this

check, select the problematic infoobject and click "Correct Error" in the

same transaction. After that, re-execute the test on the infoobject and the

inconsistency between the number range and the max SID should be resolved.

Re-import the request to verify if the import of the master data works

after resolving the possible conflicts mentioned above.

(End)

Header Data

Release Status: Released for Customer

Released on: 15.04.2013 14:46:51

Master Language: English

Priority: Correction with high priority

Category: Consulting

Primary Component: EPM-BPC-NW-TRA Transport

Secondary Components:

EPM-BPC-NW NetWeaver Version

Valid Releases



02.07.2013 of 4


Software Component Release From

Release

To

Release

and

Subsequent

CPMBPC 800 800 800

Related Notes

Number Short Text

1682385 Transport fails when formulas refer to each other

1680704 Fail to rollback importing dimension member

1671541 Member formula not expanded after transport

1666295 Fail to import master data with hierarchy level > 20

1665647 Cannot export files with same name under DM data file folder

1662950 Fail to import member with atrribute larger than 255 bytes

1660062 Business Planning & Consolidation 10.0 NW SP06 Central Note

1657427 Export of BUI Resources fails

1656600 Fix side effect caused by 16170831648376 Set relevant dimensions as "processed" after transport

1648048 'Loop warning' message when transporting content

1645050 The state of a dimension is 'processed' after transport

1643623 Import dimension fails because of reference dimension check

1643143 Need to process dimension when importing in delta mode

1626549 Transport deletion of non-existed dimension causes dump

1625496 Duplicate environment contents exported in program UJBPCTR

1616647 Fix dimension name on target is capitalized after transport

1616446 dims of model unchecked when transporting journal template

1616057 BPF template name not unique after transport

1612085 Drill Through parameter lost during transport

1605847 Work status dimension must exist in model

1599009 Check work status when importing VALID parameter-controls

1599006 Property consistency check when importing dimension member

1598046 Need to reset value on target system of jouranl parameter

1598011 Import environment twice if content exist in UJT_TRANS_DEL

1597557 Eliminate duplicated warning message when release request

1586448 Relationship between folder and subfolder issue of library

1585591 Deletion dimension roll back issue

1584175 Data checker will not execute if BUI folder import fails

1583684 Fail to transport Dimension

1537619 Changes to function group SROLETOOLSBPC

Note 1667160 - Consulting Note on BPC10 NW Granular Transport

Documents

Transcript of Note 1667160 - Consulting Note on BPC10 NW Granular Transport