Sales process in crm

Hi Can any one tel abt crm sales process.
1. once so created in crm how it will replicate to the r/3 and wht is process is gng on in r/3
2. tel the contracts scenario in crm
Help me know this scenarios.
Edited by: gs.kumar on Jun 9, 2010 7:27 AM

HI,
The best way to know the processes you mentioned is through help.sap
Follow the link:
For sales process:http://help.sap.com/saphelp_crmscen70/helpdata/en/3e/24b225d18147fd820421368dd73e62/frameset.htm
For contract process: http://help.sap.com/saphelp_crmscen70/helpdata/en/3b/eb8b523e50434cab89c71d19169711/frameset.htm
Regards,
PP

Similar Messages

CRM winclient sales process probelm

Hello Experts,
I am working on CIC winclient sales process.
I have created Quote and follwup order in winclient.
But when I open the Quote in GUI(CRMD_order) transaction it is displaying with multiple follwup Quotes along with my sales order.
When i go and see the document flow ,
From Quote to order it is showing "Next Document,"
But Quote to Quote it is showing "participent communication process"
Please let me know why the system is behaving like this.
Thanks

HI,
The best way to know the processes you mentioned is through help.sap
Follow the link:
For sales process:http://help.sap.com/saphelp_crmscen70/helpdata/en/3e/24b225d18147fd820421368dd73e62/frameset.htm
For contract process: http://help.sap.com/saphelp_crmscen70/helpdata/en/3b/eb8b523e50434cab89c71d19169711/frameset.htm
Regards,
PP

Issue with creation of sales order in CRM system

Hi Experts,
Here are the details of the process we followed
1.     We found a Function Module u201CBAPI_BUSPROCESSND_CREATEMULTIu201D which is used to create a sales order in CRM.
2.     We have set a Break point in the FM u201CCRM_ORDER_MAINTAINu201D and tried to create a sales order using the transaction u201CCRMD_ORDERu201D. For this the parameters we have given are
a.     sold-to-party
b.     ship-to-party
c.     quantity
d.     product
And after this we have saved the order and the order is saved and in the debug mode we have the parameters in u201CCRM_ORDER_MAINTAINu201D and we found all these     parameters in the FM.
3.     After this we have given all the parameters mentioned above in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and still the order is not created, gave an error message saying that CRM_ORDER: Incorrect values in the interface object.
4.     We checked the CRM_ORDER badiu2019s interface and it is having only header guid to be given. We gave this header guid also in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and then it gave a different error saying that : Document cannot be saved.
5.     Finally we are not able to know the parameters to be passed to the FM to create an order.
Any inputs will be highly appreciated.
Thanks a lot in advance.
Lakshman.

Hi Easwar,
Now i am able to create a sales order by passing the parameters to "BAPI_BUSPROCESSND_CREATEMULTI" and the parameters i am passing are Process_type in the ORDERADM_H, parner_fct (partner function), partner_no , Quantity and prod_ordered (product name) but after creation of sales order using my report program and if i see the sales order uisng transaction crmd_order (using transaction ID) or crmd_orderadm_h(using headerguid) or crm_order_index, only the PROCESS_TYPE is updated but the remaining parameters which i passed like QUANTITY,PRODUCT NAME,PARTNER NUMBER are not present in the sales order. I am providing the code which i have written for creation of the sales order. Can you please look into it and tell me where i might have went wrong??
*& Report ZCREATEORDER_TEST
REPORT ZCREATEORDER_TEST.
DATA : LV_HEADER_GUID TYPE GUID_32,
WA_HEADER            TYPE         BAPIBUS20001_HEADER_INS,
ITAB_HEADER          TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
ITAB_CREATED_PROCESS TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
ITAB_OBJECTS_TO_SAVE TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS,
ITAB_PARTNER        TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_INS,
lt_product_i TYPE STANDARD TABLE OF BAPIBUS20001_ITEM,
wa_product_i type BAPIBUS20001_ITEM,
lt_schedlin_i type standard table of BAPIBUS20001_SCHEDLIN,
wa_schedlin_i type BAPIBUS20001_SCHEDLIN,
ITAB_INPUT_FIELDS TYPE TABLE OF bapibus20001_input_fields,
ls_inputfields TYPE bapibus20001_input_fields,
WA_PARTNER          TYPE BAPIBUS20001_PARTNER_INS,
ITAB_RETURN          TYPE STANDARD TABLE OF BAPIRET2,
WA_OBJECTS_TO_SAVE LIKE LINE OF ITAB_OBJECTS_TO_SAVE,
           "To store the Objects to be saved.
