Skip to Content
avatar image
Former Member

How do I speed up mass Material Plant extension?


I am mass extending materials to plant through bapi 'BAPI_MATERIAL_SAVEREPLICA'. We are expecting ~1.7 million records in table marc. I split the load up into 4 seperate processes, and, as it is going now, looks like it will take about 2 - 3 days to complete the load. This is a lot slower than is desirable when we load into production. Does anyone have an idea as to how to make this faster? I was thinking that perhaps we could deactivate some of the data validations. Are there some more performance heavy validations in particular that we could deactivate?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Aug 08, 2017 at 07:55 AM

    The quickest way to load material master is direct input method, but this would require that you change your load programs which is probably not really efficient and may take longer as it also needs some time and you would add extra development time.

    Switching off validations and ending with incorrect data is not really gaining you any time, contrary you would even need more time to fix the issue.

    How can material master extension be really critical in time? It is done days, often weeks ahead of a go live, a inventory load is critical, as it happens in the very short time frame between finishing work in the legacy system and starting again in the new system.

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 08, 2017 at 07:46 AM

    I feel some information is lacking :

    • Have you done a Trace on which actions take up the Bulk of the Performance Drain? What were the Results / Tables / Function or Perform-Routines taking up way too much time ...?
    • Are you using the BAPI in a Custom Program?
    • Are you using the BAPI in LSMW?
    • What actions have you performed to speed up the process? Does your BAPI_COMMIT have a "WAIT" statement? Have you thought about Parallel Processing? Are you FREE-ing up your Internal BAPI-tables at each new run in a LOOP?
    • Have you checked missing SAP-KBA's on Performance in the BAPI, there are some new KBA's on this (Check "SAP ONE Support" with "BAPI_MATERIAL_SAVEREPLICA" or FM "MATERIAL_MAINTAIN_DARK")

    Your statement on "we could deactivate some of the data validations" ... What do you mean by that? Does your program do additional 'heavy lifting' validating data that is potentially already handled in the BAPI?

    Please update so we can advise in a better way ...

    Add comment
    10|10000 characters needed characters exceeded