List of tables n transaction in CRM

Hi All,
Am new to CRM and in learning process. Can u please give me a list of tables n transactions generally used in CRM.
**Points will be awarded
Thanks a lot in advance
Ajay

Dear Ajay,
BUT000 : BP: General data
BUT020 BP: Addresses
BUT050 BP relationships/role definitions: General data
BUT051 BP Relationship: Contact Person Relationship
Similar to BUT050 , additionally contains Contact Persons Address data
BUT0BK Business Partner: Bank Data & Details
BNKA Bank Master Data
BUT100 BP: Roles
ADR2 Telephone Numbers (Business Address Services)
ADR6 SMTP Numbers (Business Address Services)
ADRC Addresses (Business Address Services)
TSAD3T Table containing the Title text against a Title No.
COMM_PRODUCT Master Table for Product
CRMM_BUAG Master table for Business Agreement
CRMM_BUAG_H Header Data for Business Agreement such as Tax Category, Tax Characteristic, Form key, Business Agreement Class. Data in this table correspond to ISU CRMD_ORDERADM_H Contains the Header Information for a Business Transaction.
Note:
1. It doesnt store the Business Partner
responsible for the transaction. To
get the Partner No, link it with
CRM_ORDER_INDEX.
2. This table can be used for search
based on the Object Id(Business
Transaction No).
CRMD_CUSTOMER_H Additional Site Details at the Header Level of a Business Transaction
CRMC_PROC_TYPE Master table Business Transaction Type
CRMC_PARTNER_FCT Definition of Partner Functions
SCPRIOT Priorities for Activities with priority text.
CRMC_PROC_TYPE_T Text for a transaction type
CRMC_ACT_OBJ_T Objective Number and Text for Activities
TJ30T All the status code and text
CRMC_PR_ASSIGN : Transaction Type and its Transaction Type Object.
IBIB : Installed Base/Ibase
IBIN : Installed Base Components
Hope this will help.
Regards,
Naveen.

Similar Messages

Urgent :Fetching CRM Activity categories to the master list category table

Hi all,
I am working with groupware Integration. I am following "Best Practice" that provided in help.sap.com
I m using mySAP CRM 4.0 it is in SP-09.
the problem is in "Fetching CRM Activity categories to the master list category table" for this I am refered
http://help.sap.com/saphelp_crm40/helpdata/en/56/0efff114e54f3394bde360f3bebb4b/frameset.htm
in this page says that "GWA_FILL_ACTCAT_TO_MASTERCAT" function module is used for transforing data.
but if i am checking in my system this function module is not exist.
Please give the way for solution.
Thaks in advance.
Sridhar.
Message was edited by: Shridhar Deshpande
Message was edited by: Shridhar Deshpande

Hi Shridhar,
I am also working on the same object .
"GWA_FILL_ACTCAT_TO_MASTERCAT" is not a function module it is a Program so pl. go to SE38 and execute the program.
Cheers,
Nilesh
pl. reward points if this helps out.

Field sales related tables and Transaction code

Dear SAPGurus,
I have been working with field sales activities in mySAP CRM..
Can I have the list of the tables and transaction code related to Field sales sales activies..
I am grateful for ur help....
I would like to appreciate u by rewarding the points
Thanks a lot

Hi Pratik Patel,
Thank u very much for sending the table names.They are all very useful unto me
Can I have the more table in this area
If u have the CRM Data model and its relationship...Pls share with me..
I appreciate ur help by rewarding the points
Regards,
CRM Consultant

Error in Sales Transaction in CRM 4.0 ?

Hi All,
We are working on CRM 4.0 i have created a sales transaction in WEB and transaction will see in CRM and it is getting downloaded to R/3.
But when I go back to CRM and check Sales Transaction it is showing me error as "An error has occured in the system XYZCLNT100 while copying the document".
And i have been check in SMQ1&SMW01 ..in both T codes there is no error ..
How can i figure out this problem ?
can anyone help me in this regard?
Thanks in advance.

Please look into note 490932 for any issues of this nature
This note gives an insight into possible error causes during the download or upload of sales transactions between CRM and R/3 and helps you correct these errors. This note is relevant for CRM Release3.0.
It is also relevant for releases higher than 3.0.
Other terms
Download, initial, delta, delta download, SALESDOCUMENT, BUS_TRANS_MSG, event 00501014 501014
Reason and Prerequisites
The error causes may be included an incorrect configuration or missing system settings. The note only focuses on the sales transaction-specific configuration of the data exchange, but not on the settings for CRM Middleware in general or for other CRM Server applications.
Solution
In CRM Release 3.0, the following sales document items are transferred to the R/3 System:
Sales items
Customer return items
Substitute delivery item
Credit memo request items
Debit memo request items
As a leading system for the order entry, CRM only transfers data to the R/3 System if it is relevant for the logistical subsequent processing (delivery, billing). For this reason, requests for quotations and quotations themselves are not transferred to the R/3 back-end system with the standard delivery. With SAP note 455678, you can use a modification solution to also transfer quotations entered in CRM to the R/3 back-end system.
 Restrictions of note 455678:
