Reports & idoc

1what is the difference between IDOC types and IDOC views?
2.What is Document Tool and what is use of it?
3.what is IDOC archiving?
4.what is the difference between watch point and break point.?
5.How to add extra functionality to a standard print program without
touching the print program?
6.what is Output Determination?
7.What is the program to get the difference between two dates.
8.Write down the program to display previous date from current date by default.
9. Develpoe a program how to set month first and last date by default
for the select-options.
10. There are two radio buttons on screen wherever select one that one will be in enable mode other will display in disable mode give the code for it.

For IDOC related info have a look at below link.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
7. U can use FM SD_DATETIME_DIFFERENCE or check below code
data: fromdate type sy-datum value 15.11.2006,
todate type sy-datum value 20.11.2006,
numofdays type i.
DATA : d TYPE sy-datum.
d = fromdate - 1.
DO.
d = d + 1.
IF d > todate.
EXIT.
endif.
CALL FUNCTION 'DATE_CHECK_WORKINGDAY'
EXPORTING
date = d
factory_calendar_id = '01'
message_type = 'I'
EXCEPTIONS
date_after_range = 1
date_before_range = 2
date_invalid = 3
date_no_workingday = 4
factory_calendar_not_found = 5
message_type_invalid = 6
OTHERS = 7.
IF sy-subrc = 0.
numofdays = numofdays + 1.
write :/ d.
ENDIF.
ENDDO.
9. Use FM HR_JP_MONTH_BEGIN_END_DATE to get start date and en day of month.
Also use below FMs to get the last day of month:
SG_PS_GET_LAST_DAY_OF_MONTH
HRVE_LAST_DAY_OF_MONTH
SLS_MISC_GET_LAST_DAY_OF_MONTH
I hope it helps.
Best Regards,
Vibha
*Please mark all the helpful answers

Similar Messages

BPMon - Idoc reporting alert types

Hi folks,
I configured a biz process scenario where an ECC system delivers Idoc to a PI system.
I want to trace the average time to process IDocs, so I activated Idoc Reporting alert type. As filters I set to monitor only outbound Idocs, of type ZORDERS (customer type) for today as selected day and monitoring idocs from state 01 to 03.
The very strange thing is that this type of metric seams to compute mesures in an esotic way. In fact, this morning, for example, the monitor told me that for 4 Idocs monitored the average processing time was about 2100 seconds, but checking these idocs in we05 I found the times you can see below:
Idoc n°             init state     final state      delta time (sec)
25491614     02:40:19     02:40:20                1
25472952     02:48:33     02:48:34                1
25468881     04:50:33     04:50:33                0
25490739     05:25:59     05:26:00                1
                                                       0,75     avg time (sec)
so my expectation was to have an average value 0.75 sec and not 2000+.
Anyone of you as faced this kind of issue?
many thanks
BR
Roberto

Hi all,
I solved the issue, in fact, referring to the idocs times I reported, Idoc n° 3 wasn't in my final state = to 03 but in state 26. So this means that solman takes as starting time 04:50:33 and, as final time, the instant at the moment of measure. So if solman measure idoc data at 05:30:33 as happened, delta time for idoc 3 is 2400 secs.
To solve it, I set parameter status message number = to 083 into my idoc filter, in such a way solman consider only idoc with final state 03 and that message numer.
cheers
Roberto

Error while testing Inbound Idoc

The error message "Interface for function Z***** is incorrect*." is shown while trying to test an incoming IDOC in we19.
PL HELP!!!!!!!
The procedure followed by me was,
WE31 created custom segments,
WE30 Created custom basic type,
we81 Custom message type,
se37 function module,
we82,
we57,
bd51,
we42,
bd67,
we20,
Am not able to figure out why exactly is the error message being shown.
please tell me if a step was missed or what the possible error is, I think the parameters of function module are correct....

Hi friend,
if it is help full please give max reward point.
Standard program, RBDMOIND is scheduled or executed online to determine whether the communication was successful. If IDoc is Dispatched to destination system, RBDMOIND updates the status of the IDoc to 12 (Dispatched OK), Otherwise remains in status 03.
Two programs enable cross-system reporting:
     RBDSTATE: It reports the status of the incoming IDocs to sending system, using ALEAUD message and ALEAUD01 IDoc
     RBDAUD01: It executed on sending system to analysis the audit log and display the output as a report
