Steps:

1. From Basis point of view, the technical problem that we have to look at is the transmission of the IDOC.
2. Firstly we execute BD87.
3. Enter IDOCS status 51 and press enter. You shall see below screen shot. As we can see, error
   “Status 51″ are application or data related error.
   
4. For status 68 error, we do the same thing. Use BD87 ‘ Enter 68 on IDOC status.
   
5. As there is no error message. We double click ‘Without error message’ to see the IDOC details.
   
6. Go to status record to see what has happened with the IDOC process. As seen in the picture, the error 68 was because the IDOC had status 51 which is caused by application/data error.
   
7. Look at transaction SM58 for any hanging or error tRFC (most of IDOC use tRFC/Asynchronous). If any check the error message.
8. If the partner type is LS which is logical system, you can check and test connection of RFC connection via SM59.
9. In this case, there is no error tRFC on SM59 which proves those error are not Basis issue.

IDOCS are intermediate documents (normally in text file format) which are used as between SAP and non-SAP system. In a real work, a company may have different systems. So IDOCS are used as a vehicle encapsulate these data so these systems can exchange information.

Eg: During POS, IDOCS are generated and it includes price, number of items, description and etc. Then its transfer ASYNCHRONOUSLY to SAP system. Think of it like excel exporting a file to *.csv and then Outlook can read the *.csv file.

BDOCS on the other hand, is the CRM version of IDOCS. BAPI is another SAP intermediate documents but its used for SYNCHRONOUS transactions.

In the computer world, we called such activity as ELECTONIC DATA INTERCHANCE (EDI)

Steps:

1. Execute ST22 > Double click on any entries
   
2. Go to Source Code Extract
   
3. Locate “>>>>” and you will see Message X041 in this example. Take note of the Message class and number.
   
4. Now open SE91. Enter the details we found from Source Code Extract in ST22:
   -Message Class: RD
   -Message Number: 041
   Click Display
   
5. Here, we determine what the message indicates
   
6. Now we know that the ABAP Dump message type X is due Extract Structure does not exist at the time of transport. Informed the ABAP consultant or Function consultant about this issue.

Steps

1. Execute SM37. You found an error Job. When you double click you found
2. You saw the below error
   
3. This error is caused by job spooler is not defined when job creation hence it picks up the job owner’s default output device.
4. Since the default output device is no populated on master user record, the job log can’t find the print parameter.
5. To resolve the issue, please populate the output device and select your preference for your SAP spool request via transaction code SU3.
6. For Output device, you can choose one of SAP printer which has been defined in SAP (you can look at via transaction code SPAD)
7. Recommendation: please do not select LOCL if you want to opt ‘Output immediately’. Moreover, this output device is not good for network performance
8. Select ‘Output immediately’ if you want to immediate print for every spool request that you create in SAP. Recommendation: do not select this.
9. Select ‘Delete After Output’ if you want SAP to delete every spool that you create. Recommendation: do not select this. You can manage your spools e.g. printing, reprinting, deletion, etc via transaction code SP01 as below:

Steps

1. Execute SU01
2. Enter user name and press CREATE (notepad)
   
3. Enter necessary details such as Firstname and Lastname
   
4. Click on Logon Data Tab and enter password a password eg: enjoysap123
   
5. Click Save (floppy disk icon). Now you can informed the user that his/her account has been created.

To check the hit ratio:
1. Execute ST04

2. If the hit ratio is below 95%, you will have to increase it.

Salaries for SAP specializations increased 15.2 percent in 2006, according to research released in February by Foote Partners, a New Canaan, Conn., IT workforce research firm. Data from the first two quarters of 2007 suggests little abatement of this trend.

“Right now, anybody who is working in the SAP world, either with functional or technical skills, is doing great,” said Jim Lanzalotto, vice president of strategy and marketing for Yoh, a recruiting and outsourcing firm, based in Philadelphia. “The demands are for specialized skills, and if you’ve got to pick the right market to be a specialist in, the world of SAP is hot.”

ERP-related roles accounted for two of the best-paying IT jobs in the second quarter of 2007, according to the second quarter 2007 Yoh Index of Technology Wages, released July 23. SAP technical consultants came in first, with average hourly pay rates of $85.53, and ERP (enterprise resource planning) functional consultants came in eight dollars behind in second place, at $78.40 per hour.

more at http://www.eweek.com/article2/0,1759,2161806,00.asp

1. Stock overview and history (MMBE)
2. Warehouse overview (MB52)

If you get the below error this is due to existing data

Open FBL1N to check existing data

If you see this there are data, please reserver the entry