If you are using this solution, you cannot create any sales orders with reference to customer quotations in CRM.
Mixed document processing (partially customer quotation items and partially sales order items) is not supported in the R/3 System and is therefore not possible during the quotation upload. The solution specified here only performs the upload for documents that consist of quotation items only.
The quotation items must be defined in the Customizing for copying. This solution does not cover scenarios where the order is generated from the quotation as a result of a status change. Therefore, quotations entered in SAP Internet Sales (in particular) cannot be transferred to the R/3 System.
Only completion rule 'A' ('Completed with one-time reference') is supported in the R/3 System.
Sales transaction-specific settings for the data exchange
1. Basic administrative settings for the replication of sales transactions
a) The BDoc relevant for the distribution of all transaction types is called BUS_TRANSACTION_MESSAGE. In transaction SMOEAC, the relevant R/3 site must be subscribed to the corresponding publication 'All Business Transactions (MESG)' so that sales documents can be distributed to the R/3 back-end system. (To create a subscription, select the 'Subscription' object type in the 'Object type' selection list in transaction SMOEAC and then select the 'Object -> Create' function from the application menu or the corresponding symbol from the application function bar. The Subscription Wizard, which supports you during the creation of a new subscription, is started as a result.)
b) Check to see whether the current CRM release has been maintained in the R/3 back-end system in the CRMPAROLTP table. This has to be taken into account in particular after an upgrade. You can maintain the CRMPAROLTP table in transaction SM30 in the R/3 back-end system:
 Parameter name "CRM_RELEASE"
 Param. value "30A"
c) Event 00501014 must be activated in the R/3 back-end system so that the delta download of sales transactions from the R/3 back-end system to CRM works. The event must also be active for the upload of sales transactions from CRM to R/3.
d) The event is activated automatically after a successful initial download. Call transaction R3AC4 ('Object Class Activation') in CRM and check whether the following entries exist:
 Object class "BUSPROCESSND"
 RFC destination <R/3 destination>
 Select your entry and then choose 'Events by Object Class' (branch to the TBE31 table in the R/3 back-end system). The following entries must exist:
 Event "00501014"
 Obj. class "BUSPROCESSND"
 Function "CRS_SALES_COLLECT_DATA"
 If you do not see these entries, your initial download was not completed successfully.
e) In transaction BD97 of your CRM system, the R/3 back-end system must have been maintained as the standard BAPI destination. Check the V_TBDLS view to see whether your R/3 back-end system has been defined as a logical system. A termination message in the SAPLCRM_ DISTRIBUTED_LOCKING program when you call a transaction in CRM indicates the missing destination assignment.
Refer to notes 597812 and 674487. According to note 597812, the cross-system lock is processed using the RFC destination of the CRM middleware (SMOF_ERPSH table). However, the aforementioned entry in transaction BD97 for the Standard BAPI destination is still used to branch via the document flow to the R/3 system.
f) In Release 3.1I, you can only have one entry for the RFCDEST field (RFC destination) in the CRMRFCPAR R/3 table.
2. Definition of sales transaction-related Middleware parameters
a) If you do not want a BOM explosion to occur for document items in CRM during the transfer to the R/3 back-end system, make the following settings in transaction R3AC6:
 Key "R3A_SALES"
 name "NOSTRUCTURE"
 value "X"
 This would make sense, for example, if you have already carried out a BOM explosion on the mobile client and if you do not want a new BOM explosion in the R/3 back-end system.
 Make sure that the assigned item numbers in the sales transaction/sales document are set differently for main items and subitems so that no item numbers are assigned twice after the transfer and the BOM explosion in the R/3 System. The item numbers of the main items must be set identically in CRM and R/3. For more information, see note 496906.
 Example:
 CRM sales transaction
 Pos.Nr. Item No. Product
 100 MAT1
 200 MAT2
 R/3 order
 Pos.Nr. Item No. Material
 100 MAT1
 101 Subitem1
 102 Subitem2
 103 Subitem3
 104 ...
 200 MAT2
 You can maintain the item number assignment for the transaction types (CRM) or for the sales document types (R/3) in the Customizing.
b) If a document is created in CRM and transferred to the R/3 back-end system, the warning messages of the transferred R/3 back-end document can also be displayed in the CRM document. In this way, you can recognize, for example, in the CRM document whether the transferred R/3 back-end document is incomplete and has to be postprocessed so that it can be further processed logistically. For this purpose, make the following settings in transaction R3AC6:
 Key "R3A_SALES"
 name "COLLECT_WARNINGS"
 value "X"
c) When you transfer a CRM document to R/3, you have the following control options with regard to pricing:
 Key "R3A_SALES"
 name "PRICINGTYPE"
 value
 'B' = new pricing
 or
 'C' = copy manual pricecomponents,
 redetermine others
 or
 'G' = Copy price components unchanged,
 redetermine taxes (this value is
 delivered as a default setting)
