In Sales Transaction 'crmd_order' Implementation of Opportunity BAdI

Hello All,
I'm facing a problem in Sales Transaction 'crmd_order' . I'm displaying an opportunity . In this opprotunity page, Start Date is displayed in 'Details' tab.
I want to display this start date in a field of 'Milestone' tab.
This is Standard SAP Program. So. i think Opportunity BAdI 'CRM_OPPORT_H_BADI' we can use .
Can anybody give me some suggestion or example to solve this problem?
thanks in advance
Madhusudan

Hello Shalini,
till now my problem was not solved. So, could you plz check the following coding . I did this changes in CRM_OPPORT_H_MERGE method of CRM_OPPORT_H_BADI. This start date is not reflected on the Date_type 'Production Start Date' of Milestone tab.
CALL FUNCTION 'CRM_INTLAY_GET_PROCESS_TYPE'
 EXPORTING
 IV_ORDERADM_H_GUID = CS_OPPORT_H_BADI-REF_GUID
 IMPORTING
 EV_PROCESS_TYPE = lv_process_type
 EXCEPTIONS
 PROC_TYPE_NOT_FOUND = 1
 OTHERS = 2.
if lv_process_type eq 'ZOPS'.
 ls_appointment_com-REF_GUID = CS_OPPORT_H_BADI-REF_GUID.
 ls_appointment_com-REF_KIND = 'A'.
 ls_appointment_com-APPT_TYPE = 'ZOPPRODST'.
 ls_appointment_com-IS_DURATION = 'X'.
 CONVERT DATE CS_OPPORT_H_BADI-startdate TIME '000000' INTO
 TIME STAMP lv_from_date TIME ZONE 'UTC '.
 ls_appointment_com-TIMESTAMP_FROM = lv_from_date.
 CALL FUNCTION 'CRM_APPOINTMENT_CHANGE_OW'
 EXPORTING
 IS_APPOINTMENT_COM = ls_appointment_com
 CHANGING
 CT_INPUT_FIELD_NAMES = lt_input_field_name_tab
 EXCEPTIONS
 ERROR_OCCURRED = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endif.
thanks in advance
with best regards,
Madhusudan

Similar Messages

Add new tab for sales transaction

Hi,
I want to add a new tab in sales transaction for bank detail, the data of this tab should be get from BP master data, and save to crmd_order transaction table.
what method should I implement?
thanks
Gang

Hi Gang,
Use EEWB to enhance the order. The fields shall be added to CRMD_CUSTOMER_H table.
<a href="http://help.sap.com/saphelp_crm50/helpdata/en/43/04bede807721ece10000000a155369/frameset.htm">EEWB</a>
for populating these fields based on BP master data, use BADI COM_PARTNER_BADI method COM_PARTNER_MERGE.
This BADI gets called when you enter partners (sold-to-party). In the mentioned badi method, read bank details from BP master and set this to your Z-fiedlss using FM CRM_CUSTOMER_H_MAINTAIN_OW.
Hope this helps.
Regards
Kaushal

Regarding XIF Interface and Sale Transaction in CRM

