Difference between Extraction Structure and Datasource

Hi Gurus,
I have a very basic question here.Can anybody explain to me in detail the difference between an extraction structure and Datasource.
Thanks in advance

Hi:
I am pasting a summarized def. from sap notes.
http://help.sap.com/saphelp_bw30b/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm
Data Source:
Data that logically belongs together is stored in the source system in the form of DataSources. A DataSource contains a number of fields in a flat structure used to transfer data into BW (Extract Structure).
Extract Structure:
In the extract structure, data from a DataSource is staged in the source system. The extract structure contains the amount of fields that are offered by an extractor in the source system for the data loading process.
You can edit and enhance DataSource extract structures in the source system. To do this, in the BW Administrator Workbench choose Goto à Modeling à Source Systems à Your Source System à Context Menu (right mouse click) à Customizing Extractors à Subsequent Processing of DataSources.
While, you are on the topic, you have one more structure.
Transfer Structure:
The transfer structure is the structure in which the data is transported from the source system into the SAP Business Information Warehouse.
It provides a selection of the extract structure fields for the source system.
It may be a good idea to look into a sample Business Content extractor to get a better understanding of how they are related.
Chamarthy

Similar Messages

Difference between transfer structure and extraction structure?

Hi Gurus,
Structurally what is the difference between transfer structure and extraction structure?
I have observed that both these structures have the same fields.
Then why do we need two structures in source system?
Please clarify ...
Thanks in advance

These links describe the differences between the two.
Transfer structure:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62b2e07211d2acb80000e829fbfe/content.htm
Extraction structure:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a627ee07211d2acb80000e829fbfe/content.htm

What is the difference between (SEPA Structured) and (SEPA Unstructured)?

Hi,
Could you please teach me about "Format Payments (SEPA Structured)"
and "Format Payments (SEPA Unstructured)"?
1.What is Format Payments (SEPA Structured)?
Is (SEPA Structured) used with which case?
2.What is Format Payments (SEPA Unstructured)?
Is (SEPA Unstructured) used with which case?
3.What is the difference between (SEPA Structured) and (SEPA Unstructured)?
The customer is checking Note.791226.1.
However, he says that he cannot understand these two differences.
Please teach me.
Thanks.

From the European Payments Council website:
Remittance information: structure the unstructured
The SEPA Credit Transfer Scheme permits the end-to-end carrying of remittance data on a structured or unstructured basis appropriate to the nature of the payment (the remittance information usually contains details of the contract underlying the transaction such as an invoice number, for example). The length of the remittance information in the SCT Scheme is fixed at a standard length of 140 characters and banks are obliged to pass on the full remittance information.
The EPC supports a proposal developed by the European Association of Corporate Treasurers (EACT), which allows companies to agree on a structure for the remittance information. The EACT suggestion on how to structure the "unstructured" remittance fields allows companies exchanging a credit transfer to agree, among other, on information to be transmitted in a specific manner. Banks will carry remittance information structured in such an agreed way unaltered throughout the process chain.

Difference between Append structure and include structure

hi can anyone tell me the difference between include structure and append structure with respect to tables defined in ABAP dictionary?
Also how to create them in ABAP dictionary?

HI
INCLUDE:
Includes are used to group fields and insert them together in a table or structure.
An include program has two main functions:
It contains code which can be used by several different programs.
It helps you to modularize programs, which consist of many different logically related parts. Each of these parts is stored as a separate include program.
Include programs improve the readability of programs and make maintenance easier.
Include reports contain rolled out parts of reports. They are called by the main report, and can only be run in conjunction with the main report.
APPEND:
Append structures are used for enhancements that are not included in the standard. This includes special developments, country versions and adding customer fields to any tables or structures.
An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.
The following enhancements can be made to a table or structure TAB with an append structure:
Insert new fields in TAB,
Define foreign keys for fields of TAB that already exist,
Attach search helps to fields of TAB that already exist
Just have a look at this link:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ebd6446011d189700000e8322d00/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ebd6446011d189700000e8322d00/frameset.htm</a>
Rsgards,
Gunasree.
Award marks to helpful answers