3. Definition of the R/3 dummy division in CRM
 Note that no division exists in CRM in transactions at header level. In the R/3 order, however, the header division is a mandatory field. Thus, the R/3 dummy division must be maintained in CRM Customizing so that it can be determined during the transfer of a document. Otherwise, the order cannot be transferred to the R/3 back-end system.
 Customizing path: 'Customer Relationship Management -> Master Data -> Organizational Management -> Division Settings -> Define Use of Division and Dummy Division'.
 The use of several dummy divisions can be programmed in the CRM_DATAEXCH_AFTER_BAPI_FILL BAdI in the CRM_R3_SALESDOCUMENT_UPLOAD function module.
Hints for the initial download
Filter settings
In transaction R3AC1, you set the filters for the initial/delta download of business objects. In the SALESDOCUMENT business object, you can set the filters for the order download from R/3 to CRM. For successful execution of the initial download, you have to set at least the VBAK-ERDAT filter criterion (document entry date) for the SALESDOCUMENT business object. This filter setting is required for the successful completion of order downloads.
After you have completed these filter settings, you have to transfer these settings to the R/3 System. Select 'Filter sync.(R/3)'.
Choose your R/3 System as a source site and check whether you are using the VBAK-ERDAT filter criterion:
Example:
Table/Structure Field OP Low
VBAK ERDAT Greater than <Date>, for example, 20020128
The date must be entered in the same form as it is stored on the database (YYYYMMDD)!
The following filter criteria are also available:
VBAK-AUART Sales document type
VBAK-SPART Division
VBAK-VBTYP Sales document category
VBAK-VKORG Sales organization
VBAK-VTWEG Distribution channel
We recommend that you also use sales document numbers (VBAK-VBELN) as a further filter criterion. With this criterion, you can carry out an initial download according to sales document number intervals. The advantage of this filter criterion is that if your initial download terminates due to an error, you can restart the download after correcting the error as of the sales document number for which the error occurred. In this way you avoid having to restart a download for sales documents that have already been replicated.
Example:
Table/Structure Field OP Low High
VBAK VBELN zwisch. 0005000000 0005099999
Enter the field contents in the same way as it is stored on the R/3 database (leading zeros).
If you want to use this filter criterion, go to transaction SM30 and make the following entry in the SMOFFILFLD table:
Object name Table/Structure name Field name
SALESDOCUMENT VBAK VBELN
Note 497327 deals with possible filter-specific problems during the delta download that can occur due to missing R/3 back-end entries.
Block size
In this context, the block size specifies how many documents are selected in a transaction and transferred to CRM as a BDoc. The block size is defined on the system. The default value may have to be set to a lower value if problems occur (for example, memory overflow during the selection in the R/3 System). If the initial download terminates, check the dump log in the R/3 System (transaction ST22). The TIME_OUT or STORAGE_FREE_FAILED runtime errors indicate that the block size is too large. In this case, reduce the block size and restart the download. In addition, you can clarify with your Basis Administration whether the rdisp/max_wprun_time kernel parameter is large enough (this avoids a TIME_OUT error).
Basically, you should only download a few documents during the first download to check whether the system settings are correct. In this way, you can identify possible Customizing errors and correct them before the large load.
Queue processing during the initial download
In the case of very large transfer data sets, it may make sense to process the initial download in parallel within one object (object-internal parallel initial download) to complete the initial data transfer faster. Note 350176 describes the corresponding procedure.
Queue processing during the upload/delta download
Queues in CRM are defined in the SMOFQFIND table (for example, from CRM to CDB or from CRM to R/3).
For the BUS_TRANS_MSG BDoc type, the default setting of the queue processing is that all orders for a customer are processed in one queue.
As an alternative, you can set the queue processing in such a way that each order is processed in a separate queue. As a result, an individual order can no longer block the processing of other orders if an upload problem has occurred.
If you prefer this queue processing, go to transaction SM30 and make the following change in the SMOFQFIND table:
Select the BUS_TRANS_MSG BDoc type and change the segment field name from QUEUE_NAME to OBJECT_ID.
In the same way, you can also set the queues for the delta download in the R/3 back-end system in such a way that each order is processed in a separate queue. If you prefer this queue processing, go to transaction SE16 in the R/3 back-end system and make the following change in the CRMQNAMES table:
Select the entry for the SALESDOCUMENT object and change the BAPIFLD field from SOLD_TO to DOC_NUMBER (with BAPIOFFSET=3 and BAPIFLDLEN=10). Leave the second entry for the SALESDOCUMENT object (with QOBJPART=SAL_ERR) unchanged.
In transaction SMQR, check to see whether the queues have been registered or check transaction SMQS to see whether the destinations have been registered because otherwise, the queues are not processed automatically, and this can lead to queue overloads.
Check the queues regularly.
Composite SAP Note 504090 covers all notes that solve known problems in the transfer as of Support Package 06 (SP06).
Document cannot be maintained in online mode
If you cannot maintain a document, this can have various reasons. Basically, a sales document entered in CRM is locked until the R/3 System has confirmed the update of the order successfully.
If message CRM_ORDER019 "Document will be distributed - changes are not possible" occurs in CRM, check the queues (transaction SMQ1 and SMQ2). To analyze the data exchange from CRM to R/3, refer to note 431345.
If message CRM_ORDER013 "Transaction &1 is being processed by user &2" occurs in CRM or if message V1042 "Sales document &1 is currently being processed (by user &2)" occurs in R/3, the document is processed in the other system respectively. To avoid inconsistencies, a cross-system lock is set during the processing of a replicated transaction so that the document cannot be processed simultaneously in two systems.
Other notes
Only error-free sales documents are distributed to the R/3 System. If, in R/3, you change a sales document that was originally created in CRM, these changes are not transferred to CRM. That is, you should always make the changes in the original CRM document to ensure the consistency of the document data in both systems. Sales documents entered in the R/3 System are transferred to CRM, but they are locked for processing there. Changes to a document created in R/3 are also transferred to CRM.
In your settings for the data exchange, also make sure that the document number ranges correspond in both systems. For the successful sales document exchange between the systems, the transaction types and item categories have to be created in exactly the same way in both systems. If these objects do not exist in one system, you have to create them manually.
In transaction CRMM_BUPA_MAP, you can determine into which R/3 customer number the CRM business partner is converted and vice versa. If you do not receive a conversion for the specified business partner here, this indicates that a transfer problem has not occurred in the sales document but during the business partner download.
Header Data
Release Status: Released for Customer
Released on: 02.05.2006 15:04:13
Priority: Recommendations/additional info
Category: Consulting
Primary Component: CRM-BTX-BF-IF R/3 Interface for Business Transactions

