Data migration of account contract through EMIGALL

hi experts,
i am facing some problem, when i migrate the data of contract account through emigall,problem are-
1) enter the value in account determination id although i have given value in field koiz_sd.
2) Account holder relationship is not uniquely defined
pls reply ASAP
thanx
Pradeep Sharma
Edited by: Pradeep sharma on May 1, 2008 8:09 AM

Hi
1. You need to make sure the fields are entered in the right order in the migration file. If you didn't do it yet, try to generate a test file first using EMIGALL.
2. Make sure you have one account holder for that contract account. You cannot have more than one account holders or not a single one.
Hope this helps. If not, please be more specific.
Bogdan

Similar Messages

Data load of Service Master through Emigall

Hi Fritz,
can we load data for the service master through Emigall.
what are the Pre-requisite for it.
Regards,
Robert

Hello Robert,
I am not sure what exactly you want to migrate. Have you already checked chapters 6.9 - 6.11 in Guideline IS Migration Workbench (transaction EMIGALL).
Kind regards,
Fritz

Issue in data migration of PO contract (Updating table A215)

Hi All,
I doing data migration for PO contract throught BDC, I wanted to update the table A215,
I can't see the field of A215 on PO contract transaction screen (i.e. Transaction ME33K ).
Can anybody tell me how to load the data in A215 thorugh BDC.
Regards,
Sagar

How is this A215 table maintained manually? Thru ME33K or a different transaction like MEK1?
you are saying you do BDC, are yoou using a SAP given report or did you record the maintenance transaction yourself in SHDB?

GL Balances data migration: Vat account

Hello !
I have a question for gurus!
I have to migrate all opening balances.How can I migrate the Vat account ?
many thankss
Giulia

Hi Shekar,
You do not have to do anything in specific to make them zero. Let me explain you with a simple example.
Hope you would agree that your trial balance would be zero at any point of time. Thus, you can derive an equation as follows from your Balance Sheet -
Current Assets (Cash, Bank, AR etc.)
+ Fixed Assets
- Share capital
- Current Liabilities (AP)
- Other Debts
===
0
===
If you convert the above items as upload enteries, you would get the following -
Debit Current Assets
Credit Upload Current Assets GL
Debit Fixed Assets
Credit Upload Fixed Assets GL
Credit Share Capital
Debit Upload Share Capital GL
Credit Current Liabilities
Debit Upload Current Liabilities GL
Credit Other debts
Debit Upload Other debts GL
Thus all your upload GLs also would sum upto zero. Hope I have explained you. Else, please revert.
Regards,
Mike

Data Migration of Contracts with periodic billing and revenue recognition

Hello Experts,
I am trying to develop a legacy data migration plan for Contracts with periodic billing plan and revenue recognition.
Example of the scenario is given below:
Customer signed a contract for one year starting 01/01/2009.
Customer is billed quartely, billed in advance.
SAP going live on 04/01/2009
Customer is billed for 3 months and also for initial set up fees.
Revenue recognition is done monthly.
We have to migrate this contract to SAP.
Billing document posting may be necessay as it affects revenue recognition which spans across the total contract period.
Any ideas how to do this?
Thanks A Lot
Anil
Edited by: Anil Jose on Sep 17, 2008 9:38 PM

Hi Anil
How did you manage this? We also had the same problem in one of our contracts and what we did was that we copied the contracts from the legacy with the full value. That is suppose SAP went live on 1st April, 2009 and the contract was created on 1st January 2009 for a value of suppose 100 USD, with the first billing being done on 1st Jan for 33.33 USD for 4 months. We first created the contract with a validity from 1st Jan 2009 in the new system. We billed it with a billing type that we created that did not actually create new accounting entries as the accounting entries had already been created in the legacy system. In the new system then we recognised the revenue till the go live, so that the actual value remaining of the contract reduced. Then we started the billing plan of the contract from 1st of April 2009 for the remaining amount. So next invoice was created on 1st april for 33.33 USD. Can you share your solution.
Regards
Indranill

Error message while doing data migration

Hi all
When im doing data migration for material master through Z transaction ,it is updating global DIR documents for material while doing this ,im getting the error and the transaction is stopped intermediately the error message is CHANGE MASTER STATUS DOES NOT ALLOW CHANGES no error message number.
Kindly sujjest where is that error is coming,it would be very helpful

It seems you are using engineering change management and your change number's status is not proper (CC01, CC02, CC03; table AENR).
Configuration of the status is in T419S (use SM30 + T419S) - but I guess the problem is about your change number not about config...
How your Z-program is working, we don't know; contact the responsible functional/technical consultants.
Edited by: Csaba Szommer on Aug 19, 2011 8:41 AM

RDS for SAP data migration through IDOC's

