SLO and data conversion

I read thru the guides for SLO and get the impression that SLO can be used to do data conversion.
For example, it can convert an Oracle DB based non-SAP system into an SAP client.
Is this true?
Our company hires tons of high level consultants to convert non SAP HR systems into SAP HR
systems.
With the magic box SLO, all consultants are no longer needed?
Thanks!

SLO helps us to convert Object's Values which are no longer required or needs to be modified to harmonies the system.
For e.g. in 2012 we had Sales Orgs BBS, BBK, JJG etc. and now we want to merge these orgs to meaningful Org like BB01 and BB02, then this can be achieved by SLO.
SAP will help you to achieve this. SLO team will run the Programs on your production systems, and it will change the values on table level.
We on the other hand need to adept the custom conversions if any. And validate the data after conversion.
In your case, I don't think SLO is helpful.
Thanks,
Jaydip Patel

Similar Messages

Rounding Differences between TSQL Cast and Data Conversion component

This is using SSIS 2012. We are using an Ole Db Connection manager using the Microsoft.ACE.OLEDB.12.0 provider.
I have an Access database (accdb). It has several columns that are coming into SSIS as real data types. One column has a value of 68.8335558900872.
In the past we used the Data Conversion to convert from real to numeric 18, 6. The result was 68.833555. Rather than rounding on the last decimal place, it is returning the floor at six decimal places.
We have converted the process to load the data into a real data type column and then use a view to cast the value to a Decimal 18,6 (CAST (Col1 as Decimal(18,6))). We then load the data into a decimal 18,6 column. The result is 68.833556, which
is the rounded version of the real value.
Personally I prefer the rounded version rather than the truncated version.
I am trying to explain to explain to the QA people why the revised process is producing different results and thus I want to know if these are known behaviors for TSQL Cast and the Data Conversion component.
Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com

I think such a post is more suitable for an MS Connect bugs section as I see it a defect. And it seems no floor, but simply cutting off. Try in .Net when you convert, does it work the same? Data Conversion is a wrapper around the .net
Arthur My Blog

Data Conversion for BOMs and/or Routings

I am looking for any examples for design spec for Data Conversion of Bill of Materials and/or Routings.
Not sure if this would be in form of MD050 but any example would be appreciated

Hi;
Please check below links:
Oracle Bill of Materials User's Guide
http://download.oracle.com/docs/cd/A85683_01/acrobat/115bomug.pdf
http://horizon.more4apps.com/doco/BMWRelease/output/index.htm
Also see:
Getting Started With R12 - Discrete Manufacturing Support Enhanced Release Content Document [ID 415922.1]
Regard
Helios

Data Conversion and Derived Column issues

I have a strange issue occurring with one of my SSIS packages.
What needs to happen:
I have to read data from a table that stores a field in NCHAR(40)
Send it through a Data Cleansing SSIS Component that forcefully outputs the data at a cleansed state as DT_STR(50)
Update the same source table with cleansed data - Using an UPSERT third party tool
Of course, I can't update the tables that stores data in NCHAR(40) with data from DT_STR(50), so I'm trying to use the Data Conversion Component, the Derived Column Component or a combination of, to set the data to DT_WSTR as well as to set the correct length,
from 50 to 40.
The Data Conversion Component fails when I try to set the incoming data (DT_STR(50)) to DT_WSTR(40):
[Data Conversion [186]] Error: Data conversion failed while converting column "MD_Address1" (97) to column "_MD_Address1" (190). The conversion returned status value 2 and status text
"The value could not be converted because of a potential loss of data.".
Now I tried the same thing with the Derived Column Component, converting the data from the DQS component from (DT_STR(50)) to DT_WSTR(40) and there's the error message:
[Derived Column [196]] Error: The "Derived Column" failed because truncation occurred, and the truncation row disposition on "Derived Column.Inputs[Derived Column Input].Columns[_MD_Address1]"
specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
I also tried a combination of Data Conversion (From DT_STR(50) to DT_WSTR(50)) and a Derived Column just casting to the correct size, but that didn't work either.
Every time I try to change the size, one of the components fail.
It appears that my issue has nothing to do with the data types, but the actual data length.
Why can't SSIS CAST my input from 50 to 40?
What do I need to do to cast/convert data from DT_STR(50) to DT_WSTR(40)?