IDoc Status in Receiving System          IDoc status in Sending System via ALEAUD
53 Application docu posted     =>     41 Application docu created in receiving sys
51 Error: Application docu      =>     39 IDoc in receiving sys. Status repeated
     not posted                         each time RBDSTATE runs.
68 Error: No further processing     =>     40 Application docu not created
ALE Auditing
BDM7          =>     ALE Audit: Statistical Analysis
BDM8          =>     ALE Audit: Sending the Confirmations
RBDSTATE     =>     Run on Receiving System to return Audit Message

Processing of multiple IDocs and their status

Hi guys,
I have a problem with IDoc processing in R/3. I send multiple IDocs into R/3. These are my own IDoc types, and I send them there in a "package". Let's say, I send 5 IDocs of the same type. Each of them has the number, and each of them has the number of the whole set - this means - you know, that this one IDoc is the 1st from the 5, this one is the 3rd, and this one is the last. When they are sent, the processing of them comes... And I have an ABAP program, if the last of them is processed, errors are taken and a new report IDoc is created and sent into external application.
THE PROBLEM IS: the processing of the IDocs is parallel and when the - let's say 4th IDoc processing takes longer time than the 5th processing takes, not all of the errors are taken into the report, because some errors may occur after (the 4th IDoc processing is independent).
Do you have any ideas, how could I solve this problem?
Thanx, Peter

Peter,
Here is my suggestion, the code that actually checks for errors and sends a report IDOC, why can't we put in a check to see if all the IDOC's of a particular set have been processed or not.
How exactly this new report IDOC is being created, there has to be some kind of logic to find out IDOCS that belong to the same set.
Regards,
Ravi
Note : Please reward the posts that help you.

Need Code to generate Inbound Idocs

Hi friends
i have a flat file consists of delivery confirmation data
by using this i need to generate inbound idocs
i filled all the segments in idoc type /afs/delvry03 and message type whscon
can any one have the code to generate inbound idocs
please remember that here i am not using XI
thanks
Anil

Hi this is for Stand alone Programs, I hope it is useful to you.
Program Flow
The program logic contains the following blocks:
1. Provide a selection screen to allow a user to specify the various objects for which IDocs are to be generated.
2. Determine the key of the application document from the object specified in step 1.
3. Select application data from the database using the object key identified in step 2.
4. Populate control record information.
5. Populate an internal table of type EDIDD with data records for the various segments.
6. Call the ALE service layer (MASTER_IDOC_DISTRIBUTE) to create the IDocs in the database.
7. Commit work.
The program in Listing 32-2 generates the monthly report IDoc ZMREPT01, which illustrates a stand-alone outbound process.
Listing 32-2
REPORT ZARNEDI1 MESSAGE-ID ZE.
Parameters
object key (Social security number for the employee)
PARAMETERS: P_SSN LIKE ZEMPDETAIL-SSN.
message type
PARAMETERS: P_MESTYP LIKE EDMSG-MSGTYP OBLIGATORY.
destination system
PARAMETERS: P_LOGSYS LIKE TBDLST-LOGSYS.
Constants
DATA:
    segment names
        C_HEADER_SEGMENT           LIKE EDIDD-SEGNAM VALUE 'Z1EMHDR',
        C_WEEKLY_DETAILS_SEGMENT   LIKE EDIDD-SEGNAM VALUE 'Z1WKDET',
        C_CLIENT_DETAILS_SEGMENT   LIKE EDIDD-SEGNAM VALUE 'Z1CLDET',
        C_SUMMARY_SEGMENT          LIKE EDIDD-SEGNAM VALUE 'Z1SUMRY',
    idoc type
        C_MONTHLY_REPORT_IDOC_TYPE LIKE EDIDC-IDOCTP VALUE 'ZMREPT01'.
Data declarations
idoc control record
data: control_record_out like edidc.
employee header data
DATA: FS_EMPHDR_DATA LIKE Z1EMHDR.
employee weekly details data
DATA: FS_WEEKDET_DATA LIKE Z1WKDET.
client details data
DATA: FS_CLIENTDET_DATA LIKE Z1CLDET.
employee monthly summary data
DATA: FS_SUMMARY_DATA LIKE Z1SUMRY.
total hours and amount for the summary segment
DATA: TOTAL_HRS_MONTH TYPE I,
        TOTAL_AMT_MONTH TYPE I.
