Problems in Sales Document Exchange between CRM 7.0 and ECC 6.0

Hello,
we updated our CRM system to CRM 7.0 and the ERP to ECC 6.0 .
Now I am trying to fix the dataexchange again. However salesdocuments from the ERP are stopped in the inbound queue of the CRM system.
The error from the SMW01 is :
At least one entry could not be found in object buffer
Message no. CRM_ORDER_MISC106
I think that there is some configuration missing in the CRM or the ERP system. However I did not know where.
Does someone knows the error or is able to give me a hint?
I maintained the table CRMPAROLTP in ERP:
CRM_MAX_QUEUE_NUMBER_INITIAL     MATERIAL                              CRM     5
CRM_MAX_QUEUE_NUMBER_INITIAL     SALESDOCUMENT                              CRM     2
CRM_NO_BEFORE_IMAGES     SALESDOCUMENT     CRM                                                                               
CRM_RELEASE                                                                                  701
CRM_SCENARIO     INT_CHANGE_ORDER     YJB4                    A
CRM_SCENARIO     INT_CHANGE_ORDER     YJC4                    A
CRM_SCENARIO     INT_CHANGE_ORDER     YXIA                    A
CRM_SCENARIO     INT_CHANGE_ORDER     YXIG                    A
and the table SMOFPARSFA in CRM:
R3A_COMMON     CRM_AUTO_DELTA_EVENT_ACTIVATION                                                                        X
R3A_COMMON     CRM_DEFAULT_DESTINATION     CRM_R3MATERIAL_AVAIL                                               K90CLNT001
R3A_COMMON     CRM_R3OLTP_ACTIVE                                                                        X
R3A_COMMON     MAX_PARALLEL_PROCESSES                                                                        5
R3A_COMMON     WAIT FOR UPDATE     RESPONSE_DLV                                               X
R3A_COMMON     WAIT FOR UPDATE     SALESCONTRACT                                               X
R3A_COMMON     WAIT_FOR_UPDATE     SALESDOCUMENT                                               X
R3A_SALES     BEHAVE_WHEN_ERROR                                                                        R
R3A_SALES     INT_CHANGE_ORDER     YJB4                                               A
R3A_SALES     INT_CHANGE_ORDER     YJC4                                               A
R3A_SALES     INT_CHANGE_ORDER     YXIA                                               A
R3A_SALES     INT_CHANGE_ORDER     YXIG                                               A
R3A_SALES     INT_NUMBER_ASSIGNMENT
R3A_SALES     PRICINGTYPE                                                                        G
Best regards,
Nils Kloth

Can you bump up the trace level (to detailed) via SMWT transaction and then re-submit this bdoc ? check if you get additional details about the error.

