MDIS not pick the files in ready archive

[Former Member]

Hi Masters.

I have a problem with MDIS. is not download automatically the files in ready directories.

we was upgrade MDM 5.0 to MDM 7.1  before its working ok. but in new version no working any more.

MDIS and MDD is running status.

file is xml format

User Admin and password is correct we changes since console MDM

Port is automatic in MDM console

Port is status Has Data

no logs erros reported on MDIS logs in auxiliar Server

no errors or exceptions  in structureX or valueX or ImportX files. 

MDIS.ini  has the root distribution a new path

Distribution Root Dir=/usr/sap/MDD/MDS03/mdm/distributions  

and ftp is put the next path /usr/sap/MDD/MDS03/mdm/distributions/MDD_ORCL/DEV_CATALOGO/Inbound/ERP/_MDMContractDataTransmission_ProductID/Ready

could you please.

[Former Member · Accepted solution]

Oscar,

As per the given screenshot, Port (ERP Contract Data Transmission) is blocked with some Structural exception. In your screenshot, the second last property Block on Structural Exception of port ERP Contract Data Transmission is Yes that's why it is not processing any file.

As a solution, you have to navigate to Structural Exception folder, which will present under Exception folder of  ERP Contract Data Transmission port folder.

• Delete all the files, which exists in any of the exception folder (Import/Structural/Value).
• Refresh the port table, now Block on Structural Exception property of the selected port will be No.

Note: Always copy/keep all the exceptions files before deleting them, until you could find the problem.

Hope, it will solve your problem.

Thx/ -Tarun

[Former Member · Accepted solution]

Hi Tarun,

If i am not wrong, above screenshot shows that data is there in the ready folder.

It is not showing that port is blocked on structural exception.

Block on Structural Exception is just a property in MDM Console which will decide if Port needs to be blocked on Structural exception or not. If it is Yes, then Port will be blocked in case structural exception occurs. If it is No, then port will not be blocked and further processing will continue even if Structural Exception appears. I might be wrong, but please check once from your end as well.

Thank you.

[Former Member · Accepted solution]

thanks tarun.

but not exceptions on structural file neither Values and not blocked port the status is has data. just only not pick the file xml format and not show logs about errors.

any other idea how fix the problem.

[Former Member · Accepted solution]

Oscar,

Try the followings:

1. Are you facing this problem with All the Ports? If yes, you might need to change Import Server password, as suggested in other posts.
   
   
2. Check, if you have multiple port folders for 'ERP Contract Data Transmission' port in distribution folder under MDM Server directory. If yes, then please delete the old one from distribution folder and restart repository.

Thx/ -Tarun

[Former Member · Accepted solution]

Hi tarum thanks for you support.

today made test on other ports example _Lt_currencies it MDIS take correctly so  MDIS is not the problem is working ok.

I think is important mention the interface _MDMContractDataTransmission standar suffered some changes had to add several more fields to the standard. I previously generated manually mapping named xmlCatalogmap for the new interface and load the test . the mapping is setting in port on MDM console.

1.- On Import manager I did mapping on MDM system . maybe is necessary make to ERP ?

2.-  XML schema will be change because has a many fields add

3.- XML schema come PI interface on WSLD but it is on my lap top  how import this xml schema on mdm server.

schema come PI but in my local drive.

[Former Member · Accepted solution]

Hi Oscar,

I would request you to go for repository reload once and check if it solves your problem.

Even if the schema is incorrect, then this file should move to exception folder.

You can try one thing, copy this file and paste it in some non-production environment and see if it moves ahead of Ready folder or not. Please check and share your observations.

Thank you.

[Former Member · Accepted solution]

Oscar,

1. As suggested, could you restart your repository, it might solve your problem.
2. Are you facing this problem in Production environment?
3. Could you share the Ready folder path, where you are placing the files?

Thx/ -Tarun

[Former Member · Accepted solution]

Hi Ankush. thanks. for your help.

I was reload reposiroty and the same results no.I think is the mapping or xml schema because make other test with Lt_currencie interface and MDIS take the file and move to archive .  

