Validation rules applied to data migration templates at import

Hi everyone!
First post here for me, so please bear with me if I missed something.
My company has just started the initial implementation of ByDesign. We come from a set of disparate and partially home-grown systems that we outgrew a few years ago.
As part of this initial phase, we are basically re-creating the data on customers, suppliers, etc. since none of our existing systems makes a good source, unfortunately. We will be using the XML templates provided by ByDesign itself to import the relevant data.
It has become clear that ByDesign applies validation rules on fields like postal codes (zip codes), states (for some countries), and other fields.
It would be really helpful if we could get access to the rules that are applied at import time, so that we can format the data correctly in advance, rather than having to play "trial and error" at import time. For example, if you import address data, the first time it finds a postal code in the Netherlands which is formatted as "1234AB", it will tell you that "there needs to a space in the 5th position, because it expects the format to be "1234 AB". At that point, you stop the import, go back to the template to fix all the Dutch postal codes, and try the import again, only to run into the next validation issue.
We work with a couple of very experienced German consultants to help us implement ByDesign, and I have put this question to them, but they are unaware of a documented set of validation rules for ByDesign. Which is why I ask the question here.
So just to be very celar on what we are looking for: the data validation/formatting rules that ByDesign enforces at the time the XML data migration templates are imported.
Any help would be appreciated!
Best regards,
Eelco

Hello Eelco,
welcome to the SAP ByDesign Community Network!
The checks performed on postal codes are country specific, and represent pretty much the information that you would find in places like e.g. the "Postal Codes" page in Wikipedia.
I recommend to start with small files of 50-100 records that are assembled of a representative set of different records, in order to collect the validation rules that need reactions based on your data in an efficient way. Only once you have caught these generic data issues, I would proceed to larger files.
Personnaly I prefer to capture such generic work items on my list, then fix the small sample file immediately by editing, and do an immediate resimulation of the entire file, so that I can drill deeper and collect more generic issues of my data sample. Only after a while when I have harvested all learnings that were in my sample file, I would then apply the collected learnings to my actual data and create a new file - still not too large, in order to use my time efficiently.
Best regards
Michael

Similar Messages

Data Migration Template for Singapore Payroll.

Hi
I need a help on data migration template for Singapore Payroll.
Would also need guidance on what i srequired in case i want to migrate the last year payroll cluster data from legacy system to ECC 6.0.
Will appreciate if you can send me the migration template at my mail id.
Thanks and regards

Hai..
Check some of the fields mentioned below.. it may be of some use to u..
Client
Personnel Number
Sequential number for payroll period
Payroll type
Payroll Identifier
Pay date for payroll result
Period Parameters
Payroll Year
Payroll Period
Start date of payroll period (FOR period)
End of payroll period (for-period)
Reason for Off-Cycle Payroll
Sequence Number
Client
Personnel Number
Sequence Number
Country grouping
Wage type
Key date
Rate
Number
Amount

CRM Masterdata and Data Migration Templates

Could some one please provide me the below templates if you have any...
- CRM Master Data Mapping Template
- CRM Data Migration Design Template
- SAP CRM Data Design Template
Really appriciate your help...
Thanks in advance..
Sr

It is a duplicate one... so just marking it as answered because I could not find the option to delete.

IS validation rule export to Data Services invalidates datastore logon details

I am exporting an Information Steward 4.2 SP1 validation rule to Data Services 4.2 SP1; a part of the rule is a database table lookup. In the export process, IS creates a new datastore with that table I'm doing the lookup against.
The problem is that every time I re-export the rule after changing it, I have to maintain db server logon details in that generated datastore again.
Have I missed a configuration step, or it's just an error to raise through OSS?