Dear Experts
Just now we have installed BODS 4.1 and RDS also installed now. I am in the process of exploring the RDS. I found all the migration objects is available in the form of IDOC's. Now my questions are
How to work on custom IDOC's. Do i need to extensively code on R/3 side to upload the custom fields. Like user exit or BADI for custom fileds
If yes then i would say implementation time through RDS will remain more or less same time.
Through BODS or by RDS migration objects is there any way without coding on ABAP R/3 side, Can we achieve migrating custom fields
Please let me how to achieve above requirements by RDS
Thanks
Vijay Mukunthan

Hi Vijay,
You are right, the standard content of the Rapid Data Migration RDS packages brings the content with the standard IDoc interface for SAP standard only. So custom objects are not pre-built with the package. However, we incorporated the foundation to include custom coding as easy as possible:
1) IDoc
We are using the standard interface technology IDoc. IDocs do have an enhancement concept which is described in the online help. There are three main cases and all of them are supported, however two need additional coding:
Z-fields: Additional fields in existing tables lead to IDoc segment extensions
With the IDoc segment versioning concept this is easy to realize without any ABAP coding
Z-tables: Additional IDoc segments will be necessary and lead to a new IDoc version
With the IDoc versioning concept you can easily add Z-segments with leveraging provided user exits
Custom business objects:
You can even create a complete own IDoc message type in Z-namespace for own stuff, leveraging the given ALE layer of the IDoc middleware
2) Enhancement guide
With the RDS package we offer an enhancement guide which helps you to modify the jobs and data flows in the SAP Data Services content according to the changes in the target IDoc structure to reflect additional fields and tables. We built it as a step-by-step guide following for a sample IDoc type but will work similarly for any IDoc.
Best regards,
Frank Densborn.

SAP, Data Migration Contracts

Good afternoon, I am seeking additional SAP resources with Data Nigration, MTO and ICWC experience. Please could someone advise a reliable source to find the available skills in the current contracting marketplace.

Then my apologies and welcome as a "newbie" to our community. Much information is to be gleaned concerning Data Migration in the website area called: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/developerareas/xi">XI</a>
Also, note that community supports community and members ask questions and "reward" one another for good content.
Generally we try to search or check the site as community members to see if our post has an existing answer.
I was in the middle of this post, when Mark jumped to answer.
Again, welcome and keep posting.
Marilyn

Data migration through IDoc processing in LSMW

Hi all,
I have an requirement wherein i need to transfer material master data through LSMW conversion process into R/3 database.The data is to be posted through ARTMAS04 inbound IDoc.
The problem is to transfer the data simultaneousely through multiple instances of E1BPE1MARAEXTRT segment of ARTMAS04 IDoc.
for example:
I need to have an assignment that should work like this:
E1BPE1MARAEXTRT[]-FIELD1 = '00001'
E1BPE1MARAEXTRT[]-FIELD1 = '76545'
E1BPE1MARAEXTRT[]-FIELD1 = 'SAP'.
Can anybody help me in acheiving this example scenario in LSMW.
Thanks.

HI everybody,
i had solved the problem myself.
Thanks all.

Error in data migration through DTW

Hi All,
      I am creating a template for user define Master data table from DTW, when i am trying to port data by using that template through DTW. it is giving error like--'Master data type User table cannot add row'
So can any one have solution for this.
Regard's
Hari

hi,
object name is U_SCRAPMAST
Code     Name     U_SCD     U_SDSC     U_Status
Code     Name     U_SCD     U_SDSC     U_Status
1          SCR1     SCR1
2          SCR2     SCR2
regard's
Hari

Data Migration from Legacy System in IS-U

Hi All,
We are going to Implement a new IS-U project, I have a problem with LSMW(Legacy System Migration Workbench ), I have some Conversion Objects of IS-U and I need to know whether Data Migration is possible or not, please tell me how to find these Objects and how to know Data Migration is possible or not.
Objects are like.,
1. Accounts
2. Actuate Reports
3. Business Partner Relationships
4. Active Campaigns/Campaign Content/Dispositions
5. Connection Object
6. Contacts
7. Contracts
8. Opportunities
9. Payment Arrangement History
10. Payments
11. Premises
12. Rate Changes
13. Security Deposits
these are few and there are some more..,
Thanks in Advance,
Sai.

