Default sales Transaction in Ic Webclient 2007

Hi,
When we create a new Sales order in IC Webclient, I assume the default Transaction type is TSA (telesales). How can I change it to TA (Standard order). I was looking at business transaction profile, but where should I assign this in a Business role in CRM 2007?
Thanks

Hi Praveen,
If you've made the proper settings for TA in the Business Transaction Profile, then you assign this Business Transaction Profile to the Business Role, also in customizing:
In IMG go to Define Business Role>Choose Required Business Role and highlight>double click Assign Function Profiles folder on left side>find or add entry for IC_BT>click value help and find Business Transaction profile you created/modified.
Does this answer your question, hopefully?
Take care,
Kim
Edited by: Kimberly Davis on Jun 25, 2008 1:21 PM

Similar Messages

Searching for products via Product Hierarchy ID in CRM Webclient 2007

Hello,
When creating a sales order in CRM Webclient 2007 I would like to be able to search for products by using the Product Hierarchy ID. When clicking the search help for product in the order entry screen in the webclient UI, I get a pop-up with the available search criteria. I select Product Hierarchy ID and click on Input Help. A new pop-up is displayed with the three Hierarchy ID:s:
R3MATCLASS Material Group
R3PRODSTYP Product Subtype
R3PRODHIER Product Hierarchy
I select R3PRODHIER. When hitting the search button, I get all materials which have Hierarchy ID R3PRODHIER assigned as a product category in the material master data. I can however not search for materials which belong to a certain hierarchy node in the product hierarchy.
In transaction VA01 in ECC it is possible to drill down through the three levels of the product hierarchy to find the desired material. Is the same type of searching possible in CRM?
Any help much appreciated.
Kind regards,
Johan Wigert

Hi Johan
I want to know if finally you have found the way to deal this problem.
Thank you very much,
Yannuchi

Set default transaction in Ic webclient

Hi All,
I am working in IC WEBCLIENT. When I am launching the transaction crm_ic and going to interaction history in navigation bar and in show field I am choosing Business Activity I am getting the mails and while choosing that mail I am getting Complaint as the default transaction. I want to get Business activity as the default transaction but it is showing Complaint 0. Can I get Business activity there and how?
Thanx
Chinmaya

Hi,
You need to do configuration for Business Transaction profile with the path mentioned by Glenn. In the first screen under the column "Trans.Type" you have to use your activity transaction (e.g 0010 is used in default Business Transaction profile). With this change you will be able to create Activity transaction as default transaction. Please remember to assign your Business Transaction Profile to your IC WebClient profile. Alternatively, make the above change in the Business Transaction Profile that you are using.
Secondly, you may have Sales or Service transaction to be created as Dependent transactions based on your requirements. This can be done in the sub-category by selecting your Business Transaction Profile and double clicking "Dependent Business Transactions".
Please go through the following to give you detailed conceptual understanding on this.
http://help.sap.com/saphelp_crm50/helpdata/en/e5/e9bc787a4711d68790005004f2f41f/frameset.htm
Regards,
Deepak

In Transaction code va41 how to set default sales contract start date

Hi ,
In Transaction code " VA41 " how to set default sales contract start date and end date.
Can any one tell me the correct user exit for the same.
Thanks
Basu

hi,
u have to use user exits or badis.
use sutable exits mentioned below.
SDTRM001 Reschedule schedule lines without a new ATP check
SDVFX006 User exit: Tax line (transfer to accounting)
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
Edited by: katigiri linganna on Apr 28, 2009 12:19 PM

Follow-up transactions in IC Webclient

We have a requirement to create follow-up transactions for sales document types (ex. standard order from an inquiry or quotation) in IC Webclient.
We looked at the IC Webclient and found that there is a possibility to create follow-up transactions only from the interaction record.
The copy controls are done and we can create follow-up transactions in SAP GUI.
Does anyone know how to create a follow-up transactions for any sales transaction type and how to provide such a facility in IC Webclient?
thanks a lot.
Sam

We have the scenario where we make follow-up transactions in the IC Webclient from a standard order to a return order for example. This is no standard functionality in the IC webclient and has been custom programmed by ECENTA a german SAP partner. It uses the standard copy control. The main issue was to get the document flow correct.
Regards,
Jacco

Customer pricing procedure in Sales transactions

Hello Experts,
In our CRM 2007 we have already customized the pricing procedure of the sales transactions for each sales area / document pricing procedure / customer pricing procedure. But creating sales transactions, our business needs system to take in consideration the customer pricing procedure of the partner in role Ship to party instead of the partner in role Sold to party. Could anybody help telling how to set it?
Many thanks in advance!

