SALE transaction

Hi ,
I need to send MATMAS type idocs from BD10 transaction . How do i define the distribution model in SALE . Can somebody plz help.
Thanx and regards ,
Srestha

Hai Srestha Dutta
Go through the following Steps for sending Material form One Server to another
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode  BD64 ? Create Model View
Tcode  BD82 ? Generate partner Profiles & Create Ports
Tcode  BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
        save and goback.
2) Tcode BD50--->  check the MATMAS check box save and comeback.
3) Tcode BD51--->  goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52--->  give message type : matmas press ok button.
   select all  what ever you want and delete remaining fields.
   save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
   it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
   give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Thanks & regards
Sreenivasulu P

Similar Messages

  • Payment Terms in Sales Transaction...!

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

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

  • Error message while creating Sales transaction

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

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

  • How to restrict a Sales Transaction being created Straight up

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

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

  • Customer pricing procedure in Sales transactions

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

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

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

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

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

  • Importing Sales Transactions into Oracle Financials

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

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

  • Sales transaction details in OIC

    Hi All,
    Im new to OIC. I want to get the sales transactions details for the employee in OIC.
    I want to know the table name which stores the sales transactions details in OIC.
    I explores in cn_commission_headers_all. But couldn't find anything
    Please provide some pointers

    Hi,
    In cn_commission_headers_all there is one column 'direct_salesrepid'.
    You can find salesrep_id from cn_salesreps view.
    You need to make joins between cn_calesreps and cn_commission_headers_all.
    This was the one way.
    The other way is:
    Generally orders are collected in cn_comm_lines_api_all in which you will find the transactions made by each employee. There is a column callled employee_number.
    Regards,
    Krunal

  • How to Assign Logical System to a Client in SALE Transaction

    Hi ABAP/EDI Specialists,
    1How to Assign Logical System to a Client. In the SALE transaction window.
    I didn't see any Receiving and Sending Systems(Tree). But I can see Logical Systems. In the Definition and Assign Subtree are there. I created two Logical Systems STUD_S and STUD_R. When I executed Assign Logical Systems. I got a window, Where I can see a list of Clients. I got confused, how to Assign those Two Logical Systems to Client 800 and 810. Finally I double Clicked on each client and in the next window. I changed the Logical System to STUD_S for Client 800 and Logical System STUD_R for client 810. and saved them.
    Is this procedure correct???
    Why I need this is, While generating partner profiles in ALE Model (BD64), I am getting no list at all. When I executed I got no list.
    "No messages have been defined for the selection conditions in the Model"
    I got struck at this point.
    Please help me to come out of it.
    Thanks,
    Chinna

    Hi Chinna,
    Thanks for such a valuable information. I am able to move further. But i got struck while generating parntner profiles from ALE distribution model.
    Log For Partner Profile Generation:
    Partner:
    Partner ZVK_SS_800 as partner has been Created ( Sending System)
    Partner ZVK_SS_820 as partner has been Created (Receiving System)
    Port:
    Port Cloud not be Created
    RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
    Enter the RFC destination and Restart the generation
    It is not recognizing the RFC port, even though i followed all the steps correctly.
    While creating RFC destination, can someone tell me How to fix the above error and what is the Client No, Username and Pasword i have to give.
    Thanks
    Chinna
    Edited by: Chinna on Jun 6, 2008 7:43 PM

  • 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

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

  • 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

  • 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

  • LSMW for sales transaction

    Dear all,
    For the migration data project , to migrate sales transaction(contract) from our legacy system to SAP in a huge amount, we use LSMW with I doc processing, we upload the data with three steps :
    1. first we upload the sold to party, 2.then we upload the ship to party,3.we upload the bill to party.
    When im upload the sold to party, the system otomatically generate ship to party and bill to party with the same number BP as sold to party, so when i upload the ship to party, my contract become have two ship to party, and its also happen when i upload the bill to party. We have use the same method 6 month ago to our system and this situation doesn't happen back then(back then the system dosen't otomatically generate ship to party and bill to party with the same number BP as sold to party). Could anyone tell me what could be the problem? Thank you.
    Regards
    Indah

    Dear Glenn,
    I'm doing LSMW in CRM, just for information i already done building relationship for sold to party, bill to party and ship to party, one sold to party may have many ship or bill to party. And the data is really huge so i can't mantain which the main partner for sold to party each time, because they could have different ship to party,do you have another solution??
    Thank you
    Regards
    Indah Puspita
    Edited by: Indah Puspita on Jan 7, 2008 8:38 AM

  • 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

  • Status of sales transactions (table names??)

    Hi
    I am using status profiles for my quotations. Would you please help me which table should I use to get status of sales transaction (quotations).
    Regards
    Javed

    Link: http://www.sap-img.com/
    Topic: Free ABAP eBook Download
    SAP MM, SD, FI, PS, PP, PM, HR, System Tables
    Regards,
    Rajesh Banka
    Reward suitable points.
    How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Maybe you are looking for

  • Stock blocking for a customer

    Dear All, We have a scnario where some materials at depot needs to be blocked for a particular customer. As and when orders arrive from this customer, this material would be delivered to him. The system should NOT allow the supply of this material to

  • Openeing a pdf with native pdf reader: openwithdefaultapplication

    Hello, Wondering if anyone can help on this one. From what I have read AIR for android does not support openwithdefaultapplication. The device I am developing for , the Motorola Xoom does not support pdf viewing in StageWebView or the browser. I have

  • Variable values in composite.xml property

    Hi, i've got the similar proble to: variable values in composite.xml property Static value for property <property name="oracle.webservices.auth.password" type="xs:string" many="false" override="may">admin</property> <property name="oracle.webservices

  • TS3274 My iPad won't turn on and pressing the top button won't help

    My iPad won't turn off, it was charged and suddenly turned off and won't turn on on again, I tried holding down the top button but nothing happened. What will I do?

  • Sticky load balancing not working  because of Address Translation

              This came up before - see below. I don't understand what the           soltion is/was.           WL Server puts it's ip address in the WebLogicSession cookie           which is an internal address 192.168.201.41           WL proxy knows WL