Emigall

hi experts ,
i faced the following erroe in contract partner data maigration through account migration object. error is
1) The higher-level object for 200000, 151, does not exist
2 The higher-level object for 506070, 9829153116, does not exist

Hi Naveenkumar,
Please check this link.
http://help.sap.com/saphelp_utilities472/helpdata/en/c6/4dce68eafc11d18a030000e829fbbd/frameset.htm
Hope this will help.
Regards,
Ferry Lianto

Similar Messages

Creation of Equipment master throught Emigall

Hi Fritz,
Good Day!
I need to create a Emigall object for Equipment Master, which we can't
handle in LSMW because of the volume of data, I am using the same object as
used for Device of ISU.
The object name is EQUIPMENT in company ZISU. I have used those fileds only
which are required to create a equipmetn master in STW. While uploading the
data I am getting an error " Enter a valid device category" which is a
device category of ISU.
Can we do this or do we need to create some other customization in this case
Thanks for your support Fritz.
Regards,
Robert.

Robert,
I did some research. Please confirm you are referring to the data as copied below from the documentation.
Kind regards,
Fritz
Definition
Partners (business partners) are internal and/or external organizational units. For example, internal partners can be logistics and sales departments that perform services. External partners can be customers as service recipients and vendors as supporting service providers. A partner can be a natural or a legal entity. You can use partners in CS- and PM processing.
The following partner types are delivered with the Standard System:
Customer
Contact person
Vendor
User
Personnel number
Organizational unit
Position
Partner Function
You define partner functions in Customizing for Plant Maintenance and Customer Service. They are freely definable and always refer to a partner type. Standard functions exist (for example, goods recipient) and you can also define your own functions.
Partner Determination Procedure
The partner determination procedure is a grouping of partner functions. It specifies which partner functions are permitted or must always be specified for a particular business transaction (for example, for the processing of a service or maintenance order). In Customizing you define the partner determination procedure and assign partner functions to it. If functions are assigned to the partner determination procedure, you can assign the partner determination procedure to an object (for example, to a notification type).
Integration
You can assign partners to the following objects: Functional location and equipment

Creation of service master for the PM in Emigall

Hi Fritz,
Greetings,
I wanted to ask that can we ahead and use the Service master data loading process through Emigall.
and what are the step that we can use to avail that in Emigall.
Regards,
Robert.

Robert,
Please explain what exactly, for example, which business objects you want to create/migrate.
Kind regards,
Fritz
PS: what about the 1st thread you have opened today? Is it about the same topic?

SAP ISU EMIGALL DISC_DOC IMPORT ERROR

