on 06-26-2014 12:12 PM
Hi,
I have few questions on replication of Hirarchies & groups:
2. I am creating PCTR via single processing & then release of Edition is replicating the PCTR. However, i am the using the collective Processing for creating PCTRG & PCTRH along with the assignment of PCTR to it. But still my replication is not happening for PCTRG. This is the process that I am following.Is this the correct approach or I should go for addition of Custom Profit Center Group attribute right from the Data Modelling- UI Config -SMT Mapping?
3. What is the Idoc for Hierarchy which I can configure?
4. Can We replicate Hierarchy through IDOC?If Yes then How? If not then what is the alternative way to do it?
I would really appreciate you if you could provide me an answer or a hint.
Best Regards,
Kaustubh
Hello Kaustubh
IDOC replication work properly for Cost center group / hierarchy. Check the following setting -
1. Check whether you have configured global company code for replication
2. Check business system - add the business system - i.e 158 for CC etc
3. In outbound parameter add - send_delta_info and package_size_bulk respectively
4. Define the business object settings properly
5. Check your data model - whether the business system is assigned or not.
With this setting, entire hierarchy with group and CC gets replicated. No need for SMT mapping unless you have custom fields.
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,
I have done the testing of replication for both Groups & Hierarchy for PCTR. The replication is happening smoothly. But I am not understanding that when I check the same PCTR in KE53, it is showing the standard PCTRG.
If I check in KCH1 t-code, I can see the replicated GROUP , HIERARCHY & PCTR assigned properly at node & sub node level.But not the same case for KE53.
Even if I check in KCH5N T-code, below the Standard Hierarchy, My created PCTR & PCTRG is not coming. What is that thing which I am missing?
Can you please help for the same?
Best Regards,
Kaustubh
Hello Kaustubh
This is typical problem with IDOC. We are too facing this issue for PC. CC its working fine.
Just make sure following -
1. You group and hierarchy validity periods are same in KCH6N and KE53.
2. ECC and MDG hierarchy match 100%
3. Don't check the data atleast for 20-30 mins after replication. If you are in change mode then replication won't work.
Try this and let me know. Otherwise you have to go with SOA replication.
Kiran
Hi,
most probably you are not using the correct workflow template for changing the hierarchy. IDoc based replication of a hierarchy change requires that MDG sends two IDocs: one for the hierarchy, one for updating the master data. This is due to the fact that the standard ALE inbound for hierarchies updates only the hierarchy but not the master data. This inbound does not belong to MDG, so we cannot change the same. As mentioned by Kiran, the behavior of the SOA replication is a different one. In that case the inbound belongs to MDG so that we can update both the hierarchy and the master data with a single message.
Please refer to the MDG-F configuration guide, section workflow templates for more details.
Best regards
Michael
Hello Michael
I have used std workflow - 40 for replication. SOA setup is working fine but when we use IDOC, we are facing lot of issues. The main problem I found is validity date of MDG and ECC hierarchy. If there is a difference in validity period, then the replication fails (even though the DRF message is green) but when the validity is exactly same it works.
My understanding is that IDOC delete the entire hierarchy and replaces it with MDG. In that case still it check for validations same as in SOA?
Kiran
Hello Kiran,
w.r.t. IDoc: it's clearly stated in the configuration guide, that:
SAP delivers the standard workflow template WS72100012 for the approval process. This enables you to forward the change request as a work item to the appropriate processors. The status of the change request is automatically updated in the background. The template is mandatory for cost
center hierarchy or profit center hierarchy maintenance if the objects are distributed using IDocs to the MDG client systems.
If you are not following the same, I cannot help.
Best regards
Michael
Hi Micheal
Facing same issue .
I defined Replication Model ZF with outbound implementation 1112 for replication of CCH.
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.
Hi Kiran
It is done but still does not works for me .You can referce Thread for detail reply and please provide your comments on that MDG-F Data replication for CCH using IDOC
Hi Michael
For MDG 7.0 SAP delivered as out of box workflow templatw WS75700040 for Cost Center Hierarchy with new CR Type CCH1P1 (Single Processing) and not WE72100012. Did you need to update this for MDG 7.0?
For creation of Standard Hierarchy in MDG, is we need to update assignment of controlling area afterwords (After replication of MDG CCH)?
If we create MDG CCH then how it idenfies it is Alternative hierarchy or standard hierchy?Any differation indicator?
Hi Sanjay,
the predefined content delivered by SAP is considered as template that might need adjustments according to the actual customer project. We cannpot predict everything what our customers might do or not.
Hierarchies in MDG are identified by the actual root node (hierarchy name). For CCH and PCH there should be one root node having the same value as the standard hierarchy being defined for the actual controlling aresa. Other root nodes are alternative hierarchies.
Best regards
Michael
Hi Michael
Thank you for reply.
In MDG 7.0 we can create CC by single processing as well as processing mutiple objects.
If we create CC by single processing, after replication into target system we can see there is no Standard Hierarchy assignment seen in KSH3 but we can see MDG created CC by Single Processing in KS03.
Where as If we created CC in ECC by KS01 we can see it's assignment with Standard Hierarkey as Top node.
Any particular reason for this?
Hi Kaustubh, In DRFIMG customizing, check the replication model. You need to have a separate replication model to replicate group hierarchy.Check the Outbound Implementation and the Outbound Implementation class. The outbound implementation should have PCTRG and PCTRH entity type and the SMT mapping should also be maintained. Regards, Reema
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sanjay, Sorry for the late reply. SMT, Service mapping tool is a tool which enables to fill target structure using the source structure. It allows conversion of enterprise service data to SAP- internal format and vice versa. Here one can maintain mapping of the entities. Simple mapping- Relation between source field and target field is 1:1 Transformation method: relation is m:n. For more details you can refer the sap help page. Regards, Reema
Hi Reema
In my system I am unable to see any structure gerenation for 0G data model.
As per my understanding SMT is required for Reuse mode only and not in case of Flex mode.
Though no DRF structure for data model 0G is there I am able to replicate GL,CC.PC and CE but facing issue for replication for their groups and hierarchy's. Can we say that as no DRF structure generated for 0G model it creates issue for Group/Hierarchy replication? Then why not for CC,PC and CE.I already made all settings as mentioned by Kiran in above thread.
Hi Sanjay, SMT structure will be existing for entities and not data model. For replication of Group/Hierarchy you need to do as below steps. 1. Change request type: with entity type cctr, cctr group and cctr hierarchy. 2. Assign processor to workflow steps of the change request type. 3. DRFIMG- set ups 4. IDOC/SOA/PI set ups. DRFIMG--> Define Outbound Implementation- Check which outbound implementation is used for Cost center group hierarchy. The outbound implementation should contain entities( Cost center Group and cost center hierarchy)This is where you have to specify the SMT structure maintained for those of group and hierarchy. Also the outbound Implementation class of group is separate than that of the CCtr. Hence you need to have a separate outbound for the replication of group. Apart from this the, you will need a replication model for the outbound implementation . If still this does not solve your issue. please let me know. It will be more helpful if you provide exact error message. Regards, Reema
Hi Reema
No strucutre for Data Mode i means no structure for any entity type for Data Model 0G also.
You said that 'The outbound implementation should contain entities( Cost center Group and cost center hierarchy)' does it means I need to assign 1112 for CCH and 1102 for CC in same outbound implementation?
I already raise seperate question for this in MDG-F Data replication for CCH using IDOC
Also ;Hence you need to have a separate outbound for the replication of group. Apart from this the, you will need a replication model for the outbound implementation' is bit cofusing for me as I aready mention Outbound Implemetion only for 1112 but as per your above sentence we need to add 1102 in same outbound implementation
Hello Sanjay and Reema
1. SMT mapping for standard set ip is not needed for CC / PC replication
2. There was a bug in standard program. After applying the note -
2042236 the issue got resolved
3. Create separate replication model for CC and PC.
With the setup you have mention, the replication should work. Apply the mention note and let us know.
Kiran
Hi sanjay, Outbound Implementation 1112(Cost Center Group Hierarchy IDoc) Specify Entity: CCTRG and CCTRH Mapping: USMD_IDOC_0G_COGRP1 for both the entity 1102: Cost Center IDoc Replication Model: for 1112 will process your group- hierarchy Replication Model: for 1102 will process only cost center. Regards, Reema
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.