topic Re: Trigerring Event on Data Creation in Application Development and Automation Discussions

Trigerring Event on Data Creation

former_member207873 — Fri, 17 Oct 2014 11:37:32 GMT

Hi Experts,

I need to trigger an event when ever some data is created/Changed in TVAK table other wise through which transaction code document type is created or chagned?. I need to have hold on all document types created or changed. How to achieve this?

BR.

Re: Trigerring Event on Data Creation

JuanCarlosDelga — Fri, 17 Oct 2014 12:49:33 GMT

Hi that table has the checkbox 'Log data changes' active, so you can check changes with transaction SCU3.

Regards.

JCD

Re: Trigerring Event on Data Creation

former_member207873 — Fri, 17 Oct 2014 13:29:10 GMT

That is not the answer I am expecting. I think for all tables there is log changes, not only for TVAK. I need to know some events or function modules which will get triggered after the creation/modification of data in table TVAK.

BR.

Re: Trigerring Event on Data Creation

JuanCarlosDelga — Fri, 17 Oct 2014 14:18:40 GMT

Hi Sam,

There is a log change for customizing tables, applications tables are grouped in entities (Purchase order, Material,..), and their changes are stored in a change document.

If SCU3 read the change log, you only need to search where is created.

Regards.

JCD

Re: Trigerring Event on Data Creation

Former Member — Fri, 17 Oct 2014 14:53:58 GMT

Hi Sam,

Do you want an event in SAP-Business-Workflow-Engine, or simply an BAdi, Customer- or User Exit, you can react on entry-creation?

Or do you think there is an ABAP-OO-Event risen whenever an entry gets inserted?

Maybe you can provide some Information in your issue.

regards,

Jan Martin

Re: Trigerring Event on Data Creation

Private_Member_7726 — Fri, 17 Oct 2014 15:59:57 GMT

Hi,

Why - that is a client dependent customizing table, edited potentially via countless generated table maintenance dialogs, so you are asking for something nearly impossible. Go to SM30, enter TVAK and press either <Find maintenance dialog> or <Customizing> and then <Continue w/o Specifying Project> and you should see what I mean.

The requrement doesn't sound like anything any business would need to implement in order to solve a business task or challenge... because customizing is normally done in DEV system customizing client and then propagated through landscape - tested on test system, then moved to production. So why do you need to have hold on what "consultants" or "integrators" are customizing..? If you could tell what are you trying to accomplish in terms of process or business task, maybe it would be possible to suggest an alternative...

cheers

Janis

Re: Trigerring Event on Data Creation

Former Member — Fri, 17 Oct 2014 17:19:58 GMT

This message was moderated.

Re: Trigerring Event on Data Creation

Private_Member_7726 — Fri, 17 Oct 2014 18:26:10 GMT

Are you proposing to extend/modify all the SAP table maintenance dialogs involving that table...?

EDIT in: although, if the Change Documents are written reliably on the table, one could try Creation of Events When Change Documents are Written - Embedded Processes (SAP Business Workflow) - SAP Library (I|m not familiar with that technic).

Still - how to deal with the changes coming in via customizing transport, would they fall under the same logic..?

cheers

Jānis

Message was edited by: Jānis B

Re: Trigerring Event on Data Creation

former_member207873 — Mon, 20 Oct 2014 05:57:03 GMT

Hi Jānis B ,

The requirement is like I have to push data from SAP to MDM when ever a new data is created or changed in the table TVAK. So how to achieve the same.

BR.

Re: Trigerring Event on Data Creation

rosenberg_eitan — Mon, 20 Oct 2014 06:39:25 GMT

Hi,

I can see that table TVAK on our machine is 120 records .

Why not copy this "BIG" table on a daily basis.

Regards.

Re: Trigerring Event on Data Creation

former_member207873 — Mon, 20 Oct 2014 06:43:21 GMT

Hi Eitan Rosenberg,

I want the data to be pushed from SAP system, only when some data is created new or changed.

What you mean by copy the table data on a daily basis? How to achieve that ?

Br.

Re: Trigerring Event on Data Creation

Private_Member_7726 — Mon, 20 Oct 2014 06:43:31 GMT

Hi,

Still sounds weird (that in my understanding is customizing data, not master data...), but maybe it could be solved somehow by programming a database trigger, which would in turn raise event is SAP, if the synchronization needs to happen immediately after modification. If the time is of no importance, one could keep a copy of table in customer namespace and run a periodic job (say, once an hour) comparing contents. Or you could really look if it's feasible to extend the table maintenance dialogs.

cheers

Jānis

Re: Trigerring Event on Data Creation

rosenberg_eitan — Mon, 20 Oct 2014 07:16:28 GMT

Hi,

A yes "Database trigger" you manageg to make my mouth water.....

Regards.

I came from AS/400 .

Re: Trigerring Event on Data Creation

rosenberg_eitan — Mon, 20 Oct 2014 07:17:22 GMT

Hi,

Lets assume that you know about a record that was created .

How do you plan to push that record to MDM (What is MDM ?) .

Regards.

Re: Trigerring Event on Data Creation

former_member207873 — Mon, 20 Oct 2014 07:20:15 GMT

MDM means Master Data Management. I plan to push the data through some consumer proxy.

Re: Trigerring Event on Data Creation

rosenberg_eitan — Mon, 20 Oct 2014 07:27:54 GMT

Hi,

Shame on me !!! I just recall the lecture.....

But still it is a small table so why not push all the records .

Regards.

Re: Trigerring Event on Data Creation

Private_Member_7726 — Mon, 20 Oct 2014 08:12:15 GMT

Hi,

I obviously know too little about the particular situation, but I guess I have to explain why I'm less than enthusiastic about this requirement (I'd actually fight it tooth and nail if someone ordered it up on the system I'm supporting).

Even the most disordered SAP systems I've worked on had agreed on procedures on how the customizing (system setup essentially) is created and delivered as part of change management (in my experience, with very few exception, it's done via customizing transports DEV > TST > PRD). The more systems involved - the bigger the need for setup changes to propagate via uniform, agreed upon, known to everyone ways.

I'd be very apprehensive if someone would try to "innovate" something in this area. I'd question the feasibility of investing in programming a "replicator" for what is essentially one setting, which changes how often... - certainly not every day, I hope. If Sales Document types are part of MDM setup, it should receive changes the same way every other system receives them - after the changes have been tested (including for and on MDM system). Why shouldn't it, what's so special about it...? Someone forgot to deliver customizing changes to MDM system - not a reason to complicate change management by programming a "replicator", when the challenge can and should be addressed via organizational measures - so those setting up document types do not forget to test and transport changes for MDM.

EDIT in: furthermore, if the MDM is not a part of "normal" customizing delivery mechanism, but still needs to know Sales Document types, the control should be reversed, I feel (sorry if this sounds newbie and MDM functions the other way around) - the MDM should know where it should get the stuff it needs and not all the managed systems - what stuff to push when. And what about this: MDM Generic Extractor for Reference Data - SAP NetWeaver Master Data Management (MDM) - SAP Library:


The extractor can retrieve any customizing data such as check tables and domain fixed values needed for consolidating SAP master data objects. The extractor is generic because its use is independent of the type of SAP remote system and the master data object type.

cheers

Janis

Message was edited by: Jānis B