Workflow and Import Manager

Hi,
I want to run a workflow as a result of an import.
I connected the workflow in the configuration of the import manager and the workflow starts OK when I import records using the import manager. I have 2 problems with the process:
1. The workflow checks out the records, but at the end of it the records are not checked in (when I run the workflow manually it does check them in).
2. When I stand on the workflow in the data manager I expect to see only the new records that I imported connected to the workflow while actually I see the whole repository.
Thanks,
Tal

Hi Tal,
Before we proceed further, i would like to confirm few things from your configurations of workflow....
1. In the workflow record detail under Trigger Action property make sure you have choose 'Record Import' value only....
2. In the workflow design under start process property 'CheckOut Records' should have the value 'NO'
3. Make sure while importing records it shows up that its going to Trigger the workflow...
hope this cross-check will solve your problem,
please feel free to revert to me for further clarifications...
thanks
Alexander
p.s.Kindly reward the points, if found problem solved.

Similar Messages

How to install/run Data and Import Manager in a desktop with linux (ubuntu)

Hi all,
I need to know if it's possible run data manager and import manager in a desktop with OS linux specific UBUNTU and where can I download installer
Regards
José Luis D.
Edited by: JL Delgado on Aug 11, 2009 6:49 PM

If you have SAP SMP ID - You can download the MDM 7.1 from -
www.service.sap.com/swdc
Following the path -
Installations and Upgrades - Entry by Application Group" SAP NetWeaver" SAP MDM" SAP NETWEAVER MDM 7.1
Installation
or
Support Packages and Patches - Entry by Application Group" SAP NetWeaver" SAP MDM" SAP NETWEAVER MDM 7.1
Please confirm your MDM version. If it is 5.5 then you need to select MDM 5.5 instead of MDM 7.1 in above link.
Regards.

Difference between Workflow and Alert management

HI all
Let me know the difference between workflow and alert management. ?
In Workflow if we want to trigger alert or mail.
We can use SO_NEW_DOCUMENT_SEND_API1 FM send mail.
But in alert we can use different method?
Can i know wht the exact difference between two?

Hi,
email messages can be sent with both technologies...
If you need to send just a simple email, use the ALM.
If you need to send email and wait something adding additional flows....use the Worflow.
Remember that with ALM is not possible to attach something to the email.
You can add additional steps like web addresses in order to perform further activities.
Luciano

Help using workflow for import manager

hi all,
assumes import server is used for automation creation/update of records,
i need to design a workflow to verify existing record that:
if a validation pass: update all fields + update mapping key
if a validation fail : update mapping key only
can anyone provide good suggestion on how it can be done via workflow?
MDM API is out of scope...
thanks,
Shanti

Hello Shanti
Import manager and import server launch workflow after data loading is finished.
You cannot manage loading rules from workflow.
You can create two inbound ports:
one for keys loading
another one for keys+fileds loading
Regards
Kanstantsin Chernichenka

Brief about Console, data manager and Import manager

Hi,
Iam new to MDM we just started installing our MDM components and iam a MM functional guy Can you any one tell me about console, data manager and import manger i need to know the following,
1. what is it
2. How the 3 is interlinked
3. can the data manager be loaded directly without a import
4. is there a std way of creating repository
5. I need to do samples on vendor, customer harmonisation and the spend analysis and matl master harmonisation..
Iam asking too much in this forum but i knw you guys are there to help me out.
Thanks in advance,
Suresh

MDM Console
The MDM Console allows the system manager to administer and monitor the MDM Server, and to create, maintain the structure of, and control access to the MDM repositories themselves. Records are not entered or managed with the MDM Console, but rather with client apps such as the MDM Client.
MDM Client(data manager)
The MDM Client is the primary client of the MDM Server, and is the program most users see on their PCs. It allows users to store, manage and update master data consisting of text, images, and other rich content, and to create taxonomies, families, and relationships. Other clients include the Import Manager, the Image Manager, and the Syndicator.
Import Manager
Allows you to import master data from most types of flat or relational electronic
source files (e.g. Excel, delimited text, SQL, XML, and any ODBC-compliant source),
and to restructure, cleanse, and normalize master data as part of the import process.
<i>2. How the 3 is interlinked</i>
--->
Suppose you are sending vendor information to MDM repository be sending IDOC from R/3. Then the whole process can go as... IDOC will be sent to XI, so XI will generate XML file that contains data. Then import manager can import this file and will so place the data in repository.
Now if you want to send data in MDM repository, the process goes reverse way. Syndicator will generate flat/xml file. This file will be given to XI so that XI will generate IDOC out of it and will send it to XI. This whole process ensures data consistancy
For details refer this link
http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm

Workflows and Imports

Hi there,
I'm wondering if "Before Modified record saved" type workflows are triggerred when importing data.
For example, i'm interested in writing a workflow that updates a field when another changes.
I have the conditions setup as follows:
PRE('<IndexedPick1>') (notequal) (squarebracket)<IndexedPick1>(squarebracket)
Where notequal and squarebracket are the correct operations, just can't seem to get them to show here!
When this is true a checkbox is updated to 'Y' or 'N' depending on the value in IndexedPick1.
I tested this and it works fine when just editing a record, but when using a data import it doesn't seem to trigger.
So, is this expected behaviour and is there any workaround (other than including the 'Y' or 'N' value in the import as this has other problems for us, not crm related)
UPDATE: The workflow seems to trigger if i don't put anything in the condition and instead have it as an "IIf" statement in the "Update Field" action.. but this is not ideal
Thanks
Edited by: user11098424 on 07-Jan-2010 03:58

For new records, the import process will work exactly the same way as if you were inserting a new record using the insert page, if you choose not to import duplicates, and import only new records. Maybe for your request you will need to run the import twice, second time with your workflow inactive. Or, if possible, split the file into "new" and "existing" file.
regards,
Flavio Amorim
Brazil
www.triscal.com.br

Approval Workflows and Importing file on OIA

Hi
On OIA, we know that workflows are triggered when roles are created or modified.
I wondered if the workflows are also triggered when roles are imported instead of vbeing created through the OIA GUI?
Up to now, I saw that the workflows work only when roles are created or modified through the gui. Is it the correct behavior or must the workflows also be triggered when roles are imported?
Thanks in advance
Dali
Edited by: 877567 on Aug 9, 2011 7:05 AM

If the user is not exist, the import process will skip the user, and you'll see a related warning message.

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

Import Manager vs LSMW

Hello,
Since I started to learn SAP I've been seeing many different solutions to the same problems, but always with some added value in the newer of them. The question is: is MDM import manager supposed to be a replacement to LSMW? if not when should the late be used?
Best regards,
Younos Aboulnaga

Hi Younus
There is significant difference between LSMW and Import Manager. Although both follow the same concept of "Importing" data.
LSMW -
1. The full form of this is Legacy System Migration Workbench
2. The transaction code is LSMW and is executed in the SAP ERP system.
2. This is used to import - Master and Transaction data from legacy systems (in text format) into the SAP ERP systems (like ECC, etc).
3. This is a "workbench" that consolidates 4 methods of importing (master and transaction) data as mentioned below:
    a) Direct Input - Uses SAP provided standard programs for importing data.
        The data is imported in the SAP tables directly and hence is the fastest method.
        This must be the most preferred mode of importing data provided SAP has given standard programs.
    b) BDC - You need to create Batch import programs for specific SAP transactions to import the data.
    c) BAPI - Uses SAP provided standard BAPIs to import data.
    d) ALE/IDOCs - Use the ALE mechanism to import data via IDOCs.
MDM Import Manager -
1. This is a component in the SAP MDM suite of components used to import "master data" into the MDM repository.
2. There is no transaction code for the SAP MDM components (Console, Import Manager, Data Manager, Syndicator).
     Infact there are different applications (executable programs).
2. The import files can be XML or Text.
    It's possible to "push" data into the MDM repository using APIs and completely eliminate the middleware (NOT recommended).
Commonality in concept between the two are:
a) Both "import" data in the respective systems.
b) Source structure - Destination structure mapping
c) Field mapping
d) Value transformation & mapping
Hope this clarifies.
Regards
Neelesh

Workflows in HR: Training and Event Management (BO PDRELA_025)

Hi expert!
I have a problem in the context of SAP HCM Training and Event Management and the generation of a workflow event for BO PDRELA_025!
I have created entries in table T779X (through SWEHR3) as:
E 1001 A025 * BOKF 0 PDRELA_025 REQUESTED
E 1001 A025 * BOKP 0 PDRELA_025 REQUESTED
E 1001 A025 * BOKW 0 PDRELA_025 REQUESTED
E 1001 A025 * CNOW 0 PDRELA_025 DELETEREQUESTED
E 1001 A025 * CPRB 0 PDRELA_025 DELETEREQUESTED
...but as soon as it calls function RH_OBJECTKEY_BUILD, it fails and doesn't create the REQUESTED event.
As the key field for AttendeeID in object PDRELA_025 references OBJEC-REALO, function RH_OBJECTKEY_BUILD tries to find a corresponding field in structure PPKEY to create the object key. As it can't find this field in PPKEY, it fails and doesn't create the REQUESTED event. Is there something I've done wrong?
Can anybody help me please?
Michael

