Differentiate Record Syndication

[Former Member]

Hi Experts,

While Syndicating a record, is there any option to differentiate First time record syndication and Update record syndication ?

My intention here is, If a update record goes from MDM to XI then XI should understand this is an existing record in ECC and need to remove some segment from Idoc before posting in ECC.

I really appreciate any help regarding this

[Former Member · Accepted solution]

Hi,

We can also achieve this requirement with the help of MDM Workflows. Create one field say "Syndication" of type boolean with values Yes and No and set the default value to No. Whenever you want to syndicate the records, move the records to be syndicated to the workflow containing Syndicate step and the assignment step after the syndicate step which will check if the Syndication = "No" then set it to "Yes". Map this field with any of the destination fields and check the value in XI. If the value is No that means this is a new record else updated record has been received.

Regards,

Jitesh Talreja

[Former Member]

Almost we have decided to go with a RFC lookup in XI and check whether record already exist in ECC or not, Thanks again

Edited by: Ferose K Fazallul on Apr 9, 2009 6:30 AM

[Former Member]

Hi Jitesh,

I agree, your solution is one of the option to differentiate the record.

But in our scenario we have 4 inbound port for updating existing record and Two Workflow in which one for new material attribute enrichment and another one for update record WF for a specific attribute.

As per your solution I need to change/assign the "syndication" feild value to "YES" when ever an existing record gets updated.

But Is there any alternate option for to differentiate without adding a new field or WF. Extra WF is going to make more complex in our existing scenario and Already we are using 3 extra fields for syndication condition with some assignment in the main Workflow.

Thanks again for the reply.

Ferose

[former_member205403]

Hi Ferose,

The solution which Jitesh has suggested is the best one. but If it is not feasible for you to implement this solution, then handle it at XI/PI side. Perform a RFC lookup in XI and check whether record already exist in ECC or not. if it exists then populate required segment of IDOC otherwise skip it. XI can very well handle these kind of requirements and in your scenario this seems to be best solution to me.

Guys @ if there is any other approach for achieving this requirement then kindly let us know.

Thanks and Regards,

Shiv

[former_member205403]

Hi Ferose,

The solution which Jitesh has suggested is the best one. but If it is not feasible for you to implement this solution, then handle it at XI/PI side. Perform a lookup in XI and check whether record already exist in ECC or not. if it exists then populate required segment of IDOC otherwise skip it. XI can very well handle these kind of requirements and in your scenario this seems to be best solution to me.

Guys @ if there is any other approach for achieving this requirement then kindly let us know.

Thanks and Regards,

Shiv

[Former Member]

Thanks Minaz and Jitesh, But my Issue is different.

There is no issues while syndicating First time to ECC.

After the First syndication same material record in MDM gets updated, then the same record will re-syndicate, at this time I want to differentiate to XI that this is already syndicated earlier to ECC and coming one is just an update of some fields, So that XI will remove one of the MATMAS idoc segment which is not required to post in ECC in my scenario.

[Former Member]

Hi,

This is actually whay i have tried to explain in my earlier post, we can achieve this with the help of dummy field, assignment and workflows. Kindly check the post once.

Regards,

Jitesh Talreja

[Former Member]

Hi Ferose,

In Syndicator, check the map property, supress unchanged records.

This will syncidate only the updated or changed records since last syndication.

Hope it helps.

Thanks,

Minaz