Database Tables
Application data tables
TABLES: ZEMPDETAIL, ZEMPWKDET.
Internal tables
DATA:
    weekly details - appplication data
        IT_WKDET LIKE ZEMPWKDET OCCURS 0 WITH HEADER LINE,
    data records
        INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE,
    communication idocs geneerated
        IT_COMM_IDOCS LIKE EDIDC OCCURS 0 WITH HEADER LINE.
Program logic
********************Select Application Data***************************
SELECT SINGLE * FROM ZEMPDETAIL WHERE SSN = P_SSN.
IF SY-SUBRC NE 0.
     MESSAGE E001 WITH P_SSN.
     EXIT.
ENDIF.
SELECT * FROM ZEMPWKDET INTO TABLE IT_WKDET WHERE SSN = P_SSN.
IF SY-SUBRC NE 0.
     MESSAGE E002 WITH P_SSN.
     EXIT.
ENDIF.
********************Build Control Record******************************
Fill control record information
CONTROL_RECORD_OUT-MESTYP = P_MESTYP.
control_record_out-idoctp = c_monthly_report_idoc_type.
control_record_out-rcvprt = 'LS'.
control_record_out-rcvprn = p_logsys.
********************Build Data Records********************************
*--Employee header--
fill the employee header information
FS_EMPHDR_DATA-LNAME = ZEMPDETAIL-LNAME.
FS_EMPHDR_DATA-FNAME = ZEMPDETAIL-FNAME.
FS_EMPHDR_DATA-SSN   = ZEMPDETAIL-SSN.
FS_EMPHDR_DATA-DOB   = ZEMPDETAIL-DOB.
fill the administrative section of the data record
INT_EDIDD-SEGNAM = C_HEADER_SEGMENT.
INT_EDIDD-SDATA = FS_EMPHDR_DATA.
append the employee header data record to the IDoc data
APPEND INT_EDIDD.
*--Employee weekly details--
LOOP AT IT_WKDET.
fill the weekly details for each week
    FS_WEEKDET_DATA-WEEKNO = IT_WKDET-WEEKNO.
    FS_WEEKDET_DATA-TOTHOURS = IT_WKDET-TOTHOURS.
    FS_WEEKDET_DATA-HRLYRATE = IT_WKDET-HRLYRATE.
add administrative information to the data record
    INT_EDIDD-SEGNAM = C_WEEKLY_DETAILS_SEGMENT.
    INT_EDIDD-SDATA = FS_WEEKDET_DATA.
append the data for the week to the IDoc data
    APPEND INT_EDIDD.
Client details of each week
    FS_CLIENTDET_DATA-CLSITE = IT_WKDET-CLSITE.
    FS_CLIENTDET_DATA-WORKDESC = IT_WKDET-WORKDESC.
add administrative information to the data record
    INT_EDIDD-SEGNAM = C_CLIENT_DETAILS_SEGMENT.
    INT_EDIDD-SDATA = FS_CLIENTDET_DATA.
append the client details for the week to the IDoc data
    APPEND INT_EDIDD.
ENDLOOP.
*--Employee monthly summary--
compute total hours and amount for the month
LOOP AT IT_WKDET.
    TOTAL_HRS_MONTH = TOTAL_HRS_MONTH + IT_WKDET-TOTHOURS.
    TOTAL_AMT_MONTH = TOTAL_AMT_MONTH + ( IT_WKDET-TOTHOURS *
                                          IT_WKDET-HRLYRATE ).
ENDLOOP.
fill the summary information
FS_SUMMARY_DATA-TOTHRS = TOTAL_HRS_MONTH.
FS_SUMMARY_DATA-TOTAMT = TOTAL_AMT_MONTH.
condense the summary record fields to remove spaces
CONDENSE FS_SUMMARY_DATA-TOTHRS.
CONDENSE FS_SUMMARY_DATA-TOTAMT.
add administrative information to the data record
INT_EDIDD-SEGNAM = C_SUMMARY_SEGMENT.
INT_EDIDD-SDATA = FS_SUMMARY_DATA.
append summary data to the IDoc data
APPEND INT_EDIDD.
*************Pass control to the ALE layer****************************
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
       EXPORTING
            master_idoc_control            = control_record_out
       TABLES
            COMMUNICATION_IDOC_CONTROL     = IT_COMM_IDOCS
            MASTER_IDOC_DATA               = INT_EDIDD
       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 NE 0.
     MESSAGE E003 WITH P_SSN.