well... maybe my question is not clear... the thing is that as a sample, we have a:
1.Sales area = O 50000XXX
2.Sales document type with Pr. Procedure = A
3.SoldTo with Cust Pr. Procedure = 1
4.ShipTo with Cust Pr. Procedure = 2
When we create a sales document, system determines the Pr. Proc. of the doc as it was customized in view CRMV_PRCPROC_DET:
Sales area + Pr. Procedure of the sales doc type + Cust Pr. Procedure = Pr. Procedure of the sales doc
In our customizing we would like to have 2 rows (following the example)
O 50000XXX + A + 1 = ZPROC1
O 50000XXX + A + 2 = ZPROC2
We would need that system checks whether there is any Cust Pr Procedure in the master data of the ShipTo partner.
- If yes, the Pr. Procedure of the sales doc = ZPROC2
- If not, the Pr. Procedure of the sales doc = ZPROC1
but I have not managed to find where to adjust it (nor custom nor BADI). is there any idea or comment?

IC Account Overview - Sales Transactions & Quote Transaction BP_BPBT

CRM 7.0
I activated the Account Overview screen in the IC and realized only the oldest 100 sales transactions and quotes are showing in BP_BPBT SALESOORDERSOV & SALESQUOTATIONSOV. For me these are documents from years 2005 - 2007, nothing recent. Is there a way to change this to the 100 most recent transactions?
As a workaround I found >>>
IMG entry > CRM > Master Data > Business Partner > Specify Display Options for Business Transactions
allows entries for Role / Area / Time Frame,
Is there another spot to configure time Frame? the entries I listed below but I would like a entry of current year and previous year.
I'm using Y A This Year in the interim.
D 0     Today
D+-1     Yesterday
D+1     Tomorrow
M A     This month
M+-1     Last month
M+1     Next month
W*2     <- 14 days ->
W+-1     Last week
W+0     This week
W+1     Next week
Y A     This year
Y+-1     Last year
Y+1     Next year

Hopeful someone can provide some insight, I'm going to ask my developers to look at these badi's
Note 1131623 - BAdI for selection of business transactions at Accounts
Note 1478075 - BAdI for selection of business transactions at Accounts
1478075 has this comment but I see no place in this IMG entry in 7.0 to adjust the number of items >>>>>>>
SAP already provides a customizing at IMG for restricting the number of items which are retrieved and displayed in the assignment blocks:
Customer Relationship Management > Master Data > Business Partner > Specify Display Options for Business Transactions.

Default Sales Order type settings

Where do I set the default Sales Order type for transaction VA01. trying to avoid employees choosing the wrong order type.
Thank you.

You can setup user parameter for parameter AAT
Use transaction SU3 for every user
Goto tab Parameters
Add a line
Parameter_ID: AAT
Parameter value: Your order type
Save user profile
Please note that this solution will not prevent user to change the value of field order type during VA01. However he will always get this as default value. You should do this for every user you need to have default value.
Best regards
Aris

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

Inter company sales transaction

Hi Experts,
I have completed doing intercompany sales transaction....besides there are few question croping up which I wud like to post here...
1)How inter company billing doc type IV is able to determine ordering company as a payer at the time when I tried to create IV document(intercompany billing doc)..?
2)How sales area is determined?....bcoz am creating IV with reference to del doc which has end customers sale area...but I can see ordering company's sale area in IV doc...how it is?
3)might be this question sud hav taken the priority first but still...how billing type IV is determined automatically after creting F2 doc?.......
Thanks in advance

Hi
3)might be this question sud hav taken the priority first but still...how billing type
IV is determined automatically after creting F2 doc?.......
In the configuration of sales doc type in VOV8 in the billing tab we maintain intercompany billing type as IV
Config is maintained here
In Inter company sales transaction in the end customers sales order we change the delivering plant which belongs to different company code
Customer ABCD orders sales org 1000 belonging to company code 1000
But plant 2000 belonging to company code 2000 delivers the material
So in the sales order of 1000 sales org when the delivering plant is falling as 2000 system senses it is Inter company sales and proposes billing type accordingly
1)How inter company billing doc type IV is able to determine ordering company as a
payer at the time when I tried to create IV document(intercompany billing doc)..?
Billing type IV is used per default for the internal invoice. This is proposed
based on the document type of the order.
In principle, the payer of the internal invoice corresponds to the ordering
company code, which appears like a customer to the supplying company
code.
For this reason, you create a customer master record in the supplying
company code. You enter the relevant data for billing in this customer
master record. Finally, you assign the related customer number of the
sales organization of the ordering company code in Customizing (field
Customer IV).
The company code in the internal invoice results from the company code
affiliation of the supplying plant. It thus corresponds to the supplying
company code.
In Customizing, you assign the sales area necessary to create the internal
invoice to the supplying plant
I am not able to get clearly your qn 2. exactly your query
Try to read GLYNN C WILLIAMS materials in Inter company sales transaction
That is very clear
Regards
Raja
Note For 1 of your thread which was closed today i asked you how did you fix the issue
Pls reply to that There is so much to learn from your reply