Hi,
I have done the configuration in CRM system using XIF interface to communicate with other system.
We are in the process of implementing CRM, Product and Partner data has to upload in CRM. We are not using R3 for anything.
When i create a sales transaction using transaction code CRMD_ORDER,System allow me to save/create a business transaction even though i can see the error attached to it and at the same time I can see the BDOC number in SMW01.
But i dont see any relevant OUTBOUND IDOC against the BDOC, evenif i have configured it for external system and I was expecting Outbound IDOC with error status, please correct me if i am wrong.
I am using WE02 and WE05 to see my outbound idoc and i have not found anything here.
Am i missing some step in configuration which is required for converting BDOC to IDOC, Please suggest me.
Steps which i followed to configure the system are
1. Create a suitable RFC destination in the SAP IMG Define Target Systems for RFC Calls .
2. Create a logical system.
3. Create a receiver port (transactional RFC) in SAP IMG Define Port, indicating the RFC destination you created earlier.
4. Create a partner profile, for example, partner type LS with the partner number CRM_XML_BC, in the SAP IMG Maintain Partner Profile Manually.
5. Enter all outbound parameters for the logical system CRM_XML_BC in Create Outbound Parameters in the Outbound Parameters window .
6. Create a site (transaction SMOEAC). To do this, select Object Type Sites and Create Object. Assign your site a suitable name and select Site Type External Interface for IDocs. Assign the partner profile created previously as a Site Attribute.
7. Use object type Subscriptions to maintain a subscription for publication of the object with the predefined site.
8. Create an entry for the new site using XIF customizing transaction CRMXIF_C1 via F4 help (BDoc Type = <objname>, IF Type = 'CRMXIF_*_SAVE_M', Set relevant flag for complete Data and Return). The flag Flag for complete data is only relevant for the objects "order", "business partner", and "business partner relationship". It flags whether only delta changes or the object instance should be transferred completely. The object "business document" is always sent completely, regardless of flag status.
Thanks & Regards,
Manoj Tiwari

Hi Joao,
Thanks alot for your quick reply.
Yes i have selected "post it immediately" instead of "collect Idoc". should i select "post it immediately"??
About the Outbound parameter i specified everything like message type (crmxif_order_save_m), port , RFC destination of type R3 since we have SRM system, basic type (crmxif_order_save_m01), package and post the idoc immediately.
Here in our distributed environment we are sending data from CRM to SRM, means our target system is SRM.
I have created the Site of site type "External interface for idocs" and give the partner Number of SRM system and created subscription too as part of XIF setup.
Please reply me if i am going wrong in my approach.
Thanks & Regards,
Manoj Tiwari

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?

How to get the partners in gui transaction crmd_order

Hi,
Transaction CRMD_ORDER
Copy an complaint.
I need some help regarding how to retrieve the users of the partner functions in crmd_order.
I need them on headerlevel.
My problem is that when an order is copied then Im not able to find the usernames to the corresponding partnerfunctions.
As the order isn't saved yet; where can I retrieve the information.
Does anyone know a FM or a badi.
Thanks in advance.

Hi Lars Bernstorff Hansen,
Basically when you create a Order in CRM system it carries out the Determination of Transaction type and details for the same,now since the Order is not saved all the Determination is without any reference and is RAW data which the System stores in Buffer Memory.
After your Determination of all the Relevant Details,once you save the Order then the System Generates a Header GUID and it gets the Details of all the Items and Mapps the Corresponding Items to the Order no.
You will have to Save the Order for getting the Data you need
Also you may check the Order Data in FM:"CRM_ORDER_READ"
Also your Partner Functions for the Order shall Appear in "ET_PARTNER"
Hope it Answered your Queries..
Thanks and Regards,
RK.

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

Unable to create the implementation for BBP_PD_DOWNLOAD badi

Hi ,
Iam trying to create a new implementation for this BADI BBP_PD_DOWNLOAD as zbbp_pd_download but when iam trying to activate it .iam getting a message that already active implementation is there and i cannot create a new implementation unless i deactivate the other one.since it is a standard one i cannot deactivate it .
Has any one used this earlier . any inputs on this wil be of great help .
Thanks in advance

Hi
You can create any number of Customer Implementations, provided only one is active at a time.
Here are the steps ->
Either Using SE18 / SE19 Transaction, or
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
1. In the dialog box, enter a name for the implementation of the Add-In and choose Create. (Say ZBADI)
The system displays the initial screen for creating Business Add-In implementations.
2. On this screen, enter a short description for you implementation in the Implementation Short Text field.
3. If you choose the Interface tab, you will notice that the system has filled in the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
4. Save your entries and assign the Add-In to a package.
5. To edit a method, double-click its name.
6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
7. Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not carry out the following step:
8. Choose Activate.
When the application program is executed, the system carries out the code in the method you wrote.
Regards
- Atul

How to add tab on transaction crmd_order in sap crm