WA_CREATED_PROCESS LIKE LINE OF ITAB_CREATED_PROCESS,
ITAB_SAVED_OBJECTS   TYPE STANDARD TABLE OF BAPIBUS20001_OBJECT_ID,
WA_SAVED_OBJECTS    LIKE LINE OF ITAB_SAVED_OBJECTS,
GC_X type c.
gc_x = 'x'.
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    ev_guid_32 = lv_header_guid.
CLEAR : WA_HEADER.
Passing the respective values from the Header table to internal table.
WA_HEADER-GUID          = LV_HEADER_GUID.
WA_HEADER-PROCESS_TYPE = 'ZTA'.
APPEND WA_HEADER TO ITAB_HEADER.
*Appending the values to the ITAB_HEADER.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'ORDERADM_H'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'PROCESS_TYPE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
*ls_inputfields-ref_handle = '0000000000'.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-objectname = 'ORDERADM_H'.
ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'ORDERADM_H'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'GUID'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CHANGES MADE
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'LOGICAL_KEY'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'GUID'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
   ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'QUANTITY'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
   ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CHANGES MADE
WA_PARTNER-REF_GUID = LV_HEADER_GUID.
WA_PARTNER-REF_KIND = 'A'.
giving the partner function and partner no 000000038 for slod to party
WA_PARTNER-PARTNER_FCT = '00000038'.
WA_PARTNER-PARTNER_NO = '10017'.
APPEND WA_PARTNER TO ITAB_PARTNER.
*"ADDING VALUES for the product
wa_product_i-header        = lv_header_guid.
wa_product_i-handle        = '0000000001'.
wa_product_i-ordered_prod = '12000014'.
wa_product_i-mode          = 'A'.
APPEND wa_product_i TO lt_product_i.
*"ADDING VALUES for quantity
wa_schedlin_i-quantity   = 30.
wa_schedlin_i-handle = 1.
APPEND wa_schedlin_i TO lt_schedlin_i.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
*ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'REF_GUID'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'PARTNER_FCT'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'PARTNER_NO'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
TABLES
    HEADER          = ITAB_HEADER
    ITEM            = lt_product_i
    RETURN          = ITAB_RETURN
    PARTNER         = ITAB_PARTNER
    INPUT_FIELDS    = ITAB_INPUT_FIELDS
    CREATED_PROCESS = itab_created_process
    SCHEDULELINE    = lt_schedlin_i.
READ TABLE ITAB_CREATED_PROCESS INTO WA_CREATED_PROCESS WITH KEY GUID = LV_HEADER_GUID BINARY SEARCH.
WA_OBJECTS_TO_SAVE-GUID = WA_CREATED_PROCESS-GUID.
Appending the Guid of the contract to be saved to the internal table
APPEND WA_OBJECTS_TO_SAVE TO ITAB_OBJECTS_TO_SAVE.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
EXPORTING
    update_task_local = space
    save_frame_log    = GC_X
TABLES
    objects_to_save   = itab_objects_to_save
    saved_objects     = itab_saved_objects
    return            = itab_return.
Calling the Standard BAPI to Commit the transcation.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
I have debugged the above code, all the values are passing are passing to the FM "'BAPI_BUSPROCESSND_CREATEMULTI'" and these passed to the CRM_ORDER_MAINTAIN and then to CRM_ORDER_READ which are called inside the "'BAPI_BUSPROCESSND_CREATEMULTI'". Finally the sales order is created but not able to see all the values that i am passing except PROCESS_TYPE.
Thanks a lot in Advance,
Lakshman.

Meet a problem of data exchange for sale order from CRM to R3.

Dear Friends:
      I do the data exchange for sale oder from to R3 today , the problem's detail is as follows:
      When i save a sale order in CRM (Version is 5.0) . it can automatically generate a bdoc which bdoc type is BUS_TRANS_MSG. but the bdoc status alway is "Sent to receivers (not all have confirmed)". and the original order in CRM can not be change .it quote that "Document is being distributed - changes are not possible", so i check the order status analysis in detail .it presents two error messages ," Event 'BEFORE_CHANGE', attribute '     FINI': Error code for function module 'CRM_STATUS_BEFORE_COMPLETED_EC' , "Item is not yet completed in OLTP system". so i check the order in R/3 ,it has already been create and without any error messages.
   Would like to tell me how to solve it . thanks your any idear..

Hi Benjamin,
When performing uploads to R/3 from CRM there is a response from the OTLP system that is sent back to the CRM Middleware to confirm that the data records were received and processed correctly.
Here is a checklist you can run through to verfiy that the connections, systems and objects that are needed are all in place:
<b>On R/3 system:</b>
- Check R/3 outbound queue (transaction SMQ1) for any entries that are not reaching CRM.
- Check that all RFC destinations on R/3 are defined correctly and are pointing to CRM
- Check the CRMCONSUM table in R/3 to ensure CRM is registered as a consumer
- Check the CRMRFCPAR table in R/3 to ensure that order objects are valid for exchange between R/3 and CRM
- Check for any short dumps in R/3 (ST22/ST21)
<b>On CRM:</b>
- Are there entries stuck in the inbound queue (SMQ2) with R3AU* names?
- What does the CRM Middleware Trace show (SMWT)? Sometimes this has more detail than the specific BDoc overview (SMW01)
- Check for short dums in CRM (ST22)
Let us know what else you uncover and we can work from there.
Brad