Hi,
I am trying to import a converted file with 234 records of DISC_DOC objects with SAP ISU EMIGALL app. I am getting this error:
     Short text
               The current application triggered a termination with a short dump.
     What happened?
               The current application program detected a situation which really
               should not occur. Therefore, a termination with a short dump was
               triggered on purpose by the key word MESSAGE (type X).
     What can you do?
               Note down which actions and inputs caused the error.
               To process the problem further, contact you SAP system
               administrator.
               Using Transaction ST22 for ABAP Dump Analysis, you can look
               at and manage termination messages, and you can also
               keep them for a long time.
     Error analysis
               Short text of error message:
               Processing canceled
               Long text of error message:
               Technical information about the message:
               Message class....... "EH"
               Number.............. 000
               Variable 1.......... " "
               Variable 2.......... " "
               Variable 3.......... " "
               Variable 4.......... " "
     How to correct the error
               Probably the only way to eliminate the error is to correct the program.
               If the error occures in a non-modified SAP program, you may be able to
               find an interim solution in an SAP Note.
               If you have access to SAP Notes, carry out a search with the following
               keywords:
               MESSAGE_TYPE_X " "
               SAPLES34ALLG or "LES34ALLGU04"
               ISU_DISCDOC_OBJECT_GET
               If you cannot solve the problem yourself and want to send an error
               notification to SAP, include the following information:
               1. The description of the current problem (short dump)
                  To save the description, choose "System->List->Save->Local File
               (Unconverted)".
               2. Corresponding system log
                  Display the system log by calling transaction SM21.
                  Restrict the time interval to 10 minutes before and five minutes
               after the short dump. Then choose "System->List->Save->Local File
               (Unconverted)".
               3. If the problem occurs in a problem of your own or a modified SAP
               program: The source code of the program
                  In the editor, choose "Utilities->More
               Utilities->Upload/Download->Download".
               4. Details about the conditions under which the error occurred or which
               actions and input led to the error.
     System environment
               SAP-Release 700
               Application server... "sapec1"
               Network address...... "10.170.7.71"
               Operating system..... "HP-UX"
               Release.............. "B.11.31"
               Hardware type........ "ia64"
               Character length.... 16 Bits
               Pointer length....... 64 Bits
               Work process number.. 8
               Shortdump setting.... "full"
               Database server... "cnvhpx01"
               Database type..... "ORACLE"
               Database name..... "EC1"
               Database user ID.. "SAPSR3"
               Char.set.... "C"
               SAP kernel....... 700
               created (date)... "Oct 22 2007 23:34:45"
               create on........ "HP-UX B.11.23 U ia64"
               Database version. "OCI_102 (10.2.0.1.0) "
               Patch level. 133
               Patch text.. " "
               Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
               SAP database version. 700
               Operating system..... "HP-UX B.11"
               Memory consumption
               Roll.... 16192
               EM...... 8379680
               Heap.... 0
               Page.... 57344
               MM Used. 3152352
               MM Free. 1034864
     User and Transaction
               Client.............. 230
               User................ "ANGHELC"
               Language Key........ "E"
               Transaction......... " "
               Transactions ID..... "48B591833C495D0CE10000000AAA0747"
               Program............. "SAPLES34ALLG"
               Screen.............. "SAPMSSY0 1000"
               Screen Line......... 6
               Information on caller of Remote Function Call (RFC):
               System.............. "EC1"
               Database Release.... 700
               Kernel Release...... 700
               Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
               Call Type........... "synchron and non-transactional (emode 0, imode 1)"
               Inbound TID.........." "
               Inbound Queue Name..." "
               Outbound TID........." "
               Outbound Queue Name.." "
               Client.............. 230
               User................ "ANGHELC"
               Transaction......... "EMIGIMP"
               Call Program........."SAPMEMIG_IMPORT"
               Function Module..... "ISU_M_REPORT_SUBMIT"
               Call Destination.... "sapec1_EC1_23"
               Source Server....... "sapec1_EC1_23"
               Source IP Address... "10.170.7.71"
               Additional information on RFC logon:
               Trusted Relationship " "
               Logon Return Code... 0
               Trusted Return Code. 0
               Note: For releases < 4.0, information on the RFC caller are often
               only partially available.
     Information on where terminated
               Termination occurred in the ABAP program "SAPLES34ALLG" - in
                "ISU_DISCDOC_OBJECT_GET".
               The main program was "RE3TR_EGD01_DCD ".
               In the source code you have the termination point in line 17
               of the (Include) program "LES34ALLGU04".
     Source Code Extract
     Line               SourceCde
     1               FUNCTION ISU_DISCDOC_OBJECT_GET.
     2               *"----
     3               ""Lokale Schnittstelle:
     4               *" IMPORTING
     5               *"     REFERENCE(X_HANDLE) LIKE EBAGEN-HANDLE
     6               *" EXPORTING
     7               *"     REFERENCE(Y_OBJ) TYPE ISU05_DISCDOC_INTERNAL
     8               *"----
     9
     10               * read line of objectss's table
     11                 read table iobj into y_obj
     12                                 with key handle = x_handle
     13                                 binary search.
     14                 if sy-subrc <> 0.
     15               *   invalid handle
     16               *    message...
     >>>>>                   message x000(eh).
     18                 endif.
     19               ENDFUNCTION.
     Contents of system fields
     Name                         Val.
     SY-SUBRC                         4
     SY-INDEX                         20
     SY-TABIX                         1
     SY-DBCNT                         8
     SY-FDPOS                         2
     SY-LSIND                         0
     SY-PAGNO                         0
     SY-LINNO                         1
     SY-COLNO                         1
     SY-PFKEY
     SY-UCOMM
     SY-TITLE                         Generated program for migration object DISC_DOC
     SY-MSGTY                         X
     SY-MSGID                         EH
     SY-MSGNO                         0
     SY-MSGV1
     SY-MSGV2
     SY-MSGV3
     SY-MSGV4
     SY-MODNO                         0
     SY-DATUM                         20080827
     SY-UZEIT                         115457
     SY-XPROG                         SAPLSYST
     SY-XFORM                         SYSTEM_HOOK_OPEN_DATASET
     Active Calls/Events
     No.               Ty.                              Program                                                            Include                                   Line
                    Name
     5               FUNCTION                              SAPLES34ALLG                                                            LES34ALLGU04                                   17
                    ISU_DISCDOC_OBJECT_GET
     4               FUNCTION                              SAPLES34                                                            LES34U10                                   21
                    ISU_O_DISCDOC_ACTION
     3               FUNCTION                              SAPLEC85                                                            LEC85U02                                   103
                    ISU_S_DISCDOC_CREATE
     2               FUNCTION                              SAPLISU_M_DISCONNECTION                                                            LISU_M_DISCONNECTIONU01                                   221
                    ISU_M_DISCON_DOCUMENT_CREATE
     1               EVENT                              RE3TR_EGD01_DCD                                                            RE3TR_EGD01_DCD                                   199
                    START-OF-SELECTION
     Chosen variables
     Name
               Val.
     No.               5                    Ty.                         FUNCTION
     Name               ISU_DISCDOC_OBJECT_GET
     X_HANDLE
               0
          0
          0
     Y_OBJ
          0
          0
          2,22222E+93
          0
     WEDISCACT
                              0000 0000000000000000                                     0000
          0
          0
          2,22222E+93
          0
     WEDISCPOS
                              0000000000000000000000 00
          0
          0
          2,22222E+44
          0
     CO_CORIV
               4
          0
          0
          33
          4
     IOBJ
               Table IT_673[1x7240]
             \FUNCTION-POOL=ES34ALLG\DATA=IOBJ
             Table reference: 39
             TABH+ 0(20) = C000000416A30E60000000000000000000000000
             TABH+ 20(20) = 00000027000002A10000000100001C48FFFFFFFF
             TABH+ 40(16) = 0400008900000A10000124C001800000
             store        = 0xC000000416A30E60
             ext1         = 0x0000000000000000
             shmId        = 0     (0x00000000)
             id           = 39    (0x00000027)
             label        = 673   (0x000002A1)
             fill         = 1     (0x00000001)
             leng         = 7240 (0x00001C48)
             loop         = -1    (0xFFFFFFFF)
             xtyp         = TYPE#000039
             occu         = 1     (0x00000001)
             access       = 1     (ItAccessStandard)
             idxKind      = 0     (ItIndexNone)
             uniKind      = 2     (ItUniqueNon)
             keyKind      = 1     (default)
             cmpMode      = 8     (cmpManyEq)
             occu0        = 0
             groupCntl    = 0
             rfc          = 0
             unShareable = 0
             mightBeShared = 0
             sharedWithShmTab = 0
             isShmLockId = 0
             gcKind       = 0
             isUsed       = 1
             isCtfyAble   = 1
             >>>>> Shareable Table Header Data <<<<<
             tabi         = 0xC000000416A69840
             pgHook       = 0x0000000000000000
             idxPtr       = 0x0000000000000000
             shmTabhSet   = 0x0000000000000000
             id           = 162   (0x000000A2)
             refCount     = 0     (0x00000000)
             tstRefCount = 0     (0x00000000)
             lineAdmin    = 1     (0x00000001)
             lineAlloc    = 1     (0x00000001)
             shmVersId    = 0     (0x00000000)
             shmRefCount = 1     (0x00000001)
             >>>>> 1st level extension part <<<<<
             regHook      = Not allocated
             collHook     = Not allocated
             ext2         = Not allocated
             >>>>> 2nd level extension part <<<<<
             tabhBack     = Not allocated
             delta_head   = Not allocated
             pb_func      = Not allocated
             pb_handle    = Not allocated

