on 07-10-2014 3:02 PM
Hi
In MDG-F we are able to create and activate CCH and active data in MDG area only.
As data replication shoud immediatlely happen into ECC (as we maintained in Edition) we maintained outbound implimation as 1112 ( Replication through IDOC) and assign to replication model (In same replication Model we are able to replicate GL account and Cost Center as well)
But for Cost Center Hierarchy it is not working .
SLG1 logs says as per below
Here it says CCH uses SOA but we maintained IDOC,Is CCH replication is not possible through IDOC with message type COGRP1.
Secondally we maintained ZG replication model but it says DIRECTLY replication Model . Any Clue?
Hello Sanjay
Please make sure following -
1. Create a separate replication model for each entity
2. For CC replication outbound parameters are - 1112 and 1102. You have to give sequence number also. 1112 - Seq 1 and 1102 - Seq 2. For PC hierarchy its 1132 and for PC its 1122
3. outbound parameters make sure you have added - PACK_SIZE_BULK - 1 and SEND_DELTA_INFO - Y
4. Define business object settings - 158 - COSMAS / 895 - COGRP1 / 896 - COGRP6 and 229 for PRCMAS.
Check these settings for CC and PC and let me know.
Kiran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kiran
No luck for me.
I defined Replication Model ZF with outbound implementation 1112.
But in Outbound parameter getting error as
Entry 1112 PACK_SIZE_BULK does not exist in DRFC_PARO (check entry) and found that DRFC_PARO table does not exists in my system.
So I defined both outbound parameters as per you in DRFV_PARO. But unable to put parameter value 1 and Y respectively for that.But still it is not working for me.
Diagnosis
You want to replicate change request directly (using enterprise services). When change requests are directly replicated (regardless of the current settings in DRF Customizing), the replication is always done completely. This is because the system normally cannot determine an unambiguous delta set of data.
But we are doing replication for CCH with message type COGRP1
Guess process followed by me may be incorrect, so giving process as well.
Is the procedure is correct?
Hello Sanjay
Let me give you the step by step details - check all these points and let me know.
1. In your data model, check all the business objects are properly updated
2. Data model - Define entity type to be used for business object type - add all the entries i.e BO type and all.
3. Generate structures - DRF for IDOC based replication entry is present for your Cost center and PC
4. CC and PC edition contain - H / G and CCTR or PCTR
5. CR type - you have already done it.
6. Now replication model - Create separate replication model. Don't mix GL or CC or PC in one.
7. CC - Assign outbound imp - 1102 and 1112 - give proper sequence. cost center group idoc - 1 and then cost center idoc - 2
8. Outbound parameters - PACK_SIZE_BULK - value - 1 and SEND_DELTA_INFO - value Y
9. You can maintain these values through SM30 in the table for each implementation
10. Business object settings -
BO 158 - COSMAS
229 - PRCMAS
892 - GLMAST
895 - COGRP1
896 - COGRP6
899 - GLCORE
11. Under define business settings - define technical settings for business system - select your business system and check all the defined all the BO's properly and system filter - NO TICK.
With this setup your replication must work.....
Kiran
1. for - DRFC_PARO - go to SM30 and give table name - click on maintain. The you get a pop-up asking for implementation object.
2. There is no 897 BO type - for CC its 158 and 896
3. If you create a hierarchy in MDG its standard. Check your config for alternate hierarchy in ECC.
4., The problem seems to be with assignment of BO type. And v. imp create separate replication model. Don't combine all in one.
Hope this info is useful to you.
Kiran
Hi Kiran
Thanks for reply.
Below are current system setting for data model OG (SAP Delivered). Can you cross confim for the below steps
1. In your data model, check all the business objects are properly updated
Here not sure why BO Type 897 used for both the entity types (CCTRG and CCTRH)
2. Data model - Define entity type to be used for business object type - add all the entries i.e BO type and all.
Same as above. (Is there any need to update data model OG which is SAP delivered?)
3. Generate structures - DRF for IDOC based replication entry is present for your Cost center and PC
Here there is no Data Model 0G (As it is Flex mode). Do you want to create new 0G and generate structure for 0G?
But one question, why is working properly for replication of GL account and Cost Center even though no Business Object Setting not maintained previously?
4. CC and PC edition contain - H / G and CCTR or PCTR
Got it.
5. CR type - you have already done it.
Already done.
6. Now replication model - Create separate replication model. Don't mix GL or CC or PC in one.
Seperate replication model ZF is created with outbound implementation 1112 for CCTRH in DRFIMG.
Do you mean need to define seperate distibution model in BD64 for ALE customization?
7. CC - Assign outbound imp - 1102 and 1112 - give proper sequence. cost center group idoc - 1 and then cost center idoc - 2
Do you want to include CC in ZF replication model only and I defined seperate ZG Data Model for CC and it is working fine?
8. Outbound parameters - PACK_SIZE_BULK - value - 1 and SEND_DELTA_INFO - value Y
Done.
9. You can maintain these values through SM30 in the table for each implementation
Done for DRFV_PARC (Needed for Outbound Implementation) and DRFV_APPL_PAR (Needed for Outbound Implementation Value)
10. Business object settings -
BO 158 - COSMAS
229 - PRCMAS
892 - GLMAST
895 - COGRP1
896 - COGRP6
899 - GLCORE
Done
But one question, why is working properly for replication of GL account and Cost Center even though no Business Object Setting not maintained previously?
11. Under define business settings - define technical settings for business system - select your business system and check all the defined all the BO's properly and system filter - NO TICK.
Done.
Currently we are focusing only on CCTR,CCTRG and CCCRH, so PC structure is not maintained.
Tried with one Controlling area for which no Std Hierarchy is created in ECC but getting same SLG1 error log\ as per below
Hi Kiran
1. for - DRFC_PARO - go to SM30 and give table name - click on maintain. The you get a pop-up asking for implementation object.
Done.
2. There is no 897 BO type - for CC its 158 and 896
There are BO Type 897 for entity Type CCTRH/CCTRG
3. If you create a hierarchy in MDG its standard. Check your config for alternate hierarchy in ECC.
Is it possible to import Standard Hierchy defined to ECC already into MDG?
Is It possible to create alternate hierarchy through MDG then?
4., The problem seems to be with assignment of BO type. And v. imp create separate replication model. Don't combine all in one.
Done.Defined seperate ZF Replication model for CCTRH
Hello Sanjay
Not sure how to maintain alternate hierarchy. Need to check. But the hierarchy in MDG is standard. One more point when you use idoc based replication, system deletes entire hierarchy in ECC first and then replace it with MDG hierarchy. There is no delta update. Make sure you have back up of your hierarchy in ECC.
You can also download the hierarchy in MDG from ECC. See my document - how to load the finance master data in MDG.
Kiran
Hi Kiran
As per our FI consultant every controlling area have only one standard hierarchy. It yes, then it is only one time activity to create CCTRH per controlling area from MDG, Correct?
Also tried to generate sructure for 0G data mopdel but It asks for package. Which pacakge we have to select and why this is not delivered by SAP.
also unable to get your sentence Make sure you have DRF entry for idoc ?
Do you mean for SAP delivered IDOC structure in above path for 0G data model also ( Can we say that we need structure generation for every data model irespective of reuse area as for 0G it is Flex mode, reuse area-MDG generated tables even after activation)?
Can we say that some issue in activation of MDG 6.1?
Reasons:
Hello
For CCH even though I mentioned Replication method for outbond 1112 for replication model ZCH in DRFIMG, It is not replicated into ECC (It is stored as active into MDG Tables).
As per SLG1 log it shows below error
You want to replicate change request 000000000214 directly (using
enterprise services). When change requests are directly replicated
(regardless of the current settings in DRF Customizing), the replication
is always done completely. This is because the system normally cannot
determine an unambiguous delta set of data.
Also it says below
If applicable, check the Customizing settings for the replication in DRF
Customizing (the replication model and the assigned outbound
Implementations) as to whether a delta replication (by means of
parameter SEND_DELTA_INFO = X) is defined there, even though a complete
replication (SEND_DELTA_INFO = ' ') is defined.
Also check the data (content) that is to be replicated using the current
edition or the current change request. To do this, you can use
respective service functions (such as Edition Comparison or Display
Change Requests), which are located, for example, in the service map of
the work centerFinancial Master Data Governance.
Can any body comment on this?
Your configuration is perfect. My experience is that CCH (cost center hierarchy code) can NOT be replicated alone from MDG-F design perspective. In other words, it has to be replicated with a structure (CCH + cost center group code + cost center code).
This behavior is different from how it is done in ECC. I know in ECC, we can go ahead and create a standalone CCH and add more leaves over time.
Please let me know.
LUO
Hi Luo
Do you mean we can not create CCG/CCGH/PCG/PCGH with single processing in MDG as seperate node for each one.
In ECC it is possible (KSH1).
I want to use Collecting processing only when I want to assign my Hierarchy srtucture for this.
If Yes, Then why SAP provodes seperate change request type for CCG/CCGH/PCG/PCGH with UI
Hi Kiran
Thank you for reply!
Let me explain what I am doing step by step in MDG 7.0 SP02 so that it is easier for you to explain me if any thing is incorrect.
Cost Center Hierarchy "XCO2/0001", Field "Cost Center Group": Cost center TT02 is not part of the standard hierarchy for all exitsting MDG CCTR. Any Reason for this
Sanjay,
Sorry for the late response. What I am saying is that you can create CCG/CCGH/PCG/PCGH with Single Processing in MDG. But you won't be able to replicate CCG/CCGH/PCG/PCGH over into ECC at that point of time. To replicate a new CCG over into ECC, you will need to using MDG-F Create/Process Hierarchy for Cost Center Group to establish the relationship of this newly created CCG and its parent CCGH. Once this is done, you are able to replicate. Likewise, PCG works the same way.
LUO
Sanjay,
Let me be clear. To replicate a new CCG over into ECC OKEON standard cost center hierarchy, you will need to use MDG-F Create/Process Hierarchy for Cost Center Group to establish the relationship of the newly created Cost Center and the newly created Cost Center Group and Cost Center Group Hierarchy. the relationship will be saved in a MDG-F change request and it will go through the workflow. Once the last step in the workflow is performed, it is ready for replication. I forgot to mention cost center in my previous response.
LUO
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.