Transfer ERP HCM data per IDoc

Hello,
i want to distribute data from ERP HCM with report RHALEINI.
The IDoc is a reduced IDoc of HRMD_A.
It's working fine but i get almost 500 resulting IDocs and it would be better to have just one IDoc.
Is this possible?
If it's not possible there are 2 problems:
1) Not all IDocs receive at XI
2) I have to collect all IDocs and will need a some kind of correlation and don't want to use BPM (only if it's there is no other way)
Why do i get so much IDocs anyway? Has it to do with a maximum size of IDocs?
Regards
Patrick

Patrick,
Is this HR data replication is initial replication. or just updation. If it is for updation just mention the required infotypes. Generally if you are replicating entire data, there is an order to replicate. I do'nt remember all the objects types. the main object types sequence like,O, S, CP, P, C...
Usually we used to face the problems, if u mentioned the size as 200. If the idocs for object type 'C' the segment size will be 50000 something like that. always it is easy to process the more idocs with less amount of data. If you get big idocs, you will be facing the status 52. which is partially data posted.
| Naveen

Similar Messages

Need to transfer Custom infotype data using IDOCs

Hi,
My requirement is to transfer custom OM infotype changes using IDOCs.
But its not creating any change pointers for that infotype.
The message used is a copy of standard message OM_HRMD_A.
Can any one please help me out in this issue.
Thanks,
Sarika

You'll need to erase the drive by booting up holding command-option-r keys into your Recovery Volume.
Use Disk Utility to erase the disk and then Internet Recovery. That will take a while.
http://support.apple.com/kb/HT4718

Want to transfer data via idocs from one R/3 to different R/3

Hi!!
May i hav nay step by step pdf which gives the complete flow of how to transfer idocs from from one R/3 to different R/3.
Though i have the basics steps but some where I m stuck.
Also I have two doubts::
1.Is thr Any relation bw port name and Logical System name?Can they be same.??I hav kept Logical System name as SAPE60 AND PORT name also as SAPE60(in e60) and SAPEI6(in ei6) servers respectively.
2.Should the Logical System names be maintained same in both the servers??
Kindly respond .
Helpful answers will be rewarded points!!!

Hi Deepika ,
See the Example scenarios
MASTER DATA TRANSFERMATION BETWEEN 2 DIFF CLIENTS
     For this scenario Client 800 is the Sender and 810 is the receiving system
1. Creating Logical Systems
o     Login using 800 client
o     Go to T. Code SALE
o     Expand Sending and Receiving Systems
o     Expand Logical Systems
o     Click on Define Logical System
o     Click on New Entries
o     Create STUD_S, STUD_R Logical Systems
o     Save and come back
o     Assign the STUD_S Logical System to client 800
o     Assign the STUD_R Logical System to client 810
2. Creating the RFCs
o     Go to T. Code SM59
o     Expand R/3 Connections
o     Enter RFC Name as STUD_S
o     Connection Type as 3
o     Language as EN
o     Client as 800
o     User as SAPUSER
o     PWD as abap
o     Target host as sap
o     Click on Remote logon button to test the RFC
o     Enter RFC Name as STUD_R
o     Connection Type as 3
o     Language as EN
o     Client as 800
o     User as SATISH
o     PWD as abap
o     Target host as sap
o     Click on Remote logon button to test the RFC
3. Creating the Message Type
o     Go to T. Code WE81
o     Click on change, continue
o     Click on New Entries button
o     Give message type as ZBAPI_STUD_MAS and description
o     Save and back
4. Creating the Segment
o     Go to T. Code WE31
o     Give segment name as ZBAPI_STUD_SEG
o     Enter Short Text
o     Enter the Field Name and Data Element in the text boxes
o     Save, continue,
o     Click on Edit -> Set Release.
5. Creating the Basic IDOC Object
o     Go to T. code WE30
o     Give obj. name as ZBAPI_STUD_IDOC
o     Click on create
o     Select create new radio button, give description and continue
o     Select the IDOC obj name and click on create button
o     Enter the segment name which is create earlier
o     Select the check box if you want to make the segment mandatory
o     Enter 1 in minimum number 99999 in maximum number, continue
o     Save and back
o     Click on Edit -> Set Release
6. Creating Customer Distribution Model
o     Go to T. Code BD64
o     Click on change and Create model view button
o     Enter the short text and Technical name as ZSTUDENT
o     Select the model and click on Add Message Type Button
o     Give the Sender as STUD_S,
o                    Receiver as STUD_R,
o                    Message Type as ZBAPI_STUD_MAS
o     Select the model view & click on Environment -> Generate Partner Profiles
o     Select Transfer IDOC Immediately and Trigger Immediately radio buttons
o     Click on Execute
o     You should get a list in green color which means it executed successfully.
o     Back to main screen, select the model view
o     Click Edit->Model view->Distribute
o     Click on continue
o     You should get a list saying model view is distributed successfully.
7. Checking the Port
o     Go to T. Code WE21
o     Expand Transactional RFC
o     Find the port from the list which is created using BD64 for STUD_R (Receiving system) RFC Destination.
8. Checking the Partner Profiles.
o     Go to T. Code WE20
o     Expand Partner Type LS
o     Select the Partner profile STUD_R
o     Double click on Message Type ZBAPI_STUD_MAS in Outbound parmtrs.
o     Check Receiver Port is assigned correctly
o     Check the Basic type as your Basic IDOC object.
9. Assigning the Message Type to Basic IDOC Object
o     Go to T. Code WE82
o     Click on Change & continue, New Entries button
o     Give the Message type as ZBAPI_STUD_MAS
o     Give Basic Type as ZBAPI_STUD_IDOC
o     Release as 46C
o     Save and back
10. Creating Inbound Function Module (Posting Program)
o     Go to T. Code SE37
o     Create a function Module IDOC_INPUT_ZBAPI_STUD_MAS
o     Set the Processing type as Remote Enabled Module and mode as start immed, in Attributes Tab.
o     Import Parameters
INPUT_METHOD                 LIKE     BDWFAP_PAR-INPUTMETHD
MASS_PROCESSING     LIKE     BDWFAP_PAR-MASS_PROC
NO_APPLICATION_LOG     LIKE     SY-DATAR
MASSSAVEINFOS                 LIKE     MASSSAVINF
o     Export Parameters
WORKFLOW_RESULT          LIKE     BDWF_PARAM-RESULT
APPLICATION_VARIABLE     LIKE     BDWF_PARAM-APPL_VAR
IN_UPDATE_TASK          LIKE     BDWFAP_PAR-UPDATETASK
CALL_TRANSACTION_DONE LIKE     BDWFAP_PAR-CALLTRANS
o     Tables
IDOC_CONTRL     LIKE     EDIDC
IDOC_DATA          LIKE     EDIDD
IDOC_STATUS     LIKE     BDIDOCSTAT
RETURN_VARIABLES     LIKE     BDWFRETVAR
SERIALIZATION_INFO     LIKE     BDI_SER
o     Exceptions
WRONG_FUNCTION_CALLED
o     Source Code
DATA: FIRST_TRANC LIKE MARA_UEB-TRANC,
      ZBAPI_STUD_SEG like zbapi_stud.