Hi Ram,
Use Transaction Code EMIGALL. It will ask for company code. By default Company Code is SAP. If you entered with the SAP you will get all the objects.Then goto menu IS-U Migration-->User Handbook. It will give you details Idea.
Also Check the following Procedure
You can find detailed documentation of EMIGALL in SAP itself. Use Transaction EQ81 to display it. It provides all the concepts and procedures to work with EMIGALL.
Here are some points about EMIGALL :
1. It Migrates data Business Object wise
2. It uses Direct Input Technique
3. It has more than 100 objects of IS-U
and the steps for implementation goes like this:
1)You have to create a user specially for migration which will have all the authorizations related to migration workbench, BASIS and IS-U
2)You have to create your own company in EMIGALL. There is a default company called SAP.
3)Company SAP contains all the Business Objects
4)You have to figure out what business objects u need and then u have to copy those business objects to ur company from Standard Company SAP
5)Each objects contains more than one structure and each structure can contain more than one fields. The relation goes like this
Object ---> Structure ---> Field
6)You have to define field rules for each required field of the object. You have to mark "Not required" for fields u don't need
7)After field rules for a given object is set u have to generate load report i.e. actual Direct Input Program which will migrate data. This program is generated on basis of field rules set by u.
8)After the load report is generated u have to prepare an input file (import File) for migration. The import file should be according to structure provided by SAP and must be in binary format. SAP Provides the structure of file according to your configurations. You have to write ur own Data conversion program(in any language) for this task.
9)You take import file as input and migrate the data using generated load program
10)Finally u can check the Migration Statistics and Error Log
Thanks and Regards,
Jyotishankar Dutta
Message was edited by:
Jyotishankar Dutta
Message was edited by:
Jyotishankar Dutta

Data Migration of FI-CA Cleared Items

Hi,
Currently I am working on a Data Migration project to migrate data from our FI-CA module on ERP 4.7 to ECC 6.0.
THere has been a request from the business to migrate historical data (e.g. Cleared items).
Is there a SAP recommended approach or tools to load this data into the target environment?
Currently all documentation around SAP data migrations talks about stategies for open item data migration however I have seen nothing arouund migrating historical financial data.
Is this because it is not recommended or technically impossible?
Regards
Adam Gunn

That BAPI is used typically for straight out vanilla GL, AR, AP postings, however you still have to create the other side of the entry and then clear it.
I need to be able to migrate full history, which means from an FI-CA viewpoint:
1. Migrate FI-CA posting of liability against BP/contract account.
2. Migrate associated payments.
3. And then clearing documents.
Basically the requirement is to represent the historical data in the new system as if it was posted and matched off.
Is there a technical way to do this?
OR,
Do you migrate the FI-CA liabilties, then the associated payments and then run clearing on the target system?
I suspect this is almost an impossible data migration requirement as development of the extraction and load process would be extremely complex and testing would take months to cover all posting scenarios in FI-CA. However, I would be interested if anyone has attempted to do this before.
Adam

Data Migration from Legacy System in CRM

Hi All,
We are going to Implement a new CRM project, I have a problem with LSMW(Legacy System Migration Workbench ), I have some Conversion Objects of CRM and I need to know whether Data Migration is possible or not, please tell me how to find these Objects and how to know Data Migration is possible or not.
Objects are like.,
1. Accounts
2. Actuate Reports
3. Active Campaigns/Campaign Content/Dispositions
4. Contacts
5. Contracts
6. Opportunities
7. Payment Arrangement History
8. Payments
9. Premises
10. Rate Changes
11. Security Deposits
12. Business Partner Relationships
13. Web self-service information
14. Usage that has been used for quotes
15. Tax history information, including AXCIS
17. Service Requests
18. Service Order History
19. Security Deposits
20. Reference Values
21. Rate Changes
Can anybody please tell any transaction code in CRM where can I find the Data migration for the above objects is possible or not.
Thanks in Advance,
Sai.

Hello,
for migration into CRM I would suggest the 'XIF-Interfaces'; these are interfaces provided in CRM for connection to external systems. I'm not sure if this will cover all objects mentioned above, but at least some of them should exist.
Some information about existing interfaces can be found in the integration repository under http://ifr.sap.com/index.html; from the start screen first select 'Enter the repository' and then have a look under 'generic components' and 'SAP CRM'.
Regards, Katja Ohliger

Error when Migrating Object ACCOUNT (IS-U / CCS)

Hi,
Can anyone help me regarding the following:
I've already create a BP and now I want to create an account contract related to BP. As a relation between both objects there is a key in TEMKSV ( PARTNER - PAR01 - 6000199066 ).
My object ACCOUNT contains the structures VK_INIT, VK and VKP.
The VK_INIT structure for field GPART is set to PAR01, as also the structure VKP for field PARTNER.
As I push the button "Import Data Object" I get the message "Enter at least one number for the business partner - Message no. R11123".
Thanks for your attention.
Regards,
JMMatos

