PDF through import manager

Hi Folks,
I have business requirnment in which pdf files are kept in folder.
I need this pdf files in MDM data manager.
We are importing data from portal to import manager.
My query is shall i able to get URL in data manager, by click on the URL (LINK)
or.
Second shall ,I able to put PDF in portal and same in import mnaager so i can able to access in PDF table of data manager.
I dont want to direct upload PDF in data manager but need to come through import manager to data manager.
Thansk in advance
Rohit

Hi Rohit
Yes, you can do this.
Define a field called PDFURL in the record.
An example of the data that would be stored in the PDFURL field : "abc123.pdf".
Now go to a local web server and define a simple webpage that displays a PDF. The name of the PDF to display should be passed to the webpage in the webpage's URL (e.g. http://server.local.domain/page?what=abc.pdf).
Now define the URL in the MDM Console. Replace the filename ("abc.pdf" in the above example) with the string "<f:PDFURL>". Using the above example, the URL defined in the Console would be http://server.local.domain/page?what=<f:PDFURL>.
Reload the repository and connect with the Data Manager. Goto Configuration -> Options and find "Records -> Web pane URL for selected records". Set it to the URL you defined in the Console.
Select a record and go to the Data Manager's Web tab. You should see the PDF displayed there.
NB: Be aware of how the MDM Server and the Web Server might reference the location of the PDF. While the PDF might be on the MDM box under c:\newfolder, the Web Server will (probably) not reference the document by the same path. Either use UNC paths or map a common network drive.
HTH,
Mark

Similar Messages

Setting up Custom Priorities for Taxonomy Attributes through Import Manager

Hi,
I want to set priority for "n" number of characteristics through Import Manager.
I know Import manager allows us to set priority to one of the following : "Highest" "High" "Normal" "Low" "Lowest". But I have a requirement to set custom priority for each of the attribute through Import manager so as to avoid manual intervention.
Has anybody worked on this before?
Regards,
Amol.

Hi,
Which special properties you are talking about ?
I will just brief you the concepts of Hierarchy and Taxonomy
Hierarchy
Node1
-    Node11
-   Node12
Node2
-    Node21
--         Node211
Only leaf nodes can be assigned at the time of record creation.
Taxonomy
Used when particular hierarchy nodes needs some extra fields.
Example: If your hierarchy is like
Cars
    - Fiat
    - Maruti
Bikes
    - Hero Honda
    - Bajaj
Now for Cars, i want to store its Price but for Bikes i am not interested in Price but I want the Colour info. Now if you create the Price and Colour as fields of the repository then for all the records whose category is Cars will have NULL value for Colour and reverse in case of Bikes. Hence the concept of Taxonomy is introduced so that you can assign the fields (known as attributes) to the Nodes of the hierarchy.
For Taxonomy Import, refer the below links
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30aa1447-80a1-2a10-e483-a76087bcb12f
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6090d0bd-1da7-2a10-468f-bdd17badb396
Regards,
Jitesh Talreja

Normalisation of text string on import through import manager

Hi There, we have just uncovered an issue with our workflows where a submitted file that contains 'special' characters in a description field (text string) will cause the jobs to fail. Is there a way i can tweak the normalisation feature in the import manager to remove these special characters, while leaving 'normal' characters (such as spaces, commas and other punctuation) in tact?

Hi Adam,
The failure is happening at the import stage and not the workflow stage ,As your import of records are triggering the workflow action(Trigger action being record Import).The records may not be getting imported rightly and so the workflow failing.
But as far as i know the Text data type in MDM allows special characters entry without much problem.
Try the following:
- Check to see if the charater length of this special characters holding field is sufficiently large it could be the problem that the length of the incoming charaters are more than the length mentioned in the console settings and so truncation of charaters are causing the failure of import.
- Check to see if values of all other fields especially the date and numeric fields if any are holding correct data .
- Lastly if you find out that the special charaters are the only cause of the failure then you will have to perform the normalization of the values and save the settings in the map and then use this saved map.Try to accomodate all the possible charaters faults.You can normalize the Field by right clicking on it and say value conversion filter >Normalize.If your values are lesser you can normalize them at the value level itself using the right click.
Hope It Helped
Thanks & Regards
Simona Pinto

