Skip to Content
Overview: Product Masters can be replicated from OLTP R3 to SRM .This is a standard functionality available in the SAP. It is to be noted that only pre defined set of standard fields are replicated to SRM.Only fields that are defined in the structure of the BDoc type PRODUCT_MAT are replicated.   Customer enhancements are required in the download/upload context when customers have created additional data of their own, which needs to be transferred between the systems involved. This generally involves additional standard fields created in the material master, or fields and tables customers have defined themselves. It may also include operations, such as additional selection or filter conditions which cannot be defined with standard transactions. The document describing step-by-step procedure to accomplish the above is already available in the SAP website under the name “CRM Products: Customer Enhancements for Downloading and Uploading Product Master Data (Release 3.0)”. Limitations: The additional standard fields and customer defined fields do not get replicated from the OLTP R3 in the material create mode. This means that when a new material is created in R3 ,only the standard predefined fields available in the BDoc  PRODUCT_MAT will be replicated immediately.This is because the relational link is not established between the defined customer settypes and the product categories until the material is actually created in the SRM system.Hence the replication of these extra fields fail. The additional standard fields or the customer defined fields will be replicated only when the material undergoes a change process after its first create. Solution: There could be many solutions to this, but the simplest and easiest would be to trigger a material change process immediately after the material is created. This can be automated or manual.  If you choose to automate the process, you could schedule a job that runs a Abap program that constantly looks for any new materials created and immediately triggers a material change process using the standard function BAPI_MATERIAL_SAVEDATA.  There could be many other methods you can think of to trigger the change process ,but our main basic aim is to trigger a material change to ensure that all the desired fields are properly transferred to the SRM system. But again the frequency of the scheduled job depends on how soon you want the data to be replicated to SRM system. 
To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Stephen Johannes
    This issue has been solved from the CRM perspective:

    1.  Create a new product hierarchy/category to attach the custom attribute set.

    2.  In the user exit for the middleware on the CRM side: code the automatic assignment of the category to the product master.

    This works because when a product is created the “categories” are processed first.  A CRM product has no attributes upon first save.  The category determines the attribute sets that are available(include standard attributes).

    There is no need for an additional batch job, as the automatic assignment will allow for the maintenance of the additional attribute sets in create mode.  This solution has been available on the CRM side since version 3.0.

    (0) 

Leave a Reply