DATA: ZBAPI_STUD LIKE ZBAPI_STUD.
DATA: I_ZBAPI_STUD LIKE ZBAPI_STUD.
DATA: C_TRUE                         VALUE 'X'.
DATA: C_FALSE                        VALUE ' '.
DATA: BEGIN OF T_IDOC_ROLLNO OCCURS 0,
        DOCNUM LIKE EDIDC-DOCNUM,
        ROLLNO LIKE ZBAPI_STUD-ROLLNO,
      END   OF T_IDOC_ROLLNO.
DEFINE APPEND_RESFIELDS.
    PERFORM APPEND_RES_FIELDS TABLES T_MFIELDRES
                                     T_RES_FIELDS
                              USING &1
                                     COUNTER-D_IND.
END-OF-DEFINITION.
DATA: I_MARA_UEB LIKE MARA_UEB.
DATA: I_ZSTUD_UEB LIKE ZBAPI_STUD.
DATA: I_MAKT_UEB LIKE MAKT_UEB.
DATA: I_MARC_UEB LIKE MARC_UEB.
DATA: I_MARD_UEB LIKE MARD_UEB.
DATA: I_MFHM_UEB LIKE MFHM_UEB.
DATA: I_MARM_UEB LIKE MARM_UEB.
DATA: I_MEAN_UEB LIKE MEA1_UEB.
DATA: I_MBEW_UEB LIKE MBEW_UEB.
DATA: I_STEU_UEB LIKE STEU_UEB.
DATA: I_STEUMM_UEB LIKE STEUMM_UEB.
DATA: I_MLGN_UEB LIKE MLGN_UEB.
DATA: I_MLGT_UEB LIKE MLGT_UEB.      " //br010797 neu zu 4.0
DATA: I_MPGD_UEB LIKE MPGD_UEB.
DATA: I_MPOP_UEB LIKE MPOP_UEB.
DATA: I_MVEG_UEB LIKE MVEG_UEB.
DATA: I_MVEU_UEB LIKE MVEU_UEB.
DATA: I_MVKE_UEB LIKE MVKE_UEB.
DATA: I_MPRW_UEB LIKE MPRW_UEB.
DATA: I_LTX1_UEB LIKE LTX1_UEB.
DATA: HELP_MARC_UEB LIKE MARC_UEB.
DATA: T_MARA_UEB LIKE MARA_UEB OCCURS 0.
DATA: T_MAKT_UEB LIKE MAKT_UEB OCCURS 0.
DATA: T_MARC_UEB LIKE MARC_UEB OCCURS 0.
DATA: T_MARD_UEB LIKE MARD_UEB OCCURS 0.
DATA: T_MFHM_UEB LIKE MFHM_UEB OCCURS 0.
DATA: T_MARM_UEB LIKE MARM_UEB OCCURS 0.
DATA: T_MEAN_UEB LIKE MEA1_UEB OCCURS 0.
DATA: T_MBEW_UEB LIKE MBEW_UEB OCCURS 0.
DATA: T_STEU_UEB LIKE STEU_UEB OCCURS 0.
DATA: T_STEUMM_UEB LIKE STEUMM_UEB OCCURS 0.
DATA: T_MLGN_UEB LIKE MLGN_UEB OCCURS 0.
DATA: T_MLGT_UEB LIKE MLGT_UEB OCCURS 0.    " //br010797 neu zu 4.0
DATA: T_MPGD_UEB LIKE MPGD_UEB OCCURS 0.
DATA: T_MPOP_UEB LIKE MPOP_UEB OCCURS 0.
DATA: T_MVEG_UEB LIKE MVEG_UEB OCCURS 0.
DATA: T_MVEU_UEB LIKE MVEU_UEB OCCURS 0.
DATA: T_MVKE_UEB LIKE MVKE_UEB OCCURS 0.
DATA: T_MPRW_UEB LIKE MPRW_UEB OCCURS 0.
DATA: T_LTX1_UEB LIKE LTX1_UEB OCCURS 0.
Internal fields/ tables
DATA: FLAG_ERROR_HAPPENED.
DATA: flag_material_exists. "//br210397 zu 4.0 keine Verwendung mehr
DATA: FLAG_EXIT_TO_BE_DONE.
DATA: HELP_TABIX LIKE SY-TABIX.
DATA: HELP_TRANC LIKE MARA_UEB-TRANC.
DATA: HELP_ALAND LIKE STEU_UEB-ALAND.
DATA: HELP_VKORG LIKE MVKE-VKORG.
DATA: HELP_WERKS LIKE T001W-WERKS.
DATA: HELP_LFDNR LIKE STEU_UEB-LFDNR.
DATA: LAST_MARC_TRANC LIKE MARA_UEB-TRANC.
DATA: LAST_MLGN_TRANC LIKE MARA_UEB-TRANC.    " //br010797 neu zu 4.0
DATA: LAST_TEXT_TRANC LIKE MARA_UEB-TRANC.
DATA: CURRENT_TABIX LIKE SY-TABIX.
DATA: GENERAL_SUBRC LIKE SY-SUBRC.
DATA: HELP_FACTOR TYPE P DECIMALS 3.
DATA: USER_SEGMENTS LIKE EDIDD OCCURS 0 WITH HEADER LINE. " insert
DATA: CUST_SEGMENT LIKE EDIDD.
DATA: I_MFIELDRES LIKE MFIELDRES.
DATA: I_MERRDAT LIKE MERRDAT.
DATA: I_EDIDD LIKE EDIDD.
                                       " //br neu zu 3.1g
DATA: T_RES_FIELDS LIKE DELFIELDS OCCURS 0 WITH HEADER LINE.
DATA: T_MFIELDRES LIKE MFIELDRES OCCURS 0.
DATA: T_MERRDAT LIKE MERRDAT OCCURS 0.
DATA: T_EDIDD LIKE EDIDD OCCURS 0.
DATA: BEGIN OF t_matnr OCCURS 0, "//br210397 zu 4.0
        matnr LIKE mara-matnr,   " wird nicht mehr verwendet
      END OF t_matnr.            "