ELSE.
     LOOP AT IT_COMM_IDOCS.
       WRITE: / 'IDoc generated', IT_COMM_IDOCS-DOCNUM.
     ENDLOOP.
     COMMIT WORK.
ENDIF.

Urgent! Title in the center for ALV GRID

Hi,
I'm using FM REUSE_ALV_GRID_DISPLAY.
I need to make a header like this:
Reporting idocs (center of alv)        data time
Material & batch (center of alv)
Can anyone tell me how?
Thanks!

Hi ,
Below is the sample code you can refer.
This code also contain e.g. doing subtotals,interactive capalities of ALV ,Puting header etc. refer this code it will be very beneficial.
REPORT ZSAND_SUBTOTAL LINE-COUNT 65                        .
*& Report ZALV_LIST
TABLES : mseg.
TYPE-POOLS : slis.
DATA : BEGIN OF itab OCCURS 0,
        mblnr LIKE mseg-mblnr,
        matnr LIKE mseg-matnr,
        werks LIKE mseg-werks,
        menge LIKE mseg-menge,
        line_color(4) TYPE c,
       END OF itab.
DATA : BEGIN OF itab1 OCCURS 0,
        mblnr LIKE mseg-mblnr,
        matnr LIKE mseg-matnr,
        werks LIKE mseg-werks,
        menge LIKE mseg-menge,
        line_color(4) TYPE c,
        END OF itab1.
data: it_sortcat   type slis_sortinfo_alv occurs 1,
       wa_sort like line of it_sortcat.
DATA: it_header TYPE slis_t_listheader,
        wa_header TYPE slis_listheader.
data: var1(1).
DATA var2.
data:mytabix like sy-tabix.
data:wtab1 like line of itab,
     wtab2 like line of itab.
DATA : t_fcat TYPE slis_t_fieldcat_alv,
t_eve TYPE slis_t_event,
t_subtot TYPE slis_t_sortinfo_alv,
subtot LIKE LINE OF t_subtot,
wa_fcat LIKE LINE OF t_fcat,
gd_layout TYPE slis_layout_alv.
DATA : gt_menge LIKE mseg-menge,
st_menge LIKE mseg-menge.
data:it_extab type SLIS_t_EXTAB,
     wa_extab like line of it_extab.