CRM Table Names needed - For CRM Account, Contacts & Activity

Hi,
I liked to know "Table Names" for the following entities are stored in SAP CRM System
(a.) CRM Accounts
(b.) CRM Contacts
(c.) CRM Activity
Thanks,
Prembabu

Check the list of CRM Tables;
BUT000 : BP: General data - Contains Business Partner Number, Partner Category, Partner Type, First Name, Last Name etc.
BUT020 BP: Addresses
BUT050 BP relationships/role definitions: General data - Contains Relationship, Partner Number (PARTNER1), Relationship Category
BUT051 BP Relationship: Contact Person Relationship Similar to
BUT050 additionally contains Contact Person's Address data
BUT0BK Business Partner: Bank Data & Details BP Number, Bank Key, Bank Country Key, Bank Account Number
BNKA Bank Master Data
BUT100 BP: Roles
ADR2 Telephone Numbers (Business Address Services)
ADR6 SMTP Numbers (Business Address Services) - Contains Email Id of the BP.
ADRC Addresses (Business Address Services) - BP's Complete Address Details- City, Country, Post Code, District,
Street, Title No Etc
TSAD3T Table containing the Title text against a Title No.
COMM_PRODUCT Master Table for Product
CRMM_BUAG Master table for Business Agreement
CRMM_BUAG_H Header Data for Business Agreement such as Tax Category, Tax Characteristic, Form key, Business Agreement Class. Data in this table correspond to ISU
CRMD_OPPORT_H OPPORTUNITY HEADER DATA
CRMD_ORDERADM_H Contains the Header Information for a Business Transaction.
Note:
1. It doesn't store the Business Partner responsible for the transaction. To get the Partner No, link it with
CRM_ORDER_INDEX.
2. This table can be used for search based on the Object Id(Business Transaction No).
CRMD_OPPORT_H OPPORTUNITY HEADER DATA
CRMD_CUSTOMER_H Additional Site Details at the Header Level of a Business Transaction
CRMC_PROC_TYPE Master table Business Transaction Type
CRMC_PARTNER_FCT Definition of Partner Functions
SCPRIOT Priorities for Activities with priority text.
CRMC_PROC_TYPE_T Text for a transaction type
CRMC_ACT_OBJ_T Objective Number and Text for Activities
TJ30T All the status code and text
CRMC_PR_ASSIGN : Transaction Type and its Transaction Type Object.
IBIB : Installed Base/Ibase
IBIN : Installed Base Components
Activities:
CRMD_ACTIVITY_H Activity Header table
CRMD_ACTIVITY_I Activity Reporting: Activity Line Item Extension
CRMD_TM_ACTIVITY Activity reference
Lead:
CRMD_LEAD_H Lead Header table
Opportunity:
CRMD_OPPORT_H Opportunity Header table
Reward points if it helps.

Business Content for Bill Up transaction in CRM system

To all Experts,
I'm currently working on a project that requires Bill Up transactional data ( Source Table: CMSD_BU ) to flow from CRM to BW system. I'm looking for Business Content that can fulfill this requirement. However, till to date, I couldn't find any information of such Business Content. I'm not sure if such BC exist. Can anyone help if you have experience implement this data flow?
When searching for the DataSource / Extractor, I found BW Extract Structure CMST_BU_BW and CMST_BU_BW_C in the CRM system. But couldn't find any DataSource for both extract structure. Not sure if we need to install any support pack in order make the BC available in the system. Please help if you have any idea.
Thanks in advance.
Regards,
Hui Pin