Hi Rick,
Thank you for your help.
The problem occurs in function module RH_OBJECTKEY_BUILD. Following raise is the problem.
    loop at bor_keyfields where bor_object_type = bor_object_type.
      read table structure_key with key
                               fieldname = bor_keyfields-reffield
                               binary search.
      if sy-subrc = 0.
        bor_objectkey+bor_keyfields-offset(bor_keyfields-ddlength) =
        hr_record_key+structure_key-offset(structure_key-leng).
      else.
*     FATAL ERROR!!!! BusObjectKey do not refer Infotypekey of DDIC!!!
        raise problem_to_build_borkey.*
      endif.
    endloop.
If found SAPNote 1066444 but the recommanted SP is already imported?!
Can you help me??

IPhoto 08 and Photoshop - suggestions on workflow and managing PSD files

Hi Everyone,
I'm a long-time Photoshop user, and a recent convert to Mac (BTW - I love my new Mac), therefore I am also new to iPhoto 08. I must say that I actually enjoy how iPhoto manages my pictures, as it is not all that different from how I've been managing my pics manually for years (by year, by event, etc.). I've read the various discussion topics on how to set up and use Photoshop as an external editor from iPhoto, and have not had any problems up to now.
I'm now looking for suggestions on workflow and managing my PSD files. I apologize if this is a little long, but I want to make sure I explain the problem clearly. Here's the scenario:
- From iPhoto, I choose to edit an existing JPEG file in the external editor, Photoshop.
- I perform my edits (including advanced edits with layers etc.)
- I do both a "Save As..." and a "Save". That way, I "Save" the flattened JPEG back to my iPhoto library properly, and "Save As..." a PSD file in case I want to do further edits on the image later (days, weeks, months later).
I'm looking for suggestions on where to put my PSDs. For now, I am saving the PSD to my desktop (using max compatibility), and then importing the PSD into my iPhoto library (into the same Event as the original JPEG). However, this leaves me with 2 copies of the same picture: 1 JPEG, and 1 PSD.
The problem is, I now want to go back and do more tweaks on the PSD, the end result of which will make the JPEG version out-of-date. I can either
1) Open both the PSD and JPEG versions at the same time, tweak the PSD, then copy and paste the flattened layers on top of the JPEG version and "Save"
2) Open only the PSD, tweak, and save a copy as a JPEG onto my desktop and re-import into iPhoto.
Although a little tedious, both options seem to work. Are there any other options? What do you suggest? I'm curious to see how others manage this.

I don't have a solution for you (sorry) but I'd like to comment because I'm in a similar boat. However instead of saving PSD files to the desktop, I've been advised to save these to TIFF format in Photoshop by a professioal photographer friend of mine (I think he feels its a more universal file format than PSD for archival purposes). The downside is the files are huge.
I imported high resolution jpegs into iPhoto. I then use Photoshop to edit and save the flattened jpeg version back to iPhoto (thankfully, keywords are preserved this way). I recently realized that I need to save a copy of the edited file in a lossless format like TIFF or PSD. Unfortunately when I save the file to TIFF and import it back into iPhoto, keywords are lost. This is a drag.
What I am trying to figure out is how I can retain my keyword info in the edited archival version. Any tips?
I'm beginning to question whether I should import my photos in to Photoshop (or PS Bridge) first, save the original for archival purposes, do the majority of editing and save a TIFF/PSD file and then import this file into iPhoto for keywording, further editing, downsizing, etc.

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

Import Manager Usage : Approaches for developing Import file structure and text validations

Hi Experts,
We are having 50+ import maps. We have provided option to users to drop the files for data import. Currently Import Manager(7.1 Sp08) does not have capability of pre-import validation of file data such as
a. file structure - number of columns specific to import map
b. file text validations - special characters, empty lines, empty cells
c. Uniqueness of the records in the file
For this, we are planning to build temporary folder(port specific) in which user drops in the file. We use the custom development to do above mentioned validations and then move the files to actual import ports.
Please let us know if you have worked on similar requirements and how you have fulfilled such requirements.
Regards,
Ganga

Hi Ganga,
Assuming you have a well defined xsd and are getting valid xmls from source in the Inbound Port of MDM. Also,you have a Primary key in form of External ID (say).
So just by making and defining a XSD you get most of what you want in your questions a and b.
Now if you wish to use PI to drop files in the inbound port then you can build all the validations in PI itself and you would not need Staging table.
Otherwise,you can have another table (preferably Main table) in the same repository or other dummy repository where records are created on import based on External ID.
Here you can launch an MDM workflow on import of these records and run assignments to replace unwanted characters and Validations to give error for rejecting some records based on the data quality level desired.Once unwanted characters are removed and data is validated it can be syndicated using a syndication step in the Workflow.So records which fail are not sent and which pass are sent to a outbound port.
From the outbound port PI or some other job can pick the file from this outbound folder and drop to Inbound folder of the same repository which imports to the required Primary Main table.Here again you have the option to leverage validations in PI and further check if data is fine.
Once this activity is done you can delete the records from the staging table.
Thanks,
Ravi

