cancel
Showing results for 
Search instead for 
Did you mean: 

Auto import issue

Former Member
0 Kudos

Hi All,

Iam trying the auto import using the import server of MDM 7.1

I have made the below settings,

1. Remote System : Type Inbound

2. XML Schema : Used the Business Partner schema (xsd)

3. Port : Inbound,processing type - inbound, automatic

4. created a map and mentioned it in the port.

MDIS.ini -> changed the Interval to 10

I placed the xml file in the ready folder of the inbound port folder

restarted the import server.

But nothing seems to happen. the file is in the same place where it was

Could you please help?

  • Is there any specific naming convention we have to follow for the xml file that we place in the ready folder or the server will pick any xml file present in the ready folder?

Please help

Thanks

Suresh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Vinay,

Now the status is "has data". Can you please tell me if i have to check something else?

Regards

Suresh

Former Member
0 Kudos

Hi Suresh,

For Automatic import processing, make sure that your Import server (not Import manager) is running properly.

Also can you check the import server log for errors and update this post...

Regards,

- Shailesh.

former_member189669
Active Participant
0 Kudos

Hi Suresh,

Please connect to the port from Import manager. Check all the value mappings. Any single value mapping missing - auto import will not work. Please ensure all value mappings are done. Perform manual import for the first time.

Save the map after first successful import.

Drop xml file into Ready folder again and check for auto import.

Regards,

Vinay M.S

Answers (7)

Answers (7)

Former Member
0 Kudos

Hi Vinay,

My problem was solved, I got the server reinstalled. I guess it was not done correctly the first time. It works now. But your suggestions were really helpful

Thanks

Suresh

Former Member
0 Kudos

Hi Vinay,

Now I actually imported using the map in the import manager. It works.Not sure why this is happening.

The port status is still "Has Data"

regards

Suresh

former_member189669
Active Participant
0 Kudos

Hi Suresh,

Thanks for confirming.

Please refresh 'Console' to see latest status of the port .

Hope you have saved the import map after the succesful import (you may use Save Update incase small changes were done in mapping ).

Drop a file in ready folder and check for auto-import.

Regards,

Vinay M.S

Former Member
0 Kudos

HI Vinay,

Did not work even after all that.. the status is still "has data". I created another repository on mdm5.5 with the same settings and it worked. then i archived the same repos and placed it in mdm7.1 but here it does not work, it stops at the point where the status is "has data".

So what i understand is the steps what i have done are correct or it should not have worked in 5.5 version aswell.

Is there anything different from the 5.5 and 7.1 or is there any extra step that needs to be added in 7.1?

When you say restart mdis server do that mean i should restart the instance of import server from the services.msc or is there any other place to do it?

Regards

Suresh

former_member189669
Active Participant
0 Kudos

Hi Suresh,

Another check point - Please ensure that the root set in mds.ini. is the root of distribution directory where Ready folder resides .

Ready foler distribution path in an MDM server is generally - root/DBMSinstance_DBMStype/RepositoryName/Inbound/

RemoteSystem/PortName/Ready.

'Root' of the above distribution path has to be defined in 'Distribution Root Dir' parameter in MDS.ini.

Please restart the MDS after modifying .

Regards,

Vinay M.S

Former Member
0 Kudos

It look like I have the same problem with value mapping.

We have three major ports importing data.

We know that one port seems to be weak on value mapping ( we are searching her for a solution)

My question:

If one port blocks because of a problem with value mapping why does the MDIS stops working on all other ports, too?

lpk

Former Member
0 Kudos

HI,

copied the last bit of the log, please see if it helps. My repository is MDM_TATA