Hi Shalini,
The document is replicated from ECC to CRM without any errors.
For this document I just want to create follow up transaction in CRM.(I dont want to change the document in CRM)
The follow up transaction is in display mode. this is my problem.
Hi Rekha:
I have done following setting in CRM to create follow up transaction in CRM for the document which is replicated from ECC to CRM.
1)     Defined the Copying Control for Transaction type
2)     Defined Copying Control for Item categories
3)     Defined Item category determination when copying
Thanks in advance,
Regards,
-Rahul.

Table view in EHP1 CRM 7.0

How to create a table view in ehp1 CRM.
Is it the same way by creating a view and adding value node /model node then selecting view as table view with congigurable mode?

Hi Anita,
As per your requirement, AET table enhancement will be best suited to it.
Use the help.sap.com link i gave in earlier reply to know more about AET table enhancements.
Now to get on to this task ,
1) Use transaction AXTSYS and create an entry for Z component, give a name say ZAET_TBLEXT.
and Save. The AET Table extension, then will use this component by default( if you select the radio button there) to create the views. Remember, just give any name you desire for the component. You dont need to create this componenet. AET extension wizard will create the component automatically.
2) Open the overview page on which you would like to have the tableview as an assignment block. Since its a compititor info, i assume you want to place it on a BP/Account/Prospect. Competitor Overview Page or Opportunity Overview Page. Now chose the config button and once the Assignment blocks are highlighted, select the Header View( Compititor header or Opportunity header view depending on the overview page you are in) and config tool will open. Use the Display Enhancement button or create enhancement button and another popup will open which display the enhancements if any,
3) On this Pop up you will see the AET table extensions assignment block. Use the Add table button. Follow the wizard and create the table, mention fields, translations etc. Also mention it as 1:n relation and so the table view. Chose the Standard buttons so you get all action buttons as well as inser, editlist, delete buttons etc.
Once done, save and generate. This creates the view and also adds the component usage on overviewpage.
Now all you need to do is just configure the overviewpag to pull the new tableview assignment block from Available to Displayed blocks.
Note :
1) this creates a Ztable , name same as mentioned/defaulted while AET table enahncement
2) this create Z BOL entity with 1:n relation with Access Entity of OverviewPage , for example, BuilHeader if account overview page or BTAdminH if Opportunity overview page.
3) creates BOL strucutre, handler class etc on its own.
4) You do not need to do any coding,
Thus in half an hour, you are done with Table view enhancement with Z table based entities.
Before EhP1, we had to extend the BT/BP model with ZBOL and had to do a lot of thigs on our own. Almost 2 days job for an advance developer which is reduced to 15-20 minutes with zero coding required.
If you have a sandbox or IDES system, i would recommand you to try it there frst, get confident and then do development on your development system.
Remember ->
1) AET Enhancement tool has to be started from WEB UI - which is generally runs on Customizing client, but creating AET table and enhancements is Workbench task. So if your customizing client is locked for workbench developments, then You must run the WEBUI on your workbench client ( use transaction wui ). It does not make any difference as far as development is concerned because your development its pure Workbench activity. later, you configure the Overview Page to pull the AET table view on your customizing client.
2) Be confident and have well determined about the table design & about your table view design like the fields you need etc. because once you add the fields and mention the field type like Numeric, indicator,text etc, you can not change it later once the Tableview is generated. You can add more fields later and you can delete fields too but you can not change their type later.
All the best.
Thanks & Regards
Suchiita
Edited by: Suchita Phulkar on Jul 30, 2011 12:16 AM

List of Tables used in IS Retail

Hi ,
I am currently desingning an adapter to integrate IS Retail and non SAP BI Solution. I need your help on the complete list of tables used in IS-Retails. It would be great if you could provide me the tcodes as well.
Expecting a prompt reply from experts.
Regards,
Raghu.
SAP Adapter Specialist.

Dear Raghavendra,
There are lot of SAP tables in IS Retail.
You can search all tables using transaction code SE16 or SE16N
For which transaction, you need SAP Table details?
Bye,
Muralidhara

How to get the material list displayed in CU50 transaction into ABAP report

How to get the 'KMAT" type material list displayed in CU50 transaction into ABAP report?
I am getting the entire BOM when i am using the FM CS_BOM_EXPL_MAT_V2 in to the table in the report.
But I want only the material list displayed in CU50.

Hi,
Could you please tell us how you found a solution to your problem?
Thanks & regards
Hassan

List of tables in SRM

Hi all,
can anyone send me the list of tables in SRM.also
some useful docs for SRM ABAP development(info on BADI etc).Will reward points..
mail me at [email protected]

Hi,
Please look at following threads:
Re: List of CRM tables
TABLES
Regards,
Marcin

What is Business Transaction in CRM