Import Manager and Display Fields

I've been using SRM-MDM 3.0 for a couple of months and 1 fundamental MDM design has always bothered me and I was hoping to get some resolve on this.
The purpose of Display Field is 2 folds:
1. Display the field in the Catalog Search UI for a lookup table: i.e. if both Supplier Name and ID are Display Fields, then in the Search UI, both fields are displayed to the end-user. If only Supplier ID was the display field, then in the UI only the ID is displayed.
- From a usability pov, tables such as Supplier and Product Group should have the name or description fields displayed in the Search UI as the numeric values are meaningless to the end-users.
2. Display field ALSO affect what is the key used to import data into a table. So if Supplier ID is the display field for Supplier table, then in Import Manager, the Supplier ID values are displayed and must be mapped to the source values.
- From an importing pov, mapping values should always be an index-like field, such as Supplier ID or Product Group ID, or ISO, and usually never the actual name or description field.
But SAP has tied the two together. So in order to display the name/description to the end-user, we must enable the name/description field as a Display Field. But we also want to map based on the index/ID field, so we also enable the index/ID field as a Display Field. Now in Import Manager, we have two Display Fields for a table (i.e. Supplier ID and Supplier Name for Supplier table) and I've noticed some issues with this:
1. You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible. What is funny is that standard SAP extract program only extracts the ID fields, BUT the standard SAP repository has the name/description fields as the Display Field. Automap is a must for tables like Product Group where hundreds of lines can make manual mapping a pain.
2. I also noticed you cannot Add values to a table that has 2 Display Fields, you can only map to existing values. The Add button is grayed out.
With all that said, when you're replication ECC Contract Data using MECCM, for tables like Supplier and Product Group, what fields should be set as Display Fields, and if there are multiple Display Fields, what special setting needs to be done in Import Manager to enable automapping? Even standard SAP Import Map (_MDMContractDataTransmission_ProductID) throws errors when multiple fields are set as Display Fields.
I'm not familiar with the partitioning function, and I've seen PDF's about it, but don't really see how it could be helpful. I've also read someone suggesting changing the DF's before import, which I think is unacceptable, as this requires unloading/loading repositories everytime an import happens.
Thanks for reading my paragraph and any input is greatly appreciated.
Edited by: Derek Xu on Apr 30, 2009 6:50 PM

Hi Derek,
Thanks for writing your thoughts. I would like to provide some information on one of your points where in you have mentioned that :
You import file must have BOTH values (index/ID and the name/description fields) in the source, in order to Automap. If your source file only has 1 field, like in MECCM when extracting ECC contract, ONLY the Supplier ID, or Category ID is extracted, Automap is not possible.
I completely agree that if you have 2 fields in MDM repository and you are only importing only one of them, then you cannot use the Automap feature of Import Manager. So in your case, the description is not getting importing, so you cannot use Automap in that case.
I had a very similar requirement in one of my project and we went with creation of a Import Value template. We created a template with all the possible values for all the look up tables in that and mapped it once in the Map. Hence, next time, the Map was used to automatically Map the source and Destination values for all the look up tables.
SAP-MDM Automatic Import Requirement u2013 Creation of a Value Mapping Template:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ad0cff-19ef-2b10-54b7-d4c7eb4390dd
Please read the above article and hope its useful. You can go for this approach in your case if suitable.
I have mentioned examples of descriptions and their respective fields in the article.
Hope it helps.
Thanks and Regards
Nitin jain

MDM Maps in Import Manager crashes and does not open

I am having problems with some of my maps in the Import Manager. While working in the Import Manager the maps are fine and I am able to import the data, but once I exit out of Import Manager and try to open the same map, it crashes and closes the application. I am not sure what the issue my be. Could it be the fields I am mapping to are creating a conflict somewhere? Has anyone encountered the same problem. Any insight on this issue would be greatly appreciated. Thanks!

This was happening to me as well. Basically, the data I was submitting was much too large for MDM to handle which resulted in a timeout. To resolve this, I copied my data to temp tables to minimize the number of records I was sending it. After my experience with Import Manager, I think it's safe to say that it was not intended for large data loads. In the future I will be using Import Server and translate my data to XML.

Workflow and Import Manager

Similar Messages

Maybe you are looking for