DATA: BEGIN OF COUNTER,
          TRANC LIKE MARA_UEB-TRANC,
          D_IND LIKE MARA_UEB-D_IND,
        END OF COUNTER.
DATA: BEGIN OF t_idoc_tranc OCCURS 0,                          " 4.0
        docnum LIKE edidc-docnum,                              "
        tranc LIKE mara_ueb-tranc,                            "
      END OF t_idoc_tranc.                                     "
DATA T_IDOC_TRANC LIKE MATIDOCTRANC OCCURS 0 WITH HEADER LINE."
DATA: FLAG_FITS.
DATA: APPLICATION_SUBRC LIKE SY-SUBRC.
DATA FLAG_MUSS_PRUEFEN LIKE SY-DATAR.
DATA MAX_ERRORS LIKE T130S-ANZUM.    " 4.0
note 419281
DATA : FLG_MASS.
CLEAR : FLG_MASS.
FIELD-SYMBOLS: .            " 4.0
ALE-distribution unity : IDOC status set by locking      "note0361838
data:                                                     "note0361838
    it_dsp_idocstat like bdidocstat                         "note0361838
      occurs 0 with header line.                            "note0361838
Initialize data - general
REFRESH T_MFIELDRES.
REFRESH T_IDOC_TRANC.
REFRESH T_IDOC_TRANC.                "JH/02.02.98/4.0C KPr100004993
REFRESH t_idoc_tranc_segment.   " //br 40 : unnötig
REFRESH matnr_tranc.            "    -"-
REFRESH t_matnr.
COUNTER-TRANC = 1.
COUNTER-D_IND = 1.
REFRESH T_MARA_UEB.
REFRESH T_MAKT_UEB.
REFRESH T_MARC_UEB.
REFRESH T_MARD_UEB.
REFRESH T_MFHM_UEB.
REFRESH T_MARM_UEB.
REFRESH T_MEAN_UEB.
REFRESH T_MBEW_UEB.
REFRESH T_STEU_UEB.
REFRESH T_STEUMM_UEB.
REFRESH T_MLGN_UEB.
REFRESH T_MLGT_UEB.                  " //br010797 neu zu 4.0
REFRESH T_MPGD_UEB.
REFRESH T_MPOP_UEB.
REFRESH T_MVEG_UEB.
REFRESH T_MVEU_UEB.
REFRESH T_MVKE_UEB.
REFRESH T_MPRW_UEB.
REFRESH VKORG_ALAND.
REFRESH WERKS_ALAND.
CLEAR APPLICATION_SUBRC.
REFRESH T_MERRDAT.
Check if right function is called
READ TABLE IDOC_CONTRL INDEX 1.
IF SY-SUBRC <> 0.
    EXIT.
ELSE.
    IF IDOC_CONTRL-IDOCTP <> 'ZBAPI_STUD_IDOC'.
      RAISE WRONG_FUNCTION_CALLED.
    ENDIF.
ENDIF.
LOOP AT IDOC_CONTRL.
Initialize data - per IDOC
t_idoc_tranc-docnum = counter-tranc.
    T_IDOC_TRANC-DOCNUM = IDOC_CONTRL-DOCNUM.
    T_IDOC_TRANC-FIRST_TRANC_IDOC = COUNTER-TRANC + 2.
    APPEND T_IDOC_TRANC.
Select segments which belong to IDOC
    REFRESH T_EDIDD.
    LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
      APPEND IDOC_DATA TO T_EDIDD.
    ENDLOOP.
   BUSINESS TRANSACTION EVENT (header / data)         "note0388000
     call function 'OPEN_FI_PERFORM_MGV00200_E'         "note0388000
          exporting                                     "note0388000
              idoc_header       = idoc_contrl           "note0388000
              FLG_APPEND_STATUS = 'X'                   "note0388000
          tables                                        "note0388000
(DEL)       idoc_data         = idoc_data "note0388000 note0418561
              idoc_data         = t_edidd               "note0418561
              idoc_status       = idoc_status           "note0388000
          exceptions                                    "note0388000
              others       = 1.                         "note0388000
     if sy-subrc = 1.                                   "note0388000
        continue.                                       "note0388000
     endif.                                             "note0388000
Within one IDOC: loop through data segments:
Prepare internal tables for the current material
    LOOP AT T_EDIDD INTO IDOC_DATA.
    Transform from CoreData to Normal Data if necesary
      CASE IDOC_DATA-SEGNAM.
       WHEN 'E1MARAC'.
*--COMMENTED BY SATISH
         PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.
       WHEN 'E1MAKTC'.
         PERFORM MOVE_E1MAKTC_TO_E1MAKTM USING IDOC_DATA.
*--COMMENTES ENDED BY SATISH
         WHEN 'ZBAPI_STUD_SEG'.
          PERFORM MOVE_E1MARAC_TO_E1MARAM USING IDOC_DATA.
            CLEAR I_ZBAPI_STUD.
Second: Move E1MARAC into E1MARAM
            I_ZBAPI_STUD = IDOC_DATA-SDATA.
Third: Move E1MARAM back into IDOC-line
            IDOC_DATA-SDATA = I_ZBAPI_STUD.
            IDOC_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.
      ENDCASE.
      CURRENT_TABIX = SY-TABIX.
      COUNTER-D_IND = COUNTER-D_IND + 1.
      COUNTER-TRANC = COUNTER-TRANC + 2.
      CASE IDOC_DATA-SEGNAM.
         WHEN 'ZBAPI_STUD_SEG'.
        Initialize data - per material
          COUNTER-D_IND = 1.
          FIRST_TRANC = COUNTER-TRANC.
        interpret segment
          ZBAPI_STUD_SEG = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING ZBAPI_STUD TO I_ZSTUD_UEB.
          T_IDOC_ROLLNO-DOCNUM = IDOC_CONTRL-DOCNUM.
          T_IDOC_ROLLNO-ROLLNO = I_ZSTUD_UEB-ROLLNO.
          APPEND T_IDOC_ROLLNO.
       ENDCASE.
            if not ZBAPI_STUD_SEG is initial.
             ZBAPI_STUD-MANDT = ZBAPI_STUD_SEG-MANDT.
             ZBAPI_STUD-ROLLNO = ZBAPI_STUD_SEG-ROLLNO.
             ZBAPI_STUD-FNAME = ZBAPI_STUD_SEG-FNAME.
             ZBAPI_STUD-LNAME = ZBAPI_STUD_SEG-LNAME.
              INSERT ZBAPI_STUD FROM ZBAPI_STUD_SEG.
              COMMIT WORK.
            ENDIF.