Similar Messages

  • Basic question regarding Contract data exchange between CRM and ERP

    Hi,
    1) At a very general level, can somebody tell me via what technology are contract documents exchanged between CRM and ERP? IDocs, RFC modules or proxies?
    2) Is it possible to sychronise changes in a contract, e.g. if the contract is changes in the ERP system, those changes are auotomatically updated in the CRM contract?
    3) Can somebody point me to any documentation on this?
    Kind Regards,
    Tony.

    contracts are exchanged between CRM ans ERP ssytem ny RFC and FM , you use object SALESCONTRACT for this,it is possible to synchronize changes between both the systems

  • Sales Document Creation in CRM System

    Dear all,
    We are implementing CRM 5.0 and ECC 6.0 (IS-Retail) for our client. As per the Business Process Customer creation take's place in CRM, which uploads Customer Records into ECC system.
    Material Master (Article), Pricing Procedure and Condition Types are being maintained in ECC system only.
    Now the new requirement is to create Quotations in CRM system, in turn it has to upload into ECC system. We have to enable or maintain all article data, Pricing Data and Discounts in CRM system also.
    I don't know how could we exchange the Article Master Records (Material), Pricing Procedures and condition types between ECC system.
    I have expertise in CRM Marketing. by getting basic understanding of CRM and ECC data flow landscape, Middleware Settings and Object downloads, I have confidence to map the requirement into SAP successfully.
    I request you to educate me on this scenario, your help and suggestions will be highly appreciated.
    Thank you
    Raghu ram.

    Hi,
    i'm not quite sure about ECC retail, but for sure, as per CRM 5.0 and ECC 6, depending on your scenario, you may not need whole complete set of pricing, nor the condition tables to be maintained in CRM.
    you can use minimum pricing which is basic condition type PR00. once the quotation is saved in CRM, during the replication process, the pricing will be determined in the ERP and passed back to CRM. so when you look into CRM quotation document, you will be able to find all the condition types maintained in CRM.
    however, this scenario is not suitable if you require customer to review the pricing before saving the quotation, let say internet sales / e-commerce. then in that case you'll probably need to have complete set of pricing in CRM.
    hope this helps.

  • Document that explains the differnce between CRM 3.0 and CRM 5.0

    Hi,
    Please, do you have any power point or pdf presentation that explains delta functionalities between CRM 3.0 and CRM 5.0.
    If you could send to me I would appreciate a lot.
    Best regards,
    Xavier de Toca

    Hello Xavier,
    I would suggest that you check the <a href="http://service.sap.com/     /~form/sapnet?_SCENARIO=01100035870000000202&_SHORTKEY=01100035870000429833&">Release Notes</a>.
    Regards
    Gregor

  • Problem with Edit IN function between LR 2.3 and PS CS3

    I recently upgraded my system to a Windows Vista 64 bit Core 2 Quad with 8 GB.  Lightroom now works and loads images the way it should. I do have one major concern and need any help possible.
    I am using LR 2.3 in 64 bit and PS CS3 ver 10.0.1 (which is 32 bit - loads slowly but otherwise works fine).  The problem I am encountering is in LR Develop / Photo / Edit In...  - using any of the menu items:
    "Edit in Abode Photoshop CS3"
    "Open as Smart Object In Photoshop"
    "Merge to Panorama in Photoshop"
    "Merge to HDR in Photoshop"
    "Open as layers in Photoshop"
    Photoshop opens but no image(s) are exported and I receive the message in LR - "The file could not be edited because Adobe Photoshop CS3 could not be launched."
    Photoshop, however, was launched but no image exported and so I can't work on the image in PS.  The appropriate TIFF image is created in LR for the first two menu items - nothing for the last three menu items.
    I can create a partial work around by setting PS as an external editor, however, I can't use 4 of 5 of the menu items.
    All the menu items work fine in Windows XPpro.
    Any help is much appreciated.
    PS I also tried the most recent Window 7 RC with exactly the same results.
    Thanks
    Bob

    Don
    I wasn't shouting - I just cut and paste the exact text and font in its original size and type as was shown in the message.  Never had a thought that someone would be offended by cutting and pasting exactly what was in a message - it would appear that John Williams saw it for what it was.
    However, sorry if I offended you.
    Bob
    Date: Mon, 1 Jun 2009 19:15:15 -0600
    From: [email protected]
    To: [email protected]
    Subject: Problem with Edit IN function between LR 2.3 and PS CS3
    There is no reason to shout. There are only other users here trying to help.
    >

  • Differance between crm 4.0 and 5.0

    hi gurus
    what's the difference between crm 4.0 and crm 5.0 plz send the details
    mahesh

    HI Mahesh,
    4.0 dont support certain funtionalities such as
    tour planning
    shelf planning
    New model of WebClient
    5.0 have IPC as an integrated component for pricing compare to a standalone component in CRM 4.0
    Best Regards,
    Pratik Patel
    <b>Reward with Points!</b>

  • Key difference between CRM 4.0 and CRM 5.0

    Hy All gurus...
    I just started in CRM 5.0 and i was wondering what is the difference in between CRM 4.0 And CRM 5.0 and other version of CRM.
    If any body can send me sme useful links that will be a great help...
    Thanks In advance

    Hy,
    THE Messages and Alert are independent of JAVA in CRM 5.0
    where as in CRM 4.0 they are dependent on java.
    Difference i found is of interaction at an height level with user,
    The IC WebClient Architecture section was
    redesigned completely to offer a better
    interaction to the IC WebClient
    technology.
    Abstract graphics explain how the technical components of the IC WebClient play together in the
    architecture concept.
    To handle indvidual objects , Wide seen has been covered to get a clear vision in comparision to crm 4.0.
    Regards
    Saurabh
    Edited by: saurabh khanna on Feb 26, 2008 2:06 PM

  • Difference between CRM 7.0 and CRM 5.0

    Hi Gurus
    What’s the Difference between CRM 7.0 and CRM 5.0?
    Which one is the latest version in my SAP CRM?
    Thanks
    Mahi

    hi
    first up i should tell you version &.0 will be released in this year end
    main difference lies between CRM 5.0 and above versions is the user Interface. The whole CRM version has been refined as
    1. online Web-enabled.
    2. uses the IC Webclient Framework and
    3. provides a user frndly inferface.
    there are many mutliple functionalities being added inall the CRM modules
    but still major differnec i will say is user interface
    as u have seen the differemnce between XP and Vista in case of MS operating system
    best regards
    ashish

  • What's the difference between CRM 5.0 and CRM 2007?

    Hello Experts:
    I will join a CRM upgrade project(from 5.0 to 2007). Now I am using CRM5.0.
    I have a question:
    What are the main differences between CRM 5.0 and CRM 2007? Should my ABAP/Dynpro programs be changed to fit 2007?
    Thanks.
    LiuBo

    Hi Bo Liu,
    There are lot of functional changes to CRM 2007 from CRM 5.0.
    You can check the functional differences for each scenario of CRM in the below link.
    https://websmp106.sap-ag.de/CRM
    For features and benefits of CRM 2007, you may refer the below link.
    http://www.sap.com/solutions/business-suite/crm/CRM2007_features.epx_
    Hope this helps!!
    Thanks and Regards,
    Pavan Kumar Gali.

  • Difference between CRM  5.0 and 4.0  version.

    Hello Experts,
    Please let me know the exacat difference between CRM 5.0 version and 4.0 version.
    Please let me know.
    Thanks

    Hi Koti,
    There are some significant differences between CRM 4.0 and CRM 5.0.
    1. IC Web : Locking and Handling of entities should be handled explicitly in CRM  
                      4.0 where as the same is handled implicitly in CRM 5.0.
    2. In 4.0 most of the Std Classes can be inherited but in 5.0 most of the Std
       Classes cannot be inherited as they are made as Final  Classes.
    3. CRM 5.0 and 5.1 so on.... versions have introduced CRM specific User Interface which is very flexible and simplified as you can jus drag and drop the objects for creation of custom application.
    Thanks
    Siva

  • Difference between SAP 4.7 and ECC 5.0

    hi frnds
    .what is the difference between SAP 4.7 and ECC 5.0?
    regards

    Hi,
    Following are the basic differences as far as MM Module is concerned
    Pickup list - Batch where-used list display in transaction MB56
    u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
    u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
    u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
    Usability enhancements for transaction MIGO for the posting of goods movements
    u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
    u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
    u2022 User changes the default values in the menu path "Settings -> Default Values."
    u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
    Goods receipt
    Goods issue
    Transfer posting
    Remove from storage
    u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
    New report : display list of invoice documents (MIR5)
    u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
    u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
    u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
    u2022 In the output list, the report shows both posted and held invoices.
    u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
    Requirement prioritizations in materials management
    u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
    u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
    Mass maintenance of outline agreements
    The following two transactions available:
    u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
    u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
    Commitment plan for purchase contracts
    u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
    u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
    u2022 This commitment plan itself can have any number of items.
    u2022 User can define a value and a validity date for each commitment plan item.
    u2022 This enables user to pre plan different values for different periods of time.
    u2022 The software generates an earmarked fund document for a defined commitment plan item.
    u2022 This earmarked funds document can in turn contain several different items with different account assignments.
    u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
    u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
    u2022 Account assignment to a different account assignment object is then no longer allowed.
    Availability check in "Enjoy purchase order and requisition"
    u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
    u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
    To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
    Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
    u2022 Two settings are possible with availability check:
    Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
    Delivery proposal - Full confirmation
    External services: putting service items in the purchase order on hold (changed)
    User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
    Customizing transactions OX18 replaced by view
    The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
    Goods receipt: new movement types in inventory management
    The following new movement types are available in inventory management:
    107: Goods receipt to valuated goods receipt blocked stock
    109: Goods receipt from valuated goods receipt blocked stock
    Prepayment of invoices
    This functionality is characterized as follows:
    u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
    u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
    u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
    u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
    u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
    u2022 When the software posts invoices, it continues to execute the standard checks.
    u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
    u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
    u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
    Purchasing accounting information to the former SAP Business Information Warehouse
    u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
    u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
    Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
    u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
    u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
    u2022 Functionality for report RMMR1MRS is enhanced.
    u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
    u2022 To do so, set the relevant indicator on the initial screen of the report.
    Parking service items
    It is now possible to put service orders without errors or with commitment errors on hold.
    Report MB5B : Stock on Posting Date
    u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
    u2022 This functionality is not available in Release 4.7.
    Stock Transfer Between Storage Locations
    u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
    u2022 As a result of which user can input issuing storage location with supplying plant.
    u2022 Facility of using different delivery types for different issuing storage locations is available.
    u2022 Shipping Point data can also be determined based on the issuing storage location
    Regards
    Priyanka.P
    AWARD IF HELPFULL

  • Functional Transaction Difference between SAP 4.7 and ECC 6.0 in Case of SD

    Hi,
    Experts can you Pls tell Transaction difference between SAP 4.7 and ECC 6.0 in case of SD module.
    Like VA05n is one transactional difference.
    regards,
    Rohan

    Refer below for the Transaction codes, You can find the functional differences in Release note or Solution browser > Apart from the functional Delta most of the reports are in ALV Grid disply and few changes you can note in Organizational Structure Assignment and consistency check , Document flow , Purchase Order Data tab  and Item Conditions so on
    VA05N List of Sales Orders
    VA25N Quotation  List
    VF05N Billing Document List
    VA45N List of Contracts
    OVX8N Check Report Organization Sales
    OVX3N Assign sales organization to company code
    OVXKN Assign distribution channel to sales organization
    OVXAN Assign division to sales organization
    OVXGN Set up sales area
    OVXMN Assign sales office to sales area
    OVXJN Assign sales group to sales office
    OVX6N Assign sales organization - distribution channel - plant

  • Delta functionality between SAP 4.7 and ECC 6

    Hi All,
    Can anyone please provide me with any documents or links on delta functionality between SAP 4.7 and ECC 6.0 in MM/WM.
    Any information would be helpful.
    Regards
    Prashant

    Hello
    Following are the basic differences as far as MM Module is concerned;
    Pickup list - Batch where-used list display in transaction MB56
    u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
    u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
    u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
    Usability enhancements for transaction MIGO for the posting of goods movements
    u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
    u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
    u2022 User changes the default values in the menu path "Settings -> Default Values."
    u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
    Goods receipt
    Goods issue
    Transfer posting
    Remove from storage
    u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
    New report : display list of invoice documents (MIR5)
    u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
    u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
    u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
    u2022 In the output list, the report shows both posted and held invoices.
    u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
    Requirement prioritizations in materials management
    u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
    u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
    Mass maintenance of outline agreements
    The following two transactions available:
    u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
    u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
    Commitment plan for purchase contracts
    u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
    u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
    u2022 This commitment plan itself can have any number of items.
    u2022 User can define a value and a validity date for each commitment plan item.
    u2022 This enables user to pre plan different values for different periods of time.
    u2022 The software generates an earmarked fund document for a defined commitment plan item.
    u2022 This earmarked funds document can in turn contain several different items with different account assignments.
    u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
    u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
    u2022 Account assignment to a different account assignment object is then no longer allowed.
    Availability check in "Enjoy purchase order and requisition"
    u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
    u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
    To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
    Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
    u2022 Two settings are possible with availability check:
    Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
    Delivery proposal - Full confirmation
    External services: putting service items in the purchase order on hold (changed)
    User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
    Customizing transactions OX18 replaced by view
    The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
    Goods receipt: new movement types in inventory management
    The following new movement types are available in inventory management:
    107: Goods receipt to valuated goods receipt blocked stock
    109: Goods receipt from valuated goods receipt blocked stock
    Prepayment of invoices
    This functionality is characterized as follows:
    u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
    u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
    u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
    u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
    u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
    u2022 When the software posts invoices, it continues to execute the standard checks.
    u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
    u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
    u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
    Purchasing accounting information to the former SAP Business Information Warehouse
    u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
    u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
    Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
    u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
    u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
    u2022 Functionality for report RMMR1MRS is enhanced.
    u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
    u2022 To do so, set the relevant indicator on the initial screen of the report.
    Parking service items
    It is now possible to put service orders without errors or with commitment errors on hold.
    Report MB5B : Stock on Posting Date
    u2022 This Report is available with "Non-Hierarchy" display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
    u2022 This functionality is not available in Release 4.7.
    Stock Transfer Between Storage Locations
    u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
    u2022 As a result of which user can input issuing storage location with supplying plant.
    u2022 Facility of using different delivery types for different issuing storage locations is available.
    u2022 Shipping Point data can also be determined based on the issuing storage location.
    If u want to know more go through the following links
    http://solutionbrowser.erp.sap.fmpmedia.com/
    http://help.sap.com/saphelperp2005vp/helpdata/en/43/6880cbb88f297ee10000000a422035/frameset.htm_
    https://wiki.sdn.sap.com/wiki/display/ERP6/ERP2005+Upgrade
    check following
    http://help.sap.com/bp_bblibrary/500/html/U40_EN_IN.htm
    for more help check following
    http://help.sap.com/bp_bblibrary/500/BBlibrary_start.htm
    Go through the following link for the Delta functionality notes
    http://solutionbrowser.erp.sap.fmpmedia.com/
    Regards
    Priyanka.P

  • What is the difference between version 4.7EE and ECC 5.0

    DEAR EXPERTS
    what is the difference between version 4.7EE and ECC 5.0?WHAT ARE THE ADDITIONAL FUNCTIONALTIES IN
    ECC 5.0?

    hi,
    Diff between 4.7 and ECC 5.0:
    1. 4.7 is on R/3 platform, while ECC 5.0 is on mySAP ERP 2004
    2. ECC 5.0 is having ESA(enterprise Serviceoriented Architecture)
    3.ECC 5.0 is web enabled with Netweaver technology.
    mySAP ERP is the "newer" ERP with numbering conventions like ECC (which stands for ERP Central Component) 5 or 6
    mySAP (aka mySAP.com) Business Suite contains Solutions like CRM, SCM etc. The important thing to note here is that this contains mySAP ERP, the one above
    mySAP All-in-One Solution is designed for smaller companies (the ad that says SAP is not just for large companies but for great companies where the above mentioned functionality is scaled down and is made to run on one database on a PC type of setup as opposed to the full blown architectures on which SAP traditionally set to run

  • RFC connection error between BW 3.5 and ECC 6.0

    Hi gurus,
    We've defined an RFC destination between BW 3.5 and ECC 6.0. Connection test  (SM59) is ok, but authorization one fails and ALEREMOTE users block. These users on both systems have good profiles. We look ST22 and find a runtime error on CALL_FUNCTION_REMOTE_ERROR. We've cleaned source system on BW and RFC destination and we've created one more time, but error doesn't disappear. We've looked OSS but don't find anything.
    Any idea? Is there any other place (users, RFC) where we have to change user password on system?
    Thanks a lot!
    Regards,
    Iván.
    Edited by: Iván Cabezas Castillo on Nov 6, 2009 12:09 PM

    Solved!
    This is because of the incompatibility of password handling between
    640 and 700 systems.
    We have to use a maximum 8 character long password with only capital letters (numbers are also allowed) for the user "ALEREMOTE".
    1. Change the password for the user in SAP R/3.
    2. Maintain the password in SAP BW for the RFC destination (transaction SM59 - Logon/Security tab)
    3. Authorization test is now successful.
    (SM59 - Test - Authorization).
    Regards!

Maybe you are looking for