hi,
thanks.i have another doubt.
In Initialization- Define -> sender system is Empty, but in receiver system it has the company name.where to set the sender machine.
regards,
vinodh

EMIGALL Distributed Import Job for BP is getting cancelled in background

Hi,
When I'm restarting Distributed import and it's getting cancelled after some time with system error as "internal lock table overflow".
I checked SM12 (while job was running) it's showing 14,000 - 15,000 locks on table BUT000, even though EMIGALL is not updating that table as it's rerun of the old job. (Old job been cancelled due to network issue.).
Can anybody please help me to understand why it's happening?
Thanks in advance,
Sagar

Hi Sagar,
I think I can explain what happened in your system:
During data migration the application encountered many errors and does not release the locks immediately. Remember: it is not the slave jobs that creates locks but the called application (through the service functio module). If the application enncounters an error (also when the business object cannot be locked due to a lock table overflow) it returns the error and the load program writes it to the error log. The saved error message is not always directly related to the lock table overflow situation. Often it is saying: object already locked by user xxx).
The master jobs uses also locks to block the configuration of its profile against concurrent access (exclusive access). If a user blocks the profile temporarily during an update of the profile, the master job waits until the update operation finishes. This last usually only very few ms. If the master encounteres a 'lock table overflow' situation it cancels - as designed be the developer.
The simple solution is that you should avoid a lock table overflow situation and/or that the lock table must not be too small.
Sagar, I might also be that you find also the error 'lock table overflow' in the system log. Please check.
Kind regards,
Fritz