Saving Sales order in CRM to R/3

Dear Friends,
When i make a Sales order in CRM it is flown to R/3. There is no problem when i do this. But if i make any changes in the Sales order in CRM then the Delivery block in the item schedule lines of same sales order in R/3 comes as pending for approval. I m not gettin how to deal with this.
Please help.
Rachana.

Hi Rachana,
Do this way , create order in CRM and check the same in R/3 whether all relevant values are transfered to R/3 or not. Once you are through, then do the changes in CRm again and save then cheque whther the changes you had done in CRM is replicated in R/3 or not. if not then you need to trace why its not happend.
Secondly check in the Transction type of CRM whether the following setting is enabled or disabled:
No Change document
Post process from:
Regards
Arun Kumar

Third Party Order Processing in CRM

Hi,
I need to create an item category in CRM which enables me to activate third-party order processing in ECC. So the process should be:
- Create sales order in CRM, choose item category "TAS"
- Save sales order
- Order triggers purchase req. in ECC (or sales order with item cat. TAS)
I read sap.help. where it says we need to use SCM etc. for this process. Actually we only have ECC connected. Is it still possible like that?
Rgs
Anke

Hi Anke,
1.Create a ztrans type and item category by copying TA and TAS in CRM.Maintain the same document type and item category in ECC.
2.select the "Create PO Automatic" option in the ECC item category definition.
3.Assing the Purchase order document type to Schedulines and assign schedule line to Item category.
Hope it helps....
Regards,
S Reddy

How the sales orders in CRM replicated to ECC??????????

Hello gurus
I am implementing CRM with integration with ERP, I would like to know if I have more than one type of sales documents in CRM and I want to replicate them to ECC do I have to have the same number of the sales document types in ECC or only one document type in ECC and all the CRM Sales document types will be replicated to it
Secondly regarding the service order processing , is it replicated to sales order or service order in ECC also do I have to have the same number of sales, service document type
If there are any useful links please provide
Thanks
Jacopo Françoise

Hi Jacopo Françoise
There are some prerequisites for replication.
1. Your Item categories need to be configured to be released to R/3 for specific puposes like Pick, pack and delivery reasons.
2. Only Sales transaction and delivery related transactions will be replicated to R/3 like Sales Orders and Service orders.
3. When it goes to R/3 every order is a sales order type like Sales Order CRM - Replicated as Sales Order
4. When replicate the documents it is important that you must have same document types and same item categories..
5. If billing documents are directly created in R/3 then you dont need the exact same doucments, but your item categories will play a major role in creating a mapped document in R/3. you still have to map appripriate settings to tell the system on what item categories talk to what Doucment types.
Thats the overview but list could go on... let me know if you have any specific issues
Thanks
Raj

Bapi or function module to create a sales order in CRM 5.1 system

Hi experts,
Anyone knows any Bapi or function module to create a Sales order in CRM 5.1 system directly.
Thanks.
regards.
Ruchi.

hi ruchi,
sory for the late respond, got a lot works to be done.
based on my experience, you need several more information such as currency, uom for quantity, sales organization, etc.
and honestly, i have never tried to create an order by just using 3 information ( sold to party, item, and quantity ),
but i think it is possible because some of the information can be determined using configuration, but still some information is missing and the order that you create will have an error and you can't do next process of the order unless somebody fix / fill the information needed.
just an idea, perhaps you need some z-tables to put your certain information needed for order creation and the information is maintained for each sold to party ( sold to party is a key of z-tables ) and each time order is created, all information will be query in this tables.
and for this tables may be you can create an offline maintainance scenario using an adobe document. by this way, the sold to party can maintained all his/her/their information by them self.
and by using this scenario, you can still maintain / create the order by programming ( perhaps using function module CRM_ORDER_MAINTAIN or else ).
actually i want to implement in my company but don't have a chance becuase all has been set up and the management will think twice for implementing this scenario.
hopes it hels
cheers

Function Module to create a Sales Order in CRM

Hi Experts,
I want to create a function module which creates a Sales Order in CRM.
As of now, I'm making use of the function module 'BAPI_BUSPROCESSND_CREATEMULTI'.
I have product ID and Quantity.
Please let me know what all rest of the fields are mandatory to create a Sales Order using this function module.
Thanks in Advance,
lakshman.