*-- ALE ditribution unity : update IDOC status                "note03618
      LOOP AT it_dsp_idocstat.                                  "note036
         LOOP AT IDOC_STATUS WHERE DOCNUM = it_dsp_idocstat.    "note036
            DELETE idoc_status INDEX sy-tabix.                  "note036
         ENDLOOP.                                               "note036
         APPEND it_dsp_idocstat TO idoc_status.                 "note036
      ENDLOOP.                                                  "note036
*--GENERATING THE IDOC STATUS
PERFORM HANDLE_ERROR_EXT             " //br40
              TABLES                                        "
                 IDOC_CONTRL                                "
                 IDOC_STATUS                                "
                 RETURN_VARIABLES                           "
                 T_MERRDAT                                  "
                 T_IDOC_TRANC                               "
                 T_IDOC_ROLLNO          "JH/4.0C/KPr100004993
              USING                                         "
                 GENERAL_SUBRC                              "
                 NO_APPLICATION_LOG                         "
                 MASSSAVEINFOS         "wk/40c
              CHANGING                                      "
                 WORKFLOW_RESULT.                           "
              PERFORM HANDLE_ERROR
                          TABLES
                             IDOC_CONTRL
                             IDOC_STATUS
                             RETURN_VARIABLES
                             T_MERRDAT
                             T_IDOC_ROLLNO     "JH/4.0C/KPr100004993
                          USING
                             APPLICATION_SUBRC
                          CHANGING
                             WORKFLOW_RESULT.
SORT T_IDOC_ROLLNO BY ROLLNO. "note 315124
React on general error
DATA: I_MERRDAT LIKE MERRDAT.
IF GENERAL_SUBRC <> 0.
    I_MERRDAT-MSGTY = 'E'.
    I_MERRDAT-MSGID = SY-MSGID.
    I_MERRDAT-MSGNO = SY-MSGNO.
    I_MERRDAT-MSGV1 = SY-MSGV1.
    I_MERRDAT-MSGV2 = SY-MSGV2.
    I_MERRDAT-MSGV3 = SY-MSGV3.
    I_MERRDAT-MSGV4 = SY-MSGV4.
    APPEND I_MERRDAT TO T_MERRDAT.
ENDIF.
LOOP AT T_MERRDAT INTO I_MERRDAT
                    WHERE MSGTY = 'S' "success
                    OR    MSGTY = 'D' "dummy
                    OR    MSGTY = 'I' "Information " //br011097 zu 3.1I
                    OR    MSGTY = 'H' "dummy       " 4.0
                    OR    MSGTY = 'W'. "warning
    DELETE T_MERRDAT.
ENDLOOP.
    ENDLOOP.
ENDLOOP.
ENDFUNCTION.
*&      Form handle_error_ext
FORM HANDLE_ERROR_EXT
        TABLES
           IDOC_CONTRL                   STRUCTURE EDIDC
           IDOC_STATUS                   STRUCTURE BDIDOCSTAT
           RETURN_VARIABLES              STRUCTURE BDWFRETVAR
           T_MERRDAT                     STRUCTURE MERRDAT
           IDOC_TRANC                    STRUCTURE MATIDOCTRANC
JH/02.02.98/4.0C KPr100004993 (Anfang)
           T_IDOC_ROLLNO                 STRUCTURE T_IDOC_ROLLNO
JH/02.02.98/4.0C KPr100004993 (Ende)
        USING
           GENERAL_SUBRC                 LIKE SY-SUBRC
           NO_APPLICATION_LOG            LIKE SY-DATAR
           MASSSAVEINFOS                 LIKE MASSSAVINF
        CHANGING
           WORKFLOW_RESULT               LIKE BDWF_PARAM-RESULT.
DATA FLAG_ERROR_HAPPENED.
DATA I_MERRDAT LIKE MERRDAT.
DATA IDOC_INDEX_2_SUBRC LIKE SY-SUBRC.
DATA AL_HANDLES TYPE BAL_T_LOGH. "//br99
SORT T_IDOC_ROLLNO BY ROLLNO.                        "note 315124
React on general error
IF GENERAL_SUBRC <> 0.
    REFRESH T_MERRDAT.
i_merrdat-tranc = 0.                              " //br261197
    READ TABLE IDOC_TRANC INDEX 1.     " zu 40b
    I_MERRDAT-TRANC = IDOC_TRANC-FIRST_TRANC_IDOC.          "
    I_MERRDAT-MSGTY = 'E'.
    I_MERRDAT-MSGID = SY-MSGID.
    I_MERRDAT-MSGNO = SY-MSGNO.
    I_MERRDAT-MSGV1 = SY-MSGV1. I_MERRDAT-MSGV2 = SY-MSGV2.
    I_MERRDAT-MSGV3 = SY-MSGV3. I_MERRDAT-MSGV4 = SY-MSGV4.
    APPEND I_MERRDAT TO T_MERRDAT.
ENDIF.
DATA: C_TRUE,
      C_FALSE VALUE 'X'.
If error happened ==> Rollback whole work....
LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY NA 'SDHWI'.
    EXIT.
ENDLOOP.
IF SY-SUBRC = 0.
    FLAG_ERROR_HAPPENED = C_TRUE.
    ROLLBACK WORK.
ELSE.
    FLAG_ERROR_HAPPENED = C_FALSE.
ENDIF.
Set IDOC status
two cases:
single IDOC-processing: ==> error can be written in IDOC status
package processing ==> anononymous "package error" for all IDOCs
READ TABLE IDOC_CONTRL INDEX 2.
IDOC_INDEX_2_SUBRC = SY-SUBRC.
IF SY-SUBRC = 0.
    IF 1 = 2.                          "//br40
      MESSAGE E051(B1).                                     "
    ENDIF.                                                  "
    CLEAR I_MERRDAT.
    I_MERRDAT-MSGID = 'B1'.
    I_MERRDAT-MSGTY = 'E'.
    I_MERRDAT-MSGNO = '051'.
ENDIF.
IF IDOC_INDEX_2_SUBRC NE 0 OR FLAG_ERROR_HAPPENED = C_FALSE.
Nur in diesen Fällen wird Application Log geschrieben
Delete all Successes and Dummy records from t_merrdat
DELETE t_merrdat WHERE msgty = 'S' "success         " testweise
                   OR    msgty = 'D'. "dummy           "
    LOOP AT T_MERRDAT INTO I_MERRDAT WHERE MSGTY = 'D'.     "
      I_MERRDAT-MSGTY = 'S'.                                "
      MODIFY T_MERRDAT FROM I_MERRDAT.                      "
    ENDLOOP.                                                "