Error while Device Installation creation in Emigall

Hi Utility Gurus,
When creating full installation through EG31, i am able to create Installation successfully. But while creating Full Device installation through Emigall (object INST_MGMT) I am getting error 'Enter Rate Type'.
I am entering the correct Rate Type and Rate category in structure DI_ZW apart from that other required fields. And in structure DI_GER I am adding the Legacy Device no. Have also added the required fields in DI_INIT structure.
When I enter Rate type in DI_GER structure I get the error "Enter permissible Rate Type'.
Can anybody please let me know how this error can be removed and what are the things to note/configure before Device installation from Emigall.
Regards

Hello All,
I know this is a very old thread but just to help anyone else who comes across the same error hope this helps.
In order to complete Full install you need the following structures to be activate/generated
1) Interface (DI_INIT)
2) OKCODE    -- this is a hidden auto structure
3) ZWSTAND -- this is a hidden auto structure
4) AUTO_ZW (DI_ZW)
5) AUTO_GER (DI_GER)
6) CONTAINER -- this is a hidden auto structure
In order to view the hidden structure follow the below steps:
- Once you click on the INST_MGMT go to Automatic Structure--> Display List --> All
you will now be able to view all the hidden structures. IN order to activate/generate them you will have to click them go to automatic struture --> Change --> generate
Commonly required fileds in different sturctures are below (please note, these are the commonly used fields and varies based on the project requirments)
--> Interface
   - ACTION
- ANLAGE
- DEVLOC
- EADAT
--> AUTO_ZW
    - ABFAKTE
    - ANZDAYSOFPERIOD
    - ANZERG
    - EQUNRE
    - KONDIGRE
    - PERVERBR
    - PERVERBRE
    - TARIFART
    - ZWNABR
    - ZWNUMMERE
    - ZWSTANDCE
--> AUTO_GER
    - ABRFAKT
    - ACTION
    - DEVLOC
    - EQUNRNEU
    - GERWECHS
    - GVERRECHG
    - KONDIGRG
    - MATNR
    - PREISKLAG
    - TARIFARTG
Hope this helps.
Thanks,
Edited by: Anshul Varshney on Feb 2, 2012 5:09 PM

Adding a new field to Emigall

Hi All,
I was interested in knowing how we can add a new field to an existing emigall object and also how to process the logic after adding the field ie. how would emigall handle the field after we have added the field in emigall.
I would appreciate if you can share the screen shots (if any) at karanchopra dot kc at gmail dot com.
Thanks,
Karan

Hello,
Before I provide you with solution, can you be more ellobrative with your requirement.
a) Are you adding new 'Z' field?
b) Do you want to just extend the existing Structure?
Depending on your requirements, there are different approaches to solve this problem.
Regards,
Anup Mohite

Use OBJCLASS object of Emigall for Class & characteristics creation in FL

Hi Fritz,
Good day,
I want to use OBJCLASS object of Emigall for
Class and characteristics cration of Functional Location, The object is
desiged for Equipment only,
I read the document of this object which says
that it can be modify to use for functional location as well by changing
some rule, I tried by changing the field "Name of database table for
object" from the standard which is made for DEVICE/EQUIPMENT
I need your help to modify the rule to use this object for class and
characterstic creation for Functional Location, the migration object field is set to Device
which I want to change to FUNCLOC but that field is not modifiable.
Can you help me Fritz
Regards,
Robert