SELECTION-SCREEN : BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001.
SELECT-OPTIONS : doc FOR mseg-mblnr.
SELECTION-SCREEN : END OF BLOCK blk1.
START-OF-SELECTION.
PERFORM build_cat USING t_fcat.
PERFORM build_layout.
PERFORM build_eve.
perform fill_sort.
PERFORM get_data.
PERFORM display.
*& Form build_cat
*text
*-->TEMP_FCAT text
FORM build_cat USING temp_fcat TYPE slis_t_fieldcat_alv.
wa_fcat-tabname = 'ITAB'.
wa_fcat-fieldname = 'MBLNR'.
wa_fcat-seltext_m = 'Material Doc.'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
wa_fcat-tabname = 'ITAB'.
wa_fcat-fieldname = 'MATNR'.
wa_fcat-seltext_m = 'Material'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
wa_fcat-tabname = 'ITAB'.
wa_fcat-fieldname = 'WERKS'.
wa_fcat-seltext_m = 'Plant'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
wa_fcat-tabname = 'ITAB'.
wa_fcat-fieldname = 'MENGE'.
wa_fcat-seltext_m = 'Quantity'.
wa_fcat-do_sum = 'Y'.
APPEND wa_fcat TO temp_fcat.
CLEAR wa_fcat.
ENDFORM. "build_cat
*& Form build_eve
*text
FORM build_eve.
DATA : wa_eve TYPE slis_alv_event.
data:mytabix type sy-tabix.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
i_list_type = 0
IMPORTING
et_events = t_eve
EXCEPTIONS
list_type_wrong = 1
OTHERS = 2.
IF sy-subrc <> 0.
*MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE t_eve into wa_eve WITH KEY name = slis_ev_top_of_page.
*INTO wa_eve.
IF sy-subrc = 0.
mytabix = sy-tabix.
MOVE 'TOP_OF_PAGE' TO wa_eve-form.
append wa_eve to t_eve.
*modify t_eve from wa_eve index mytabix transporting form.
ENDIF.
READ TABLE t_eve into wa_eve WITH KEY name = slis_ev_end_of_page.
*INTO wa_eve.
IF sy-subrc = 0.
mytabix = sy-tabix.
MOVE 'END_OF_PAGE' TO wa_eve-form.
append wa_eve to t_eve.
*modify t_eve from wa_eve index mytabix transporting form.
ENDIF.
ENDFORM. "build_eve
*& Form build_layout
*text
FORM build_layout.
*gd_layout-no_input = 'X'.
gd_layout-colwidth_optimize = 'X'.
gd_layout-info_fieldname = 'LINE_COLOR'.
gd_layout-subtotals_text = 'SUBTOTAL'.
*gd_layout-totals_text = 'TOTAL'.
gd_layout-EDIT = 'X'.
ENDFORM. " BUILD_LAYOUT
*& Form get_data
*text
FORM get_data.
SELECT mblnr matnr werks menge FROM mseg INTO CORRESPONDING FIELDS OF
TABLE itab
WHERE mblnr IN doc.
SORT itab BY mblnr.
sort itab by mblnr matnr.
read table itab into wtab1 index 1.
mytabix = 1.
loop at itab into wtab2 from 2.
if wtab1-mblnr = wtab2-mblnr and wtab1-matnr = wtab2-matnr.
wtab1-menge = wtab1-menge + wtab2-menge.
modify itab from wtab1 index mytabix.
else.
modify itab from wtab1 index mytabix.
clear wtab1.
mytabix = sy-tabix.
move wtab2 to wtab1.
endif.
clear wtab2.
endloop.
delete ADJACENT DUPLICATES from itab comparing mblnr matnr.
ENDFORM. "get_data
*& Form display
*text
FORM display.
wa_extab-fcode = '&ETA'.
append wa_extab to it_extab.
wa_header-typ = 'H'.
   wa_header-info = 'SANDY is Great'.
   append wa_header to it_header.
   clear wa_header.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_INTERFACE_CHECK                 = ' '
I_BYPASSING_BUFFER                = ' '
I_BUFFER_ACTIVE                   = ' '
   I_CALLBACK_PROGRAM                = 'ZSAND_SUBTOTAL'
I_CALLBACK_PF_STATUS_SET          = ' '
   I_CALLBACK_USER_COMMAND           = 'USERCOMMAND'
    I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE'
I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
I_CALLBACK_HTML_END_OF_LIST       = ' '
I_STRUCTURE_NAME                  =
I_BACKGROUND_ID                   = ' '
I_GRID_TITLE                      =
I_GRID_SETTINGS                   =
   IS_LAYOUT                         = gd_layout
   IT_FIELDCAT                       = t_fcat
   IT_EXCLUDING                      = it_extab
IT_SPECIAL_GROUPS                 =
   IT_SORT                           = it_sortcat
IT_FILTER                         =
IS_SEL_HIDE                       =
I_DEFAULT                         = 'X'
I_SAVE                            = ' '
IS_VARIANT                        =
IT_EVENTS                         = t_eve[]
IT_EVENT_EXIT                     = 'BUILD_EVE'
IS_PRINT                          =
IS_REPREP_ID                      =
I_SCREEN_START_COLUMN             = 0
I_SCREEN_START_LINE               = 0
I_SCREEN_END_COLUMN               = 0
I_SCREEN_END_LINE                 = 0
IT_ALV_GRAPHICS                   =
IT_HYPERLINK                      =
IT_ADD_FIELDCAT                   =
IT_EXCEPT_QINFO                   =
I_HTML_HEIGHT_TOP                 =
I_HTML_HEIGHT_END                 =
IMPORTING
E_EXIT_CAUSED_BY_CALLER           =
ES_EXIT_CAUSED_BY_USER            =
TABLES
    t_outtab                          = itab
EXCEPTIONS
PROGRAM_ERROR                     = 1
OTHERS                            = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. "display
***& Form top_of_page
*text
FORM top_of_page.
if var1 is initial.
wa_header-typ = 'H'.
   wa_header-info = 'SANDY is Great'.
   append wa_header to it_header.
   clear wa_header.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
    IT_LIST_COMMENTARY       = it_header
    I_LOGO                   = 'HR_LOGO'
