Questions on syndication

Hi,
I have two worklows - one gets triggered when adding a record to MDM and another on update of existing record. Both these workflows will always have only one record in job.
I would like to syndicate the record at the end of approval step in each workflow. I have created the syndication map and ports as required. Our scenario doesnt allow us to put the syndicate step in workflow.
Questions:
1. Will adding a record to mdm trigger syndication before it gets added to the workflow? I want to syndicate only after it is approved and checkedin
2. if I set the syndication map setting to "syndicate only changed records", will it trigger syndication on update of record before workflow completed?
3. What other specific settings should I maintain in the syndication map to syndicate only new records and updated records?
Regards!
Durai

Hi Durai,
Questions:
1. Will adding a record to mdm trigger syndication before it gets added to the workflow? I want to syndicate only after it is approved and checkedin
2. if I set the syndication map setting to "syndicate only changed records", will it trigger syndication on update of record before workflow completed?
3. What other specific settings should I maintain in the syndication map to syndicate only new records and updated records?
Answere:
Ans1.For both the workflows you can have the records in checked out state "on import" and "on update" actions.
Once that approval can take its course.Maintaining a filter in the automatic syndication map criteria can serve the purpose.
A filter can be maintained as suggested in the above post,this can be assignment or the user updates this status.
Ideally we create a lookup table with various status entries,this entries also tell where does the record lie and on a particular final status it gets checked in and syndicated.
It is important to note that you choose the entry from the lookup table entry in the syndication map,this ensures less load on MDS as against writing in Expression box.
Ans2. The filter on the automatic port's map can take care of this.You can use the same lookup for Create and update scenario,only more entries have to be added depending upon the course of action of MDM workflow.
Ans3. Suppress Unchanged record - SET
Suppress Records Without Key - SET
Choose appropriate remote system for this map and assign it to the syndication port.
Hope this helps.Please revert in case of a query.
Thanks,
Ravi

Similar Messages

Certain character string in RSS truncates the feed

Safari 3.1.2 - When the string "%&#$@" shows up in an RSS feed (presumably random - it was used in place of profanity), the RSS feed is truncated after the "%", so the rest of that article and all subsequent articles are not displayed. Bug? Or, are such character sequences supposed to be properly escaped or encoded somehow by the feed generator?
feed in question:
feed://syndication.thedailywtf.com/TheDailyWtf
link to the article, in case it has expired out of the RSS feed:
http://thedailywtf.com/Articles/The-Greatest-Idea-Contest.aspx

Hi,
The value that is written to the new record is the "r" (=return) value not the "d" (=display) value, so you should check the definition of the field on the new record to make sure that it is large enough to accept the CD_ORDEM_SERVICO value. If it is, you should then do a View Source on the page, locate the option tags and check the value attributes to make sure that they are being rendered correctly.
Andy

MDM Data Security/Syndication Question

Hi,
   Is it possible to setup security profile in a way to restrict Qualified table data? For example A customer record looks like :
Main table:
CustomerNumber               Type                        SalesData
A1                           Internal                1001, 1009
A2                          External                1002, 1005
Sales Data is a qualified table with sales org. I want to setup a role wherein a user has access to sales org 1001 records only. So if that user logs in he should see only :
A1                         Internal                     1001
Also similarly for syndication is it possible to syndicate the main record with only selected qualified records? (same as above)
Harsha

Hi Harsh ,
Its very much possible .
You have to define these roles in console .
Admin - Roles - Tables and Fields - Constraints
Here , you define the sales org 1001 in constraints field for your qualified table .
Now define a user with this role .
If you need more info . pls let us know ,
- An .

Question about patchset 6810189