Value Mapping in Import Manager

Hi All,
I have Probelm while loading data to MAIN TABLE through Import manager,I am getting XML file from Legacy System in which legacy sends State Code like NM (for New Mexico) .In my region table I made Name and Code as display field .Created my Import map ,when ever new value comes for region value mapping is not working ,I tried changing my region table with code only display field it works ,but I want Name also display field .
Note : all my lookup table Remote key mapping Enabled
Is there any way we can acheive this or am I missing some thing here .
Thanks,
Madhu

Hi Madhu,
to achive this:
1. First go to the table where you are maintaining the region codes.
2. Enter the region code there and then go to the import manager by connecting to the source file.
3. go the region field map by opening the map.
4. go to value mapping pane and select unmap.
5. then select Automap and check the that your region code added manually is mapped with the source file.
6. You may see some unmapped source values, map it to Null values at destination.
7. Save the map.
8. This shoul enable the import for you.
if you want to avoid the manual mapping everytime, you should be getting all the region codes once and import/update it in the data manager as a one time job.
Then you avoid steps 1 to 3 everytime and carry out the remaining steps to import the records.
Hope this helps resolve the issue.
Thanks
Rahul

Create key mapping using import manager for lookup table FROM EXCEL file

hello,
i would like create key mapping while importing the values via excel file.
the source file containing the key, but how do i map it to the lookup table?
the properties of the table has enable the creation of mapping key. but during the mapping in import manager, i cant find any way to map the key mapping..
eg
lookup table contains:
Material Group
Code
excel file contain
MatGroup1 Code System
Thanks!
Shanti

Hi Shanti,
Assuming you have already defined below listed points
1) Key Mapping "Yes" to your lookup table in MDM Console
2) Created a New Remote System in MDM console
3) proper rights for your account for updating the remote key values in to data manager through import manager.
Your sample file can have Material Group and Code alone which can be exported from Data Manager by File-> Export To -> Excel, if you have data already in Data Manager.
Open your sample file through Import Manager by selecting the remote system for which you want to import the Key mapping.
(Do Not select MDM as Remote System, which do not allows you to maintain key mapping values) and also the file type as Excel
Now select your Soruce and Destination tables, under the destination fields you will be seeing a new field called [Remote Key]
Map you source and destination fields correspondingly and Clone your source field code by right clicking on code in the source hierarchy and map it to Remote Key if you want the code to be in the remote key values.
And in the matching criteria select destination field code as a Matching field and change the default import action to Update NULL fields or UPDATED MAPPED FIELDS as required,
After sucessfull import you can check the Remote Key values in Data Manager.
Hope this helps
Thanks
Sowseel

Skipped items in import manager

Hi,
If i have around 10000 masterdata and in that i impoted around 8000 through import manager and 2000 i skipped as duplicates, Is there a way to check that this 2000 records will there be any way to track this as below,
10000 record recd in import manager
8000 records created
2000 skiped.
Thanks,
Suresh

Import stats are displayed in the Import Status tab of the Import Manager.
Here's what I\ve found at the end of the report:
Import Actions Action # of Source Records
Skip 2000
Create 8000
Update (NULL Fields Only) 0
Update (All Mapped Fields) 0
Replace 0
Delete [destination] 0
Is that what you want?

Truncate / Trim and Convert the values while importing in Import Manager

Hi,
I am facing the following issues while importing the values in Import Manager.
1) The incoming value is a 4 character text value (e.g. D004) and i need to truncate the 1st two characters so that i get the output as "04" and map it to the destination numeric 2 character field.
Can any1 help me on this as to how can i truncate the 1st two characters?
2) My incoming value is a numeric field which is coming from ECC. this value can be negative as well. the ECC sends this value as (78.00-) ie the minus sign is suffixed to the value but in MDM i need it as (-78.00) ie minus sign prefixed to the value.
Is there any setting in Import manager where i can set the minus sign as a prefix?
Useful answers will be rewarded with points.
Regards,
Roshani