Robert,
Yes you are right. The following changes have to be made:
HEADER-OBJECT_TYPE need to be set to IFLOT (Fixed Value or Transfer field rule)
DATA-FIELD need to be set to TPLNR (Fixed Value or Transfer field rule)
DATA-VALUE need to be set to either CONNOBJ or DEVLOC (Via KSM field rule)
Kind regards,
Fritz

Use of Emigall for creation of masters in the production environment

Hi,
The EMIGALL objects are normally used for migrating legacy master data and/or cut-over data before production environment is up.
I am contemplating to use EMIGALL object for creation of contract account masters in production environment. One more option that I have is to use standard BAPI for creating contract account masters.
Can anyone tell me whether it is proper to use EMIGALL object for day to day creation of master day in production environment. Is there any disadvantage or risk involved in it.
Kindly reply soon.
Regards,
Ganesh

I've already used emigall multiple times to do delta migrations into an operational prod environment.
Purely looking at the functionalities, it should/would/must be possible to use emigall as a master data generator. I just think you need to look into the requirements:
who will use it? end-user/application manager/...
what's the amount of data to be loaded?
what's the time window of the load? Day/night
how is the data supplied?
As you know, emigall EATS system resources like mad, so using it during the day might not be preferable. emigall is also very picky about the file format, whereas in a custom report you can define the input structure yourself.
On the other hand, the error handling and follow-up of emigall is great...
Personally, I'd go for a custom report with a BAPI... It'll give you more flexibility than emigall.

EMIGALL performance for migration object OBJCLASS

Hi all,
my previous question, was Classification of IFLOT & EQUI via CLB2 / CLB1 & was focused on improving performance of classification of IFLOT & EQUI objects.
Testing EMIGALL for migration object OBJCLASS I am seeing no performance gains between a single thread update & parallel update threads. IE the single thread throughput is reported as ~the same as the parallel threads throughput combined.
I note in the job logs of my various tests;
for a single thread, that no messages are logged between the start & end of the migration.
for parallel threads, that message C4 200 'Class "CLASSNAMEHERE" is locked' appearing many times.
I don't see any unexpected migration errors in ether case.
Are there any insights on how I might improve over all throughput using this method? I cant see any control parameters for this object, nor does the Guideline have much information on OBJCLASS.
First world problems :-/

Hello Daniel,
Without having much insight into your system and infrastructure details or the volume that you are working with, I suggest for you to try below for performance improvement.
1. Run DB Statistics on functional location and Equipment related tables such as EQUI, IFLOT, ILOA, etc. (these are HLO objects that you are updating by way of classification). Also update classification table such as AUSP. These tables mentioned here as a starting point.
2. Also strongly suggest that a performance trace be done on this job to analyze and identify another table or steps that may be a performance bottleneck and maybe a candidate for DB statistics refresh Or some other corrective action.
3. The locks maybe occurring due to a mass update which is as expected. Perhaps to get by that you may want to use "commit buffering allowed" option for this migration object and set to say a number "10" or "20" to start with and see if it helps better the performance. As you would have noticed, locks will also impact performance.
4. Please also refer to Cookbook for ISUMIG Performance and refer to sections for DEVICE, CONNOBJ and DEVLOC. These are HLO objects for classification and there may be some useful insight in that document too.
Hope this helps.
Ash

How to change the status in emigall

Hi All,
Can any body please let me know how to change the blocking status of each object to '000' instead of the default '100'(Blocked) in emigall.
Thanks

