GENERAL FUND ENTERPRISE BUSINESS SYSTEM. Transaction SBWP IDoc Error Reporting via Business Workplace Job Aid

Transcription

1 GENERAL FUND ENTERPRISE BUSINESS SYSTEM Transaction SBWP IDoc Error Reporting via Business Workplace Job Aid Version 1.0 Prepared by Accenture August 10, 2009

2 IDoc Error Reporting via SBWP 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 SBWP for use in analyzing IDoc errors. 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. Business Workplace is similar to many software products in that you can send and receive messages. When IDoc errors occur an message can be sent to a user(s) associated with the unique interface Message Type. Trigger: Use this job aid when you need to review the errors that occurred during routine 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. There are several additional job aids related to IDoc processing o IDoc Processing Job Aid o IDoc Message Types Job Aid o Transaction ZOS_IFV Job Aid o Transaction ZOS_IST Job Aid

3 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.

4 SBWP Display IDoc Errors Purpose: The purpose of this transaction is to review IDoc errors and take any corrective action that is needed. Trigger: Use this transaction when you need to review IDoc errors when interface data that has been received or sent to/from the GFEBS system. Start the transaction by entering the transaction code SBWP. The main screen is shown below.

5 Expand the Inbox folder by clicking on the arrow to the left of the Inbox icon. The resulting screen is shown below. Expand the Workflow Inbox by clicking on the arrow to the left of the Workflow Inbox icon. The resulting screen is shown below.

6 There are several ways to view the IDoc errors presented here Grouped According to Content, Grouped According to Task, Grouped According to Content Type and Grouped According to Sort Key. First we will look at the Grouped According to Content Folder. Expand the Grouped According to Content folder by clicking on the arrow to the left of the folder icon. The resulting screen is shown below.

7 Notice that there are IDoc numbers displayed in this folder. These IDocs are displayed in numerical order and are only shown in this folder if an error has occurred with the IDoc. Click on any of these IDocs and the right hand side of the screen will display additional information about the IDoc error. In this example IDoc has been clicked and the resulting screen is displayed below.

8 Click on the Display button. The resulting screen is shown below. Select the Available objects tab

9 The display button that corresponds to the Application IDoc link under the Process objects folder will take you to the IDoc Display screen shown below. This is the same screen you would see if you display an IDoc using transaction WE02. Use the back button at the top of the screen to return to the SBWP screen.

10 When you are back in the SBWP screen, by double clicking anywhere on the line showing the Title, Status, Creation Date, etc you will be taken to the Display Status Record screen shown below. This is the same screen you would see if you click on the Page icon next to the status record in transaction WE02. Click the back button at the top of the screen to return to the SBWP screen.

11 Now you can close the Grouped According to Content folder and expand the Grouped According to Task folder. The resulting screen is shown below. Click the link Inbound, error message with IDoc. The resulting screen is shown below.

12 Notice on this screen that the IDoc error messages are displayed in a list. The first line on the right hand side of the screen is highlighted. To see additional information about this IDoc error, such as the IDoc number, double click the desired IDoc from the list. The Display IDoc detail screen is discussed previously in the Grouped According to Content section. Notice the Menu bar at the top right side of the screen. There is functionality included here that allows you to Display, Forward, Print, Sort and Filter the IDocs on this list. Note that if you Forward an IDoc from this screen you will no longer see that IDoc in this folder however you can still see the IDoc under the Grouped According to Content folder as well as in the Workflow Outbox Forwarded Items folder.