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

Similar Messages

  • How to create customer in crm sales with crm 7.0

    hi,
    can anyone tell me how to create a customer?
    i am new to crm. I am learning crm sales
    Thanking you
    prasad

    Hi,
    As explained before, go to SALESPRO, SalesPro and SPRO are different.
    SALESPRO is a role in UI..make sure that it is added for your login.
    go to transaction crm_ui -> SALESPRO business role ->Account Managemnt in the navigation bar -> Accounts -> Corporate Accounts.
    Hope this helps!!
    Prerna

  • Error while creating "RETURNS" as ERP Sales transaction type

    Description: We are getting error while creating ERP SLO type "Returns-ZRE". Message prompts as "Creation of ERP Transaction failed". We do not get the message for other order types for example "Standard order".
    Please suggest. Please note that this is an ERP sales order in CRM UI not a CR< sales order.
    Thanks
    Shree

    Is this only for a particular order type?
    As stated above this can be to do with user authorisations or the trusted RFC set up. Some things to check are:
    - ST22 dumps in ECC
    - ST01 authorisation trace for the user in ECC
    - Trusted RFC connection set up

  • Adding custom fields to CRM Sales transactions

    What are the steps to add custom tab and fields to CRM transactions?
    By the way, we are on CRM 6.0 and are using SAPGUI.
    Thanks in advance
    Srini

    I tried using Easy Enhancement Workbench (EEWB) and was able to successfully generate the task under the project.
    But now I am getting short dumps in transaction CRMD_ORDER. Snap shot of the error is below.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "CL_EX_CRM_CUSTOMER_I_BADI=====CP" had to be
         terminated because it has
        come across a statement that unfortunately cannot be executed.
    Runtime Errors         MOVE_CAST_ERROR
    Except.                CX_SY_MOVE_CAST_ERROR
    Date and Time          01/26/2011 16:52:47
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_MOVE_CAST_ERROR', was not
         caught in
        procedure "IF_EX_CRM_CUSTOMER_I_BADI~CRM_CUSTOMER_I_SET_TITLE" "(METHOD)", nor
         was it propagated by a RAISING clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        It was tried to assign a reference to a rereference variable using the
        'CAST' operation ('?=' or 'MOVE ?TO').
        However, the current content of the source variable does not fit into
        the target variable.
        source type: "\CLASS=ZCL_IM_EEW_CUSTOMER_I01"
        target type: "\INTERFACE=IF_EX_CRM_CUSTOMER_I_BADI"
    Also, is there a clean way to back out these changes? Will deleting the project undo these changes?
    Thanks in advance
    Srini

  • How to create Oppertunity doc automatically after lead in CRM SALES

    Hi,
    how to create oppertunity doc automatically after creating lead in crm sales
    Thanks7regards
    kishor kumar

    Hi Kishore,
    Create SAP Business Workflow for Opportunity from Lead 
    Use
    A lead is a business transaction that describes, stores, updates, and manages the potential business interests of a business partner, and the interactions based on this over a period of time. The goal is to provide the "sales" area with the information gained in the lead, in order that it can be used as a basis for deciding whether to create an opportunity.
    The information gathered in the lead is transferred to the "sales" area via the workflow "create opportunity from lead".
    In the workflow, you decide whether the opportunity is generated manually or automatically.
    If the lead-specific attributes Priority and Lead group fulfill specific criteria, the workflow automatically generates an opportunity. Otherwise, the workflow sends a work item to the sales employee responsible, for manual creation. Once he has checked the data in the lead, the sales employee can either reject this lead or create an opportunity from it.
    The workflow is automatically started when the lead is saved.
    The sales representative entered in the lead is first taken as the sales employee whose task it is to create the opportunity based on the information in the lead. This person can be determined using partner determination in CRM, depending on the prospect in the lead, and can, for example, be a manager of a sales area. If no sales representative is entered, the workflow takes an organizational unit assigned in the workflow template, and sends the work item to all users assigned to the organizational unit.
    Prerequisites
    u2022     The type linkage for the start events AttributeChanged and SetErrorFree for the workflow WS10001011 are deactivated as a standard procedure, and, if you wish to start the workflow template, they have to be activated again in Customizing. The workflow task processors must also be maintained. In Customizing, choose Customer Relationship Management  Basic Functions SAP Business Workflow  Perform Task-Specific Customizing.
    u2022     The workflow template uses the user statuses SAAC (accepted by sales) and SARE (rejected by sales) of the status profile CRMLEAD. If you have defined several user statuses, the data flow for task TS10008154 (set status) must be adapted accordingly.
    u2022     When the opportunity is created, the workflow template uses the opportunity transaction type OPPT. If you have defined several transaction types for the opportunity, the data flow for task TS10008151 (create opportunity) must be adapted accordingly.
    u2022     If the sales employee rejects the lead, the workflow resets the qualification level to value 02 (warm). If you have specified your own qualification levels in Customizing, you need to adapt the data flow for task TS10007918 (change qualification level) accordingly.
    Process of Workflow WS10001011 (create opportunity from lead)
    The workflow "create opportunity from lead" is started when a lead is saved with qualification level Hot and status Error-free. The system uses the lead-specific attributes Priority and Lead group to check whether an opportunity can be automatically created, or a sales employee first needs to decide. If the sales employee decides that an opportunity can be created, the lead status is set to "accepted by sales", and an opportunity is created in the background. If necessary, this is forwarded to the sales employee to check. If the sales employee rejects the lead, the lead status is set to "rejected by sales", and the initiator is informed by mail.
    The workflow is ended if no opportunity is created and
    o     the lead is deleted or
    o     the qualification level of the lead is changed to a value other than Hot or
    o     the status of the lead is changed to a value other than Error-free.
    Path for the workflow:
    ==> SPRO
    ==> Customer Relationship Management
    ==> Basic Functions
    ==> SAP Business Workflow
    ==> Perform Task-Specific Customizing
    Select the Application Componenet  Abbrevation as CRM and expand
    Select CRM-BTX and expand
    Select CRM-BTX-LEA and click on Activate event linking  and acivate workflow WS 10001011
    It may helps you
    Regards
    Narayana

  • 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

  • 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>

  • 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

  • Unable to create sales transaction in POSDM though BAPI

    Hi
    ICurrently I am trying to create sales transaction in POSDM which is coming from POS thru XI to POSDM. But the BAPI  /POSDW/CREATE_TRANSACTIONS_EXT is throwing an error
    " Error determining sales item category for code 2001"
    It was working perfectly fine in development. I  have imported all transports from development to quality sytem. we also have BI plant and article data in our system. But not sure if anything other than this needs to be done.
    Thanks
    Naina

    Hi Amit,
    I would recommend you to raise the same query in the forumSAP CRM: Mobile Applications which is dedicated to queries related to mobile application and where you have more chances of getting the answer.
    <b>Reward points if my post helps!!</b>
    Best regards,
    Vikash

  • How to creat Action Profiles in CRM

    Hello Experts,
    Can any one guide me how to create Action Profiles in CRM for attaching the smartform ????
    Regards,
    Amol Tambe.
    SAP CRM Technical Consultant.

    TR: SPRO --> IMG -->Customer Relationship Management -->Basic Functions -->Actions -->Actions in Transaction >Change Actions and Conditions>Define Action Profiles and Actions
    Best Regards,
    Vishant

  • Getting an error while creating a ERP Quotation from CRM Sales Web-UI.

    Hi Experts,
    I am getting an error while creating a ERP quotation from CRM Sales Web-UI. Here  I am enclosing the screen shot. Please give me the solution for this.Thank you in advance.
    Regards
    Kishor Kumar.

    Hi Kishore,
    Please refer to the link below -
    Entry of ERP Sales Documents in SAP CRM - Sales Quotation and Order Management - SAP Library
    Also, refer to the SAP note -
    1446253  - FAQ note: ERP documents in the CRM Web UI (lead-to-cash scenario)
    This note will give you the related topic and the configuration required through SAP help links.
    Hope this will be useful.
    Thanks and Regards
    DJ

  • 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.

  • Create complaint with reference to CRM sales order

    Hi,
    We have the requirement to create a complaint as a follow-up to a CRM sales order.
    We don't want to reference the invoice, but only the sales order. The sales order is available in CRM,
    so I would expect that we can reference the CRM sales order when creating a complaint.
    However, what I find is that we need to implement BAdI "CRM_COPY_BADI_EXTERN". Is that true? Do we need
    to implement this BAdI?
    Is there a sample coding available?
    regards,
    Wim Olieman

    Perhaps I should create a new thread, appears the standard complaint return CRMR allows me to create the return mulitple times against the same sales order number in CRM 7.0.
    Our pricing flunctuates a bit, so we don't want the same order to be used over and over again in creating the return.
    Is this the same behaivor you see?

  • CRM sales order and APO transaction /n/SAPAPO/AC03

    Which sales order is seen in /SAPAPO/AC03 or /SAPAPO/RRP3 when you create an CRM sales order (ATP check is done in APO) and the order is replicated in ECC?
    Is the CRM sales order or the ECC sales order item displayed in the APO product availability overview?

    Hi Marc,
    The ECC sales order display depends on the availability of integration
    model and active ATP fields maintained in ECC material master
    In APO, the product view display is controlled in Order view
    customisation at APO under PPDS
    Regards
    R. Senthil Mareeswaran.

  • Which function module could be used to create ACTIONs in transaction

    HI,
        when we open a transaction use TCODE CRMD_ORDER, there is always a tab named 'Action'. And Which function module could be used to create a new action?
    THS!

    Hi Gang,
    I am not sure about the Function Module but ya if you access through this link i belive you will be able to create ACTION for your Transaction.
    Link:[Action|http://help.sap.com/saphelp_crm70/helpdata/en/54/238e39e1ba3541e10000000a11402f/frameset.htm].
    Let me know in case you need any more help.
    Vijayata

Maybe you are looking for