GENERAL FUND ENTERPRISE BUSINESS SYSTEM. Transaction ZOS_IFV IDoc Field Values Report Job Aid

Transcription

1 GENERAL FUND ENTERPRISE BUSINESS SYSTEM Transaction ZOS_IFV IDoc Field Values Report Job Aid Version 1.0 Prepared by Accenture August 10, 2009

2 IDoc Field Values Reporting Job Aid Overview Purpose: The purpose of this job aid is to provide step-by-step instruction that end users can easily use to execute transaction ZOS_IFV for use in analyzing IDoc processing. An IDoc (Intermediate Document) is the standard GFEBS format for sending messages (transaction data, master data, etc). IDocs are used to send this data between any external systems that support IDoc processing or the conversion of IDocs to other data formats. Trigger: Use this job aid when you need to analyze the results of IDoc processing between an external system and GFEBS. Prerequisites: Understanding of use of WE02 transaction Audience: Interface Processing Monitor Helpful Hints: Fields that are not used are not referenced in this job aid. Use F1 Help for standard explanations. The R/O/C column in the field description table represents the three types of data entry fields in SAP. o R is for required fields that must be populated to complete a transaction. o O is for optional fields that are not mandatory to complete a transaction. o C is for conditional fields that are dependent on population of related fields and specific transactional events. On certain screens you may need to scroll to view additional data fields. Data used in this job aid is a representative sample of the data that is available in the production environment. Actual transaction data in the production environment may vary based upon your given scenario. There are several additional job aids related to IDoc processing o IDoc Processing Job Aid o IDoc Message Types Job Aid o Transaction SBWP Job Aid o Transaction ZOS_IST Job Aid

3 ZOS_IFV Display IDoc Field Values Purpose: The purpose of this transaction is to display IDoc field values for use in analyzing data issues as a result of IDoc processing. You can extract up to 10 different fields from IDocs using this Tool. Trigger: Use this transaction when you need to analyze IDoc data either as the result of errors that occur multiple times or to research specific data that has been received or sent to/from the GFEBS system. Start the transaction by entering the transaction code ZOS_IFV. The selection screen is shown below. It has two sections Segment Field Names and Select IDocs. IDoc Segment Field Values 1) Top Section is to type in 1) Segment Name 2) Field name OR 2) Off-Set Begin and Total Length. See next few pages for how to lookup these values for specific type of IDocs. 10 rows are available in top section. Any or All of 10 can be utilized. 2) The bottom section is for IDocs selection. This section works exactly same as WE02. Type in same selection criteria that you would use for WE02.

4 What is Segment and Field Name? The following is for IDoc number in PRD from TCode WE02. E1PORDCR1, E1BPMEPOHEADER, E1BPMEPOHEADERX, E1BPMEPOITEM etc. in left pan in Tree Structure are examples of segments. This is what you would put in the Seg. Box for each row on top section. You can extract data from different Seg.. Lookup Fields names as well while getting the Segment Names. In screenshot below, for highlighted segment E1BPMEPOHEADER in left tree structure, bottom right side shows PO_NUMBER, COMP_CODE, DOC_TYPE etc. which are field names for the selected segment. These are the fields that you can extract from multiple IDocs. Note that WE02 shows only those fields which have values. If a field within segment doesn t have a value, it won t be displayed in standard WE02. Lookup all the segment names that you want to pull data from along w/ Field names. Any number up to 10 can be extracted. First, fill in all Seg boxes and Hit Enter key. (Hitting enter key enables F4 lookup for field names in Field Name boxes for selected segments)

5

6 Now you can do F4 to Lookup Field Name for given segments. The following is an example of doing F4 from FN box for Seg. E1BPMEPOHEADER.

7 Here is how Example Selection Looks.

8 Notice the Radio Buttons?? You can either put in Field names to pull values from, or you can put in off-set values. Click on Radio Button by FN if you know what fields you want to pull data from. If you want to pull by Off-Set, Check Off radio button and put in Off-Set Begin, and total length to retrieve in the right most two boxes. In the screenshot above, First 9 Seg. are looking at specific fields in given segments. The last one is for offset. (The off-set option is mainly for those IDoc types which have only one field defined in the segment. These types of segments have all data contained in one very long field. Use the Mapping Document from TD or FD to lookup Off-Set Begin and Total Length that you want to retrieve.) Below is an example of Seg. E1BPMEPOITEM (it does have multiple fields though. The off-set function works w/ all type of segments). Suppose we want to pull first 5 chars of Field SHORT_TEXT in Segment E1BPMEPOITEM. To get the Off-Set Begin, get the segment definition by doing SE11 -> Data Type -> Seg. Name ((E1BPMEPOITEM). Then add Lengths of all the Segments that come before the field that you want, and then add 1. For Short_Text, total for all fields before it is 5+1 = 6. Add 1 to it and that is where Short_Text begins, at 7. Put in the 5 in the last box since we want to get 5 chars for Short Text.

9 *TIP*: Save this a variant if you need to extract certain Fields very often! The variant used for this example is SPSPO in PRD.

10 Execute the Program now. The output should look like below. It is standard ALV showing IDoc Number, Segment, Segment Number which the field value comes from, Field name, field content, and Off-Set Content. Note that an IDoc may have multiple segments of all types. Data is retrieved from all segments. Double clicking on any row will take you to the detailed view of the IDoc similar to transaction WE02.