What are the DB tables for 0FI_GL_4

Hi experts,
Can any one tel me what are DB tables for the data source like 0FI_GL_4.
regrds
manoj

Tables:
BSEG - Segment
BKPF- Header
0FI_GL_O02 - Standard ODS - FIGL: Line Item
Regards
Naga

Similar Messages

What are the main tables for BOM (Bill of Materials)

Hi Gurus,
I need to know the tables involved in BOM (Bill of Materials) for Oracle EBS.
Can anyone point out the list of related tables?
Thanks

Hi Sudipta,
Following are the BOM main tables.
bom_bill_of_materials
bom_inventory_components
bom_reference_designators
bom_substitute_components
mtl_item_revisions
bom_operational_routings
bom_operation_sequences
bom_operation_resources
BOM_BILL_OF_MTLS_INTERFACE
BOM_INVENTORY_COMPS_INTERFACE
BOM_REF_DESGS_INTERFACE
BOM_SUB_COMPS_INTERFACE
MTL_ITEM_REVISIONS_INTERFACE
BOM_OP_ROUTINGS_INTERFACE
BOM_OP_SEQUENCES_INTERFACE
BOM_OP_RESOURCES_INTERFACE
MTL_RTG_ITEM_REVS_INTERFACE
=======================
Following are all tables of BOM.
BOM_ALTERNATE_DESIGNATORS
BOM_ALTERNATE_DESIGNATORS_TL
BOM_ATO_CONFIGS_TEMP
BOM_ATO_CONFIGURATIONS
BOM_BILLS_HEADER_TEMP
BOM_BILL_OF_MATERIALS
BOM_BILL_OF_MATERIALS_ARCHIVE
BOM_BILL_OF_MATERIALS_TEMP
BOM_BILL_OF_MTLS_INTERFACE
BOM_BILL_REVISIONS_B
BOM_BILL_REVISIONS_TL
BOM_CALENDARS
BOM_CALENDAR_DATES
BOM_CALENDAR_EXCEPTIONS
BOM_CALENDAR_SHIFTS
BOM_CAL_WEEK_START_DATES
BOM_CAL_YEAR_START_DATES
BOM_CMP_USR_ATTR_INTERFACE
BOM_COMPARISON_TEMP
BOM_COMPONENTS_B
BOM_COMPONENTS_EXT_B
BOM_COMPONENTS_EXT_TL
BOM_COMPONENT_COLUMNS
BOM_COMPONENT_OPERATIONS
BOM_COMPONENT_OPS_INTERFACE
BOM_COMPONENT_TYPES
BOM_COMP_OPTCLASS_TEMP
BOM_COMP_OPTIONS_TEMP
BOM_CONFIG_EXPLOSIONS
BOM_COPY_ORGANIZATION_LIST
BOM_COPY_STRUCTURE_ACTIONS
BOM_COPY_STRUCTURE_REQUEST
BOM_CTO_MLSUPPLY_MAIN_TEMP
BOM_CTO_MODEL_ORGS
BOM_CTO_ORDER_DEMAND
BOM_CTO_ORDER_LINES
BOM_CTO_ORDER_LINES_UPG
BOM_CTO_OSS_COMPONENTS
BOM_CTO_OSS_ORGS_LIST
BOM_CTO_SRC_ORGS
BOM_CTO_SRC_ORGS_B
BOM_DELETE_ENTITIES
BOM_DELETE_ERRORS
BOM_DELETE_GROUPS
BOM_DELETE_SQL_STATEMENTS
BOM_DELETE_SUB_ENTITIES
BOM_DEPARTMENTS
BOM_DEPARTMENT_CLASSES
BOM_DEPARTMENT_RESOURCES
BOM_DEPENDENT_DESC_ELEMENTS
BOM_DEPEND_DESC_ELEM_ARCHIVE
BOM_DEPT_RES_INSTANCES
BOM_EAM_DEPT_APPROVERS
BOM_EXCEPTION_SETS
BOM_EXCEPTION_SET_DATES
BOM_EXCLUSION_RULE_ARCHIVE
BOM_EXCLUSION_RULE_DEF
BOM_EXPLOSIONS
BOM_EXPLOSIONS_ALL
BOM_EXPLOSION_TEMP
BOM_FORM_QUERY
BOM_IMPLOSION_TEMP
BOM_INTERFACE_DELETE_GROUPS
BOM_INVENTORY_COMPONENTS
BOM_INVENTORY_COMPONENTS_TEMP
BOM_INVENTORY_COMPS_ARCHIVE
BOM_INVENTORY_COMPS_INTERFACE
BOM_INV_COMPONENTS_TEMP
BOM_ITEM_ATTACH_CATEGORY_ASSOC
BOM_ITEM_BACKFLUSH_SUBINV
BOM_LISTS
BOM_LOW_LEVEL_CODES
BOM_MIXED_MODEL_MAP_CELLS
BOM_MIXED_MODEL_MAP_HEADER
BOM_MIXED_MODEL_MAP_PROCESSES
BOM_MIXED_MODEL_MAP_RES
BOM_OPERATIONAL_ROUTINGS
BOM_OPERATION_NETWORKS
BOM_OPERATION_RESOURCES
BOM_OPERATION_RESOURCES_EFC
BOM_OPERATION_SEQUENCES
BOM_OPERATION_SEQUENCES_TEMP
BOM_OPERATION_SKILLS
BOM_OP_NETWORKS_INTERFACE
BOM_OP_RESOURCES_ARCHIVE
BOM_OP_RESOURCES_INTERFACE
BOM_OP_ROUTINGS_ARCHIVE
BOM_OP_ROUTINGS_INTERFACE
BOM_OP_SEQUENCES_ARCHIVE
BOM_OP_SEQUENCES_INTERFACE
BOM_PARAMETERS
BOM_PERIOD_START_DATES
BOM_REFERENCE_DESGS_ARCHIVE
BOM_REFERENCE_DESIGNATORS
BOM_REF_DESGS_INTERFACE
BOM_RESOURCES
BOM_RESOURCES_EFC
BOM_RESOURCE_CHANGES
BOM_RESOURCE_DOWNCODES
BOM_RESOURCE_EMPLOYEES
BOM_RESOURCE_EQUIPMENTS
BOM_RESOURCE_FLEX_FENCES
BOM_RESOURCE_SETUPS
BOM_RESOURCE_SHIFTS
BOM_RES_INSTANCE_CHANGES
BOM_RTGHEADER_TEMP
BOM_RTG_ITEM_REVISIONS_ARCHIVE
BOM_RTG_NETWORK_TEMP
BOM_RTG_OPERATION_TEMP
BOM_RTG_OPER_RES_TEMP
BOM_RTG_RESOURCE_TEMP
BOM_RTG_SUB_RESOURCE_TEMP
BOM_RULES_B
BOM_SETUP_TRANSITIONS
BOM_SETUP_TYPES
BOM_SHIFT_DATES
BOM_SHIFT_EXCEPTIONS
BOM_SHIFT_TIMES
BOM_SMALL_EXPL_TEMP
BOM_SMALL_IMPL_TEMP
BOM_STANDARD_OPERATIONS
BOM_STD_OP_BONUS_CODES
BOM_STD_OP_RESOURCES
BOM_STD_OP_RESP_EXCLUSIONS
BOM_STD_OP_SCRAP_CODES
BOM_STD_SUB_OP_RESOURCES
BOM_STRUCTURES_B
BOM_STRUCTURES_EXT_B
BOM_STRUCTURES_EXT_TL
BOM_STRUCTURE_EXT_B
BOM_STRUCTURE_REVISIONS_B
BOM_STRUCTURE_REVISIONS_TL
BOM_STRUCTURE_TYPES_B
BOM_STRUCTURE_TYPES_TL
BOM_SUBSTITUTE_COMPONENTS
BOM_SUBSTITUTE_COMPS_ARCHIVE
BOM_SUB_COMPS_INTERFACE
BOM_SUB_OPERATION_RESOURCES
BOM_SUB_OPERATION_RESOURCE_EFC
BOM_SUB_OP_RESOURCES_INTERFACE
BOM_WORKDAY_PATTERNS
HTH
Sanjay

