unable to find SAP object type BUS2032 from content server

David Weichieh
David Weichieh Member
in Extended ECM #1

SAP object type BUS2032 has been configured on SAP (SPRO - xECM). Workspace type Sales document also been configured on the content server, However, Ima not able to find the BUS2032 during business object type configuration on the conten server.

Comments

  • David Weichieh
    David Weichieh Member
    #2
    can see old business object types.docx

    Please see the attached screen shot. BUS2032 has been defined on SAP (xECM spro).

  • appuq
    appuq Member
    edited July 30 #3

    I feel as if something is not done correctly in SAP. You should go to connections and make sure this CS is talking to SAP connection test should yield result. The same needs to happen from SAP side as well. If you look at your screen where the BUS2032 entry is there should be a popup screen that should talk to SAP. The content server you are testing should have a log file called ECMlink.log this can indicate communication from CS to SAP. Watch the screencap I show which lists all configured objects that I can use in my CS to model SAP BOs

    In fact, if this is a first-time setup there's a whole nine yards in SAP, there's about 2 or 3 yards in OTDS and a whole 9 yards in OTCS.If OTCS, SAP and OTDS cannot talk to each other then no dice.In SAP there is a checklist application with traffic lights and you have to get green on all of them.

    image.png

  • David Weichieh
    David Weichieh Member
    #4

    Thanks for your response. Connection is fine for both SAP and CS. I configure BUS2032 in "Business Object Declaration (SPRO -XECM)". What else do I need to define the object type?

    Also, I use the generic provider "/OTX/RM_GEN_PP_CL_BO". Anything I miss?

  • appuq
    appuq Member
    edited July 30 #5

    in CS I do it in this fashion. one has to follow the XECM guide to the letter.

    1. Create Classification
    2. Create Category
    3. Create Workspace Type
    4. Create template
    5. Put classification and category on that
    6. Create a folder and match the classification.
    7. Create BO Type if SAP configuration is correct on that screen Business Property will come as type ahead and you map it to the corresponding category. This part will only work if SAP BPP is sending those so it serves as a check.
    8. If everything is mapped I go to the folder and say add BO and if the config is correct the correct template should be visible and it should be creatable from OTCS.(this can vary as SAP has concepts of early workspace etc)
    9. Send SAP transaction or send SOAPUI create or update workspace call mimicking sap code.

  • David Weichieh
    David Weichieh Member
    #6

    Hi Appuq,

    MDG solution accelerator has been installed; and it's working fine.

    I need to create a new workspace for sales documents. Is BUS2032 correct business object for the sales document?

    I have followed the steps (you mentioned), but I still received "BUS2032 has not been found as a valid business object type on S40". We had installed MDG

    The connection between SAP and the content server is working fine. I can see all the existing business types (from the

    BUS2032 issue.docx

    MDG solution accelerator) from content server. Please see the attached.

  • David Weichieh
    David Weichieh Member
    #7

    By the way. I used the generic property provider "/OTX/RM_GEN_PP_CL_BO".

  • appuq
    appuq Member
    edited August 2 #8

    Please take it up with either CS Support or SAP support.BTW as I said try to look in the file ECMlink.log when you receive the error you will see OTCS Oscript reaching out to SAP and returning success or failures. What you see in the GUI is often a programmer's translation of what it means.

    The idea behind XECM is the leading application like SAP, Maximo is responsible for sending metadata to CS as Business Property, this is why they call it Business Property Provider(BPP). If that is not done correctly it will fail. In the case of SAP one is writing ABAP4 code. I have no idea how that looks but most likely if OT is saying the end customer is (I am assuming you are an end customer and not a consultant) able to do this all by themselves that is why I suggested using support.

    You may want to check your SAP connection our demo system talks to SAP S4 HANA using the Default web service adapter and when I look at BUS2032 I see metadata available for me to map which means the ABAP code is doing what it is supposed to do. I am not a SAP programmer. If the ABAP code is correct when you go to the Business properties at least OBJKEY, and OBJTYPE should come through the rest is whatever is in the SAP DD.

    See page 216 https://www.opentext.com/file_source/OpenText/en_US/PDF/OpenText_Extended_ECM_for_SAP_Solutions_10_-_eBook.pdf

  • bpawanchand
    bpawanchand Member
    #9

    Hello @David Weichieh ,

    I am new to open text and we have a similar situation what you might have already gone through in integrating SAP MDG with open text. Currently, we have implemented SAP MDG and we have open text in place . However the documents which we upload in SAP MDG application be it Material or Supplier or customer currently it is referring to the DMS configurations. However we are looking to replace this with Open text. Can you help us with any reference document about how to integrate a SAP MDG application for materials or suppliers to have the links or documents loaded into Open text.

    IT would be of great help if you can guide us.

    Thanks

    Pavan

Categories

image
OpenText CE Products
Extended ECM
Docs & APIs