GMT, Friday, November 06, 2009"" pid=""2184"" host=""idphl717"" compile-type=""RELEASE_64""",,,,,,,,,Open,,

2009-11-06T09:23:55.750,4272 ,23,"==================================",Background_Thread@Main,.\XCatServer.cpp,411,,,,,,,,

2009-11-06T09:23:55.750,4272 ,23,"Version: Server = 7.1.00.76 Build = Built on 2008-Oct-21 Repository major =13 minor =13",Background_Thread@Main,.\XCatServer.cpp,420,,,,,,,,

2009-11-06T09:23:55.750,4272 ,23,"config filepath: D:\usr\sap\L5M\MDS00\config\mds.ini",Background_Thread@Main,.\XCatServer.cpp,423,,,,,,,,

2009-11-06T09:23:55.750,4272 ,24,"No RFC Gateway registered. Maintain SAP RFC Gateways within server configuration file mds.ini .",Background_Thread@Main,.\RfcConnectionManager.cpp,156,,,,,,,,

2009-11-06T09:23:55.750,4272 ,24," RFC Gateway configuration format SAP RFC Gateways=<Gateway Host>:<Gateway Service> || GWHOST=<Gateway Host> GWSERV=<Gateway Service> [, ...] .",Background_Thread@Main,.\RfcConnectionManager.cpp,159,,,,,,,,

2009-11-06T09:23:55.750,4272 ,23,"mds Configuration setting: ""Max Threads Per Operation""= 4",Background_Thread@Main,.\XCatServer.cpp,530,,,,,,,,

2009-11-06T09:23:56.750,4272 ,23,"User authentication method: Repository",Background_Thread@Main,.\XCSGlobalFunctions.cpp,415,,,,,,,,

2009-11-06T09:23:56.953,4272 ,23,"Init Database Tag: VENDORIDPHL717.PHL.SAP.CORPMSQL_6_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:23:57.610,4272 ,23,"Init Database Tag: PRODUCTIDPHL717.PHL.SAP.CORPMSQL_7_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:23:58.157,4272 ,23,"Init Database Tag: MATERIALIDPHL717.PHL.SAP.CORPMSQL_8_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:23:58.735,4272 ,23,"Init Database Tag: EMPLOYEEIDPHL717.PHL.SAP.CORPMSQL_8_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:23:59.203,4272 ,23,"Init Database Tag: CUSTOMERIDPHL717.PHL.SAP.CORPMSQL_8_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:23:59.813,4272 ,23,"Init Database Tag: BUSINESS_PARTNERIDPHL717.PHL.SAP.CORPMSQL_16_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:24:00.344,4272 ,23,"Init Database Tag: MDM71_RKTIDPHL717.PHL.SAP.CORPMSQL_9_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:24:00.906,4272 ,23,"Init Database Tag: MDM71_Test_ProductsIDPHL717.PHL.SAP.CORPMSQL_19_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:24:01.469,4272 ,23,"Init Database Tag: NSCIDPHL717.PHL.SAP.CORPMSQL_3_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:24:02.63 ,4272 ,23,"Init Database Tag: MDM_TATAIDPHL717.PHL.SAP.CORPMSQL_8_21_4_3",Background_Thread@Main,.\XCatDB.cpp,711,,,,,,,,

2009-11-06T09:24:03.516,4272 ,25,"Unable to register server in System Landscape Directory: Call to SLDREG Utility in D:\usr\sap\L5M\MDS00\exe\ failed, Error = 0xFFFFFFFF@lf;If you are not using SLD, set parameter 'SLD Registration' to false in server configuration file so that the server does not try to register with SLD. This will avoid this error in the future.@lf;STACK TRACE::@lf;Using 'imagehlp.dll' version: 4.0.5 @lf;SymbolSearchPath: D:\usr\sap\L5M\MDS00\exe;D:\usr\sap\L5M\MDS00\exe;D:\usr\sap\L5M\MDS00\symbols;C:\WINDOWS@lf;--> Register Dump <@lf; rax=0x00000000437895f4 rbx=0x00000000ffffffff@lf; rcx=0x00000000437895f4 rdx=0x0000000000000000@lf; r8 =0x0000000000000004 r9 =0x000000004009a614@lf; r10=0x0000000000000001 r11=0x000000000000ffff@lf; r12=0x0000000000000000 r13=0x000000000012c888@lf; r14=0x000000000012c870 r15=0x000000000000000a@lf; rip=0x0000000077ef0a2a rsp=0x000000000012c4c8 rbp=0x000000000012c610@lf; rsi=0x0000000000000000 rdi=0x00000000000006c0@lf;> Stack Back Trace <--@lf; ...<skipping 4 internal stackframes>...@lf; 1) mds!SLDRegAgent::RegisterServer + 19253 bytes@lf; Source: sldregagent.cpp ( Line: 440 )@lf; SFrame: IP:00000001401489dd RA:00000001400ff75e@lf; FP:000000000012ec30 SP:000000000012c630@lf; Params: 01:000000000000000a 02:000000000000000a@lf; 03:000000014284d5f8 04:00000000040fe340@lf;@lf; 2) mds!A2i::CXCatServer::Init + 6354 bytes@lf; Source: xcatserver.cpp ( Line: 666 )@lf; SFrame: IP:00000001400ff75e RA:00000001400d734c@lf; FP:000000000012efc0 SP:000000000012ec40@lf; Params: 01:000000000012f000 02:0000000000000127@lf; 03:00000001437ae001 04:0000000000000001@lf;@lf; 3) mds!MDMServerApp<A2i::CXCatServer,A2i::XcsServiceInitializer>::Execute + 60 bytes@lf; Source: mdmserver.inl ( Line: 7 )@lf; SFrame: IP:00000001400d734c RA:00000001400188fe@lf; FP:000000000012f740 SP:000000000012efd0@lf; Params: 01:0000000001d39e40 02:0000000000000001@lf; 03:00000001437ae060 04:0000000100000400@lf;@lf; 4) mds!MDMServer::Run + 778 bytes@lf; Source: mdmserver.cpp ( Line: 269 )@lf; SFrame: IP:00000001400188fe RA:0000000140019011@lf; FP:000000000012fb20 SP:000000000012f750@lf; Params: 01:000000000012fb68 02:0000000001cfc1b0@lf; 03:0000000001df48b0 04:0000000001d4b830@lf;@lf; 5) mds!MDMServer::MainImpl + 981 bytes@lf; Source: mdmserver.cpp ( Line: 133 )@lf; SFrame: IP:0000000140019011 RA:0000000140015326@lf; FP:000000000012fe70 SP:000000000012fb30@lf; Params: 01:0000000000000000 02:0000000000000005@lf; 03:0000000001d4c9f0 04:0000000001d4c9f0@lf;@lf; 6) mds!wWinMain + 114 bytes@lf; Source: winmain.cpp ( Line: 45 )@lf; SFrame: IP:0000000140015326 RA:0000000140001330@lf; FP:000000000012feb0 SP:000000000012fe80@lf; Params: 01:0000000000000000 02:0000000000000000@lf; 03:0000000000000005 04:0000000140000000@lf;@lf; 7) mds!__tmainCRTStartup + 608 bytes@lf; Source: crt0.c ( Line: 324 )@lf; SFrame: IP:0000000140001330 RA:0000000077d596ac@lf; FP:000000000012ff70 SP:000000000012fec0@lf; Params: 01:0000000000000000 02:0000000000000000@lf; 03:0000000000000000 04:000000000012ffa8@lf;@lf; 😎 kernel32!BaseProcessStart + 44 bytes@lf; SFrame: IP:0000000077d596ac RA:0000000000000000@lf; FP:000000000012ffa0 SP:000000000012ff80@lf; Params: 01:00000001400013b0 02:0000000000000000@lf; 03:0000000000000000 04:0000000000000000@lf;@lf;",Background_Thread@Main,.\SLDRegAgent.cpp,440,,,,,,,,

2009-11-06T09:24:52.984,6872 ,23,"Starting Repository: MDM_TATA on IDPHL717.PHL.SAP.CORP",MDSAdminServer@StartRep,.\CatMgrDatabase.cpp,1049,,,,Admin,MDM_TATAIDPHL717.PHL.SAP.CORPMSQL_8_21_4_3,,,

2009-11-06T09:24:55.969,7360 ,23,"Workflow Initialization. Could not retrieve mail server information.",Background_Thread@Workflow,.\Workflow.cpp,1342,,,,,MDM_TATA <IDPHL717.PHL.SAP.CORP [SQL_Server]>,,,

2009-11-06T09:24:55.984,7360 ,23,"Number of unlaunched jobs loaded: 0",Background_Thread@Workflow,.\Workflow.cpp,1747,,,,,MDM_TATA <IDPHL717.PHL.SAP.CORP [SQL_Server]>,,,

2009-11-06T09:24:55.984,7360 ,23,"Number of launched jobs loaded: 0",Background_Thread@Workflow,.\Workflow.cpp,2456,,,,,MDM_TATA <IDPHL717.PHL.SAP.CORP [SQL_Server]>,,,

2009-11-06T09:24:55.984,7360 ,23,"Daemon is started at: 11/06/2009 09:24:55 GMT",Background_Thread@Workflow,.\Workflow.cpp,10228,,,,,MDM_TATA <IDPHL717.PHL.SAP.CORP [SQL_Server]>,,,

2009-11-06T09:24:55.984,7360 ,23,"Workflow initialized.",Background_Thread@Workflow,.\Workflow.cpp,1363,,,,,MDM_TATA <IDPHL717.PHL.SAP.CORP [SQL_Server]>,,,

2009-11-06T09:24:55.984,7360 ,23,"Load complete on MDM_TATA",Background_Thread@Main,.\Preload.cpp,894,,,,,MDM_TATA <IDPHL717.PHL.SAP.CORP [SQL_Server]>,,,

former_member189669
Active Participant
0 Kudos

Hi Suresh,

Not able to infer anything from log. Sorry.

Can you please confirm if you could check missing value mappings in your import map ?

Regards,

Vinay

Former Member
0 Kudos

Hi Vinay,

The port status is still empty.

Mapping was done correctly, and i saved the map only when it showed the message "ready to import"

Thanks

Suresh

Former Member
0 Kudos

Hi,

Changed the password under mdis.ini and restarted the server it still does not work !!

Under the exception folder there are three subfolders "ImportX", "StructuralX", "ValueX" and they all are empty

Thanks

Suresh

former_member189669
Active Participant
0 Kudos

Hi Suresh,

Thanks for confirming . Your port status must now be ' Has Data' . Can you please check and confirm ?

In that case, please check if you have ensured all the field values are mapped. If the fields are mapped but if any value mapping is missed , auto import will not work.

Regards,

Vinay M.S

former_member189669
Active Participant
0 Kudos

Hi Suresh,

In addition, check if the file has exception. Please navigate to 'Exceptions' folder to check/check port status in Console .

Presence of exception will set the port status to 'Blocked'.

If the file has exceptions, connect to port from import manager> resolve the exception and perform manual import> Save the map.

Subsequent imports will happen automatically.

Regards,

Vinay M.S

Former Member
0 Kudos

Hi Suresh,

If your Admin user has some password then same is to be mentioned in MDIS.ini file under your repository section. Navigate to your Repository section in MDIS.ini, Replace the parameter PasswordS to Password = <Admin password> and restart the Import server. Now check the MDIS.ini file again, password parameter written by you should get converted to PasswordE = <some encrypted value>.

Check the file again in Ready folder

Regards,

Jitesh Talreja