I have question the system remote will be ERP because the mapping was made to MDM do you think maybe is the problem .

thanks a lot

[Former Member · Accepted solution]

thanks tarum.

1.- I restart repository and the situation is the same .  maybe exist problem on mapping or xml schema because the interface is really new.

2,. the problem is not in Production enviroment . is on quallity environment

this is my xml scheme  could you check if is correct

<?xml version="1.0" encoding="ISO-8859-1"?>

<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p2="http://sap.com/xi/SAPGlobal/Global" xmlns:p1="urn:holcim.com:srm_mdm_catalogo" name="CatalogueUpdateNotification_Out" targetNamespace="urn:holcim.com:srm_mdm_catalogo">
<wsdl:documentation>
A notification about a new, changed or updated catalog
</wsdl:documentation>
<wsdl:types>
  <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:p0="urn:holcim.com:srm_mdm_catalogo" xmlns="http://sap.com/xi/SAPGlobal/Global" targetNamespace="http://sap.com/xi/SAPGlobal/Global">
   <xsd:import namespace="urn:holcim.com:srm_mdm_catalogo" />
   <xsd:element name="CatalogueUpdateNotification" type="p0:DT_Catalogue_Laser_table" />
  </xsd:schema>
  <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:holcim.com:srm_mdm_catalogo" targetNamespace="urn:holcim.com:srm_mdm_catalogo">
   <xsd:complexType name="DT_Catalogue_Laser">
    <xsd:annotation>
     <xsd:appinfo source="http://sap.com/xi/TextID">
     b85eefd95f1a11e2863b001a6447bfda
     </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
     <xsd:element name="Pais" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efa0842f4411e2bcfa54cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Sociedad" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8d62f4411e2c4d254cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Centro" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8d72f4411e2ba1654cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Nombre_proveedor" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8d82f4411e2baae54cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Nombre_catalogo" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8d92f4411e2ca6f54cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Nombre_pieza_proveedor" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8da2f4411e2aacf54cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Descripcion_breve" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8db2f4411e28b5854cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Grupo_productos" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8dc2f4411e2920954cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="No_producto" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8dd2f4411e287f654cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Clase_valoracion" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8de2f4411e28cbe54cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Categoria" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8df2f4411e2c01554cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Precio_contrato" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e02f4411e2a44e54cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Importe" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e12f4411e2b41b54cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Moneda" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e22f4411e2b05d54cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Cantidad_base" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e32f4411e28a6154cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="UM_Cantidad_base" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e42f4411e2be9954cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Criterios_busq_esp" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e52f4411e2826754cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Fabricante_externo" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e62f4411e285b754cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Plazo_entrega" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e72f4411e2891854cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Unidad_medida" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e82f4411e2ac7854cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Unidad_pedido" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8e92f4411e2929154cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Imagen" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8ea2f4411e2adc154cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Periodo_validez" type="xsd:date" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8eb2f4411e2a54854cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Cond_pago" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8ec2f4411e2a52054cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Status_posicion" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8ed2f4411e28d5854cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
     <xsd:element name="Texto_Explicativo" type="xsd:string" minOccurs="0">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       48efd8ee2f4411e28c1454cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
    </xsd:sequence>
   </xsd:complexType>
   <xsd:complexType name="DT_Catalogue_Laser_table">
    <xsd:annotation>
     <xsd:appinfo source="http://sap.com/xi/TextID">
     b85b8fcd5f1a11e2a5d6001a6447bfda
     </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
     <xsd:element name="Catalog_items" type="DT_Catalogue_Laser" maxOccurs="unbounded">
      <xsd:annotation>
       <xsd:appinfo source="http://sap.com/xi/TextID">
       92628a9f2ffc11e2a45754cac679310d
       </xsd:appinfo>
      </xsd:annotation>
     </xsd:element>
    </xsd:sequence>
   </xsd:complexType>
  </xsd:schema>
