triadabuster.blogg.se - Multiple url extractor

#MULTIPLE URL EXTRACTOR FULL#

For example, let’s say we are connecting SAP BW and Informatica system to SAP ECC. When the two systems are connected to one source system there will be two logical systems, one for each. To extract the data into multiple systems we will have to establish communication between the two systems which would involve following:Ī) Logical system creation (tcode – SALE)ī) RFC destination creation (tcode – SM59)Ĭ) saprfc.ini file settings (in case of Informatica this is done on Informatica app server side) – we faced a lot of issues with saprfc.ini file entries so make sure these are correctĭ) ALE idoc configuration (tcode – WE31, WE30, WE21, WE20, BD64) System Configuration: Ideally this is the basis activity and I will only provide some tcode information. Initialization of datasource from two systems and its effect on source system.Understanding of Change pointer based datasources functioning.System Configuration understanding in case of two target system.We will go through system configuration and necessary steps that need to perform before we could even start the extractions. In this section I will discuss only change pointer based datasources and in coming sections I will try to explain functioning of others too. However, this is little tricky when it comes to extract data into multiple systems when running the delta in parallel as datasources have specific characteristics that they follow based on their kind. So how does this work basically, answer to this is simple Delta Queues. Good News: All of the above type of datasource work very well when these are extracted in multiple target system even when the delta extraction is running in parallel or in sequence.

#MULTIPLE URL EXTRACTOR FULL#

FULL load datasources- Most of the master datasources are full loads and do not follow delta mechanism.

Custom Datasources or Generic Datasources- These datasources which we create of our own and we provide our generic delta fields in RSO2.

These datasources have special timestamp table BWOM2_TIMEST which mainly manages the delta mechanism. A few examples of these datasources are 0FI_GL_4, 0CO_OM_OPA_6.

Time Stamp Based Datasources- These are the datasources which follow the time stamp table logic i.e.

For example, 2LIS_18_I0NOTIF is one such kind and almost all datasources starting with 2LIS

Setup Table Based Datasources- Mainly LO extractors which deal with setup tables, ideally application area datasources in LBWE and follow delta mechanism of ABR etc.

The delta mechanism these follow is of type ‘E or NEWE’ (You can find it in table ROOSOURCE)

Change Pointer Based Datasources- These are mostly master datasources like 0CUSTOMER_ATTR, 0MATERIAL_ATTR, 0MATERIAL_TEXT and follow the change pointer based delta mechanism (i.e.

While working on this kind of scenario I could classify the datasources in some broad categories depending on their Delta Mechanism or if they are FULL loads. Scenario: Two systems ‘SAP BW’ and ‘Informatica’ are connected to a single source system SAP ECC.

Also I will try to be as simple as I can. I will try to shed some light on the how the delta mechanism works in this case of all datasources. I would like to share some knowledge about the various datasources that can be used to extract data into multiple systems let’s say SAP BW system and other be Informatica System. Hello All, this is my first ever document on SDN so pardon me if I miss anything and your valuable suggestions are welcome.