I_END_OF_LIST_GRID       =
          var1 = 'X'.
endif.
ENDFORM. "top_of_page
FORM end_of_page.
if var2 is initial.
wa_header-typ = 'H'.
   wa_header-info = 'SANDY is Great'.
   append wa_header to it_header.
   clear wa_header.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
    IT_LIST_COMMENTARY       = it_header
    I_LOGO                   = 'HR_LOGO'
I_END_OF_LIST_GRID       =
          var2 = 'X'.
endif.
ENDFORM. "top_of_page
*&      Form fill_sort
      text
--> p1        text
<-- p2        text
form fill_sort .
wa_sort-spos      = 1.
wa_sort-fieldname = 'MBLNR'.
wa_sort-SUBTOT    = 'X'. "subtotals any totals column by this field
gd_sortcat-tabname
APPEND wa_sort TO it_sortcat.
wa_sort-spos      = 2.
wa_sort-fieldname = 'MATNR'.
gd_sortcat-tabname
APPEND wa_sort TO it_sortcat.
endform.                    " fill_sort
FORM status USING rt_extab TYPE slis_t_extab.
set pf-status 'ZSTANDARD'.
endform.
form USERCOMMAND USING R_UCOMM type sy-ucomm
                       rselfield type slis_selfield .
set parameter id 'MAT' field rselfield-value .
call transaction 'MM03' and skip first screen.
endform.

Delivery Output & Billing Output

Hi All,
Are there any standard transactions for Delivery and billing ouputs, other than VL02N & VF02
So that user can view and take print outs of only those documents.
Thanks & Rgds
Naveen