Hi Roshani,
Can any1 help me on this as to how can i truncate the 1st two characters?
As suggested by everyone, none of these options will work. Since your field has alphanumeric Value i.e. D004. Use Option Replace.
After mapping your source field with target field which must be of Type TEXT, Right click on your source field>Set Value Conversion filter>Replace..-->a pop up window will come Replace write Find What: D0 and Replace with: keep it blank(dont write anything) and then Press Ok, you will see all your Source values D0XX converted to XX and then can save in Import Map which will give you the desired result.
If you set your target field of type INTEGER, you cant have option Replace. And the TRUNCATE option as suggested by everyone will not work as Operand 2: you can set as Numeric values only, you would not able to write D.
Is there any setting in Import manager where i can set the minus sign as a prefix?
I dont think this is possible alone with Import Manager, you need MDM workflow for this where your workflow trigger action = Record Import in Data Manager, and need to select the same workflow in configuration options of Import Manager>Import>checkout/workflow = select the workflow name from drop-down which you set in Data Manager and then need to save this in your Import Map. So in this manner whenever record comes through import Manager, these records automatically will go through this Workflow and will give you the desired result.
START(CHECKOUT)>Assign>STOP(CHECKIN)
Assign step where you give assignment on this field and write assignment expression as:
IF(FIND(XXX, "-"), "-"&LEFT(XXX, (LEN(XXX)-1)), XXX)
where XXX = Field name which you defined in MDM repository.
Regards,
Mandeep Saini

Error while using Import Manager in MDM 7.1 SP7

Hi,
We are using MDM 7.1 SP7. I am trying to import a Tab delimited flat file through import manager. When I try to connect the source file, I get the following error * Logon Error: Found non-complaint CSV format in input stream [Encoding:UTF16].96*
If I try to import through an excel there is not problem. Can someone help to solve this error while importing in Tab delimited flat file through import manager.
Best Regards
Manoj

Hello Mandip,
I had tried doing it before posting my question. I saved it in UTF8 and then tried importing. Saving in UTF8 format made the import manager accept characters like Ä and the original error was solved, but when then a new error came which called for UTF16 format. When I digged into it I found that it is due to the double quotes(" ") in the flat file. When I removed the quote import manager accepted it.
So the conclusion is there should be a way to save the flat file in UTF16 format or the workaround is importing it in excel but again excel has limitation of importing 100000 records in one file.
Can you suggest how to save the flat file in UTF16.
Best Regards
Manoj

Letter case in SAP import manager

Hi,
We are facing a strange issue with SAP import manager. we have the value 'n' for a field in XML file. when we tried to open the XML file through import manager, in map/value fields tab, the value is showing up as 'N' for that field where as it is correctly showing up as 'n' for that field in source preview tab. In the XML file, we have the values 'o', 'e', 'n' for that field. The remaining letters are showing up correctly in map/value fields tab and we are facing issue with letter 'n'.
Could you please assist on this. Any help is greatly appreciated.
Thanks & Regards,
Pradeep Kumar

Hi Pradeep,
Can you check whether any value converstion filter (Replace) is set for that particulat field where you are getting this error. if so just choose none for value converstion to source field,save map updates and reload the xml file.
for eg: by using replace command the values can be changed.
Thank you
Rahul

Import attributes thru import manager

Hi,
What are are steps to import the attributes and LINK them to records through import manager. Is there some blog or articles refer please. Excel file with supporting different attribute types (numeric,coupled and text) will help along with steps to import the attributes import manager.
Is linking of attributes to records is possible through import manager?
Thanks
Edited by: SDN POWERED on May 21, 2009 9:59 AM