HI all, I'm about to apply the patchset of the subject on production cluster, I did some tests on test environment, and everithing works fine, as you can see below:
SQL> select COMP_NAME, VERSION, STATUS from dba_registry;
COMP_NAME               VERSION STATUS
Oracle Enterprise Manager     10.2.0.4.0 VALID
Spatial                    10.2.0.4.0 VALID
Oracle interMedia          10.2.0.4.0 VALID
OLAP Catalog               10.2.0.4.0 VALID
Oracle XML Database          10.2.0.4.0 VALID
Oracle Text               10.2.0.4.0 VALID
Oracle Expression Filter     10.2.0.4.0 VALID
Oracle Rule Manager          10.2.0.4.0 VALID
Oracle Workspace Manager     10.2.0.4.3 VALID
Oracle Data Mining          10.2.0.4.0 VALID
Oracle Database Catalog Views     10.2.0.4.0 VALID
Oracle Database Packages and Types     10.2.0.4.0 VALID
JServer JAVA Virtual Machine     10.2.0.4.0 VALID
Oracle XDK               10.2.0.4.0 VALID
Oracle Database Java Packages     10.2.0.4.0 VALID
OLAP Analytic Workspace          10.2.0.4.0 VALID
Oracle OLAP API               10.2.0.4.0 VALID
Oracle Real Application Clusters     10.2.0.4.0 VALID
18 rows selected.
But on production environment I have the following situation:
SQL> select COMP_NAME, VERSION, STATUS from dba_registry;
COMP_NAME                              VERSION STATUS
Oracle Application Server Syndication Services          10.1.2.0.2 VALID
Oracle Application Server Portal               10.1.2.0.2 VALID
Oracle Application Server Single Sign-On          10.1.2.0.2 VALID
Oracle Workflow                              10.1.2.0.2 VALID
Oracle Ultra Search                         10.2.0.1.0 VALID
Oracle Enterprise Manager                    10.2.0.1.0 VALID
Spatial                                   10.2.0.1.0 VALID
Oracle interMedia                         10.2.0.1.0 VALID
OLAP Catalog                              10.2.0.1.0 VALID
Oracle XML Database                         10.2.0.1.0 VALID
Oracle Text                              10.2.0.1.0 VALID
Oracle Expression Filter                    10.2.0.1.0 VALID
Oracle Rules Manager                         10.2.0.1.0 VALID
Oracle Workspace Manager                    10.2.0.1.0 VALID
Oracle Data Mining                         10.2.0.1.0 VALID
Oracle Database Catalog Views                    10.2.0.1.0 VALID
Oracle Database Packages and Types               10.2.0.1.0 VALID
JServer JAVA Virtual Machine                    10.2.0.1.0 VALID
Oracle XDK                              10.2.0.1.0 VALID
Oracle Database Java Packages                    10.2.0.1.0 VALID
OLAP Analytic Workspace                         10.2.0.1.0 VALID
Oracle OLAP API                              10.2.0.1.0 VALID
Oracle Real Application Clusters               10.2.0.1.0 VALID
Oracle Application Server Integration B2B          10.1.2.0.2 VALID
Oracle Application Server Integration BAM          10.1.2.0.2 VALID
Oracle Application Server Certificate Authority          10.1.2.0.2 VALID
Oracle Internet Directory                    10.1.2.0.2 VALID
Oracle Application Server Metadata Repository Version-R     10.1.2.0.2 VALID
Oracle Application Server Distributed Configuration Management     10.1.2.0.2 VALID
Oracle Business Intelligence Discoverer               10.1.2.0.2 VALID
Oracle Application Server Web Clipping               10.1.2.0.2 VALID
Oracle Application Server UDDI Registry               10.1.2.0.2 VALID
Oracle Application Server Wireless               10.1.2.0.2 VALID
33 rows selected.
As you can see, I have more components on production.
My question is :
It's possible to loss functionality applying the patchset?
(I did read the README, but I'm not sure)
Thanks in advance!

Your first issue is that QA is not exact copy of Production. It makes it difficult to really test these sort of stuff. Most of the differences are related to Application Server stuff. Have you checked the compatibility matrix for App server and its repository? Maybe you should upgrade App server as well.
I've applied 10.2.0.4 on HP-UX cluster many times without problem. But that doesn't mean it works for everyone. Your safest option is to make QA like Prod.

Workflow Questions - How to execute the steps in a workflow automatically?

I am using MDM 5.5 SP6.
My Question is how to execute the steps in the workflow automatically. That means NO user interaction.
I have a simple workflow, Start- Process -- Syndicate - Stop.
When a new record added /updated/inserted this workflow will start automatically. The workflow inbox, the workflow status is u2018Receivedu2019 Step is u2018Processu2019. Now I have to right click on the record then u2018Next Stepu2019 then click on u2018Syndicateu2019 then workflow completes automatically.
How to execute the Syndication step automatically?. I donu2019t want to have any user interaction to syndicate these records.
Is this possible?
The reason for this is I want to do some field validation and based on the field validation some assignments then then I want to syndicate these records without user interaction..

Hi,
If you want to do some validations and then based on result assignments on some of the fields before syndicating, then you have to use workflow. Only syndication server will not fulfill this requirement.
you may try by making validation's automatic property as "Error". This way it will not allow to add any record not fulfilling validation. You can also try using calculated fields instead of assignment.
I am not sure if you can make your workflow fully automatic, because atleast one process step is must for any workflow, and process step means user action.
Regards,
Shiv

Syndication event for new MDM PI Adapter in MDM 7.1

Hi,
We have setup the new MDM PI Adapter for MDM 7.1 and have created interface in PI using this new MDM PI adapter. All neccesary steps as mentioned in the installation guides are done.
Also all necessary remote systems/ports/syndication maps are created in MDM, and syndication is running fine on the MDM side (using the syndication server, so not manually!)! The syndication files are created in the Outbound/../Ready folder, so again, on MDM side everything looks OK.
However, when the syndication server has run, there's no syndication event triggered (or at least not captured by the MDM PI Adapter), hence PI is not picking up the files from the outbound folder. It looks like PI is not getting any syndication event, or at least is not catching the event, since monitoring on PI side does not show us any trigger.
Now I have the following questions:
1. Does anyone know how we can verify/monitor if MDM raises any syndication event (the export log in the console of MDM 7.1 does not say anything about an syndication event that is raised, only that the export itself was succesfull)?
2. Is there any additional setup to be done on MDM side in order to make sure that the syndication event is raised as soon as the syndication server is ready (or is the syndication server ALWAYS raising the event, independent of using the MDM PI adapter)?
If anyone else has any experience with the new MDM PI Adapter for MDM 7.1, please share us your valuable information. Thanks in advanve for your answers/advice.
p.s. We are using MDM 7.1 (build 7.1.01.72).
Regards,
Marcel

Hi
We are also currently experiencing a similair issue. Seems to occur when some sort of matching activity occurs on the MDM Server. What happens is that syndicated files remain in the 'Ready' folder on the Outbound Port. In the PI Netweaver Trace Log files we start seeing this error message:
Jul 13, 2009 4:34:41 PM com.sap.mdm.logging.MdmLogger warning
WARNING: NotificationDispatcher - Connection failure. Original exception: 'java.net.SocketException: Connection reset'.
If we restart the Connector and Adapter from the NetweaverJ2EE Application Admin screen, this files still remain in the READY Folder. However, if i syndicate another data record into that folder, the syndication for that file work as well as for the rest of the files that were sitting in the READY folder. Seems like the "failed" files seem to latch off the syndication event.
Doesn't seem like the stability and robustness is there?
Any feedback would be greatly appreciated.

Custom name to output file of syndication

Hi
It may be a dumb question can we control the name of output file while using Syndication server.
Regards
Bala Pochareddy

Hi,
No...You can not. May be you can try to use OS level commands to rename the file once it is placed in the folder.
Regards,
Rajani

Conceptual questions

hello experts,
since i am new to MDM, there are a few doubts i would like to clear
these apply to particular scenarios
1) I have two different R/3 systems
two records are present, one in each system
in the real world, both these refer to the same data
they are merged in MDM - some attributes are changed in both the records
now, what happens on syndication ?
eg: if the names were different originally, what gets reflected back ?
2) I have one R/3 system
it has two different records which are similar in the real world
these records are matched and merged in MDM
what happens on syndication ?
will there be one record or two and what will be the key field of this record(s) ?
3) I have one R/3 system
suppose i send 100 MATMAS IDocs to MDM via XI
a. suppose I create 20 more matmas records, can i only send these 20 at a later point of time, if so, how do i choose these 20 ?
b. suppose I change some of the original 100 records in R/3 before MDM syndicates them back, will there be inconsistency when i syndicate those old records back ? If not, how does SAP avoid it ?