ENDIF.
WORKFLOW_RESULT = 0.
LOOP AT IDOC_CONTRL.
Set IDOC status
    CLEAR IDOC_STATUS.
    IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
    IF FLAG_ERROR_HAPPENED = C_FALSE.
Application log
      PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC
                                    T_MERRDAT
                                    IDOC_STATUS
                             USING IDOC_CONTRL
                                    FLAG_ERROR_HAPPENED
                                    NO_APPLICATION_LOG
                                    MASSSAVEINFOS
                                    AL_HANDLES.
    idoc_status-status = '53'.       "OK!
    APPEND idoc_status.
JH/02.02.98/4.0C KPr100004993 (Anfang)
    Fill Return variables
      CLEAR RETURN_VARIABLES.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
      APPEND RETURN_VARIABLES.
    Verknüpfungseintrag anlegen
      READ TABLE T_IDOC_ROLLNO WITH KEY ROLLNO = IDOC_CONTRL-DOCNUM
                              BINARY SEARCH.
      IF SY-SUBRC = 0.
        RETURN_VARIABLES-DOC_NUMBER = T_IDOC_ROLLNO-ROLLNO.
        RETURN_VARIABLES-WF_PARAM = 'Appl_Objects'.
        APPEND RETURN_VARIABLES.
      ENDIF.
JH/02.02.98/4.0C KPr100004993 (Ende)
    ELSE.
      IF IDOC_INDEX_2_SUBRC NE 0.
Application Log
        PERFORM WRITE_APPL_LOG TABLES IDOC_TRANC
                                      T_MERRDAT
                                      IDOC_STATUS
                               USING IDOC_CONTRL
                                      FLAG_ERROR_HAPPENED
                                      NO_APPLICATION_LOG
                                      MASSSAVEINFOS
                                      AL_HANDLES.
      ELSE.
        IDOC_STATUS-MSGID = I_MERRDAT-MSGID.
        IDOC_STATUS-MSGTY = I_MERRDAT-MSGTY.
        IDOC_STATUS-MSGNO = I_MERRDAT-MSGNO.
        IDOC_STATUS-MSGV1 = I_MERRDAT-MSGV1.
        IDOC_STATUS-MSGV2 = I_MERRDAT-MSGV2.
        IDOC_STATUS-MSGV3 = I_MERRDAT-MSGV3.
        IDOC_STATUS-MSGV4 = I_MERRDAT-MSGV4.
        IDOC_STATUS-STATUS = '51'.     "ERROR!
        APPEND IDOC_STATUS.
      ENDIF.
    Fill Return variables
      CLEAR RETURN_VARIABLES.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
    return_variables-wf_param = c_wf_par_processed_idocs.
      RETURN_VARIABLES-WF_PARAM = 'Error_IDOCs'.
      APPEND RETURN_VARIABLES.
      WORKFLOW_RESULT = 99999.
    ENDIF.
APPEND idoc_status.
ENDLOOP.
IF NO_APPLICATION_LOG IS INITIAL.
    CALL FUNCTION 'BAL_DB_SAVE'                           "//br99
         EXPORTING
              I_IN_UPDATE_TASK = ' '
              I_SAVE_ALL       = ' '
              I_T_LOG_HANDLE   = AL_HANDLES.
       EXCEPTIONS
            LOG_NOT_FOUND    = 1
            SAVE_NOT_ALLOWED = 2
            NUMBERING_ERROR = 3
            OTHERS           = 4.
    CALL FUNCTION 'BAL_GLB_MEMORY_REFRESH'                "//br99
         EXPORTING
            I_AUTHORIZATION          =
              I_REFRESH_ALL            = ' '
              I_T_LOGS_TO_BE_REFRESHED = AL_HANDLES.
       EXCEPTIONS
            NOT_AUTHORIZED           = 1
            OTHERS                   = 2
ENDIF.
ENDFORM.                               " handle_error
Save, check and activate
11. Assigning the Inbound Function Module to Basic Type & Message Type
o     Go to T. Code WE57
o     Click on change, continue, continue and New Entries Button
o     Enter the Module as IDOC_INPUT_ZBAPI_STUD_MAS
o     Type as F
o     Basic Type as ZBAPI_STUD_IDOC
o     Message Type as ZBAPI_STUD_MAS.
o     Direction as 2
o     Save and back
Now Login in 810 client
12. Assigning the Inbound Function Module in ALE Table
o     Go to T. Code BD51
o     Click on continue, New Entries button
o     Give the Inbound Function Module IDOC_INPUT_ZBAPI_STUD_MAS
o     Give Input t. as 0 (zero)
o     Save and back
13. Creating Process Code
o     Go to T. Code WE42
o     Click on Change, New Entries Button
o     Give Process Code name as ZSTUD, give Description & Save
o     Select Processing with ALE Services Radio button
o     Select Processing by Function Module Radio button
o     Click the ALE Table (arrow Icon) in Identification
o     Give the Function Module Name ZIDOC_INPUT_ZBAPI_STUD_MAS
o     Give maximum number of repeats 0
o     Save and back, back
o     Select the process code from the list & click on Logical Messages Icon
o     Give the Message Type as ZBAPI_STUD_MAS
o     Save & Back, Save & Back, Save & Back
14. Changing the Customer Distribution model in Receiving system
o     Go to T. Code BD64
o     Click on change and Create model view button
o     Select the model view & click on Environment -> Generate Partner Profiles
o     Select Transfer IDOC Immediately and Trigger Immediately radio buttons
o     Click on Execute
o     You should get a list in green color which means it executed successfully.
15. Assigning the Process Code to Message Type in Receiving System
o     Go to T. Code WE20
o     Expand Partner Type LS
o     Select the Partner Profile STUD_S
o     Double click on Message Type ZBAPI_STUD_MAS in Inbound parmtrs.
o     Give the Process Code as ZSTUD
o     Click on Trigger Immediately Radio button
o     Save & Back
o     Save & Back
16. Creating the Selection Program (Outbound Program)
     Login in client 800.
     Go to T. Code SE38
     Create a Report Program as   ZSTUD_SEND with the following code
REPORT ZSTUD_SEND
       NO STANDARD PAGE HEADING.