Depending upon the configuration many things could be mandatory. Assuming no such things in your system, Process type (order type) is required and it is good to give the Sold-To business partner and the Org Details, for the Header information. For the item information, you need the Product and Quantity.
In theory, in CRM, you can create a transaction and "save" it with lot of errors. So, even if you don't give enough information, you will have a transaction with error. You can later fix it the input to fix the errors.
Best way to know is to use your SAPGUI (CRM Online) version crmd_order and find for your implementation.
Easwar Ram
http://www.parxlns.com

Sales Process at the Opportunity Revenue Level

Hello,
My client is managing all the opportunities at the part level (product revenue) level. All there approvals happen at the part level and it is possible that for an opportunity there could be muiltiple parts with some Closed/Won and some Closed/Lost.
I believe managing sales process is currently available at the Opportunity header level. I tried to expose the existing Sales Stage field on the Revenue record on the Related Object page layout. But it is read-only. OD does not allow me to enable it and looks like it copies the sales stage values from Opportunity header.
Is there a way to enable Sales Process at the Product Revenue level ?
Thanks

Robin, this functionality is not available at this time. You can submit a enhancement request to CRM On Demand customer care.

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

Cannot do MIGO in Third Party Sales Process with shipping notification

In the Third party sales process with Shipping notification,the item category for the material is TAS (Billing relevance=R),item category group is BANS.
Intially sales order is created,then using me21n with reference to purchase requisation purchase order is created,then in MIGO stage i used the PO No there but i get the message no item found in PO.
what adjustment have to be done in order to do MIGO

Refer following SDN thread, by that you will be able to get overview on best practices about Third Party Sales & necessary configuration you need to follow for statistical GR:
- Third party direct shipment (II)
Further maintain Billing Relevance for Item Category as G - Order-related billing of the delivery quantity.
Regards
JP

Accounting Entries hit in Third party Sales Process

Hi,
Can anybody tell which accounting entries are hit when we create the following entries in third party sales process
1.When Sales Order is created.
2.When PR is Created
3.When ME21N is done
4.MIGO
5.MIRO
please provide your valuable suggestion..
Thanks...

Hi,
1. When Sales Order is created.
No FI Entry
2. When PR is Created
No FI Entry
3. When ME21N is done
No FI Entry
4. MIGO
(GBB-VAY) COGS - 3rd Party A/c - Dr
(WRX) GR/IR Clearing A/c - Cr
5. MIRO
Vendor Account - Cr
GR/IR Clearing A/c - Dr
6. VF01
Customer Account - Dr
Sales Revenue A/c - Cr

Number Range issues with sales orders in CRM and R/3

Hi,
We are currently using CRM4.0. I have sales orders created in R/3 and they are replicated into CRM. These sales orders can only be created in R/3. I have given them a number range of 0000000001 and 0005899999, however we have reached the number 0005899999 so we increased the internal number range for the sales orders in R/3 to 0009499999, however we forgot to update the number range for the corresponding sales transaction type in CRM so we are getting the following error in CRM:
+Enter a business transaction number between 0000000001 and 0005899999
Message no. CRM_ORDERADM_H532
Diagnosis
You have attempted to enter a transaction number which is not allowed for the transaction type.
Procedure
Enter a number between &1 and &2. Make sure that you issue a number which has not already been issued.+
We have now updated the CRM number range to match that in R/3 to 0000000001 and 0009499999 but we are still getting the error above on our existing sales orders in CRM. I thought that increasing this number range it will remove the error but when I open sales orders in CRM the error is still there.
Is there any way to remove this error message? Any tips or advice would be much appreciated.
Please note we've already checked the post Re: Number Range Problem and note 427289.
Kind Regards
JoJo

Hi Sirisha,
The solution depends on the exact issue you are facing.
The CRM Sales Order is created OK, but you only see the error when you open the Sales Order?
If this is the case, then you can follow the steps below:
1. Find the Message ID and Message No for the error message
2. Use Program - CRM_MESSAGES_DELETE to delete error messages from the error producing Sales Orders.
Let me know if this is not the issue you are facing.
Regards,
Nelson

Mass sales orders from CRM to ECC

Hi,
We have a requirement to mass upload sales orders from CRM system ECC system. I could not able to find any option to push sales orders in bulk from CRM to ECC.
Could you please let me know if you know any kind of solution for this kind of scenario.
Thanks in advance!
Regards,
Kumar B.

Hi Maggie,
Thanks a lot for your response. But I could not able find CRMD_MASS_UPDATE in CRM system as well as in ECC.
Could you please let me know how to try this other please let me know the program or tcode.
Regards,
Kumar B

Sales process in crm

Similar Messages

Maybe you are looking for