Hi Naveen
DELIVERY OUTPUT:
VL71    Output from Outbound Deliveries
VL74    Output from Handling Units
VL70    Output From Picking Lists
VL75    Shipping Notification Output
FOR GENERAL TRANSACTION CODE REFER BELOW:
VL02N    Change delivery document
VL04    Delivery due list
VKM5    List of deliveries
VL06G    List of outbound deliveries for goods issue
VL06P    List of outbound deliveries for picking
VL09    Cancel goods issue
VT02N    Change shipment
VT70    Output for shipments
BILLING:
VF02    Change billing document
VF11    Cancel Billing document
VF04    Billing due list
FBL5N    Display Customer invoices by line
FBL1N    Display Vendor invoices by line
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
VL04    Delivery due list. Run the delivery due with your order number to create the delivery
LT03    Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
In LT03 go to menu option Transfer Order -> Confirm Transfer Order
Enter
Save
The transfer order is now confirmed.
VL02N    Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit
FOR ALL THE REQUIREMENT:
Transactions
search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
EDI Specific Transactions
VOE1    Translation between EDI categories and SD item categories
VOE2    Table EDSC view. Customer link to sales area detail
VOE3    Table view EDPVW. Add partner types that will be transferred to the IDoc
VOE4    Table view EDPAR. Link external partner number with our internal number
WEDI    EDI Administrator Menu
BALE       Idoc Administration
Scheduling agreements
OVA9    Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
OVAI    Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
OVAJ    If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
IDoc Transactions
WE09 / WE02    IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05    View IDocs
WE19    EDI test tool. Use to test inbound Function module changes.
WE20    Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30    Create IDoc extension type
WE31    Segment create
WE57    Assign function module to logical message and IDoc type
WE60    IDoc type documentation tool
WE82    Link Release detail to Extension IDoc Type
BD55    Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87    Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA    ALE Application Distribution
BALM    ALE Master Data Distribution
Output determination
856 - ASN
V/36   Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 V7ALLE SHAD for grouped ASNs. I.e. Group deliveries into shipments
VV21,VV22,VV23   Create output condition records for shipping. LAVA WE (Partner function) - We must add each new partner with VV21
VL71   Reissue output for deliveries
810 - Invoice
V/54   Maintain access sequence for billing documents
VV31,VV32,VV33   Create condition records for billing documents. (RD00 RE Billing party)
VF31   Reissue output for billing documents
855 Order Response
V/30   Sales document output types (BA00)
V/48, V/32, V/43   Maintain access sequence for sales documents
VV11,VV12,VV13   Create condition records for sales documents. (BA00 SP Sold to party)
Requirements coding
V/27    Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
VA02    Sales order change
VA05    List of sales orders
VA22    Quotation change
VA32    Scheduling agreement change
VA42    Contract change
Billing
VF02    Change billing document
VF11    Cancel Billing document
VF04    Billing due list
FBL5N    Display Customer invoices by line
FBL1N    Display Vendor invoices by line
Delivery
VL02N    Change delivery document
VL04    Delivery due list
VKM5    List of deliveries
VL06G    List of outbound deliveries for goods issue
VL06P    List of outbound deliveries for picking
VL09    Cancel goods issue
VT02N    Change shipment
VT70    Output for shipments
General
VKM3, VKM4    List of sales documents
VKM1    List of blocked SD documents
VD52    Material Determination
Workflow
SWEAD    Event queue administration
SWE2    Event type linkages
SWE3    Event linkages
PPOME    Organizational Unit Maintenance
SWE5    Consistency Checks for Event Linkages
SWUD    Workflow Diagnostic Tool
General
The following section provides detail on other useful SAP areas.
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
VL04    Delivery due list. Run the delivery due with your order number to create the delivery
LT03    Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
In LT03 go to menu option Transfer Order -> Confirm Transfer Order
Enter
Save
The transfer order is now confirmed.
VL02N    Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit
Purchase Orders
ME22N      PO Change
ME57         Create PO from purchase requisition
Goods Movement
MIGO    Post goods receipt
Other
MD04    Material Requirements. Shows material requirements and releases against materials
SE38    ABAP Editor. Used to modify ABAP programs
SM01    Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
SHDB    Transaction recorder (BDC)
CMOD    User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
SE16    Table contents display
SOST    View mails sent externally from SAP
SU53    Check authorization object
SQVI    Table Quickviewer Used to created quick client dependent reports
ST22    ABAP Dump Analysis
ST01    System trace
ST11   Display developer trace
ST05          SQL Trace
SM21          System log
ST22           Display short dumps
SM12          Display locked entries
Programs
List of ABAP Reports
Idoc
RBDAPP01   Post inbound Idocs to application documents
RBDAGAI2   Re-processing of IDocs after ALE input error
RBDAGAIE   Reprocessing of edited IDocs
RBDMANIN   Start error handling for non-posted Idocs
RSEINB00   Idoc inbound processing by file
RSEOUT00   Process outbound IDocs
General
RV80HGEN    Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.
RSWUWFML    Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status' sent from SAP.
RHSOBJCH    Corrects the following error in workflow customizing:
Transport object PDST
Information Table SOBJ is consistent as regards key tables
**Error** Table HRP1600 Not an entry in table SOBJ
Information Table SOBJ is consistent as regards PAD tables
See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.
RSPO0075    Run report RSPO0075 to activate access method M for device types.
Reward if useful to u
Message was edited by:
        narendran vajravelu

Change Pointers for Vendor Master

Hi All,
I have to activate change pointers for Vendor Master data. I have some doubts regarding the same.
1. An Idoc will be generated for newly created vendor, right?
2. If I extend the vendor master IDOC, where should I write code to extract the values of newly added fields?
3. If I create a custom IDOC for vendor master, what is the procedure to configure this in the change pointers for Vendor Master?
Thanks & Best Regards,
Kumar.

>
Sivapuram Phani Kumar wrote:
> Hi All,
>
> I have to activate change pointers for Vendor Master data. I have some doubts regarding the same.
>
> 1. An Idoc will be generated for newly created vendor, right?
> 2. If I extend the vendor master IDOC, where should I write code to extract the values of newly added fields?
> 3. If I create a custom IDOC for vendor master, what is the procedure to configure this in the change pointers for Vendor Master?
>
> Thanks & Best Regards,
> Kumar.
Hi,
1. Afer doing all the settings required to create change pointers (BD61, BD50, BD52), the idocs will be created when u run the report RBDMIDOC or execute transaction BD21.if any changes happen in master data
like new vendor is created or vendor data is changed, then only change pointers will be created and on executing the aforesaid report, idocs will be generated.
Also idocs can be generated by replicating vendor data through transaction BD14 or any other custom transaction.
2. When you add custom segments to basic type, you have to write code in suitable user exits.
Identify suitable user exit to populate data in custom segments and write the code in oubound side.
Identify suitable user exit to populate the values in custom segments to database table, this code is to be written in inbound side.
Regards
Vinod