What are the standard tables for plant maintenance in r/3

I need the list of standard tables for plant maintenance in r/3. and also
is there any way we can find the field name and table which it belongs to in r/3, based on the description of the field.

I NEED THE FIELD NAMES FOR FOLLOWING FIELDS AND CORRESPONDING TABLE NAMES
Equipment status
registration number
insurance type
insurance type description
registration date
expiry date
insurance companies
expiry date
policy number
amount insured
premium paid
created by ..so ..on
for our report in PM .. insurance data report
THANKS

What are the field names for below mentioned

Hello Friends
What are the fields names for below tables
in EKKO
Purchase Document Date
Net Value of the purchase document.
In EKPO
Item Description
From which place We bought it. (It means in Sales Items there we can know from which plant we sold the goods, like in EKPO, there is any field like this)
Please let we are defining the report to find out the stock availability for perticular storage location using select Options plant, company code, material no.
How many tables involve her to build this report. and also field names, they come under which table.
Please send me this information ASAP. PLz Plz Plz..........
Regards
Praveen

You can check the fields of these tables via SE11
Purchase Document Date - EKKO-BEDAT
Item Description - EKPO-TXZ01
Net price per item - EKPO-NETPR.
Regards,
Rich Heilman

What are the Update tables?

In LO Delta scenario, Data posted parallel into document tables and update tables. What are the Document tables? What are the Update tables?
Give example for Application 11, which is document tables, and update tables?

