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.

Similar Messages

Transaction type of sales order under Account overview doesnt appear

Hi Experts,
Need help, We are implementing the replciation of sales order from CRM 7 to ECC. Now i already manage to maintain the transaction types and created a link in navigation tool bar.
Now the problem is the assignment block of sales order and quotation under account information create new button doesnt appear the transaction types i maintained under CRM->transactions->settings for sales transactions->define profiles for ERP transactions. and the sales order created doesnt appear on that assignment block as well..
Any suggestion or ideas is welcome.. thanks in advance
best regards,
etrafanob

Hi Etrafanob,
New button on sales order assignement block in account overview page shows the list of transaction types which are maintained via below customizing.
Spro->Customer Relationship Management->Define Transaction Types..
All the transaction types which are active and defined in leading transaction category "BUS2000115 Sales" for the same Channel will be displayed.
Not sure if defining those transaction types under erp sales order will help in this scenario..
Hope this helps..
Cheers,
Sumit Mittal

Account Overview Screen with no sales, service order & Transaction history

Hi All,
I have come across an issue with Account Overview link in IC webclient CRM 5.0.
One Z Webclient profile is created (ZSERVICE) which is assigned to few users. When user with this profile logs in and confirms any acc. ID on Identify Account screen, if he goes to Acc. Overview screen the viewareas for Sale Order History, Service Order History and Transaction History shows zero entries even if there are entries for given Acc. ID.
Identify Acc. is using Z BSP Z_SV_IC but acc. overview is using the std. BSP crm_ic_ovw.
Is this a problem with IC webclient configuration in SPRO or a problem at BSP level. please Help.
Regards,
Sameer

Hi John,
Thanks for the reply.
My problem is not with Interaction history screen but with account overview screen. On interaction history screen I can find the interactions for given Acc.ID. But after I confirm the account on identify account screen when I click on account overview screen I can see few details of that account on acc. overview screen but the other details are blank. And ofcourse I cant directly go to acc. overview screen without confirming the acc. ID as the account details on this screen are readonly.
Also you said 'Maybe a problem with your custom controller?' .. can you throw some more light on this.
Regards,
Sameer

Financial accounting comparative analysis Transaction F.03 "inconsistence"

Dear all, we just checked out over transaction F.03 that we have inconsistencies
between accounts receivables on the basis of customer line item (transaction FBL5N),
G/L account line item (transaction FBL3N) and report S_ALR_87012284 which shows the balances of the period on the sales account and on the accounts receivables.
Background for this "inconsistence" was a "retrobilling"-transaction (VFRB) which
caused an error in SM13 (but no ABAP-Dump or similar....).
1) For some document numbers SAP was able to create document numbers and entries in BKPF und BSEG
2) Unfortunately BSID und BSIS were not created ==> means that we did not get a proper view in FBL5N for the accounts receivable-entry and we did not get a proper view in FBL3N for the G/L sales-account.
3) one FI-consultant went then in the system and changed the documents with transaction FB02 - he just added a dot in the field ZUONR
4) All lines arised then in FBL3N and FBL5N (I thought everything is fine now....)
5) No we checked with transaction F.03 that on the balance-side that the summary of the amount of this documents is too high on the balance of the sales account and on the G/L accounts-receivable-account is to high, the sub-ledger for the customer seems to be fine!
Could anybody give me a hint what to do?
Is there maybe a report which creates again the balances in the current period out from the item-lines?
Txs in advance whoever can help me!

Hallo Andreas, vielen Dank für Deinen Input
Zur Situation ist folgendes zu sagen:
Wie gesagt ist das ganze aus der VFRB (Nachverrechnung) entstanden, wobei
ich es nicht zusammengebracht habe, aus SM13 heraus nachzubuchen - es ist ein einziger Satz drinnen, wobei das System einen "Fehler beim Lesen von VBHDR" zurückgibt...
Wir konnten diese Sätze nicht nachbuchen ==> das Arge dabei war, dass Gutschriften erstellt wurden, die wurden in die BKPF und auch BSEG gebucht, allerdings nicht in die Sekundärindizes (BSIS, BSID).... - d.h. sowohl in der Darstellung von FBL5N (Debiorenposten) und FBL3N (am Erlöskonto) waren diese Belegnummern nicht dargestellt.
Habe im OSS gesucht und bin auf keinen grünen Zweig gekommen, da die Meldungen, die ich gefunden habe, sich zwar beispielsweise mit Inkonsistenzen zwischen BKPF und BSEG beschäftigt haben, aber habe nichts gefunden, was auf ein Nichtvorhandensein der BSIS und BSID hinweist.
Wie auch immer ==> unser FI-Consultant ist dann einfach in den Beleg mittels FB02 reingegangen, hat auf der ZUONR einen weiteren Punkt gesetzt und plötzlich waren die Sekundärindizes erstellt ==> so weit so gut.
Leider sind wir erst gestern über die F.03 draufgekommen, dass nun die Salden für das Erlöskonto als auch für das betroffene Forderungskonto genau um die Summe des Betrages dieser Belege zu hoch sind (ich nehme an, dass ein Programm oder Funktionsbaustein 2x die Salden hochgezogen hat - ist aber reine Vermutung...)
Ich muß gestehen, dass ich mich auf der Baustelle nur bedingt auskenne, die GLT0 habe ich gestern zum ersten Mal aufgerufen ==> ich nehme an, dass das die Saldotabelle ist ==> beim Forderungskonto konnte ich auch herausfinden, dass der S/H-Betrag dem Betrag gem. S_ALR_87012284 entspricht...
OSS-Call habe ich übrigens gestern nacht schon aufgegeben, hoffe, das SAP mich da unterstützen kann.
Vielen Dank für Deinen Input und lg