Hi Apurva ,
Now I got Variable Id and Varibale Value i have give From Data Fields of VC .
When i click on Button Export To Excel it gives
SET_VARIABLES_STATE is Correctly placed For
VARIABLE_VALUES VARIABLE_VALUE
if give
VARIABLE_VALUES VARIABLE_VALUE instead of SET_VARIABLES_STATE it is giving No MetaData is available for VARIABLE_VALUES VARIABLE_VALUE
it throws like .
please help in this regard.
I Have given The Formuls AS Below
"pcd!3aportal_content!2fcom.sap.pct!2fplatform_add_ons!2fcom.sap.ip.bi!2fiViews!2fcom.sap.ip.bi.bex?QUERY=zmp_prodn_mtef_ccp_1&BI_COMMAND_1-BI_COMMAND_TYPE=VARIABLE_VALUES VARIABLE_VALUE&BI_COMMAND_1-VARIABLE_VALUES VARIABLE_VALUE_1-VARIABLE_TYPE=VARIABLE_INPUT_STRING&BI_COMMAND_1-VARIABLE_VALUES-VARIABLE_VALUE_1-VARIABLE_TYPE-VARIABLE_INPUT_STRING="&2009&"&BI_COMMAND_1-VARIABLE_VALUES-VARIABLE_VALUE_1-VARIABLE=0P_FYEAR&BI_COMMAND_3-BI_COMMAND_TYPE=EXPORT&BI_COMMAND_3-EXPORT_FORMAT=XLS&BI_COMMAND_3-null="
Regards ,
venkat p

Validation Rules in Standard Lockbox

Hi All,
Can anyone let me know what are the validation rules applied when transferring data from AR_PAYMENTS_INTERFACE_ALL to AR_INTERIM_CASH_RECEIPTS_ALL and AR_INTERIM_CASH_RCPT_LINES_ALL.
In otherwords what are the validation rules appplied when cerating a Quick Cash batch using lockbox.
Thanks,

And can we add the rejected batch if we correct the error and rerun the Process Lockbox program?

Validation Rule not fitting for calculated figure

Hi,
I want to add a validation rule in my data form. My requirement is in the data form I want row value 2 should be greater than (row value 1 * 0.2).
Now when I'm trying to solve this through validation rule I did not found any such condition that fit with this case. Is there any way out for this scenario in validation rule?
Thanks in advance.

Hi. So you have two segments at least in your dataform (row1, row2)
As we can't do math operators with cell's values in validation rules, it looks like you have to create formulae row3 (with hide option)
It is very simple as follows: [1]*0.2
And then you can create your validataion rule:
IF Row value 2 <= Row value 3
Then Process cell ...
Also you may include additional conditions for Missing values in rows 1, 2 if any

Data migration to N97 from Palm

I'm about to take delivery of an N97 and want to know how to go about getting contacts and mcalendar meetings from my Palm into the N97. From various searches i've done this is probably going to be a nightmare, so i'm not hopeful of an easy solution. Want i want is ANY method that will work, however laborious.
suggestions ??
thx
les

Hello Kayal,
We did this for one of our internal Customers.
As mentioned by Ginger, we took a dump of all the Productive data from SF.Com, cleansed it, populated migration templates of Cloud Solution with this data & performed manual load into the Cloud system using the Migration workbench.
Few inputs on this:
1. Data Cleansing will be a task in itself, so make sure you are completely familiar with the Cloud Data migration templates, & read the Introduction sheets & Fields sheet thoroughly before you populate data from SF.com to Cloud templates.
2. Data format has to be maintained as permitted in the templates, refer to the last sheet of the template which you sue for migration for All the fields with their data types & length permitted.
3. Make sure you download Value conversions while you do first time migration so that you can use them later when you do further Data migration, this will save time on converting values again & again while performing uploads.
The other option is to use SAP's Rapid Data Migration services, which is a tool available from SAP which allows you to create mappings between Cloud & other systems from which you want to migrate.
This I believe comes with an additional cost & you would need a proper KT from one of the SAP's experts to use this tool.
I would still suggest go by the manual load.
Hope this helps!
BR
Ankur

DATA MIGRATION - Fails in Cloud for Customer

Hello Community,
I was doing a test load for Marketing lead in Cloud for customer and I am getting following error:
The error - some how doesn't have much explanation.
Can anyone please guide how to resolve the issue and what could be the probable cause for the same?
Awaiting quick response.
Regards
Kumar