TABLES: ZBAPI_STUD.
DATA: IT_STUD LIKE ZBAPI_STUD OCCURS 0 WITH HEADER LINE.
SELECTION-SCREEN:BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-H01.
SELECT-OPTIONS: S_ROLLNO FOR ZBAPI_STUD-ROLLNO.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN:BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-H02.
PARAMETERS: P_MESTYP LIKE EDIDC-MESTYP,
             P_RCVPRN LIKE TBDLST-LOGSYS.
SELECTION-SCREEN:END OF BLOCK B2.
SELECTION-SCREEN:END OF BLOCK B1.
START-OF-SELECTION.
PERFORM CREATE_STUDENT.
PERFORM CREATE_IDOC.
*&      Form CREATE_STUDENT
      sending student
FORM CREATE_STUDENT.
SELECT * FROM ZBAPI_STUD
   INTO TABLE IT_STUD
   WHERE ROLLNO IN S_ROLLNO.
ENDFORM.                    " CREATE_STUDENT
*&      Form CREATE_IDOC
      IDOC Creation
FORM CREATE_IDOC.
DATA : IMAS_DATA LIKE EDIDD OCCURS 10 WITH HEADER LINE,
       IMAS_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE,
       ICOM_CON LIKE EDIDC OCCURS 10 WITH HEADER LINE.
IMAS_CON-RCVPRT = 'LS'.
IMAS_CON-RCVPRN = P_RCVPRN.
IMAS_CON-IDOCTP = 'ZBAPI_STUD_IDOC'.
IMAS_CON-MESTYP = P_MESTYP.
IMAS_CON-DIRECT = 1.
APPEND IMAS_CON.
LOOP AT IT_STUD.
IMAS_DATA-SEGNAM = 'ZBAPI_STUD_SEG'.
IMAS_DATA-SDATA = IT_STUD.
APPEND IMAS_DATA.
ENDLOOP.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
     EXPORTING
          MASTER_IDOC_CONTROL            = IMAS_CON
        OBJ_TYPE                       = ''
        CHNUM                          = ''
     TABLES
          COMMUNICATION_IDOC_CONTROL     = ICOM_CON
          MASTER_IDOC_DATA               = IMAS_DATA
   EXCEPTIONS
        ERROR_IN_IDOC_CONTROL          = 1
        ERROR_WRITING_IDOC_STATUS      = 2
        ERROR_IN_IDOC_DATA             = 3
        SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
        OTHERS                         = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK.
LOOP AT ICOM_CON.
WRITE :/ 'IDOC: ', ICOM_CON-DOCNUM, 'CREATED SUCCESSFULLY'.
ENDLOOP.
ENDFORM.                    " CREATE_IDOC
17. Transferring the student records from 800 to 810 client
     Execute Report Program   ZSTUD_SEND
     Give the Range of Roll Nos to Transfer
     Give Message Type as    ZBAPI_STUD_MAS
     Give Receiver Logical system as   STUD_R
     Execute
     You should get the IDOC Number
     Take the IDOC Number and go to T. Code WE05 & Execute
     In Outbox you can see the IDOC Status
     Select the status record in left side window
     Double click on the Status record in right side window
     You can see the Control Record, Data Record and Status Records for that IDOC
     If the ICON is green and the status code is 3, it means the IDOC is passed to PORT Successfully.
Now Login in 810 client
     Go to T. Code WE05 & Execute
     You can see the status record in left side window
     If the status no is 53 and color is green, it means the IDOC is Posted to Application successfully.
     You can see the Log Information by double clicking on the status record in right side window.
     Now in left side window, you can see the Control Record, Data Record & Status Record of the IDOC
     Now go to T. Code SE16
     Give the table name ZBAPI_STUD & press F7
     See the contents of the table
     The table is updated with the students records transferred from 800 client with our selection program.
Reward if useful
Thanks
Jagadeesh.G

BADI_IDM_HR_COMMUNICATION update employee data in the SAP ERP HCM system.

Hi Guys,
I am using SAP identity management 7.1 and ERP ECC 6.0 EHP4. I amanage to pull data from HCM into identity store and create an account in active directory.
I am now trying to update employee data in the SAP ERP HCM system with the email address using Business Add-In (BAdI) Implementation BADI_IDM_HR_COMMUNICATION of BAdI definition BADI_EXTEND_IDENTITY.
I do not know how to call the BADI from SAP identity management.
Can you please help as i need this to finish the user provisioning ?
Many thanks

Hi Scott,
Thank you very much for your help.
I am working on trying those steps. I will let you know the result.
in this document you sent me above they mentionned "see IC-supervisors-guide.pdf that is delivered within the installation.
I did a full search on the install and could not find it.
Have you seen this file before ?
Many Thanks

HCM errors in phase Identify Objects for Transfer and Start Data Selection.

Hello Colleagues ,
Background: We are using TDMS HCM PA PD Expert package to transfer all of the HCM data
We are using TDMS 4.0 SP 5. We are trying to do the Configuraition in Identify Objects for Transfer and Start Data Selection.. In this phase, we are encountering the issue of 'choose to confirm to trigger data selection'. The only option in this activit is'confirm batch' and 'confirm online'. Even if we press the button, we are still encountering issues. What selections then or values can we use?Thank you. Kindly see screen shot
Regards,
Meinard

Hello Meinard,
There could be two issues:
First check if you have assigned the target ranges for the dialog user which you are using to select data from sender system. You need to maintain target ranges in activity 'Define target ranges for users' which you can find under activity "Configuration and Utilities in Control system".
Secondly, there could be authorizaton issues for the sender system user. Check for any authorization issue in SU53 in sender system for the user which you used to logon to sender system.
Thanks
Anita

HCM Best Practices version 1.500 (HCM Data Transfer Toolbox)

Hi,
Does anyone have the HCM Data Transfer Toolbox (BPHRDTT, HR-DTT, HRDTT)? This seems to be discontinued and been replaced by LSMW which does not provide anything even close to this tool!!!!
I wish this would have been posted in the Downloads on SDN.
Thanks
Check out the following link to see what I mean:
http://help.sap.com/bp_hcmv1500/HRBP_DTT_V1_500/index.htm
Edited by: Andreas Mau on Jan 30, 2009 8:42 AM

