Skip to Content
author's profile photo Former Member
Former Member

extend filter criterias in: MDS_LOAD_COCKPIT

Hello experts,

I'm using mds_load_cockpit for massdata replication in one-client scenario (SRM@ERP) - replication tests were successful (vendors and materials). Now I'd like to use filter criterias to get the desired vendors and material ranges because I'dont want all vendors or materials to be replicated.

My first step was using the listed filters (listed as "fieldnames") in mds_load_cockpit.

But there are only a few fields available which set the criterias:

-Vendors: Account Group, VendorID, Centr.Del Flag

-Materials: DF at client level,, mat.ID, mat.type

These don't fit my filter requests...

Is there there any way to extend these criterias?

For example like in transaction R3AC1 (which i cannot use in one-client-scenario) for "r/3 material master".

I'd like to use this for materials--> Table: MARA-MAGRV

For vendors i'd like to make a limitation on purchsing org, but I dont know how to do this.

Any suggestions how to proceed? Maybe there is a table where I can maintain/create new entries for my own crits listed as "Filedname" in mds_load_cockpit for filtering.

Could anyone give me a hint?

BR, Patrick

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Aug 19, 2010 at 07:11 AM


    solution in my case was to extend table MDSV_SYNC_ID_FL

    e.g. with new entry for: MARA-MAGRV

    afterwards it is possible to use this predefined criteria in MDS_LOAD_COCKPIT

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member


      i have a big problem during using mds_load_cockpit

      when i click on product category->material group and un select backround proccess and execute the transaction i have terminated in program

      Category ABAP Programming Error
      Runtime Errors MESSAGE_TYPE_X
      Application Component AP-MD-BF-SYN
      Date and Time 10.06.2014 09:39:47

      Short text
      The current application triggered a termination with a short dump.

      What happened?
      The current application program detected a situation which really
      should not occur. Therefore, a termination with a short dump was
      triggered on purpose by the key word MESSAGE (type X).

      Error analysis
      Short text of error message:

      Long text of error message:

      Technical information about the message:
      Message class....... "MSI_PRODCAT_CUST"
      Number.............. 303
      Variable 1.......... 1
      Variable 2.......... 432339
      Variable 3.......... " "
      Variable 4.......... " "

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.