Hi IgorSantos_FL,
It is the expected behavior when we try to convert DT_STR(50) (means maximum 50 characters in the value) to DT_WSTR(40) (means maximum 40 characters in the value). However, the truncation issue should not occur if you convert DT_STR(50) to
DT_WSTR(50). Could you post the error message that you received when converting DT_STR(50) to DT_WSTR(50)? It may be a different issue.
Regards,
Mike Yin
TechNet Community Support

Data Conversion - BP and Item

Dear all,
Would like to ask for the advice of Data conversion of BP code and Item Code.
Any guideline ?
i know it is not suggested to do so, but i really need to change the bp code and item code.
Thank you very much

Hi Tac,
once journal entries are linked to any master data, the code cannot be changed anymore. If you are just implementing & have a very low number of transactions, you might consider creating a new database using copy express & then just import your amended codes & start working with tha new db.
Alternatively, you could group all the 'old' codes in an appropriately named BP/item group (e.g. DoNotUse_BP) & mark them as 'on hold'. Then create new master data with the correct codes use opening balances. The master data could carry a header udf where the old & new codes are referenced.
If you do this, be careful if you use FIFO items, you might want to import the already posted transactions using the now item codes to recreate the layers, instead of starting with 1 opening layer.
All the best,
Kerstin

Data Conversion: LSMW and CATT

Hi Experts
I am plaiing to use LSMW and CATT in data conversion for PP objects.
Can somebody provide me training material on how to record and use these tools.
Any help will be appreciated.
Thanks
Gaurav

hi,
catt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erpfi/catt%2b-%2bcomputer%2baided%2btest%2btool
http://help.sap.com/saphelp_nw04/helpdata/en/74/17f6eaecf511d2bdd4080009b4534c/frameset.htm.
lsmw:
http://help.sap.com/saphelp_nw04/helpdata/en/87/f3ae63e68111d1b3ff006094b944c8/frameset.htm
reward if useful,
thanks and regards

Planning and Scoping- Data conversion and testing

hello Gurus
Good people i'm looking for your help in these areas.....
1) Planning and scoping for data conversion....we will be in the process of acquiring information from the client soon. So, what sort of information or questions do i need to get from the client and also the plan needed?
2) Test planning...... things i need to get from the client to prepare for this plan???
thanks
rasham

Hi,
the question which ou have asked is really very broad. so let me give some idea regarding the planning of data conversion. first of all you should identify which all objects you want to be transfered to SAP, obviously In MM material master, inforecord source list e.tc. then you need to decide which SAP tool you will be using to upload these data like LSMW, CATT e.t.c.
once it is decided what and how you are going to transfer then comes the Functional spec for data conversion in which you will give the details of data mapping in SAP. these FS will be translated to Tech Spec by technical consultant.
Test Planning,
first of all you will decide what type of testing you want to cary out like String test, Unit test, and integration test but these are decided by the testing team not Func consultant but anyway once it is decide how many level of testing is carried out then as a func consultant you will have to create test scenario for integration testing,
Regards
Vikrama

SLO in HR data Conversion

Hi All,
Is there any specific role defined for using SLO in HR data conversion?, if so which are the areas we should consider in using SLO?
Thanks!
Joe

Hi Joe,
Yes SLO has some services in regards HR data.
Please check the link to get further informaiton
https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000587352006
Regards,
Vishwa.

XPath and dom4j xs:date() conversion exception