Hi,
What is Business Transaction in CRM? What is deifference between partner and partner_guid? What is significance? and also product, prodcut_guid?
Thanks,
Shashikanth

Hi Shashikanth,
Most of the transaction that you carry out in CRM are Business Transaction. E.G. Service Contract, Activities, Lead, Task etc.
Business Transactions are further divided into Subobject Category, these Subobject Categories are again subdivided into Transaction Type.
Categorization of CRM Business Transaction based on Subobject Category
Business Transaction Name SUBOBJECT CATEGORY
Activity BUS2000126
Service Contract BUS2000112
Lead BUS2000108
Opportunity BUS2000111
Task BUS2000125
Utility contract item BUS2000147
Note:
1. For Example if you want to retrieve all the activities in CRM, pass the OBJECT_TYPE as BUS2000126 in CRMD_ORDER_INDEX table.
2. The Subobject Category can be customized for a business transaction from the transaction SPRO.
Partner : Partner is a 10 char number used to identify Business Partner in the system.
PArtner GUID : It is global unique identifier to identify the partner globally.
As such there is no difference in partner and partner guid, both refer to the same entity in CRM and are unique across the system. Refer the table BUT000.
Same applies to product and product guid. Refer the table CRMM_PRODUCT.
Reward points if it helps and close the thread.

Please provide a program or fm to find a table in transaction

Please provide a program or fm to find a table in transaction
tell me some methods

"1st
This is the Table name : D010TAB
Execute the table in se16 , give your Program name it will list all Tables used in this Program .
or else
"2nd
Function Module : GET_TABLES .
Execute this FM in SE37 , give your Program name it will list all Tables used in this Program .
"3rd
This is the Program which will give you the List of tables used in your Program .
REPORT ztesttables.
DATA line(100) TYPE c .
DATA:itab TYPE TABLE OF line,
wa_tab LIKE LINE OF itab.
PARAMETER program TYPE sy-repid.
CALL FUNCTION 'GET_TABLES'
EXPORTING
progname = program
TABLES
tables_tab = itab.
SORT itab BY line.
DELETE ADJACENT DUPLICATES FROM itab COMPARING line.
LOOP AT itab INTO wa_tab.
WRITE wa_tab-line.
ENDLOOP.
Reward points if it is usefull ...
Girish

PM Tables and Transaction

HI...
Plz provide the Plant maintenance(PM) Tables and Transaction.
And detais about PMIS?? Use of it??
thanks..