Hi,
In order to work with the Taxonomies, you need to perform the following steps:
1. Import Categories
2. Import Attributes
3. Attributes values.
4. Attribute links
Please refer to the links below to understand the Taxonomy import process step by step:
Master Data Management Import Manager - Taxonomy Data (Splitting Into Hierarchy) u2013 Part 1:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30aa1447-80a1-2a10-e483-a76087bcb12f
Master Data Management Import Manager - Taxonomy Data (Attributes) u2013 Part 2:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6090d0bd-1da7-2a10-468f-bdd17badb396
Master Data Management Import Manager - Taxonomy Data (Attribute Text Values) u2013 Part 3:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8090941f-a5a7-2a10-3ba6-b4af5ec6d97b
Master Data Management Import Manager: Taxonomy Data (Attribute Links), Part 4:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/308c62a2-5faa-2a10-fda6-fa4aa7169734
Hope this helps.
Thanks and Regards
Nitin Jain

Relationship import | Import manager

Hi ,
I am trying to import relationships through import manager in the material repository . What I do is , there are some existing relationships that I created in the data manager . I export them first [ data manager > relationships > export to a file ] to a file and then make changes to the existing file . I use the same file to import relationships but this time with the import manager . I have the following column names in my ".TXT" file ...
1) material numbe <name of the relationship defined in the console>
2) material number <>
3) quantity
I can successfully map the fields and then when I choose the import action it gives me the following error ...
Import failed. Field not found.
Import action: NoneSource record no: 8
there is no record in my file actually at number 8 . I removed the last "Enter" from the file and then imported it but with same results . I exported the existing relationships to an excel file and then tried to import it through the import manager but with the same result .
To verify if there is a problem with the file I use the same file to import the relationships through data manager [relationships > import from file > name of the relationship defined in the console ] and I am able to successfully import it .
What do you guys think is the problem ??
Regards
Deepak Singh

Hi Deepak,
I had performed the following steps and it worked perfectly fine.
Just go through them once and check that you have did the same.
1. Export Relationship using Data Manager -> Relationships -> Export to File.[There is only Display Field i.e. Material]
2. Imported the same text file with Type="Delimited Text" and Delimiter="\t"
3. Select the Relationship table from the Destination drop down list.
4. Map the Parent Material with the Material[Parent] and Child with Material[Child].Also Quantity with the qualifier Quantity.
5. Execute the import.
Note : Please dont make any changes to the Text file and try importing.
Regards,
Jitesh Talreja
Edited by: Jitesh Talreja on Apr 10, 2008 7:25 AM

Differ between import manager and import server

Hi to all,
Can any one explain difference between import server and import manager and how the data will be imported to the same.
Regards
MM

Hi reddy,
Can any one explain difference between import server and import manager and how the data will be imported to the same
Please follow the text below, which has been taken from the help.sap.com
Both MDIS and the MDM Import Manager can import data from a source file into an MDM repository. However, each has unique capabilities that distinguish it from the other. When each is used to its advantage, the result is an import strategy which provides the most efficient importing of data possible.
The strength of the Import Manager is its connection to the source data, which enables its interactive map-making capabilities. When the Import Manager connects to a source it preloads the entire source file, giving it knowledge of every field and every value in the source data. This u201Ctotal awarenessu201D is crucial for preparing a complete import map. To help ensure a map is complete, the Import Manageru2019s Import Status tab alerts users to any discrepancies between source data values and the current map. The user can fix these problems interactively within the Import Manager and save the corrected map before any data is imported.
Preloading an entire source file comes at a price, however. It consumes memory on the computer running the Import Manager and very large source files may exhaust the computeru2019s available memory.
By contrast, MDISu2019s strengths are its scalability and automation.
For scalability, instead of preloading the entire source file into the host machineu2019s memory as the Import Manager does, MDIS processes records in a stream by loading a record at a time into memory.
This streaming technique enables MDIS to process much larger source files than the Import Manager, as the demand for memory on the host machine is not affected by the size of the import file.
In addition to file size, file quantity poses a second scalability challenge. For example, a real-time transactional environment may produce a staggering number of files, each containing only one or two records. To import these files individually through Import Manager would be extremely inefficient. MDIS tackles this problem with a file aggregation feature that processes files systematically in batches rather than as individual files, resulting in faster, more efficient import of data.
As it relates to automation, MDIS requires no user intervention to import files to an MDM repository. Instead, it relies on maps created previously within the Import Manager. Once an import file is placed in the appropriate folder, its data is imported automatically into the MDM repository using the rules of the pre-defined import map. Once a file is processed, MDIS scans the repository for the next file to import. This process continues 24 hours a day, seven days a week, until either MDIS or MDM Server are stopped.
The trade-off for this scalability and automation is that if discrepancies between the source data and the import map arise, MDIS cannot u201Cfixu201D these problems by itself. Instead, the u201Cproblem casesu201D can be fixed manually at a later time using the interactive capabilities of the Import Manager. Unlike the Import Manager, however, MDIS can set aside problem records or files and continue importing.
These conceptual and operational differences between the Import Manager and MDIS are summarized in the table below.
Item
Import Manager
MDIS
Source file location
Anywhere
Automatic inbound port
Import process
Interactive
Automatic
Import map state
Editable
Read-only
Object loaded in memory
Entire import file
Individual records
Streaming import support
No
Yes
File aggregation support
No
Yes
Maximum import file size
Limited (50,000 records)
Unlimited
Status location
Import Status Tab
MDM Console/Report file
Error correction prior to import
Yes
No
Exception handling during import
No
Yes
For additional info, kindly refer the link below:
http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm
GO to-> MDM import Server
Hope it helps.
Thanks and Regards
Nitin Jain