Hello Mannev,
Document tables are the actual application tables where the data is posted when you post a document in R/3.
Examples can be MSEG, VBRK etc.
Update tables are the intermediate tables which store data read from document tables. The V3 runs collects deltas in form of LUWs from these update tables and populates the delta queues.
hope this helps..
thanks,

What are the optimal values for mac and arp timeout values

Hi Guys.
What are the best values for "mac address-table aging-time" and "arp timeout" by following scenarios?:
- single sg300-10 as layer3-switch with a maximum of 10 local (direct connected) hosts
- and a 3750x-stack with 100 local hosts + hsrp with a other stack of the same sort
or for asa 5520 as internet gateway for 500 clients?
I use at the moment a mac aging-time from 300 seconds and a arp timeout from 3600 seconds.
Is this o.k.?
Thanks.

Marvel.
As far as enhancing the CLI, it will of course be enhanced when new firmware releases provide new features. As far as making it more IOS-like, best to my knowledge, no. The only other supported CLI on the SB switches are on the SX500 series and SX200E series which the CLI are all consistent. If you bought a SX500 series the commands are nearly identical minus the different feature sets.
-Tom
Please mark answered for helpful posts

What are the possible values for the JOB status?

What are the possible values for the JOB status in the table TBTCP and significance for each?

Hi,
Have a look at include LBTCHDEF.
The standard include from SAP.
-> Definitions and Constants for Function group BTCH
Kind Regards
Raymond

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

What are the input parameters for Function Module

Dear Experts,
I want to generate a Sales Tax returns report,those fields are not available in my existing Datasources.
For that i want to write a Generic Datasource with Function Module.
audat
bukrs
vkorg
vtweg
spart
aurat
auart
netwr
mwsbp
kschl zedp(consition type)
kschl zvat(condition type)
ksch zcst(condition type)
matkl material group
Here what are the Input parameters for Function Module.
Thanks in Advance.
Srinivasan.

Srinivasan-
For creating a Generic extractor based on a FM, you first of all need to know what is going to be your structure.. i.e. what all fields you need to pull from what all tables. A functional consultant may help you identify the exact DB tables.
Once you know them, hand over the requirement and the pdf mentioned by Krishna to the ABAP guy, he would be able to take this up further.
Also decide 1st whether you would be using a full load or delta. There is a slight difference in the way they are built.
Let me know how it goes.
-Bhushan.

What are the best approaches for mapping re-start in OWB?

What are the best approaches for mapping re-start in OWB?
We are using OWB repository 10.2.0.1.0 and OWB client 10.2.0.1.31. The Oracle version is 10 G (10.2.0.3.0). OWB is installed on Linux.
We have number of mappings. We built process flows for mappings as well.
I like to know, what are the best approches to incorportate re-start options in our process. ie a failure of mapping in process flow.
How do we re-cycle failed rows?
Are there any builtin features/best approaches in OWB to implement the above?
Does runtime audit tables help us to build re-start process?
If not, do we need to maintain our own tables (custom) to maintain such data?
How did our forum members handled above situations?
Any idea ?
Thanks in advance.
RI

Hi RI,
How many mappings (range) do you have in a process flows?Several hundreds (100-300 mappings).
If we have three mappings (eg m1, m2, m3) in process flow. What will happen if m2 fails?Suppose mappings connected sequentially (m1 -> m2 -> m3). When m2 fails then processflow is suspended (transition to m3 will not be performed). You should obviate cause of error (modify mapping and redeploy, correct data, etc) and then repeat m2 mapping execution from Workflow monitor - open diagram with processflow, select mapping m2 and click button Expedite, choose option Repeat.
In re-start, will it run m1 again and m2 son on, or will it re-start at row1 of m2?You can specify restart point. "at row1 of m2" - I don't understand what you mean (all mappings run in Set based mode, so in case of error all table updates will rollback,
but there are several exception - for example multiple target tables in mapping without corelated commit, or error in post-mapping - you must carefully analyze results of error).
What will happen if m3 fails?Process is suspended and you can restart execution from m3.
By having without failover and with max.number of errors=0, you achieve re-cycle failed rows to zero (0).This settings guarantee existence only two return result of mapping - SUCCSES or ERROR.
What is the impact, if we have large volume of data?In my opinion for large volume Set based mode is the prefered processing mode of data processing.
With this mode you have full range enterprise features of Oracle database - parallel query, parallel DML, nologging, etc.
Oleg

