Hi Team
The purpose of the document is to share the information if anyone facing issues/errors on the below topics/areas. Please find the information and solution.
1797459 - Permanent parameters not defined for UCBATCH01 or UCBATCH11
Symptom
During the execution of report UCBATCH01 or UCBATCH11 (task execution in the background) the error message UCS0038 appears: "Permanent parameters not defined".
Cause
Report UCBATCH01 and UCBATCH11 were slightly extended due to other changes in the application.
Resolution
The user who executes this report has to have maintained permanent parameters in the tables UCMP000 / UCMP020.
- Please maintain and save the permanent parameters in transaction UCPP with the user who executes the report UCBATCH01 or UCBATCH11,
- If maintenance of the parameters is not possible in transaction UCPP due to user restrictions (e.g. the user is a system user for process chains), please copy the appropriate parameters in table UCMP000 and UCMP020 of another user to the given user. This workaround has to be applied only once, the error will not appear anymore for this user.
1879392 - Duplicate company codes exist in consolidation group after transport
Symptom
After transport with T-code SE01, in T-code UCWB->Master Data->Consolidation Units->Company, dupliate company codes exist in consolidation group.
Reproducing the Issue
- Go to T-code UCWB -> Master Data -> Cons unit.
- Right-click ->choose "Transport ", then execute and import the transport request.
Cause
It is due to wrong customizing without setting the flag 'Hierarchy Structure' when creating transport request.
Resolution
- Go to T-code UCWB -> Master Data -> Cons unit.
- Right-click -> select Transport, set the flag 'Hierarchy Structure' , then execute and import the newly created transport request in target system.
2029841 - Interpretation of First and Last Consolidation Dates for a Combinations of Consolidation Units in a Matrix Scenario
Symptom
You need detailed clarification about, how the first and last consolidation dates are considered and calculated by the system for a combination of cons unit.
Resolution
The consolidation unit CU1 is consolidated in the consolidation group CG1 mentioned as below:
Yr First | Per First | FCEP | Yr of Div. | Per. Div. | DABP | Div. Acc. (merge) |
2013 | 3 | | 2014 | 3 | | |
The profit center PC1 is consolidated in the profit center group PC1 mentioned as below:
Yr First | Per First | FCEP | Yr of Div. | Per. Div. | DABP | Div. Acc. (merge) |
2013 | 6 | | 2014 | 9 | | |
The combination of consolidation unit CU1 and profit center PC1 is defined as follows:
Company | Profit Ctr | FCEP | Yr of Div. | Per. Div. | DABP | Validity |
CU1 | PC1 | | | | | X |
For a combination the system takes into account with the higher first consolidation date and the lower and end consolidation date, if there is no further restriction made in the combination of consolidation units.
In the described example this means, that the combination CU1/PC1 is valid from 2013/6 to 2014/3.
However it needs to be mentioned there, that the explicit definition of the first and last consolidation dates for the combination of consolidation units fully overwrites the above described inheritance-logic.
Regards
Rajesh SVN