Difference between Info structure and Table

Hi Friends
I need to know difference between info structure and table (updating a table using a scheduled program),Which one of this is better and why?
Please help me to get the Pros and Cons of the two available approach.
Thanks
Mitesh

Hi,
No different, these are just transparent tables like any other. You can select data from them the same as any other transparent table.
Refer
https://forums.sdn.sap.com/click.jspa?searchID=4342729&messageID=1424611
https://forums.sdn.sap.com/click.jspa?searchID=4342729&messageID=3609095
Regards

Difference between include structure and Append structure

Could you please tell me
I have bsis table and it contains append structure in 4.7 SAP System.
my program in 4.7 system contains internal table which used same structure of bsis table ( which contains additonal field in its append structure ).
I need to have same table structure in 4.6 C because I am copying the same program into 4.6 system.
As I could not append structure to bsis table in 4.6C SAP system,
instead of that shall I add the field or Shall include the structure to run .
What is the difference between Include structure and Append structure ( I forgot )
How to achieve this please help me ?

Hi ,
As you know append structure can be used only once in table ,that to at last of all entries,
Append structures are used for enhancements that are not included in the standard. This includes special developments, country versions and adding customer fields to any tables or structures.
An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.
The following enhancements can be made to a table or structure TAB with an append structure:
Insert new fields in TAB,
Define foreign keys for fields of TAB that already exist,
Attach search helps to fields of TAB that already exist,
These enhancements are part of the append structure, i.e. they must always be changed and transported with the append structure.
When a table or structure is activated, all the append structures of the table are searched and the fields of these append structures are added to the table or structure. Foreign keys and search help attachments added using the append structure are also added to the table. If an append structure is created or changed, the table or structure assigned to it is also adjusted to these changes when the append structure is activated.
Since the order of the fields in the ABAP Dictionary can differ from the order of the fields on the database, adding append structures or inserting fields in such append structures does not result in a table conversion.
The customer creates append structures in the customer namespace. The append structure is thus protected against overwriting during an upgrade. The fields in the append structure should also reside in the customer namespace, that is the field names should begin with ZZ or YY. This prevents name conflicts with fields inserted in the table by SAP.
The new versions of the standard tables are imported after an upgrade, and the fields, foreign key definitions and search help attachments contained in the append structures are added to the new standard tables at activation.
A standard table contains the fields Field 1, Field 2 and Field 3. An append structure containing the fields ZZA and ZZB is defined for this table. After activating the table, the corresponding database table contains fields Field 1, Field 2, Field 3, ZZA and ZZB.
Further Remarks:
An append structure can only be assigned to exactly one table or structure. If you want to append the same fields to several tables or structures, you can store these fields in an include structure. In this case you must create an append structure for each of these tables or structures and include the include structure there.
Adding an append structure to an SAP standard table is supported by the Modification Assistant.
If you want to insert a field that is to be delivered with the R/3 standard in the next Release in the customer system in advance, you must include it in the table itself as a repair. If you include such a field in an append structure for the table, it will occur twice when the new standard table is imported. This will result in an activation error.
No append structures may be added to tables with long fields (data types VARC, LCHR or LRAW). This is because a long field must always be the last field in the table. However, structures with long fields can be enhanced with append structures.
If a table or structure with an append structure is copied, the fields of the append structure become fields of the target table. Foreign key definitions and search help attachments appended with the append structure are copied to the target table.
Foreign keys for the appended fields must be defined within the append structure. Fields of the table or structure assigned to the append structure may be defined when assigning the key field and foreign key field.
Indexes on the appended fields must be defined in the original table.
A table or structure TAB can only be enhanced with new foreign keys or search help attachments using an append structure. You therefore cannot change an existing foreign key definition or search help attachment for a field of TAB with the append structure.
Thanks
Manju

Difference between append structure and include structure in DDIC

Plz give me the apt difference between append structure and include structure in DDIC.
Thanks in advance.
Regards
Raj