Hi Fritz,
Hope you are good.
In fact, both structures are populated and specially the field regarding BP with the right value - 6000199066.
For the structure AUTO-VKP there are one single line.
Now, I've just running the migration process and as I display the migration statistics I got one line with an Imported Data Records and no errors:
EDPG ACCOUNT 31.07.2009 09:55:40 001 DIALOG 1 0 0
But, as I look into the KSM list there is no entry for the object ACCOUNT as well as no account contract for the BP.
Another thing, that I've detect is after I've run the migration object if I tried to run the same object with the same file, I see that some lock entries are made for this object.
Thanks for your help.
Regards,
JMMatos

Treasury Data Migration

Friends,
One of our client has decided to use SAP Treasury and Risk Management. I have been asked to lead data migration within this area. For the same, I would like to know the generally used and needed master and transaction data for SAP Treasury Management. Also, let me know the various ways of migrating data into SAP TRM eg. BAPI's, Transaction Manager, LSMW etc.
Regards,
Amey

Hello Amey,
Please find list of steps which might be helpful for data migration.
Legacy Data Transfer
1. Legacy data
transfer always happens on a key date.
2. The procedure is
different for securities and OTC because they deal differently with positions
on a key date.
3. For securities, we
simply need to copy the positions with all values as of the key date.
4. For OTC, the
entire transaction is copied as there is no explicit position management in the
transaction manager.
Customizing the Legacy Data Transfer:
You primarily need
customizing for the update types that the flows of the legacy data transfer
business transactions are to carry. We can find the settings under Treasury and
Risk Management à Transaction Management à General Settings à Tools à Legacy
Data Transfer à Flow Data à Update Types.
The update types are
divided into those for valuation area independent & dependent. The
independent one only relates to securities. à While the legacy data transfer is
usually not intended to update the general ledger, nevertheless you must mark
most of the update types as posting relevant and maintain an account
determination in customizing. This is necessary to ensure that the data in the position
management is complete and in particular the account assignment reference
transfers can be performed correctly.
Legacy Data Transfer for OTC:
Step
1: Existing OTC transactions enter the same way as new transactions.
Enter either manually (or) use existing BAPIs to import them. BAPIs list à Use
BAPI_FTR_FD_CREATE & BAPI_FTR_FXT_CREATE
for creating FD & FOREX transactions respectively. Similarly there are many
BAPIs for each product and we can get the list of BAPIs in BAPI transaction code
under the node Financials à Financial Supply Chain management. Use FTR_BAPI
Transaction to test run the Treasury BAPIs.We may define separate transaction
type for legacy transactions so that settlement (or) posting release is not
necessary.
Step 2: Now we must change status of all the historical flows
created in Step 1 to POSTED without actually generating accounting document. To do this we will use transaction TBB1_LC.
This is similar to transaction TBB1. Unlike TBB1, TBB1_LC affects all the valuation areas without giving an option to affect only operational area. We can see the posted flows by TBB1_LC in posting journal (TPM20) without any reference to accounting documents.
Step 3: Till now the historical flows do not yet explain the book value of OTC transactions. Hence we must first enter the historical valuation results. This is done using TPM63C which you can find under path Treasury and Risk Management à Transaction Management à General.Settings à Tools à Legacy
Data Transfer à Flow Data à Enter Valuation Area Dependant Data for MM.After entering the
valuation results use TPM63 to transfer values to Internal Position Management.
Legacy Data Transfer for Futures & Listed Options:
Step 1: Similar to OTC
Step 2: Similar to OTC
Step 3: Use transaction TPM63D (Valuation area dependant data for futures). We must establish the relationship between lot & the transaction on which it is based via the transaction number.
Legacy Data Transfer for Securities:
For securities position, it does not matter whether is arose in the past through a single purchase (or) a series of business transactions. The legacy data transfer thus seeks to build up the positions through One Business Transaction on the transfer key date.
Step 1: Before we enter business transactions, we must first create the master data of security position i.e. their Position Indicator. I) Use TPM61A (or) menu path Treasury and Risk Management Transaction
Management à General Settings Tools à Legacy Data Transfer à Position Data Enter Position Information for Securities
II) Now create the position indicator using TPM61.
Step 2: Now we will enter the business transaction.
I) Valuation area independent data for securities à For External Position
II) Valuation area dependant data for securities à For Internal Position Nevertheless, we need to use transaction set the effects of update type on position to change the positions. If you want to enter LOT Positions with the transactions of legacy data transfer, use the Item Number. Ensure that business transaction generating the position and the one for valuation results carry the same item number.
If you have built up
lots via normal procedures, you must specify the corresponding transaction number
when entering the valuation area dependant business transaction in the
transaction column.
Step 3: Now generate the business transactions using TPM63.We can initially build only valuation area independent data (external position) by checking “only valuation area independent data” button in TPM63. The external position can be checked in securities account cash flow i.e. external securities position in TPM40.
Also we created LSMW for each product.
Regards,
Jain

Data migration of account contract through EMIGALL

Similar Messages

Maybe you are looking for