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

Similar Messages

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 main tables using in vendor performance report.

what are the main tables using in vendor performance report.
how many select statements are in ABAP reports.

Refer the links -
vendor performance report !!!
vendor performance report
vendor performance report
I need standard vendor performance report
Regards,
Amit
Reward all helpful replies.

What are the main tables to refer in ASAP(asap 7.2)?

what are the main tables to refer in ASAP(asap 7.2)?

what are the main tables to refer in ASAP(asap 7.2)?

What are the main uses for a Macbook Pro, and also for a Macbook Air?

I'm curious of whether I should buy a Macbook Pro, or Macbook Air. Before I make my decision I would like to know what are the main purpaces for each Macbook.

Here's an article that compares the two.
http://news.cnet.com/8301-13579_3-57458148-37/13-inch-macbook-air-vs-13-inch-mac book-pro-which-should-you-buy/?tag=postrtcol;posts

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

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 main reasons for SAP-HR Implementation Failures?

Dear Consultants,
Can some one shed the light on the following items:
1. At least 3 main reasons for failure of SAP-HR Implementations?

Hi,
Check this link
http://searchsap.techtarget.com/news/article/0,289142,sid21_gci892265,00.html

What are the main steps to be taken care while doing recording for LSMW

Hi,
I am facing problem in LSMW.
Can anybody suggest me that What are the main steps to be taken care while doing recording for LSMW for recording mm01 ?
thanks'
naresh

Hi,
Recording in LSMW is similar as SHDB.
in LSMW after you give Project-Subproject and Object.
1)Go to-> Maintain Object Attributes -> double click
2)Press Display/Change Button at top left to make editable mode.
3)Select radiobuton -> Batch Input -> Give Recording name say Z_mm01
4) Click the Recording Overview boton on right -> Give TCode which u want to record....
Rest refer the Document link attached.
Please find the links to various threads on the same.
Re: LSMW - Using a BAPI
BAPI, IDOC in LSMW
Upload the data in LSMW using BAPI
This one is the most complete document for the same
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://service.sap.com/lsmw.
Regards
Kiran

What are the main instruction followed in flatfile for hierarchy

what are the main instruction followed in flatfile for hierarchy

Hi,
If you want to load InfoObjects in hierarchy form, you have to activate the indicator With Hierarchies for each of the relevant InfoObjects in the InfoObject maintenance. If necessary, you need to specify whether the entire hierarchy or the hierarchy structure is to be time-dependent, whether intervals are permitted in the hierarchy, whether additional node attributes are allowed (only when loading using a PSA), and which characteristics are allowed.
The detailed procedure is listed in the link below
http://help.sap.com/saphelp_bw33/helpdata/en/b0/ab8e3cb4340b14e10000000a114084/frameset.htm
Remya

What are the CSS selectors for the FireFox 4 Main Menu?