Hi all,
I want to add a tab on transaction crmd_order .on this tab I hav to put some fields and pushbuttons.When I click on this button then data will save on the external system .i.e. I hav to call third party system through this button and also we hav to retrieve that data from ext. sys.Plz tell me any enhancement method to enhance this transaction.I didn't find any user exit for this transaction.I can add fields or buttons on this transaction using EEWB but don't know how to call ext. sys.
Plz help me out.
Rewards will be given for good answer.
Regards,
Hemlata

Hi,
My solution is straight and simple and has following steps:
1. create a screen that you want to see in teh new tab. write code behind it.
2. Now the screen that you have created can be called into a new tab in CRMD_ORDER by using a BADI:
CRM_CUSTOMER_H_BADI~SET_SCREEN:
In this badi, you pass teh prgram name and the screen number.
Reward with points in case helpful
Sharif.

Reg: Can I code in standard implementation of a BADI "WCM_DECOUPLING"

Hi all,
I'm trying to use a BADI (WCM_DECOUPLING) for transaction IW32. But when I tried to create an implementation for this BADI in SE19, it is throwing the following error "BADI definition WCM_DECOUPLING is only provided for SAP internal use".
Then I've checked the attributes of this BADI in se18, an option "within SAP" is checked.
I've checked the old threads also, but I couldn't find any help to use this BADI somehow.
MY QUESTION: later, I've found using transaction SE84 that this BADI is already implemented by standard SAP in the name
"WCM_DECOUPLING_IMPL" and activated. But, it's runtime behavior is shown as "EA-PLM is deactivated; implementation will not be called". Can I use this standard implementation to code my changes or validations.
Thanks,
Rajan U

Dear Shahin,
Thanks for your prompt reply.
I've adapted the same method (SE24) to find this BADI. I see other BADIs doesn't have the required parameters flowing in. That is the reason why I am trying to some how implement this BADI.
My requirement: After creating work order in Iw31, a list of people has to approve the work order by using permit (ech one will have the unique permit key). For this a pop window containing table control of permit keys listed in the order is provided.
I've to place a check/validation to ensure that these permits are approved in the same order as it has to be done.
for example: 1) Functional head 2) General manager 3) Managing director
I've also searched for user exits, but, on that is suitable for this req is not working.
Please suggest me a method to do this.
or
if I create ZBADI i.e. ZWCM_DECOUPLING, will this be called inside the standard program? will the exit handler call this?
Please give me your suggestion.
Thanks,
Rajan U
Edited by: Rajan Usman Basha on Jun 2, 2011 5:45 AM

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.

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

Implementation of existing BADI

Hi All,
I'm stuck at a point where i want to implement a existing badi for selection screen enhancement of ik07 tcode..Wanna put input parameters on selection screen of Transaction IK07..
i think i've the correct badi please help me in implementing that..
here is the snap for the same..

Dear Sujeet,
For any t-code, if you want to implement BADI, check for Badi Names. After getting the exact exit name or BADI implementation name, go to transaction code se18,
Write the BADI name display.
In the menu, select implementations -> create and give one zname. double click and write coding. save and activate the implementation.
Regards,
Arati

No workitem found error in BBP_PD after Implementing N-Step BADI

Hi Gurus,
We have implemented N-Step BADI BBP_WFL_APPROV_BADI For Approvals Levels in SRM.
Work flow is triggering correctly and workitem is sent at all the levels. But in transaction code BBP_PD the status of the workitem is not updating showing the error message "NO WORKITEM FOUND" also status is not updating in BBP_PD.
Please reply with your suggestions.
Thanks in advance.
Madhukar

Hello,
Message should be raised within BBP_DOC_CHECK_BADI.
This badi would check if there is any approver available (you can use a FM BBP_WFL_DIN_APPR_CONTAINER_GET and take the return parameter ET_APPROVAL_AGENTS).
If it is empty, you could raise a message informing that no approver exists.
I hope this helps.
Kind regards,
Ricardo

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

In Sales Transaction 'crmd_order' Implementation of Opportunity BAdI

Similar Messages

Maybe you are looking for