Payment Terms in Sales Transaction...!

Hello,
I am basically an SD consultant. I am not familiar with CRM much.
I have an issue with the Payment Terms in a Sales transaction. It shows different Payment Terms at header and different at item. There is nothing in a Docuemnt's change log. May be user has changed the Peyment Terms is changed while creating Sales Transaction, but the user says he/she had not done so.
This caused a mismatch of Payment Terms at header and item level in R/3 Sales Order and so in Final R/3 Invoice.
What can be the issue..?
As in R/3 the Payment Terms is retrived from the customer master, in CRM also it should be the same as I believe. But I first would like to check the Customer Master (Business Partner) in CRM in Transaction BP. But within Transaction BP where to check the Payment Terms? The Sales Area Data button is there but not active.
Thanks in advance.
Best Regards,
HP

Hi Hardik,
To check the business partner payment temrs, you much change the 'role' of that business partner to, for example, 'sold-to-party' or 'payer'. Then the sales area button will became available so you can check the sales area dependent information, like payment terms.
Can you check?
Kind regards,
Garcia

Error message while creating Sales transaction

Hi Gurus
While creating a sales transaction in Mobile Sales I am getting the following error message.
No Valid sales channel exists for this business partner enters a sales channel in the business partner sales area data.
I have checked in table SMO_KNVV, there is an entry for this business partner. What can be the possible reason? Please help.
Regards
Javed

Hi Javed,
Your logged employee should also have some sales area assigned to him/her.
This can be done by assigning you employee to sales position under sales area in CRM Org Management (PPOMA_CRM).
Once this is done and org. data is replicated to Mobile. you can very much create the transactions without error.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

How to restrict a Sales Transaction being created Straight up

Gurus,
We have a business requirement where a perticular Order type (Sales Transaction) can only be created as a follow on Order.
But the problem is, when i configure the Sales Transaction type, it is also appearing in the standard Transaction type list.
I have configured this Order type in the follow on Transaction configuration, but i cannot remove/hide this transaction type from standard transaction type list.
Pls advise.

Gurus,
I would really appriciate some help here.
Thanks in Advance.

Creating action in CRM sales transaction to trigger RFC in R/3?

Hello gurus
We wish to replicate our contracts from CRM to R/3 but since SAP is not supporting it, I heard that one option that we have is to enable actions in our CRM sales transactions, which when executed will trigger an RFC call to R/3 system and then create same transactioon there as well...
Could anyone please shed some light as to how this can be done?
Please advise.
Regards
Jai

Hello,
I should prefer using the ORDER_SAVE Badi, using a queued RFC to create the dat in the R/3 system.
Regards,
Fred

Importing Sales Transactions into Oracle Financials

I have a customer who is planning to use Oracle Financials as their finance solution, but we need to auto-feed the sale transactions from the sales system. These transactions corresponds (loosely speaking) to sales (or purchase) orders and delivery order. We have the ability to reformat the data (if necessary) to any format or through most interfaces (ODBC, XML, etc).
I just do not know enough about Oracle Financial to determine the appropriate format and connectivity.
I read on the Oracle Financial product page that it is possible to integrate that solution with third party solution - but there is hardly any other information available. So,
1. Has anyone done similar integration before ?
2. If so, can you kindly offer some advice - where (or whom) should I go next for more information ?
Thanks and best regards
Lai Hock

Hello:
Project's activity management gateway (AMG) is the means to
import transactions into projects. This includes creating
tasks, budgets etc. For importing/recording commitments there
is a table that needs to be created and a view that needs to be
modified to show external commitments within projects (I believe
the view is named something like
PA_External_system_commitments_view)
Robert

Default sales Transaction in Ic Webclient 2007

Similar Messages

Maybe you are looking for