Kris,
When you are trying to merge two records from systems A and B, there is every chance that some attributes in the record from A will differ from those in the record from B. In such a case the concept of the "System of Record" (SOR) will come into play. Your data governance process might be set up such that attribute F1 from system A is always correct (A is the SOR for F1) and attribute F2 from system B is always correct (B is the SOR for F2). So, when you are merging your records from the two systems the value of F1 in the record from A will "survive" and the value of F2 in the record from B will "survive" in the merged record. In the situation that you have described in 3b, your governance process may be set up such that R/3 is the SOR for classification data and MDM is the SOR for everything else. In such a case, if there is any change to classification data in R/3, your process should be set up so as to overwrite any changes to the classification data in MDM with the R/3 data. If there is any change to any other type of data in R/3 then you don't bring that over to MDM. You can setup XI to do a lot of this activity.
To cut a long story short, the easiest way to handle such cases is through an airtight governance process where you identify what the SOR for every attribute is and then don't let that attribute be overwritten if it is from the SOR.
Regarding #1, I am not very sure I understand the question. If MDM is simply being used for consolidation of your master data records, then your transactional data is still in the R/3 systems and you are not deleting any master data from those. Are you asking about things like changes to a "bill to" address in MDM and that change being syndicated?

Update of XML syndication map when XSD is changed