Posting keys for account determination for transaction do not exist

Dear SAP Gurus,
While release to accounting service sale billing bellow error occurs while i made all necessary changes in VKOA.
Posting keys for account determination for transaction do not exist
Please guide me to coorect this error.
With Regards
MK

Dear IMUKUL,
Please search the forum before posting.
Check the following thread and see whether it helps you.
CIN Error
Kindly make it a point to search forum before posting
Thanks & Regards,
Hegal K Charles

Posting keys for account determination for transaction EXC do not exist

hi
i am doing Sales order for 1 month,no error i have got
but now i am getting error
Posting keys for account determination for transaction EXD do not exist
HELP

There will not be any such postings called FI side / SD Side.
Positng always done in Financial perspective only into Certain G/L accounts depends on configuration we did.
As we know,
To post Invoice Conditions in G/L accounts , we configure Account Determination . These tables will be communicated through Account keys maintained in Pricing procedure & in Account determination tables.
To account the stock in Inventory, will configure the same in OBYC - FI/MM Account Determination.- this will be triggered through Movement type - Transaction key / General modifier / Valuation calss / Valution group code n other factors.
In your issue,
Which Postings you are referring to?
In SO creation, Controlling documents will be created ( Ref: COPA - Controlling & Profitablity Analysis Customization)
After PGI in Delivery: Inventory will accounted through OBYC settings
After releasing invoice to Accounting, G/L accounts posted through VKOA settings.
Hope ,now you provide exact information related to your query

Posting keys for account determination for transaction EXD do not exist

hi
i am doing Sales order for 1 month,no error i have got
but now i am getting error
Posting keys for account determination for transaction EXD do not exist
HELP

Hello,
I have following suggestion to overcome this issue.
1. In the t-code "FTXP", check for assignment of the G/L account for the posting key.
2. Check out the SAP Note:200348.
3. In t-code "OBCN",for the account key EXD, make sure that the value of posting indicator is 2.
4. In t-code OBYZ, for the tax calculation procedures, change the key to EXD. The account keys in tax pricing procedures and SD pricing procedures Should be same.
Regards,
Sarthak

Posting keys for account determination for transaction ERS do not exist

Dear All,
When I try to create an accounting document for a billing document, the below error happened:
Posting keys for account determination for transaction ERS do not exist.
Could any one of you meet the issue before and give me some advice? Thanks a lot.
Ray

Dear,
In your pricing procedure check whether any sales deductions / discounts condition type is maintained and against that maintain ERS account key.
and Go to VKOA and maintain gl account against your Kofi and KOFK for account key ERS.
try and let us know
regards,
SUdhir

Process types and Sales Transactions not Sync with SM2.5

Hi Experts,
1) We have custom process types for leads, opt and quotations etc.. but the TYPES option is not activated or greyed out when creating any sales transactions from app SM 2.5.
Please help on this.
2) With our accounts as a relationships, leads and opportunity are syncing well but not quotations and activities. Is there any settings for that which needs to be activated.
Thanks for your help.
Thanks
VS

Check out these instructions: http://support.apple.com/kb/ts5223

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

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.

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?

Error in VF02 (Posting keys for account determination for transaction JTS)

Hi,
I have created new account key JTS and also assigned G/L account in VKOA, But at the time of releasing the billing document to accounting, I am getting the below error;
Posting keys for account determination for transaction JTS do not exist
Message no. F5598

Hi Amanulla,
once we create the Account key in revenue determination we have to assign that account key to respective procedure and condition types.
check that.
please award points.
ravikanth

IC Account Overview - Sales Transactions & Quote Transaction BP_BPBT

Similar Messages

Maybe you are looking for