cancel
Showing results for 
Search instead for 
Did you mean: 

ALE distribution of SDS - no set to "historical"

Former Member
0 Kudos
256

Good morning again,

we are facing the following problem: we are distributing SDS from one SAP central EH&S system (ECC 6.00, EhP 5) to another SAP logistic EH&S system (4.7 110). When we distribute SDSs the current existing versions on the logistic system are not automatically set to status "historical".

We already checked the generation variants and the "set historcal automatically" flag is set.

Does anybody have an idea how to solve this issue?

Thank you in advance for your support!

Best regards,

Christoph

Accepted Solutions (1)

Accepted Solutions (1)

christoph_bergemann
Active Contributor
0 Kudos

Hello Christoph

your assumption is, that be distributing of the new version of WWI document in the target system the "old" version is set to historical as well (because the GenVar does have this set up). Therefore the "update" is down only in target system.

First of all you should check something in your recent setup: If the WWI document will be set up in the target system in "theory" the "status" list must be generated as well. I am not sure if ALE is here really doing it right. Example: in your source system User A started generation, and then may be user B released the document. This information is in some sense part of the "info" on the document level. Now please check if in the target system the "history" is shown (with ready, released etc.). The "user" which is linked to this information should be in my opinion the "batch" user of the inbound processing. The same user should be linked to any other "header" info of your document in the target system (as long as "user" information" is of interest); I am really not sure how SAP standard handles that (we are not using it like that) but you should as well check if the "released" date on document level in target ist the same as in source system and is not the "recent day".

(PS: may be this link could "help" as well: http://www.consolut.com/en/s/sap-ides-access/d/s/doc/YD-EHSENVP_ALE_REP_DOCMAS_WAIT); may be read cross this thread as well: http://scn.sap.com/thread/2036612

http://www.se80.co.uk/sapfms/e/exit/exit_saplcvale_001.htm

http://scn.sap.com/thread/1477601

On top I assume that we are not talking abound ALE of reports of type "MSDS" but prepared as "inbound" because by standard normally you have information attached to the document in a document class.

Could you please conform the following;: in your target system you have two document which are released after ALE distribution?

That means

Spec NUmber      GenVar     language     Status released     version2.0 (only an example!)

Spec NUmber      GenVar     language     Status released     version1.9 (former WWI document)

Spec Number etc. is always the same.

C.B.

PS: may be debugging in target system might help: I assume that during inbound processing the func. module C1F3_REPORTS_UPDATE should be called to set the old document historic (check other function modules of the same function group as well)

Former Member
0 Kudos

Hello Christoph,

thank you very miuch for your very valuable information.

Let me start from the end: we are NOT distributing Inbound documents, we are distributing SBRs (report category MSDS) due to the fact that we don´t have any customer data on the central EH&S system. So we need to distribute the documents as SBRs to be finally processed to SBEs in the report shipping process.

We are distributing two IDocs, the DOCMAS and the REPMAS. The first problem was that some REPMAS have been on the target system prior to the DOCMAS - this is handled now by different ALE settings for both IDoc types.

I can confirm that we have identical data on both systems for the Spec ID, GenVar, language and status. Everything is working properly with the exception of the status change in CG50/CG54. When I create SDS on the target system itself it works (as you described) but it is not working in case of ALE distribution. And of course the status change is done properly on the source system as well.

Taking a look on the document in the target system by CG54: the only status in the log is "released" with the ALE user assigned. The "created by" user in this case is my user, as I created this SDS in the source system.

Does that give a more detailed picture?

I will check the other options the mentioned as well.

Best regards,

Christoph

christoph_bergemann
Active Contributor
0 Kudos

Hello Christoph

thanks for providing details. Could you please check this:

In the source system during update of WWI Document the new one is getting released and the old one is set to historic. In theory this should be taken into account in ALE as well. Now the whole topic depends a little bit on ALE filter. Here you can "surpress" things (that means only Released documents are distributed etc.). Please check your filter.

I have had always the feeling that ALE (as well as Import) are "hard" update processes. That means that the new data is inserted without taking care (in this special case of WWI documents) of old documents. I believe that if you use cg50 and release the document the above mentioned function module should be called to make an update on the old one (so that the status is then historic). And this (I have the feeling) is not done in ALE processing. I am "nearly" sure that the same will happen if you upload inbounds (that means if your gen variant is "released" with "setting historic automatic flag" that exactly this will not happen in the import process and you will get two released documents)

Personlly I believe that this behaviour of SAP EH&S is independent of release: I was not able to find suitable OSS notes regarding your topic.

May be one of the exits which I have mentioned above might help. At least (and this is what I believe you have done taking into account a different thread in this FORUM) you could prepare a report which is scheduled once a day in the target system which uses the above mentioned function module to set "old" documents in the target system historic

PS: could you please check in any cases your ALE scenario: I believe the Status net of WWI document in source system should be part of ALE scenario and should be distributed to the target system

PPS: pay attention here: if you are using "references" in report header in your source system you should really check if your recent set up of ALE support this (this is a different table)

Now what are the impacts in target system? As discussed you will have many released documents. Now the user would be "forced" to check only the "newest" one. This is "simple" as normally versioning is activated and therefore the newest one is the recent one having the highest version number. If now in the target system you have activated MSDS distribution to my knowledge as well the recent released version is used in MSDS distribution process.

With best regards

C.B.

Former Member
0 Kudos

Hello Christoph,

thanks again for your information.

As we are getting in real time pressure and the report shipping process is not affected by this we decided to eihter "ignore" the status or use the job (set to historical on daily basis) workaround.

Nevertheless I will follow up on this one later on and once the solution is found I will distribute it here.

Best regards,

Christoph

Answers (0)