What are the payment tables in R12?

Hello,
What are the payments tables in R12,
I need retrieve the below columns from tables in R12
Payment_id,
Invoice_num, Invoice_amount
Payment_num, Payment_amount
please help us,
Thanks,
Raj

Hello,
Thanks for your helping,
1). DUNS_NUMBER
2). JP_DUNS_NUMBER
3). CHECK_AMOUNT
4). CHECK_NUMBER
5). BANK_NUMBER
6). DISB_BANK_ACCT
7). COMPANY,
8). VENDOR_NAME
9). CMP_IDF
Please help me to get this columns in payments
If you know anything about NACHA Payment Format report customization in R12 please help me, Im struggling to customize this report in R12
Thanx,
<-- Raj -->

What are the main tables of SITs?

Hi
What are the main tables of SITs? How can I find out the tables related to SITs?
Regards
Rahman

PER_SPECIAL_INFO_TYPES: This table holds the definitions of SITs that are available to each Business Group. Each special information type is a user defined structure for the personal analysis key flexfield. The name of the special information type is the same as the name of the corresponding key flexfield structure.
PER_SPECIAL_INFO_TYPES_V : This table has the Employee's SIT info. A supplementary view used to simplify forms coding
PER_SPECIAL_INFO_TYPES_V2 : A supplementary view used to simplify forms coding.

What are the other tables in B2 cluster

hi experts,
what are the other tables like ZL table in B2 cluster..and what data is stored in them.

Results related to a time evaluation period in cluster B2
PSP
Personal work schedule
Time evaluation result
For each day
QTACC
Generation of quota entitlement
Time evaluation result
For each day
QTTRANS
Transfer pool
Time evaluation result
For each day
ZES
Time balances for each day
Time evaluation result
For each day
SALDO
Cumulated time balances
Time evaluation result
Time evaluation period
ZL
Time wage types
Time evaluation result
For each day
VS
Variable balances
Time evaluation result
For each day
CVS
Cumulated variable balances
Time evaluation result
Time evaluation period
FEHLER
Messages
Time evaluation result
For each day
PT
Time pairs
Raw data/time evaluation result
For each day
KNTAG
Core night work (relevant only for the German country version)
Time evaluation result
For each day
Results related to a time period in cluster B2
Table
Description
Origin
Time Dependency
VERT
Substitutions
Copy of infotype 2003
Period
ABWKONTI
Absence quotas
Copy of infotype 2006
Period
AB
Absences
Copy of infotype 2001
Period
ANWES
Attendances
Copy of infotype 2002
Period
RUFB
On-call availability
Copy of infotype 2004
Period
MEHR
Overtime
Copy of infotype 2005
Period
ANWKONTI
Attendance quotas
Copy of infotype 2007
Period
SKO
Time transfer specifications
Copy of infotype 2012
Period
ALP
Different payment
Raw data
Pointer to table entry
C1
Cost distribution
Raw data
Pointer to table entry
Edited by: BALAPANI on Oct 19, 2009 10:38 AM

What kind of financial periods exist in SAP? What is the relevant table for

What kind of financial periods exist in SAP? What is the relevant table for that?

Hi venumadhav
                In FInancial Accounting , Period is during time that you post G/L account and you have to close period after end of period and you will see the balance each G/L Account in each period.
                 There are 12 normal period and 4 special period (normal case , but can be changed by configuration ). normal period are Jan , Feb ,...Dec and Special period are the extended period that use for posting in special case .For example if you close period in Dec and you have to adjust G/L Account by auditor checking , you can post G/L Account to special period . special period are 13,14,15,16. 12 may use for Audit , 13 may use for changing after Sending to audit and found something mistake . that 's sample.
              normally there is posting date to control the period (BUDAT) in the table BSIS. if the posting date is in the during time of period , we can say this posting is in that period .
posting date : 03.09.2007            period : 09
posting date : 30.11.2007            period : 11
Regards
Wiboon

What are the pre requisites for SAP SRM7.0 DB Rrefresh?

Hi,
What are the pre requisites for SRM DB Rrefresh?
Thanks

Hello Peter,
When it comes to DB refresh you need to know what all the client dependent data which needs to be retained.
For example you need RFC connections, Variants, User master etc.
As a pre task of Database refresh you may need to export the tables which are related to this so that once the database is refreshed you need to import them.
Ensure the proper backup of production database is available. Also check all the STMS configurations which need to be retained again.
Make sure that you need to have enough disk space which can accommodate your production data in to the pre production system.
These are some of the general consideration one needs to have but again it depends on the environment on which one runs SAP systems.
Regards
Vivek

What are the DB tables for 0FI_GL_4

Similar Messages

Maybe you are looking for