Realistic release date errod idoc

Hi
in inbound process of mg type: delins and basic type: delfor01
fm:IDOC_INPUT_DELINS_START
we r getting the below error..what could be the reason?
IDoc: 0000000000401326 Status: Application document not posted
Realistic release date: 03.08.2007

Hi,
you have to check the idoc in debugg mode and pull it out the reason why i has 52 and you know how to debug inbound - go to we19 and here give any existing idoc no and press F8 and enter into screen, in that select 'INBOUND FUNCTION MODULE' select give ur standard F.M name and select the background mode.
or thre way is goto BD87 make the correct the error idoc manually.
--Use Tcode BD87 to check for IDocs that are not been processed and reactivate.
u can find here if any data wrong or missing.
Reward if useful
Regards,
Vijay

Similar Messages

Realistic release date

Hi
Am not functional.
Please can some one help me.. how realistic release date will be calculated?
I am getting error in idoc process during sales sched agreement updation.
any documents abt it pls?

This is similar to the material availability date and the schedule delivery date calcualted by system as per the Availability check and transfer of requirements.

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

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

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

SEGMENT FOR WITHOLDING TAX DATA FOR IDOC CREMAS03

Hi all!
Is there any segment for withholding tax data when creating creditor master data with IDoc CREMAS03? I need an other IDoc for this purpose?
Thanks in advance
Zapla

Dear Atul,
In function module AC_DOCUMENT_CREATE there is the structure
T_ACCWT to pass the calculated tax items. In the
BAPI_ACC_DOCUMENT_POST the corresponding BAPI structure has been added
with release 6.0. For older releases it is posssible to pass the
withholding tax items in structure EXTENSION1 and map it to T_ACCWT
using a customer exit or the Business Transaction Event RWBAPI01.
For the corresponding IDOC ACC_DOCUMENT the same holds.
From release 6.0 on there is the IDOC segment E1BPACWT09 for
passing WT information, in older releases E1BPPAREX
can be used to pass the extension data, see note 487722.
I hope this can help You.
Mauri

MSI Big Bang XPower II X79 release date

Whats the release date for this motherboard to the UNITED STATES?
MSI Big Bang XPower II X79 LGA 2011

We don't know, we have nothing to do with MSI marketing. We are MSI product users the same as you helping each other with problems and have nothing to do directly with MSI. You would need to ask MSI. Question like that my typical answer is that you will know the release date after you see it for sale in the stores.
>> How to contact MSI <<
http://us.msi.com/service/PreSaleForm/
As a matter of fact if we knew the release dates of products like that we would post it in the forum to avoid those kind of questions all of the time.

Why is it that when looking through new apps in the apps store on my ipad in release date mode does it return to the first 1-12 after viewing pparticular apps?

why is it that when I look through the new apps in the apps store in release date mode it returns to the first page after veiwing more information about some apps, I could be ten to twenty pages in and have it happen.
Also, I only speak and read English and although there are probably great apps for people from other nations, I don't want to wade through all the apps that I can't make use of. I expect that people of other nationalities or languages don't want to have to wade through every app that they can't make use of, is there not a way that alI users could filter by language?
I mean no offence to anyone but with a collection of hundreds of thousands of apps in all languages and the jump back to the begining after possibly being into the list by a number of pages I stop looking after awhile and I'm sure I've missed some excellent apps by doing so.

Contact iTunes support : http://www.apple.com/support/itunes/contact/

Standard report with po released date

hi mm experts,
request pl let me know is there any standard report which gives the po details and release indicator with released date of po.
pl help.
regards
Srihari

Hi
U can get Po release date per release code, use CDHDR and CDPOS tables in SE16
Enter transaction as ME28/ ME29N, Enter the range date,enter the object value as PO number (PO number should be 10 digit if the PO is not 10 digit, then add zero value for the prefix).
Then you can find the release date
Rest details u can find from ME2N report i.e Po details and Release indicator using dyanamic selection
Vishal...

Purchase Order released date field and table name

Hi,
Please tell me the Purchase Order released date field and table name.
Regards
Deepak

Hi,
Table : EKKO.
Fields : FRGKE,FRGZU.
You can get release date of PO from CDHDR table.
give object value as your po number and check.dont forget to give leading zeros.
The udate will be date field and transaction will be me29n for relaesed po.

Populating the data into idoc

Hi
Could you plz tell me the ways through which we can populate the data into idoc ?? I can think of two ways.
1. By writing the report program and executing the same
2. By change pointer concept.
Are there any ways through which we can populate the data into idocs ??
thanks
Kumar

Hi,
Others are
1. Creation through NAST message control
2. Creation through workflow
aRs

Release date and release no of Scheduling Agreement

Hi All,
I have a problem with Scheduling agreement.
I have created a scheduling agreement with long validity period.
I maintained delivery schedules within that validity period.
I have generated forecast schedules. then using ME84, creating a releases.
the problem is occurs here.
it was not updating the release no and release date for the schedule line.
still it is showing a *yellow light* .
where is the problem and why it was not updating.
and can u please explain the process and significance of those lights.
Thanks in Advance.
Regards
Kishore

Verify the table T161M has the values
kvewe = 'B'
kappl = 'EL'
druvo = 1
kschl = LHPA
as mentioned in the code.
The solution is add in SPAD the

Table for Invoice release date

Hello,
Can anyone tell me the table name in which I can get the Invoice release date (Invoice was blocked previously and released with MRBR). I want the date at which it is released through MRBR.
Thanks,
Input

Dear Input_Output,
When ever we perform LIV and is blocked for payment (due to price variance or other variance) is stored on table RBKP_BLOCKED
Now when we release it through t. Code MRBR that time its get deleted from RBKP_BLOCKED
Now to get the date of release Use can Use table CDHDR
Where OBJECTID =Invoice no+year (e.g 51056066022011 where is 5105606602 invoice no 2011 is year)
Tcode =MRBR
You will get the fields called UDATE and UTIME these are your release date and release time
Hope it clears

TAble for PO Release date

Hi all,
Plz tell me the table in which i can get PO Release date.
Best Regards,
Savita

Hi Savita,
The Release dates of the PO are unfortunately not stored in SAP but as stated above you can check the change documents in the follwowing manner:
Go to CDPOS table with Objectid = <PO Number> and OBJSCTCLASS = EINKBELEG and FNAME = FRGKE and NEW_VALUE = <Final release code> and get the CHANGENR from CDPOS. Then go CDHDR with the CHANGENR and get the update date..

Table for PR Release date

Hi Friends,
I want to capture the PR release date. But I could not find the table. Can anybody please provide me the table where PR relase date is captured?
In ME53N, in item detail, in "Quantities/Dates", the release date is not the actual relaease date on which the PR got released. I can see the actual release date in Environment-->Item change. But I could not find the table wheere it stores the actual release date.
Please suggest.
Thanks & Regards
Satya

Hi,
As I have explained in my mail, that field is not the actual PR release date. even afterrelease also that field is changeable. System bydefault takes the PR creation date as release date. But If I release after 10 days of PR creation, then EBAN-->FRGDT is not getting updated.
Please suggest.
Thanks & Regards
Satya

Realistic release date errod idoc

Similar Messages

Maybe you are looking for