04.12.2015 Views

SAP ERP Financials and FICO Handbook

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

8 CHAPTER 1 INTERVIEW QUESTIONS AND ANSWERS<br />

amount of customer reports for their day-to-day use, they may want to include<br />

these reports in the <strong>SAP</strong> menu.<br />

Follow these steps to include a report menu in the <strong>SAP</strong> Easy Access Menu:<br />

1. Create your own area menu using transaction code SE43. While saving, you<br />

will need to assign the proper development class. The system will then create<br />

a transport request for your area menu.<br />

2. Now you will need to include your new area menu in the <strong>SAP</strong> Easy Access<br />

area menu (transaction code S000). Use transaction code SE43, enter transaction<br />

code S000 in the Area menu field, <strong>and</strong> click on the Change icon. A pop-up<br />

window will appear with three options: Extend, Change, <strong>and</strong> Cancel. Choose<br />

Extend <strong>and</strong> click on to create a new enhancement ID or use an existing<br />

enhancement ID.<br />

3. In the Edit Area Menu S000 screen, use the icons to add your area menu<br />

<strong>and</strong> save. The system will create another transport request.<br />

4. Now log off <strong>and</strong> log on again; you will find your new menu in the <strong>SAP</strong> Easy<br />

Access Menu.<br />

Similarly, you can extend the IMG menu through transaction code<br />

S_IMG_EXTENSION.<br />

10. What do you do with errors in batch data conversion (BDC) sessions?<br />

You use BDC to post data into <strong>SAP</strong> solutions with the help of the system.<br />

Sometimes, while posting data through BDC, the system will encounter problems<br />

<strong>and</strong> cannot post data. When the system encounters a problem, it will<br />

create BDC error sessions. The following are common reasons for BDC error<br />

sessions:<br />

■ Posting periods are locked<br />

■ Changes in master data, e.g., in general ledger (G/L) accounts, profit centers<br />

are locked for posting<br />

■ Changes in screen layout of <strong>SAP</strong> program<br />

These scenarios are only examples; there may be several reasons for errors. To<br />

process incorrect BDC sessions, you need to find out the reasons for these error<br />

sessions. The easiest way to do this is to analyze the BDC log. In transaction code<br />

SM35, select the BDC sessions in question <strong>and</strong> click on the log. The Batch input:<br />

Log Overview screen will appear; double-click on any of the rows of the Log Overview<br />

tab to see an error screen. After analyzing the error, fix it <strong>and</strong> process the BDC<br />

sessions.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!