Hi,
PM T codes and PM Tables
Equipement-- Maintable-EQUI
Functiuonal location-     IFLOT
Serial number             -SERI
Material master         MATNR
IE01                 Create Equipment
IL01                 Create Functional Location
IB01                 Create Equipment BOM
IQ01                 Create Material Serial Number
MM01               Material Master
IB 01, IB11       Bills of materials
IW21 - Notification creation
IW31- PM order IA07 Display General Task List IA03 Display Equipment Task List IA13 Display Functional Location Task List IR03 Display Work Centre KO88 Settle Order (Single) IW32 Change Work Order IW31 Create Work Order IW33 Display Work Order IW38 Work Order List Editing - Change IW39 Work Order List Editing - Display IW40 Work Order List Editing - Display Multi Level ME21 Create Purchase Order (pre R4.6) ME21N Create Purchase Order (R4.6 onwards) IP41 Create Single Cycle Plan (R4 onwards) IE02 Change Equipment IE01 Create Equipment IE03 Display Equipment IE05 Equipment List Editing - Change IE08 Equipment List Editing - Display IW42 Overall Completion Confirmation IW26 Create Notification QS42 Display Catalog ML81 Create Service Entry Sheet MM03 Display Material CS03 Display Material BOM IW13 Material Where Used List IW66 Change Notification List of Tasks IW67 Display Notification List of Tasks IW22 Change Notification IW23 Display Notification IH01 Display Functional Location Structure MB11 Goods Movement MB31 Goods Receipt IW8W Goods Receipt for Refurbishment (R4 onwards) IP02 Change Maintenance Plan IP03 Display Maintenance Plan IP10 Schedule Maintenance Plan IP30 Deadline Monitoring IP11 Change Maintenance Strategy IP12 Display Maintenance Strategy IP19 Maintenance Scheduling Overview Graphic IP24 Maintenance Scheduling Overview List IW28 Notification List Editing - Change IW29 Notification List Editing - Display IW30 Notification List Editing - Display Multi Level IW64 Change Notification List of Activities IW65 Display Notification List of Activities IW68 Change Notification List of Items IW69 Display Notification List of Items IQ03 Display Serial Numbers IW24 Create Notification IP42 Create Strategy Maintenance Plan (from R4 onwards) IW25 Create Notification IL02 Change Functional Location IL01 Create Functional Location IL03 Display Functional Location IL05 Functional Location List Editing - Change IL06 Functional Location List Editing - Display IW41 Time Confirmation - Indvidual Entry IW48 Time Confirmation - Collective Entry with Selection IW44 Time Confirmation - Collective Entry no Selection IA11 Create Functional LocationTask Lists IA12 Change Functional Location Task List IL02 Change Functional Location IA05 Create General Task List IA06 Change General Task List IA01 Create Equpment Task List IA02 Change Equipment Task List IE03 Display Equipment IR01 Create Work Centre IR02 Change Work Centre CA85 Replace Work Centre IP13 Strategy Package Sequence IP14 Strategy Package Sequence IP04 Create Maintenance Item IP05 Change Maintenance Item IP06 Display Maintenance Item IP17 Maintenance Item List Editing - Change IP18 Maintenance Item List Editing - Display IP02 Change Maintenance Plan IP03 Display Maintenance Plan IP15 Maintenance Plan List Editing - Change IP16 Maintenance Plan List Editing - Display IK11 Create Measurement Documents IK12 Change Measurement Documents IK13 Display Measurement Documents IK22 Measurement Documents List Editing - Create IK21 Measurement Documents List Editing - Create IK22 Measurement Documents List Editing - Create IK18 Measurement Documents List Editing - Change IK17 Measurement Documents List Editing - Display IK41 Measurement Documents List Editing - Display Archive IQ01 Create Serial Numbers IQ02 Change Serial numbers IQ04 Serial Numbers List Editing - Create IQ08 Serial Numbers List Editing - Change IQ09 Serial Numbers List Editing - Display IK01 Create Measurment Point IK02 Change Measurement Point Ik03 Display Measurement Point IK08 Measurement Point List Editing - Change Ik07 Measurement Point List Editing u2013 Display and a few PM related tables: TPST -- Functional Location - BOM Link STAS -- BOMs - Item Selection STKO -- BOM Header STPO -- BOM item STPU -- BOM Subitem STZU -- Permanent BOM data RESB - Reservation, Material number, Requirement date, Required Quantity, Quantity withdrawn, Work order number RSADD - Date created, User ID of person who created the reservation MAKT - Material Description AUFK - Work Order description AFIH - Revision (as a selection field) MBEW - Total valuated stock (SOH) USER_ADDR - The User ID first name & second name RKPF - Reservation Header information if required.
IP01 - maintenance plan
Plant maintenance (PM) IHPA Plant Maintenance: Partners OBJK Plant Maintenance Object List ILOA PM Object Location and Account Assignment AFIH Maintenance order header AFIH Maintenance Order Header AFKO Order header data PP orders AFPO Order item (not used much) AFRU Order completion confirmations AFVC Operation within an order AFVV Order position data CRCO Assignment of work center to cost center OBJK Plant Maintenance Object List CRHD Work Center Header PLAF Planned order HIKO Order master data history HIVG PM order history: operations Logical databases: CNJ AUFK Order master data AFKO Order header data PP orders AFPO Order item JSTO Status object information JEST Object status Logical databases: ODK 12.1 Routings/operations MAPL - Allocation of task lists to materials PLAS - Task list - selection of operations/activities PLFH - Task list - production resources/tools PLFL - Task list - sequences PLKO - Task list - header PLKZ - Task list: main header PLPH - Phases / suboperations PLPO - Task list operation / activity PLPR - Log collector for tasklists PLMZ - Allocation of BOM - items to operations 12.2 Bill of material STKO - BOM - header STPO - BOM - item STAS - BOMs - Item Selection STPN - BOMs - follow-up control STPU - BOM - sub-item STZU - Permanent BOM data PLMZ - Allocation of BOM - items to operations MAST - Material to BOM link KDST - Sales order to BOM link 12.3 PRTu2019s production orders AFFH - PRT assignment data for the work order CRVD_A - Link of PRT to Document DRAW - Document Info Record TDWA - Document Types TDWD - Data Carrier/Network Nodes TDWE - Data Carrier Type 12.4 Work center CRHH - Work center hierarchy CRHS - Hierarchy structure CRHD - Work center header CRTX - Text for the Work Center or Production Resource/Tool CRCO - Assignment of Work Center to Cost Center KAKO - Capacity Header Segment CRCA - Work Center Capacity Allocation TC24 - Person responsible for the work center 12.5 Classification CABS Result of the Statistical Analysis of Table AUSP CUFM Customizing: Class/Config: Screendesigner Form TCME Validity for Global Characteristics KLAH Class Header Data KLAT Classes: long texts KSML Characteristics of a Class AUSP Characteristic values SWOR Classification System: Catchwords KSSK Allocation Table: Object to Class TCLG Class groups TCLO Key Fields of Objects TCLS Classes: Organizational areas TCLST Classes: Org. Areas (Texts) TCLU Class Status COCC PP-PI attributes for characteristics COFV Process management - process instr. charact. in ctrl. recipe COME Process management - message characteristics CORE Process mgmt.- display characteristics of the eval. version PLFV PI Characteristics/Sub-Operation Parameter Values TCLA Class Types TCLAT Class Type Texts TCLT Classifiable Objects LTCLTT Classifiable Objects: Texts CABN Characteristic CAWN Characteristic values Logical databases: - Matchcodes: CLAS, MERK en KLSW 12.6 Equipment EQUI Equipment master data EQKT Equipment short texts EQUZ Equipment time segment EAPL Allocation of Task Lists to Pieces of Equipment EQUI Equipment master data JSTO Status object information JEST Object status TJ30 User status TJ30T Texts for user status TJ02 System status TJ02T Texts for system status 12.7 Functional Location IFLOT Functional Location (Table) IFLOTX Functional location: short texts IRLOTX Reference functional location: short texts TAPL Allocation of task lists to functional
Edited by: Sreenivasu on May 18, 2009 12:43 PM
Edited by: Sreenivasu on May 18, 2009 12:48 PM
Edited by: Sreenivasu on May 18, 2009 12:50 PM
Edited by: Sreenivasu on May 18, 2009 2:06 PM
Edited by: Sreenivasu on May 18, 2009 2:07 PM
Edited by: Sreenivasu on May 18, 2009 2:14 PM
Edited by: Sreenivasu on May 18, 2009 2:15 PM