Hey all Java folks
I'm having a hard time deadling with XPath and date datatype using dom4J and seeking for guidance :)
Let say I have the following XML header:
<site:Blog xmlns:site="http://xml.netbeans.org/schema/blog" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:schemaLocation="http://xml.netbeans.org/schema/blog blog.xsd">and this expression :
site:Blog//site:Entry[@date=xs:date('2007-09-07')]In XMLSpy I do get correct results but in my java code all I get is this exception:
org.dom4j.XPathException: Exception occurred evaluting XPath: /site:Blog//site:Entry[@date=xs:date("2007-09-07")] Exception: No Such Function xs:date
at org.dom4j.xpath.DefaultXPath.handleJaxenException(DefaultXPath.java:374)
at org.dom4j.xpath.DefaultXPath.selectNodes(DefaultXPath.java:134)
at org.dom4j.tree.AbstractNode.selectNodes(AbstractNode.java:166)
at com.mor.blogengine.util.xpath.SearchEngine.getEntriesforDate(SearchEngine.java:142)
at com.mor.blogengine.util.xpath.SearchEngineTest.testGetEntriesforDate(SearchEngineTest.java:120)Does anyone has a clue of why it works perfectly outside of JAVA but not within my code ?
Any enlightenment is welcome! :)
Laurent

String xPathExpr= "/documentFiles/documentFile[xs:date(documentDateXML) > xs:date(\"2005-05-21\")]";should of course be
String xPathExpr= "/documentFiles/documentFile[xs:date(documentDate) > xs:date(\"2005-05-21\")]";

Pdf portfolio source file name and date in file details

Is it possible to import the source file name and extension as well as the source file created date in the portfolio file details? Need to document source to portfolio in working with 3rd parties that will only have the original source. Need to document what was converted into pdf as not all files in a directory will successfully convert to pdf. Sometimes need to convert 100's of files. Manual entry is inefficient. the file names and modified dates are displayed on the Combine Files dialog. is there a way to capture the detail on that page?

I don't need the detail of when the pdf was added to the portfolio. I
need know which dwg or jpg or word file was converted and the original
created date of that file for control of information.
That is impossible; sorry. For some *very specific* types of conversion to PDF the pdfx:SourceModified XMP tag will be set to show the last-modification date of the source file (for example DOCX files converted using MS Word), but there will never be a human-readable record of the source filename or its creation date unless you have manually added them as document XMP properties after conversion (this is what the "Custom Properties" dialog is for). To embed source data automatically would raise no end of privacy and security problems for customers, who most certainly do NOT want their recipients seeing details of internal documents.
Without writing a plugin there's no access to the internal workflow of the Combine Files dialog, so you cannot use a script to read the names and dates of the files *before* conversion and store them automatically in the new PDF Portfolio's Fields array.

Not able to convert string attribute to number and date please help me out

not able to convert string attribute to number and date attribute. While using string to date conversion it shows result as failure.As I am reading from a text file. please help me out

Hi,
You need to provide an example value that's failing and the date formats in the reference data you're using. It's more than likely you don't have the correct format in your ref data.
regards,
Nick

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

GL Data Conversion from Legacy to Oracle EBS

Hi All,
I am tasked with converting legacy data into GL. I have worked on other conversions like supplier, AR and AP conversions but never worked on GL conversion, so I don't know how and where to start, what are the pre-requisites for entering data into gl_interface table how to ensure that data is correct in the .csv file etc.
Kindly request you all to guide me in right direction. Hope to hear from you all very soon!!! :)
Regards

Hi,
When you talk about GL-Data it is the trial balance to be loaded from legacy to oracle applications.
You can use Web-ADI to upload it ,the check list are
The balance for each account comibnation in the legacy system to be mapped to GL-Oracle code combination balance
With respect to open AR, AP Invoices if the invoices are converted using a control account for migration in GL then
the the balance transfered from AP,AR need not be reversed in GL from the source receivables and payables.
In case if the same account combination are for migrating the balances from AP,AR to GL ..Then the balances transferred from AP,AR should be reversed ..so that it does not affect the TB-GL-Balance
Finally ensure that the balance for the TB-tallys with your legacy system and upload it using Web-ADI ,import and
review and post it.
Hope this points helps your GL-Data conversion.
Regards,
Ramaa

