Dear Amol

hope you are fine ?

Assumptions:

1.) both SAP systems of concern are on the same "status of release" (same SAP ERP release)?

2.) both do have the same EHS customizing set up?

Therefore: first you should look to "optimize" your inbond and outbound ALE process, You should optimize the "ALE" process so that you need not to "manipulate" manually in target system to get the IDOC data moved to data base.

Normal set up is as:

IF you have set up ALE scenario and you have distributed once the DG master data then any thing "on top" (changes in data) should be handled automatic. Here you need to set up several reports as jobs (ask ALE experts for guidance) in source and target system.

Now coming back to your "inbound" topic: Proposal:

1.) first check on source system that the data which should be distributed is distributed (check the important message in BD87 (topic of ALE filtering !). E.g. you have set up a new "phrase position" using language " IT" in source system. This should be dispatched to target system (and now customizing ! must be ! the same (same phrase langauges) automatically.

So check first: is the IDOC generated correct in your source system (e.g. using BD87)

2.) check the content of the IDOC in target system. Is the data present as expected?

3.) If (by accident) the "phrase" is "blocked" (in this case() by a user or process ALE can not succeed.

Hope this helps as starting points to look at

C.B.

PS: may be https://archive.sap.com/discussions/thread/3780222 is of interest

same as: https://archive.sap.com/discussions/thread/3713792

Other" related" threads are e.g:: https://archive.sap.com/discussions/thread/3637564 (may be for future use ? and https://archive.sap.com/discussions/thread/3637742

PPS: may be reread: http://help.sap.com/saphelp_erp60_sp/helpdata/en/d0/26bf53d25ab64ce10000000a174cb4/content.htm?frameset=/en/29/20693701e08332e10000009b38f8cf/frameset.htm¤t_toc=/en/ef/27bf53d25ab64ce10000000a174cb4/plain.htm&node_id=88

and http://help.sap.com/saphelp_erp60_sp/helpdata/en/9b/25bf53d25ab64ce10000000a174cb4/content.htm?frameset=/en/d0/26bf53d25ab64ce10000000a174cb4/frameset.htm¤t_toc=/en/ef/27bf53d25ab64ce10000000a174cb4/plain.htm&node_id=89&show_children=false

PPS: the "job owner" of the job on target system side must have the "full EHS" write access (without that the "user" can not move the data to database

Dear All,

Thanks a lot for your feedback on the same. This issue is not yet resolved. Since user was on leave till last week, i took a benefit of ignoring this topic till then. :-)

Now since he is back, taking forward this requirement now. Will update you soon on the same.

Hi Mark,

I have noted your input that Phrase ALE is also required. Thanks for valuable hint.

Regards,

Amol Joshi

Dear All,

Mark was right. Phrase ALE is also required.

I am testing in Development client. I sent idoc from one system to other. Following is the result

Case 1) when it is new phrase ( Phrase is available only in Source System and not in Target System)

ALE works well and in Target system, new phrase got created successfully.

Case 2) phrase text of existing phrase is updated.

here is problem.

e.g. in my case, phrase id CUST-000000000010133 is available in both the systems ( source and target ).

Now, the text of phrase is changed in source system and idoc sent to target but getting below error.

system is not update the phrase text is target system.

Getting follow error - Data record number exists twice. It seems, in this case also, system is considering it as new phrase creation AEL and not the updation ALE...

any guidance to overcome this problem?

Thanking You,

Regards,

Amol Joshi

Just teo hinta from my side:

First: Usually the number range in the target system is set to internal. As you want to Import a RECN with that number it won't work. You have to change the number range to external. (or you delete it in a user-Exit)

Second: You also must delete any Change numbers which are parts of the IDOCs. They're not known in the target system hence booking fails.

Hi Amol,

Please check distribution model languages filter , what are the languages you maintained in distribution model, and the phrase languages configured in both system have to be same.

if configuration is same the go fo

r distribution model

Hi Amol,

RECN number is the we tried by deleting the Phrase, it's working fine but it's not permanent solution. If you have anything can you please share us also.

Thanks

Satya

Hi Amol,

Is the phrase ALE set-up as well? I think you need to have both ( DG ALE and Phrase ALE) in place for this to work correctly! DG ALE only syncs the DG data part - but not the texts of the assigned phrases!

Kind Regards

Mark

Dear Amol

Mark is clearly correct (sorry missed this part of the topic). Clearly the ALE for phrases must be up and running as well to support the DG topic. A "huge" part of the DG master data is stored in database using phrases. During the DG Filling any new translations for identifiers etc. and other stuff should be detected in the phrase part as during the DG filling either a new phrase is generated or an update is happening for some phrase language (as in your case). The ALE will then push (normally) only the new phrase or the new prase language data to the target system and therefore Phrase ALE must be up and running as well (if set up is done properly for phrase ALE).

C.B.

PS: may be check: http://help.sap.com/saphelp_erp60_sp/helpdata/en/ba/75a54180505643b4160c20f5dd1220/content.htm

PPS: I found some old threads of you in contetx of some DG topics. E.g. https://archive.sap.com/discussions/thread/3429385

and

https://archive.sap.com/discussions/thread/1611556

A "different" thread of potential interest https://archive.sap.com/discussions/thread/3238565

Dear Amol

any progress on your side regarding the feedbacks as shwon above?

C.B

Dear Gernot

quite helpful hints. For "Change numbers" if the change number exists in target I would assume that ALE should work (but never tried ALE scenario including change numbers)

C.B.