All,
So we recently upgraded to MDM 7.1 SP 06 and found a new feature which we were waiting for quiet some time. Thought i'll share with the community as well.
Update of XML syndication map when XSD is changed in Console
In earlier SP's of MDM, if we had to update an XML syndication map, we had to upload the new XSD in Console, go to syndicator and basically re-create the whole map. there was no way for syndicator to preserve the old mapping.
Well with this new feature, the old mapping is preserved, we only need to re-map the new fields.
The process is as below:
1. Upload the new XSD in Console.
2. Go to syndicator and open the syndication map which you want to update(File->Open).
3. Click File -> Update XML Schema. (this is the new option)
4. It will give a pop-up, select the new schema you have uploaded in console and hit OK.
5. You will get a prompt saying that syndication map is being changed, hit OK.
6. Now you will see the new XSD in syndicator, the older fields are still mapped, you only need to map the new fields.
It a nice feature which will definitely save lot of time. Thanks SAP
Regards
Aamir

If this post answered your question or helped, please mark it as such.
This works.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
<mx:Script>
 <![CDATA[
 import mx.events.DataGridEvent;
 import mx.collections.ArrayCollection;
 [Bindable] private var ac:ArrayCollection = new ArrayCollection([
 {bgColor: "0xFF0000", num: 100, name: "Test1"},
 {bgColor: "0xFF0000", num: 200, name: "Test2"},
 {bgColor: "0xFF0000", num: 300, name: "Test3"},
 private function changeBK(evt:DataGridEvent):void{
 var row:uint = evt.rowIndex;
 var data:Object = ac.getItemAt(row);
 data.bgColor = "0x00FF00";
 ]]>
</mx:Script>
<mx:DataGrid id="dg" dataProvider="{ac}" itemEditEnd="changeBK(event);"
 editable="true">
 <mx:columns>
 <mx:DataGridColumn dataField="num">
 <mx:itemRenderer>
 <mx:Component>
 <mx:TextArea backgroundColor="{data.bgColor}" text="{data.num}"/>
 </mx:Component>
 </mx:itemRenderer>
 </mx:DataGridColumn>
 <mx:DataGridColumn dataField="name"/>
 </mx:columns>
</mx:DataGrid>
</mx:Application>

Syndication Map Issues

Hi Experts,
I am trying to populate the LFM2 segment in SAP (Plant Data) from MDM. Since it is underneath the LFM1 segment (Purchase Org) I have created a tuple with all necessary fields, then in the Purchase Org tuple I have added a 'Plant' field that is a tuple (that points to my Plant Tuple). So essentially, I have nested it (in MDM) inside the Purchase Org tuple to mimic how it is on the iDoc.
My question is, I've mapped all of the fields on the Syndication Map (the fields under the nested tuple - NOT the multi-valued Plant Tuple itself - nested tuple in the Purchase Org is pointing to).
In Syndicator under the Destination Properties tab: I also put an 'X' in the static text field WERKR (suggestion by an SAP consultant)
When I syndicate to ECC 6.0, I am getting an iDoc error: "enter a valid value"
If I do not have an 'X' in the static text field - I get an iDoc error (something to the effect of) "Plant data not defined in SAP"
Cannot figure out why this is erroring out in SAP! Any suggestions?
Niki

Hello Niki
SAP MDM may syndicate data to outbound directory in text or xml formats.
For check your syndication map you can do it through Syndicator application.
If syndication map is OK
You can configure syndication server for automatic syndication
Syndicated file should be created in outbound directory.
In another case error file wil be create in "Exception" directory.
After that SAP Netweaver PI(XI) get syndicated file from outbound directory and send it to ECC
File may be modified or transform to another format into PI(XI)
If first part work fine - search error in SAP NetWeaver PI(XI)
Regards
Kanstantsin Chernichenka

When Syndication does not happen

Hello
Although I checked everything I could regarding the Port's configuration and Syndicator (Mapping, eligible records), the syndication does not happen.
The processing type is Automatic and processing interval hourly. The console does not get updated with the next syndication time.
Any ideas about what else should I be verifying ???
thank you in advance
Luciana.

Hello Ravi,
I re-created the ports for both repositories and it seems ok now. The processing date and time are being updated by the system now.
Question : Do we need to re-start the server when we do changes to the ports ?
I used to do this in the past because my changes never seemed to be saved by the system.
thank you

Experiencing poor syndication service performance in MDM SP06

I have installed MDM SP06 on our test server and have had to switch our syndications from using the syndication manager batch utility to using the syndication service.
These syndications all have the "suppress unchanged records" option selected (checked) so that we only send recently inserted/updated records.
I have found that when no records have been updated, the syndication service seems to be invoking SQL Server repeatedly nd frequently and between MDSS and MSSQL, they pretty much keep our CPU busy most of the time.
However, if I touch one or more rows, the perfromance, for the run immediately following seems to improve.
I notice similar behavior in Syndication Manager. If no rows have been updated, syndication manager just runs and runs when I execute the syndication. But if I touch one or more rows, then it executes the syndication in a reasonable time.
Does anyone have any ideas as to what I might be doing wrong, or may have missed when installing/configuring 5.6?
The repository in question is not particularyn bik -- there are about 67K vendor records on the main table.
Thank you for any assistance or ideas,
Vince
Edited by: Vince Moore on Oct 7, 2008 10:40 PM

Cherry,
Thanks, but unfortunately we had previously committed to send files to certain systesm every 10 minutes (with our old, home-grown, Oracle based solution it was every 5). We had been able to do that with batch syndication, but we couldn't hold off upgrading forever as we needed some other new features.
I also tried increasing the Auto Syndication Task Delay, but that just gives us brief intermittent periods of idle time.
What would have been helpful was a real scheduler -- not just the choice of continuous, hourly daily or weekly -- that's pretty lame.
Thanks,
Vince

MDG Questions...

MDG experts,
I donu2019t know much about MDG. I assume the process will be similar to MDM and that includes consolidation, harmonization & central master data management scenarios. If that is true then, could anyone clarify the following questions?. If not, guide me how MDG works. I am in the process of reading the MDG doc's.
1.     In MDG, where is the master data is stored?. Is it in MDM?
2.     Is there any architecture diagrams for initial load & Harmonization process?
Initial load
1.     How master data from SAP source systems will be loaded?. Is there any specific interface will be in-built with MDG?.
2.     How Non-SAP master data will be loaded?. By using file upload to MDG?
3.     Is Hierarchies can be build in MDG for example, Profit Center group hierarchies, UNSPSC codes?
Syndication of Master data from MDG to SAP & Non-Sap systems
1.     Is there any specific interface is already built for SAP ECC and BW systems?
2.     How to syndicate master data to Non-SAP systems? Downloading data in to files then load these data in to non-SAP systems?
Thanks
Mike.

1. In MDG, where is the master data is stored?. Is it in MDM?
ADB : could be in SAP systemsor in MDM or both.
2. Is there any architecture diagrams for initial load & Harmonization process?
ADB : yes - check link down
Initial load
1. How master data from SAP source systems will be loaded?. Is there any specific interface will be in-built with MDG?.
ADB : yes - specific extractors are designed in the MDG to extract from source and have them in MDM staging area
2. How Non-SAP master data will be loaded?. By using file upload to MDG?
ADB : file upload is supported
3. Is Hierarchies can be build in MDG for example, Profit Center group hierarchies, UNSPSC codes?
ADB : - yes can be done
Syndication of Master data from MDG to SAP & Non-Sap systems
1. Is there any specific interface is already built for SAP ECC and BW systems?
ADB : - there are syndicator interfaces built for any targets with PI as integrator
2. How to syndicate master data to Non-SAP systems? Downloading data in to files then load these data in to non-SAP systems?
ADB : - there are syndicator interfaces built for any targets with PI as integrator
this is Not MDG;s headache - it gives u the data out of its systems how u integrate to 3rd party systems ur effort and idea.
read this for all u want on MDG ! :
http://help.sap.com/erp2005_ehp_05/helpdata/en/3e/b67a9facd34cb09ce87e3bc24b4c52/frameset.htm http://help.sap.com/erp2005_ehp_05/helpdata/en/18/a64e59f0744143a0c2ff9bc1b6aabc/frameset.htm
http://wiki.sdn.sap.com/wiki/display/SAPMDM/SAPMasterData+Governance
Embedded Master Data Management
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60022998-5d17-2b10-dbaa-8e3ab357fa55
hth
thanks
-Adrivit

Field length during syndication & Automatic scheduling

Hi All,
I have 2 questions and need your valuable suggestions for same.
1) I have one field in MDM called Article code which contains value as 012345 thats 6 digit. My target system wants only 12345. Mean to say we need to do some settings in syndicator so that we can remove 0 and make it as 5 digit instead of 6 digit code.
2) Suppose I have schduled a automatic file generation in MDM that takes place in the evening 7PM daily. This will cover all the changes made in master data in whole day and will generate xml file covering all those changes. Let say on some day no changes were made. Then i need a file containing no values but it must generate a file atleast. How can we do this.
Please let me know if you ned any further info.
Thanks
Himanshu Nijhawan

Hi Himanshu,
See MAX ITEM LENGTH will take care of field value which will always have <= 5 characters.
Suppose if you set only this property then if you have length with 6 character then it will eliminate the last char of value.
e.g. 012345 to 01234 which you actually not looking for so alone this property will not solve your problem.
If you also set this property too along with MAX ITEM LENGTH, I mean Leading Character to strip = 0, then it will always eliminate field value with all the leading character's to 0 first and then count max item length should not > 5
e.g. 012345 to 12345
001234 to 1234 not 01234, if you want to contain 0 if it has length 5 then with leading char strip to 0 will not work.
It will work if your 5 char does not have leading zero. e.g 12345 to 12345 but not 01234 to 01234 but will result in 1234
So, If you are sure that when it comes to 5 char then it will not have leading 0 and for 6 char it will always have leading 0 then you can set these both properties in Syndicator and then can save in map which will give you desired result.
e.g. 12345 to 12345
e.g. 012345 to 12345
So, if you feel that you always want 5 char value irrespective of leading char 0 then you should go for this below approach.
e.g. you want when its 5 char value as 01234 and you want to maintain in the same manner during syndication 01234.
Here i would suggest go for assignment and write assignment expression as below in Data Manager.
IF(LEN(XXX) > 5 , RIGHT(XXX,5), XXX)
XXX is the Field name, this expression pass for value > 5 , e.g 6 then it will give the last 5 char of value
e.g. 012345 to 12345
It fails when the field value is not > 5 that means = 5 then it will put this same value e.g. 01234 to 01234. So in this manner you will always have length of 5 char and you don't need to cut off the 1st char and need to do this for 6 char only.
Regards,
Mandeep Saini

MDM Syndication selection option restrictions

Hi all,
In the MDM Syndicator is it possible to only syndicate certain details of the header record for a header and detail hierarchy structure?
For our Scenario, GL Account has the hierarchy as a Single Chart of Accounts assigned to multiple Company Code records.
· GL Account Master Record
· Chart of Account Details (SKA1 - Header)
 o Company Code Details (SKB1 - Detail)
In the repository we have SKA1 as the Main table and SKB1 as a sub table within SKA1. While the content is imported it comes in as 1 Record with multiple Company code level details. Is there anyway to restrict the selection for syndication for a given SKA1 - Header and get only the selected SKB1 - Details syndicated?
For example if for Chart of Account has 5 company codes A, B, C, D and E. Can we restrict the syndication of the of the record with selected company code details only (Example B and D - without the details for A, B, C being syndicated).
I appreciate the time.
Thanks,
-Raj.

Hi Raj
Here I do have some suggestions regarding your request, correct me if i am wrong, basically you are looking to syndicate the records by applying the filter row wise or column wise.
Row wise : Required all the field but search criteria as one or two fields ( for example filtering based on COA and Company code).
Column wise : Required only few fields to be syndicate, either row wise filter applied or not.
Hope I understood your question.
Solution:
Row wise : Use search parameter tab, search for particular COA and Company code and save the search for future purpose [from MENu SEARCH->SAVE SEARCH].
Column wise : Create Destination items for the fields which u want to syndicate and try to map those fields wt Original source items and try to syndicate the same.
Hope I have covered the point what you expected.
thanks
Alexander
P.S. Kindly reward the points, i found helpful.

Questions on syndication

Similar Messages

Maybe you are looking for