This has been discussed please check it in forum
https://forums.sdn.sap.com/click.jspa?searchID=480466&messageID=114309
https://forums.sdn.sap.com/click.jspa?searchID=480466&messageID=1419481
https://forums.sdn.sap.com/click.jspa?searchID=480466&messageID=1479212
Shortly:
Append structures are used for enhancements that are not included in the standard. An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.
http://help.sap.com/saphelp_erp2004/helpdata/en/cf/21eb61446011d189700000e8322d00/content.htm
Includes are used to group fields, an include structure can be assigned to many tables. If you add a fields to an include structure, all tables/structures, which contain that include structure, will be updated too.
http://help.sap.com/saphelp_erp2004/helpdata/en/cf/21ea6a446011d189700000e8322d00/content.htm
Regards,
Santosh

How to Transport Extract Structure and datasource

Hi all!
I had recently made enhancements to 0CO_PC_PCP_01 datasource.When I transported the datasource and the Extract structure, I noticed that only the append structure has been transported. The datasource has not been transported.
Could some one tell me how to collect the datasource and the Appended extract structure and transport them.
Thanks,
S.P

Hi Jaya,
I had already tried this already. When I selected the dtasource and selected the transport button. I got the message, action successfully executed. When I checked in SE09, I see no transport. Unless it asks me for a transport request, I will not see it in SE09, right.
~S.P

Different number of fields in extract structure and Datasource

Hi All,
There is a data source 0FUNCT_LOC_ATTR, which are showing 16 fields in the datasource. But when i went into the extract structure, it shows 25 fields. Is it any kind of bug?
thanks
Annie

Hi MTi,
Thanks for your reply. I checked in ROOSOURCE and ROOSFIELD table and found that we activated the datasource somewhere in 14.08.2008 and the delivered version is in 18.11.2008. Now i reactivated the datasource in RSA5 and could see all the fields in RSA6.
Actaully we posted the issue to SAP and they have come back with the same reply what you have mentioned.
Cheers
Annie

Differences between jdbc connection and datasource connection

Hi all
What are the differences between javax.sql.datasource and java.sql.connection.
Is the datasource needed on in distributed databases or ??
In a distributed EJB enviornment, what happens if a component has a transctionattribute setting as SUPPORTS and tries to commit data - will the ejb container start a transaction though the setting is SUPPORTS.
Thanks in advance.

Hi all
What are the differences between javax.sql.datasource
and java.sql.connection.
Both are database connections. A connection is a handle to database. When you are directly creating a connection by calling Drivermanager.getConnection(..) , you are creating a connection by yourself and when closing close() on it, the link to database is lost. On the other hand when you get a connection from a datasource, when you call the close() on it, it will not close the link to database, but will return to a connection pool where it can be reused by some other classes. It is always better to use a connection pool because creating connections are expensive
Is the datasource needed on in distributed databases
or ??
>
You can create datasource to any databse local or remote.
In a distributed EJB enviornment, what happens if a
component has a transctionattribute setting as
SUPPORTS and tries to commit data - will the ejb
container start a transaction though the setting is
SUPPORTS.
hmmm..i am not sure. I think the container sets the commit and rollback points for it . so container will override database settings.

DataSource - difference between ejb-location and location

Hi,
Does anyone know difference between ejb-location and location attribute specified in datasources.xml for an emulated datasource.
There are few connection leakage errors reported in log files though the connection and other database objects have been closed in finally block in all places.
So just wanted to find out whether specifying the same value for location as well as ejb-location is not the root cause of connection leakage errors.
Thanks in advance for any help.
Regards,
Smita

Smita,
Personally, I think you should make sure that all locations (in your "data-sources.xml" file) should be different -- although I can't tell you why.
According to the documentation, the "ejb-location" uses a connection pool and I exclusively use the "ejb-location".
Good Luck,
Avi.

Structural Authorization: Difference Between AUTSW-DFCON and AUTSW-ORGPD?

Dear All,
Can anyone explain to me the difference between AUTSW-DFCON and AUTSW-ORGPD in tbale T77S0?
And what is the relationship between these two switches?
Thanks!!

