cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to GL account replication with company code

Former Member
0 Kudos


Hi

I am using MDG7.0 SP02.I am uable to do replication of GL account but unable to replication with company code means SKA1 is fine but not updated SKB1.

I alread\y define global (Corss) company code and tested through BD50 and find it is working Fine.

But in MDG 7.0 when we create GL aacount in single proceesing as we can add new CC in company code UIBB.

But after replication found that only GL account withchart of account is replicated (segmentE1SKA1M) not company code (SegmentE1SKB1M).

In SLG1 it issues message like below

Filter object F_GLACCASS - GL Account CompanyCode Ass.: end result offiltering 1

Message no. DRF_FILTER034

and found that no company code assignment in details as below

Can you tell reason behind this?

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member465215
Discoverer
0 Kudos

Hi,

Check the inbound error message where
you are trying to replicate the GL.
Also, check if the field status group in MDG and replicating system is in sync.
Use the common field status group for company code extension.

Thanks,
Mrinal

dharamveer_gaur2
Active Contributor
0 Kudos

Hi Sanjay,

Did you find any solution ? I am also facing similar issue while GL Master replication Company Code

segment E1SKB1M not populating.

I have already gone through

and verified Key Structure.

Thanks in advance.

Regards,

Dharamveer

riaan_oosthuizen2
Participant
0 Kudos

Hi Sanjay,

We had a similar issue and the cause was Authorization. Try to test it with SAP_ALL access.

Regards

Riaan

Former Member
0 Kudos

Hi Riaan

Thank you for reply. But unable to digest user needs SAP_All access then we have to provide SAP_ALL authorizations to business also which is not recommanded.

I am able to do replication in ECC but not through MDG integreation.

I found that even though I provided company code value in MDG in Replication IDOC does not considered segment E1SKB1M (only E1SKA1M) in WE02.Any reason for this?  

former_member206605
Active Contributor
0 Kudos

The problem is with IDOC segment. Raise this with SAP. We too faced similar issue and implemented correction note. Check in service market place. There are couple of notes already available for similar issue.

Kiran

Former Member
0 Kudos

Do you know which SAP note?