Recording the incident is absolutely the right path. Sometimes I get this error when:
There is an updated version of the data migration template.
When I copied and pasted, I overwrote the format of one or more cells in the XML template.
I pasted data into the wrong column within the XML template.
To resolve these issues, I download the newest XML file template from within the system, repopulate the data using and try again. The important thing is to use copy > paste special > values only so that the format isn't overwritten. Also check that the data is in the right columns before uploading.
If these troubleshooting tips don't work, then I have to depend on support's assistance to resolve the error.

ASAP Data Migration / Data Conversion / Data Transfer Templates

Hi,
I'm looking for the ASAP Data Migration / Data Conversion / Data Transfer Templates that used to be available in ASAP.
Some time I ago, and I believe it was on this site and can no longer find it, I found a zip file which contained the above .xls template to manage all the data conversions on a project. Also included was the data mapping template .xls
Many thanks.

Hi,
I'm looking for the ASAP Data Migration / Data Conversion / Data Transfer Templates that used to be available in ASAP.
Some time I ago, and I believe it was on this site and can no longer find it, I found a zip file which contained the above .xls template to manage all the data conversions on a project. Also included was the data mapping template .xls
Many thanks.

How to apply validation rule for View Object (VO) attributes?

How to add Validation Rules to VO attributes, just like EO Business Rules?
I got 2 problem with that:
1. VO can join multiple tables, and the attribute's validation rules may reference to the fields from multiple entities.
2. Since the EO Validation Rules only execute before the data actually write to entity (Commit operation). But user may need to input data from multiple pages with only 1 commit.
I am using JDeveloper 11g with ADF BC.
Regards,
Samson Fu

Just something to point out, the EO validation doesn't fire on a commit (if you mean commit as in the database/AppModule commit). You can also access VO information from the EO validation rules by using view accessors.
Regards
Grant

Validation Rules, No data to validate

Hello all,
I'm trying to setup the Business Rule "Validation Rules" in SAP BPC NW 7.0 but I'm getting a message that says NO DATA TO VALIDATE, I have done the configuration steps such:
1. Add to the Entity Dim the correct OWNER.
2.In BPC WEB ADMIN I changed the WorkStatusValidate to "YES".
3. I changed the Work Status Setting at application level, ith the next parameters:
     ENTIDAD---> owner
     TIEMPO---> yes
     CATEGORIA--->yes,   and the other dimensions as NO
4. I Changed The Work Status Setting at appset level too.
I have edited the Validation Rules as follows:
VALIDATIONACCOUNT        REMARK          VALIDATIONOPERANT             VALIDATIONTOLERANCE
      REGLA1                          ACTIVO                          =                                                   0.01
When I click on Save without validate, there are no problems, but it is happenning When I Click on Validate Validation Rules Rule Table. Have you ever seen this error before?
Thanks in advanced!
REgards!

Hi Miguel,
You are comparing work status and the validation rules. However, these 2 are completely different functionalities.
For maintaining validations, please take a look at the below links from help.sap:
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/72/027eddf803405eb131738b655408ce/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/d9/7e49e5b686462a9f2a2d38c98b8446/content.htm
For work status, please refer to the below links from help.sap:
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/f8/d51b881cfa4c5992de481ccfa05db3/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/75/712b5c7be845cbb1e76cfe78650343/content.htm
Hope this helps.

Filter data by cross validation rules

Hi all,
Is there any way to build report that filter out data by cross validation rules ?
For e.g:
Acc. Flex -> Company.CC.Natural.Future.
The cross validation rules are excluding CC -> 01 and 05.
So all the combination_id that contains CC 01 and 05 will be filter out.
TIA,
Fendy

Perfect! This is how you define cross validation rules. It's not back to front but from R11.0.3, Oracle standard is to use the cross validation rules like this.
- Kiran

Validating accuracy and quality of migrated data

Does anyone have recommendations or suggestions with respect to validating the quality of the data migrated from one database to your Oracle database? Basically I'm looking for suggested steps (queries) to run to verify the accuracy of the data migrated and include those checks in an automated process.
At an entry level I can compare rowcounts between tables and verify they match but I was thinking more along the lines of creating an offset to be more sure about it. For example I can add the sequence number primary key column with another number column(s) and sum that to create an offset that I can compare against the same table in the old database.
I was just wondering if there were any schools of thought or existing routines that anyone had to do some of these types of post-migration quality checks (in a timely fashion). If anyone has any suggestions I would appreciate it?