</wsdl:types>
<wsdl:message name="CatalogueUpdateNotification">
  <wsdl:documentation>
  A CatalogueUpdateNotification is the notification about a new, changed or deleted Catalog by a Catalog provider to an interested party.
  </wsdl:documentation>
  <wsdl:part name="CatalogueUpdateNotification" element="p2:CatalogueUpdateNotification" />
</wsdl:message>
<wsdl:portType name="CatalogueUpdateNotification_Out">
  <wsdl:operation name="CatalogueUpdateNotification_Out">
   <wsdl:output message="p1:CatalogueUpdateNotification" />
  </wsdl:operation>
</wsdl:portType>
<ifr:properties xmlns:ifr="urn:com-sap:ifr:v2:wsdl">
  <ifr:category>
  ifmmessif
  </ifr:category>
  <ifr:methods>
   <ifr:method name="CatalogueUpdateNotification_Out">
    <ifr:isSynchron>
    false
    </ifr:isSynchron>
    <ifr:isInbound>
    false
    </ifr:isInbound>
    <ifr:interfaceCategory>
    outbound
    </ifr:interfaceCategory>
   </ifr:method>
  </ifr:methods>
  <ifr:messages>
   <ifr:message name="CatalogueUpdateNotification">
    <ifr:messType>
    ifmmessage
    </ifr:messType>
    <ifr:technicalNamespace>
    urn:holcim.com:srm_mdm_catalogo
    </ifr:technicalNamespace>
   </ifr:message>
  </ifr:messages>
</ifr:properties>
</wsdl:definitions>

this is the path distribution file

/usr/sap/MDD/MDS03/mdm/distributions/MDD_ORCL/DEV_CATALOGO/Inbound/MDM/_MDMContractDataTransmission_ProductID/Ready

[Former Member · Accepted solution]

Oscar,

Thanks to provide Ready folder path. There is no problem with it.

The problem is with your XML schema only. You have uploaded XML/WSDL file as XML schema.

If you look at your screenshot. The file, which is selected for 'MDMContractDataTransmission' record is XML file. However, it must be an XSD like others.

Solution: Ask PI team to provide you XSD file, rather XML/WSDL file. Once you receive, delete the 'MDMContractDataTransmission' schema record from XML Schema table and recreate it with XSD path.

Hope, it will solve your problem..!!

Thx/ -Tarun

[Former Member · Accepted solution]

Hi Oscar,

As suggested by Tarun, you need to ask PI team to generate XML Schema(.xsd file) and then you need to maintain the same in your MDM Repository.

After that you would require to update your import map accordingly and then paste the file in Ready folder. Changing XSD should resolve your problem. Kindly check and update us with your findings.

Thanks and Regards,

Ankush Bhardwaj

[Former Member · Accepted solution]

Hi Tarum,

the problem has been solved.

the XSD SCHEMA was the problem . I created a new from interface PI and interface is working ok.

thanks for you support.

[former_member638448 · Accepted solution]

Hi Tarun

I have a question regarding the ERP >> PI >> SRM-MDM catalog set up for contract data and inforecord interfaces.

In PI, we are using standard interfaces provided by SAP and the data needs to be sent via PI adapter to SRM-MDM catalogue. The import manager in SRM-MDM then needs to pick up the file created by PI.

My question is - which file location should the file be placed by PI for these interfaces and how do

we map the file created by PI with the contract data and info records in the Import manager.

The source list for MDM Import Manager includes the option ‘Ports’. is this the right option to take?

Thanks

Vikas

[Former Member · Accepted solution]

Hi Vikas,

The file created in PI must be placed in ready folder of the inbound port : ERP Contract Data Transmission & ERP Info Record Data Transmission.

XML file that's created in PI must be directed to the following path (might look somewhat like this)-

:\Distributions\Server**\Repository_Name**\Inbound\Remote_system**\Port_Name**(ERP Contract Data Transmission)\Ready

:\Distributions\Server**\Repository_Name**\Inbound\Remote_system**\Port_Name**(ERP Info Record Data Transmission)\Ready

Copy the above path (as in your case) and paste it in PI system as target directory.

Later Import server must be started (if not started already) for the xml file to be processed automatically from Ready folder. This will update MDM.

Hope this helps.