Hi Uwe,
Thanks for giving it a try, but my question is very specific for the reason that SAP has discontinued a perfectly good tool and replaced it with some do-over.
LSMW - is not always suitable and for large loads the performance is out of wack. You always have to start from scratch creating the stuff.
PU12 - The interface toolbox is nice but it could offer something more like XML or MHTML formating so you can actually reuse the data without pain. Also for payroll extraction on retro-results for only deltas this is not useful either.
HR-DTT - Was a tool that had all you really needed and was working just fine. It had everything not just infotypes but also T558B/C/E load although I prefer T558D than T558C. Here SAP is totally lacking support. The 2 BAPIs for BUS1023 do not support all one is only for outsourcing, the other for only B/D tables. In the code the E table update is commented out since they forgot to actually add the corresponding structure for the load as importing parameter...
SXDA - A rather unknown Data Transfer Workbench which also uses projects to organize the data transfer hooks up onto LSMW as well, but again that is where the tools end. There are no example projects for any area that are of any use. SCM/SRM has some minor examples but nothing that could be called exhaustive.
The Link: Thanks to SAP support this link has been discontinued so that no-one can ask questions any more on this issue. You may still find the docu on the service marketplace in 50076489.ZIP for HRBP_USA_V1500
Edited by: Andreas Mau on Apr 23, 2009 10:36 PM
Edited by: Andreas Mau on Apr 24, 2009 1:39 AM

Hr data transfer in SRM system throgh Idoc

Dear All,
i am trying to send data throgh idoc in sap hr in srm system i am using basic type is HRMD_ABA05 to update somefirlds from t code ppoma , when i am processing idoc my idoc status is green but changes are not gettin reflected also i am unable to see any database update in infotype 0001, will you pls tell me why this is happening and also which is table for infotype 0001.
Many Thanks
Regards
Santosh L

It is important for the user that is creating the IDOC (sending it from the source system) does actually have access to the data. The IDOC will be limited in data, dependant on the users authorisations.

Issue loading Meta Data for IDoc Type WPUKSR01 in XI Integration Repository

Hi,
I want to load the Meta Data for IDoc Type WPUKSR01 in XI Integration Repository out of BI. Unfortunately, this IDoc is not available in the IDoc List. I checked in BI and the IDoc Type is available in WE60 and WE30. Also, I can load the Meta Data for the Idoc in XI ABAP (IDX2).
Can someone tell me why the IDoc doesn't show up in XI Integration Repository Import Object List?
Thanks in advance.
Best Regards.
Alex

Hi Aamir,
The Idoc is released since Release 30A. I also tried to load the IDoc Meta Data from ERP with the same result: it does not show up in the list.
Thanks anyway.
Alex

(urgent)How to transfer(outbound) the data of invoices to flat file?

HI All,
i am new to oracle Receivables. i have assigned task like below. How to transfer Oracle Receivables data(open invoices) to flat file(format like Xl Sheet or csv).i mean to say that outbound interface with sample data and code. can some one help me to sort out this issue. pls send me sample code for invoices outbound.
Thanks.
Edited by: user627525 on Feb 18, 2009 9:30 PM

Hi, Here is what you required...Below logic shows how to use utl_file to write a data into file which is store outside of database. Please let me know in case of any additional information is required. Thanks!
V_Extract_Dir:=ltrim(rtrim('/cdunix/erp/'||V_Instance_ID||'/global/acctrecon/wrk'));
V_Rename_Dir:=ltrim(rtrim('/cdunix/erp/'||V_Instance_ID||'/global/acctrecon/snd'));
V_Fname := 'ASSURENET-GL-'||V_SOB_ID||'-'||V_Date||'-'||V_Fnum||'.csv';
FND_FILE.PUT_LINE(FND_FILE.OUTPUT,V_Fname);
V_File:=UTL_FILE.FOPEN( V_Extract_Dir,V_Fname,'w');
FOR C3 IN C2 LOOP -- Header record
UTL_FILE.PUT_LINE(V_File,'"HEADER"'||','||C3.V_Con ||','||C3.V_Total);
END LOOP;
FOR C4 IN C1 LOOP -- Body
UTL_FILE.PUT_LINE(V_File,C4.md);
END LOOP;
FOR C3 IN C2 LOOP -- Footer Record
UTL_FILE.PUT_LINE(V_File,'"FOOTER"'||','||C3.V_Con ||','||C3.V_Total);
END LOOP;
Regards,
Murali

Invoice issue -transfer to FI dat

hii all,
please resolve this issue with clarification is point-by-point.......
"Invoice amount is completely correct, but if you look at the trip details in the body of invoice they do not match.
On the service billing document the expense detail on the services invoice is determined by the "Transfer to FI" date. This is causing details to be missed for trips where the "Transfer to FI" date is in a prior billing period. This is critical as we have reached another billing cycle. I currently have 10+ invoices that are incorrect and cannot be sent to the customer."
please go through and give me the clarification ......
1. explain the issue..
2. after understand explain the steps for solving this issue...
thanks
babbal

Your question should be posted on the ERP Financials board -- it has nothing to do with Asset Accounting.

Java.lang.OutOfMemoryError during transfer of large data from SAP to PI

Hi experts,
We are trying to transfer large data from SAP to external system via PI but the transfer stucked in sm58 of SAP system with 'error java.lang.OutOfMemoryError'. We have tested before this and we can only get approximately 100K of records to go through successfully. We neeed approximately transfer 300k datas per time. Current setting of max heap size (in mb) of our PI system is 512 at message server and bootstap tab. At servers general tab the max heap size (in mb) is 2048 and its java parameters are having the values below:
-Xmx1024m
-Xms1024m
-Djco.jarm=1
-XX:PermSize=512m
-XX:MaxPermSize=512m
-XX:NewSize=320m
-XX:MaxNewSize=320m
What need to be increased to solve the error?
Thanks.
Regards,
Thava

Hi Thava,
We can set a limit on the request body message length that can be accepted by the HTTP Provider Service on the Java dispatcher. The system controls this limit by inspecting the Content-Length header of the request or monitoring the chunked request body (in case chunked encoding is applied to the message). If the value of the Content-Length header exceeds the maximum request body length, then the HTTP Provider Service will reject the request with a 413 u201CRequest Entity Too Largeu201D error response. You can limit the length of the request body using the tting MaxRequestContentLength property of the HTTP Provider Service running on the Java dispatcher. By default, the maximum permitted value is 131072 KB (or 128MB).You can configure the MaxRequestContentLength property using the Visual Administrator tool. Proceed as follows:
       1.      Go to the Properties tab of the HTTP Provider Service running on the dispatcher.
       2.      Choose MaxRequestContentLength property and enter a value in the Value field. The length is specified in KB.
       3.      Choose Update to add it to the list of properties.
       4.      To apply these changes, choose (Save Properties).