Hi,
a blocking status ending with 1, 2 or 3 does not allow further changes on object level. In order to 'unblock' the object you must execute the following steps (let's assume you change the blocking status of migration object PARTNER):
(1) copy the migration object PARTNER either into the same migration company (with a new name) or into another migration company in order not to loose the customizing of the blocked migrationobject PARTNER. The name of the copied migration object might be PART_TEMP. A copy allways sets the blocking status of the copied migration object to 100. You can now continue working with the copied migration object for follow the steps (2) - (4) to have a migration object back with the original name.
(2) Delete the migration object PARTNER with the blocking status 002. For this select Utilities -> Delete MigObjects and delete the migration object PARTNER
(3) copy the copied migration object PART_TEMP back with the name of your original migration object PARTNER.
(4) Delete the migration object PART_TEMP.
Alternatively, if you changed the blocking status accidentially in the development system, you may change the field TEMOBS-SPERRSTATUS back to 000 with a direct update.
Kind regards,
Fritz
PS: There will be a correction soon warning the user with a confirmation popup.

IS-U: Migration- Issue with DEVICE object using EMIGALL

Hello Friends,
I need a quick help. The issue is here below.
I am using the object DEVICE to create Device/Equipment. I could able to create an Equipment however I found that in EQUI table the field SERNR is not updated. Actually this field should have the value of EQUNR.
I had tried many times wih differenct possible options but this field is empty in all the trials. I am also using the auto structure CONTR and its sub strucutures COMMIT, UPDATE, INDIV, CONV filling with 'X' but the result is only this field SERNR is not updated in the table EQUI.
Without this field SERNR being field I cannot perform Device Installation (Full/Technical/Billing).
Please share your ideas.
Thanks in Advance,
Vijay.

Hi Vijay
That's possible...
I assume transaction IQ01 and EMIGALL are using the same function EQUIPMENT_INSERT.
If NEW_VEQUI-EQUNR contains already a number, the function does not get a new number from the number range object, for example with external numbering. In case there's no EQUNR given, a new number is taken from the number range object, internal numbering.
If no SERNR is provided when calling EQUIPMENT_INSERT, there won't be a SERNR in EQUI. Just check if IQ01 provides the serial number when calling EQUIPMENT_INSERT.
This means another possible solution is to get a new number for EQUNR in EMIGALL and populate EQUNR and SERNR before calling the service function module ISU_M_EQUI_INSERT. Call function module NUMBER_GET_NEXT for object EQUIP_NR.
This can be done on field level by setting the Processing Type to 4 = Rule (check which of the two fields comes first - EQUNR or SERNR - to assign the number from NUMBER_GET_NEXT and copy the value for the second field) or via events see menu item Utilities: Event, when you're in the object maintenance screen.
Yep
Jürgen

EMIGALL - BCONTACT : Problem in upload

Hi,
I am using EMIGALL to upload BCONTACT.
However, I am getting the error that Business Partner does not exist.
I have successfully uploaded BPs using PARTNER object and relationships using PART_REL.
I alos gave PARTNER as KSM for BCONTACT. But still I get the same error.
I have tried by specifying both the Legacy Sysetm Key and the new genrated BP Number, but I always get the same error.
Can any one tell me what could be the problem??
Thanks,
Sachin.

Hi Dominic,
I have tried it but i am getting the same error.
Also, Is it necessary to give the values to IOBJECTS structure?? If yes, then what values do you suggest should be provided to these fields?
I tried giving the BP number in this structure also, but i get the same error.
Thanks,
Sachin.

How to write program for the long text in EMIGALL for the DEVICE LOCATION.

Hi,
I am pretty new to this ISU field and i have been asked to code for a Long Text in EMIGALL for DEVICE LOCATION,
so i would like someone can help me with it.
thanks in advance.
Robert.

Robert,
You can find most of the answers to your questions in the Guidelines:
Chapter 2.4.2 describes how to configure the field rule Fixed Value.
Chapter 2.4.5 describes how to configure the field rule via KSM.
Chapter 2.5 descibes the Key- and Status Management and the usage of the the KSM in field rules.
The specific answer to your questions are:
(1) ...When i was adding the fixed rule, it was asking for domain so what should be the Domain that i should add ... You may ignore the domain field when creating a fixed value object. It's more for information purposes.
(2) ... and what should i keep the fixed value, string or filed or abap rule ... I'd suggest to use 'String' and enter the specific value in the field 'FV contents'.
(3) ... Finally you need to adjust the RETURN-FIELD of the newly created BAPI migration object to AUTO-X_HEAD-TDNAME, where do i make this adjustment can you specify that ... The return field can only be adjusted int the migration object maintenance screen (MigObject -> Change). Please see chapter 3.1 for more details on the 'return field' and figure 3-8 in chapter 3.4.2 how to generate a BAPI migration object.
(4) ... Well i would also like to ask about the x_head-tdname = via KSM (e.g. DEVLOC), where should i put the value ... You wanted to know how to migrate a long text of a device location migration object DEVLOC). According to chapter Chapter 2.4.5 you need to enter the name of the superior migration object (here DEVLOC) in the 'MigObject1'field on the 'via KSM' sub-screen on the field maintenance screen.
(5) ... and what exactly would it be can i put DEVLOC in the ID of technical Object and where should i put this value... I am not sure I understand your question. In the end you will need to pass the number (ID) of the technical object in the TDNAME field. Either you put the id into the import file (only if you know the id) or you need to use the 'via KSM' field rule to replace the legacy system key of the device location by the SAP key by the load report and prior to passing the auto data to the application thus your new function module.
Kind regards,
Fritz