Regards,

Ali

[Former Member · Accepted solution]

Vikas,

Ques: Which file location should the file be placed by PI for these interfaces?

Ans: PI will place the file in the Ready folder of the inbound port e.g. Ready folder of ERP Contract Data Transmission inbound port.

Ques: How do we map the file created by PI with the contract data and info records in the Import manager?

Ans: You have to create Import map to save the mapping b/w the file (which PI will send) and the fields in repository schema. Once it is saved, you can configure the same in port configuration. If you are importing data using Import Server, the file will be picked automatically and data will be imported in the configured table.

Ques: The source list for MDM Import Manager includes the option ‘Ports’. is this the right option to take?

Ans: If you are importing data manually, using Import Manager and you have configured the import map in the port configuration for the required tables, then 'Yes' you can select 'Ports' option in the source list.

     Note: If there is no file in the ready folder of the port then table name will be grayed-out.

Hope, it will clear your doubts.

Thx/ -Tarun

[former_member638448 · Accepted solution]

Thanks Tarun & Mir. Your replies have cleared a lot of my doubts now.

One question regarding ready folder - Is there a way I can see in the system as to where does this folder exist? In our landscape, we have a shared file system that is used by all the SAP systems in the landscape. The path provided by Mir starts with :/distribution...

I am not sure if this exist in our system.

Thanks

Vikas

[Former Member · Accepted solution]

Vikas,

You might have to contact your basis team to get exact path. I am sure they will help you with this.

Pls make sure you get access rights to path so that any manual interventions can be handled, just incase.

Regards.

Ali

[Former Member · Accepted solution]

Vikas,

I would request you to create a new thread for your question, else this answered thread will be confusing.

You can check the path under the MDM server directory, which starts like:

<drive_Name>/usr/sap/<MDM_server_instance>/<MDM_server>/mdm/distribution/<database_name>/<repository name>/inbound/<remote_system>/<port_name>/Ready.

Hope, it will help you.

Thx/ -Tarun

[former_member638448 · Accepted solution]

Created a new thread

http://scn.sap.com/thread/3307388

Please check.

Thanks for your help so far.

[former_member638448 · Accepted solution]

thanks Mir, basis team helped me to find out the path. Though i have another issue now.. please refer to the thread -

http://scn.sap.com/thread/3307388

Thanks

Vikas

[Former Member]

Hi Oscar

We have a lot of inbound and outbound ports in our MDM solution(SAP MDM 7.1 SP7) and we had the same problem (automatic import doesn't happen)

We asked SAP support team, but they haven't provide solution yet.

SAP support reccomend to delete all files in your inbound archive folders and then restart mdis.

it's may help you.

Regards

Kanstantsin Chernichenka

[Former Member]

Hi kanstantsin.

My problem was the schema was wrong. so change schema an put the new schema in port .

and yes is necessary delete all files on Inbound file to port bee empty and reload the repository too. 

also reviews logs on MDIS.

Regards.

[Former Member]

Hi Oscar,

As suggested above restarting is an option.

I have faced this issue earlier how i solved it is by logging into import manager selecting type as port and select the port which has the exception.

Fix the exception according to the Action Items section of the Import Status tab and save the corrected map.

[Former Member]

Hi Oscar,

Seems to me that issue lies with your MDIS.

Please check if the user credentials are maintained right in the auxiliary server for the given repository.

As suggested above a restart should help your cause.

Please update with results.

Thanks,

Ravi

[Former Member]

Hi Oscar,

I would request you to do repository reload.

I have faced this situation many times and repository reload has always solved the issue.

If reload also does not solve your issue, then it might be that there is large amount of data in XML file and MDM system is taking a lot of time to process single file. So you might need to check if data is coming in the XML file as expected. Please check and share your observations.

Thanks and Regards,

Ankush Bhardwaj

[Former Member]

Hi Oscar,

I think you might want to import xml file manually through Import Manager once. I have experienced this issue once. You can give a try performing manual import of xml file through Import Manager and later import should happen automatically. Good Luck!

Regards,

Ali

Message was edited by: Mir Ali