Data conversion strategy for new SOB

Dear Viewers
on 11.5.10
We are creating a new SOB with a change in currency from Feb-11 as this is the requirement
For the same, we need to do data conversion.
I have a confusion for Purchase Orders and Sales Orders
Purchase Orders:
Open purchase orders will be converted, means the unfulfilled PO`s i.e the ones not received and are fully open.
The PO`s which have been recieved but not delivered, Requested the users to clear the intransit receipts.
The PO's which are partially received, what to be done for them?
If a PO is fully received and Delivered will not me converted to the new SOB as its not an open PO
but If invoice comes after Feb-11, than how the matching will be done?
What if a return has to be made moving forward in FEB-11 under new SOB
Sales Orders:
Open sales orders will be converted, that is the ones that have been entered and not yet booked.
Users have been requested to clear off the Sales order lines which are already pick confirmed but not yet shipped, hence they will be shipped and interfaced to AR
For the Sales orders that have been booked, those lines that are not yet processed further will also be converted.
Now what if a receipt comes after feb 11, how to handle this as the sales order wiould not have been converted?
Please give your advise on the data migration strategy for PO`s and SO's.
Please do add any point that may have been missed by me
Appreciate your help
Thanks
Emm

Hi David,
for master data conversion you can use LSMW and the RE-FX BAPIs. (please refer to SAP note [782947|https://service.sap.com/sap/support/notes/782947] ).
Regards, Franz

Data conversion for new sob

Dear Viewers
on 11.5.10
We are creating a new SOB with a change in currency from Feb-11 as this is the requirement
For the same, we need to do data conversion.
I have a confusion for Purchase Orders and Sales Orders
Purchase Orders:
Open purchase orders will be converted, means the unfulfilled PO`s i.e the ones not received and are fully open.
The PO`s which have been recieved but not delivered, Requested the users to clear the intransit receipts.
The PO's which are partially received, what to be done for them?
If a PO is fully received and Delivered will not me converted to the new SOB as its not an open PO
but If invoice comes after Feb-11, than how the matching will be done?
What if a return has to be made moving forward in FEB-11 under new SOB
Sales Orders:
Open sales orders will be converted, that is the ones that have been entered and not yet booked.
Users have been requested to clear off the Sales order lines which are already pick confirmed but not yet shipped, hence they will be shipped and interfaced to AR
For the Sales orders that have been booked, those lines that are not yet processed further will also be converted.
Now what if a receipt comes after feb 11, how to handle this as the sales order wiould not have been converted?
Please give your advise on the data migration strategy for PO`s and SO's.
Please do add any point that may have been missed by me
Appreciate your help
Thanks
Emm

emm wrote:
Purchase Orders:
Open purchase orders will be converted, means the unfulfilled PO`s i.e the ones not received and are fully open.
The PO`s which have been recieved but not delivered, Requested the users to clear the intransit receipts.
The PO's which are partially received, what to be done for them?
If a PO is fully received and Delivered will not me converted to the new SOB as its not an open PO
but If invoice comes after Feb-11, than how the matching will be done? <br>Business needs to take a decision whether they are fine with matching the POs manually (i.e. referring the documents and verify), in this case you may capture the PO information in a DFF in the Invoice distribution. Otherwise if it has to be converted identifying the POs under this scenario, you may consider converting those maintaining receipt close tolerance as 100% and matching type as 2 -way (again business approval needed to handle audit issues) in order to avoid the receipts/delivery conversion etc.<br>
What if a return has to be made moving forward in FEB-11 under new SOB<br>Ideally returns can be done using Miscellaneous/Account Alias Issues specifying the appropriate transaction reasons to clarify the scenario.<br>

SLO and data conversion

Similar Messages

Maybe you are looking for