What are the CSS selectors for the FireFox 4 Main Menu?
[http://img228.imageshack.us/img228/5512/ff4menubar.gif http://img228.imageshack.us/img228/5512/ff4menubar.gif]

Still the same as in Firefox 3.5 and 3.6 versions:
<pre><nowiki>#main-menubar
#file-menu
#edit-menu
#view-menu
#history-menu
#bookmarksMenu
#tools-menu
#helpMenu
</nowiki></pre>

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 main differences between 3 three important class types

PP members
What are the main differences between class type 300(variants) , class type 200 (configurable objects) & 001 ( material class)
Please elucidate on the above
Thanks
Suren R

Hi,
The class type is a central concept in the classification system. The class type determines how classes are processed, and how objects can be classified and retrieved in these classes. In Customizing for Classification, you define the settings for a class type. You define class types for a specific object type, such as materials. You can then use classes of this class type to classify objects of this object type.
When you first create a class, you must enter a class type for the class. Each class type is a closed system. There is no link between the different class types.
he class type determines the following:
Which object types you can assign to a class
Which class maintenance functions you can process
Whether you can classify objects in more than one class
Which class statuses, organizational areas, and text types are supported in class maintenance functions
Whether you can use engineering change management for classification
Which filter functions you can use to restrict the search result
All materials can be classified with class type 001. Class type 300 is for variant configuration the variants under a class item are called as variants and can be picked during sales order creation. Class type 200 is for classes that are used as class items in bills of material. You can classify the same materials separately in these class types.
This is basically used to differentiate the BOM class items.
Prakash

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 main transaction codes in XI?

What are the main transaction codes in XI?

SAP XI TRANSACTION CODES
ALRTCATDEF- Alerts Configuration.
ALRTDISP - Display of Alerts Created
SXMB_IFR -> Start Integration Builder
SXMB_MONI -> Integration Engine - Monitoring
SXI_MONITOR -> XI: Message Monitoring
SXI_CACHE -> To Access IS runtime cache
SXI_SUPPORT -> Test all the Repository and Directory Objects
SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter
IDX2 -> idoc metadata
IDX5 -> monitor idoc adapter
SM21 -> log di sistema
ST22 -> dump abap (analisi di eccezioni)
SMQ1 -> messages inbound e outbound queue
SMQ2 -> messages inbound e outbound queue
SMICM -> J2EE administration
ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.
ST03 -> workload.
SCC4 -> visualizza mandanti del sistema
WE20 -> partner profiles
sale - ale settings
RZ10 - edit system profile
SM59 ->mantain rfc destinations
BD64 -> mantain distribution model (trasformazioni)
SU01 -> users
AL08 -> list all logged users(user login logon)
SE10 -> Change Request
SE09 -> Change Request
WE05 -> All idocs
WE19 -> IDoc Test Tool
WE21 -> port definition
SE11 -> Data dictionary
SM21 -> log sistema xi
se37 -> mantain funcion modules
SICF -> http server configuration
SMGW -> trace, alzare livello di trace.
BD13 ->
BD64 -> modelli di distribuzione
PFCG -> Roles
tabella TSTC -> sap transactions codes
tabella TSTCT -> transaction descriptions
STMS -> transports management
SPAM -> apply ABAP support packages
SPAU -> manage objects after apply support packages
SE01 -> manage change requests
SLDCHECK -> Test SLD Connection
SLDAPICUST-> SLD API Customizing
SXMB_ADM -> Integration Engine - Administration
SXMB_MONI_BPE -> Process Engine - Monitoring
SE38 -> ABAP Editor
SE11 -> ABAP Dictionary
ST22 -> ABAP dump analysis
SPROXY-> ABAP Proxy Generation
SE80 -> Object Navigator
ABAPDOCU -> ABAP Documentation and Examples
SE24-> Class Builder
SM21-> Online System Log Analysis
SMQ1-> qRFC Monitor (Outbound Queue)
SMQ2-> qRFC Monitor (Inbound Queue)
RZ70-> SLD Administration
SM58-> Asynchronous RFC Error Log
SM59-> RFC Destinations (Display/Maintain)
SMICM-> ICM Monitor
WE60-> Documentation for IDoc types
BD87-> Status Monitor for ALE Messages
IDX1-> Port Maintenance in IDoc Adapter
IDX2-> Meta Data Overview in IDoc Adapter
WE05-> IDoc Lists
WE02-> Display IDoc
WE19-> Test tool
WE09-> Search for IDocs by Content
WE20-> Partner Profiles
WE21-> Port definition in XI
SE16-> Data Browser
SE93-> Maintain Transaction Codes
SM30-> Call View Maintenance
SU01-> User Maintenance
SM02-> System Messages
BD54 -Logical System Creation.
SWXF_PBUILDER -> for Detail BPM Process
SMQS - > to register the destination in QOUT scheduler
WEOUTQUEUE - > to start the queue processing
SMQR - > to register the queue
IDXPW - > to activate the IDOC message package
IDXP - > to monitor the message packages.
SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes.
http://www.erpgenie.com/abaptips/content/view/452/62/

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

Similar Messages

Maybe you are looking for