Watch this user - Moderators

Hi,
I have watching this user for quite a while. He is giving more points to a particular user. Please don't do this here after. It affects the enthusiasm of other user.
Don't encourage this kind of users.
answers plz
Re: Types of reports
idocs
ABAP Certification
Regards....
Arun.

Can you be a bit more specific on this?

Report for multiple IDOCs with multiple POs

Hi,
In our project PO goes out to vendor through EDI 850 and Outbound IDOC is generated for this.Some times its failed due to connection issue at vendors end. so sometimes we need to send PO nos and its related IDOC nos to EDI team as per their request.I can get IDOC number for a particular PO from WE09.But that transaction is for single PO i belief.But sometimes there are 20-30 pos and if we want to search its related IDOC at a single time then how can i search this in SAP?Is there any standard SAP functionality or i have go custom report?

you need to copy the idoc failed idoc numbers, and segment name in which your PO resides
Go to table EDID4, pass Segment name and idoc numbers, you will find all related PO numbers in
Application data column, please note this column is a merged column
You will need to download it as unconverted Text , call in Excel -Text column and get the records
There is no other easy way for this
Thanks
DD

Custom report error through idoc

Hi
We have the custom invoice report .
Purpose of the custom report is to get the parked invoice list, which are invoices not posted those invoice will get parked automatically..
These invoices are usually posted in transaction MIRO throgh IDOC. So there is no manual input while doing MIRO. But now many invoices are getting parked instead of posting .
So for above proble i wanted to know the automatic backend job after IDOC for invoice posting .
How exactly the automatic posting of invoice is happening in backend , how we can rectify this or how we can find the creteria for posting and paring invoice in backend program ????
Thanks

Hi,
when we submit the request in SRS the output is fine generating but when we do the trtansaction in the Module(no SRS) the report is erroring outWhat do you mean by do transaction in the module? Could you please elaborate more?
Enable trace and run the program, and see if the collects more details about the error in the request log file.
Regards,
Hussein

Standard Report with IDOC Number and PR number

Hi
My client need the Standard report with the combination fields of " Purchasing Number , Requirements tracking number in PR,
IDOC number , IDOC Processing status. "
(Our PR will generates through IDOC from other system via XI interface)

Hi Nagendra,
for Purchasing Number , Requirements tracking number in PR you can use -ME5A
Purchasing Number-EBAN-BANFN
Tracking number goto- MELB.
table name-EKPO
for IDOC number , IDOC Processing status -we09
For IDOC number -EDID4-DOCNUM
IDOC Processing status-EDIDC-STATUS
Regards,
Krishna.
Edited by: kris_hna on Sep 8, 2011 1:14 PM
Edited by: kris_hna on Sep 8, 2011 1:19 PM

Status report of idoc.

Hi,
I need to generate a status report for an idoc which I have processed using the FM IDOC_INBOUND_AYNCHRONOUS.The FM only takes the control and data sections of the idoc.Could anyone help me to know how to generate a status report for this idoc?

Hi Sandeep,
Please refer the link,
Report to display all the status records of an Idoc
Best Regards.
Reward points if it is useful.

Report RSMIPROACT gives Customer could not be determined for IDOCs

Hi Friends,
I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
I have noticed that 2 things .
1. E1ADRE1 field is NOT being sent by the ECC system .
2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
Has anybody faced this problem before ?
I look forward to replies.
Detailed error is given below.
Regards,
Ranjini.
Customer could not be determined
Message no. /SAPAPO/EDI010
Diagnosis
The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
The section was not available in the processed IDoc.
System Response
The system cancels processing.
Procedure
Configure the EDI convertor in such a way that the corresponding section has a value.

Hi,
i'm facing the same problem. Could you solve it?
Regards

Report layout to idoc

can i send report layout to idoc

I understand what you are saying.
Leave this first date column as it is but create a third column to the left of the first date column. And put a MIN(promotion date) formula on this. Now your new column will pull a single date for the combination of the 03 GHI. We still need the original promotion date column for our promotion date2 column to work correctly. but we dont have to show it. so adjust the format of this column (white on white) so that its hidden.
Thanks,
Karthik

Reports & idoc

Similar Messages

Maybe you are looking for