Issue in Importing Cleansing package in to Repository through Repo Manager

Hi,
For using Data Quality, we have installed the cleansing package installble into our server. It has created all the ZIP/DAT Files in to the ...DataQuality\Datacleanse directory. After that while importing into Metadata through Repository Manager, we are getting
" A Probelm occurred while verifying data cleanse repository connection".
Note : We have installed BODS XI 3.1 Version
And the cleansing package using here is SBOP CLEANS PACK XI 3.2
Is there any problem with version incompatibility?
Any other solution??? Kindly help us on this.
Reg,
John

John,
BODS XI 3.1 requires cleansing package XI 3.1. You will need to download the cleansing package XI 3.1. Or, you can download BODS XI 3.2 and install the latest version.
Paul

Importing Contact numbers through Content Manager

I have imported my phone numbers through content manager onto my iphone and every number is there except all the fax numbers and email addresses. Rather than inputing each one manually, is there a way that I can import all the contact info for all persons?

Allan,
For reference, Content Manager is the Windows-only application provided by AT&T for reading contact information that has been transferred from a SIM card to a USB Flash drive. AT&T also provides support for Content Manager through the AT&T owned retail stores.
In general when you are exporting the data you export it to a .CSV file, and then tell Outlook or Outlook Express how to read the data. If you have contacts have all the information in Content manager, make sure you are exporting all of the fields to the .CSV file.
Hope this helps,
Nathan C.

When opening import manager, it is used to through an Error message?

Hi All,
I have extracted xml file using generic extraction from SRM system, now when i want to import this xml file using my import manager.. while at opening import manager it is throwing error message.
Error Message:
Logon Error : Error: Can't open C:\Program files\SAP MDM 7.1\Import Manager\xsd.exe
I have also refered SRM-MDM catalog document, In that they have mentioned it as.. while importing xml file you will get this error first time and you need to change xsd.txt file to .exe file. But i don't find any file such type in above path which i have mentioned.
Can any one have solution for it.. I request to help me out.
Thanks
Chinthapatla Bharat

Hi Bharat,
You need to place the xsd.exe file at location C:/Program files/SAP MDM 7.1/Import Manager.This xsd.exe file can be downloaded from the Microsoft website. Please refer SAP Note https://service.sap.com/sap/support/notes/1331426
Also, Please find the similar thread with more details:
Re: Problem with XML import MDM 7.1 SP2 u2013 XSD.exe Issue
Regards,
Mandeep Saini

PDF through import manager

Similar Messages

Maybe you are looking for