Dispute Case Key (Replicated) (0DPM_D10); what is meant by Replicated?

Hi everyone,
I am working on implementing FSCM Dispute Managment module. I have some questions regarding the new standard content provided by SAP for this:
Earlier I have seen clients using the Stanadard InfoSet 0DPM_I0 for all the Dispute's reporting as it combines data from AR, Dispute Case key and 0Customer. But now I am seeing a bunch of new objects like 0DPM_M10, 0DPM_M20, 0DPM_C10, 0DPM_D10, 0DPM_DCAS_10 etc. provided by SAP as standard content.
Does any one have any experience with this new content; can anyone explain me how this new content is useful. My client is reluctant against using the standard InfoSet as its is built on two DSO's; I have suggested to build a cube on top of them and can still use an InfoSet to combine AR line items, Disputes, Dispute case key and Customer. Correct me if I am wrong with thid statement.
Also please let me know what is meant by a Replicated DSO.
Any comments or suggestions will be greatly appreciated.
Thanks & Regards,
SRV

There are a few things to consider:
     1) The data is stored in deserialized form until it is read. The first read will deserialize the data.
     2) There is some overhead per-entry. 750MB/(3,000,000-30) = ~250 bytes per entry. Some portion of this is attributable to the per-entry overhead.
     3) How did you measure memory usage? Usually invoking <tt>System.gc()</tt> before measuring heap usage will clear garbage but is not guaranteed.
     Jon Purdy
     Oracle

