Synchronisation between ECC and GTS documents

[Former Member]

Hello Experts,

We are facing a strange requirement of setting up of email notifications when a document is deleted in ECC and still exists in GTS. Do we have any table for this maintainance? Do we already have any OSS notes related this kind of scenario?

Replies and knowledge sharing would be most appreciated.

Regards,

Bobby

[Former Member · Accepted solution]

Hi Bobby,

Depending on how your client needs this, there are 2 options

1) Standard Option: We have a transaction in GTS to monitor and check if the customs documents in GTS has a valid reference in ECC. If there is no valid reference in ECC, system will show you those customs documents for deletion. You will have to select those documents and delete.

SAP GTS Area Menu- System Monitoring- Synchronization(Reorganize Customs Documents)

But mail notification is not possible in standard. In fact, you don't need a notification here when the users can delete those unnecessary customs documents directly from this transaction.

2) If they need a mail notification immediately when a document in feeder system is deleted, you will need a code change. But this is unnecessary standard SAP provides you an option to monitor and delete those documents.

Try checking those transaction under Synchronization tab

Actually, you will find 2 transactions

1) Check Synchronization of Customs Documents- This will just compare the entries in index tables of 2 systems and will delete all the entries that were successfully transferred to GTS. So, executing this transaction will just make sure that the index tables in ECC and GTS holds only the documents which are deleted in ECC and not available in GTS.

So, this will help you extract or identify the list of documents which are deleted in ECC and not available in GTS.

2) But if you need those inconsistent ones to be deleted, then you need to go for Reorganize Customs Documents

I would suggest you to convince your client to use these transactions or you can setup a batch job and get this done instead of investing sometime to develop a RICEFW to trigger mail notifications etc.

Ideally the need for their request could be to identify these inconsistent documents.

Regards

Dhilipan

[Former Member · Accepted solution]

Hello Dhilipan,

Can you please explain a bit on 1) Check Synchronization of Customs Document. Executing this program makes sure that  what all the entries are in index table of ECC exists in GTS and remaining would be deleted from GTS? Am I right?

I can see different documents in synchronisation of customs document and reprganisation. All documents from Reorg are in Check Synchronisation report but it also contains extra entries. What is the difference?

Thank you for your time.

Regards,

Bobby

[Former Member · Accepted solution]

Hi Bobby,

Yes, Check Synchronization of Customs Document will basically include all the documents(ones that are consistent with ECC and the ones that are not).

So, the logic is something like this... There are 2 tables, one in ECC and one in GTS.  I don't remember those tables by heart now.

-->When a document is transferred from ECC, an entry is created in the table in ECC.

--> Once the document is replicated in GTS, an entry is created in the tablein GTS.

Check synchronization will actually pick up all entries from the table in GTS and will check in ECC to indicate the ones that are consistent with a check box marked in the last column(Document Exists in Feeder system).

When you download the list that are there without a check for column (Document exists in FS) and compare with the output of Reorganize, results should be identical.

Hope this is clear. Please close the thread if you query is answered.

Note: Check Synchronization- When run in simulation mode, no impact. If you run in live mode, all those documents that are consistent(with check box VBAK,VBAP table. It's just the table used by GTS to check if a document is consistent. When a document is identified as consistent, entry from the table in ECC is deleted. Only the inconsistent ones will remain.

Regards

Dhilipan

[Former Member · Accepted solution]

one last question please, So, re organise option shows only documents that exists in GTS and doesnt exists in ECC? Right?

Thanks a lot for your answers Dhilip!!! You are a star

[Former Member · Accepted solution]

hi Bobby,

Yes, but it doesn't always mean that the document in ECC was deleted. There could be cases where the document exists in ECC and GTS. But the linkage/reference is missing in GTS.

So, basically the reorganization is to identify the list of documents in GTS which doesn't have a reference/linkage to a document in feeder system. Once you have the list of documents in GTS, you can delete those customs documents here and retransfer the corresponding document from feeder system(if the problem was with linkage). If the case was the feeder system doc deleted, you can recreate the same and customs document will be created in GTS automatically.

Regards

Dhilipan

[Former Member · Accepted solution]

Hello Dhilipan/Thomas,

Can I please know what does follwoing status indiacte. I have run the program in live (Not simulation):

Check mark in last column (Indicates document exists in FS and No check mark in Ex.Checked)

Regards,

Bobby

[Former Member · Accepted solution]

Hi Bobby,

It's same that I explained previously.

Document Exists in Feeder system is set- When the program finds an entry in GTS sync table and ECC sync table. These 2 tables are filled in when a document is successfully replicated in GTS. If there is an entry in these sync tables, system will set the indicator "Document Exists in feeder sys" and will consider the document is not deleted in ECC. If the entries are found in the sync tables in ECC and GTS, system will not go ahead further looking for entries in all transactional tables of ECC

If the program couldn't find entry in the sync tables in ECC or GTS, you will not find "Document Exists in feeder sys" checked.

.

Existence Checked is set- When the program doesn't find an entry in the sync. tables in ECC or GTS. It will automatically look for an entry in the transactional tables VBAK,EKKO and LIKP depending on the document type it's trying to deal with. This is called existence check.

So, you will find Existence Checked set for all those documents which were not available in those tables(Document Exists in FD is blank). Similarly the ones with Document existsin FD will not have Existence check performed.

Note: Depending on indicator "Simulation mode or Live mode" System will delete the entries from sync. table if it finds the documents in ECC and GTS consistent.

Table in ECC: /SAPSLL/OBJSYNC

Table name in GTS:  /SAPSLL/CDSYNC

Hope this was helpful.

Thanks

Dhilipan

[thomasrausch]

Hello Bobby,

what kind of document do you mean?

Regards,

Thomas

[Former Member]

Sorry for being unclear. any document that is transferred to GTS (Sales/purchase orders)