The value of the parameter MaxRequestContentLength has to be set to a high value.
In short parameters to reset values for ABAP side are
icm/HTTP/max_request_size_KB
icm/server_port_ TIMEOUT
rdisp/max_wprun_time
zttp/max_memreq_MB
Parameter to reset values for JAVA side is MaxRequestContentLength.
You can use following link to know more about ICM parameters
http://help.sap.com/saphelp_nw04/helpdata/EN/61/f5183a3bef2669e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/25/b0a4f6f2b03a43a727a165a4d6a555/frameset.htm
regards
Anupam

How to transfer the transactional dat a using ale

hi to all abap gurus
i heard that we can transfer the transactional data ( like so data , po data ) using message control technique by ale technology . . can u please give all steps in message control technique with one exapmle . i searched in the forum but i did not get answer . pls points will be rewrared for good answers. if u want to give links pls give exact links .

Hi ,
here is the configuration.
MESSAGE CONTROL (USING EDI / ALE)
For Purchase order (Message control using EDI and message type ORDERS) STEPS
Settings to be done in the Sending system
From NACE
Choose Application EF ( Purchase order), press on condition record
Output type NEU Purchase order / double click ;choose Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11) execute. Key in the data (vendor vendor11, name name1, partner function - VN, Partner Vendor11,Medium 6 (EDI), time 4(send immediately), language EN).
Press on output types , choose NEU Purchase order, double click, Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time send immediately, Transmission medium EDI, Partner function VN)
Create RFC destination from SM59 (ZNARA_ALE_EDI).
Create a port from ZNARA_ALE.
Create partner profile vendor11 under LI and not LS. PARTNER NUMBER SHOULD BE SAME AS THAT OF VENDOR SET IN THE CONDITION TYPE.
In the outbond parameters of the partner profile Vendor11 key in the data (Reciever port -> ZNARA_ALE,
Basic type ORDERS05, Message type ORDERS ) Go to the message control and key in the data (Application EF, Message type NEU, Process code ME10, Transfer immediately )
Create a purchase order from ME21 with data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11). System will generate an outbond Idoc automatically which can be seen from WE02.
For Purchase order (Message control using ALE and Message type ORDERS) - STEPS
To transfer the idoc from Client 555 to 500
Settings do be done in 555.
From NACE
Choose Application EF Purchase order, press on condition record
Output type NEU Purchase order / double click ;choose Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11) execute. Key in the data (vendor vendor11, name name1, partner function - VN, Partner Vendor11,Medium A (ALE), time 4(send immediately), language EN).
Press on output types , choose NEU Purchase order, double click, Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time send immediately, Transmission medium ALE, Partner function VN)
From SALE create two logical systems and assign them to the respective clients (ZALERECV_N 500, ZALESEND_N 555).
From SM59 create RFC destination with the same name as that of the receiving logical system (ZALERECV_N).
From BD 64(distribution model), create a model view with Technical name ZNARA_PO (message type ORDERS, Sender ZALESEND_N, Receiver ZALERECV_N). Generate partner profiles. Distribute.
Note that partner profile will be generated under LS.
Settings do be done in 500.
From NACE create two logical systems and assign them to the respective clients (ZALERECV_N 500, ZALESEND_N 555).
From BD 64(distribution model), keep the cursor on Technical name ZNARA_PO. Generate partner profiles. Note that partner profile will be generated under LS. Change the process code to ORDE in the inbond parameters .
Now in client 555, Create a purchase order from ME21 with data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11). System will generate an outbond Idoc automatically which can be seen from WE02. The purchase order details will be updated in 555 thru the inbond idoc.
IMP data for message control in Sales order creation.
Partner profile to be created under KU.
Outbond parameters in the partner profile (Message type ORDRSP, Basic type ORDERS02, partner profile - SP) In Message control (Application V1, Message type BA00, Process code SD10)
Notes:
Check the entries in the NAST table to see whether outbond idoc has been created successfully or not
If you have choosen collect idocs in the partner profile, use trans code BD87 to process them
Table EDP13 - Partner Profile: Outbound (technical parameters)
Table EDP21 - Partner Profile: Inbond (technical parameters)
Please reward if useful.

What is the procedure to transfor the data to idoc.

Hi Abapers,
What is the procedure to transfor the data to idoc.
I have added some new fields in my program. so now i need to transfer those same filed into IDOC.
Can any body tell me the procedure.
Points will be given.

Hi,
First of all, you have to find an EXIT in the driver program. In the exit, you have to populate the values to the new segments which you created.
Creation of custom idoc includes the following steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon Type the short text Enter the variable names and data elements Save it and go back Go to Edit -> Set Release Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon Select the create new option and enter a description for your basic IDOC type and press enter Select the IDOC Name and click Create icon The system prompts us to enter a segment type and its attributes Choose the appropriate values and press Enter The system transfers the name of the segment type to the IDOC editor.
Create IDOC Type
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter Click New Entries to create new Message Type Fill details Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back

HCM Data Scrambling

Hi,
I am having some trouble with HCM Data scambling. I have copied the templates from client000 as per the TDMS Operations Guide and am using the HCM_DE_Germany scrambling group with the HCM_DE_Name scrambling set only. I have removed the condition set for Mann/Frau as I am not bothered about assigning differemt names for male/female.
The scramble kind of works, the last name and first name are scrambled however the ENAME and SNAME does not get changed.
I have not changed the field set for either first name or last name, so it still includes the default :
PA0001-ENAME->TRANSLATE & TO UPPER CASE
PA0001-SNAME->TRANSLATE & TO UPPER CASE
CONCATENATE & OUT INTO & SEPARATED BY SPACE
Can anyone offer any help ?
Thanks
Craig

Hi Craig,
Techincally speaking removal of condition Set will not have any affect in Scrambling ENAME and SNAME.
Since you say you not changed the standard field-set, Its better to raise a OSS message regading the same. And your Problem will be solved as soon as possible.
Component XX-PROJ-DMS-HR.
Best Regards,
Krishna Prasad

How to transfer service ticket data from ECC6.0 to CRM 7.0 using LSMW?

how to transfer service ticket data from ECC6.0 to CRM 7.0 using LSMW?
Plz suggest me any BAPI or IDOC for that ..
thanks in Advance .

You have to convert your long string to a table of shorter strings.
There may be other ways, but one possibility is to use a loop to process you string.
while (there is something left)
put the next e.g. 1024 characters in a new row of your table
endwhile
If you need to reconstruct your string from the table, don't use simple concatenation since it will remove blanks at the end of lines. Believe me (from experience) sooner or later this will happen.
Instead you need to either set the subsections of your long string, or insert from the end of your table and keep shifting the contents (probably less efficient) right

Transfer ERP HCM data per IDoc

Similar Messages

Maybe you are looking for