Hi,
This is one of those "how long is a piece of string" questions. For some people row counts will be sufficient, yet for others they will require that every column in every row can be validated against the original dataset.
The Oracle Migration Workbench does not perform any validation of the data load process. We have had customers request this function and will probably look into this in more detail in the coming year.
The approach you are talking about, by creating a scheme to validate the data in a table using the sum of a column or series of columns, seems like a sensible compromise between simple row counts and complete validation.
Regards,
Blair.

Apply a validation for a "prompt date"

Hello friends.
As I can include a validation to a "Prompt" date. operator is between and.
Basically what I want is to limit the "prompt".
example:
Date between: 01/01/2012 and: 12/01/2012
The date range exceeded 6 months.
Thank you for your cooperation

You will need to do this:
1) You will need to build your between prompt like this:
http://oraclebizint.wordpress.com/2008/02/26/oracle-bi-ee-101332-between-prompts-for-date-columns-using-presentation-variables/
The reason is because we need the PV for the start date and end date. (I call the PVs pv_StartDate and pv_EndDate, respectively in my example below.)
2) Create a small report with 3 columns: one column from your SA, it doesn't matter what; and one dummy column.
3) In the dummy column, click on the fx button, delete the contents and enter the following:
CASE WHEN TIMESTAMPADD(SQL_TSI_MONTH, 6, '@{pv_StartDate}' > '@{pv_EndDate}' THEN NULL END
4) Put a filter on the second column for IS NOT NULL
What this small report does is this: when the difference between the start and end dates is greater than 6 months, then the CASE statement will be NULL and since the filter is only looking for "not NULL" values, the report will return no rows.
5) Now in your dashboard, add a section and put your report in it. In the Section properties, click on Properties>Guided Navigation and point it to the small report "if request returns rows."
6) Add another Section below the one above and this time drag a Text object to the section. Put the text you have: "The date range exceeded 6 months. Please choose a date range within 6 months. Thank you."
7) On the Section properties of this one, click on Properties>Guided Navigation and point it to the small report "if request returns nothing."
I think you get the picture. When the date range exceeds 6 months, the top section does not appear; instead the user sees the text to change the date range.
That should resolve your issue.

SAP HR Data Migration Strategy

Hello Guys,
I worked in Data migration in the areas like SD,MM,FI. But I am new to HR. Can anybody please give me the HR data migration stratagey like what data's (eg, Master ,transactional etc) we need to load and sequences and methods available for each type?
Thanks
Kal

Hi chakri,
Documentation we use is Data Convertion Bueprint which is simply customer's requirements accroding to what infotypes he needs, what data should be migrated and which org. elements will be imported.
Another one is Master Template which is actually prepared by us (technical team). We prepare LSMW for each infotype mentioed in former document, then we document it in this master template to provide to customer required flat files format. We prepare such becuase sometimes some filed may be fixed, some added and even are read-only so should be skipped. So this document differs a bit with previous one in regards to infotypes' used fields. Than we sent this document to our local functional team which is resposible for providing files with given format.
In first document there are also some Golden rules, which describes exact steps for one entire cycle (staring from deliveirng the file, ending with validation of loaded data for one infotype), which each involed party should follow.
The last but not least important document is what we call Loading sequence. I already described it previously. It is just the order of loading the data to infotypes which you should follow. It also contains such information as
- number of records in provided file
- number of errors, successfully loaded records
- files which we share with functional team (error logs)
- finally files which we sent as validation data (extracted from system after successful load of infotype)
Unfortunatelly I can't provide you any of them as these are company documents which are not to be distributed. Sorry I am not allowed to break this rule.
Anyhow I hope it will give you an overview of what kind of documentation you need. It is of course of your team how you organize your work and documentation.
All in all crucial thing is communication between teams, which from my experiaence sometimes fails.
One more thing:
Always remeber to give points to usefull answers, that's how the forum works. Of course it is not obligatory !
Rememebr if you get something, you appreciate it by assigning points:)
Cheers
Marcin

Validation rules applied to data migration templates at import

Similar Messages

Maybe you are looking for