HI Mr. potato,
working off dilek's informative post you may be considering ? context vs non-context?
this image explains how context problems arise in HCM. http://help.sap.com/saphelp_470/helpdata/en/b3/bfb83b5b831f3be10000000a114084/content.htm
I would say generally, when an organization decides to use structural authorizations, they also need to take into account a "context solution". This is most frequently used to "lockdown" how different parts of the HR organization has different authority access to different groups of employees (potentially overlapping). As an HR manager i might have full read access on IT0002 for the entire company (root org), but IT0008 view access only for a sub-org unit.
in this case you need to use the DFCON switch. the 'most restrictive setting for dfcon is value 2. the most iberal setting is, 4. Generally, you need to test all 4 to figure out what works for you.
settings for dfcon:
http://help.sap.com/saphelp_470/helpdata/en/56/db5bc71a64c94f9f2e3cb63e14c867/content.htm

Difference between Switching Structure in CCA and Transfer Structure in PC

Hi experts,
Could anybody define the difference between Switching Structure in CCA and Transfer Structure in CO-PCP? I can't also define when we create Primary Cost Component Split, do we use only range of Primary Cost Elements in the Cost Components for the Primary Cost Component Structure? Thanks for the help!
Best Regards,
Georgi

This has been discussed please check it in forum
https://forums.sdn.sap.com/click.jspa?searchID=480466&messageID=114309
https://forums.sdn.sap.com/click.jspa?searchID=480466&messageID=1419481
https://forums.sdn.sap.com/click.jspa?searchID=480466&messageID=1479212
Shortly:
Append structures are used for enhancements that are not included in the standard. An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.
http://help.sap.com/saphelp_erp2004/helpdata/en/cf/21eb61446011d189700000e8322d00/content.htm
Includes are used to group fields, an include structure can be assigned to many tables. If you add a fields to an include structure, all tables/structures, which contain that include structure, will be updated too.
http://help.sap.com/saphelp_erp2004/helpdata/en/cf/21ea6a446011d189700000e8322d00/content.htm
Regards,
Santosh

EXACT DIFFERENCE BETWEEN FULL LOAD AND REPAIRFULL LOAD?

HI Champ,
Can anyone explain me the exact difference between full load and Repairfull load?Give e some senario where we can go for this?Please.....
10zin

Hi,
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets."
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
repair full request
Re: Repair Full Request
Thanks,
JituK

Difference between Field symbols and field group

Hi experts,
Can you please advice me what is the difference between field symbols and field groups.
Thanks in advance,
Logu.

Field symbols: are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field Groups:
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
A field group combines several existing fields together under one name
like
FIELD-GROUPS: fg.
then you can use one insert statement to insert values in fields of field-group.
INSERT f1 f2 ... INTO fg.
Field symbols
If u have experience with 'C', then understand this to be similar to a pointer.
It is used to reference another variable dynamically. So this field symbol will simply point to some other variable. and this pointer can be changed at runtime.
FIELD-SYMBOLS <FS>.
DATA FIELD VALUE 'X'.
ASSIGN FIELD TO <FS>.
WRITE <FS>.
Field symbols: are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field Groups:
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
example :
DATA: BEGIN OF SPTAB OCCURS 0,
line(1000), " or type string
END OF SPTAB.
DATA: IDX LIKE SY-INDEX.
field-symbols <FS1>.
split tb_sip AT ';' INTO table sptab.
LOOP AT SPTAB.
IDX = IDX + 1.
ASSIGN COMPONENT IDX OF STRUCTURE tb_detsip TO <FS1>.
If sy-subrc = 0.
<FS1> = SPTAB-line.
Endif.
Endloop.
append tb_detsip.
clear idx.
Field Groups / Extracts
http://help.sap.com/saphelp_46c/helpdata/EN/9f/db9ede35c111d1829f0000e829fbfe/frameset.htm
Field Symbols
http://help.sap.com/saphelp_46c/helpdata/EN/fc/eb387a358411d1829f0000e829fbfe/frameset.htm
Reward points if useful.

Difference between Extraction Structure and Datasource

Similar Messages

Maybe you are looking for