Similar Messages

  • When using program RFDM3000/Automatic creation of dispute cases what is the difference with the option of Automatic incoming payment and Open items?

    We currently have a batch jobs running for each, automatic incoming payment and open items.  This was set up in the past and we are trying to determine what the difference is for each of these functions?  Do you need to have the automatic incoming run prior to the open items for residuals and payments on accounts?

    Hi Chris,
    Program RFDM3000 creates dispute cases for residual items arising during automatic incoming payments (account statement, lockbox), during check presentation, or in postprocessing.
    Alternatively, you can use the program to create dispute cases for open receivables items. You can use the selection criteria to restrict the quantity of open items (for example, using the document type and posting key for residual items from incoming payment postings).
    You will find more information in the link below
    http://help.sap.com/saphelp_erp2004/helpdata/en/0b/e07340b0c6980ae10000000a155106/content.htm
    Regards,
    Jose

  • What is meant by costing key?

    Dear Experts ,
                          while releasing the billing document to accounts , i am getting  error like
                Valuation with material cost estimate: error, The system looked for the material cost estimate using costing key "002", as defined in the Customizing settings for CO-PA,  incomplete due to FI/CO interface
    what is meant by costing key?
    regards
    rajakarthik

    Hi,
    In Costing based Profitability analysis you define costing keys. A costing key is a set of access parameters which are used in valuation to determine which data in Product cost planning should be read. In the costing key you attach the costing variant.
    In the costing key you specify whether the system should read the current standard cost estimate, the previous standard cost estimate or the future standard cost estimate or a saved cost estimate.
    The configuration settings to determine this costing key is as follows:
    Assign costing keys to the products u2013 Three costing keys can be attached to a single product for a specific point of valuation, record type, plan version.
    Assign costing keys to Material types
    Assign costing keys to any characteristics u2013 You can use your own strategy to determine the costing keys. This is through user defined assignment tables.
    regards,
    Santosh kumar

  • Dispute Case - Linked Objects- Various- URL

    Hello,
    We have a requirement to create a Dispute Case through a custom interface program. We have been doing this using BAPI_DISPUTE_CREATE.
    Now, I need to programmatically link a URL to Dispute Case -> Linked Objects->Various->URL. An custom element type for u2018URLu2019 was configured in the Registry for this in our SAP system.
    This is usually achieved programatically using the tables parameter OBJECTS of the BAPI. We have to pass the OBJ TYPE & KEY to this parameter.
    Since configuration does not allow the BOR_TYPE to be defined on tab u2018Connection Parametersu2019 of the Element Type URL in the Registry, what OBJTYPE and KEY works for this?
    Thanks,
    Smitha/Aneel

    Hello Andy,
    I have a question. We're also trying to use BAPI_DISPUTE_CREATE in order to create dispute cases, but the function needs a unique GUID number in order to create the dispute case. How did you manage to maintain this guid number?
    Because of this problem, we started using the function UDM_DC_CREATE, which generates a GUID itself, if you do not maintain one.
    Sorry for the inconveince, the problem was because of a wrong attribute, I can create a dispute case with this function without maintaining the guid id.
    Edited by: Karabiber Kerem on May 21, 2010 11:03 AM

  • What is meant by change pointer and change request

    hi,
    what is meant by change pointer and change request in sap r3
    plz can u any one notes or link on this , or if possible briefly tell about this..
    i am looking for clear idea on this..
    thanks
    Ruban

    With respect to Dictionary Change pointers means all the changes done to dictionary objects.
    All the change logs with respect to tables are stored in CDHDR and CDPOS table
    Change Pointers in broad sense are used with respect to IDOC
    Change Pointers & Reduction of IDOCs.
    Applications, which write change documents, will also try to write change
    pointers for ALE operations. These are log entries to remember all modified
    data records relevant for ALE.
    Following Steps must be followed in case of Change Pointer.
    1) Goto Transaction BD60.
    Note down the Details of the Message Type for which change pointer has to activate. Details like Function Module, Classification Object, ALE object Type etc.
    E.g. ZDEBP3
    2) Next step is goto transaction BD53
    Click on change button.
    First select the segment for which the fields has to modified (either remove or
    add ).
    It will show the fields in a pop-up window where the user can select, deselect the respective fields.
    Save the settings for the Message type. Don’t forget to activate the change pointers by clicking Activate Change pointers button on the main screen.
    3) Once the activation is done system will reset the settings for the Message type in Change pointers (BD60). Maintained the old settings for the Message type.
    Check this FAQ
    . Do you really need change pointers?
    You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
    You can deactivate change pointers and activate them again with the transaction BD61.
    2. Do you really need to activate change pointers for this messages type?
    If some messages types are no longer to be distributed by change pointers, you can deactivate change pointers for this messages type.
    You can deactivate change pointers for the message type
    and reactivate them again.
    For reduced message types, deactivate the change pointer with the
    Reduction tool (transaction BD53).
    3. Are there still too many change pointers to be processed?
    The change pointers are analyzed with the transaction BD21 or the report RBDMIDOC in ALE and flagged as processed. If the change pointers are created periodically, this report should also run periodically.
    4. Are no longer required change pointers reorganized in time?
    The report RBDCPCLR (transaction BD22) to reorganize the change pointer should run periodically. Depending on how many change pointers are created or processed, you can schedule the background job hourly, daily or weekly. You should delete all obsolete and processed change pointers. You can also use this report for specified message types.
    We come across change pointer technique while dealing with master data distribution thru ALE/IDOCs
    When we want to reflect changes made to master data(i.e customer master, vendor master, material master ...) visible to other clients listed in customer distribution model, we follow change pointer technique.
    What is customer distribution model?
    A customer model depicts various messages (master data, transactional data) exchanged between the systems and establishes a sender and receiver of data
    A customer model is always maintained on any system for the entire distributed network of SAP systems, so it must be distributed to various systems in the distributed network.
    These r some details regarding change pointer technique which u may find it usefull.............
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master, vendor master & sales orders. changes made to a document are recorded in the change document header table CHDHR, and additional change pointers are written in the BDCP table for changes relevant to ALE. BDCPS table stores the status of changed documents processed or not.
    The process for distributing master data using change pointers involves the following steps.
    The application writes change documents. SAP maintains change documents for
    several objects in the system, such as materials, customers, invoices, and bank data, to provide an audit trail for changes made to an object. A change document object represents a set of tables for which changes are recorded. For example, the change document for the material master is named MATERIAL and it contains the various tables of the material master object, such as MARA and MARC.
    When an application transaction makes changes to an object, the application writes change documents, which are stored in the CDHDR and CDPOS tables for each change made to an object.
    Tip
    Execute transaction SCDO to see a list of change document objects and
    their tables.
    The SMD (Shared Master Data) tool writes change pointers. When changes are made to an object, the SMD tool checks the ALE settings and consults the ALE distribution model to determine whether a receiver is interested in the object that was changed. If the system finds an appropriate receiver, the system creates change pointers in the BDCP table that point to change documents in the CDHDR table.
    The ALE programs analyze change pointers and generate IDocs. SAP provides
    standard function modules that read the change pointer table and generate IDocs for the objects that were changed. These programs are designed to ignore multiple changes and create only one IDoc. For example, if a material is changed four times before the function module is invoked, only one IDoc with the latest data from the material master data is created. The function modules are invoked by a standard report, RBDMIDOC. The selection parameters of this report allow you to specify the message type for which change pointers are to be analyzed. Configuration
    you must carry out the following configuration steps to enable master data
    distribution based on changes to the object.
    Step 1: Enable Change Pointers Globally
    Transaction: BD61
    This option enables the change pointer process globally. Make sure that the flag is checked.
    Step 2 :Enable Change Pointers for a Message Type
    Transaction: BD50
    This setting is required for activating change pointers for a specific message type.
    make sure that the Active flag is checked for your message type.
    Step 3 :Specify the Fields for Which Change Pointers Are to Be Written
    Transaction: BD52
    For standard master data objects such as the material, customer, and vendor objects, SAP already provides a list of fields for which change pointers are written. If you are satisfied with the standard set of fields, you can skip this step. If you want to add new fields, you must add entries for the required fields. If you are not interested in IDocs being generated for changes to a particular field, you can remove it from the list. For example, if you do not want to distribute the
    material master for changes made to the Catalog Profile (RBNRM) field, you can delete this entry from the table.
    Step 4: Changing a Field in the Master Data
    Change a field in the master data object for which the change pointer is enabled. For example, if you change the net weight of a material in the material master data, a change pointer is written.
    Tip : You can verify a change document and change pointer by viewing entries in
    tables CDHDR and BDCP, respectively.
    Step 5 :Executing Program RBDMIDOC to Process Change Pointers
    Execute program RBDMIDOC to initiate the process of generating an IDoc. On the selection screen, specify the message type. For example, you can specify MATMAS. After you execute the process, it displays the number of entries processed.
    Note :
    Normally, you schedule this program to run frequently and start IDoc
    generation for different message types.
    Step 6 : View the idocs in WE02/05

  • Diff: Linkage of Credit memo and Dispute Case in EHP 4 and EHP5

    Hi Experts
    I am bit confused ...on the Linkage of Credit memo and Dispute Case in EHP 4 and EHP5.
    Does the following statement is valid in EHP4 or EHP5.
    "You can add a credit to a dispute to close it or reduce the amount disputed."
    If it is possible in EHP 5 or EHP 4, please let me know what is the procedure to follow?
    If i need to activate anything in SFW5, please provide what is the Business function i need to activate.
    Thanks in Advance.
    Regards,
    Meenkashi.N

    Linking a credit note has nothing to do with EHP4 or 5. You have to do a config sertting:
    Dispute Management-Process Integration with Accounts Receivable Accounting-Assignment of Open Credits and Payments-Activate Assignment of Open Credits and Payments
    And make sure the business adapts the correct process:  When you reverse a charge on a debit invoice you have to make sure the credit is properly linked to the debit note.
    If this is the case then the credit will show up in the dispute case.
    Rgds,
    Richard

  • Error in creating Dispute case

    Hello Experts,
    i got this error in su53
    Evaluation of Last Failed Authorization Check of User KHPSAROM
    Description                                                                                Authorization values
    User Name                      KHPSAROM     Authorization Object                     CPE_SETTIN
    System                         FCP          Client                                   400
    Date                           15.10.2010   Time                                     13:34:30
    Instnce                        fghsrv014    Profile Parameter auth/new buffering     4
        Authorization check failed
       Object Class AAAB Cross-application Authorization Objects
         Authorization Obj. CPE_SETTIN Commodity Pricing Engine: General Settings
           Authorization Field ACTVT Activity
                                                                                    03
       User's Authorization Data KHPSAROM
       Object Class AAAB       Cross-application Authorization Objects
         Authorization Object CPE_SETTIN Commodity Pricing Engine: General Settings
           Authorizat. T-FD96017500 Commodity Pricing Engine: General Settings
             Profl. T-FD960175   Profile for role Z:ROLE_AR_ARACC
             Role Z:ROLE_AR_ARACC
             Authorization Field ACTVT Activity
                                                                                    03
    User cannot create dispute case
    try to solve it
    Thanks and regards
    Dhaval Thaker

    To disspell any doubts, SU53 shows the last failed auth check which the user invoked in a program, immediately before executing Su53. It is not necessarily the correct one to assign!
    Melissa Salamone wrote:
    > And this is way out from left field but I actually had this happen to me a week or two ago - double check the role and make sure that authorization is actually there. I had one pop where it showed an authorization that was an old version of the role but not in the current version.
    >
    I assume by this that you are referring to profile name collisions. This has two common causes:
    The SID ID's of PROD, QAS and DEV etc systems all have the same identical characters in the 1st and the 3rd place. Only these two are used in the generation of the profile name. Search for "AGR_NUM_2" for more infos and options.
    Another (IMO more likely possibility) is that which SAP Note 1373111 describes in the reason codes of the FOR USER construct. The check might infact have been performed against a different user ID...
    Please run the same with an ST01 trace on and check the reason code (if your kernel release is high enough).
    Personally I am rather sceptical about this new mechanism in the wild. The old mechanism via FM AUTHORITY_CHECK at least gave us a where-usd-list and when jumping from the trace to the source it was clear what the developer had intended to do, even if they have already left the building...
    Cheers,
    Julius

  • Dispute case ID no longer in cleared document visible

    Hi,
    we have voided a dispute case.
    Now, when I go back into document display or through FBL5n I have no longer visibility of the case. How can that be?
    The disputed FI document has been cleared. And the FI document is still visible as linked document in the case.
    for reporting reasons and account overview I would need to see this.
    What can I do?
    Thanks + Regards
    Hein

    Are you saying you disputed an item.
    Then you voided it
    Then the item was cleared
    If that is the case I believe everything is fine.
    You will always be able to see a voided dispute - you can use the status to remove it from reporting
    By voiding the item - the AR data will no longer link back to the dispute. This allows the AR item to be disputed again.
    Hope this helps

  • Dispute Case attachments: CMS, DMS, RMS, ArchiveLink... Confused!

    Hi,
    We're starting to implement SAP Collections & Dispute Mgmt. One of the things that excited our business users on the SAP solution was the ability to attach unlimited (word, pdf, jpg, email, etc) files directly to the Dispute case. However, we have a large volume of disputes and estimate to wish to attach an annual total of ~500,000 files, ~200Gb directly to Dispute cases.
    But I'm confused as to the options we have in doing this and the potential pros/cons related to those options. From the documentation I have found, I see references to SAP DMS (Document Management System), SAP CMS (Content Management System), SAP RMS (Records Management System), SAP ArchiveLink, and also SAP integration "3rd party DMS solutions" (whatever those are...)
    Is SAP CMS & SAP RMS the same thing?
    Has anyone implemented a 3rd party DMS solution? If so, what were the benefits of this over the SAP solutions?
    Has anyone else implemented Disputes with a large volume of attachements?
    Many thanks in advance for those of you with knowledge & experience in this area,
    JJ
    Edited by: James Parkes on Oct 18, 2011 4:13 AM

    Hi,
    DisP.Mgt uses RMS as base so when you link objects in UDM_DISPUTE then you already using RMS. Archivelink & CMS are connected to RMS so if you create an archivelink document in UDM_DISPUTE, you would be creating an archivelink document in ARL already.CMS is in the base for managing content. This is done for all RMS objects & would already be set up. What is means is that if you store say a archivelink documetn then meta data is stored in sap DB but content sits in content server. This content server can be SAP own or 3rd-party. Same goes for RMS objects like cases, records, editable documents.
    Best Regards,
    Pragya

  • Dispute Cases on partial Payments

    Hi
    How to create Dispute cases for partial payments?
    I have an invoice. A payment comes and its partial. We dont set up residuals. So on the invoice it says partially paid for some amount. And we want the job to create the dispute for the remaining amount.
    Do i need to define anything new in case record model for this?
    Thanks for help.

    I have an invoice for 1000. No dispute case is created till now.
    I made a pyment for it for 500.
    And now If I run FDM_AUTO_CREATE what is my selection criteria to select this invoice for dispute case creation.
    We want to schedule a job everyday to pick up all invoices that are partial paid and we want to create cases for them.
    Can it be done in FDM_SUTO_CREATE?
    If it can be done then how the program knows which invoices has partial payments and how does it change the disputed amount to invoice amount minus partial payment?
    I know how to do it manually by selecting both debit and credit item in FBL5N to create the case.
    I also know that when case is created and if a payment is made partially it reflects the case disputed amount.
    I just want to know if FDM_AUTO_CREATE can be used to to create cases on invoices that are partially paid.
    If it can then how?
    Thanks,

  • Dispute Case - Write off multiple cost centers

    Hi Experts,
    I have a different requirement on automatic writing off of dispute cases. There is one collection specialist who handles multiple location customers. Each location/branch is created as profit center and in each location/branch there are many customers. So if there is a dispute case which needs to be written off for Customer A in Location A, the cost center needs to be A which belongs to Location A, similarly for other locations too, where ever the customers belongs to it needs to written off to that partcular location cost center.
    In settings of automatic write

    sorry experts, fat fingure, accidentally pressed the enter key, here is the continuation of the message.
    In customizing for automatic write off, i dont have the option except by person responsible and cost center. Location/branch is also equal to sales office which is assigned to the customer master.
    Is there a way we can address this requirement, could you guide which direction i need to move.
    Thanks in advance
    Best Regards,
    Jen

  • Closing dispute case

    Hi Gurus,
    i am currently working on a custom program for closing the dispute case.can anyone suggest me what is the criteria to get the resolved dispute cases to be closed.
    Thanks.

    see this:
    http://esoadocu.sap.com/socoview(bD1lbiZjPTgwMCZkPW1pbg==)/render.asp?packageid=DBBB6D8AA3B382F191E0000F20F64781&id=95E135C04B5011D487540000E81D646F

  • Dispute Case - Paid amount shown in 'Cleared Manually' field

    Hi
    I am configuring dispute mnagement. When I pay an invoice using standard incoming payments transaction F-28, then the dispute case status changes to CLOSE, but the amount paid is being shown in the 'Cleared Manually' field rather than 'Paid' field. What is the cause of this issue and how can this be fixed?
    Thanks

    I used case record model UDM_DISPUTE as a copy template. It had following structure nodes: Business partner, Disputed objects;Resolved objects;Items assigned during clearing; Other objects;and Various.
    Now, amongst these I cannot see anything which says 'Paid' and Cleared Manually' . Could you elaborate which values would have been copied incorrectly in your opinion?I am testing a full payment scenario and not Residual or Partial payment.

  • Dispute Case- workflow

    Hi we want to send email to occasional processor using workflow about dispute case. Please tell the setting.
    I have already activated event linkage for work flow. Do I need to also check the process route check mark in case type configuration. Please guide through the key steps.
    Thanks

    Hi Nik,
    Are you activating the event linkage for workflow WS01700044? If yes, the workflow should be trigger when you create or change the dispute case.
    For the processor that need to receive the email when the dispute case created, the processor user id should not be maintain in the Regular Processor table.
    Another thing that you need to check is SWU3->Maintain Additional Settings and Services->Maintain Standard Domain for Internet Mail, is setup correctly, else the workflow not able to send email to user's outlook.
    Hope this help.
    Regards,
    Edison Wang

  • Dispute Case - Write-off entry

    Dear Experts,
    When we write off any invoice through UDM_AUTOWRITEOFF in FSCM, system Debits the Bad debts write off (P&L) A/c and Credits the Customer A/c. However, we want system to segregate VAT, Tax and Freight amount from Bad debts write off A/c. So that the entry would be VAT -Dr. Tax-Dr. Freight -Dr. Bad debts -Dr. and Customer -Cr. Please could you through some light on How to achieve this?
    Thank you.
    With Kind Regards,
    Naresh B. Pandya

    HI Naresh,
    To my understanding there is no configuration in FSCM by which you can achieve what you have stated, since we want to achieve something in FI area by doing an acitivity in FSCM, whereas vice-versa would probably work. I can possibly think of a work around. You can post a normal write-off entry giving the tax code therein, which will clear customer open item, and post to tax GL as well. Now, since the open item (document) which was "disputed object" in FSCM - Dispute case, that object will get updated with resolved object as the new document posted. Basically, the dispute case attribute will reflect the changes that has occurred in FI (FI-FSCM integration). However, I'm not sure whether this amount will get updated in field "paid amount" or "written off" amount. You can simulate and check out.
    I am also interested to know how you deal with this, so keep me posted.
    regards,
    TV.

Maybe you are looking for