Let me know what is new table and transaction code in ECC6?

Hi
As the above title, I want to know what is new table and transaction code, through from R/3 4.6c to ECC6.
Regards
Sang lim.

Hi Sang lim,
Apart from the tocdes listed above,
Transactions that changed from Release 4.6 C
Rel. Old TCode New TCode
46C ME51 ME51N
46C ME52 ME52N
46C ME53 ME53N
470 FNBD FNBT
470 ME54 ME54N
470 ME59 ME59N
46A MR01 MIRO
46A MR02 MRBR
46A MR08 MR8M
46A MR1G MIRO
46A MRHG MIRO
46A MRHR MIRO
46A MRRS MRRL
46B S_P99_41000327 S_ALR_87100205
46C MR03 MIR4
46C MR1B MIR6
46C MR2M MIR4
46C MR3M MIR4
46C MR41 MIR7
46C MR42 MIR4
46C MR43 MIR4
46C MR44 MIR4
46C MR5M MIR4
46C OAA2 AUFW
620 AFAB AFABN
620 AL01 RZ20
620 AL02 RZ20
620 AL03 RZ20
620 AR11 AR11N
620 AR29 AR29N
620 ASKB ASKBN
620 CA97 CA97N
620 DB02 DB02N
620 FM3S FMCIA
620 FM3U FMCIA
620 FMN3 FMN3N
620 FMN4 FMN4N
620 FMN5 FMN5N
620 O02E BMBC
620 OACR OAC0
620 RZ23 RZ23N
620 SCOM SCOT
620 SM22 SM21
620 SWID SWI2_DIAG
620 S_P9C_18000190 S_PL0_09000447
620 S_P9C_18000247 S_P6B_12000136
620 VOPA VOPAN
620 VOTX VOTXN
620 WE49 WE42
620 WE52 WE41
620 WE53 WE41
640 ABAW ABAWN
640 AL04 RZ20
640 AL19 OS07
640 COHVOMAVAILCHECK COMAC
640 COHVOMPI COHVPI
640 COHVOMPP COHV
640 KE1F KE1FN
640 KE29 KE29N
640 MKH1 MKH1N
640 MKH2 MKH2N
640 RZ02 RZ20
640 RZ06 RZ20
640 RZ08 RZ20
640 STAT STAD
640 STMP SLPP
640 VL22 VL22N
700 AL05 RZ20
700 AL16 RZ20
700 AL17 OS07
700 OVXA OVXAN
700 OVXG OVXGN
700 OVXJ OVXJN
700 OVXK OVXKN
700 OVXM OVXMN
700 OVX3 OVX3N
700 OVX6 OVX6N
700 OVX8 OVX8N
700 WLAM WLAMN
700 WLMM WLMMN
700 WLMV WLMVN
700 WLWB WLWBN
700 WPLG WPLGN
Regards,
Kiran

How to know the List of Tables that are updated through a ABAP Program

Hi,
Is there a program or something that will help me to identify the List of Tables that are used in a ABAP program(ABAP Report, Transaction .... program) without debugging it or looking at the dictionary structure.
I really need this urgently. Try to give me many methods as possible.
Thkx
Kishan

Hi,
I created a Z-transaction for my SE49 and debugged a little bit - it's not so fantastic any longer - just like the proposal of SE80 - DDIC list.
SE49 (and I guess similiar functions, too) just scan the source code for a list of key words: tables, select, update, insert, modify, export, import.
But very (very!) often updates are encapsulated into function modules - and here this technical cross reference (just like SE80 DDIC list) is of no help.
So a SQL trace (or runtime analysis) is still the best option to get a complete list. Still these tools just analysis one process - if in other circumstances more tables are involved, can't be judged.
E.g.:
- creating one new entry: 1 table
- changing existing entry: 2 accesses to 1 table + log table
Regards,
Christian

List of tables n transaction in CRM

Similar Messages

Maybe you are looking for