30 December, 2007 at 5:00 am
· Filed under EDI
How Basis troubleshoot IDOCS error error status 51 and status 68
Steps:
-
From Basis point of view, the technical problem that we have to look at is the transmission of the IDOC.
-
Firstly we execute BD87.
-
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.
-
For status 68 error, we do the same thing. Use BD87 ‘ Enter 68 on IDOC status.
-
As there is no error message. We double click ‘Without error message’ to see the IDOC details.
-
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.
-
Look at transaction SM58 for any hanging or error tRFC (most of IDOC use tRFC/Asynchronous). If any check the error message.
-
If the partner type is LS which is logical system, you can check and test connection of RFC connection via SM59.
-
In this case, there is no error tRFC on SM59 which proves those error are not Basis issue.
Permalink
30 December, 2007 at 4:17 am
· Filed under EDI ·Tagged BAPI, BDOCS, EDI, IDOCS, RFC
What BDOCS and IDOCS.
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)
Permalink
30 December, 2007 at 12:12 am
· Filed under ABAP ·Tagged ABAP, DUMP, MESSAGE, se91, st22, TYPE, X
Permalink
30 December, 2007 at 12:11 am
· Filed under Job ·Tagged Error, Job, sp01
Most common SPOOL error encountered by BASIS. How do we resolve this issue?
Steps
- Execute SM37. You found an error Job. When you double click you found
- You saw the below error
- This error is caused by job spooler is not defined when job creation hence it picks up the job owner’s default output device.
- Since the default output device is no populated on master user record, the job log can’t find the print parameter.
- To resolve the issue, please populate the output device and select your preference for your SAP spool request via transaction code SU3.
- For Output device, you can choose one of SAP printer which has been defined in SAP (you can look at via transaction code SPAD)
- Recommendation: please do not select LOCL if you want to opt ‘Output immediately’. Moreover, this output device is not good for network performance
- Select ‘Output immediately’ if you want to immediate print for every spool request that you create in SAP. Recommendation: do not select this.
- 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:
Permalink
30 December, 2007 at 12:10 am
· Filed under User Maintenance ·Tagged create, maintenance, su01, user
How to create user in SAP
Steps
- Execute SU01
- Enter user name and press CREATE (notepad)
- Enter necessary details such as Firstname and Lastname
- Click on Logon Data Tab and enter password a password eg: enjoysap123
- Click Save (floppy disk icon). Now you can informed the user that his/her account has been created.
Permalink
26 December, 2007 at 2:24 am
· Filed under Database ·Tagged Database, db2, mssql, oracle, st04
What is it?
The hit ratio is a mean value that gives a snapshot of a short period of time before the analysis. This value should always be above 95%, even during periods of heavy workload. If the hit ratio is significantly below 95%, the data cache could be too small.
To check the hit ratio:
1. Execute ST04
2. If the hit ratio is below 95%, you will have to increase it.
Permalink
26 December, 2007 at 1:05 am
· Filed under News ·Tagged high, News, pay, salary, sap
From eweek.com
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
Permalink
13 March, 2007 at 4:36 pm
· Filed under Uncategorized ·Tagged MB52, MMbE, overview, Stock, warehouse
What T-Code should I use for stock and warehouse overview?
- Stock overview and history (MMBE)
- Warehouse overview (MB52)
Permalink
4 January, 2007 at 7:34 am
· Filed under Sap Script ·Tagged change, sap, script, SE71, se93
1. Firstly open SE71. Enter the Form name.
2. Click change
3. Click on Page window
4. You can now change the attributes.
5. Only those highlighted in blue on page window will
enable you to change the attributes
6. To select or highlight, just double click any entries on page window
7. Once you are satisfy with the new changes click on
8. Form > Activate
9. To change the SAP script, click on ‘text element’
10. Now go to > goto> change editor for a better view
11. Here you can perform your adap changes.
12. Once you click save, a transport number will be generated.
13. Remember the transport number as subsequent changes will be save
directly to the new transport request
14. Go to SCC1 to import to different client in the same ever
15. Go to STMS to import to different client in different server
16. To test your new program, go to SE93
Permalink
4 January, 2007 at 7:19 am
· Filed under Master Data ·Tagged FBL1N, Master Data, ORB2, vendor list
Enter OBR2 to open deleting master data
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
Permalink
Older Posts »