EMIGALL - Issue in INTCASHDEP EMIGALL Object

HI,
I am trying to create interest document through EMIGALL.
I am getting error as No cash security deposits available'
Security deposit # in INTCASHDEP EMIGALL Object
I have adopted Rec data type as INT, FKKKO, FKKOP & FKKOPK.
In FKKKO I have adopted interest related fields (doc type, origin key and start and end date)
In FKKOP I have adopted attributes of main and sub 0020 and 0010.
In FKKOPK I have adopted attributes of FKKOP doc (payment)
So can anyone share comments to resolve issue.
Regards,
Paresh

Hi Paresh
What value/reference did you put into field INTCASHDEP-INTERFACE-OPBEL?
You have to populate it with oldkey of the PAYMENT on the SECURITY.
Here again the load order:
SECURITY
PAYMENT - linked to SECURITY
INTCASHDEP - linked to PAYMENT
For example:
SECURITY - Requested on 01.03.2012, amount $200
PAYMENT - Paid on 20.03.2012 against security, amound $200
INTCASHDEP - All interest on payment from 20.03.2012 until go-live (20.03.2014 or 2 years) for 5% p.a., amount $20
If the security is returned at go-live the customer gets the migrated $220 back (payment plus intcashdep).
If the security is returned one year after go-live the customer gets the migrated $220 (payment plus intcashdep) plus all interest within SAP after the go-live (another $10).
Also your main / sub transaction is incorrect, because it's used for Cash Security Deposit Payments. At the end of the day it doesn't matter, because your HVORG/TVORG input values are not used anyway - you can leave the fields on SAP default processing type "1 - Initial" in EMIGALL. They are determined internally (event 1310) and I would expect it to end up as 0025 / 0010.
In general, after you copy an object from the SAP company, keep it simple and add only fields if you really need them. The copied object contains all mandatory and often-used fields.
Yep
Jürgen

Security deposit # in INTCASHDEP EMIGALL Object

Is there a way to reference the Security Deposit number in the EMIGALL Object INTCASHDEP so the migrated Interest indicates the Security Deposit number upon being migrated? INTCASHDEP uses the KSM link to the Security Object but is it required that the INTCASHDEP Object uses the SAP Security Deposit # while trying to migrate the interest amount?

Hi Caroline
There's no direct link between INTCASHDEP and SECURITY.
Please have a look into the documentation of the INTCASHDEP migration object (EMIGALL: Migration Object: Display, then Documentation: Display):
Transfer concept for cash security deposits and interest calculation
    The transfer of cash security deposits, including the requests, payments
    and interest calculations of credit is a process performed in several
    steps. They are:
    1. Creation of cash security deposit
        Migration object SECURITY.
        You can classify a security deposit as a cash security deposit using
        the NON_CASH field. When you create a cash security deposit, the
        system posts a request. You can determine the number of the document
        using the number of the security deposit in table FKK_SEC_REQ (field
        OPBEL).
    2. Transfer of cash security deposit
        Migration object PAYMENT.
        You must create a rule for determining the document number from the
        security deposit.
    3. Transfer of interest information
        Migration object INTCASHDEP.
        This object generates the necessary interest document for credit
        originating from cash security deposits.
The interest document is not linked to the SECURITY, but the PAYMENT on SECURITY.
The interest is the amount the power company has to pay back on top of the original payment when the security (payment) is returned to the customer.
Yep
Jürgen

Emigall

Similar Messages

Maybe you are looking for